Dead radios on Pac man Rom - Sprint Samsung Galaxy Note II

Hello all,
I hope someone can help. I had everything working great on Pac man Rom (cm10 based). I decided to flash the 4.2 keyboard and when I rebooted the phone, my radios were dead. No calls, no mobile data. I tried the terminal fix solution slick Rick posted in the paranoid android thread but it didn't work.
Does anyone know what I can do? Please help, thank you.
Sent from my SPHL-L900 using xda app-developers app

Have you tried flashing another rom or restoring an old backup?
Sent from my SPH-L900 using Tapatalk 2

mexiking713 said:
Have you tried flashing another rom or restoring an old backup?
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I have this exact problem. After using PAC-man ROM, even after doing a full wipe and everything, and going to ParanoidAndroid, I've still got nothing whatsoever.
I've since tried restoring to a previous ParanoidAndroid NANDroid, as well as ones for the PAC-man and even the stock TouchWiz ROM, all to no avail.
I have noticed that upon the first boot after attempting to restore one of these, a process I believe is called "com.android.phone" force closes.
I would greatly appreciate any help; for reasons I won't mention, I can't fully restore to stock until tomorrow or perhaps the next day. Before then, unless this can be fixed, my phone is completely and utterly useless to me.

Is your about phone > status normal or is there values missing or unknown. IMEI, phone#, MIN etc
I like to break stuff!

So don't be mad at me but I somehow got everything working again without having to go back to TW or even flashing anything new per se. I tried a bunch of things, from flashing older nandroids, to restoring my settings from TB, etc... Nothing worked. At one point, I decided to create a nandroid of my current setup, so that I could possible flash back to it after fixing the issue in TW. I then tried to reboot, but got stuck at boot animation. I went back into TWRP, restored from the previous nandroid (not the one I just made), and magically, everything was almost working. I say almost because I got my data and calls back, but the call app kept crashing in-call. I tried fixing permissions but that didn't help. After another reboot it stopped crashing. Again, I don't know why.
What's weird is that I had restored the nandroid that ended up "working" earlier and that didn't do it then...
I don't know what I did but I am operational once more. Sorry as I know this probably doesn't help anyone...at all.
Good luck to all!

-EViL-KoNCEPTz- said:
Is your about phone > status normal or is there values missing or unknown. IMEI, phone#, MIN etc
I like to break stuff!
Click to expand...
Click to collapse
OP says he no longer has a problem, but I do, so I'll proceed.
I'm not even entirely sure what all of these things are, but when I went through the About Phone, Data, and Debug menus came up with some things:
I don't have: Signal strength (-120dBm 99 asu), Mobile network type: unknown, Service state: Out of service, Roaming: Not roaming, Mobile network state: Disconnected, My phone number: Unknown, IP address: Unavailable.
I do have: User name, ICCID, MNC, MCC, P_REV, HTTPPD things, RTSP stuff, DSS Proxy IP, mmsc Proxy, SCM, EVRC-B, Vocode stuff, ESN, HA IPs, ICCID, MEID, and IMEI.
My device status is modified.
I think that I have an IMEI means that I'm not totally boned like (http://forum.xda-developers.com/showthread.php?t=1997150), but I'm still not sure what to do at the moment.
All of this is from the stock (albeit rooted) TW ROM NANDroid from before I'd done anything more with TWRP than this backup.
Where should I go from here?
EDIT: One thing I've tried to do is flash the TK8 modem, to no effect.

