Hi folks,
I received the OTA update notification for Android 5 yesterday, downloaded it and while installing it - I received an error and the device restarted to normal Android mode (Kitkat 4.4.4 - Nexus 5). I dont know what went wrong, the OTA notification is gone now. And I tried many times for updating the device via OTA, but there is no update information.
Wanted to know the following things:
1. Does any one had similar problems like this?
2. What really went wrong?
3. Will I get the OTA update or should I follow any of the manual method?
PS: Device Used : Nexus 5 - running Kitkat 4.4.4 - Rooted via TowelRoot - Stock ROM
If you feel I miss any major inputs, please do comment, so I can add it.
TIA Have a Great day !!
If it failed chances are you've made a change to a system app/file which is why it's failing. You have to be 100% stock to successfully apply an OTA update
Thanks for the quick response !!
EddyOS said:
If it failed chances are you've made a change to a system app/file which is why it's failing. You have to be 100% stock to successfully apply an OTA update
Click to expand...
Click to collapse
Thanks for the quick response !!
Does unroot help in here? How about unroot and factory reset?
Will I get the OTA anyway?
gladijames said:
Thanks for the quick response !!
Does unroot help in here? How about unroot and factory reset?
Will I get the OTA anyway?
Click to expand...
Click to collapse
If you're the chosen one then, yes, you should get it again.
Related
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
I know the newest update isn't a big deal and it only helps Canadians but I still a. want to update and b. Just know for future updates. I have my phone rooted via saferoot and I tried unrooting and updating and it failed. Tried updating while rooted and failed. I'm running android version 4.3 and VRUCML1. Any help would be apprecaited.
Commies said:
I know the newest update isn't a big deal and it only helps Canadians but I still a. want to update and b. Just know for future updates. I have my phone rooted via saferoot and I tried unrooting and updating and it failed. Tried updating while rooted and failed. I'm running android version 4.3 and VRUCML1. Any help would be apprecaited.
Click to expand...
Click to collapse
I am having the same issue. I don't really care whether the update is applied or not. I just want the annoyingly persistent update message to go away. It is there every time I turn my phone on. Can the update either be applied somehow, or if not, can it be disabled?
Thanks.
Hi everyone!
I've just received and successfully installed a system update for Android 5.1.1 and it says exactly zero about itself. Even Android's version hasn't changed.
Does anyone have any idea what it fixes? I surmise it fixes two recent holes but 10MB sounds a little too much for that.
I also got but nothing happened
Sent from my Nexus 5
I got it, I'm updating manually since for some reason my phone never wants to update the regular way.
It addresses the Stagefright vulnerability
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
ApTeM said:
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
Click to expand...
Click to collapse
flash it through ADB
I use this thread as reference just to make sure I don't miss any step but there are a few others threads like this. http://forum.xda-developers.com/google-nexus-5/general/guide-update-rooted-device-to-5-1-lmy47d-t3050789
OTA install error
I got the OTA notification to download & install the Stagefright patch. Every time I try to install it, it says "error!" shortly after it starts to install and shows the android with a red exclamation point.
My nexus 5 is stock & unrooted.
Any idea what's causing this and how to force the install? If not, I can sideload OTA with ADB later tonight.
Thanks!
I think the build number should have changed to LMY48I.
vagosto said:
flash it through ADB
Click to expand...
Click to collapse
adb fastboot
I've had my first freeze and first complete blackout since this small update
This should be the monthly update mentioned on main page
This update is worthless: http://www.theregister.co.uk/2015/0...efright_fix_wont_be_resolved_until_september/
I will skip it.
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Yes, I think a great number of people know the answer... I had to ask the same question myself a long time ago.
Since Android 5 (I think) the OTA process looks at the entire system for any changes to the ROM partitions, and it will update only if the ROM is intact and unchanged. Root changes the ROM, therefore no update.
I believe that you can update manually by flashing just the system partition, but you'll then have to re-root the phone.
It was precisely for this reason that I got fed up with root, despite its many advantages, and now run encrypted, unrooted, and with Netguard firewall protecting at least some of my privacy.
NoOne12 said:
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Click to expand...
Click to collapse
u should update before making any changes in the system folder or to the recovery.
You should not take the OTA updates while rooted.
One solution would be to download the factory image for the update and fastboot flash system.img from the download, wipe cache, then reinstall supersu.