Develop Bugs

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?

[Q] Going from JSS15R to KTU84P on rooted flo with TWRP 2.6.0.0

I tried flashing the KTU84P zip using TWRP, but that didn't work. From what I've read, I apparently need to flash stock recovery, do the OTA update, then flash TWRP again? Won't that get rid of my root?
Ideally, I don't want to lose my data or have to excessively fiddle around with tools to get root again, if possible. I've kept my tablet at 4.3 for months because I didn't want to do a ton of research for this, but WiFi issues forced me to try upgrading.

archer007 said:
I tried flashing the KTU84P zip using TWRP, but that didn't work. From what I've read, I apparently need to flash stock recovery, do the OTA update, then flash TWRP again? Won't that get rid of my root?
Ideally, I don't want to lose my data or have to excessively fiddle around with tools to get root again, if possible. I've kept my tablet at 4.3 for months because I didn't want to do a ton of research for this, but WiFi issues forced me to try upgrading.
Click to expand...
Click to collapse
Update TWRP, link in signature.
Download factory image, link in signature.
Flash all img files manually except userdata.img and recovery.img. Delete those two.
Read my post here http://forum.xda-developers.com/showthread.php?t=2789463

Aerowinder said:
Update TWRP, link in signature.
Download factory image, link in signature.
Flash all img files manually except userdata.img and recovery.img. Delete those two.
Read my post here http://forum.xda-developers.com/showthread.php?t=2789463
Click to expand...
Click to collapse
Thank you! I was under the impression that I could just flash the zip since 4.x updates seemed much more incremental than 1.6 to 2.2 and then 2.2 to CyanogenMod on my old CDMA HTC Hero. I guess that isn't the case though.
Mostly I didn't want to re-arrange my icons but thinking about it I can probably get Titanium Backup to back up everything in my tablet so that flashing a Google factory image won't be a pain...

archer007 said:
Thank you! I was under the impression that I could just flash the zip since 4.x updates seemed much more incremental than 1.6 to 2.2 and then 2.2 to CyanogenMod on my old CDMA HTC Hero. I guess that isn't the case though.
Mostly I didn't want to re-arrange my icons but thinking about it I can probably get Titanium Backup to back up everything in my tablet so that flashing a Google factory image won't be a pain...
Click to expand...
Click to collapse
You won't lose any data if you don't run the flash-all batch/script, and don't flash userdata.img.

[Q] Proper Way to Flash SuperSU.zip/Root N7 - Fresh Tablet 4.4.2??

Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,

Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.

_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.

Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.

_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.

Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.

How I can apply Security Patches on a Rooted Rom?

Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?

If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.

Accept OTA or Flash entire ROM?

Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!

I'm not sure, but, you can just flash the ota in twrp and make sure to flash the twrp img after flashing the ota. And, always make a twrp backup

AFAIK you need stock recovery for OTA to work (not 100% sure).
If downloading whole 1.4GB ROM is not a big issue, it's safer to dirty flash the whole ROM. Otherwise you could flash back stock recovery, install small OTA, then flash TWRP again. A bit more work, but less downloading.
Sent from my OnePlus 3 using Tapatalk

This question doesn't belong in this section. @Stephen please move this to the Q&A section. Thanks.

DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
Let me make it clear, the full rom flash is a better option and you can do so from twrp. You would not loose twrp after the flash and need not flash the recovery again. SuperSU/Magisk flash is optional after the ROM flash. I see that you are running 3.0.4-1 which is a 7.1.1 compatible TWRP so there is no need to worry of any data loss. TWRP is also able to flash the OTA's provided you have not made any changes to your system partition and have remained unrooted.
You can come to General / OOS thread and ask there for further understanding :fingers-crossed:

You can flash OTA as long as your kernel is on default, what I mean is stock/untouched which is basically same situation as yours since youre unrooted. ? So yes you can flash OTA no need for full flash

If me, i like waiting full ROM zip release and do clean install.
Sometimes, flash OTA getting error (cause root, bla bla bla hahaha )
Yeah, it could be lazy gonna install back all apps at least you backup it
My advice, if you update same Android version, no problem to do a dirty flash (same ROM like LOS 14 to LOS 14, but if different ROM, i suggest better do clean install)
But if different version, mean 7.0 to 7.1.1, better clean install (dirty also no problem, but wonder in future got problem)
But hey, different people, different way right? This just my 2cent

It is my understanding that when moving from whole version number changes (6 to 7, 7 to 8) etc that a clean install is definitely way to go but even from 7.0 to 7.1? Also when you download the OTA, is the file saved somewhere so you can then locate it in TWRP for flashing? I don't want to allow the system to install the ota automatically correct?

DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
It is best to clean flash if you've major upgrade like 6->7 or 7>8 something like that but if as your question you're still on marshmallow so you can flash OTA zip through twrp and make sure after OTA you've to flash twrp again to maintain it. If the system shows OTA it can't flash it via open recovery on twrp, you must have stock recovery to do it.

This thread is not for ROM development. Please get a mod move this thread to the Q&A section.