yashsingh1/xdaforums huggingface dataset:
[SuperSU] grep_i:
Ofcourse you will do it differently, this is very basic just cleaning up superSU nothing more.

No intelligence in it that checks existence of type of root and only remove what found only remove everything, this worked for me in all cases until now so I never looked in it to change it further.

I hope you will make a good replacement for this simple flashable zip superSU cleaner.

[MENTION=4544860]osm0sis[/MENTION]

Added some intelligence in the script with test if file exist
[SuperSU] ruchern:
What's the compatibility of SR3?

Marshmallow onwards?
[SuperSU] Chainfire:
Froyo+

EDIT: Eclair 2.1, even! I have actually tested on Gingerbread a month or so back.
[SuperSU] milojoseph:
Is it possible Plz, in no disrespect, if you can find a root method for the s7e without the engineering boot. Amusing the cowmodexpolit
[SuperSU] NotATreoFan:
Confirming that SR3 flashable zip worked like a charm on my TMO LG V20. It was already rooted with SR2, but even without TWRP decryption support, I was able to push the zip over ADB and install normally.
[SuperSU] bagarwa:
Hi Chainfire. My Nexus 6P was running Stock Android 7.1.1 DP1, Stock Kernel, SuperSU-v2.78-SR1 and storage was unencrypted. I flashed the SR3 now and it is at the boot animation stage since last 25 minutes. I'm afraid that it is encrypting the storage and if I force reboot, it will "corrupt" the encryption and I'll have to do a full wipe. Any tips?

EDIT - It finished boot. And now it says "Encrypted" under Android Settings > Security. :( Anyway to unencrypt it without wiping everything?

SuperSu doesn't disable force-encrypt anymore?
[SuperSU] blempka:
Is there anyway to create these modified boot.imgs that can be used with fastboot for other devices? Specifically the Nexus 5x or 6P using File-Based Encryption.
[SuperSU] andreoide:
Hi

I am from beginning on Sr1.

Can I flash Sr3 with TWRP without unroot first "over" the version Sr1 I use now? Like an " app_update" I mean?

Samsung SM-G901F (S5 plus kccat6)
[SuperSU] Chainfire:
It does, but Android 7 uses a new form of encryption. If the encryption flags are removed while content is encrypted, all data is lost and the device will not boot. The installer does remove the forced encryption if the device is unencrypted - probably that detection has gone wrong on your device.

CFARs do exactly this, but haven't been updated with the new SuperSU's yet. Probably won't happen until next week.
[SuperSU] xell75:
I done it on my S4 with CM14.1 Android 7.1 and have no issues! :)
[SuperSU] ruchern:
Yes you can. I just did it.
[SuperSU] MArtyChubbs:
Same here...

[MENTION=631273]Chainfire[/MENTION]. My Unlocked VZW Pixel XL was running Stock Android 7.1.1 63P, Stock Kernel, SuperSU-v2.78-SR1 and storage was also unencrypted. I flashed the SR3 now and it is at the boot animation stage since last 30 minutes. Is this expected? Is my only choice to wait or can I reset it? Holding power + vol- does not reboot it. It's encrypting, is it not? Thank you for your awesome work!
[SuperSU] Pkt_Lnt:
Read Chainfire answer to the post you quoted.

http://xdaforums.com/showpost.php?p=69449446&postcount=7788
[SuperSU] MArtyChubbs:
delete
[SuperSU] Gandalforce:
Changelog for SR3? Apologies for the nuisance question
[SuperSU] hatchet13rydin69:
Anyone used on lollipop yet? If so any known issues?
[SuperSU] gleggie:
2 pages back...
[SuperSU] safety1st:
Please refer on this link http://xdaforums.com/showpost.php?p=64916199&postcount=3

Hope it helps;)
[SuperSU] Gandalforce:
Thanks Safety, already read.
[SuperSU] nathanchance:
Thread cleaned, let's keep it civil in here, shall we?

The Flash

