yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ch3vr0n:
Then it must be the first, I remember seeing mine once in a folder with the cache name.
[SuperSU] nubia11:
I don't see "FlashFire" app in the play store. Do you mean flashify?
[SuperSU] LoverBoy2415:
Click this link & become a tester for flashfire .. Now you will see flashfire in Googleplay ;).

https://play.google.com/apps/testing/eu.chainfire.flash ...

Sent from my Nitro
[SuperSU] Ja_som:
I don't, search it on XDA ;)
[SuperSU] nubia11:
Thank you! Much appreciated
[SuperSU] LoverBoy2415:
;) [emoji1] ...

Sent from my Nitro
[SuperSU] corkiejp:
Flashfire should detect an OTA that android has downloaded, so you don't need to know where it is stored.

You can also probably get OTA zips from your device forum or the latest from here.

Further discussion, plus how to get the app check the FlashFire thread.
[SuperSU] xpmule:
Make sure you use either v41 free or v35 pro (Stericson BusyBox)

Those versions contain the fixes for SuperSU systemless (see PlayStore release notes about xbin)

And guys you have gone insane off-topic here. (so surprise)

Some of you act like every topic you happen to be reading is your own personal tech-support.

Is this the best place for noob help on restoring stock firmware? Or advertising your new private app?

Many of us have asked questions or left feedback and were simply buried and ignored.

And many people have problems with getting SuperSU to work so your making life hard for them.

I had asked a few questions and was mostly ignored.

i think others would have liked to know the answer too..

Such as i thought "Namespace Seperation" use to be off default but now ON with a systemless install.

If so can we turn it back off?

And anyone with a Moto-E right now has to flash an old version of this then a new version after

just to get the Bootloader patched (it seems the choice of when a systemless install is triggered is random)

Can we get back on topic?
[SuperSU] Pkt_Lnt:
Yes, Titanium Backup gives "not enough free space errors" for many when checked.

Please! :good:
[SuperSU] grep_i:
Personally I used "file explorer" and did not like it all, the whole look and feel it's too much for me.

I'm a big fan of "root browser" and my second best is "total commander" which I seldom use because of the greatness of root browser.

On Linux it is "midnight commander" or even "gnome commander".

On Windows it was "Norton commander" and now "total commander" or "free commander".
[SuperSU] D-an-W:
Is there a recommended method for upgrading from 2.68 to 2.71 please (It's on the NVIDIA SHIELD Android TV if it matters)?
[SuperSU] Ja_som:
Flash 2.71 zip file over old one...
[SuperSU] maddoggin:
will this work on stock 6.0.1 marshmallow? if not which one works on stock marshmallow? thanks
[SuperSU] Ja_som:
Why it should not work?
[SuperSU] maddoggin:
sorry thought it was for android N only!
[SuperSU] hameerabbasi:
Hello, I think I've found a bug in SuperSU. I'm on a Nexus 6P with CM nightly 20160409.

I can't open SuperSU from the recent apps list. I tap, recent apps, a list of them pops up. I tap on any other app, it goes to that app. I tap on SuperSU, nothing happens, so I'm assuming it's a bug with SuperSU.

Can anyone help reproduce/confirm this?
[SuperSU] LoverBoy2415:
I Don't think Its a Bug...I think that's the Way, SuperSU App is Designed :) .. Iam On CM12.1 ..
[SuperSU] swallowingled:
I'm on stock 6.0.1 and I don't think I've ever seen the SuperSU app show up in the recent apps list. I just assumed that was by design, so I don't believe it's a bug.
[SuperSU] RandomPooka:
Same with PureNexus on the nexus 6
[SuperSU] computerslayer:
The stable build has the same behavior.
[SuperSU] LoverBoy2415:
If You are Speaking About SuperSU Is Not Showing In Recents Menu.. It's The Way The App Is Built... It's Not A BUG :) ..
[SuperSU] hameerabbasi:
It's showing up there, maybe that's a bug.
[SuperSU] LoverBoy2415:
It Only Shows When Opening the App and Clicking Recent Button(Without Closing the App) ..but after Closing the App Manually or Getting back go home screen & Clicking Recents Now,

