yashsingh1/xdaforums huggingface dataset:
[SuperSU] thorium666:
Hi,

The device is encrypted, where to copy it to? I was always using (on previous phone) TWRP with ADB commands. Is there any difference if i install it using TWRP ADB functions and file based ?
[SuperSU] brotbuexe:
This was reported by Chainfire himself. Currently there is a bootloop issue with S7 7.0, encrypted data and TWRP.

Maybe he releases a cfautoroot that supports encrpyted data without having to flash TWRP. Maybe TWRP gets fixed to not break boot.

For now if you want root on 7.0 you have to format data to get an decrypted data. Then you can get a boot with TWRP installed and flash SuperSU. If you have, you could then restore /data with flashfire or maybe TWRP itself.

(I restored a pre 7.0 data backup I made with flashfire, lost root, flashed supersu in twrp again and it works fine, but for now it has unencrypted data)
[SuperSU] thorium666:
I have flashfire installed but - it is currently not working because no root on the phone.
[SuperSU] brotbuexe:
Of course you can restore with flashfire only after you get root working.

Read the post from chainfire: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post70618589
[SuperSU] thorium666:
So, i can not use this method because root is not working without decrypting (Chicken vs Egg) :)
[SuperSU] brotbuexe:
Which method?

You HAVE to format data to get the device boot with TWRP and SuperSU flashed. Then it will work with root.

After this you can restore your data within flashfire if you made a backup before updating to 7.0.
[SuperSU] thorium666:
I made only a backup using this Samsung software, so i can't use flshfire to restore anything. I had several phones, all routed, the last 3 encrypted, had never such issues what was the reason not do something special for the backup, especially this is just a phone so there is no critical data on it. (i will just not spend 1/2 day on configuration again)
[SuperSU] BartVCD:
same here, we have to wait ;)
[SuperSU] shoey63:
Guys, N kernel is more secure than ever. You can't expect TWRP to read encrypted data with default_password. If your phone was stolen and you had an unlocked bootloader it would be easy for your data to be accessed by flashing TWRP.

Best way is to

- Flash TWRP

- Wipe /data factory reset (which will format data partition)

- Then flash SuperSU

You will be then rooted with no encryption.
[SuperSU] Ch3vr0n:
Well that's exactly what's it's doing for me. Haven't changed password yet, TWRP reads my data just fine.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] brotbuexe:
Yeah, the problem isn't Nougat kernel.

The problem on Samsung devices is the custom/different encryption Samsung uses which isn't just supported by TWRP (yet). And it was the same with pre Nougat. But we have a different issue with Nougat on the S7, it doesn't boot into system if you have TWRP flashed and data encrypted.
[SuperSU] Galactus:
Yeah, I was cool running encrypted data on Marshmallow and simply flashing system mods from TWRP. No desire to use TWRP backups etc. Since Nougat though, even flashing TWRP can cause bootlops, let alone the need to format /data so that it is decrypted. So looks like I'll be waiting for the time being.
[SuperSU] tauru242:
SuperSu 2.27 beta works great on nexus 4 with stock unpatched kernel. Tks Chainfire You are doing great things!
[SuperSU] mbirth:
Well, depends on your desired colour temperature. Even at more natural temperatures, black gets brown-ish. Try CF.lumen, you don't want to go back...
[SuperSU] Nicknoxx:
In that case, I've just bought the Pro version. Thanks
[SuperSU] dangelkov:
Nexus 5: Android 5.0, LRX21O, stock unpached kernel, SuperSU 2.27 BETA - Work perfectly!
[SuperSU] MarcraM90:
So if the Sony Xperia Z3 Series gets Android 5.0 it should work on it or am I wrong?
[SuperSU] vacsed:
Just found an app which doesn't work together with a stock N5 and 2.27: AirAudio. The app does request root and I can grant it but then it tells me that it couldn't get the SU privilegies. Used to work with 4.4.4 and 2.16. All the other apps work just fine with 2.27.
[SuperSU] Srandista:
It depends on Google, if they will fix this "issue" in system or not. But it does not matter too much on Sony devices, because you can unlock bootloader on them. So even if this method will not work on later firmwares, you will be able to flash patched kernel, like on previous releases of SuperSU and CFARs.
[SuperSU] MarcraM90:
the problem with unlocking the bootloader is that the camera quality gets hit
[SuperSU] Srandista:
Yes, I know. But at least, you still have that option to unlock and root your device. Then it's up to you, what you prefer more, if camera quality in stock camera app or root. I would take root every single day.
[SuperSU] Flowsen21:
On Lollipop / Nexus 5:

Is there a way to go back to complete unrooted stock to receive OTA-Updates after flashing the SuperSU zip?
[SuperSU] cgibbons51:
Go into SuperSU and do complete unroot [emoji4]
[SuperSU] galom:
Factory images on grouper and mako. Fastboot latest twrp , had to adb push file to flash in twrp. Running without issues on both devices. Thanks
[SuperSU] roundaway:
Unlocked, TWRP 2.8.2.0, Stock Lollipop, previously rooted with CF-Root.

Decided to fastboot the stock boot image so I could try the 2.27 beta. Now I can't boot into recovery. Reinstalled TWRP via fastboot but no good. When at bootloader and rebooting into recovery I get the TWRP splash but then the rom boots. When I use adb reboot recovery same thing. What did I do wrong?
[SuperSU] Ben36:
Use twrp 2.8.1.0

Sent from my Android 5.0 Nexus 5
[SuperSU] vacsed:
No reason to unroot, just flash back stock recovery and you still get all the OTA updates.
[SuperSU] occtec:
Just wondering, do we still need busybox with SuperSU?
[SuperSU] roundaway:
That recovery version worked perfectly. Thank you.
[SuperSU] K2ouMais:
Nexus 5?

Hello guys,

i flashed CF-Root with SuperSU 2.20 the day Lolipop got released by google on my Nexus 5.

Did CF-Root changed my bootloader or the kernel? How do i get back?

Do i need to get my bootloader or kernel back before flashing SuperSU 2.27? Or can i just get the Superuser.apk on my phone and install it?

I have the standard recovery, because i wanted to be able to get OTA updates.

