yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
Well someone releases updates to Stericson's installer on the Play Store, and they paid enough attention to add /su/bin as default and later /su/xbin to the list when systemless root is detected, but not enough attention to make /su/xbin default like it should be for something with as much possible breakage as a busybox installation..

As for apps not detecting busybox, it's a similar issue to apps not detecting systemless root, just not as detrimental; the apps are at fault, likely using a hardcoded path where they should just do a "which busybox" command. You should send the app dev an email.

And to answer your question, there's nothing wrong with using /system/xbin so I wouldn't expect any side-effects, it just means you've modified /system, which some users want to avoid nowadays for OTA/Delta purposes, depending on their ROM.
[SuperSU] gothicVI:
[MENTION=1792279]ivicask[/MENTION] please use spoiler/hide functionality...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] BenPope:
You can apply OTA with busybox installed to system? Or you haven't tried?

Have you tried the widely available alternative methods?
[SuperSU] Ch3vr0n:
Yes and no. You'll need to flash stock system.img first, then apply ota and reinstall busybox. But installing it to system modifies it and voids ota. Precisely why it 'needs' to be installed to /SU/bin or /SU/xbin. But all of that is offtopic, has nothing to do with superSU itself.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] The Analog Kid:
Further reading inside BusyBox installer, tells us it is Denys Vlasenko maintaining BusyBox, and apparently it is Stericson himself compiling and updating the installer. Whatever, thanks to both. Hope they noticed and change the path.

As a side note, I've noticed that BusyBox installer apparently "removes" binary from previous path in order to reinstall it in system/xbin. At least, that's what "Root Checker" app shows, just one path used. On a previous LG G3 D693n, I had this "conflict" of having BusyBox installed in two different paths (because of Kingroot) again as stated by Root Checker.... It brought no issues whatsoever.

As for OTA updates, personally I don't care. Why should I if having a rooted, unwarranted device? Frankly, I don't even know what is "Delta", but I don't think I'm ever gonna need it as well. I like to know things about stuff, but I'm not this kind of hardcore Android user always looking for the latest; just want my device to look and perform as I like; then, if BusyBox in system/xbin does the trick, so be it.

Since we're at the early stages of a brand new "Android way" and therefore must have tools like SuperSU are evolving, such app compatibility "issues" and people's confusion, should not come as a surprise. It's just that the resulting mess is making me miss the previous OS builds joy and easiness. A lot.

BTW, one of the apps not working without BusyBox in system/xbin is the good old "Ninjamorph" (a bit less useful on 6.0), which happens to be of Stericson's creation... and as we know, he's not responding email!...

Thanks and greetings

---------- Post added at 08:44 PM ---------- Previous post was at 08:25 PM ----------

Haven't tried. And there's a good chance I won't. Even if would, I can't with BusyBox installed in system. There you have it. Updates are becoming way too restrictive for my own taste. But as you mention, there are widely available alternative methods for those interested in OTA updates... and they work
[SuperSU] m+a+r+k:
I'm nagging the moderator/developer in the G+ community but he doesn't seem to be listening. I've even pointed him to Chainfire's advise...

He's more interested in ****ting on the app though from latest developments.
[SuperSU] Didgeridoohan:
Towards the end of your log I see this:

I think that's your problem, the installer can't find a clean boot image to patch.
[SuperSU] The Analog Kid:
Yeah there's a trend. Devs are leaving the building. Even some long time trusted apps are not properly up to date even if updated. We should evolve at once and start trying new stuff. Even just for the sake of change. Thankfully, Chainfire's SuperSU remains away from said trend...
[SuperSU] Maxr1998:
My question is not directly related to your post, but I always wondered, what's the difference between calling "which busybox" and then running the executable at that path, and just calling "busybox" (which grabs the location from $PATH as well)?
[SuperSU] pkelly517:
which returns the path to the binary.

#date

Thu May 12 16:49:43 CDT 2016

# which date

/bin/date

If 'date' wasn't in the $PATH, then it would return a

date: command not found

HTH
[SuperSU] Didgeridoohan:
Nope, not the same issue. Nothing like the last warning about not finding a clean backup. In fact, looks like that part of the install went just fine.

Don't know if the last part of your log has anything to do with it (no space):

Hopefully someone with more knowledge can help you out. I've run out of competence in this matter. :)
[SuperSU] ivicask:
Sorry, ment the same general issue that SU doesnt get installed, not that the log is the same.

