yashsingh1/xdaforums huggingface dataset:
[SuperSU] aavvaallooss:
No personal experience, sorry. I guess you need do it in 2 steps, but not sure
[SuperSU] sandeepdarklord:
How to flash in devswift1 jellybean in Xperia u
[SuperSU] juliatan:
Root survival worked!

Root survival mode worked on my Nexus 7 Flo (with stock recovery). Just updated OTA 4.4 to 4.4.2 (via Google server not manually). I still have root. Makes SuperSu Pro worth every penny. Now I don't have to temperarily 'boot' TWRP via Adb and Usb-cable to flash SuperSu again. Really great and thanks a million!
[SuperSU] paour:
I've also been having this issue: the battery will start to drain and when I pull up a top view, a daemonsu:nnnnn process will consume 100% off one core. Also usually connected to an adaway update. Is there any logging I could preform to help trace what's happening?
[SuperSU] khaytsus:
Yeah, I really think adaway is causing this. I've gone back to manual adaway updates. I dunno what they're doing wrong, but it's really pissing off daemonsu. One thing that makes me think it even more is that the supersu logs show adaway asking for root a dozen or more times each time.

None the less, adaway is the best tool for ad blocking since you can put in your own sources.. Just gotta have it notify and manually apply I guess.
[SuperSU] paour:
I've submitted a ticket on adaway's github.
[SuperSU] giovaorama:
Does anyone have problems to download the flashable zip file?

I follow the link in op and the zip file is actually a text file.

I never be able to get a good one and just now I understand why twrp always tell me "bad zip file"

Inviato dal mio Nexus 4 utilizzando Tapatalk
[SuperSU] Pkt_Lnt:
I download from my desktop or phone browser just fine.
[SuperSU] giovaorama:
It must be a Tapatalk bug or a malformed link: if i press the link in OP it download the web page that a web browser open on the same address and it save as update-supersu-1.80.zip

Strange

Inviato dal mio Nexus 4 utilizzando Tapatalk
[SuperSU] Pkt_Lnt:
It is a tapatalk bug, use the browser.
[SuperSU] NCguy:
I can now happily confirm that superSU root also survives on the N5 when going from 4.4 to 4.4.2 using OTA survival mode. Nice when a product works so well.
[SuperSU] Taomyn:
What version of Adaway are you running? V2.8 is notably buggy and was constantly hanging on my N5. Went back to v2.7 and it's fine.
[SuperSU] paour:
I just had the exact same thing happen with 2.7, sadly. Adaway hangs on "updating the hosts file" and keeps the daemonsu process running wild.

For some reason, it copies several times (using dd, oddly) /proc/mounts to /data/local/RootToolsMounts.
[SuperSU] mjb:
Chainfire,

I've just recently taken delivery of my Omate TrueSmart smartwatch - nice device so far...

Anyway, the prompt dialog from SuperSU is 'too big', so I can't actually see the allow/deny buttons (See attached image).

Would it be possible to create a reduced size dialog for small screens such as the Omate?

Cheers.
[SuperSU] Chainfire:
I'm not sure what's going on with AdAway. While it seems obvious that AdAway is causing the issue for you guys, that doesn't necessarily mean it's AdAway's fault. I'll try to look into this specific case in the next few days to see what's up, but no promises.
[SuperSU] Chainfire:
Can you figure out what resolution it has in both PX and DP ? Also how much DPI is the screen ?

Might help.
[SuperSU] mjb:
sorry - should have mentioned. It's nominally 240x240, ldpi.
[SuperSU] aavvaallooss:
AdAway 2.8 and SuperSU 1.8 work fine here on 4.4.2
[SuperSU] mikemod:
I am trying to install the latest version of SuperSU on my Galaxy Note 10.1 (GT-N8010) Android 4.1.2.

I have the pro version running on my Nexus 5 with no issues.

On the Note it is continually asking to update the SU binary each time I try to open the App.

This always fails and also the option to flash through TWRP and ClockworkMod Recovery also has no effect.

I have also manually flashed the zip through both TWRP and ClockworkMod Recovery but although it always says it has succeeded the App always says the SU binary needs updated and fails again.

I have removed the Root and SU, cleared the cache partitions and reinstalled but it still does the same thing when trying to run the App.

I have manually copied the latest SU binary to he correct location but it still asks to update on opening.

I have tried other SU apps and they are working, but I would like to stick with SuperSU as I use it on my other devices.

