yashsingh1/xdaforums huggingface dataset:
[SuperSU] seanvree:
So I have the Nexus 7 (2013 Wifi (FLO)). and I'm trying to get the modified boot.img for the Nexus 6.0 firmware. I looked on the thread below, but I'm not seeing FLO. Which one should I flash?

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

THanks,
[SuperSU] smelenchuk:
You are looking for 'razor', which is the product name that corresponds with the device name of 'flo'.
[SuperSU] seanvree:
Thanks so much! Got it!
[SuperSU] jblazea50:
Do we flash the zip or the boot.img that's inside the zip?
[SuperSU] smelenchuk:
You'd be using fastboot to flash the boot.img inside the zip to the boot partition, assuming you're following along with the systemless root instructions. If you just want to use 2.52 normally, use this boot image instead.
[SuperSU] jblazea50:
Thanks, that's what I figured. Got confused because inside the zip, there's a boot.img along with another zip file.
[SuperSU] jackdulouz:
Hi,

My Nexus 6 ( running MRA58N) is unable to update the SuperSU binary in TWRP 2.8.7.1. Flashed the systemless root V2.56 beta and the boot.img, which was updated a few pages back. Currently using elementalx kernel.

Please help. Thanks.
[SuperSU] carlese:
Hi guys, hi [MENTION=631273]Chainfire[/MENTION],

today I installed the new android 6.0 MRA58N factory image for my nexus 5, rooted it (used the modified MRA58K boot.img) and installed supersu 2.52 and blu spark kernel. Everything good until i deleted some apps (gmail, webview, youtube and other NON CRITICAL apps, like I ALWAY DO SINCE KITKAT), then rebooted and my phone is stuck at the Google logo, not even the bootanimation shows up.. Tried to reflash the boot.img, wipe cache, wipe data, factory reset but nothing.. The only thing that worked is to reflash the factory image! What am I doing wrong? Happened 2 times in a row so something must be wrong.. Another thing, I can't access TWRP every time, sometimes it skips and boots directly..

Thanks!
[SuperSU] seanvree:
does the process change if we already have TWRP installed with the bootloader unlocked?
[SuperSU] carlese:
I used MRA58K modified boot.img yesterday and first boot went fine, then rebooted and stuck at google logo (see post above), could the boot.img from the older build be the problem?
[SuperSU] r1ky932:
Hi guys,

I have the same problem :(

Any ideas?

Thanks a lot
[SuperSU] jhill110:
I would suggest going through the whole process again (sigh) but don't delete the apps... Freeze one at a time with TiBu and see how it goes.

Reboot after freezing 1 app at a time.
[SuperSU] carlese:
Are you on the latest MRA58N with root? Did you face these problems so far with tibu? Something must be related to the boot image I suppose..
[SuperSU] ittakary:
where did you get this ZIP from? :)
[SuperSU] GROGG88:
I made it.
[SuperSU] shoey63:
Just a thought on the "systemless root " method. What do users do when they achieve root? They immediately modify

/system anyway with adaway, exposed, or change build.prop or whatever.

Also, TWRP doesn't make a clean backup of /system either. It splits it, thus breaking dm-verity verification upon restore.
[SuperSU] fink.nottle:
Instead of the modified MRA58K boot.img, try the modified hammerhead-mra58n-boot.zip posted a couple of pages ago. That worked for me. I had similar issues when i tried to use modified MRA58K boot image with MRA58N.
[SuperSU] carlese:
What kind of issues did you face?
[SuperSU] Krynn!:
Could you do the same for the hammerhead MRA58N boot.img? Thanks!

Ok, so I sat down and figured out how to do it myself... see post #2535 for the N5 MRA58N systemless root download.
[SuperSU] monza1412:
jeez..166 view and only 5 thanks..shame.

