yashsingh1/xdaforums huggingface dataset:
[SuperSU] martytoo:
I searched forum but didn't find the problem I am having with SuperSU 2.00 listed anywhere. I installed 1.99 on my rooted Verizon S5. This works fine but the PlayStore lists 2.00 available as an update. Twice I have updated and twice I have uninstalled 2.00. In both cases the phone took more than twice as long to boot up with 2.00 as compared to 1.99. I run "Android Assistant" which reports boot time in the notification bar, but even without this objective measure it is obvious that it takes more than twice as long to boot with 2.00 installed.

I think this may be because the binaries don't install with 2.00 but I don't really know if this is the case. There is no notification to update the binaries and I don't know how to update them manually. Furthermore the "Custom" message shows on the boot screen with 2.00 and not with 1.99.

This isn't a big deal except that there is the nag to install 2.00 every time I go to the Play Store.
[SuperSU] :
Try flashing the SuperSU zip through recovery...
[SuperSU] remotehugger:
should I uninstall SuperSu before flashing the zip or doesnt it matter ?

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] 72off:
I'T WORKED

Uninstalled 1.97 and installed 1.94,checked root apps and was OK,

Opened SuperSU and it asked again to update binary :crying: ,

was going to close the app but decided to let it try to update for the last time ...

15 secs latter it have been updated :D

Many many thanks for the community

Tip for Motorola users with tethered root by jcase pie

Use SuperSU 1.94 and disable Google play update, should work like a charm
[SuperSU] Pons:
Doesn't matter. The zip will either replace the existing SuperSU, or add it if it's not there. For simplicity, I'd say leave it.
[SuperSU] camerona:
I started an official bug report on this issue https://jira.cyanogenmod.org/browse/CYAN-4447 Please post your log cats.
[SuperSU] :
[MENTION=5639583]72off[/MENTION] Glad that it worked... :)

Be welcome and remember you too can keep contributing to the community by helping someone else next time... :good:

[MENTION=4529281]remotehugger[/MENTION] It won't matter, but I'd advice flashing the zip to update/enable SuperSU... :good:
[SuperSU] keneth_c:
Yes... As u r using CWM.

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[SuperSU] :
You're using Nexus 5 and stuck with CWM!!!

Dude, take my 2 cents of advice and move on to TWRP.... Its much superior to CWM...

As for SuperSU, move to the latest version i.e. v2.00 and forget about incompatibilities and bugs.... :good:
[SuperSU] martytoo:
Is this possible with a Verizon S5? I have read that installing a CWM recovery on this phone will brick it.

Is 2.00 available as a zip to download?. I would like to try to install it without using the Play Store.
[SuperSU] Pkt_Lnt:
That is a question for your phone forums.
[SuperSU] martytoo:
I already had the answer from there. It is in my question. The advice is that it will brick the phone. I wondered if there was something I was missing.
[SuperSU] :
Well, then custom recovery is not a option yet...

For you're phone the safest option is to root through towelroot....

Here's the link... http://towelroot.com/

You will get the instructions there...

After you've rooted this way successfully, install SuperSU through Play Store and you're good to go...

Hope this helps... :good:
[SuperSU] martytoo:
I am rooted. As I said I installed 1.99 manually with no trouble. When I let 2.00 install over 1.99 by using the Play Store 2.00 caused the phone to boot extremely slowly and I could not fix this without manually installing 1.99 after uninstalling 2.00
[SuperSU] :
I should say you must go to SuperSU and select cleanup for reinstall option in settings...

Then try installing SuperSU v2.00... :good:
[SuperSU] martytoo:
You were correct. Thanks. :good::fingers-crossed::good:
[SuperSU] remotehugger:
sorry to keep asking questions guys, but should I run the cleanup for reinstall before flashing the zip since I already have SuperSu installed or isnt that necessary ?

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] Pkt_Lnt:
Not necessary
[SuperSU] :
Not necessary at all unless you experience any slowdowns in the performances of SuperSU...

I would say you go forward and flash that zip through recovery.....

If you're afraid of anything going wrong, create a NANDROID backup, i.e, backup through CWM/TWRP before flashing the zip... :good:

But since you're running tethered root and don't have custom recovery this isn't an option for you yet...

If you've got any more questions feel free to ask... :)
[SuperSU] keneth_c:
Go to chainfire's website to see if your phone is supported. I don't see why it won't be.

SuperSU latest version zip is always at:

http://download.chainfire.eu/supersu

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[SuperSU] volkmadi:
Soft reboots solved?!

Hi,

I have a question (no criticism!).

