yashsingh1/xdaforums huggingface dataset:
[SuperSU] molesarecoming:
same with the new one it seems.

<4>[ 105.121490] EXT4-fs (mmcblk0p10): Couldn't remount RDWR because of unprocessed orphan inode list. Please umount/remount instead

weirdest thing we have ever had. we believe its a granting issue perhaps... but no clue until now
[SuperSU] Chainfire:
Looks to me like the filesystem is corrupt ?
[SuperSU] goodtimes50:
I've posted a couple times and even emailed Chainfire with no response. I believe I've discovered a bug with the notification messages. It seems that when multiple apps are granted root automatically in short succession the notifications loop indefinitely. For instance, on boot BetterBatteryStats, ROM Toolbox Pro, SetCPU, and LightFlow all request (and are automatically granted) root. When this happens I see a little notification above the dock for each that just loop indefinitely. This has happened on two different ROMs now (AOKP and TW).

Is anyone else seeing anything like this?
[SuperSU] My1xT:
well lightflow, something with acore and adblockplus get root@boot and I have no problems (Note 2)
[SuperSU] polobunny:
Ah yes! Someone else has the same issue has me. The apps are different, one is a personal app the other SM Manager and since they both launch at boot they happen to show the notifications in a loop until I force close SuperSU. I'm on CM10.1.

When it happens all I see is

SM Manager has been granted root

Personal app has been granted root

SM Manager has been granted root

Personal app has been granted root

and so on...

Weirdest is that I have global notifications disabled and those apps notifications also disabled. :|
[SuperSU] goodtimes50:
Glad to know I'm not alone!
[SuperSU] mobilecj:
is there any solution to the supersu binary update reboot problem?
[SuperSU] DKaine:
Why not just turn off the notifications? I'm pretty sure Chainfire said to turn off notifications if you notice issues in terms of speed bumps, or lag...

Also, I have a weird issue where after flashing SuperSU, on boot of my phone it updates from the Play Store. Literally on every boot, it will pull an update from Play store.. Any ideas, anyone?
[SuperSU] bleggy:
dumb question: what exactly does survival mode do?
[SuperSU] shaggyskunk:
I'll take a guess and say that it's because you're running an AOKP based rom. From what I understand, it's because the superuser script is embedded into the AOKP roms, I believe that there is a way to "fix" it, but frankly I don't think it's worth the effort. In any event I flash between AOKP & CM. When I'm running CM, I don't see it happening.
[SuperSU] zelendel:
I don't have this happening on the aokp rom I run at all

Batcom2
[SuperSU] DKaine:
I'm actually running a CM10 based ROM, no AOKP... I actually never had this happen on an AOKP ROM at all...
[SuperSU] My1xT:
bump.
[SuperSU] -star-:
1. Install/ flash the supersu.zip and the app will be a system app. There is not a need to copy it into the ROM. Or are you talking about a ROM release? Then don't put the supersu pro.apk in it.