thanks man, will test it later
[SuperSU] ittakary:
Worked like charm :) thank you
[SuperSU] osm0sis:
If systemless ends up being the preferred choice going forward then I'm thinking the root community will have to alter the way things operate, e.g. Installing to /su/bin/, or using bind mounts to override/replace system files instead of actually modifying them in place, leaving system untouched whenever possible, etc.
[SuperSU] Captain_Throwback:
For devices that use dm-verity, TWRP leaves system untouched and allows a stock "system image" backup to be performed that will pass the verity check. This image can be restored by the user if an OTA needs to be taken.
[SuperSU] OMJ:
thx...I have it working now...I was following his guide to create the modded boot, but the ROM would boot w/ stock boot.img after flashing SuperSU 2.52
[SuperSU] Captain_Throwback:
Of course, not everyone has access to a stock system image for their device, which is why the option was added to TWRP ;).

I hope that as [MENTION=4544860]osm0sis[/MENTION] mentioned, root devs will look into ways to achieve their desired result without actually modifying system. I think Xposed will be the most challenging, in that case, though.

Hopefully [MENTION=631273]Chainfire[/MENTION] has some ideas on how best to move forward with the systemless method that'll give everyone the ability to have what they want.
[SuperSU] JsChiSurf:
Ha, ha, you mean not everyone has a Nexus device ;) My narrow-sightedness showing there.
[SuperSU] Krynn!:
Thanks! I started with yours and modified it for systemless root.
[SuperSU] netinetinet:
This is flashable zip?
[SuperSU] .bucch:
Nope, it's the boot.img for the fastboot flash
[SuperSU] Rocky1988:
I just tried flashing your boot.img. Still no root. Is there more too it than that? I assumed system-less means it gives you root without modifying /system
[SuperSU] ijustwantaname:
I feel like I'm missing something really obvious here... I'm on a Nexus 6 and coming from a rooted stock MRA58K. I flashed the MRA58N system.img, GROGG88's MRA58N boot.img, & TWRP 2.8.7.1. When I boot into Recovery and try to install SuperSU 2.56, it says everything worked but when I hit "reboot" it warns me that SuperSU doesn't seem to be installed and offers for me to swipe to install it. If I do, it installs SuperSU 2.45 and then complains in the OS that I need to update the binaries. If I don't swipe to install it (again, immediately after flashing the SuperSU 2.56.zip) and then boot into the OS, SuperSU says there's no SU binary installed. Wat do?

EDIT: apparently the answer is "post to XDA," because as soon as I did SuperSU succesfully updated the binaries and all is well!
[SuperSU] Lrs121:
Twrp only checks to see if the su binary is installed to /system/xbin do not allow it to install su if you want to have systemless root.
[SuperSU] .bucch:
Just installed MRA58N and systemless root with your boot image and worked like a charm.

Thank you very much :D
[SuperSU] mrRobinson:
For all you guys who are creating your own modified boot.img, are you able to do it on linux with no android device (not even a reference)?

Obviously all the steps and modifications to ramdisk can be done pretty easily by unpacking/editing/repacking, the one piece I'm struggling with is modifying the sepolicy.

So basically trying to run supolicy from linux. I've pulled its binary from the supersu.zip for x86_64.

run LD against it shows it wants libc.so, liblog.so, libstdc++.so and libsupol.so.

I grabbed the first 3 from x86_64 dir in the ndk and the last from the supersu.zip and set them in my LD_LIBRARY_PATH.

The last error i get is:

# ld supolicy
ld: warning: cannot find entry symbol _start; not setting start address

and if i run supolicy --file sepolicy sepolicy_out on my local system where i have the unpacked sepolicy it just outputs "No such file or directory"

Either I'm missing something stupid or everyone is still using a reference device?

