yashsingh1/xdaforums huggingface dataset:
[SuperSU] DPyro:
Not working on Moto E (Surnia). Stuck on boot in stock Android 6.0.
[SuperSU] xpmule:
Yup happened to me too. v2.7.1

How do you undo a failed install from Flashable-ZIP/TWRP ?
[SuperSU] edgarf28:
[MENTION=631273]Chainfire[/MENTION] Can you please look at this issue?

I have this issue on the Galaxy S6 (G920F/G925F) with 100% original stock Marshmallow Odin firmware (no other modifications than flashing supersu & installing twrp)

With supersu 2.70 & 2.71 the SocketListener message shows up every 5 seconds in my logcat.

With supersu 2.68 I don't have this issue.

Supersu 2.70 & 2.71 also uses more battery on the Galaxy S6, because above issue.
[SuperSU] onesolo:
I just discovered today, I flashed 2.71 some days ago, that after I flashed 2.71, it reverted back my kernel, from the one that I had installed, Ex Kernel 6.15, to the stock kernel!!!

I can't figured why this happened!!! Plus, on the first reboot after flash SuperSu, Xposed was all crazy, I had to reboot once again so he could assume that modules were installed.

I guess that something went wrong cause I didn't do anything else after I flashed 2.71. Very strange indeed.
[SuperSU] corkiejp:
[MENTION=298306]onesolo[/MENTION] Flashing of supersu restores stock kernel and modifies it again for root.

That is why you lost the Elementalx Kernel. Every time you flash supersu, you need to reflash elementalx afterwards.
[SuperSU] xxskorpion88xx:
Updating binary fail on Nexus 4 6.0.1 hellcore kernel b-87

I was updating from superSu 2.70 ( always updated normally not in twrp).

After fail I updated my twrp from 2.8.7.x to 3.0.0.1(last a avable) I did updated selecting TWRP , system rebooted in recovery applied script but still notification appear "supersu mast be updated".

Please fix
[SuperSU] RandomPooka:
It took me a couple SuperSU flashes to realize that's what was happening. Now, I know to just add EX to the flash after a SuperSU update.
[SuperSU] Spartacus500:
Galaxy S4 I9505 stock 4.4.2, I have a problem on 2.71 with the update binary files failed, can I rewrite the file "su" in /system/xbin/su and it will solve my problem ? I note that now I have root and super su 2.66, later I have a probrem update su binaries , please answer
[SuperSU] Namelesswonder:
Anyone take the dive yet on testing SuperSU 2.71 on the new April security update? I'm about to test it.
[SuperSU] MrKaon:
Working fine after today's nexus security update, thanks

---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------

Yes everything is fine.
[SuperSU] MrKaon:
Yes everything is fine.
[SuperSU] corkiejp:
Successfully used FlashFire to update my Nexus 9 with 6.0.1 (MOB30D) Factory Image and rooted in the process with 2.71.

Google has since pulled the image for reasons yet unknown.
[SuperSU] dechronic:
logcat errors for ES File Explorer v4.0.4.9

04-04 20:40:51.731 832 832 W PackageManager: Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.estrongs.android.pop (protectionLevel=18 flags=0x3848be44)

04-04 20:40:51.731 832 832 W PackageManager: Unknown permission android.permission.ACCESS_SUPERUSER in package com.estrongs.android.pop

04-04 20:40:51.731 832 832 W PackageManager: Unknown permission .PERMISSION in package com.estrongs.android.pop
[SuperSU] Kustaa:
I've searched for this but without luck. After I flash stock system and boot (for the Google security updates for example), can I go straight from the fastboot screen to recovery and flash SuperSu, Xposed, Bootanimations etc like queued? Or I need to reboot between them, or just reboot after SuperSu and then flash the others...?
[SuperSU] RandomPooka:
Have you tried deleting the app from supersu settings, forcing it to reacquire permission?
[SuperSU] dhruvdave:
supersu doesnot grant right to es explorer.Nor es explorer ask for rights.I am using samsung j7 5.1.1 Help
[SuperSU] haseoxth:
This post may help you.

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post66140836
[SuperSU] dhruvdave:
Installed root explorer it is working fine
[SuperSU] RandomPooka:
Wondering if the app was hard coded to look for su in an "old" location.

