yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Google Drive?
[SuperSU] Frank Westlake:
However you wish, I don't know what your "ROM" is set up to do, but SuperSU.apk must have already been installed and created as a user so that the data directory will have the correct user id. You could, for example, include a "installSuperSU" script which installs and launches the package so that a data directory will be created, writes the defect file, then deletes itself (the "installSuperSU" script) so that it won't be run again.

Frank
[SuperSU] justforreply:
Problem with SuperSU.

Hi, guys

I'm having problems with supersu 2.02 on my s3 running glamours5 rom.

When i enter the root apps they asks for root permission (like when i enter terminal emulator and type su), and nothing happens as a non-rooted device.

Sometimes after a long time when i enter SuperSU app it asks me permission for the apps i entered ago at same time with a lot of messages of su request, but at now nothing happens.

Please guys can you help me ? This problem are making me crazy :p:p.

What you suggest to me guys, i was thinking on downgrade to 2.01.
[SuperSU] bearusa:
I had different issues but op suggested to wipe dalvik cache then reinstall 2.02

Downgrade to 2.01 wipe dalvik then reinstall 2.02 see if it works.. problem I had was sorted after
[SuperSU] Frank Westlake:
My memory was faulty, the data directory is created when the package is installed - its the 'shared_prefs' directory that is not created at that time; so you need only install the package and write the directory and file on first boot.

Frank
[SuperSU] Solace50:
yea had to make some room for that one, i pmed on irc/emailed the url.
[SuperSU] Tarun93:
i just ported LENOVO S650 VIBE UI 2.0 rom to my Device Q700S i have a strange problem i have root access but i can open the Supersu it asks me to update binaries if i press ok it asks normal or CWM/TWRP tried both normal n CWM/TWRP thing nothing works can someone pls help me out if is it just possible to grant all permission automatically if there is no solution to the update binary thing
[SuperSU] Chainfire:
v2.04 BETA

Test release for your enjoyment:

ZIP: BETA-SuperSU-v2.04.zip

Changelogs: http://xdaforums.com/showpost.php?p=23427824&postcount=3

Let me know if this solves problems ... or introduces new ones! I want to release the next Play update in 48 hours or so, so please let me know ASAP.
[SuperSU] Pons:
Works with Lux Pro (updated June 2014) and CF.lumen, but not Lux Lite (updated Jan 2014). So the Lux dev needs to update Lite. That, or users need to spring for Pro.
[SuperSU] Pkt_Lnt:
Samsung Glaxy S4 Active Intl I-9295 with AOSP 4.4.4 ROM. Cannot press Grant or Deny buttons and SSU times out. Tried with two app upgrades from Play Store and by forgetting apps. No touches on screen worked.
[SuperSU] Pons:
Using Lux Lite perhaps? Or another app that messes with overlays?
[SuperSU] Chainfire:
Note that you en/disable the tapjacking protection feature from SuperSU settings ...
[SuperSU] Pkt_Lnt:
No Lux, though I have pro version. I use Velis Auto Bright that does not normally use overlays. I looked at the tapjacking and left it checked, which is now obvious that I was backwards. It works fine now.
[SuperSU] jesssiii:
I was having this problem, gonna try it now!

VS980 LG G2
[SuperSU] MikeRL100:
Flashing the zip after wiping cache and dalvik may have caused SuperSu pro to be uninstalled. May have. Investigating now.
[SuperSU] Pons:
Velis has overlay/addView, but SuperSU still worked when I enabled it. Anything else you can think of? I'd preferably like to get this ironed out, rather than disable a security feature. I'm never a fan of compromising security more than necessary.

Mine wasn't uninstalled, and there's no mention of removing Pro in the script. Though I didn't wipe cache and dalvik.
[SuperSU] jesssiii:
Ok, LG G2 using xdabbeb's new 2.0 stock rom with Verizon. The grant option now sticks. But it's flashed so it should show as a system app, but it doesn't. It's goo going into /system/private app but if i move it to system/app it shows correctly. Thanks!

VS980 LG G2
[SuperSU] Pons:
I'll have to look into that ROM, but according to the flashable script:

cp $COM/Superuser.apk /system/app/Superuser.apk

