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.

[Q] Does Unlocking and Rooting stop/effect OTA updates

Hi guys I was just wondering if I unlock and root my stock GSM Nexus, not installing CWM or any custom roms at all just keeping it stock (aside from Superuser, root). Does that stop or affect the OTA updates from google at all.
I did a search but its all basically about putting on CWM and flashing roms and pretty much all rooting help apps I found seem to want to install cwm as well so I'm curious if once I root it is my only way of updating is manually flashing roms myself

http://forum.xda-developers.com/showthread.php?t=1441478

Ahh damn my search skills must suck but I still have to say that the answer was a little vague too
Rooting will not affect OTA updates. If you make any changes to anything outside /sdcard/ it'll cause problems. Manual update will not wipe the device.
Click to expand...
Click to collapse
I guess it means your fine and update will work as long as you don't go modding the original files ?

The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance

Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You should still get your OTA updates. They may break the root on your phone though but thats not really a big deal.
Sent from my XT860 using XDA App

Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You get a different answer because there are a lot of people who have no clue what they are talking about, passing on wrong information.
First of all, there is a difference between "getting" an OTA update notification, and having it install. Those are two separate things. You will get the OTA update notification. Whether or not it will install depends on many things, and it changes with every update. The update has a series of "asserts" or verifications that it runs through to make sure all the files it is going to update are there. You wanna know which files it checks? Don't be lazy - open up an OTA zip file and look at the updater-script file and go through it. There you will see yourself what files need to be stock. Doing it yourself is the only way to learn. Trusting a bunch of xda members who don't know what they are talking about is not the way to learn...
Having said all that, having an unlocked bootloader or having root will in no way impact your ability to receive OR install an OTA update.
Sent from my Galaxy Nexus using Tapatalk

Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..

Laynee1 said:
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..
Click to expand...
Click to collapse
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk

The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Edit - These things also can affect OTA
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.

efrant said:
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ye i know .. I have unlocked bootloader and rooted phone.. But i dont want to flash any custom rom.. I wanna keep it stock.. Just , im saying i cant wait for OTA 4.0.3

jd1001 said:
I have seen this questions posted a number of times from the same user. The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Click to expand...
Click to collapse
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).

adrynalyne said:
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
Click to expand...
Click to collapse
Well thanks for correcting me eventhough I wasn't actually wrong in what I said.
Thanks for adding those bits too I had no idea that other mods could affect OTA although I have read here a few times that the bootloader won't affect OTA. There should be an actual topic on this because with all the information floating around it is confusing.

Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...

danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
Totally agree! Sometimes it's just frustrating becaus eeveryone thinks they know the right answer when in actual fact people post rubbish that is incorrect. I am guilty of it too but I always go back and edit when I make a false statement.

danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.

This is the sort of uncertainty I am talking about. We should create a new topic and nail it down finally!

Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to install an ota update are greatly diminished.

adrynalyne said:
Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to ota are greatly diminished.
Click to expand...
Click to collapse
Ha ha ha sorted!

adrynalyne said:
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
Click to expand...
Click to collapse
No OTA update to date has checked the recovery. In fact, every OTA update to date has forced a flash of the stock recovery.
Sent from my Galaxy Nexus using Tapatalk

Here we go again!

[Q] Android with the red exclamation appear after OTA

Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.

That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.

Jubakuba said:
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Click to expand...
Click to collapse
Why dont you show this guy the light and let him flash google factory image by himself..
OP: there you go http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3

Thank you, guys.

RaptorHawk said:
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
Click to expand...
Click to collapse
You are seen that screen because you have something on your device that is not stock. (Unlocked and rooted makes no difference.)
To be 100% sure that an OTA update will install automatically, you need to have all of the following:
1) the radio that came with the ROM that you are using;
2) the stock recovery that came with the ROM that you are using;
3) the stock kernel that came with the ROM that you are using;
4) all of the original files in /system that came with the ROM that you are using.
Have a look at the thread here. It is for manual installation of an update, but the requirements still apply to an automatic update OTA.

So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.

RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
You are not reading at all at what efrant says and you havent looked at the link i provided.. Until you do so you wont go farther
Galaxy Nexus AOKP m5 Franco kernel m3

Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.

Forget about toolkits, follow this guide please
http://forum.xda-developers.com/showthread.php?p=25477039
Galaxy Nexus AOKP m5 Franco kernel m3

RaptorHawk said:
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Click to expand...
Click to collapse
There are two ways to get 4.0.4:
1) Flash a full 4.0.4 ROM, which is what the link msedek posted is.
2) Upgrade 4.0.2 to 4.04, which is the link I posted a couple of posts back.
In the first case, you easily end up with a clean install, but your data is erased (so back up before)
In the second case, you need to make sure that you undo any modifications you made to the /system partition, the kernel, the radio, and the recovery. Then you apply the update, and you will have an upgraded ROM with all your data and settings intact.

RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...