there is no Trace of SuperSU in Recents ..

..
[SuperSU] Pkt_Lnt:
It is because CM handles how root shows differently than regular android; it is in setting, not app drawer. In any non-CM android I have never seen it in recents. Talk to CM, not SuperSU bug.
[SuperSU] hameerabbasi:
Yes, I just tested, that is how it works. In fact, if I tap on it, it goes to the last app BEFORE SuperSU. If there was no other app in the recents list, then tapping on it does nothing.
[SuperSU] LoverBoy2415:
Yup And BTW it's not a Bug :) ..
[SuperSU] RandomPooka:
For future reference, it's not necessary to quote the entire post of screenshots to answer a single line of text.
[SuperSU] gothicVI:
Same in my moto g 2014 running cm13, mm 6.0.1, however:

On my girlfriend's moto g 2014 stock lp SuperSU shows up in recent apps after going back to home screen! Thus I would not label it a cm related issue only...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] mark manning:
I removed the Lucky patcher conversation. As long as you are on XDA, even the mere mention of it is not allowed! I couldn't care less if you consider it legal or not. Whether you want to realize it or not, many many many members use it for illegal purposes trying to circumvent paying the developer their just dues. Therefore, it was decided long ago that isn't something we need on a developer's site. If you don't agree with me, feel free to PM me but lets keep the conversation to the thread topic please

Thread cleaned
[SuperSU] zelendel:
I will say this only once. Knock if off and follow the mods advise. He is being nice about.
[SuperSU] matssa:
I did the same thing as you did for Secure Settings, but I can't seem to make it work, it says that root can't be found...

What ROM are you using? What SuperSU version? What Secure Settings version?
[SuperSU] Andro-Man:
is it possible to make PRE-Rooted ROM with systemless root method? like for Samsung 6.0.1 Stock ROMs?
[SuperSU] Wickii:
Samsung Galaxy 6 (SM-G920F)

XtreStoLite v3.1 (Android 6.0.1)

SuperSU v2.68 system-less

Secure Settings Pro v1.3.6
[SuperSU] matssa:
Arg crap... I think it is linked directly to my ROM (COS 13 for the 1+1). It can't manage to have the System root access, which is strange... Using the coding of Chainfire didn't do anything. Surely the debugging image should have the root access included, may need to wait (or use a kernel with the root).
[SuperSU] jesssiii:
Yes, I do it on PureNexus by flashing [MENTION=1143630]osmosis[/MENTION]' unsu zip after the rom, then mount system and using the terminal within twrp

echo SYSTEMLESS=true>>/data/.supersu

Then:

echo BINDSYSTEMXBIN=false>>/data/.supersu

Then flash SuperSU 2.71.

Voila!
[SuperSU] maxpower679:
thanks! but isn't that contradictory to the CM built in root solution?
[SuperSU] freexx89:
i cant get this to work after april update. Not sure if im doing anything wrong. Flashed twrp and booted into recovery and flashed the zip. This ends up with boot-loop. any idea why?
[SuperSU] gothicVI:
You're welcome [emoji6]

I don't see how or why this should be contradicting anything in any way. AFAIK SuperSU overwrites cm su - please correct me if I'm wrong!

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] grep_i:
Correct me if I'm wrong but where is your method of creating a rom also why do you have to use command line to issue commands to make Supersu systemless which it is already by default ?
[SuperSU] jesssiii:
I don't create roms. I was using a rom that used to include system root with SuperSU 2.52, so I was explaining how I made it Systemless so I could use Android Pay.

I thought the guy was asking how to make a rom that was pre-rooted with system root, Systemless.

Sent from my Nexus 6P
[SuperSU] grep_i:
OK that's nice.

So the easiest would be to update your SuperSU to a more recent version which are systemless by default instead of what you suggested, your suggestion would be great if you do not want to upgrade your SuperSU if you're using version 2.52.

Better advice would be to upgrade I guess.
[SuperSU] jesssiii:
My rom has since updated, but my prices 5 DID upgrade it by flashing SuperSU 2.71

