Database Info

[Q] What Would YOU Do

Hi All -
So I'm posing a somewhat esoteric question. If you were starting with a new Android device tomorrow, what would you do to it to make it your own?
Root? Unlock? New ROM? Must Have Apps?
Here is the reason for my question. I am ABOUT to be the proud new owner of a Nexus S that should arrive tomorrow. I'm completely new to Android, but am a self proclaimed computer geek and have been an iPhone user since their inception and I just want a new challenge.
I'm on AT&T in the US and bought the i9020A. From what I have read, I will want to get the 2.3.4 update that is now available, and will also want to flash the radio to KB3 to get uncapped data speeds on Ma'Bell...
But what else??

I am pretty much in the same situation.
Bought the NS last Saturday but still far from home (and so having time to evaluate whether to root or not).
Meanwhile you can easily update to 2.3.4 going to the proper menu.

If you are new to Android it might be a good idea to just use it as is for a while. Get used to how everything works and where everything is.
Once you have a good understanding of how to use the OS you can then venture out and flash custom roms and since you've used stock Android you'll be able to spot the changes people have made and appreciate the new functionalities more.
If you are coming from iPhone a lot of the things that you can do only with jail breaking can be done out of the box on Android. You can customise your phone a lot without rooting or flashing a custom rom. One example which comes to mind is the transitions between home screens. On Android switching to any of the popular homescreen replacements (LauncherPro or ADW) will allow you to have many different transition styles.
When using Android you just have to keep in mind that practically everything is customisable. If you really want to you can change individual graphics in the OS. Anyway, congratulations on your new purchase, I do hope you enjoy it and welcome to Android!

ttcrew said:
Hi All -
So I'm posing a somewhat esoteric question. If you were starting with a new Android device tomorrow, what would you do to it to make it your own?
Root? Unlock? New ROM? Must Have Apps?
Here is the reason for my question. I am ABOUT to be the proud new owner of a Nexus S that should arrive tomorrow. I'm completely new to Android, but am a self proclaimed computer geek and have been an iPhone user since their inception and I just want a new challenge.
I'm on AT&T in the US and bought the i9020A. From what I have read, I will want to get the 2.3.4 update that is now available, and will also want to flash the radio to KB3 to get uncapped data speeds on Ma'Bell...
But what else??
Click to expand...
Click to collapse
I was in you shoes a few months ago, Nexus S was my first ever android device, i was on stock for 2 days then flash cyanogenmod.
In short, do everything you said xD. The differences between custom and stock ROMS are HUGE, especially in Cyanogen Mod

I would update to the latest official Nexus S firmware first (to get the latest radio, etc): http://forum.xda-developers.com/showthread.php?t=1056062
Then unlock the bootloader, flash latest cwm recovery, nandroid backup, flash the latest CM7 nightly, flash latest gapps, then reboot.
Enjoy your new Nexus S with CyanogenMOD 7.
All this can be done without fully booting up your Nexus S.
PS: (KB3 is not the latest radio, KD1 is)

I'm just going to say that I was on stock unrooted Android 2.2 HTC Evo for 4 months before I ever rooted and flashed Cyanogenmod 6. And I'm really glad I had that time. I appreciated the customizations so much, and really understood why they were a big deal.
I've moved to the Nexus now and had it for a month. I'm back to stock for a while and loving it. Not sure if I will root or flash CM again. Its just not as necessary in the Nexus. Its possible to have a great Android experience without it. Not so true on other phones.
Anyways, I agree that you should run stock for a while until you are feeling really comfortable with all the nuances of the OS.
Sent from my Nexus S using XDA App

If you want to the rooted/custom rom route straight away might I suggest you give miui a go. It is quite possibly one of the most customised and visually polished Android roms available.

