yashsingh1/xdaforums huggingface dataset:
[SuperSU] Strephon Alkhalikoi:
[MENTION=7796876]ted24j[/MENTION]: That is only the app, not the su binary. Chainfire keeps full packages at his site. A Google search should pull up the version you want.
[SuperSU] ~El Julio~:
As anyone can see, on Chainfire’s website homepage are all his previous G+ posts links as well as his tweets. (https://chainfire.eu)

There will be found the links to older versions of his apps...

Happy downloading !
[SuperSU] jdegreef:
[MENTION=7380600]~El Julio~[/MENTION] [MENTION=7796876]ted24j[/MENTION] [MENTION=2807229]Strephon Alkhalikoi[/MENTION]

Thanks for you replies ;)
[SuperSU] fefuzzo:
problem with Amlogic Km8 Pro

i have a problem to install systemless root on my smart box android with Amlogic S912, model

KM8 Pro

.

I have android 6.0 and twrp installed, and when i try to install supersu 2.79 SR3 the system recognize the systemless capability capability, but then i have the messagge "boot image: not found. aborting "

Is possible to fix this problem??? thanks a lot to all!
[SuperSU] barry123:
I hope I'm using the right forum as this was not an issue before I used SR3-SuperSU-v2.79-SR3-20170114223742. I've decided to root my Nexus 6P again. Using Lineage OS build NMF26B [7.1.1]. So the problem is, in developer options, I've enabled Android debugging/notify. Root access page only gives me option to ADB or disabled ONLY. ADB & Apps is NOT in the list since using the 2.79 file. Security: unknown sources is ticked off as well. I don't have a notification at all on my status bar about android debugging nor notification on connection options i.e. USB charging/MTP....etc. It was working before tho'. Anyone can help out on this problem? I am rooted, SuperSu app is enabled, etc. Double/triple checked everything, re-booted in case I did make any changes to be certain. I installed Lineage OS/GApps/SuperSU 2.79,etc from a flash drive, cleaning up my phone completely. It's only the problem with developers options problem. Thanks!
[SuperSU] jdegreef:
You don't have ADB & Apps in Developers Option > Root because you didn't flash the su add-on that comes with LineageOS to have root access. Nothing to do with Supersu.

As you want to use Supersu that doesn't matter. Just disable root in Dev. Settings.

Does Supersu work after flashing it ?

Concerning the notifications I don't know if it is related to Supersu. Did they display before you flashed Supersu ?
[SuperSU] Salem's galaxy:
Please Mr. Chainfire, could you please help us to root lg gpad 3 8.0 V-522? There is a root bounty. It would be greatly appreciated.
[SuperSU] CVAngelo:
Please Mr. please, don't play B17. It was my song, it was her song, but it's ooover! Dude, you are so off thread here, it ain't funny. (By the way, this is the FIRST attempt at a joke that I've ever posted on XDA...and I know I'm OT too. Lol)
[SuperSU] shoey63:
ONJ is an Aussie legend[emoji106] Jokes are a good way to break up the otherwise dry replies, or frustrating noobish questions and pleas. Everyone has a sense of humour. Keep 'em coming ?
[SuperSU] barry123:
If I recall, I flashed addonsu-arm64-signed.zip originally, downloaded SuperSU from Play Store but like many people, could could not update it. As far as I remember, I re-flashed with TWRP SR3-SuperSU-v2.79-SR3-20170114223742.zip and Super SU [Play Store] updated [I think] and works fine now. All my apps requiring root, i.e. Toggle Data [Play Store]/Secure Settings ] Play Store], etc., which I use with Tasker work fine now. I didn't realize disabling root in Dev. Settings would not have an effect on SuperSU itself. Yes, SuperSU works fine now. It's funny because older ROMs I've used before, I rooted fine but in Dev.Settings ADB & Apps were always available, not just ADB/Disabled only. About the notifications, I don't get any now, Edit: I revoked USB debug authorizations, and re-set it. I get the notifications now, but just did a re-boot and notifications don't show up again. Very strange. Yes they displayed before flashing SupSU. Thanks for your help and for the cross post I did. <blush>

