Since I rooted my Nexus 5X, whenever I'll go into the SuperSU app, it'll ask me to update my binary but a few seconds after I go to do that, it pops up with the message "Installation failed ! Please reboot and try again." However even after reboot it won't work. Has anyone had the same problem, or have any idea how to fix it?
Other things to know is that I'm using a Mac so if I need to use it, I'll have to use Terminal commands on Command Prompt, the version of SuperSU I flashed was Beta 2.56 and the custom recovery I'm using is TWRP.
Thanks in advance.
guessing you flashed SuperSU to your phone via TWRP. after you flashed it, did TWRP ask you again specifically if it should flash SuperSU?
if that was the case the solution is easy: repeat the process and decline that offer from TWRP, because that replaces the version of SU you initially flashed.
Related
My 4.4.3 OTA installed just fine this afternoon and I immediately grabbed the latest SuperSU .zip and installed it with TWRP to get re-rooted, but after I told SuperSU to get itself re-installed from Google Play, it wanted to update the binary, and the "normal" method wouldn't work, even after a couple of reboots and retrys.
I don't have TWRP installed on my Nexus 7, instead just using fastboot to boot it when I need it for something, so the technique that finally got the binary updated was to tell SuperSU to use the TWRP update mode, then when it I got the popup saying it was about to reboot to recovery, I plugged in the USB cable and ran:
adb reboot bootloader
fastboot boot openrecovery-twrp-2.7.1.0-flo.img
That worked. As soon as TWRP booted, it installed the script SuperSU had prepared for it, and the binary was indeed updated.
I never had a problem with the "normal" binary update method before. Something new and "helpful" in 4.4.3 I guess.
You can share the script SuperSU?
RazrBR said:
You can share the script SuperSU?
Click to expand...
Click to collapse
If still having issues, try the 1.99r4 from the link in my signature.
It fails to install Rom, when I go to reboot TWRP it says Kindle doesn't have root. Is there a way to check for root in TWRP. When I go to install Cyan nightly ROM i get stuck at; detected filesystem ext4 for /............ then Error; Error executing updater binary in zip
Then I downloaded a cyan release and it fails right away with Error executing updater binary in zip
I think it has something to do with not verifying root first.
If that's the case what steps should I take to get root?
akimity said:
It fails to install Rom, when I go to reboot TWRP it says Kindle doesn't have root. Is there a way to check for root in TWRP. When I go to install Cyan nightly ROM i get stuck at; detected filesystem ext4 for /............ then Error; Error executing updater binary in zip
Then I downloaded a cyan release and it fails right away with Error executing updater binary in zip
I think it has something to do with not verifying root first.
If that's the case what steps should I take to get root?
Click to expand...
Click to collapse
CM usually has root built in - the reason you're getting the "no root" error is likely because CM isn't flashing properly. This might be the case because your TWRP version is out of date. Download the latest TWRP zip from this thread, then flash it from TWRP, reboot back into TWRP when prompted, and then try flashing CM again.
monster1612 said:
CM usually has root built in - the reason you're getting the "no root" error is likely because CM isn't flashing properly. This might be the case because your TWRP version is out of date. Download the latest TWRP zip from this thread, then flash it from TWRP, reboot back into TWRP when prompted, and then try flashing CM again.
Click to expand...
Click to collapse
Thanks, trying now.
akimity said:
Thanks, trying now.
Click to expand...
Click to collapse
My kindle fire refused to flash CM11 saying that it wasn't compatible with my device, but once I updated TWRP, it flashed just fine.
Sent from my Samsung Galaxy S6 Edge+ using Tapatalk
I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!