ttcrew said:
Hi All -
So I'm posing a somewhat esoteric question. If you were starting with a new Android device tomorrow, what would you do to it to make it your own?
Root? Unlock? New ROM? Must Have Apps?
Here is the reason for my question. I am ABOUT to be the proud new owner of a Nexus S that should arrive tomorrow. I'm completely new to Android, but am a self proclaimed computer geek and have been an iPhone user since their inception and I just want a new challenge.
I'm on AT&T in the US and bought the i9020A. From what I have read, I will want to get the 2.3.4 update that is now available, and will also want to flash the radio to KB3 to get uncapped data speeds on Ma'Bell...
But what else??
Click to expand...
Click to collapse
The phone stock is very nice, so you might not have to jump into flashing ROMS ATM. Rooting though gives you alot of options. One being is for titanium backup.
Best backup app on the market IMHO. Android at default lacks a way to backup app data. Say u drop your phone get a replacement and now all the angry birds levels you beat are gone.

nxt said:
I would update to the latest official Nexus S firmware first (to get the latest radio, etc): http://forum.xda-developers.com/showthread.php?t=1056062
Then unlock the bootloader, flash latest cwm recovery, nandroid backup, flash the latest CM7 nightly, flash latest gapps, then reboot.
Enjoy your new Nexus S with CyanogenMOD 7.
All this can be done without fully booting up your Nexus S.
PS: (KB3 is not the latest radio, KD1 is)
Click to expand...
Click to collapse
Hey - Thanks for the info!! You mention that KD1 is the latest radio, but I've read that KD1 still suffers from the speed capping issues and that KB3 is the radio to use if you want full speed 3G connections over AT&Ts cell network.

BrianDigital said:
The phone stock is very nice, so you might not have to jump into flashing ROMS ATM. Rooting though gives you alot of options. One being is for titanium backup.
Best backup app on the market IMHO. Android at default lacks a way to backup app data. Say u drop your phone get a replacement and now all the angry birds levels you beat are gone.
Click to expand...
Click to collapse
Thanks for the feedback - is it your contention that Titanium Backup is better than some of the other backup methodologies ... i.e. Nandroid?

ttcrew said:
Thanks for the feedback - is it your contention that Titanium Backup is better than some of the other backup methodologies ... i.e. Nandroid?
Click to expand...
Click to collapse
Titanium Backup is the best for backing up all your apps and system settings, nothing compares ie. installs busybox for you, can sync to dropbox and etc. Look for your self its saved me plenty of time and reconfiguring a lot. But you need to be carefully with it if going from Stock ROM to Custom. As for a nandroid backup, that is a backup of your entire ROM from the phone. Its a function in Clockwork Recovery.

Where is my 2.3.4?!
guildamx said:
Meanwhile you can easily update to 2.3.4 going to the proper menu.
Click to expand...
Click to collapse
I feel like I'm missing out on a secret menu, my nexus has yet to update! Not sure why.. I thought it was due to my carrier. But if the NS is pure google experience that shouldn't impede my update. N1 users have their update! Where is mine!

Flash SuperAosp! Such a tasty rom.. Makes my phone feel so satisfyingly fast

Thanks everyone for the suggestions!!
Here's what I decided to do...
I got my phone, immediately unlocked the bootloader and rooted (installed Clockwork Recovery).
Once rooted, I installed the KB3 radio (immediately see speed improvements - went from .51Mbps Down, and .14Mbps Up to 2.10Mbps Down and 1.12 Mbps up - equivalent if not better than what I was getting on my iPhone).
I think I'll take the majority of the advice I got on here and stick with the stock ROM for now - that's why we bought Vanilla Google, right? I'll play with that for a while and get familiar then go for a custom ROM.
Thanks again everybody...you guys were really helpful and welcoming to an Android N00b!!

[Q] I can't decide, to flash or not to flash...

