yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] doitright:
No. Not correct. This has *nothing* do do with whether the selinux is enforcing or not. If it had anything to do with selinux, it would have to do with the *enforcing* policy in use, being allowed to write to the system partition or not.

Frankly, there is no justifiable reason *for* there to be writes done to the system partition, since we have the ability to bind mount from the userdata partition over the system partition as needed.

At this point, I am not aware of there being any changes to the boot image that would explain different behaviors in something like titanium backup, so it would definitely be premature to just go and build new images in hopes of it fixing something that may-or-may-NOT be broken.

A possible difference that could account for pierre's binaries working differently, is in the policy. He is working on abilities to patch existing binary sepolicy, whereas my work focuses on building EVERYTHING from source. I don't know the exact state right now, but I recall that he had something he labeled as "engineering" configurations, that basically put it permissive or something. That is far less secure than having even a basic enforcing sepolicy, so I wouldn't run that.

If anybody wants me to look at titanium backup, please provide a logcat and dmesg that captures the failure event without the cruft around it (I don't want to filter through however many hours worth of logs there are from before or after the event). Note that I do recall there being problems with titanium backup before, which were due to HACKS added to comply with somebody's binary implementation of root.

Also to be absolutely clear... DO NOT FORGET TO DELETE SOME CRAP from the system partition before you try writing to it!!! I have a strong feeling that the "update" causes people to overwrite their system partition and often *FORGET* to delete crap after they do so. The system partition is FULL.
[Nexus 6  General] JavaTiggy:
I will see if I can get you logs to look into TiBackup. Thanks for all the hard work!
[Nexus 6  General] doitright:
I'm 100% certain that everybody complaining about the writability of /system is experiencing THAT.

I'm 99.9% certain that everybody complaining about titanium backup not working is experiencing THAT.
[Nexus 6  General] doitright:
Make sure you delete a bunch of crap before you try it.
[Nexus 6  General] JavaTiggy:
Are you saying that disabling apps isn't enough? On the last release that is all I did and they are still disabled after my manual flashing of the latest rom

Update: checked my system partition with df in terminal emulator and I have 15MB free
[Nexus 6  General] doitright:
I will not help you further until you increase that to 100 MB.
[Nexus 6  General] JavaTiggy:
Just so i can understand, what exactly is the purpose of needing space in the system partition? I thought the whole point of this was that it is systemless? I didn't have this issue with the first 6.0.1 and I haven't done anything differently.
[Nexus 6  General] JavaTiggy:
Ok well I'd still like to understand exactly why but I have almost 200MB free now
[Nexus 6  General] JavaTiggy:
So I am trying to get you a logcat but I don't exactly know what I am looking for to help you out. Basically TiBackup doesn't crash it just infinitely hangs when you try to restore apps. So I ran a logcat but I can't find anything at a glance in it to cut out for you to read through.

Update: I have a logcat of just the time I started TiBackup, tried to restore, % done hangs and then I force close the app. How would you like me to get you the log?
[Nexus 6  General] doitright:
I said logcat and dmesg/kmsg. How? How about by directing the logs to text files? Clear the log buffers, start capturing logs, do whatever it is that doesn't work, stop the log capture, and put the contents here.
[Nexus 6  General] JavaTiggy:
[MENTION=6124077]doitright[/MENTION] I am attaching logcat and dmesg log files. Let me know if you need anything else to investigate. Thanks.
[Nexus 6  General] doitright:
This is technically a defect in the program you are running.

It is messing around with selinux contexts when it should NOT be.

The reason it is doing this, is to work around a very poor su implementation -- the binary one. It has some serious flaws where rather than defining appropriate contexts that actually have access to the necessary components, it instead expands existing contexts. This is a VERY flawed approach, since it grants that expanded context to things that are supposed to be caged by it.

We had a workaround for this problem, I'm not sure why it isn't working any longer. I'll take a look at it, but no promises. What I would recommend that you do, is file bug reports with the developer of that program.
[Nexus 6  General] JavaTiggy:
Thank you for looking into it, I look forward to what you find. In the mean time I'll file a bug report with TiBackup.
[Nexus 6  General] JavaTiggy:
Any updates on this now that the Feb updates are out?
[Nexus 6  General] doitright:
Unless someone says it is broken, then I'll assume that there is no new issue that must be fixed urgently.

You know that the monthly updates are just a placebo, don't you?
[Nexus 6  General] JavaTiggy:
Didn't you say that you were going to look into why the workaround wasn't working any longer?

I personally prefer to update when there is a new update. Just my preference.
[Nexus 6  General] androcraze:
Did you get a response from your bug report? I'm wondering if TiBU is willing to try and fix this.
[Nexus 6  General] JavaTiggy:
No basically an automated response saying we can't respond to everyone's reports
[Nexus 6  General] androcraze:
That's the ONLY reporting process? Yeah, I'm looking at the website; just a lone email. No tracker. Generic response. No love.

Customer service at its finest.
[Nexus 6  General] Krzysiek_CK:
I used boot-shamu-MMB29Q-su-eng-r177.img (http://superuser.phh.me/nexus/shamu/MMB29Q/boot-shamu-MMB29Q-su-eng-r177.img) and phh's SuperUser (https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en) and I'm still not able to set the System RW permission.
[Nexus 6  General] doitright:
Wrong thread.
[Nexus 6  General] doitright:
Sorry, I've got 2 year old and 3 week old boys at home driving me and my wife out of our minds, hard to get time to work on this.
[Nexus 6  General] JavaTiggy:
I hope you don't think that my response was out of a lack of appreciation for what you have done or even thinking that you need to be working on this all the time because it wasn't. I was just simply checking in because you mentioned you would look into it that is all. If you haven't had a chance yet that is fine, I just thought I would check.

Thanks again for all of your hard work!
[Nexus 6  General] androcraze:
Try PHH's thread:

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
[Nexus 6  General] androcraze:
I'll also point you to PHH's thread. Doing a search for "Titanium", I'm seeing some users reporting luck with Titanium Backup, I believe with the "eng" version of the patch.

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

The biggest issue appears to be the SELinux issue, but again, I think the "eng" patch is very forgiving. This really isn't an issue with either version of the root implementation; rather, it's a program (TiBU) breaking some rules to do what it does do.

I'm using the PHH version right now, and it's working on my N5. I'm NOT running TiBU, however. I just don't see the need; my emails are all synched with GMail, and SMS Backup+ does a great job with SMS messages and call logs. It takes me 15 minutes to backup, and I'm up and running with a new ROM within 30 minutes of hitting the launcher post-install.

FYI: https://github.com/seSuperuser/AOSP-SU-PATCH/issues/1
[Nexus 6  General] doitright:
I don't suggest the "engineering" configuration, it turns selinux OFF.
[Nexus 6  General] androcraze:
""eng" which puts "su" in permissive mode. This is the most compatible mode, but you should trust the apps you give root to. This does NOT put SELinux in permissive mode."

The others (verity, nocrypt) build on "eng". The "user" mode failed with every root app I tried.

What's a guy to do?
[Nexus 6  General] shadowcore:
very interesting, adaway doesnt seem to find that the device is rooted, but I dont have any issues with other apps.

Im running a custom rom.
[Nexus 6  General] androcraze:
http://xdaforums.com/showpost.php?p=64875256&postcount=444
[Nexus 6  General] shadowcore:
Well, I feel stupid now. Just a suggestion. Perhaps it would be good if the OP was modified with a few FAQ and a possible answer to that to the post.
[Nexus 6  General] androcraze:
No need for a FAQ here. DIR and PHH have slightly different approaches, and this is DIR's thread. PHH has a thread at: http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

I think PHH's "user" and DIR's method are the same, or very close. Unfortunately, DIR has been busy and his pre-built images aren't current, so I can't play with his method. But the "user" version (SuperUser in full-enforcing mode) doesn't work with the root apps I use.

BTW, you'll have to use the "AdAway_systemless" zip provided in the first post of that thread, or you may want to try my modified version:

http://www.mediafire.com/download/ta8iav6leamv0be/AdAway-PHH-seSuperUser.zip

The original zip BINDs /system/etc/hosts to /su/etc/hosts; my fix changes it to /data/data/hosts. The only issue is that I have to enter the app, then set the host file location in AdAway's setting to /data/data, exit the app, then return. For either version, you have to patch, then install the app. If you already have the app installed, uninstall it first.
[Nexus 6  General] doitright:
If you are operating in a permissive context, the distinction between whole or part becomes meaningless. It is still permissive.
[Nexus 6  General] phhusson:
If being able to set SELinux to permissive means it is in permissive, your method is also permissive.
[Nexus 6  General] muratturatci:
I've came across this excellent thread while exploring nexus 6 threads. I'm shocked because i've always thought like [MENTION=6124077]doitright[/MENTION] and i'm the only one didn't feel safe about su. The work deserves all the best. I want to use it too. But I'm a Galaxy S5 user and there is no chance to use or port this work (KNOX makes everything worse). What can you suggest me? Is it safe to use older versions of Supersu (versions before sold to strange company). If it is safe wihch version must i use? (My device is SM-G900F stock 4.4.2 rooted Knox 0x0). Thanks in advance.
[Nexus 6  General] androcraze:
You can always check with PHH here:

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

http://superuser.phh.me/
[Nexus 6  General] doitright:
Go try. My policy does NOT allow it to be set permissive.
[Nexus 6  General] phhusson:
Transition to install_recovery domain (allowed by allow su { domain -kernel }:process *; ), write a recovery which writes permissive boot.img and then reboot, reboot to recovery.
[Nexus 6  General] doitright:
.... which requires a reboot.

Edit: but good idea that that should be blocked. No reason for recovery to be installed from running system.

However, if you're going to reboot to get through it, you can fastboot it a heck of a lot easier.
[Nexus 6  General] phhusson:
I can't see how disabling permissive mode for users is a feature.

It is a feature only for rogue apps. They don't have access to fastboot, but with su they can reboot to recovery
[Nexus 6  General] Voight Kampff:
MMB29V

If you are wondering if seSuperuser still works with MMB29V, there's good news. Yes, indeed it does work.
[Nexus 6  General] Shadow53:
Don't know if this is the latest comment on the idea of a flashable zip, but a search doesn't seem to give much more than this, so I'd like to say there are reasons to desire one. I run OmniROM, which resets /system and overwrites the boot partition on every nightly update, and provides a directory to place flashable zips to make system changes for you to be flashed automatically on every update. Without a flashable zip, I'm stuck manually rebooting into recovery after having just booted out of it, flashing boot through TWRP, and rebooting again. Which is a pain.

I've got a flashable zip for the 6.0.1 boot image for that purpose, but there seems to have been a post warning not to post binaries. Not to start that whole argument again, but would it be possible to provide flashable zips in the GitHub repository along with the boot images (or have people download the zip and extract the image) since that is the only place you want to provide binaries?
[Nexus 6  General] AlxMAX:
Although this thread seems to be dedicated to rooting Nexus 6 stock ROMs, I would like to know if the method mentioned in the first messages may be applied to OmniROM at build time.
[Nexus 6  General] jisoo:
If you mean applying the required patches against the source tree and building it yourself, I think it should work. I've done the same for my own AOSP fork and it is working great.
[Nexus 6  General] AlxMAX:
This rooting method still works for the android-6.0.1_r46 release
[Nexus 6  General] drawde40599:
[MENTION=6124077]doitright[/MENTION]

Has this project been abandoned ?
[Nexus 6  General] Shadow53:
I can't say for certain, but I imagine that we haven't heard anything because there's been no changes to be made. I'm still using the 6.0.1 boot image on the 8/30 OMNIRom nightly without issue. We'll hopefully see an update as the 7.0 shamu AOSP source hits.
[Nexus 6  General] drawde40599:
Ahhhhhh I see. The lack of activity made me think it may have been abandoned . I don't like this SuperSu change that happened today and it's time to move on .

Thanks !
[Nexus 6  General] Shadow53:
Incompatible boot image? As long as you have a backup of the stock boot image handy...

Just checked the github. Looks like there in an N boot image for shamu:

https://github.com/seSuperuser/AOSP-SU-PATCH/tree/AOSP-N/bin - don't forget to download Superuser.apk from there too.
[Nexus 6  General] drawde40599:
Ya , I just thought about that . Oh well guess I'll just keep an eye out on this thread .
[Nexus 6  General] Shadow53:
Well like I said, there is an Android N boot image that would be more likely to work with your Android N rom. You can also back up the stock boot image through TWRP just to be safe. You *should* be able to restore it if things get screwed up.

Or you can wait. Not trying to force you either way, just showing your options :p
[Nexus 6  General] drawde40599:
Nah your right . I think I'll wait for the factory img to come out for 7.0 first though so I can completely remove SuperSu that and I'll feel alot more comfortable messing around knowing I have it . I do see that the Dev's are active on GIT so that's nice .

I Appreciate the link

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

Nah your right . I think I'll wait for the factory img to come out for 7.0 first though so I can completely remove SuperSu that and I'll feel alot more comfortable messing around knowing I have it . I do see that the Dev's are active on GIT so that's nice .

I Appreciate the link
[Nexus 6  General] dahawthorne:
I'm very pleased to see that this project is still alive. Yesterday I got a Play Store SuperSU v2.78 update and thought "That's funny, I haven't seen that in XDA" and then read that it's not Chainfire's work (have I got that right...?), so as soon as I see a doitright version that works with Nougat I'll be moving on too.
[Nexus 6  General] Younex:
That "SuperSU Now supports Android N" in the changelog was pretty suspicious... I thought SuperSU worked already with Nougat...

Some people compared 2.78 and 2.77 and it's basically the same app. I'm wondering what could be the reasons of that update.

---------- Post added at 10:20 AM ---------- Previous post was at 10:20 AM ----------

That "SuperSU Now supports Android N" in the changelog was pretty suspicious... I thought SuperSU worked already with Nougat...

Some people compared 2.78 and 2.77 and it's basically the same app. I'm wondering what could be the reasons of that update.
[Nexus 6  General] doitright:
Should work fine with N right now.

I've built images for all current Nexus devices, and am currently using those for Nexus 9 and Nexus Player. Obviously I haven't *tested* the Nexus 6 image, since we don't have a 7.0 sysimage yet, but since the AOSP boot images are working to run the "useless nougat" rom somewhere in this forum, mine should be just fine.
[Nexus 6  General] doitright:
That is a really strange question.

Always check GIT first. If commits are still happening, then you know that it isn't abandoned.

There really isn't a whole lot of reason to continually post in the forum thread.
[Nexus 6  General] drawde40599:
Ok thank you .

I also decided to try your latest Angler boot.img ( I'm assuming it's for N Preview ) with 7.0 (NRD90M) and it got stuck at the Google logo , I figured it wasn't going to boot but worth a try .

Looking forward to trying your Root method here in future .
[Nexus 6  General] doitright:
No. Its for final.
[Nexus 6  General] dahawthorne:
I'm a bit unsettled (perhaps unjustly and unnecessarily) about the change of SuperSU ownership, so my plan is to totally refresh my N6 when Google finally gets round to posting the N final version. Are these instructions still current after a wipe and install?

1) Install the Superuser.apk.

2) fastboot flash boot shamu-N-boot.img.

