Database Info

SuperSU needs to update binary

Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.

What if you upgrade it using the "normal" method?

If I do a normal install i get the following:
Installation failed!
Please reboot and try again.

brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?

rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.

brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.

rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?

brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards

rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app

brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.

[Q] Recommended recovery?

I've been running TWRP 2.6.0.0 but it doesn't seem to be working with some of the newer roms. It seems difficult to update TWRP these days. GooManager throws an HTTP error at start up and when trying to update the recovery it claims it can find one for my device. The fastboot usb method doesn't work well in 8.1. Would you recommend moving to another recovery?

fredrick255 said:
I've been running TWRP 2.6.0.0 but it doesn't seem to be working with some of the newer roms. It seems difficult to update TWRP these days. GooManager throws an HTTP error at start up and when trying to update the recovery it claims it can find one for my device. The fastboot usb method doesn't work well in 8.1. Would you recommend moving to another recovery?
Click to expand...
Click to collapse
Download the free 4ext recovery updater app and flash latest recovery using the app. No need for fastboot
http://4ext.net/

jmcclue said:
Download the free 4ext recovery updater app and flash latest recovery using the app. No need for fastboot
http://4ext.net/
Click to expand...
Click to collapse
That worked great thanks! Painless install!

fredrick255 said:
That worked great thanks! Painless install!
Click to expand...
Click to collapse

I have a sensation XE, i would highly recomend the 4EXT recovery as well. However i think the only issue i have ever come across it was when i selected "auto reboot" when using a kernal update with the aroma installer. As long as i leave it unticked, i can perform updates without any boot issues on startup.

[Q] Unable to root my OPO! [SOLVED]

So I have watched lots of tutorial videos, used toolkits, etc. but I am unable to root my OPO!
I have unlocked the bootloader and flashed TWRP.
I have flashed SuperSU from TWRP 5-6 times, it says it is flashed successfully, but when I reboot, I don't have root.
I have also tried downloading a pre-rooted stock rom and flashed it but it had the same result!
Any ideas anyone? Btw I am on the latest stock rom (30O)

suffix642 said:
So I have watched lots of tutorial videos, used toolkits, etc. but I am unable to root my OPO!
I have unlocked the bootloader and flashed TWRP.
I have flashed SuperSU from TWRP 5-6 times, it says it is flashed successfully, but when I reboot, I don't have root.
I have also tried downloading a pre-rooted stock rom and flashed it but it had the same result!
Any ideas anyone? Btw I am on the latest stock rom (30O)
Click to expand...
Click to collapse
Here is the best root thread here. have you tried flashing Calks pre-rooted rom. Once you flash this there is no need to flash supersu. Give it a try

playya said:
Here is the best root thread here. have you tried flashing Calks pre-rooted rom. Once you flash this there is no need to flash supersu. Give it a try
Click to expand...
Click to collapse
That's the rom I flashed.. but when I rebooted the device I had no root access!

suffix642 said:
That's the rom I flashed.. but when I rebooted the device I had no root access!
Click to expand...
Click to collapse
did you try and download supersu from the play store and install it that way. also what did you to test the fact that you have no root

playya said:
did you try and download supersu from the play store and install it that way. also what did you to test the fact that you have no root
Click to expand...
Click to collapse
I have tested whether I have root with various apps. Also I cannot remove SuperSU so I tried installing Superuser app from play store but still the same..

suffix642 said:
I have tested whether I have root with various apps. Also I cannot remove SuperSU so I tried installing Superuser app from play store but still the same..
Click to expand...
Click to collapse
go into developer options and check under root access and see what it says

Are you planning to use a custom ROM or what is the goal you're trying to accomplish?
I understand that you're trying to root. But what ROM are you planning to use with ROOT?
Try a custom ROM, do the following
1. Download your ROM, Gapps (if needed), custom kernel (if you want), supersu http://download.chainfire.eu/supersu
2. Put it on your phone
3. Boot into TWRP
4. Factory reset
5. Flash ROM, Gapps, custom kernel, supersu
6. Reboot
... and you should have root.

zephiK said:
Are you planning to use a custom ROM or what is the goal you're trying to accomplish?
I understand that you're trying to root. But what ROM are you planning to use with ROOT?
Try a custom ROM, do the following
1. Download your ROM, Gapps (if needed), custom kernel (if you want), supersu http://download.chainfire.eu/supersu
2. Put it on your phone
3. Boot into TWRP
4. Factory reset
5. Flash ROM, Gapps, custom kernel, supersu
6. Reboot
... and you should have root.
Click to expand...
Click to collapse
Yea he said he did this already but still did not have root. He flashed Calks stock rooted rom