I can't decide, and I'd appreciate your advice. I'm kind of noob. I flashed a custom ROM on my mytouch 4g. And I only did it once. Afterwards, I kind of regretted it because the ROM seemed to be more buggy than the stock. Now, I'm waiting to get ICS on my sensation, but I keep looking through the threads at the ICS ROMs that are already out there and they look sweet. I'm not sure if I want to wait for the ICS OTA, or just flash a custom ROM. The only things that are stopping me from rooting my phone are the fact that I am kind of a noob, and I don't want to flash then have the OTA happen the next day, and have it screw with my stuff. Would I be able to go back to stock after the OTA, and then just have tmobile push the OTA? Also, I have a mac... and I'm pretty sure I can't use a mac for flashing new ROMs. I don't mean to be redundant and I hope this doesn't piss anyone off, cause I see a new thread everyday about the new ICS release. Thanks for any feedback.

You can revert back by flashing via RUU, after this you can receive the official OTA when it gets pushed. Now the part about you having a make may cause some problems. I suggest you do some Googling and find a good virtual machine to run Windows with on your Mac.

i would flash
i think you should definitely flash a custom rom. since the sensations release many roms out now have fixed issues of being buggy/ slow and battery draining. im using the newest insertcoin rom and had android hd revolution before that. both are super smooth and fast. as for reverting to a stock rom, i believe all you would have to do is find the update RUU file for the stock rom to go back, this will cause you to lose root, but after you flash a rom you'll probably feel no need to go back. and always make a backup
btw 1st post

I came from the mytouch 4g as well. If you rooted and flashed on that phone you will do just fine on the sensation. The sensation is about 100 times easier to root than the mytouch.
Sent from my HTC Sensation 4G using XDA App

[GUIDE] How to get v21y over the air on G2x

UPDATE 6-15-2012: i just wanted to update the beginning of this post to make it a little clearer, the original text is below
to get the v21y base band on your phone over the air, you have to go back to stock
to do this you need a stock rom, either your own backup or the one from this thread
http://forum.xda-developers.com/showthread.php?t=1248644 (the first and second link is a stock 2.3.3 nandroid which is a zip you extract on your pc and run flash.bat from inside that folder)
if you need the drivers, download the third link.
follow the steps in that thread, it works
if you have your own stock nandroid, just boot into ClockworkMod Recovery and restore it (after you backup whats on your phone now)
then reboot your phone
after restoring either your stock nandroid or the one from the post above, shut your phone off and remove the battery and use NVFlash to restore the stock recovery
http://forum.xda-developers.com/showthread.php?t=1056847
reboot your phone
now that you have your phone like it was from the beginning you can go to System Settings/About Phone and click on Software Update. this should pull down the updated Gingerbread version 2.3.4 and the new baseband v21y. IT WILL OVERWRITE YOUR PHONE AND WILL BE PLAIN STOCK
it takes a few minutes so be patient
once it is done and it rebooted your phone you will have to put ClockworkMod Recovery back on it using NVFlash. then you can flash other roms to your phone
please keep in mind that there is a bluetooth issue with both GB and ICS roms on this baseband and that only a few roms actually support v21y. Owain has written an update file that you flash to get support on any rom with v21y, supposedly it does work on any rom (GB or ICS) but i have not tested it, so read up and test if you want.
as of CM7 RC3 all CM7 builds support v21y
please thank the owners of the threads linked above, their methods worked flawlessly for me and i hope they work for you as well. this was a very easy way for me to get the new baseband. good luck!
original post------------------------------------------------------------------------
i was having a heck of a time trying to get the new baseband installed on my phone. i had all the stuff downloaded and all the instructions ready, had the KDZ file, the LG tool, everything...but i could not get anything to work
so what did work?
well using CWM Recovery i restored my stock backup i had made when i first got the phone (best to save this off the phone as well in a safe place) and then using NVFlash i put the stock recovery back on it
once that was done and i was booted back into stock you can go into the About Phone and choose Software Update (or whatever its called) and check for an update. it found one and proceeded to download a 30meg file. asked if i wanted to apply the update, installed it, and rebooted into a nice shiny new 2.3.4 GB setup with v21y and the new baseband installed!
the CM7 nightly build (June 3) is working great. getting ready to try a couple of others (Buru, EB, Genesis (although i was having a problem there, see that thread))
so its only been one day on it but so far calls are good, gps lock is fast, overall loving my phone even more than before!!

