SPC/MSL issue... Please Help!
 

Phone: Qwest PPC6700 flipped to Cricket

Problem: I had prepped the phone to be programmed OTA. I hit *228 and nothing. It then dawned on me that the SPC code was not the typical 000000 on this phone and that when the OTA system was trying to unlock the phone for NAM programming, it was failing because by default Cricket uses 000000.

At that point I went ahead and fired up QPST and the EFS explorer and found my nvm_security file and went ahead to set the SPC to 000000... But in a moment of what can only be described as complete idiocy... I set the hex to 00 00 00 00 00 00 rather than 30 30 30 30 30 30!!!

Needless to say rather than the 000000 I wanted I now have a broken SPC code.

What I need help with:I need a way to "force" the correct nvm_security file back onto the phone. I had save a copy of it on my PC in its correct form and need a way to get it on the phone. Normally you can use QPST or any other "normal" solution... The problem is they all require the SPC in order to write to the phone. Kind of a catch 22... I need the SPC to fix the SPC!

Is there anyone out there who knows of anyway to force the file on there or where I may go to get the directory unlocked?

Any ideas will be appreciated!
Maddog~

*EDIT*
Perhaps a better way to look at this would be to ask it this way:

Lets say that the nvm_security file becomes corrupt and is no longer useful. You are no longer able to enter an SPC to program the phone. Is there a way to replace this file with a new non corrupted version WITHOUT having to enter the code?

Did you try to read the file system with bitpim? Go to the NVM forlder and open NVM_SECURITY file. In there the SPC will be posted as ******.00000000 If this doesn't work try out cdma worshop. You can download that for free as a trial. The only thing is you have to set the COM port somewhere between COM2-COM6 I think. I usually use COM4

boy u look like u r in a pickle/ maybe u can get your new spc code with this and do it right


Two different ways to get MSL:

Method A:

* Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
* Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
* Check to see that the file \Temp\ATDbg0.txt has been created.
* Return the values back to what they were (most likely 0) waiting the same amount of time as above.
* Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:

Code:

11:9:3 Tx:AT+HTC_RMSL=0\r
11:9:3 Rx:+HTC_RMSL: 354201\r\n0\r
11:9:3 Tx:AT+HTC_ROTKSL=0\r
11:9:3 Rx:+HTC_ROTKSL: 216112\r\n0\r

* The numbers next to the Rx: +HTC_RMSL line should be your MSL... I do not know what the ROTKSL is for, but included it in the snippet incase someone knows.

Method B:

I fixed it using CDMA workshop a couple of days ago. Just didn't get a chance to post. Apparently it is designed to fix my exact problem, lol!

Maddog~