Guest cellar Posted August 13, 2006 Report Posted August 13, 2006 (edited) I have a T-Mobile SDA (USA version) that I'm trying to upgrade to i-mate SP5m firmware. Followed another unlocking guide instead of mfurse 's Guide to Upgrading Qtek 8310 to the Latest (2.0.9.0) AKU2 ROM cuz modaco was returning blank pages at the time ;) and skipped/changed order of some of the steps. Specifically, I: Changed "00001001" value to 1 (decimal) (recovery note: default is 2) Changed "00001005" value to 40 (decimal) (recovery note: default is 16) rebooted ran SDA_ApplicationUnlock.exe rebooted ran cert.cab rebooted ran SPVServices.exe; SIM unlocked & set SuperCID rebooted Phone is now app and sim unlocked, but the CID unlock won't "stick." Everytime I go through the CID unlock process in SPV-Services, it reports success, but then when I check it again (before or after reboot) it shows Current CID: 0800313131313131313100000000000000000000000000000000000000000000 Here's the rest of the info: Technical details: Now: 160 = 7290075f382c3b85d7a5ac5c8bf45589ed53ac8089610897ed53ac8089610897, 160 = e191cea4100391a0 Chg: 160 = 7290075f382c3b85d7a5ac5c8bf45589ed53ac8089610897ed53ac8089610897, 160 = e191cea4100391a0 I've tried going through this again in the order suggested by mfurse, and a couple of other ways, same result. I just did this a few days ago to another phone and upgraded to Qtek 8300 firmware no problem. After the upgrade, the other phone showed the same Current CID as above, but I was able to reset it following mfurse's steps. Any suggestions anyone? I've spent about 3 hours rebooting re-unlocking etc. without success.... :) Edit: FWIW, I did try "Accessories > Clear Storage" to no avail. Edited August 13, 2006 by cellar
Guest cellar Posted August 14, 2006 Report Posted August 14, 2006 OK, does anyone know how I would manually find and edit the CID?
Guest merwin Posted August 15, 2006 Report Posted August 15, 2006 Phone is now app and sim unlocked, but the CID unlock won't "stick." Everytime I go through the CID unlock process in SPV-Services, it reports success, but then when I check it again (before or after reboot) it shows Current CID: 0800313131313131313100000000000000000000000000000000000000000000 I believe that is the correct CID... if you notice in that sequence of numbers there is 31 31 31 31 31 31 31 31. That is hex for 11111111 :-)
Guest cellar Posted August 16, 2006 Report Posted August 16, 2006 I believe that is the correct CID... if you notice in that sequence of numbers there is 31 31 31 31 31 31 31 31. That is hex for 11111111 :-) Doh, good eye! Wasn't looking for ascii. :) Also sorta expected it to tell me it's already SuperCID (like it does when you go to SIM unlock a phone already unlocked). Anyway, I'll go ahead and try firmware update again and see if it works...
Guest grumpy_old_technobyte Posted August 17, 2006 Report Posted August 17, 2006 I have a T-Mobile SDA (USA version) that I'm trying to upgrade to i-mate SP5m firmware. I tried the same thing to no avail a couple times too with the SDA. No problems ever flashing rom on the SmT5600. The latest sp5m rom 2.6.331.2 installer always crashed after 30 seconds and terminates the activesync connection. My error message was invalid operator id. I thought it was the SuperCID also but I can install other software from other carriers like Cingular ClearVue Suite and Im running on a Cingular Sim. It might be the installer giving you errors.
Guest cellar Posted August 22, 2006 Report Posted August 22, 2006 I tried the same thing to no avail a couple times too with the SDA. No problems ever flashing rom on the SmT5600. The latest sp5m rom 2.6.331.2 installer always crashed after 30 seconds and terminates the activesync connection. My error message was invalid operator id. ... It might be the installer giving you errors. Yeah, that happened the one time I tried it, which is why I really thought the SuperCID wasn't sticking. Tried it again after fresh boot on computer and hard boot (from removed battery) on SDA, i-mate firmware installed fine. My thought is that the installer gets confused by having multiple Tornado devices connecting to the same computer via ActiveSync (sounds like you were doing that too). Or that the extra registry changes in mfurse's guide are really necessary. In any case, it upgraded eventually. :D
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now