Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
To get the donor password the donor needs to be connected, might be a typo in the guide.So I am in step 4 of the guide using QXDM. I have my doner incognito hooked up to com 6. I activated the port in QXDM and ran the commands in the guide. I do not see the HA Shared password in the results generated. I am also a bit confused, in this guide I am assuming he means to have the doner phone hooked up. But in the PDF guide at this steps he mentions to choose the HTC EVO port at this step. Which is correct?
Thank you in advance for any help you can provide. I can't yet attach images. so here are the results I am getting.
13:33:59.778 Password 01f2030f5f678ff9
13:33:59.778 RequestItem "Send Security Password Request" 0x01 0xf2 0x03 0x0f 0x5f 0x67 0x8f 0xf9
13:33:59.887 DIAG TX item:
13:33:59.887 Password[0] = 0x01
13:33:59.887 Password[1] = 0xF2
13:33:59.887 Password[2] = 0x03
13:33:59.887 Password[3] = 0x0F
13:33:59.887 Password[4] = 0x5F
13:33:59.887 Password[5] = 0x67
13:33:59.887 Password[6] = 0x8F
13:33:59.887 Password[7] = 0xF9
13:33:59.887 DIAG RX item:
13:33:59.887 Password Result = Correct
13:34:34.137 Requestnvitemread ds_mip_ss_user_prof
13:34:34.137 DIAG TX item:
13:34:34.137 index = 0
13:34:34.137 mn_ha_shared_secret_length = 0x00
13:34:34.137 mn_ha_shared_secret[0] = 0x00
13:34:34.137 mn_ha_shared_secret[1] = 0x00
13:34:34.137 mn_ha_shared_secret[2] = 0x00
13:34:34.137 mn_ha_shared_secret[3] = 0x00
13:34:34.137 mn_ha_shared_secret[4] = 0x00
13:34:34.137 mn_ha_shared_secret[5] = 0x00
13:34:34.137 mn_ha_shared_secret[6] = 0x00
13:34:34.137 mn_ha_shared_secret[7] = 0x00
13:34:34.137 mn_ha_shared_secret[8] = 0x00
13:34:34.137 mn_ha_shared_secret[9] = 0x00
13:34:34.137 mn_ha_shared_secret[10] = 0x00
13:34:34.137 mn_ha_shared_secret[11] = 0x00
13:34:34.137 mn_ha_shared_secret[12] = 0x00
13:34:34.137 mn_ha_shared_secret[13] = 0x00
13:34:34.137 mn_ha_shared_secret[14] = 0x00
13:34:34.137 mn_ha_shared_secret[15] = 0x00
13:34:34.137 mn_aaa_shared_secret_length = 0x00
13:34:34.137 mn_aaa_shared_secret[0] = 0x00
13:34:34.137 mn_aaa_shared_secret[1] = 0x00
13:34:34.137 mn_aaa_shared_secret[2] = 0x00
13:34:34.137 mn_aaa_shared_secret[3] = 0x00
13:34:34.137 mn_aaa_shared_secret[4] = 0x00
13:34:34.137 mn_aaa_shared_secret[5] = 0x00
13:34:34.137 mn_aaa_shared_secret[6] = 0x00
13:34:34.137 mn_aaa_shared_secret[7] = 0x00
13:34:34.137 mn_aaa_shared_secret[8] = 0x00
13:34:34.137 mn_aaa_shared_secret[9] = 0x00
13:34:34.137 mn_aaa_shared_secret[10] = 0x00
13:34:34.137 mn_aaa_shared_secret[11] = 0x00
13:34:34.137 mn_aaa_shared_secret[12] = 0x00
13:34:34.137 mn_aaa_shared_secret[13] = 0x00
13:34:34.137 mn_aaa_shared_secret[14] = 0x00
13:34:34.137 mn_aaa_shared_secret[15] = 0x00
the aaa is a 32 digit alphanumeric number.So the weird thing is that I was able to gather all 4 Nv items from the Incognito w/o issue and saved those 4 files. I was also able to gather the NAM1/2 info and save that as well in the prior steps, so i know my phone had to be unlocked successfully with the spc code i had entered in CDMA prior to all that. So basically I am unsure as to why i can't get this password, I believe I have the AAA password, as the guide says its in the NV 466 file I saved. So I think i am only missing the HA shared pw
the aaa is a 32 digit alphanumeric number.
lolNot to split hairs with you optimus, you know your stuff but...
The aaa is a 32 character alphanumeric string.
Just rubbing it in, pun intended.

For the prevail you just need to use the default samsung password in cdma ws then the spc should show up in the box.where should I start my spc scan for the prevail the incognito is 0363 not sure for prevail?
That is normal, happens with every write to phone I have done on the evo.New guy here flashed from sprint to boost... last night everything worked for a second then i got error 67 and got authentication code could not be verified when making data call.
the NV items have been written the NAMs have been written ESN and meid is good. NAIs look good. the only thing i can think of is when i write the NAMS and i get an error NV_UE_IMEI_I status: NV_READONLY_S
Anyone know what that means?
i would really like to get this working any help is appreciated
ok so i moved you to the boost guide thread, where you can get better help.New guy here flashed from sprint to boost... last night everything worked for a second then i got error 67 and got authentication code could not be verified when making data call.
the NV items have been written the NAMs have been written ESN and meid is good. NAIs look good. the only thing i can think of is when i write the NAMS and i get an error NV_UE_IMEI_I status: NV_READONLY_S
Anyone know what that means?
i would really like to get this working any help is appreciated
thanx optimus for responding. rock on guys!!!!!That is normal, happens with every write to phone I have done on the evo.
2 questions, 1 did you make sure the meid was correct. and 2 did you make sure the donor phone was not turned on.
You can never have both phones on and trying to get signal at the same time.

You dont want to follow the old method of clearing the memory locations.i have been at this for a week now... everything goes as planned but no luck... am i missing something in clearing the meid and esn? i have tried the list provided, the search method provided and this guide.... my esn and meid never change... my phone number and current username change to my donor phone but mied stays the same... don't know if i'm clearing everything correctly or not.... i am about ready to throw in the towel....
*edit - if i can convince the wife, (yeah right), i'm going to spend the money outright for the GS3 and have boost activate that
i have been successful in clearing esn, i will follow the 3d directions and attempt the meid...
* edit - so far so good except i have no file "0" or "1943". going to pull each file and scan for meid...
Try this, dialer menu ##786# reset, phone will go back to basic factory settings, it will try to activate, dont let it, put the phone in diag mode connect up to qpst service programing profile 0 the nai will be the phones original meid@sprintxxxxx what ever right, change the meid to the donor meid@ and everything behind the @ leave the sameyes, figured that out eventually... rackin' my brain on this darn thing... finally got everything zeroed out and written but something is not sticking.... phone doesn't "reboot" after final write... hook back up and check settings, profile is back to 1, not zero... everything else looks fine, meid, esn, phone #.... gonna try again tomorrow...
Yes, that is usually from the AAA wrong, but I have seen that from the stupidest thingsif it ain't one thing, it's another. now i come up with "error code 67. registration failure. pcs vision username/password may be incorrect". what is this referring to? ha and aaa passwords?