I've unlocked and rooted my Nexus 7 2013 the day I got it (first week of release). Had no troubles with the device. All OTA went fine.
I think - not sure - I lost root when OTA Kitkat was delivered.
I rooted again last week, with xda update supersu-v1.86.zip.
It looks like everytime I shut down the Nexus, my root dissapears. I have to test this further, but does this sound familiar to someone ?
Anyone that might explain what is going on ?
sbtwister said:
I've unlocked and rooted my Nexus 7 2013 the day I got it (first week of release). Had no troubles with the device. All OTA went fine.
I think - not sure - I lost root when OTA Kitkat was delivered.
I rooted again last week, with xda update supersu-v1.86.zip.
It looks like everytime I shut down the Nexus, my root dissapears. I have to test this further, but does this sound familiar to someone ?
Anyone that might explain what is going on ?
Click to expand...
Click to collapse
Try opening Supersu and see if it needs to be updated - it probably does since chainfire just released a new version (1.91). Let Supersu reboot to recovery and update using twrp or cwm and it *should* solve your problem.
added- after an OTA its probably better to install Supersu through TWRP or CWM if you lose root, installing it through Google play seems more hit and miss in my experience (YMMV, but it always seems to work better for me this way)
SuperSU has a survival mode for OTA updates, however it requires the paid version.
If you did an OTA you will have to re-root unless you had survival mode enabled.
I recommend reflashing TWRP, then reflash supersu.
Then clear Dalivik cache and cache.
Thanks @oldsoldier2003. SuperSu was saying that the bin file was not present. So I went in recovery and adb pushed the 1.91 file in recovery with twrp again and let it install. It's back ok now.
@userdelroot : I only use the xda version of supersu never the google play store ones.
I don't know what messed it up ... but I'm glad it's back again.
Thanks all of you for your help.
Just curious as to the reason to not use the Google play superSu?
Once you are rooted etc
Sent from my Galaxy Nexus using xda app-developers app
Related
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.
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Click to expand...
Click to collapse
There are many ways to accomplish the same end goal.
You can actually install the OTA while rooted. Just need to run the small fix in this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
Rerooting on this device is super simple.
There are also other options like flashing the factory images or one of the pre-rooted odexed/deodexed repackaged mostly stock ROMs. You can find them described here:
http://forum.xda-developers.com/showthread.php?t=2415497
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Sent from my Nexus 7 using xda app-developers app
datallboy said:
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Click to expand...
Click to collapse
You need to run the fix I mentioned above OR unroot BEFORE installing the OTA or the OTA will fail near the end.
You can find the OTA here:
http://forum.xda-developers.com/showthread.php?t=2415497
Don't quite understand the post, so better to just hold off on an attempt.. Would using the unroot option in SuperSU, allowing the OTA update to go through, then rerooting work fine without deleting data?
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Sent from my Nexus 7 using xda app-developers app
Super-Su unroot never help you if you delete something in the /system directory
1)you must flash fix after root
2)do not flash permanent custom recovery and relock bootloader (if your bricked you devices you can send to Warranty Service)
3)replace backup of /system directory before update
and after update clean Dalvik Cache before flash Root again (if superuser privilegies still anavalable for you)
Understand the fix now. Noticed the update went through, but got an error when it finished. Flash ota update in temporary recovery. Correct?
Sent from my Nexus 7 using xda app-developers app
I just downloaded the OTA to the device, unrooted, installed the OTA in TWRP, and then the latest superSU zip (still in recovery). Reboot and voila.
datallboy said:
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Click to expand...
Click to collapse
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
The fix worked, and I'm still rooted. with all data. Temporarily booted into TWRP, flashed the fix and forced OTA update. Thank you!
ripelli part
Don't fear the ota update. There were no negative effects on my rom or kernel.
-cleanROM1.3
- 3.4.0 ElementalX1.1+
sfreemanoh said:
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
Click to expand...
Click to collapse
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
sambistt said:
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
Click to expand...
Click to collapse
I'm not sure what you're saying in reference to my earlier comment...are you saying something I said was incorrect?
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
Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
goldengutz13 said:
Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
Click to expand...
Click to collapse
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
muiriddin said:
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
Click to expand...
Click to collapse
so I have to unroot it first, install update then root again?
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Dekxster said:
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Click to expand...
Click to collapse
I used the LG Support Tool method which involves putting the tablet into download mode and doing the update recovery procedure in the LG Support Tool. This (after a long download process) should result in a tablet which is identical to what came in the box. (in the US the procedure currently installs 4.2.2). When it finished the download and install, it reboots the tablet, if you then are stuck in a boot loop, simply do the key combination for a factory reset and it then should boot.
The unroot procedure via SuperSU does seem to leave something behind that the OTA still detects...
If you need further details I have another post in one of these threads detailing exactly what I did...
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
goldengutz13 said:
so I have to unroot it first, install update then root again?
Click to expand...
Click to collapse
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
muiriddin said:
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
Click to expand...
Click to collapse
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Subtleone said:
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Click to expand...
Click to collapse
True, more than likely a flash-able version will exist once someone makes it.
It already has a work around for loki by reinstalling the old aboot
http://forum.xda-developers.com/showthread.php?t=2698267
Just do steps 2 and 3.
Works fine on mine
Sent from my LG-V500 using xda app-developers app
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
I think the issue with this procedure is the recovery / bootloader, not the rooting itself. Still, you will most likely end with an unbootable OS. You are better off flashing via recovery a perfectly stock, pre-rooted image, like this http://forum.xda-developers.com/showthread.php?t=2707363
Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
goldengutz13 said:
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Click to expand...
Click to collapse
I had to click on "recover" Something sorry I have no my PC now.. I left it at work. But I think you'll find.
U got some option and considering lgpad did not boot after update.. I had only one.
It's the procedure that you got to follow after you set gpad in download mode.
No issue at all, just one thing: after rooting you will have to flash a custom recovery if you need, because flashing with lg, flash even lg stock recovery.
erwaso said:
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
Click to expand...
Click to collapse
No I did not unroot.. But only because I did not think about it. And that's the reason why gpad was not able to boot to system and I had to flash it via lg software.
I set gpad in download mode,,then flash via lg software, root with ioroot and finally flashed with flashify custom recovery
Hope to have helped guys
Now I'll go to sleep!
tapatalked..
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
------------------------------------------------------------ Edit --------------------------------------------------------------------------
3- Rooted with IOroot25
I've done an OTA update on my rooted G Pad, no issues either. I didn't do a factory reset, just did the update.
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Hugo-PT said:
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
Click to expand...
Click to collapse
I froze a few apps using rom toolbox, think that would matter?
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
GePeKo said:
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The development section has a thread on IOROOT and it works. Have at it! I'll do this whole thing when the kids nap lol
erwaso said:
I froze a few apps using rom toolbox, think that would matter?
Click to expand...
Click to collapse
with frozen apps you shall have no problems.
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
ChenZ86 said:
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
Click to expand...
Click to collapse
Because you have applied systemless root. Anything, ANYTHING different from completely stock will cause the normal OTA process to fail. These posts keep asking the same question and the answer never changes. It is what it is. There are a ton of posts here which will explain alternate flashing processes to update, then re-root your device.
Try using flashfire from Chainfire. It detects downloaded ota and ask you if you want to try and flash it. Also there is an option to re-root after updating. If the ota doesn't install then download the factory image for February and flash the whole thing. Make sure data is uncheked so that it doesn't wipe your data. It's a bigger download than ota but it will definitely work.
I had stock + root + xposed + layers. Managed to update to latest build with automatic re-root. Then I just flashed twrp-recovery using flashify and installed xposed through twrp. Took me 5 mins to flash everything (excluding time to download the factory image). All without using a PC!
Skickat från min Nexus 5X via Tapatalk
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
2x4 said:
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
Click to expand...
Click to collapse
[emoji106] Or even stock rom.
Sent from my Nexus 9 using Tapatalk