yashsingh1/xdaforums huggingface dataset:
[SuperSU] sansnil:
Thanks, Chainfire. Since you have to do the heavy lifting I figured the least I could do was the most helpful route.

Device info

: Galaxy Nexus GSM, tuna/yakju/maguro. Android 4.3, baseband: I9250XXLA2, Kernel: 3.0.72-gfb3c9ac, Build number: JWR66Y

After the full reinstall, steps to reproduce are

:

1) Get root (unlock bootloader, flash TWRP, flash SuperSU-v1.65.zip with TWRP 2.6.1). Reboot device to system.

2) Verify root access by checking app install of SuperSU, testing with a couple different apps that need root. Root confirmed working - cool.

3) Use the phone normally for a few hours. Email, Tapatalk, web, hangouts, etc. After a few hours reboot.

4) White Google logo appears as per normal, then the Google colored X which is where it boot loops. If you've ever obsessively watched like I have now there's an initial longer period where the X is on full brightness, then toward the end of a normal boot it dims slightly probably when it picks up the "auto" brightness setting. When it boot loops, I can see it transition to the dimmer X but it lasts longer than it normally would and then eventually flips back to the brighter X again. It stays this way.

A few additional notes in case helpful

:

1) I have found by booting into TWRP recovery when it's boot looped I can temporarily solve it by deleting two files /data/system/locksettings.db and /data/system/locksettings.db-shm. No idea why - I used trial & error to find these.

2) The boot loop doesn't occur right away. After I did the new full install and after I manually delete the two files if I reboot the device right away it won't loop. If I use the device for a few hours it will boot loop the next time. I have no insight as to what's occurred (i.e. I didn't install anything new/different, haven't noticed any app I use correlating to it etc.)

3) This issue most definitely started after the recent Google OTA 4.3 security update.

4) After the SuperSU 1.60 update very occasionally when it boot loops the screen while finally wink out after a long long long boot. The device is barely responsive but if I keep trying I can sometimes get a partial draw of the normal device screen as if it's booted correctly but somethings making it so unresponsive the screen is never fully drawn and I can't interact with it at all. I can't be certain but it looks like the pattern lock scren has been bypassed or maybe just hasn't had time to be displayed. This doesn't happen every time but I never saw it get this far until the 1.60 update.

Hope this helps -- let me know if there's anything more I can do help. Many thanks!
[SuperSU] shivasrage:
Nearly the same issue for me:

Nexus 4

JWR66Y deodexed stock

Kernel: stock

Baseband: stock shiped with JWR66Y

First I flash SuperSu v 1.65 then I have to install the new binary after that SuperSu recommend a reboot.

5-10 sec. after phone booted (quite normally) ....some FC appear for example...

calender has stopped, clock has stopped and so on...after that phone reboot....

into recovery (6.0.3.6 is latest cwm i think) and ask fix root?

It doesn´t matter if I tap yes or no phone reboots and and all happens from beginning.

But sometimes there is no FC and the phone works full normal and there are

no issues like that at all.

Tried a clean install....same issue.

thanks
[SuperSU] efrant:
It's something with your ROM or one of your apps. SuperSU v1.65 works fine on my N4 running stock JWR66Y.
[SuperSU] Chainfire:
Ok, I've flashed a GNex with the same firmware, rooted it, let's see what happens. As I take it, you can reproduce this problem even after a data wipe / reinstall ?
[SuperSU] sushil888:
thanx a lot

yes !!

at last this version works for me 1.65.

with last two i did struggle. galaxy mini india, 10.1. rom cm 7-9-2013.

thankx, chainfire.
[SuperSU] :
works great here.. galaxy nexus stock 4.3 jwr66y deodexed...
[SuperSU] abobobilly:
EDIT: Thats strange. It was the 3rd time i lost root by updating the app to 1.65 (through play store) ... and then while updating the binary (when it shows the message in the app). But when i flashed the older 1.51 ZIP (for root), not only was i able to get the Root back, but the App also stayed at 1.65.

Well the problem solved by itself -.-

-----------

I have a Nexus 7 2012 runnng 4.3 JWR66Y.

The problem is that if i keep the version 1.51, the root remains.

As soon as i update the app to the latest version 1.65 and update the binary after booting, tablet loses root. If i flash back the 1.51 AGAIN then i get back the root.

What could be the issue?

Just to mention it, i received the JWR66Y update a couple of days ago. Previously all was going well on JWR66V.
[SuperSU] sansnil:
Yes, it's definitely reproducible on my device. It takes a while to start occurring though, almost as if something has to update or change, but then after rebooting it will loop.
[SuperSU] ElBeaner:
Ok have a small issue on my HTC One