Forum Moderator
[SuperSU] grep_i:
Works fine for me thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] fhem:
Thank you sir --- You are the very best. SR3 seems to have resolved the issue for rooting non-stock boot image on Nexus 9.
[MENTION=5501864]USBhost[/MENTION]
[SuperSU] Srandista:
No, for sure. Stock kernel have SELinux enforcing.
[SuperSU] GtrCraft:
Thanks. And thanks chainfire for getting this milestone [emoji106]
[SuperSU] note crazy:
As far as viper working on stock kernel it works 100% on my att note 3 rooted and ss
[SuperSU] Srandista:
Yeah, but I don't think, that you have Lollipop on your Note 3...
[SuperSU] psygbert:
well my bad. since cerberus is not crashing. it is the one preventing usb debugging. it just crashes on startup before. everything works fine now.
[SuperSU] note crazy:
I have 4.4.2 brother
[SuperSU] GtrCraft:
Then your comment made no sense...
[SuperSU] theone_s_me:
I flashed the stock boot in my moto x 2014 to remove what cf auto root did with the previous method of rooting.. Then flashed supersu 2.27 everything is working perfectly... Thank u chainfire... U deserve a noble prize lol
[SuperSU] note crazy:
But why would it not work on your stock kernel it works on mine is it because lolipop changed something that would make it not work
[SuperSU] GtrCraft:
Yes it does. That's the news on xda this week
[SuperSU] note crazy:
I never liked lollipops anyways lol there to sticky bahahaha
[SuperSU] Frank Westlake:
2.27 OK through TWRP on:

- Note_ SGJ-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing

Looks good.

Frank
[SuperSU] lafont28:
What did you use to flash the zip? Or do you have a pure edition?

Sent from my XT1254
[SuperSU] 0.0:
You can use twrp. Only pure edition will work

sent from my Moto X (2014)
[SuperSU] lafont28:
Thought so but I was hoping to pull this off on my Turbo. Wishful thinking I guess

Sent from my XT1254
[SuperSU] Blümchen Blau:
Perfect on nexus4!!!

Great work Chainfire!

Just flashed my Nexus 4 with factory image 5.0 (LRX21T) and loaded up openrecovery-twrp-2.8.2.0-mako.img to install your great SuperSU 2.27 and - without any glitches - apps like Titanium Backup, ES File Manager and Total Commander work perfectly with root.

NO PROBLEMS AT ALL!!! :highfive:

Thanks BB
[SuperSU] Evo_Shift:
Anyone flashed the beta using the kernel that was patched for no encryption on the Nexus 6?

Edit - Well I did and it worked fine.
[SuperSU] nightfishing:
How do I check if my flash of the stock boot.img worked? How can I tell if I am back on the stock image or still on the CFAR patched one?

TIA
[SuperSU] Trialz Nexus One:
Hi all...I realise my GPS apps such as Waze do not get a fix with SU 2.27. Only reverting to SU 2.23 do I get a consistent GPS fix. Has anyone else noted the same?
[SuperSU] USBhost:
v2.27 working awesome

No problems

---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------

Gps working just fine here

Nexus 9
[SuperSU] blempka:
Awesome! Thanks so much!!
[SuperSU] raviindia:
Dear [MENTION=631273]Chainfire[/MENTION]

how can I make system less-root into permanent root.

please let me know.. I tried to make data app as system app but it is getting crash after I restarted the device.
[SuperSU] smitharro:
The latest build running fine on CM14.1 on my Moto G4 Plus! Out of the box!

Send with my Moto G4 Plus (XT1642) on CyanogenMod 14.1, Android 7.1, using Tapatalk!
[SuperSU] Jdban:
I just got a system ui crash at 15% on SR3: http://imgur.com/a/7ujOT
[SuperSU] maximusmullivan:
Are implying it's a SuperSU caused issue? Your log does mention Reddit frequently
[SuperSU] Jdban:
https://plus.google.com/+Chainfire/posts/24xhJN724HG