2. If both accounts are there the license check will work.
[SuperSU] My1xT:
I want the Pro also as system app, not just the nrmal sSU and its not for release, just for flashing on my (or my sister's) device.
[SuperSU] goodtimes50:
It happens even with notifications disabled. Probably should have mentioned that. Only way to stop it is to go into SuperSU, enable notifications, save, then disable and save for all the apps affected.

I did see this when I was running AOKP 4.1, but I'm currently running a debloated TW rom (CSROM) and it's happening there too.
[SuperSU] polobunny:
Or FC SuperSU (I have hold back to kill options in dev options, so I simply open SuperSU then hold back).

But yeah, I don't think he read my reply. :p
[SuperSU] dragxdk:
Chainfire dont answer to questions....:(

tapatalked
[SuperSU] polobunny:
It's only been 2 days. The bug isn't a deal killer, I'm sure he'll answer eventually.
[SuperSU] goodtimes50:
Actually, I've posted about this a couple times in the last few weeks (and emailed him a week or two ago). I ain't mad or anything, I understand this isn't a huge deal in the scheme of things, but the above statement isn't entirely accurate...
[SuperSU] polobunny:
Woops, wasn't aware of that then.
[SuperSU] goodtimes50:
For some reason this has started happening much more in the last few days. Every time I reboot and then randomly at other times. It's quite frustrating.
[SuperSU] thesebastian:
edit: wrong thread!
[SuperSU] polobunny:
Wrong thread. This isn't a nexus 4 rooting place.
[SuperSU] My1xT:
yeah.

sSU has nothing to do with the rooting process, it's just some kind of barrier that alles you to select which apps may use root and which not, so it doesnt get out of control...
[SuperSU] fsdfcerdsfxzcds:
I have just flashed my GSM Galaxy Nexus successfully Android 4.1.2 using the Galaxy Nexus ToolKit 10.1 and successfully rooted. Then I got OTA update to Android 4.2.1, but root was lost. I then tried to root again (selecting Android 4.2.1 and SuperSu method), but when finished Root Checker says that I am not properly root. I open SuperSu and I get a message: "The SU binary needs to be updated. Continue?" and then "Installation Failed". I have still the bootloader unlocked. What I should do? :confused:

Thanks in advance!
[SuperSU] -star-:
Install cwm through fast boot mode, flash the supersu.zip in cwm and everything should work.
[SuperSU] Bigdrago:
After rooting and updating SuperSU I did a factory reset.

Now when I start SuperSU it tells me it needs to be updated. I click "continue" and get "installation failed" and then it restarts.

I have flashed SuperSU many times and tried updating. I still get "installation failed".

Is there any fix?
[SuperSU] rawintellect:
What phone do you have?

What version of hboot is on your phone?
[SuperSU] My1xT:
just a question

WTF is hboot?
[SuperSU] samarain:
Use the google, he knows. .
[SuperSU] whateheck:
hi I have the SuperSU from flashing the ARHD rom sometime ago. just checking, do i need to check if I need to update binary or something if I need to flash again ? I didn't see any update binary option in the SuperSU app so just wondering about it. thanks !
[SuperSU] Bigdrago:
hboot: 2.15.0000

HTC One S
[SuperSU] -star-:
The app will ask you if it wants to update the binaries.

Sent from my Nexus 7
[SuperSU] hapybrian:
"Ask Me Again"

Awesome. Actually, I prefer the (default unchecked) "Don't ask me again" type of prompt, but

a default checked "Ask me Again" is fine too. As it is, I don't want adb to have default grant

(since my "locked" phone could be violated by a USB cable and adb), but I have to be careful

to say, "Ask me again" and "grant", each time I use it..

Thanks for this useful app. :D
[SuperSU] My1xT:
but Maybe an always ask with a timer or alike, coz when I use my Solid Explorer, the problem would be @ always ask that I surely would have to enter PIN and grant access for EVERY LITTLE THING I do...
[SuperSU] whateheck:
oh, ok, thanks !
[SuperSU] erikieperikie:
EDIT: restored nandroid, tried running SuperSU again, same problems. Opened Play Store, found that SuperSU needed to be updated. After update and su binary update it works fine!

I have a problem:

The SuperSU prompt to grant/deny root access to an app flashes on screen when I enter that app for the first time! Is this a known issue and how can I fix this?

I rooted my Nexus 4 through efrant's guide: http://xdaforums.com/showthread.php?t=2010312

The ONLY things I have done after that process are:

nandroid backup

installed busybox (smart install)

nandroid backup (so I rebooted in the meantime)

installed dropbox, TitaniumBackup, Root Explorer.

Everytime a root app asks access, the SuperSU prompt flashes on and off. I can hardly press the grant button and SuperSU force closes when I run it from the app drawer. Running it a second time works just fine, so the problem lies within the moment the prompt appears.
[SuperSU] TheByteSmasher:
Just use this: http://xdaforums.com/showthread.php?t=1766475 all these rooting issues. Wug uses Chainfire's SuperSu so no worries. Also is quicker and easier.

Sent from my Nexus 7
[SuperSU] My1xT:
there is a problem with sSU that happens on my Galaxy S Wifi 5.0 @CM9 when I enter Pin Code the pressed buttons turn transparent.

on Huwei Ideos x3 @CM7.2 this doesnt happen.

I will check Galaxy Note2 after warranty repair finished...
[SuperSU] scarecrow420:
Due to the latest HTC JB update for my Telstra HTC One XL (LTE) causing System to be not writable, I am having issues with SuperSU. I have flashed 0.99 version from this thread, however it still wants to update su binary when i run SuperSU. If i say OK, it fails and then reboots the phone (i guess this is the system write lock protection). If i say cancel then it exits out of SuperSU. I wanted to get in there so I can change the settings to not display the toast notification when apps are granted su access etc.

In the next version of SuperSU could you consider making it so that you can still get into the application and change settings etc, even if you cancel from updating the binary? Or prompt whether to reboot or not (if it's superSU that does the reboot that is)...

Also how come if ive flashed the latest version, it still wants to update the su binary? Does this mean i need to wait for a new flashable zip that includes the latest su binary? Can someone post a URL to where the latest su binary is (where does SuperSU check for it and download it from?)? Maybe i can make my own flashable zip with the latest binary to get around this issue

Many thanks for an awesome super user app :)
[SuperSU] Bigdrago:
Is there a way to unflash it from the phone? :)
[SuperSU] -star-:
Use the unroot option in the app to remove supersu and the binaries.
[SuperSU] Flowyk:
what is superSU returning if the access is denyied? ... there is an app that knows if the phone is rooted even if he dont get access

I think that if the app dont get access to root functions it should not know that there is a root
[SuperSU] DarkhShadow:
Re: [04.12.2012] SuperSU v0.99

It could be looking for the binary or superuser.apk

Sent from my Jelly Nexus 4
[SuperSU] Flowyk:
if u have root you should be able to hide the app ... that will be good feature (maybe for pro?)
[SuperSU] :
Re: [04.12.2012] SuperSU v0.99

Everyone loves CF
[SuperSU] qzem:
Hey!

I want to thank you for **** great program. I boufht pro licence to support your work. I have one problem though. I have flashed Latest Jellybean rom on my HTC One S C2, and when ever I am trying to update binary from super su I got Install Failed! and then my phone reboots. I also get a reboot when I grant root permission to a new program :S. Please try to correct this bug. Do you need some log to see what is going on?

Cheers
[SuperSU] :
Re: [04.12.2012] SuperSU v0.99

Sounds like you may not have full root access

Sent from my GT-N7000000000 using Tapastalker 2
[SuperSU] DarkhShadow:
Re: [04.12.2012] SuperSU v0.99

Is your phone s-on? In which case it is not the fault of the app, it means your /system cannot be written to while booted, you need a special thing added to your ROM(might be kernel, not sure) that enables r/w on /system.

Sent from my Jelly Nexus 4
[SuperSU] AlxMAX:
I have exactly the same problem with SuperSU as described by scarecrow420. The only difference was that I have tried a one more step (after seeing the reboot problem): I booted the phone in recovery mode and copied manually SuperSU.apk, the su binary (to /system/xbin), changed the owner to 0:2000 (root:shell), changed the access rights (rwsr-sr--), made the symbolic link to su in /system/bin. The necessary files were picked from a phone with an up to date SuperSU.apk and su binary. I have even copied a busybox binary in /system/xbin and made a symbolic link to it in /system/bin. The firmware version is 3.17.207.1 (for O2 Germany), the kernel version is 3.4.10. I can produce a logcat, if you want me to.

I have found one more guy having this problem. The guy has an HTC One S this time which means the problem is not necessarily related to One XL. mikaelft, which kernel does your phone have?
[SuperSU] Whiler:
Pro version?

Hi,

I'd like to confirm that I'll be able to do what I want to do with the Pro version:

First, I have a not very common phone: Wiko Cink Slim (compare to HTC, Samsung, ...)

When I use the free version, I can see in the log the authorized applications with a green #, and ADB shell with a red #. This is normal, as I need the Pro version to use ADB shell...

Moreover, I haven't find the driver for my phone on Win7x64 when the phone is on recovery mode (unknown device). If the phone is started normally, I have the needed driver and can access it...

For instance, as a first step/try, I try to replace the file /system/media/bootanimation.zip.

To do it, I run DOS prompt and ADB shell like this:

>adb shell
$su -c 'mount -o remount,rw /system'
$mv bootanimation.zip bootanimation.ori
mv bootanimation.zip bootanimation.ori
failed on 'bootanimation.zip' - Permission denied

Finally, my question... if I purchase the Pro version.. permission will be granted?

Commands are used ok?

Regards,

W.
[SuperSU] y2kshin:
excuse me..

a little question..

galaxy note, I am now in ICS 404 with cmw+root supersu.

is it okay if I uninstall supersu from app manager?

I want to keep the safe bootloader but need to uninstall supersu.

if I use the full unroot menu from supersu, will I lose the safe bootloader?

thanks...
[SuperSU] :
Re: [04.12.2012] SuperSU v0.99

What kernel are you on.
[SuperSU] y2kshin:
thanks..

I am on PhilZ-cwm6-XXLSC-XJB-3.99-signed
[SuperSU] :
Re: [04.12.2012] SuperSU v0.99

You can unroot and you will still be on brick bug free philz.

After unrooting confirm by booting into recovery and make sure it says phiklz touch cwm.
[SuperSU] bbrad:
Re: [04.12.2012] SuperSU v0.99

Love this app thanks for the work :D

________________________________

If I Helped Press The Thanks :D . Sent From My Handheld Mobile Device
[SuperSU] Chainfire:
Icon competition results are in !

http://www.chainfire.eu/articles/128/_Results_SuperSU_Icon_Competition/
[SuperSU] osm0sis:
Haha That's amazing! Glad to hear Super Andy saved the day, even though I was a fan of the original's simplicity.

SuperSU by Robert McKenna was one of my definite favorites (other than my own submission of course ;)), so I'm glad to hear I'll be able to select it as well. Thanks Chainfire! :D
[SuperSU] polobunny:
You don't need to buy SuperSU Pro to ADB shell to your phone. You should be able to grant it access with the free version.