I like Total Commander for it's dual pane interface and many plugins, and it works wonderfully with the most recent SuperSU
[SuperSU] HansiHusten:
I am planing to OTA update my N9. Last update I did was around December and did afterwards the "systemless root" methode.

Can I do a regular OTA now via internal update and root with this current beta afterwards? Is this still the "systemless root" mothode? Dont see any info about this in 1st posting
[SuperSU] haseoxth:
Total Commander is a very powerful file manager app, and yes that's exactly the reason of this issue these apps really need an update for that.

By the way I have 10+ apps which need root for some functions to work on my device, only two of them won't work properly due to the reason above, ironically they are both made by Chinese company (and I am a Chinese user...) :eek:
[SuperSU] RandomPooka:
So far, the only app I had that gave me trouble was "Secure Settings", and I don't use it anyway. I was going to try to use it with Tasker, but it didn't play nicely with systemless root. So, I threw that idea out the window and found another way to do what I wanted to do.
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] may I ask you for support?

I'm on Android N on my Nexus 5X and I use Total Commander app. But I can't write to system, I can only read from it, only one file manager which works is Root Browser, but I don't like it, as [MENTION=3670820]haseoxth[/MENTION] wrote TC is best :)

I tried to report this issue to ghisler (author of Total Commander) and he don't know what to do.

Here is our communication on his forum:

http://ghisler.ch/board/viewtopic.php?t=43730

Here is screenshot of error which I get when I try to remount system to RW:

And here is log (CatLog):

https://drive.google.com/file/d/0B0bWVvdcNSQlS0VUNjFjTmV3dmc/view?usp=sharing

Thank you
[SuperSU] Chainfire:
Point him towards https://plus.google.com/+Chainfire/posts/dGPQytapwe3, it goes into detail about which mount commands do and don't work, and why.
[SuperSU] Ja_som:
Thank you :)

This command works in TC :good:

mount -o rw,remount /system
[SuperSU] RandomPooka:
Odd. I was using TC on the N preview for shamu with Elementalx kernel 4.01 and had no problems writing to system. May have been something with EX helping me out
[SuperSU] dechronic:
ES File Explorer only works in the compatibility mode when su is binded to /system/xbin.

Anyone has the link to the documentation of the correct way to call SuperSU for both system and systemless for me to point to for the authour?

Edit: Found the info in OP of the Stable thread
[SuperSU] MrKaon:
Total commander is very nice file explore but it shows its age. Try fx explore let me think what you think :

https://play.google.com/store/apps/details?id=nextapp.fx
[SuperSU] Ja_som:
No, thanks... I use TC for years, also on my PC, I like two panels side by side. Also my issue was resolved, thanks to Chainfire...
[SuperSU] aursta:
Cant modify system files.any solution?
[SuperSU] casouzaj:
Me too. I use it since the long time dead Windows Mobile. Don't have plans to switch it for any other file Explorer anytime soon. Thanks a lot to Christian Ghisler for such a marvelous app!
[SuperSU] MrKaon:
For the record fx explore has two panels, and also multi windows.
[SuperSU] dechronic:
I use ES because I can gain root, cut/ copy and paste files, open/modify files and access my network shares.

Any suggestions on an explorer that has all those features?

EDIT: Total Commander seems to have those features. Will check it out.
[SuperSU] Fif_:
So does FX + FX Root Plugin.

I think you only have to pay for network and cloud connectivity.

I bought the app just because it is a very good file manager.
[SuperSU] spainter:
Root Explorer also has those functions.

I used ES as well until they started cutting features and injecting ads. When people started complaining then they came out with the pro version to get the features back and remove "some" of the ads.