But dont understand whats the issue, all partitions have plenty of space..
[SuperSU] Didgeridoohan:
Sorry, don't know. You've got some warning about failed mounting in there as well, but like I said hopefully someone with a wee bit more knowledge in this matter can help you out.

Good luck.
[SuperSU] Galactus:
hey guys simple question. Is it possible to have root and encrypted device (S7 Edge) I just want to be able to flash mods and have an encrypted device. Not fussed about TWRP back ups etc. Ideally I'd use FlashFire to flash zips
[SuperSU] osm0sis:
That dd no space thing isn't anything to worry about, it's just the partition getting wiped before write.
[SuperSU] daniel3x:
New SE policy update breaks root

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

I don't know if was already reported here, but there is a new update that comes out yesterday for "security policy updates" in samsung devices, and is breaking root putting the phone in infinity bootloop. Only way to fixit is enter in TWRP and delete all files found in "data/security/spota" and then we can boot but we need to disable auto updates for security policy updates.

Can you look at this issue?

Thanks
[SuperSU] alex00006:
Hi guys

I have N920C MM

I think deep sleep problems in the new version SU 2.72 was excellent and very fluent with kernel stock and the battery life is really better

Tnx a lot Chinfire for all Your efforts

Just GALAXY Note
[SuperSU] durgis:
Not sure about rooting the S7. In general root just allows you to decrypt your data partition by stopping enforcement of encryption. It doesn't decrypt it for you automatically.

Apparently with 2.72 you can disable that as well to continue enforcing encryption through a flag. I think that seems like it should be the default behavior, but you'll probably hear a lot of people argue the other way too.
[SuperSU] wetxxx:
Batter drain for is worse than 2.71. Maybe I check this update on fresh, stock rom

Send by Tapatalk
[SuperSU] ianmacd:
It's possible to have an encrypted, rooted S7 if your device isn't carrier-locked (i.e. with a locked bootloader).

Just use CF Auto Root to root and then use FlashFire to flash whatever you want to install (e.g. Xposed, SuperSU update, etc.) and you'll never need TWRP or have to give up encryption.

Just make sure you don't have a bootloader-locked device.
[SuperSU] Galactus:
Thanks, the issue was that I didn't interpret the TWRP install steps. I thought I HAD TO flash dm verity and disable forced encryption for the phone to boot. Didn't realise that simply flashing SuperSU was enough.

/data is still encrypted, I simply flash mods from the SD card inside TWRP, which is what I was looking for.
[SuperSU] ianmacd:
You don't need to go anywhere near TWRP unless you want a custom recovery on your phone, but that will cost you encryption, because TWRP can't read Samsung's encryption. For the same reason, it will also cost you /data the first time you install it, because TWRP needs to reformat the partition without encryption.

That's why I, myself, went for CF Auto Root and kept stock recovery. Too much effort has gone into configuring my device down to the last detail and, anyway, I don't want to lose encryption. I also don't like the dm-verity hack that TWRP requires. TWRP is great, but there are just too many little compromises required for it on the S7(E). It feels too prone to breakage.

I flash everything with FlashFire from the SD card. I also make back-ups using the same tool. The only disadvantage of FF over TWRP is that you won't be able to get to it when you need it most, i.e. when the device won't boot. But even then, you still have Odin, so you can still recover, albeit less conveniently.
[SuperSU] Galactus:
Hey I don't think you understand. I am rooted AND encrypted with TWRP. I didn't use the dm verity zip. I did the same steps as you regarding FlashFire but I lost root somehow and just went the TWRP way but without full wipe and without flashing dm verity.

Reading the TWRP steps, it does say you can do either one (I read it wrong though). To boot you must root or you flash dm verity. The two mods I've flashed (Xposed, Sound MOD) don't need /data to be readable, just /system
[SuperSU] nicolap8:
Hi all.

Tried installing beta 2.72 on Huawei Y6 SCL-L21 using TWRP, System mode.

Not working.

This is what got:

- the SuperSu app says that there is not su installed

- if an app try to get root the SuperSu app dialog compares and I can select the options I want BUT the daemonsu is not getting this info and

1) the app waits

2) after some time I see another notification that "app xyz got root access" (oh, dont remember the exaxt message but is the usual)

- no app got root access

Then I deleted the SuperSu app (from TWRP) and this is the result:

- no app can detect the root

- in the terminal I can do "su" and get root! But I can't access /data directory.

With "id" command this was reported:

uid=0(root) gid=0(root) context=u:r:rmt_storage:s0