it should be going to system/app, not priv-app
[SuperSU] Pkt_Lnt:
Not that I know, I don't use any other screen type app outside Velis.
[SuperSU] Solace50:
permission issue is resolved.
[SuperSU] muniz_ri:
Seems to be working fine on I337 running stock NC1.
[SuperSU] Herk718:
[MENTION=631273]Chainfire[/MENTION], Beta v2.04 is running flawless on my Sprint Note 3! Thanks... And also the problem everyone's been complaining about I also was experiencing and can comfirm it's fixed in the latest BETA.
[SuperSU] deathsquad737:
It works great on my vs980 running xdabbeb 2.0

But i had to unistall the apk that was in this rom i flashed it without uninstalling. It and it still said version 2.2 but when i uninstalled system su apk and then flashed it was the updated beta release

WHATSAMATTA U ALUMNI
[SuperSU] mrchambo:
I have tried to flash Beta 2.04 over 2.02 twice now with no success. I am running ART. Do I have to go back to Dalvik in order to flash the BETA?

TIA,

MrC

A Super SU Pro subscriber
[SuperSU] amarjit_rsingh:
Permission issue is solved on my motorola moto e
[SuperSU] tantrums:
Hi [MENTION=631273]Chainfire[/MENTION],

I have an OPPO Find 7a device and we have an issue on supersu. SuperSU root is working but the latest superSU versions (from version 1.51 to 2.04 su binary) cannot detect the internal and external sd card mounts properly. This results to non-working Titanium Backup backup operation and other root apps that involves accessing sd cards. The last fully working version of SuperSU in my test was version 1.45.
[SuperSU] Raverbunny:
Installed and working fine on Gummy Rom

Nice work, no problems to report here :good:

Nexus 7 LTE (deb)

Gummy Rom

ElementalX Kernel
[SuperSU] Zen Arcade:
I317 stock NE5 4.4.2 - no issues found with 2.04
[SuperSU] anuajayan:
Each time when i enter into supersu i got a pop up message as "The SU binary needs to updated, continue? "

How to rectify this issue?

Please help me out..
[SuperSU] Zoltan-X:
Hey chainfire, the installation script of SuperSU zip is faulty on OPPO find 7! We don't have busybox in "/sbin" it's in "/system/xbin" therefore we have many reporting errors with various root apps.

Tia
[SuperSU] murdoch1:
Su beta 2.04

Installed on lg g2 d802 running mahdi ROM. Perfect.. No issues whatsoever.
[SuperSU] Chainfire:
Hmm, I could actually see this happening. Will investigate.

As in, SuperSU's settings tab says it's not a system app?

You should not move it into priv-app, SuperSU does not expect that.

You're going to have to provide more details than this.

Please get me the output of these commands from a terminal emulator app (NOT adb shell!), both as the app's normal user, as well as from su:

printenv
mount

I'm not sure what is going on, but the sentence as you wrote it doesn't make any sense. The ZIP is installed through recovery, where you never depend on /system (or what kind of weird recovery are you using?). But even if that was correct, switching these around in recovery would not have any influence over root apps running on normally booted Android.
[SuperSU] Zoltan-X:
Files aren't copied, cause busybox cp command is failing, cause we have no busybox in sbin! That's done for daemonsu? and the ".su" so root is working and not.
[SuperSU] Chainfire:
Again - what sort of recovery are you running?
[SuperSU] Zoltan-X:
It's with Philz cwm mod 6.48 and Twrp 2.7 too
[SuperSU] tantrums:
These are the output logs.
[SuperSU] Chainfire:
Both of those have busybox available in /sbin. Either way, I have removed the dependency in the in-app TWRP/CWM installer. Still, if you're installing using the normal flashable ZIP, that should not be a problem, as it doesn't reference busybox at all.
[SuperSU] Zoltan-X:
Hmm i don't know why I corrected it with changing the busybox path and it works free of those mentioned bugs? Thanks for those fast reply.
[SuperSU] Chainfire:
Strange values ... can you pull /init.rc , and run printenv from ADB shell (without su!) ?

