Related
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.
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.
Hi to everbody here
I googled and found lots of tutorials how to update to yakju.but what i dont understand will i be able to ota and install the update after i change to yakju? i just want to switch it to yakju and after that to install updates over air normally? Whats the easiest way?
Thanks
Theres how to instructions here. Search: imm76d 4.0.4 yakju/maguro repacks, it's odin way to do it and easiest
Sent from my Galaxy Nexus using xda premium
errepu Medical
But thats when you have yakju version??im on yakjuxw!
arydrsr Excerpts
I have the Canadian galaxy nexcus so is its not on yakju.all i want is to change it to yakju and then receive ota updates and install them.
aldenh said:
I have the Canadian galaxy nexcus so is its not on yakju.all i want is to change it to yakju and then receive ota updates and install them.
Click to expand...
Click to collapse
Use this to convert to yakju. Make sure you do all the optional steps in part D, and you will receive every OTA update. yakju is the first build that receives OTA updates, so I'm not sure I understood your initial concern.
efrant said:
Use this to convert to yakju. Make sure you do all the optional steps in part D, and you will receive every OTA update. yakju is the first build that receives OTA updates, so I'm not sure I understood your initial concern.
Click to expand...
Click to collapse
My concern was that when i switch to yakju and receive ota updates in the future im not able to install them.because some reprted their not able to install the updates they get the notification but when they go to install it shows up a error or something.
aldenh said:
My concern was that when i switch to yakju and receive ota updates in the future im not able to install them.because some reprted their not able to install the updates they get the notification but when they go to install it shows up a error or something.
Click to expand...
Click to collapse
That is because those people did something wrong...
efrant said:
That is because those people did something wrong...
Click to expand...
Click to collapse
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
aldenh said:
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
Click to expand...
Click to collapse
not unless you modify some of the system files. if you leave everthing stock, you will get the OTAs properly and not have any issues.
aldenh said:
So when i do it like in this link that you posted im not gonna have problems receiveing and installing ota updates in the future?
Click to expand...
Click to collapse
Not if you follow the steps, and do the optional steps in part D. No problems.
Notes on optional items and other issues:
4) WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the corresponding boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically, but it will install using a custom recovery like CWM. See this thread for details.
Click to expand...
Click to collapse
what does this mean then??
means thats if you want the update to install, you need to have the radio, boot.img and recovery from the stock version that you are on. if you dont, it will fail on install.
aldenh said:
what does this mean then??
Click to expand...
Click to collapse
Exactly what Zepius said and what I said before: you need to do the optional steps in part D.
Ok now I understand thank you guys
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
aldenh said:
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
Click to expand...
Click to collapse
I personally have no issues whatsoever, but some have indicated that they have signal loss issues. There are threads on the topic. A quick search will pull them up...
EDIT: Regardless, you can always go back to 4.0.2 or even 4.0.1 if you want...
aldenh said:
are they any known issues with this 4.0.4 version?because i dont have any issues with this 4.0.1 version but I want better battery life and camera performance.
Click to expand...
Click to collapse
These are the exact reasons why I went to 4.0.4 as well.
I think that it's worth it and I haven't had any issues either. In fact, it also fixed my random signal drop problems on the Rogers network as well.
Hi,
I did it and everything went good.but after i was done with everything a backed up my files with the galaxy nexus root toolkit 1.4 before and when i was restoring my files with that app it said something like "modifiying boot bla bla" cant remeber so im worried that now the boot file is different and im not gonna be able to install the updates when i receive ota updates in the future??
aldenh said:
Hi,
I did it and everything went good.but after i was done with everything a backed up my files with the galaxy nexus root toolkit 1.4 before and when i was restoring my files with that app it said something like "modifiying boot bla bla" cant remeber so im worried that now the boot file is different and im not gonna be able to install the updates when i receive ota updates in the future??
Click to expand...
Click to collapse
That's right, if you have a different kernel (contained in the boot.img), the next updates will not work. You need to flash the stock kernel. Like in the link I had posted earlier.
That's what happens when you try to take shortcuts by using toolkits -- you could have easily backed up your data yourself by running a nandroid script...
efrant said:
That's right, if you have a different kernel (contained in the boot.img), the next updates will not work. You need to flash the stock kernel. Like in the link I had posted earlier.
That's what happens when you try to take shortcuts by using toolkits -- you could have easily backed up your data yourself by running a nandroid script...
Click to expand...
Click to collapse
But i locked the bootloader again before i did the restore so you think the boot file now is different??
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?
Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!
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