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.
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Diger36 said:
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Click to expand...
Click to collapse
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Chaosblast said:
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Click to expand...
Click to collapse
Now that IS weird. The screenshot you took is indeed the screen you get in Stock Recovery and pressing Volume up + Power simultaniously should bring you into the recovery menu.
If not: I'm afraid this problem is over my head. Sorry about that... Maybe anyone else?
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
Diger36 said:
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
Click to expand...
Click to collapse
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
jhuynh said:
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
Click to expand...
Click to collapse
Oh ok I thought that was the issue! So it's when you install a custom recovery that the OTA updates won't work. Sorry for the incorrect info.
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
danger-rat said:
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
Click to expand...
Click to collapse
Thanks for that. I got bootloader and recovery mixed up!
Thanks all of you guys. That should be the problem. Then I delete the CWM and then update with the OTA. Then I reinstall the CWM and that should be fine.
It's weird because I my cousin has installed the OTA, and he had also rooted his Galaxy Nexus, and I think he also changed the recovery.
Anyway, it's good to know. Thanks again.
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
danger-rat said:
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
Click to expand...
Click to collapse
I don't want to flash any update via CWM for now. I prefer doing that by the official way until I see some ROM that I like.
I understand what you mean of the firmware. But I think I haven't changed the firmware. I mean, I have only unlocked the bootloader, rooted, and then installed CWM. I don't think that changes my firmware.
By the way, I have installed Android System Info, and checked it. But I don't know how to stay sure. I have attached the screenshot.
Thank you.
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
danger-rat said:
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
Click to expand...
Click to collapse
It's true, but where can I find the exact update (not the full ROM) in a zip package? I don't know how to get it from the OTA, and didn't find it on the forum either.
I want to be sure it's the correct update for my version and only the 4.0.1 to 4.0.2 package.
Bump! Could you answer my last question? It's the last one and all this thread is done.
Thank you.
I have exactly the same problem that Chaos, i tried to do the same as you told him but the problem persist, each time that i try to upgrade 4.04 by OTA it stopped and appair the android with the red exclamation on it.
I have the Nexus rooted and the stock recovery flashed
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??
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
Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?
Did you reflash the ota after you flashed supersu?
What was the error message?
sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?
It will lose the option to blend milkshakes
church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.
datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.
Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!