There are also a couple of comments in the original post on page 1:

"we aren't (yet) authenticating the communications between the android application and the binaries, or validating the application by signature"

Is there any progress on this? It's not a showstopper for me, just asking. I'll pick up from Github, which I guess is properly monitored.

"there are some significant visual glitches in the android application; craigacgomez has been working on fixing up the UI."

Has this been done? When I tried this apk last year it seemed ok - as long as it works I'm not too bothered by fancy glitz... :)

It's great to see this sort of development, so thanks again to doitright.

(I'm sorry if my questions have been answered elsewhere - I couldn't face reading all 50+ pages...)
[Nexus 6  General] zelendel:
Then don't be surprised if/when you get infraction/banned for not following the rules you agreed to when you joined.
[Nexus 6  General] dahawthorne:
Harsh but fair... Understood.
[Nexus 6  General] szale9001:
Hi all, question for [MENTION=6124077]doitright[/MENTION] , or anyone who might know the answer. I installed the superuser.apk and then the custom boot image (Shamu N) and root was working. Now I did this to test it (and it worked great) but ideally I would like to use my own kernel (one I compile locally). So I added the su binary to my ramdisk /sbin along with the daemonsu service at the end of init.rc. Then I copied over the file_contexts.bin and sepolicy from the patched boot image to my ramdisk but after booting up, there is no root. Am I missing something else that is required? Any help would be appreciated. Thanks.
[Nexus 6  General] doitright:
Yep, you are missing most of this patch; https://github.com/seSuperuser/AOSP-SU-PATCH/blob/AOSP-N/system_core.patch which set the file permissions and run restorecon on /sbin.