when issued the command "su --context u:r:init:s0" i got access to /data dir and to others that before I can't see.

Tried also to install in systemless mode but without success: maybe there is a version with more logs/feedback...

Any thought? Thanks

N
[SuperSU] grep_i:
http://www.android.gs/root-huawei-y6-one-click-root-solution/

Check the link it will help you solve your problem.
[SuperSU] belek1979:
Please leave encryption off in next builds
[SuperSU] greeneyez15o:
Did it encrypt ur nexus ? Im holding back on flashing it
[SuperSU] drewski_1:
Forced encryption is off. 2.72 on my Pixel C
[SuperSU] belek1979:
Chainfire might set encryption on by default from 2.73
[SuperSU] greeneyez15o:
I wonder if the disableforcedencryption.zip will work after flashing supersu, as of right now i think its only flashed after rom (just in case).
[SuperSU] belek1979:
SuperSU disables force encryption by default. No need fixed zips:

https://www.google.pl/url?sa=t&sour...LV99hmDqzAPYs_vKQ&sig2=Ut2nfvQ3n2S6A0iLrRzgwQ
[SuperSU] topjohnwu:
Is it possible that you wiped the cache partition after the SuperSU zip flashed through the ROM zip?

I spent quite some time figuring out what the SuperSU flashing zip and the systemless root mechanism.

If the data is not available in TWRP(which is the case on HTC 10), it will place the files in cache. Then a script added to the sbin in ramdisk will move and merge the files to data partition after the first reboot.
[SuperSU] ivicask:
I do wipe cache, but before anything else is extracted, and weird things happen, same user flashes rom, some got root working but app is not installed (all SU actions are accepted), some dont get root in any way on for example sprint phone...
[SuperSU] vanessaem:
Hello,

Thread cleaned...

A general message to all. Please stay on topic, stop the arguing and please be respectful towards others.

Regards...
[SuperSU] Godaemon:
Hello i need some help because ive been absent for a while. Currently im on custom 5.1.1 ( NEXUS 5 ) . I want to flash a 6.0.1 Custom Rom so so i dlike to know if i need to go back to stock images before i flash a custom 6.0.1 ROM + Custom Kernel ? Finally do i have to flash SuperSu AFTER or BEFORE flashing the custom Kernel ? Thanks in advance .
[SuperSU] obones:
I just tried that and when I call "cat /data/.supersu", I see this:

BINDSYSTEMXBIN=true

Then I rebooted in download mode and reapplied the CF autoroot file for my S5 mini (5.1.1) with Odin but I must have done something wrong, because /system/xbin does not contain su, it's still located in /su/bin

What have I missed?

I tried getting in the FlashFire beta to be able to flash the 2.72 version from Chainfire website, but I could not find how to do it with Odin v3.10

Any help would be most welcome.
[SuperSU] Captain_Throwback:
Misspelling?
[SuperSU] obones:
Well, there was one in my message (I edited it), but I don't think there is one in the file, it looks exactly like what was typed by Chainfire.

Is the flashing method I used ok?
[SuperSU] egingell:
He means you misspelled "BIND" as "BIN". Is this reflected in your .supersu file?

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] obones:
I believe it is fine in the supersu file, but I may have trouble seeing it, so here is a copy/paste of the transcript sent by Terminal Emulator :

u0_a274@kminilte:/ $ su
root@kminilte:/ # cat /data/.supersu
BINDSYSTEMXBIN=true
root@kminilte:/ #
[SuperSU] Fif_:
You may want to update your bootloader and radio firmware. I think at least one of them has changed for MM on the Nexus 5.

You can download the latest Google firmware, then just flash these two images. No need to flash system, userdata nor cache, although it won't hurt.

You will want to clear userdata before flashing your ROM though.
[SuperSU] beerbaronstatic:
Latest beta seems to be running fine on npd35k on the Nexus 6, Titanium Backup restore is working using the beta version found on the TiBu twitter
[SuperSU] Ja_som:
Agree, I also did not found any issue on my N5X :good:
[SuperSU] ElementRn:
Perfect.

Have a great day?
[SuperSU] RandomPooka:
I see that it is posted with a note saying it can run as a 64 bit system app. My Nexus 6 is a 32 bit device. Can anyone confirm that it's a 32/64 bit app package that will install properly on either?
[SuperSU] egingell:
If it's not, it just won't work. There's literally no harm in trying.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] casonswag:
Link please?
[SuperSU] Ja_som:
http://www.apkmirror.com/apk/titani...nium-backup-7-4-0-test1-android-apk-download/
[SuperSU] RandomPooka:
I was planning on it. Just finished flashing and going through initial setup DP3
[SuperSU] zrilman:
Does SuperSU supports the latest Beta release for android N?
[SuperSU] Abdullaharis:
how can i hide SuperSU App From Launcher

