yashsingh1/xdaforums huggingface dataset:
[SuperSU] Maxr1998:
[MENTION=631273]Chainfire[/MENTION] yesterday I flashed the May factory image on my Nexus 6P (only bootloader, radio, boot, system and vendor manually), but then I booted up by mistake by hitting BP Tools in bootloader, and since it stuck, I resetted it with the power button. Now TWRP tells me my device is encrypted, and default_password decrypts with an empty /data.

Does Android automatically encrypt when booting without the SuperSU kernel patches?

And is my data really gone? My last backup is 10 days old.
[SuperSU] nathanchance:
Yes, fstab.angler tells the device to force encrypt via the forceencrypt flag; SuperSU disables this by turning it to encryptable. So if you flashed the boot image and didn't flash SuperSU before booting, the device would have started the encryption process and force rebooting it probably corrupted the data.
[SuperSU] Maxr1998:
Well **, that's what I already feared. Funnily, after decrypting with the default_password, TWRP still can't write data to it. Means I will have to actively wipe the device, and try if my backup works.
[SuperSU] nathanchance:
And this ladies and gentlemen is why backups are key. Hope it works out for you!
[SuperSU] Naman Bhalla:
[MENTION=631273]Chainfire[/MENTION]

I want to bring to your attention that SuperSU is bootlooping for Official Marshmallow OnePlus ROMs (OxygenOS and HydrogenOS) ever since the first release of it. A person did modify SuperSU 2.67 at that time for making it work with them and it can be found here (It works perfectly) :-

https://www.androidfilehost.com/?fid=24459283995297946

The full latest Official ROM can be found here :-

https://www.androidfilehost.com/?fid=24572388905583156

Please tell me if you need any logs for debugging and I will surely try my best to help you find the issues.

Thanks.

Best Regards,

Naman.
[SuperSU] Scherzengel:
Just posted about this in the General OP2 Forum. Install SuperSU in systemless Mode and everything goes well.
[SuperSU] Chainfire:
Who changed it, and what did he change?
[SuperSU] Scherzengel:
[MENTION=631273]Chainfire[/MENTION]

I don't know who changed it, but i think he only changed it that the Installer is forced to install in systemless mode.
[SuperSU] Chainfire:
Can you post stock(!) kernel ?
[SuperSU] Scherzengel:
(link removed. If you need it again, send me a message.)

This is the boot.img extracted from the latest OOS 3.0.2 full zip. Hope this is what you are looking for.
[SuperSU] Naman Bhalla:
I first found it in a Zip by [MENTION=4794403]Yash98[/MENTION]

It will be better if he can explain what all was changed. I uploaded it to my AFH for a Guide.
[SuperSU] magnamentis:
v2.68 has been working all the time, i recommend that version wherever i can, not because the others are not good but because it's the one with zero issues and risk for such (almost LOL) it just works on all my 7 babies and 13 roms on them. no headaches flash and forget.
[SuperSU] Yash98:
The only thing changed is that instead of detecting whether ROM needs systemless mode or not, it is forced to go through with a systemless install.

EDIT: Attached zip is working on OOS 3.0.2
[SuperSU] Nekromantik:
On systemless mode, if you flash kernel update do you need to reflash SuperSU after updated kernel?
[SuperSU] Fif_:
Yes.
[SuperSU] tiga_x:
Hi Chainfire.

My phone is Japan docomo Galaxy S7 Edge(SM-G935D/Snapdragon 820).

I installed BETA-SuperSU-v2.74-2-20160519174328.zip from TWRP.

Get rooted!! but network connection not work.BaseBand is unknown.

https://pbs.twimg.com/media/CjOX-5fUUAA7lfY.jpg

SuperSU(script) supported S7/Edge Snapdragon's model?

Sepolicy's patch seems for exynos models.

I shared stock boot-img and rooted boot-img(After installed BETA-SuperSU-v2.74-2-20160519174328.zip).

https://www.dropbox.com/sh/st9tu15v8u74luj/AACyCx5siq1Fnc3tTRbcHIAaa?dl=0

Could you support?

---

