No connection - G1 Q&A, Help & Troubleshooting

Background: Switched to backup battery pack, lost internet service. Rebooted a few times, then had no reception at all.
I backed up and wiped, but nope. I'm guessing the SIM card's damaged? (happened before)
So I need to call Tmobile. Before I call Tmobile, though, I need to downgrade and unroot. So I went back to RC 29 with DREAIMG.nbh as usual (done this before. kiiiiinda getting sick of the g1 now.)
Now I have original SPL and have RC29. Also have RA recovery, but I can reapply dreaimg and get rid of that.
Problem: I need to upgrade my phone, since it'd be kinda weird if I called and I said I was on RC29. Thing is, either cellphone reception is needed for OTA updates (that is, non-wifi internet connection), or they're simply not supplying OTA updates for the 29.
I guess I need to manually update, but that would require root (which I have, but need to get rid of before I call t-mo). If you have a way to update an RC29 to 1.6, or have a way to unroot without using DREAIMG.nbh, please post. Also might need a link to the standard, no-root 1.6 file.
If there are any questions, or at some point in the above post i was spouting nonsense, please tell me.
Thanks!

Related

Rogers Dream questions

I realize there are numerous threads about the phone, but I have several questions and I don't think they fit into any single thread. Merge this if necessary.
First of all, the phone in question ran on Dwang's rom using EBI0 root hack. After the 911 bug thing with Rogers, they disabled the internet and the phone did not have data and sms. I found out about Cyanogen's radio update trick and proceeded to try it. I flashed the latest Cyanogen rom first, then did the radio update with the EBI1 kernel patch. The phone boot up normally.
Several days later (haven't used the phone), I realized another problem. Data and sms came back, but now I can't call or receive. Has anyone any idea about this problem?
[edit] Realized it is a temporary issue (one of many) with Rogers as other people I know can't call either.
I also pulled the battery out for some reason and noticed it was bloated/fatter/expanded/etc. Went to Rogers store and they were going to replace whole phone instead of just the battery. They're probably doing that to ensure I get a phone with the unrootable update.
Question is: Will Rogers realize if I send the new phone back with the old battery?
yingjai said:
Question is: Will Rogers realize if I send the new phone back with the old battery?
Click to expand...
Click to collapse
Yes due to IMEI, but if they ask just say you didnt need the phone.

HTC Dream losing 3G?

I'm wondering if anyone else ever came across this weird issue. I am on the Rogers network with a HTC Dream. I've tryed several ROMs and none make a difference. The issue is, I lose 3G connection and my SIM card gets corrupted. I have a LG GW620 and I used it for a long time and this never happened. What happens is I totally lose 3g capability and I can't get it on any other phone unless I get another SIM card activated. I've had this happen to me twice now and it ONLY happens when I used my HTC Dream for couple weeks it seems. Could this be due to that my phone is using roms or is my phone just mangled? I'm just thinking of smashing this phone with a hammer as it is useless to me if my 3G connection is gone.
Any information would be appreciated.
Thanks
IIf you currently have radio 3.22.26.17, please find and download the 3.22.20.17 radio image and flash via fastboot 'fastboot flash radio-3.22.20.17.img'
The image is on bcrooks server.
Please note the imei-sv is 3 in 3.22.26.17 but 2 in 3.22.20.17, this means if you are a rogers/Fido customer with a rogers branded dream you will be flagged by rogers for not having the e911 rom.. and thus they will disable your data if you have not filled the wavier. To reactive a call to the call center is usually required (preferably on a phone other than the cell in question)
Note the radio has nothing to do with the e911 issue, as the bug was in android not the radio.. so if you have signed the wavier or are not a rogers customer feel free to use 3.22.20.17.. of if preferred downgrade to 2.x via fastboot
(its unknown if the lattest 2.x or the older 3.x provides better signal on the Rogers network .. but the newer 3.x has problems in every rom.. including the official one HTC/rogers forced on everyone, sad since the bug was just in the Java code of one file on the phone in /system.. nothing to do with the radio)
Alright just let me get this straight.
So they are flagging me because of my phone, or radio? I am a Rogers Customer, have been since 2004 I believe. How would I go about getting data to not dissapear on my phone again? I had just bought this phone used and rooted it and put on a custom OS. I'm not exactly sure which radio I have at the moment, but if i update to 3.22.20.17 would that fix the issue if I got rogers to re-activate my data?
What radio do you have now
I believe this one is on there.
Radio Image update 2.22.23.02
So if I update to Radio 3.22.26.17 via Fastboot and call the support line to re-activate my data or w.e that will work?
Not quite that simple your current rom wont work with the 3.x radio as is..
I recommend one of two things..
1) goto http://rogers.com/htcwaiver and sign it.. then call rogers saying you signed the waiver and want data back.. if it fails tell them that..
2) if this is a rogers branded dream and I assume it is unroot to the stock e911 patched rogers rom and start from scratch on android 1.5 .. this is not optimal and I highly recommend option 1.. and you still may need to call after to get data back http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
Huge low blow in Rogers case. Plus I have to call them cause they say my number does not exist when I put it in that Waiver. What a joke in my opinion.
Thanks for the information though. Much appreciated.