You should apply the patches to your Android tree, and create the boot image using "make bootimage".

EDIT: you just COPY your zImage that you built into device/moto/shamu-kernel/ and it will be used in the new boot.img.
[Nexus 6  General] wally897:
Has any one done a root with the latest update I'm tired of my original installed apps.
[Nexus 6  General] doitright:
Please keep useless questions out of the thread.
[Nexus 6  General] wally897:
Why useless it's just a question! You could of just said no there is no root for the new update...... Thanks
[Nexus 6  General] Lugia:
Hi everyone.

I currently are a bit confused.

Can anyone point out the correct post where i can find the most recent instructions to root my Nexus 6 (NPD90G).

Ofcourse i have looked in the forums, but i am a bit scared of using any of the instructions mentioned here and there, because of the "latest developments around chainfire etc."

Excuse me in advance if this is an idiotic question to ask, but i was active years ago and last time i rooted was my HTC Hero and DesireHD.
[Nexus 6  General] Shadow53:
The intended method of rooting is to download and install the zip file from http://superuser.phh.me/superuser.zip or download a boot image from the folder relating to your device and update, in this case http://superuser.phh.me/nexus/shamu/NPD90G. You'll likely want to use the eng version, though the first post should have information on what the different versions entail.

I found with Marshmallow that the boot image from GitHub worked with OmniROM while the boot images and zip from the links I provided didn't. As a backup method if the above doesn't work, you might download the shamu boot image from GitHub and flash that. Here's the link: https://github.com/seSuperuser/AOSP-SU-PATCH/tree/AOSP-N/bin
[Nexus 6  General] doitright:
No.