Tiga
[SuperSU] Nekromantik:
Slight issue. I changed kernel from kylo to ak however when I flash supersu system less it reverts to previous kernel. Tried few times.
[SuperSU] nathanchance:
Either flash the latest boot.img (if on stock Android) or dirty flash your ROM then flash SuperSU then flash the kernel. Flashing SuperSU on an already patched ramdisk causes the SuperSU installer to restore an unmodified boot.img, which will be your previous kernel.
[SuperSU] Nekromantik:
Thanks will give that a go.

I thought system less mode patches kernel so you loose root if you flash kernel over existing su patched boot disk. Asked question on last page about needing to flash supersu after updating kernel and got told yes.
[SuperSU] nathanchance:
Most kernels (at least for Nexus devices) are in an AnyKernel2 format by [MENTION=4544860]osm0sis[/MENTION], which leaves the ramdisk intact, which holds the systemless SuperSU settings so you won't need to reflash SuperSU if you are upgrading your kernel. If you are changing kernels, you will need to reflash SuperSU since you should reflash the boot.img of your ROM/stock when changing kernels so ramdisk edits get reset.
[SuperSU] SpasilliumNexus:
Force it to install as systemless via terminal. Search this thread since it's been answered a few times on how to do it.

It works fine on my Moto X Pure with CM13.
[SuperSU] Adler12:
I have a new Moto XT1572 Pure . When I try to root with the current Supersu I land in bootloop . When I go off on systemless I suddenly no Mac address more . Several tries. No way?
[SuperSU] KaMyKaSii:
How do systemless root in Lollipop on another device than Samsung ?
[SuperSU] Ch3vr0n:
By using the search for compatibility mode.
[SuperSU] Vegerot:
I'm sorry. I tried searching this thread for "systemless" but all I get is a bunch of people asking about how to do it, and nobody actually saying how to do it.

I tried following this tutorial, but installing SuperSU along with GApps, and I get an error saying something like "Decompressing ramdisk Failure, aborting"
[SuperSU] ktmom:
In this thread, searched for "force systemless". [emoji57]

http://xdaforums.com/showthread.php?p=67135909
[SuperSU] Vegerot:
Thanks! When attempting that, SuperSU beta 2.74-2 says things such as "System-less mode, boot image support required", "-Decompressing ramdisk. --- Failure, aborting". And then nothing happens.

So unfortunately, system-less mode does not fix the problem of decompressing ramdisk failing.

Maybe I can try decompressing the ramdisk myself. How can I find CM 13's ramdisk?
[SuperSU] akarol:
Is there any particular reason as to why 2.72 SU is flashed in FlashFire when maintaining root?
[SuperSU] Ch3vr0n:
Afaik the latest FF uses 2.74. if it doesnt, well that simply means that the FF you're using is older than the most recent superSU and FF would need an update.
[SuperSU] KaMyKaSii:
Your answer was to me? If so, could you explain me better? I searched but did not see anything that can help me
[SuperSU] Ch3vr0n:
See post #6362 how to force systemless.
[SuperSU] Captain_Throwback:
Since when does SuperSU work in systemless mode on non-Samsung ROMs < 6.0?
[SuperSU] Ch3vr0n:
That wasn't the question. The question was how to force systemless, I didn't say it could/would work.
[SuperSU] Captain_Throwback:
Actually, it WAS the question....
[SuperSU] Ch3vr0n:
No it wasn't. See above. Asking how to force systemless on lollipop.
[SuperSU] Captain_Throwback:
I don't see the word "force" in the question. Systemless root doesn't work on Lollipop on non-Samsung devices. It seems like that's a much simpler answer than playing the semantics game.