Maybe [MENTION=336863]garyd9[/MENTION] did this?
[SuperSU] garyd9:
I'm using a reference device and running the commands via adb.
[SuperSU] GROGG88:
I'm pulling sepolicy from the [MENTION=631273]Chainfire[/MENTION]'s boot images.
[SuperSU] Krynn!:
It's just one of the steps... Read here for the full instructions. The file I posted is the one for the latest image that dropped this week.
[SuperSU] jackdulouz:
Can someone help create a systemless root boot.img for the Nexus 9 (wifi)? Thanks.
[SuperSU] Ketawa:
Anyone able to post modified boot for angler MDB08M? For use with SuperSU v2.52 and traditional method of modifying system for root. Sorry, I'm not familiar enough with this stuff to generate my own. I realize several people have reported success with the modified boot from MDB08K on MDB08M, but I'm not comfortable enough to use that version with the new images. Thanks in advance!
[SuperSU] Captain_Throwback:
Give this one a shot.
[SuperSU] ijustwantaname:
Hmm, yeah, I got it to work by having TWRP install the (/system) version and then flashing the latest .zip on top of that. I definitely want systemless though, so I did a full unroot in SuperSU but now that I've rebooted and flashed the SuperSU.zip from TWRP, I'm back to SuperSU saying there's no binary installed and it can't install it. Is there a trick to getting a systemless SuperSU on here?
[SuperSU] Rocky1988:
Hmm. You're right. It seems like you have to install SuperSU 2.56 from the link you provided. I just had a look at the update-binary script in the zip file. It has an if/else for $RWSYSTEM which is set to false when running in systemless mode.

Older versions of the SuperSU.zips will still install to /system!

I happened to install this BETA SuperSu v2.52 which I did notice install to /system. Oh well. At least I'm rooted...
[SuperSU] Lrs121:
You're going to have to reflash the system.img since its been modified to return to an unmodified state. The trick is to flash the systemless modified boot.img then flash the systemless zip in twrp. if twrp ever asks to install supersu select the do not install button. You can use the mra58k boot image with mra58n system.
[SuperSU] treIII:
OK so I'd I'm understanding this correctly about systemless boot.img and its root capabilities if I use this method I cannot modify my build.prop? Is this correct? Thanks to anyone who may answer.

Sent from my Nexus 6P using Xparent Blue Tapatalk 2
[SuperSU] ijustwantaname:
Bingo, re-flashing the system.img, the MRA58K boot.img, and then installing from TWRP worked. Thanks a lot!
[SuperSU] osm0sis:
E.g. The following in a su.d script with systemless root allowed AdAway to work perfectly again and still believe it's modifying /system even though it's not:

mount -o bind /su/etc/hosts /system/etc/hosts;

I'm not sure how far this method could be pushed for more crucial things like system libraries (e.g. for Xposed) but it's certainly worth a try. :)
[SuperSU] egingell:
FYI: a file or folder, respectively, must exist in both locations for the mount command to work (eg modified system). It could work for mundane things like replacing the Play Store with an inverted one, but I think the app_process binary is executed long before any bootup scripts, so it wouldn't be viable for Xposed.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] wewewi999:
Hi guys!.. I'm getting a " E: Could not find "META-INF/com/google/android/update-binary' in the zip file error when flasing the Angler systemless.zip in TWRP 2.8.7.1 .

Did I miss something?
[SuperSU] 29y6145:
I want root Lg g4 F500 android 6.0 but my devices LG no support Unlock bootloader :(

pls help me add root system
[SuperSU] shoey63:
Is it possible to get su.d scripts to run without creating an su.d folder in /system, which by doing so, modifies /system ?
[SuperSU] id242:
The "XX-boot-systemless.zip" file is just a simple zip archive with a "boot.img" file inside. Extract the file and flash it through fastboot.

ON YOUR DESKTOP PC:

1) From the MRA58K or MRA58N factory rom archive, Extract the "system.img"

2) From the "XX-boot-systemless" ZIP archive, Extract the "boot.img"

3) Copy "SuperSU-v2.56-20151030013730.zip" to your android device.

FROM FASTBOOT:

4) "fastboot flash system system.img"

5) "fastboot flash boot boot.img"

FROM TWRP RECOVERY:

6) Flash the SuperSU ZIP (SuperSU-v2.56-20151030013730.zip) you copied to your device in step 3.

7) Reboot, but DO NOT allow TWRP to install SU to system.

done.
[SuperSU] wewewi999:
I had figured it out by now, (Was probably a bit too much enthusiastic atm I wrote that ^^) but I'm sure itll inevitably help someone at some point.

Thank you for your time anyway; very nice of you.
[SuperSU] Captain_Throwback:
There's an su.d folder in /su when using systemless root ;).
[SuperSU] chrysik:
Does "razorg-mra58v-boot.zip" has been already posted ?

(for Nexus7-LTE)

(I found custom "boot.img" for "hammerhead-mra58n" and "razor-mra58v" but ...)
[SuperSU] shoey63:
Yep. There sure is. Thanks :good:
[SuperSU] bunklung:
I am also curious if there is a workaround for this.
[SuperSU] Captain_Throwback:
/data/local.prop

Anything put there should override build.prop, if I'm not mistaken.
[SuperSU] Poser:
Could this method be used to install v4a? I would like to keep an untouched /system for now.
[SuperSU] TMG1961:
quick question. I flashed the factory image just a few minutes ago, then installed apps and had all updated. Must i also do a flash system system.img before flashing boot.img (steps 3 and 4)? Seems not needed to me but better ask before i made a mistake and can start all over again. Thanks for your help.
[SuperSU] OMJ:
[MENTION=7037653]chrysik[/MENTION] here ya go...this one is for systemless root

https://www.dropbox.com/s/y305729ml89rzbv/razorg-mra58v_systemless_boot.zip?dl=0

and this one's w/o systemless root...

https://www.dropbox.com/s/yi9yg36wuxcsi2l/razorg-mra58v_boot.zip?dl=0
[SuperSU] id242:
Flashing of boot.img and then system.img can be reversed, in to flashing system.img and then boot.img, if you choose.

It does not matter.

Flashing boot.img will overwrite your current boot partition.

Flashing system.img will overwrite your current system partition.

If you currently have a working factory MRA58K/MRA58N rom installed, or one that is factory with just the root/kernel setup (such as gerar_f's , "Custom Stock kernel with root and color control"), you can flash the factory system.img over it. This will replace the entire /system with a clean factory /system (system.img). You will keep all your files and settings within /data, except your /system will be refreshed back to factory stock again -- without custom kernel, or any custom build.prop edits...etc.
[SuperSU] TMG1961:
It was a fresh factory image i flashed. After flashing bootloader and radio i first erased recovery, system and boot, then format cache and userdata and after that flashed everything again.

When i followed the steps to Root without modifying /system the phone i got the message "Your device is corrupt. It can't be trusted and may not work properly."

Phone didnt boot anymore and i had to reflash all again. Not sure what i did wrong but how to prevent it from happening again?

I decided to follow the steps to the letter, meaning i also did flash the system.img, but sadly it didnt work.
[SuperSU] Vadzhik:
Please, add mra58v-boot-systemless for razor (flo)
[SuperSU] Chahk:
MRA58R for Nexus 6 (shamu) was just released. Can someone build the systemless root boot.img based on that one please?
[SuperSU] elreydenj:
Has anyone built a new systemless boot.img based upon the newest Angler/Nexus 6P factory images with the Nov. security updates? Thank you.
[SuperSU] Khaon:
[MENTION=631273]Chainfire[/MENTION] & anyone else

Using your latest recommandation(patching sepolicy file + editing ramdisk) for 2.56 on AOSP v6.0.60 (master branch) does'nt fully work.

I have to

adb root;
adb shell daemonsu --auto-daemon

to make su works.

I edited the source sepolicies to make the server /su/bin/daemonsu --auto-daemon starts but the build got stuck to the animation logo.

Does anyone has a clue how to edit the source code to make supersu works ? My build are selinux permissive however seems init context intereffere or something and I have no clue what to do !
[SuperSU] Pumpino:
My 5X is arriving today. I believe the latest build is MDB08L. Since the boot.img for this build doesn't appear to be available yet, can we use the boot.img for MDB08K, or will that not work (I'm guessing it's a bad idea).

Also, I saw a reference to SuperSU 2.56. I thought 2.52 is the latest. Is there a newer buld available from somewhere?
[SuperSU] billyx1:
I think it would be easier to download the system image from google than making a backup.

Additionally it was possible to start TWRP for ages without to modify something on the phone (except unlock). I really don't understand why ever How-To starts with "install twrp on the phone ..." :confused:
[SuperSU] osm0sis:
Maybe TWRP image flashing can be modified to add system.img support, that'd be pretty badass and useful.
[SuperSU] Corvida:
Not sure if this is the right place to mention this, but ever since switching to root without modifying the system ES File Explorer isn't able to get root access (for me). I get an error that the Root Explorer feature can't be enabled on this device. However, prior to using this root method it was working just fine.

Thoughts or a helpful nudge towards the right place to pose this question is appreciated.
[SuperSU] Captain_Throwback:
TWRP has always "touched" system on initialization, which is why the code had to be modified.

As for your first statement, I already replied to it ;).
[SuperSU] provolinoo:
[MENTION=912474]Dees_Troy[/MENTION] :)
[SuperSU] itlnstln:
If it hasn't been posted, here is a boot image for Shamu MRA58R with system root enabled (no forceencryption, disabled dm-verity).
[SuperSU] itlnstln:
Here's Volantis' (WiFi) system root for MRA58N.
[SuperSU] sir*mez:
Can you provide an Angler (Nexus 6P) MDB08M with system root enabled (no force encryption, disabled dm-verity) boot.img, please.
[SuperSU] defconoi:
[MENTION=631273]Chainfire[/MENTION] hey just bought your SuperSU Pro last night to support you, would love an updated systemless for angler.

