Develop Bugs

[Q] Root and OTA updates

Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.

zljk said:
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
Click to expand...
Click to collapse
That will never happen with the GN. When you own this phone you're first in line for the updates until the next is coming out then you're second but still faster than the others.
Sent from my HTC Desire using XDA App

When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.

You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk

TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery

TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
If my experiences with my OG Droid match up with the Nexus line, if you've only rooted and haven't actually installed another ROM, you should be able to apply the OTA update and lose root because of it. Then just root again.

martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?

zljk said:
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
Click to expand...
Click to collapse
The alternate way to get official Nexus updates is to download the update zip file once someone copies it off their device and uploads it, and install it in whatever fashion works.

I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google

TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
It will often download and you can try but it will either fail, unroot you, or cause troubles.
You're best off applying the pre-rooted update, or unrooting and taking the OTA.

martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.

blunden said:
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
Click to expand...
Click to collapse
Of course, as is often the case for most phones supported here on XDA. the rooted OTA comes in the form of a .zip soon after it comes out.

slowz3r said:
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
Click to expand...
Click to collapse
When flashing the rooted OTA via recovery, does it wipe the phone (apps and all)?
Also for the other method, when unrooting >> applying OTA >> rooting again, does it wipe the phone at any point during this process?
Help would be appreciated and rewarded!

I just received my OTA update notification and found the update zip itself in the cache of my phone. I can post that update zip here if a mod can come along and tell me where to put it. I am going to wait till I'm home so I can have my rooting facilities handy before starting.

phazerorg said:
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
Click to expand...
Click to collapse
+1. Exactly.
There is a lot of wrong (or slightly incorrect) information in this thread.
Have root has no impact whatsoever in your ability to receive or apply the OTA update. This has been the case on every Android device. However, if you have a custom recovery flashed, you will not be able to automatically apply the update - you will have to find the zip file in the cache and use your custom recovery to apply it.
On a slightly separate note, once you apply the update either automatically or manually via custom recovery, you will lose root. However, if you do have a custom recovery, as long as you flash ChainsDD's superuser package immediately after applying the update, but before rebooting, you will retain root.
On another separate not, if you flash the update as is from Google, it includes a file (/system/recovery-from-boot.p) that re-flashes the stock recovery on every boot, so you will lose your custom recovery. Either remove the file before flashing the update, or just re-flash your custom recovery.

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

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] When I get KitKat OTA, can I still update easily via OTA even though I'm rooted?

Hi!
My Nexus 7 is rooted and bootloader unlocked, with TWRP custom recovery. If I accept the KitKat OTA update when I get it, will it brick my device? Will my device be wiped? Do I need to do anything special? Will anything break (I use Skype and the camera a lot)? Do I need to re-root?
Sorry for the noob question...
-Orange

Apparently it overwrites default recovery and you lose the root. But still it's not safe.
Instead
Download the ota and supersu to your tab.
Goto TWRP
Flash ota first. then immediately flash super su. You retain root with custom recovery.
That's it.
Follow this and nothing breaks.

littleromeo said:
Apparently it overwrites default recovery and you lose the root. But still it's not safe.
Instead
Download the ota and supersu to your tab.
Goto TWRP
Flash ota first. then immediately flash super su. You retain root with custom recovery.
That's it.
Follow this and nothing breaks.
Click to expand...
Click to collapse
Where do we download the ota zip?
Thanks.

poloruiz714 said:
Where do we download the ota zip?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2524978

make sure you are on jss15r
Here's the OTA link
Code:
http://android.clients.google.com/packages/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
and super su just in case
Code:
http://download.chainfire.eu/supersu

littleromeo said:
make sure you are on jss15r
Actually I am on jss15j (rooted tablet as soon as I opened the box), clockworkmod recovery (latest build) so what files do I need? Also do I perform a full wipe or flash on top of current system? Sorry for the noon question. Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Root should not affect the OTA update.
I have a rooted Nexus 7 LTE which ran on 4.3.1 until yesterday. Last night I received the update message. So I updated to Kitkat 4.4.
It worked great especially since SuperSU managed to keep the root access. So after the update I had no additional work to get it rooted again

bama35453 said:
Root should not affect the OTA update.
I have a rooted Nexus 7 LTE which ran on 4.3.1 until yesterday. Last night I received the update message. So I updated to Kitkat 4.4.
It worked great especially since SuperSU managed to keep the root access. So after the update I had no additional work to get it rooted again
Click to expand...
Click to collapse
How about custom recovery?
Sent from my SPH-L710 using XDA Premium 4 mobile app

Unlocking & Root N7 (2013) on Kit Kat?

Hey everyone, Im new here, just got the Nexus 7 2013 Asus.
I updated to Kit Kat right away, I tried using that root toolkit thing or whatever... it got my tablet unlocked but it would stay stuck on a message that it was trying to boot some .img file when I clicked root...
Long story short, I restored 2 times and I guess that doesnt work with Kit Kat yet... and I relocked my tablet. Anyway know how I can correctly unlock and root my new Nexus 7 on Kit Kat?

