I am running Timat 2.2.2. My market asked me to update superuser which I did and it worked. However I keep getting a message that my su binary is out of date. It's on v2.3.1-ef. I check for updates and it finds 3.0 however when I go to update it fails on "Gaining root access... fail!"
Why would this be happening if root is working fine on all other apps? I tried the SU Update Fixer app but that didn't help.
I forgot to mention that I also tried to have SuperUser automatically approve new su requests; still no go.
uninstall the update and re update it again and then try...should work
LPHS said:
uninstall the update and re update it again and then try...should work
Click to expand...
Click to collapse
this worked, thanks.
Related
Somehow, I managed to lose root access. Supersu always gives me the message error saying "There is no SU binary installed, and SuperSU cannot install it." Now applications that requires root access do not work and F/Cs..
Anyone got some information about this problem?
insanehadi said:
Somehow, I managed to lose root access. Supersu always gives me the message error saying "There is no SU binary installed, and SuperSU cannot install it." Now applications that requires root access do not work and F/Cs..
Anyone got some information about this problem?
Click to expand...
Click to collapse
have you tried re rooting?
smaw51 said:
have you tried re rooting?
Click to expand...
Click to collapse
Not yet. Will try flashing the jb rooted rom first
I uninstalled xposed framework as suggested to success installing newest OTA 4.4.3. Now when I try to install xposed framework again I get prompt: Failed to get root access.
I don't know what to do. Can anybody help me?
juniorkm7 said:
I uninstalled xposed framework as suggested to success installing newest OTA 4.4.3. Now when I try to install xposed framework again I get prompt: Failed to get root access.
I don't know what to do. Can anybody help me?
Click to expand...
Click to collapse
Is Root still enabled try testing some other apps that use Root.
If they aren't working chances are you didn't update the root binary after the OTA. Therefore apps can't talk to the binary.
brichardson1991 said:
Is Root still enabled try testing some other apps that use Root.
If they aren't working chances are you didn't update the root binary after the OTA. Therefore apps can't talk to the binary.
Click to expand...
Click to collapse
How can I check if root is enabled? I still have unlocked bootloader and installed TWRP.
If it is locked how can I unlock it?
juniorkm7 said:
How can I check if root is enabled? I still have unlocked bootloader and installed TWRP.
If it is locked how can I unlock it?
Click to expand...
Click to collapse
Open up superuser or SuperSU and see that they are still working, i know SuperSU prompts for a binary update if it needs one.
Other apps to try like titanium backup etc..
Just see if it works with any of those and if not you will need to flash the latest version of the root app you are using.
brichardson1991 said:
Open up superuser or SuperSU and see that they are still working, i know SuperSU prompts for a binary update if it needs one.
Other apps to try like titanium backup etc..
Just see if it works with any of those and if not you will need to flash the latest version of the root app you are using.
Click to expand...
Click to collapse
Ok now I am trying to install SuperSU and after typing:
cd Desktop/android-sdk-windows/platform-tools
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
I get message error: device not found
It is of course connected and run in bootloader mode. What to do?
If you were already rooted before then you probably already have the SU Zip on your sd. Flash it through TWRP. As for checking root, there are numerous root checkers on the play store as well.
juniorkm7 said:
Ok now I am trying to install SuperSU and after typing:
cd Desktop/android-sdk-windows/platform-tools
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
I get message error: device not found
It is of course connected and run in bootloader mode. What to do?
Click to expand...
Click to collapse
adb is used in Android (with USB debugging enabled) and recovery. Fastboot is used in bootloader.
I downloaded root checker and it shows that device is rooted. If so how to install Xposed again?
juniorkm7 said:
I downloaded root checker and it shows that device is rooted. If so how to install Xposed again?
Click to expand...
Click to collapse
Download Xposed http://dl.xposed.info/latest.apk and load it up to your phone to install it. Remember to grant it Superuser request.
Sent using Etch-a-Sketch
Last night I successfully unlocked and rooted my phone, but I've been having some issues getting SuperSU to work completely. When I install SuperSU and open it, it gives a popup saying the binary needs to be updated. I click on normal update, and it says "Installation failed! Please reboot and try again." After reboot, I get the same error. The app itself seems to be working as my ad blockers and whatnot are calling up the root checker, but It just doesn't want to update to the latest binaries. Any suggestions? Thanks!
*update* I fixed the issue. I installed CWM, and was able to update the supersu binaries through recovery.
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
pstgh said:
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
Click to expand...
Click to collapse
Boot to twrp and reflash the SU binary.
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Questions go in the "Google Pixel Questions & Answers" section.
Always use the latest of both unless you read otherwise - for example, if you read the TWRP thread, you'll see a lot of people have trouble with RC2, so just stick with RC1.
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Boot to TWRP RC1, then install SU RC3. Assuming you don't want TWRP permanently installed.
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Crav3 said:
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Click to expand...
Click to collapse
Its been a while since I used Magisk. But at that time, PHH superuser had to be used?? Not sure if that is still the case though. Sorry I could not be more help
Yes it does need to be used and it was already installed. But after rebooting the app was not in my app drawer and i had a notification to install SU through play store. But when i go to play store it says it is installed and needs an update. After updating it tells me su binary occupied and takes me to a page to help fix it but i already tried flashing superuser zip file through recovery and nothing changes
Similar Problem
Have you fixed it already because I am havibf the same problem here. I am usibg Samsung J7 Core
You can do what you said you would do (reinstall stock ROM) and then you can try again. Looks like thats the only thing you can do, unless you can somehow remove the root binary and the app using something like ES File Explorer (but again, it requires root) or you can try another root provider.