Database Info

[Q] Will the 6/2 OTA update cause rooting problems?

Hi all,
I received my Thunderbolt today from Wirefly and one of the things it's offering me is an OTA update dated today.
Has anyone experienced any rooting issues with this update? So far, my phone is stock, and it would be easy for me to apply the update. But, if it's going to be an issue with rooting it then I'd rather hold off.
Thoughts?
Robert

Its probably the MR1 update the phone got a little bit ago. When they send phones out, they come with the factory firmware (meaning not updated). If you root your phone, then return to stock, your phone won't be on the latest firmware anymore.
What I'm trying to say is it's probably not a new update.

The info on the update is:
Mecha_VERIZON_WWE_1.13.605.7-1.12.605.6
Does that help figuring out which one it is? If it is the MR1 is it OK to update without causing issues for rooting?

Robertjm said:
The info on the update is:
Mecha_VERIZON_WWE_1.13.605.7-1.12.605.6
Does that help figuring out which one it is? If it is the MR1 is it OK to update without causing issues for rooting?
Click to expand...
Click to collapse
Go to the root tutorial sticky in the development section and compare them. If it is the Mr1 then rooting will not be a problem.
Sent from my HTC Thunderbolt

Im pretty sure its fine... we have that update already anyways so if you just have them ship you the phone when you root it you'll end up with the update. Rooting on this phone requires a downgrade first so I would just have them ship you the phone then you can update when you root.
Sent from Gingertits, I mean itis...

So I went and checked that does appear to be the OTA update number. I already have the phone. Sounds like it really doesn't matter whether I update now and then root, or vice versa.

I wouldn't update it if your planning root, its the update that has been causing reboots, so I would just not update, root your phone and do whatever mine was never updated and it works great.
Sent from my ADR6400L using Tapatalk

I just got my Thunderbolt today, I got the same message about an update, I went ahead with it, thought it was GB Anywho, just finished jcase's PermRoot all is good, so you should have no problems.

So I chose "reject" the last time I was offered the OTA. Does that mean it's going to embargo that update going forward?
Robert
oxidant11 said:
I wouldn't update it if your planning root, its the update that has been causing reboots, so I would just not update, root your phone and do whatever mine was never updated and it works great.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse

Robertjm said:
So I chose "reject" the last time I was offered the OTA. Does that mean it's going to embargo that update going forward?
Robert
Click to expand...
Click to collapse
If you decide you changed your mind, you can always go to Settings ->Software Update -> Check new, and it will prompt you again.
Like somebody else said, though, if you are planning on rooting, there is no need to do the OTA beforehand. You will end up with a rooted version of the OTA update at the end of the rooting process, anyway (assuming you follow jcase's instructions...which you should).

If you accept the update is there a way to remove it?

captinmahem said:
If you accept the update is there a way to remove it?
Click to expand...
Click to collapse
Only by rooting and flashing a new ROM.
Thanks, Robertus

Rogers System Update - (1.94.631.3)

I've been checking for updates on my one x almost everyday for a month now, and an update just went out.
It's a system update (1.94.631.3) 67Mb.
Still not sure what its updating.

Try it and let us know!
Sent from my HTC One XL using xda app-developers app

I'm currently on version 1.73.631.1.
I can download the update and run the installer.
It gets halfway through the update then shows a phone with an error icon on it.
phone resets and im still on the old version.

Berserk87 said:
I'm currently on version 1.73.631.1.
I can download the update and run the installer.
It gets halfway through the update then shows a phone with an error icon on it.
phone resets and im still on the old version.
Click to expand...
Click to collapse
Are you unlocked/rooted? Or pure stock?

I think I'm going to wait a bit before installing this update...
for the record I'm on 1.73 still... not sure what's in this update

That's odd.. from other X & XL 4.0.4 releases they have used a 2.x.x.x release code and I'm surprised they would release another 4.0.3 version with 4.0.4 out.

I called HTC.
They couldnt tell me how to fix the error or what the update includes.
I was told to factory reset and try it again, which I did. The update still failed and I have to resetup my phone now...

Custom Recovery Screen
I downloaded the update successfully on my rooted One X (with stock ROM). When I hit install, it restarts the phone and goes into the custom recovery screen... I don't really know what to do from there though... anyone got any ideas?

Berserk87 said:
I called HTC.
They couldnt tell me how to fix the error or what the update includes.
I was told to factory reset and try it again, which I did. The update still failed and I have to resetup my phone now...
Click to expand...
Click to collapse
Need to relock bootloader, restore recovery and return OS to stock.
Basically relock bootloader and flash original RUU.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
ComposMentis said:
That's odd.. from other X & XL 4.0.4 releases they have used a 2.x.x.x release code and I'm surprised they would release another 4.0.3 version with 4.0.4 out.
Click to expand...
Click to collapse
Only Singapore has gotten 2.x aka 4.0.4.
All other regions were recently updated to things like 1.88(previous Singtel), 1.89(Telstra), 1.91(Telus), 1.92(o2 Germany) and now 1.94(Rogers). There is probably a 1.90 and 1.93 somewhere. Eg maybe 1.93 is the soon to be released AT&T and maybe Vodafone Germany is at 1.90?

Only thing I can think that might mess it up, is that my phone was rooted, but i've done a factory reset already.
So the only other thing I can think of is that the update fails because my phone shows "tampered" from rooting.

You need to install a ruu(the correct rogers one). That will remove tampered warning.

I just downloaded the update. It's def worth doing it. My phone was rooted as well but had no issues with update. Multitasking issue for me seems to be fixed, well a million times better than it was anyways (Seems i spoke too soon on the multitasking, its a bit better, but after a couple apps its back to normal) no more reloading every time you go back to something. Also I used to find it slow going into text messages etc, and the contact list was slow to update especially when scrolling through, totally eliminated now. So much faster and less bogged down feeling.

lurker82 said:
I just downloaded the update. It's def worth doing it. My phone was rooted as well but had no issues with update. Multitasking issue for me seems to be fixed, well a million times better than it was anyways (Seems i spoke too soon on the multitasking, its a bit better, but after a couple apps its back to normal) no more reloading every time you go back to something. Also I used to find it slow going into text messages etc, and the contact list was slow to update especially when scrolling through, totally eliminated now. So much faster and less bogged down feeling.
Click to expand...
Click to collapse
Any tricks to the update?
did you download over wifi?
plugged in during update?
use htc sync?

twistedddx said:
You need to install a ruu(the correct rogers one). That will remove tampered warning.
Click to expand...
Click to collapse
I don't think that removes the tampered flag.
Sent from mobile

Installing a RUU does remove the tampered flag. so run the stock ruu, flash the update then unlock the bootloader again then push the custom recovery. flash a root for cmw then you will be rooted again. If you want a custom rom from it, then do a system dump after the upgrade.

OTA Link
Here's the link for the OTA download for anyone who wants to go through it: http://fotadl.htc.com/OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
It contains hboot 8960_1.11.0000_20120607 and an updated radio, the version of which I'm not sure of.

Oh. Didn't actually try an ruu myself.
Sent from mobile

TelusHTCHero said:
Here's the link for the OTA download for anyone who wants to go through it: http://fotadl.htc.com/OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
It contains hboot 8960_1.11.0000_20120607 and an updated radio, the version of which I'm not sure of.
Click to expand...
Click to collapse
Where did you get that and how do I flash it?
I would also like to keep root if possible.

I assume people catch the link while the phone tries to download it.
You can't manually flash a fota. You need to apply all the patch files against the original firmware intended to be updated.
It's a long tedious process, only a smart dev will be able to pull it off.
It was done to get 4.0.4 but is it worth the effort for this? This is likely equal to all the other regions recent 4.0.3 updates.

Why are you guys so eager to flash this? I'm sure there are better custom roms. This will update your hboot so beware. If s-off is achieved you'll be **** out of luck.
Sent from my HTC One XL using xda app-developers app

Trouble downloading new update

Hey guys I'm having trouble downloading the update (I know, shocking... who would want the update my issue is is that I first tried to download the update when my battery was below 35%. It said that there was an update available but I had to wait until I battery was above 35%. now that it is above 35%, when I click on the check for updates button, literally nothing happens. no dialogue no confirmation... nothing. I've already rebooted the phone and tried to clear the cache for the updater app. any suggestions? I know for Motorola phones there is a way to install the updates manually... anything like that for HTC? I'm not rooted or unlocked.
Sent from my HTC One X

Set your date ahead 2 days and try again.

Why do you want the update. Honestly there's no reason to want it. YAY you lose root and probably can't get it again and furthermore you can get all the features the update gives in a rom.
Sent from my magical box

atticusmas said:
YAY you lose root and probably can't get it again
Click to expand...
Click to collapse
Actually, as long as you were rooted and unlocked before, you're fine.
http://forum.xda-developers.com/showthread.php?t=1812039

So I set the date forward 2 days, it discusses the update, then I got a dialog with a spinning circle saying "verifying update" with an "ok" button. I clicked the button and the dialog disappeared. Now I can't get it to reappear or download the update again. I keep setting the date forward two days and it says there's an update available but it never downloads.
Sent from my HTC One X

atticusmas said:
Why do you want the update. Honestly there's no reason to want it. YAY you lose root and probably can't get it again and furthermore you can get all the features the update gives in a rom.
Sent from my magical box
Click to expand...
Click to collapse
So they can make threads asking how to root because they "made a mistake" and upgraded.
Sent from my HTC One XL using xda app-developers app

I wouldn't recommend updating yet. I was having a hell of a time getting TWRP to work properly to the point of destroying my sdcard forcing me to RUU back to stock. Until a Recovery fix or Root for 2.20 is found I wouldn't update.

SkizzMcNizz said:
So they can make threads asking how to root because they "made a mistake" and upgraded.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
LMFAO aHAHAHA....:highfive:

Help. I still don't see an update after manually checking for one. Does anyone know why ? (I even changed the date back)
Sent from my HTC One X using xda app-developers app

They do these things called staggered roll outs.

mosesman86 said:
Hey guys I'm having trouble downloading the update (I know, shocking... who would want the update my issue is is that I first tried to download the update when my battery was below 35%. It said that there was an update available but I had to wait until I battery was above 35%. now that it is above 35%, when I click on the check for updates button, literally nothing happens. no dialogue no confirmation... nothing. I've already rebooted the phone and tried to clear the cache for the updater app. any suggestions? I know for Motorola phones there is a way to install the updates manually... anything like that for HTC? I'm not rooted or unlocked.
Sent from my HTC One X
Click to expand...
Click to collapse
i guess hard reset will do the trick for you. here is a procedure of performing a hard reset on HTC One X
http://howmobile.net/htc/2152-how-hard-reset-htc-one-x.html

[Q] Update to 2.2

Hello,
I have HTC one X (not rooted) on ATT with version 1.85. I got an update notification in the past but I ignored it. Now I am trying to check for update it is doing nothing.
When I click on check for update nothing happens. I tried changing dates, restarting phone etc.
Can anyone help me with this?
Regards,
Alex

Maybe one of the other guys can back me up on this if I'm right, or tell me I'm a dummy? 2.2 update only locks up your phone. If you intention is to root later? I'd leave it be. And I would imagine that att is no longer interested in sending that ota because we now have a exploit for 2.2. Your next update offered will more likely have more securely locked bootloader. No fun for anyone looking to customize their HOX
Sent from my One X using xda premium

subarudroid said:
Maybe one of the other guys can back me up on this if I'm right, or tell me I'm a dummy? 2.2 update only locks up your phone. If you intention is to root later?
Click to expand...
Click to collapse
2.20 update includes an updated 1.14 hboot, which plugs the holes by which kernels and radios can be flashed in recovery. Downgrading the hboot is only possible currently using a Linux computer. If the OP has any desire in the future to root, and flash custom ROMs, my advice is that he should root and unlock the bootloader now. Not sure, but I think some people have had forced OTA updates to 2.20.

[Q] Jelly Bean OTA Update Failed?

My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)

