yashsingh1/xdaforums huggingface dataset:
[SuperSU] MikeRL100:
I've just installed 2.00 on my Nexus 5. Don't let the lack of a major UI change fool you, this is a Superuser management tool, not a pretty app that's broken under the hood. Who needs a new UI when the current one works well enough? Starting with 1.99r5 I haven't seen a "silently denied" error at all. I would've said something earlier, but I wanted to test things over a few days for good measure. All the more critical issues from the betas or 1.99rx's or whatever you want to call them seem to be gone. About halfway through the 1.99's roughly I donated. I can't even begin to imagine how tricky it must've been to overhaul things under the hood to not only be compatible with future major changes in AOSP Master, but also the already existing Android versions. Add to that crap like Knox that is the spite of any root app developer. Great job Chainfire! The work of a true professional!

P.S. Minor UI issue. Try tapping an app in the first tab. Then long press some of the buttons. In my experience, you can get a cursor to come up along with the option to paste. I don't know 100% how to reproduce it, and I cannot get a screenshot since the cursor disappears quickly, and yes this is minor, but it just looks a bit odd. It's the king of papercuts it's so minor. But yes IMHO it's a bug of trivial importance. But a bug nonetheless.
[SuperSU] tvisforme:
I'd like to make one suggestion for a enhancement. It would be helpful to be able to select apps that appear in the log and add them to the Apps page.
[SuperSU] brunodu91:
V2.00 is run as well on i9505

Envoyé de mon S4, via tapatalk 4 Vip .

Slimsaberkat 4.4.3 released...., alucard Kernel , buzz launcher , modem ET bootloader NC4.
[SuperSU] trd360:
How can I get the zip file onto the phone to flash? My N5 won't show up on my computer through USB because it's stuck in bootloop
[SuperSU] Blac Caesar:
What apps are logged as requesting SU but aren't in your apps list? [MENTION=631273]Chainfire[/MENTION], I thought any app that's requested SU privileges would be listed on the first page.. just looked thru my log, all the apps that requested SU are listed on the first page

#KCCO.. PARANOID four.Four.Three Nexu5
[SuperSU] Pkt_Lnt:
Odd. I just went through my 3 day log and there is nothing in there that is not already in the apps tab that I have granted access.

---------- Post added at 10:48 AM ---------- Previous post was at 10:47 AM ----------

ADB Sideload in recovery.
[SuperSU] trd360:
When I try to sideload through recovery, I get an error:closed message

edit: Fixed it by pushing to the phone and flashing with TWRP...but I'm still stuck in bootloop
[SuperSU] culson_35:
Update to 2.00 everything OK... Stock rom, ktoons kernel, xposed....
[SuperSU] JerryGNYC:
Wanam Xposed still working as it did before updating to 2.00. Sprint GS4 with 4.4.2 (NC6).
[SuperSU] JVital2013:
I've run into a bug with SuperSU 1.99r4-2.00. When I open SuperSU and tap on one of the app settings, the popup comes up but the app goes away and shows whatever launched the app, be it the play store "open" button or the app drawer. Also, when I close the SuperSU, it snaps back to the home screen in an awkward way. I demonstrated the problems here: https://drive.google.com/file/d/0BxfeLGNBuP9LbmU2ZUkzMGRmYVk/edit?usp=sharing

I'm on a Nexus 4 with stock 4.4.3 and GNL
[SuperSU] jkeuclid:
Updated to 2.00 via store and happy to report all 5x5 on my SGS4A SGH-i537
[SuperSU] ziggyyy:
update to 2.00 worked perfectly! thanks!
[SuperSU] GroteBozewolf:
Exact same issue here. After granting an app root access, the previous active app gets focus, not the one that asked for root.

On Stock 4.4.3, Nexus 4, SuperSu 2.0
[SuperSU] Thomas_BA:
Updated from beta 4 to 2.0. Working well, did not asked for binary update.
[SuperSU] fifo209:
[Q] how to install SuperSU via rooted adb shell (not via recovery)

[Q}