EDIT: And even so, you can't FORCE systemless root on Lollipop. Just adding the flag won't make the install systemless. So your argument is invalid.
[SuperSU] KaMyKaSii:
[MENTION=1754043]Ch3vr0n[/MENTION], [MENTION=1162986]Captain_Throwback[/MENTION] No discussions about what I meant. But it is possible to do systemless root in Lollipop (not Samsung) or not?
[SuperSU] Captain_Throwback:
I actually did answer your question in the post right above yours.
[SuperSU] KaMyKaSii:
I just saw, so sad. But thanks
[SuperSU] Vegerot:
Attempting to do a Systemless install on MARSHMALLOW doesn't fix my issue. I get the same error message trying to install the beta. The only difference is that when the install starts, it says it's doing a systemless install.
[SuperSU] white7561:
Sorry if this question asked before. But. Im using systemless beta on smsung mm. Knox disabled selinux permissive. Mount namespace thing i disable it. Then if i use like smanager app. It cant open commands with permission denied even tho root is acquired . Can someond help ? Thx
[SuperSU] Pkt_Lnt:
Chainfire has posted many times that only gzip is supported for compression, and your failures are probably that. What compression is used on your phone?
[SuperSU] white7561:
What ? Tapjacking protection prob is that u cant grant right. I can grant it. In fact the app granted . But it cant use commands saying permissions denied. And it seems the busybox is on /su too.
[SuperSU] Pkt_Lnt:
That reply was to another post in another window that was not meant for you, sorry. XDA crossed them up somehow with multiquote. I deleted when I saw it.
[SuperSU] GTMonster:
Morning All,

Just a quick one. Has anyone got 2.74 to grant Clean Master root access. The old problem seems to have returned again? This seem to be the case on my S7 Edge and with Marshamllow and my Note 2014 with Lollipop.

Chainfire, are you aware of any issues?

Thanks again for all you do for us!
[SuperSU] egingell:
The issue is with Clean Master not SuperSU. Take it up with its dev.

Sent from: SGS5 - LP 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

There's been some speculation that systemless root works on non-Samsung devices running Android versions < 6.0. I haven't personally seen it work, but [MENTION=5327466]Mr.Yawnie[/MENTION] says it was working for him on Lollipop on an HTC device.

My understanding is that SuperSU will only install in systemless mode if it detects that sepolicy needs to be patched, which is currently only the case on Android 6.0+ and Samsung stock 5.1 ROMs. Attempting to force a systemless install using the SYSTEMLESS=true flag is ineffective on other devices running older Android versions because the installer detects that the sdk is < 23 and sepolicy doesn't require patching.

So I have three questions: Is the above correct? And if so, would you consider allowing systemless root on older Android versions? Or is there another reason it wouldn't work?

Or perhaps you can correct my post, as I'll admit my understanding of how all of this works isn't the best :eek:.
[SuperSU] Mr.Yawnie:
*worked for my friend (or so he told me). I haven't personally tried as I have no non-samsung device atm.

But it'll be interesting to see what Chainfire has to say about this.
[SuperSU] Vegerot:
I don't know. I use CyanogenMod 13 on Moto X 2014.
[SuperSU] DIDIandroid1997:
I want to have systemless root and systemless xposed so I can recieve OTAs on my touchwiz device. But when I flash the zips throug TWRP, my device should not be able to recieve OTAs cause of TWRP...

I wantedto flash the files with flashfire, but the app needs root access. So how can I get systemless root running without having TWRP.

TWRP would make the whole systemless thing pointless?
[SuperSU] Phil3759:
On Samsung Note 4, either 5.1.1 or the new 6.0.1, as soon as device is rooted (or maybe because of the kernel change, or selinux policy changes), it breaks screen mirroring function to Samsung TV. The issue is well known and affects most if not all Samsung devices.

Adding this line to build.prop fixes it:

wlan.wfd.hdcp=disable

If it has no other side effects, would you plan to edit the default.prop when SuperSU is installed on Samsung devices?

Otherwise, editing the build.prop will defeat the systemless root, or we have to manually edit the ramdisk to set the property in default.prop or su.d

Since root seems to break the stock function, seems logical to me to fix it during rooting

By the way, I did many searches but found no exact explanation about the cause.

I only found that HDCP enforcing is implemented mainly for media copy protection rights. I am not sure if adding that line will make you break some copyright!

PS: SuperSU Pro user :)
[SuperSU] KaMyKaSii:
You can do systemless root with TWRP and then install stock recovery
[SuperSU] corkiejp:
On Nexus devices Flashfire can restore stock recovery before applying OTA's. Can it do the same with your device?

