Develop Bugs

Rooted and Unlocked can't install OTA update

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

[HELP] Can't Figure Out Why I'm Not Rooted?

Here's some info:
GSM Galaxy Nexus - Retail (bought from amazon).
Version: 4.0.1 (says no further update available).
Build Number: ITL41F
Can't remember if I rooted, then updated to ITL41F or not.
Followed THESE instructions successfully:
Code:
- Got drivers for Galaxy Nexus installed.
- Used "fastboot-windows oem unlock" and unlocked bootloader.
- Used "install-superboot-windows.bat"
Does this mean I am rooted permanently or have I missed out something?
I do not have Clockwork MOD installed. I don't plan on putting a custom ROM on the phone, I just want root access on the stock ROM.
Superuser is installed.
RootExplorer is denied superuser permissions (never had a prompt or anything). I can navigate to system/app/ and see superuser is in there. RootExplorer does see all the folders and files, but cannot be mounted in R/W mode.
Superuser Update fixer app says (under "force):
Code:
Checking signatures... ok!
extracting tiny busybox... ok!
extracting superuser.apk... ok!
Gaining root access ... fail!
In laymans terms, what do I need to do now to gain root access to my phone?
Also, to clarify, if I run a OTA update to the stock ROM, will it un-root my phone?
Thanks

Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html

fastboot-windows.exe boot boot.superboot.img
Should have just used this after you unlocked boot loader for route
Anyways , the above will get you sorted
Merry Christmas

40Glock said:
Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html
Click to expand...
Click to collapse
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.

I don't understand why you want to be rooted then...
Sent from my Galaxy Nexus using XDA App

you should move your question to the galaxy nexus q&a forum, you will get more help there, if not find someone who already had the same issue. Read ALL stickies at the top of the forums. This will help solve your problem. Posting here will most likely get you bad attitudes fyi
Sent from my Galaxy Nexus

anotherxdauser said:
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.
Click to expand...
Click to collapse
1. Unlocking the bootloader wipes the device not CWM. Mine came unlocked from retail store.
2. According to Superboot thread you can root without CWM.
3. Did you install busybox like the instructions say?
Similar to the previous post...since you have a GSM phone post/look in GSM thread for proper help.
Sent from my Galaxy Nexus using xda premium

Ditto what alot of others have said. Post about GSM model in CDMA area, plus not dev related. Asked for post to be moved to help you out.
merry xmas and good luck

Thanks for not flaming guys!
Thread moved......

drpancake said:
I don't understand why you want to be rooted then...
Click to expand...
Click to collapse
I need to be rooted to allow various apps to run to their full potential.
Well, tried the rooting process again, now no matter what method I choose, they are all saying "waiting for device".
Any pointers on what to do next?

you can try below if you like.
first of all, make sure your boot loader is unlocked.
secondly,
download CWM recovery from below.
http://forum.xda-developers.com/showthread.php?t=1357642
then download below su binary package i have made
http://forum.xda-developers.com/showthread.php?t=1395155
place su_signed_signed.zip into your sdcard (copy into your phone internal storage)
then turn off you phone, boot into bootloader mode (hold vol+ and vol- and power button).
once you are in it,
type
"fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img".
then using vol+ switch to boot recovery option and press the power button.
once you are in Clockwork Mode Recovery,
choose option "install zip from sdcard"
then browse and select "su_signed_signed.zip"
once it has done, you have rooted your phone.
now all you need to do is, reboot your phone, go to android market,
and install https://market.android.com/details?id=com.noshufou.android.su
then run Superuser,
go to settings,
then select "Su binary v3.XXX, tap to check for updates".
after you tap on that, it should say that SU is out of date.
click on update su binary, then you will be prompted for Superuser request.
once you have permitted it, it will then download the latest su binary and install it.
then you are done.

^^ Except I DO NOT WANT CLOCKWORK MOD on my phone.
However, as closure, I did manage to re-root my phone. I dried different drivers for the Samsung and somehow it just accepted the deivce and rooted it for me.

Return to stock with a broken USB connector

Hi all
My USB connector does not work, I would send him assistance, but unfortunately my device has the bootloader unlocked, with root and rom Mincov6.
I tried to use Mobile Odin, I downloaded directly from the phone the factory image of 4.2.2 and tried to open the file .tgz, however, tells me: "Partition could not be found in file."
What can I do? I'm desperate, I await your response
Thanks in advance.
Sorry for english, but i'm italian :crying:

http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128

bodh said:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
Click to expand...
Click to collapse
My device is GSM, not Verizon

It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.

bodh said:
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
Click to expand...
Click to collapse
From what I understand, who used the Verizon tar in GSM, brock the device.
Now, I can not find anywhere the. Tar for GSM..

This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..

bodh said:
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
Click to expand...
Click to collapse
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?

Try this
ciccionicosia said:
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Click to expand...
Click to collapse
You should've replaced the stock recovery before locking the bootloader. You can try finding a flashable .zip of the stock recovery, but it'd probably have to be made. Has the device ever gotten an OTA update? I'm thinking you could use the following OTA script and patch to reflash the stock recovery in a very minimal sort of way.
First, you'll have to re-root by installing supersu.zip from sdcard download via custom recovery(which youll need to remove later).
Install Root Browser Lite by jrummy, and say no to installing the additional features (you may have to remove some binaries from your sdcard later after unrooting).
Unzip the attachment.
Place the install-recovery.sh in /system/etc/ with r-xr--r-- permissions and root root ownership and group ownership (via long pressing the file once it is in place, first permissions, then ownership).
Place the recovery-from-boot.p in /system/ with rw------- permissions and root root ownership and group ownership (same way as above).
Now power down.
Boot into recovery from fastboot (vol up+down+power, scroll with volume keys until the top says recovery, then press power).
Does it say android recovery on top, or is it still your custom?
If it's stock, let it sit until it boots on its own.
Remove the supersu.apk and su binary via root browser.
Remove rootbrowser and its binaries on the sd.
You should now be in business.
P.S. You could also look for an odin flashable .tar for your device, and flash it to return, but i think that'd be more complicated for you. Those files I provided are put in place during every ota update, and I believe this should work for you.

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

On straight talk, dont have access to a computer! 5.1.1 update for recovery. PLEASE!!

I am on straight talk. I don't have access to a computer, so no Odin or Kies. I haven't rooted in years but I think if I remember correctly. I can use stock recovery for the update. Am I correct? If so could someone please get me the link to the correct file, and verify that. I should load the zip on root directory of internal storage. Then go to recovery mode and apply update.

santacruzmofo said:
I am on straight talk. I don't have access to a computer, so no Odin or Kies. I haven't rooted in years but I think if I remember correctly. I can use stock recovery for the update. Am I correct? If so could someone please get me the link to the correct file, and verify that. I should load the zip on root directory of internal storage. Then go to recovery mode and apply update.
Click to expand...
Click to collapse
I don't have an answer for you, but you may want to ask your question in this thread: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
That thread has downloadable firmware (just beware that these are the Verizon OTA firmware versions, so if you update using these you won't ever be able to root the Note 4 if that ever becomes possible AFAIK). The firmware files are zipped, so you would need some way to unzip the files. The instructions (see post #3) are based on using Odin, but @hsbadr should be able to answer your question about doing the update from internal storage.