Finitesimal said:
OP says he no longer has a problem, but I do, so I'll proceed.
I'm not even entirely sure what all of these things are, but when I went through the About Phone, Data, and Debug menus came up with some things:
I don't have: Signal strength (-120dBm 99 asu), Mobile network type: unknown, Service state: Out of service, Roaming: Not roaming, Mobile network state: Disconnected, My phone number: Unknown, IP address: Unavailable.
I do have: User name, ICCID, MNC, MCC, P_REV, HTTPPD things, RTSP stuff, DSS Proxy IP, mmsc Proxy, SCM, EVRC-B, Vocode stuff, ESN, HA IPs, ICCID, MEID, and IMEI.
My device status is modified.
I think that I have an IMEI means that I'm not totally boned like (http://forum.xda-developers.com/showthread.php?t=1997150), but I'm still not sure what to do at the moment.
All of this is from the stock (albeit rooted) TW ROM NANDroid from before I'd done anything more with TWRP than this backup.
Where should I go from here?
EDIT: One thing I've tried to do is flash the TK8 modem, to no effect.
Click to expand...
Click to collapse
Ok this is what I did to fix this problem and it was the only thing that brought me back 100%
First you need your MSL. To get it download terminal emulator over wifi or thru pc and sideload it.
To get the MSL after you get terminal emulator installed: open dialer and type ##3282# then click edit. Type 000000 in place of the MSL then back out of dialer. Open terminal emulator and type getprop ril.MSL (case sensitive) and copy the 6-digit code thst shows on the next line.
Now that you have the MSL its time to fix the problem:
Open dialer again and type ##786# select reset and enter your MSL, let it do its thing and automatically reboot. Once it boots up your signal bars should be back and you should now have generic sprint info where all the unknown values are.
Now go to settings > activate device and let it do hands free activation.
After HFA finishes open dialer again and type ##72786# and select edit, enter your MSL. Now you need to enter your phone # and MIN in their respective fields. The MIN should be the same as your 10-digit phone # enter both with no spaces or symbols example: 0000000000 then back out of dialer and reboot. You should now be fully operational.
Basically what you are doing is master resetting the device and manually reprovisioning, reprogramming and reactivating your device to regain your missing NVdata
Edit: if for some reason your MIN isn't a match to your phone #(this happens rarely but does happen one of my lines has a different MIN than #) after you get everything else done, call sprint or hop on chat and ask them to reprovision your device and they will go over all the same steps with you ad I did but give you the proper value for MIN if its different than#. If it's the same the steps I listed above will have you fixed
I like to break stuff!

-EViL-KoNCEPTz-;367e65375 said:
Ok this is what I did to fix this problem and it was the only thing that brought me back 100%
First you need your MSL. To get it download terminal emulator over wifi or thru pc and sideload it.
To get the MSL after you get terminal emulator installed: open dialer and type ##3282# then click edit. Type 000000 in place of the MSL then back out of dialer. Open terminal emulator and type getprop ril.MSL (case sensitive) and copy the 6-digit code thst shows on the next line.
Now that you have the MSL its time to fix the problem:
Open dialer again and type ##786# select reset and enter your MSL, let it do its thing and automatically reboot. Once it boots up your signal bars should be back and you should now have generic sprint info where all the unknown values are.
Now go to settings > activate device and let it do hands free activation.
After HFA finishes open dialer again and type ##72786# and select edit, enter your MSL. Now you need to enter your phone # and MIN in their respective fields. The MIN should be the same as your 10-digit phone # enter both with no spaces or symbols example: 0000000000 then back out of dialer and reboot. You should now be fully operational.
Basically what you are doing is master resetting the device and manually reprovisioning, reprogramming and reactivating your device to regain your missing NVdata
Edit: if for some reason your MIN isn't a match to your phone #(this happens rarely but does happen one of my lines has a different MIN than #) after you get everything else done, call sprint or hop on chat and ask them to reprovision your device and they will go over all the same steps with you ad I did but give you the proper value for MIN if its different than#. If it's the same the steps I listed above will have you fixed
I like to break stuff!
Click to expand...
Click to collapse
Absolutely fantastic! My phone works again! Im even using it to type this message.
How important is it that my MIN be identical to my phone number? It's not, but my phone (calls, sms, data) works perfectly regardless.
Regardless, you are awesome. Thanks so much!

Finitesimal said:
Absolutely fantastic! My phone works again! Im even using it to type this message.
How important is it that my MIN be identical to my phone number? It's not, but my phone (calls, sms, data) works perfectly regardless.
Regardless, you are awesome. Thanks so much!
Click to expand...
Click to collapse
Only matters if they are supposed to be HFA will usually set those for u but I had the chameleon and HFA errors when I did mine and had to do them manually. My personal line the match but my work line they are different. That's how I knew theres a chance they aren't the same and if the MIN didnt work to just call sprint and ask to reprovision your phone :thumbup:
I like to break stuff!

