yashsingh1/xdaforums huggingface dataset:
[SuperSU] mobileman88:
Make a Nandroid and do a full wipe before flashing if it happens again. Have never had this issue.
[SuperSU] belloni:
Currently have a pixel running root but the app naptime doesn't seem to run itself? See image of my SuperSu log, anyone else facing this issue? The times it show are when I've opened the app.

http://imgur.com/awr54DP
[SuperSU] grep_i:
I have a cleanup script for that, flash it before SuperSU and your good to go.

follow link here
[SuperSU] egingell:
Your problem is with whatever naptime is.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ajay vadaparthi:
Thanks for your reply. In the meantime I flashed SuperSu latest version again using twrp and wiped only & Only Dalvik Cache. this solved my issue currently. I'll try your cleanup script and report.
[SuperSU] belloni:
It's by Franco, he said it would be SuperSU.
[SuperSU] egingell:
An app that is supposed to run by itself, but doesn't even attempt to, is somehow a SuperSU problem?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ulxerker:
indeed there's no problem between naptime and supersu, they're working fine together like always and ever. so there has to be another issue.
[SuperSU] Muhammad Rihawi:
Anyone tried to root S7 android 7.0 beta?
[SuperSU] Ibuprophen:
Try searching XDA for Rooting the S7.

This is SuperSU Stable Specific...
[SuperSU] HorstiG:
He means Nougat root with SuperSU, everything else is sh...

I mean the same.
[SuperSU] belloni:
Are you using them with no problem then?
[SuperSU] ulxerker:
exactly.
[SuperSU] belloni:
Do you have it as in optimised the app itself also? And it's running fine for you in the background under SuperSU each time you press screen off?!
[SuperSU] ulxerker:
you mean battery optimized by system? if so, then yes.

