yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
Some toybox commands are still broken (IMHO) or incomplete. Some examples (obviously not complete):

mount (usable, obviously, but still broken. "-o rw,remount" and "-o remount,rw" should both work the same instead of one throwing an error)

md5sum (no -c option)

xargs (the -r option isn't currently available)

patch (can't specify original file and patch file on the command line)

Terminal and scripting use. Mostly terminal use. For scripting TWRP already uses busybox and in the os proper I try to stick to the default available command. So mainly a convenience thing. There was a period of time when I deleted the toybox symlink for mount to force the use of the busybox one in order to have my file manager be able to mount /system rw, but that was eventually fixed.

Also TWRP and Android use different shells. Most of the shell script commands function the same, but there are some differences. Busybox can provide a shell to test with (this caught me up once).

Toybox is getting better, but it's not there yet (IMO)

Just find a good busybox implementation. I recommend osm0sis' ?

Speaking of which I've been playing with xbin for the past couple of hours. So anything in /system/xbin is copied to /sbin/supersu/xbin_bind at boot. In effect merging the contents of the 2 directories, with /system/xbin taking precedence if 2 files have the same name. Delete a file, that exists in /system/xbin, it will be restored on a reboot.

That's all fine, once I understand it I can deal with it. The funny thing is that it appears that "BINDSYSTEMXBIN=true" isn't needed. I'm getting the same results both with and without it. (Yes I remembered to reflash supersu when changing it).

As far as locating /data/adb/su I found a way that works (when /data is available).

. . .
target=$(find /data -name supersu_is_here -print0|xargs -r0 dirname)
if [ -e "$target" ]
then
target=${target}/xbin_bind
else
. . .

TWRP uses busybox so the -r works for xargs

(Note [MENTION=4544860]osm0sis[/MENTION] - used the above to modify your busybox installer. Inserted following line 134 of update-binary. Worked fine)
[SuperSU] Ibuprophen:
I'm not sure [MENTION=631273]Chainfire[/MENTION] if this is tied into the latest SuperSU v2.82 SR2...

My device is a Verizon Galaxy S3 (SCH-I535) with CM13 and the Latest TWRP.

The flash went well without an issue and my device seems to be working very well but, there's just 1 thing that started happening after the install.

When I'm using either/or the ES File Explorer Pro and the Total Commander, and I attempt to access something on the External MicroSD card, primarily archives but, other files as well, i get those popup screens for permission to access the External Storage.

Those requests are typically done when initially performing actions on the External Storage and then it's good to go but, it is becoming more frequent and shouldn't be. Basically those are typically a one time deal and it's good to go.

So I can't state for sure if it's tied into the latest Service Release but, wanted to post this in case maybe someone else may be experiencing this too.

Thank you ALL for your time and understanding! :)

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] quincho54:
Interesting. I observed it too. But I thought it was Rom related and flashed the Rom again. But the request of permission for external storage and USB are still there.

I'm on a Note 4, Costume Rom MM 6.0.1
[SuperSU] shaggyskunk:
Just quickly read your post - and one thing that caught my attention was ES Explorer... No idea if it's an issue - But....

https://xdaforums.com/showthread.php?p=67764418

From Down the Rabbit Hole by:

My SM-G930W8 ??
[SuperSU] Ibuprophen:
Thank you for your response!

The post referred to another post (LOL!) and that post, though it did refer to the Samsung and ES File Explorer but, it was regarding the stock Firmware and Knox too.

I don't have the stock Firmware nor Knox (THANKFULLY!).

I appreciate your input definitely! :thumbup:

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] r1l_Alex_™:
[MENTION=631273]Chainfire[/MENTION]

Noticed the External SD issues reported a few times on multiple threads here and there. Has anyone got with you on testing?

I have both Gt-9205 and SGH-m819 devices running current 7.1.2 Lineage bases showing the reported "Mount/Unmounted" External SD and or "Not Visible”

On boot, after device unlock, notification showing ExternalSD is mounted as portable. Inbuilt file manager sees it but as stated FileBrowsers like RE show the following

/mnt/meda_rw (visible)

/Storage missing external

Both Sr1 and Sr2 282 Systemless Variants on clean flashed Samsung Devices

Let me know if you need me to test. I'm working on scope data now.
[SuperSU] Wolfcity:
Seems to be a Samsung thingy... ?
[SuperSU] shaggyskunk:
Have a look at this post from Chainfire:

https://plus.google.com/+Chainfire/posts/N6EARb8LF3d