Edit: Just plugged my phone in to re-charge. Dev. now shows debugging connected & USB charging notifications......when unplugged, no notifications
[SuperSU] barry123:
Edit: Just plugged my phone in to re-charge. Dev. now shows debugging connected & USB charging notifications......when unplugged, no notifications
[SuperSU] Crescendo Xenomorph:
Bootloop on SM-T705 stock T705DDU1CPL3.

It just show KERNEL IS NOT SEANDROID ENFORCING and reboots.
[SuperSU] jdegreef:
Well, I have no idea about your notification problem...
[SuperSU] Base2:
Barry123 - I'll take a guess at this. Going back to your original post you have flashed a Lineage OS based on version 7.1.1 (Nougat). Are you charging your phone from a computer or a wall charger? If you are charging from a computer then those notifications are same that I get when connected to my computer running Linux. Stock 7.1.1 for me always defaults to USB charging and I have to switch it to MTP file transfer manually each time even though Settings>Developer options>Select USB Configurations is set to MTP. (I abandoned Windows for personal use along time ago so I can't speak to that.)

As for the debugging connected, most of us trying alternative ROMs or are rooted usually have it enabled as well.

If you are charging from a wall charger then this is definitely unexpected. Is it the one supplied by the manufacturer with you phone?
[SuperSU] barry123:
I charge from both PC/wall and all Dev. notifications show up either way using Win 7. [USB debugging/charging or whatever]. Debugging should show up as well plugged or not, but doesn't when phone is unplugged. Mine doesn't have the problem of reverting to USB charging. It sticks to where ever it was last set, i.e. MTP/USB charging/etc. I use the manufacturers wall charger supplied. I just noticed something else. Before I didn't see all the Dev. options for ADB/Apps for "Root Access," only ADB or Disabled. Now I have the option of "Apps" as well. LOL! I re-boot normally after making changes just in case, but this time everything seems to be working fine. I'll live with the no notification on the "debugging" notification when unplugged, but I know that it always showed up in other ROMs I've used before. So I guess we can close this thread now. Thank you very much for your help on this!

---------- Post added at 04:46 PM ---------- Previous post was at 04:41 PM ----------

That's ok, it's fixed now. TY!
[SuperSU] jdegreef:
Here the "debugging" notification as always been displayed when the phone is connected to the computer. This is the case with all roms I've used from CM7 to LineageOS 14.1, RR and Slimrom. And stock, of course.
[SuperSU] barry123:
Yes "debugging" notifications show when plugged in whether on PC or A/C but used to show up even if unplugged, now it doesn't. On other ROMs, RR older CM and PN it showed notification unplugged, but I'm not concerned about that now. Thanks!
[SuperSU] barry123:
For your USB charging "problem" go here to use Tasker and Autonotifications plugin for that.. http://forum.joaoapps.com/index.php...ransfer-mtp-connection-with-the-computer.198/
[SuperSU] ~El Julio~:
Clearly not an issue or a problem, just a little and odd bug :

GUI crashes sometimes when using split screen mode on (up-to-date) Pixel C. This only happens when it's launched as the second app.

Re launching it usually works without anymore crash when reiterating.

The odd part is right before crashing, the "app might not work in split-screen mode"(or whatever it is in English) toast shows. Next launches don't show the toast message.
[SuperSU] dhplap:
Hello, could someone tell me if I have to do anything else after flashing SuperSU v2.79 SR3 ? I'm on EmotionOS and root is already enabled. Thank you
[SuperSU] Recl@imer:
Hey Guys,

Was just wondering, if I flash supersu 2.27 beta to gain root on N5, can I flash the stable SuperSU v2.1 after? will that cause me to loose root?

I'm planning to flash Vomer's rom, by the way.

Thanks.
[SuperSU] jayplusone:
Honestly this beta is stable enough. I'd just keep it. I'm not sure I'd risk the trouble. I'm on bigxies stock ROM without issues.