and yes, its running as expected in the background when switching off the screen.
[SuperSU] belloni:
Hmm strange, so to clarify under your SuperSU log it appears each time you've screen locked? My phone has barely any apps so don't know what could be causing the issue.
[SuperSU] ulxerker:
sorry, I disabled logs completely. but I see in third party apps (i.e. Greenify's doze monitor) that doze kicks in immediately after screen gets off. so if it doesn't show up in logs its maybe a reporting issue by Naptime but its working, though.
[SuperSU] Gudiputisai.008:
Super su is safe

i heard supersu is not safe on my think kingoroot is safe can u tell its right or wrong:confused:
[SuperSU] grep_i:
Don't know what you mean with it, both methods can root and can be potentially harmful to your device as your toying with the device's security.

You have to watch what you're doing every step and know about everything you install after rooting your device because of the potential security breach you created by rooting.

So I think the answer is both methods are as safe as the user that's applying them.
[SuperSU] ldeveraux:
Hilariously wrong.
[SuperSU] lehongwang:
Im.using s7e with nougot 7.0, after supersu, I cannot turn on wifi, please help
[SuperSU] mcscout:
Only one app becomes root

Habe ein neues Phänomen. In SupperSu sind mehrere APP's mit Root-Rechten eingetragen. Starte ich eine davon, erhält nur die APP Root-Rechte, die nach einem Start des Systems zu erst gestarted wurde. Alle anderen nicht.

Bsp.:

1. Neustart

2. starten der APP PhoneInfo *Samsung* -> erhält root

3. start TitaniumBackup -> kein root, auch kein Eintrag im Log von SuperSu

4. Neustart

5. start TitaniumBackup -> erhält root

6. starten der APP PhoneInfo *Samsung* -> kein root, auch kein Eintrag im Log von SuperSu

Was habe ich falsch gemacht?

Achso:

SM-G800H

Android 5.1.1

G800HXXU1BPB4

Root-Methode: CF-Auto-Root-kmini3g-kmini3gxx-smg800h.zip nach autoroot.chainfire.eu

SuperSu 2.78

I Have a new phenomenon. There are several APP's with root privileges in SupperSu. If I start one of them, only the APP root rights will be issued after a system startup has started. All others do not.

Ex:

1. restart

2. start the APP PhoneInfo * Samsung * -> gets root

3. start TitaniumBackup -> no root, also no entry in the log of SuperSu

4. restart

5. start TitaniumBackup -> gets root

6. start the APP PhoneInfo * Samsung * -> no root, also no entry in the log of SuperSu

What I have done wrong?

btw

SM-G800H

Android 5.1.1

G800HXXU1BPB4

Root method: CF-Auto-Root-kmini3g-kmini3gxx-smg800h.zip from autoroot.chainfire.eu

SuperSu 2.78
[SuperSU] Cookie Ninja:
It's the other way around....supersu has, so far been created by chainfire, while kingroot/kingoroot is a dubious app from China....

Dead Cookies leave no trails...
[SuperSU] shaggyskunk:
THIS!

Sent From My SM-N910W8 ??
[SuperSU] andrew2432:
The dubious is opinion right? Just leaves some files that are very very difficult to remove that MAY OR MAY NOT allow unwanted access...
[SuperSU] Ibuprophen:
Try looking through (or post this question) in the S7E portion in the XDA Forums...

This may be something that another individual had an issue with that could be S7E specific.

Just a suggestion...

Peace and Love!

Peace and Love!
[SuperSU] egingell:
It's not opinion. Kingroot makes it incredibly hard to remove itself for no reason other than spite.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Ibuprophen:
Kingroot does the job but, there's a price (not monetary...) as it installs other bloatware type of apps and will stop working if you uninstall those.

I'm not a fan of Kingroot :(
[SuperSU] shaggyskunk:
The discussion of kingroot is getting a little OT - So here's something more.. You can see the source from the screen shot - I should point out that I have no experience with kingroot whatsoever.

Apologies to Chainfire for the OT - However I wouldn't dream of trusting any of my devices to anyone else but Chainfire.

Sent From My SM-N910W8 ??
[SuperSU] Ibuprophen:
Maxed out my Thumb's Up So here you go.

I give you 3 Thumbs Up!

:good: :good: :good:
[SuperSU] CptGia:
I was snooping around in the supersu update-binary script when I found, in the boot patching pre-checks at line 1330:

$CONTINUE=false

Shouldn't it be

CONTINUE=false

without the dollar sign? It may causes problems for chromeos ramdisks...
[SuperSU] Ibuprophen:
Usually the 3 periods in a row "..." indicates either "etcetera" or "to be continued" or "continuing".

Or your just trying to build up the number of posts.

Can you please elaborate?

Thank you!
[SuperSU] Jiikuy:
I have successfully installed SuperSU and anything is working good. But if I open a root shell, go to /sdcard and type ls, the folder is empty. If I type in 'mount' it also doesn't appear. Can anyone help me?

I have a SWITEL Rock S4500D (only available in Switzerland) It's running Android 4.4.2. I have installed SuperSU from TWRP.
[SuperSU] jcmm11:
Are you sure it's a root shell? Is the shell prompt #

Once you start the shell did you enter sure

If the answer to the above is yes then do you have Busybox installed? Pretty sure those commands aren't available natively in 4.4.2 (they would be in 6+)
[SuperSU] Jiikuy:
Yes, it is a root shell, and i have already installed BusyBox.
[SuperSU] mcscout:
Could someone help me with this problem please http://xdaforums.com/showpost.php?p=69631164&postcount=504?
[SuperSU] grep_i:
Unroot completely from within SuperSU app boot to recovery and flash SuperSU again.
[SuperSU] mcscout:
I've done it twice, but no effect!
[SuperSU] pkelly517:
Google is your friend.

If you can't decide on your own, why ask random people on the internet?
[SuperSU] elbi14:
Lol
[SuperSU] jdegreef:
I got an email notification to read this !!!

Nice contribution :eek:
[SuperSU] floel:
I flashed SuperSU 2.7.8 using TWRP on my S7 (european) with Android 7 beta. WiFi wasn't working anymore (stayed on "enabling..." forever). Other seem to have similar issues.

FYI for those asking.
[SuperSU] NLBeev:
When you 'think' a program is safe, it is interesting to tell why.

About SuperSU.

The dev. Chainfire is active here on XDA and other forums. We get a lot of info about SuperSU. Do you have that kind of info about kingoroot?
[SuperSU] vampirefo:
Doesn't work om my Intel, the app can't unpack the boot.img, is there a command to just have it install in system?
[SuperSU] grep_i:
It's embarrassing, why you answer a 4 days old post, that was already been dealed with.

No need to do that, see what happens people react on your reaction.
[SuperSU] FernBch:
I have a question. I am a tester for a group of custom ROM developers for the Galaxy S4. We are now publishing AOSP 7.1 builds with unified device support (CDMA/GSM variants). Some of the devices supported have locked bootloaders but can flash custom ROMs/kernels thanks to Loki. My question/request is related to systemless root on these devices. Please see the below post I copied from another thread I created. I can get a recovery.log of the install if it is needed.

I have a SU question for those in the know.

Device: SCH-I545 VZW SGS4

Bootloader: VRUAMDK Original Loki exploitable, never took an OTA

ROM: Custom AOSP 7.1/CM14 based Nougat

Here goes, hopefully I make sense.

In the past custom ROMs used "system mode" for SU, 2.52 or 2.65. With the introduction of "systemless" the way of the future is becoming apparent. Some updated apps don't work well or at all with system mode.

The SCH-I545's bootloader is locked but can be gotten around with the "Loki" exploit by [MENTION=1978378]drbliss[/MENTION] for installing custom ROMs/kernels. The problem with SuperSU in systemless mode is patching the ramdisk with a locked bootloader. During the install of a systemless package when it gets to the step where the boot.img is patched it fails. Screen output will say "decompressing ramdisk" then "failure, aborting" and continue until complete but SU does not work.

Some SGS4 variants like the I9505 have an unlocked bootloader. So, for an experiment, I got a copy of the boot.img from someone using the same ROM as I (we have a unified device tree) after SU install and boot. This file has been patched by the SU flash process.

I took the ROM zip, deleted the boot.img, replaced it with the patched img, and flashed the ROM. Lo and behold it booted AND has SU access. The ROM flashes SuperSU 2.78-SR1 by chainfire.

During SU install from recovery it showed the usual failure when it attempted to patch the boot.img but since I had a "Pre-Patched" file systemless mode installed and works just fine. A quick look in the file system shows a systemless install. End result? Systemless install is possible on a locked BL device.

My question is how to get there. I am no developer. Beyond hacking/modding zips and editing the build.prop, updater-script, update-binary, etc. I get lost and java/C++ is a mystery. Is it possible to get it to succeed with something similar to the Loki process or by modifying Loki??

Just thinking out loud here but thought, input, etc. is most certainly welcome.
[SuperSU] andrew2432:
One of my Gmails got blacklisted due to using kr...

To try to be on topic, trying stables with my lgg2 but it's not my daily so updates may be sporadic...
[SuperSU] Ibuprophen:
You'll have to ask [MENTION=7678190]SuperSU Release[/MENTION]
[SuperSU] Strephon Alkhalikoi:
The latest SuperSU versions can be forced into system mode; something that the current install script for the ROM does not do. If you're able to update SuperSU to the latest by forcing it into system mode, then JDC Team should stop automatically rooting the device since for you and others like you some preparation is required. Otherwise, JDC Team could provide the pre-patched boot image with their release instead of the original and remove the automatic flash of SuperSU after flashing the system image.
[SuperSU] hungapple:
[STABLE][2016.09.01] SuperSU v2.78

:Dthank your
[SuperSU] FernBch:
Thanks for the info. One of the bundled apps no longer works with system mode and the majority of the devices will flash systemless without issue since the BL is unlocked. I'll pass the info along and see what the consensus is.
[SuperSU] Strephon Alkhalikoi:
The developer of that app needs to update the app then to support both system and systemless modes. Otherwise, they need to offer two different versions of the app, one for system root and one for systemless, as I do for the pre-malware versions of ES File Explorer linked in my signature. Not supporting users that have system root, such as most users of Cyanogenmod, is silly.
[SuperSU] grep_i:
I think it's not silly but a choice you can't keep supporting everything, so one should make choices what seems logical to support and what not.
[SuperSU] FernBch:
There are two versions of the app available and root is needed for each. The app allows all kinds of kernel mods for governor, hot plugging, etc. so root is part of the ROM.

I was just curious about how difficult it would be to modify the install script so systemless works on the locked BL. In the system mode versions of SU it would flash successfully on all devices but systemless does not. Someone tried to tell me that systemless is not possible on a locked BL but I already know that's not the case. If I could figure out how to get past "decompressing ramdisk, failure, aborting" it would be perfect. In the eyes of a ROM developer everyone then runs the initial build as published without any mods.
[SuperSU] Strephon Alkhalikoi:
[MENTION=6952047]grep_i[/MENTION]: Cyanogenmod still uses system root, so an app that cannot find system root is silly. In doing so a large portion of the custom ROM scene cannot use the app.

Developers could eliminate this headache by searching for the su binary, but some of them apparently take shortcuts, like ES File Explorer.
[SuperSU] FernBch:
I should add in there since swapping the kernel in the ROM's zip file with a prepatched version I see no difference in how root and root dependent apps work.
[SuperSU] egingell:
Nobody needs to search for it and it's actually lazier to do it the right way.

su CODE

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] FernBch:
Also, the ROM of choice for me is AOSP, not CM based.

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