playya said:
Yea he said he did this already but still did not have root. He flashed Calks stock rooted rom
Click to expand...
Click to collapse
I read that, I was suggesting try another flashing custom ROM. I know Mahdi ROM has SuperSU built in but just incase never hurts to flash it.

zephiK said:
I read that, I was suggesting try another flashing custom ROM. I know Mahdi ROM has SuperSU built in but just incase never hurts to flash it.
Click to expand...
Click to collapse
Ok, it does not hurt to try them all if need be. Just the way your post read I am sure he would of said he tried a custom rom but trying more than 1 is something I hope he at least did prior to posting.
OP how many roms have you tried?

Also when your phone boots up, give it a good 1-2 minute before you check if you have root.
Download the SuperSU from the link I provided in the previous post.
Use https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to check. A pop up will appear asking if you want to grant or deny access, grant it.

ok so I found the solution to my problem after flashing supersu using all available recoveries several times!
I unchecked the option "Respect CM root settings" in the SuperSU app and it worked!
btw I can't find a root access setting in the Developers Options. can you guys see it?!

suffix642 said:
ok so I found the solution to my problem after flashing supersu using all available recoveries several times!
I unchecked the option "Respect CM root settings" in the SuperSU app and it worked!
btw I can't find a root access setting in the Developers Options. can you guys see it?!
Click to expand...
Click to collapse
Depending what ROM you're using, its missing built-in Superuser. Just use SuperSU

Can't root after OTA 3.1

This afternoon I applied OTA 3.1 to my Shield Tablet, and reinstalled CWM and flashed supersu. My tablet booted correctly but I don't have root. If I open the SuperSU app, I get "there is no SU binary installed and SuperSU cannot install it. This is a problem!" anyone know how to fix this?
Thanks

I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.

Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk

sixstringedmatt said:
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.

Aventura5 said:
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Click to expand...
Click to collapse
I'm having the same problem.

Im also with the same problem, on 3.0 i used kingroot, but with 3.1 doesnt work also.

Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.

King root 4.5 works to root easily

Got it rooted again
I finally got it rooted again.
1) Put supersu.zip on to sd card.
2) Flashed TWRP with ADB fastboot.
3) Rebooted into recovery.
4) Flashed supersu.zip from the sd card.
5) Rebooted
After that it was finally rooted again. Hope this helps anybody else who has this problem.
Unfortunately though since I got my tablet when it first came out I have a recalled one. This will be my 4th RMA. LOL

danjull said:
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
Click to expand...
Click to collapse
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
EDIT: This worked and now CWM sticks, but i still get the SU binary not installed error.

Aventura5 said:
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
Click to expand...
Click to collapse
No. It restores stock recovery on first reboot.

Kingroot worked for me guys

What I don't understand is how the zip can install the SuperSU app as a system app, but not install the SU binary. Is it possible to manually copy the Su binary to my device? I have root access in recovery mode.

Dose anyone have any idea why this happens?

It works now with the new version of supersu

Is there a guide for rooting the shield from 3.0 and up? Thanks.

tecnoworld said:
Is there a guide for rooting the shield from 3.0 and up? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044

That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.

tecnoworld said:
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
Click to expand...
Click to collapse
It dose say for 2.0, but it should work on everything. This is the "real" way, other methods are hacks that work only on certain versions. I prefer this method, it gives you the most insurance against damage, but you could always just use kingo root. Also, versions 2.x and 3.x are both lollipop.

Aventura5 said:
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Click to expand...
Click to collapse
Just out of curiosity, doesn't fastboot boot (image of recovery) just boot into the recovery and not flash it?
From previous experience, to reflash recovery you need something like flash_image or a way to write the image on the recovery partition... Correct me if I'm wrong...

Impossible to install TWRP 2.8.6.0

First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?

mustang_ssc said:
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
Click to expand...
Click to collapse
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk

Renosh said:
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.

mustang_ssc said:
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
Click to expand...
Click to collapse
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version

Renosh said:
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Click to expand...
Click to collapse
I did that you told me and now i have the Sultan cm13 working perfectly.
I didn't know that, thanks.