PaisanNYC said:
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
Click to expand...
Click to collapse
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Click to expand...
Click to collapse
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL

PaisanNYC said:
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
Click to expand...
Click to collapse
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.

efrant said:
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
Click to expand...
Click to collapse
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!

PaisanNYC said:
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
Click to expand...
Click to collapse
Oh, you were referring to a CWM backup. I understand now.
But regardless, you can still flash the Google images via CWM, they just have to be packaged up in a CWM-flashable zip.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for all help. I'm succesfull flash my GNex.

Scared to update to 4.2 JB Pls guide

Model Number: Galaxy nexus
Android Version: 4.1.2
Build Number: JZO54K
this is rooted and unlocked.
Now i am getting messages - system update available Android 4.2 Jelly Bean
I m scared. Should i update?
Will it affect my clockwork mod recovery or root and unlock issues?
Pls guide.

Download one of the roms in Development section..pick the stock OTA or Factory images or any of the custom roms..that way u can stay rooted and unlocked while still getting JB 4.2 (or 4.2.1)

sunandoghosh said:
Model Number: Galaxy nexus
Android Version: 4.1.2
Build Number: JZO54K
this is rooted and unlocked.
Now i am getting messages - system update available Android 4.2 Jelly Bean
I m scared. Should i update?
Will it affect my clockwork mod recovery or root and unlock issues?
Pls guide.
Click to expand...
Click to collapse
if you want to apply the ota you will have to flash stock recovery.. and after applying it you will lose root so you will have to root again. like the other user said its better to just flash one of the factory image from the dev section

AndyGnex said:
Download one of the roms in Development section..pick the stock OTA or Factory images or any of the custom roms..that way u can stay rooted and unlocked while still getting JB 4.2 (or 4.2.1)
Click to expand...
Click to collapse
I have always used stock rom and just rooted and unlocked.
I am not very tech saavy.
I tried updating just by clicking on system update but got red exclamation point on rboot.
is there no simpler step by step way?

You have a custom recovery, as you have mentioned in OP..Hence you cannot update via normal system update.
Just download a rooted rom, put in your sd card and flash via CWM.. Voila! JB 4.2!
Advantage = stay rooted with unlocked bootloader, keep your apps (if you didnt factory reset before flashing, i dirty flashed 4.2 over 4.1.2, so far so good.) , awesome community support for roms
Disadvantage = can't update normally.

Before flashing a new ROM I would update your recovery first.
Sent from my Galaxy Nexus using xda app-developers app

k786 said:
if you want to apply the ota you will have to flash stock recovery.. and after applying it you will lose root so you will have to root again. like the other user said its better to just flash one of the factory image from the dev section
Click to expand...
Click to collapse
Thank u...it clears a little bit...am i correct in understanding that factory image from dev section is actually original android google only...where do i download it...sorry for being so non tech but all help is great. thx

Robert00001 said:
Before flashing a new ROM I would update your recovery first.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thank u...pls say me how should i go about updating my recovery pls...thanks bro

AndyGnex said:
You have a custom recovery, as you have mentioned in OP..Hence you cannot update via normal system update.
Just download a rooted rom, put in your sd card and flash via CWM.. Voila! JB 4.2!
Advantage = stay rooted with unlocked bootloader, keep your apps (if you didnt factory reset before flashing, i dirty flashed 4.2 over 4.1.2, so far so good.) , awesome community support for roms
Disadvantage = can't update normally.
Click to expand...
Click to collapse
You have a custom recovery, as you have mentioned in OP..Hence you cannot update via normal system update.
got it now as i was thinking why i am unable to do direct system update....no it makes sense why i was unable.
Just download a rooted rom, put in your sd card and flash via CWM.. Voila! JB 4.2!
could u pls point me to step by step somewhere...i dont want to mess up picking wrong step pls.
thanks U ALL

sunandoghosh said:
You have a custom recovery, as you have mentioned in OP..Hence you cannot update via normal system update.
got it now as i was thinking why i am unable to do direct system update....no it makes sense why i was unable.
Just download a rooted rom, put in your sd card and flash via CWM.. Voila! JB 4.2!
could u pls point me to step by step somewhere...i dont want to mess up picking wrong step pls.
thanks U ALL
Click to expand...
Click to collapse
bk201doesntexist: http://forum.xda-developers.com/showthread.php?t=1626895
there's also a part about rooting.
then read this one:
http://forum.xda-developers.com/showthread.php?t=1419170
all you need to know about OTA (system) updates.
my advice is to start fresh, google nexus factory images for both 4.2 JOP40C and 4.2.1 JOP40D have been made available. only do so when you've read and fully understand (at least the first link) what your device is about, and what you'll need to interact with it on a more technical stance. read questions from other people. read their experiences and troubles and how they got out of it. prepare yourself to reach the light, and know the true ways of the Force.
any doubts with terminology: http://forum.xda-developers.com/showthread.php?t=1812959