But this is really off topic for this thread.
[SuperSU] tvisforme:
Solid Explorer has all of these functions, and looks good as well. I used EX for quite some time because I needed some network features that Root Explorer lacked at the time. However, recent versions of EX became bloated and have privacy issues, so I've switched to Solid.
[SuperSU] jesssiii:
Yes you can.
[SuperSU] joe_clasher!:
You need to use FX File Explore and Root add on
[SuperSU] MrKaon:
If this prompt crashes where would be bug?

TWRP or SuperSU system less?

Nexus 6P stock
[SuperSU] Captain_Throwback:
That's Android, so it shouldn't have anything to do with TWRP - though I also don't see what it has to do with SuperSU?
[SuperSU] MrKaon:
How can I remove it?

It appeared after I unlocked the bootloader and flashed TWRP,

At first run twrp asked for pin code and I gave it my pin code, since then after each reboot it is asking for my pin.
[SuperSU] corkiejp:
http://xdaforums.com/nexus-6/help/disable-pin-start-t2954652
[SuperSU] joe_clasher!:
I wonder why he didn't remember enabling it.
[SuperSU] MrKaon:
Silly me :eek:
[SuperSU] xpmule:
Ok i am confused.

What do i have to do to get systemless install on Marshmallow with a Moto-E rev2 ?

I thought it was suppose to have a built-in bootloader patcher.

I tried that 2.67 from that topic thinking it's different than the 2.71 beta which is NOT systemless capable.

All i ever get is a failed boot.

I am trying to flash from TWRP with the flashable zip of course on a fresh install of Marshmallow 6.0

XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml

All anyone ever says is "Install it in TWRP"

I am and its not working and since others say it works i must be doing something wrong.

Then when i Google it it gets even more confusing.. many topics say you need the download & flash a custom bootloader

RIGHT AFTER they tell you it NOW has a bootloader patcher.. a massive contradiction !

Can somebody say what they actually did with SPECIFIC details?

My TWRP log looks like it's doing a normal install with 2.67 (downloaded from the Systemless topic)

And when i Googled it i seen for example some guy ALSO flashing some other thing too.

I would be sooo grateful if someone can clear this confusion up for me and has anyone else got it on the Moto-E installed ?

I also have been using the normal install on Lollipop since last year and it has worked great so i am not a full noob LOL

So please and thank you guys... HELP hahhahahah

EDIT:

OK i got working :)

Seems to be working PERFECT NOW !

I read this.. http://androiding.how/root-moto-g-2014-marshmallow/

So i tried that on my Moto-E rev2 and i used Squid's TWRP 3.0.2-r1 (Telus MM mentioned earlier)

I tested TWRP + System etc and used Root Checker and rebooted and checked them all again.

All is working properly best i can tell.. AND unlike others i see no slow down using the OS at all.

I also had no trouble on first boot or after.. it booted FAST (after rooting)

I paid attention to what the TWRP console logs said too.

When i had just run 2.67 beta it seemed to do a normal install then i couldn't boot. (Flashed from TWRP)

But when i used 2.62 it detected my Bootloader and patched it..

Then when i ran the same 2.67 installer again afterwards NOW it tried the systemless install.

And it too checked the bootloader and reported it was already patched etc.

No idea what is going on but thanks to that web site for the Moto-G Trick (which worked on my Moto-E 2015)