And just search this Thread for ES Explorer and you'll get the picture.

From Down the Rabbit Hole by:

My SM-G930W8 ??
[SuperSU] warmanz:
downloaded the latest supersu from post #1 still get corrupted file while test with winrar, is it okay to flash it?
[SuperSU] jcmm11:
Tested with rar app on Android. Showing 4 errors, all having to do with NTFS ACL extra fields.

You can ignore these errors (for starters we're not using NTFS). They're false positives.

Testing using zarchiver shows no errors.

I used the zip and it installed fine.

Md5 checksum, if you want to check it, is

f9d743ca6228b9e7ec41634b55887b18
[SuperSU] warmanz:
test it with 7zip and got no error, thanks mate
[SuperSU] Chainfire:
Thanks for the detailed explenation.

xbin_bind isn't cleanup on every boot for performance, but now you're actually not using it as designed. But hey, if it works, it works.

As for the BINDSYSTEMXBIN flag, SuperSU only uses these variables at flash time, not at boot/run time. The flash will create xbin_bind, and at boot the bind will be created purely if the xbin_bind folder exists. So you are right, secondary flash, you don't need it to be set.
[SuperSU] Chainfire:
I didn't notice this before, but it seems all external SD weirdness is on CM/Lineage... that might be a good clue :)
[SuperSU] j1gga84:
I can second that, running Resurrection Remix 5.8.4 on my Samsung Galaxy S5 and Galaxy Tab S tablet..

The strange thing is that I can see external SD when I flash 2.82 zip first and install 2.82 SR1 or SR2 per apk.

When doing it this way external SD is still visible.

It just don't work when I flash SR1 or SR2 zip in recovery.

When I unroot and flash 2.82 zip again, external SD is visible again.

regards
[SuperSU] Chainfire:
I think the attached test version will solve your sdcard issues. Please test and let me know.
[SuperSU] DB126:
Ugh - that it itself it a problem. Hard coded references, parasitic background processes that interfere with other apps, copious outbound communication. Borderline malware.
[SuperSU] r1l_Alex_™:
Initials are clear!

Mounted ExternalSd!

Testing R/Rw mount. Nailed it [MENTION=631273]Chainfire[/MENTION] :good:
[SuperSU] Wolfcity:
I'm using ES pro too since the normal version got full of ads etc. I thought that the pro version isn't that bad.

What file explorer with similar features would you recommend?

And sorry for being offtopic for this post.
[SuperSU] Sr. Zé Alguém:
One with even more features for free: MiXplorer (reading the linked FAQ is a quickstart for learning the app). As a second file manager, if you have some trouble copying/moving files with the first, try Total Commander (find at Play Store).
[SuperSU] jcmm11:
I'll give you 2. One is a dual pane free one. It's the one I use. X-plore

https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore

The next is 14 day trialware. Would probably be my next choice if I wasn't happy with the one I have. Solid Explorer

https://play.google.com/store/apps/details?id=pl.solidexplorer2&hl=en

Another possibility is FX file explorer

https://xdaforums.com/showthread.php?t=1253399

There's lots of options out there. Try them. Do a play store search for file explorer and eliminate anything that's rated less than say 4.4.

ES used to be great - that was a long time ago. It's still riding on its old reputation.
[SuperSU] DB126:
There are many fine public options - I am sure members will chime in with their thoughts. I happen to use Solid Explorer as it meets my needs; FX File Explorer is another good choice. The right feature set is more important than the variety or quantity. Good luck with your search.
[SuperSU] Wolfcity:
Thank you all for your recommendations. Have stuff to test now.;)
[SuperSU] bemanet:
Thanks Chainfire:D the Testversion from 20170810 works perfect and extSD is accessible again...
[SuperSU] quincho54:
The same from my side. So far works o.k..
[SuperSU] balagtaz:
After flashing last beta version can't move files from internal storage to sdcard and I can't even set permissions on it. I used to move files to sdcard before and set permissions.
[SuperSU] martyfender:
Then you might try the test version he released a few post above and report back to him if that solves your problem.
[SuperSU] combat44:
SR2-SuperSU-v2.82-SR2-20170808115921, SuperSU-v2.82-SR2-20170810134923 - no network.

Samsung Galaxy Note 5, Android 7.0, ROM, kernel - stock.
[SuperSU] Chainfire:
Interesting. The only report of this kind so far. Don't see anything obvious in the log :(
[SuperSU] balagtaz:
why there is an sbin? So that's mean I successfully BINDSBIN=true?
[SuperSU] r1l_Alex_™:
I'm trying to reproduce this as well.

