[Q] Lost root when updating Busybox - Nexus 7 (2013) Q&A

Hello All - hope you can help me.
Until a few days ago I was on JSS15Q, unlocked and rooted using the excellent Wugfresh NRT. I downloaded an update to BusyBox as I was prompted, and since then I've lost root.
BusyBox (now v9.3) has a message stating "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is inproperly rooted. Try removing superuser/supersu permissions, uninstaling this application, reinstalling this application, and then regranting superuser/supersu permissions for this application."
SuperSU (now v1.65) has the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!".
Since losing root I've done the JSS15R OTA without issue, and last night I tried re-rooting using NRT (latest version) , but the same error messages as above appear.
Is there something obvious (and fool-proof!) that I can do to fix this? Is there any detail I've omitted?
Epic thanks in advance - Digi

digi-sol said:
Is there something obvious (and fool-proof!) that I can do to fix this? Is there any detail I've omitted?
Click to expand...
Click to collapse
Boot into TWRP and install SuperSU 1.55 (the 1.65 install script is a placeholder that does nothing)
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

sfhub - thanks
Before I boot into TWRP, what will installing SuperSU 1.55 actually do, if I'm already on 1.65? Why has updating BusyBox caused this problem, or is that a coincidental thing?

digi-sol said:
sfhub - thanks
Before I boot into TWRP, what will installing SuperSU 1.55 actually do, if I'm already on 1.65? Why has updating BusyBox caused this problem, or is that a coincidental thing?
Click to expand...
Click to collapse
If you post the install script for the busybox you installed I can probably tell you what went wrong, but without that, any number of things could have gone awry.
SuperSU 1.55 should be OK to install on top of 1.65. It usually makes a reasonable attempt at cleaning up past installs before installing itself.

OK - how do I go about getting the install script? - I'd really like to find out what happened and why (might help someone else too!)

It is in the apk for busybox.

sfhub - thanks for your help. Root has been restored!
I installed SuperSU 1.55 via TWRP - I still don't know what went wrong or why, but it's fixed now - cheers. Now, where's that thank you button...

Related

"su binary is not updated" - problem updating

Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Are you s-off? If so not sure what the problem is. If you're not s-off, that's your problem
Sent from my HTC Desire using XDA App
pspuser007 said:
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Click to expand...
Click to collapse
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this zip
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
pspuser007 said:
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
Click to expand...
Click to collapse
If u updated super user through the market, uninstall the update..after that flash the zip in recovery
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
pspuser007 said:
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
Click to expand...
Click to collapse
u never looked in settings/applications?
super user i guess is a system app (like gmails, gmaps, gtalk, etc)..so u can't uninstall those applications..but u can uninstall updates for those applications..mean for system apps u can only uninstall updates
so go in settings/applications, select super user app and u should see uninstall updates, if yes do uninstall updates, if not then its ok and flash the zip
do a nandroid backup in recovery before touch something, just to be sure
I hadn't checked system applications so far.
Unistalled the update, did a nandroid backup and flashed the zip!
Everything OK now!
Thanks a lot for your help!
Many many thanks!!!
what does the zip need to be named?
Does the zip need to be named update or does it stayed named like it is?
Name it whatever makes you happy. Remember its whats on the inside that counts.
Sent from my PG86100 using XDA Premium App
I'm getting the same warning message with my market updated su, when I open Titanium Backup but it hasn't affected anything. I just ignore the message and everything still seems to work. Am I missing something?
Problem Updating
andQlimax said:
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this "goo-inside.me/superuser/su-3.0-efgh-signed.zip"
Click to expand...
Click to collapse
I have uninstalled SU and installed the super user update and I get the following error when I update the binary updater:
"Failed to find currently installed su binary. Update cannot continue"
UPDATE:
I downloaded and installed the binary file (su-3.0-bin-efgh-signed.zip) from androidsu.com and now get FC error "The application Superuser has stopped unexpectedly. Please try again"
Thanks for your help.
When this issue occurred for I found that just by simply reflashing the SU zip in recovery and then running the update fix it seemed to fix it. I think for me it may have had to do with using an outdated version though.
su binary update failed..
Hi, I'm using CyanogenMod 7.1.0 RLS3 for Kaiser.. Today I got a "su binary outdated" I try to update it.. Going ok until "Moving su to it's final location - Fail" how to solve this? guide me please.. I'm newbie..
Hi, I had rooted my Garmin-Asus A50 about a year ago with help from these fora. Also installed Titanium backup and other related apps.
My question: upon waking thisr morning and waking the phone, a message said "SU binary outdated - tap to update" I let it update without thinking -but immediately had doubts about some trojan doing this to gain access.
So I switched off the phone and am trying to gather some info here and on WP. From your post I see that this 'update' message may be legit - or am I wrong?
Thanks ffor any further tips.
.-.

[Q] Vzw G-Nex running CM10 and su problem

I'm on a Vzw G-Nex and running the CM10 nightlies. the issue I'm having is that some apps like Titanium get superuser privileges and that gets remembered. other apps, like Wireless Tether, it asks me EVERY time I after I launch and then select the start tether and then again when I select stop tether.
I also see a warning when in CW recovery that root appears broken and it offers to fix that but I found out the hard way that this doesn't seem to fix anything and can break things instead...
when the phone was running the stock rom and was just unlocked and rooted, I did not have this issue.
it would seem that I'm partway rooted and partway not? any suggestions/ideas please?
*bump*
anyone got anything?
tgeery said:
*bump*
anyone got anything?
Click to expand...
Click to collapse
use supersu instead of superuser. heres a flashable in recovery version http://download.chainfire.eu/212/SuperSU/CWM-SuperSU-v0.96.zip
after you flash, open the supersu app, if it says to update your su binaries, press yes. if the problem still persists, update your busybox.
simms22 said:
use supersu instead of superuser.
after you flash, open the supersu app, if it says to update your su binaries, press yes. if the problem still persists, update your busybox.
Click to expand...
Click to collapse
thanks... I'll give that a shot.

Accidently flashed wrong SU binary, need help!!

My phone is a Huawei u8160 (AKA Vodafone 858) and I rooted it a long time ago with z4root and have had no problems eversince.... until recently when my mate got hold of my phone and accidently flashed an experimental/beta (possibly a binary for x86 systems) SU binary through CWM recovery. I thought I could fix this quite easily by using z4root to uninstall root and then do a fresh reinstall, but it would force close on me after a few seconds. I tried this method with both temporary and permanent root options but nothing worked. The button that pops up saying ''unroot'' wasn't there even though there is still a SU file in /system/xbin as it showed in Rom toolbox. I soon realised that the version of android i was running on my custom rom was not compatible with z4root, so i searched for how to root android version 2.3.9 pro. I dont know the name for that version and it must have been a bit of a flop because google didnt know it either. I dont know how akiro-E (the developer that cooked up the rom) got his hands on version 2.3.9 pro but i recommend to other devs reading this to not use it as there is not much compatibility.
Anyway, i found this apk made by chainsDD called gingerbreak and decided to give it a go. It said that it needed debugging on and that it might take a while, so i did that and pressed the root button. I left it to do its business, but 15 minutes later it was still trying to run the exploit so I stopped and removed it. When i got home later on i searched up how to root any phone and it came up with the pc program 'superoneclick'. I got it, opened it and clicked unroot. It did its thing but failed to remove su and the superuser app like it was meant to. So then i clicked on root and shell root but it did not reinstall properly and got the same error as in unroot error. I did all the steps multiple times but it still wouldnt remove/replace su from the xbin folder. I then reinstalled superuser 3.1.3 and tried using the binary updater on there. I noticed that the su installed was called 'legacy'. The updater was having a spaz and didnt want to update so i tried manually removing su with the root explorer in rom toolbox butvrealised that you needed root (a working one) to do that. Then i found an app on my sd called root cleaner. I tried quick and full cleaning but to no results except for a force close multiple times. I tried to fi the foce close issue by running the script for this in rom toolbox but you need root (surprise surprise) Then i tried flashing cwm recovery through fastboot as i have done lots of succesful times before. It flashed after putting my phone in download/debug mode (power and volume down) but i cant boot to it as you need proper root rights to do that.
I am going to use total commander to check if the permissions are set to 644 for the su binary, if not ill attempt to change them.
I know this a long desciption and technical question but does anyone know any ways to delete the retarded root from my phone and help me restore root as normal? This is a question for the more experienced users and devs on this forum but any help will be appreciated, cheers.
If you've got recovery, you can install one of these zips in recovery mode.
Google "superuser 3.1.3 arm signed zip" and click the first link that comes up - the androidsu one. Then download the superuser zip package that suits your device to your phones internal storage, reboot into recovery, install the zip and there you go! Your root is fixed.
Sent from my LG-E400 using xda app-developers app
Thanks
@odigITECH thanks for the help. I fixed the problem using your method. . . kind of. I flashed recovery via fastboot and then just flashed another rom from my sd card via cwm after I rebooted. Thanks for the help anyway, much appreciated!
No probs
Sent from my LG-E400 using xda app-developers app

