I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
AstroDigital said:
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
Click to expand...
Click to collapse
Install could have failed for a variety of reasons. If you are rooted, or have a custom kernel, or are unencrypted, of there is any modification to the system.
You can sideload the OTA, but really? That's as much work as fastboot flashing the system image.
So, if your bootloader is unlocked, I'd suggest that you just fastboot flash the individual .img files, extracted from the system image.
.... I did a manual install, I have not had much luck with OTAs
Related
My Nexus 9 is stock, un-rooted with an unlocked bootloader.
I have received the OTA update but when it reboots it gets part way through then shows "error" with and android on his back. I have downloaded the OTA file from AndroidPolice and tried flashing via adb sideload.
It attempts to verify the current system but then errors with the following message:
Package expects build fingerprint of google/volantis/flounder:5:/LRX21L/1546449:user/release-keys or google/volantis/flounder:5:/LRX21Q/1573789:user/release-keys; this device has google/volantis/flounder:L:/LFW73W/1491895:user/release-keys
Click to expand...
Click to collapse
Why have I got a different build?! Is there a different OTA that i need?
I have the same issue, any one any idea?
same here. tried factory reset just to eliminate didn't help
https://plus.google.com/110305043896789356373/posts/bHyo4UazRpH
As I have an unlocked bootloader i've just flashed the recovery from the factory image and then applied the OTA update (mostly to see if it would work, otherwise i'd have continued with factory image). It's booting up now. I guess Google will need to push a new OTA that updates from this version... a bit of a screw up though!
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
And now my phone is stuck with a white screen. Menu options are:
Reboot
Reboot to Bootloader
Boot to Download mode
Boot to Recovery Mode
If I select recovery mode, it is unable to launch and takes me back.
Ok, I set it to Download mode and re-ran the RUU .exe, and it seems to have flashed properly now. So I guess I'm good. But I do have questions:
A) Why did the OTA fail multiple times with the System 7 message
B) Why did the RUU .exe wipe everything and give me the 155 failure the first time
C) Is there anything I should do/install/check to prevent problems in the future?
shawndoc said:
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
Click to expand...
Click to collapse
you did something to make status modified
Yes, but what? Every other OTA has installed fine. I haven't tried to root or mess with s-on/off. The only thing I can think of, is last time I reset my phone (due to gmail failing to get push notifications) I uninstalled a bunch of the bundled apps, but I did it using the normal apps management settings.
shawndoc said:
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Click to expand...
Click to collapse
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
schmeggy929 said:
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
Click to expand...
Click to collapse
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
shawndoc said:
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
Click to expand...
Click to collapse
Gotcha, the 2.11.651.180 was the pre-MM update then the MM full OTA. Yes it is weird you were getting those error on a OTA. Even the RUU shouldn't have lead to an error as well. You still having problem or everything ok now?
Yup, all good now. Forcing the phone into download mode and performing the upgrade took. Thanks.
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.