^^ Yes, follow what the user above mentioned, besides, our gNex is really hard to f*** up.. Unless you intentionally did something wrong, its very unlikely you will do anything stupid, if you followed the guides correctly
Sent from the depths of Hades

bk201doesntexist said:
bk201doesntexist: http://forum.xda-developers.com/showthread.php?t=1626895
there's also a part about rooting.
then read this one:
http://forum.xda-developers.com/showthread.php?t=1419170
all you need to know about OTA (system) updates.
my advice is to start fresh, google nexus factory images for both 4.2 JOP40C and 4.2.1 JOP40D have been made available. only do so when you've read and fully understand (at least the first link) what your device is about, and what you'll need to interact with it on a more technical stance. read questions from other people. read their experiences and troubles and how they got out of it. prepare yourself to reach the light, and know the true ways of the Force.
any doubts with terminology: http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Thank u sir for pointing in correct direction...i was tryiong to find correct guides but it was so so confusing...i will read links and see if i can work thank u

AndyGnex said:
^^ Yes, follow what the user above mentioned, besides, our gNex is really hard to f*** up.. Unless you intentionally did something wrong, its very unlikely you will do anything stupid, if you followed the guides correctly
Sent from the depths of Hades
Click to expand...
Click to collapse
yes now that i have correct links for guides i will go thru...there is so much guides and info i was very confused

[Q] Howto delete pending OTA update

I have a yakju GNex with stock 4.1 (unrooted). It has the 4.2.0 update on it - it has tried and failed to install this update several times.
I would like to delete this pending 4.2 update, so I'm wondering where I would find the relevant files.
I figure that, once I've deleted them it might automatically download and install 4.2.2 (and hopefully that will install properly), and if that doesn't work then I will try to manually flash 4.2.2. Either way, I'd like to start by deleting the pending update.
Thanks.

Tomaxda said:
I have a yakju GNex with stock 4.1 (unrooted). It has the 4.2.0 update on it - it has tried and failed to install this update several times.
I would like to delete this pending 4.2 update, so I'm wondering where I would find the relevant files.
I figure that, once I've deleted them it might automatically download and install 4.2.2 (and hopefully that will install properly), and if that doesn't work then I will try to manually flash 4.2.2. Either way, I'd like to start by deleting the pending update.
Thanks.
Click to expand...
Click to collapse
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.

Zepius said:
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.
Click to expand...
Click to collapse
Thank you for clarifying about the OTA being dependent on each other. I take it that applies to the OTA, and not to the published Nexus images so I could still download 4.2.2 and flash it to the phone (bypassing 4.2).
I can see why you suspect that I have modified system files, but I have not. It has stock, unrooted, yakju 4.1 on it.
The only thing non-standard about it is that a Canadian GNex, with an unlocked bootloader, and flashed (via fastboot) to the standard Google firmware. But that is extremely common here, and the problem I'm having is not extremely common, so something must have got mucked up on the phone.
Regardless of how it happened, I would still like to delete the update files if it can be done w/o root.

Zepius said:
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.
Click to expand...
Click to collapse
Now I think that is wrong...
I 'reset' the phone - using the option in settings that erases user data.
It appears that this cleared the pending update, as a day later I was prompted with a new OTA install, but now it was for 4.2.2. I confirmed that I was still on 4.1.1 and it was offering me an OTA update to 4.2.2.

Tomaxda said:
Now I think that is wrong...
I 'reset' the phone - using the option in settings that erases user data.
It appears that this cleared the pending update, as a day later I was prompted with a new OTA install, but now it was for 4.2.2. I confirmed that I was still on 4.1.1 and it was offering me an OTA update to 4.2.2.
Click to expand...
Click to collapse
good, did the 4.2.2 update install fine?

thegtfusion said:
good, did the 4.2.2 update install fine?
Click to expand...
Click to collapse
No, it did not. But I believe that the problem that prevented it from installing OK is the same problem which brought me here in the first place. I don't think it would have offered me the 4.2.2 if that update was not suitable for me.
In the end, I downloaded yakju 4.2.2 stock from the Android Nexus Images page, and then followed efrant's instructions in post#1 of this thread:
http://forum.xda-developers.com/showthread.php?t=1626895
I did each of the fastboot flashing steps, including the optional ones, to get the best chance of overwriting whatever was causing the problem. This worked and the phone is now running 4.2.2.

Tomaxda said:
No, it did not. But I believe that the problem that prevented it from installing OK is the same problem which brought me here in the first place. I don't think it would have offered me the 4.2.2 if that update was not suitable for me.
In the end, I downloaded yakju 4.2.2 stock from the Android Nexus Images page, and then followed efrant's instructions in post#1 of this thread:
http://forum.xda-developers.com/showthread.php?t=1626895
I did each of the fastboot flashing steps, including the optional ones, to get the best chance of overwriting whatever was causing the problem. This worked and the phone is now running 4.2.2.
Click to expand...
Click to collapse
Great man!
Enjoy your perfect Galaxy Nexus now