Followed "All-In-One Toolkit" rooting instructions, but not rooted

I followed all the instructions in this thread to root my HTC M8: http://forum.xda-developers.com/showthread.php?t=2699065&highlight=binary
I've got the TWRP recovery installed and did the "perm root" thing, which appeared to work as the SuperSU app was in the app launcher.
Now today when I tried to install xposed framework I discovered that the root apparently doesn't work. Opening up the SuperSU application gave this following warning:
"There is no SU binary installed and SuperSU can’t install it"
I googled around but didn't find anything concrete on what to do. I did find this one page that has a supposed fix in the comments, which I tried using but that hasn't done anything: http://www.theandroidsoul.com/root-new-htc-one-2014-m8/
I then thought I'd re-do the "perm root" step again, so I tried that using the all-in-one app, but now when I boot the phone up the SuperSU app doesn't show up in the app drawer at all and doesn't appear to be installed on the device at all, but the flashing step in the recovery doesn't give any errors at all.
So I'm stuck and don't know what to do now. I tried manually doing the flashing that the "perm root" step does but that hasn't given any other results either.
Searched the forum for "supersu binary" and found this thread, which had the solution to this problem: http://forum.xda-developers.com/htc-one-m8/help/help-accidentally-hit-ota-upgrade-t2852100
EDIT: Success!
Turns out I needed to re-flash my SuperSU binary from TWRP. I re-flashed the version I had first which actually removed the SuperSU apk. I re-downloaded it from Play Store, then flashed the 2.01 update. Runs like a charm.
Thanks to everyone for the help.
Click to expand...
Click to collapse
This worked for me. Just went to the store and got supersu. Upon running it, it tells me to upgrade, the Normal mode didn't work but the Recovery mode did. Now after that, root checker says I'm successfully rooted and another app I has can get root permissions too.

SuperSU on CM13

Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
You ALREADY HAVE root with CM-SU. To enable it, just go to developer option and give root permissions to app. Some SuperSU's versions are incompatible afaik. CM-SU preinstalled is just fine.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Meneldur said:
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Click to expand...
Click to collapse
Have you try this method http://forum.xda-developers.com/lg-g2/general/bump-supersu-t3273251
CustomPatcherScript_Bump.zip + UPDATE-SuperSU-v2.65-20151226141550.zip
But it's also can cause reboot loop
Do backup before doing flash that script
That worked fine with my D855 32Gb + CM13

Categories

Resources