Great that the OTA worked for you, I left my phone stock the whole week it was mentioned about sending it and I checked the software update and it always told me the software update check failed/timed out lol
Sent from my LG-P999

I am extremely pleased with the update.
I had been running a rooted stock ROM + CWM Recovery. I had been dismissing the update notice for weeks now. Finally, earlier this week I flashed back the stock recovery and let the OTA proceed.
Current uptime: 67:59:06
I haven't gone a full day without either a random reboot or a sleep of death in a LONG time.

Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium

edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
which cm7 are you using? i had the last nightly june 3 and could not get mass storage to work

I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks

lamdaman said:
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
Click to expand...
Click to collapse
there were a few people that got a bad motorbooting sound when making calls and lg released an update to the new bb but it was only for people who had the sound issue

its was hard
i swear it was hard trying get it to work but once i found me a stock rom i was all good from there

Can you test if the 6.3.12 nightly has working in call bluetooth?

Joe333x said:
Can you test if the 6.3.12 nightly has working in call bluetooth?
Click to expand...
Click to collapse
i dont believe it was, i just had that installed on my phone and coming to work today i tried to connect it to my car bluetooth and it would not connect. i have an ICS rom on my phone now, hope it works with that...i know it did on EB ICS

updated the first post

Reverted back to stock this morning and installed the OTA update...now i'm back on cm7 with no issues. Great suggestion on an easy way to get the March baseband.
Thanks!
Sent from my LG-P999 using Tapatalk 2

im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi

adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
Use the LG update tool
Sent from my LG-P999 using XDA

adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
you are on stock rom AND stock recovery? data connections good otherwise?

A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.

partylikeaninjastar said:
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
Click to expand...
Click to collapse
yes that will work as well and whether you get a stock rom from the link i posted or the one you posted makes no difference this was just how i did it

Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.

partylikeaninjastar said:
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
Click to expand...
Click to collapse
you're welcome
there is a bluetooth issue with all roms and the new BB so if you use BT you might want to stick with the stock 2.3.4 that you will get with the upgrade. lots of devs are working on that issue so hopefully it wont be long

suggestions?
I followed the instructions in the first post, and now am back on the stock rom (21e, july 15 2011). However, when I go to try the software update, I get the following message: "current version is the latest version." Is there another way to get the new 21y baseband?

should i upgrade from 6.5.5 to 6.7.2?

Is there any difference between 6.5.5 and 6.7.2? I don't want to lose anything on my phone. Would it just flash over everything? I think u put a wrong radio before my signals suck. Is it worth the time and risk of losing ie bricking or should I just stay in 6.5.5. I love it btw thanks to this site.

I'm assuming you mean arhd. Go with 6.7.1 first.make a nandroid when jumping that far up.
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2

That will be a good idea I think I do that with titanium

Yeah, you really should because the new kernels and Jelly Bean animations are pretty nice and battery life and signal seem to have been improved as well. Just remember to use 3.33 firmware. The only downside is that 3.33 ROMS seem to be slightly more prone to rebooting every now and then but other than that, it's worth the upgrade.

Cool. Starting my research now. I assume if I make a backup with titanium I could always go back. Do you know if my app and other data will stay?
Update. I already have 4ext from 6 months ago installed. I was going to nandroid, backup apps and sms. Then flash either.3.33 universal or the one linked for t-mobile. Then flash the arhd 1.2.2 t-mobile rom. I hope I'm not missing anything. Maybe I can skip superwipe?

chopt51 said:
Cool. Starting my research now. I assume if I make a backup with titanium I could always go back. Do you know if my app and other data will stay?
Update. I already have 4ext from 6 months ago installed. I was going to nandroid, backup apps and sms. Then flash either.3.33 universal or the one linked for t-mobile. Then flash the arhd 1.2.2 t-mobile rom. I hope I'm not missing anything. Maybe I can skip superwipe?
Click to expand...
Click to collapse
Hi,
Superwipe is essential when making such a jump in versions.

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