Thanks!
[SuperSU] corkiejp:
As you named this as system root, I assume it is not for the systemless root method.

Thanks for posting it.

Do you also like quoting yourself?
[SuperSU] itlnstln:
That's correct, it's not for systemless root.

I was being lazy by replying to myself. I didn't feel like scrolling all the way down to the bottom of the page. :)
[SuperSU] CeRe666:
I'm trying to root on s5 modle SG-M900W8 on andriod 5.1.1 an keep getting the message that says success in Odin but when I unplug it's stuck in a boot loop I need help guys!! I don't care what rom it us as long as I get root access
[SuperSU] Ch3vr0n:
Wrong place to ask. Use your device forum and if you had read the odin thread it doesn't work on lollipop devices. You need to use flashfire as indicated.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] mech_supernova:
what are the chances of getting root for the moto Droid Turbo 2? thanks
[SuperSU] vacsed:
@ GROGG88: Is your hammerhead kernel image safe to flash with encrypted devices (forceencrypt disabled)?
[SuperSU] vt0r:
Yes, it is safe to use forceencrypt disabled kernels when you already have encryption enabled.
[SuperSU] retired_mnbooze:
I am having an issue with my su.d script persisting through reboot in /su/su.d. My hosts file in /su/etc does persist.

I copied them both via add shell...

Any thoughts?
[SuperSU] vacsed:
The question being: Is GROGG88's kernel "forceencrypt disabled" or not?
[SuperSU] GROGG88:
The kernel does not handle 'forceencrypt', fstab handles that. Hammerhead does not force encryption by default and nothing has been changed with fstab:

/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata

I'm not sure what ramdisks you've been using, but I have not seen forced encryption enabled by anyone...
[SuperSU] vt0r:
Here's a systemless-root boot.img (inside a zip file) for Shamu MRA58R, since I haven't seen one posted yet.
[SuperSU] Pumpino:
Do we have MDB08L for the 5X yet? Is flashing a modified boot.img going to be required every time we sideload an update and need to reflash supersu, or is it only the first time we root?
[SuperSU] birdie:
Help!!