I flashed the new SuperSU v1.65 in recovery after I upgraded my rom(Dev includes Superuser in rom).

Rom is ARHD 20.2 4.3jellybean w/ Bulletproof Kernal

Now whenever I flash something new in recovery(mod/bootsplash) at reboot time I am greeted with TWRP telling my Root has been lost and I need to fix permissions. I always say yes.

How I do I fix so this no longer happens?
[SuperSU] slebit:
That is a problem with twrp.
[SuperSU] Azarin:
Just a quick update on my missing SU binary issue. I verified each step had been done in the installation zip from recovery and still wasn't having any luck.

Finally got it working again with a full factory reset in the end!
[SuperSU] ElBeaner:
Ok, so known bug TY.

Do I need to be overly worried about this? Or just keep choosing fix permissions?
[SuperSU] Bill Gamble:
It's just an annoyance. It makes no difference whether you pick "Fix" or "Don't Fix".
[SuperSU] edd080:
In my case i had managed to solve it by installing the official TWRP recovery which is at version 2.3.2.3 if iam not mistaken.. and i dont get the fix root warnings anymore... Hope this helps.
[SuperSU] Kustaa:
Works fine here too. Galaxy nexus stock 4.3 jwr66y. No bootloops.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[SuperSU] SYRE123:
I'm running Janjans GE-ROM on my GT-I9505 and updated to 1.65 by mistake from the play store. When I open SuperSU it tells me that I have to update my binary files. I'm new to root and doesnt want to make any mistakes so I just pressed the back-button. My rooted apps still works, downloaded root checker and it seems that I still have root access.

Now I'm afraid to reboot my phone in cash I get stuck in a boot loop. What am I supposed to do? Any suggestions?

I'm using Philz recovery btw.

Thanks in advance, hope someone will help a newbie out!
[SuperSU] Dan1234567890:
I have the same issue running twrp 2.6.0.0. on N4 and PA 3.99.

I solved it by flashing supersu 1.65 AGAIN from recovery, and the message disappears... And doesn't reappear till I flash something again... ;)
[SuperSU] NicholasQ:
I'm no developer, so this post may be just me going full retard.

But I've noticed my phone (nexus 4) will sometimes start getting hot just randomly. I opened betterbatterystats to get some info on what may have been revving the processor up and the top process was daemonsu: 10082. I kept refreshing every few seconds and daemonsu was at the top by a large margin.

Is this supersu causing some issue? Or completely unrelated?

I'm running stock AOSP with xposed framework.
[SuperSU] Bill Gamble:
http://xdaforums.com/showthread.php?p=45470872
[SuperSU] sansnil:
[MENTION=5266287]enricocid[/MENTION] and [MENTION=4689937]Kustaa[/MENTION]

Are you using "Delayed Lock" by any chance? I'm unsure what the difference would be between why your gnexs don't have this and others do unless there's another app at fault.
[SuperSU] Kustaa:
No, I'm not using that app.

If any help, I first rooted with 1.5x, then update to 1.60, and finally to 1.65, vía PlayStore

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[SuperSU] sansnil:
I'm still waiting to hear back from a couple folks on whether they're using the app but I'm pretty sure it's a problem with Delayed Lock not SuperSU after all. I froze Delayed Lock on my gnex and it's been rebooting with the loop.

[MENTION=631273]Chainfire[/MENTION] I appear to have barked up the wrong tree. Apologies for any calories you burned looking into it but thanks very much for your help.

I'll update if anything changes but I opened a bug with the other Dev so this can be closed/ignored here.
[SuperSU] :
no ;)
[SuperSU] Azarin:
Strike that, I am now experiencing problems with the SU binary being missing, so here are a few more details as I think I have narrowed it down what is causing the issue, for me at least:

Phone details

Nexus 4, running stock Android 4.3 with the security update (JWR66Y)

When things stopped working

Everything was working fine on 4.3 until the security update, at which point whenever I start the SuperSu (Pro) app I get a missing binary error. I have tried various versions (1.43, 1.51, 1.60, 1.65), installed via TWRP, choosing NOT to fix SU file permissions when exiting.

What seems to be the problem

After experiencing the missing SU binary issue when loading, I resorted to performing a factory wipe + reset. After setting up all my apps and installing SuperSU 1.65 everything seemed to be working fine, root was functioning without any problems.