In I9505XXUGNE5 to disable knox app leaded to soft reboots, I found a workaround and let knox app enabled.

Now in 2.00 when you open the supersu app it still proposes to disable the found knox.

My question is, are the issues around soft reboots through the disable of knox app soved and can/should I use the feature in supersu app?!

Is there a restore function in supersu if I use the feature and face soft reboots again?!

Ps: I'm now on I9505XXUGNF1.

Thx!

Dirk
[SuperSU] mrQQ:
I have reboots on NF1 even without SuperSU installed :( now I installed it and let it disable KNOX, will see how it goes..
[SuperSU] exodius48:
of course
[SuperSU] Nasvyazi:
SU binary needs to be updated - no luck

I'm unable to update SuperSU binary. I tried all 3 known methods with no luck.

I created a separate thread for the problem before I found that I can post in this thread.

Here is a link for the thread:

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

Please help!!!
[SuperSU] remotehugger:
thank you - one more question - lol - do I need to uninstall my pro key before flashing the SU zip ? and thank you again for all the assistance !!

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] :
Nope, you don't need to uninstall the Pro key if you've got the normal SuperSU app in your app drawer....

Just go forward with the flash....

Don't worry... There won't be any apocalypse... :laugh:

Mention not... :)

Remember to provide assistance to someone else next time... ;)

That's the beauty of community...
[SuperSU] :
Hi,

I'm getting the force close issue on the recent 4.4.2 KitKat release (T310XXUBNE9) for Galaxy Tab 3 8.0, I initially used 1.93 zip which FC's, I then updated via the Play Store to SuperSU 2.0, that opens but it never updates the binary.

Tried flashing SuperSU 2.00 zip through TWRP, rebooted but it never updates the binary, I say yes to disable KNOX then it says installation failed.

Although root apps do seem to be granted root permissions via the popup.

Any thoughts?

EDIT: At last, installing/updating the binary via TWRP/CWM option instead or Normal works, now I can access SuperSU, one question though will that always be the case for future updates to Supework?

EDIT 2: Well that was short lived, after another reboot SuperSU is stuck in an endless update binary situation, Normal method fails and TWRP/CWM appears to do nothing as its still saying it needs to update, had to wipe & reflash to get rid as no matter what I did didn't seem to work. All roots apps still work and request access, its just SuperSU keeps wanting to update the binary so I can't access the app.
[SuperSU] remotehugger:
grrrr.....lol - still getting the "please update binaries" everytime I flash something - ive reflashed rom - tried playstore SuperSu and flashing the zip - when first installing it asks to disable knox then update binaries - i choose to update the normal way - it says everything is successful - and I have no problem with SU permissions - I just always get that notice when I flash something - it doesnt seem to be hurting anything but it leaves me feeling like im broken - lol -

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] camerona:
I know I will eventually the only thing holding me back is the incompatibility with Cyanogenmod updater and Twrp . On another note I just got my ten required posts and god it feels good to be able the post in the dev forum:p
[SuperSU] jazzruby:
After a successful binary update, open/run Terminal Emulator:

su -v

should return:

2.00:SUPERSU

Flash something and boot back into system and (re)run the above command

[MENTION=631273]Chainfire[/MENTION]

Line 132 has a TAB at EOL

cp $BIN/su /system/xbin/sugote

Just sayin.....

-JR-
[SuperSU] Siutsch:
frequent reboots

I have the same issue with my S4.

Rooted last week and have reboots several times a day (if I notice them), Samsung Logo and lock screen (NO SIM card PIN).

I only rooted, Knox is still 0x0.

Tried everything I can:

- removed every app from SuperSU Apps list

- deinstalled every app, that needs root (SuperSU 1.99r4, AdAway, Root Checker Basic, System App Entferner)

- installed again (new version of towelroot and SuperSU 2.00)

- cleaned dalvik cache with Titanium Backup

- cleaned temp-data from recovery

- removed and reformatted SD Card (Samung SD card)

- disabled dynamic background (I used Earth HD Free since the beginnig of time ...)

- changed launcher (I use Action Launcher now which is great)

- some other things I can not remember ...

I have no idea what triggers these reboots and how to find out.

BTW: Is it possible to unroot with SuperSU?

I have not yet dared to try it.

Towelroot can't do this itself (yet).

It might be interesting to see if the reboots stop when the device is not rooted anymore.

Siutsch.
[SuperSU] mrQQ:
I've tried to leave the phone connected to PC and logcat running, however, for some reason, logcat stops after few minutes? Chainfire, do you have any idea as to why?

