Database Info

rooted, stock-ROM, rejected update .... what now?

OK, I rooted my t-bolt but haven't done any custom ROM flashing yet. I checked today for the s/ware update and when it found it I chose "reject" ... 2 questions..
First, will this sucker eventually push to my phone automatically via VZW?
Second, should I install another radio (and if so for what reason?). I do have some intermittent GPS weather issues (right now it says I'm in Vosu, which I think is near Finland somewhere --- I can assure you the phone is wrong) but IDK if this OTA (or leaked) update addresses that or something different.
I do plan on, one day, running a custom ROM I'm just not ready for that yet. I would update the radio though if it does something for service or whatever.
Advice, thank you.

The new radio is a piece of ****. Don't bother with it. I don't think that HTC pushes silent updates so I wouldn't worry about it. Just check your software version to make sure you're still running the stock radio.

everytime i have had a rooted phone, OTA updates did not succeed in installing itself, even if i agree to the update, and am not running custom roms

So, I guess if it asks me I'll just keep telling it 'reject' - it told me where I could find it if I needed it again, lol.

this will stop it from asking
http://forum.xda-developers.com/showthread.php?t=1077405
or showing up
and the OTA is the same the leak here by jcase and radio is also same as leak so if you flashed new mecha and flased new radio in hboot and ran this buildprop
you would be up to date like the rest just rooted atleast

[Q] Trying to bring I9020A back to stock?

I am sending my phone back into samsung for repair, and I want to bring it back to its stock condition. I have unlocked the bootloader, flashed CW recovery, and installed superuser with no problems, however cannot seem to figure how to go into reverse. I understand how to re-lock the bootloader. I have read on the forums through the countless amounts of people asking this. I am however trying to use the ROM for the GTJ61 build found from this thread http://forum.xda-developers.com/showthread.php?p=13478981 When I try to use Clockwork Recovery, and go to restore, it states there is a MD5 mismatch. Am I suppose to install from zip or update from SD with CWR, or should I try to flash everything back onto there? I do not know what to do. Am I even trying to use the right ROM? The GTJ61 build is the original build that came on my phone, but would another one work?

follow this thread http://forum.xda-developers.com/showthread.php?t=1033269
all you have to do is clear your data, flash the stock rom and stock recovery, and then lock the bootloader

Thank you very much. I figured it out. All I have to do now is destroy the evidence on my sd and seen my NS away.

I realize superuser is still alive and well after I did everything. How I would I get rid of it?

I just uninstalled it. it might have gotten restored when you logged in with your gmail account. did you wipe data and the cache with cwm before you flashed the rom?
edit: did the ots update to 2.3.4 install fine for you?

I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.

SleepyFox said:
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
Click to expand...
Click to collapse
I did mean ota lol. my bad. where'd you get a 2.3.4 rom from?
edit: if you used the 2.3.4 rom from the thread you posted, just be aware that it isn't official. i'm not sure if the link I posted has the official rom, but you can download OTA updates with it so I would assume that it's pretty damn official lol

I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?

SleepyFox said:
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
Click to expand...
Click to collapse
I don't know much about it either, but I would assume that you should put it on a stock rom if you're sending it back into samsung. I could be totally wrong though

I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.

SleepyFox said:
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
Click to expand...
Click to collapse
I would guess that superuser would be one of the first things they check for to see if you broke warranty. you could just uninstall it and wipe everything through cwm again to make sure it's gone

I managed to fix everything. I just was searching through the system folder of the 2.3.4 rom and to my surprise there was little old superuser. So I deleted the .apk and bin files. After that I restored the ROM. Fixed everything. The stress of sending in a phone with superuser is gone and I am back to being stocked

Two questions for you OP:
1. How do you have a warranty on a I9020A? Is it the subsidized version from Best Buy (i.e. "AT&T's sanctioned model")
2. Why do you need warranty repair? What broke?

Yes I got my phone from best buy. I just registered the imei with samsung and I am under the 1 year warranty. I have a problem with my battery draining 80% in 6 hours little to no use with all radios besides 2g turned off. I know that the NS has not so stellar battery life, but there is genuinely a problem with mine. It cannot even survive for half a day.

Hmm, I had that very issue with three past i9020a's (two from Amazon, one white one from Newegg). They were all the Rogers model, which is said to be identical to the one Best Buy is selling as a subsidized model.
I just bought another i9020a on eBay (no, I never learn) and hope to try some fancy methods to save on battery life (ROMs, etc). I also experienced VERY slow 3G with the i9020a on AT&T's 3G network here in the US. Like 300kbs download slow. I read that if you flash the radio to KB3 it gets very fast, like HSPA 3G should be.
I don't care about rooting and flashing because my phone will not have a warranty. I do, however, suspect that there is nothing wrong with your phone, rather the battery life is just random. One of the i9020a models I had drained a fresh charge in like 3 hrs of sitting idle w/full bars. The phone was burning hot. I restarted it, charged it up, and it lasted over 16 hrs the next time. Very erratic and strange, but that seems to be par for the course with the NS.

I would first see if the phones you bought were registered yet. You never know when you would need samsung to take care of something for you. The correct radio for the US ATT is UCKE1. You should be getting data speeds of about 3.3 megabits. My battery has been consistently low.

SleepyFox said:
The correct radio for the US ATT is UCKE1.
Click to expand...
Click to collapse
So that may explain what's different between the international (i.e. Canadian) I9020A and the "Best Buy" AT&T sanctioned I9020A...a different radio?
Is it possible to flash the KB1 radio of the Canadian I9020A to the AT&T friendly UCKE1 radio?

[Q] Installing OTA update / reinstalling stock recovery

Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.

hbforce
Thehurst said:
Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.
Click to expand...
Click to collapse
Right, go for it.
"IF I HELPED YOU HIT THANKS BUTTON"
.

You don't need to re-lock bootloader. Just remove superuser and restore stock recovery, then you are ready for OTA update.

So It worked but I encountered another issue, after the update was done my phone was unable to stay connected to the telus network.
it will connect to 4g with almost full bars for about 2 mins of which i can use data then it will disconnect me entirely, I can't search for the network or automatically configure it.
I took it to telus the sales guy played around with it reset the setting, nothing, then he Gave me a new sim (said it fixed his htc one which he did the same update last week) but it didn't work for me.
Does anyone know why this is happening or how i might fix it. They want me to sent my phone into for repairs but I don't want a loner phone for the 3 weeks it takes them to fix it.
I'm tempted to run the RUU again and sent my phone back to the stock 4.0.3 from 4.1.1 to see if it works and then try upgrading again.
Any advice?

maybe clear cache and possibly check the apn setting.

I tried that, and even factory recoveries with no luck so i returned it to Telus and hopefully it'll be repaired, It says re-locked and the tampered was removed so hopefully i don't get my warranty void'd if it is i'm sure i can down grade to the original os then load a custom rom and it should work

Just got my phone back from HTC
Despite having previously rooted my phone, they repaired it with no questions, and for free. Turns out my phone had a defective mainboard so once i updated the defect affected the phones ability to connect to the wireless network or something. But with the replaced board and with the new software update its working perfectly again.

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

Solution if you are stuck on 2G!!

i found the solution for those stuck on 2g speeds here in the US after flashing an RUU....your phone is probably on ICS 4.03 or 4.04 after you installed the official tmobile RUU...you have to keep checking for software updates on your phone until you get the official JB update installled from tmobile (it was officially posted at the end of April and available as a manual download through the "check software updates" option on your phone). i had to check for updates and install them about 5 times because the RUU i used restored my phone to ICS 4.03...i kept updating until i got to JB (it's going to be very large file, over 600mb).
IMPORTANT!!! --> after the update, your phone will still be stuck on 2g speeds....you them have to do a FACTORY RESET...yes, you have to wipe everything from your phone so make sure you backup to your laptop or something like that and then do a factory reset....once your phone reboots, it should now get 4g speeds (hspa+)...i read through alot of threads since my phone was stuck on 2g after i restored to the official tmobile RUU and finally got it to work after incrementally updating through the "check for software updates" option til the official JB update was installed.....good luck and hope this works for most of those that were stuck on 2g after the previous update!

I tried the above and it did not work. The following did, however, and I GOT 4G BACK on my HTC One S!!
I did not ever have S-OFF, I tried pretty much everything I could think of in terms of factory resets, flashing tons of different ROMs, bootloaders, even going completely stock again with RUU. I'm pretty sure it's a lost cause and a waste of time.
Solution: I relocked my bootloader and sent it in to HTC because I was still on warranty. They had it back to me in a week's time, and 4G now works fine. I'm going to try to find out what they did, whether it was hardware or not. Note: I did get it back with the bootloader being "locked", not "relocked".

skaters05 said:
I tried the above and it did not work. The following did, however, and I GOT 4G BACK on my HTC One S!!
I did not ever have S-OFF, I tried pretty much everything I could think of in terms of factory resets, flashing tons of different ROMs, bootloaders, even going completely stock again with RUU. I'm pretty sure it's a lost cause and a waste of time.
Solution: I relocked my bootloader and sent it in to HTC because I was still on warranty. They had it back to me in a week's time, and 4G now works fine. I'm going to try to find out what they did, whether it was hardware or not. Note: I did get it back with the bootloader being "locked", not "relocked".
Click to expand...
Click to collapse
Hi,
Did you find out what changed on your new HTC ONE S that fixed the Stuck on 2g issue?

skaters05 said:
I tried the above and it did not work. The following did, however, and I GOT 4G BACK on my HTC One S!!
I did not ever have S-OFF, I tried pretty much everything I could think of in terms of factory resets, flashing tons of different ROMs, bootloaders, even going completely stock again with RUU. I'm pretty sure it's a lost cause and a waste of time.
Solution: I relocked my bootloader and sent it in to HTC because I was still on warranty. They had it back to me in a week's time, and 4G now works fine. I'm going to try to find out what they did, whether it was hardware or not. Note: I did get it back with the bootloader being "locked", not "relocked".
Click to expand...
Click to collapse
4G? You mean 3G? HOS doesn't support 4G. Anyway, glad you fixed it! Considering the bootloader is locked again, I'm guessing they swapped a few parts?

I'm going to try this. I've been stuck on 2G ever since I updated my HBOOT to use 3.4 Kernel ROMs. I will get back to you to see if this method works for me.
how would you go about doing this method if you are coming from a custom ROM?
I'm on UnKnown v1.8 with S-Off on HBOOT 2.15 if that helps.

Yes, I suppose in the interest of accuracy I got H+ back, which shows as "4G" on the Sense UI. I'm really not sure what they did or how I would find out. According to the timeline they gave me it looks like they only had it in repairs for half a day or so, so it was either a simple hardware issue or some kind of deep software reset I wasn't able to access.

doesn't work. tried it the same exact way you said and it didn't work.still on 2G