However, things when wrong when I connected my phone up to an exchange server which requires device encryption. After the device had been encrypted using Android's built in device encryption root stopped working at the missing binary error came back.

It seems that the encryption process is somehow stopping SuperSU from working. My device has always been encrypted in the past, and it hasn't caused any issues.

Has anyone else tried a JWR66Y build with an encrypted device and root access?

EDIT - More information provided below - it seems to be not just device encryption on its own
[SuperSU] wbedard:
I am also struggling with periodically loosing root with SuperSU 1.65. Unfortunately, my problem is with an unencrypted Galaxy Nexus running JWR66V. I'm still sorting out the various facts involved but it runs v1.51 without a hitch.

To answer your question though, I also have an encrypted Nexus 7 running JWR66Y and it uses v1.65 with no problems. I flashed the SuperSU zip from TWRP recovery, which supports encrypted devices.

R/

wbedard
[SuperSU] Azarin:
Interesting thanks for the feedback. The encryption seemed to the point at which it stopped working, for me at least, I'm not sure what else it could be.
[SuperSU] Azarin:
Update

Having done a bit more testing, it seems it is not device encryption on its own which causes the problem. It appears to be a combination of device encryption and Franco's Kernel.

I did a couple of tests flashing between the stock kernel and Francos, Root works fine with either encrytion OR Franco's, but not both. For the moment I have settled with the stock kernel so at least I can have root working.

The reason I didn't think Franco's was causing a problem before was that SuperSU seemed to work, but that was prior to encrypting the device. All very strange!
[SuperSU] Cyclu:
Chainfire if possible you can add: display the version of binary ex. in parameters under the version of SU
[SuperSU] Chainfire:
For the billionth time: no. Because if your binary version wasn't right, you wouldn't be able to get to that place anyway. And if it is right, there's no reason at all to know.
[SuperSU] xfim:
I've installed Android-x86 4.3 (from android-x86.org) on my stick and, well, its missing root. I can access USB stick storage so I already pu superuser.apk to system/app. However when i rebooted to android, it updated and said it needs su binary. i selected to install normal way but it failed. so i was wondering if i can add su binary manually via Win 7. Can somebody please tell me what and where should i put? i dont know if its already written somewhere in the thread but i dont have time to read all pages...

Thx
[SuperSU] einstine:
Ever since I tried to update to the new update for HTC One with Supersu survivor, it said it worked but it didnt, now the update wont show at all.

My battery now seems to drain very fast! and when I go into TWRP and go to reboot it asks if I would like to fix root, so I do it and I still have root. Just dont know what is wrong.
[SuperSU] :
supersu works for me... but on n7 i'm experiencing lags and battery draining after this update :(
[SuperSU] einstine:
n7?
[SuperSU] :
nexus 7 grouper ;)
[SuperSU] einstine:
haha my heads not in the right place, battery issues cause me to slightly loose myself. I hope there is a fix to this.
[SuperSU] NicholasQ:
The consensus is that daemonsu is going to show up when any app is using root.. But I'm looking at processes and can't find which app is causing this excessive heat and battery drain on my nexus 4. Does anybody have any ideas? Have you guys found a root app that was the culprit?
[SuperSU] NZgeek:
x86/su => /system/bin/.ext/su

x86/su => /system/xbin/su

x86/su => /system/xbin/daemonsu

common/Superuser.apk => /system/app/Superuser.apk

common/install-recovery.sh => /system/etc/install-recovery.sh

common/99SuperSUDaemon => /system/etc/init.d/99SuperSUDaemon

Everything you needed to know was right there in the zip file. Buried several folders deep under the META-INF folder are the updater-binary and updater-script. Usually the script does the install, but in this case it's just a dummy. The real work is done by the "binary", which is actually a shell script. Even if you don't know edify or sh syntax, it should be easy enough to follow what's happening.
[SuperSU] russellvone:
[MENTION=5383632]einstine[/MENTION]

I've experienced this also. What I did to fix it was:

Boot into TWRP recovery

Choose advance and then choose file manager

Now find the file 'su' and open it. While in the file choose the select button in the bottom right of the screen then choose delete. Now wipe cache and dalvick. NOW when you choose reboot and it asks you to fix root, swipe to install. Then of course, 'profit'
[SuperSU] einstine:
Didnt work still says that it needs to fix root every-time I reboot from TWRP. Thanks though.
[SuperSU] russellvone:
[MENTION=5383632]einstine[/MENTION]

If you have a flashable zip of superSU, after doing the delete su folder in twrp, flash it before reboot
[SuperSU] einstine:
Still didnt work
[SuperSU] Shafwan7:
after i update SuperSU v1.65 from playstore, it wont work on my device.

