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.
I have cat s40 met 5.1 Lollipop. This Smartphone is success rooted by rootking.
I want have Xposed on that phone, but when i fail mod that phone how i recover back it?
Caterpillar don't released PC suite like "Samsung Smart Switch" or "Odin". Is any alternative for flash cat s40?
I don't saw any Stock ROM in internet for that phone and i don't found source code for that phone.
I don't found TWRP for that phone is released for it?
Caterpillar s40 is compatible to Xposed? someone have Xposed on that phone?
I search too good program for backup NAND and recovery before try install custom recovery.
Could you find or possibly post your stock Cat S40 rom?
Fudgehog said:
Could you find or possibly post your stock Cat S40 rom?
Click to expand...
Click to collapse
Can't no tools for do that and i don't search more because i my cat s40 send on warrianty.
Now i have formatted clean and no more root that... :/
I had bricked this phone after change root ap KingRoot to SuperSU.
This phone don't have recovery or anyother program like SmartSwitch. No TWRP.
Now i don't try mod this phone like my Samsung because i don't want again brick this phone.
OK I see. Thanks anyway.
Fudgehog said:
OK I see. Thanks anyway.
Click to expand...
Click to collapse
I think I am able to get hold of a rom!!
That would be great but..
I have the S50 and there are still no custom recoveries for either that I'm aware of.
someone has problems with the touch?
cangrejon said:
someone has problems with the touch?
Click to expand...
Click to collapse
Double posting, duh!
Click here.
Source Code S40 + Recovery Mode
Source code cat s40
http://www.catphones.com/en-gb/legal/general-terms-and-conditions
but we don't have access to file for now lol
Cat S40 Source Code
but Cat B15Q can download normally.
Cat B15Q Source Code
i found too how enter Recovery Mode maybe isn't it CWM or TWRP but better that than nothing
1. PowerOff phone
2. Connect USB cable to phone
3. Press and hold the Vol +
4. Connect USB cable to PC or Power Supply
5. Recovery Mode!
I hope after we can download source code someone can make TWRP of custom ROM for us ;]
Cat s40 SuperSU + Xposed
I have SUCCESS ROOT + SuperSU + Xposed on my Cat s40 :]
1. Kingroot root
2. install "SuperSU_v2.65.apk" ( i installed it by Lucky Patcher as System app)
3. Reboot
4. use script "switch_armv7.sh" i added script i found that on XDA forum but i don't remember where.
If script don't work you can try again gain root by kingroot and in SuperSU update supersu binary ( SuperSU can detect Kingroot so you must uninstall it) This script worked for my Cat s40 fine.
5. After script install new binary in SuperSU app
6. SuperSU succes!
7. FlashFire flash Xposed Binary ( i added too Xposed binary)
7. Reboot ( boot is longer than normal)
8. You have SuperSU root and Xposed Framawork on your Cat s40
You can too by FlashFire make backup your system partition and use it in TWRP if someone do it for us... or flash it after gain SuperSU root ( FlashFire on Kingroot don't working)
You do it at your own risk!
First i tried that method on myPhone Infinity LTE ( i can that flash by computer when it bricked )
I think it can work on all Android 5.1 lollipop.
Wirusx, thanks for the feedback.
Can i get more detail and confirmation :
First use kingroot 4.9.3 found here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After that it's rooted, and then you install the script in supersubinary.rar . But can you explain in detail to put what file where on the S40, or do we only need to install the superuser.apk file?
Is xposed framework nessesary found here: http://forum.xda-developers.com/showthread.php?t=3034811
How about use uptodate kingroot and after that supersumepro ?
Rooted Cat S40 running 5.1 Lollipop
After several attempts and reboots all ok. Caterpillar Cat S40 running Lollipop 5.1 working fine.
1st thanks to all devs. (VickyB, MrW0lf, Chainfire etc). :good:
Then. My attempt consisted from pointers or several threads. Started with Wirusx and got something else from somewhere else. I try getting a whole picture here.
(I did not look for fresh look, but better battery consuption, better security and such. So no new roms etc needed. Cat is quite plain and sleek anyway.)
Basically it was of Wirusx instructions, but with some tweaks as apparently at this stage some update has tightened Cat OS that fewer exploits work.
Several files has be in phone (internal storage worked for me, sdcard not). One app from Gplay (Terminal Emulator) and ->
see this thread: http://forum.xda-developers.com/android/apps-games/replace-kingroot-supersu-t3339950
1. Kingoroot - 2. Reboot - 3. Run Script (which will give you also SuperUser app). - 4. Reeboot - 5. Updated Superuser and another reboot.
- Done.
There were some moments when not all ok. After 3, verified through Emulator who is "in charge". "su -v" in same directory as you ran the original script. Showed SuperUser 2.65, so all ok. But apps listed listed KingoRoot/Purify. But not SuperUser, although the root was through it. I had to download it again via Play. After 5 all ok "in Wonderland".
Some pointers from unknown threads (which I failed to find again). Apparently the situation was like the following exerpt shows.
"It seems that the script doesn't work the same way on every device. For me, it just deleted Kingroot,
and left me with just a temporary root terminal, . SuperSU was never launched nor installed,
and when I installed it I got a "There are no su binaries installed".
I did the following to install SuperSU:
1. Run the script for your proper architecture.
2. If it doesn't launch SuperSU at the end or even worse, if you install it but get the
" no su binaries", DON'T close the last root terminal.
3. Run
su -v
If it returns something like SUPERSU-2.65 you're good to go. If it doesn't,
re-run the script again in order to push the proper su binary again.
4. Go to the terminal and type:
mount -o rw,remount /system
chmod 7777 /system/xbin/su
chmod 7777 /system/xbin/daemonsu
Note: at this point SuperSU will start to work, even if you didn't update its binaries.
4. Open SuperSU. It'll ask you to update its binaries, press yes.
5. Since it's highly advised to have SuperSU in /system in order to preserve root access
through updates, you just gotta move the SuperSU.apk included in the zip to /system /app and
chmod it with 0755 permissions.
I downloaded SuperSu from Play and it worked.
Rooted Cat S40 firmware update
Hi!
Is it possible (ad if yes, how) to update the firmware of a rooted Cat S40. My rooting process was the previously mentioned Kingroot -> SU, but after this the OTA update does't finish, even with FlashFire.
jeroensky said:
Wirusx, thanks for the feedback.
Can i get more detail and confirmation :
First use kingroot 4.9.3 found here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After that it's rooted, and then you install the script in supersubinary.rar . But can you explain in detail to put what file where on the S40, or do we only need to install the superuser.apk file?
Is xposed framework nessesary found here: http://forum.xda-developers.com/showthread.php?t=3034811
How about use uptodate kingroot and after that supersumepro ?
Click to expand...
Click to collapse
supersumepro = android frezze on boot = send phone for warrianty ;/
pliz share
anyone else succeeded in rooting?
After contacting CAT and bullet-group they managed to fix their "Open Source Codes" section and add links. Sadly, no actual response
(*sigh* can't add links)