yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ch3vr0n:
Looks like he already did, or te IP flags worked. The knockoff app is no longer listed on the play store!!!

https://play.google.com/store/apps/developer?id=nxlab

No "Superuser SU" :)
[SuperSU] PhrostB:
Wow I can't believe I didn't think about that... so is there any way to get CM12 to update using CyanDelta without running into errors?
[SuperSU] mmonaghan34:
No, not possible unless you use twrp and use a openrecoveryscript to flash the updated CM, then flash SuperSU. As CM has its own root management, every time you update it replaces the su binary which SuperSU doesn't work with unless it replaces the binary with its own.
[SuperSU] PhrostB:
But what if I completely Uninstaller super su and use the built in cm root? Then is it possible?
[SuperSU] Badgerkiller:
It didn't work, really? If nobody tell me... Do you confirm or you say that because I'm not recognized contributor :confused:. FYI I used [MENTION=4544860]osm0sis[/MENTION] tool and compared hash for every files in ramdisk and replaced only files needed.:eek:
[SuperSU] GROGG88:
I cannot speak for anyone else's, but here is one I just whipped out. It's untested (I don't use systemless), but you can try it.
[SuperSU] BullHorn7:
Just flashed the latest 6.0 and rooted with the systemless on an encrypted phone. So far so good. I'll be sure to come back and whine a lot if something goes wrong.
[SuperSU] stangri:
Sorry, can't tell you which one I've downloaded because I forgot. I just searched this and the official announcement threads for attached files and found one for hammerhead-MRA58N.
[SuperSU] Link_of_Hyrule:
Has anyone made an update to the systemless root for mra58n Fugu yet? Much appreciated if anyone has it thanks :)
[SuperSU] Alxoom33:
I used the Shamu Systemless Boot.image MRA58K from [MENTION=631273]Chainfire[/MENTION]. My Nexus 6 is encrypted.
[SuperSU] Badgerkiller:
Try this I used mra58k systemless to replace proper files in original mra58n for your Fugu.;)

I'm not a recognized contributor so if you are like [MENTION=4290287]Dr0idgroove[/MENTION] and don't trust me, please wait :rolleyes:
[SuperSU] kostur:
Strange version of SuperSU

I have successfully installed systemless root on my Nexus 5 and root is fully functional. But when I open SuperSU app it's show me v2.46 instead v2.56. Is it normal?
[SuperSU] veesix:
Guys dumb question: I'm about to flash Marshmallow on my Nexus 6. I plan to root with the systemless boot image, will I be able to decrypt too?

edit: Found my answer, I should be able to.
[SuperSU] TR2N:
Hi guys,

I have wiped my Nexus 6 today and installed the MRA58R images. I flashed the systemless root boot image someone provided in this thread (thank you!!!) and SuperSU 2.56 - works great so far.

In the case an OTA update comes up... I have also installed Busybox Pro and did modifications to the Build.prop. To "restore" stock system I have to uninstall Busybox from within the app, restore the original Build.prop and delete the SuperSU app from system? Is this the way to go, did I understood correctly?

Thank you and kindly regards

Nico
[SuperSU] accolon.:
Your boot.img for systemless root on Nexus 5 MRA58N from here works fine.

[MENTION=535343]all[/MENTION]: Simply replacing the files sepolicy, file_contexts, init.rc and init.environ.rc in the ramdisk with those from a working systemless-root boot.img for your device should be enough. When in doubt, diff those files against those from the boot.imgs provided by Chainfire to see what changes are necessary (as explained in the WIP thread).
[SuperSU] efrant:
No, that won't work. You will need to flash the stock boot image and the stock system image. Only then will you be able to apply the OTA update.
[SuperSU] TR2N:
Okay, thank you. But where is now the advantage of systemless root?
[SuperSU] efrant:
To be honest, I don't really see any big advantages on Nexus devices because they have full stock images available, and it is trivial to return to stock.

