yashsingh1/xdaforums huggingface dataset:
[SuperSU] gerardo87:
Now with 1.94 rr are less frequent but I have had a couple from my last post in this 3d... Now I try to change settings, rom and kernel and finally downgrade to previous fw (NDG if I remember well) to make other tests

P.S. I hope that log (attachment) are helpful

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] :
Off course its not a bug with my android system...:mad:

If you browse the last 2 pages of this thread, you will see all users who have flashed v1.99 are facing the problem...:rolleyes:

So it's better you look before you post....

The forum rules suggests that!!!

---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------

Yup, so far it seems the safest bet unless the dev comes with a workaround or fix...:good:

v1.99 seems to be a work in progess, that's why the changelog in this thread haven't been updated which is quite unusual...
[SuperSU] BurlaMatto:
Remove those apps:

univesalMDMClient.apk

SPDClient.apk

KnoxSteupWizardStub.apk

KnoxSetupWizardClient.apk

KnoxMigrationAgent.apk

KnoxAttestationAgent.apk

KNOXStub.apk

KNOXStore.apk

KNOXAgent.apk

KLMSAgent.apk

ContainerEventsRelayManager.apk

ContainerAgent.apk

Bridge.apk

I had random reboot, after removing them everything is ok (source http://xdaforums.com/showthread.php?p=47177193#post47177193)
[SuperSU] evildog1:
today i flashed CM 11 and SuperSU v1.99 and i have no problem at all.
[SuperSU] Chainfire:
So, I've also flashed the DBT version, let SuperSU disable KNOX, and guess what - not a single reboot.

So unless somebody is actually going to list all those root apps they have installed that may thus be the problem, I'm just giving up on this issue. I have to reproduce to be able to fix, so unless you guys help me reproduce, this problem isn't going away.

It is good to know that solves the problem, but unfortunately it doesn't help at all with pinpointing the issue.

Please stick to the facts - not *all* users who have flashed v1.99 are facing the problem (please look before you post?). In fact it seems only a very small number are, seeing as there are now several thousand users on v1.99, and only a handful reports of this issue.

I am doing my best to reproduce every single issue, but it's not exactly going well so far ...
[SuperSU] stuart0001:
I have a HTC M8 with stock sense and have no issues with 1.99.

Thanks Chainfire for your priceless contribution to our Android experience. :good:
[SuperSU] :
Sorry [MENTION=631273]Chainfire[/MENTION]...:(

'Twas rude on my part... Didn't intend to hurt you....

Sorry again and thanks for such a wonderful app....
[SuperSU] Chainfire:
I just did a clean flash of cm-11-20140529-NIGHTLY-jflte, followed by a flash of the 1.99r2 package, and that works fine for me.

So then I first flashed v1.94, then installed the 1.99r2 APK and updated that way. Updating normally failed ("yay"), while updating through recovery worked fine.

Aside from the in-app update that thus apparently still has an issue (will work on fixing that), I believe the root of the problem for you is actually your recovery. Which recovery and which version of that recovery are you running? For reference, I am using TWRP 2.7.0.1.
[SuperSU] darkrevlis:
Hello ChainFire, thanks for responding. I'll try to give some details of my experience with reboots. Since installing the latest firmware and put the last SuperSU I started having random reboots even without third-party applications installed.

Later I restore a data recovery all my apps from titanium backup and run applications like Orbot and Psyphon had more reboots. Could it have relationship with wi-fi or data network?

I also want to add that with this last upgrade both wifi and data network are more stable.
[SuperSU] Chinaboy5216:
Still wondering where I can find 1.99r2
[SuperSU] Chainfire:
It must be something additional rather than just this firmware and SuperSU. I flashed this firmware yesterday, installed SuperSU, and left the phone on since then, without as much as a single reboot ...
[SuperSU] Pons:
http://xdaforums.com/showthread.php?p=52856053&highlight=1+99r2#post52856053

Edit: but it says no longer available.
[SuperSU] bobbarker2:
That is odd. I'm using TWRP 2.7.0.1 but it's been modified by Ktoonez to support F2FS. It actually works better than the original TWRP as I had a ton of freezes with that. Could it be something to do with my /system being F2FS formatted when flashing, rather then the recovery doing something wrong? I don't think KT touched anything in his TWRP other than to support f2fs formatting.
[SuperSU] Chainfire:
Kindly adb shell into your recovery, flash the 1.99r2 package, "mount /system", then "ls -lZ /system/xbin/*su*" (just copy/paste that) and post the output ...
[SuperSU] Chainfire:
****ty dropbox, apparently generating too much traffic or whatever. r3 is in testing now, it will be available from my own server probably later today, and linked here.
[SuperSU] bobbarker2:
http://pastebin.com/xBrB3kWP

The board was turning chars into emoticons, just dumped the text to pastebin instead. Also the zip available at download.chainfire.eu/supersu is r2 right?
[SuperSU] Chainfire:
Doesn't seem to be too wrong ...

Not sure about if that link *was* r2, but it *is* now, or use this link directly: http://download.chainfire.eu/444/SuperSU/UPDATE-SuperSU-v1.99r2.zip
[SuperSU] bobbarker2:
Pretty sure I had redownloaded the r2, but just to be safe I grabbed the one you just linked and repeated the process. Same results and same "binary needs to be update" bug loop.

Is there anything else I can do to help you debug this?
[SuperSU] D@nge1:
Nexus 5 everything is fine. Version 1.99r2

Отправлено с моего Nexus 5 через Tapatalk
[SuperSU] Chainfire:
Well, you could pastebin the output of "ls -lZ /system/xbin/*su*" from a fully booted Android, just to be sure. If that doesn't lead anywhere, check again with r3 later - some things have been fixed that might (or not) be relevant.
[SuperSU] bobbarker2:
Hmm my getenforce returns Enforcing but I don't have a -Z option in ls. Maybe a busybox thing? v1.22.2-Dormanx

ls -l /system/xbin/*su*

-rwxr-xr-x 1 root root 121260 May 29 16:36 /system/xbin/daemonsu

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/lsusb -> busybox

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/md5sum ->busybox

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/sha1sum -> busybox

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/sha256sum -> busybox

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/sha3sum -> busybox

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/sha512sum -> busybox

-rwxr-xr-x 1 root root 121260 May 29 16:36 /system/xbin/su

-rw-r--r-- 1 root root 121260 May 29 16:46 /system/xbin/sugote

lrwxrwxrwx 1 root root 7 May 27 13:20 /system/xbin/sum -> busybox
[SuperSU] jazzruby:
[MENTION=631273]Chainfire[/MENTION] did you catch/notice [MENTION=5417405]bobbarker2[/MENTION] previous ls (pastebin) has 06755 (rws r-s r-x) for su

-JR-
[SuperSU] Chainfire:
sugote should be chmod 0755 - that is probably the issue. The problem causing that has been fixed in r3 this morning, so this issue should go away - in the meantime, 'su' probably just works, so you can change that manually and see if that fixes the problem.

Try 'toolbox ls' instead of just 'ls'.

Having busybox symlinked is one of the most horrible things ever though ... there should be laws against it.

Yes, but as you can see that is corrected in Android boot. The upcoming r3 actually no longer sets 06755 for newer API levels, but it is required pre-4.3.
[SuperSU] jazzruby:
My bad; forgot that paste was from an adb shell.

-JR-
[SuperSU] bobbarker2:
Hmm I went in manually and chmod 755 sugote but still get the same "needs to update" loop. Thought maybe a reboot was needed but ofc the permission gets reset to what it was originally on reboot. Here's a pastebin of the abbreviated output. http://pastebin.com/h3jX1fjw

I'll just wait for r3 unless it assists you to have me test something. Thanks for all your help CF.
[SuperSU] Chainfire:
v1.99r3

Still very much beta, still not official release, still no new official changelogs since v1.97

http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip

I request anyone who knows their way around and can revert to an older version if needed, to flash this version and see if there are still any issues present.

Note that this version needs to be flashed through recovery if you are running an earlier v1.99 version, or the su binaries will not be updated.

I've tried fixing all the reported issues from the last few days (including various installer issues and dis/enabling su, but also the battery drain issue with Greenify and FKU), but there have also (again) been changes to AOSP which have been incorporated, those changes may break things in new and interesting ways.

There are at least two outstanding issues left, both of these I was not able to reproduce:

(1) I9505XXUGNE5

(2) Language reset ( [MENTION=1561430]Crescendo Xenomorph[/MENTION] and others )

Please continue reporting these issues if they are still present, and help me solve them.
[SuperSU] aavvaallooss:
Once again reporting, 1.99 r3 works well on Nexus 5 stock.

Flashed with TWRP 2.7
[SuperSU] muniz_ri:
Just put r3 through its paces on my i337 gs4 running stock twz 4.4.2 nc1. No issues to report.
[SuperSU] brunodu91:
Idem on i9505 slimkat aosp

Envoyé de mon S4, via tapatalk 4 Vip .

Slimkat 4.4.2 v5.4, Kernel stock , buzz launcher , modem ET bootloader NC4.
[SuperSU] Frank Westlake:
1.99r3 OK on:

SM-N900T/MI7 Android4.3 TWRP2.7.0.1

SM-N900V/MI9 Android4.3 SafeStrap3.7.1/TWRP2.6.3.1

SGH-I717/AoCP6.4 Android4.3.1 TWRP2.7.0.0

Frank
[SuperSU] bobbarker2:
Still update looped here. When I get a chance I'm going to try a clean flash of the CM build I'm using and see if it's still an issue.
[SuperSU] The Gingerbread Man:
R3 seems fine on flo, stock rom, flashed using latest twrp
[SuperSU] Chinaboy5216:
r3 running ok on TF101 and KatKiss 4.4.2 v25

Thx for the link Chainfire!!
[SuperSU] 089man:
R3 works fine with aicp kk rom, Samsung s2 device

I9100 Tapatalk 4, AICP-Rom 4.4. 2
[SuperSU] eurochild:
all good with r3 / nexus 4 purity rom
[SuperSU] boyheadkick:
No problems with 1.99 R3 on Archiport n7100 based Blekota KitKat Rom for i9300

Edit: also working good with Archidroid 1.7.15 Sammy official 4.3 based

Both flashed with TWRP 2.7.0.0 for i9300

-aL

Tapatalked from my BoefflaDroid i9300
[SuperSU] chteh2008:
R3 works well on my HOX with stock ROM Android 4.2.2 and CWM touch recovery v6.0.4.8

Thanks again...
[SuperSU] WR3CCKL3SS:
R3 working well on C-RoM v6.6 on JFLTEATT, Flashed thru modified KToonsez TWRP 2.7.0.5 EXT4

AT&T Samsung Galaxy S4 I337

ROM: C-RoM v6.6

KERNEL: KT-SGS4 V7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] MikeRL100:
1.99R3 working well thus far on OmniROM 5/29 Nightly on both a Nexus 5 and 7 2013.
[SuperSU] kashortiexda:
working well on DN3V5+ N7100 4.4.2 Philz recovery Agni Kernel
[SuperSU] Yeti47:
No issues on s3 i9300 using cm11 Nightlies (30/9) and philz touch 6.41.6
[SuperSU] 200:
1.99r3 working fine with OMNI 20140530 nightly on i9300
[SuperSU] khairulez:
1.99r3 working well on OmniRom 20140525 with Next Kernel on HOX
[SuperSU] The Gingerbread Man:
I do have a query and I'm not sure if this is related to root or not, here goes anyway.

My nexus 7 2013 has a primary and secondary user account. I have enabled the option within SuperSU apk for multiuser root. On my primary account I use the paid per app mode app by fransicofranco and I tried to use the free version of the same app on the secondary account. The app works fine on my primary account but on the free one within the secondary user account profile after su permissions have been granted the app force closes. I haven't tested rolling back to older 1.94 su yet as didn't have time before I left for work. I was wondering if any one else might of had issues with root apps on multi account devices like tablets? I tried using the 1.99r3 for this, when I'm home again and have more time I'll roll back to an older version and try again.
[SuperSU] mag01:
1.99r3 and battery drain issues

[MENTION=631273]Chainfire[/MENTION]

So I tested 1.99r3 on those battery drain issues with the following results:

1. set to FKU prompt only

- after approx 2.5 minute of screen on it goes off and then it seems fine

- all su attempts (incl. Greenify which is allowed) visible in the SuperSU log

2. set to Greenify prompt only

- after approx. 30s of screen on it goes off and then it seems fine

- all su attempts (incl. FKU which is allowed) visible in the SuperSU log

However things start to be a little tricky when there's more than just one app set to display the su prompt:

3. set to FKU and Greenify prompt, but nothing for Greenify to hibernate

- similar to 1st case

- but Greenify's su attempt (there should be one denied that should match one allowed from the 1st case) isn't visible in the SuperSU log

4. set to FKU and Greenify prompt, but there's an Opera browser running for Greenify to hibernate

- screen goes on and stays on (tested for about 10 minutes and it was on all the time)

- again Greenify's su attempts (this time there should be at least 2 I think) aren't visible in the SuperSU log

- after unlocking the phone, the SuperSU prompt is still visible (for FKU) while for all the above 3 cases is would be gone.

Attaching verbose logcat logs if they're of any help.

Also one last thing:

If SuperSU denies any such su attempts I won't know about it (well, except for the 4th case above which You will probably fix) unless I check those affected apps or check the SuperSU log...

Would it be somewhat possible to generate a notification about these particular denied su attempts?

It may be a little tricky to not mess up with too many notifications as for example FKU produces about 12 su attempts in a row.
[SuperSU] stef_ladefense:
prob with 1.99R3

hi Chainfire,

have instaled 1.99R3 in my T520 (T520XXUAND1) with supersu.apk

at lunch, propose to upgrade SU binary, and faled ...

reboot, re faled ...

return in 1.94

Stephane
[SuperSU] Gold_Phenix:
Where I find SuperSU v1.97 ? I want stable version on Google play it's only v1.94.

Wysłane z mojego LT26i przy użyciu Tapatalka
[SuperSU] kingvortex:
The Google Play release is the stable version. Is there a particular reason that you need to upgrade? If not, just wait until the latest version is out of testing and pushed to the Play Store. :)
[SuperSU] eddvys:
There should be more thanks bars for this developer :good::angel: Imagine stuff without Chainfire :confused:
[SuperSU] DSA:
There should be more donations, the thanks meter is irrelevant
[SuperSU] MikeRL100:
I'm a bit broke ATM. But I've bought other developers coffee. I've bought SuperSu pro, donated to OmniROM a good amount ($50), but maybe Chainfire himself could use a little money. He's not greedy like Koush can be. (As in, make incredible apps and abandon them for money). I'm kind of ticked I coughed up for Helium and ROM Manager and they continue to suck. Wouldn't mind paying again for a massive update if it was done right. So the apps I tend to use the most I don't just pay once and forget. Or worse pirate them and ask for support (a lot of idiots do). People cannot live off of one time payments for an app that's expected to get free updates for life. So, I guess in timing for 2.0 (if that's what it'll be called) I'll donate. I suggest others do the same. Especially if you're using a stock Samsung ROM since Knox and all that other crap makes developer's lives a living hell.

Edit: $15 sent, regardless.
[SuperSU] Surge1223:
[MENTION=631273]Chainfire[/MENTION]

Have the latest su issues been exclusive to Samsung devices? The reason I ask is I noticed Sysscope has gotten more aggressive lately in 4.4.2. Not only does it keep a list of all things in /system/bin running as root (except for debuggered, thermald, and a few others) but I started taking Sysscope apart last night and it also has the chmod and chown functions used in libcordon.so. I dont know if its changing perms on su and dameonsu, along with install-recovery.sh and etc yet or not but its a good candidate for being the potential issue. I can provide more info if needed.
[SuperSU] bobbarker2:
Got around to doing a clean CM11 flash. Just CM11 5/30 nightly, gapps and supersu 1.99r3. Still "needs to update" bugged. Not complaining, just reporting in info. Let me know if I can be of assistance.
[SuperSU] Lgrootnoob:
"hits thanks button"
[SuperSU] Frank Westlake:
I have had SysScope.apk uninstalled from my SM-N900V and SM-N900T for several months without any apparent problems. I don't use them for phone service (SecPhone.apk also uninstalled) so I don't know if the absence of SysScope.apk will cause problems for devices used as phones.

Frank
[SuperSU] DSA:
Lol :p
[SuperSU] marbulas:
Disabling/Re-enabling Superuser of 1.99r3 works fine on Galaxy Note 3(SM-N900S, Sammy 4.4.2, SELinux : Enforcing). :D
[SuperSU] iamnotkurtcobain:
I had 1.94 on my S4 9505 cm11 rom (flashed via recovery) but when I flash 1.99r3 via recovery and open supersu in Android I'll always get that supersu has to be updated. I tried with normal and via recovery but nothing worked.

Gesendet von meinem GT-I9505 mit Tapatalk
[SuperSU] bobbarker2:
Yeah I still get that problem too, tried on several ROMs now, Omni, CM11, Nameless. Best thing to do is go back to an older version until CF can fix. I finally found 1.94 on CF's website after guessing at folder names. You can dl it here: http://download.chainfire.eu/396
[SuperSU] CyberpodS2:
Running 1.99r3 on Carbon nightly 5/31 and flashed from kt's TWRP 2.7.0.5 ext4 with no issues to speak of.
[SuperSU] cbeckstein:
Since the Supersu beta updates > 1.94 Mobile Odin Pro 4.20 no longer can identify device model on SGS4 Stock ROM XXUBMGA (Android 4.2.2)
[SuperSU] Le Ch@land:
All seems fine here on galaxy note 3 N9005 lte Stock KitKat 4.4.2, ;) rooted with su 1.99r3.

Installed over custom recovery on 1.94.
[SuperSU] jan2jan:
I'am using cm11 30052014 and installed supersu 1.99 r3 via cwm after that I installed the boeffla kernel for cm11. When the boeffla kernel is installed I get the message of the boeffla install script that the su binary has to be updated. Though after reboot everything works fine.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[SuperSU] coukou:
199r3 installed with TWRP 2.7 over 1.94 works like a charm on ZOPO zp998

Thank you :D
[SuperSU] Gold_Phenix:
If i want root permission, I must install only flashable update SuperSU.Zip ? Or I must install busybox to?

Wysłane z mojego LT26i przy użyciu Tapatalka
[SuperSU] kingvortex:
The SuperSU zip is all that is required for root permissions.

Some root apps require busybox to function though.
[SuperSU] papei:
I would think, that depends on the rom you are on. If you are flashing the SuperSU.Zip from a stock rom you may need to install busybox. Some root apks require it.
[SuperSU] asferican20:
Have the same issue with Galaxy Note 10.1 (GT-N8013) running Stock 4.1.2 ROM (N8013UEUCMD3). I've tried every version since 1.94 (1.97,1.99,1.99r2,1.99r3) all of them break the ability for MobileOdin Pro to identifiy device model. Flashing back to 1.94 works every time.
[SuperSU] koolboyztn:
running v1.99r3 on stock rooted T-Mobile S5 without any problem so far.
[SuperSU] :
Only SuperSU is needed for root permissions...

Average Joes like us don't need the BusyBox...

Though some apps have BusyBox dependencies.... The most popular being Titanium Backup...

So unless you plan on using TB, SuperSU would suffice....

Btw, most custom ROMs like CM comes with BusyBox baked in the ROM...

Hope this helps...:good:

---------- Post added at 12:37 PM ---------- Previous post was at 12:27 PM ----------

Here you go... http://download.chainfire.eu/416/SuperSU/UPDATE-SuperSU-v1.97.zip;)

Flash it via recovery...

The Google Play releases are the most stable, you should stick with them...

But having said that, there are some exclusive releases for SuperSU which are stable as rock... For eg, v1.97...

These releases do not get a Play Store release not because they are not stable but they are built by the dev in anticipation of changes in the next version of android which may pose problems for the root app going by the commits in the AOSP...

But thankfully these don't deter CF, thats why he's called the GOD OF ROOT!!!

You can check out these things for yourself by viewing the release notes...

Hope this helps...:good:

---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------

Can you please elaborate how you browsed the folders???

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------

As of now, v1.97 is your safest bet....

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

Flash it via recovery....:good:

---------- Post added at 12:57 PM ---------- Previous post was at 12:51 PM ----------

It's because of people like you, that the android community remains a better world....

Thanks for sustaining development for the devs...

Guys like you deserve a special mention because you drive forward the development... I hope this type of attitude rubs on others too....

Here's a salute from me...:good: and you deserve IT!
[SuperSU] volkmadi:
Hi,

I have a question.

I read the last days over here a bunge of posts where, as a solution against the soft reboots with newest stock rom for S4,

the proposed solution was to uninstall all knox apps.

I have choosen an other way and do not like the way to uninstall all knox apps (and have at the moment no reboots just an knox warning in the notification area). There was a reason for me (and I suppose others too) to choose the latest stock and not a mod version where the knox apps are anyway no prob.

So now to my question:

Will there be a solution provieded like in

https://plus.google.com/+Chainfire/posts/5ggu7naWtaW (what unluckily now leads to the soft reboots)

where not all the knox stuff needs to be uninstalled?!

Maybe just some packages needed to be disabled again and others like the seandroid can stay enabled to avoid the reboots?!

Regards

Dirk
[SuperSU] bobbarker2:
I guessed at the folder names, which are numbers.
[SuperSU] :
Well, the best person to answer your question would be the dev... We can just speculate....
[SuperSU] volkmadi:
100% correct! :laugh:

I hope for an answer by them! :good:

Dirk
[SuperSU] badnaam:
Superuser pro is required for this feature

I am trying to copy a file in ES File Explorer from a FTP server in my LAN to my SD card. I am not sure why this task shows a supersu prompt to grant the file explorer root access, don't think it used to do that. The task fails.

When I enable the root explorer features, es file explorer also says "test failed".

When I look at the logs in supersu, I see messages for ES FIle explorer like.."Supersu Pro is required for this feature".

What root permission are limited in the free version of supersu that won't allow this operation?

This is on LGE980 rooted with stock ATT 4.4.2 ROM

Thanks
[SuperSU] :
Well AFAIK the latest version of ES File Explorer i.e., v3.1.5 is very buggy and going by my personal experience and the reviews on the Play Store, the latest release is having FCs and having many other problem with root.

Therefore, it will be safe to assume that this has got to do with ES rather than SuperSU.

As for now, your safest bet would be to install ES v3.1.4 from estrongs website which is running without these hiccups.

Here you can download v3.1.4 http://www.estrongs.com/

Hope this helps...:good:
[SuperSU] BurlaMatto:
Same question :) i'm getting random soft reboot with all knox app disabled and not deleted
[SuperSU] volkmadi:
Hi,

to solve your problem, enable all konx apps again and switch se state to permissive, there are some apps (as I remember, but at least one) that does that for you and the reboots are gone!

Don't forget the "Thanks Button" ;)

Dirk
[SuperSU] MrKaon:
4.4.3 is out for Nexus and SuperSU is working fine with it:

https://developers.google.com/android/nexus/images#hammerheadktu84m