The patch notes for SuperSU 2.78 SR3 mention adding a fix for system ui crashing at 15%. It seems likely to me that SuperSU is the culprit, and that the issue may have cropped up in a different way or something with SR3.
[SuperSU] Chainfire:
Make sure you update by fastboot booting the new images, as instructed.
[SuperSU] Jdban:
I did update to the new images. I am on the Pixel XL running 2.78 SR3. I updated from SR2 to SR3 yesterday using 'fastboot boot boot-to-root.img' with the new image, but it seems that I hit the 15% System UI crash on SR3.

I can also verify that I am running 2.78 SR3 via the SuperSU app: http://i.imgur.com/KRrnQvd.png
[SuperSU] Chainfire:
By that as it may, I can see from the logcat that your boot image is *not* updated and still running some SR2 code. You can try reflashing the stock boot.img from the official firmware, then booting SR3.
[SuperSU] Jdban:
Interesting. I'll try flashing the stock boot.img and then booting SR3 to see if that solves the issue, and then I'll report back.

Thanks!
[SuperSU] Jdban:
That worked.

I flashed stock boot.img, drained my battery from 16% to 14% without a crash, then I flashed boot-to-root again and drained my battery again from 16% to 14% with no crash.

Thanks!
[SuperSU] GPS3:
Does it take 10+ minutes to boot the first time after booting boot-to-root? I'm trying to be patient, but I thought I'd ask for peace of mind. Currently stuck on the boot animation. Thanks!

EDIT: Restarted and booted up instantly, however SuperSU is not installed. I have a feeling I should have booted in between bootloader unlock and booting boot-to-root.
[SuperSU] Jdban:
It didn't take me that long for it to boot after booting boot-to-root. You should try again.
[SuperSU] cridtohs:
is it possilbe to just flash the new supersu over the old one? So far I have always gone and done "unisntall supersu for reinstall from app store" option before flashing or did a full unroot even before flashing, but then sometimes If I do a full unroot it causes problems and I cannot root again without flashing a fresh boot.img.
[SuperSU] :
Of course you can. I do it always like this. Just flash over the old version
[SuperSU] ZabiGarma:
How about suhide? Can you just flash the newest SuperSU over suhide?

Or should I uninstall suhide prior to updating SuperSU? Should I also uninstall Xposed?
[SuperSU] mjohnson4580:
does init.d work with the current superuser? If no how do you set up for su.d to run on boot like init.d use to.
[SuperSU] andreoide:
I flashed it right 5 minutes ago.

Booted twice (but when flashing there was warning not to interrupt anything!) So it booted again and started normal without delay. Checked root and it works like a charm!

Thanks!

(And thank you too Chainfire! !!)

[emoji111]
[SuperSU] Nomelas:
getting failure, aborting at calling user ramdisk patch script part....

I've completely removed all xposed, magisk, older superSU and suhides using their respective uninstallers, also ran unSU and reflashed my rom.... no dice!
[SuperSU] grep_i:
Yes you can flash the newest SuperSU over previous one, you don't have to uninstall anything.
[SuperSU] Alxoom33:
yes. But don't know about Xposed. Don't like the xposure.
[SuperSU] whitelyon78:
Chainfire, Huawei few days ago released his update to MM G7, but in trying to make the root with SuperSU 78, this does not work, you could us help the community of holders G7 Huawei able to root. Thank you
[SuperSU] ashyx:
Logs and full details required. At least post the recovery log after attempting. The God of root [MENTION=631273]Chainfire[/MENTION] maybe, but mind reader I'm afraid not.
[SuperSU] vital21:
Perfect answer! And yes it is sarcasm . For which question exactly did you provide your fantastic "YES"?

IMHO if you're really up to help somebody, first you'd better read the question! Because such "helpful" answers will only confuse somebody ---> producing more questions and more confused people.

The % of usefull information will rapidly decrease and sometime you will have to read tons of useless pages to finally get some info you was looking for...

Just think about it...