I have a similar question and reading through the forms (and Google) this looks to be the best place to post it. I apologize in advance if this was asked and answered but in spite looking, I can't find the answer anywhere.

Here is my problem.

1. The device I am trying to install the SuperSU is a developer unit. I have Root / Remount access via adb from my computer.

2. I can NOT install custom recovery on this unit even though it is a developer unit because I am testing a 4.4.4 and the GPT on it is different, so no TWRP or other recovery image will run on it (.)

3. I have a rooted 4.4.3 device I was able to dump the system partition off of, so I have a working SU and other bin, as well as all the scripts used by SuperSU when installed via recovery on the 4.4.3 unit.

3. I tried to push and set permissions based on older patches I made for 4.2.2 and earlier and based on modified info posted by Frank here (thanks, Frank)

Here are the commands I am sending:

adb shell mkdir /system/bin/.ext

adb push .su /system/bin/.ext/

adb push su /system/xbin/

adb push daemonsu /system/xbin/

adb push install-recovery.sh /system/etc/

adb push Superuser.apk /system/app/

adb push .installed_su_daemon /system/etc/

adb shell chmod 0777 /system/bin/.ext

adb shell chmod 06755 /system/bin/.ext/.su

adb shell chmod 06755 /system/xbin/su

adb shell chmod 0755 /system/xbin/daemonsu

adb shell chmod 0755 /system/etc/install-recovery.sh

adb shell chmod 0644 /system/app/Superuser.apk

adb shell chmod 0644 /system/etc/.installed_su_daemon