Has anyone any ideas what may be wrong? cheers.
[SuperSU] jazzruby:
Hi mikemod,

Can you provide the TWRP recovery log (although recovery shows success the log may show errors).

In TWRP recovery, flash the SuperSu ZIP pkg

then go to

Advanced > Copy log to sdcard (swipe to copy)

Boot back into the ROM and post/attach the log located at /sdcard/recovery.log

The recovery copies a log to root (/cache/recovery) however I have seen it truncate the tail of errors whereas the 'Copy log to sdcard' does not.

You may want to post both by renaming one of them, e.g. recoverySD.log | recoveryCAC.log etc...

-JR-
[SuperSU] mikemod:
Here is the Cache recovery log, there do seem to be a lot of errors associated with the install.
[SuperSU] glancer2315:
I'm having trouble with SuperSU on 4.4.2 on Nexus 4.

So at 4.3 I unrooted first, then OTA'ed to 4.4 and now 4.4.2.

Yesterday I used cf-auto to root my phone, but there was no SuperSU. Then I downloaded one from Google Play. But it keeps saying "unfortunately SuperSU has stopped" when there is a need to use SuperSU, i.g. when there is a root explorer app running. I doubt whether the root was successful so I downloaded a root checker, but it kept saying "please wait". So I even don't know whether my phone is rooted.

Please help.
[SuperSU] xI mEzMeRiZe Ix:
Currently using Koush's superuser on my Nexus 5 and Adaway hangs frequently just like it does with my Nexus 7 using SuperSU 1.80.

Sent from my Nexus 5
[SuperSU] adgj533:
im using beanstalk rom and it comes with superuser but inorder to use titanium backup i need super su. how to switch? i tried installing supersu but it didnt install binary and i lost root so i had to reflash the rom. and also titanium backup says no sufficient memory to do backup, i have like 8gb left anyone know why??
[SuperSU] yaonos:
I have faced this issue more than once. Here is how to fix it : go to settings/Apps and remove SuperSU's update. You may need to repeat this many times until the system stops offering you the choice to remove the update. SuperSU should then start to work properly.

[MENTION=631273]Chainfire[/MENTION], I wanted to report this bug regarding the way the unroot feature deals with SuperSU's updates : if the SuperSU app has been updated via the play store, if the device is completely unrooted by the app then rooted again, the SuperSU App doesn't appear in the launcher all the apps requesting root hang. If the app is then installed via the play store, it force closes.

The only way to fix this issue is to uninstall SuperSU's update - even if the app has just been installed via the recovery and not been updated by the play store app.

I first encountered this bug when taking an OTA (4.3 to 4.4 on my N7, then 4.4 to 4.4.2 on my N5), but I have verified that it is not related to the OTAs has I have been able to reproduce it on my N7 without taking an OTA. I was on 4.4 and had initially installed v1.75 and updated it to 1.80 via the play store. I completely unrooted and rooted again under TWRP with v1.80. After the system boot, SuperSU didn't work and I had to remove the update in order to fix this.

It seems the system keeps traces of the previous SuperSU's updates even after a complete unroot. This prevents the app from working properly the next time it is installed.
[SuperSU] jazzruby:
Log doesn't show any errors for SuperSU app, binaries, scripts, etc..that hamper the install.

The errors for chcon (change context) are from only 1 of 2 calls (diff locations) to the program.

-JR-
[SuperSU] mikemod:
Still not working so I am just going to use ClockWorkMod Superuser, on the Galaxy Note 10.1, as it is working fine.

However SuperSu v1.8 is working OK on my Nexus 5.
[SuperSU] Chainfire:
Updated to v1.85 - https://plus.google.com/113517319477420052449/posts/f43NqJa9AUR
[SuperSU] ChungHung.Chen:
Hi,

v1.85 still failed when I install zip from CWM, got a "status 6" error.

Could you help to fix this problem?

Thanks for great app.
[SuperSU] Braxos:
Chainfire when I upgrade to pro even I have always granted enabled I can pick a timer to auto deny.

Brb forgot to take SS or it never happened

Here we go same was on 1.70 and after as at that point I started using omni ROM on my n7000 and I had to have it always granted root rights.

I did reported it when I reproduced the bypass of the pin on supersu that someone had reported and you wanted us to check it out.
[SuperSU] aavvaallooss:
No problem here upgrading from 1.80 using Flashify/TWRP
[SuperSU] robygt:
I've flashed the .zip file with twrp and it's all fine.

