Re: How To: Use another carriers HTC on VZW
 

EPST stuff? Yeah, I edited all that stuff, it's got my (PHONE)@vzw3g.com login on every relevant page, and "verizon" as the password (for some reason during my Cricket fiddling, I had "cricket" as the password). Cleared the secrets and they get reset (filled in) the next time I go back into EPST after rebooting/reconnecting.

DMU? Well, for some reason the "DMU" folder on it was empty when I went there (it was still doing the "Vision PCS" error before that, with an empty DMU folder), and I yanked the 10.key file off my VX8300.

I'm still really curious about that NVM_HTC file... like I said, OP is really unclear about what to do with NVM_HTC and that's got me thinking that I missed an important step. =\

But thanks for the reply!!! :)

Re: How To: Use another carriers HTC on VZW
 

if i already have a vzw apache can i flash it and not have to pay for a data plan?

Re: How To: Use another carriers HTC on VZW
 

password is "vzw"

No the supercid is only needed on certain bootloaders that don't work with NoID RUU namely 2.04 and 2.05 and is only needed to get the other carriers rom on there in those cases. You must have missed something redo the steps I outlined in the first post over. I've done many of these and never once gotten a sprint error unless my M.IP wasn't correct. Not to mention the fact you have esn cloned it and may/will cause many data authentication errors once you get it working.

Re: How To: Use another carriers HTC on VZW
 

"vzw"? Really? I'd been using "verizon" on my VX8300 with hax'd tethering programming for its DUN connection...

I'll give that a try though and post back with the results! Still dying to know where it's getting this "Vision PCS" error from though...

Re: How To: Use another carriers HTC on VZW
 

Aha! I think I found where my errors are coming from!

In EPST, under M.IP Customer Profile 1, I have what appear to be some old Sprint settings with some VZW stuff mixed in...

Enable Profile: Enable
NAI: (NUM)@vzw3g.com
MN HA SPI Set: Enable
MN HA SPI Value( Hex ): 4D2
MN AAA SPI Set: Enable
MN AAA SPI Value ( Hex ): 4D2
Reverse Tunneling Preferred: Enable
Home Address: 0.0.0.0
Primary HA Address: 68.28.49.** (iptools.com shows this is a Sprint PCS IP)
Secondary HA Address: 68.28.57.** (same)
HA Shared Secret: (blank)
AAA Shared Secret: (blank)
DMU Public Key(PKOID): 0
MN Authenticator( Hex ): 0

(All spacing and typos preserved, lawl)

I take it this is probably where my error is coming from? I'll try DUN again with the "vzw" password (on the security page under "HDR AN AUTH Password(LONG)" and "PPP PASSWORD")... but I'm certainly curious about those old Sprint values in the Customer Profile 1... everything under Default Profile matches OP's post though.

edit: Hahahaha... under M.IP Settings, Active Profile was set to "1" (this messed up one). It looks like none of those settings saved properly! Therein probably lies my problem. Okay, well, time to give it a good ol' try once again!

Re: How To: Use another carriers HTC on VZW
 