Here's the difference between Pro and non-Pro

- OTA survival mode (no guarantees)

- Full color-coded command content logging (input/output/error)

- Per-app logging configuration

- Per-app user override

- PIN protection
[SuperSU] Whiler:
Yes, I finally managed it with the regular version.

Thanks for the difference matrix.:good:

W.
[SuperSU] bruce the boss:
Hi all,

I do have a Ace 2 (I8160) mobile which I have rooted and also installed SuperSU v.099 but during the last days I have problems with my Wifi and I loosing connection all the time.

The mobile keeps scanning and for a long time he can't find anything and suddenly I do have connection for a short time and I'm wondering if this can be occurred by SuperSU or can't this be true?
[SuperSU] -star-:
AW: [04.12.2012] SuperSU v0.99

SuperSu won't influence your WiFi signal or the scanning time, maybe you are to far away from your router? Or came an radio upgrade with the flash?
[SuperSU] sudoo:
Hi all, I installed SuperSu from play store and last LBE virus scan alerts :

...

Do I have to skip or clean this ?
[SuperSU] My1xT:
ya should skip. sSU is a root app, so it has quite some rights, which LBE notices...

I dunno why there is the word Exynos written, but it cant be the exynos abuse, for that chainfire has a dedicated apk...
[SuperSU] Chainfire:
When in doubt, consider that LBE is Chinese suspected spyware and SuperSU is well... made by me.
[SuperSU] shaggyskunk:
Re: [04.12.2012] SuperSU v0.99

