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.
Related
Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.
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...
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
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying firewater and HTCdev) was Sunshine. I eventually paid for it and tried to root. I installed CWM at first but didn't realize that Supersu had to be present on my sd-card, so I rebooted. I then flashed TWRP over CWM and tried to root with it instead. Unfortunately, I had downloaded Supersu off the Play Store and (of course) didn't achieve root from the bootloader. That was a few hours ago.
Now I'm stuck with TWRP and no matter what I do, I cannot figure out how to root. I've flashed 3 different versions of Supersu from recovery and none of the zips I install offer me the option to root. I've tried to flash Supersu through adb sideload. I've even tried using ROM manager to reboot and install a copy of Supersu downloaded off my phone's Chrome (probably didn't work because I'm not rooted - it tells me "an error occurred while trying to run privileged commands").
I was under the impression that after installing the Supersu zip from recovery, you would be asked to root either directly after installation or upon rebooting. However, when I reboot, TWRP warns me that "There is no OS installed, are you sure you wish to reboot?" From what I've read, that normally indicates a soft-brick, but my phone is definitely not bricked (yet).
How can I flash Supersu in a way that gives me root?
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
harper3663 said:
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Jyotirdeb said:
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Click to expand...
Click to collapse
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
ashyx said:
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
Click to expand...
Click to collapse
I can boot into twrp, and it's the most recent version from their website (for the Verizon HTC One). For some reason, it didn't ask me to install the su binary the first time I rebooted, and now I don't know how to do it.
harper3663 said:
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
Click to expand...
Click to collapse
Thats why u shouldnt use toolkit.Try an ruu then follow the link i have posted
Just got a dev edition and I'm having trouble getting rooted. I followed the guide here very carefully and I've gotten TWRP installed and then I backed up. I accepted the TWRP prompt to install SuperSU and all seemed to have gone fine. Then I rebooted and tried opening the SuperSU Install app and it told me that the SuperSU install was not complete and that I had to download the SuperSU GUI from the Play Store... The app took me straight to the Play Store and it appeared to already have been installed so I hit Update. Nothing happened. I tried searching for SuperSU on the Play Store and found SuperSU myself and hit install... already installed though. I hit update. It updated. At this point the normal SuperSU icon was showing in my app drawer (the superman one with the pound sign on it --- or as the youngsters call it a 'hash tag'). I tried opening it but I'm getting "There is no SU binary installed, and SuperSU cannot install it." I tried downloading SuperSU direct from chainfire's site, saved it to the download folder on my internal SD and then tried installing in TWRP. I'm getting "Zip Signature Verification Failed: 1" and "Error installing zip file '/cache/recovery/update.zip'.
I've tried reading around but don't want to just try a bunch of stuff without being sure it will work for this particular device. Any help much much much appreciated.
I finally got it working... I uninstalled the SuperSU from the Play Store and then went into TWRP and flashed the same version of SuperSU that was current in the Play Store... I was trying to flash an older version of SuperSU in TWRP... I flashed 2.4 in TWRP (which is the Play Store version) and then I had to reboot and go to Play Store and install it (b/c even though I flashed it, there still was no icon). That's it. Works.