Sent from my 3310 Chuck Norris approved.
[SuperSU] cmstlist:
Thanks for the update!

Just wanted to indicate my continued support for a feature that would hide root from nosy apps. The Telus "Optik On The Go" app has now introduced live TV for subscribers but rooted users are still locked out.
[SuperSU] Mr.Its:
With Gingerbread if you view the credits it'll force close.

java.lang.NoSuchMethodError: android.widget.ScrollView.setScrollY at eu.chainfire.supersu.SettingsFragment$16$2.run(:771)

I believe setScrollY is API level 14 and so you should be using scrollTo or smoothScrollTo?

Thanks.
[SuperSU] Chainfire:
Ah it's still planned but I need Substrate (a package by another author) to be updated for SELinux/Android 4.4 first.

Thanks for the heads up, overlooked this.
[SuperSU] mikemod:
Tried 1.85 on my Galaxy Note 10.1 but the app still asks to update su binary each time it is opened.
[SuperSU] precardo:
Hi all:) I always use the flashable zip, all seems pretty fine for me, I'm using (Android 4.3 AOSP). SuperSUv1.85 is working
[SuperSU] scuba4436:
Updated from v1.80 to v1.85 on my Nexus 5 with KitKat 4.4.2 (rooted). The app asks to update the binary each time I start. But the update by the app is not successful.

Edit:

Just got it to work. There was an interference with BusyBox. Uninstalled BusyBox, got su to work and installed BusyBox again.
[SuperSU] myrthain:
My update from the latest version to 1.85 just ended up in appearing to be successful and asking me to reboot the device. When doing this I get into recovery mode but just rebooting the system does not help, because I always get automatically into recovery mode again and again.

Shall I delete the cache partition or what advice do you have for me?

device: rooted Samsung Galaxy Nexus on 4.3 (JWR66Y_maguro)
[SuperSU] Lownita:
Just ended up in a bootloop after flashing 1.85 on http://xdaforums.com/showthread.php?p=48521320. I am using art and latest franco kernel r21. Any suggestions?
[SuperSU] myrthain:
My rebooting into recovery ended after switching it off and on the 3rd time... Whatever that means.
[SuperSU] Lownita:
Yes, I switched phone off completely and on again. It booted but rebuilt complete ART cache. So perhaps cache was wiped while flashing or so?
[SuperSU] arifhazwan:
Hello. This might be a silly question but how do I remove koush cwm superuser and install this supersu?
[SuperSU] cmoG530:
You can't if superuser is built into the ROM. SuperSU just overrides it.
[SuperSU] ChungHung.Chen:
Hi,

I know that TWRP works well but CWM 6.0.x.x in my XT910 doesn't.

Due to locked bootloader ( and can't unlock ), I'm still need CWM as my recovery.

So I wish I can help to find the solution of this problem.

I've done some test and reported to [MENTION=631273]Chainfire[/MENTION], hope it's helpful.

Thanks for your reply.
[SuperSU] arifhazwan:
I just install SuperSu and unroot my device after that I reinstall the SuperSu back and everything is working fine now. Thank you very much.
[SuperSU] adgj533:
hi im using beanstalk rom 4.3 and superuser is built in to the rom as a system app. i wanna flash supersu how can i do it? i tried download from play but i lose root as soon as i uninstall superuser, please help
[SuperSU] SignetSphere:
Just updated and everything went well. Thanks again Chainfire :good:
[SuperSU] ben_pyett:
Latest update appears to have generated a ro,remount directory at root level
[SuperSU] rogers11:
Same here, N4 and N10.
[SuperSU] kvevand63:
Running v1.85 on E4GT with CM11 and ART enabled. Logcat is showing error "invalid stream - problem with parameter iterator supersu". I am not sure what this means, not seeing any sort of performance issues. What causes this and should I just ignore it. Thank you in advance for your response.
[SuperSU] ceza1380:
Go for clean flash, select ROM, gapps and after that SuperSU. Flash those 3 via TWRP and that's it.
[SuperSU] californicated:
Anyone else getting some battery drain since updating to v1.85? Even after rebooting SuperSU is still listed with 9% battery drain under settings. You want a log?

It's the first time I'm getting any issues. So nevertheless great work :)
[SuperSU] rogers11:
This does not happen here. SuperSU does not even appear in the list.
[SuperSU] claytonjn:
Not seeing that here either.
[SuperSU] SignetSphere:
This is the first I've heard SuperSU appearing on the battery stats (or maybe I'm not just checking lol). Try wiping your dalvik cache and see if that helps.
[SuperSU] xI mEzMeRiZe Ix:
Is there anything I need to do before flashing SuperSU when coming from stock + Koush's superuser?
[SuperSU] mouseglider:
I am interested also - funny thing happened, I thought I flashed the same recovery tar when I was in the rooting process of two GS3's - one installed superuser and the other installed SuperSU - I am sure I most likely did something wrong - but at least they both are rooted and work well - but when using root checker app by joey k when verifying root SuperSU finishes faster. :D
[SuperSU] ChungHung.Chen:
Hi,