GL!
[SuperSU] whitelyon78:
You're absolutely right, thanks
[SuperSU] EViollet:
Do you have f2fs on your data by any chance?

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[SuperSU] Nomelas:
yay thanks this fixed it for me too!

---------- Post added at 10:55 AM ---------- Previous post was at 10:24 AM ----------

See above :D
[SuperSU] Alxoom33:
The yes was that you can flash 2.78 SR3 over Suhide. The rest was a qualifier due to my lack of current experience with Xposed in this setting. So the partial answer was directed to the asker's question and an attempt at some humor.

Remember, sarcasm is the lowest form of humor and often needlessly clutters. Did you add anything useful, answer the question or were you trying in the least to be helpful?
[SuperSU] -Happy Feet-:
hi updated from SR1 to sr3 with flashing the zip file.

when I disable root and open a Game, like Pokemon go, the phone freeze and reboot. this happen with the SR1 and SR3 Version. Anyone with the same issue?
[SuperSU] vandyman:
Did Supersu SR3 give you root. If yes than it is working .

Pokeman has nothing to do with Supersu, you need find a thread about Pokemen to get an answer.
[SuperSU] GidgetTheGnome:
works great on j320az
[SuperSU] andreoide:
Edit: flashed the Samsung October update (wich undo the root and twrp and xposed) , boot, twrp flashed, Sr3 flashed and than xposed.

All working without problems whatsoever.

Sm-g901f Samsung s5 plus kccat6
[SuperSU] bdwilk:
What he was pointing out was the guy you were helping asked multiple questions "do I, or do I not..." and you answered with "yes" without explanation.

ASUS Z00LD_LG f320s_Lenovo a328
[SuperSU] MaFiBoSS:
I removed the root from the application SuperSU. No problem found. But today, I try to flash again the last stable root and I have the bootloop on the phone starts (splash image). The unique way to resolve this bootloop, is to flash (from TWRP recovery) again the original boot.img and the phone starts normaly.

Already tested with these versions of SuperSU:

https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip

https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip

https://download.chainfire.eu/1012/SuperSU/SR3-SuperSU-v2.78-SR3-20161103171345.zip