EDIT: even stranger - external sdcard should still be available from su, even though internal sdcard would not be
[SuperSU] Zoltan-X:
And yes I'm using the zip method!
[SuperSU] tantrums:
Here:
[SuperSU] Chainfire:
This is very odd-ball storage setup I have not encountered before. It's not unfixable - I just really have no idea how to, as I have no device to test this on myself.
[SuperSU] denyo81:
[MENTION=631273]Chainfire[/MENTION], the pro unlocker from Playstore isn't compatible with the new Beta version 2.04. But I can set the pro unlocker in the App. All the rest works fine for me. Greetz Daniel

Edit: Now it works perfect on CM11 with my S3. Thumbs up ?
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION], Beta v2.04 works perfectly here. Nexus 5; latest Paranoid Android, latest MultiROM TWRP
[SuperSU] deathsquad737:
Uninstall previous supersu then flash beta in recovery

WHATSAMATTA U ALUMNI
[SuperSU] Frank Westlake:
Fleshed and lunched Supper Sue on:

-SGH-I717 Note Android 4.0.4 stock except TWRP.

-SM-N900T Note3 Android 4.3 stock except TWRP.

-SM-N900V Note3 Android 4.3 stock except SafeStrap.

The Note 3s were OK.

On the Note, good flesh but after lunch Supper Sue continued to display the busy indicator over an empty apps list. I swipped across to Settings and for something to do checked 'Survival Mode'; Supper Sue immediately locked-up and unresponsive. Rebooted, ran Term into 'su', exited, lunched Supper Sue and apps list immediately displayed fully. All three devices OK now.

Frank
[SuperSU] MikeRL100:
It was actually a bit odd. On both my Nexus 5 and Nexus 7 2013 I installed SuperSu by wiping cache and dalvik followed by flashing the zip. Then I rebooted. On the Nexus 5, SuperSu pro was gone. I noticed this immediately once I had booted. Went into SuperSu and reinstalled Pro from Play. SD Maid later found app-lib corpses remaining. On the Nexus 7 2013, everything was fine. I wonder what happened? Last version I was on was 2.02.
[SuperSU] dhampire:
Sir, 2.04 stil su binary loop on lenovo s930 kitkat 4.4.2.
[SuperSU] WR3CCKL3SS:
[MENTION=631273]Chainfire[/MENTION] having an issue with the pro unlocked for SuperSU. I re-download it thru playstore and it still shows SuperSU as the free version.... Its not until I enable pro features at the bottom of the settings menu that it will turn into the pro version... I'm sure it's been reported but just thought you could need more confirmation. Running latest AICP jflte build... On latest Alucard new Cm kernel
[SuperSU] ne0zone75:
Good evening,

v2.02 flashable archive is running perfectely fine on latest ASUS stock ROM (TF701T)... KK (4.4.2) !

I've flashed SuperSU throgh CWM recoveryfor my device : as a result it is working perfectly well (i had to reflash SuperSU after 4.4 upgrade is done... from 4.3...

You will find a screenshot below :

My very best thanks to [MENTION=631273]Chainfire[/MENTION],

Be well, all :D

Tapatalked from my TF701T
[SuperSU] Pkt_Lnt:
I had the same thing with my S4 Active, had to reinstall Pro.
[SuperSU] classic757:
Hello [MENTION=631273]Chainfire[/MENTION], I am using your SuperSU 2.04 Beta with no problems to my knowledge on my xt1028 Moto G.

Thanks for your hard work. Looking forward to the next PlayStore update. :good:
[SuperSU] Zen Arcade:
At the risk of over reporting same behavior on the Note 2 - I317. After reinstall of Pro I reran the 2.04 install and Pro was uninstalled again.
[SuperSU] hinnn:
2.04 updated?
[SuperSU] Skhulile:
Hello

Does anyone have an idea of how I can get rid of the SU Binary update bug. I just updated Super SU to 2.04 and I get the msg; "SU Binary needs to be updated" but whichever option I choose it keeps on failing to update. I'm running Gnabo Custom ROM, based on kitkat 4.4.2 Galaxy Note 10.1, Philz Recovery.

Thanks in advance
[SuperSU] Pkt_Lnt:
Beta 2.04 is the attempt to solve that. Look back and read messages from when Chainfire announced beta 2.04 it to see the logs and terminal output he needs to identify it. Even a nandroid if you have the same device he have.
[SuperSU] Skhulile:
I already read through the thread from the one 2.04 was announced, but I didn't see any commands that I have to do. If you know may you please tell me, because this bug is really annoying.

Thanks in advance
[SuperSU] Pkt_Lnt:
Read these, post what he asks.

http://xdaforums.com/showpost.php?p=54937116&postcount=6333

http://xdaforums.com/showpost.php?p=54937694&postcount=6340
[SuperSU] Skhulile:
[MENTION=4403217]Pkt_Lnt[/MENTION] thanks man

[MENTION=631273]Chainfire[/MENTION] I ran the printenv and mount commands. See attached text files

EDIT: Just extra info, there are times that when I choose Recovery Install, when the device boots up again, it seems like the SU Binary has been updated successfuly, because I don't get that error again. but if I reboot the device again(without changing anything) the bug is back up again
[SuperSU] boe323:
where can I download the 204 zip ?
[SuperSU] Pkt_Lnt:
The other post he asked for specific files too.
[SuperSU] deathsquad737:
Here http://download.chainfire.eu/454/SuperSU/BETA-SuperSU-v2.04.zip

WHATSAMATTA U ALUMNI
[SuperSU] cschmitt:
Running CM11 on m7. Each time a nightly is flashed SuperSU prompts to update the su binary on reboot. I've narrowed it down to one missing file: /system/xbin/sugote-mksh that is not being backed up or restored by /system/addon.d/99-supersu.sh. Is this behavior by design or an oversite?
[SuperSU] MikeRL100:
It's a good thing I noticed that issue with flashing SuperSu after wiping cache and dalvik where Pro was uninstalled. Originally I didn't even think it was a SuperSu issue. Now it looks like two other users have reproduced it. Anything we can do to help you, Chainfire? Logs or anything?
[SuperSU] Chainfire:
at everyone: I'm leaving on vacation in a few hours, so this will all have to wait until I return.

Oversight. Will be fixed next update

It's already fixed in my dev version.
[SuperSU] seschaum:
Happy Holidays!
[SuperSU] MikeRL100:
Have fun. As for the issue, glad it's already fixed on your end. Hopefully the next beta will also include the backup script fix. Then you will be one more step closer to release. Hopefully nothing else ugly comes up.

I can easily wait, but I'm wondering if I should flash the current beta when upgrading my nightly next. Or downgrade SuperSu. I'm leaning towards downgrading to the last stable, unless that can cause issues.

Off topic: Is your vacation spot nice? I wonder where it is, if you don't mind me asking. Also how dare you take a vacation! Everyone knows caffeine is all that is needed to code. No sleep or breaks allowed. According to most users, developers are all robots.
[SuperSU] Blac Caesar:
Have fun on your vacation.. Thanks again for all your hard work as always!
[SuperSU] rkuijpers:
Enjoy! I do! :cool:

Verstuurd vanaf mijn XT1039 met Tapatalk
[SuperSU] erad1:
Enjoy your vacation...when returning what would you need to make a fastboot flashable img for a Oneplus One?
[SuperSU] Pons:
I don't have that phone, but I'm pretty sure you can't make a fastboot flashable IMG for an app.
[SuperSU] polobunny:
Why would you need to make a fastboot flashable img for a Oneplus One??
[SuperSU] deathsquad737:
Ok about this ota survival?is it good?

WHATSAMATTA U ALUMNI
[SuperSU] erad1:
From the CF AUTO-ROOT Repository:

Fastboot flashable devices

BASIC INSTRUCTIONS

All downloads contain .img files bootable through Fastboot.

Make sure your device is in Fastboot mode (usually you can get there by holding VolUp+VolDown+Power when the device is turned off), then run the included script for your OS. On Linux and Mac, you may have to chmod +x root-linux/mac.sh before the script does anything.

A special boot image will load, which will install (only) SuperSU, then reboot into Android.

UNLOCK BOOTLOADERS

The included scripts perform an "OEM unlock". If this fails, the root will not work. If it succeeds, and you were not previously unlocked (first time rooting ?), it will probably wipe your data !