Thanks chainfire.. ;)
[SuperSU] linqdesires:
anyone with supersu working on mhc19q Nexus 5X? which version? thank you
[SuperSU] SamuriHL:
2.7.1.
[SuperSU] Aman Dewett:
:(

Hello [MENTION=631273]Chainfire[/MENTION] sir i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.

1. I tried every version of TWRP for moto G

2. Tried every version of supersu

3. Without flashing supersu i boots up perfectly.

4. I can't provide log as phone is not booting up.

I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.

First two are after flashing supersu on cyanogenmod and the last one is after flashing supersu on stock
[SuperSU] dahawthorne:
I've searched Google & this thread and I find no references to this.

My Nexus 5 is running MMB29X with TWRP 3.0.2-0.

I've just noticed (after seeing an unrelated question in another XDA thread) that the Supersu version in the Nexus 5 SuperSU settings page is "Supersu Pseudopro v2.71".

Any idea what this is?

My Nexus 6 with the same version installed the same way (via TWRP) shows the normal "SuperSU Pro v2.71".
[SuperSU] Pkt_Lnt:
In setting there is a "freeload" checkbox that lets you have Pro features for free. Install the Pro key and it goes away.
[SuperSU] dahawthorne:
Ah, thank you. In fact I checked that and it was ticked. I've unticked it and now it says "SuperSU Free".

I appreciate the quick answer. :)
[SuperSU] RandomPooka:
It's worth buying (provided that the purchase still goes to [MENTION=631273]Chainfire[/MENTION] ) .. I don't know if the play store purchase goes to the new owners or him, but I'd hope it goes to him as the original author.
[SuperSU] USBhost:
nvm
[SuperSU] meekrawb:
2.23 seems to be working great on 4.4.4.(slim 8.12.1) on bacon and razor. I'll post back if there is a problem. Thanks CF.
[SuperSU] bountygiver:
flashed beta version on xt1063 lollipop over old SU and now it won't boot now restored /system to pre-root and trying again.

... ok flashed on fresh /system still can't boot. Reverting to stable version

nvm, it works now

ES File explorer root explorer still not working on android L
[SuperSU] radz_:
I dont know what to test...hahaha

But since then i never had issues with Supersu

Latest is working fine in my 4.4.2.. as always
[SuperSU] Scipizoa:
Works like a charm, no issues here.
[SuperSU] Redplanks:
2.23 on hammerhead, Wakelock Detector works without having to switch SELinux to permissive with the mode changer.
[SuperSU] Paschfire:
color control within the Franco kernel FKU pro apk

nexus 5 LRX21O Franco Kernel R68 TWRP recovery v2.8.1.0, FKU color control was working in v2.19 (sorry did not test on v2.22 could not find) but seems to be broken by v2.23, su permissions are granted access and interactive shell is working for other settings IE freq max min control,voltage ect. Just now when you turn off/on the display to apply color profile it does not change colors stay the same but the profile does apply in the settings.

!!!UPDATE!!!

re-flashed v2.19 then v2.23 to test again this time color control is working
[SuperSU] Sc4ryB3ar:
N5 LRX21T sykopompos's frank .99 Rom, running hybrid kernel. Synapse App was working in 2.22, no longer working in 2.23. "No UCI support detected"
[SuperSU] DownbeatClique:
N4 on LRX21T. BusyBox wouldn't install and LMT had limited functionality, both are working fine on v2.23.
[SuperSU] rskyline:
N4 LRX21T. Power Toggles and wake lock detector need to switch the SELinux to permissive to work. Now on .23 is working flawlessly without change that! Thanks [MENTION=631273]Chainfire[/MENTION], you are the man
[SuperSU] bhp090808:
Helium backup is now working. On moto x xt1095
[SuperSU] bwells88:
Flashed on the OnePlus One just fine and running smooth...

CM11-XNPH44S, 4.4.4, latest TWRP and Franco r33... Awesome work... 8)

PS, I bought the SuperSU Pro today... You've always been a staple of every one of my android devices.. Thanks you!
[SuperSU] Blac Caesar:
Nexus 5.. v2.23 running perfectly, no issues to report
[SuperSU] Drifus Dreskeke:
Nexus 9 LRX21Q - v2.23 installed through apk, binaries updated, PRO license recognized.

Converted to system app after 5 minutes locked and manually restarted.

- Power Toggles - GPS toggle is working now;

- MyAndroidTools and Disable Services working flawless.

- ES File Manager 3.23 (test version, not yet on market) 100% functional - already working since v2.22 - just a note;

