yashsingh1/xdaforums huggingface dataset:
[SuperSU] Frank Westlake:
Long-press the download link and choose to open it instead of downloading it.

Frank
[SuperSU] BookCase:
I don't know why that worked, but it did. Thanks!
[SuperSU] Chainfire:
Interesting. I have adjusted the download page so this should no longer be necessary...
[SuperSU] dragonfixed:
beta supersu v2.12

I have ran full unroot from the super su program and restarted and then reinstalled the zip from cwm and then i was able to access ssh and adb. I also tried to do this several times on my cell phone. i have not tried it on my tablet.
[SuperSU] Paschfire:
supersu Beta v2.12 + pro key nexus 5, Rom Pa 4.6 Beta4, FK R63, I see No issues I will report if any arise.
[SuperSU] Alex_rac:
Xperia Z2

[MENTION=631273]Chainfire[/MENTION]

Hi I want inform you that with v 2.12 there is no problem im my Z2 (now i can grant root permission again with root explorer and lucky patcher :) )

installed flashing the zip :good:
[SuperSU] adeich:
Chainfire

Tried Beta-2.12, also on reboot lost root access to applications installed on the sd card, as well as 2.10-2.11

previous post - http://xdaforums.com/showpost.php?p=55885365&postcount=238

Set v2.13 - Root access applications just disappears :(
[SuperSU] Chainfire:
Try unchecked the "Re-authentication" option on SuperSU -> Settings, let me know if that fixes the issue
[SuperSU] adeich:
Thank you!

Yes, disabling this option solved the problem. Apps on sd card now re not asking for Root Access
[SuperSU] marshy73:
Funny... I had version 2.02. Downloaded and flashed, 2.13 via Recovery... Reboot and... Still App still shows 2.02!???
[SuperSU] Gold_Phenix:
First open app enter in to menu and select uninstall next make reboot and flash superSu from recovery.

LT26i tap from Poland
[SuperSU] marshy73:
Thanks but didn't work...
[SuperSU] khairulez:
Wipe cache and dalvik-cache before flash new one.
[SuperSU] marshy73:
No Go.... ?
[SuperSU] bmdixon:
I tried installing on my encrypted Nexus 5. It claimed to have flashed in recovery OK but after booting up it complained when trying to launch Super Su "App not installed". I installed via the Play store (v2.01?) and it then launched albeit the old version. I manually installed v2.13 from /system/app, overwriting the Play Store version and it seems to be working ok...
[SuperSU] osm0sis:
It's the same command in both threads. The problem is you missed the part of my post where I said to leave AdAway's target at the default /system/etc/hosts file; because of the bind mount it'll actually only modify the /su/etc/hosts file and the /system one will remain untouched.
[SuperSU] Taomyn:
Thanks to both of you.

What's the best way to check that the mount is correct? I type "mount" but I don't see it
[SuperSU] osm0sis:
It should be there. /su is mounted to /dev/block/loop0 so that's what the bind mount inherits.

/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)
[SuperSU] Taomyn:
Ah yes I see that, but I was looking for something that confirms that "mount -o bind /su/etc/hosts /system/etc/hosts" has worked.
[SuperSU] srqrob:
N5 6.0, stock rooted unlocked, Chain fire's moded bootloader for beta su, can I flash the system maintenance update Google has pushed?
[SuperSU] vt0r:
But that actually does confirm it worked. When you mount a single file as a filesystem on Linux (/data/su.img --> /su), you use what's called a loopback.

Since you're just reusing the existing loopback mount that's already on /dev/block/loop0, even though you're binding a file inside it, you'll see the same original loopback mount as the source.

In that case, you would just confirm that the loopback adapter is mounted at /system/etc/hosts, and that confirms it's mounted properly (just don't look for /su/etc/hosts, since you can only confirm the destination + loopback source).
[SuperSU] Taomyn:
Once again, thanks. I see what you mean now, at least I think I do, so how I "confirm that the loopback adapter is mounted at /system/etc/hosts"? Sorry for the rookie questions, *nix is not my strong suit. I just want to be absolutely sure that if I set AdAway back to /etc/hosts that it's really changing /su/etc/hosts
[SuperSU] vt0r:
There may not have been changes in the zImage, but there were definitely lots of binary changes in the ramdisk between MRA58K and MRA58R outside of just the usual selinux_version and default.prop changes with every release. Specifically, init, adbd, healthd, slideshow, ueventd and watchdogd have all changed. This could be due to somehow non-reproducible builds, but that's unlikely when using the same machine for each build, so that's why I posted the MRA58R systemless root image here, just to be safe.