Can you post a screenshot?

Some apps may cause this and shows "daemonsu" in battery status.
[SuperSU] arifhazwan:
I install the SuperSu, choose the option to full unroot the device then I wipe the cache etc and sideload the SuperSu zip again.

Everything works fine.
[SuperSU] VivaErBetis:
Yep!. Can this “ro,remount“ directory be deleted without issues?
[SuperSU] miten_sheth:
Had updated from the play store caused issues.. But when I flashed the zip here.. It worked. :good:
[SuperSU] funfun99999:
After update to v1.85 whenever I restore apps/data using Titanium backup the restored apps keep FC !!!

I did not had this problem before

This happen on galaxy Note 3 and galaxy 10 2014

I just re-rooted my p600 with CF-AUTO Root, which install SuperSU 1.65 and every things work perfect (restoring apps/data with Titanium backup). then update again to SuperSU 1.85 again the same happened restoring apps/data with Titanium backup and the restored force close . And the android firewall don’t work with SuperSU 1.85 doesn’t block any apps any more.

I will re-root again with CF-AUTO Root.

Is there any way to overwrite the su binary without custom recovery?
[SuperSU] trahzebuck:
Since the update 1.85 (playstore) I also have problems with TB.

Moving Apps to System or Integration of updated Systems apps lead to FC of apps. especially the stock camera app.

Happens on Sony Xperia Z1. Rooted stock rom. No mods. Worked flawlessly with SuperSU 1.80.
[SuperSU] chemcup:
here the same problems with Note 3 android 4.3
[SuperSU] aavvaallooss:
Same problem since 1.65 at least. Not sure if SuperSU fault
[SuperSU] Chainfire:
Well there is something wrong with v1.85 on some phones and firmwares ... update soon.
[SuperSU] apatal:
Haven't encountered any issues so far for my use, but I'm not one to reject any fix. Update away! :)
[SuperSU] chemcup:
The problems are happened for me on android 4.3(note 3). I had note 2 android 4.1.2 no problems.

I tried some of the backup apps and all had problem to restore apps/data . For example, titanium can restore apps but when restore data the apps FC. Rom-toolbox cannot restore apps/data. System tuner cannot restore apps but restore data successfully. mybackup and go-backup cannot restore apps/data.
[SuperSU] GroteBozewolf:
[MENTION=631273]Chainfire[/MENTION] would you suggest reverting back to 1.80 just to be safe? And could we in that case just reapply the 1.80 zip over the 1.85 install?
[SuperSU] moom999:
Need update because the people like me who don’t have custom recovery can’t reverting back to 1.80!
[SuperSU] Chainfire:
Actually posting the logcat might help

Please check (and report back ASAP) if this version solves the problem:

http://download.chainfire.eu/supersu
[SuperSU] trahzebuck:
Nope, dear Chainfire. Problem is still there...

Flashed update via TWRP. App reportet V1.86. But same problem. Sorry.

Thanks for you support anyway. You'll solve it, I'm sure. :good:

Restoring in the moment...
[SuperSU] RHBH:
Hello!

I flashed UPDATE-SuperSU-v1.85.zip on my Xperia Z1 with Stock Android 4.3, I have root access but isn't working properly, I can't remout system, got a permission denied error.

I spoke with another devs and I received a suggestion to use su including daemonsu, does UPDATE-SuperSU-v1.85.zip have daemonsu?
[SuperSU] Chainfire:
Try 1.86 ... http://download.chainfire.eu/supersu
[SuperSU] chemcup:
@ Chainfire

apps restore test with titanium, Rom-manager and System tuner work without problem.

I just install the 1.86 as normal apps and it did update the su.

And android firewall work now too
[SuperSU] funfun99999:
thanks Chainfire