In order to use the advantages of system-less root, you can't make modifications to /system. For example, if you install busybox, you need to install it in /su/bin not /system/bin. There can be no changes to /system.
[SuperSU] Enddo:
Chainfire says that he hasn't tested this experimental SuperSU with encrypted devices, but has anyone else? I'm curious if I can root my Nexus 6P with default encryption enabled

edit - I just flashed it and so far so good :)
[SuperSU] TR2N:
But the SuperSU app for systemless root is also installed to system partition. So there are changes made to system. Hmm, thinking about to reflash and use the old way...
[SuperSU] efrant:
No, the SuperSU app is installed in /data, not in /system.
[SuperSU] Badgerkiller:
Ahhh thx for confirmation, this is what I did and I found 4 files to replace as Chainfire said in the WIP thread. I done checksum verifications before read his advice ;)
[SuperSU] JaCh0o:
Still impossible boot/erase/flash/format commands of fastboot are availible after unlocking oem.
[SuperSU] GROGG88:
The only advantage is root checking apps can be used (though that may not last). As long as custom boot and recovery are necessary there is no major advantage.
[SuperSU] TR2N:
Thank you very much for your explanation!

Is there a way to uninstall SuperSU for systemless root?
[SuperSU] USBhost:
yes flash stock boot.img
[SuperSU] TR2N:
And the app?
[SuperSU] GROGG88:
You will need to re-flash the system image to return to stock.
[SuperSU] bflmpsvz:
As you wished posting here details about previously reported problem (install binaries fail on CM11);

Device: Sony Xperia P (LT22i nypon)

Android version: 4.4.4 KK

ROM version: CM11-20141006-UNOFFICIAL-nypon

Kernel version: 3.0.101_by_Munjeni_and_XperiaSTE-gf801e64-dirty

AndroidBuilder@LinuxHost #1

Tue Oct 07 01:11:44 EST 2014

Recovery version: TWRP 2.8.0.0

ROM dl link: cm11.0-68-nypon.zip

ROM thread on Xda: http://xdaforums.com/xperia-u/p-development/rom-cyanogenmod-11-0-t2626639

Kernel only image: boot.img

wanting more info let me know :cowboy:
[SuperSU] Chainfire:
It would have been nice had you included details of the actual problem. I need to keep track of a lot of users and their issues.

First flash latest SuperSU, then open SuperSU after Android has booted up, allow it to update the binaries, if it still fails, do a full adb logcat and post that
[SuperSU] bflmpsvz:
The details: App is installed but binaries won't install in normal mode.

Ok trying that and have 2 questions: 1) what do U mean by flash latest SuperSU, do I need that? Pls. giveme link to flashable file

2) how do I full adb logcat, never done it.

Thank U!
[SuperSU] adeich:
Chainfire,

Do familiar phone SGSIII, android 4.4.4 CM11

All beta version 2.04 is asked to update a binary file in the status bar # sign, even if the update via TWRP.