I Already Added Shortcut In Settings

Please Help Me
[SuperSU] haseoxth:
Working flewssly...
[SuperSU] zrilman:
Can you tell me (send me a link) how to root in on Android N?
[SuperSU] spevil07:
[MENTION=6337907]zrilman[/MENTION] What's your phone?

If you're at N flash TWRP Recovery an there you have to flash SuperSU 2.72.

Gesendet von meinem Nexus 6 mit Tapatalk
[SuperSU] zrilman:
Nexus 6P (Android N DP 3)
[SuperSU] spevil07:
If you're at N flash TWRP Recovery with fastboot or try WugFresh Nexus Root Tool.

If TWRP is flashed go to Recovery and flash SuperSU 2.72

Gesendet von meinem Nexus 6 mit Tapatalk
[SuperSU] Spark007.:
Even though SuperSU is getting installed but I am not able to read or write to system using any application (tested AdAway and ES File Explorer) .

Using Nexus 5x with N DP3.
[SuperSU] zrilman:
I tried to flash twrp3.0.1 and 0.2 and the flashing process succeed but when I want to boot into recovery it just displays the twrp boot logo and stays on it :rolleyes:
[SuperSU] junioramboy:
1. Use FX Explorer + Root Add-on then mount system as r/w.

2. For Adaway, flash the systemless version, then install the apk. It should work.
[SuperSU] junioramboy:
Because using any toolkit doesn't do you any good. Learn how to fastboot, pretty easy. Then, fastboot flash TWRP.
[SuperSU] MrKaon:
Why people still using ES [emoji15] let it go man, fx explore + root add-ons
[SuperSU] white7561:
If i was in prerooted rom with systemless or not systemless root.. Can i just flash to replace to newer version? Thx.. I know i can search but wanna makesure :) thx
[SuperSU] lucadalba:
Good morning to all guys!

First of all thank to the dev for his fantastic SuperSU!

With lollipop I could run the SuperSU 2.46 system mode zip from my rom zip (to preroot the rom) without any problem..

Now with Marshmallow and SuperSU 2.72 systemless I can't.

I got failure!

Here some screenshots:

To start the zip I use the following commands:

But, as you can see in the screenshots, the zip fails..

Have you any idea for solve it?

Here is a link: https://mega.nz/#!up1WBTAJ!45QPYeVvSuLm3KB-ZGpJXXHP9SWVq7cXWRrpxP00KLE

When you download and extract it, you can see 2 folders: in normal-su there is the original supersu 2.72 systemless zip and the relative recovery log.