As for the Project Fi question by [MENTION=711602]wrecklesswun[/MENTION], I'm using the updated boot image I posted with no issue (I'm a Fi user as well).

---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------

The following entry in the list of mounts confirms it worked:

/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)

To easily check for just that single mount point, just run the following command via adb shell or in the terminal:

mount | grep 'hosts'

If you see the above line in the output, you can be certain it's working.
[SuperSU] CeRe666:
[MENTION=1754043]Ch3vr0n[/MENTION] can you point me to a flashfire guide
[SuperSU] Ch3vr0n:
Nope, not using it but a simple search up top will tell you. That's what the search is for. Took me a 5 second search to find it.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Taomyn:
Can't see that line at all. I've also changed the permission to the script file 000adaway.script as someone else has suggested and it's now 0700, and rebooted and the line still doesn't appear.
[SuperSU] samteeee:
Greetings;

Any chance a "systemless" boot image is made for 6P MDA89D?

Thank you.
[SuperSU] GROGG88:
There is much more in a boot.img besides the kernel. Quicker to change sepolicy vs. dig for possible source changes.
[SuperSU] MikeRL100:
I noticed a very minor bug on my rooted Nexus 9 with SuperSu beta 2.52. Open up SuperSu. Scroll to the right one tab at a time. You'll notice the clear all trash can for the logs tab. But scroll back to the left after reaching Settings, and it disappears. Minor but worth noting. On Marshmallow of course. Latest build with a modified boot image someone in the comments was kind enough to share.

See? Maybe that extra publicity helped nail a bug. I'm sure Chainfire has much more important stuff on his mind now, with 6.0 still being pretty new, but it's worth noting every issue I encounter so he can note it for the future. Will make tackling things down the road much easier.
[SuperSU] retired_mnbooze:
No, not in recovery. For some reason the file change was not being written to su.img, so upon reboot it wasn't there(???) I have tried a couple times since my original question, and it seem to be working now. Thanks for getting back to me.
[SuperSU] Taomyn:
All sorted now - after several more attempts someone on the AdAway thread gave me a copy of their script and even though I had recreated mine twice, their's worked first time :good:

Thanks again to those that help me out.
[SuperSU] pkelly517:
This would be an ideal time to link the working script for those that have been watching.

You'd also be able to credit the user who supplied you with the solution. As always in open source, take what you need, but always give credit to the provider.
[SuperSU] madbat99:
thanks bro. Worked like a charm.
[SuperSU] Rektifying:
Rooting the Nexus 6 on Android 6.0 Question:

So as many of you obviously know, you have to flash a modified boot.img to obtain root. I am wondering if this modified boot.img for root also disables encryption? If not, can one flash a different boot.img or will root then be lost? Sorry I am newer to this and I don't quite understand how/if I can flash a different boot.img without losing root. Thank You!

EDIT: I can not believe I am having this hard of a time finding an answer to my question. All I want to know, is this. Rooting the Nexus 6 on Android 6.0 requires you to flash a modified boot.img. So, after obtaining root, can I flash a different boot.img, or will I lose root???????
[SuperSU] Krynn!:
I did a binary diff between the two zImages. I don't know exactly what changed, but it was a pretty long list.
[SuperSU] Taomyn:
Of course you're correct: http://xdaforums.com/showthread.php?p=63692784#post63692784 was in a rush to leave earlier.
[SuperSU] vt0r:
This only differs from what both [MENTION=4544860]osm0sis[/MENTION] and I posted by ending the command line with a semicolon, which is unnecessary anyway. Something else (permissions?) had to have changed in order to make it work where it didn't before. Glad you got it working, but for anyone else trying to figure it out, the earlier advice was correct.
[SuperSU] twilighttony:
Does anyone know when the HTC One M gpe marshmallow will get root? Or if it requires the same method? Just curious
[SuperSU] Captain_Throwback:
Might be helpful if you search in your device forum. But there's no reason the root methods here shouldn't work on any Marshmallow device.
[SuperSU] Ifuk1203:
I encountered the same problem you do not know how to solve it?

I encountered the same problem you do not know how to solve it?
[SuperSU] shoey63:
Switch to Fx File Explorer with Root add-on
[SuperSU] mhmadfarooq:
Hi guys: I have Samsung Galaxy E500H running lollipop 5.1.1, I flashed TWRP recovery then flashed the latest beta Supersu, but my phone went into bootlop till I reflashed a new stock rom.