Flameninja00 said:
My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Click to expand...
Click to collapse
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you

flying_dutchman said:
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
Click to expand...
Click to collapse
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X

Flameninja00 said:
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Click to expand...
Click to collapse
I'm having the same exact software. I uninstalled and froze a few bloatwear. Used MotoFail2Go to get my root. So what do we do now??? are you tell me we're stranded unless we beef up another 300.00 for a new device?????? Nahhh all these nerds on XDA someone's gotta have an answer....................right?

I'm glad I'm not the only one having issues, but I agree. Someone's gotta have an idea on what to do, or try next.
Sent from my DROID RAZR HD using xda app-developers app

Well I gave up. Luckily I got Verizon to send me another device
Sent from my DROID RAZR HD using xda app-developers app

same thing happened to me..and yes they gave me another device too...

Ncruze said:
Well I gave up. Luckily I got Verizon to send me another device
Click to expand...
Click to collapse
johnxpotter said:
same thing happened to me..and yes they gave me another device too...
Click to expand...
Click to collapse
I'm assuming you both were rooted via MotoFail2Go? What did you do before you sent it in to hide your root? Just unrooted and restore to factory?
Thanks everybody for your help!!!
Sent from my DROID RAZR HD using xda app-developers app

Cool did your new device come pre installed with job? If not did you have any problems upgrading to job on ur replacement device?
Sent from my DROID RAZR HD using xda app-developers app

Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.

djousma said:
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
Click to expand...
Click to collapse
The bloatware came back and works fine after a factory reset though.
Are you telling me I'm screwed then?
Sent from my DROID RAZR HD using xda app-developers app

No, you are not screwed. You may have to reload original ICS from FBR process. It is documented on this site. I had to do that not because the OTA failed, but because I lost root.

"UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail."
I have the Dev Edition with an unlocked Bootloader.. is this why my update is failing?
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean.
When I try to load the update my self through recovery, same thing happens, but the error shows....
assert failed:motorola.update_bl_backup()
Any one...Any one...Bueller.

rebretz000 said:
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean
Click to expand...
Click to collapse
Mine fails 1/3 of the way up the bar, but the animation is the same.
Sent from my DROID RAZR HD using xda app-developers app

Hi I am using galaxy S2 i1900g. yesterday i downloaded the jellybean update for my device OTA. when installing it said device will reboot .
After the droid loading symbol it rebooted and now its stuck where the device name "Samsung GALAXY SII" comes and its stuck here for the past 2 and a half hours .
what should i do..... should i reset the device in the middle of installation but that will curru[pt the device right?? Has the installation failed.???? please help