As a final solution I will have to flashing the ROM again :(

Someone had this problem? Thanks.

EDIT

: OK, I flashed the stock recovery and after entering on recovery, I have this message "supported API : 3 , dm-verity verification failed".
[SuperSU] Teddan Fred:
Sry for being noob here, but im confused. I have not made a boot.img before i Rooted my device with SuperSU.

To flash "a different boot.img" I understand this is usually done with TWRP and you have a backup of your Boot.Img? Correct?

BTW is it possible to make a backup of your Boot.img using TWRP, when your device is UNroted?

As an alternative, Can I use Odin and flash Samsung stock BL file?? Is this something else?

Thank you VERY MUCH for your time.
[SuperSU] ulxerker:
compared to SR1 version SR3 seems to drain more battery. is anybody else seeing this?

I think I'll downgrade to SR1, the newer versions even haven't huge benefits for most of the "older" phones according to the changelogs.
[SuperSU] andrew2432:
Hey sr2 or 3 with the patch using adb commands:

Echo SYSTEMLESS=true>>/data/.supersu

I've seen you need to flash twice. No clue if you need to run the adb both flashes. Also a ramdisk patch needs pushed and renamed into the data folder. No clue of you run this before both flashes or not. I heard one flash, run patch, flash again. The added adb command...idk when you run it for sure. Still in the reading phases. Flashed 2.78 over magisk manager 2.1 and su applications and lost my apns. I'll be back with the quote I read in a different thread.

If you find the stock image. Best to do is have a twrp backup right before trying serious modifications. Yes, twrp and it's backup are NOT related to root. You can have twrp and no root, you can have root and no twrp. And I believe boot, sysrem, data are the big three to backup, so probably can backup your boot alone. Idk about Odin, unless I left something unchecked I didn't overwrite my /data, leaving me with standard settings on my same phone...hmph.

[MENTION=1751716]theflash[/MENTION] let us go nutsssss

From another thread...magisk general support:
[SuperSU] Teddan Fred:
Thank you for your informative response, however this raises a new question for me:

Some time ago, I tried to perform a TWRP backup without ROOT, and it didn't work. Are you sure I am able to perform a backup with TWRP when device is not rooted?
[SuperSU] _that:
"root" is a concept of an operating system. So you don't root a device, you root an operating system. TWRP is its own tiny operating system (which always gives you root). To remote control TWRP from your Android OS might require root in your Android OS.
[SuperSU] Teddan Fred:
Thank you, I truly appreciate your response.
[SuperSU] Alxoom33:
Understood. I didn't like or appreciate the attitude. He was being sarcastic, not helpful like you are being. I also think that you can understand the answer from the context.

---------- Post added at 01:32 PM ---------- Previous post was at 01:30 PM ----------

look in /data for the boot.img file.

---------- Post added at 01:35 PM ---------- Previous post was at 01:32 PM ----------

Go to TWRP and then you can flash boot.img from /data folder.
[SuperSU] andrew2432:
I'm currently flashing magisk when I need root and unflashing when I need to pass sn. I don't used xposed (yet) on the new methods, or v4a, or other root dependant entities right now.

With that said, my most recent backup is unrooted and passing sn. I have a full backup but don't need efs, cache, and...? Just being worried and included them in case. You may have avoided system modifications within twrp when you first set it up. I forget where ta at, maybe mount within the options.

---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------

And root is NOT an unlocked bootloader right? It's a gui for for managing administrator access?
[SuperSU] Pkt_Lnt:
The bootloader just loads the OS when you start the phone, it is NOT root.

This is root.

https://en.wikipedia.org/wiki/Rooting_(Android_OS)

The GUI is just the manager for applications that request root, to allow or deny.
[SuperSU] andrew2432:
Did you have a backup? Won't a twrp backup solve all of this...?

Thanks I've been looking for the difference. LG has locked up bootloaders, requires a "bump" on certain models. Samsung has locked boot loaders but root allows system mods. Just trying to actually understand rather than read read read flash like hell!!!!
[SuperSU] pkgnex:
I'm not seeing battery drain, but big performance lag. Every touch action has a like a 1 second pause before it, and root-requiring actions are like 2 seconds. It's so bad that typing su in terminal emulator, I thought it locked up the first time. I get splash screens from apps saying "please wait while app is acquiring root access". Since nobody else is reporting this, I'm assuming I just have a bad install somehow. Will report back if this persists after next factory image push next week. Stock rom on Nexus 6, latest factory image. Was working great with SR1, and I skipped SR2. Doubt if there are any logs I can provide since everything is working... Just really slowly.
[SuperSU] WakerPT:
How does one flash in systemless? You quoted someone saying to add that command before flashing su, but, add that command where? Do I need to open the zip file and edit something somewhere? Or do I open terminal on twrp and run that command and afterwards flash SU as usual? I don't get it...
[SuperSU] Teddan Fred:
Want to easily remove SuperSU and xposed if I change my mind

Hello all. Sry if this is a noob question again :) I use TWRP and have a backup of Boot, System, Data partitions. Does this Backup remove all traces of SuperUser and Xposed? or is other partitions affected as well by these wonderful tools?

Any explanation is highly appreciated :)
[SuperSU] candys.world:
re Permissions

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

Im fairly new at all of this and would like to know if it's normal to not have any rw permissions allowed? I've noticed that no matter what with the systemless root I am honestly not able to do much. No disrespect meant as I am sure it's user error but I am hoping you can tell me exactly what I need to obtain this or what I may be doing wrong compared to others who don't have any issue. I have a Nexus 6p on NBD90X. Thanks, Candy
[SuperSU] marc.ientilucci:
What are you using to try and modify system? I've only had luck with some file explorers (root explorer