I wish I could remember to type all this in one post, sorry.

The SU version that is used is not baked into the ROM either, it's a su zip that installs after the ROM.
[SuperSU] Strephon Alkhalikoi:
Obviously I didn't phrase things correctly. What I had meant was that developers shouldn't use the method ES File Explorer uses to find root, which is hard-coded paths. It's not an issue of laziness, unless you consider unwillingness to use the right way lazy.
[SuperSU] grep_i:
Can you post the recovery log maybe we can help to find out what makes this error message appear and fix it.

Is there a specific reason as why you can or will not unlock the bootloader ?

If people with Cyanogenmod want to use that specific app they can always go and install SuperSU systemless but that's not the discussion here.

A developer may choose what he wants to support even if you don't like it and therefore it is still not silly but a choice.
[SuperSU] FernBch:
Personally, if I could unlock the BL it would have happened yesterday. The device is a Verizon device and and no matter how many times I ask they nor Samsung will not unlock or let me know how to unlock it.
[SuperSU] bhavstech:
solved
[SuperSU] FernBch:
Solved?

---------- Post added at 11:33 AM ---------- Previous post was at 11:30 AM ----------

I have a new build to test and I will be flashing after work today. I'll save the recovery log and upload to DB and link here.

Thanks
[SuperSU] FernBch:
Hello Everyone,

