With all major changes to SuperSU, there are updates to both the GUI and binary. The GUI is the part you see on screen, the binary is what allows other apps to actually acquire root access. The first time you open SuperSU after such an update, it will attempt to update the binary to the latest version.
There are a lot of components to the binary and it needs to be set up just right for everything to work. This is a complex operation, and sometimes it fails. SuperSU is used by dozens of millions of users across hundreds of different devices, running even more different firmware revisions - any change always has the potential to break something somewhere.
SuperSU offers multiple ways of installation: in-app 'normal', in-app TWRP/CWM, and ZIP via TWRP/CWM. These all have their own strengths and weaknesses, so if one doesn't work, try the others if available.
If you are reporting an update failure, you should include at least the following information. Some information requires some skill with adb to retrieve.
- Exact device model
This includes the brand, the model, and the carrier variant (if applicable: mostly USA, Korea, China)
- Exact firmware version
Which exact firmware are you using? If you are using a custom firmware, please include a link to the download for this firmware. If on top of that, you are also using a custom kernel, please include a link to the download for that as well.
- Exact Android version
Android x.y
- Exact SuperSU version
Which version were you running, and to which version are you updating? If using Pro, do you have OTA survival mode enabled?
- Interfering apps
There are some apps that can interfere with SuperSU installation, primarily:
- other Superusery apps
- Xposed
- BusyBox (symlinked or non-symlinked)
Include in your report if you have one or more of these installed.
- Update methods tried
In-app 'normal', in-app via recovery, and ZIP via recovery. If you used one of the recovery options, please include exactly which version of which recovery you are using, and if it's not an official build (so a TWRP not from the TeamWin website, a CWM not from CWM's site, etc) a link to where you got it from.
Note that if you let TWRP or CWM "fix" root for you, or let them disable the firmware from flashing a new recovery (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
- What kind of root are you left with?
After a failed binary update, multiple outcomes are possible:
- Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc
- Root seems to mostly still work. Most apps still work, and/or "su" still works from an adb shell
- Nothing seems to have changed at all, even the GUI still shows the old version number
Report what state your device is in now. Note that you can get the version of the main "su" binary by running "su -v" from a terminal emulator or adb shell.
- Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app
After pressing the TWRP/CWM button, the device should reboot into TWRP, do it's thing for a few seconds, then reboot into Android. If SuperSU still complains about the binary, please retrieve the TWRP log file. You can retrieve it via adb pull /cache/recovery/last_log, which should produce the last_log file in your current directory. You still need at least partial root from booted Android to retrieve this log. Sadly it is wiped and replaced with a new file when you boot into recovery a second time, so you cannot retrieve it that way. Note that this log will always contain a number of errors, as the installer tries several things in several ways, that work differently on different firmwares. Attach this log file.
- Logs from TWRP, when updating SuperSU completely via ZIP
If after you boot back into Android, SuperSU is not working right or still asks for updated binaries, reboot back into TWRP, install the ZIP again. After the ZIP is installed, you can retrieve the log file via adb pull /tmp/recovery.log, which should produce the recovery.log file in your current directory. Attach this log file.
- Logs from SuperSU (very important)
If SuperSU keeps asking you to update the binaries after trying any which way and failing, please post the detection log. After updating has failed, don't reboot, but produce detection information via adb logcat -d | find /i "installer" > logcat.txt (Windows, use 'grep -i' instead of 'find /i' on Linux or OSX), which should produce a logcat.txt file in your current directory with several lines mentioning SuperSU. Attach this log file.
- Various logs (very important)
Some additional handy information can be gotten by via some adb shell calls. If you that working, copy/pasting the following commands should produce a nice sulog.txt file in your current directory, which you should attach to your post:
(as always with copy/pasting, make sure you press enter a few times afterwards to make sure the last line was flushed)
Code:
adb shell getprop > sulog.txt
adb shell set >> sulog.txt
adb shell toolbox id >> sulog.txt
adb shell busybox >> sulog.txt
adb shell su -v >> sulog.txt
adb shell su -V >> sulog.txt
adb shell su -h >> sulog.txt
adb shell su --self-test >> sulog.txt
adb shell ls -l /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/bin/toolbox >> sulog.txt
adb shell ls -l /system/bin >> sulog.txt
adb shell ls -l /system/xbin >> sulog.txt
adb shell ls -laR /su >> sulog.txt
adb shell ps >> sulog.txt
In closing
All this information will help diagnose the problem, and potentially help fix the issue if there is something wrong with SuperSU itself (which is not unheard of). The more information you provide, the better you can be helped. Still, be aware that often it takes a while to get a problem sorted. Even when a lot of people are having the same problem (and many problems may look the same but deep down are separate issues), it is rare to find a user who actively wants to help fix the issue. Most users will only complain but then don't really assist in solving the issue. If you can be someone who can actively help, and by that I mean being responsive to questions, being available for a live debugging session, etc, you are a rare gem indeed, and your assistance will be greatly appreciated.
If you are writing multiple posts, it is always helpful if you keep linking back to your original post with the report. Saves me time.
Sorry for the inconvenience!
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Update has make my Galaxy S5 is unusable...
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
shadow322 said:
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Click to expand...
Click to collapse
As stated on IRC, I'm going to need the logs described above.
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Chainfire said:
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Click to expand...
Click to collapse
I've done a factory reset & stoll have the same problem. How would I restore data?
Emmie0702 said:
I've done a factory reset & stoll have the same problem. How would I restore data?
Click to expand...
Click to collapse
You would restore the data from a backup you've made before resetting ?
In SuperSU you can try 'full unroot' from Settings (twice if necessary) and unroot, see if that resolves the slowness/crashing.
The only backup I have is a titanium backup. I can't get anything to download from the play store. I never flashes recovery because it wasn't available when I rooted. I never went back to add it (which I could kick myself for right now). Would re rooting help? Supersu isn't on my phone anymore either. I'm not sure what happened to that.
Edit: could the platform.xml under /etc/permissions/platform.x ml have anything to do with it?
Knox
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
@Emmie0702 I think it's a weird Knox Action -i mean, It MAY happen 'coz Knox
Chainfire said:
Note that if you let CWM "fix" root for you (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
Click to expand...
Click to collapse
CWM is asking for that. I have to answer Yes or No. So I should click No ?
sorry wrong thread
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
p220fhf said:
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
Click to expand...
Click to collapse
You can give it a shot, rerooting via the ZIP ( http://download.chainfire.eu/supersu ) with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
SuperSU Problem!
I've rooted my device (GT-1335 - Android 4.4) with Windershare Rooting Toolkit, After rooting I've installed Root checker basic from the market and run it. It says your device is rooted. But when i wanted to go to root using FX explorer, it says you need permission from Advance user. When i click SuperSU after that it says that "There is no Su binary installed, and SuperSu cannot install it. This is a problem!", After that i checked whether my device is rooted or not with Root checker basic, but now its says that my device isn't rooted!
Please Help, and replay soon!
Note: My device isn't original samsung model!
super su still loading
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
I had problems with using Stock 4.4.4 on my i9305.
Was freezing/not opening, then when it did it wouldn't update.
So I went to the SuperSu site and downloaded the latest to instal via CWM.
Now working fine. Hope this helps someone.
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
SuperSU 2.14 not working on s4 4.3
gokunjp said:
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
Click to expand...
Click to collapse
same problem here on my S4-quad-16G with samsung 4.3-stock, which was rooted mothns ago via AutoROOT+twrp2.7.01
p220fhf said:
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
Click to expand...
Click to collapse
same here update 2.14 from PlayStore f.cked-up the SuperSU app (i have waiting-donut on APPS and LOGS-tabs...)
Device stays rooted, and root-requests from other apps seems to work too, because there is a typical SuperSU-reuqest popup there....
So please fix the APP for Samsung 4.3 4.4 firmwares...
Versions 2.01+2.06 worked flawlessly.
what i have already tryed:
1) On the [Settings]-TAB: => UNINSTALL APP: Effect 'uninstalling...'-popup stays 4ever w/o effect
2) On the [Settings]-TAB: => UNINSTALL APP for a NEW SuperUserApp: Effect 'uninstalling...'-popup stays 4ever w/o effect
3) Booted into TWRP => INSTALL the SuperSU-2.14.ZIP, rebooting phone -> in SuperSU (the same waiting donuts on APPS/LOGS...)
Phone: i9505-OpenEUROPE quad-core/16G Samsung-stock-FW 4.3
Device I9505
Android Version: Stock 4.3 MKF
BusyBox v1.22.1
Wanam Xposed installed
Stock Recovery
Kingo Root
Google Play Update
Issue: After update from 2.13 to the latest 2.14 when supersu try to reinstall it stuck more than 5 minutes, I reboot my phone, reopen supersu but now in my "APPS" and "LOGS" I have some kind of neverending loop load, I can't manage to see my rooted apps there, and in my SETTINGS if I try to make some changes it stuck and need phone reboot, otherwise all my rooted apps work fine!
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I think i figure out the problem, is the SU bin update. My note 2 is rooted and is using SU 2.14 pro, but i don't update the bin. It works fine, but when opening the su app, it asks you to update the bin.
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?
dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.
Hi,
First, I'm a noob with some experience!
I know how to root my phone with Magisk and I helped Jen to root the LG G4 Vigor (H731) for Videotron/Telus. She was working on the H735 if I'm not mistaken but it worked for mine too since it's the same phone without the same name. It was with SuperSu, I don't think Magisk was out at this time.
Well... at that time I bought Busybox Pro... I don't know why except everyone had it!!
I'd really like some explanation. I searched for at least 4 days, 1-4 hours per day and it was a LOTS of different things! I'm really confused about the difference between Busybox and Magisk, expect Magisk is SystemLess.
I can install "add-ons" with Magisk like Xposed!!
I really don't know what I can do with Busybox except installing "things" but are those "things" are like a module in Magisk/Xposed?
P.S. I know that if I install Xposed in Magisk, it become systemless like Magisk!
And! I know that I can install Busybox from Magisk! But I bought the Busybox Pro app from Google Play Store.
Can someone tell me all those differences? I'm really messed up and really need help +++ I think a good explanation could help lots of others than me.
Thank you VERY much!!!
Busybox is just a set of tools that some apps/programs/processes/etc use. Magisk actually has its own internal Busybox that it uses for a lot of things, but it's not exposed to the rest of your system, which is why you need to install a separate Busybox if something about your setup needs it. It used to be more common that a separate Busybox installation was needed, but nowadays not so much, since most apps that need it already come with their own version of it to ensure compatibility. You can read more about what Busybox is at https://www.busybox.net.
I actually had the same question. I've rooted a few of my devices already. And years back I've also bought some apps via Play-Store. But a lot of these apps seems to be dated and not maintained annymore.
For instance I've bought a few apps from JRummy back then, from which I still use Busybox and Rootchecker nowadays. But this bussybox seemed to be quite dated when looking to the last update moment.
I'm using Magisk now and I was thinking going to use it's integrated Busybox too. Can it just work next to each other? Or do I need to unstall the JRummy Bussybox before?
Didgeridoohan said:
Busybox is just a set of tools that some apps/programs/processes/etc use. Magisk actually has its own internal Busybox that it uses for a lot of things, but it's not exposed to the rest of your system, which is why you need to install a separate Busybox if something about your setup needs it. It used to be more common that a separate Busybox installation was needed, but nowadays not so much, since most apps that need it already come with their own version of it to ensure compatibility. You can read more about what Busybox is at https://www.busybox.net.
Click to expand...
Click to collapse
You can activate and use busybox by typing or copy and paste the busybox magisk location. Such as
/data/adb/magisk/busybox xz -d /storage/emulated/0/Download/root.img.xz
This is the busybox command to decompress xz archive.. as long as your root with busybox no need to install unless an application requires it.