Exactly!

+1 billion!
[SuperSU] sudoo:
Yeah I know no problem that was not any kind of accusation :)

Just wanted to know what to do and I skipped this alert.

Thank you
[SuperSU] osm0sis:
Edit: Whoa. Wrong thread. Not sure how that happened. :eek:
[SuperSU] junkmail9:
Re: [04.12.2012] SuperSU v0.99

Pro version also supports the dev...

Sent from my Fireball using Xparent Blue Tapatalk 2
[SuperSU] bruce the boss:
What do you mean with "Or came an radio upgrade with the flash" ..... can you please explain that and how can I check this and/or change this so that my Wifi keeps working al the time ? :)
[SuperSU] MaestroOrg:
Problem on AT&T HTC One X

Hello,

I've been using SuperSU on my rooted HTC One X and like other I've been getting the mksh requests. However I've had no luck in preventing the constant popups. Roughly once / twice a minute I'll get a notification appear in in a grey box informing me that the request has been granted or denied (have tried both ways). The phone appears to work fine otherwise, including WiFi& data connections, and I've not notcied any odd behavior in any apps.

However I can't get rid of the blasted notifications no matter what I do. I've tried disabling notifications in the SuperSU app, but they persist. More worrying, when I un-check 'Enable Superuser' I get a warning saying 'Uninstallation failed!', and even though the box remains unchecked I continue to get notifications.

