Hey all.
I've tried to perform the recent OTA update that came out last month, but have been unsuccessful. I had at one point uninstalled much of the bloatware that came with my Bionic, but I believe I've reinstalled them. I unfreeze everything on my phone, I have used both the Voodoo temp unroot and the Superuser temp unroot and OTA survival, but no dice. i'm not sure where to go from here. maybe unroot completely with Pete's root tools, but I would like that to be a last resort if possible.
Only way the OTA will take is if all stock bloatware is there and no apps are frozen. If you did not make a stock nano back up before making all those changes then you will need to rsd the phone back to stock. I have my wife's phone rooted and debloated flashed it to .902 and took the OTA .905 with no issues.
What is the exact error you are getting and how are you applying the OTA? Usually if you apply the OTA manually it'll give you an error specific to why it won't install. As stated above you need to make sure you're fully stock or the OTA will fail. It does check for root. Mine failed too even with Voodoo unroot. It would keep detecting that the file was incorrect. I had to manually go into file manager and modify the root file which fixed my problem with OTA not installing. You may need to go and do a FXZ to get back to full stock.
Related
I was on stock, rooted 5.9.902 and was just prompted to Download and Install 5.9.905 OTA. I backed up root with Voodoo OTA Root Keeper, temp unrooted, downloaded and installed 5.9.905, let the phone reboot, then restored root using Voodoo OTA Root Keeper. All went smooth and am now on the official OTA with root. I noticed the addition of Google+ as a preinstalled app. I am assuming, however, that there is no difference between the 5.9.905 that was pulled from Motorola's servers a few weeks back.
Thanks I was wondering what I should do about the root. Went back to unsafe mode, unrooted with backup thanks to rootkeeper, and now I'm waiting for the update! Cheers.
You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.
that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.
I will wait for the OTA notice. if I have to reroot and reeinstall Safestrap I will.
cellzealot said:
You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.
Click to expand...
Click to collapse
OHbenhamean said:
that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.
Click to expand...
Click to collapse
You don't have to remove Safestrap, or un-root as long as you haven't removed any bloatware apps. They can be frozen in TB and it will install. You will lose root, I used Motofail to re-root, then you will have to rerun the install for safestrap recovery. 15 minutes and your good to go.
Agreed. I just removed safe strap, didn't bother to unroot. Tried to force the update repeatedly with no luck. So i took it from the Phandroid news link. Flashed in stock recovery. Kept root (used for3ver root to root I months and months ago). Reinstalled safe strap, then switched back to my safe side which was DroidTheory's ICS, but now with a better radio now. Radio synced immediately...whereas normally it takes a minute or two. Loving this update.
--Sent from GlaDos baked potato
hey just fyi if you flashed it back to 902 stock and took the update you can use the 902 one click root to reroot, i just tried it
Still rooted
I just let the 5.9.905 ota run this morning on my rooted Bionic. No unroot, no backup, or nuthin. I know, not the wisest thing to do but hey, I was caffeine deficient and spoiling for a fight Anyway after the reboot:
Root check shows it's still rooted.
Opened a shell on the handset with Terminal Explorer and successfully su.
Opened an adb shell and successfully su.
I haven't had a chance to explore what's changed yet, but I did notice that Google+ is no longer un-installable.
I might be the exception, but it appears that the ota doesn't affect root on a previously rooted handset. All seems good in my little piece of the world.
Every time I try to update, it says I need a valid Motorola account. I'm on stock, but have done many customizations to it, along with the webtop. I know how to get back to plain stock, just haven't felt like doing it yet. I suppose at some point I will have to when we finally get ICS.
the funny part is that I never had any issues with my data connection until 905 came around, but I have been having them for the past 2 weeks or so.
Sent from my DROID BIONIC using XDA
Non-rooted Bionic constantly trying to download 5.9.905
The past few days my Bionic has been constantly trying to download an update. I came online to investigate the reason and found that 5.9.905 just got released. The download symbol has been in the notification bar all day for the last few days and the battery is always dead when I wake up.
I have looked online to try to update manually but all the filenames of the 5.9.905 download links are actually labeled Blur_Version.5.9.902.XT875.Verizon.en.US.zip. Link this one here at xda: http://forum.xda-developers.com/showthread.php?t=1297714&page=40. Anyone have any suggestions? Thanks.
The filename is in regards to the version over which it can install.
You just have to download one from may or later, I believe. Pick a page that says it's the 905 update, download the zip file with 902 in the name, put it on your external sd card, and reboot into stock recovery (I use adb reboot recovery), press both volume buttons in, then "install zip from sdcard" use power button to select. go down to the zip file we just put on the sdcard, hit the power button and BING BANG BOOM 905!
Re: Non-rooted Bionic constantly trying to download 5.9.905
Thanks, 5thAgent. I'll give it a try.
I think I might have painted myself into a corner on this one. I got my phone rooted on ICS & have been loving it. I used TitaniumBackup+ to do a full system backup and then proceeded to nuke the bulk of Verizons apps. All was well. Now, the Jellybean update is out. The OTA update hasn't hit my phone yet. So I went and downloaded the official build. It turns out the upgrade won't run without the missing Verizon apps. So I went to my backup folder & lo and behold: they didn't get backed up.
My fear is that the OTA update just hasn't made it to me yet & will also fail because those applications are missing. Right now, it's stuck on BackupAssistantClient.
Someone suggested I go and get gapps, but that won't install either.
Does anyone know where I can find copies of those apps or am I just SOL? It's not TOTALLY awful. It just means I have to wait until November for my contract to be up.
Thank you in advance!
Google "House of Bionic" read all insructions, download program, and use it to FXZ back to stock ICS with all the apps then you'll be good to go.
It should be nice and simple in your situation.
1. Use RSDLite plus the 6.7.246 FXZ file to put the phone all the way to stock.
2. Get root on ICS and then install OTA Rootkeeper. Make sure that the only things you do are root and install OTA rootkeeper.
3. Use Stock Recovery to apply the JB update. Check for root, which should hopefully have stayed.
All should be well after that. I've done some reading but I'm not 100% sure if it's safe to downgrade flash back to ICS after you take the JB OTA.
The House Of Bionic works perfectly! I did lose root though. I used the Voodoo app to back it up, but for some reason it just didn't protect it. I'm ok with it for now as I was more interested in JB than having root. All I really used root for was to get rid of the bloatware in the first place.
Wait!
Steve.Cena said:
The House Of Bionic works perfectly! I did lose root though. I used the Voodoo app to back it up, but for some reason it just didn't protect it. I'm ok with it for now as I was more interested in JB than having root. All I really used root for was to get rid of the bloatware in the first place.
Click to expand...
Click to collapse
STOP!
Use HoB to root as well. In the main menu, it is under utilities. THEN update the superuser binaries and use Voodoo to save root.
Then you should be able to run the update from the stock recovery and restore root when you reboot.
No need to keep the annoying bloatware! Or once updated you can add Safestrap and try out some of the cool JB ROMs.
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
I was rooted and just installed the update. Went through fine and kept root. All my had to do was install/update xposed framework and reboot to get my modules working again. Aside from xposed I had no modified system files and stock recovery. I had not uninstalled any pre-installed apps, just have a few frozen with titanium.
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
If you find a solution would you kind enough to share? Ive been delaying my install and when i finally decided to do it, it errors.
wujuyamakin said:
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
Click to expand...
Click to collapse
Other than root, are you stock? If so, should be able to take ota with non issue. If you modded wifi hotspot, need to change it back for ota. Did you also install custom recovery?
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
I didn't have any errors but I have no system files modded.
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
wujuyamakin said:
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
Click to expand...
Click to collapse
I tired this with no success. So i didnt delete my stock wifi hotspots (apk and odex) just renamed them. I removed my modded one and switched back to original names, rebooted, downloaded ota and it errored when it tried to install. Am i missing a step? Thanks in advance
lg g2 Verizon ota update with twrp
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
TheJuicer said:
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
Click to expand...
Click to collapse
You should never attempt OTA unless you are stock (having only root will be ok).
Yeah i had forgotten i had performed those mods after i rooted. Initially i thought i was just stock and rooted. Thankfully pretty easy to go back to stock.
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
fleggett1 said:
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
Click to expand...
Click to collapse
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
dirtydodge said:
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
Click to expand...
Click to collapse
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
fleggett1 said:
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3149146
If you want root, go to the OP in that post, scroll down to step 4 or the notes section and download the "downgrade to nce.zip" flash that in odin "ap" slot. Then root with towel root. After that you can either download titanium backup and fees the ota's or use that same thread to upgrade to the OF2 version and keep root.
Edit:
If you want to just take the OTA's and not root your phone then still download the "downgrade to nce.zip" flash in odin but don't root. The ota's will push through with no problem then. But you won't be able to downgrade and root if you take the OTA's all the way up to oc4 i believe.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.