Thank you sir!
[SuperSU] parag60288:
WHere can i find ES File Manager 3.23 apk?
[SuperSU] Drifus Dreskeke:
It's an internal test, non-public release. I'm not allowed to make it public, I'm afraid. Maybe asking for it through support channel you can get a copy.
[SuperSU] ajack2001my:
Stupid question from a n00b:

I used CFAR to root my Nexus 4 Lollipop and read that it patches the kernel to successfully root the device. Can I now boot into CWM to install the BETA-SuperSU-v2.23.zip file like I previously did with older firmwares?
[SuperSU] Ben36:
Got a link to the support channel?

Sent from my Android 5.0 Nexus 5
[SuperSU] Drifus Dreskeke:
ES File Explorer > Settings > About > Feedback

Send an email trying to detail your reason, device, OS etc.
[SuperSU] Ben36:
Thanks! Have they by any chance gone material yet?

Sent from my Android 5.0 Nexus 5
[SuperSU] vercety974:
With the latest build V3.2.3 available on play store https://play.google.com/store/apps/details?id=com.estrongs.android.pop root is properly working with ES File Explorer :)

+1, Material Design would be great with this marvellous app :p
[SuperSU] alex00006:
hi

In your opinion

in now better use version su for root MM (Example Root Note5 N920C MM)

su2.68 or 2.71?????

Which version of deep sleep better with stock kernel ??
[SuperSU] banciii:
Hello. Is it possible to install 2.71 on N? Since I can't boot into TWRP (3.0.0-0, 3.0.0-1, 3.0.1-0, 3.0.2-0, all stuck at TWRP logo), how can I flash it? The CF autoroot works fine with the 2.70 RC.

Edit: ok, I downloaded the cf autoroot from the official site. Didn't know or see that that one is also 2.71 already, sorry. After some reboots (maybe 3), it booted up and working fine. Thx.
[SuperSU] yanleites:
SuperSU 2.71 and twrp 3.0.0.0 works on Android N. Other versions really stuck on twrp logo. I wrote the dev, and he told me that only after the RELEASE of android N, there will be twrp that supports it.

Use wugfresh to flash twrp 3.0.0.0 and then use sideload from the twrp to flash supersu zip.
[SuperSU] dahawthorne:
[MENTION=3053466]RandomPooka[/MENTION]

"It's worth buying (provided that the purchase still goes to [MENTION=631273]Chainfire[/MENTION] )"

Yes, I completely agree. I have bought it - it's on my N6. And I've got half a dozen other paid-for Chainfire apps. The guy has a great talent.

The N5 is a spare phone which I use for testing and as a backup in case I lose or destroy one of the other phones in the house... :)
[SuperSU] Ja_som:
Or, you don't need TWRP, first time use cf auto root, and when you want to update SuperSU use Chainfires FlashFire app, is it really great app. You don't need custom recovery to flash zips, don't need PC for flash factory images, everything you can flash via FlashFire ;)
[SuperSU] The Analog Kid:
I have BETA-SuperSu-v2.62-3 installed on my Moto X Play 1563 (6.0 Marshmallow) and BusyBox is asking to install it by default in '/su/bin'. Somewhere else, somebody suggests to go on and install there "IF" you got CF's systemless root. Is BusyBox suggesting to install in '/su/bin" actually an indication that I have "CF's systemless root in my device? Is v2.62-3 systemless? Should I go install BusyBox in '/su/bin'? BusyBox path dedicated threads are a tad bit unclear about it, that's why I'm asking here...
[SuperSU] egingell:
It's not probing your system. It's just a hard-coded list of targets.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] iakoboss7:
hello, i installed 2.71 (updated from 2.68), if i install 2.68 again i will have problems? or i can do it?
[SuperSU] corkiejp:
It is better to install BusyBox to '/su/xbin' to not cause conflicts with system apps.
[SuperSU] LoverBoy2415:
I think you can..I Used to switch back to versions from newer to older & viceversa..