Sent from my Nexus 6P
[SuperSU] nathanchance:
That's incorrect. New versions of SuperSU (after 2.64) use system root by default and should it not be possible to achieve root via a modification to /system, it will fall back on systemless root. So those commands ARE needed for most custom ROMs that choose to modify sepolicy, otherwise you will just get system root again.
[SuperSU] nextelbuddy:
Would anyone be able to tell me how to force systemless mode?

i feel like I have been reading forever and just cant figure it out. I used to be rooted systemless in 2.56 but everything after that just forces systemmode. I see other people saying they installed 2.71 as systemless but when i ask how they dont reply back.

Is it even possible?
[SuperSU] jwds1978:
You can force systemless with the following when in recovery:

echo SYSTEMLESS=true>>/data/.supersu

After that, proceed to flash SuperSU. It should then try to install as systemless.
[SuperSU] Christiancs1969:
I use 2.60 then latest. If I get trouble
[SuperSU] nextelbuddy:
when I go into TWRP>ADVANCED>TERMINAL and then type in

echo SYSTEMLESS=true>>/data/.supersu

Terminal says "sh:can't create /data/: Is a directory"
[SuperSU] Andro-Man:
Thanks for replay :)

What I Mean is to Unpack Samsung Stock Firmware, And mount the System.img and place the needed files for rooting then pack again, Convert to TAR file to be flashed via Odin3.exe

In the old system root I used to do it, But as now we need systemless root for new Samsung models then can that be done?
[SuperSU] mielletseed:
then you have a blank between / and .
[SuperSU] nextelbuddy:
thank you that was it.
[SuperSU] beerbaronstatic:
2.71 appears to still work just fine with NPC91K on Nexus 6 at least, was able to use Adaway
[SuperSU] yanleites:
On 5X I got systemless root.

What can I flash to use normal root ?

Thanks
[SuperSU] grep_i:
I do not use custom roms and in my setup the default is systemless since version 2.56

So if I understand correctly the default for SuperSU is still systemless unless you have a custom rom that chooses to modify sepolicy, SuperSU will then revolt back to system mode since version 2.64 that modification is possibly made because of the many complaints in the beginning of users with custom rom's that couldn't make an OTA survive script working in systemless mode

Found in changelog of version 2.64
[SuperSU] RandomPooka:
Did you need to use the CFAR to obtain root, like with the Preview 1? I'm going to have to go back and look at how it goes again. Downloading Preview 2 now, and backing up all the relevant goodies.
[SuperSU] beerbaronstatic:
For Beta 1 all I did was flash bootloader/radio/system/boot/cache/userdata images manually, booted into TWRP and flashed SuperSU 2.71 zip

Today I just flashed bootloader/radio/system/boot/cache images since I didn't want to wipe userdata, then booted into TWRP and flashed SuperSU 2.71
[SuperSU] RandomPooka:
Nice! I was thinking that the CF Autoroot was a requirement. Going to backup, then wipe my N6 and give it a shot.
[SuperSU] Erik Rye:
installed NPC91K on nexus 6 via OTA and it didn't wipe my data. previous build was MOB30D and SU 2.71.

flashed SU 2.71 again and all root apps working. cant write to /system with solid explorer or mount in twrp. all terminal commands i could find couldn't get system remounted rw...

time to buy [MENTION=631273]Chainfire[/MENTION] a few beers! :laugh:
[SuperSU] NewRoot1:
"BETA-SuperSU-v2.68-20160228150503.zip" for root without modyfying system is working fine with new Factory-Image for Nexus 5.
[SuperSU] grep_i:
The same goes for 2.71
[SuperSU] NewRoot1:
Not with my Nexus 5...same issue as in post 5681.
[SuperSU] cjkacz:
Same issue for me on Nexus 6
[SuperSU] gothicVI:
Hi folks, can anyone clarify something for me: on cm13 SuperSU beta works flawlessly but the stable version gives me boot loops. What's the origin of this? I read about this issue in several places (e.g. cm forum and others) but never found an explanation.