Can u help me sove this problem or rooting my phone, please?
[SuperSU] HansiHusten:
Just want to report that I updated my Nexus 9 from 5.1.1 to 6.0 and rooted it immediately with this nice new methode. It worked like a charm.

Thx man, will send you some bitcoins!
[SuperSU] jackdulouz:
Can someone create a systemless root boot image for the Nexus 6P (MDB08M)? Thanks in advance..
[SuperSU] thekenster:
I updated my Nexus 5X to MDB08M. I havent found a system root boot image for M so I flashed Chainfires MDB08I and all seems to be working. Does anyone have a boot image for M? Thanks
[SuperSU] bunklung:
This does not work on user builds:

https://android.googlesource.com/pl...dbda7e1c5bcebc501b4943cd6483122297e1834^!/#F1

Any other suggestions? Would there be a way for the kernel to enable /data/local.prop on user builds?
[SuperSU] v12xke:
Anyone have the N9 LTE (Volantisg) modified boot.img for MRA58N? Because I am stock, unencrypted and wish to stay that way, this file is always seems to be the hold up for me. Could I just:

a) use the existing CF modified boot.img from MRA58K or

b) d/l a custom MRA58N ROM and extract their boot.img and then flash it with the other Google image files? (bootloader, radio, system, vendor, modified boot, SU v2.52)
[SuperSU] ashyx:
Welcome to the boot.img request thread formerly known as SuperSU. :confused:
[SuperSU] Alferboy:
Modified boot

*Deleted not to offend* Please delete the post.
[SuperSU] mondohow:
SMH Too true. I had to turn off notifications just yesterday. I saw all the notifications and thought damn CF's been busy. Only to see this...
[SuperSU] a g bell:
Is an outrage?
[SuperSU] Captain_Throwback:
setprop in init.rc
[SuperSU] lifelesslegend:
Ignore this, sorry for the stupid post :( :(

Does the latest BETA 2.52 work with the Oneplus One running SultanXDA's unofficial CM13 ROM?
[SuperSU] Alferboy:
I just asked *if there was* an official boot.img, not for someone to get me one.

I managed myself and created what I needed and shared it, tested and working.
[SuperSU] GROGG88:
Yes, completely unbelievable that the community would step up and provide image updates in [MENTION=631273]Chainfire[/MENTION]'s absence! I'm taking my toys and going home in protest, and encourage everyone else to do the same!
[SuperSU] Khaon:
[MENTION=631273]Chainfire[/MENTION]

I was not understanding why my service from init was not starting the su daemon

As I was using Master branch, this was the cause of my failure

So to fix my error I had just to specify a context for daemonsu.

I chose the following.
[SuperSU] Manuel15:
Maybe they sould create a thread apart for boot.img request

Inviato utilizzando XDA One
[SuperSU] thekenster:
Thank you for understanding GROGG88!!! Not all of us have the "know how" to update a boot.img and with Chainfire absent some of us were just looking for help from the community.
[SuperSU] chazall1:
Wow! an incredible low. Stay on task.
[SuperSU] mrRobinson:
Hey I understand. I just feel those requests belong elsewhere, not in this thread. Maybe in the device relevant forum with a link back here so those with the know how in that device forum can go ahead and provide.
[SuperSU] kibmikey1:
08K still works fine!
[SuperSU] osm0sis:
It actually already does! install-recovery_original.sh is the untouched version as long as you haven't flashed SuperSU twice. Check out my unSU script zip a few pages back for how to unroot cleanly for OTA purposes (or to switch to systemless root more easily). :)

I agree it's burying the more relevant bug hunting/troubleshooting and working-around myself and others have been doing, so when CF does get back we're going to have to dig up all our posts again to link for him...

I think the most sensible thing would be to start an "Unofficial CF Marshmallow Stock Rooted" thread here in the SuperSU section for people to post their images in. [MENTION=3667193]GROGG88[/MENTION], perhaps you or someone else motivated with some time could start it and keep the OP of it up to date with the latest for each device? Gather the links to the ones from here since CF's absence too? It'd be good to keep them all in one place but not continue to clutter things up here. :good:

P.S. To start playing around with updating flashable mods for systemless root, you can modify /su while in recovery with these commands:

suimg=$(ls /cache/su.img /data/su.img 2>/dev/null);
mount -t ext4 -o rw,noatime $suimg /su;

(If it's after the initial flash but before first boot it'll be /cache/su.img instead so I just used ls as a quick catchall there.)
[SuperSU] elreydenj:
It does but there are probably changes to the binary and ramdisk.... Someone should create one that has an understanding of how.
[SuperSU] Alferboy:
Thought this was an helping community and didn't want to offend anyone by making them think I was trying to step-up into Chainfire's absent shoes. Not my idea at all!!! Sorry!!!

Deleted my post along with two working images.
[SuperSU] confanet:
Hi guys,

I read many members posting solutions for rooting but I haven't understood if there is a tested and recognized method to obtain root on N6 with MRA58R without using the systemless method.

Maybe I missed something.

Thanks
[SuperSU] shoey63:
Would the same method apply to build.prop? ie: Copy build.prop to /su and create an su.d script something like this?

mount -o bind /su/build.prop /system/build.prop;

Then presumably you could make build.prop tweaks in /su/build.prop and they would stick.
[SuperSU] Alferboy:
I see!

root@hammerhead:/ # find . -name install-reco* 2>&1
./system/bin/install-recovery_original.sh
./system/bin/install-recovery.sh
./system/etc/install-recovery.sh

I was looking for it in the file's original place whereas it's created on the symlink's location.

About the systemless option, it really has advantages (since you'd always have to flash boot).

Yet, a lot of applications are still broken either by relying on su's location or on modifications being made to the system partition.

---------- Post added at 01:03 PM ---------- Previous post was at 12:34 PM ----------

Don't think that mount would be done "in time" (i.e. on boot) for the file to be read and the tweaks to be incorporated.

AFAIK build.prop is read by 'init'. Don't know if it can be reloaded without restarting.
[SuperSU] Manuel15:
Flash the supesu.zip file, you can find it in the first post

Inviato utilizzando XDA One
[SuperSU] Phil3759:
ro.xxx properties are read only, you must reboot to load them

This shows the limitations of systemless root. Or, I'd say, it questions the limitation of rooting but be denied /system modifications

Rooting while wanting to not modify /system is for people that would like access to /data, /cache and limited /system files modifications, provided that these files are not read at init. This makes it rather of a limited use.

To have full root advantages and access to /system, recompiling the kernel will soon be the only option, unless google stays at ramdisk changes to toggle dm verity
[SuperSU] Phil3759:
Another thing:

I am not expert in security, but locking users to be obliged to recompile kernel and not only modify ramdisk is rather extreme. A bootloader parameter with a default property check looks enough (like it was with selinux at some point). Added to a startup warning that /system or /boot are modified, we have a secure thing: People that need root, can still use the stock zImage, no need to recompile. Others are completely secure anyway.

The actual move is something like bootloader locking. Any modification and your system won't boot. When devices will start verifying boot partition in addition to /system and lock at startup if they are modified, ramdisk changes won't be enough and there will be no workaround other than compiling the kernel anyway

Many low end devices, and even brands like Samsung do not provide sources in a short time. Often the sources need changes/fixes to be compiled. And they are not always 100% working like the original one. It proves manufactures don't always release the true full sources of the zImage

Sorry, as it is going off topic. But just a reminder that with a pure systemless root, don't expect all root benefits you're used to. It is in fact a half root: accessing some parts (just a r/w mount to /system) will prohibit device from booting on next run
[SuperSU] bunklung:
I known Chainfire has made it clear he has no intention of playing whack-a-mole with Google on security. I think that ultimately Google will not allow security strict apps (Android Pay) to work when the bootloader is unlocked at any point (some efuse thing). This would include all the other verification done with dm verify.
[SuperSU] CeRe666:
I'm looking for help rooting my galaxy s5 SG-M900W8 running 5.1.1, I ran cf auto root with Odin it flashed an said passed, when I unplug ed the phone it was in a boot loop, I put it into recovery mode it was still saying I had no root access an that it was the original recovery, I flashed the original rogers room to get out of the bootloop as a factory reset didn't help, is there a way to root my modle on andriod 5.1.1 kingroot dose not support nor dose kingo app, I heard for the s6 running 5.1.1 you need to flash a custom kernal before rooting it this true? Can someone point my to the right place plz! This isn't my first time rooting but my first time with issues!
[SuperSU] Ch3vr0n:
The proper place would be your device forum not the superSU thread.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] kylebenton:
Conversation from Recently v1.30 Thread:

[MENTION=4703968]AndroidSlave[/MENTION] :

Here's the conversation from the recently app thread where I got off topic:

http://xdaforums.com/android/apps-games/placeholder-t3050998/page22

-------

Short Version - I flashed stock 6.0 from bootloop w/ADB/Fastboot, got it up and running, then flashed the modified boot.img, TWRP, and then in TWRP flashed BETA-SuperSU-v2.52.zip, then Busybox. I wound up with SuperSU v2.45 and BB is fine. I haven't had the opportunity to try again yet.

I rebooted into TWRP to see where the SuperSU Rooting feature in TWRP was, and I couldn't find it.

Maybe I just didn't see it, but I looked through the 8 basic menus (Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). Or is it buried in sub-directories?

I did not flash a ROM. Only clean install of M (MRA58K from Google); unlock, modified boot, and TWRP through ADB/Fastboot; and finally flashed SuperSU.v2.52.zip and Busybox with TWRP.

What did I miss? If I reboot in twrp and attempt to flash the SuperSU.zip again (or a different version) will it mess anything up?

Thanks man.
[SuperSU] egingell:
There are no SuperSU root features in recovery. Recovery (custom or stock) uses its own root - it's basically a separate, self-contained OS.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] kylebenton:
I didn't think so. I guess I read it wrong. So I am trying to update my SuperSU to v2.52. I did a clean flash of MRA58K (Marshmallow) from Google, flashed modified boot, then twrp. then i flashed the SuperSU.v2.52.zip and busybox, and I have SuperSU v2.46 (the Playstore version that is not BETA). Chain told me in the other thread to update my SuperSU to v2.52 to get my application (Recently) to work with Android 6. I flashed the zip and restated and still have the same version (2.46). What did I miss?

Thanks :)

EDIT: I flashed the Android version, boot.img, and twrp with adb/fastboot, then the SU.zip and busybox in twrp. I should have made that more clear.
[SuperSU] ashyx:
Both twrp and cwm have the inbuilt ability to root.

In twrp it's only available if it detects the system doesn't already have root, then it will offer to root otherwise you will never see it.

Why they don't make it a menu item I don't t know.
[SuperSU] :
When I try to install systemless on nexus 5 I always get an error, how can I fix this?
[SuperSU] kylebenton:
Alright! Got it to install SU 2.52 after downloading the zip again and flashing the zip... Just like I did the first time. Dumb luck I guess. Thanks all. :)
[SuperSU] vt0r:
Just so you're aware, nobody will be able to help you unless you provide the actual error you're receiving, as well as what steps you're taking to "install systemless" on your Nexus 5.

