yashsingh1/xdaforums huggingface dataset:
[SuperSU] giacomociani:
Possible bug: SuperSU causing reboot if superuser binaries not updated

Hi,

I just spend one day figuring out an issue with my girlfriend's phone continuously rebooting. I now have strong evidence that it is due to SuperSU, and wanted to share my experience in case it's useful to someone else (or it points to a bug)

This is what happened: around june 22nd, she rebooted the phone, that she doesn't do very often, and hadn't done in a few days (see "hypothesys" at the end for why I think dates are important here). Upon reboot, the phone seemed to act normally, got to the unlock screen but then suddenly rebooted after just a few seconds and started all over again, rebooting spontaneously after 3-4 seconds from displaying the lock screen. In these few seconds, the phone could be unlocked and appeared to be functional, although it hadn't fully completed the boot process (not all widgets loaded, etc...). There was no way of stopping the reboot if not by letting the battery drain, or rebooting in recovery and powering off from there.

We were on travel and I had no time nor resources to debug the problem, which I did yesterday. After backing up important data from ADB and factory resetting the phone, the problem seemed to be gone. However, after letting google Play update all the apps, the problem will appear again (note that the problem will only appear on the next reboot after updating: if you don't reboot the phone, it will act normally even after the updates are done).

I then re-reset the phone and started selectively updating apps, and was able to single out SuperSU as the cause of the strange behavior. If I didn't update SuperSU, the phone will act normally.

Here is last piece of the puzzle: after updating all the apps and veryfing that the phone was working normally, I did update SuperSU and lunched it before rebooting. When started, SuperSU asked me to update the superuser binary by rebooting into recovery, which I did. Problem gone! Now SuperSU is updated and the phone works correctly.

Hypothesis (more of a guess...):

- on June 18th (latest release before the problem appeared) SuperSU updated in background from the market, but my girlfriend never started it, so the superuser binary never got updated

- a few days later, she rebooted the phone

- the new superSU version, finding the old superuser binaries, would cause the phone to reboot at some point (pretty late) in the boot process

- if she had started SuperSU before rebooting the phone, it would have prompted to update the binaries and maybe the problem would never have appeared

Does all this make sense?

Giacomo
[SuperSU] Strephon Alkhalikoi:
Will Terminal Emulator work or is there something specific that the ADB output provides that the Terminal Emulator output doesn't?

Standard shell:

ANDROID_ROOT=/system
EXTERNAL_STORAGE_UDISK=/mnt/usbdisk
LD_LIBRARY_PATH=/vendor/lib:/system/lib
HOME=/data/data/jackpal.androidterm/app_HOME
PATH=/system/bin:/system/xbin
LOOP_MOUNTPOINT=/mnt/obb
ASEC_MOUNTPOINT=/mnt/asec
DOWNLOAD_CACHE=/cache/download
ANDROID_SOCKET_zygote=9
TERM=screen
ANDROID_CACHE=/cache
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
ANDROID_BOOTLOGO=1
ANDROID_ASSETS=/system/app
EXTERNAL_STORAGE=/mnt/sdcard
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=8,32768

With SU access:

ANDROID_ROOT=/system
EXTERNAL_STORAGE_UDISK=/mnt/usbdisk
LD_LIBRARY_PATH=/vendor/lib:/system/lib
HOME=/
PATH=/system/bin:/system/xbin
LOOP_MOUNTPOINT=/mnt/obb
ASEC_MOUNTPOINT=/mnt/asec
DOWNLOAD_CACHE=/cache/download
ANDROID_SOCKET_zygote=9
TERM=screen
ANDROID_CACHE=/cache
USER=root
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
ANDROID_BOOTLOGO=1
ANDROID_ASSETS=/system/app
LOGNAME=root
SHELL=/system/bin/sh
EXTERNAL_STORAGE=/mnt/sdcard
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=8,32768
[SuperSU] apitnauli:
Can I flash update-supersu-vx.x.zip via HTC unlocked boot loader stock recovery?
[SuperSU] bgs_piece:
I have a Note 3 on 4.4.2 and with the newest update the binary can't be updated. I do not have CWM or TWRP recovery so I select normal when asked to update the binary. I then reboot and try again and no luck. Any suggestions?

edit: For some reason, sometimes after rebooting when I open the app everything is fine. It doesn't tell me to update binary. Other times it flashed the message the supersu has restored superuser permissions and when I open the Supersu app it says binary needs updating and then tells me it failed after trying to update. This only started after the phone was updated to 4.4.2 from 4.3.
[SuperSU] dragid10:
Hey i have an issue. I've set the option to auto grant superuser requests with re-authentication turned off, but i'm still gettings prompted to grant root . I have no idea why
[SuperSU] Rinoceros:
@giacomociani

Nice story, but without phone brand, model, OS-version and logcat is this just stumbling in the dark. You have to provide much, much more details for Chainfire (if he ever wants to have a look at it at all!).
[SuperSU] Chainfire:
SuperSU's auto-update feature tries to write to /system, and your device reboots when a /system write is attempted. The only solutions are indeed quickly opening the app and manually updating the binary, or updating via recovery in the first place.

Don't see any differences here that would matter...

Are you using some sort of modified kernel? Seems to me like the binary gets replaced each boot.
[SuperSU] andrei1015:
I can't even install the backup script :(
[SuperSU] Chainfire:
I have seen this once - I would love to be able to reliably reproduce this so I can fix it ...
[SuperSU] andrei1015:
Please tell me how I can help you. Do you have a nexus s at hand? Logs, screenshots, etc.?

Flowed from Nexus S
[SuperSU] Frank Westlake:
Does SuperSU use the word "superuser"? Could it be a problem having both installed?

Frank
[SuperSU] Chainfire:
Unfortunately I have no idea aside from live debugging, which is why I need to be able to reproduce. I don't have a Nexus S either. Did try the latest CM nightly on my S3, worked fine there.
[SuperSU] bgs_piece:
I downloaded the OTA and used supersu to keep root. After that, I used odin to flash a new radio/modem because the original one had bad reception. It was after flashing the new radio these issues began. I didn't think it would cause problems because I had done that before and didn't have issues.
[SuperSU] mrjeancw:
weirdest thing...using the supersu that came in with cf auto root...all went smooth and when i click on supersu in my apps it says "unfortunately super su has stopped working". i cant uninstall it either.
[SuperSU] sancho_panzer:
Hi guys. I'm on CyanogenMod M8 (4.4.4) with SuperSU 2.00. May I presume from the OP it's not necessary update to 2.01 because are just pinpoint details to Android L? Could this update have any significant impact (for better) on my system?

Sent from my GT-I9505
[SuperSU] Chainfire:
logcat
[SuperSU] simonbigwave:
i am on CM 707 (4.4.4) nightly (which is not far from ur M8 release date) , for me both SuperSU worked just as fine and stable on 9505 for me. AFAIK you should b ok on 2.00 as is already good, so I wouldn't worry about it too much unless you wanted jus to test 2.01.
[SuperSU] donshaffer:
[MENTION=631273]Chainfire[/MENTION]

I have a Samsung tab 10.1 and am on 4.4.2 KK. I am using multi user with me as the primary user and my daughter is secondary user. Have superSU 2.00 pro installed on both but having a small issue, not sure if it is a root problem though. Our music is on the internal sdcard. I can access it, but the file is empty on her profile. Is there a way to make it visible for her as well? If this is not the place for this, I apologize. Just point me in the right direction please.
[SuperSU] 78Staff:
v2.01 is fine on M8 fwiw... I'm about to update to latest nighly as well.
[SuperSU] giacomociani:
Hi Chainfire,

I understand your explanation, but there is a caveat: the problem does not appear when SuperSU is updated, but on the next reboot. So, I deduce that SuperSU tries to write on /system (presumably to update the superuser binaries) only at the next reboot after it has been updated from the market? If this is the case, I would suggest either of this two "fixes" (although I have no idea if any of either one is practically feasible):

SuperSU updates the superuser binaries when it is updated, and not upon the next reboot, even if the user doesn't start it, or

when SuperSU is updated from the market, it displays a notification that warns the user to open SuperSU and update the superuser binaries _before_ rebooting the device.

Would any of this be possible? It would avoid some inconvenient situation... even now that I know where the problem is, if it happens again I doubt I would have enough time to open the app and update the binaries before the phone reboots; I would have to go via recovery... that is not that bad, I agree... just not as easy as starting SuperSU and agreeing to update the binaries! :D).