Sent from my Nexus 5
[SuperSU] Recl@imer:
Cool. Thanks.
[SuperSU] olarf:
Thanks a lot, the 2.27 works like a charm with cm12 on a S4 Active (GT-9295)
[SuperSU] GroteBozewolf:
2.27 running fine on my Nexus 4 lollipop. Did a clean install of lollipop using the full factory image. Then flashed TWRP 2.8.2.0 and rooted using the zip.
[SuperSU] GldRush98:
Chalk up another Nexus 5 working well!

-Flashed stock unmodded kernel back on

-Flashed via TWRP 2.8.1.0 (2.8.2.0 is having trouble on the N5 it seems)

su access seems to be working great, even for stuff like ES File Explorer that weren't previously working :)

Thank you sir. So glad I paid for Pro. You never disappoint.
[SuperSU] thesnipsnap:
Flashed Beta on N5 with stock Lollipop using TWRP. Works great.

Also, apps like Wakelock Detector started working.

Thanks a lot :)
[SuperSU] TheWilkieWay:
On CM12 if an app freezes once I hit grant superuser permissions and I close it, I lose root and have to flash supersu again, anyone else have this problem?
[SuperSU] ArclightX:
Please remind me again? How does Bigxie's Stock ROM differ from Google's Factory Stock ROM?

I'm on day 3 of looking for an answer to that question without any luck so far.

Thanks!
[SuperSU] jayplusone:
Honestly they don't AFAIK. I believe Vomer's is very similar if not the same. It's just a flashable zip for people like me that don't want to oem lock, receive OTA, or flash the factory image.
[SuperSU] abobobilly:
I just flashed the latest 2.27 BETA on my Nexus 7 (2012) running stock Lollipop. Seems to work perfectly fine.
[SuperSU] ZhekaS:
I have flashed v2.27 via TWRP on N4 with freshly installed Lollipop factory image and got a strange issue. The emulated sdcard storage became inaccessible. Tried to access it with file manager, it was shown as empty, and when tried to create new directories it gave errors. It was not accessible throug USB storage as well with the same symptoms. I could see the storage mounted, but empty, giving errors when trying to copy anything. In the TWRP file manager the folder was readable and shown content. I am not sure this is SuperSu related or not and I was too frustrated and rushed to reflash it, so unfortunately no additional info.
[SuperSU] jediratte:
2.30 looking fine on N4 linaro-frank [MENTION=3201173]Syko.[/MENTION] No issues.
[SuperSU] occtec:
[MENTION=631273]Chainfire[/MENTION] after flashing the latest 2.30 zip I now have x2 separate SuperSU icons in my app drawer?? I'm on the latest TWRP 2.8.2.0 running stock lollipop with Franco r68..
[SuperSU] occtec:
See attached.. I can access SuperSU from both??
[SuperSU] Chainfire:
Go into SuperSU -> Settings -> Launcher Icon, then select the one you want. This is because the default icon has changed this release.
[SuperSU] scoobyjenkins:
Double the fun!

Tapatalked that shiznit.
[SuperSU] occtec:
Thanks mate, that fixed it! Love the new material icon, very nice. All good here by the way all root apps working as expected and no problems with twrp. Thanks mate, good work!!
[SuperSU] veez21:
If there's no problem then all you have to do is to install root apps ;)
[SuperSU] dhplap:
I tried installing Supersu from the Playstore but after updating binary phone wouldn't reboot. That's why I'm trying to find out if this is compatible with EmotionOS which is Lineage.
[SuperSU] 77777772:
Are you working on next supersu release? If it is so, can you tell me release date and if it will support Nougat on "Huawei P9 Lite (VNS-L31 C432B336)"? At moment it seems so, that no one is able to become supersu working. But I want it :) Greetings, 77777772
[SuperSU] veez21:
don't ask for ETAs
[SuperSU] camp0s:
Small report here: Nexus 7 (2012), just flashed The Pure Nexus Project/6.0.1_r62 and latest SuperSU 2.79SR3. After reboot the SuperSU icon was in the launcher once, I was able to open it and trigger "grant on every request". After that the icon disappeared (I literally saw the icon in the launcher fade away on it's own). I also tryed reinstalling, from TWRP, but nothing appeared.

Root works, Busybox, some kernel tuner apps seems to work - what could have happened to the icon?
[SuperSU] Pkt_Lnt:
Look in Settings, PN puts it there.
[SuperSU] montafede:
pleaase could u explain better " If you were encrypted, format /data (ext4) and reboot into TWRP again " ?

is OEM mayby?
[SuperSU] habylab:
Having issues with apps accessing and modifying system root. I've seen this before as an issue but cannot for the life of me find it!
[SuperSU] SimplyCity:
If you are on device/rom with encrypted data partition (like for instance Sammy S7) to get what you need (root) you have to: turn on 'OEM unlock' in devs section in settings and unencrypt data partition. Best way to do that is to FORMAT it in TWRP and right after that reboot to recovery. That is pretty simple operation. While in TWRP again you can flash SU. But remember : formatting data partition REMOVES your all data, make backup first. I hope it helps. :)