There is a program - the balance of the widget (https://play.google.com/store/apps/details?id=fahrbot.apps.ussd.widget.pro&feature=search_result#?t=W251bGwsMSwxLDEsImZhaHJib3QuYXBwcy51c3NkLndpZGdldC5wcm8iXQ), the phone is switched on and off she checked the network for a couple of seconds. After installing version 2.12 or 2.13 phone hangs when updating a binary file, only helps pull the battery
[SuperSU] sndrdg:
Hi - my apologies for the delay - On extended holiday. I have solved my problem - No logcats though - so my solution may be less than satisfactory to you - sorry. Quick rehash, unable to bring up SuperSu 'Application' or 'Log' tabs - displays spinning circle (settings tab displays correctly). Has occurred 2.07 thru 2.13. SuperSu working properly in all other ways - just cant access/manage existing apps through GUI tab.

Supposed 4.3 MK2 ROM obtained here.

http://xdaforums.com/showthread.php?p=48865057

This alleged stock ROM & kernel was supposedly DeKnoxed (observation: Selinux was reported as Enforcing, I could never get it to go Permissive and stay 'Permissive' - for more than a split second before it appeared to revert back to 'Enforcing').

For other reasons - I also happened to need init.d support - and this stock kernel - was lacking this too. So I searched for Sprint sgs4 4.3 MK2 kernel - and found one by [MENTION=1354510]Unknownforce[/MENTION] (thanks) here. (thanks [MENTION=3616556]jstntp[/MENTION])

http://xdaforums.com/showthread.php?p=48885413

After flashing this new kernel - the spinning circle behavior stopped. (Observation: Selinux now permanently shows 'Permissive'. Don't really understand Selinux, Knox, -or- whether this was related to my problem - just know flashing this kernel - was the single thing that worked)

Highest regards for spending so much time with me - sorry for the less than satisfying fix.

Doug
[SuperSU] bflmpsvz:
So I flashed SuperSu vie zipfile and this time the binaries are installed but I have additional problems. Some appz don't seem to start (particularly Root Call Blocker telephony service). Root access to the app is granted. Any idea?
[SuperSU] adeich:
Now the next problem.

After disabling the option "Re-authentication", the application after the update not seek re-root-access, whether incorporated or not the option "Auto-refresh apps and logs tab"
[SuperSU] tetakpatak:
Could it be, that you have disabled root access in the developer options of your CM11?

tetakpatalked from Nexus 7 flo
[SuperSU] DesertEagleSlim:
I'm running 2.13 and since a few releases back I've noticed that no apps show in the configured apps list. Any ideas why? Sorry for the dumb question in advance.
[SuperSU] sndrdg:
Having had a similar problem - I'd be interested in knowing your phone type, what ROM and kernel you were running?

See my post if you're interested :

http://xdaforums.com/showthread.php?p=55944548

Doug
[SuperSU] DesertEagleSlim:
Have i337 running Nameless rom and Alucard 2.7.2 kernel. I was flashing the SU updates seperate but he includes 2.13 in nightlies now.
[SuperSU] adeich:
No. Root access is enabled. And I did not CM11, usual android 4.2
[SuperSU] shekinahsmoke:
delete ///
[SuperSU] kmcphee:
No problems
[SuperSU] dorimanx:
0 problems, thanks chainfire, you are the best :)

Sending all my users to update to 2.13 asap :)

Big thanks for hard work.

Sent from my LG-D802
[SuperSU] Smultie:
Not sure if this has been answered yet, but I can tell by personal experience that Lux makes SuperSu unable to register you pressing Grant or Deny.

Temporarily disabling Lux fixed the problem for me.

Thanks for the tip!
[SuperSU] camerona:
Try disabling tap jacking in super su settings
[SuperSU] Ben36:
Hi. New L preview is out and unfortunately root does not work. Says no binary installed /unable to install... Just letting you know
[SuperSU] tetakpatak:
I think you're probably doing something wrong. It works perfectly fine on L here.

tetakpatalked from Nexus 7 flo
[SuperSU] Ben36:
On today's release?
[SuperSU] TR2N:
Okay, thank you!!
[SuperSU] efrant:
The app is installed in /data if you used "system-less". To remove root, you would need to flash the stock boot image and uninstall the app. That should do it.
[SuperSU] elreydenj:
I know. I'm using it. However someone should create a new one off of the newest update. There may be slight differences in the ramdisk. I see updated systemless boot img popping up for other device updates but none for the 6P. I'm sure someone has done it for the 6P and they should share it here.
[SuperSU] Link_of_Hyrule:
Ok I'll give it a go thanks a lot. Can you explain in detail how you extract the files and such to do this to the images? Is it possible to do it on Windows 10?
[SuperSU] Tzfardaya:
Looks like there are differences... Haven't dug in to see what they are yet, but a diff check (and md5sum) show differences... I'll keep looking.
[SuperSU] elreydenj:
There are. Someone should create one for MDB08M for the Nexus 6P. I know there would be a lot of thankful 6P owners.
[SuperSU] GROGG88:
You could be the one everyone thanks...
[SuperSU] Tzfardaya:
I'm looking into it... It'll be my first attempt. ;)
[SuperSU] elreydenj:
Would love to be that guy. I have a low level understanding and know it isn't difficult. However, there are more qualified members than I. Trust me, I don't mind helping out but I don't have a complete grasp of it.
[SuperSU] Ketawa:
Someone already has. Check the "[GUIDE] Unlock/Root/Flash for Nexus 6P" thread in the Nexus 6P forum.
[SuperSU] elreydenj:
Thank you! Much appreciated.
[SuperSU] SimoxTav:
Hi Grogg, I tried with your boot image on my N72013 but after I'm experiencing issue both with and without installing superSU 2.52. The device stays softbricked on the animated logo.