tried flash .ZIP v1.65 but still same superSU not work.

after revert back flash .ZIP to v1.60 , it work like usual. what happen to me ?
[SuperSU] sansnil:
As far as the TWRP message about fixing root permissions it seems to have been fixed in the latest version of TWRP (2.6.3.0) at least with my device (gnex).
[SuperSU] Dan1234567890:
Still no 2.6.3.0. for N4...

Edit: no 2.6.3.0 for mako through goo manager, but in twrp thread there is flashable zip in the latest posts... Just flashed it and seems like the issue is gone

:thumbup::)
[SuperSU] Will_Xda:
Hold another competition (like the icon one) but for in app themes. We've got a great selection of icons to choose from but not themes..... Make it happen dude! :D

Sent from my HTC Desire X
[SuperSU] Mardon:
@Chainfire

Just tested to install SuperSU 1.65 on Android 4.3 CM 10.2 and have a problem (ARMv6 device Galaxy ACE GT-S5830 Used ROM). On Android 4.2.2 CM10.1 everything works fine.

Install from market --> cant install binary

Flashable zip --> rom wont boot (stays in black screen) If i use Aroma filemanager from recovery i see all files are in right place

Integration into rom flashable zip itself --> rom wont boot (stays in black screen) If i use Aroma filemanager from recovery i see all files are in right place
[SuperSU] cteaser:
SuperSU 1.65 broken on my Nexus 7

SuperSU 1.65 appears to be broken on my Nexus 7 with (stock/OTA) Android 4.3.

Shafwan7 (post #3772) seems to have a similar problem.

After downgrade to UPDATE-SuperSU-v1.50.zip with CWM "su" worked again (1.60 might work as well)

With 1.65 "su" did nothing when testing in shell, daemonsu processes were not running.
[SuperSU] einstine:
How do you go about updating TWRP I tried goo manager but it of course did not give me the latest.
[SuperSU] polobunny:
It's a su management app, not a freaking ricer civic...
[SuperSU] Bill Gamble:
http://xdaforums.com/showthread.php?p=45570154
[SuperSU] jeetS:
Maguro

1.65 is working but I keep losing root on reboot....
[SuperSU] sansnil:
I usually look at the web site which does have 2.6.3.0 for N4:

http://techerrata.com/browse/twrp2/mako

Nice to have the older versions there too.
[SuperSU] wraithdu:
More to the BetterBatteryStats weirdness... even after I grant it permission, it still shows up in the SuperSU app with a gray hash sign. Further I can't remove / delete / forget it. If I do, it will disappear momentarily, but will reappear after hitting the refresh button or switching to a different view and back again. The only way I was able to fully remove it was to clear SuperSU's data.
[SuperSU] Sebby:
great apps

with root explorer i get only the popup in virtuous a3 sense 4.0

the other sense 4.0 rom no luck at all (no popup deny and grant with rootexplorer and some other apps)

i find it really wierd.....:confused::confused::confused:
[SuperSU] sparksco:
I'm still having a strange issue. When my battery level gets low I loose all cellular service to where I can't make or receieve calls/text. If I plug it in to charge I do not get service back. If I reboot my phone.apk starts force closing non-stop. I thought maybe this was a issue with my battery but after reading others issues on the battery stats I'm thinking this is related to that. The only thing that fixes it is a nandroid restore. And it only started happening after I switched from SuperUser to SuperSU. Normally I'm not able to replicate it ondemand to get a logcat of it when it happens :banghead:
[SuperSU] dadi_pas:
Beter than Superuser... SuperSU slow notification....
[SuperSU] segv11:
Better Battery Stats doesn't record your "grant always" permission when the dialog pops up

Workaround: after this happens, launch SuperSU and go to the Apps tab. BBS will show up with gray #, meaning default is "prompt". Click on it, choose Access: Grant, and save. Next time you unplug, BBS will do its "dumpsys alarm" without error. Check SuperSU log to verify.
[SuperSU] yajirob3:
Hi CF,

I got some problem with SuperSU. When I open TerminalEmulator and type su, then the subsequent commands always getting this error:

sh: precmd: not found

When I switch back to use superuser and do the same thing, I don't have this error.

I'm on I9100 with DXLP7 and Siyah3.0b4 kernel.
[SuperSU] grgsiocl:
go in to supersu application settings and set default access to grant...

Thats, all ...none of the apps will not bother you for asking the permissions!
[SuperSU] segv11:
That kinda defeats the purpose of having SuperSU ;) Some apps (like Google Wallet, as well as random malware) need to be denied.

