[Q] Seem to have lost root, help! - Nexus 4 Q&A, Help & Troubleshooting

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!

Related

Root and recovery without adb?

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.

[Q] After rooted for a month suddenly unrooted

I rooted my Nexus 10 using the Google_Nexus_10_ToolKit_v1.3.0. When I did this I used SuperSU as my super user app.
After being successfully rooted for over a month my device is no longer rooted.
When I try to open SuperSU I get this message:
"There is no SU binary installed, and SuperSU cannot install it.
This is a problem!"
I no longer can run applications that require root access.
I tried installing Superuser and did the fix associated with that but it failed as well.
I haven't done anything to my device except for root it. Why would it all of a sudden become unrooted?
I still have the unlock icon on my boot screen.
Can anyone help?
Did you apply the 4.2.2 OTA update that came out recently? Updates will often unroot the device by removing suid from the su binary.
Easy enough to fix with an unlocked bootloader,new enough versions of Clockwork Mod recovery will check and fix it for you, or you can use adb with any of them to chmod u+s the su binary.
Edit: or use TWRP, was thinking of the Galaxy Nexus.
derobert said:
Did you apply the 4.2.2 OTA update that came out recently? Updates will often unroot the device by removing suid from the su binary.
Easy enough to fix with an unlocked bootloader,new enough versions of Clockwork Mod recovery will check and fix it for you, or you can use adb with any of them to chmod u+s the su binary.
Edit: or use TWRP, was thinking of the Galaxy Nexus.
Click to expand...
Click to collapse
Yes. I think this problem happened right after the 4.2.2 OTA update.
I am not able to get into my recovery. When I try I just get a picture of a dead alien with a red triangle.
Do you happen to know the exact adb commands to perform this? I've tried search but I could not find anything.
Thank you for your help.
Skullpuck said:
I am not able to get into my recovery. When I try I just get a picture of a dead alien with a red triangle.
Click to expand...
Click to collapse
That's stock recovery. You need to use fastboot to re-flash just your recovery.
The adb command is something like "chmod u+s /system/bin/su", from the recovery (where you'll have a root shell in adb).
Or you could just install the superuser zip file from your recovery, once you've got the recovery running again.
derobert said:
That's stock recovery. You need to use fastboot to re-flash just your recovery.
The adb command is something like "chmod u+s /system/bin/su", from the recovery (where you'll have a root shell in adb).
Or you could just install the superuser zip file from your recovery, once you've got the recovery running again.
Click to expand...
Click to collapse
I tried accessing fastboot but the Nexus Root Toolkit says I do not have a fastboot enabled device.
I tried running your command but nothing happened.
Do you have any other suggestions?
You could try installing the recovery through the Goomanager app. Once installed select menu and install recovery script.
Sent from my Nexus 10 using Tapatalk HD
this happened to me also.. but my nexus 10 is more than a month rooted.. from out of nowhere it suddenly becomes unrooted, caused by an unkown reason.. it didn't made any notification/alets or any dialog box when it suddenly becomes unrooted.. i noticed it when i used sb game hacker.. it says that the device is not rooted.. anyway i'll find a way to root it again this weekend..

[Q] Lost Root, Motochopper Error. OTA?

I have a Razr M -- if there is a better place to ask this, please don't hesitate to let me know. I am new to this, but trying to learn.
I had the phone rooted and the bootloader unlocked, 4.1.2. I haven't accepted the OTA, but as you'll see below it's a pain because I've lost root and can't freeze the updater. The phone is still unlocked, and TWRP is still installed, but no root.
I had a problem with Safestrap where it would not create new ROM slots. I fixed it with a data format and factory reset. I was able to reroot with Motochopper, and then used Titanium to restore my apps. I must have restored something that the system didn't like, because I got stuck in a bootloop.
I then factory reset again, to start over. Only now Motochopper doesn't root.
I get a success message from Motochopper, Superuser does appear on the phone, but I also get the lines:
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory
Superuser itself says that the binary needs to be updated, but none of the install options (install, recovery install) work. I tried Voodoo OTA Rootkeeper, since I had a protected SU installed, and it didn't work either.
Since I had Safestrap installed, I thought I might be able to get CMOD to a custom ROM slot even if the stock had lost root. I went ahead and created a custom ROM slot and tried to flash the Razr M CMOD 10.1 and gapps to it. I got a success message, but when I boot I just get a blackscreen; I've waited it out for 20 minutes or so, and nothing loads.
I have the Razr 1.20 utility, but frankly I am afraid to use it to try to go back to stock 4.1.2. I don't know what the OTAs have done, and frankly everything I have loaded to the M has bombed, and if I mess with my (now screwed up) stock install, I don't know that I'll be able to recover. But using the 1.20 utility and flashing 4.1.2 is my last idea.
Any help or thoughts? Why the hell did Motochopper stop working? What does this line about busybox mean? Can it be fixed short of trying to go back to stock 4.1.2?
Any help would be deeply appreciated. Because I lost root (and Titanium) I can't freeze the updater any more, which means it's now a matter of postponing every 12 hours. Not my favorite thing. And because my bootloader is unlocked I really hesitate to accept the OTA.
Since you have TWRP installed, get rid of Safestrap, you don't need it. If you're unlocked you can use Utility1.20 with no issues. If, somehow you did install the OTA, and you still have TWRP, then you just need to flash a SU zip in recovery to retain root. However, I think your best bet right now to get everything back to normal is to use the utility.
Sent from my Droid RAZR M using xda app-developers app
Many thanks. A few questions.
First, I may have misspoken, apologies -- the terminology is new to me. Safestrap has a version of TWRP, and that is what I mean when I say that I have TWRP installed. I don't have it separately installed. Does that change your advice?
Second, can I flash a zip of SU from Safestrap? Would I navigate to the Titanium Backup .zip and use the install function of Safestrap?
I deeply appreciate the advice. I may indeed have to go back to stock with the 1.20 utility, as you note.
Safestrap isn't a version of TWRP. It's based off of TWRP, but it's designed to work with a locked bootloader. Honestly, I would just use the utility and flash back to stock, re-root, and then install TWRP.
If you don't want to do this, your next step needs to be flashing TWRP, deleting and uninstalling SS, and flashing SU. You shouldn't be able to flash SU in SS. If you want to take the OTA, then you need to install an aftermarket recovery, first, so you can flash SU.
Sent from my Droid RAZR M using xda app-developers app

[Q] Lost root and TWRP after JWR66Y update.

Hi,
I lost root after updating to JWR66Y, and when I open up SuperSU, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
So I turned off my phone, pressed volume down+power button to go into TWRP and re-flash SuperSU.zip, but the screen only shows broken android with exclamation mark on it.
So, my question is, what do I do? I want to flash TWRP via adb and then flash SuperSU.zip via TWRP. Is that the correct procedure? I'm afraid if something goes wrong I won't have a way to restore my nandroid backup or something.
Thanks.
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
simms22 said:
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
Click to expand...
Click to collapse
To add on what simms22 said,
SuperSU 1.60 flashable zip: http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip

Trouble rooting on 4.4.2

I've had trouble rooting since I updated to stock 4.4.2. Device has been unlocked & rooted before the update. It still is unlocked, of course.
I've tried using WugFresh's toolkit but that doesn't work. I've tried manually flashing TWRP (v2.6.3.1) and SuperSU (v1.8.5). They install without any errors but when I boot to system and open SuperSU I get the "There is no SU binary installed, and SuperSU cannot install it." error.
Help? Suggestions?
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
planet_x69 said:
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
Click to expand...
Click to collapse
I stopped using the toolkit after it wouldn't work. I already have the latest SuperSU installed and am using TWRP as my custom recovery. When I open SuperSU it says, "There is no su binary installed" and then closes. That's it. I can't even remove SuperSU because it's installed as a system app and while not rooted I cannot uninstall system apps.

Categories

Resources