Database Develop

Can't use a Phone as a Phone

So I flashed my Captivate with Serpendity or whatever, and my sim card didn't work. I flashed cognition, and I even flashed stock. I tried master clear and everything.
My sim still isnt working.
Im not just understanding whats going on. I hope its the sim card, but it was working before I did this, and it wasnt in the whole time.
I followed the directions and and search the forums, and Im not getting any help as to why this might have occured.
Please, whats the use of a phone if I can't communicate with people.
I would really appreciate it.

what you should have done, instead of flashing around after serendipity, is:
1. unplug phone from computer
2. reboot
and if it still doesn't work, post on the serendipity thread.
hope that helps, and keep me updated.

absolutechaos92 said:
So I flashed my Captivate with Serpendity or whatever, and my sim card didn't work. I flashed cognition, and I even flashed stock. I tried master clear and everything.
My sim still isnt working.
Im not just understanding whats going on. I hope its the sim card, but it was working before I did this, and it wasnt in the whole time.
I followed the directions and and search the forums, and Im not getting any help as to why this might have occured.
Please, whats the use of a phone if I can't communicate with people.
I would really appreciate it.
Click to expand...
Click to collapse
When the phone is powered on, go to Settings, About Phone. Do you see a kernel version listed, are there any blanks? Also, try going to your dialer and dial *#1234# After you press the last # sign it should take you to an info menu. See if you have any blank areas.
I've had this happen in the past and for some reason I had a bad kernel or modem flash. Either way my sim wasn't seen.
My fix was to go to the samfirmware.com site and picked up a stock ROM like JF6. These version use Odin but they are not 1-click. So you download the ROM, 512 Pit, and regular Odin. When you unpack the ROM you will have the CSC, Modem, and Phone files. Try flashing that way. Setup is the same as one-click, but in odin you actually have to specify the files you are flashing.

I want back to stock. That didnt help. But thanks. At&t rushed delivered me a new Sim card in one day. No worries. But I flashed Serendipity or whatever to have 2.2 and now I have 2.2 and a working sim card.
Yes !
I help this don't happen again.

Not Recieving text
So after enjoying having service again. Now Im not receiving or sending texts. I can make and receive phone calls. This whole things is really annoying, and I doubt I'm going to flash again.
Im on serendipity. 3.5 or something.
Please help.

absolutechaos92 said:
So after enjoying having service again. Now Im not receiving or sending texts. I can make and receive phone calls. This whole things is really annoying, and I doubt I'm going to flash again.
Im on serendipity. 3.5 or something.
Please help.
Click to expand...
Click to collapse
Have you checked our APN ?? You seem to have flashed alot lately so my guess is your final rom as not installed your provider APN and you must add them manually.

It wasn't the Rom fault. Somehow and I dont know how, messaging was removed from my Att service plan.
But while I got some attention. Serendipity 4.1 just came out, is it safe to stay on 3.5 because Im scared of flashing and breaking something again.

XT862/XT860/XT883 Radio Tweaking with RadioComm?

I have been fiddling with RadioComm v11.11.11 (is this the latest version?), and there are some sections that deal with the TX power and other items for the radio. Has anyone successfully tweaked the radios on these devices? I am running a XT862 with a Xt883 radio, on T-Mobile. The reception of this phone is pretty bad, and it takes it a LONG time to find signal again, once you get it into a known good reception area. Any ideas/pointers?

Did you try using CM9 for some reason I get better reception on it.

nemiroG1 said:
I have been fiddling with RadioComm v11.11.11 (is this the latest version?), and there are some sections that deal with the TX power and other items for the radio. Has anyone successfully tweaked the radios on these devices? I am running a XT862 with a Xt883 radio, on T-Mobile. The reception of this phone is pretty bad, and it takes it a LONG time to find signal again, once you get it into a known good reception area. Any ideas/pointers?
Click to expand...
Click to collapse
Does it do this with all roms? It sounds like something may be wrong with your phone. I have had very few issues and I live in a notoriously poor reception area for both AT&T and T-Mobile.
Also, are you running the updated build.prop? I added some signal improvements in the v2 file.

It has done it with .894, .905 and now on .906. I realize these are VZW CDMA ROMs. Not sure if something is hanging around in there. I also have not tried swapping out any of the RIL files. Should I? I've made my own build.prop (attached), renamed build.txt, for the .906 VZW build. It gets GSM and EDGE data on T-Mobile. Would you mind looking it over? If it can be tweaked, I'm all over it!
I have tried flashing CM9, and it just keeps giving me boot loop issues. I will download the latest, and try it tonight.