The problem the poster had (which I had too) is that I granted permission to BetterBatteryStats when the permission popup appeared, but SuperSU did not "remember" this grant, even though it was asked to do so. SuperSU seems to remember the grants for other apps no problem; it's just BBS that is not being remembered.

In this case, going into the main SuperSU interface and manually granting permission to BBS seemed to be the correct thing to do, and it solved my issue. I hope it solved the poster's issue as well.
[SuperSU] brycie:
Tried that and it still asks for root access every time. I have the green # in superSU for BBS but its still asking for root everytime I choose alarms.

UPDATE:

Plugged phone in and tried the alarms again this time no prompt. Rebooted phone and tried again without the prompt.

Left it 5 mins tried again and got the prompt.
[SuperSU] segv11:
Interesting; that fix worked for me. I wonder if we can figure out what's causing the difference between your system and mine because that might give the dev a hint on what BBS is doing that confuses SuperSU.

I have SuperSU 0.83 (83) with the Pro key. I moved the SuperSU APK to /system/app using TiBu. SuperSU is configured with PIN, and with Survival mode. Default access is "prompt", default logging is "Full Content". BetterBatteryStats is 1.7.1.0 (16). Phone is LTE GNex running 4.0.2 ICL53F.

@Chainfire, can you think of any other info that would be useful to debug this funny interaction with BBS?
[SuperSU] brycie:
SuperSU 0.83 Pro as installed on CF LC1 kernel for GT-N7000 all settings default.

BBS XDA version 1.7.1.0 shows in superSU as com.asksven.betterbatterystats have turned logging on for this app but it doesnt log anything. Just get red text telling me that contents havent been logged.

Hope that helps
[SuperSU] hadi_rena:
I already grant access in SuperSU (# already green from app) but still same... and for the log show allowed because I grant it in pop up
[SuperSU] monomer888:
My setup is almost the same as yours with prompt windows using BetterBatteryStats 1.7.1.0 (listed as com.asksven.betterbatterystats in the Super SU app) even if set to Grant root access.

SuperSU was installed with the CF-Root LC1 kernel (on stock Gingerbread LC1 firmware on the Galaxy Note). I bought the SuperSU Pro key and I'm able to enable full logging though, and all it gives is a very long list of alarms beginning with "Current Alarm Manager State".
[SuperSU] brycie:
If I turn full logging on at global level then I do get log results for BBS. Just seems the app only loggin doesnt work for BBS works fine for adfree.

UPDATE

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

OK I seemed to have fixed the problem I was having by purchasing the version from the market. So it looks like the issue is in the XDA version and not the market one if that helps anyone.

Market version shows up as BetterBatteryStats in superSU not com.blah.
[SuperSU] segv11:
Yep, I have the Market version, and it works "correctly" after I manually "grant" in SuperSU. It still doesn't work the first time though, I have to grant from within SuperSU, not the popup.

@Chainfire: if the buggy interaction is different between the two versions of BBS, does that help pinpoint the problem? I would be curious what the differences are between the two BBS versions.
[SuperSU] hadi_rena:
Hi after some restart (more than 3 times) suddenly SuperSU doesn't prompt for access anymore :confused:

Nothing changed in superSU configuration (root access already granted) maybe it's can help others cheers
[SuperSU] segv11:
On a related note, Stericson's Busybox Pro also has a similar problem where granting permission from the popup doesn't work, but once you grant from inside SuperSU it works fine.

It looks like both BBS and Busybox Pro may be hitting SuperSU with a lot of superuser requests in a row, without waiting for the response from the user. Could these rapidfire requests be tickling a race condition where the grant from one request doesn't get written before the next request comes in?
[SuperSU] shaggyskunk:
Yeah, I just updated BusyBox & wasn't sure if it was me... but granting permission seemed a bit dodgy... Had to hit grant several times, before it accepted? But in the end, all seems fine.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Chainfire:
This is probably the root of the problem yes, hopefully it will be fixed in the next version :)

I thought I caught all the possible race conditions for v0.83, but I found another one which I suspect is the cause of these problems. Will be checking this out over the next few days. However, I still can't reproduce the problem itself, so... rough going!
[SuperSU] sparksco:
I had the same issue on my sense rom so I could update the busybox version to v0.83. It kept prompting over and over again and then finally I just went into the SuperSu settings and selected grant.
[SuperSU] Cyclu:
Sorry Chainfire i have overlooked with my first search in the thread.