Echoe™ team member / S7E
[SuperSU] -Deco-:
It could be that the apps you are using have not updated to be compatible with SuperSU systemless. Make sure you are flashing a .zip which does not include systemless SU.
[SuperSU] habylab:
It could be, you're right.

For testing, can you install Wakelocks Detector (green icon) and see if you can install it to system? In the sidebar there is that option. Doesn't work for me.
[SuperSU] -Deco-:
Sorry, personally I'm using SU systemless which means that it won't be there for me either. Flashing an earlier version of SuperSU will solve your issue.
[SuperSU] thorium666:
Hi,

after successful rooting of Nougat S7 i have been asked by SuperSU if it should disable KNOX for me. I've accepted to disable it. The problem is currently, that i can't enable device- or SD card encryption. Is it possible to enable Knox again without loosing root ? Is the disabling of Knox the reason for not working encryption?
[SuperSU] KyeWalker:
Hey guys looking for a bit of help!

I'm trying to install SR3 and I've tried STABLE version but not having any success!!. Systemless I get errors and System Mode I get boot loop.

I'm trying this on Galaxy S2 I9100, running CM13 Security Version October patch. Obviously I have fully un-rooted CM's built in root.

I have no issue on my Galaxy S4 mini running CM13 with same security patch, also have suhide on this device and pass SafetyNet successfully

Attached is recovery log for Galaxy S2. Ive never done a "log" before so it's got devices whole flashing history on there but right at the bottom is my problems with SR3.

Any help would be really appreciated and if it's possible for [MENTION=631273]Chainfire[/MENTION] to have a look and see what he can do would be a huge bonus!!

Many thanks in advance guys and girls!
[SuperSU] osm0sis:
S2 has a headerless boot.img format, which is more difficult to support.
[SuperSU] KyeWalker:
That's where it says it fails I think?

I've had to put log in zip, I couldn't upload in txt
[SuperSU] KyeWalker:
Is there anyway to support it?? Or does it require someone to work on it??
[SuperSU] osm0sis:
Yes, it fails at "could not find header" - the way other scripts unpack the older Samsung headerless format all involve blindly searching for the beginnings of the zImage and ramdisk, sometimes also second ramdisk. It would require some work.
[SuperSU] cupidsuck:
thanks this is really helpfull
[SuperSU] veez21:
:eek:, yeah and everyone thinks so too

:eek:
[SuperSU] KyeWalker:
I guess the likely hood of this getting done/tried is next to none.

If I'm right in my thinking, when it searches for boot image it looks in mp.... Something 5

But I swear it is in mp.... Something 9
[SuperSU] Galactus:
You must pick one or the other, both will not work.

Encryption - No root - can have TWRP - can flash mods that edit /system - will pass safetynet

Root - All of the above but no encryption unless you want to go back to Marshmallow
[SuperSU] thorium666:
Hi,