after installing 1.86 (Installed it normal I have no custom recovery) the restoring with titanium works now and the firewall too.
[SuperSU] RHBH:
Thank you sir!

I'm at work right now, but as soon I get home I'll test it.
[SuperSU] RHBH:
Unfortunately my issue persists.

I have root checker, please take a look, is this a problem related to su binary or my rom?

Congratulations! You have root access!

Super User Application Status:
SuperSU application - version 1.86 - is installed!

System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.

Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104800 2013-12-17 16:51 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!

Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.

Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:
Root user id:
uid=0(root)

Root group id:
gid=0(root)

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1

Results provided on your C6943 device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
[SuperSU] Odysseus1962:
[MENTION=631273]Chainfire[/MENTION] I think there's a problem with the SuperSU v1.86. Update zip. Since I'm s-on with my HTC amaze, 4g I usually try to save time and just flash the zip from here whenever I see It's been updated at the play store. This time there are issues. Every time I've tried flashing in recovery the installation aborts. I thought that perhaps the download was corrupted so I tried again with the same results. I have never had this issue before.

Fortunately, I was able to update through the store, but It's a pain in the behind. I had to install with the recommended HTC recovery method, which installed the update. However launching it showed that it still needed to be moved to /system. I selected the move to system option, but upon reboot it still wasn't done. Finally, after three attempts I got it moved.

Details of my setup are in my signature.

I love your work and support it by purchasing the paid version. I hope this gets resolved in the next update. TIA
[SuperSU] klau1:
I've been getting weird System User UID 1000 usr request on SuperSU with no known explanation.

nOTE: This appears even without Xposed Installed.

But could the folllowing be why?

Regarding the problem of weird System User Request:

If I understand this properly, it's saying SuperSU accesses some functions as the System User 1000 on Android devices previous to OS version 4.3

On Android 4.3 and newer, SuperSU access those same functions without using System User 1000.

This would explain why this permission request does not appear on my Android 4.3 device, but it does on my Android 4.1.2 device.

So it's normal to get the System User UID 1000 request upon startup once SuperSU is installed on an Android 4.1.2 device?

Is this the correct understanding?
[SuperSU] aavvaallooss:
No problem with 1.86 in Nexus 5
[SuperSU] marbulas:
UID 1000 still appears via 1.86.

I'm using Galaxy Note 3(sammy 4.3) and wanam xposed 2.5.1 with xposed framework 2.4.1.

If I try killing foreground app by touching back button long featured from Wanam Xposed, UID 1000 appears.
[SuperSU] kewinh0727:
knox detected by super su

hey i just flashed superSU 1.86 in CWM when i oppened super su then it said that it had detected KNOX... that has never come up before..

well

im on samsung galaxy s4 i9505 android 4.2.2 XXUBMEA firmware as far as i know knox is not activ on that rom right? in download mode it says nothing about KNOX and 0x0 nothing of that... should i press cancel or or try to disable KNOX by pressing OK ?
[SuperSU] marbulas:
And if UID 1000 requested with same way again, SuperSU doesn't prompt that. Denies automatically. Not belongs to the setting of SuperSU.
[SuperSU] LeftyGR:
I am on a note 3. On the stock rooted firmware, I get the same message. When pressing OK to disable, it successfully does so. And no other messages or problems happened after that.

♢NoteIII♢
[SuperSU] kewinh0727:
thnx for the reply :)

yeah well i am afraid of getting that KNOX sh!t since i only read about problems with it xD that's why i wont update my phone to 4.3 or 4.4 at least not on stock firmware xD

well it does not trigger knox to start or something like that right so it is completely safe ?: ) ? can someone more confirm :) [MENTION=631273]Chainfire[/MENTION]

perhaps :) ?
[SuperSU] marbulas:
And this is the logs when UID 1000 appeared and catched via Syslog
[SuperSU] funfun99999:
I had this UID 1000 on my note 3 and it was related to Wanam Xposed. I removed Wanam and delete the item from supersu and never saw UID 1000 again
[SuperSU] klau1:
I have seen it on Android 4.1.2 even on a BLANK system, no wanam, no Xposed.

And the ROM is stock from Samsung from http://www.android-hilfe.de/origina...jellybean-4-1-2-20-11-2013-a.html#post6823310

This also happened to another older rom I got from Sammobile.

Is it possible these Stock ROM uploads are infected with malware?

Just SuperSU.