Thanks ahead!

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Ch3vr0n:
To put it really simple, I believe there's certain fixes in the beta that make it work with cm13 that aren't present in the latest stable yet, which is why the stable causes the problems. Don't know the exact details though, you might find them in the changelog.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] yanleites:
​

Flash 2.70 and then 2.71.

Working fine this way.
[SuperSU] loucapo13:
rooting question

sorry if this isnt the right place for this, but...

trying to find out if this will work on my nexus 6 running android n preview 2. will it wipe my device? are there more step by step instructions for doing this? seems like in the past the steps were more documented.

appreciate the help in advance
[SuperSU] suku_patel_22:
Latest SuperSU beta is working fine in system mode on N Preview 2 on Nexus 5X.
[SuperSU] mr.natural:
It won't wipe and: http://xdaforums.com/showthread.php?t=1538053
[SuperSU] corkiejp:
If your bootloader is already unlocked, it won't wipe.
[SuperSU] Ch3vr0n:
Well considering this is the superSU, the fact is that superSU itself doesn't a device. Period. it's unlocking the bootloader that wipes not superSU.
[SuperSU] 911Guy:
2.71 PRO (I bought it ages ago) working awesome on my Canadian SM-G930W8!!

[MENTION=631273]Chainfire[/MENTION] you seriously rock!

Have a beer on me! 6UU17148JX242020W
[SuperSU] Erik Rye:
Flashing SU2.70 and then SU2.71 still isn't allowing me to modify system on N preview#2. When I try to rename the boot.zip to .bak i get error: unable to remount the file system under "/system"
[SuperSU] yanleites:
When I flashed 2.71 I got systemless out, then I flashed boot.img again, then 2.70, restarted, then 2.71.
[SuperSU] ohad129:
Also cf luman not working
[SuperSU] Erik Rye:
tried that exactly, still getting error when I try to rename boot.zip

Thx though
[SuperSU] dml1851:
Sorry if has been asked but is twrp working well on N preview 2? In order to flash supersu 2.71, it's boring to be stock non rooted, but I love android N
[SuperSU] Alxoom33:
Some versions of TWRP Working better than others, at least on N6. I like 3.0.0.1 which worked fine with N2.
[SuperSU] corkiejp:
It will depend on your device and if it is encrypted?

Nexus 9 Encrypted does not work properly.

You could always use CFAR to root, or use FlashFire app to update and re-root in the process.
[SuperSU] dml1851:
I just flashed the Dev preview 2 using fastboot flash all, so I all stock, all clean and encrypted as factory (bootloader unlocked is the only difference).

I'll try cf auto root then, never heard about flash fire, I will investigate on that

Enviado desde mi Nexus 5X mediante Tapatalk
[SuperSU] arturox:
Sorry for the late response, I wanna thank you because it worked with the version you told me. Thanks
[SuperSU] tuxStyle:
I downloaded the full image and used FlashFire to upgrade and root.

Everything seemed fine excepting the /system issue.

I hope at some point we will have a way to mount it RW
[SuperSU] Alxoom33:
You can use TWRP 3.0+ to mount System. Then use Solid Root Explorer or Rom Toolbox.
[SuperSU] _that:
How should a mount done in TWRP affect an app running Android?
[SuperSU] Erik Rye:
tried that. didnt work
[SuperSU] Alxoom33:
It shows that the system is not read only, and can be mounted.
[SuperSU] suku_patel_22:
[MENTION=631273]Chainfire[/MENTION] libsuperuser has been spamming logcat on Android n preview 2 with lot of gibberish
[SuperSU] Alxoom33:
First, were you able to mount System in TWRP?

What kind of Root Explorer are you using?
[SuperSU] egingell:
Being able to mount the system rw in TWRP is no indication that it can be done in Android.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
Try "root browser"
[SuperSU] mousemighty:
I have an HTC One M9 GSM. When I install 2.71 beta I get bootloop. Even let it go for an hour yesterday. I go back to TWRP and install latest stable version and boots fine after a couple loops. Any ideas?
[SuperSU] corkiejp:
Root on N-DP2 with CFAR?

[MENTION=631273]Chainfire[/MENTION] Does CFAR need to be update to support rooting with it on N-DP2?