Tonight I flashed the next test and, as expected, SU2.78-SR1 failed to install. Steps to flash:

Wipe data, cache, davlik, and system.

Flash ROM

The install process for the ROM is the ROM installs first. When the install finishes then SU installs. Screen output shows extracting ramdisk, decompressing ramdisk, then failure, aborting.

When the ROM is booted there is no root access available. As requested I saved the recovery log

https://www.dropbox.com/s/qyaiplisfc9tdsu/recovery.log?dl=0

Hopefully the solution is an easy one if anyone decides to take a look.

In the meantime I'll get a pre-patched kernel, swap it into the zip, and flash the build again. After flashing with this mod the ROM will boot with a fully functioning systemless root.

Thanks for looking.
[SuperSU] Elanza_48:
Deleted**
[SuperSU] JonnyTech:
I read that this now supports Android 7.0 but can anyone confirm that it works on 7.1?
[SuperSU] shaggyskunk:
Absolutely v2.78 works perfectly with 7.1 on 3 different devices - Samsung Galaxy Note 3 & 4 and Nexus 7.

Sent From My SM-N910W8 ??
[SuperSU] Mempler:
Nice

Very Nice!
[SuperSU] bladenet:
Hi guys! i've try to install supersu with TWRP 3.0.2.0, but i've a problem with extracting ramdisk.. when i reboot the phone, i haven't supersu installed.