thanks Galactus. So this is final ? I had with 6.0.1 a well working root with encryption. In this case i better think about a roll back to M. Without root = useless ad-spam device, 7.0 with root = useless for any type private data :).
[SuperSU] Vlad Paul:
Hi! I flashed SuperSU v2.79 SR3 from TWRP 3.0.3-0 on my mi4c, MIUI 8.3 beta xiaomi.eu v7.2.23, all working great. Lot of thanx.

Best Regards,

Vlad
[SuperSU] Pkt_Lnt:
Chainfire answered this for you back in January. Very prescient of him, huh?

https://xdaforums.com/showpost.php?p=70618589&postcount=8960
[SuperSU] thorium666:
Don't got what you mean. Root is working, just encryption is completely dead and about this nobody mentioned a word (for sure, for rooting i had to format). Not a problem, i think i go back to M...
[SuperSU] Pkt_Lnt:
It is explained by Chainfire, the SuperSU developer in the post I linked above. Did you read it carefully? Your answer is there.
[SuperSU] thorium666:
Sorry, no idea what you mean. He is writing about encryption and rooting the device. The device is rooted already following his instructions, i just wanted to re-enable encryption (no idea how to store data on it where such devices quckly get stolen and my data i don't want to have it the hands of some facebook kiddies)
[SuperSU] Garfae:
We are having issues with language reversion to SIM1 default at each reboot/reenable. After some quick glace around it would appear this problem should have been solved back in November 2013. Could it be a reoccurrence? (Phone is not encrypted; we know this issue is persistent with encrypted phones.)
[SuperSU] sdembiske:
Unlocked Bootlader on your LG4 ... ?

Quick question as the H815 has the ability to officially unlock the bootloader, did you unlock first before installing Chainfire's Beta SuperSU? I am on an H12 with locked bootloader and no ability to unlock officially, hence my asking.

Thanks, S. .
[SuperSU] extrahelper88:
Working perfectly on my HTC one M8 GPE Thanks for creating it!
[SuperSU] sdembiske:
Have you rooted your own LG G4 with this process yet?

Given that you sent your post from an LG G4, have you managed yourself to root using this method with a locked bootloader? If so, would appreciate any info you can provide on what issues etc you ran into etc.

Thanks, S
[SuperSU] egingell:
No, I didn't and it's super easy to unlock the bootloader. Just search Google.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] sdembiske:
Brilliant ...

Brilliant, gee I wonder why I didn't think of that ..... Yes, easy if you have an H815, unfortunately I don't and most of what's posted on XDA doesn't cover MM 6.0 for different models - try it yourself ... and prove me wrong.

Cheers, S
[SuperSU] egingell:
I said Google, not XDA.

The Android version has absolutely nothing to do with the bootloader.

My phone is an H811 and I have successfully unlocked the bootloader.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] sdembiske:
811 yes, lots of how to do's but ...

None of the posts on how to enter bootloader/download/recovery mode on my model (H812) work either through adb commands (yes the device is recognized in adb) or physical button presses + usb cord insertions etc., so I'm sure you found a post to guide you as there are a number of them on XDA), unfortunately there seems to be some new lock-downs that have been incorporated with the MM release so I beg to differ - it may be carrier dependent.
[SuperSU] mamamuh32:
Root
[SuperSU] Ch3vr0n:
Root what? Tree? Yes, a tree has roots

Sent from my Nexus 6P with Tapatalk.
[SuperSU] brunopio:
Unsupported device: Moto G4 Plus ATHENE NPJ25.93-14 Android 7.0

Unsupported device: Moto G4 Plus ATHENE NPJ25.93-14 Android 7.0

Do not boot...

SuperSU-v2.79-SR3-20170114223742

instaling from twrp-3.0.3-n4-athene_shreps