A report here that it failed to work.

I successfully flashed N-DP2 from 6.0.1 (Nexus 9 - Encrypted) using FlashFire and achieved root in the process.

Anyone else successfully root N-DP2 with the CFAR for DP1?

Just also got the Pro version of Flashfire for €3.68
[SuperSU] TimeFlies7:
I have a OnePlus One running COS13. However, I can't get the root access for apps like ES Explorer and Selinux changer. Apps like titanium backup and greenify do work fine. Is this version of SuperSU(v2.71) having issues?
[SuperSU] shoey63:
Nope, it's because the apps that don't get root access don't know how to deal with systemless root. Contact the app developers and tell them to look for su in /su/bin as well.
[SuperSU] TimeFlies7:
Thanks for the speedy reply. :)
[SuperSU] vt0r:
It would be very helpful if you provided the logs for review.
[SuperSU] magnamentis:
revert to v2.68 this version which was originally made for N preview has changes with which some root apps have issues. no since we're still on marshmallow the app developers will most probably not make the necessary updates to work with the restrictions that N will seemingly bring and tighten the rope one more notch. just stay with 2.65 stable or beta 2.68 for the rest of the season and you'll be fine. there are no downsides to use 2.68 or 2.65 and there are no benefits to use v2.71. Newest is not always best for each configuration.
[SuperSU] Erik Rye:
I was able to 'select' system from the mount menu in Twrp but when I rebooted still wasn't able to rename the boot.zip using Solid Explorer
[SuperSU] Erik Rye:
maybe i missed something in the writeup from [MENTION=631273]Chainfire[/MENTION] about 2.71, but thought he said it was the N build merged with the other recent updates...
[SuperSU] Pkt_Lnt:
Chainfire posted a possible solution for 2.71 using the terminal.

http://xdaforums.com/showpost.php?p=66140836&postcount=5493
[SuperSU] Erik Rye:
TIA!!!
[SuperSU] Alxoom33:
Exactly what are you running and what are you trying to accomplish?

---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------

Try Root Toolkit Pro.
[SuperSU] Erik Rye:
N6 stock and when rooted (2.71) on N dp2 all root apps work except I can't rename boot.zip using solid explorer (which has always worked the best for me with systemless root, as far as file managers go). This the only issue I am having but not critical... it will all get worked out in a reasonable amount of time.
[SuperSU] Badger50:
TIA?...Transient Ischemic Attack! Dang, no need to have a stroke over this stuff [emoji15]
[SuperSU] Erik Rye:
Ez, Badger, nobody is having a stroke-- it's Thanks In Advance. Lolz
[SuperSU] mitchdickson:
Right over your head.
[SuperSU] Badger50:
I know bruh...was just having some fun. My old PT skills always come out [emoji106] [emoji3]
[SuperSU] Erik Rye:
good one. Gump
[SuperSU] Alxoom33:
That's similar to mine. J Rummie's Root Toolkit, Root Explorer Pro works for me.I also had some issues renaming with Solid Explorer.
[SuperSU] Erik Rye:
FAST ( i PT'd awhile..) cheers man
[SuperSU] loof13:
I flashed the new developer preview today. I rooted it by flashing SuperSU 2.71. Titanium Backup's restoring doesn't work, I'm not able to install Busybox. (error in installing). Any help?
[SuperSU] TimeFlies7:
I can just flash 2.68 over the 2.71 I'm having rite? :)
[SuperSU] magnamentis:
try this:

Terminal Commands for Secure Settings in N-Preview and probably other apps to be fixed (write to system)

mount -o remount,rw /system

touch /sbin/su /system/bin/su /system/xbin/su

mount -o remount,ro /system

su

mount -o remount,rw /system

ln -s /su/bin/su /system/bin/su

ln -s /su/bin/su /system/xbin/su

mount -o remount,ro /system

Terminal Commands to allow SELinux Mode Changer to work without reboot into Safe Mode !

1. stop logd

2. setenforce 0
[SuperSU] RandomPooka:
I had that problem on the first try. Second time around, I clean flashed N2 and used CFAR to root first, and booted into the ROM. Went back into recovery and flashed SuperSU 2.71. No problems with Titanium after that.
[SuperSU] grep_i:
So basically you are symlinking systemless root to act as system root that's the smartest and simplest solution to this issue
[SuperSU] joedajoester:
Would it be possible to flash SuperSU without twrp? I'm on the N preview and can't decrypt data unless I wipe userdata, so I'm wondering is it possible to flash it without a recovery. Thanks
[SuperSU] Ch3vr0n:
Flashfire can do that, besides you don't have to flash a twrp. You can fastboot boot into a recovery too
[SuperSU] suku_patel_22:
[MENTION=631273]Chainfire[/MENTION] As mentioned earlier, libsuperuser has been spamming logcat on Android n preview 2 with lot of gibberish.

Logcat is attached.

obtained via:

bullhead:/sdcard $ logcat | grep libsuperuser >su_spam.log

^C
[SuperSU] corkiejp:
Use CFAR method.
[SuperSU] 666biker:
it is possible to have SuperSu still active after flashing new CM13 nighlies? on CM12.1 I saw that kind of option in SuperSU preferences, but Beta SuperSU and CM13 nighlie I have to install it always after new nightly version.

my device: mako (Nexus 4)

thanks
[SuperSU] joedajoester:
It says that CFAR will wipe the phone, but only if the bootloader is locked. I just want to clarify, my bootloader is already unlocked so my phone won't be wiped. Is this correct?
[SuperSU] Ja_som:
Correct, when bootloader is unlocked, then it will NOT wipe your data ;)
[SuperSU] Fif_:
Yes.

