yashsingh1/xdaforums huggingface dataset:
[SuperSU] HorstiG:
V 2.27 even works with KK 4.4.4 without Problems on Galaxy S3 - Liquid Smooth Milestone KK 4.4.4 Boeffla Omni NG Kernel Beta 7, Busybox Pro 1,22.1
[SuperSU] Srandista:
So, as I flash stock kernel from factory image for my Nexus 7 2013 (flo), and after that I installed SuperSU from TWRP. I successfully rooted my tablet, I verify that by running Total Commander and Wakelock Detector. Thank you Chainfire, for your awesome work!
[SuperSU] akidsix:
back to stockrom via flash factory image nexus 5

download supersu beta v2.27 > flash TWRP > flash supersu beta v2.27 via TWRP > reboot = StockRom + Root !

thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] SamuriHL:
Another update. I updated my S4 GPE 4.4.4 to 2.2.7 and it's working fine there, as well. Hopefully I'll get to test it out on 5.0 "soon". :)
[SuperSU] vukis:
Just for curiosity: how i should revert to stock kernel? Flash system.img? Boot.img? Both of them?

I restored full twrp backup and flashed 2.27 and it works! Even call recorder works without aditional kernel patch supporting permissive SELinux.

Cool! I like this being completely stock with only root. ;)

Thank you !
[SuperSU] Srandista:
fastboot flash boot boot.img
[SuperSU] Dave08:
FWIW (since you're up to 2.27 now), 2.26 is working great on my N5, stock Lollipop with Franco kernel. For the first time since updating to 5.0 Secure Settings can set airplane mode again, the only change was SuperSU. So, the SELinux-oriented changes appear to be spot on. Thanks.
[SuperSU] vacsed:
Is the bootloop issue with encrypted devices fixed with 2.27? Why did the bootloop happend in the first place when both the system and the boot partition are not encrypted?
[SuperSU] rhamej:
I wanted to clean everything up, so I fastbooted the factory img and wiped everything. Let it boot and set up all my apps again except for the ones that require root. Then I fastbooted TWRP (2.8.2.0). Flashed CF latest SU and booted up system. Installed my root apps and checked them out. Busybox, Root explorer. Worked fine on the stock kernel. Booted back to recovery and installed EX. Went through the aroma installer. Booted back to system. Checked my root apps again and all were working fine. Installed the EX app and set up my settings. Rocking along fine.

Edit: Device is a nexus 5
[SuperSU] psygbert:
seems 2.27 breaks usb debugging mode on both my nexus 4 and nexus 5
[SuperSU] rhamej:
Working flawlessly on my n5.
[SuperSU] psygbert:
have you tried connecting your usb? it will be checked then later it will be unchecked.
[SuperSU] rhamej:
Unchecked it, plugged in phone. No Debugging. Unplugged phone, rechecked, plugged it on, still checked. Unplugged it with it both unchecked and unchecked, stayed off and stayed on.
[SuperSU] Paschfire:
nexus 5 android 5.0 LRX21O + franco kernel r68 super SU v2.27 usb debugging, adb and mtp connection all is working flawlessly here( i just tested all)
[SuperSU] psygbert:
nope. doesn't work on both of my phone. downgrading supersu did the trick. debugging logo appears then disappears on several seconds while connected.
[SuperSU] Ltdrev:
I was to post this on G+ when I read carefully :P

Happy to report:

N5 stock kernel/rom lrx21o is fine (cleared the log it works)

N5 franco kernel r68 lrx21o fine (just installed about 40 min ago, rebooted twice no harm, just cleared the log it works)

N4 stock lrx21t fine (since lunchtime, no wifi no sim)

No bootloops ADB/Fastboot fine (concerning first post up the page; USB debug mode ok)
[SuperSU] pjd2011:
Anyone have any luck getting this on a bootloader locked device? Flash Gordon and the apk isn't giving me any luck on 4.4.4
[SuperSU] ramjet73:
Testing of SuperSU 2.27 with ElementalX L 2.03

I tested SuperSU 2.27 with the stock LRX21O 5.0 ROM for the Nexus 5, then flashed a modified version of the ElementalX L 2.03 kernel, and everything worked as expected. My modification to the kernel removed the edit to the ramdisk that mirrored what was being done in CF-AutoRoot if that mod wasn't already installed.

The results of my testing are in this post.

ramjet73
[SuperSU] GtrCraft:
What I am interested in is, do root apps like viper4android works with stock kernel + 2.27? Can anybody tell me?
[SuperSU] midgarsormr:
I don't have 06suhide...so maybe that's the issue. Root switcher also keeps putting me in a bootloop.
[SuperSU] grep_i:
I would I knew the answer but honestly I don't I'm happy it suddenly started working for me as I was ready to give it up and wait for another solution, that seldom happens I was really desperate from all the flashing, testing etc.

The only thing I can tell is what setup I have now and that this works for me.
[SuperSU] egingell:
To be fair, Google Wallet still exists, but without tap-and-pay. It's basically Google's version of PayPal.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] midgarsormr:
I guess I should've told you my set up. I couldn't boot 7.0 but I'm reverting back to 6.0.1.
[SuperSU] midgarsormr:
EDIT: I was on multirom so I cleaned up and went back to the latest TWRP, flashed back to 6.0.1 and restarted. All of a sudden it works for me. I don't really know why or what I did differently this time but it works.
[SuperSU] Ketawa:
FWIW, I successfully updated to 7.1.1 NPF10C on my Nexus 6P and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
[SuperSU] tag68:
The default on many Moto devices (E <variant>, G <variant>, X <variant) seems to be system, but only systemless if using that ECHO line to configure seems to work. Users keep asking for help after flashing current SuperSU, but the device does not boot anymore. Can that detection be modified to give a more appropriate result on Motorola devices, to avoid these discomforts?
[SuperSU] miloytyn:
Are you planning to add file based encryption support also?
[SuperSU] Chainfire:
Yes.
[SuperSU] grep_i:
Than we're at the same point now, the same happened to me.