nemiroG1 said:
It has done it with .894, .905 and now on .906. I realize these are VZW CDMA ROMs. Not sure if something is hanging around in there. I also have not tried swapping out any of the RIL files. Should I? I've made my own build.prop (attached), renamed build.txt, for the .906 VZW build. It gets GSM and EDGE data on T-Mobile. Would you mind looking it over? If it can be tweaked, I'm all over it!
I have tried flashing CM9, and it just keeps giving me boot loop issues. I will download the latest, and try it tonight.
Click to expand...
Click to collapse
It should not matter since the radio is independent. Only some custom roms might have issues with GSM. Stock Verizon would be the best place to test reception issues.
Try this build.prop on your existing rom and see if it makes any difference:
http://forum.xda-developers.com/showthread.php?t=1406812&page=8

Hi, I forget to enter my unlock code and I just flashed the phone with XT 883, so no GSM sim is not working even is not asking for activation code, only CDMA sim is working. How I can get back the verzion ROM to enter the unlock code ? Please help me out

radiocomm
radiocomm-I have 11.12.2- here it is if u need it
https://www.dropbox.com/s/ctgg9obrjdkf1in/RadioComm_v11.12.2_Install.msi

Not the latest version,the latest version is 12.xx

can u post it
Can u post it or pm me,I like to stay on top o the newest of the radiocomms,thanks for the reply

I9000L no signal issue.....

Well, just as the title says. I have an I9000L in here that has no signal. Thought it might be an issue with csc files since it was updated to ICS, but then i flashed it back to gingerbread and nothing change. I used the stock rom with no luck, problem is that it shows imei, baseband and everything in place. Thinking it might be a hardware problem to this point. But i oppened it and everything seems in place. Just wondering if it may have a burned baseband chip. But then again it shows the baseband version so my guess is thats not the case. Could someone help me on this???

enelyam said:
But then again it shows the baseband version so my guess is thats not the case. Could someone help me on this???
Click to expand...
Click to collapse
Check your network settings
menu.settings>wireless and networks > mobile networks
or try https://play.google.com/store/apps/...SwxLDEsImNvbS5ha3ZlbG9uLnNpZ25hbHRyYWNrZXIiXQ..

Nope, no luck with the apk. Neither checking network or anything like that. The phone will just not allow me to do so. Like i said, the weird thing is that everythin seems to be working fine. I have an efs backup so i deleted the nv_data.bin to check if the phone is creating a new one and it is. It shows baseband, imei and everything. im starting to guess its a hardware failure but then again. The phone is almost brand new. I mean it was bought not too long ago. It was unlocked, and after flashing it shows multiple csc contents. I have fix something similar to this by applying the PCT csc(Claropr csc). But this time nothing is working...

The reason you didn't have a signal on ics is probably due to the fact you didn't flash a modem from here http://forum.xda-developers.com/showthread.php?t=1158783
[CM7/MIUI/ICS/CM9][06.01.12] Modems + Bootloaders(MD5)
So it might be worth going back to ics, doing that to get your signal back, and then reverting to Sammy Rom to see if that sorts it....btw there are no csc files on aosp/cm9 Roms

Okay thanks M8, one other thing. Initially the phone had signal on ICS. It was DOCs ICS if i can remember. I think that custom firmware will flash a new modem? Or not? And is it possible that it had signal and lost it because of that? Anyways thanks i will give it a try then....

enelyam said:
Okay thanks M8, one other thing. Initially the phone had signal on ICS. It was DOCs ICS if i can remember. I think that custom firmware will flash a new modem? Or not? And is it possible that it had signal and lost it because of that? Anyways thanks i will give it a try then....
Click to expand...
Click to collapse
Some ics Roms do, some don't, you can always flash another in recovery of the one that comes with Rom is no good for your region

ALWAYS make sure you are using the right radio for your phone. It solves many network issues

Ok then so i guess it might be a hardware issue if thats the case. Because i have use that rom before on a i9000 and never seen something like this. Hummm! Ive done just about everything and i cant still get signal. Goshhh! I rather have the phone showing no baseband or something than dealing with this....

You have checked your apn settings haven't you?!

Yeap M8 APN settings are correct. But in fact APN settings have nothing to do with the cell phone signal in terms of calls. If your phone is working it will receive the signal. The APN settings as far as im concerned will just set the internet and mms settings. Maybe with them set the phone will try to reach the towers(Antennas) but anyways the APN settings are correct.

[Q] Unlock and Radio Issue, Please Help

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.

[Q] Unrooting HTC One running 3.04.651.2 with hboot 1.55

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...