The constant notifications make the phone hard to use for things such as watching videos or playing games, or even typing as the notification area covers the keyboard.

The problem has been going on for quite sometimes (over 2 months now) but I've simply tolerated due to a combination of not having time to research it and figuring a future update would probably fix it.

I'm using an HTC One X from AT&T, stock rom, but rooted (of course I guess).

Anyone able to provide some direction on what I should do or try? Would be greatly appreciated. :)
[SuperSU] :
Re: [04.12.2012] SuperSU v0.99

Maybe try the cleanup feature and uninstall then reinstall

Sent from my GT-N7000000000 using Tapastalker 2
[SuperSU] -star-:
AW: [04.12.2012] SuperSU v0.99

Some Roms update your radio with a newer version, the only way to check this is to compare the old baseband name with the new one. And just to make sure that supersu is not the problem you could try the temporary unroot feature.
[SuperSU] polobunny:
That list was taken directly from the SuperSU Pro page, not from my own.

'sides, still having infinite notifications loop and I don't think Chainfire has looked into it...
[SuperSU] claytonjn:
Re: [04.12.2012] SuperSU v0.99

I finally switched to a 4.2 ROM about a week ago, and not long after I began having issues with toast notifications popping up, over and over for the same thing, even though I have notifications turned off. Also, it was saving log information even though that was turned off... Basically it had reverted to default settings, and the notifications were going berserk. I was able to resolve it by clearing the SuperSu app data and flashing the SuperSu zip. I was also able to determine that it started happening immediately after flashing a zip which ran fix permissions as part of the script. Since fixing it as I stated above and not running fix permissions it has been a week and I have had zero issues.

