• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root WTF! WTF! WTF! my msl code is "0:00"

33colburn

Newbie
I had my phone rooted and removed some apps and it bricked. So after flashing several roms I cant get into my spc menu because I don't know the msl code. After a terminal emulator command it said my msl code is "0:00" without the quotes. The problem is even if I enter that figure it won't unlock. Also cant get phone to be found by qpst. I need some help. Phone is sch-r720 running cyanogenmod 7.2 RC1 beta 2. Please help have no phone. I am currently disabled and can't afford a new phone.

TIA.
:confused:
 
Search MeidConverter in Google. ;) then use the looooong Meid number. It'll give you your SPC CODE

Take that and convert it to get your spc

You Can Find Your ESN Or MEID Under The Battery!!!!

The problem is not finding it. I did what all of you have suggested and got the spc/msl number converted but it didn't work when plugged into the phone. This is a cricket phone and msl used to be 333333. but somehow the spc/msl got erased during flashing and now I cant program the phone. I have the drivers installed on a windows vista 32bit computer and it finds it. I can also install the 2.3.6 update via the samsung upgrade program but I cannot get QPST to find the phone to program or read spc/msl code. I tried the android app Get my MSL and used the terminal emulator and both return a code of "0:00" but when i type that in it doesn't work either. So 000000, 111111, 333333, 123456, and the converted msl from the web you suggested don't work. I believe that somehow I have to program in an MSL number but don't know how since QPST won't recognize the phone even thought other programs do and Windows device manager shows it. HELP ME AAAHHHH!
 
Ok go to the return to stock tread and flash that then try the spc to see if it will work my old ascend used to be real picky when I was run cm on it
 
Ok go to the return to stock tread and flash that then try the spc to see if it will work my old ascend used to be real picky when I was run cm on it

Yes, I already did that and no luck. I followed the guide from the ACS return to stock 2.3.4 thread and also tried ugrading to 2.3.6 and I found a nandroid another guy had posted of a Cricket stock rom 2.3.4 and tried that. All of the roms install fine but none of them allow me to get into programming mode. All of them return a spc/msl code of "0:00". I'm thinking that maybe "0:00" is what gets returned if the spc/msl is blank??? I think the only solution is to upload an new spc/msl code to the phone through QPST but I can't get the program to recognize the phone. I do have a QPST backup of the original stock settings I had from Cricket I would like to upload If I could get QPST ver. 2.7 366 and 355 to recognize the phone. Maybe someone could help me with getting connected to QPST???

TIA.
:o
 
androidforums.com/optimus-m-all-things-root/407952-guide-meid-thread-didnt-restore-service-my-phone-000-000-xxxx-help.html try this op..
 
androidforums.com/optimus-m-all-things-root/407952-guide-meid-thread-didnt-restore-service-my-phone-000-000-xxxx-help.html try this op..

I tried this as well as all other suggestions in this thread. I cannot get qpst to see the phone on the port. ADB works and I am able to install CWM or stock rom via odin so I know it is not a driver issue. I get a returned value of "0:00" for my msl/spc code. I am not able to program the phone in order to get service working again. I have all values needed to program but I just cant get the phone into programming mode because I don't have a valid msl/spc. My phone says its current # is 000-000-xxxx. I could use some advice.

Please help me. TIA.

:confused:
 
i just went through a similar problem with qpst. turns out my drivers somehow got fubar'ed. try to:

uninstall the samsung drivers from your computer
if its a driver package uninstall it through control panel>programs and features, otherwise plug in your phone, go to computer>device manager and uninstall the drivers one at a time, windows 7 should have 5 drivers for the admire.
make sure your phone is not plugged into the computer
reboot the computer
download the admire drivers: Support - More Cell Phone Providers SCH-R720 | Samsung Cell Phones
and install them
plug tthe phone into the computer and WAIT while windoze configures the drivers
after the pc pops up the msg about drivers being installed sucsessfully you should be good, but if this doesnt work, look at the driver install window and let me know where it fails. if i remember right the problem was with the wdm diagnostic port driver, or something like that anyway...
 
i just went through a similar problem with qpst. turns out my drivers somehow got fubar'ed. try to:

uninstall the samsung drivers from your computer
if its a driver package uninstall it through control panel>programs and features, otherwise plug in your phone, go to computer>device manager and uninstall the drivers one at a time, windows 7 should have 5 drivers for the admire.
make sure your phone is not plugged into the computer
reboot the computer
download the admire drivers: Support - More Cell Phone Providers SCH-R720 | Samsung Cell Phones
and install them
plug tthe phone into the computer and WAIT while windoze configures the drivers
after the pc pops up the msg about drivers being installed sucsessfully you should be good, but if this doesnt work, look at the driver install window and let me know where it fails. if i remember right the problem was with the wdm diagnostic port driver, or something like that anyway...

ok i will try tomorrow and getb back with you. thank you.:)
 
Well, I gave up. I flashed cm7.2 rc0 and everything works just no phone. ADB works, Driver install ok, can flash cwm, stock odin or put a stock rom on. Did the back to stock and didn't work. I cant get qpst to find it and IT IS NOT A DRIVER PROBLEM. I have retrieved the spc/msl and it reads "0:00" I cant get phone to program because I cant get msl code to work. I tried the online msl converter using me serial number. I tried using Terminal Emmulator and several other methods and all return MSL as "0:00" So out of interest I thought I would post 1 more time to see if anyone has found a solution. BTW I just bought a new phone since I couldn't fix. I am intrigued if there is a solution just for personal knowledge gain as this is the 1st android problem I could not fix. BTW I have tried all solutions already posted without success.

TIA.
 
I have no idea what to ttell you man, you may meed to send it back to Cricket and say it doesn't work
 
I'm on my phone atm so can't post a direct link, but check out my thread in the vitality forums on the corporate flash. That may be your ticket. After flashing, try *228.
Good luck!
 
Back
Top Bottom