yashsingh1/xdaforums huggingface dataset:
[SuperSU] alexxandro84:
can i use this method?

1- i flash boot.img with nexus root toolkit

2-i click Root (and also flash custom recovery TWRP) on Nexus Root Toolkit

3-when reboot device on recovery, i flash perm-recovery

4-i flash BETA-SuperSU-v2.50.zip

is it right?
[SuperSU] palmbeach05:
See WIP thread above
[SuperSU] alexxandro84:
Rooting procedure:

- flash/upgrade to Marshmellow

- flash modified boot.img

- flash/boot TWRP and sideload latest v2.50+

yes with nexus root toolkit
[SuperSU] palmbeach05:
Personally, i do not have a nexus. For flashing, i have rsd lite and fastboot and a flashing toolkit called mythtools. If the nrt you're referring to is what i think it is (comparable to mythtools for me) and is used to flash imgs and stuff, then yes, use that. Thats at least the impression i'm getting from what you're saying without looking it up
[SuperSU] sirob71:
I had root through hC-b7-M / SuperSU 4.49 on my Nexus 6. I'm with encryption.

Today I tried to "upgrade": flashed your modified boot.img, flashed supersu 4.50 through twrp.

I examined the log texts on the screen and didn't find any errors.

The result after the restart was that it spins on the boot animation forever. It never asked to pattern unlock my boot process.

After that I flashed the stock boot.img, hC-b7-M, SuperSU 4.49. Everything works again. I didn't lost my userdata.
[SuperSU] cartman_73:
Yes, I always unistalled before flash the OTA update and it always has been ok.
[SuperSU] BestWorker:
I have the same issue. It works with ElementalX-N6-3.00 and Despair, but goes to boot loop with modfied shamu-mra58k-boot
[SuperSU] MrKaon:
Use fx explore

https://play.google.com/store/apps/details?id=nextapp.fx
[SuperSU] Phil3759:
Note 4 COH4 and COI3 kernels based on Chainfire recommendations:

http://xdaforums.com/note-4/snapdra...5-1-1-kernel-root-t3208778/page4#post63178320

Many thanks [MENTION=631273]Chainfire[/MENTION]

However, a quick explanation on what is patched in sepolicy file would be great, so that we understand what is broken exactly in SE policy to allow SuperSU on boot
[SuperSU] Chainfire:
Something with the encryption on these devices that I'm missing. It clears up after a format of /data. Possibly a more seasoned kernel guy can look at my instructions and see what I did wrong.
[SuperSU] spinetingling:
Flashed boot.img and SuperSU on my hammerhead. Root works, but cannot restore any backups with TB.
[SuperSU] mdamaged:
Yes, I tried it, then and now, and it open his page which has a link to the file.

https://download.chainfire.eu/741/SuperSU/BETA-SuperSU-v2.50.zip is a html page (which is what he links in the OP), https://download.chainfire.eu/741/SuperSU/BETA-SuperSU-v2.50.zip?retrieve_file=1 is the link to the file which is on that page.

It's an unfortunate way to name a page link since some braindead browsers may look at the extension rather than the file type.
[SuperSU] Chainfire:
If you're running something that bases content on the URL rather than the headers, download the wrong file is the last of your worries.
[SuperSU] Smultie:
Is there any reason why this Explorer works, while Solid and Root Explorer don't?
[SuperSU] beerbaronstatic:
Having the same issue on shamu
[SuperSU] Danilo Pantelić:
Any plan for SM-N910C 5.1.1 (http://www.sammobile.com/firmwares/database/SM-N910C/) auto root ?

On your site still 4.4.4 version - https://autoroot.chainfire.eu/
[SuperSU] MrKaon:
No idea, but it works.
[SuperSU] Masterchief87:
Maybe y'all should check out the ElementalX kernel. It already has a version for 6.0 available. You can find it at http://elementalx.org/devices/nexus-6/
[SuperSU] Smultie:
True. Was just curious ;)
[SuperSU] flar2:
In fstab, perhaps try replacing "forceencrypt" with "encryptable" instead of removing it.

I only took a quick glance at your modified boot images last night, that is the only thing I noticed that could be related. I think dm_verity only affects /system.
[SuperSU] torecdude:
Flashed the modified boot image with fastboot flash boot boot.img

then boot to recovery and flash 2.50 SU.

stuck at bootloop, please help?

edit: i had ElemetalX kernel installed and rooted with 2.49 SU. if that matters.

edit2: I just flashed the factory image all over again and then flashed boot image twrp and SU again and its working. thanks Chainfire!
[SuperSU] PalmCentro:
You can do it without CF....