I'm absolutely clueless as why it's working now for me.
[SuperSU] Govar Jabar:
Thank you for your work!
[SuperSU] MigoMujahid:
Hey man!

Sorry to disappoint you, but supersu doesn't work with cm13 in our s2, you need a patched boot image......i stopped trying when they told me that in Q&A thread, use cm root instead, it's not bad actually, I like it :D
[SuperSU] F3N!X:
I'm not disappointed. I've successfully repacked boot .img for the Mokee Rom 6.0.1 that I wanted to install, following the advices shared here with me by xda members, as explained in previous page (post #7572).

But you have to know that I've also tried Dirty Unicorns for i9100 and it's full of choices that I don't have in Mokee, but the most important to me was the inclusion of SuperSu into the ROM and the SELinux feature set to permissive (+Synapse integrated too). I've finally kept Dirty Unicorns and I'm very happy with it.

Note that Bliss Rom is very good too, very close to Dirty Unicorns, SELinux permissive and no problem with SuperSU. It means that grep_i was right when he told me "probably your devices ramdisk is not compressed with gzip and can therefore not be decompressed by the SuperSU installer as it only supports gzip", so it's not related to hardware or partitioning as I thought first.
[SuperSU] MigoMujahid:
Happy to hear that, I think I'm gonna try DU again, last time i tried it, it had some problems with animation that i couldn't fix, I'm using AICP now, it's a great rom too, and full of customizations, and also lite in its usage, I'm planning to move to android 7.0 now, AICP is the first s2 rom to use cm14 and make it customizable thanks to [MENTION=5651185]GreekDragon[/MENTION], I hope they make cm14 official soon, that would be awesome :D
[SuperSU] robburns20:
good day guys and gals, i am really stuck as i flashed the latest ruu for my htc m9 and made sure all my ota were done after that...Now im trying to reroot and i flashed twrp then put superuser on sd and flashed in recovery but im stuck in a bootloop at the white HTC screen...its been 30 mins plus and it still keeps going....i have tried over and over with diFF twrp and super user combos but still the same boot loop...Please help...Thanks in advance i am unlocked and s-off threw Sprint
[SuperSU] furyin:
Just get a phone cover with card slots at the front and put your card there. You not only get to tap and pay , but you protect the screen of the phone too.
[SuperSU] iXaidyiu:
I am unable to remove SuperSU inscribed in /system by the ROM maker, after flashing the UNsu.zip, clear cache & davik cache and immediately refalsh SR1 (I tried also clean boot without SuperSU then reboot into TWRP to reflash), it always install back in System mode. Any fix or methods for me to make SuperSU systemless? Thanks!

P's sorry for quoting an ancient post.

P's2 sorry for asking a noob-like question.

P's3 I tried to search the thread but I doubt know what to search for:crying:

--------------------------------------------------------------------------------------------------------------

EDIT1:

Problem SOLVED by installing this "adapter", then flash SR1, after that flash suhide. Big thanks to [MENTION=6892913]darrendude1[/MENTION] for prompting me this mod:D

---------------------------------------------------------------------------------------------------------------

EDIT2:

Was happying too soon, suhide seems not working, I repost over the suhide post here.
[SuperSU] iXaidyiu:
I tried, but it didn't work. Still in system mode.
[SuperSU] RandomPooka:
Only slightly related to the topic, but my bank's tap and pay app detects root, gives you the option to continue anyway by clicking 'OK' on a nag screen, and then works just fine for transactions with your phone. As long as you open the app while waiting in line and pre-click the nag screen, no time is lost and other customers aren't inconvenienced by the delay. Win.

Now I can focus on just using Supersu for root functions and not worry about hiding it from AP. PoGo can suck it if Niantic continues to prevent modded devices from running the app.
[SuperSU] Pkt_Lnt:
Contact the ROM maker.since they placed the SU that you cannot remove.
[SuperSU] dastinger:
Hi,

I'm having the same issue on a stock HTC 10. Could you please PM me the same information?

Thanks!
[SuperSU] Nekromantik:
Anyone noticed the following issue:

Flashed a ROM that came with SuperSU installed.

It states flashing in systemless mode however there is a SU binary in /system/xbin

Tried to unroot using zip and flash Magisk + supersu

Removed Magisk

Flashed SuperSU again

Lost root no matter how many times I flash supersu.

Only option was full wipe.
[SuperSU] dcroz:
if i flash this on my moto g 2014 then try to flash suhide i get "fatal error number 1" and it askes my if i have supersu installed in systemless mode. i also tried that echo SYStemLESS=true.... command. does not work.
[SuperSU] mitchdickson:
I bet you did not remove system root before entering the systemless command.
[SuperSU] tc0566:
Titanium backup is not working..supersu grants it root access and then titanium backup says it is not rooted.
[SuperSU] Paschfire:
Wow! The amount of supporting information provided about your device and current setup is astonishing, I bet you'll get the help you need right quick.
[SuperSU] tc0566:
The device didn't seem to matter as it is an issue with titanium backup not being able to see root properly.. But it's a nexus 6 with latest PN.
[SuperSU] Phazmos:
Works fine on 6p with latest pn
[SuperSU] tc0566:
titanium backup is unable to access system says it's read only
[SuperSU] Phazmos:
R u trying to restore system data?
[SuperSU] reiichiroh:
I just got a request for root from "zygote 64" on this version or SuperSU. Does anyone know what this is about?

---------- Post added at 02:43 PM ---------- Previous post was at 02:21 PM ----------

Accidentally granted it permission after it appeared on the initial reboot after a TWRP backup. Went back and re-restored the same backup but it didn't appear this time.
[SuperSU] drothenberger:
I had a similar request two days ago. I did not grant access and didn't notice any problems. I have not had the request since.
[SuperSU] reiichiroh:
I granted by mistake and tried restoring my TWRP backup 5+ times without seeing it again weirdly enough.
[SuperSU] dcroz:
seeing as i do not know what that is i will say, no i have not. is that doing the rm /bin/su or something because that didn't work either, said there was no such thing. i remember there being an issue just with moto g 2014's that had a work around, something like flashing a special boot image or flashing regular supersu first? how do i do what youre saying?
[SuperSU] Hinzman420:
I have tried to flash the systemless root but none of the boot images work for my phone. I have a Lenovo k3 note. It is a mediatek device. I have tried magisk as well with no results except bootloop. With magisk I think it's because when it unpacks and repacks the boot.img it does not repack with mediatek headers. If I send you my boot.img could you get systemless root to work on my phone.
[SuperSU] egingell:
It's /system/bin/su.

At any rate, there's an unsu zip in this thread somewhere.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] blacknikname:
Hello brave people, need some help.. Flashing supersu systemless resulting in error patching boot image and aborting...and no root... In system mode result is bootlooping... Android 7.1
[SuperSU] mielletseed:
Since systemless came out it's not working stable on my Samsung Galaxy S5 Mini G800H with stock ROM. Sometimes it seems to loose root, sometimes it hangs, sometimes there is no root access dialog opening. All get's fine after reboot ...

previously I used to root it twice one time systemless (for patching the policies) and one time in system mode. This works stable for me. But now I completely reinstalled all wiped complete phone, reinstalled ROM with erase option and decided to give systemless an other try. But it's still quite unstable to me :-/

has anyone a suggestion how to get it stable?
[SuperSU] dcroz:
thanks
[SuperSU] vandyman:
I have a Nexus5x with the 7.1 ota installed. If I install su, some of my apps will crash. Without su my apps will work okay. Some of the apps that crash are; Amazon, MS Outlook.

The only reason that I need root is for some apps that require root like Titanium and Root Explorer.

Very odd...
[SuperSU] ulxerker:
SuperSu isn't fully compatible with 7.1 yet, you'll have to wait for an update.
[SuperSU] vandyman:
Thanks.. I went back to 7.0 for now.

Just read in the Pixel thread that Chainfire is looking into this when he gets the Pixel delivered in a couple of weeks.

I guess fixing root for the Pixel will help us with the Nexus5x. :confused:
[SuperSU] Pkt_Lnt:
He posted on Twitter that he has it, bootloader unlocked, rooted, but looking for a better method still.
[SuperSU] d4nvjpl0ng4n:
Anyone can send me the file "su.img" of supersu 2.78-SR1 in /data.

I need it urgently. thank you in advance
[SuperSU] egingell:
There are a few things in there that you can delete once it's mounted (all the files (non-folders) in the root, everything in the folder "su.d", and the folder "eu.chainfire.supersu" (it might just be a symlink--I forget)), but here's mine.

http://cloud.tapatalk.com/s/5812940a0a49e/su.img.zip

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] dtriguero:
Why not reflash supersu it will recreate the su.img

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] Constrabus:
Nexus 6p