Let me know if you need any specific info about my device (for whatever reason), as suggested by Rinoceros.

Thanks

Giacomo
[SuperSU] vinylmeister:
Can i use this without any misbehaviour on paranoid android which has already superuser in it?
[SuperSU] radzik2908:
Yes Sir.
[SuperSU] Olivier_V:
Hi,

I have a problem with Android 4.3 on Galaxy S3 i9305 4G/LTE : when I reboot the root is lost.

I asked here : http://xdaforums.com/galaxy-s3/help-i9305/loosing-root-reboot-android-4-3-t2813568 and the solution given is to uninstall SuperSU, reinstall SuperSU and reboot ...

So I think there is a bug with SuperSU and this version of Android.

If possible could you look at this bug.

Thanks.
[SuperSU] zezoassiri:
The root dosen't work if I change the language from English.

why is that happening? ?

what is the relationship between the root and English language ???
[SuperSU] bweN diorD:
just trying to help another user out here, please help if you can.

original question/problem below.

thanks
[SuperSU] egingell:
The pin file is stored in the /system dir, so if you have an OS that restores the /system partition, such as HTC's Sense, then the pin file will disappear on reboot.

Edit: Add

If I'm right, you can try this:

1) Set a pin.

2) Move the newly created pin file from /system/.pin to /data/.pin