Nope! Still exactly the same Vision PCS error, exactly the same sequence of events, exactly the same everything. :(

Augh, what's wrong with this stupid thing?

edit: Also, the ESN is from one of my own phones and I'd smash the original into little bitty pieces to make sure it never turns on again, if I weren't hoping to use that phone for anything else in the future. So I shouldn't get any authentication errors (I would think...!) since I'm extra careful to never turn that phone on! Hey, if I could get Verizon to give me the VCast package and ignore that my Apache's ESN isn't VCast capable... I'd keep its original ESN. I figure there's no legitimate harm in swapping two of my own phones... =\

Still, really wondering how it knows anything about Sprint after all this flashing and programming! :(

edit: OK, I skipped the PRL step because I swore I did that either with earlier flashing or with *228 option 2, and the phone functionality is working fine. But I'm now trying it again with the included PRL from OP...

edit: Nope. Same old same old. It did fail much faster this time though... dialing -> "!" in title bar -> Vision PCS error -> "Your username or password is wrong". :(

Re: How To: Use another carriers HTC on VZW
 

Mip profiles are MIP Profile
Number of profiles: 6
Active user profile index: 0
MIP_MODE: Mobile IP Prefered
MIP Reg Retries: 2
MIP Reg Retry: 1750 ms
MIP Pre-Reg Timeout: 0
Mobile Node-HA: Enable
Send A Reg: Disable
Dormant Handoff Opt: Enable

MIP Default Profile
Enable Profile: Enable
NAI: mynumber@vzw3g.com
MN HA SPI Set: Enable
MN HA SPI Value: 12C
MN AAA SPI Set: Enable
MN AAA SPI Value: 0
Reverse Tunneling: Enable
Home Address: 0.0.0.0
HA Shared Secret:
AAA Shared Secret:
Primary HA Address: 255.255.255.255
Secondary HA Address: 255.255.255.255
DMU Pub Key: 10
MN Authenticator: 0

Do you have values for Ha and AAA? Password is not "vzw" under security tab in epst but under the connections menu if you need to manually create a data profile of dial string #777 username is your mdn@vzw3g.com and pass is vzw. Under security the passwords are your PPP passwords not "vzw".

Re: How To: Use another carriers HTC on VZW
 

Alright, everything there is right, but I don't understand what you mean by "the passwords are not 'vzw'"... if they're not "vzw" then... what are they? Usually that's how it goes... "it's not this, it's that" ;)

I mean, do I leave them blank then? Not "vzw" but just, blank?

edit: I tried putting the DUN username/password as "dongs/nothing" and guess what? Exactly the same error... what could this mean...? :(
edit: ^^ In the Windows connection options, that is. Not EPST. EPST at the moment is:
Security:
HDN AN AUTH User Id(LONG): (Phone)@vzw3g.com
HDN AN AUTH Password(LONG): (blank)
PPP USER ID: (Phone)@vzw3g.com
PPP PASSWORD: vzw

(where "(phone)" is in the format 5551234567)

M.IP Settings:
(Same as OP)

M.IP Default Profile:
(Same as OP, blank secrets)

M.IP Customer Profile 1:
(Same as Default Profile & blank secrets)

M.IP Customer Profile 2 through 6:
(Same as OP except...)
MN HA SPI Set: Disable
MN HA SPI Value( Hex ): 0
MN AAA SPI Set: Disable
MN AAA SPI Value ( Hex ): 0
Reverse Tunneling Preferred: Disable
Secondary HA Address: 0.0.0.0
DMU public key(PKOID): 0

Re: How To: Use another carriers HTC on VZW
 

[quote=Falcon4;666885]Alright, everything there is right, but I don't understand what you mean by "the passwords are not 'vzw'"... if they're not "vzw" then... what are they? Usually that's how it goes... "it's not this, it's that" ;)

I mean, do I leave them blank then? Not "vzw" but just, blank?

edit: I tried putting the DUN username/password as "dongs/nothing" and guess what? Exactly the same error... what could this mean...? :(
edit: ^^ In the Windows connection options, that is. Not EPST. EPST at the moment is:
Security:
HDN AN AUTH User Id(LONG): (Phone)@vzw3g.com
HDN AN AUTH Password(LONG): (blank)
PPP USER ID: (Phone)@vzw3g.com
PPP PASSWORD: vzw <--- that would be true if verizon was a Simple IP network like cricket.

They are unique keys. I would suggest changing your esn back to its original one and using *228 option 3 to esn change it to your account. Call tech support and ask for a "dmu reset" and if that doesn't fix it request that they change you to "IS-95" and then back and that will rebuild your keys correctly.

Re: How To: Use another carriers HTC on VZW
 

Well hell's. If I switch my ESN back, I can't get VCast and I may as well not even have data access... VZW charges way way way way way too much for data access on PDAs...

You think that if I switch it back, activate it, and get data to at least connect (on the $0 pay-per-KB plan), then switch it back to my VX8300's ESN and activate VCast, that would actually work? I mean I know it's not the most honest of things, but damnit they've got me locked in a contract and I'd've jumped to Cricket like jumping out of a sinking ship by now, if not for the contract.

I'll try switching it back though... I've noticed another oddity, I haven't gotten any of Verizon's "free texts" (like minutes used when calling #MIN), but I can still receive texts specifically sent to me. I wonder if that's the reason for the weirdness...