(h t t ps://xdaforums.com/moto-g4-plus/development/recovery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337)

Logs and boot.img (google drive):

h t t ps://drive.google.com/drive/folders/0B0Fg4kGChrccbklpTlJyNkN0X2c?usp=sharing
[SuperSU] jdegreef:
[MENTION=8104781]brunopio[/MENTION]

Look here.
[SuperSU] Simbalage22:
Sorry wrong thread. This was for the CM13 Unofficial Build

---------- Post added at 09:45 PM ---------- Previous post was at 09:32 PM ----------

[/COLOR]AWW SNAP.. Is that the real ChainFire?

If so I must say a million thank you's as you have been my hero sense i did my first custom rom many years ago. I admire your work, and have been into I.T for about 15 years. Worked with shadowmite many years ago with the treo's and sense then been android all the way wide open.. Now If only you could crack the wifi calling, we'd never need oem roms :)
[SuperSU] oc2:
Hi

I don't know where the problem is.

Yesterday i updated my Nexus 5X to the March-Patch (i use Heisenberg's Guide and install the img's with fastboot), then i installed Francos Kernel as allways, and then SuperSu SR3.

Without SuperSU my device starts, when i install SuperSU i have a bootloop. Crazy.
[SuperSU] rbeauch:
I tried to reinstall 2.79 sr3 after updating my nexus 9 with the March security patches using twrp zip installer. Supersu appears to install correctly, no errors. Upon reboot it's not there but some apps show that the device is rooted but supersu is not installed. I've tried three times. Same results.
[SuperSU] Pete02:
Not sure if it makes any difference but I always install the rom, gapps, and superSU first then boot. After I'm up n running I go back for kernels. Just a thought.
[SuperSU] dahawthorne:
" install the rom, gapps, and superSU first then boot"

I've been doing this too for a number of months now, using the TWRP "Add another zip" function so that the three zps install one after another before rebooting. It has always worked fine (touch wood... :)).
[SuperSU] Xak:
[MENTION=631273]Chainfire[/MENTION] can you update S7QC super su to latest stable version which would be like SuperSU-v2.79-S7QC if existed 2.79 su is latest stable i think. its troublesome to keep super su as skip updates and then having to click yes skip many times. if you dont feel like updating it could you tell me how? this is probably in issue with all root engroot for usa s7 models. since we will not get perm root ever. not trying to be nagging but figured i could ask since its a bother and sometimes we click yes at least i do and it ****s up s7 usa root and you have to do a complete re install and engroot boot root etc it gets annoying is all. id rather be able ot update the su version my self manually if possible via replacing files in your version with files from latest su apk etc. or something like that.

Thanks
[SuperSU] ulxerker:
I have the same device and setup without any issues. flash supersu first and custom kernel afterwards.
[SuperSU] oc2:
Thx for your input/help, also to Pete02, i tested this but i have also this way a bootloop :(
[SuperSU] Ketawa:
The same thing happened to me, although I only tried once on my Nexus 6P. I went back to stable 2.79 and it installed successfully.
[SuperSU] Matce:
S6 920F, just upgraded to Nougat.

Had SpaceX Kernel while on MM also rooted of course.

Now installed TWRP after the upgrade and tried to install SuperSU 2.78 - stuck at "Creating image".

Phone wont' boot if I kill it and restart.

Do I have to get a custom kernel on there again? Really stuck here without a phone...

Please help!

Thanks
[SuperSU] Rami04:
I have the same problem as matce with SU 2.79 SR3
[SuperSU] MusikMonk:
Also true for the Galaxy S6 apparently (Nougat and TWRP 3.0.2).
[SuperSU] Alxoom33:
I have a Nexus 6, Android 7.1.1 March update and latest EX Kernel v. 4.18. Never had any problems with SuperSU 2.79 SR 3
[SuperSU] rbeauch:
I tried using 2.79 stable and i have the same result. My device us rooted as far as previously existing apps are concerned but supersu is not installed. Something is wrong with the Msrch security patches.

Here is the message from root toolkitDevice DOES have (system-less) root!

O/S - root info:

Android O/S: 7.1.1

SE Linux enforcing: true

su ctx: su

SuperSU installed: false

Root present: true

Device info:

Board: flounder

Device: flounder

Product: volantis

Bootloader: 3.48.0.0141

Maker: htc

Model: Nexus 9

Carrier: none (wi-fi device)

Filesystem Mount Status:

/system: mounted R/O

/ (rootfs): mounted R/O