Also - when SuperSU asks to disable KNOX - what exactly does it do? Can it be undone?

Thanks.
[SuperSU] remotehugger:
thank you - i get the 2.00:SUPERSU return both times - but still get the "please update to latest binaries" when flashing something - so dang odd - and that's with both the latest TWRP and with the latest philz - I'm starting to think its a 4.4.2 issue - or at least a VM/Boost 4.4.2 issue - although I haven't seen anyone else having this problem - :confused::mad:

VM SIII - jdsingle76's deodexed NDC 4.4.2
[SuperSU] :
Go to SuperSU>Settings>Cleanup>Reinstall... Select reinstall then reboot your phone...

Then flash the latest SuperSU zip from recovery...

Hope it solves your problem, else report back ASAP...

Hope this helps... :good:

---------- Post added at 08:59 PM ---------- Previous post was at 08:55 PM ----------

Both of you try what I've said above and report back ASAP...

This will most probably solve your probs... :good:

---------- Post added at 09:02 PM ---------- Previous post was at 08:59 PM ----------

Try what I've advised above and report back ASAP....

Hope this helps... :good:

Yup, it's possible...

Go to SuperSU>Settings>Cleanup and select full unroot and after the process completes reboot....

See if it stops those reboots but if you've followed what I've said above I don't think this would be necessary at all... :good:
[SuperSU] Nasvyazi:
I cann't even enter setting in SuperSU or use any other function.

It just displays a popup "The SU library needs to be updated" and SuperSU exits if I click Cancel. Otherwise when I click Continue it continues with SU binary install and reboots the phone to recovery, installs a zip, reboots with no effect. SU needs an update again.

I've also installed a SuperSU 2.0 zip update from recovery which made no effect. SU library needs an update again.
[SuperSU] :
Same here, done the same thing.

SuperSU won't allow you to enter the app until you update the binary which we can't do.
[SuperSU] Frank Westlake:
If the binaries are there and you have root access with a terminal then try the script at the bottom of this message, then reboot. You should see "Android is upgrading...". The script mskes a '/tmp' directory then runs Chainfire's installation script in the zip, which in turn installs the binaries. You'll probably see a bunch errors because Chainfire's installation script tries things that might not exist on your device. I'm just curious to see if installing through system will be different.

Frank

EDIT:

Script deleted.
[SuperSU] bimmerdriver:
I have a question specific to the Samsung Galaxy S5. What happens if you install SuperSU after using towelroot and you do not disable knox? Does knox detect that the phone has been rooted and "do something" about it?
[SuperSU] :
AFAIK, towelroot doesn't knock KNOX.... There's no way to detect your phone's been rooted....
[SuperSU] LEENO:
same random reboot problem with last NF1 (knox 2.0)

Stock Rom

AP: I9505XXUGNF1

CP: I9505XXUGNF1

CSC: I9505OXAGNF1

DOWNLOAD STOCK FIRMWARE

knox counter 0x0

rooted

last supersu

xposed framework

Freezing knox apps not solved the problem,

deleted knox apps, since 1 hour no reboot
[SuperSU] Nasvyazi:
Tried the script. Still no luck.
[SuperSU] kaczkalolo:
me too, none of previous answers work, i cannot get into supersu app because it still wants to update binaries...
[SuperSU] gvc803:
me too. nexus 7 running 4.4.4. stock rooted. originally rooted through wugfresh. cant update the binaries through the SuperSu app or through TWRP. Have downloaded and flashed SuperSu 2.00 update successfully but still get the binaries need to be updated message when trying to open the app. All root apps work fine except LBE security master which will not hold root permissions on a reboot but will get root manually after restart.
[SuperSU] Depressed T.Bear:
Howdy folks, I have a question. I'm running ArchiDroid 1.x and on every update flashing the SuperSu app loses all its settings and rules for apps.

Hence, I'm looking for an easygoing way to back it up! But SuperSu doesn't come with such a function and titanium backup pro excluded the SuperSu app in a previous version for "security reasons".

How can I perform a backup?

Gesendet von meinem GT-I9300 mit Tapatalk
[SuperSU] nexusmaniac:
I wonder if root will still work on Android L? ;)
[SuperSU] keneth_c:
Check ROM Toolbox Lite...
[SuperSU] Pkt_Lnt:
https://twitter.com/ChainfireXDA/status/481860338267062273

---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------

Enable survival mode in SuperSU settings.
[SuperSU] gvc803:
Solved this by just force closing the SuperSu app and restarting. now I get no message to update when starting the app and can access all settings.
[SuperSU] bill1clinton:
I just tried this but still get the message to update binaries.
[SuperSU] 白い熊:
I'm trying to use the su --mount-master option, so that I can mount external storage system-wide, accessible to user apps.

