I've got a rooted Nexus 9 (WiFi) with TWRP installed. A few days ago I got a notification to install an update. I was surprised, as I didn't think OTA updates would come through once TWRP/root was set up. I tried installing it, but it just gets stuck at the TWRP logo.
I'm guessing that you can't just install OTA updates, so I have two questions:
1. How can I install the update (without losing all my data)?
2. If I can't install the update, how do I get rid of the "System update downloaded" message that keeps showing up?
It's been a few years since I've been in to this kind of stuff, so forgive me if these are dumb question
Thanks!
If your using systemless supersu and have an unmodified/untouched system partition then Flashfire app, maybe able to apply the update.
http://forum.xda-developers.com/showpost.php?p=65189334&postcount=77
Otherwise you will need to flash factory images (which can be done without wiping data) to update.
Related
I have a D2G. I rooted it.
But it now wants to do a 2.4.3 update. of course the update fails when it reboots
So my question is, could i apply the update using the bootstrap. has anyone tried doing this, would it brick my phone if i tried.
jbroderick said:
I have a D2G. I rooted it.
But it now wants to do a 2.4.3 update. of course the update fails when it reboots
So my question is, could i apply the update using the bootstrap. has anyone tried doing this, would it brick my phone if i tried.
Click to expand...
Click to collapse
You probably could if you remember to wipe data and cache, and you should probably get the Team Black Hat app and download the SBF/driver/RSD Lite files just in case.
Edit: Oh, the update file. If it's failing to install, you should probably just try the full install. I'm not sure why it wouldn't go through unless you're on stock, in which case, you HAVE to use full install.
I think he is talking about the official Verizon update. Not FRM...
When you rooted did you stop or remove any of the Blur apps? That will cause the update to fail. All of the Blurr must be there for the update to work.
If you used Z4Root to root your device, try to unroot the device with zroot and then try the update again.
You may have to re-install Zroot after it is completed to re-root the phone. But I did the update before I rooted almost the day I got the phone so I had not really done enough to notice if it wipes the device and data. My guess would be no!
Since I did this from the stock rom I did not bother to look but if the file is a zip file then chances are likely you can run it from the clockwork recovery.
But best bet is to unroot and then try it again before you go that route.
I would however get RSDLite and the stock SBF to have handy in case you run into problems.
You cannot apply the OTA update (I assume you are talking about 2.4.330 Verizon official OTA update) from the custom recovery. It must be instaled via stock recovery. But due to the way update is made (patch based) it will fail if there are alternations (missing files) in any of the system areas. You must restore all changes you made in /system/app (assuming you froze/delete some stock apps), if you are rooted it is ok, update will not bother (extra files in system do not break the checksum - update only checks original files. But if there is even a single file missing (deleted/renamed) in system area, update will fail to install. If you can't figure it out (what is missing) and update keeps failing, simply flash full SBF to return to stock, apply the OTA update then reroot and freeze/remove all apps that you don't want in system area.
Hi,
I was previously current with the stock firmware, but rooted. I have OTA Rootkeeper. SU was backed up and did a temp unroot before the update.
After installing the OTA 2012.11.07 Update, every app at startup threw "Unfortunately, ... was closed" errors. I could not even launch any apps without them closing. Subsequent reboots ran through the "Updating Applications" cycle, but kept the same error result, basically creating an error loop.
I was able to "fix" it by manually installing the firmware update (now running 10.4.4.20-20121026 without error), but have lost root. OTA rootkeeper has no listing to restore root. So 2 questions (1 is very obvious, at this point):
1. Did I lose/overwrite the rooted SU binary or can this be relocated/replaced somehow?
2. What the root options (if any) for the TF700T Android 4.1.1 version?
Any other suggestions?
Thanks!
acraigl said:
Hi,
I was previously current with the stock firmware, but rooted. I have OTA Rootkeeper. SU was backed up and did a temp unroot before the update.
After installing the OTA 2012.11.07 Update, every app at startup threw "Unfortunately, ... was closed" errors. I could not even launch any apps without them closing. Subsequent reboots ran through the "Updating Applications" cycle, but kept the same error result, basically creating an error loop.
I was able to "fix" it by manually installing the firmware update (now running 10.4.4.20-20121026 without error), but have lost root. OTA rootkeeper has no listing to restore root. So 2 questions (1 is very obvious, at this point):
1. Did I lose/overwrite the rooted SU binary or can this be relocated/replaced somehow?
2. What the root options (if any) for the TF700T Android 4.1.1 version?
Any other suggestions?
Thanks!
Click to expand...
Click to collapse
There was another OTA update? my crappy tablet hasn't received any update since the original JB update. It says no update available. ASUS website doesn't show any new firmware update files.
I (painfully) solved my problem. I flashed back to Gingerbread, got root, then upgraded to the latest Jelly Bean. This time OTA rootkeeper did it's thing. No idea why it was so broken before. Unfortunately, it removed all my apps and settings so I'm busy restoring for the night
I picked up a second hand Galaxy S8 over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization?
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
jwoegerbauer said:
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
Click to expand...
Click to collapse
Thanks, I've heard different in the past. That OTA updates can lock you out of being able to run certain bootloaders for multiboot and such.
bump for input from others
Downloaded one S8 ota zip and checked. According to install-recovery.sh the command and path to fota package is on cache.
So going into recovery and wiping cache should do it.
edit: then again it might write it back on boot... but does it install it right away? IDK. Factory reset?
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
deusfaux said:
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
Click to expand...
Click to collapse
You're rooted so you're failing the pr-OTA block verifications, thus the OTA is failing, is the likely scenario.
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
deusfaux said:
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
Click to expand...
Click to collapse
I normally manually flash updates with fastboot.
Only use OTA update on one or two devices.
You have to restore the original boot image.
Run the update and patch the new boot image with Magisk.
Normally the steps are something like this.
1. Open the Magisk app and restore images.
--- Do not reboot ---
2. Open the OTA Updater
- Download and install the OTA -
--- Do not reboot to continue ---
3. Open the Magisk app and install to inactive slot (after OTA).
4. Switch back to the OTA updater and select reboot to continue.
Cheers.
You could use PixelFlasher to make the process a little easier If you don't want to do everything manually each month.