For what it's worth, after a shut down and reboot my phone is having this problem again. None of my nandroids fix this. I'm on cm so I can't do the fix posted above.
Going to flash back to stock tonight when I get home and start from scratch.
Sent from my SPHL-L900 using xda app-developers app

-EViL-KoNCEPTz- said:
Only matters if they are supposed to be HFA (hands-free activation) will usually set those for u but I had the chameleon (what?) and HFA errors when I did mine and had to do them manually. My personal line the match but my work line they are different. That's how I knew theres a chance they aren't the same and if the MIN didnt work to just call sprint and ask to reprovision your phone :thumbup:
I like to break stuff!
Click to expand...
Click to collapse
Let me rephrase what I understood:
The hands-free activation that automatically initiates after the radios/modem/whatever are hard-reset will usually properly configure everything.
You had "chameleon errors". (What are chameleon errors? Were they caused by the same thing (PAC-man or another rotten ROM)?
You have two different Sprint handhelds; on one, the MIN and phone number match, on one, they don't.
If it's working, I'm good.
Regardless, thanks very much for helping me to restore my phone to proper working order!

Finitesimal said:
Let me rephrase what I understood:
The hands-free activation that automatically initiates after the radios/modem/whatever are hard-reset will usually properly configure everything.
You had "chameleon errors". (What are chameleon errors? Were they caused by the same thing (PAC-man or another rotten ROM)?
You have two different Sprint handhelds; on one, the MIN and phone number match, on one, they don't.
If it's working, I'm good.
Regardless, thanks very much for helping me to restore my phone to proper working order!
Click to expand...
Click to collapse
From going back to ljc from lk8 you get HFA on every boot and chameleon apk force closes randomly
Edit: amd yes if you're working you're good. The HFA got your provisioning done correctly. I had to manually do mine from HFA failing part way thru. And yes there are 5 lines on my account 4 all have the same MIN as phone# one has a different MIN same area code entirely different last 7 digits
I like to break stuff!

mikelav456 said:
Hello all,
I hope someone can help. I had everything working great on Pac man Rom (cm10 based). I decided to flash the 4.2 keyboard and when I rebooted the phone, my radios were dead. No calls, no mobile data. I tried the terminal fix solution slick Rick posted in the paranoid android thread but it didn't work.
Does anyone know what I can do? Please help, thank you.
Sent from my SPHL-L900 using xda app-developers app
Click to expand...
Click to collapse
when radios is dead u cannot accces modem exmpl : ##anyHiddenDial#
try this one on terminal emulator on your device :
"su [enter]
rm[space]-r[space]/sdcard/android [enter]
reboot [enter]"
after that reflash ur number and username data packet via ur favorite way. i prefer via qpst 378 or DFS 4...
happy try...i hope it will help u man...

-EViL-KoNCEPTz- said:
And yes there are 5 lines on my account 4 all have the same MIN as phone# one has a different MIN same area code entirely different last 7 digits
Click to expand...
Click to collapse
That's interesting. My MIN is completely unrelated to my phone number, and also to my area code, and also to any place's area code I've ever lived.
There seems to be no similarity whatsoever. Hm.

Related

[FIX] IMEI Backup/Restore using QPST

With the ongoing issues surrounding lost IMEI's and lost phone functionality due to a lost IMEI. It may be in all of our interests to backup the NV Data to our phones. I have provided in this thread information on how to do so. Hope it helps =)
http://forum.xda-developers.com/showthread.php?t=1801997
DX
Thanks for the guide. I got as far as starting the backup in QPST, but got an error.
SPC given could not unlock the phone. The phone will not respond for 10 seconds.
Guess I need to try on an insecure kernel, but can't find one for our phone. The two that used to be on samsung-updates.com are dead links as of right now.
I got the same SPC lock error.
I believe that is because you need the MSL. This should work for you phone credit to shiftr182 for this guide.
http://forum.xda-developers.com/showthread.php?t=1745888
DX
Peoplearmy said:
I believe that is because you need the MSL. This should work for you phone credit to shiftr182 for this guide.
http://forum.xda-developers.com/showthread.php?t=1745888
DX
Click to expand...
Click to collapse
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be read."
Tried on both stock and insecure kernel. Tried PRL/Profile update + reboot for kicks, no change. Not sure what else to try, googling doesn't help.
edit: Do you know of anyone on Verizon that has successfully backed up? I checked their forum and they only have a guide for doing the IMEI injection. I'm assuming the 7 successful Verizon restores you have listed in your original thread are restores by injection and not from a backup?
Philosuffer said:
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be read."
Tried on both stock and insecure kernel. Tried PRL/Profile update + reboot for kicks, no change. Not sure what else to try, googling doesn't help.
edit: Do you know of anyone on Verizon that has successfully backed up? I checked their forum and they only have a guide for doing the IMEI injection. I'm assuming the 7 successful Verizon restores you have listed in your original thread are restores by injection and not from a backup?
Click to expand...
Click to collapse
That is correct 6 were through injection 1 was through a backup. There are however plenty of Verizon folks who were able to do the backup without any problems. They also however didn't need their MSIL and were able to use the default spc of 000000. I will have to dig a bit deeper for Sprint. I prefer us all safe and not just 3 carriers. Thank you for your efforts
DX
Are there any reports of this happening to sprint users? Jw
Sent from my SGH-I747 using Tapatalk 2
did anyone try...
The option in mskips toolkit. Cant say wheather it works(as I haven't had to restore it) but it does a efs backup now. I know the imei isn't there anymore (don't know that I necessarily believe that) but don't hurt to try.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
bgolden84 said:
Are there any reports of this happening to sprint users? Jw
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Haven't seen any with this phone. Have seen cases on other sprint phones tho, so I'd definitely say it can
Backup work for me with the default 000000, but that being said the only way i was able to get my MSL was an app "Get My MSL" from google play
this guilde didn't work for me http://forum.xda-developers.com/showthread.php?t=1745888
credit goes to hofs1 for post in guilde above
with "Get My MSL" if it doesn't work at first for you do these steps
1. run get my MSL app
2. hit home button to not close app
3. go to dialer type ##DATA#
4. select edit
5. type any code
6. rerun get my MSL app
you should be gtg
spyderdreams said:
Backup work for me with the default 000000, but that being said the only way i was able to get my MSL was an app "Get My MSL" from google play
this guilde didn't work for me http://forum.xda-developers.com/show....php?t=1745888
with "Get My MSL" if it doesnt work at first for you do these steps
1. run get my MSL app
2. hit home button to not close app
3. go to dialer type ##DATA#
4. select edit
5. type any code
6. rerun get my MSL app
you should be gtg
Click to expand...
Click to collapse
How exactly did that guide "not work for you" but your repeating the the instructions almost to a T here? Dont get it
billard412 said:
How exactly did that guide "not work for you" but your repeating the the instructions almost to a T here? Dont get it
Click to expand...
Click to collapse
getprop ril.MSL in terminal and / or adding /system/bin/msl and running getprop ril.MSL is not the same thing as downloading an app from the market
I am not going to go into anymore in detail about this for you cause we will be getting off topic
edit: ok found hofs1 post further in thanks "hofs1"
If "get my msl" fails to return a number ho to the dialer an ##3282# select edit and enter any Number. Press home and run get my msl again.
Sent from my SPH-L710 using xda app-developers app
ooxcfhxoo said:
If "get my msl" fails to return a number ho to the dialer an ##3282# select edit and enter any Number. Press home and run get my msl again.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
It worked perfectly for me!
Sent from my SPH-L710 using xda premium
Philosuffer said:
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be
Click to expand...
Click to collapse
I realize this is the Sprint forum and I have a US Cellular phone my Google search landed me here. I am getting this exact message and was wondering if you have been able to get past this and get a complete backup of your IMEI. If so could you describe how you did it hopefully the info would be helpful for us USCC users.
Sent from my SCH-R530U using Tapatalk 2
how are people loosing their imei in the first place
Roaming Lists could not be read.
I put in my correct MSL. Is there a fix for this?
When attempting to do the AWS mod I get:
Could not Communicate in Diagnostic Mode
I now have a bricked modem due to some sort of lock. I'll flash a modem and see what happens.
I flashed a ROM and my ICCID is now listed as "unknown". Any fix for that?
Sent from my SPH-L710 using xda app-developers app
I have a SPRINT SPH-L710 (Galaxy S3) with stock Rom and it is NOT rooted.
I have not lost my IMEI i just want to make a regular backup.
I have followed the directions in the first post perfeclyt and i can see my phone in backup section and under Port (it shows my phone)
I enter my SPC and hit "Start Button" to start backup procedure and it unlocks phone and starts to read phone and backing up.
it makes it to 47% every time and says
Status = Memory Backup Failed
Errors = Received an invalid command from the phone
thanks
just wanted to add i have now rooted phone and installed CWM and it still does same exact thing

Is my EFS messed up

I just got my Galaxy S3 a week ago. I rooted it and flashed between a few roms before deciding on codename android. The phone is activated on AT&T straight talk, and works sometimes. Other times, it will show 5 bars signal, not connect phone calls or receive text. Also my phone will connect to HSPA+ for only a short period of time then go down to H, and then Edge where it stays all the time now. When I check phone info it shows my IMEI is 0. Is my IMEI really gone or is the rom not properly reading it. If so could this be the cause of my signal woes, and what should I do to restore it.
hampsterblade said:
I just got my Galaxy S3 a week ago. I rooted it and flashed between a few roms before deciding on codename android. The phone is activated on AT&T straight talk, and works sometimes. Other times, it will show 5 bars signal, not connect phone calls or receive text. Also my phone will connect to HSPA+ for only a short period of time then go down to H, and then Edge where it stays all the time now. When I check phone info it shows my IMEI is 0. Is my IMEI really gone or is the rom not properly reading it. If so could this be the cause of my signal woes, and what should I do to restore it.
Click to expand...
Click to collapse
if your IMEI is reading "0" you need to go here to fix it http://forum.xda-developers.com/showthread.php?t=1801997
This should help
http://forum.xda-developers.com/showthread.php?t=1801997
**damn task.. beat me my milliseconds!
task650 said:
if your IMEI is reading "0" you need to go here to fix it http://forum.xda-developers.com/showthread.php?t=1801997
Click to expand...
Click to collapse
Do I need to do the full restore from step one, or just the data part?
Follow the IMEI injection portion
Uncle Irish said:
Follow the IMEI injection portion
Click to expand...
Click to collapse
I followed the instructions and ran the scripts in the second post. now it's saying hardware id missing in windows
windows cannot identify the device plugged into the samsung mobile usb composite device
OK, I managed to work all that out, and my IMEI did not exist at all. I'm at the step to insert it, but I don't understand the hex conversion part.
(skipping the 8) Start at the top left number and go one row down diagonally to the right to get your number
Hopefully this screenie will help illustrate. If there is only 1 number in a row, the first number would be a zero
Also, sounds like you need to use a more current version of CWM.
I use TWRP which can be found in the development thread. Works very well
Uncle Irish said:
Also, sounds like you need to use a more current version of CWM.
I use TWRP which can be found in the development thread. Works very well
Click to expand...
Click to collapse
Thanks for all the help. I'm on CWM Recovery v5.8.4.5 should I replace that with TWRP?
hampsterblade said:
Thanks for all the help. I'm on CWM Recovery v5.8.4.5 should I replace that with TWRP?
Click to expand...
Click to collapse
Your recovery version is fine, so something else caused the borked IMEI.
Using a different recovery is up to you really. I prefer TWRP because it has nice big buttons and has never steered me wrong. Either CWM or TWRP is a suitable recovery. Give it a try and see if you like it. If you don't, you can always go back to CWM.
Did you get your IMEI issue resolved?
I gave it a week to sink in after, and my network has at least been stable now, but I'm stuck on EDGE. Sometimes It will connect to HSPA+ for about a minute, but quickly drops down. I did run the tool to generate a QCN.
I think the problem may actually be the APN settings for straight talk, or even straight talk in general. I'm just going to switch back to t-mobile monthly 4G once my curent set of minutes expires.

[Q] ##Data# Corrupted -- Device refuses to provision data

Hi,
I'm at wits end. I recently updated to GA10, but through a bad flash (I believe), my device lost ALL data for the modem. It now refuses to provision any data. Voice works, and is provisioned correctly.
Have Sprint.
Sprint has tried ##72786, ##RDB, full factory reset, settings -update profile, pushing reactivation, ##123456, ##update, everything. No amount of stupid stuff has seemed to work. My ##data profile is completely empty. Does anyone have any idea how I can rebuild it?
David Turner
f0ru0l0rd
Do you have an old CWM backup?
Oh sweet Mary... YES!
garwynn said:
Do you have an old CWM backup?
Click to expand...
Click to collapse
At first I forgot I did, but... YES! I believe I do. What do I do oh wise guru?!?
f0ru0l0rd said:
At first I forgot I did, but... YES! I believe I do. What do I do oh wise guru?!?
Click to expand...
Click to collapse
Restore it. Hopefully will get your EFS back.
Sent from my SPH-L900 using Tapatalk 2
Well, I'd like to, but apparently restoring it borks the system. So I tried to just advanced restore the datat. It looks like it's all corrupted. Does anyone know where I can find the file containing my sprint data settings?
garwynn said:
Restore it. Hopefully will get your EFS back.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Sometimes Sprint does have OTA provisioning issues, so it could be a problem with the tower you are near.
Regardless, here are some quick tips on how I would fix it in your shoes:
1) Install Stock, non-rooted software (pick your flavor of one-click). The new GA10 leak is fine.
2) After phone reboots, it will try to OTA provision. Click cancel.
3) Go to phone, ##786#, enter your MSL, phone will reboot.
4) After phone reboots, it will try to OTA provision. Let it. If it works, great. Otherwise, post what error code you get (if any)
5) Go to phone, ##(MSL)#, Edit, punch in your phone number and MSID (not always the same as your phone number, so make sure you have the correct info), click OK, reboot.
6) After phone reboots, it will try to OTA provision. Let it. If it works, great. Otherwise, post what error code you get (if any).
6b) If it doesn't provision, make sure you can make/receive calls.
Nah
Already tried all of that. The screen says: Error: Error downloading data (or something like that)
Sadly, I sent my phone in. I couldn't live with it. I had tried everything I knew to do. Full factory reset, swap esn's on spint's side, everything. Hopefully It's better now though.
UPdownLoAD said:
Sometimes Sprint does have OTA provisioning issues, so it could be a problem with the tower you are near.
Regardless, here are some quick tips on how I would fix it in your shoes:
1) Install Stock, non-rooted software (pick your flavor of one-click). The new GA10 leak is fine.
2) After phone reboots, it will try to OTA provision. Click cancel.
3) Go to phone, ##786#, enter your MSL, phone will reboot.
4) After phone reboots, it will try to OTA provision. Let it. If it works, great. Otherwise, post what error code you get (if any)
5) Go to phone, ##(MSL)#, Edit, punch in your phone number and MSID (not always the same as your phone number, so make sure you have the correct info), click OK, reboot.
6) After phone reboots, it will try to OTA provision. Let it. If it works, great. Otherwise, post what error code you get (if any).
6b) If it doesn't provision, make sure you can make/receive calls.
Click to expand...
Click to collapse