Confirmed success on external SD mount. :)

Too add.

Later on I shutdown the device for a restart. Reset logs etc.

On start noticed the same thing

"Cellular Data" disabled.

Showing no SIM mounted.

AirPlane Mode Toggled ON after reboot.

Settings showed CellData ON

I toggled Airplane mode Off and Enabled cell Data.

Sim mounted.

LTE fired up and all was good.

Used the devices for a little while and shut down again.

This time,

Sim mounted but Data was toggled off

Toggled it back on LTE and all was good again.

I'll test further. I'm planning on cleaning up and testing clean flashes again with your 0810 test build.
[SuperSU] osm0sis:
I was testing SBIN SuperSU on my OnePlus 5 last evening, and it seems like even though there's a /sbin/supersu/bin and /sbin/supersu/xbin neither are in the $PATH (I'm talking without xbin_bind), so all that awesome mod functionality from su.img is gone.. :confused::(
[SuperSU] Chainfire:
The question is what to do with this. You weren't really supposed to use /su/bin (or /su/lib) anyway, but yeah, /su/xbin functionality is currently broken.

Modifying the PATH breaks SafetyNet. It would be relatively easy to re-introduce /sbin/supersu/xbin to the path for root shells, but it would still not work for non-root shells. What do you think about that?
[SuperSU] osm0sis:
If it's the best we can do then yeah, absolutely. That's sounding similar to what the custom_ramdisk_patch.sh from Root Switch does if I recall correctly.
[SuperSU] Chainfire:
Attached test version.
[SuperSU] negativman:
And on SR1 and SR2 does not work memory card, it is constantly offered to format it.
[SuperSU] Alxoom33:
If previous SR2 version is installed in a device running N 7.1.1 do we need to use the terminal command again before flashing this version?
[SuperSU] SlimSnoopOS:
Try the zip above.
[SuperSU] jcmm11:
No. /data/.supersu should still exist with the correct entries. You can always look at the contents (simple text file) to verify.
[SuperSU] negativman:
This version works fine. Thank you.:o
[SuperSU] Ibuprophen:
I apologize for not getting back to you sooner [MENTION=631273]Chainfire[/MENTION], that Test version had taken care of the External MicroSD issue for both the ES File Explorer Pro and the Total Commander.

Thank you very much my Friend!

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] r1l_Alex_™:
X2 Confirmed

Too add, the weird issue experienced with radio Automatically toggling itself off on shutdown/restart has vanished. Wierd too, it happened on 3 different Samsung test devices here. All are clear of the anomaly at this time.
[SuperSU] Ibuprophen:
I never had any issues with the radio...

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] bggold:
Had a weird issue when I installed SuperSU 2.82 SR2 latest test version and SUhide v1.07. After installing on my pixel xl v7.1.2, August update and ADB shell commands the phone locked up twice. This is my daily driver.

I noticed this earlier in the week when installing on my test pixel xl with the same configuration.

The first lockup occurs a few mins after booting for the first time after installing suhide and the second time occurs a few mins after the hard reboot from the first lockup. Both times the screen goes black.

After the second hard reboot the phone is fine. Never locks up again.

---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------

I understand that FlashFire v0.57 is not fully supported yet, but I am able to confirm that you can do a normal backup and restore with SuperSU v2.82 SR2 and FlashFire v0.57 with SBIN mode enabled on a pixel xl, August update.

This backup was restored on another pixel with screen lock security disabled.
[SuperSU] Chainfire:
I've had the Pixel XL freeze a couple of times as well. Can't reproduce it, never saw any error. Only happens on the Pixel as far as I know too.

As for FlashFire, the new version is almost ready :)
[SuperSU] j1gga84:
I can confirm that on my Samsung Galaxy S5 and Galaxy Tab S

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[SuperSU] Chainfire:
Please try the attached version and let me know if that fixes the problem.
[SuperSU] ulxerker:
[MENTION=631273]Chainfire[/MENTION] I hided supersu and suhide from the launcher by pressing that volume key combo. but how do I get them back? using the same volume key combo again didn't help.
[SuperSU] nguyentankiet:
Yes, it working now
[SuperSU] ulxerker:
got it ... uninstalled suhide and reflashed it, after that in suhide I first switched suhide to normal and did that volume key combo to unhide supersu.
[SuperSU] Midomad:
Sadly the problem still persist...
[SuperSU] GopalKaul:
[MENTION=631273]Chainfire[/MENTION]? I think that should be the fix. But idk
[SuperSU] bggold:
Thanks for letting me know, if there is anything I can do let me know.
[SuperSU] Draygon:
Is Adaway working for someone, if 2.82 SR2 is installed to SBIN?

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