שלום!
[SuperSU] theliquid:
Sadly root doesnt work for me with Android 6.0 on my Nexus 5. I followed the instructions, SuperSu is installed but TitaniumBackup or RootExplorer both dont work.
[SuperSU] MrKaon:
Titanium backup has been updated on play store to support Android 6,make sure you have it.
[SuperSU] palmbeach05:
Any plan to submit the recovery img to him or are you going to make him dl the entire OTA?
[SuperSU] saltyteabag:
Seems to be a problem with those two apps rather than root itself. Someone further up reported success with FX File Explorer:

https://play.google.com/store/apps/details?id=nextapp.fx
[SuperSU] omametsnor:
I can confirm problems with Titanium backup, will this get fixed by TB developer himself or should I just wait with Android 6.0 for another root method??
[SuperSU] theliquid:
I just got the update but still doesnt work :( Maybe I start all over since it should work.
[SuperSU] MrKaon:
Already updated on play store, works fine.
[SuperSU] theliquid:
Update: It seems to be related to TB - no to SuperSu. I just installed Adaway and it works fine.
[SuperSU] torecdude:
Im confused. Root checker shows eveything good but Rashr cant backup any kernels, titanium backup is still not working after updating. I had all those working when i flashed ElementalX kernel and SuperSU 2.49.

Now when im running modified boot with 2.50 nothing seems to work altough it seems im rooted.

So the problem are the apps not compatiable with M? or root on M is the problem?
[SuperSU] omametsnor:
Exactly this, I would like some clearance also :D
[SuperSU] billyx1:
On my encrypted Nexus 5 unfortunatlly a factory reset was forced after installing SuperSU 2.50 and the boot.img. Some data/settings are missing... :crying:
[SuperSU] omametsnor:
are you rooted with elemantalX or decrypted boot.img?
[SuperSU] Chainfire:
Yup, that was it, thanks.

EDIT: Bah, spoke too soon. Now I'm getting an 'input password' dialog.
[SuperSU] billyx1:
Same device here, but Titanium is working. Only restoring of call history and wifi-networks is not working (does nothing).
[SuperSU] MrKaon:
ElementalX.
[SuperSU] omametsnor:
that explains it, mine also worked with ElementalX but not with the new method of the decrypted boot.img
[SuperSU] palmbeach05:
Update for you. Since you failed at following the do it yourself instructions and wanted chainfire to do all the work, one of your fellow device owners/developers has done what you asked for. I'm now referring you to the 5.1.1 thread in the general section of your device page.
[SuperSU] Ja_som:
Chainfire's boot.img and SuperSU 2.50 on my N5 and everything works (Titanium Backup, AdAway, Total Commander - copy files from system, ....)

EDIT: now I found that not everything works :(
[SuperSU] omametsnor:
I guess Nexus 5 and Nexus 6 are alot different in that case
[SuperSU] Ja_som:
I didn't know you have N6, you never mentioned it (in last few pages)
[SuperSU] omametsnor:
haha sorry, automaticly assumed people would know.

sorry I am quite new here :D
[SuperSU] jblazea50:
Stuck in bootanimation on Nexus Player.

Flashed factory image, flashed boot.img, flashed SuperSu 2.50, factory reset. This led to continuous bootloop.
[SuperSU] Chainfire:
Should have a solution in +- 15 mins.
[SuperSU] omametsnor:
Sir what do ppl with a Nexus 6 have to do were Titanium backup and Root explorer and such dont work? should we wait for a new file or something or when the app dev of TB makes a patch or something??

I have no idea what to do should I flash back to 5.1.1 or root with the ElementalX kernel and get rid off the boot.img?
[SuperSU] pkgnex:
All,

The current boot.img and beta_su_2.50 works for me on Nexus 6, so it's not a "Chainfire problem" I don't think.

The one problem I DID have is that there wasn't any space left in /system after flashing the new factory image. I had root, and could mount and write to /system, but adaway, busybox, etc. were failing due to lack of space.

I simply deleted some garbage from /system (like all the foreign-language google keyboard inputs) and everything is now working great!

I suggest those on Nexus 6 experiencing issues give this a try.
[SuperSU] torecdude:
How did you deleted those?
[SuperSU] omametsnor:
My only problem is that TB stucks on 0% while restoring, ive tried everythif

Manual location selection, usb debugger,reinstallig supersu. Complete system reinstall
[SuperSU] palmbeach05:
All this panicking over a new android release thats less than a week old. You knew the risks of upgrading, we all know things don't automatically work on a major update like this. Relax, take a deep breath, and be patient for a fix. Chainfire has already explained things regarding root on 6.0. Its properly rooted, the rest of the android world needs to get themselves on the same page.
[SuperSU] omametsnor:
Okey but I just wantes to make sure rhe problem is not on my end. I will patiently wait for a update drom TB. I am not stressing haha i honestly couldnt xare less
[SuperSU] akilger14:
Lucky for you, that day is today. TB updated with initial support for 6.0.
[SuperSU] DummyPLUG:
Also using chainfire's boot.img and supersu 2.50 on N5, my titanium backup, root explorer and morelocale2 correctly ask for root permission, all of them fail to read file from system :(

still trying to figure out what is going on.
[SuperSU] palmbeach05:
I wondered when they were going to pay attention and push out that update

---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------

Update your TiB. User above you just said they released their initial 6.0 support version
[SuperSU] Chainfire:
Uploaded all new images to the WIP thread, these should no longer cause bootloops on encrypted devices, but just work properly instead.

That means new kernels for every Nexus device, aside from the Fugu. I'm still figuring out what the issue with that one is.
[SuperSU] pkgnex:
I used root explorer, navigated to the /system/app directory, then started deleting stuff that I knew would be safe to delete / wasn't needed. I started with 16MB free in /system, and ended with about 120MB free. Busybox (sterricson) would then install, and AdAway could write the new hosts files.
[SuperSU] DummyPLUG:
Already using that version.
[SuperSU] torecdude:
funny thing, i cant access root folders cause my Fx cant access those although hes granted with root. Any one familiar with a method i can use to boot temporary to ElemantelX kernel?

im familiar with fastboot boot boot.img but which file in flashing zip i need as " boot.img"?
[SuperSU] osm0sis:
Fantastic work as always! :)

Just wanted to report I'm noticing a couple oddities with the modded sepolicy still:

1) init.d scripts (run from an init.rc class late_start service) can mount /system rw and write to it, but for some reason can't write to /sdcard, instead reporting a file/path not found error;