(I could not find the 99SuperSUDaemon on my 4.4.3 (could this be my problem?)

when I am done pushing and changing permissions with no errors, I restart the device then, when I lunch SuperSU it prompt me to update the SU binary and give me the option for Normal or Custom Recovery. As I mentioned before I can not use the Recovery option so I select normal.

it try to install, then fail then prompt me to restart.

any way to get this working please?

Thanks,
[SuperSU] Frank Westlake:
[MENTION=3652984]fifo209[/MENTION]:

==========

EDIT:

NO, YOU CAN'T DO THIS!! The script deletes the binaries that are giving you access to root. But I'll leave what I have written because you might be able to modify it to work anyway.

==========

I'm not an expert at any of this yet but chainfire might not have time to reply.

You chose stock Recovery because you do not have a custom Recovery and it failed because the zip archive does not have the signature that the stock Recovery wants.

Maybe you can do all this in the root. Extract the script from the archive (META-INF/com/google/android/update-binary). It isn't binary. I think you need only modify the first 6 lines below the first line. Ignore OUTFD but change ZIP to the archive path and change the 'echo' statements to simply echo.

==========

OUTFD=$2

ZIP='path to your zip archive';

ui_print() {

echo "$1"

}

==========

With the device booted into Android use a terminal and go to root (/). I don't think we have /tmp so you might need to mount it or just make a '/tmp' directory in root. So you might need to 'mount -o remount,rw /' to do that before running the script, then run the script.

I have not tried this and I have not examined it closely.

Frank
[SuperSU] Chainfire:
You can extract the su binaries from the download zip ( http://download.chainfire.eu/supersu ). Use 0755 instead of 06755. You're also not setting the correct chcon's as provided by the script (check the update-binary file from the ZIP, it's a shell script). Nothing is publicly known about 4.4.4 so I cannot comment on specifics beyond this. Perhaps we can talk in private if you trust me enough - though I have to warn you for the next two weeks I'll mostly be out of the country and have very little time to directly assist.
[SuperSU] Murshad007:
I have updated it from Google play, 194 to 2.0

Opened, binary need to updated.

Normal install

Binary failed..

Reboots

Open and check install as system

Reboots, cleans

Tried again

Reboots. Uninstalled automatically

Reboots by me and Enjoying..
[SuperSU] jrbxx7:
Thanks chainfire!

TaPpEd from my XpOsEd 4.4.2 NIII
[SuperSU] triathlete66:
No Problems with Update 2.0 on 4 Devices with different ROM's

Thanks for good work :good:
[SuperSU] sinisin:
Had it installed in /system per app before 2.00. 2.00 update comes. It's now in /data and won't install to /system and shows the backup script is installed. Gonna try to uninstall and reinstall the app. If that doesn't work, I'll full unroot it reroot with Philz and reinstall from Play.
[SuperSU] ceza1380:
Is it even possible that SuperSU effect about that i have a problem with Active Display? It doesn't turn on screen when pocket mod enabled?
[SuperSU] killoid:
@Chainfire i've enabled re-authentication option but when i uninstalled an app,it's permission was still present in supersu.re-installing an app doesn't call out supersu pop-up too. i am on v2.00 & my device is galaxy y duos,stock 2.3.6 rom.
[SuperSU] bill1clinton:
Am I the only one with this issue? Any assistance is appreciated.
[SuperSU] bigpp85:
Apps like gamekiller or gamecih2 stoped working with new SU 2.00 :/
[SuperSU] adrianflo:
Updated via Play Store and Recovery ..... still doesn't work. Keep asking for binary update and reboot ( HTC One M8 ). this update is a nightmare :
[SuperSU] G.M.L:
LG L3 E400 with ICS 4.0.4

Working normally!!!!!!!

G.M.L._V7

http://pasakalis.blogspot.gr
[SuperSU] jeswinjv:
Yes u can....

By deltng old versn n flashng new version or nothr....:)

via XDA Premium developer's-app
[SuperSU] fifo209:
Chainfire, Frank,

First let me say THANK YOU !! you help make this fun (as well as working).

When I grabbed the files form my 4.4.3 I assumed they were the same as the files in the SU-v2.00 update pkg since I just updates the 4.4.3 before I dumped the system. but tunes out it was not. (Note to self, when in doubt, use beyond compare).

Taking Chainfire's advice, I grabbed them directly from the UPDATE-SuperSU-v2.00.zip. As recommended, I also changed the chmod to 0755, created the missing folder in the system, grabbed the missing demon99 from the UPDATE-SuperSU-v2.00.zip and pushed it in to /system/etc/init.d/ then changed mode.

This did it. When I lunched SuperSU it did not ask to update (I assume, since the binary is now the latest) and just worked out of the box.

I now have a stock 4.4.4 with SuperSU running on it. :victory:

Thanks again !!
[SuperSU] toinktoink:
anybody experiencing lag when taping "grant" or "decline"?

i have note 3 and rooted via towelroot, i run cleanup and redownload 2.00 and it's still the same. and also updating binary before is also slow.
[SuperSU] bill1clinton:
Glad it worked out for you! However, I do not have the technical expertise to achieve this. I have already tried to flash the UPDATE-SuperSU-v2.00.zip directly from CWM. That did not solve my issue. Is there another fix? Thanks.
[SuperSU] Pkt_Lnt:
You need to get a logcat for [MENTION=631273]Chainfire[/MENTION] if you want help.
[SuperSU] :
Is this some sort of typo or are you a Google employee???

4.4.4??? :cyclops:

Is 4.4.4 in the pipeline, the next release???

Can you shed some light please??? PM me if you want... :fingers-crossed:
[SuperSU] Pkt_Lnt:
Read this.

http://xdaforums.com/showpost.php?p=53506255&postcount=5815

Developer units come with a serious NDA. Just forget you saw it.
[SuperSU] Frank Westlake:
That's the second time you have done that; lunching SuperSU is not permitted - it is a violation of the user license. You may consume it as super, but not lunch.

Frank

---------- Post added at 09:31 AM ---------- Previous post was at 09:26 AM ----------

I think someone here said that CWM won't install SuperSU and that you need to use TWRP.

Frank
[SuperSU] bill1clinton:
[MENTION=218722]frank[/MENTION]: unfortunately, I tried flashing with TWRP as well and that still did not work.
[SuperSU] nexusmaniac:
If your talk of 4.4.4 is truly real and you are running a nexus 5 fell free to do a system dump ;) Would love to check it out as you've already (If you're being serious about 4.4.4) broken the crazy NDA that you would need to sign :D Thanks!
[SuperSU] aavvaallooss:
https://developers.google.com/android/nexus/images
[SuperSU] USBhost:
Then no NDA
[SuperSU] loveninecube:
I can't download UPDATE-SuperSU-v2.00.zip from CF-Root download page, what happened? :confused:

If I download zip file, network error happend every time.
[SuperSU] jong31:
Working here...
[SuperSU] 72off:
Moto G Error

the new update does not work on my Moto G

or supersu keeps loading forever or it says that i have to update binary

if i click on Update is will after a while say that it failed and that i should restart my phone

if i click cancel it will just close

I'm using the "tethered" Root,so if i restart my phone i have to root again [and i did]

and it keeps saying that need to update

Even reinstalled from playstore but no succes

[if no solution,please give me the old .apk]
[SuperSU] Strephon Alkhalikoi:
Device: Dell Streak 5

OS: Cyanogenmod 7.2 (Gingerbread)

Problem: Prompted to update su binary repeatedly

Expected Behavior: When updated via the Play Store, app should only ask to update the binary if the binary has not already been updated. If updated through Clockworkmod or TWRP no prompt to update the binary should appear.

Actual Behavior: Regardless of how SuperSU is updated, the app asks to update the binary every time it's opened. This occurs even if the correct binary is already installed. The update fails and the app closes, yet granting access to apps is still possible.

Additional Details: Only occurs on Gingerbread. My ICS tablet updated through the Play Store without trouble. I suspect a bug in the app as the binary itself appears to function properly. When feasable I'll provide a logcat.
[SuperSU] :
[MENTION=5639583]72off[/MENTION] Here you go....

v1.97 http://download.chainfire.eu/416/SuperSU/UPDATE-SuperSU-v1.97.zip

v1.94 http://download.chainfire.eu/396/SuperSU/

Flash any one of these through CWM/TWRP....

You will get permanent root on your falcon....

Tested working here on mine... Even v2.00 works fine for me....

Hope this helps... :good:
[SuperSU] remo0073:
On my Moto G with Android 4.4.3, new version SuperSU 2.00 works fine...

Inviato dal mio XT1032 utilizzando Tapatalk
[SuperSU] verny94:
ChainFire: Can I help you with translating to Czech Language?
[SuperSU] xlollomanx:
Flashed SuperSU 2.0 on Galaxy W with CM11 with 4.4.3. Supersu doesn't show superuser granted app even the logs, it stuck on continuous loading. It shows just sometimes if I do a wipe cache and dalvik.
[SuperSU] betulin:
Xperia M c1905 15.4.A.1.9 JB 4,3

Hi guys, I've used towelroot APK by GEOHOT and UPDATE-SuperSU-v2.00.zip chainfire.eu. It worked and the phone is rooted without rebooting. The problem comes up when the device turn off, manually or (I don't know why) after using TA backup to uninstall any apk. The phone begins to restart, appears SONY logo, then XPERIA and finally waves but suddenly turn off. A reboot loop starts over and over again, sometimes 3, 4 and up to 7 times until finally, it manages to restart normally. I've noticed that sometimes the loop stop by pressing the power button. Any help or suggestion? Thanks

Xperia M c1905 15.4.A.1.9 JB 4,3
[SuperSU] Strephon Alkhalikoi:
I'd recommend going back to the last version that worked for you. Because of the issue I'm having on my ancient beast of a device, I've told the users of my PseudoCream ROM to uninstall the update and set SuperSU to not auto-update in the Play Store until this is resolved. The ROM came with 1.94 already included.

On a side note, I might have to try updating just the binary through recovery, just to see if it works. :)
[SuperSU] Lord_Flaya:
Anyone using motorola defy that can confirm last working version? Currently on 1.94.
[SuperSU] GroteBozewolf:
Any word on Android 4.4.4? Will SuperSU still work with it?
[SuperSU] jacknicholson:
Flashed the latest zip after updating on my N5, and all is well as expected.
[SuperSU] Yeti47:
Works for me. On cm11 (4.4.4) with SuperSu V2.00. ☺
[SuperSU] Persechini:
Everything perfect. Just took the opportunity to flash the 4.4.4 factory images on my nexus 4 and nexus 7(2013), rooted with towelroot and installed supersu from play store, couldn't be easier :good:
[SuperSU] 78Staff:
working great here, details below.