It is only working in systemless mode, which is overwritten when using above command to use suhide lite.

Help please
[SuperSU] ulxerker:
It's working for me and it's still systemless according to SuperSU app.
[SuperSU] Draygon:
For me, systemless mode is greyed out at Adaway settings, when installing SuperSu to SBIN.

Can I force Systemless + SBIN on install via TWRP?
[SuperSU] ulxerker:
It's greyed out but SuperSU says systemless in settings and adaway works fine for me.
[SuperSU] Draygon:
What is the hosts path you are using at adaway settings?
[SuperSU] ulxerker:
system/etc/hosts
[SuperSU] jcmm11:
Adaway is going to have to make some changes to fully support this. In the meantime you can set it up manually. SYSTEMLESS mode will be greyed out since files won't be where it expects them to be, but it will work.

1) create /sbin/supersu/etc/hosts by either copying a backup of a populated hosts file or just copying the one from /system/etc/hosts

Give it permissions of root:root 644 (rw- r-- r--)

2) create /sbin/supersu/su.d/0000adaway.script with permissions of root:root 755 (rwx r-x r-x). Contents should be

mount -o bind /sbin/supersu/etc/hosts /system/etc/hosts;

reboot and you should be good to go. Adaway will now populate hosts as before, still in a systemless manner, even though that option is grayed out.
[SuperSU] Draygon:
Thanks for the reply, I tried method 1) and it didn't work.

Adaway wants to set a symbolic link when changing the hosts path to /sbin/supersu/etc/hosts and reboots my device.

After that it still is disabled, but I can see a bigger hosts file at the mentioned path. It was created but is not applied.
[SuperSU] ulxerker:
Sounds like you aren't properly rooted or you don't have write access to system, double check that.
[SuperSU] jcmm11:
It's not 2 different methods. You need to do both steps.

Do not change the hosts path, I never said to do that. Leave the path as it is (was). (Should be pointing to /system/etc/hosts). The bind mount mounts the host file in sbin over the top of the host file in system. This has the effect of actually writing to sbin even though it's pointing at system, and is why it's systemless (not actually writing to system).

This is the same as how Adaway currently works in systemless mode. The only real difference is the location of the hosts file (sbin as opposed to su), which is why the script needs to be modified. And since Adaway no longer sees a script in /su/su.d it greys out the systemless option.

---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------

He doesn't need, or want, write access to system if he wants to run in systemless mode.
[SuperSU] bggold:
I just experienced an unexpected restart. The first one since using 2.82 r2. The only change was flashing the most current build from today.

Strange thing was the boot animation was moving very slowly and eventually stalled. Had to hard reset. Came up fine after that.

Pixel XL

7.1.2 August stock

If it occurs again I will plugin and try to get a logcat.

Thanks
[SuperSU] Black Shade:
I just flashed SuperSU after removing Magisk, which was somehow interfering with my partitions. The ROM I'm using - RR 5.8.4 - comes with Magisk pre-installed, removing it helped solving the issues I had. Problem with SuperSU is that my SD Card isn't detected anymore, I can access it from TWRP but not from a file manager. Is this a known issue?
[SuperSU] ktmom:
Yes, it's been reported several times in this thread. Try using the version in this post.
[SuperSU] Black Shade:
Thanks, I tried searching the thread but didn't find the solution, I'm gonna flash it right now
[SuperSU] bggold:
Chainfire. So you know my pixel locked up again. Not a bootloop. I will plug it in tonight and see if I can get you any useful logcat info. I know you said you saw no errors yourself.

That's of course if it will lockup again.

Thanks
[SuperSU] peterlee928:
just fyi - pixelfix supersu working with no problems.

verizon pixel xl

august update stock

rooted via twrp/pixelfix supersu