su reports no errors, mount reports no errors, but the storage is only accessible to root.

Running KK on Note 3. What's wrong?

--

白い熊
[SuperSU] Sam7777777:
Multi user issues, flashed version 2.0 then updated binary after 3 attempts (Su is already system app) installed su on other users, it gets installed but doesn't show the option to open the app, tried cleanup too, any ideas?
[SuperSU] LEENO:
Still random reboot problem, even with knox apps deleted. Sometimes, after auto reboot, there is no network, imei null and baseband unknown. Rebooting manually network is ok and baseband ok. No hardware problem, same issue with 2 phones. Maybe auto reboot caused by code in modem?

With knox deleted apps, If i delete knox library phone freeze at startup, maybe library needed by bootloader?

Random reboot solved going back to fnb8 knox 1.0

Taptalked
[SuperSU] gvc803:
Force closing worked again on reappearance of update notification

This morning I turned on tablet (was not rebooted) , opened up the SuperSu app and got the binaries need updating message again. I then went into android settings/apps, scrolled to SuperSU app info and forced closed. went back to open up the app again to restart and did not get the update notification. dont know what triggered the reappearance of the update message to begin with. decided to reboot to see if it would revert back to needing update again but it didn't. dont know how long it will last. Using SuperSu 2.00. LBE security master still wont get root on reboots but I can manually get it to work inside the app itself, but thats probably more of a problem with that particular app than with SU as no other root app loses root on reboots.
[SuperSU] MrKaon:
Apparently super user is working with Android L:
[SuperSU] nexusmaniac:
I couldn't flash Super SU, twrp didn't install, can't flash the 2.00.zip :(
[SuperSU] MrKaon:
Fastboot erase cache before flashing TWRP.
[SuperSU] :
This works, but where did this boot.img come from?
[SuperSU] MrKaon:
It's stock boot.img with tweak:
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION]

I think the reason the SuperSU v2.00 zip doesn't work out of the box on stock L is because they changed the location of install-recovery.sh from /system/etc/ to /system/bin/ (and of course also in init.rc of the kernel ramdisk).

So we shouldn't need a modded boot.img at all, just to make the zip put the SuperSU script in /bin instead. That or move it with adb shell or AROMA Filemanager from recovery. Or keep it in /etc for back compatibility but symlink it to /bin, something like that. :good:
[SuperSU] lzyllp:
This work like modded boot.img.root explorer work fine.but still a lots of apps root not work.like shadowsocks,quick boot,Titanium backup.

SuperSU still need some update
[SuperSU] osm0sis:
Actually I think the apps need updating to use the new contexts like Chainfire outlined on G+ awhile back. He's done his part.

---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------

Looks like Chainfire responded and agrees:

https://twitter.com/ChainfireXDA/status/482384834468126720

Thanks [MENTION=2918596]Nburnes[/MENTION] for taking a moment to fix the zip for everyone while Chainfire's away, and while I'm too busy reflashing my device / lazy. :D

Edit: Haha apparently [MENTION=3418703]Tasssadar[/MENTION] had this figured out 6h ago. Man, we're slow. :p
[SuperSU] adnan.makarevic:
did somebody know something about tb, would be there an update for us with L?
[SuperSU] Pankaj Rai:
:-0
[SuperSU] pyrogoggles:
That method put me in a bootloop while trying to install Mirror.
[SuperSU] MadFlava:
This may have been mentioned in this thread.. I read back quite a few pages and didnt see anything so if I missed it, I apologize.

I have a Verizon Note 3 that Ive rooted with Towelroot. When I install SuperSU, I get asks to update the binary which I approve and everything is great. Then I get asked to disable Knox and this is where things go sideways. When I say Ok, SuperSU just sits there with "Disabling Knox" for literally hours. I can reboot and open SuperSU again and get the same message about Knox, click Ok to disable it and SuperSU immediatley says "Knox Disabled" but then it starts nagging me to update the binary and fails every time.

Not only that, when it gets to this point, all my apps randomly start FCing. Ive tried doing this process any number of ways and cant see to get it to work. Am I missing something, is there an alternate way I can do this?

Im now on reload #6 for my phone.. Ive yet to make it through the process unscathed.

Thanks!
[SuperSU] osm0sis:
I doubt that had anything to do with the method. The root daemon running is the root daemon running.
[SuperSU] pyrogoggles:
I'm sorry if this is a stupid question, but that means it is the app at fault? If so, I'll try to get koush to fix it.
[SuperSU] osm0sis:
Almost 100% positive it's the app, yeah. :good:

I had something similar happen to TiBU after I set it to use the system busybox (Stericson's installs flawlessly, by the way). TiBU recognized root but then ate ****, likely because it doesn't support ART at all. Anyway, kicked me out to the bootani. Hard reset and an ART cache rebuild and everything's fine.
[SuperSU] M3ntalPurg3:
I had the exact same issue but finally remembered that I needed busybox and sqlite. After install and reboot everything worked fine but now I'm having weird bugs with certain apps either FCing or zooming in way too much when it should be zooming out.
[SuperSU] osm0sis:
No luck with that here. Where'd you grab your sqlite3 binary from? I used the 3.8.x one from an xda thread I found awhile back (it's from April).
[SuperSU] M3ntalPurg3:
From Busybox Installer by JRummy it's the only one I've found that lets me install it. Did you Hard reset while rooted? Or Un-Root first? Don't want to create more issues than I already have. Just got this as a warranty replacement for shattered camera lens.
[SuperSU] osm0sis:
Not sure what you're asking here.. Root works in L so I left it alone. TiBU, not so much. I used Stericson's busybox installer and that's working well too, but no sqlite. I'll try the JRummy. :)
[SuperSU] M3ntalPurg3:
I'm asking if you did the hard reset while rooted and then everything was fine or did you unroot first, then hard reset and towelroot again? I want to try to fix the issues I'm having.
[SuperSU] osm0sis:
I have a Nexus 7, so I have no need for Towelroot. I had some sdcard issues that a data format and clean L install fixed but I haven't done any "hard reset" other than by holding down the power button to get out of the stuck bootani from TiBU sh*tting the bed, but that doesn't seem to be the way you're using the term so I have no idea what you're talking about.

If you want to explain your situation a little more clearly maybe myself or someone else can help you out. :)
[SuperSU] bendavis78:
There is no SU binary installed

I flashed SuperSU 2.00 (from download.chainfire.eu/450/SuperSU) on my Nexus 5 using TWRP. When I reboot and load the SuperSU app, it says "There is no SU binary installedand SuperSU cannot install it."

I've tried re-flashing several times with no luck. Am I doing something wrong?
[SuperSU] osm0sis:
If you're running L you need to move install-recovery.sh from /system/etc/ to /system/bin/ after flashing.
[SuperSU] bendavis78:
I'm not using L yet. I just realized I flashed an outdated SuperSU zip and not the 2.00 one. It works now.

Although, now that you mention L, I'm tempted to try it... Naah, I'll wait until it's stable
[SuperSU] mikereidis:
Thanks ! :)

Confirmed working for me. I just rooted L for the first time:

- Installed L

- Installed TWRP via fastboot: openrecovery-twrp-2.7.1.1-flo.img

- Installed via TWRP UPDATE-SuperSU-v2.00.zip

- Ran this while in TWRP/recovery to save old file and install in new location:

adb shell cp /system/bin/install-recovery.sh /sdcard/
adb shell cp /system/etc/install-recovery.sh /system/bin/install-recovery.sh

Now "adb shell"" and "su" works.

My root apps not working yet though. I expected "much breakage" from the context stuff.
[SuperSU] The Gingerbread Man:
How I did it on my nexus 5 from another thread the advice given was. Provided you have the entire L package loaded was to reboot to fastboot, fastboot format cache, fastboot flash cache cache.img, reboot to recovery, flash a SuperSU L preview.zip ( http://xdaforums.com/showthread.php?p=53713991 ) and boot to OS. Usimg these steps my nexus 5 is rooted using L. Any root apps that don't work (titanium, ES) need app updates to work with the newer OS.
[SuperSU] aircooledbusses:
Congrats man, we all started somewhere
[SuperSU] remo0073:
Confirm working good for me.

Moto G GPE with Android 4.4.4

- Installed TWRP via fastboot: openrecovery-twrp-2.7.1.1-XT1032.img

- Installed via TWRP UPDATE-SuperSU-v2.00.zip

Thanks
[SuperSU] Sam7777777:
sir provide backup restore too for permissions granted to other apps (userful after fresh rom installation)
[SuperSU] remotehugger:
ok - all seems fine but from within philz/TWRP/CWM whenever flashing something I get this message : "using legacy property environment for update-binary...please upgrade to latest binary"

things are flashing ok as far as I can tell but I've never seen that message before ??? any insights ??

VM SIII - jdsingle76's deodexed 4.4.2 NDC

philz recovery/stock kernel ?