Can no longer get MSL with 4.1.2

Hello,
I used to be able to get my MSL by doing ##DATA# in dialer, entering 6 random digits then doing getprop ril.MSL in connect bot, but this no longer works after 4.1.2 update.. I even wiped my phone and rooted with CWM and tried it again.. no luck.. I have googled the crap out of this trying to see if there is a way to get msl from CWM recovery but I cannot find anything..
Help would be appreciated!
Lord
Sprint GS3
lordinfamous666 said:
Hello,
I used to be able to get my MSL by doing ##DATA# in dialer, entering 6 random digits then doing getprop ril.MSL in connect bot, but this no longer works after 4.1.2 update.. I even wiped my phone and rooted with CWM and tried it again.. no luck.. I have googled the crap out of this trying to see if there is a way to get msl from CWM recovery but I cannot find anything..
Help would be appreciated!
Lord
Sprint GS3
Click to expand...
Click to collapse
I believe this belongs in the Questions forum instead of the General section. Anyways, to answer your question, use aLogcat.
1. Open up dialer, enter ##3282#
2. Open aLogcat
3. Menu > Clear log
4. Hold home button, go back to EPST Menu
5. Enter random 6 numbers into MSL field
6. Go back to aLogcat
7. Locate the line that says "MSL Code="
8. Write down those digits and store them somewhere they will not be lost
Android Attack said:
I believe this belongs in the Questions forum instead of the General section. Anyways, to answer your question, use aLogcat.
1. Open up dialer, enter ##3282#
2. Open aLogcat
3. Menu > Clear log
4. Hold home button, go back to EPST Menu
5. Enter random 6 numbers into MSL field
6. Go back to aLogcat
7. Locate the line that says "MSL Code="
8. Write down those digits and store them somewhere they will not be lost
Click to expand...
Click to collapse
Thanks, I tried this 5 times following exactly what you said and there is no msl line anywhere in the alogcat list.. even searched for it
ive tried the same thing and no luck. it was working before the update. though it was just me. none of the previous ways work now.
I'm having this problem too. I was thinking of flashing a 4.0.4 rom after backing up and get my MSL then restore from my backup. That should work right?
Sent from my SPH-L710 using xda premium
Let me help y'all out http://forum.xda-developers.com/showthread.php?t=2159054
Sent from my SPH-L710 using Tapatalk 2
auau465121 said:
Let me help y'all out http://forum.xda-developers.com/showthread.php?t=2159054
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
That seems good, but it doesn't say anything about MSL. Will it still work on getting MSL?
Sent from my SPH-L710 using xda premium
Humzaman said:
That seems good, but it doesn't say anything about MSL. Will it still work on getting MSL?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just installed the .zip file in CWM and rebooted and i still am in the exact same boat
lordinfamous666 said:
I just installed the .zip file in CWM and rebooted and i still am in the exact same boat
Click to expand...
Click to collapse
Yup I tried it too. Nothing changed...
Sent from my SPH-L710 using xda premium
I was lost at hello??????
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for you cooperation
Friendly Neighborhood Moderator
Thanks!
Bumping for anyone who has an idea now that thread is in the right place! I still have had no luck.
lordinfamous666 said:
Thanks!
Bumping for anyone who has an idea now that thread is in the right place! I still have had no luck.
Click to expand...
Click to collapse
Same here
Sent from my SPH-L710 using xda premium
Use terminal emulator instesd of connect bot. Works fine for me on 4.1.2 on the note 2 which is pretty close to the same base firmware just different add ons
You can also get it by starting an online activation on sprint.com and then once you enter your esn/imei it will bring up the master reset and provisioning info and your MSL will be in the instructions list, write it down and close out the page
I like to break stuff!
-EViL-KoNCEPTz- said:
Use terminal emulator instesd of connect bot. Works fine for me on 4.1.2 on the note 2 which is pretty close to the same base firmware just different add ons
You can also get it by starting an online activation on sprint.com and then once you enter your esn/imei it will bring up the master reset and provisioning info and your MSL will be in the instructions list, write it down and close out the page
I like to break stuff!
Click to expand...
Click to collapse
Already tried terminal Emulator, that did not work either and trying to activate phone on sprint.com gave me an incorrect number message... I KNOW i was typing the right number... I ended up just calling Sprint, telling them that I had work done for poor signal issues with a tech and I did a full wipe of my device so I need my MSL to repeat the steps that the tech gave me.. they handed the MSL right over no problem and this time I saved it in my email...
I would recommended spending 10 minutes on the phone with Sprint instead of loading a 4.1.1 or older ROM.. save yourself some time.
lordinfamous666 said:
Already tried terminal Emulator, that did not work either and trying to activate phone on sprint.com gave me an incorrect number message... I KNOW i was typing the right number... I ended up just calling Sprint, telling them that I had work done for poor signal issues with a tech and I did a full wipe of my device so I need my MSL to repeat the steps that the tech gave me.. they handed the MSL right over no problem and this time I saved it in my email...
I would recommended spending 10 minutes on the phone with Sprint instead of loading a 4.1.1 or older ROM.. save yourself some time.
Click to expand...
Click to collapse
That's great. What exactly should I say to them though?
Sent from my SPH-L710 using xda premium
Humzaman said:
That's great. What exactly should I say to them though?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
All you gotta do is call support and say I need my MSL. If they ask why, say "because it's mine and I'd like to keep it in my records and lost the ome I wrote down when I activated my phone"
I like to break stuff!
http://forum.xda-developers.com/showthread.php?p=38416225
I had this same problem. The solution is to downgrade rom to ics low ship as referenced in URL. Once on the rom use the suggested get my msl app technique. Works flawlessly.
Sent from my SPH-L710 using Tapatalk 2
There's several methods because I myself had the same problem using 4.1.2 but i wrote down my msl code when i downflashed to 4.1.1
All you need to do really is the methods mentioned above BUT you'll need to do this.
Wipe cache dalvik 2x. Reboot device.
Download and install android terminal emulator from play store.
Open it
go to the dialer and press ##3282#
Edit.
type 000000 or any random number.
Go back to Android Terminal Emulator via Task Manager.
then type this.
Code:
su
getprop ril.MSL
if no number shows. go back to the MSL code screen
retype 000000
let the phone reboot due to typing in the wrong msl too many times.
Go back to dialer and ##3282#
Type in 000000
then redo getprop ril.MSL in the terminal.
You then should be able to get the MSL number.
I've tried it on 4.0.4 and 4.1.1 - LG8 and LJ7 and i've gotten the MSL number but it
didn't work for me on MA4/MA6 leaked and MB1 official OTA.
bump this up because i am too looking to get my MSL from my build MD4 (4.1.2)?