Sorry for the questions, but i am a noob just now ;o(

Thanks in advance
[SuperSU] Srandista:
So... Yes, CF-Auto-Root change your kernel. If you want to get it back, you have to flash boot.img from factory image for Nexus 5. But, you don't need to do that just because you want to update SuperSU 2.27, it works with stock or modified kernel from Chainfire.

But I have bad news for you, OTA process has changed in Lollipop. So even if you will have stock kernel and bootloader, you won't be able to update with OTA. Same apply, even if you will uninstall root before applying OTA.
[SuperSU] K2ouMais:
Thanks for you help.

I just updated SuperSU to 2.27 without a problem. (I did just installed Superuser.apk with ES Explorer)

That means even if google releases a new android update i have to install everything from new again. I think i am alright with that.

Are the kernel changes that CF-Root made bad or good for anything?

It seems touch still doesnt work or the app HiroMacro isnt made for lolipop. ;o(
[SuperSU] Fif_:
[MENTION=631273]Chainfire[/MENTION], I ran into the same problems with zygote and zygote64 pop-ups and traced it to apps requesting su, then crashing before su had the time to grab the invoking app information.

As SuperSU can't find the invoker (it crashed), the su request proceeds, but SuperSU displays the zygote process name instead.

So it's nothing nefarious, but you probably want to find which app crashes while SuperSU requests are inflight and maybe uninstall it.
[SuperSU] folusmile:
It's not a virus. Plz Google it. I begin to noticed zygote popup when I installed Whatapp Extension. Whenever I open Whatapp it wil ask for Su permission and I grant it. Chainfire has said it a code from developer. If people are having headache concerning it once u grant Su go to Su again and denied it. Or u uninstall the app that bring it. ITS NOT A VIRUS.
[SuperSU] Crazy Chuckster:
I was looking at the SuperSU pro features and I have 1 question. It says - OTA survival mode (no guarantees)

Can anyone say if this works on a nexus 5x with the latest nougat update?

I upgraded manually yesterday to N4F26l by uninstalling SuperSU only and the OTA installed fine by itself on reboot. If the pro feature will let me OTA without uninstall I will gladly grab it.
[SuperSU] NLBeev:
You don't have to yell at me; search for the guy that did the suggestion.

Furthermore it's not logical too. When it's a virus it would be published elsewhere too.
[SuperSU] robertusIT:
i have trouble with securesettings app that doesn't recognize root.

how can i fix that?

I'm on nexus 5 with nougat and blue spark kernel
[SuperSU] Ja_som:
Securesettings works only with system (not systemless) root. Everything is in this and also in the securesettings thread.
[SuperSU] Pkt_Lnt:
Enable Compatibility mode via terminal in /data/.supersu as explained by Chainfire.

https://xdaforums.com/showpost.php?p=66140836&postcount=5493
[SuperSU] robertusIT:
thanks a lot, works!
[SuperSU] vandyman:
I am using the stock N5x January update with Su pro and and installed sr3 after. It has been working for me well over a week.
[SuperSU] robertusIT:
with securesettings works, but with Helium Backup not.

Stay in check superuser and doesn't go.....
[SuperSU] Pkt_Lnt:
Talk to the Helium Backup dev. He likely hard coded the path for /system su.
[SuperSU] egingell:
ADB, which Helium relies on, was removed from Android on some devices (my LG doesn't have ADB). And if Secure Settings works with its hard-coded path to su, then so should Helium. The whole idea behind Helium is to do backups without root. Root just allows you to not have to use the PC as a buffer, but it still requires ADB.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Cuculuz:
ROM Xpower X5

Device: xperia z5c

Ver: 6.0.1

Unable to update root binaries.

Installing from recovery fails ( bootloop)

Installing from google play (unable to update binaries " and root is lost")

Installing latest 2.79 r3 fails ( no root brinary update fails)

Back to old version.

I have SuperSu pro.
[SuperSU] Ja_som:
https://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] CyberpodS2:
[MENTION=631273]Chainfire[/MENTION] , After reading your post about the root and twrp issue with encrypted data, do you have any thoughts on if there is a connection between that and the current ongoing fiasco of Nexus 6P phones going into the bootloop of death?? So far nobody seems to have any real ideas on something that is happening practically every other day.
[SuperSU] freaky2xd:
Is there a non:systemless root for Android 7.0?!?!
[SuperSU] Ch3vr0n:
Yes. System or systemless is defined by ROM build. If certain root APS don't get root on systemless, the paths are hardcoded and the devs need to update the apps

Sent from my Nexus 6P with Tapatalk.
[SuperSU] Neo3D:
Do we have to wipe Dalvik and Cache after flashing? I didn't do that and it's taking like 30min to start? It doesn't look like a boot loop? The startup animation is frozen?

---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------

I'm having this same issue as you. But, I'm using TWRP v2.8.6.0.

I'm using RR-N-v5.8.0-20170117-hlte-Official.zip ROM
[SuperSU] Cuculuz:
Rom : xpower 5

Device : xperia z5c

Software : 6.0.1. (305)

Superuser fails to update (binary update fails)

Some apps will still have root "some have lost it"

Tried apk. Install

Recovery install

And changing to kingroot and back to Su with no luck.

Reverted back to previous ver of app.
[SuperSU] Elanza_48:
Of course its an bootloop, the device must boot up with in 15min even after u wipe the delvik cache. If u dirty flashed it then u might have to restore the boot image or reflash it then try flashing superSU. U need TWRP v3.0.x.x to flash the superSU.
[SuperSU] ipdev:
- Post moved. (Wrong thread.)

Note :

lineage-14.1-20170123-nightly and SR3 seem to be working for me.
[SuperSU] Neo3D:
Thanks, I didn't know we needed a higher version of TWRP to flash this. I'll figure something out.
[SuperSU] Elanza_48:
U can tryout with flashfire
[SuperSU] bdwilk:
I don't think you do. I'm using an old version of Philz Touch CWM and it flashed fine.
[SuperSU] jdegreef:
https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] napolionnardo:
Hi, I'm annoying to inform you that when you want to use the AdAway application I turn off the cell phone or something to you as you say bootloops. The same thing happened with the previous version of supersu when I told him that my cell phone was turned off. The Rom I am using is the same as before, called Nemesis v4.0 my device is g900h.

---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------

But that's not the worst. I tell him. I have integrated the latest version of supersu to the Rom and when installed from scratch in my device the supersu icon does not appear. It's strange, but that's the way it is. Is there any way to fix that? Thank you very much, sir. Again, it is a pleasure to have you.

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

If you want, I can upload my rom to some server for you to look at and see if everything is fine. Uploading it would only take me 5 minutes since I have 100 mega internet.
[SuperSU] clyder:
I just flashed SR3-SuperSU-v2.79-SR3-20170114223742 on a Galaxy S3 (i9300 international) with todays LineageOS and opengaps. No bootloops, all is working fine.

I am on a 3.0.2.2 TWRP.
[SuperSU] notameme:
I have a similar problem as well.
[SuperSU] noratroll:
Flashed successfully on SM-T815 (TabS2) ResurrectionRemix5.8.0
[SuperSU] thorium666:
Any idea when something will be released what supports encrypted nougat S7 with no wipe of data required? I'm open for tests.
[SuperSU] BartVCD:
me too, need a new F5 Key :D
[SuperSU] Az Biker:
Same SU version here, no issues, (TWRP 3.0.2-0)

PN 7.1.1 Rom, Full Dynamic GApps, EX 4.04 Kernel
[SuperSU] thorium666:
Hi,

in the Autoroot thread i got this tip which i don't understand. He is telling me to install SUperSU in system mode. Quesion: How to do this if SuperSU is currently not installed, can install it into the system directly ? I know this option only from already installed SuperSU.
[SuperSU] Amit™:
Now I'm on latest Official Lineageos Nd flashed Super Su Sr3 . . it's working great ...
[SuperSU] KaMyKaSii:
Ok, something strange happened here after using the app below. I'm going to report to dev, but I still think I should report here, maybe there's something to fix in SuperSU. Despite the 5GB data, I "only" found 1GB in /data/data/eu.chainfire.supersu. I looked in /data/app/eu.chainfire.supersu and the dalvik-cache folder, but I did not see anything suspicious. /Android/data/eu.chainfire.supersu does not exist in both internal and external memory. My finger is scratching to clear the data (since I'm out of space) but I'll wait for some instruction

https://play.google.com/store/apps/details?id=com.defianttech.diskdiggerpro

Edit, dev's answer:
[SuperSU] ktmom:
An easy way of doing that would be using this version. I have to wonder if installing in system mode isn't a work around for a out-of-date app though. You might consider reading Chainfire's post on compatibility mode.
[SuperSU] gothicVI:
Just wanted to report that sr3 runs fine on lineageos 13 on thea with xposed framework.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] thorium666:
This is what i tried, installed this version of SUperSU using TWRP, bootloop..
[SuperSU] ktmom:
I linked to the thread for system supersu. This thread is systemless. You tried installing the version I linked to? (Just go to the first post in that thread).
[SuperSU] thorium666:
Hi,

Thanks again, I've overlooked this detail.

Now flashed TWRP, installed no-verity-opt-encrypt-5.0 & SR3-SuperSU-v2.79-SYSTEMMODE, booted and waited 15 min, bootloop :(.

Did something wrong (S7, encrypted, nougat) ?
[SuperSU] egingell:
You can disable logging for that one app from the Apps tab in SuperSU...

You can also clear the logs from the Settings tab of SuperSU.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] jdegreef:
Ask in the SR3-SuperSU-v2.79-SYSTEMMODE thread. Encryption might be the problem.

Search for "encryption" in the box at the top of this thread.
[SuperSU] USHERROB:
You're Awesome! Thanks
[SuperSU] Dbj.Dhaval:
I am on nitrogen rom with flash kernel nexus 6p.since I have converted cache to f2fs only cache no data. I can't flash SuperSU. Getting ramdisk error.
[SuperSU] itinkerstuff:
Can anyone confirm if this is working on S7 Edge nougat?
[SuperSU] ulxerker:
yeah, its supposed to.
[SuperSU] BartVCD:
only with wipe and decrypted, encrypted not possible yet
[SuperSU] Meandi51:
Maybe noob question, but I don't know.

If installing older Rom (SlimLP on Gnex) should I use latest SuperSU

or the one (SuperSU 2.46) that was up to date, when Rom came out (12/2015)
[SuperSU] noratroll:
I recommend the latest
[SuperSU] nestade:
Hello :)

There is also a problem regarding "Systemless Devbase" by _alexndr (https://xdaforums.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178).

If you try to keep your device encrypted to be able to receive OTA you also get stuck at Samsung splash screen (TWRP -> Keep read only).

However it seems to be caused by TWRP because if you only flash TWRP and don't format data (Keep read only) and reboot without any modifications you're also getting stuck at the Samsung splash screen.

Seems like we have to wait for a TWRP update.

Regards,

Nestade
[SuperSU] tag68:
If you want OTA you don't flash twrp. Just use

fastboot boot (filename).

instead of fastboot flash recovery.
[SuperSU] egingell:
Fastboot doesn't work on Samsung devices.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] napolionnardo:
Hello, just annoying to report that now is more often the bootloop. I do not know what to do. I thought that with the latest version of supersu I was not going to have these ones turned off again.

---------- Post added at 03:50 PM ---------- Previous post was at 03:45 PM ----------

Anyway Friend Chainfire, thank you very much.
[SuperSU] gothicVI:
Can you provide logs for [MENTION=631273]Chainfire[/MENTION] ?

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] napolionnardo:
Yeah right. That's what I'm going to do. Now how do I get that logs?

Assume that since the Recovery true?
[SuperSU] napolionnardo:
[MENTION=631273]Chainfire[/MENTION], If you are viewing this post, please help me!

I attached the log file so I can see it and if you can give me a solution so that I will not put the screen off. From now on I am very grateful and thank you.
[SuperSU] _alexndr:
The reason is not clear - in the meantime I did following tests @ encrypted device (S7 edge G935F):

Test 1:

- flashed TWRP and went directly to it (keep read only) - result: bootloop

- went again to TWRP (keep read only) and flashed SuperSU 2.79 SR3 - result: bootloop

- restored stock recovery via PC Odin - result: still bootloop

- went to to stock recovery and reboot - result: still bootloop

- restored stock (unmodified) kernel via PC Odin - result: still bootloop

- went to stock recovery and reboot - result: phone booted fine !!!

Test 2:

- flashed TWRP and went directly to it (keep read only) - result: bootloop

- went again to TWRP (keep read only) and flashed SuperSU 2.79 SR3 (KEEPFORCEENCRYPT=true in /cache/.supersu) - result: bootloop

- wipe data / factory reset from TWRP - phone booted fine with encryption enabled !!! (but do not get too excited yet...)

- restored stock kernel & stock recovery via PC Odin - phone booted fine !!! (unfortunately, with custom status despite the encryption, stock kernel & stock recovery)

- went to stock recovery and reboot - result: bootloop :( :(

UNFORTUNATELY - I can't perform more tests as next day (after performing above tests) I broke screen in my S7 edge :crying: I sold it as damaged, for spare parts...

Maybe these 2 last tests will help [MENTION=631273]Chainfire[/MENTION] somehow...
[SuperSU] thorium666:
i can perform tests if there is a new way or new, updated binary. Same as you, all things resulting in a bootloop, wipe of data i never tried and i will never try.

The goal needs to be to have an encrypted N S7 rooted without any wipe and i can support with testing this way.
[SuperSU] gothicVI:
I don't understand your last question.

For the first one: search the thread. I guess [MENTION=631273]Chainfire[/MENTION] could need dkms log but I'm not sure.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Ja_som:
Just FYI, I rooted my N5X with new beta Android 7.1.2 with SuperSU v2.79 SR w/o any issue
[SuperSU] Cuculuz:
Non of the versions work.

Using xpower rom xperia z5c. Undable to update, root is lost or phone is in bootloop and bricked.

Thinking of going with kingroot as this app is hopelessly broken.
[SuperSU] jdegreef:
Have you ever heard about recovery.log ?
[SuperSU] Cuculuz:
Nope.

I just don't understand why Google play has the 2.79 Superuser update available if it breaks the root and is unable to update. Binaries. Why dont the dev revert it back to 2.78 ver what was working.

And all the beta ones here on the forum are broken also .

I have 2 xperia phones z5c and a old xperia z, both have different versions of roms installed and both fail to update the app.

What else can I do to change my Superuser app to something else what at least works.
[SuperSU] ashyx:
Google play couldn't give a monkeys if an app works or not.
[SuperSU] koekoek91:
There are some ways to fix failure of updating binaries.

The thing is you have to do some research and experiment with your phone yourself.

For example completely removing the app from your phone first and then flash a zip (COULD) work.

Or completely Unroot from the option menu in supersu, and then flash a supersu zip.

These are 2 examples of how I troubleshoot and have fixed my supersu issues on my xperia z5 e6653 in the past.

But if you want people to help you, I would start by providing logs.
[SuperSU] Ja_som:
There is a whole thread about update failures, so why you are here and so disrespectful?

Do something more as only posting rude words, and read...

https://xdaforums.com/apps/supersu/support-update-failures-t2907365

And, if you updated SuperSU app from the Google Play Store, then you are on the wrong place, this thread is for beta releases, which are not on the Store.
[SuperSU] jdegreef:
Please help, where can I find these bata releases :laugh::laugh::laugh:
[SuperSU] Ja_som:
hmmm, yes, thanks...
[SuperSU] Cuculuz:
I have posted my issues there in the link you provided long time ago.

I have done a full unroot, I have tried the beta installs.

Recovery twrp install fails.

Installing from google fails.

All the things fail after the app was updated to 2.79

Thats why im so salty I have paid for the pro app what is not working anymore and no solution to fix it.
[SuperSU] Portgas D. Ace:
Maybe in the first post? :confused: ;)

As you were told before: provide logs, otherwise you won't get much help.
[SuperSU] Ja_som:
I had a typo, not beta but bata, so it was soooo funny...
[SuperSU] Cuculuz:
How can i provide a log after I update the app and try to renew the binaries my device wont even boot up. The phone reboots itself after that.

Need to use flashtool to fix it after.
[SuperSU] Portgas D. Ace:
You can grab a log file by using ADB. If you don't know how to do so, just search for "how to logcat".
[SuperSU] bdwilk:
https://xdaforums.com/showthread.php?t=2274119&p=47172724
[SuperSU] Cuculuz:
Log uploaded.

https://drive.google.com/file/d/0Bz5TB-HngPmtX05SdEJ0LU0xU0U/view?usp=drivesdk
[SuperSU] jdegreef:
If you flashed Supersu from TWRP the recovery.log might be useful too.