Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Alan1727 said:
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Click to expand...
Click to collapse
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Devo7v said:
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Click to expand...
Click to collapse
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Alan1727 said:
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Click to expand...
Click to collapse
To explain a bit further, the way the update works is there's a program built into the OTA. This program checks the signature of all the system files on your phone against a database included in the OTA. If all the signatures match then the update will proceed, but if even 1 of the signatures doesn't match then the update will fail as you have experienced.
When you root your phone you are exploiting a weakness in some aspect of android that allows you to modify system files. Once you modify system files by rooting you change their signature. Even if you unroot, it is impossible to change the signatures back to what they originally were. This is the reason that even if you unroot the update will fail.
By resetting the device you are essentially deleting all the user apps and settings, the system files go virtually unchanged. So if you unroot, your signatures still don't match and when you factory reset the device the system files don't get touched so the signatures still won't match. The only thing you can do to get the signatures to match is to flash the NE3 full Odin package. This will completely wipe out our phone and install everything (the bootloaders, modems, system files, etc.) from scratch.
So like I said you have 2 options:
Follow the guide I linked to above; or
Flash the NE3 Odin package and take the OTA.
Either way you have to use Odin at some point.
Related
I have a quick question and I think I am right but want to make sure before I do it. I have a note 3n900a version NB4. I rooted it cant remember now what i used, was thinking kies but that could be wrong. I know at the time I checked and I had not tripped the knox count. I froze auto update and left phone alone. At the time i was thinking I would just have to unfreeze auto update and it would update and relock phone when it came time to turn back in. That is my only question, can i still do that and not have any issues? Its about time to return it for upgrade and I do not want to wait till last min to do it and have a dead phone and all. Thanks a bunch
You have 2 options. You can uninstall root, and hope it updates, then factory reset and return.
Or you can just use Odin to flash the latest firmware, factory reset and return.
To do the first painful option unfreeze everything you froze. Restore any deleted system apps. Open superuser and choose "full un-root". Open settings and navigate to software update. Now pray it updates because it failed at 20% for the majority of users here. If it updated, factory reset and return.
If your update fails you need to use Odin and flash the latest firmware. Then you'll be completely stock and up to date. For instructions and firmware files read this thread.
http://forum.xda-developers.com/showthread.php?t=2703006
thanks a bunch, yea i guess i could use odin i still have all the files. thanks too for the link.
Another question along the same lines. So if i just do a factory reset would that mess up my root in any way? or can i do a factory reset and reinstall super su and be good to go again? thanks a bunch.
Forgive me here. I have a VZW dev edition.
Currently running 4.4.4 stock rom. I had it rooted before and I think I recently lost root. Forgot why but I didn't really need it.
EDIT: I remember now. I did a factory reset. Did I lose root?
anyways the OTA that came a few weeks ago the small one will not install. I have enabled my apps again that I had disabled. I do not remember if I did a tether hack before which was just replacing a file. Bootloader is unlocked still.
So after the OTA downloads and reboots the android shows up the bar starts to move and then red exclamation mark.
Update unsuccessful.
What do I need to do? I also do not want to wipe data.
The OTA alert is annoying me to no end.
It sounds like the pre-flash validation checks are failing for some reason.
A few things don't add up in your post...
You have a Dev Edition, so to root you unlock the bootloader, flash TWRP, boot into it, and when it prompts you too, allow it to root (or if you don't get rooted, install SuperSU while booted to TWRP). IN that state, a Factory reset doesn't remove root. So did you root by some other method? If so, that is why the OTA is failing.
Next.. you say you did a tether hack that was just replacing a file. Did you put the ORIGINAL file back? If no, that will cause the OTA to fail.
The only way to really know exactly why is to NOT install the OTA, instead just download it. Move the OTA zip from /cache to your /SDCard (which takes root) after it finished downloading. Again Do NOT install it the "normal way". Make sure you have a working STOCK Recovery on your phone. Manually boot to stock recovery and apply the update zip via the menu options. When it errors, it will pause and tell you why, what caused the issue. You need to correct it and try again.
One final option... See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 you can take some time and read the first post... then skip to Post #2, and use the Requirements section, and Option 2.
I have an unlocked Nexus 6 64gb from Ebay that I activated on Verizon. I rooted it, installed 5.1 and did the build.prop and settings.db changes and have tethering, etc (unlimited).
A few questions:
Will the OTA update show up on my phone since it is rooted and/or since it was not purchased from Verizon?
If it does show up and I let it update to 5.1.1, will I need to do the build.prop and settings.db changes again?
If it does not show up and I install from Google's image, do I need to do the build.prop and settings.db changes again?
I am sure these are basic questions... sorry... this was my first phone root and will be my first update to apply since doing that.
an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.
simms22 said:
an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.
Click to expand...
Click to collapse
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?
hifiaudio2 said:
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?
Click to expand...
Click to collapse
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).
simms22 said:
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).
Click to expand...
Click to collapse
Thanks again for the help. So my wife has the exact phone and same root with hotspot enabled as I do. I forgot to tell her to ignore the update, so when the OTA verizon update showed up this morning, she installed it. Her phone still says 5.1, so I assume it just tried to install but didnt work, but the Hotspot icon was removed (I just went into settings and selected it again, and it seemed to work still), but I dont know what error it might have given when she tried to install or what settings or files that I had changed, like build.prop, etc, might be changed back. Is it likely that the system trying to install the OTA update would have changed my modified settings?
Going forward, I plan to fire up Wug's rootkit and just flash the 5.1.1 image with no wipe. SO everything I did on both phones should already be ready to go when the flash finishes, right? No settings for me to change all over again?
Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.
prdog1 said:
Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.
Click to expand...
Click to collapse
Cool, all done, thanks.
I recently rooted my device, and want to install a system update. I unrooted my phone using superSU, and tried installing the update. It downloads, then restarts the phone. After 10 seconds, the phone restarts and it tells me that the download was unsucessful. I rooted my phone using mobileGO. I am thinking about doing a factory reset - will that remove any files preventing the update. I really want this update, and any help would be appreciated.
:fingers-crossed: Thanks.
I have never user Mobile Go. I don't know how it works but I think it disables OTA.
You can always flash the complete stock ROM (There is a tool in the dev's section) but you will loose everything.
A factory reset will not help because it will not delete any file in the root directory. OTA updates verifies all files while flashing.
Try redownloading the update first.
Then if you don't mind loosing everything, flash the complete stock ROM.
There may be an easier solution, but I don't know it...
Hope it helps
Mavireck said:
I have never user Mobile Go. I don't know how it works but I think it disables OTA.
You can always flash the complete stock ROM (There is a tool in the dev's section) but you will loose everything.
A factory reset will not help because it will not delete any file in the root directory. OTA updates verifies all files while flashing.
Try redownloading the update first.
Then if you don't mind loosing everything, flash the complete stock ROM.
There may be an easier solution, but I don't know it...
Hope it helps
Click to expand...
Click to collapse
Thanks for the reply; I tried redownloading the update with no success. Would you still need root access to flash the stock ROM?
No
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.