Database Info

Updated: JB nav issue also on 100% stock ROMs

EDIT 3/16: After more detailed testing during the day today I withdraw all of the claims below. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text below intact for context.
------------------
It would appear that the JB nav issue some of us are plagued with is exclusively due to something devs are doing with their custom ROMs. Here is why...
I am one of the unlucky ppl who could not get Nav to work with JB. I have tried multiple custom ROMs, including stock rooted, and nav always crashes within two minutes. Today I RUU-ed back to 2.20, changed CID to AT&T, took the official OTA and played with Nav without a hickup for 30 mins. I then unlocked again, Super_CID-ed and flashed CleanROM 6 R2. Nav immediately went haywire with the same symptoms as before. I then went through the RUU and OTA process once again, and Nav purrs like a kitten.
Not sure what custom ROMs are doing to mess up things...but the above suggests that something common that devs use to root is interacting incorrectly with JB on some phones. We seem to be a minority of users, as busy as our devs are we may get no love.
At this point I will stick with AT&T true stock for a while, will just flash a custom recovery and debloat it to an extent with the TWRP file manager or just slim down update.zip.

Re: JB nav issue seems to be caused by custom ROMs
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2

Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.

pablo11 said:
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It is well documented that only some HTC phones suffer from this problem. It has been seen on the HOX, the EVO, even on some SG3s. This is what has made it so maddeningly frustrating. It affects a small fraction of the users, so the devs don't spend any time trying to address it. Not blaming the devs, they can't go after every small issue. However, for those of us unfortunate enough to have it it has been a PITA.
slippers67 said:
Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.
Click to expand...
Click to collapse
Yes, I tried AT&T stock rooted, no dice. The ONLY thing that has worked so far is 100% stock unrooted OTA.

Re: JB nav issue seems to be caused by custom ROMs
don't know much about it, but I have the issue and I am most puzzled why the app hasn't had an update with bug fix. It's been too long an issue for the official channels not to have been noticed. If it IS ONLY custom roms, I wouldn't be surprised of the official channels just ignored the bug.
I initially thought maybe HTC made a deal with Google too break nav so people would start paying for a subscription to the HTC nav app. But I just use waze now. It seems to find better routes anyway.
This post was created and transmitted completely in analog.

I thought we had already covered it .. isn't it some people have a little diff hardware then others I think one member suggested gyroscopes differentiations being the problem...but I've never had a problem with nav on any jb sense rom nor jb in general ... It shouldnt be caused by custom roms as that doesnt make sense

Re: JB nav issue seems to be caused by custom ROMs
It really would be nice to see a firmware upgrade pack for the hox. It seems we actually need it.
Sent from my HTC One X using xda premium

Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.

slippers67 said:
Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
Click to expand...
Click to collapse
I already did this and try to convey it in the OP but perhaps was not clear.
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was done
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
Click to expand...
Click to collapse
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.
Click to expand...
Click to collapse
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.

GroovyGeek said:
I already did this and try to convey it in the OP but perhaps was not clear.
This was done
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.
Click to expand...
Click to collapse
Don't use CR6.2. Use the stock 3.18 rom he released. Then restore the boot.img from the backup. At that point, the only difference will be the different recovery on your phone, as everything else will be the same as taking the OTA.

I've had the issue but only after updating to the latest ViperXL OTA.

After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.

GroovyGeek said:
After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.
Click to expand...
Click to collapse
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL

ECEXCURSION said:
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL
Click to expand...
Click to collapse
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?

GroovyGeek said:
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?
Click to expand...
Click to collapse
I'm confused. This phone was released 11 months ago. Announced 13 months ago.
10 months in the US, even.

Not sure why groovygeek thinks the phone was released so long ago... May 9th 2012 in the US.
Sent from my HTC One XL
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
For those with the nav crashing, are you charging the phone when this happens? Does it cash both ways?
Sent from my HTC One XL

I have two phones bought at the same time. One is stock unrooted and runs the OTA 3.18 with no google maps crashes. My phone as described in my sig has map crashes always. I haven't jumped around to many other JB roms besides Viper to this point because they all seemed to be having issues with the JB and Google Maps. Didn't have any crashes with ICS.

Just wanted to say that many one s owners are experiencing the same problem.
Sent from my HTC One XL

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.

uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium

good flashing

uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

[Q] Bizarre Sound Issue with New Phone??

Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!

Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..

lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...

sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable

vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.

econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.

Boot into recovery and factory reset from there. That should clear up the boot loop issue.

theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:

CM 10.2 "stable" build crashing

I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.

stjake said:
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
Click to expand...
Click to collapse
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)

CWGSM3VO said:
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
Click to expand...
Click to collapse
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.

stjake said:
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
Click to expand...
Click to collapse
By their very nature, Nightlies are not considered stable in the strictest sense of the word. For most of us, they have been. But if you need reliability over cutting-edge, I'd stick with 10.2 or one of the CM11 Milestone builds (however, the RAZR HD only has one that I know of, CM11-M2).
My personal take is that given you're in an area with poor reception, choosing CM11 over CM10.2 (for example) wouldn't give you any better results over the other. Signal is signal.
My suggestion, given your circumstances and criteria, would be to stick with 10.2 but do a FULL backup via Recovery of your stock ROM (or whatever you're using instead of CyanognMod) and then do a FULL wipe of the following (and only these):
- user data
- /system partition
- /cache partition
- dalvik cache (usually found under Advanced in CWM recoveries)
Your phone will be in an unusable state after this. From here, still in Recovery, flash CM10.2 and then the appropriate GApps (make sure you choose the right one; a 4.4.2 GApps isn't suitable for a 4.3 OS) and reboot. If memory serves, CM10.2 is Android 4.3.1
If you're still having problems, you can restore your backup in Recovery or worst case, RSDLite the appropriate SBF for your phone to return to the carrier-stock ROM. But be aware if you chose the RSDLite path, you will lose everything. Basically it'll be like day-1 when you got the phone

Unroot help!!!
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!

Lanevox said:
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Click to expand...
Click to collapse
Find the FXZ you want to flash and use RSD or House of Moto to flash it.

[Q] Which Cyanogen ver. for KK 4.4.2 after using AutoRec?

Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:

Nevermind, I got it working.

fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?

fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.

Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?