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.
Related
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
How many times per day does this thread need to be made?
You're either going to have to flash just the update via fastboot on your own, or unroot and accept the OTA normally.
Well I appreciate the answer, sorry to be a bother...
Anyway, is this the way it's always going to be since I'm rooted and unlocked? Where will I be able to download the OTA updates so I can flash manually with fastboot?
It won't work if you have ClockworkMod's recovery, you need the stock recovery.
Sent from my Galaxy Nexus using XDA App
105437 said:
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
Click to expand...
Click to collapse
Dowload from http://code.google.com/android/nexus/images.html. It needs 7Zip to uncompress the file. Once decompressed it has a file with no extension, decrompress that again and you will have the several file.
The just power the phone off and power back on with the volume up and down pressed. Same as when you rooted it.
Then run these commands:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot update image-yakju-icl53f.zip
This will not wipe your phone!
You will need to root it again.
This is what I just did and works prefectly!
Root and unlocked bootloader shouldn't prevent you from installing if you still have stock recovery. If you have ClockworkMod recovery instead, you can use that to flash it manually. If your phone downloaded the update zip, it should be located in /cache.
You'll probably have to re-root after applying the update, regardless of how you install it.
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
105437 said:
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
Click to expand...
Click to collapse
I believe that in rom manager you should be able to set the recovery back to the default.
Bad Liar said:
I believe that in rom manager you should be able to set the recovery back to the default.
Click to expand...
Click to collapse
ROM Manager only has the option to flash ClockworkMod, not stock recovery. But the stock recovery can be extracted from the Google factory images and flashed with fastboot.
I have same problem like yours, how can i solved it? my device is SE WT19i
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
ceribaen said:
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Click to expand...
Click to collapse
Each if those warnings that you are getting is because something is not stock. You will need to download the appropriate stock file for each of those warnings. I have already posted the stock build.prop and boot image in the main IMM76I update thread. If you need others, instructions can be found in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
philipdeane said:
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
Click to expand...
Click to collapse
bingefister said:
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
Click to expand...
Click to collapse
toxaris said:
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
Click to expand...
Click to collapse
All of you guys recommending using a toolkit: do you even understand the OP's issue? I don't think so, otherwise you would know that a toolkit won't do what he needs done.
My opinion:
On an unrelated note: you need to figure out how to do things manually before you start using toolkits, otherwise you will never learn anything. There is a reason they teach you long division in school before letting you use a calculator...
Sent from my Galaxy Nexus using Tapatalk 2
Guys i heard that galaxy nexus got at the end of march 4.0.4 update and i still didn't got it.Every day i go and check for updates but no luck.Also i have tried clear data at google framework services but still on 4.0.2 .I have bootloader locked and i don't want to manual install it because i have to unlock it and i will lose all on my phone.Any trick or something that can show me to update the phone?Thx
popab said:
Guys i heard that galaxy nexus got at the end of march 4.0.4 update and i still didn't got it.Every day i go and check for updates but no luck.Also i have tried clear data at google framework services but still on 4.0.2 .I have bootloader locked and i don't want to manual install it because i have to unlock it and i will lose all on my phone.Any trick or something that can show me to update the phone?Thx
Click to expand...
Click to collapse
Are you on the samsung or google stock rom? IF its a google stock rom (yakju or mysid) then you should have got an update push but if you are still on the samsung rom then there is no update from them.
Mark.
Check my guide for an unlock procedure...that includes backing your applications up.
Where can i see if is samsung or google rom?(thx for reply)
Jubakuba, to make a nandroid should i have the bootloader unlocked?(thx for reply)
popab said:
Jubakuba, to make a nandroid should i have the bootloader unlocked?(thx for reply)
Click to expand...
Click to collapse
If i may, that's something even google can find the awnser.
To make a nandroid, you need cwm/twrp. To have any of those, it is understated that you need to be unlocked, and stated on first post of each custom recovery you will find that a custom recovery needs to be flashed by fastboot, or... by a custom recovery already installed.
sent from my i9250
bk201doesntexist said:
If i may, that's something even google can find the awnser.
To make a nandroid, you need cwm/twrp. To have any of those, it is understated that you need to be unlocked, and stated on first post of each custom recovery you will find that a custom recovery needs to be flashed by fastboot, or... by a custom recovery already installed.
sent from my i9250
Click to expand...
Click to collapse
Again, this is wrong. There is no need to unlock if he is running 4.0.2 to install CWM.
@OP:
If you are not running yakju or yakjuzs, there is no update available for you. You either have to switch to yakju (see here) or wait.
If you are running yakju or yakjuzs, and want to get the update without losing any data do this:
1) Follow the procedure here to get root access.
2) Install ROM Manager and use it to flash CWM. Use CWM to do an nandroid backup.
3) Unlock your bootloader
4) Use CWM to restore your nandroid backup
5) Follow the procedure here to update.
Hello Guys
To start off , i was on YAKJUUX version on 4.0.1 ICS stock
i converted my YAKJUUX in to YAKJU using this http://forum.xda-developers.com/showthread.php?t=1626895
Now i am running YAKJU version 4.0.4 IMM76I
while doing this backed up my 4.0.1 by using Clockwork Mod.
I took 2 backups namely one of the stock 4.0.1 before updating and one after of 4.0.4 after updating
Question: How do i restore to the versions that i backed up if i want to ?
After this
I tried to update to Jelly bean 4.1.1 yakju JRO03C from IMM76I using this link http://forum.xda-developers.com/showthread.php?t=1419170
After following the thread meticulously, the Recovery mode only shows an Android with open stomach and a red exclamation mark !
Then i tried to use my brain (which i regret) i used command prompt to Boot CWM: fastboot boot recovery-clockwork-5.5.0.2-maguro.img and then tried to flash that .zip file ( yakju JRO03C from IMM76I: http://android.clients.google.com/p....signed-yakju-JRO03C-from-IMM76I.f946a412.zip )
It didnt work .. the adnroid said " INSTALLATION ABORTED" so i cut my losses and here i am querying you guys !
NOW I DONT KNOW WHAT TO DO ! ... ANY SUGGESTIONS?
PS : I WANT JELLY BEAN and dont want to go to a candy shop !
My phone originally came with Yakjuux, lovely right?
My question is, why would you want to restore to it?
I highly advise you to pick up the GNex Tool Kit by mskip, set it up, and reflash stock 4.0.4 yakju.
It's very simple, and easy to use. If you are not sure, read tutorials! Take your time!
You will be prompt with a Jelly Bean OTA soon after you complete this. You need FULL STOCK for the official update to work.
Hence: Reflash Stock.
Assuming you backed up by going in to clockworkmod, then choosing "backup", simply go back in to CWM and choose "restore" (I think the option is actually called "backup/restore"
You obviously need your backup folder on your phone to do this.
DevilishSerpent said:
My phone originally came with Yakjuux, lovely right?
My question is, why would you want to restore to it?
I highly advise you to pick up the GNex Tool Kit by mskip, set it up, and reflash stock 4.0.4 yakju.
It's very simple, and easy to use. If you are not sure, read tutorials! Take your time!
You will be prompt with a Jelly Bean OTA soon after you complete this. You need FULL STOCK for the official update to work.
Hence: Reflash Stock.
Click to expand...
Click to collapse
To answer your first question, i would intend to restore to the previous version if the current builds for Jelly Bean are not stable... just want to have security to go back to in case something goes wrong.
.
I really dont want to root my phone as i use this for official purposes .. so unlocking the bootloader is the farthest i can go..
in my current situation would i be getting an OTA on to my device? if yes then would it be able to be installed with no issues?
Matt08642 said:
Assuming you backed up by going in to clockworkmod, then choosing "backup", simply go back in to CWM and choose "restore" (I think the option is actually called "backup/restore"
You obviously need your backup folder on your phone to do this.
Click to expand...
Click to collapse
Well i copied the back up on to a separate USB and i am trying to restore it back on to my phone again.
TO do that , i have to copy in to the phones` SD ... its not letting me do that !
any idea how i can get around that?
Also, How do i put in Jelly Bean?
dushrox said:
To answer your first question, i would intend to restore to the previous version if the current builds for Jelly Bean are not stable... just want to have security to go back to in case something goes wrong.
.
I really dont want to root my phone as i use this for official purposes .. so unlocking the bootloader is the farthest i can go..
in my current situation would i be getting an OTA on to my device? if yes then would it be able to be installed with no issues?
Click to expand...
Click to collapse
You do not need to root your phone to reflash to 4.0.4 Yakju via Tool Kit. All you need to do is unlock your bootloader, flash, lock bootloader.
You can back up Yakju 4.0.4, then update to JB. No root is required. Requires 3 minutes of your time, at most. There will be no issues if installed properly.
DevilishSerpent said:
You do not need to root your phone to reflash to 4.0.4 Yakju via Tool Kit. All you need to do is unlock your bootloader, flash, lock bootloader.
You can back up Yakju 4.0.4, then update to JB. No root is required. There will be no issues if installed properly.
Click to expand...
Click to collapse
Roger
I`ll get on it and keep u updated .. Thanks
dushrox said:
Roger
I`ll get on it and keep u updated .. Thanks
Click to expand...
Click to collapse
No problem. If you run into any issues you can send me a message and I will walk you through.
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
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root
ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.
Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.
Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD