yashsingh1/xdaforums huggingface dataset:
[SuperSU] Prasad:
I tried that... now my phone is stuck on the boot logo :eek:

EDIT: Phone just booted, still no root.
[SuperSU] leninke:
Maybe you can try with twrp. For me works without problems
[SuperSU] Prasad:
Tried standard CWM, PhilZ CWM and now TWRP... still no root! :/ SuperSU ALWAYS worked for me on all my devices.. what's wrong?
[SuperSU] Pons:
Not a clue. Works perfectly on my m7vzw. I've never heard of the other m7 variants causing problems lately, but I've never looked past mine. Try redownloading the zip to ensure it's not corrupt. Other than that, I'd say check your device and/or ROM thread since this seems pretty isolated.
[SuperSU] shaggyskunk:
But from what I have read, if you flash a rom... Because supersu is not a system app, you'll loose root..?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] dimebagdan65:
Friends just call me Dime lol and if you followed that guide to the letter you just update from the Play Store, I haven't had a single issue other than the one I described with Tasker (And btw, Chainfire, they e-mailed you to see about working out the kinks ^_^) with updates or access.
[SuperSU] Pons:
Depends on which ROM you're flashing, and if you're doing a new ROM, or an upgrade. If you're flashing a new ROM, you should wipe /system as it is before you flash, which will replace your current su manager with the ROM's (almost universally Superuser), and then you just follow the steps that have already been outlined to switch. If an upgrade (and it doesn't wipe /system as part of its updater-script; some do, some don't), then you'll still have SuperSU installed, but now Superuser as well, and might have to change binaries, which also has been covered.

But no, you shouldn't lose root.
[SuperSU] bsoplinger:
There's an issue with the latest version of Google Play and it's licensing mechanism. I'd point you to the thread I originally saw if I remembered but unfortunately I don't. It's purely a timing thing with SuperSU being released at the same time as the Market app update that makes it seem that SuperSU has anything to do with the problem. Bottom line:

To fix the FC issue with Titanium Backup Pro, delete and reinstall the pro license key app. You can leave the regular Titanium Backup app installed. That fixed my problem instantly.

Sent from my PG41200 using Xparent Purple Tapatalk
[SuperSU] dimebagdan65:
Couldn't have said it better myself ^_^ The man speaks wisdom! BTW I wish more ROMs didn't clear out /system before installing. Makes upgrading a pain (But I enjoy restoring all my apps and settings, it's a zen thing for me, go figure... lol)
[SuperSU] pugfantus:
I was also having crazy FC issues recently with Titanium Backup, I found that deleting Google Play's data, rebooting and relaunching Google Play fixed all my TB issues as well.
[SuperSU] dimebagdan65:
Exactly why in my guide I walk you through installation, moving to a system app and troubleshooting solutions... I quite literally hold your hand step-by-step through the entire process of coming from using Superuser and converting to SuperSU... The truth is out there... www.dimedroidhq.com Read, don't be skeered, words are where knowledge hides, pal (^_^)>b
[SuperSU] shaggyskunk:
Thanks! The solution was, as you'd said.... UNINSTALL the pro license key, then reinstall!!

Bsoplinger... For PRESIDENT!! :thumbup::D

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] ehab-subh:
!!!!!!

Thank you very very much.
[SuperSU] shaggyskunk:
:confused:?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] BULL3TPR00F:
Hey guys I couldnt find this in the OP or by searching the thread but are there any special steps required for switching from ChainsDD superuser, to this one?

I have this working fine on my SGS II running Litening 2.5 but im trying to get it to work properly on my Transformer TF101 on Revolver 4.0
[SuperSU] Pkt_Lnt:
@dimebagdan has about a dozen posts just above, about his tutorial on how to do just that. He is probably lost in a big facepalm right now, but should return soon. :D

http://xdaforums.com/showpost.php?p=24178797&postcount=434
[SuperSU] BULL3TPR00F:
I tried his method but it still isn't working for me.

From the moment the SuperSU binary is installed, all root access is gone. I have to reinstall Superuser binary to get root access back.

So for the step after installing supersu and rebooting and then deleting the original superuser, i cant even delete the superuser.apk cuz i cant get root access to get into the system/app folder. i dont get any prompts for su from either SuperSU or original Superuser.

i'm trying some other methods right now to see if i can get any of them to work with revolver rom. does anyone have an update.zip for revolver rom that works? (the one in the OP gives an error, and yes i read the note that it might not work on all roms which is why im asking if anyone has a revolver specific one for the TF101)
[SuperSU] dimebagdan65:
Gotta be something model specific, cause just changing binaries shouldn't kill root. Sorry the guide didn't work out for you. You said Asus TF101, right? And you followed instructions to the letter? Coming from standard superuser installation, downloading via PLAY STORE (not installing via .zip), etc? Please advise cause if you did everything exactly as I laid out and it still didn't work, I gotta update my guide. Probably should anyways lol
[SuperSU] dimebagdan65:
Lmfao nah, I show folks a max of 3 times, after that, my sh*t's Google-able, let em find it themselves XD I seriously get more laughs from reading XDA than anything else I read or watch during the day. It's a serious Cassandra complex (look it up) and the reason my wonderful girlfriend got me this sweater last year:
[SuperSU] dimebagdan65:
What REALLY cracks me up is when folks think I'm just trolling for page hits. I don't get paid SQUAT per page visit, only for clicks on little unobtrusive ads. I didn't start my website to make money, I started it to get the knowledge and experience that I have found and gained on my personal journey with Android starting with the Motorola Droid 1 out to as many people that could benefit from it as possible. I guess that's why they say, nice guys finish last (to which I add, of course, because they make sure their girl finishes first hehe)
[SuperSU] BULL3TPR00F:
Yeah i tried your method to the T.

It must be an issue with the rom itself, as another user in the roms thread has stated he had similar issues trying to switch to SuperSU from the built in roms default superuser.

link to the post:

http://xdaforums.com/showpost.php?p=24333014&postcount=1458
[SuperSU] dimebagdan65:
Lmfao case in point! "Flashing the rom again restored root access" NO IT DIDN'T! How can you flash a rom on an unrooted phone...?! Lol thanks for that, updating the guide as it's evidently not perfect for all situations
[SuperSU] BULL3TPR00F:
lol well its not to say that root access is gone ENTIRELY, its that the binary cannot be accessed correctly, which results in unable to grant SU access to apps (no permission popups or anything, apps say they cannot get root access, etc)

recovery still works fine and can flash roms/zips, thats how i was able to restore the original superuser.apk and binary.

I asked the dude in the original thread to test out your method exactly, so we can confirm its an issue with our rom and/or device.
[SuperSU] dimebagdan65:
Thanks, before reinstalling the superuser binaries, did you try my trick that I used to trick Tasker into working? Just install superuser as a user app from the market, don't run it, and try the app in question and see if a SuperSU prompt comes up
[SuperSU] Prasad:
Redownloaded the zip twice. I don't see anyone posting anywhere that SuperSU didn't work. Yeah, it does seem isolated. Any information I can extract from my device to pinpoint the issue ?
[SuperSU] jazzruby:
Start with the last recovery log:

/cache/recovery

see if there was any issue flashing/installing

-JR-
[SuperSU] Prasad:
cannot access /cache without root :/

Alternately, Koush's superuser package didn't work either..

I'm on 4.4.2 btw..

[MENTION=631273]Chainfire[/MENTION], please chime in.
[SuperSU] jazzruby:
After flashing in TWRP you can go to Advanced > Copy log to SD

-JR-
[SuperSU] Pons:
You could also do an adb pull. And Chainfire is on vacation. Check back 2-3 pages.
[SuperSU] Frank Westlake:
Also, the terminal in TWRP might be of some help.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] andee39:
Hi,

Am hoping someone can help with my issue. Flashed MOAR 9.0 (4.3) the other day and by accident while I was looking for something else discovered I have intermittent prob with root. Went into Titanium Backup and got the following error - sorry could not acquire root privileges, very that your ROM is rooted. This attempt was made by using "/system/xbin/su" command. I had previously gone from 4.1 to 4.3 with MOAR 8.0 and everything was fine. If I reboot I can access TB again with no error but then next reboot the error comes back and so on with every reboot. Any idea why this happened and how I can fix it? Thanks!
[SuperSU] Prasad:
I believe it's a kernel specific issue I'm experiencing. I'll now try flashing superSU while on another kernel... Will report back shortly. :)

