Related
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Gilkauss said:
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Click to expand...
Click to collapse
download this, boot into recovery, then flash it. its the latest supersu binaries http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip
Or simply boot into twrp, reboot it and it's gonna give you the option to do so.
Twrp should have told you that you lost root and gave the option to repair it.
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Gilkauss said:
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Click to expand...
Click to collapse
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
It seems that many users have had issues with the last few SuperSU updates in one way or another. Some get errors trying to update the binary. Some say Titanium Backup will no longer work unless you use the paid version of SuperSU. The latest installable zip doesn't work on all devices and needs a fix according to the first post on the official SuperSU thread...
http://forum.xda-developers.com/showthread.php?t=1538053
I decided to switch to the new Superuser by Koush.
sos
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
luubutmucxanh said:
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
Click to expand...
Click to collapse
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
simms22 said:
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
Click to expand...
Click to collapse
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
luubutmucxanh said:
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
Click to expand...
Click to collapse
well, im not familiar with rooting it, heres a link http://www.xda-developers.com/andro...one-m7-and-install-recovery-xda-developer-tv/
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
nickf123654 said:
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Click to expand...
Click to collapse
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
simms22 said:
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
Click to expand...
Click to collapse
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
nickf123654 said:
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
Click to expand...
Click to collapse
you are also missing that its a completely different device. of all my time ive spent in the nexus 4 and nexus 5 forums here, not once has an issue like that been reported. this would better be posted in the note 2 forums.
Thank u very much
gee2012 said:
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
Click to expand...
Click to collapse
Thanks a lot.........your suggestions helped me a lot...... :good:
Updated CF-autoroot with latest Supersu binaries and combined TWRP recovery for SM-T800/SM-T805/T700/T705 Exynos only, Lollipop and Kitkat
I've noticed that quite a number of people seeking to root their device also flash TWRP afterwards, seeing as it's unnecessary to do both steps I have made an all in one package to root and install TWRP recovery.
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version (ADB root shell and Download mode fixes).
UPDATE - I have updated all versions with new builds. TWRP is now v2.8.6.2 and now includes the fixes recently pushed to their repo for encrypted backups. I have also addressed the slow wipe issue, cache, system, etc., which some have experienced and should now be much quicker.
Each device now has it's own build, this is to ensure that TWRP recovery build properties reflect the device it's installed on. ROMs such as CM12 should now install without issue.
Feedback is welcome.
Simply flash with ODIN. Odin 10.6
cf-autoroot-twrp-t700
cf-autoroot-twrp-t705
cf-autoroot-twrp-t800
cf-autoroot-twrp-t805
Check root status with ROOT VALIDATOR
Guide how to flash, credit to Usama m.
http://techbeasts.com/2015/05/01/root-twrp-recovery-galaxy-tab-s-84-running-lollipop-502/
UPDATED TWRP:
http://forum.xda-developers.com/showthread.php?t=3074633
NOTE: It is important to boot to recovery after flashing or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Credits to chainfire for his great work.
FEEDBACK PLEASE
AND DONT FORGET THAT THANKS BUTTON :good: HIT AND RUN IS NOT NICE
.
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
d3xtr0 said:
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
Click to expand...
Click to collapse
Good stuff. :good:
Just picked up a T800 as a birthday present to my mom.. Its going to be hard to give this thing to her..lol
Anyways.. just used this to root and it worked perfect.. Had already took ota to LP..
Thanks !!
delete post !
tids2k said:
delete post !
Click to expand...
Click to collapse
What?
ashyx said:
What?
Click to expand...
Click to collapse
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
snapper.fishes said:
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
Click to expand...
Click to collapse
Why the forum doesn't allow users to delete their own posts is beyond me?
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
lloydb9382 said:
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
Click to expand...
Click to collapse
Correct.
thanx so much it worked great ,
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
almony8 said:
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately AT&T lock the bootloader, so atm you're stuck with a device that cannot be modified in any way.
Sent from my SM-T805 using XDA Free mobile app
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
cyaclone said:
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
Click to expand...
Click to collapse
Use Root Validator and post the output. Root checker doesn't give enough information.
ashyx said:
Use Root Validator and post the output. Root checker doesn't give enough information.
Click to expand...
Click to collapse
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
cyaclone said:
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
Click to expand...
Click to collapse
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
ashyx said:
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
Click to expand...
Click to collapse
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Thanks
Not sure if it matters but what version of twrp is being installed?
AKfortyseven said:
Not sure if it matters but what version of twrp is being installed?
Click to expand...
Click to collapse
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version.
Click to expand...
Click to collapse
= 2.8.6.1
I was running Adaway on my rooted/soff M7 and would like to run it on my now rooted/soff 10. I tried downloading v3.3.1 from @mrRobinson thread here but each time I tried to open the program it said something about a SuperSU error. I'm guessing that it didn't like the modified SuperSU we used rooting the 10 to keep forceencrypt? Any one have an idea or see something I did wrong?
Edit:
Looking through my apps list I can't find SuperSU, but I know it's on here cause it ran when sunshine requested root access and I had to side load it through TWRP for root. Why wouldn't it show up in my app list?
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Load this app: jRummy Root Check
It should work if the SuperSU process was successful. I used jcase's guide Root-optionally-s-off-radio
After that, I loaded the XDA Labs App, then loaded AdAway. Everything working as it should.
You may want to retrace your steps to jcase's quide, and see what might have been missed.
HTH.
I followed jcases method for root and soff and had to side load the modified SuperSU that @starbase64 linked to in that process. That jRummy app says I do not have root. Can I just flash the modified SuperSU in TWRP? I'm definitely soff, so how would I be able to get soff without root? So weird
yes, but restore stock boot.img first
Yes that should work.
Root these days is in the boot.img so if you reflashed that at any point you are back at stock.
Adaway is working fine here!
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
starbase64 said:
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Click to expand...
Click to collapse
Did you flash this file in twrp yet? That should be all you need to do.
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
Oh well
If SuperSU isn't in the app tray and you haven't hidden it manually, flashing back SuperSU (preferably topjohnwu version) should bring it back.
10-4 brb. Thanks
Edit: yes, I checked with jcase too. Just reflashed the zip in TWRP. Although when it was going through its process it said it already found the files and over wrote them anyways, maybe something got corrupted at some point. All is well now, thanks for the help all.
May also be something in /data/ somewhere which will be lost as S-Off forces data to be reset -- but again a TWRP install of SuperSU should cover it.
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device
xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!
I want to uninstall some system apps but always getting failed or bootloop
Tried -
Titanium backup (soft bricked ) stucked at bootloader unlock warning
Root uninstaller (not working )
Es explorer with root enabled (not working) it says un-installation failed
Some more uninstallers but seems they all not working
I am currently on OOS 9.0.17
Unlocked bootloader , magisk v20.3
Can someone point me out why this is happening !!
newborn0089 said:
I want to uninstall some system apps but always getting failed or bootloop
Tried -
Titanium backup (soft bricked ) stucked at bootloader unlock warning
Root uninstaller (not working )
Es explorer with root enabled (not working) it says un-installation failed
Some more uninstallers but seems they all not working
I am currently on OOS 9.0.17
Unlocked bootloader , magisk v20.3
Can someone point me out why this is happening !!
Click to expand...
Click to collapse
Try to reinstall Magisk without avb preservation. First disable it in Magisk manager, then use install option from Magisk manager to reinstall it with this option disabled.
Report if it helped you.
Sent from my ONEPLUS A6013 using Tapatalk
DaOldMan said:
Try to reinstall Magisk without avb preservation. First disable it in Magisk manager, then use install option from Magisk manager to reinstall it with this option disabled.
Report if it helped you.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Tried without avb preservation .... Re installed from magisk manager and tried again but still same... Apps are remaining after reboot
newborn0089 said:
Tried without avb preservation .... Re installed from magisk manager and tried again but still same... Apps are remaining after reboot
Click to expand...
Click to collapse
Check in Magisk manager avb is disabled please.
Sent from my ONEPLUS A6013 using Tapatalk
DaOldMan said:
Try to reinstall Magisk without avb preservation. First disable it in Magisk manager, then use install option from Magisk manager to reinstall it with this option disabled.
Report if it helped you.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
DaOldMan said:
Check in Magisk manager avb is disabled please.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Yes it's disabled..
newborn0089 said:
Yes it's disabled..
Click to expand...
Click to collapse
Use root explorer. Go to /system/app. Rename an app from x.apk to x.apk1 then reboot. See that the app is gone and that the name is still apk1. Done.
Sent from my ONEPLUS A6013 using Tapatalk
Just thinking out loud here, if you have TWRP install why not use it at worse you my need to mount the system then go to the file manager and delete what you want just be careful...
DaOldMan said:
Use root explorer. Go to /system/app. Rename an app from x.apk to x.apk1 then reboot. See that the app is gone and that the name is still apk1. Done.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Yeah looks like good try I will try that...
lilbrat said:
Just thinking out loud here, if you have TWRP install why not use it at worse you my need to mount the system then go to the file manager and delete what you want just be careful...
Click to expand...
Click to collapse
Yeah I also thought this but seems it won't be clear description there that which app works what so needed to be careful otherwise may be system error or soft brick can heppen
newborn0089 said:
Yeah I also thought this but seems it won't be clear description there that which app works what so needed to be careful otherwise may be system error or soft brick can heppen
Click to expand...
Click to collapse
There a debloat app in the cross device section, that has 3 different levels...not really current but you can check it out , worse comes to unzip the files and see what can be deleted.. as its listed by package names..
https://forum.xda-developers.com/on...tot-debloater-basic-script-to-t3869427/page91
lilbrat said:
There a debloat app in the cross device section, that has 3 different levels...not really current bit you can check it out , worse comes to unzip the files and see what can be deleted.. as its listed by package names..
https://forum.xda-developers.com/on...tot-debloater-basic-script-to-t3869427/page91
Click to expand...
Click to collapse
Thanks I checked already tomato debloater and xxx no limits also having debloater ... So gonna try with tomato ones first bcoz it's more clear and understandable for me
But still main issue is why titanium backup and other system app removers won't be able to remove system apps even with root granted...
newborn0089 said:
I want to uninstall some system apps but always getting failed or bootloop
Tried -
Titanium backup (soft bricked ) stucked at bootloader unlock warning
Root uninstaller (not working )
Es explorer with root enabled (not working) it says un-installation failed
Some more uninstallers but seems they all not working
I am currently on OOS 9.0.17
Unlocked bootloader , magisk v20.3
Can someone point me out why this is happening !!
Click to expand...
Click to collapse
Total commander
cultofluna said:
Total commander
Click to expand...
Click to collapse
I use x-plore, also works fine. Root explorer is the least successful. Total commander is also very good, I agree.
Sent from my ONEPLUS A6013 using Tapatalk
see this thread
https://forum.xda-developers.com/oneplus-6t/help/removing-preinstalled-google-bloat-t4048075
davorq19 said:
see this thread
https://forum.xda-developers.com/oneplus-6t/help/removing-preinstalled-google-bloat-t4048075
Click to expand...
Click to collapse
thanks but used twrp method
cultofluna said:
Total commander
Click to expand...
Click to collapse
thanks... didn't tried..but lets see how its works