2) BATTERY_STATS and DUMP are granted to BetterBatteryStats automatically with your hammerhead boot.img, but aren't with your razor boot.img;

Cheers!
[SuperSU] Chainfire:
1) There is so much wrong with depending on init.d I'm not even going to explain. Use su.d or die trying (or run-parts from su.d so init.d also gets executed). /sdcard may not be mounted at any given time - init may not have mounted it, and there may be changes to the sdcard mechanism that have not yet been incorporated into SupersU.

2) This will need some further looking into, but most likely this will come down to BBS having to make a supolicy call. Only in the event that a great many apps break without doing this policy change in SuperSU, will it actually be done by SuperSU.
[SuperSU] Chainfire:
Figured out what the issue is with Fugu. Aside from the encryption issue, there is something different with x86 binaries on 6.0. This will require a patch in SuperSU itself.
[SuperSU] osm0sis:
This is pretty much what I was thinking, hence reporting it. Thanks for the insight. ;)
[SuperSU] corkiejp:
Stickmount app probably needs to be updated?

Stickmount app probably needs to be updated?

The new OTG feature of Marshmallow conflicts with stickmount and prevents the stick from been mounted!
[SuperSU] Ch3vr0n:
Post in the stickmount topic? You're in the SU beta thread

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Tarcis:
I swear I searched a lot before posting, but I still have a doubt.

I have stock 6.0 on my Nexus 5, do I have to flash any kernels (never done that) before, or can I just install v2.5 like the older ones (install cwm and use it to install supersu)?

P.S: I only found that supersu will only work with custom kernels
[SuperSU] Masterchief87:
Deleted
[SuperSU] boxcar8028:
I know this is work in process and it’s very much appreciated. I have one question about this new root method. Can I still use SELinux Mode Changer to change to Permissive? I’m a big fan of Viper FX and it needs to be Permissive mode to work.
[SuperSU] scoobyjenkins:
Not necessarily: http://xdaforums.com/showthread.php?p=61242973

Tapatalked that shiznit.
[SuperSU] Chainfire:
Advising everyone who is having trouble with root apps ( == trouble with the current security ) to just go and use a kernel without any security at all, will never lead us to figure out which security problems need fixing and how, and will result in eventually everyone just running with all security disabled. It is pretty much the least productive thing you can do in this thread.

Then again, if you were expecting problem free usage at a couple of days in, you may be in the wrong thread/forum/website/planet in the first place.