I would recommend that everyone with the notification issues try this. Also, hopefully it will help Chainfire troubleshoot. I've read every page of this thread and I don't recall anyone providing any information other than that notifications keep popping up. Without a way to reproduce the issue, there's no way he could possibly find the cause. I'm fairly confident that the fix permissions script is what screwed with it.
[SuperSU] osm0sis:
If it were fix_permissions, then maybe it's got something to do with the backup copy of su that lives in the hidden dir under /system/bin/. The system apk and /system/xbin/su should still work normally after a proper fix_permissions (ran one via CWM last night and checked su after; still 06755 :good:). You could try removing that hidden bin dir and letting SuperSU move it in again to see if that also helps.
[SuperSU] claytonjn:
I should note that the script in recovery printed that it was fixing permissions. I don't know if it triggered the recovery's fix permissions feature (TWRP 2.3.3.0 for me btw) of if the script itself was running some sort of permissions fix. I was experimenting with the Pimp My ROM app that I'd been hearing a lot about, and the script was for some apps it includes, such as a beats audio, IIRC.
[SuperSU] osm0sis:
Fair enough. Point me to the zip and I'll take a look later on today to let you know what it's really doing if someone else doesn't beat me to it. :)
[SuperSU] AlxMAX:
I'm back with a logcat and a dump of last_kmsg with the supersu crash (the attached ZIP contains the 2 dumps). The logcat starts with the moment I launch SuperSU.
[SuperSU] Chainfire:
If anybody can reliably reproduce and fix the issue at will, I will definitely be interested in working to find a solution. It could indeed be a permission issue.

SuperSU's su binary checks for the following conditions:

/data/data/eu.chainfire.supersu/files/supersu.cfg

- user root

- group root

- permissions 0600

/data/data/eu.chainfire.supersu

- same user as SuperSU GUI runs as

If these conditions are not met, the su binary will ignore SuperSU configuration and as such behave as with default settings. The permissions on supersu.cfg should be reset to the above every time you change an app permission in SuperSU itself. Furthermore:

/system/xbin/su

- user root

- group root

- permissions 06755

Anybody who can shed a light on the problem, please do so. I have personally been unable to reproduce the problem.

As for the HTC specific mksh issue (caused by the Wi-Fi driver), in the upcoming SuperSU version there will be an option to trust the system user, that option can be enabled to circumvent the problem (probably)
[SuperSU] Chainfire:
Those files do not say anything useful.

If your problem is your HTC rebooting after a recent firmware update, when SuperSU tries to update the binary, that is an issue with the firmware where it detects writes to /system and reboots. There are custom firmwares that fix this problem.
[SuperSU] claytonjn:
Here's one of the zips from Pimp My ROM that seemed to cause the issues. It does indeed have its own script for fixing permissions. A couple things I should mention; I didn't reboot into recovery and flash it, the app did it automatically... Not that it should make any difference. Also, I flashed this both on my Galaxy Nexus (with TWRP 2.3.3.0, running a 4.2.1 build of PA), and on my Galaxy Note 10.1 (TWRP 2.3.3.0, TW-based 4.1.2 ROM). It caused no problems on my Note 10.1, only on my Galaxy Nexus.
[SuperSU] shaggyskunk:
Re: [04.12.2012] SuperSU v0.99

Chainfire,

On twitter you were saying that you've got a new build of SuperSU, with "lots of improvements to SuperSU code", but you were weighing whether or not to release it now, due to the multi-user requirements....?
[SuperSU] polobunny:
If it's indeed a permission issue, then CWM v5.8.0.2 fix permissions is breaking it, because that's the only thing touching permissions I run after a rom update.

ROM update goes like this:

-Download and install newest CM10.1 nightly

-Flash custom kernel

-Flash SuperSU v0.99

-Wipe dalvik/cache

-Fix perm

-Reboot

I've now fallen back to CM10 (JB 4.1.2 based instead of 4.2.1) and issue seems gone. I wonder if others having this issue are also on >=4.2.

Edit: Looked into the script you posted above (PimpMyBeats) and the permissions fixing script is the same included in all CWM recovery recent versions (scrip v2.04). AFAIK, this script wasn't touched in over 2 years, meaning if it's that then a lot of users would be getting affected.
[SuperSU] goodtimes50:
Just to be clear, are we talking about the notification loop here?
[SuperSU] bruce the boss:
How can I go to "temporary unroot feature" ?

Could you help me with that?
[SuperSU] polobunny:
I am. Hope others are also talking about this. :p