You'd have to install SuperSU in system mode. However I have no idea if that works well with CM 13.

Look up in the thread for instructions on installing SuperSU in system mode if you want to try.
[SuperSU] ipdev:
http://xdaforums.com/showthread.php?p=65177799

Type in terminal before install. (Works with a lot of builds including cm13)

echo SYSTEMLESS=false>>/data/.supersu
[SuperSU] ipdev:
So I updated from SuperSU 2.49 (Installed by a root script method to remove kingroot.) to SuperSU 2.65 by apk, no problems.

Installed 2.71 by apk and I can not get the binaries to update.

Funny thing is that a root checker shows SuperSU 2.70 is installed, I never had 2.70 let alone install it.

(I went from 2.68 to 2.71on all my devices - save for this one.)

I do not have twrp or cm recovery.

(FlashFire does not work on this yet.)

Anyone have an idea?

Currently running on fire 8 (5th gen.)

fire os 5.1.1

SuperSU 2.7?

FlashFire .31 (Backlit grayish black screen currently. Last 20 mins. Time to power off.)

GooglePlay (Generic)

Nova Launcher 4.3-beta5

BusyBox-v1.24.1-Stericson
[SuperSU] Ch3vr0n:
As the instructions stay, don't update simply by apk. Flash the zip file.
[SuperSU] ipdev:
Open to idea's how.

(Normally I would flash the zip in twrp or using FlashFire.)
[SuperSU] Ch3vr0n:
Fastboot boot into twrp, check your device forum to flash twrp, ask in the proper superSU troubleshooting thread,... This isn't it.
[SuperSU] Alxoom33:
Use Wug Fresh Android Toolbox.
[SuperSU] harsh2193:
Ever since i updated to SuperSU 2.71, I can't seem to get root explorer mode to work in ES Explorer. Root works in other apps, but I can't even get ES Explorer to acknowledge that root exists. It doesn't even ask for root permission. Just gives "Sorry, test failed. This feature can not run on your device". I searched and found that I need to flash the pie patch (Does this still work?) but the links that I found were dead. Can anyone re upload it or suggest another fix? Any help is appreciated :)
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=66394691&postcount=5722
[SuperSU] DingoBat:
ES Explorer does not currently support systemless root. Suggest using another explorer. Solid Explorer is a great choice.
[SuperSU] harsh2193:
If I'm aware of how things have been going, then systemless root has been in use ever since marshmallow was rooted? I've used all the way up to SuperSU 2.68 with ES file explorer without any issues. Just updated yesterday and root explorer is now broken...