Hi
I have Android 5.1.1 running with root on my Nexus 4 (using Nexus Root tool kit)
So there's a stock recovery installed.
There's Superuser installed.
There's an update waiting to be installed and I would like to keep the root or be able to root without losing data.
My phone has bootloader unlocked. And SU app installed.
Cheers
Sent from my Nexus 4 using Tapatalk
I don't remember if you need to be unrooted or not, but you can just try to see if it works rooted first. If it doesn't you can unroot your phone by going to settings in the SuperSU app. To reroot after that just flash the SuperSU zip.
EDIT: You can get the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
Hi again
So I tried to apply the OTA update and it restarted and started to install the update and it gave me an error in the midway with a red exclamation () mark in the androids stomach.
So I pressed power + Vol up button and restarted my phone using the menu.
I thought it was probably because of the root. So I went to SUPER SU app and Uninstalled it (un rooted). Restarted and SUPERSU was gone.
After a while the update came back. And I applied it again. And this time the same error.
So I pressed power + Vol up again and checked the log and it says that /cache/update.zip has unexpected contents.
Anyone got any idea why is this happening?
This time I've formatted cache. And so far (5 mins) no update Notification yet.
Looking forward to your help.
Cheers
Sent from my Nexus 4 using Tapatalk
You can't have an amended /system partition to use the OTA with 5.0+. Even uninstalling SU will not work. If you want to use the OTA Process, you will need to flash the factory /system image, which will cause you to lose root (and is sort of redundant in light of the fact you can just extract the updated system.img file from the latest Factory Image and just flash that to upgrade to it). That said, it only takes a minute to root so would suggest just making sure you are comfortable with the process as opposed to trying to preserve root.
Thanks.
Sent from my Nexus 4 using Tapatalk
Related
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
GatorsUF said:
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
To enable ADB to go:
Settings-> About Tablet-> Click Build Number for Easter Egg Multiple times! BOOM!
I am not sure if there's a way of rooting without PC and custom recovery.
I got a Google Nexus 4 about a month ago. Somebody told me I should root my phone so I installed the Nexus toolkit and did all of that. I proceeded to install a buncha stuff on it like Call Master, Titanium backup, etc.
But then I kept getting notifications saying there was an update to Android 4.2.2 so I updated it thinking maybe it wouldn't cause a problem. But now none of my programs work, and when I open up SuperSU it says:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
how can I fix this?
htothez said:
I got a Google Nexus 4 about a month ago. Somebody told me I should root my phone so I installed the Nexus toolkit and did all of that. I proceeded to install a buncha stuff on it like Call Master, Titanium backup, etc.
But then I kept getting notifications saying there was an update to Android 4.2.2 so I updated it thinking maybe it wouldn't cause a problem. But now none of my programs work, and when I open up SuperSU it says:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
how can I fix this?
Click to expand...
Click to collapse
Do you have a custom recovery? You'll have to flash the SuperSU zip again so it can install the binaries.
http://forum.xda-developers.com/showthread.php?t=1538053
Alot of times u lose root when u install an OTA. You will need to reroot your phone
CMNein said:
Do you have a custom recovery? You'll have to flash the SuperSU zip again so it can install the binaries.
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
What's a custom recovery exactly? I'm a complete noob to this stuff.
And how do I flash the SuperSU zip again?
Just download the toolkit from WuFresh and in it they have an for Nexus 4 on 4.2.2 proceed to root again since your bootloader should be already unlocked (when the phone boots you see under Google a lock that has been unlocked) once it's rooted again, you'll be clear, I would suggest making a fresh Nandroid after you rooted having the new OTA.
Sent from my Nexus 4 using xda app-developers app
Sparta507 said:
Just download the toolkit from WuFresh and in it they have an for Nexus 4 on 4.2.2 proceed to root again since your bootloader should be already unlocked (when the phone boots you see under Google a lock that has been unlocked) once it's rooted again, you'll be clear, I would suggest making a fresh Nandroid after you rooted having the new OTA.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i might try this.
So basically I gotta re-root my phone again? If I do that am I gonna lose everything?
No only unlocking the bootloader will erase your data
Sent from my Nexus 4 using Tapatalk 2
Get OTA Root Keeper from the Play Store and back up. Then whenever there is an OTA update, you just restore the back up and you will have root again.
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
My device was fine and rooted until 4.3 dropped and just like when 4.2 dropped I lost root access.
I downloaded the Nexus Root Toolkit and ran through the Root process. There were a couple of times where the on screen messages weren't going forward such as push files to device, etc. but when I rebooted the device it seemed to be ok and it went into TWRP.
After it went into TWRP it said Rooting but nothing happened. I hit reboot, system, then it asked if I wanted to root. I swiped for yes.
I rebooted my device and started Super SU. It says my device isn't rooted.
Can anyone assist me with this. I'm almost thinking this isn't worth it if I have to jump through hoops every time there is an update.
Thanks.
Nevermind I fixed it. I had to install SuperSU 1.5 manually in recovery in order to get it to work.
Will tht work on my razor hd maxx xt926..same issuie had root.then over the air ota update 4.3 took my root accsess..tried reroot several ways..no luck.got it to install a diff su app..but when reboot..says su not installed .everytime I reboot the symbal # pops up says update binary .try to says same .su not installed..plz tell me step by step how u went in recovery to manually install.how reboot in recovery?.then update from playstore?.or flash again?and re root?
Sent from my SCH-I545 using xda app-developers app
http://techglimpse.com/steps-root-custom-rom-android-nexus/
I have a rooted N10, but not running any custom ROM. Have Lollipop 5.0 installed and just got the notice for the 5.1 upgrade. I'm somewhat of a noob to Android, but learning alot. Wondering if doing the OTA would be better than manually installing the upgrade. I'm gonna backup using TWRP no matter what. I want the simplest, most effective way to get the update. Thanks.
You'll likely loose root by applying the OTA, but that maybe the easiest way to upgrade assuming you've not altered or removed any apps from /system/app directory as the OTA does a check before installing. You may also need to re-apply recovery but I doubt it. Assuming you are using TWRP you can use that to gain root again. 5.1.1 has worked flawlessly for me for the last week or so.
Sent from my Nexus 10 using XDA Premium HD app
3DSammy said:
You'll likely loose root by applying the OTA, but that maybe the easiest way to upgrade assuming you've not altered or removed any apps from /system/app directory as the OTA does a check before installing. You may also need to re-apply recovery but I doubt it. Assuming you are using TWRP you can use that to gain root again. 5.1.1 has worked flawlessly for me for the last week or so.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I wasnt sure if the OTA would install since it was rooted, but if I lose root, I can always root again. I've not removed any apps from system/app. I'll make sure I backup and if i need to recover, I can figure that out.
The OTA threw an error on my rooted N10 and wouldn't install. Stock recovery. I ended-up installing the 5.1.1 factory image in "no-wipe" mode, and everything was successful.