This is a photo of the screen.. how i can fix it?
[SuperSU] FernBch:
Which device and is the bootloader locked?
[SuperSU] bladenet:
My device is SM-G361F and i think that bootloader is unlocked. How i can control it?
[SuperSU] Ibuprophen:
When it comes to the inner workings of the SuperSU, asking the dev(s) [MENTION=7678190]SuperSU Release[/MENTION] is your best bet.
[SuperSU] FernBch:
If your bootloader is unlocked that isn't the cause of your issue.

Maybe someone else can help.
[SuperSU] onetwoselekta:
Not working on CyanogenMod 14.1
[SuperSU] shaggyskunk:
Really???

Looks like it's working just fine on CM14.1

Sent From My SM-N910W8 ??
[SuperSU] Chucky_xxl:
no root after this install stock 6.0.1 but su 2.46 works fine only without binaries update
[SuperSU] Elanza_48:
Guys

I had a question, that is, does systems less root really works on cm 13 and 14.x on flashing SuperSU ?

The reason for asking this question is, I find it merges with the cm superuser after flashing and the su binaries does stays in the bin and xbin directories in the system partition. Unable deleted through any file managers . I think that is because it is executed on every boot. So I deleted those through recovery and noticed many apps like SELinux enabler and stock cm file manager does breaks root permission despite of been granted by the SuperSU.
[SuperSU] grep_i:
You have to flash SuperSU after removing CM superuser
[SuperSU] Elanza_48:
So can you tell me how to do so ?
[SuperSU] grep_i:
I guess you already removed CM superuser as I read your former post.

So at this point you should probably flash SuperSU again and the problem will be solved.
[SuperSU] Elanza_48:
Oh, you mean to say after removing the cm su binary files I have to reflash it over the same ?
[SuperSU] grep_i:
Yes flash chainfire SuperSU after cleaning the cm su binaries.
[SuperSU] Elanza_48:
Ok, let me try. Thanks for the reply.
[SuperSU] jdegreef:
What error message do you get ?

My technical knowledge is too limited to understand the log properly but apparently it's searching for busybox and don't find it...
[SuperSU] HakanCelikMK1:
SuperSu reports that the SU binary needs to be updated. When I tap continue, it provides two choices (Normal and TWRP/CWM). I select normal, then it tries to update the su binary and after about a minute reports that the su binary couldn't be updated. Then it says "Installation failed! Please reboot and try again.".

I've repeated that procedure a few times, but the result is the same.

I've also tried with BusyBox installed, but the end result is the same. I'm not even sure this device is rooted. Does being able to execute "mount -o remount,rw /system" on adb shell indicate that it is rooted ?
[SuperSU] jdegreef:
Try the TWRP/CWM option. I should create a zip file to flash from TWRP or CWM depending in the recovery you have.
[SuperSU] shaggyskunk:
Have you just gone to the OP - Download the v2.78 zip - Flash with TWRP? Works every time for me on multiple devices.

Sent From My SM-N910W8 ??
[SuperSU] Ibuprophen:
By the way...

Just an FYI, when you flash the current SuperSU (Stable or Service Release) via recovery, it will reflect that SuperSU is installed via the Play Store. Flashing it via the recovery installs both the app as well as the scripts all at once. So don't fret it.

I remember someone asking me this (a little panicky) previously. So I just wanted to add this little bit of a caveat.