Works)
[SuperSU] candys.world:
re: Permissions

Hi, well I can somewhat with FX file explorer, but not on everything not that I should be able to on everything but the way I think is that I want the option if so I decide. Is it this way with systemless and is there not a way to disable dm verity or if I'm misunderstanding that this is the problem let me know. I was reading here and does this offer any help? As a reminder I'm very new so this link may be irrelevant lol... It was interesting reading tho.... :laugh:

http://stackoverflow.com/questions/38304435/how-to-enable-and-disable-dm-verity-on-android-devices
[SuperSU] marc.ientilucci:
Not to sure about DM verity but try root explorer. There were some things like modifying build.prop that wouldn't work for me unless I used that specific explorer.

I suppose I would need to know the end goal to try and assist further. For example, if you are trying to get rid of the orange boot screen, I have not found a way around that using systemless.
[SuperSU] andrew2432:
It did for me. I have a passing SN unrooted backup. This had magisk applications but binaries out of date. I flashed 2.78 sr2 over magisk apps and maybe a zip too :/

On boot, all apn data had been lost, apps were failing all over and the phone was nearly unusable. I get back to recovery, wipe cache and dalvik/art, restore my data, system, and boot, and the phone booted, optimized, and had to activate again. Maybe needed to wait for that the first time, but I definitely had magisk files left, which is bad. But a twrp backup restore DID SUCCESSFULLY bring ME back.

Edit: didn't have xposed. Wondering also if a twrp backup can basically save all of this.

Supers 2.78 I'd system less and installs on 6.0+ nicely. I'm on lollipop. I have to run this echo command prior to flashing so that it installs correctly. I think I flash sr2, push the ram disk patch files, run the command, flash sr2 again.

[Q] Does the zip include a root program GUI or do I still need the application apk?
[SuperSU] WakerPT:
Hey, for some reason even though I'm on marshmallow my supersu didn't install systemless so I had to force it. Then It worked and I was able to install everything flawlessly. Thank you anyways.
[SuperSU] andrew2432:
With:

echo SYSTEMLESS=true>>/data/.supersu

In adb??
[SuperSU] corkiejp:
Nexus 9 - November NRD91N

Successfully used Flashfire app to flash the latest factory image along with v2.78 SR3 instead of using everroot option.

But when booted the supersu app was removed from my tablet, so installed it from the playstore and reported version was 2.78.

Flash the supersu zip again and then installed the app from within the zip. Correctly showing v2.78-SR3.

[MENTION=631273]Chainfire[/MENTION] It would be handy if flashfire reported what version of supersu everroot was using.

Edit: - Also the Nexus 9 has a new bootloader, which Flashfire does not give the option to flash, had to use fastboot.
[SuperSU] fink.nottle:
I'm getting a bootloop while flashing this on nexus 5x november image (nrd91n).
[SuperSU] petrus764:
My N5X doesn't boot after flashing either. Tried with SR1 aswell, looks like google changed something. Gonna manage without root for a few days I guess.
[SuperSU] Alxoom33:
Open Terminal in TWRP and run the commends, shown below. Then flash SuperSu 278 SR3

In TWRP Terminal.
[SuperSU] coyote968:
Make the flash with SR3 ... everything runs smoothly..[emoji6]

Inviato dal mio CoyoteX
[SuperSU] petrus764:
As in, you have managed to boot with SR3 on a 5X updated with today's November security update (NRD91N)? Mine did not, but it could have been suhide that I flashed with it.
[SuperSU] andrew2432:
Is that the first time you flash or second time you flash or both??
[SuperSU] stevetrooper:
I am unable to get root to stick on my Nexus 6p running November's security update (NBD91K). I flash SR3 in TWRP and when I boot up, supersu is not there. I try to reboot back into recovery and TWRP is gone. Appears the new security update is doing something with recovery and root.
[SuperSU] twan69666:
I'm on the Nexus 6 and am just stuck bootlooping no matter what I try. I tried the terminal command in TWRP, but no luck