Did:

-full unroot

-flash latest franko

-flash SR1 superSU

-reboot

-flash suhide

-reboot

-run suhide06 fix command

-reboot

Not passing CTS profile
[SuperSU] grep_i:
Install root switch and you should pass safetynet, if not remove 06suhide and reboot with root switch still installed try again
[SuperSU] d4nvjpl0ng4n:
your su is 2.78 SR1, right? Thank you so much.

Because my supersu is attached into the boot.img so even I flashed it, it still returns to the old one. I need the su.img to edit the boot.img and flash boot again
[SuperSU] egingell:
It is, but I don't think it matters.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] d4nvjpl0ng4n:
Ok let me try. thanks :*
[SuperSU] 127cwho:
Hi, everyone. I just understand what is systemless today, so how can I install systemless root which work with Magisk?
[SuperSU] ashyx:
You're not making sense.

As said all you need do is reflash supersu.

It will recreate the su.img.
[SuperSU] frecciak:
I tried installing supersu sr1 2.78 in systemless mode in my galaxy i9505 whit lollipop stock, forcing the command echo systemless = true from TWRP, but it always installs in system mode .... I must use some special kernel?

i tryed whit :

echo "SYSTEMLESS=true" > /data/.supersu

and whit:

echo SYSTEMLESS=true>>/data/.supersu