[Q] Rogers Dream and non-working 2G/3G

I have a Rogers Dream on the Rogers network with the old radio and eng spl which I tried to upgrade. It was already rooted and working with CM6.1, but I tried to flash the new radio and spl on it.
I flashed hboot-1.33.0013d.img and radio-2.22.27.08.img.
I wiped everything and reflashed CM6.1 and realized that the phone no longer connects to EDGE or 3G. It can still connect to the internet through wifi.
This is actually my wife's phone and I did this a while ago, so I don't remember that clearly, but correct me if I'm wrong, the board is supposed to be 32A on a Rogers Dream right?
I finally decided to try and revert to the old radio / spl and see if that would fix the problem, but she still doesn't have data connection.
I flashed radio-3.22.26.17_dream.img with hboot-1.33.2005.img, but bootloader still says 32B. Is there something I'm doing wrong?
remember that e911 upgrade... They forced you to upgrade or cut data.. what they are checking for is that you have installed that craptastic radio that keeps dropping 3g until you either giveup and use 2g only, or go to airplane mode and back.
If you change to *ANY* other radio rogers then blocks your data.
Take a spin: http://www.rogers.com/htcwaiver/
you win if it works (data back in 24h or so and you can use the new radio.. call if you need then to be more proactive)..
-1 point for invalid IMEI,
-2 points for invalid mobile number.
(note to self never buy a phone a on contract [didn't but a reminder] or from a Canadian carrier I may ever use.. ie. phone must be unlocked from an independent source)
I guess I have to call them, their website conveniently says I entered an invalid IMEI code.
Which version was the Rogers radio that worked anyway?
yingjai said:
I guess I have to call them, their website conveniently says I entered an invalid IMEI code.
Which version was the Rogers radio that worked anyway?
Click to expand...
Click to collapse
um 3.22.26.17 was the one that they won't disable your data.. "worked" is a bad word for it since it has a nasty habit of dropping 3g.. if you are calling them anyway ask to sign the wavier.. you may want to upgrade to the e911 update with 3.22.26.17 + re-root to an ebi1 rom until they actually add you .. then fastboot back to 2.22.28.25 + 2708+ kernel
So they won't let me sign the waiver if i have the 2.22.28.25 + 2708+ kernel?
I just rerooted her phone trying to fix things and reflashed that stuff...
yingjai said:
So they won't let me sign the waiver if i have the 2.22.28.25 + 2708+ kernel?
I just rerooted her phone trying to fix things and reflashed that stuff...
Click to expand...
Click to collapse
If you are on the list its fine to install 2.22.28.25, but if there will be a delay before you are added.. 3.22.26.17 may be better while you wait for them to add you or you may get the boot again while you wait to be officially on the list
boot as in they'll say no if i ask to sign the waiver? what's the point of the waiver if i already have the radio?

[Q] .905 update fail

Stock rooted rom, gsm radio on, TMO sim card installed. Everytime I try to update my phone, it tells me that I need to be a member of Motorola Services. But when I go through the motions to sign up, the system wont let me connect.
Did I screw up my phone and not realize it somewhere.
Also a side note. Everytime I disconnect from wifi, I get a download icon that says "Download suspended. Will resume shortly..."
Don't think you are going to be able to take OTA while running a TMO sim. Have you looked through: http://forum.xda-developers.com/showthread.php?t=1297714
Yup, read every page. Un-rooted, return to complete stock, put VZ sim card back in. Still no joy. Still tells me I need to be a member of Motorola services. Cheesecake does the same thing. I'm about ready to use Dragon to put a few holes through the phone.

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

Categories

Resources