The N5 modified boot image instead works like a charm. Both were clean installs through NRT 2.0.5 (cause 2.0.6 is still bugged). It seems I'm not alone with this issue:

LINK

Thanks :)
[SuperSU] GROGG88:
No issues here mate.
[SuperSU] shoey63:
So how about this approach? Disable dm-verity and use patched sepolicy in the RECOVERY.img. Then OTA updates can occur, regardless of /system modifications.
[SuperSU] Captain_Throwback:
Block-based OTAs verify the checksum of the entire system block device in order to confirm whether the update can be applied. If the checksum of /system doesn't match what's expected, the OTA won't apply. I'm not sure how your suggestion changes that. You wouldn't want to try and apply a block-based OTA to a modified system - it would just result in complete corruption (though I'm not sure you'd even be able to force it to apply).
[SuperSU] SimoxTav:
Well, indeed it worked on my fourth try :D (no idea why this time everything went smooth). My apologies for doubting :P
[SuperSU] shoey63:
My assumption is that the modified recovery would allow the block based OTA to just overwrite the system files, without verification. I'll try it and see if it works (on Sony's z3 MM concept rom)
[SuperSU] Captain_Throwback:
Maybe you should read this . . . https://source.android.com/devices/tech/ota/block.html
[SuperSU] vaindil:
When my phone boots, I get a message saying the following:

This is a Nexus 6P (angler), I'm trying the systemless root. I followed the instructions--clean flash of system.img, flash boot.img from the zip file on the first page, flash SuperSU 2.56 zip. TWRP is v2.8.7.2, and I rebooted the bootloader after flashing each of the .img files.

I do have a TWRP backup, so I'm fine for now, but I'd love to fix this. No errors are thrown inside TWRP, only at boot. The error pops up on the main screen after booting (my home screen is underneath it).
[SuperSU] steviemch:
This error typically occurs if you haven't manually updated the vendor img through Fastboot. There's actually a flashable zip somewhere on the N6 forums to make the process a bit easier.

steviemch
[SuperSU] vaindil:
I have the factory image downloaded, do I need to just fastboot flash vendor vendor.img ?
[SuperSU] steviemch:
Yep, I also found the flashable zip post here

http://xdaforums.com/showthread.php?p=63831294

steviemch
[SuperSU] vaindil:
Perfect, flashed that and the error is gone. Thank you!
[SuperSU] jockovonred:
Does any of this discussion regarding systemless apply to any thing other than the new Nexus 5/6 devices?

It seems most of the discussion now involves 2.56 beta for Nexus.
[SuperSU] stevetrooper:
Could you create one for shamu mra58r?
[SuperSU] osm0sis:
It's a patch still, but instead of patching files it patches the entire system block. So overwriting with mismatched contents still isn't something that could be done.

You bring up an interesting concept though, I wonder if there are any files identifiers in there so that, if someone could get acquainted with the format, perhaps it could be split or decompiled from the .dat into file-specific patches and things could go back to being only a concern if it needs to modify a system file you've changed.
[SuperSU] Wyneg:
Using SuperSU-v2.56 in Moto G XT1040 with Lollipop 5.1 retail Brazil (Using Xposed Framework too). All OK until now ;)

Thanks for your work!
[SuperSU] Onebryteday:
+1 on this request. Or point me to a link of how to customize the boot image.

Cheers!
[SuperSU] vt0r:
I already posted one. Check the link in my signature and grab the stock systemless image for MRA58R.