But everytime i get system installation.

Can someone help me?
[SuperSU] grep_i:
It's not possible on lollipop without the usage of Magisk as far as I know.
[SuperSU] frecciak:
damn...i cant find solution to get hidden systemless root in my i9505...suhide dont work in lollipop, magisk dont hide root and sr1 systemless dont work in lollipop :(
[SuperSU] grep_i:
Magisk can hide root, go over to Magisk thread and learn about automagisk and phh supersu and hidesu maybe that can help you out.

Or you have to flash a custom rom like CM13 for your device as it supports Android 6.0 Marshmallow on Samsung Galaxy S4.
[SuperSU] kylemd:
Hey guys,

Searched in the thread and couldn't seem to find an answer.

Just doing a clean install of the latest CM13 nightly on a Xiaomi Mi5, and I can't seem to get SuperSU 2.78 to install without either bootlooping.

I have tried systemless and system versions, as well as the Aroma installer. All fail when trying to extract ramdisk.

2.77 says it fails while extracting ramdisk, but then "applies hex patches". The SuperSU app doesn't like the fact that I don't have the latest binary, but that does work.
[SuperSU] Chainfire:
v2.78 SR2 released - https://plus.google.com/+Chainfire/posts/fvEPo42GKXS
[SuperSU] marc.ientilucci:
still unsure how to flash this without a custom recovery :(

any1?

EDIT: I found the README in the zip :)
[SuperSU] ipdev:
Nexus 5x (bullhead) NPF10C (7.1.1)

SR2-SuperSU-v2.78-SR2-20161029143931

Seems to be working so far.
[SuperSU] marc.ientilucci:
Phone: Google Pixel

- I have tried two times now and still no root detected.

- When i boot into the phone, I have to start setup. I log into my Google account and choose a previous point to restore from the cloud.

- I head to the Play store and install SuperSU When I open it, no root detected.

-- Let me know if you'd like me to pull any logs.

Anyone having any luck?
[SuperSU] rockman1117:
Flashed the boot as per the README and rocking root on my Pixel XL. Thanks CF!
[SuperSU] marc.ientilucci:
were u coming from a fresh bootloader unlock by chance or were u already unlocked, booted into the OS before flashing the boot.img?
[SuperSU] Golf c:
Unlocking bootloader wipes your phone. You have to setup phone and enable USB Debugging in developer settings and it will work.
[SuperSU] nk950357:
Mi 4i with miui 8,android 5.0.2

after patching the boot.img,wifi doesn't work,and sim card couldn't be detected .
[SuperSU] sionicion:
Pixel XL user here, in the time being, without FlashFire and custom recoveries, does anybody know a way to flash ZIPs? Trying to get viper4android up and running.
[SuperSU] vandyman:
Nexus5x, SR2 & 7.1 is working for me.

Thanks......
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Flashed SR2 with flashfire on 6P running 7.0

All systems GO. AdAway working, Root checker working, Flashfire working
[SuperSU] Alxoom33:
Working on my Pixel C running Android 7.1.1 beta. Took 2 tries though.

Suhide v. 0.55 bootloops, though.

Working just fine on my Nexus 6 running latest stock Android 7.0
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Spoke too soon. Had a random shut down, after that it takes an enormous long time for su to initialise. Root aps like root checker basic fail to detect su, because su daemon doesn't seem to respond. Goes into 2nd attempt, then fail because daemon doesn't respond. Tempted to restore backup, but can't until prior questions are addressed. SR2 slows down my 6P to a crawl. None of the apps that rely on root will work. Cf lumen doesn't boot, nothing does. And since ff needs root i can't restore the backup. Device simply locks up completely and I have to force reboot constantly.

Using stock everything. No custom kernel, rom, xposed...
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], I am having Issues with Orbot dropping my connection since using SR1 and the latest Orbot app, same thing happens with SR2. I am now in touch with the developers of Orbot to find the root cause on the two devices I have. Just wanted to let you know in case this might be caused by SuperSU (I don't think that it is). Everything else works supersmooth, I simply love your app. Do you accept cash send via letter for donations?
[SuperSU] HAPPYSADPERSON:
[MENTION=631273]Chainfire[/MENTION] Having root on the Pixel XL will endlessly force close System UI when you hit 15% battery or lower. Plugging it in or having battery higher than 15% will immediately stop the force closes.
[SuperSU] blacknikname:
[MENTION=631273]Chainfire[/MENTION], how could solve this problem?
[SuperSU] ashyx:
Well you can start by giving more details, which device, which OS build, stock, custom?

[MENTION=631273]Chainfire[/MENTION] might be a superb dev, but I'm sure his talents don't go as far reading minds. [emoji55]
[SuperSU] blacknikname:
Ha ha) reading mind it's something over our talent))