You could see if there is CFAR method available for you device?
[SuperSU] danielcr12:
Well after experimenting I got it working on my moto x on cm 12.1, it's working great.

PS: the flag is indeed useless it will not force systemless, what I did was however simple.

What I did was to just change this line in the updater script as you can see it was replaced with my devices info

SAMSUNG_CHECK=$(cat /system/build.prop | grep "ro.product.brand=" | grep -i "motorola").

PS: you must disable CM built-in root for this to actually work, if not cm will place the su binary back to xbin.

edit: added recovery logs.
[SuperSU] Ingenium13:
You may be able to change that setting with a su.d script like with tethering http://xdaforums.com/showpost.php?p=64733104&postcount=117

In this case, I'd change the line to read:

setprop wlan.wfd.hdcp 0

Sent from my Nexus 6P
[SuperSU] Yudh:
You should mention [MENTION=631273]Chainfire[/MENTION] only then he will get notified that someone mentioned him.

Thanks for the solution even i needed it.

✌
[SuperSU] DIDIandroid1997:
When I do a backup through TWRP while having stock recovey, can i systemless root and then flash the backup, but with only "boot" checked in the image? Would that restore the stock recovery?
[SuperSU] DIDIandroid1997:
It can but the thing is, Am I able to recieve OTAs while having TWRP installed?
[SuperSU] Ch3vr0n:
Yes, because FF takes a backup of twrp, restores stock recovery, flashes the ota, and then puts twrp back.
[SuperSU] nicolap8:
On many terminal you dont need to install the recovery on it!

You can simply boot the recovery with command:

fastboot boot twrp.img
[SuperSU] Phil3759:
As I wrote in my post, I am aware about the /su/su.d

Since I didn't follow this thread closely, I wasn't aware that changes in su.d persist after reboot

So, adding a script manually and chmod it to 0700 is enough:

#!/su/bin/sush
setprop wlan.wfd.hdcp disable

No need to modify build.prop or edit ramdisk for the script

Still, since it will affect any rooted Samsung device, just like the deep sleep fix, wouldn't be an option to add this by default, or maybe mention it in one of the first posts under "device specific fixes" ?
[SuperSU] livelie:
XModGames not working

XModGames not working on Nexus 5 with Android 5.0 with root and [BETA][2014.11.17] SuperSU v2.23
[SuperSU] Lil Geeky:
Thanks for BETA-SuperSU-v2.24.zip works great on cm12 5.0 for S3
[SuperSU] niccolomarchi:
AdBlock, TWRP Mnager & Clean Master