3) Reboot into recovery and connect to adb.

4) Make a symlink.

adb remount

adb shell su -c ln -s /data/.pin /system/.pin

5) Reboot.

*) You might need to mount either /system, /data, or both. I can help you with that if you post the contents of /proc/mounts while the phone is in normal mode.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] dnlilas:
Hello,

I have Kitkat 4.4.2.

Either by rooting (installing SuperSU) from within recovery TWRP 2.7.1.0 Kitkat version, or after

replacing vroot/kingo root with SuperSU, Titanium Backup although got root access is not functional

(hang during backup/restore operation)!

Are there missing rights for Titanium Backup under Kitkat?

Thank you for your explanations.
[SuperSU] polobunny:
No, I'm using Titanium Backup daily on Kitkat 4.4.4 with SuperSU v2.01 and everything works.
[SuperSU] _jis_:
Including Protect this backup?

;)
[SuperSU] dnlilas:
Thanks to your answer, now I have a guess. Probably the problem is to use backup data made from 4.2.2

to restore after upgrading to 4.4.2. Some user applications are not 4.4.x-aware so their data could not be restored

causing Titanium backup to hang. If I remake all backups from 4.4.2 from scratch, it should work.

Anyhow SDFix would be useful (to check) for other application like Total Commander since it could access /sdcard0

but not /sdcard1 after switching Kinguser with SuperSU. So Kinguser probably adds some more permissions dynamically.
[SuperSU] polobunny:
No. (I believe that function is broken though)
[SuperSU] _jis_:
You know, I asked you intentionally :).

No, it isn't broken, it just doesn't work under 4.4.x as a lot of other things (thank you Google) and BTW it is a very useful functionality. Here is how I solved this problem:

On my Samsung Galaxy W with CM11 4.4.4 I couldn't protect backup archive in Titanium Backup Pro. I read this thread: [Help] Titanium Backup PRO - protected archive not working.

So I modified file /system/etc/permissions/platform.xml according http://jrummy-apps.com/fix-sdcard-on-kitkat/ and make new file /data/local/userinit.sh with this content:

#!/system/bin/sh

busybox mount -o remount,rw /
chmod 770 /mnt/media_rw

You should have move your TiB backup folder to /mnt/media_rw/sdcard1/TitaniumBackup

Now I have no external card write issues anymore.
[SuperSU] polobunny:
So that problem isn't related neither to SuperSU or TitaniumBackup, non surprisingly. It's a matter of changing SD card permissions in KK, which you can do in many different ways (including yours). I'm sure some could find the tip useful.

Either way, enough polluting of SuperSU thread. :)
[SuperSU] Pkt_Lnt:
Or this, if you use Xposed.

http://repo.xposed.info/module/kz.virtex.android.sdcardfix
[SuperSU] xdafly:
Hello

Just received new SG4 Active phones, stock ATT SGH i537 with Android 4.3 I537UCUBML2

my problem is that these phones fail ATT update to 4.4 from 4.3

I thought phones were unrooted from online vendor but today I found SuperSU installed

when I access it, a message pops up ".... SuperSU ... Samsung KNOX has been detected. This might limjit root capabilities and cause annoying popups. Try to disable KNOX ? " (options are Cancel and OK)

on the top are choices for ADB shell, APPS, LOGS, SETTINGS

in settings, SuperSU v1.91 Chainfire, Enable Superuser is checked and Re-Authentication is checked (ask for permission again if an app is reinstalled or upgraded)

Now I wonder if this is the reason the stock ATT OS System Update to Android 4.4 is failing, it downloads the 444 MB file, reboots, starts Installing and stops with Install failed at 29 percent
[SuperSU] remo0073:
If you have root you can't make OTA update. Maybe you should flash new firmware using Odin.

Ask in your device section
[SuperSU] Olivier_V:
Up ...

No idea for this problem of lost root after each rebooting on Galaxy S3 i9305 ?