I've just installed BETA-SuperSU-v2.52.zip via twrp-2.8.7.1 on my Nexus 5 running vanilla Android 6.0 (boot loader unlocked) and now it's stuck on a boot animated logo. :(

Is this normal? I've been looking at this logo for five minutes already.

Edit: I've reflashed MRA58N (without flashing SuperSU or anything) and now everything is back to normal.

I still wonder why this thread doesn't contain the following in big red flashing letters:

This zip file is not compatible with Android 6.0. Please refer to this thread for further instructions.
[SuperSU] ashyx:
This is crackers all these people asking for boot images and filling the thread with nonsense. :confused:

Every time I come back to see if Chainfire has posted anything important it's lost in a sea of posts for boot.img's

People should first be asking a dev or someone with a bit of kernel knowledge on their own device forum then just link back to here.
[SuperSU] joni2012:
Hello, boot.img for m8 GPe Android 6? Thank for work.

Team SkyDragon loving
[SuperSU] deusfaux:
Instead of just another person begging for particular files - I'm merely asking - do I need the modified boot.img of the latest OS version to root? ie - does someone need to create a modified MRA58N boot.img (and accordingly all future security updates) for me to get root the same way I used the MRA58K boot.img to get root for 6.0 the first time/version?
[SuperSU] Taomyn:
Any chance of an LTE version?
[SuperSU] pigr8:
http://xdaforums.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
[SuperSU] TJKV:
I doubt there are any kernel changes in Hammerhead's MRA58N versus MRA58K (according to [MENTION=4684315]flar2[/MENTION] over here). One should be able to use chainfire's ~58K modified one on ~58N, along with SuperSU 2.52 (IE without the systemless jazz). Then again people have reported problems in that thread, so best hold off for now or test after backing up.

For future updates, if there are kernel changes, then the new kernel would need to be modified and flashed. If there are no updates to the kernel, one can continue to use the existing file of course.
[SuperSU] c3k:
seems that kernel isn't changed between hammerhead MRA58K and MRA58N, below you can find two stock devices screenshots:

View attachment 3533145View attachment 3533146
[SuperSU] wrecklesswun:
Will the boot img work for MRA58R for Project Fi?

---------- Post added at 02:55 PM ---------- Previous post was at 02:55 PM ----------

CF Auto root worked for MRA58k but stopped with R keep getting a message about a corrupt phone
[SuperSU] osm0sis:
ADB shell in recovery? su.img doesn't even get loaded in recovery (maybe something TWRP will add support for in the future if it becomes the way to go). I just used FX File Explorer while booted to copy my init.d script over to su.d and added the bind mount line for AdAway.
[SuperSU] Taomyn:
What does your bind command look like for AdAway? I tried one suggested to me in the AdAway thread but I don't think it works. I assume I point AdAway to the hosts in /su/etc but when I do, it changes the file but then complains about the symlink being missing.
[SuperSU] vt0r:
He already posted this earlier, but my script that does the same thing (and works well) is the following:

#!/system/bin/sh

mount -o bind /su/etc/hosts /system/etc/hosts

Just make sure you touch /su/etc/hosts first, then leave the original settings on Adaway, and only run the update after you're sure it's been mounted.
[SuperSU] citBabY:
What... I'm actually shocked lol, I downloaded it again, was the same size in bytes tho, but this time it did work :cyclops:

Anyways, thanks... I FINALLY got rid of this damn "The SU binary needs to be updated".
[SuperSU] BookCase:
I don't know why but, I have been unable to flash any betas since v2.10 via twrp on Kindle Fire HD (tate). It says "failed to open .zip" or something.
[SuperSU] BookCase:
Works on all other devices tho (Galaxy S5, Galaxy Tab4).

Example:
[SuperSU] Frank Westlake:
Try opening the SuperSU URL as a web page instead of as a file to download.

Frank
[SuperSU] BookCase:
I have no idea what you mean.