How to fix 4lte or data on any rom ? Read this .....

Disclaimer: what ever you do to your phone is on you! me or nobody will be responsible if your phone get mess up or die... it will be up to you !!!!!!!!!!!!!!!!!
This only work if your Data profile is missing which is why you lost data otherwise its something else that broke it.
You need!!!!
To be on stock.
The msl password.
Copy the Data profile down or the whole thing... in case you rom in missing more information which the phone need to communicate to the service. Since some rom cant read data profile you need to reprogram the phone you seft.Just put the data profile info back in and enable lte.
Note: if something is missing just add it back in.
1_Flash your rom and dial ##3282#
2_ In the "edit" program put your msl password
3_add your phone info. back in
4_ restart your phone
5_ in setting / update/ update profile.... just update the profile and you are good to go.
If you want the msl password root your phone and download get my msl at the android market then try to put a ramdom msl password then go back to the msl app the try it again
Dont forget to thank.
Sent from my SPH-L900 using xda app-developers app
Can you please beter define step 1? "flash your rom on deal ##3282##... I recognize the dialer code but what exactly are you saying here?
As for "any ROM".. is that really true? Dialer codes don't work on CM ROMs, right? So this only works on TW ROMs with in-tact dailer codes?
honki24 said:
Can you please beter define step 1? "flash your rom on deal ##3282##... I recognize the dialer code but what exactly are you saying here?
As for "any ROM".. is that really true? Dialer codes don't work on CM ROMs, right? So this only works on TW ROMs with in-tact dailer codes?
Click to expand...
Click to collapse
I'm sure he meant, "...AND DIAL ##3282#"
Yeah It will work if your rom support it...
If not find out how to get the programming to work so that you can dial the ##3282# and program your phone from there. In cm10.1 or other nonexistent programming you may have to add the hidden file back in which the developers removed for a reason.
Sent from my SPH-L900 using xda premium

Categories

Resources