Help with repairing TP2

[duff]

Wow, so glad I found this forum. Hopefully I can get some help here since mobile-files.us has way to many stupid rules. ;) I miss MF:(

Anyways, I am using a touch diamond as the donor to "repair" my tp2. I need my aaa shared secret password. So I used QXDM to read my hex key in nv browser item 01192. The strange thing is that about halfway threw the 32 digit hex key, I get 0x00. Is this normal? Because every time I try to write it with qpst, only half of the 32 hex key is written. It cuts off right where it has a 0x00 key in the middle. I thought that the 32 key would not have any 0. Is that right? If so, how can I fix this.

By the way I am using sprint.

[Dex]

for that key i suggest reflashing the shipped sprint rom to the fone if that doesnt work since ur on sprint take it to sprint and they can get it back to 100% for you

[cricketmodder]

you could just read that nv item using cdma workshop and see if it will read that way, and then convert it from hex to ascii

[duff]

for that key i suggest reflashing the shipped sprint rom to the fone if that doesnt work since ur on sprint take it to sprint and they can get it back to 100% for you

Thanks. I have flashed the shipped ROM, still have same problem. Closest sprint store is about an hour away, so I am trying to fix it on my own.

[duff]

you could just read that nv item using cdma workshop and see if it will read that way, and then convert it from hex to ascii

I'm sort of a noob with cdma workshop. Can I read it with cdma workshop 2.7? Can please tell me how?

[cricketmodder]

Should be able to, connect your phone to cdmaworkshop, send the spc and go to the memory tab, there you should have a NV items option and click read

[duff]

Ok, so I got it to read. But I'm still getting the same 0x00 key..

[cricketmodder]

first is 0000, last is ffff, then save it to a text file and search for 01192 in the text file, that should be what you are trying to get in qxdm

[duff]

So, for sure no 32 hex key should contain 0x00 right? Cause I haven't received a definitive answer on that yet.

[cricketmodder]

hmm that i dont know, but i do know the way qxdm works is sometimes you have to send the hex in format 0x30, 0x30, 0x30, etc

[duff]

ok, but if both programs are giving me the same hex key with the 0x00, does it probably mean its the correct 32 hex key. Because if it wasn't correct I wouldn't have evdo, right?

[cricketmodder]

i believe that is correct

[Dex]

i think the aaa shared secret is the word secret in all lower lol

[duff]

i think the aaa shared secret is the word secret in all lower lol

I've tried that, and keep getting wrong username errors. Also when using the original tp2 esn meid repair guide, it says to write the hex key.