In any case, this is the TWRP log: http://pastebin.com/YJc8V26G

Confirmed: WORKING on stock kernel. :)
[SuperSU] Frank Westlake:
This is in your log:

cp: can't create '/system/etc/init.d/99SuperSUDaemon': No such file or directory

See if the directory 'init.d' exists in '/system/etc'. If not, see if you can create it with ADB after mounting /system as rw, but you will probably need to add a 'mkdir' statement to the install script in the install archive. This is just a hope.

If that fails, maybe one of the older versions will work.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] jazzruby:
99SuperSUDaemon contains the same line of code as install-recovery.sh to start the su daemon (daemons) but will only be used/installed if the kernel/system supports init.d directory.

-JR-
[SuperSU] Frank Westlake:
Thanks. An 'if [ -d' would avoid the error report and the misunderstanding.

Frank

ADDED:

For [MENTION=2961427]Prasad007[/MENTION], you can ignore my suggestion to check/create 'init.d'.

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] Prasad:
Guys, like I said in my last post, the issue is resolved... it was kernel specific :)
[SuperSU] gianmarco00:
I'm having the same issue on my HTC Evo 4G LTE. Never had an issue before and for some reason SuperSU zip doesn't want to flash in TWRP after installing the new Sense. Thus, no root and I can't access most things.

For whatever reason, it's just not playing nicely and I can't figure out why. Captain tried helping in another thread and the verdict was just a bad download.
[SuperSU] mutantkeyboard:
I don't know is it the new update for SuperSU or is Paranoid OTA, but my root access is completely screwed up. Basically I can't update binary any way. I tried to install zip from recovery (I use CWM touch and SuperSU Pro) but CWM aborts installation and says bad zip. I tried with older version 0.97 and it installs, but it can't update binary either. I tried downloading ChainsDD binary and installing it instead and it didn't work. The worse thing is that it shows the list of apps that require root access and it says "The app has been granted superuser permissions for interactive shell" but it doesn't work.

Any suggestions without involving factory reset or installing TWRP recovery?
[SuperSU] NZgeek:
If you're getting a bad zip message then perhaps you haven't downloaded the file correctly. Download it on a PC, then open it on the PC and make sure you can see files in it. The list of contents for a zip file are stored at the end, so it won't open correctly if the file is corrupt.

Once you've verified that the file opens correctly, copy it to your phone and try flashing it again. If that still fails, write down the exact error message and post it here.
[SuperSU] Super_Dork_42:
Look, I know you're trying to solve a problem here, but can we take a moment to celebrate being on page 500, and make a special thing out of the upcoming post 5000 please?
[SuperSU] sajju73:
Try un checking the respect CM settings option and reboot.
[SuperSU] Fallen Spartan:
No you didn't. Post deleted lol :p

Let's Stay on topic folks

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] mutantkeyboard:
Thanks

Thanks it did the magic... :)
[SuperSU] iwobanas:
How can I access root mount namespace on Android 4.2.2?

On Android 4.3+ --mount-master works fine because su is running in daemon mode, which leads to another question:

Why is daemon mode not enabled on Android 4.2.2?

Is there some way to enable it from the app? I could modify etc/install-recovery.sh and reboot the phone but that wouldn't be a best user experience and I guess this feature is not enabled on 4.2.2 for a reason so I'd like to know this reason before I go and hack with users systems.

Or maybe there is some alternative way to get access to root mount namespace?
[SuperSU] iamsuperuser:
[Help] Integrating SuperSU into custom rom

I made a small custom rom for Note 3 Exynos SM-N900 KitKat 4.4.2

After flashing everything is fine BUT the phone is not rooted.

I'm currently using the following lines and files in my rom

ui_print("Installing SuperSU");
set_perm(0, 0, 0777, "/system/bin/.ext");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 06755, "/system/xbin/daemonsu");
set_perm(0, 0, 06755, "/system/etc/install-recovery.sh");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");

When I open the SuperSU app I get the error message saying "SU binary in not installed etc....."

Please help
[SuperSU] egingell:
Those permissions for the executables are not valid.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] iamsuperuser:
Ok can you please correct me
[SuperSU] egingell:
You don't know and you're messing with it?

At any rate, 0755 - not 06755, which isn't even valid for anything - is for executable files.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
This is what the instsller uses:

0777 /system/bin/.ext

06755 /system/bin/.ext/.su

06755 /system/xbin/su

0755 /system/xbin/daemonsu

0755 /system/etc/install-recovery.sh

0644 /system/app/Superuser.apk

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] egingell:
Really? Then there's no reason it shouldn't work. Unless /system/xbin isn't in the $PATH or there's no /system/bin/su.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
These are missing:

0755 /system/etc/init.d/99SuperSUDaemon

0644 /system/etc/.installed_su_daemon

Also missing are some 'chcon' settings. 'iamsuperuser' should check ChainFire's install script.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] egingell:
[MENTION=4218294]iamsuperuser[/MENTION] needs to be a little more forthcoming with error messages and/or the whole install_script file and/or any other relevant files. Seems like he's missing a lot. One needs more than just file permissions to install a ROM... or even just su.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] jazzruby:
The 6 in that chmod command is for 'setuid' (UserID) and 'setgid' (GroupID) attributes on the file(s)

2 = setgid

4 = setuid

6 = setuid and setgid

-JR-

edit: http://en.wikipedia.org/wiki/Chmod#Special_modes
[SuperSU] egingell:
I know. I tired it after it was pointed out that it's in the current install script.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pug123:
Sorry for posting this here but couldn't find a discussion thread, I would just like to thank (And have donated) [MENTION=631273]Chainfire[/MENTION] (and others) for this Awsome work which in the years of using has never let me down, so thanks again and hope you remain at the top of your game for years to come..

Sorry again for this spam post.
[SuperSU] Scarface1991:
I have the same issue from time to time. Phone just becomes really warm and CPU runs at 100% clock speed at all 4 cores and a process called "daemonsu: 10206" is responsible for the most cpu load. The logs show that GMD Gesture control asks for root a lot especially at the time where that happens. Damn this is really bad news since this is one of my favorite Apps.
[SuperSU] ayoubij:
Bro i have the same problem as well. It say daemon process running cpu.
[SuperSU] Scarface1991:
Well it looks like GMD Gesture Control is responsible for this. I have written on the GMD Thread about this problem. Maybe the developer can do something about it.
[SuperSU] ayoubij:
will test without it now and see if this will be fixed. Didn't know apps that ask for supersu can do such behavior
[SuperSU] Scarface1991:
Me neither until I started investigating. Turns out that several other people already reported the same issue on the GMD Thread but I guess so far nothing has been done to solve that issue

Gesendet von meinem GT-I9300 mit Tapatalk
[SuperSU] NZgeek:
The 10206 says that the daemonsu process is running for the app with user ID 206, which in your case is GMD. Whatever GMD is doing as root is chewing up the CPU, and it's making daemonsu look guilty.
[SuperSU] Kappa Lamda:
One silly, noob question.

I use a rom that has intergrated superuser instead of SuperSU.

If I flash superSU-update.zip in recovery, will this remove superuser and give me SuperSU??? Am I right? Cause I always liked more the SuperSU instead of superuser.
[SuperSU] PiggySmalls:
It will switch it to SuperSU, yes. However, the Superuser tab will remain in the settings panel, as it is baked into the ROM. Simply don't open it.
[SuperSU] Kappa Lamda:
Ohhh yes. I was not expecting removing the option inside the settings. I just want SuperSU as it works better for me and wanted to see if I had any conflicts! thanks again.
[SuperSU] Chainfire:
N7100 NB4 4.4.2 leak force close fix

Attached is a v1.94 version of SuperSU for the N7100 NB4 4.4.2 leak that FC's on open.

This is not an 'official' release and it will not be spread through Play. Something about this firmware's framework doesn't play nice with Google's v4 support lib. This is definitely a bug in the firmware, I hope this firmware will not see official release from Samsung. Though this issue would occur with very few apps, this problem is not limited to SuperSU.

It is absolutely no use installing this version instead of the v1.93 release on any other firmware than N7100 NB4.
[SuperSU] Elzbach:
I have a similar problem. I also get the message "The app has been granted superuser permissions for interactive shell" but in the app itself it says that it still needs superuser permissions. BotBrew Basil is the only app that notifies me of this, but the problem is evident in other apps that need root access too. I have the option to respect CM root settings unchecked, and the option checked to display warning if permission.ACCESS_SUPERUSER permission is not declared in manifest.
[SuperSU] YOSEFE:
Chainfire,