After an unlock you can manually flash the recovery IMG then just flash the super su zip for root.
Adb fastboot recoveryimage.IMG
Then the super su zip can be flashed once in a custom recovery.
If needed I can do a team viewer with you and get you all set up.
prshosting.org

ta_help said:
Hey everyone, Im new here, just got the Nexus 7 2013 Asus.
I updated to Kit Kat right away, I tried using that root toolkit thing or whatever... it got my tablet unlocked but it would stay stuck on a message that it was trying to boot some .img file when I clicked root...
Long story short, I restored 2 times and I guess that doesnt work with Kit Kat yet... and I relocked my tablet. Anyway know how I can correctly unlock and root my new Nexus 7 on Kit Kat?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2536420
Make sure you download the correct custom recovery for your device (prerequisite 3).
Sent from my Nexus 6 using Tapatalk 4

Unlocked & Rooted N7 on 4.3.1 will it stay so after update to 4.4 ?
prsterero said:
After an unlock you can manually flash the recovery IMG then just flash the super su zip for root.
Adb fastboot recoveryimage.IMG
Then the super su zip can be flashed once in a custom recovery.
If needed I can do a team viewer with you and get you all set up.
prshosting.org
Click to expand...
Click to collapse
Dear Experts,
I'm still new at this game, so bear with me please.
I have a LTE N7 on 4.3.1 (JLS361) that is unlocked & rooted.
Now I get tho OTA Update to 4.4 (KRT16S) downloaded & ready to install.
Aside from all those bad things that don't work anymore in 4.4 (eg. FLASH), what will happen ?
Will my N7 revert to a locked & unrooted device ? or will it stay unlocked & rooted ?
Or will it stay unlocked, but unrooted, and I only need to flash the SuperSU ZIP again ?
Thanks for enlightening me.
JMF

fiechterjm said:
Dear Experts,
I'm still new at this game, so bear with me please.
I have a LTE N7 on 4.3.1 (JLS361) that is unlocked & rooted.
Now I get tho OTA Update to 4.4 (KRT16S) downloaded & ready to install.
Aside from all those bad things that don't work anymore in 4.4 (eg. FLASH), what will happen ?
Will my N7 revert to a locked & unrooted device ? or will it stay unlocked & rooted ?
Or will it stay unlocked, but unrooted, and I only need to flash the SuperSU ZIP again ?
Thanks for enlightening me.
JMF
Click to expand...
Click to collapse
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Mine is also unlocked and rooted and want to upgrade to KK.
When you said flash, you meant I had to install TWRP first then flash SU again?
I am curious because when I first rooted my N7, I used the Nexus 7 Toolkit and did not install TWRP. Can't I just use the toolkit again to re-root?

lanwarrior said:
Mine is also unlocked and rooted and want to upgrade to KK.
When you said flash, you meant I had to install TWRP first then flash SU again?
I am curious because when I first rooted my N7, I used the Nexus 7 Toolkit and did not install TWRP. Can't I just use the toolkit again to re-root?
Click to expand...
Click to collapse
If you had a TWRP installed and downloaded the superuser binaries when you rooted initially, all you need to do is flash them again by pressing the "install" button in recovery. Based on the way he asked it, I believe that was the context of the question.
If you don't, you should install a custom recovery:
Wi-Fi only: http://techerrata.com/browse/twrp2/flo
LTE: http://techerrata.com/browse/twrp2/deb
Then download the superuser binaries to your N7:
http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
And flash them by pressing the "install" button in recovery.
Your toolkit might work, but why not just do it yourself?
Full instructions (skip unlocking the bootloader):
http://forum.xda-developers.com/showthread.php?t=2536420
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
If you had a TWRP installed and downloaded the superuser binaries when you rooted initially, all you need to do is flash them again by pressing the "install" button in recovery. Based on the way he asked it, I believe that was the context of the question.
If you don't, you should install a custom recovery.
Click to expand...
Click to collapse
I assume there's no other way to re-root other than installing TWRP?

lanwarrior said:
I assume there's no other way to re-root other than installing TWRP?
Click to expand...
Click to collapse
You can install another custom recovery, e.g., clockworkmod.
Some toolkits reflash stock recovery after rooting, but that could only useful if you have something like a Samsung or HTC. Absolutely no point on a nexus device.
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
You can install another custom recovery, e.g., clockworkmod.
Some toolkits reflash stock recovery after rooting, but that could only useful if you have something like a Samsung or HTC. Absolutely no point on a nexus device.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Thanks again for the help, xdhall. Sorry if I sound like a newbie, but I had the Note 8.0, I rooted and I could never get it back to stock. The original stock image for the US Note 8.0 was not available so I was stuck.
Didn't want the same thing happened with the N7, but you brought up a good point... this IS a Nexus device!

Thanks
xdhall said:
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Thanks xdhall.
That makes it much easier to get back to ROOT then.
Just having to reboot in Recovery Mode and install the latest superSU.zip will be a breeze.
I'll probably wait a few weeks/months to upgrade to 4.4 though, as the comments on the 4.4 release are not that good, and I have several very important (for me) sites that still use Adobe Flash.
Anyway, I'm glad I haven't to start from scratch (backup, unlock, restore, flash recovery, flash superSU), as this is extremely time-consuming and tedious.
Again Thanks & have a nice WE.