Back-story: Started on ICS (4.0.4), rooted, did OTA to Jelly Bean (JB) and lost root.
Followed the full video here: How to Root the Droid Razr HD on Jelly Bean and went back to ICS, got root.
Now, when I try to OTA to JB, after the reboot, I see an Android lying on it's back with a red exclamation mark. When the phone finishes booting and I'm back home, I see a message that says "Software update failed" (or something close to that).
What further stinks is that as I try to make tweaks w/ Superuser, Voodoo OTA RootKeeper, etc., I have to download the full update every time!
Any idea on what might be happening and how to trace down a fix?
Update w/ Fix: I fixed my problem (luck) and thought I'd come back to update for anyone that might be encountering the same.
When following the video mentioned above, i used Matt Groff's 1.10 utility found here. In this version of the utility, there's the following option:
4 Install Safestrap 3.05.17 App by Hashcode
Click to expand...
Click to collapse
I think I made the mistake of installing this before the upgrade back to JB. For the fix, I did the following. Re-activated root using RootKeeper, went into Safestrap, did "Uninstall Recover" (since I'd installed one earlier) and then deleted the Safestrap app.
The only other things I did:
- Turned off USB debugging
- Made sure my USB cable wasn't connected
Regarding these last two, I don't know if they made any difference, but that was the state when I tried the OTA update again when it succeeded.
I am having the same problem with the JB OTA.
I am going to try uninstalling safestrap
Thanks!!
droidcutie said:
I am having the same problem with the JB OTA.
I am going to try uninstalling safestrap
Thanks!!
Click to expand...
Click to collapse
Did that work for you?
aagha said:
Did that work for you?
Click to expand...
Click to collapse
Not the person you were asking, but it did NOT work for me after uninstalling safestrap. Going to have to RSD Lite back again
Related
I searched the forum but couldn't find an answer. I have tried several times to update my TF to 3.2.1 but the update keeps failing.
I get a system update notification. The tablet shuts down. The little green android with the gears on his stomach appears with a progress bar under it. The progress bar gets about 1/3 of the way then an exclamation mark appears in a yellow triangle. The a few minutes later the tablet restarts and it says that the update failed.
I am currently on build number HTJ85B.WW_epad-8.6.5.9-20110816. My TF is unrooted.
Is this happening to anyone else? Anyone have any suggestions besides doing a factory reset then trying the update again? Thanks in advance for any help.
Was it rooted before?
Rooting itself doesn't break updates it's what you do whilst rooted that can, so unrooting isn't necessary. I'm having this issue again as I removed some Asus apps with Titanium Backup which I now can't get back (I did them when there was a bug in TB which didn't backup apps properly). The OTA update script checks the integrity of a bunch of apps and files, which if it fails will abort the update in the way you are seeing. Very annoying.
---
Sent from my Asus Transformer using Tapatalk
Yeah it was rooted. I just realized that immediately after I rooted it, I had made a CWM backup. I'm going to try to restore the backup and see if the update goes through. (fingers crossed)
Sounds like you're running a custom ROM
baseballfanz said:
Sounds like you're running a custom ROM
Click to expand...
Click to collapse
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
yeah, I think that your kernel will cause the update to fail since it updates some of the kernel modules.
tmcquake said:
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
Click to expand...
Click to collapse
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Got the problem, too!
Now I use Revolver!
I flashed revolver, too. Works like a charm.
ppzoid said:
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Click to expand...
Click to collapse
I got it from here: http://forum.xda-developers.com/showthread.php?t=1281161
It's only a 3.2 to 3.2.1 update though, it's not a full ROM, so you have to already have 3.2 on your TF. Hope this helps!
i have the same problem too.
my TF101 was totally non rooted .
is there a download for this 3.2.1 update? so i can prehaps update my TF mannually ....
I didn't find one, because of that i flashed revolver.
ppzoid said:
I didn't find one, because of that i flashed revolver.
Click to expand...
Click to collapse
i wish too....the thing is ....my TF cant even load into recovery....
it is a B40...TW 8.6.5.9
is this normal ??
coz I saw people can do it with B40 with 3.2.1....
http://forum.xda-developers.com/showthread.php?t=1280796
I too have a problem with the update on my rotted tf.I got an unofficial update apk here but I still get an error message when trying to flash in CWM.I heard that this could be due to a modified system file,but I don`t remember having done such a thing thought...
Good luck.
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app
This morning, I got a message on my Motorola Droid Razr Maxx HD (2 days old) that Verizon had pushed an update (0.7.2.en.US) and wanted my permission to install it. What is this? Jelly Bean? What version?
The phone came with ICS 4.0.4 and I immediately rooted it and installed Voodoo OTA RootKeeper, so there's that. Will I lose root if I let this update install? I installed JB on my tablet and it broke many of my utilities so I backed it out. Also, JB is hard to root without unlocking the bootloader, which I don't want to do.
permutations said:
This morning, I got a message on my Motorola Droid Razr Maxx HD (2 days old) that Verizon had pushed an update (0.7.2.en.US) and wanted my permission to install it. What is this? Jelly Bean? What version?
The phone came with ICS 4.0.4 and I immediately rooted it and installed Voodoo OTA RootKeeper, so there's that. Will I lose root if I let this update install? I installed JB on my tablet and it broke many of my utilities so I backed it out. Also, JB is hard to root without unlocking the bootloader, which I don't want to do.
Click to expand...
Click to collapse
Its not jelly bean. Its just a security update. You will lose root when you upgrade. ( I believe?)
I just read on another forum that it fixes some Smart Action bugs. I've encountered those, so I'll let it install. Someone else said he was rooted and it wouldn't install, so... I guess I'll see. It's trying to install now.
Well, that was a mistake. It did not fix my Smart Actions problem. As far as I can tell, all it did was take away my root access. Voodoo OTA RootKeeper is not able to get it back
No harm done - I just rooted again, the way I did the first time.
I've had this update since Monday. Not bragging but it's interesting how the updates rollout to different regions.
Sent from my DROID RAZR HD using xda premium
I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4
What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app
I added the info to the original post
bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.
If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.
Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium
Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it
O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now
bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.
Are you looking for jb sense?
omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?
I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app
SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!
mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!