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!
Related
I did an OTA upgrade to LG8 and Rooted with CF-Root6.4 and now every time I reboot it shows the "Android is upgrading" message, so anyone know how to fix this without reflashing Rom because I won't be home until next week.
Try to remove the synchronization with samsung account , if there is still a notification, you have to do a wipe date , factory reset ....
unable to update after root
why did i can run the OTA after root? is it normal? the clockwork recovery said the the signature was not recognized.
Fundamental element in order to be able to complete the update process of the Galaxy is to have a firmware entirely original.
If you have on your phone a test version, root permissions enabled or a modified kernel installed (e.s. , CF-Root) will be unable to update.
kintol said:
why did i can run the OTA after root? is it normal? the clockwork recovery said the the signature was not recognized.
Click to expand...
Click to collapse
Root no OTA update as per then thousand posts .
jje
I was Rooted when I got the OTA update and apart from this problem which isn't really a problem it all went through fine, so guess I'll just wait and use Odin to see if it fixes.
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
For the most part, updates will be baked into roms so you won't need to take the OTA
Sent from my Tricked out HTC One
jznomoney said:
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
Click to expand...
Click to collapse
On top of stock recovery, you need to have all stock apps present on the phone. They can be frozen, but they must be there. The first thing any official OTA does it check the signatures of all .apks it expects to find on the device--if any are missing, the update will abort. I learned today that when you unlock your bootloader, several HTC-specific applications are automatically deleted from the phone and this will prevent the phone from accepting the OTA. You'll need to either A) replace those apks, or B) flash a stock NAND backup, flash stock recovery, do the update, then re-flash custom recovery and continue on from there.
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
I installed it and it worked great. I have a unlocked bootloader but I am not rooted.
AT&T update file name and location?
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
StanAnderson said:
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
Click to expand...
Click to collapse
no it will not work
Please...a little advice
Many thanks for all your help.
One question:
I have an HTC One (ATT) - SW Ver 1.26.502.10, bootloader unlocked, rooted, bloatware erased.
If I flash CM 10.1 - does this include the latest OTA update.
Many thanks
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
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?