I would have a better solution than uninstall and reinstall SuperSU after each reboot ...

Thanks
[SuperSU] _jis_:
Unfortunately, this module doesn't help if you couldn't protect backup archive in Titanium Backup Pro. I just tested it and returned to my method.
[SuperSU] MikeRL100:
As for those types of programs, and the topic of antipiracy from a developer standpoint (not myself but from experiences others have dealt with) as much as Chainfire would surely prefer you buy pro, if someone cracked the app with such tools, why should be bother placing in antipiracy tools? It's an endless headache of a fight to implement antipiracy measures, and on any one man team it's too much work to be worthwhile. I've talked with developers dealing with headaches caused by apps and some developers will fix bugs introduced by warez, just for the sake of completion. I don't know why piracy is completely banned to be mentioned on XDA, and no I don't mean posting cracked stuff, I mean constructive discussion for developers, I may need to brush up on the massive list of rules. I'm going to have a little constructive talk on this. A developer of a certain root app made a patch a while back to deal with odex files created by the aforementioned piracy app. Just for the sake of stopping users from complaining. Next time anyone pirates anything, think about what damage you're doing. Essentially all of the apps worth installing that cost money are done by one man teams. So don't steal their income. Especially considering when they now have time wasted by dealing with warez. Why should Chainfire embrace antipiracy in SuperSu? I'd say it's too much work for him and also he has a checkbox to unlock all pro features legit without paying. So why pirate it? He's doing pirates a favor in fact. If you're not gonna pay just check that box, no need to install dubious APKs with Lord knows what modified. IMHO he and other developers help pirates too much. No need for antipiracy. People just get around that, anyhow. I'd rather live in a world without DRM and crap where people respect hard work and pay for it. Just think of how much nicer stuff would be. End massive rant.
[SuperSU] RBucci:
Hi all, got a Galaxy S 5 G900H and I'm unable to root the phone entirely (it roots but it doesn't fully root it). I have tried every possible steps (fully wiped the phone, installed CF-AUTOROOT for my version) to no avail.. Is there something I might be missing?

It's like a partial root and I've tried 4 or 5 times now..
[SuperSU] biustech:
hi i got a lg g3 last week and i've been installing all my stuff into my new device and then i checked wakelock detector and saw this.

not sure what is causing. i've search the thread, forum and google it but couldn't find any definitive solution...
[SuperSU] RBucci:
Everybody jumps against hacked/cracked apps but nobody wants to help a brother properly root his phone?

I'm going crazy with this thing.. Please help..
[SuperSU] egingell:
There's plenty of help for rooting your phone. Chances are high that there's a forum on XDA specifically for your phone.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] SecUpwN:
I can very much recommend the official XDA Developers Root Directory. A great place with all needed ressources!
[SuperSU] RBucci:
Much obliged! Sorry for the aggressiveness..
[SuperSU] SecUpwN:
No problem. You can make your Karma positive again when pressing the button below my post to support the XDA thread of our App being featured. :cowboy: And if you're really wanting to make a change this world to fight for our Privacy, check out the Android IMSI-Catcher Detector (AIMSICD). Thank you!
[SuperSU] sushidog:
I guess you don't know the 15th rule on Xda.

Sent from my GT-I9505

---------- Post added at 11:29 PM ---------- Previous post was at 11:17 PM ----------

Did you followed this steps? http://www.howtoroot.mobi/2014/04/root-galaxy-s5-sm-g900h-with-easy.html

I don't have an S5 but these steps are quiet familiar to what I've done on my S4.

Sent from my GT-I9505
[SuperSU] RBucci:
I have, yes. That one, the vroot, the SuperSU but none worked..

Is there a manual way to install SU on Android??

I'm guessing it's complicated as performing an heart surgery in a bouncing jeep but I'm willing to give it a try..
[SuperSU] SecUpwN:
Link to it if it makes you feel better.

Do you actually get ny error messages? Please describe as best as you can what you did, including logs!
[SuperSU] RBucci:
No error messages at all. I'm reflashing G900HXXU1ANCI_G900HOJV1ANCH_G900HXXU1ANCI_HOME.tar.md5 Stock Firmware because the one I changed to started messing around with my modem.

The only partial root result I find is that when I attempt to run Titanium Backup or memory viewer like Game Hacker (just an example) and it states that it still needs root access. When I run Root Checker Pro it says root is not properly configured.

As soon as I'm done with the flashing, I will post all the updates as I re-root for the eleventh time haha..
[SuperSU] Elveneleven:
Hi,

Today i had a Root Request from SuperSU (UID) which i rejected for now.