AdBlock, TWRP Mnager & Clean Master don't work with SuperSU 2.24
[SuperSU] Kirpman:
download link does not work :(
[SuperSU] JulianJenner:
Same problem for me. A blank (white) page...
[SuperSU] dannyella:
how about in 2.24??
[SuperSU] Chainfire:
v2.24 has been updated from the earlier download, so if you downloaded it before this post, please download/install it again.

v2.24 release notes: https://plus.google.com/113517319477420052449/posts/7sti4Z27usv
[SuperSU] Chapter 1:
Thank you Chainfire you are the one we look up to. Wake lock detector now working fyi
[SuperSU] JulianJenner:
Thanks.

LGE-P760 Lollipop Android 5.0 by Artas182x
[SuperSU] Chainfire:
Too many issues with v2.24 reported. Download removed. Will investigate and get back to you all.
[SuperSU] sean222:
After flashing 2.24, Chrome wouldn't even boot up (FC). Reflashed 2.23, rebooted and Chrome started. No time to do a logcat today :( thanks for your hard work! :)
[SuperSU] peecs121:
Is it safe to revert to 2.23?
[SuperSU] Murshad007:
Chrome is working fine..

Although com.gapps error came back again...

Sent from my LG G Flex F340K Stock KitKat 4.4.2 Rooted

using XDA Free mobile app
[SuperSU] Rapper_skull:
I'm having the same problem. I also cleared data and cache of Chrome.
[SuperSU] goran_oh:
Same problem with chrome on 2.24

Send from my Nexus 5 using Tapatalk
[SuperSU] kskevinstewart7:
Can someone give me a link for 2.23 BETA ??
[SuperSU] mag01:
http://download.chainfire.eu/624/SuperSU/BETA-SuperSU-v2.23.zip
[SuperSU] devil-kin:
Version 2.23 resolved the root related issues I had with power toggles. Thanks!
[SuperSU] hydro945:
DiskUsage - I'm on version 2.23 beta on my N5 stock lollipop and I am unable to use the root functions in the app DiskUsage.

The error message is "java.lang.RuntimeException:Error: no more data"

Can anyone else confirm if this app is working?
[SuperSU] Aldo101t:
link for 2.24 is down
[SuperSU] Pkt_Lnt:
He stated in his first post he has a touchwiz device. Fastboot does not work on Samsung / Touchwiz devices.

http://xdaforums.com/showpost.php?p=67262067&postcount=6387
[SuperSU] durgis:
TWRP is a "recovery" not "boot" partition. So restoring boot from a backup will not remove TWRP but will remove root. You can look through your device forum for stock recovery images or find another way to apply the OTA manually.
[SuperSU] knpk13:
Deleted
[SuperSU] Paz9:
is 2.74 still latest version? any known bugs?

also whats the difference between flashing supersu and odin' cf-auto-root?
[SuperSU] Ch3vr0n:
Did you bother to read the first post?
[SuperSU] A.R.I.S.E. Sound Systems:
Worked great on Preview 3, awesome job as always.
[SuperSU] ipdev:
op is up to date. 2.74 is current beta.

Bugs? I'm running it on everything, no problems so far.

(Samsungs, Nexus, Kindles, Nooks. From kitkat to npreview)

Flashing / updating supersu requires root access, normally an installed recovery (twrp) or custom kernel.

cf-auto-root (If available) will install supersu then reinstall stock recovery.

cf-auto-root link.

http://xdaforums.com/showthread.php?p=33855452#post33855452
[SuperSU] Jostian:
just to confirm, am running stock kernel and SuperSU 2.65 on OnePlus 2 on MM, I guess to upgrade to 2.74-2 I can just flash in TWRP? phone is rooted etc. I read OP which says just flash in TWRP is fine, but have read posts saying one needs to unroot in SuperSU prior to flashing 2.74-2, so just wanna make sure, thanks.
[SuperSU] Mr.Yawnie:
If you want to install the root as systemless, then you need to uninstall system root first. If not, then just flash it on top.
[SuperSU] Jostian:
thanks, am I right to understand that the only benefit to systemless is fixing the loss of root on ROM updates? or are there other benefits to systemless?
[SuperSU] Mr.Yawnie:
It allows for OTA's and systemless Xposed for example.
[SuperSU] egingell:
Nobody ever said root won't be lost on ROM updates. Root will still be lost on ROM updates.

The benefit is a clean system for OTA updates.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] DIDIandroid1997:
Will there be systemless root for samsung 6.0 some time soon, or is it already supported?
[SuperSU] ianmacd:
What is Samsung 6.0? Android 6.0 on Samsung devices?

If so, it is already supported, depending on your device.
[SuperSU] DIDIandroid1997:
Yea, I thought the community would understand that :P

Thanks
[SuperSU] sansnil:
Latest version is working great.
[SuperSU] MiloGermany:
I have just tried the actuall BETA SuperSU v2.74. It is working well for me.
[SuperSU] DarTro'15:
I am in a bootloop after flashing to my Nexus 5, what do I do?
[SuperSU] Ch3vr0n:
Post in the update failures thread, cause it works just fine on my Nexus 5
[SuperSU] ktmom:
Restore your nandroid.
[SuperSU] Heisenberg:
[size=+1]Thread cleaned.

A couple of points I'd like to make.

The first rule of XDA is to search before posting. No, this doesn't mean you need to read 600 pages. Use the search feature. Use Google. Even just read the first post. If it is too much to know what is necessary prior to flashing something to your device because your life is so important, then you shouldn't be flashing anything to your device and you shouldn't be clogging the thread with pointless questions that could be answered by clicking a couple of buttons. Laziness is not an excuse.