Good Luck!
[SuperSU] HakanCelikMK1:
Thank you. I'm still trying to find a suitable TWRP image for this device. Since it is a generic Chinese device (Allwinner A31 / sun6i) I haven't been able to locate an image for it.

It appears I will have to search harder :(
[SuperSU] jdegreef:
First link searching Google with "Allwinner A31 / sun6i twrp" http://j.mp/2gRQSOY

But might be a too old version.
[SuperSU] Ibuprophen:
Yes, there are some TWRP Recovery releases for your device.

Here are some links to help you along:

1) [ROOT/CWM/KitKat MOD] Allwinner A31 Series - Dyno 7.22 / Bmorn M2 (1024) by JBolho

2) [ROOT][TWRP RECOVERY] Onda V972 Quad-core | Allwinner A31 by ankar84

3) Nobis NB07 and DA-741QHD rooting and ROM thread by neatojones

4) [rom] CyanogenMod 10.1 for Allwinner A31 (SDK 3.2) devices - 2013-07-15 update by Christian Troy

5) [recovery] TWRP 2.6.0.0

6) stable TWRP 2.6.6.0 now working for Kasty Onda 3.2 SDK firmware

7) [ROOT][TWRP RECOVERY] Onda V812 | Allwinner A31

8) Installing CWM or TWRP Recovery on ONDA V972 / V812 (Allwinner A31 tablets) with ArcTools

It looks like there are not allot out there for your device but, where there's a will, there's a way.

Always do your homework before altering a device because it can take a small innocent mistake to render a device to never work again.

Good Luck and God Speed!

Peace and Love!

Peace and Love!
[SuperSU] Ibuprophen:
Chainfire just posted the following:

This may or may not resolve the issue you are having.

Give it a try when it's released on the SuperSU SR thread.

I am assuming that it will be labeled:

SuperSU 2.78 SR5

Good Luck!
[SuperSU] Artieza:
That's really good, but I saw this, and it won't fix my problem which arrived with SuperSU 2.76.
[SuperSU] shaggyskunk:
If you have the skills - Here's the link from twrp.me on how you might be able to compile TWRP for your device...

https://twrp.me/faq/howtocompiletwrp.html

Sent From My SM-N910W8 ??
[SuperSU] jesssiii:
Try using FlashFire to flash the zip in the OP. Should work if, as you indicate, you have root.

NeXus 6P
[SuperSU] Alxoom33:
So Gabby, take the plunge. Don't be a wimp. LOL.
[SuperSU] RandomPooka:
Pretty sure that the *other* requirement named was Xposed for N. That one might take a bit, and even longer for module devs to update to the newer SDK.
[SuperSU] grep_i:
After flashing SuperSU-v2.78-201609011115.zip

In terminal it still says that su binaries are version 2.77

Checked also with an app which I normally don't (JRummy root check) and this also shows I have Supersu 2.77 binaries.

Can anybody tell me if this is a bug, normal as expected or did I probably do something wrong.

PS I had to reflash Xposed (systemless) also and my custom kernel (ElementalX). Which is normal because the SuperSU install reverts back to backup of stock kernel.

This makes you loose modified boot and because of that you have to reflash your custom kernel if you have that and in the case of having Xposed (Systemless) you have to reflash that too.
[SuperSU] ktmom:
That is normal this time around. The app was updated but not the binaries.
[SuperSU] grep_i:
So the binaries updated zip package is also only build for the updated apk.

So it was just to please the people who could not update through playstore than I guess.
[SuperSU] gregfrankenstein:
Under the new ownership, will there still be modified boot images I can flash? Not asking for an ETA, just whether they'll be a thing eventually. I clean installed Nougat rather than using FlashFire so I'm not rooted anymore.
[SuperSU] Federacion:
That's a big problem for me. Unfortunately I have to stay to version 2.77
[SuperSU] Chainfire:
CF-Auto-Root isn't going anywhere, at least not short term.