oddly enough, with 4.4.4 all the sshdroid/ftpdroid issues I had been posting about on 4.4.3 went away :).
[SuperSU] Razzzzer:
pro not recognized + disable knox spins/locks supersu

Howdy kids,

did a bit of searching but couldn't find the solutions to these two issues.

I purchased supersu pro..

but when I go to supersu it doenst appear that the pro is unlocked (still tells me to go pro), click on the link in the app to go pro and takes me to the store which only option is uninstall.

tried to uninstall everything and reinstall

tried to clear app data...odd

other thing is that on my Verizon s5, it doesn't seem to be able to disable knox. just spins on that option. reboots and tried again multiple times... USB debug mode is off.. (someone mentioned this in a thread)... not sure what to try next.

any tips would be appreciated!

thanks!
[SuperSU] koolboyztn:
when it ask to update binary, select TWRP/CWM then turn off yr phone and boot into Recovery mode, it should update yr binary, if not try to that couple times then it will update.
[SuperSU] codified:
I don't think this is related to SuperSU. I had the same issue on my stock Z1 Compact. Holding volume up +power for three seconds will break you out of the bootloop. A software update to 4.4 may fix it more permanently for you
[SuperSU] Skyrocket2:
Did you update through Play Store?
[SuperSU] 72off:
Thanks [MENTION=5879883]g33kparineeti[/MENTION] and [MENTION=4874684]koolboyztn[/MENTION] for support

I don't have a custom recovery because that would void my Motorola Warranty [unlocking bootloader]

i tried adb sideload the 1.97 and it failed

but i opened the .zip and found the .apk

uninstalled supersu and installed the older version and rooted again my phone [tethered root by jcase for Moto]

now,i can grant/deny applications

If i try to open the superSU application, it still wants me to update the binary

ond my only option is continue or cancel [ no TWRP/CWM maybe because i dont have them ]

so I can't manage old permissions

Thanks

it's not perfect, but way better

thanks in advance for any other tip
[SuperSU] :
[MENTION=5639583]72off[/MENTION] Sorry there seems to be no other solution....

I think you've got to flash custom recovery sometime... coz the tethered root method you said works only on 4.4.2! :eek:
[SuperSU] The Gingerbread Man:
Regarding su v2.00 on nexus 5 and nexus 7 (2013 WiFi only) both running stock 4.4.4 factory image SU pop up message to grant / deny SU permissions for apps are very slow initially to the point where I thought SU isn't working. This was on 1st couple of boots after flashing factory images. Essentially loosing root after flashing system.IMG and then booting back into android after flashing SU in recovery. Just to be clear I don't mean toast notification messages when apps have been granted, I mean the actual pop up asking for SU. After apps have SU permissions when you grant it they all work fine, just the pop up request took a very long time and wasn't sure if root was working.

I fastbooted the factory imgs for both devices, the entire lot apart from userdata.img, flash twrp, flash SU 2.00 and reboot.

The first boot I couldn't get root at all (both devices). I left my devices a good 3 or 4 minutes and opening root apps which I was hoping would trigger a SU request pop up, the apps just hung and didn't load.

Flashed SU again and had the same but after a while SU requests decided they would work again, after granting root to the pop ups root was working fine. I now have both devices rooted. Not sure why it took so long for my devices but I thought I should report this here.
[SuperSU] bokagavrilov:
I think that's a normal behavior I always get that too ... It's been since 4.4 that's like that after a factory image (normal roms are fine I guess) compared to 4.3 times it boots a lot slower.. But I guess that's Off-topic
[SuperSU] ErMeglio:
Hi, since last 2.00 I can't get it to be installed back as a system app. Nexus 4, 4.4.3. The problem is supersu stays forever in the "installing in /system" window...