In in-zip-su there is a simulate rom zip with the su zip and commands to start it (as prerooting in rom installation.. but obviously there isn't the rom..) and the relative recovery log.

Please can you look into it and advice me how to solve? I really would appreciate it[emoji4]

Thank you in advance!
[SuperSU] white7561:
I'm just guessing :P.. But.. If it was prerooted rom like stock rooted with mods.. Can u try flashing the stock boot img from ex the rom is samsung stock modded.. That means try to flash stock samsung boot.. And try to reflash the supersu.. Just guessing tho.. Hope it works :)

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

Used to use fx.. Its super duper great.. But now im using solid explorer.. Its solid as well.. But the good thing from fx is it can read large size in text editor.. Coool

---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------

Used to use fx.. Its super duper great.. But now im using solid explorer.. Its solid as well.. But the good thing from fx is it can read large size in text editor.. Coool
[SuperSU] lucadalba:
Sorry but I don't understand.. mostly for the english..

I'm developing a marshmallow rom for Samsung Galaxy S5 SM-G900F.

The kernel I used isn't Samsung stock kernel but the tamirda's PhoeniX Kernel v8 (I obviously got his permission to use it)..

When I have flash the complete rom zip, the rom hasn't been rooted because there was a problem in the updater script.. so I also couldn't see the supersu installation log during the rom installation..

So, after some tentatives (using my in-zip-su zip) I succeed to see the SuperSU installation log. But (as you can say in screenshots) it got me fail.

If I try to install the normal supersu zip it works like a charm.. so I can understand that the failure isn't a SuperSU general problem.. but I got failure only when I try to boot supersu zip from my in-zip-su zip (like prerooting a rom)..

Anyway I don't understand your post.. can you write\correct it with more simple words or edit it refering to this new post..

Because I think I'm good enough at English.. but my english knowledge has anyway a limit[emoji28]

Thank you in advance[emoji4]
[SuperSU] white7561:
Oh in that case if flashing manually works.. That mean maybe the supersu script that the rom makers implement maybe got something error. Maybe some syntax error?
[SuperSU] white7561:
Samsung note 4. Btw.. It should be same right? Thx
[SuperSU] grep_i:
Those are problems with other apps than Supersu can you please post that in appropriate thread.

Also the discussion Adaway/ES explorer not working has been here a couple of times so with a little bit of searching you shouldn't even had to ask this question it has been answered many times.

Everybody has a preference for the file explorer he or she likes the most, let's respect that and don't flame somebody for using one that you dislikes, I myself doesn't like any of the mentioned file explorers but I'm not demanding you to stop using it.

Let's get us back on topic please ?
[SuperSU] lucadalba:
I'm the rom maker.. and I've implemented this code.. I'm writing here because it doesn't work and I don't know what is the error.. I don't think there is a syntax error in updater-script.. because similar commands works in lollipop..

Here are the code I'have used:

Maybe in marshmallow (or with supersu systemless) changes something..

But I don't know how to solve.. I'm posting here for this problem..

In the previous link I've posted you can found my zip and complete recovery log..

Anyway thank you in advance for the help and the attenction[emoji4]

Inviato dal mio SM-G900F utilizzando Tapatalk
[SuperSU] MrKaon:
Why are you quoting me :eek: Did I ask a question ?
[SuperSU] grep_i:
Yes you asked why people are still using es explorer and suggested your own favorite FX explorer[emoji4]
[SuperSU] fmc000:
What do you use to compress the kernel? SuperSU can uncompress only gzipped images if I remember correctly.
[SuperSU] white7561:
Why? I flash the supersu systemless on stock mm with no problems.. Boots fine.. Supersu fine.. I thought only xposed need to be different version
[SuperSU] lucadalba:
I don't know.. the kernel is not mine.. but if I root normally the rom (for normally I mean I flash the SuperSU zip separately.. and not starting it from my rom zip, like I would to do..) it works fine and root the rom..

But if I try to start it from my installation rom zip, it fail.. this is the problem
[SuperSU] grep_i:
My bad thought I was in Xposed thread although I wrote Supersu
[SuperSU] white7561:
Stock.. And cm should be same right.. I flash systemless on stock mm with no prob btw
[SuperSU] grep_i:
Stock and cm are very different but the answer to your initial question is yes you should be able to update the easy way just flash newer version
[SuperSU] white7561:
Thx :)
[SuperSU] junioramboy:
The guy asked in good faith, we answer in good faith. There's nothing wrong, no policing necessary. No one is above the other.
[SuperSU] Spark007.:
Lol, looks like I tested the wrong apps. :p

FX file explorer is working totally fine with root.

Thanks.
[SuperSU] shoey63:
Aaand, you can use it to set r/w permissions to external sd card.
[SuperSU] zrilman:
I've used fastboot with Android SDK and that's what I've got.
[SuperSU] ohad129:
Working for me on nexus 6 with latest beta N
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

Just flashed v2.74 on my HTC 10 (currently rooted with 2.72). I have a .supersu file with KEEPVERITY and KEEPFORCEENCRYPT flags in /data. The installer seemed to restore my stock boot.img fine, but when it went to backup the ramdisk files, sukernel threw this error:

Saving to [/sutmp/ramdisk] ...

- Creating ramdisk backup
invalid address or address of corrupt block 0x55796d8620 passed to dlfree
Segmentation fault
--- Failure, aborting

Any idea what could be going on? Full recovery log is attached, in case there's some other info that would be helpful. Thanks!
[SuperSU] drewski_1:
i'm not the dev, but these are lines from a working updater-script that installed systemless supersu. BadBoyz stock, rooted MM ROM for my N7-deb

ui_print(">>> Installing busybox");
ui_print("");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
symlink("/system/xbin/busybox", "/system/bin/busybox");
ui_print("");
ui_print(">>> Installing Systemless SuperSU...");
ui_print("");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
[SuperSU] Chainfire:
Thanks, I'll investigate, fix, and upload a new version. Will probably keep the same version number, though.
[SuperSU] :
Running supersu on the latest n preview but some apps don't seem to see that I have root, even after I've already granted it to them, why might that be?