My device was running Fire OS 5.0 and I installed my copy of Titanium Pro (used APK extractor on another Android device as play not working on 5.0).
I then proceeded to kill as many Amazon processes based on my Remove Bloat thread - I actually deleted them from the device so that they were no longer there. I kept the OTA processes in place - reset the device from [Recovery Mode] and upon boot joined WiFi and proceeded with the upgrade to 5.01
The update by the looks of things repaired the Fire OS and the system processes that I had deleted were now back on the device (Kindle Book Store etc). It also removed root from the device.
So just like everyone says - disabled OTA updates if you do not wish t remove root.
Were you able to reinstall root post update?
shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Would love to know also
Sent from my Amazon Fire 2015
i reinstalled the firmware to give it real factory reset, and applied OTA twice yesterday, but I could make it rooted after that. So I guess you can reinstall root again because the updated system did not reject root.
shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Yes I was able to root 5.01 after the OTA update
I would strongly advise everyone to disable the OTA processes. If you want to update a new device from 5.0 to 5.0.1 you can do so manually. Fire (5th Gen) updates are available here https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Who knows when amazon will roll out the next OTA, tomorrow, next week, next month. And they certainly might block root with it. The fire cost us only $50, amazon may be losing money on the straight device price. They want us to spending money on all the premium amazon services that we are striping out as bloat. They may need the money to even break even.
Huh... This actually gave me some insight into the OTA bit. I went and pulled the latest update and it basically overwrites the system partition. That's why it seems to undo everything you did. This is good though because it also means if it won't boot then I should be able to get into 3e recovery and sideload the most recent update back to the device. I tested this by flashing google play then "repairing" using the update and google play was no longer present from this. It also doesn't seem to wipe userdata when doing this which is nice.
Related
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
JadedRescue said:
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
Click to expand...
Click to collapse
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
slogar25 said:
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
Click to expand...
Click to collapse
I definitely did defrost those apps.
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
If you really want the ota then why don't you try mattlgroff's utility here:
http://forum.xda-developers.com/showthread.php?p=39576818
It will return you back to completely stock with one click and then you should be able to take the ota and reroot unlock if desired
Sent from my XT907 using Xparent BlueTapatalk 2
RSD
vLegend said:
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
Click to expand...
Click to collapse
I tried using Mattlgroff's method (which i'm sure is fine for most) but seems to be geared towards linux users mostly, and I ran into some issues. I have always used RSD to get back to stock and never had an issue. Check it out How To Restore Stock Firmware on Razr M. This will hard restore your phone to the factory image, as well as unroot it, no need to unfreeze or reinstall bloat. It will also obviously erase the internal SD card contents so make sure you back those up.
Yeah looks like slogar25 and cliMAKtic are right. I tried a few more things and its not working. I'll do an rsd in the next couple days and try the ota again.
I'm going to try rsd sometime tonight, I'll let everyone know how it goes. Thanks for all the help!!
I like rsd too. The point is to return too stock.
Sent from my XT907 using Xparent BlueTapatalk 2
Same issue, stops 1/4 of the way through.
Flashing back to stock with the RAZR M utility 1.10 once my phone hits 100% battery (at 93% now). Will let you know if I can take the update after.
Keep in mind
RSD is great to get back to clean stock, but keep in mind that it will remove your root. After taking the OTA update, you will be running firmware v4.1.2. If you used MotoFail2Go exploit to root your phone originally you should note that the exploit apparently does not work for the updated firmware. Instead you should use motochopper, an updated exploit that works on 4.1.2 to root your phone, developed by Drjbliss over at Droidrzr.
I honestly don't care too much about being unrooted at this point anyway, having root wasn't doing too much for me. I managed to get back to the original stock ICS using RSD and everything worked out! Downloaded one update to 4.1.1, then the second update to 4.1.2, and everything went swimmingly.
Thank you so much for all your help everyone!
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
System Updates Frozen
I have the System Updates App frozen in Ti BU. Haven't gotten any hint of an update and I hope it stays that way.
Same thing happened to me it tried installing the update all on its own luckily it said waiting for wifi network to update so I froze the system updates app with titanium back up.
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
RyanEJ25 said:
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
Click to expand...
Click to collapse
trailrunner76 said:
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
Click to expand...
Click to collapse
The main thing that threw me off was that USB charge modes have changed. Charge and internet connection are removed from PC connections other than that its general improvements to the keyboard and docs and stuff.
You can temp unroot, take the update, then reroot assuming Verizon didn't load a bullet that kills root.
Voodoo OTA Root Keeper
Sent from my VS985 4G using XDA Free mobile app
I'd tend to avoid the update, at least for now, if you want to keep root and twrp. Seems to be a number of people mentioning issues, including trouble reverting to 10b.
I also froze "System updates" with TiBU, going to stay on 10b until things clear up. Freezing that app seems to do the trick.
Why are you posting here, instead of the Verizon forum: http://forum.xda-developers.com/verizon-lg-g3/general
If you take the update, you can't re-root and you can't roll back.
Some people have maintained root after updating.
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.
Amazon has posted the 5.1.2.1 version on the website :
https://kindle-fire-updates.s3.amaz...Wt5/update-kindle-20.5.4.2_user_542169020.bin
Kingroot probably does not work ...
I'll take it for a spin, to make sure the update via TWRP works smoothly, and report back.
Exercise caution until we know if downgrading 5.1.2.1 to the earlier versions is safe or not. The 2015 Fire forums report that the downgrade works fine. But the 2014 Fire HDs is a different beast ...
The bad news, the great news
bibikalka said:
Amazon has posted the 5.1.2.1 version on the website :
https://kindle-fire-updates.s3.amaz...Wt5/update-kindle-20.5.4.2_user_542169020.bin
Kingroot probably does not work ...
I'll take it for a spin, to make sure the update via TWRP works smoothly, and report back.
Exercise caution until we know if downgrading 5.1.2.1 to the earlier versions is safe or not. The 2015 Fire forums report that the downgrade works fine. But the 2014 Fire HDs is a different beast ...
Click to expand...
Click to collapse
5.1.2.1 definitely can't be rooted with Kingroot. Tried multiple times, using all suggestions I've read, like clearing recents, clearing data/cache, standing on head (FWIW, there's a weird message: "Research requests is not enough (1 ppls)" Wonder if ppls is people and if more tried Kingroot on HD 7s (and 2015s) running OS 5.1.2.1 the KR folks might try to get us root. IDK, the msg may mean something else entirely.) Anyway . . .
OS 5.1.2.1 downgrades to 5.1.2 just fine!!! In stock recovery I factory reset, adb-sideloaded 5.1.2, and cleared cache. It booted into 5.1.2 purring like a kitten. Rooted with Kingroot no problem!
I have a nice little Windows tool that installs kingroot and as soon as user tells it tablet is rooted (hits Enter), it blocks OTA installation, looks for downloaded updates (and finds them!) and lists them for user to delete. Very handy. I've used it after several downgrades and haven't been caught with my OTAs down yet. Upgrades don't install until device is idle, so just have to hit enter as soon as rooted and you're safe. Will post it tomorrow. Needs testing on other (non-Win7) systems.
DoLooper said:
OS 5.1.2.1 downgrades to 5.1.2 just fine!!! In stock recovery I factory reset, adb-sideloaded 5.1.2, and cleared cache. It booted into 5.1.2 purring like a kitten. Rooted with Kingroot no problem!
I have a nice little Windows tool that installs kingroot and as soon as user tells it tablet is rooted (hits Enter), it blocks OTA installation, looks for downloaded updates (and finds them!) and lists them for user to delete. Very handy. I've used it after several downgrades and haven't been caught with my OTAs down yet. Upgrades don't install until device is idle, so just have to hit enter as soon as rooted and you're safe. Will post it tomorrow. Needs testing on other (non-Win7) systems.
Click to expand...
Click to collapse
OK, nice ! Thanks for testing!
Not sure why cannot you block OTA before Kingroot ? Why not do "pm disable com.amazon.otaverifier" right away with Network off , then turn Network on, and run Kingroot?
bibikalka said:
Not sure why cannot you block OTA before Kingroot ? Why not do "pm disable com.amazon.otaverifier" right away with Network off , then turn Network on, and run Kingroot?
Click to expand...
Click to collapse
Since 5.1.1 neither hide nor disable work without root. Disable won't run and hide returns new state=true, but hasn't done anything. Check output of Debloater.
EDIT: Disable=permission denial. Looks like hide doesn't return anything.
DoLooper said:
Since 5.1.1 neither hide nor disable work without root. Disable won't run and hide returns new state=true, but hasn't done anything. Check output of Debloater.
EDIT: Disable=permission denial. Looks like hide doesn't return anything.
Click to expand...
Click to collapse
This is weird. It's a major departure from the usual Android, where one can block programs via adb & PC.
Is it just OTA that cannot be blocked ? Or other stuff like lockscreen ads are also unblockable ? Was this discussed somewhere here ?
This seems to suggest then that going to 4.5.3 first is preferred, this way one can block OTA before Kingroot, and then upgrade to Lollipop via TWRP.
bibikalka said:
This is weird. It's a major departure from the usual Android, where one can block programs via adb & PC.
Is it just OTA that cannot be blocked ? Or other stuff like lockscreen ads are also unblockable ? Was this discussed somewhere here ?
This seems to suggest then that going to 4.5.3 first is preferred, this way one can block OTA before Kingroot, and then upgrade to Lollipop via TWRP.
Click to expand...
Click to collapse
Discussion was mainly in 2015 forums, where people started getting updated. It's true of everything we block, although there were some reports of ads staying gone until a reboot. Not sure about that since (FWIW) if you pm hide anything, Debloater shows it as unblocked. When I first saw posts I assumed it would apply to Fire HD and tested. Just assumed it was known.
OTAverifier could be blocked on 4.5.3, so downgrading to that makes sense and is safest. I'm confident in my tool, though, although there's a risk of a update if an inattentive user walks away and leaves the system idle. I've got warnings in the script and as long as one is trying to root (or otherwise keeping the system busy), a download won't install--and the moment devicesoftwareota is renamed it CAN'T install. I've done this more than 10 times and found that I usually don't get a download, even when it takes many tries with a couple of reboots to root. Still, I once found an update in /sdcard/Android/data/com.amazon.device.software.ota/files and once found the prelimary file in /cache. Although they couldn't install after the rename block, this is why I put in the file check.
Finally tested the upgrade via TWRP, everything worked fine :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
This new version reports itself as 5.1.2 (Mar 30, 2016 build). Not sure what was fixed other than the bug that lets Kingroot in !
Paging DoLooper here, thanks again for the early testing!!!
Hello, I recently got the September update for Moto X Pure and I want to know how to update my phone. I've read around and it seems that I need to restore to unrooted stock before I can flash the image as opposed to just flashing the image without doing anything else then re-install TWRP and reroot. Can anyone provide steps in how to do this?
Do you have systemless root?
Open SuperSU, settings, full unroot. if you have Xposed installed, you'll need to flash the xposed uninstaller through TWRP. Now to remove TWRP, you need to download the latest stock rom and flash only the recovery.img from your computer.
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Sean89us said:
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Click to expand...
Click to collapse
Is there a way to stop the constant notifications that I have a system update that needs to be applied?
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
eigerzoom said:
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
Click to expand...
Click to collapse
The OTA update in January, dated Sept 2016, is 40.2MB in size and build number 24.221.8.en.US.
Not sure what is chewing up 700mb of data, but it isn't the OTA... Do you have automatic update on in the Play Store? There were tons of large updates in January, I may be exaggerating but it seemed like 2-3 times a "normal" month.