2.65 to 2.56 & 2.52 & back to 65 next 68 then 70 then back to 65 then now 71 [emoji12] [emoji6] ..

No Issues for me..

Using CM12.1 :)

Sent from my Nitro
[SuperSU] magnamentis:
if it works like others say fine, should you encounter issues flash the stock boot.img first before re-rooting and best practice is to unroot from withing root app, flash stock kernel (boot.img) and re-root vie 2.68 zip.
[SuperSU] osm0sis:
Worth mentioning my latest busybox installer (1.24.2) will now clean up an old installation in /su/bin before installing to /su/xbin, reversing any breakage from a default Stericson installation. :) :good:

Available in my Odds and Ends thread.
[SuperSU] Zlatty:
I've been away from the thread for some time. Just wondering if the new version (2.71) and the new TWRP (3.0.2) fix the issue with AdAway not working? Or, do you still have to unencrypt the phone to get TWRP to work to make the adaway zip work.

Edit: Install the latest adaway APK from here, flash the systemles zip with flashFire, reboot, apply hosts, reboot. Stay encrypted and TWRP free.
[SuperSU] RandomPooka:
Is this necessary if installing a system root instead of systemless? Or, is that not even an option with the G3?
[SuperSU] iakoboss7:
i am on omnirom right now on my optimus g. i guess after each install of the "rom" the boot.img gets replaced... right?

omnirom is rooted by default, i just install supersu zip via twrp (3.0.2-0) and root works... this is what i use http://xdaforums.com/optimus-g-intl/orig-development/romgeehrcaosp6-009-10-15-t3221743
[SuperSU] osm0sis:
If I'm not mistaken it's necessary if the boot.img needs to be modified in any way, which it does for Marshmallow and above due to the sepolicy changes, system root or not.
[SuperSU] magnamentis:
yes, flashing the rom replaces whatever kernel was there before. just unroot so that you can re-root form scratch. perhaps it works without but as i said, just in case you encounter issues, you can try the easy ways first if you have a working nandroid backup :)
[SuperSU] RandomPooka:
I think the G3 is still stuck on Lollipop with sprint. I'm fairly certain that the ROM I intend to flash on it is L based
[SuperSU] H4X0R46:
What exactly determines whether it chooses to install systemless or system root? I've installed it on many MM roms, and it almost seems random which the installer chooses to do. Either way work perfectly fine, just wondering what qualifies! Thanks chainfire for another awesome root method!
[SuperSU] MrKaon:
I have a question :

Other than updating SuperSU, can I use FladhFire to flash and apply OTA while I'm systemless rooted with custom recover installed?
[SuperSU] Orginator:
[MENTION=631273]Chainfire[/MENTION]

Phone: Samsung Galaxy S6 with 6.0.1

SuperSU: BETA-SuperSU-v2.71-20160331103524

Issue: The app proxydroid doesn't get root (eg. says root first as an error message)

any ideas?

PS other apps like adaway work fine
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=66140836&postcount=5493
[SuperSU] ElementRn:
Search the thread for hard coded?. The app probably wasn't updated to support systemless root.
[SuperSU] Ja_som:
I'm not sure about custom recovery, maybe yes, but if you don't touch your system, you can install OTA, and FlashFire will also root your device again. Look in FlasFire thread, you will get more info about it...

;)
[SuperSU] corkiejp:
On nexus devices FlashFire restores stock boot and recovery before flashing an OTA.

Your system has to be unmodified/untouched for OTA to be applied.

FlashFire can also be used to flash factory images.
[SuperSU] Alxoom33:
When using Flashfire to flash an OTA, which folder do you look in for the OTA .tar file?
[SuperSU] Ch3vr0n:
Unless I'm mistaking they are

1. Located in /system/cache

2. Called update.zip and not a tar file

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] egingell:
It's either /cache or /data/fota or similar. Not anywhere in /system.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1