If you really need permissive, just use a permissive kernel. I've always wondered why Viper needs this, surely there must be a fix possible.
[SuperSU] scoobyjenkins:
There is, I just posted a link to an supolicy that lets Viper run on enforcing, been working great on LP for me!

Tapatalked that shiznit.
[SuperSU] bunklung:
Does this mean the possibility of a automatic factory reset still stands when flashing your boot image? I have been staying clear since I don't want a factory reset to occur unless II specifically invoke one :)

Thanks for your hard work!
[SuperSU] shaggyskunk:
For Viper4A to run with SEAlinux Enforcing - Flash this zip in recovery

https://www.dropbox.com/s/rphlajc2o64rdla/ViPER4Android-supolicy.zip?dl=0

Sent From my SM-N910W8 Running SlimRemix V5.1
[SuperSU] Chainfire:
It should be fixed, but is it impossible? Too soon to say.
[SuperSU] boxcar8028:
WOW! Didn't see that new Permissive.zip I'm going to give it a try as soon as I get home tonight. Now it looks like all of my must have apps are okay with the Android Marshmallow rooted. Thanks man.
[SuperSU] omametsnor:
To eliminate the problems I had with TB and stuff i installed custom kernel ElementalX once again, everything working fine again. BUT i kept the decryptes Boot.img from Chainfire which apperently fixed the error message "this device is corrupted" got my ass happy as **** because that was the main reason I wanted to root in a another way

Thankyou!
[SuperSU] shawek:
Updated to Beta 2.50 and running fine on Htc m7,5.1 GPE rom...Thank you for all hard work !!!:thumbup:

Sent from my HTC One
[SuperSU] tom1807:
That applications having problems with root access when a new major version of Android is released is nothing new, same happened when LP was released.

However, I would like really to see here reports whether any problems occur with the root process, original kernel, phone model, factory reset occurred.

I think this is more helpful to others and also for CF to figure out whether there are still any problems left.

And yes, I admit it, I didn't update to MM yet, because I cannot afford a factory reset currently.

Cheers

Tom
[SuperSU] wirelezzz:
I rooted my nexus 5 with your stock image boot file and its perfect ! Only thing I could not use root explorer to edit my mixer path I ha'd to use es file explorer it worked perfect editing files .
[SuperSU] garyd9:
Chainfire, you suggested the following to be run on a reference device for modifying sepolicy (to be pulled back into a ramdisk for a "target" device boot image.)

adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out

Does the "reference" device need to be of the same architecture (or even the same platform) as the target device? (I'm a bit short on devices. I'd need to use a nexus7 (2012) for modifying the sepolicy for a boot image on a 64bit exynos kernel... different processor, different bitness, etc.)

Thanks

Gary
[SuperSU] Masterchief87:
I wasn't really thinking about it like that but I see what you mean & deleted my previous post. I apologize. You gave me a different perspective in regards to the issues people have been having and I'll bear that in mind.
[SuperSU] Phil3759:
I am interested too, maybe worth trying a hybrid S4/Note 4 approach in my case.
[SuperSU] dreams60:
Aarch64 architecture

I am using lenovo tab2 a8-50f.

But is there any root solution for aarch 64?:confused:
[SuperSU] JulianJenner:
New SuperSU is working good with my RedmiNote1 3G stock MIUI7.

But not working on ported Android 5.1.1 custom ROM.

Thanks Chainfire!

居廉测试仪助手 - 红米Note WCDMA国际版 - MIUI v7 5.9.29 联通版
[SuperSU] Chainfire:
Shouldn't matter, I've done this cross-platform before.

Note that you may actually be able to run this on the target device as well. You'd push sepolicy (0644) to /data/local/tmp, as well as the correct supolicy (0755) and libsupol.so (0644) files for your architecture. (just take them from the SuperSU ZIP), then do something like the following:

LD_LIBRARY_PATH=/data/local/tmp:/system/lib[64] /data/local/tmp/supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out

That might work (no guarantees), but you may need to play around a bit. Generally you won't be able to pull the running policy as root though, so you still need to extract the sepolicy file from the ramdisk. No worries though, if this ends up being the way to go, I'll automate the solution (and more).

The binaries do support aarch64 ( == arm64 ), but you'd still have to get the binaries on the device.
[SuperSU] palmbeach05:
If you were following along with developments with your device, you would have already found out that the answer is no, but there is a team working on it. Now the useful thing to do would be take the fix for android 6.0 devices and the possible fix for Samsung devices mentioned by chainfire and apply the method to your device. That might work. Talk with your device's team.
[SuperSU] solidus636:
for the record supersu lollipop works fine on marshmellow
[SuperSU] nekalbus:
I've made it with Nexus Root Toolkit v2.0.5:

Rooting procedure:

- flash/upgrade to Marshmellow

- flash modified boot.img

- flash/boot TWRP and sideload latest v2.50+

But Nexus 5 (Marshmallow MRA58K) not start, always shows new logo animation ... what's wrong ?
[SuperSU] palmbeach05:
Su now comes in flavors? :p jk if you mean the 2.50 release, its already been confirmed to work properly on 4.4.4 and up.
[SuperSU] Chainfire:
v2.51 has been posted, so has a new boot image for fugu (Nexus Player). These are meant to be used together.

There is no reason for v2.50 users to flash v2.51 unless you're on an x86-32 device, which you aren't, unless you're running a Nexus Player :)
[SuperSU] matrixzone:
Awesome
[SuperSU] Ejvyas:
I for 2.49 beta on bacon 5.1.1 Do I need to update to 2.51?
[SuperSU] torecdude:
I dont get it... i had first rooted with ElementalX + 2.49 Su and titanium was able to restore. Now im using ElementalX with 2.50 and i cant restore any of my apps...

Using the lastest titanium update 7.2.3
[SuperSU] bdorr1105:
absolutely sorry if this is a super dumb question, Nexus Player? as in any nexus device?
[SuperSU] mdamaged:
Nexus Player as in this device only.
[SuperSU] teddy0209:
I think the Nexus Player is a different device... ?
[SuperSU] doitright:
I'm noticing a lot more problems dealing with selinux on 6.0+root now than I did in 5.1. I'm not sure if it is actually a function of 6.0, or if it is a function of the selinux policy changes added to the 2.50 modified ramdisk images. Root certainly is working, but just about everything, from a simple "kill -9 pid" requires something other than the default policy. I've been achieving success using the system server context for most things.
[SuperSU] Chainfire:
"kill -9 pid" works for me without issue (from a su shell) ? Please elaborate.
[SuperSU] tom1807:
Ok, I bite the bullet and flashed MM on my N9

Flashed all, except recovery

Let it boot (no problems, except GooglePlayStore stopped several times)

Reboot again PlayStore was fine

Boot into bootloader, flashed the modified boot,img from CF (fastboot flash boot boot.img)

Reboot again

All fine, no problems

Reboot to bootloader again, flashed TWRP 2.8.7.0 again (fastboot flash recovery recovery.img)

Boot normal, then reboot into Recovery (adb reboot recovery)

Found that TWRP asks for my password

Reboot normal, removed my pattern, rebooted to recovery, still same

Pressed Cancel, go Advanced -> ADB Sideloading, swipe

on the PC type "adb sideload BETA-SuperSU-v2.51.zip" without quotes

Successful, rebooted, everything fine

Root works, CF Lumen asked for root, asks for updating the driver, reboot, asks for updating the driver, reboot -> give up

ES File Explorer has root access, Link2SD and AdAway, TitaniumBackup also

Most important for me, no factory reset
[SuperSU] doitright:
I have a couple of receivers;

the first is for android.intent.action.BOOT_COMPLETED

It disables a few services (the kind that automatically re-enable themselves when the device is rebooted) using "pm disable", then sets an alarm for the second receiver to run 20 seconds later after it all settles. The second receiver checks for a wakelock using "dumpsys power", and kills the process if the wakelock exists "kill -9 pid" where the pid is pulled from dumpsys power.

It possibly could be related to the context of the process being killed rather than a general right to kill processes. In this case, we are talking about com.google.android.gms

Root shell is through this library; https://github.com/Stericson/RootShell

If I run in the normal context (ShellContext.NORMAL), nothing works. It spits out denials in the dmesg from both receivers. Both "pm disable" and "dumpsys power" run fine in ShellContext.SYSTEM_APP, but kill requires ShellContext.SYSTEM_SERVER

More detail and easy to check;

In standard android terminal emulator, the following unexpectedly does not work;

$ su -c "dumpsys power"

Can't find service: power

BUT!!!!

$ su --context u:r:system_server:s0 -c "dumpsys power"

...

normal output

...

All of this worked normally under 5.1.

I'm currently working with a Nexus 6, which is more or less bone stock except for your modified ramdisk image and superuser 2.50.
[SuperSU] Chainfire:
I'm running out right now, but before I look at this, I'll need a log of the audits.
[SuperSU] TunedFish:
Su 2.50 works with tibackup. Ex 5.00 also works. Ex 5.01 does not work with tibackup. Check your kernel version.