EDIT FOR THE LAZY: https://androidfilehost.com/?fid=24269982086994468
[SuperSU] rczrider:
Did you ever try this? Just got my NP (fugu) today and let it update...including the MRA58N update which, apparently, is so new that it's not supported by NRT?

I've only gotten so far as to unlock the bootloader, but I'm not entirely sure what to do to root, given the update. Love to know if this worked for you and if so, what you did, exactly.

TIA!
[SuperSU] Link_of_Hyrule:
Yeah it seems to work fine so far.
[SuperSU] EvanVanVan:
Are we waiting for a new boot img for the latest nexus 6p -m factoryimage or will the most current posted for -k work with it?

Thanks
[SuperSU] Vadzhik:
Tell me pleas, when will be boot image MRA58V systemless root for razor (flo)?

Thank You!
[SuperSU] stevetrooper:
Thanks, but I am not using the systemless root option.
[SuperSU] Badgerkiller:
Sorry for my late response :(

Primary all credits goes to [MENTION=4544860]osm0sis[/MENTION] and [MENTION=631273]Chainfire[/MENTION]

- D/L osm0sis tool Android Image Kitchen

- Retrieve the old systemless kernel provided by Chainfire here

- Get the original boot.img from your version (factory images)

Extract the modified kernel (boot.img) into Android Image Kitchen folder :

Drag and drop boot.img into "unpackimg.bat"

Go to the folder ramdisk and keep these files :

Move it into another folder (on your desktop for exemple).

Clean your working folder with the batch "cleanup.bat"

Now we'll extract the original unmodified kernel boot.img from the factory images.

Put it into your working folder as the first step.

Drag and drop boot.img into "unpackimg.bat"

Move and replace your 4 files extracted before (file_contexts ; init.environ.rc ; init.rc ; sepolicy) into the ramdisk folder.

It's time to repack your modified kernel => execute "repackimg.bat", image-new.img will be created.

Delete the original boot.img and rename the file image-new.img to boot.img

It's done :victory:

Sorry for my bad english I hope you'll understand ;)

Edit : if you don't use systemless feature, follow the same instructions but keep "sepolicy" only.
[SuperSU] Alxoom33:
Use the uninstall Root function in the SuperSu app.
[SuperSU] Link_of_Hyrule:
It's not out yet but could these same files be used to make a systemless root for the Android 6.0 for the OnePlus One once it's out or are they device specific?
[SuperSU] Badgerkiller:
You can't use same files but all files could be adapted for O+O except patched sepolicy provided by Chainfire.

For the meantime there is no tool to extract kernel and repack easily or I'm not aware about it.
[SuperSU] Link_of_Hyrule:
It would be awesome if someone just made a tool that did all the steps for you so you just put the new boot.img and it injects the files into it.
[SuperSU] Starphish:
Try this thread... http://xdaforums.com/nexus-7-2013/development/rom-stock-5-1-1-lmy48i-t3175835
[SuperSU] GROGG88:
Relying on tools for simple edits is not the best approach. Learn what and how and you will not have to rely on others.
[SuperSU] GROGG88:
This is the last one I am posting. Others need to learn to fish...
[SuperSU] GROGG88:
sepolicy can be retrieved manually. Just refer to the WIP

Then simply extract sepolicy from the boot.img of that rom and copy to the boot.img of 6.0 when available...
[SuperSU] Link_of_Hyrule:
Ok thanks for your help I'm ready for next time there is an update :)
[SuperSU] elreydenj:
The current works but there is one in the 6P index thread under general for M build.
[SuperSU] ashyx:
There is its called SuperR kitchen.
[SuperSU] psychomaniac189:
i did everything here on the bottom and i still have 2.46 why? http://androiding.how/root-marshmallow-supersu-2-50-selinux-enforcing/
[SuperSU] embql:
I can for the life of me not install BusyBox to any other paths than system/bin or system/xbin. I've tried almost all possibilities of writing /su/bin/ with slashes, no slashes, and in between. Any help for a frustated being here? :( Root is confirmed.
[SuperSU] JsChiSurf:
If you're using Stericson's BusyBox, I found only the PRO version would write to a folder outside of /system.
[SuperSU] embql:
Alright, better donate to that guy... Thanks for pointing this out, info was nowhere to be found otherwise!

Now i only have a lot of BB files with 0.00b size, I hope that in the future it doesn't interfere with the systemless root - we'll see, otherwise it's time to begin from scratch again.. thanks!
[SuperSU] osm0sis:
And even then it's buggy about it. ;)
[SuperSU] JsChiSurf:
Yes, I referenced this issue in this thread a week or so ago, but other than that, I'm not sure it had been brought to light, especially considering systemless root is relatively new.

If by chance you have a system image available, just flash back over top your current system to restore to stock w/o starting completely from scratch. I had to do the same thing after the free version of busybox wrote to /system/xbin despite me specifying /su/bin.
[SuperSU] naveen52640:
Marshmallow rooting
[SuperSU] embql:
Yeah, I found it, interesting read.

Though as shoey63 concludes, editing build props, using Xposed, AdAway etc afterwards, breaks the goal of a non-modified /system/ folder anyway, so there's that.

Exactly same problem I ran into with BusyBox.

Since I'm/we're using NRT on 'Nexii', yes, it's fairly quick to flash new updates/images and get it set up again. Thanks a bunch for clarification.
[SuperSU] Badgerkiller:
Thanks to clarify :good:

We have to "adb shell su -c "supolicy --file...." the future "sepolicy" file 6.0 put in a temp folder on a rooted Lollipop device right?
[SuperSU] GROGG88:
You can use adb to pull it, or extract from a recovery boot backup.
[SuperSU] Badgerkiller:
It's not clear :(

Every sepolicy is different for each device so if not available for Marshmallow we have to create one 6.0 compliant from 5.x or 4.4x rooted system. This is what I understood no?
[SuperSU] GROGG88:
Yes, from 4.4.4.
[SuperSU] goose2600:
Systemless root works flawless for me on Nexus Player with Marshmallow latest build (MRA58N)!
[SuperSU] ratatella:
Ok, so after installing MM 6.0 ROM on my GPE converted htc one m8, I did the systemless root and flashed back stock recovery (still can "fastboot boot custom-recovery.img" for nandroid backup/restore) so I should be able to receive and install future OTA.

Now I'm curious what the exact way would be to unroot this systemless root.. some people talked about it in this thread a bit but still missing an exact "tutorial" on how to do so..

Could somebody tell me if this is the right way and order to do so?

1. Uninstall SuperSU v2.56

2. Remove /data/su.img (or will this be removed when uninstalling SuperSU v2.56 app?).

3. Remove folder or content in /su (or will this be removed when uninstalling SuperSU v2.56 app?).

4. Restore boot.img from before systemless root (by booting into TWRP via "fastboot boot twrp.img", select the nandroid backup from before systemless root and only tick the boot to be restored).

Will you be back to the state of before systemless rooting or still missing something?
[SuperSU] ashyx:
2. Is only an image, can be removed, but wouldn't matter if it wasn't.

3. Not required, it doesn't exist.

All others are correct.
[SuperSU] ratatella:
#3. does exist.

I read somebody mentioning it here in this thread, I checked with root explorer and it's on my phone.

Maybe it'll get removed when uninstalling the SuperSU app?
[SuperSU] c3k:
su.img content is mounted in /su by the modified boot.img

so when you restore original boot no longer exists
[SuperSU] vacsed:
why only 4.4.4? or do you mean any system above 4.4.4?

CF mentions 4.4+ so I guess 5.x and 6.0 should also work to update sepolicy?
[SuperSU] ashyx:
Grogg actually said from 4.4.4.
[SuperSU] vacsed:
I took what he said as "create one ... from 4.4.4", not "from 4.4.4 and above". There is a minor but important difference between those two.

Was just wondering if there might be compatibility problems with supolicy with Android version 5.x or 6.x and therefore you have to use 4.4.4. Just wanted to be sure before I patch sepolicy myself.