no custom roms/kernels/add-ons (eg magisk)
[SuperSU] balagtaz:
[MENTION=631273]Chainfire[/MENTION] my permission is broken and system process is not working properly got two option wait and OK :(

After flashing latest beta :(
[SuperSU] m0han:
hi, sorry to be quoting an old post of yours.

i'd tried magisk v13.3 on n2os rom for kenzo. i had trouble getting a particular app to run (reason: busybox failed to install or something). i'd posted elsewhere about it, i think. anyway, i'm running the first release of supersu v2.82 sr2 now. i believe there have been 2 more releases of v2.82 sr2. i can see magisk.img as well as su.img in /data. since i'm now using supersu, can i simply delete magisk.img? is it safe? and, how can i, without wiping everything, remove all remnants of magisk from my device?
[SuperSU] Alxoom33:
I've been getting a few unexpected shutdowns of my Nexus 6, both in standby and on the charger. Boots up ok.

With the Pixel C boot animation slows down, shakes and freezes, every once in a while. Then if I manually reeboot, boots up again.
[SuperSU] karrouma:
This version has patch fixed also
[SuperSU] Chainfire:
To ease configuration and do away with all the echo "...">>/data/.supersu commands, at least on ARM-based devices:

SuperSU Config (AROMA)
[SuperSU] grep_i:
There is an uninstall button in Magisk, if you already used that and still see the magisk.img I guess you can remove it manually.
[SuperSU] m0han:
no magisk now; if i remember right, i did flash the uninstaller. so, let me trying deleting that after a backup.
[SuperSU] Chainfire:
v2.82-SR3

SuperSU v2.82-SR3 has been released. See the release notes here: https://plus.google.com/+Chainfire/posts/JRn87G77gey
[SuperSU] nguyentankiet:
This released inclued simfix yet?
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] My 6P apparantly locked up a couple hours ago too with SR2. Syslog file attached. Don't know if it will help as too much time may have elapsed between the lockup and device shutdown, and me noticing and rebooting the device. Now booting into twrp and flashing SR3
[SuperSU] Chainfire:
It does!
[SuperSU] Chainfire:
Let me know if the same thing happens with SR3. I haven't noticed any lockups yet, but...
[SuperSU] Sr. Zé Alguém:
[MENTION=631273]Chainfire[/MENTION] could you please explain why "As with all SR releases, you are supposed to update them by flashing the ZIP, not by installing the APK" ?

Don't you update the apk contents every time the Zip is updated? Another question (that may eventually answer the previous): Are the binaries included in the apk? If not, where are them retrieved from?
[SuperSU] Chainfire:
Well, you update by flashing the ZIP in TWRP or FlashFire or CF-Auto-Root...

Flashing the ZIP updates the APK and the binaries (and the boot image).

Some people extract the APK from the ZIP, then install the APK in Android. That is *not* what you are supposed to do.
[SuperSU] Sr. Zé Alguém:
Yes, I know. They can also download the apk from a site. My doubt is about the mechanism the app uses when the user chooses the update option... If the binaries are not included with the app, are them retrieved from a server, generated/compiled or what?
[SuperSU] Chainfire:
If the binaries are updated through the APK, the APK uses the versions inside the APK. Nothing is downloaded.
[SuperSU] Sr. Zé Alguém:
Ok... But the apk doesn't include the binary files in their original form as in the zip, nor the size matches, therefore my curiosity about how this is possible. If you can't talk about or want to keep it secret, no problem, I understand ;)
[SuperSU] Chainfire:
I'm not sure what you're looking at, but yes it does. The files in the ZIP\<arch> folder are also present in the ZIP\Common\Superuser.apk\assets folder (with slightly different names).

Either way, I don't understand why you need to know these implementation details.
[SuperSU] Sr. Zé Alguém:
I guess I was blind... They are .png there lol. Sorry my dumb questions.
[SuperSU] Ch3vr0n:
I will. Maybe it's a clue but doing power off & boot into recovery failed (stock one that is. Forgot for a moment that full ota replaced twrp), it was stuck on google logo for 2 min before i gave up. Booting to bootloader then fastboot boot twrp worked and enabled me to flash SR3 that was on the device.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], am I correct by stating that I should be flashing the Aroma Before Flash updating the Stable/SR/Fixes of the SuperSU?

The Aroma thread states what, how and why but, not "When" (the order of flashing them both).

Thank you very much! :)

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] Chainfire:
If you want to configure something outside of the defaults, yes.

Otherwise the SuperSU flash will just use the defaults, or old configuration options of the /data/.supersu file is still present.
[SuperSU] osm0sis:
Linux/Android kernels use the legacy LZ4 compression, set with lz4 -l in the latest builds. That's what any LZ4 ramdisks I've seen use as well, has that changed?
[SuperSU] Chainfire:
The O Developer Preview release on Pixel uses 'normal' lz4... Or at least it succeeds in booting with it recompressed in the new format. Anything else, I don't know.

If it doesn't work with a specific popular kernel that has an edition for one of my test devices, do let me know.