Ideas?

[EDIT]

OK, a reboot fixed this issue.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[SuperSU] JulGer01:
Hi there, I'm on the latest cm11 nightly. My question is, can I flash the new superSU over the included superuser? Just flash in recovery (cwm)?

Gesendet von meinem GT-N7000
[SuperSU] Pons:
Yes.
[SuperSU] JulGer01:
I'm asking because I tried it several weeks ago. Flashed the older build in recovery. But I lost superuser privileges after that. I'm afraid this will happen again.

Gesendet von meinem GT-N7000
[SuperSU] The Gingerbread Man:
Sorry what I meant by prompt was the actual pop up su request, not the toast notification when apps receive su granted. I don't use ROMs so I wouldn't know about boot times being different but I know kit kat takes longer to get its self organised than jelly bean did. I'll try to edit my post to be clearer about what I meant as you mis understood and maybe chainfire might too.

Edit

Edited prev post to try to be clearer
[SuperSU] bokagavrilov:
Sure.. True I can confirm this too on my n4 and n7 2013
[SuperSU] betulin:
Hi bro, thanks. Here I've found http://xdaforums.com/showthread.php?t=2784638&page=3., This worked for me

Thanks
[SuperSU] 72off:
Yes, tethered have some problems but I will keep my warranty for more 5 months

I know 4.4.4 is out, but 4.4.2 is okay for me

Couldn't SuperSU just deal with the old binary and let me use his GUI?

The "old binary" was just "binary" for 1.97 and now 1.97 wants the "new binary"

1.97 was at least one week older than 2.00 right? If so, it must be using internet to check binary

#Edit

What was the last play store version before 2.00?

Maybe I'm looking at 1.9x but should use 1.8x or 1.7x
[SuperSU] remotehugger:
not sure if you can help me - whenever I flash something, I get a message that says to please update to latest binaries - when I updates SuperSu it said it successfully did update to latest - i have un and reinstalled a few times but i still get that message - any ideas ?
[SuperSU] gorilla p:
I would recommend flashing the latest TWRP recovery, doing a clean flash of your ROM, flash latest SuperSU (2.00) and go from there.
[SuperSU] edgarf28:
Does anyone know a way how I can see if the context (chcon's) of the supersu files are set correct?

I want to see if they're set correct in my own rom.
[SuperSU] Tungstwenty:
Just run "toolbox ls -Z /system/path_to_file"

You can double check the files present on the zip for 2.00:

ch_con /system/bin/.ext/.su
ch_con /system/xbin/su
if ($SUGOTE); then
ch_con_ext /system/xbin/sugote u:object_r:zygote_exec:s0
ch_con /system/xbin/sugote-mksh
fi
ch_con /system/xbin/daemonsu
ch_con /system/etc/install-recovery.sh
ch_con /system/etc/init.d/99SuperSUDaemon
ch_con /system/etc/.installed_su_daemon
ch_con /system/app/Superuser.apk

They should all be "u: object_r:system_file:s0" except for sugote (if you're on Android 4.2+), which should be "u: object_r:zygote_exec:s0"
[SuperSU] remotehugger:
i did that day before yesterday - im using the latest philz, that shouldnt matter should it ?

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] Pkt_Lnt:
Last Play Store was 1.94, link posted just above.

http://xdaforums.com/showpost.php?p=53538199&postcount=5844
[SuperSU] gorilla p:
Ehhh possibly. I've heard mixed reviews on that one and I believe it is CWM based. CWM has fallen behind drastically after 4.4 and there has been a mass exodus to TWRP for those who hadn't already switched. (I'm included in that group). Switch to TWRP. There's no reason not to.

If you want to do it quickly and easily, just install goomanager from play store, select options, select 'Install OpenRecovery Software".
[SuperSU] Pkt_Lnt:
TWRP is just not available for some devices when CWM is available. I face that with my Samsung Galaxy S4 Active International.
[SuperSU] :
The last Play Store version before v2.00 was v1.94....

v1.97 didn't get a Play Store release.... :good: