I am deployed to Afghanistan right now. I ordered a brand new XT862, rooted it, and installed safestrap 2.10 and cm-9-20120815-UNOFFICIAL-solana.zip. That worked beautifully.
Unfortunately I am having problems getting the radio to work. I would set an APN but then sometimes it would just not appear in the list. I would set it again and again, then sometimes all of the APNs would appear in my list until the radio failed. After flashing, formatting, and reflashing several times and having the default Verizion access points finally pop up out of nowhere in my APN list, I realized I never "unlocked" the phone. I am using a Roshan SIM.
The weird part is the radio would work for a period of time. First for several hours, then it would start failing more and more frequently.
I found the XT862-5.7.906-SAFE and flashed it, hoping it would ask me for an unlock code upon booting, but no dice. It just went into "Global" mode. I am testing right now to see if the radio stays stable.
So, I am wondering if these instructions:
Guide - Unlock XT862 for T-mobile/ATT
http://forum.xda-developers.com/showthread.php?t=1406812
will get me to the unlock code screen, and once unlocked, will my radio problem disappear when I reflash CM9? My Internet connection is painfully slow here in Afghanistan so I only want to download what I know will work.
I do have a second XT862 that I had unlocked, then rooted and flashed CM9 to and it is working very well on Roshan out here.
Thanks for your help!
While running the XT862-5.7.906-SAFE, the radio cut out and I got a BP paniced message. I couldn't remember all of it before it crashed completely, but it asked to connect the USB for debugging. While the screen was flickering, a window popped up asking if I wanted to switch to GSM.
The radio doesn't seem to be stable even with this firmware.
Any suggestions or help would be greatly appreciated.
The radio cut out again, so I tried switching it from global to CDMA and then to GSM to see if I could get it to reset.
It told me there were no GSM networks available, and then asked to switch to Global.
I hit ok, then it told me that the SIM was invalid...
I'm a noob to this phone stuff, but this just seems crazy.
It seems it's definately the phone, because I swapped the SIMs in my two phones and the problems persist with the new one. My functioning phone continues to work fine on the chip designated for the problem phone.
Did you flash the 883 radio?
MrObvious said:
Did you flash the 883 radio?
Click to expand...
Click to collapse
No, I haven't yet because I didn't know if that was going to solve my problem or not. Downloading is a challenge for me right now, too.
I don't know if not unlocking the phone before flashing CM9 caused the problem or if it's something else entirely that I am missing. I will want to have the phone usable in the states again. Will flashing the 883 radio give me any difficulties there?
I've went back though the steps that I did on my other, working phone and [edit] not unlocking is [/edit] pretty much the only difference.
I'm probably going to try to download the 883 radio stuff tonight when I get home from work and give it a try.
ThunderZuk said:
No, I haven't yet because I didn't know if that was going to solve my problem or not. Downloading is a challenge for me right now, too.
I don't know if not unlocking the phone before flashing CM9 caused the problem or if it's something else entirely that I am missing. I will want to have the phone usable in the states again. Will flashing the 883 radio give me any difficulties there?
I've went back though the steps that I did on my other, working phone and [edit] not unlocking is [/edit] pretty much the only difference.
I'm probably going to try to download the 883 radio stuff tonight when I get home from work and give it a try.
Click to expand...
Click to collapse
Unlocking the phone MUST be done on stock firmware. The XT883 radio is only required for using US GSM networks, such as AT&T and T-Mobile. The stock XT862 radio (after unlock) supports foreign SIM cards (and of course Verizon's Vodafone SIM).
As I recall, CM9/10 normally has issues with the GSM radio, if you need your phone, I suggest flashing a ROM based on a stock GB system, such as Maverick (4.0 version, 4.5 has a battery drain issue with an overclock script) which is based on 906. I tend to keep the phone on GSM/UMTS mode, as "Global" also turns on the CDMA radio, which utilizes more battery. The APN only matters for Data/MMS without the proper APN, you should still get talk/text/signal (no EDGE or 3G icons, which indicate data connection).
Skreelink said:
Unlocking the phone MUST be done on stock firmware. The XT883 radio is only required for using US GSM networks, such as AT&T and T-Mobile. The stock XT862 radio (after unlock) supports foreign SIM cards (and of course Verizon's Vodafone SIM).
As I recall, CM9/10 normally has issues with the GSM radio, if you need your phone, I suggest flashing a ROM based on a stock GB system, such as Maverick (4.0 version, 4.5 has a battery drain issue with an overclock script) which is based on 906. I tend to keep the phone on GSM/UMTS mode, as "Global" also turns on the CDMA radio, which utilizes more battery. The APN only matters for Data/MMS without the proper APN, you should still get talk/text/signal (no EDGE or 3G icons, which indicate data connection).
Click to expand...
Click to collapse
I didn't update the radio on my working phone to 883. It has been doing just fine on Roshan Afghanistan and AIS in Thailand. In the states I use Verizon, so I don't think GSM is a biggie.
So, I have to get back to stock and unlock, then go through the hack process again. I figured I probably did. So before I try to download this file, do you think the 1-click SBF here:
[xt862] .906 1-click-sbf.exe + tools [10-8-2012]
http://forum.xda-developers.com/showthread.php?t=1686911
will do the job? If not, do you know what will? I'm still running XT862-5.7.906-SAFE. I do have Blur_Version.5.6.890.XT862.Verizon.en.US.zip but I don't know how to install it. I'm still learning all of this stuff. Would RSDLite do it?
I wasn't very specific when I talked about the radio, sorry. More or less the voice connection would stop along with the data. It was just weird that sometimes the APNs would show up in the list and sometimes they wouldn't. When they did, it showed multiple from when I tried entering them several times. I don't know why it would write the changes but not read the list.
When about five Verizon APNs showed up and none of my Afghan APNs showed up, I realized I must have needed to unlock the phone. When I hacked it I just assumed it wouldn't have to be unlocked. I figured I WAS unlocking it. LOL!
Thanks everyone for your help.
ThunderZuk said:
I didn't update the radio on my working phone to 883. It has been doing just fine on Roshan Afghanistan and AIS in Thailand. In the states I use Verizon, so I don't think GSM is a biggie.
So, I have to get back to stock and unlock, then go through the hack process again. I figured I probably did. So before I try to download this file, do you think the 1-click SBF here:
[xt862] .906 1-click-sbf.exe + tools [10-8-2012]
http://forum.xda-developers.com/showthread.php?t=1686911
will do the job? If not, do you know what will? I'm still running XT862-5.7.906-SAFE. I do have Blur_Version.5.6.890.XT862.Verizon.en.US.zip but I don't know how to install it. I'm still learning all of this stuff. Would RSDLite do it?
I wasn't very specific when I talked about the radio, sorry. More or less the voice connection would stop along with the data. It was just weird that sometimes the APNs would show up in the list and sometimes they wouldn't. When they did, it showed multiple from when I tried entering them several times. I don't know why it would write the changes but not read the list.
When about five Verizon APNs showed up and none of my Afghan APNs showed up, I realized I must have needed to unlock the phone. When I hacked it I just assumed it wouldn't have to be unlocked. I figured I WAS unlocking it. LOL!
Thanks everyone for your help.
Click to expand...
Click to collapse
If you were on the 906 OTA, the one click EXE would work, no programs required. Connect phone in bootloader > run the exe > The phone will flash. In Global mode, when you check the APNs, only the Verizon ones will show, you MUST be in GSM/UMTS mode for your own APNs to show up. Also, if it's occasionally in and out, I wonder if the connection between the SIM and phone are bad, like a shake or movement will break the contact. (Which when a SIM is not present, only the Verizon APNs will show as well and would prompt for global mode)
Try taking the SIM out, cleaning the contacts, and placing it back in. If the sim seems loose, try slipping a single thin piece of paper behind it to make sure it's getting full contact. Otherwise, it might be a hardware fault.
Skreelink said:
If you were on the 906 OTA, the one click EXE would work, no programs required. Connect phone in bootloader > run the exe > The phone will flash. In Global mode, when you check the APNs, only the Verizon ones will show, you MUST be in GSM/UMTS mode for your own APNs to show up. Also, if it's occasionally in and out, I wonder if the connection between the SIM and phone are bad, like a shake or movement will break the contact. (Which when a SIM is not present, only the Verizon APNs will show as well and would prompt for global mode)
Try taking the SIM out, cleaning the contacts, and placing it back in. If the sim seems loose, try slipping a single thin piece of paper behind it to make sure it's getting full contact. Otherwise, it might be a hardware fault.
Click to expand...
Click to collapse
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
ThunderZuk said:
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
Click to expand...
Click to collapse
The Droid 3 does not require RSDLite, as it has fastboot. Which is able to flash certain parts alone instead of the whole system (or the whole thing together) it's easier than RSDLite and can make modifications without losing everything. That's how the XT883 radio is flashed without modifying the system.
The one click method would fully flash it as if you used an SBF in RSDLite. If you have safestrap enabled on safe; make a full backup with recovery, then disable safe-mode. You'll then reboot into your stock system, unlock there, then enable the safe boot again, restore your backup.
SIM unlocking is for good, no amount of flashing, updating, etc will revert it. If the phone DOES get service with the sim, then it's already unlocked.. if it's occasionally cutting out, that's a different issue.
ThunderZuk said:
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
Click to expand...
Click to collapse
Holy shinto! I didn't know it saved that! I figured it was gone!
So I disabled safestrap, then it kept telling me com.android.phone had stopped. I'd force close and it would say it again. I went back into safestrap, did a factory wipe, rebooted and now it is connected in "Global" mode again on the stock 5.6.890.XT862.Verizon.en.US. It was looking good for a while, until the phone just rebooted itself.
I put my other SIM in the phone, booted back up and it worked for a while until the signal dropped and the phone gave me an invalid SIM error again. So, it's given me an invalid SIM on two different SIMs now in stock and flashed ROMs.
The SIM is in there tight. I couldn't get a piece of paper in there. I cleaned the contacts again, but they don't look dirty at all.
I put the original SIM back in there, it booted up, never got signal, and rebooted itself again. It doesn't have signal now, and I assume it's just about to reboot itself again.
You think I got a bum phone? I didn't test it at all before I started hacking it.
Also, if I do the *#*#4636#*#* while it has no signal it tells me my IMEI number is unknown, if that helps. If press the turn off radio button, it does nothing.
[edit]It also tells me pretty much everything (MEID, IMEI SV, SIM ID, ect...) is unknown if I go into About Phone>Status[/edit]
ThunderZuk said:
Also, if I do the *#*#4636#*#* while it has no signal it tells me my IMEI number is unknown, if that helps. If press the turn off radio button, it does nothing.
[edit]It also tells me pretty much everything (MEID, IMEI SV, SIM ID, ect...) is unknown if I go into About Phone>Status[/edit]
Click to expand...
Click to collapse
That happens if either; Airplane mode is on, or you have an incorrect build.prop, have you modified it in any way? Also have you tried making a backup and turning safe boot off?
Also; If the zips are still on your SDCard, try reflashing your rom to make sure you have the correct build.prop.
Skreelink said:
That happens if either; Airplane mode is on, or you have an incorrect build.prop, have you modified it in any way? Also have you tried making a backup and turning safe boot off?
Also; If the zips are still on your SDCard, try reflashing your rom to make sure you have the correct build.prop.
Click to expand...
Click to collapse
I have safestrap turned off and it appears I am running on stock? It says I am running 5.7.890 and not 5.7.906. There is a Superuser icon in the all apps, but I think that is from where I rooted it.
I rebooted and all the numbers came back... for now.
I don't have airplane mode on. I tried to turn it on after reading your post. It caused the phone to reboot. Once rebooted, it came back up in airplane mode. I turned it off and it is connected again, for now.
I haven't messed with the build.prop that I know of. I only rooted, installed CM9 several times, formatted everything several times in-between those installs, and most recently flashed that XT862-5.7.906-SAFE.zip.
And before I even finished this post it rebooted itself on me again...
ThunderZuk said:
I have safestrap turned off and it appears I am running on stock? It says I am running 5.7.890 and not 5.7.906. There is a Superuser icon in the all apps, but I think that is from where I rooted it.
I rebooted and all the numbers came back... for now.
I don't have airplane mode on. I tried to turn it on after reading your post. It caused the phone to reboot. Once rebooted, it came back up in airplane mode. I turned it off and it is connected again, for now.
I haven't messed with the build.prop that I know of. I only rooted, installed CM9 several times, formatted everything several times in-between those installs, and most recently flashed that XT862-5.7.906-SAFE.zip.
And before I even finished this post it rebooted itself on me again...
Click to expand...
Click to collapse
Alright, did you put the sim in and get the unlock screen to put in the unlock code? 890 is alright to be on, that's what my stock system is. I would suggest staying away from CM9/CM10 as they are unstable when using GSM networks. Either stay stock or flash a ROM based on Blur (I suggest MavRom 4.0).
Skreelink said:
Alright, did you put the sim in and get the unlock screen to put in the unlock code? 890 is alright to be on, that's what my stock system is. I would suggest staying away from CM9/CM10 as they are unstable when using GSM networks. Either stay stock or flash a ROM based on Blur (I suggest MavRom 4.0).
Click to expand...
Click to collapse
It never asked me for an unlock. It just immediately put the phone in world mode.
I literally did this with the phone.
1. open factory sealed box
2. root the phone
3. install safestrap
4. format all partitions
5. install CM9
6. install SIM
7. repeat 4 and 5 serveral times
8. install 5.7.906 hoping to get an unlock screen in order to possibly fix radio issue
9. start this thread.
Now, I did steps 4 and 5 over and over again over about 2 weeks off and on while I tried to figure out what was going wrong. Like I said, I am running CM9 very successfully here since August on a different XT862 that I did unlock before rooting. I installed a KANG build, not a KEXEC.
The amount of times your device seems to be rebooting makes me think there is something wrong with it.
Sent from my XT860 using xda premium
ThunderZuk said:
It never asked me for an unlock. It just immediately put the phone in world mode.
I literally did this with the phone.
1. open factory sealed box
2. root the phone
3. install safestrap
4. format all partitions
5. install CM9
6. install SIM
7. repeat 4 and 5 serveral times
8. install 5.7.906 hoping to get an unlock screen in order to possibly fix radio issue
9. start this thread.
Now, I did steps 4 and 5 over and over again over about 2 weeks off and on while I tried to figure out what was going wrong. Like I said, I am running CM9 very successfully here since August on a different XT862 that I did unlock before rooting. I installed a KANG build, not a KEXEC.
Click to expand...
Click to collapse
Hm... while in unsafe (stock) the unlock screen should have come up. It will not on other roms, as for global mode, that is a default setting, without unlock, will only work with the verizon vodafone sim that came with the phone. Reboots can be either hardware, rom, or app problem. You can try a factory wipe and see if that helps the reboots. Trying to find solutions without you having to download more.
Endoroid said:
The amount of times your device seems to be rebooting makes me think there is something wrong with it.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I was kind of worried that was the case. I just ordered a refurb unit just in case.
Related
Quick background:
- I have an International version, sourced from Latin America
- I have rooted the phone but NOT custom ROM
- I have Straight Talk service
The phone was just working fine for almost 1 month, can receive call, SMS, etc. Just today, I shutdown the phone and took out the microSD card and SIM.
I copied some files to the microSD card using a reader and left the phone with the SIM and battery out for about 30 minutes.
I put the microSD, SIM and battery and rebooted the phone. Suddenly, I got Emergency Calls only!
I have tried to "fix" it but to no avail:
1). Looking at the 3 PIN in the SIM slot, they are all INTACT, nothing bend or broken or lopse
2). The SIM card works - tested it in another 2 different phone and can make calls, etc.
3). I did CWM recovery to a backup from 1 day ago (when the phone still works)
Anyone have this experiences or my phone just DEAD?
weird...
try do the hard reset (try not to restore anything yet), if still doesn't change anything... flash new radio (LC1)
I disassembled my Note using the instructions from here to check if any of the 6 (SIX) SIM Card connector is bent and it is NOT.
I am putting it back together now and will do factory reset (this is what you meant by "hard reset", right?). I will post back with updates/
PS: this is INDEED weird. The phone works OK, Wifi works, sound works, screen works, microSD card is readable, everything works EXCEPT the GSM connection! And I didn't even mess aroud with the custom ROM/kernel/radio!
did u test other sim card on that phone yet?
thehackersz said:
did u test other sim card on that phone yet?
Click to expand...
Click to collapse
I don't have an extra SIM card. What I did was take out the Straight Talk (ST) SIM card from my Note and put it in another unlocked GSM phone (Nokia N73). The Nokia N73 works with the ST SIM.
I just did a "Factory Reset" and still the same thing.
Before I try the radio flash, what will this "software" do to the Note modem? I am just curious how it will fix it.
BTW, my Baseband vesion is "BKK1", and I don't see the radio for this baseband in the link you provided. Which one should I use?
PDA: N7000UBKK2
PHONE: N7000UBKK1
CSC: N7000UWHKK2
flashing the radio doesn't effect your rom... try them.
try to borrow your neighbor sim card first before flash new radio.
thehackersz said:
flashing the radio doesn't effect your rom... try them.
Click to expand...
Click to collapse
Which radio files I should use? The link you provided show multiple radios, but I don't see one for my phone:
PDA: N7000UBKK2
PHONE: N7000UBKK1
CSC: N7000UWHKK2
Try to clean the Sim slot.
Yes, I tried cleaning the SIM slot. I have been very careful with my Note since day 1.
Someone mentioned that they have the same problem and was able to fix it by flashing STOCK ROM back.
I searched in the development section and could not find ROM for my phone (N7000UBKK1). Do you have any idea where I can get this from?
Well, looks like my phone is toast. I have tried the following:
1). Wipe data, cache, Dalvik and restore to CWR backup --> NO GO
2). Do a "factory reset" --> NO GO
3). Install stock firmware using Odin --> NO GO
NOTE: had to search for stock firmware on the Internet since it is NOT available in XDA
The only thing I haven't tried is flashing the modem firmware, but this is NOT available anywhere in XDA either.
The ST SIM card works because I tried this on two other GSM phone. Only the Note show "Emergency Call Only" message.
So now I have a $600 media player that I can't event sell. I guess serves me right for buying an International version with ZERO warranty and just happen that there is NO modem firmware for my phone.
lanwarrior said:
Well, looks like my phone is toast. I have tried the following:
1). Wipe data, cache, Dalvik and restore to CWR backup --> NO GO
2). Do a "factory reset" --> NO GO
3). Install stock firmware using Odin --> NO GO
NOTE: had to search for stock firmware on the Internet since it is NOT available in XDA
The only thing I haven't tried is flashing the modem firmware, but this is NOT available anywhere in XDA either.
The ST SIM card works because I tried this on two other GSM phone. Only the Note show "Emergency Call Only" message.
Click to expand...
Click to collapse
Boy.. That's a serious issue man.
So now I have a $600 media player that I can't event sell. I guess serves me right for buying an International version with ZERO warranty and just happen that there is NO modem firmware for my phone.
Click to expand...
Click to collapse
LOL
Anyhow,
I found out the solution to this problem by accident, and there doesn`t appear to be a solution anywhere else on the internet. Turn off your phone and restart it. As soon as you are able to do so, open up setting, or any other app. When your phone goes into cool down mode, hold down the home button. A screen will come back asking you to select an app. Select whatever you opened prior to cool down mode (If you need to get into settings press the search button and search for settings after your out of CDM). You then need to do two things. Go to Running services (Settings>Applications>Running services), find detect battery service, touch it and stop it. To the best of my knowledge, it doesn`t do anything to your phone, other than activate cool down mode. Then go to manage applications (Settings>Applications>Manage applications) press your menu button and select filter> all applications. Find Battery protect, click on it, and select force stop. This allows your phone to get reception. You will have to do this every time your phone starts up, but it isn`t too much of a hassel for a truely excelent phone. The Cool down mode problem is definitly a software fault.
Source:
askmefast.com/My_galaxy_s2_shows_i_have_signal_but_says_emergency_calls_only-qna1783355.html
I'm also having the same problem and mine is also N7000UBKK1. Anyone know what's going on?
Try another rom. I have it on some roms and some not
Sent from my GT-N7000 using Tapatalk 2
Try the following link
http://forum.xda-developers.com/showpost.php?p=25289773&postcount=207
If you can get into download mode then flash using PC odin
AbyssNotekernel42CWTouchOriginalLogo.tar
If it pass you can flash a GB rom in your sdcard.
HELP!!
I have also had this same problem. My phone is STOCK I have not touched it. got the phone on last Monday working fine until the battery level ran right down yesterday, then I got message to "insert sim card!", ever since re-starting the phone I no longer can make calls!. I had no intension of rooting or messing with this phone and decided to wait until official ICS, but now what do I do?, is this a common problem?.
Tried previous instruction on this post, but unable to find any battery service running on the device.
Please help!!
I now also have this issue after updating to the latest firmware via Kies.
UPDATE: I got mine checked and it looks like the replacement unit I got had its SIM card broken. Dodgy eBay seller.
Just fyi, never insert MicroSim card adaptor in Galaxy Note. Mine works now after spending $100. Jeez
FYI, I tried all of the suggested solutions in this thread and I still have problem. So I returned the Note and got the AT&T version... At least now I got US Warranty
Same thing just happened to my phone. Rogers Galaxy note II.
Tried bunch of different SIM cards, none work.
Got the SIM reader app, phone reads SIM just fine. Data connection also works, but refuses to make voice calls "emergency only".
So pissed, wanna throw this phone against the wall.
Did anyone find a solid solution? Mine did this today, Stock never been rooted or anything! Any ideas?
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.
centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.
centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.
Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
anyone got the Radio.img?
inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium
I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up
Return it.
Sent from my HTC Holiday using Tapatalk 2
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Mmmm... tell me some things:
1- Is your phone unlocked in some way?
2- Do you have tried another ROM? (i think yes)
3- use the base build.prop
4- do you have XT860 or XT862? because MAVRom has 2 versions..
kelz20 said:
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Click to expand...
Click to collapse
Try replacing libmoto_ril.so file on /system/lib.
Follows attached. Unzip and place on the folder mentioned above, overwriting the existing one.
This is the only way that I'm able to use custom roms made for XT862. I hava a XT860 running on GSM networks, so this could help.
Probably after that you will need to check if you need to set up the APNs accordingly.
I'd just go back to what was working. There is nothing in Maverick that is worth the hassle of a phone that doesn't work the way that you want.
kelz20 said:
A couple days ago I followed the instructions to unlock my D3 to use on T-Mobile. Everything went perfect and I was using it with T-Mo. I just decided to flash to a custom rom (MavRom 4.5) and now I'm getting a general error of my SIM not being detected. I do not think there is anything wrong with my SIM since I was just using it in the phone this morning. I have tinkered with the build.prop and tried using a custom one too. It was like the phone was trying to work with my SIM but eventually failed or does so immediately. I just want to use my phone. I really don't know what's going on. I'm honestly tired of searching too. I'm kind of at a loss. Please someone help. It'd be much appreciated.
Click to expand...
Click to collapse
Hm, I use Maverick 4.0 without any issues (4.5 is the same thing with overclock scripts, but they cause a battery drain, so I stuck with 4.0). The only issue I have (rarely) is sometimes it'll say invalid sim, but usually it'll still work, just have to reboot to fix that. Long as you have the XT883 radio and proper edited build.prop it *should* work. Please do NOT use any libs for the XT860, you will only make the radio not work at all and potentially cause damage. The XT860 libs were made for a GSM only radio, the XT862 has a dual CDMA/GSM radio, so the libs do not know how to control the radio.
If you require any files or info, let me know. Where I work happens to have refarmed T-Mobile's HSPA to 1900MHz so my D3 can use it. You might have just missed a step somewhere or missed a permission.
Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
jharre08 said:
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
Click to expand...
Click to collapse
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
tuckprodigy said:
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
Click to expand...
Click to collapse
Also, check this out - http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
It's a bit dated, but I am going to try this method if I can find a 3.04 RUU. Note, he is doing this to an S-On phone, which is what we have. So it SHOULD work:good:
Nothing against the first method I posted, but I'd much rather do a RUU and get a clean slate...
There is no RUU for 3.04 yet ( that I know of)...
this is your best (and pretty much only) option: http://forum.xda-developers.com/showpost.php?p=46565593&postcount=27
Did you ever find a way to resolve this issue? Also did this start after flashing Cyanogenmod? I have the exact same issue and it seems I have exhausted all available resources. Currently have the following setup:
Android version - 4.3
Sense version - 5.0
Software version - 3.04.651.2
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
Noticed that the phone is unable to update PRL correctly. Version will switch from 00000 to 1 to 55016. I am also unable to commit changes to any EPST settings (which is the first thing sprint tried to do). MDN and MSID both currently say 'no' and I can't update.
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
kindabizzie said:
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
Click to expand...
Click to collapse
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
jjmckaskie said:
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
Click to expand...
Click to collapse
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
kindabizzie said:
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
Click to expand...
Click to collapse
Hmm. That's pretty much the issue that I had except 4G/Wifi was working and 3G/Call/Text didnt seem to be. You might try switching the CDMA mode to SIM and then back to NV to make sure the setting takes. I know CM can be really finicky with network changes.
tuckprodigy said:
Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
Click to expand...
Click to collapse
You may need to flash a stock rom and manually enter you MDN and MSID using the epst menu
no luck
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
kindabizzie said:
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
Click to expand...
Click to collapse
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
I still took it to Sprint just to see and they fixed it. Downside is my GPS and LTE is messed up again (Me trying to fix those things is the reason all this happened in the first place) but I'd rather not have GPS than not have phone capabilities on my phone (And LTE in Los Angeles is garbage anyway). I think I'm gonna leave my phone alone for a while tho, lol.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
jharre08 said:
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
Click to expand...
Click to collapse
Yup. I actually dont remember if it does a full wipe, or just forces an activation/profile/PRL update. But either way it's worth a shot.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Sounds like you solved your issue, but for anyone else having trouble....
I re-tried GURU's reset and it worked. The first time I downloaded it over the 4G network. I also downloaded the OTA over the 4G network. My radio has been giving me fits ever since. Finally, I downloaded GURU's reset over WIFI, then made sure the OTA downloaded over WIFI, and my phone is like new again! No radio issues, everything is perfect. Hope this helps some people...
Okay, I just got through doing this myself and it seemed that nowhere was this all said at once, or at all. So I thought I'd whip up a quick tutorial concerning how to Domestic Unlock the Samsung Galaxy S4 on any of the newer bootloaders/firmwares/modems. (Knox-enabled)
I did this on both a 4.4.1 galaxy and a 4.3 galaxy- one one NAE and one on MK2
First, for anything to work your modem must be an older one, like version MDL. Download the file SPH-L720_MDC_Modem.exe which is a one-click
Odin .exe that will flash ONLY your modem to MDL.
Steps- put into download mode by taking the battery out and putting it back in. Hold the volume down button, the home buttone and then press the power button. When it vibrates, let go. Press volume up.
Run the SPH-L720_MDC_Modem.exe odin one-click installer.
Connect the usb to computer from phone
when com[24] or whatever shows up, press start.
Now, for the domestic lock to work you first need to do the international unlock @ http://forum.xda-developers.com/showthread.php?t=2415587
It's real easy and explained well at the link above, but I'll run through it quickly anyways.
Download the s4unlocker installer from the post linked above.
Put your phone into diag mode by dialing ##3424#. Press Qualcom button and select the bottom selection.
connect (if it wasn't already) usb from phone to PC
You already installed the proper samsung drivers, right? If not, you'd better do that now.
Okay, now run the s4unlocker and press the scan and unlock button, then wait for the phone to reboot.
Now for the Domestic Unlock part.
Follow the directions at http://forum.xda-developers.com/showthread.php?t=2530610
I'll run through it real quick, too because there were a few things I wanted to mention.
dial *#0011# (or #*0011#, I can't remember)
when it comes up "No service", press the menu key on the bottom left of your phone. This brings up a menu (wow!), on which you should press "back"
Now press the menu key again and in the menu select "key input" A box will open up asking for you to type in something- enter a "1" and then press the enter key BEFORE hitting the OK button. Mine would not work unless I did this.
Now wait, sometimes it takes a good couple of seconds to give you the menu. Follow the rest of the directions from the above link, setting all the settings to what is stated. EXCEPT where he says to set all the preferences to WCDMA ALL, GSM ALL and LTE ALL. When I selected one, however, an asterisk appeared after my selection leading me to believe that you can only select one of these and so I set mine to GSM ALL and left the others alone. This worked for me, so I thought I'd mention it.
Now that you've manually rebooted after following the directions, you still have to edit your build prop to allow you to edit the apn settings. To edit your build.prop you must be rooted so root with CF auto-root http://autoroot.chainfire.eu/ download the proper one for the galaxy s4.
It's just an odin flash, so enter download mode
load up odin 3.x
hit the pda button and select the cf auto root tar
hit start.
After rooting I found that one time I had to do some of the service mode settings again and one time I did not, so I mention it here even though I think I had to because of some other error I had made at the time.
Go to play store and download build.prop editor and APN settings Shortcut
Load the build.prop editor and add these two lines to the end of the file
ril.sales_code=LOL
ro.csc.sales_code=LOL
Now reboot manually
add the apn settings widgit to the main screen and open it
click on menu and add an apn
Enter the apn settings for your carrier here. They're all different,(the carriers) but you can find them(the apn settings) easily with google, since they (carriers) all post their apn settings on their webpages.
Don't forget to save the apn settings.
Now select it.
Now reboot, since it couldn't hurt, right?
If you've done everything right you should now have an domestic and international unlocked Sprint galaxy s4. Enjoy.
I suppose you could now reflash the new modem back onto the phone, but I don't have firsthand knowledge whether this works or not- I've only read that others have said that it works. Remember, ONLY FLASH THE MODEM, the rest isn't necessary and will probably knox you all up
All I did was list these things- credit goes to all those who were linked in the above post. Thanks for all you do.
On stock 4.3 and higher you can go into settings and change your APN, so there's no reason to root and mess around with build.prop editor.
Every time i try this i cant get my wifi back up when i flash back to the nae modem. If i could get pass that then I'll definetly be do that.
can the modem be downgraded
mine came with mk2
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
tomy1986.nt said:
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
Click to expand...
Click to collapse
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
You can downgrade modem, but can not downgrade bootloader (aboot)
Sent from my Phone using Tapatalk
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
goblue30093 said:
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
Click to expand...
Click to collapse
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
ecs87 said:
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
goblue30093 said:
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
Click to expand...
Click to collapse
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
tmobile rom
jaywaka2713 said:
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
Click to expand...
Click to collapse
hi can you tell me where I can download 4.4.2 samsung s4 T-mobile odexed rom for l720. thanks.
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Imeisv visible, definitely unlocked as i can make calls texts and use edge data on redpocket mobile (att mvno)
But in phone number I still see my sprint number and I can't get hspa (picking the wcdma all gives me red x no bars, picking gsm all gives me full bars and edge data)
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Crossvxm said:
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Click to expand...
Click to collapse
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
ecs87 said:
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Must be an issue with my PC, nothing new...
And I know a thing or two about QPST. I still have it on my computer from a few days ago from when I was fixing a horribly corrupted IMEI on a G2 a friend of mine bought. I'm assuming I have to use a NAE stock tar with ODIN, because I tried a ROM of it and it lags and stays on black screens for seconds and WiFi doesn't work im sure because of the fact that the modem is older than the rom. Let's see if that works cause ive been trying to flash back to any stock ROM since I got this thing yesterday.
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
daniel4653 said:
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
Click to expand...
Click to collapse
Yeah I remember that part but from what I was understanding, that's for the international. Domestic requires messing with some files and done. I already got the international part by tossing CM10.2 along with the MDC modem because stock Touch wiz would cause lag and reboots and non working wifi I'm assuming because of the mismatched combo. I DO know that obviously we need a TW rom in order to unlock domestic.
EDIT: I finally got the hint and got it to work. But I only get Edge instead of 3G. Does anyone know where I may be able to find that T-Mobile rom made for us? When I Google it I end up on the T-Mobile side.
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
I downgraded from latest bootloader on 4.4.2 or was it 4.4.4? Down to 4.3 which is the absolute best ROM version for service mode menu. It got me into service mode menu on first try by selecting menu back and input of 1. What I did was first install cf autoroot to root then cwm and used cwm to flash the 4.3 stock deodexed, I only used Odin for flashing modem. Odin gave me an error when flashing modem and phone got stuck in kies mode but i got it to get unstuck by just flashing cf auto root again to make the kies mode error thingy think odin flash has went well. Turns out MDC modem flashed despite odin error.
Anyways. While on 4.3 and MDC modem I noticed no WiFi but I had sound. I followed the international and domestic unlock instructions and WiFi was still broke when I got back to 4.4.2 but I had unlock and sim card working and got bars. I am on aosp 4.4.4 now and the nae modem I finally flashed works well with this ROM but soon I gotta go to touchwhiz 4.4.4. If I go to 4.4.4 touch whiz WiFi and all else will work fine just as they do on slim aosp . 4.4.2 touchwhiz is still not giving me wifi on NAE modem. Update NAE 4.4.2 stock deodexed rooted rom i got from xda android thread did the trick and all works well now. All is perfectly working after i flashed it in cwm.
For aosp lovers. aosp requires additional things to do so aosp dialer can make and receive calls fine. I can call but there are issues until I follow another guide on xda that resolves those issues on aosp ROMs using sprint s4.
http://forum.xda-developers.com/showthread.php?t=2539794
If you see system slow, no wifi, no audio and lockscreen being nearly impossible to unlock, its due to you being on a higher ROM than the modem was meant for.