Once that info is provided, someone should be able to assist.
[SuperSU] kentoe:
Can also confirm I flashed my 5X to MDB08M and used the MDB08I modified boot image and SuperSU seems to be working fine. Everything booted up correctly. Would be nice to have an updated boot image to be sure of things though.
[SuperSU] BladeRider:
Anyone have the N9 LTE (Volantisg) modified boot.img for MRA58N? Thanks for sharing though
[SuperSU] !@ndre@!:
Hi guys, I've a N5 with 6.0. I've rooted it with this method and several minutes ago I've received the notification of the OTA update to LMY48X. Can I install the OTA or have I to flash the stock boot?
[SuperSU] ashyx:
It has been said that you would need to reflash the stock boot, but that doesn't make sense.

If you have already received the ota then once the device boots to stock recovery to flash the ota the system partition will be untouched so should flash just fine.
[SuperSU] michierusama:
Hi I tried flashing with the Stock recovery and it gave me an error for the OTA so it dos not work for me. TWRP wont work either.
[SuperSU] ashyx:
This is with systemless root? Did you modify system in any way by installing any apps that would?
[SuperSU] michierusama:
Im going to get informed about that method because I dont know how to respond your question, sorry.
[SuperSU] ashyx:
Did you root with v2.56 or v2.52?
[SuperSU] michierusama:
I used nexus root toolkit and it used the .52 file
[SuperSU] ashyx:
You didn't have systemless root then as that requires v2.56.

v2.52 modifies system so the ota wouldn't have worked.
[SuperSU] michierusama:
Thank you. So can I flash 2.56 and proceed or will I need a clean install and then flash the zip?
[SuperSU] ashyx:
Will need a clean install then someone that has posted a systemless boot.img for your device.
[SuperSU] michierusama:
Then I will wait some more because I have 6.0 since day 1 and I don't want to go back just to update the OTA :P maybe some other time, but just to make sure I understand, there is a 2.56 version that doesn't modify the system partition and lets you update OTA with the official recovery then you can go back to any custom recovery you desire.
[SuperSU] ashyx:
Yep, as long as you never modify the system partition ota should work.