thanks all the same.

---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------

Is this still the case after the 1.94 posted by Chainfre?
[SuperSU] Elzbach:
Unfortunately, yes.

My device is a Samsung Galaxy S4 SGH-1337, Android version 4.3, and I'm running CM 10.2-20130816-NIGHTLY-jflteatt if that helps.
[SuperSU] YOSEFE:
Thank you for sharing.
[SuperSU] wmarcin:
[MENTION=336807]YOSEFE[/MENTION] & [MENTION=5782136]Elzbach[/MENTION]: some apps also need busybox installed to work. If you've already done it, please disregard.

... Moto X VZW DE ...
[SuperSU] DF5JT:
I updated to 1.93 and everything works just dandy, except for actually becoming root through shell access:

adb shell
shell@jfltexx:/ $ su -
1|shell@jfltexx:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
shell@jfltexx:/ $

Is this ROM specific (Using AOSB 1.3.2 here) and what do I have to do to finally see '#'?
[SuperSU] Frank Westlake:
Shell access is through an application which gets root access the same as other applications.

The procedure for installing 'su' is device specific; use a forum for your device to learn how to install 'su'.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] DF5JT:
We have a misunderstanding here.

I get root in a shell on the device itself, i.e.e in a terminal emulator.

I do not get root through "adb shell"

Why?
[SuperSU] egingell:
Stock kernel? No direct root through the stock kernel. Use adb shell su -c COMMAND or type su when you get to the shell prompt.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
In SuperSU, search for a setting to respect your custom ROM's root settings. In device Settings, either under Developer Options or Security, there may be an option to restrict root to apps only. Changing one of those may solve your problem.
[SuperSU] dvdivx:
Flashable zip is still 1.93
[SuperSU] egingell:
It's not official. If you want 1.94 in the zip, open it up and drop in it where 1.93 is and rename as needed.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] DF5JT:
Bingo!

Thank you so much! :good:
[SuperSU] dvdivx:
Problem with that approach is there are two su files. One in the arm folder (not counting the x86 folder since my chip is not an x86 chip) and the apk file in the common folder. If the actual superuser file changed I'm pretty sure the su file would also change.
[SuperSU] egingell:
Extract them from the APK. It's just a zip file with a different extension.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] jazzruby:
1.94 is a fix/patch for a specific firmware:

Having said that, it appears the assets/binaries haven't changed so you should be good with drop-in/replacement of just the Superuser.apk

-JR-
[SuperSU] igoivo:
Please, also make fix for GT-N7100 DLK7 (4.1.2). It's force close due to the appearance of the empty entry in the list of rooted apps.

I am not sure that it is firmware error.
[SuperSU] egingell:
Have you tried clearing the data of SuperSU?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] igoivo:
Of course, many times. But the empty entry reappears after couple days. The log says nothing since it is empty entry.
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], how come version 1.94 is already available on the interwebz but is neither featured here, nor in Google Play? Never mind, just discovered your announcement. All cleared up. You still rock and I refuse to use anything else but SuperSU. ;)
[SuperSU] Rinoceros:
Those files might be suspicious, because they have also the license file for the pro version...

BTW what is a couple of bucks to support Chainfire for the Pro version?
[SuperSU] Chainfire:
It's probably a bug in SuperSU combined with some root app you are running (or a call made by the firmware). Unfortunately, there is absolutely nothing I can do about this until I can replicate the issue.

I do have an N7100 though... So if, for example, you'd make a CWM/TWRP backup, then clear out all personal data (accounts, app data, etc), then make sure the issue keeps occurring (clear SuperSU's data first, then see if it happens again), then make a second backup, and send me that second clean backup (after which you can restore your first backup, getting your phone fully operational again), then I would be able to reproduce and fix the problem.

I know, sounds completely overkill, but this issue has been popping it's head occasionally for over a year, and I really would like to fix it somehow.
[SuperSU] igoivo:
You could make an additional check to prevent writing an empty entry in

/data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml

file.
[SuperSU] Chainfire:
This only treats the symptom, not the cause.
[SuperSU] igoivo:
As a user, I don't care on the way how you will fix your app.

I am tired to fix it manually each couple days.