This is open source. The INTENDED way to use it, is to download the source code, and compile it yourself.
[Nexus 6  General] equlog:
Cant apply system_sepolicy patch ?

Enviado desde mi Nexus 7 2013 mediante Tapatalk
[Nexus 6  General] jisoo:
You need to provide a lot more information, if you are hoping for someone to be able to help you
[Nexus 6  General] doitright:
Do you know HOW to apply patches?

I've tested that patch successfully against r3 and r6. It applies cleanly.
[Nexus 6  General] equlog:
Nvm, small error..

Working fine in r6 for bullhead/mako/flo and waiting shamu blobs.

Thanks.
[Nexus 6  General] dahawthorne:
A quick word of thanks to doitright, Craig Gomez & Koushik Dutta, and maybe some info that will encourage others to move over to Superuser from SuperSU. I've been reading again the various concerns raised by doitright and others about the lack of transparency of SuperSU's new owners, and it prompted me to take the leap. I have no specific worries about CCMT, but without knowing why they would spend money on a root app I can't be certain of their motives in buying it. This isn't casting aspersions on CCMT - it's more a reflection of my lifelong cynicism.

I've just upgraded my N6 (finally, after six long and frustrating weeks) to NBD90Z. Although I fully intended to do a full wipe and clean install before installing Superuser, the thought of the hours of reinstalling & reconfiguring (even from app backups) was too miserable a prospect, so I took the lazy way out. I did yet another TWRP backup, stored it on my PC as well as on the phone, and did a SuperSU "full unroot" using the built-in function, followed by a search of the phone for any reference to "SuperSU" and deletions of the few objects I found - a bit Mickey Mouse, maybe, but as I said I'm lazy... :). Then a reboot, install of the Superuser.apk, back into bootloader to flash the N boot image (and flash TWRP again just to save myself the annoyance of maybe discovering that it had somehow disappeared), and rebooted back into Nougat. And everything works perfectly. The different Superuser dialogue box threw me for a moment the first time, but one by one I granted root access to my root apps. It was a much simpler process than I'd hoped for.

So again thank you to doitright, Craig & Koushik (and any other developers involved), and I hope that this will encourage others to adopt Superuser.
[Nexus 6  General] b8842dc0:
Agreed. I've been using the "root done right" option since Marshmallow came out. Very happy. Works great!
[Nexus 6  General] b8842dc0:
[MENTION=6124077]doitright[/MENTION] do you have a copy of the old flounder-6.0.1-boot.img (before your upgrades for N)? I'm needing to apply that boot.img to an Android 6.0.1 install on flounder. The current flounder-N-boot.img doesn't boot with 6.0.1. And the current patch fails to apply on 6.0.1 code. I'd really appreciate it if you could make the older flounder-6.0.1-boot.img available for me somewhere, to get me out of a bind. Thanks!