Develop Bugs

OTA Update failed

Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?

For me the same problem.
I think something went wrong during the update. The installation of the update was already 30 minutes ongoing and nothing happened. After resetten the phone it started up with still 4.0.1 and no system update availiable.
Anyone an idee what went wrong?
---------- Post added at 11:53 AM ---------- Previous post was at 11:13 AM ----------
chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
See following guide : http://forum.xda-developers.com/showthread.php?p=20843237
Worked for me. The problem is that I have CWM recovery installed.

People use this phone on stock?
Sent from my Galaxy Nexus using Tapatalk

I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.

chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.

dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237

Laintsurge said:
I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.
Click to expand...
Click to collapse
Yeah, I had the same problem, but see link from above: http://forum.xda-developers.com/showthread.php?p=20843237

dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
True.
EddyOS said:
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237
Click to expand...
Click to collapse
Your link contradicts your reply.

Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj

sstang2006 said:
True.
Your link contradicts your reply.
Click to expand...
Click to collapse
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.

efrant said:
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.
Click to expand...
Click to collapse
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.

chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
sstang2006 said:
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.
Click to expand...
Click to collapse
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.

I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.

Quidlor said:
I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.
Click to expand...
Click to collapse
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.

efrant said:
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.
Click to expand...
Click to collapse
In his first post he did not specify which recovery he had.
chrisjaffe said:
Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj
Click to expand...
Click to collapse
(I suppose you have the GSM version because of your ATT logo)
As you are describing right now, you are not rooted and in stock recovery.
Try flashing manually the OTA 4.0.2 which you can find here: http://download.peteralfonso.com/maguro
If it fails, then the original OTA 4.0.1 you forced was not the real OTA from google, so reflash the 4.0.1 from the above link and then flash 4.0.2.
If you have he CDMA version then find the OTA for that.

efrant said:
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.
Click to expand...
Click to collapse
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.

Quidlor said:
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.
Click to expand...
Click to collapse
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)

efrant said:
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)
Click to expand...
Click to collapse
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.

Thank you very much for the answers. I did not mean to cause such a fuss. I am aware of how to flash the image manually, as I did that to force the 4.0.1 update.
I guess what (as it turns out) I was really asking was, What caused this to stop? And how to I retry/restart the automatic update?
The only other info that I can think that is relevant here is that I am sure that I forced the actual OTA. I wonder if something happened during the flash, or since, that corrupted something that the update is checking.
Oh and it is an unlocked GSM Nexus though I am currently in the UK for about 6 months so I have given up my ATT contract for a Pay-as-you-go Lebara SIM while here.
Thanks again for the answers, next time I'll try to be more clear the first time.
cj

Quidlor said:
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.
Click to expand...
Click to collapse
When the next update comes out, you can either either flash back the original radio before updating, or remove the assert in the update-script file in the new update.

How I can apply Security Patches on a Rooted Rom?

Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?

If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.

Help with softbrick nexus 5x

Hi!
I had 2 nexus 5x phones. One rooting went fine, the other is stuck at the Welcome to Android cycle.
I unlocked the bootloader, and I used chainfire auto-root script from linux.
When the phone boots up it has the blue welcome screen. I setup wifi and then it forces me to install an android update. It downloads the update, reboots, tries to install it, fails, and then boots into android where it tries to force me into the update.
How can get out of the loop?

Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.

draggehn said:
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
Click to expand...
Click to collapse
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
OP, the way googles OTAs work these days, is that they basically check your system partitions for any modification (e.g. root). if that check fails, so does the update. now what can you do about your little update trap?
if i recall correctly, chainfire includes ways to revert to unrooted. so there is you first possible option. use it, fire up your phone, let it take the OTA (make sure you're on the latest version after that) and attempt to root again.
if that is not an option, you could grab the newest factory image directly from google, flash the whole thing and then root again.
once your phone is up and running (and rooted ofc), it won't be able to apply future OTAs, but instead of forcing you to update, it will only show a notification.

Broken303 said:
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
Click to expand...
Click to collapse
Which is why there was a parenthetical note that you can also flash stock.

Rooted 5.01 want to flash 6.01 - will i lose root?

I have 5.01 and I want to update to 6.01. I want to wipe it clean. Got factory image from Google site.
What's the difference between the OTA and factory downloads?
I can just flash the factory in TWRP right? Will I lose root, or will TWRP ask if I want to keep root?
I still have boot loader unlocked.I just can't remember for the life of me, haven't done flashing etc in a few years.
Thanks!

So...not a single person can tell me if I lose root, or if TWRP will re-root?
Please?

N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.

You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Sent from my XT1565 using Tapatalk

k23m said:
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
Click to expand...
Click to collapse
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
atifsh said:
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Click to expand...
Click to collapse
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...

Syntax323 said:
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Click to expand...
Click to collapse
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.

atifsh said:
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
Click to expand...
Click to collapse
Ahhh what happened??? Why can you not flash them with TWRP???
Thats what I used to do no problem. Not referring to custom roms either.
I am wanting stock rooted.
I used to download the update when one was released from Google's site, put the update.zip in main directory, go in recovery and flash update.zip. TWRP would ask me if I wanted to keep root, I say yes, reboot, update installs... than i'm on the new Android version still rooted.
How is that not possible now?

I am so annoyed... I never had to go through ADB or fastboot to update to latest. I did everything on my N7, it kept root for me and everything.
I feel so dumb right now its ridiculous lol
So than what way can I go about updating my N7 2013 Wifi, which I currently have 5.01. I am Rooted w/ unlocked bootloader.
What is the best way not using ADB, or a PC at all for that matter to update to the latest, 6.01. If possible, how can I keep root, if not i'm not worried about it, i'll just re-root myself.
I appreciate all the responses, sorry if i'm just being an idiot. I just know for a fact I never had to use ADB or my PC to update and keep root...

I'm not familiar with Stock OTA done with twrp (if that's even possible)
Already told you get a custom ROM, get the one mostly stock or if there's a stock ROM in zip format available.
In future you might need to update that bootloader of yours for newer ROMs
Sorry if this sounds harsh why are you so into keeping root as you can't do it again? It's simple as flashing SuperSU. Root method changed after 6 you cant have old methods with 6.
Best bet for you at the moment.
http://forum.xda-developers.com/showthread.php?t=3219148
Sent from my XT1565 using Tapatalk

Rooted P2XL with stock recovery

Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!

youssefkr said:
Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
Click to expand...
Click to collapse
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:

Badger50 said:
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Click to expand...
Click to collapse
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.

youssefkr said:
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
Click to expand...
Click to collapse
Stock recovery yes, however, root is the ota killer as well :good:

There was a moment that flashing twrp would brick the phone and that they made it where you couldn't flash twrp anymore
Looks like they found a work around
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Sent from my Pixel 2 XL using Tapatalk