For some device (Sony, Verizon, etc) you may need an OEM-specific tool to unlock the bootloader. Please do not forget to check and use this tool, if provided by the OEM.

Device details	Votes	Download

OEM	Model	Name	Device	Board	Platform	Good	Bad	Size	Link	#

samsung	Galaxy Nexus	mysid	toro	tuna	omap4	862 +1	811 +1	6752462	File	2054

samsung	Galaxy Nexus	mysidspr	toroplus	tuna	omap4	719 +1	717 +1	7144750	File	920

samsung	Galaxy Nexus	takju	maguro	tuna	omap4	751 +1	788 +1	6758899	File	14207

samsung	Galaxy Nexus	yakju	maguro	tuna	omap4	788 +1	778 +1	6758869	File	35361

samsung	Nexus 10	mantaray	manta	manta	exynos5	805 +1	784 +1	7028463	File - Forum	14494

LGE	Nexus 4	occam	mako	MAKO	msm8960	1303 +1	976 +1	8605922	File - Forum	334222

LGE	Nexus 5	hammerhead	hammerhead	hammerhead	msm8974	1941 +1	1092 +1	9953201	File	407286

asus	Nexus 7	nakasi	grouper	grouper	tegra3	1043 +1	877 +1	7292187	File - Forum	84217

asus	Nexus 7	nakasig	tilapia	grouper	tegra3	878 +1	814 +1	7292145	File - Forum	26558

asus	Nexus 7	razor	flo	flo	msm8960	744 +1	682 +1	9304491	File - Forum	40834

asus	Nexus 7	razorg	deb	deb	msm8960	646 +1	644 +1	9305242	File - Forum	9346

GET THE RIGHT FILE

Make sure you get the correct file. Using the incorrect file may brick your device.

REQUESTS AND DISCUSSUON

The central CF-Auto-Root thread can be found here on XDA-Developers.com. Use that thread for requests for new roots and generic discussion.

These are images for Fastboot flashable devices...correct? I have a (Oneplus One aka; NOT A SAMSUNG) fastboot flashable device which doesn't appear to be listed. I am asking if any dump files would need to be provided by me for an img to be created and added to the Repository list. Hope this makes things a bit clearer.
[SuperSU] meesotrev:
SuperSU v2.04 installed and working perfectly on HTC One XL, running Venom Viper XL 4.2.2 and ElementalX 8.3+ many thanks for the upload bud! :D
[SuperSU] aircooledbusses:
Same here with pro ......nexus 7 flo carbon nightly glitch expirimental

Sorry I didn't opt for the pro version sooner, you been keeping me rooted for a while now
[SuperSU] Thomas_BA:
Running without problems (so far) on Moto X Stock KirtKat 4.4.4
[SuperSU] Technical:
Am I right to think that the .zip flashed install SuperSu as a system app?

Is there any .zip file to flash SuperSu as normal user app?

I'm asking this because in a multiboot environment sharing app as mine, only user app are shared and SuperSu will be better as an user app for me.

By the way, I'm using SuperSu Pro if this make any difference. Thanks.
[SuperSU] Pkt_Lnt:
Install from Play Store as a normal system app. Yes, flash from recovery makes it system, and you can convert from user to system within SuperSU itself.
[SuperSU] Conte Mascetti:
If I'm not wrong there's a multi user option, so you can choose if supersu it's available just for the main user.

From GNexus
[SuperSU] denyo81:
When you install the apk from Playstore so you have the choice supersu to move into system app.

But when you use the flashable supersu zip this application move automatically into the system app.
[SuperSU] Technical:
Thanks. But it's not a problem of multi users, but multi boot environment.

Thanks for the confirmation about system. I've described my issue here: http://xdaforums.com/showpost.php?p=55005074&postcount=6931

I'm not being able to update the binary using SuperSu when I use SlimKat ROM as secondary or multislot boot. I was thinking that the problem would be in a system app (which is not shared among ROMs), but I've tried SuperSu as an user app and it cannot update SlimKat binary either. I don't know how to use SuperSu in the secondary ROMs, it works only in the primary one.

---------- Post added at 12:28 PM ---------- Previous post was at 12:22 PM ----------