Well, it's a AOSP 7.1 ROM, Nexus 4, custom) with 2.78 SR1 same... any ideas?

Attached boot.img
[SuperSU] psygbert:
SR2 cannot read the SuperSU logs
[SuperSU] Ja_som:
I also have "No logs available" in SuperSU app on my Nexus 7 2013 with AOSP 7.1

But root works OK
[SuperSU] kylemd:
Having issue installing any version of SuperSU as below - think it may be recovery related but can't hurt to ask. Any solution to install SuperSU?
[SuperSU] Chainfire:
Which form of encryption are you using - none, full disk encryption, file based encryption ?
[SuperSU] Ja_som:
AFAIK none, in Settings - Security, option to encrypt my device is available, so I think that full disk encryption is not enabled, I can't find option in Developer settings to enable file based encryption, so if is not default, then I think none. I did not encrypted it manually...

Is there any way to check it?

Thanks
[SuperSU] Midomad:
Same thing here No logs available using Nexus 5x with stock 7.0 and elementalX kernel.

View attachment 3920404
[SuperSU] vandyman:
I have no problem reading the logs using the supersu pro app.

Nexus5x 7.1.1 with no add ons.

I normally only use Francos kernel, but he has not updated it yet.
[SuperSU] Ch3vr0n:
Woke up this morning to a completely dead phone, i mean not even 1%. It had only stopped charging to 100% a few hours before, so there was severe drain on the phone. Only way to fix it atm was to reflash boot.img and flash sr1 over the top to get root again. After the normal reboot of doing that and issueing a root checker check, the app responded in a second the phone was rooted. Definitely something wrong with SR2.
[SuperSU] quincho54:
Can't confirm that. I'm on a note 4 exynos with costume Rom sixperience, no problems so far.