If you are not a moderator you have no place moderating other members because they've failed to search. You certainly have no right to belittle them for the same reason. Either be helpful and answer anyway, ignore the post, or report it. Do not turn a thread into a flame war, that's worse than failing to search.

Anyone having issues with this can contact me via PM but the nonsense in this thread needs to stop, please.[/size]
[SuperSU] ralfbergs:
"Regression" in latest SuperSU

Hi [MENTION=631273]Chainfire[/MENTION].

I'm not sure whether this is the right place to post this, please advise if I should go somewhere else, or if I should take a completely different approach to discuss this.

I noticed that the latest Marshmallow build for Huawei P8 cannot be routed with BETA-SuperSU-v2.74-2-20160519174328.zip. The boot image it creates is somehow broken, my P8 boots into fastmode boot afterwards. I manually reflashed the stock boot image, and all was fine again.

If I go back to BETA-SuperSU-v2.67-20160121175247.zip I can still properly root this firmware as described here .

Is this something you can/want to fix? Can I somehow help?

Kind regards,

Ralf
[SuperSU] qwerty22:
About the pre-root access on the stock firmware. Android SDK v23.

Is it possible to rooting stock firmware Android 6.0.1 (in system.img.ext4 image) on a Samsung devices whith SYSMEMLESS=false? SuperSU-v2.74 perfectly integrated in the /system Android 5.0, but the same does not work in 6.0 (I think, boot patched needed).
[SuperSU] Samin Mondal:
Which recovery are u using.?
[SuperSU] durgis:
That's a bit off topic, but I've been using TWRP for a while on my stock Nexus 6 rooted with SuperSU 2.74. It's a bit of a hassle but I usually manually apply the updates in fastboot and flash root and kernel in TWRP.
[SuperSU] droid_1989:
Used CF root to get root, still can't get twrp flashed though
[SuperSU] egingell:
That's unfortunate. Perhaps you could ask Team Win for help with that.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Midomad:
Sorry if it's off topic!

But it is possible to delete the yellow(you're device can't...) warning on boot with 5x and 6p?

Envoyé de mon Nexus 5X en utilisant Tapatalk
[SuperSU] Maxr1998:
Look here, on the first page there are already a few fixed imgs: http://xdaforums.com/nexus-5x/themes-apps/tool-change-bootlogo-images-imgdata-tool-t3240052

This doesn't remove the extra loading time, it only hides the warning.

Note that this may permanently brick your device. Proceed with caution!

Also, this isn't suited for the Nexus 6P. Only use it on the 5X.

By the way, this was a 3 minute search..
[SuperSU] Midomad:
My connection is limited for searching...

Thanks anyway.

Envoyé de mon Nexus 5X
[SuperSU] rgavioli:
Just tested the v2.74 with HTC M9: Still getting bootloop, I'm afraid.

Back to v2.65.
[SuperSU] ktmom:
Have you tried forcing a systemless install with 2.74?
[SuperSU] Samin Mondal:
NVM its Ok.

Use latest systemless SU.. Its better. :)

---------- Post added at 01:58 AM ---------- Previous post was at 01:55 AM ----------

Did you wipe caches...??

---------- Post added at 03:23 AM ---------- Previous post was at 02:58 AM ----------

I am on 2.74-2 su. Works well. But some op my apps not getting root permission.. Like secure settings app, es Explorer app. Etc
[SuperSU] nathanchance:
This has been talked about MANY times in the thread. Search "compatibility mode".
[SuperSU] grep_i:
Try contacting the developers of the specific apps that are not working as you say yourself SuperSU is working well.

It probably is the other app that's not working well and this thread is about Supersu and not about other apps, although other apps gets spoken of a lot in this thread it's still about SuperSU.

Anyways the answer is already giving in here many times the search option is working very good.
[SuperSU] Samin Mondal:
Thanks.. Found that... :cyclops:
[SuperSU] banciii:
Have anyone tried 2.74 with NPD56N?
[SuperSU] suku_patel_22:
Been using it in system mode since yesterday.
[SuperSU] hyno111:
Just tested the Systemless mode is not supported on Xperia MM firmware.