does anyone know what this is for and if i can or should allow it?

System is rooted Stock I9300XXELL4 (Jellybean 4.1.2)

Thanks for the help.
[SuperSU] Pons:
You got a root request from SuperSU and want to know what SuperSU is? Read the OP of this thread.
[SuperSU] egingell:
Looks to me like he wants to know why SuperSU is asking for root not what SuperSU is.

Edit: I know it's ambiguously worded, but that's what I got from it. :)

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Elveneleven:
You're right. That's what I wanted to know. Why is SuperSU (UID) requesting Root access and why is there this UID amendment? I never had that before.
[SuperSU] grant2:
blarg wrote in wrong thread, sorry
[SuperSU] SecUpwN:
Are you sure SuperSU is your only Superuser App? Re-check if you also have another Superuser-App integrated (as can happen with CM) and uninstall that one then. Most convenient thing is to flash SuperSU through recovery when you do a fresh install of your ROM.
[SuperSU] Elveneleven:
Yes it's the only one. No other Superuser App. And it was installed with CF-ROOT when Rooting the phone. Im on Stock Rom.
[SuperSU] egingell:
I've been experimenting and, based on observation, I think the problem is that you have an app (most likely Greenify) that keeps asking for root and getting denied (e.g. the dialog times out).

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] biustech:
I thought this at the beginning, but i installed a custom rom and then only few apps (not greenify) and still had the wakelocks. But thanks for investigate this issue. i think my problem is now under control i don't now exactly what i did besides install busybox. i'll keep eyes on this and report if anything changes.
[SuperSU] mdiaz33685:
Im not sure on the S5, but on my cousin's S4 and all other phones,,

if u already used cfroot... well that would be one of the 1st steps...

but what I do 1st is Odin a recovery, usually TWRP, then I flash SU, try using SU version 2.00 then when u get back to the phone after the restart, if u don't already have it, from the playstore download busybox, from steriscon. :good:
[SuperSU] RBucci:
I did, bro. Just that I have this weird half root thing. It installs in xbin/su but it's not propperly configured. Rather, it does not install in the proper folders (sbin - system/bin).

Some weird thing.

I never had problems installing Root on ANY device (Galaxy S2, Galaxy S3, Galaxy S4 I9505) but this one seems to be a headache for Chainfire.
[SuperSU] mdiaz33685:
I believe I seen u mention u had the ATT model, lucky for u if so, ATT has been making it harder for u guys... :eek:

AT&T Samsung Galaxy S 5 > AT&T Galaxy S5 Android Development > [RECOVERY LOCKED/ND3] Safestrap Recovery v3.75 [2014-06-26 B03]

http://xdaforums.com/showthread.php?t=2794087

try reading this, not sure but it might be your problem...
[SuperSU] SecUpwN:
Uncool. Why don't you try another awesome ROM? I strongly recommend giving AOKP a shot.
[SuperSU] RBucci:
Is the G900H Equinox a AT&T model? I'm currently in Paraguay. Not sure if this phone crash landed here and I just so happen to buy it lol.. I gave it a glance and it kind of makes sense.. Although it's really simple enough, they haven't given much thought to the "security" of their software..

I'll be testing it out, [MENTION=4686037]SecUpwN[/MENTION]. Thanks!

No pun intended with the headache part though :)
[SuperSU] revolt1:
how do i stop the yes root xbin su issue

when ever i do a back up using cwr
[SuperSU] CHEF-KOCH:
Can someone explain me why the log gave me this:

SU BINARY IS NOT RUNNING AS "u:r:init:s0" - THIS WILL CAUSE ISSUES

Su seems to work fine, but this the only error that is shown. I'm on 4.4.4 with slim Rom i9100 as single user with dorimanx kernel (app not installed as /system/).
[SuperSU] bovirus:
I installed SuperSU via recoivery with update.zip posted on first post.

When I run SupeSU app, it showed version 1.86 (not 2.01). What's the matter?

I checked that in /system/app/ the app is the latest version.
[SuperSU] aavvaallooss:
Install from here using custom recovery

http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip
[SuperSU] bovirus:
As I explained it's the file that I installed via recovery (the link is in the first post).

But when you ran the app it show SuperSU v. 1.86.
[SuperSU] Frank Westlake:
Maybe the install script failed. Try again and watch closely for the error message.

Frank
[SuperSU] bovirus:
I tried several times with different devices.

I downloaded also the SupeSU.apk from Gogle Play and I compared it with the /system/app/SuperSu.apk installed in the device.

Are equal. But show version 1.86. Did you check in your device?