By the way, where could I found v2.04 Beta to download?
[SuperSU] guycan:
/COLOR]By the way, where could I found v2.04 beta

It a few pages back on page 631

SGNote2
[SuperSU] Chainfire:
Problems are just very specific to setup and apps. There have been some problems that truly have SuperSU to blame (like the Root Explorer issue). There have also been a lot of problems that were the apps fault (like this Gemini issue that keeps being mentioned). And if don't use any of those apps, or not in a specific way that causes a problem to occur, you simply won't have problems.
[SuperSU] sparksco:
Aw, thanks it updated.

To CF I updated to v0.88 and I currently have v0.87 installed in the system. However in Titanium Backup pro I am unable to merge new update into system rom. I'm not sure if this is a issue with TB or SU app. I rebooted my phone once and still it doesn't show up in TB. Not a big deal, but all the previous updates would merge into system rom so that way if I did ever have to do a factory reset I could keep root access. Any suggestions?
[SuperSU] dimebagdan65:
Guess I'm just lucky like that

:thumbup::D:beer:

Anybody with an Evo 3D CDMA that's curious about my setup, hit me up
[SuperSU] Chainfire:
That is completely beyond the scope of SuperSU ... It's a function of TB.
[SuperSU] DarkhShadow:
Well from just looking at the dev console its not exactly the most simple thing xD

Sent from my ice cream powered Nexus S
[SuperSU] DarkhShadow:
To clarify on chainfire

The currently used superuser/superSU does NOT show in TB so that it doesn't risk breaking your root

Sent from my ice cream powered Nexus S
[SuperSU] sparksco:
Yes it's a funtion of TB pro version and honestly one that I like to us quite often for many of my system updates.
[SuperSU] RalphLauren:
@Chainfire,

in GooglePlay's "What's New" there is a phrase:

"Voodoo OTA Root Keeper backup removed at binary install",

I'm not so technical, could you be a bit more specific and explain what does it mean exactly.

I mean, I successfully used Voodoo OTA Keeper to get my root back after 4.0.4 IMM76D OTA and recently after 4.0.4 IMM76I OTA updates, what will happen now if I update to SuperSU0.88?
[SuperSU] Chainfire:
SuperSU has it's own OTA survival mode (Pro version), more importantly, OTA keeper tends to restore the wrong binary. You can still use it if you want, but everytime SuperSU updates the binary, you need to let OTA keeper re-make its backup.
[SuperSU] RalphLauren:
Ok, thank you for information. I know that SuperSU has it's own OTA survival mode, but since it's listed as a "not guarantee" feature I was a bit concerned.
[SuperSU] Chainfire:
I understand I can see why it would be nice to use. I have not done anything specifically to disable this functionality, and as this is a TB function, I can't begun to speculate on the how or why of it.

OTA Root Keeper isn't guaranteed either, it also uses pretty much exactly the same method as SuperSU, if one doesn't work, neither will the other.
[SuperSU] RalphLauren:
Right, before IMM76D and IMM76I updates, the OTA survival option was checked in SuperSU settings, however in both cases root did not get back. And all root-dependent apps were screaming that I do not have a root. So, in both cases after the updates, the root was returned with the help of Voodoo.

Do I miss an extra menu or an option in SuperSU to get back the root after OTA, or it's really meant to fix it by itself, or should be Voodoo be deleted from the device in order this option works in SuperSU???
[SuperSU] wraithdu:
Are there any real advantages to having SuperSU installed as a system app versus a user app? I've actually found one minor annoyance that the Play Store doesn't always offer updates to system apps, so in that respect it seems better to keep it as a user app.

Thoughts?
[SuperSU] k2trill:
the Rezound in my sig...
[SuperSU] dimebagdan65:
Bah, stupid tapatalk doesn't show XDA website custom signatures :thumbdown::(
[SuperSU] Pons:
For titanium backup, they made SSU not show up due to safety reasons, the same ones that Chain's SU doesn't show.

http://www.titaniumtrack.com/changelog/titanium-backup/4-9-1-1

The only real reason that yall noticed is SU is already a system app so you never looked for it. SSU, on the other hand, is a data app so yall are trying to make it system app.