yashsingh1/xdaforums huggingface dataset:
[SuperSU] magnamentis:
it works for me, need is relative it just proved good to have over the years, never had issues with it but sometimes when not installed.

you have to see that it's installed to the right place, it's mentionen earlier in this thread, i think it's /su/xbin instead of into system which is default

so you have to change install location manually. http://xdaforums.com/showpost.php?p=65990167&postcount=377
[SuperSU] Kombat wombat:
Anyone got any ideas, I flashed the unencrypted android N on mutirom and it works perfect as a second ROM. Until I flash SuperSU 2.70 then it just hangs on the google screen. Any ideas.
[SuperSU] magnamentis:
as far as i know the kernel needs a kexec-patch that allows for multirom to work and it's possible that it's not included. use elementalX kernel

which has this included and all will work well most probably.

further flar2 has a permissive zip available which in the current state of N and apps not yet updated further solved a few issues with certain root apps, mentioning it just in case
[SuperSU] magnamentis:
works flawlessly as usual on Nexus 6, great job ;)
[SuperSU] ohad129:
Done ! I expririence the first random reboot
[SuperSU] yanleites:
Deleted
[SuperSU] Help The Peace:
[MENTION=631273]Chainfire[/MENTION]

What recovery should we use? I didn't understand [MENTION=5201515]Ja_som[/MENTION]'s help...
[SuperSU] Ja_som:
Which part you don´t understand, unzip or run one file?

No recovery needed, only your phone/tablet and PC
[SuperSU] Help The Peace:
Both. What should I unzip and what is TAP?
[SuperSU] Ja_som:
I edited my post from "tap" to "run" ;)

Unzip file for your device from first post...
[SuperSU] Help The Peace:
That didn't help me much more. But reading Chainfire's post fully did, lol.

"But as TWRP isn't working yet on all N Preview (...)" ??
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] great work ;) , but I have few issues on my N5X.

I can´t install busybox and AdAway, and I can´t write to system with TotalCommander, but I can uninstall system apps with Titanium Backup, also some other root apps can work without any issue.

If I can help you somehow more, let me know ;)
[SuperSU] Yahfar:
I'm getting this error.

downloading 'boot.img'...

FAILED (command write failed (Unknown error))

finished. total time: 5.003s
[SuperSU] yanleites:
+1

Adaway can't update hosts and ES file explorer cannot reach /system

---------- Post added at 09:14 PM ---------- Previous post was at 09:08 PM ----------

@Chainfire, after flashing your root, phone became ENCRYPTED and I cannot access the /system from TWRP or ES.
[SuperSU] Younex:
Downloading now (flounder) awesome work ! :good:
[SuperSU] Help The Peace:
Lol? How? That's actually not possible...
[SuperSU] stangri:
Flashed 2.69 from TWRP 3.0.0.1 on Nexus 6 (shamu), rebooted, TiBu and double-tap to wake app successfully gained root. Rebooted back into TWRP 3.0.0.1, mounted system partition and deleted some crap from /system/app just fine thru adb shell. So it works on N6 at least. Good luck with your 5X.
[SuperSU] yanleites:
I was not encrypted, flashed original boot.img, then flashed SuperSU.
[SuperSU] Linux23:
Ok, thanks. Will give this a shot.
[SuperSU] flar2:
Google is getting very restrictive with N, regular apps basically can't read anything in sysfs (there are a few exceptions like sysfs_devices_system_cpu)

Of course, apps can read and write with su shell, but that's no good for non-root apps. Things in sysfs weren't writable before, and I wouldn't expect them to be, but at least they were readable.
[SuperSU] Freak07:
The boot.img from the official dev preview will encrypt your device. You have to search for a boot.img that has disabled forced encryption.
[SuperSU] suphan95:
as I understand it, you must not use any TWRP, but only the files you posted. right?
[SuperSU] OmegaBlaze:
2.69 works on Nexus 6p, however, my phone is now encrypted.

I thought flashing the supersu.zip was supposed to solve this by patching the boot.img?
[SuperSU] Kombat wombat:
Wow thanks, I'll grab the elementalx kernal now. Is there a specific one for N, also do you have a link to the permissive zip. Many thanks.
[SuperSU] magnamentis:
yes there is, it's v4.01 explicitly made for N-Preview. the link to the zip is in the thread, just search for "permissive.zip" further you might find it on flar2's download page (linked from the OP) but certainly with search function, it's relatively new, hence will pop up relative high up in the search result. i don't have the link handy else i would paste it here of course :highfive:
[SuperSU] Kombat wombat:
Ah sadly I just tried again with the kernal and zip and still hangs :(.
[SuperSU] magnamentis:
do you think it's possible that some changes made in N just doesn't make it compatible to share stuff on the same partitions?

i basically gave up on multirom long ago, too many restrictions for my gusto (recovery for one) and i went to swap nandroids. totally safe, all is totally independent and then it takes exactly 3-5 minutes longer :)
[SuperSU] Kombat wombat:
To be honest I'm not sure what the issue is, works fine without root, but at as soon as I flash it bang it hangs. Really odd. Mutirom has come along way.
[SuperSU] magnamentis:
ahh... ok that hints to another reason than i suspected, hence can't say more, too long since but certainly there are a few guys switching back and forth and hopefully you'll get an answer or even better a solution.:cool:
[SuperSU] Kombat wombat:
I appreciate the help. I would run N as my main ROM, sadly I need root and tibu, as all my work rotas are on there ect. :(

---------- Post added at 04:00 PM ---------- Previous post was at 04:00 PM ----------

If it helps this is where I got the ROM from.

http://itechify.com/2016/03/22/run-android-n-secondary-rom-android/
[SuperSU] magnamentis:
same here root a have but a few root apps need to be updated, still nice to look a bit ahead in time and get a feel :)
[SuperSU] Kombat wombat:
Yeah can't argue with that maybe I'll flash it as second ROM but leave it unrooted.
[SuperSU] Chainfire:
Please, this is not a slow-chat.
[SuperSU] magnamentis:
sorry you're right we got drawn away, will pay more attention. :angel:
[SuperSU] Alxoom33:
I actually have Busybox Pro. So su/bin is my default location. I also tried su/xbin with no luck.

Edit: Tried again, this time it installed. Thanks :}

---------- Post added at 11:21 AM ---------- Previous post was at 11:18 AM ----------

As mentioned above, my default is su/bin, I tried changing to su/xbin with similar fail; but just tried again and miraculously, this time it worked.

Thanks, :=}

Now, if I could just root my Pixel...
[SuperSU] magnamentis:
i could swear that it worked after a reboot. all such tasks should be followed by a reboot, there are so many things which only works after rebooting.
[SuperSU] Alxoom33:
Yes, Reeboot=Magical cure!
[SuperSU] Didgeridoohan:
Just reporting in that 2.70 works without major problems on Nexus 6, 6.0.1 build MMB29V, Franco Kernel.

Only problem I've had (and this was also true for 2.68) is that granting permissions was delayed by about 1 minute and after that minute a long string of splash messages would declare that permissions were granted for different apps (qued requests). This was remedied by installing Busybox (su/xbin). No such problems on 2.67.
[SuperSU] johnlgalt:
[MENTION=631273]Chainfire[/MENTION] - would this be a reason to use the setting to enable su during boot? Or is this setting for pre-OS UI?

If this is after UI load, my understanding about this setting is that, if enabled, there will be no prompt(s) during the boot process, correct?
[SuperSU] Didgeridoohan:
It was not only during boot... Every time an app would request permission. Very annoying.
[SuperSU] artikle:
Guys, on my 6P with N preview (W) most apps are unable to get proper root access. I get toasts saying they were granted root permissions but the apps fail their own root check and say root access not available. Apps like GMD Gesture Control, ES File EXplorer, AdAway etc. Rootchecker shows root is available. Could someone help me out here. Thanks.
[SuperSU] magnamentis:
just search this thread and read, it's not so many pages and has been addressed in detail, at least up to the current state.
[SuperSU] Chainfire:
Does this persist after a reboot ?

It's not uncommon for this to happen after first install, the first boot. If it doesn't clear up, something is wrong, though.
[SuperSU] artikle:
I have read most of the thread and have tried various things suggested by people in the thread but to no avail. The last time a similar issue was discussed in the thread was several days ago and there was no solution then, so was wondering if there anyone figured out anything. Thank you.
[SuperSU] magnamentis:
nothing has changed over the last few days and mostly it's the apps that have to be updated, was last mentioned about 1-2 pages back and is state of the art :)
[SuperSU] Didgeridoohan:
It did persist across a reboot, both on 2.68 and 2.70. I won't have much time for tinkering until next week, but I'll try to replicate and grab some logs when I get an opportunity.
[SuperSU] fmc000:
This version seems to work fine on my OPO running SlimSaber (6.0.1) . Only nitpick, looking at the logs:

- Flashing boot image
dd: writing '/dev/block/mmcblk0p7': No space left on device
4097+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 0.040466 seconds, 395.4MB/s
1821+0 records in
1821+0 records out
7458816 bytes (7.1MB) copied, 0.131281 seconds, 54.2MB/s

[MENTION=631273]Chainfire[/MENTION] : Should I worry about it? The system has booted after the update and root seems to work fine.
[SuperSU] drewski_1:
Systemless has not worked for me on Secondary MM ROMs with Multirom. Sounds like the issue carried over to N-preview.

in the Secondary ROM try creating a text file "/data/.supersu" and put "SYSTEMLESS=false" into it and see if that helps.
[SuperSU] urgali:
Flashed on OnePlus Two + Resurrection Remix rom and it's working with no issues at all.

I'm on twrp 3.0.0-2 and i'm even using xposed
[SuperSU] skvalex:
If Google didn't remove them yet, it doesn't mean they don't violate the rules. It's clearly said:

setenforce disables SELinux, supolicy modifies. Both are not allowed. Am I wrong?

My app was removed twice. The first time it was in April 2015 for using setenforce, the second time Google removed it in November 2015 for using supolicy. So the app was running with supolicy for about 7 months. I made about 20 updates for that period.

Can you consider adding the required policy to SuperSU?

supolicy --live "allow audioserver audioserver process execmem"
[SuperSU] jwds1978:
I've been using this (RC-SuperSU-v2.70-20160314191951) on my Note 3 (SM-N900W8) with Android 5.0, without any apparent issue, except for one. The only thing that I've noticed, is that the Logs tab within the UI is always empty; no logs are being shown. Other than that though, I've noticed no problems.
[SuperSU] Chainfire:
Unlike setenforce, supolicy isn't a standard command. It does nothing unless you are also running SuperSU.

There have been reasons to believe the setenforce thing is detected by a text scan of the decompiled APK, as someone got an app removed containing the string but the app never actually executed it.

As has been stated before, others have also had the experience that once their app was flagged, it kept being flagged, regardless of the issue being fixed or not.

I am not happy structurally opening a hole for everyone for this, nor am I convinced it will get your app off of Google's ****list.
[SuperSU] Chainfire:
N Preview RC BETA's have been rolled into the normal BETA releases. Continue in the BETA thread.

CLOSED
[SuperSU] mils69:
Same thing happened to me on an N6P

Re-flashed boot.img (via fastboot)

Re-flashed system.img

Flashed 2.69 using TWRP 3.0.0.1

Wipe Cache/Dalvik

Rebooted

Noticed it had started encryption
[SuperSU] yanleites:
I just flashed the Unofficial 2.68 :)

And stayed encrypted.

Are you still encrypted ?
[SuperSU] zocex:
how can i flash this?
[SuperSU] yanleites:
What exactly ?
[SuperSU] Help The Peace:
Yeah, okay... Right. It is possible, lol.
[SuperSU] snowrelyt:
Same here..
[SuperSU] gammaxgoblin:
CTAR for shamu failed to run in twrp 3...flashed 2.69, rooted. tibu, rom toolbox asked and granted su access. layers manager wont run ( sadface)...i know thats not a CF issue! TY
[SuperSU] ktimque:
Flashed in multiom over preview as secondary ROM, N6 shamu, stuck at Google logo and I can't get past it
[SuperSU] Andriy2:
You are someone like a God!

(though I have Nexus 5)
[SuperSU] bagarwa:
That's what I came here to search. That's how the 2.68 works on M. Stock M's boot.img will encrypt the device. So, after flashing stock boot.img, I boot into twrp and flash SuperSu 2.68 and then reboot system. SuperSu patches the boot.img and prevents phone from becoming encrypted.

Is that not the case with N and SuperSu v2.69?
[SuperSU] yanleites:
Check it out:

http://xdaforums.com/apps/supersu/unofficial-supersu-v2-68-android-n-t3333423

It has an option to remove the encryption
[SuperSU] bagarwa:
Thanks for the link but I would rather wait for an official update from chainfire than flash a root zip from an unknown dev.
[SuperSU] yanleites:
You are right, but for now the unofficial works better on 5X !
[SuperSU] Chainfire:
I'm not sure what is going on with encryption, on my own devices I always run encrypted so I hadn't noticed, but I'll look into it at some point.

If you're having trouble with apps that write to system, it's because N Preview's toybox mount implementation is complete and utter ****e. It appears to be even worse than Marshmallow's toybox mount implementation. To add some more insult, they actually removed toolbox's mount applet, so you can't use that either. Apps that have an internal copy of busybox will not have these issues.
[SuperSU] yanleites:
OK Master :)

So can you make (of course you can) a "busy box" integrated for Nexus 5X, and how do you mange with encrypted phone ? Backup\Restore.....
[SuperSU] minieod:
let me rephrase then. using your new supersu version on a nexus 6p, does anyone have a clue how to get it working in harmony with a boot image and twrp? like others have stated, using the stock boot.img and supersu 2.69 has been forcing encryption to start and causing issues. others have been locked out of twrp.

or is it just a waiting game at this point for twrp to update and fully support N dev previews?
[SuperSU] mikereidis:
CF-Auto-Root works fine on Nexus 6p and Nexus 9.

Was fully stock and encrypted.

I see "setenforce 0" reboots the device into a "Safe Mode" without access to 3rd party apps, :)
[SuperSU] dgk823:
No R/W access. Adaway gets root permission bit when applying the hosts file it fails. I hope this get resolved. Thank you Developer for your hard work. Nexus 6, Android N Preview / TWRP 3.0.0.1
[SuperSU] Zer0_Cool:
Thanks for the heads up, adblock is really the only reason I still want proper root now that I can scale down the dpi as a stock feature in N. Running the preview for the last few days made me REALLY appreciate ad blocking, web browsing absolutely sucks without it.
[SuperSU] Zlatty:
Just to make sure I'm on the same page, flash the new TWRP and then flash the WIP Super Su through the new TWRP?

Got it working finally!!

On Nexus 6P TWRP 3.0.0-1 does not seem to work. It is stuck on the decrypting screen. What I did to get roo installed:

Extract CF-Auto-Root-angler-angler-nexus6p.img from the zip, then fastboot boot CF-Auto-Root-angler-angler-nexus6p.img

The phone rebooted three times, and now I'm rocking some root.
[SuperSU] dgk823:
Same here, I'm so spoiled. I can't stand the ugly terrible ads. I've noticed that even on xda+-developers.com, it takes an extra 8 seconds to fully load ads. I hope proper r/w is resolved soon. ES File exporer cannot access my system directory.
[SuperSU] Zlatty:
Ads are cancer ruining the mobile experience. We should have a fix soon and get adbock working soon.
[SuperSU] Alxoom33:
Bump, please...:silly:

Thank you [MENTION=631273]Chainfire[/MENTION]! Does this root method reside in the System Partition, or is it Systemless. Also, do we need to type in adb commands in TWRP before installing to force Systemless installation?

Thank you again:laugh:
[SuperSU] dtroup64:
So I'm probably doing something obviously wrong... but I've now tried flashing this on Stock N three times, with three different downloads (to make sure it wasn't a bad download)... I'm on Shamu...I keep getting this error in TWRP: cannot find meta-inf/com/google/android/update-binary in the zip

help anyone?
[SuperSU] SageWilliams:
Same here as well
[SuperSU] RandomPooka:
So it *IS* possible to get TWRP 3.0.0-1 and N working together? Do you need to reboot to recovery immediately after pushing the system images to the device and allow TWRP to protect itself before booting into N? Or can you reboot to bootloader and fastboot it at your leisure after setting up N?

--- addendum ---

Was TWRP not booting for me a few days ago because the new bootloader is not OEM unlocked? If it's that stupidly simple, I'm going to feel like a complete knob of a noob. Please assure me that I'm an idiot.

Is it possible to set up the sysfs to be writeable by changing permissions in either recovery or with a file manager app that has the ability to modify the system? It isn't exactly like we have to worry about being eligible for OTA if we can fastboot the updated N images when the next preview drops

From what I've been reading and by looking at the contents of the zip files in the OP, you are correct. This is a PC tool to be used while your phone is connected via USB cable. It will do some pull/push/patch/replace gypsy magic to get a bootloader on your device that works with SuperSU.

I'm curious about the first legit commands in the root-linux.sh file. They appear to be bootloader unlock commands (which is why I added to the first quote above)

[MENTION=631273]Chainfire[/MENTION] - Am I to take it that using this image will wipe my userdata (To be expected), and also my external SD? I want to make sure that I have full backups of the SD, if that's the case. I'd hate to accidentally waste out my nandroid of PureNexus on shamu, or my TiBu saves, because I wasn't paying close attention.

---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------

It isn't a flashable zip. It's a tool you run from your PC with your phone connected.
[SuperSU] Zer0_Cool:
I can confirm that RC-SuperSU-v2.69-20160313161431.zip from the OP can be flashed with twrp-3.0.0-1 on the Nexus 6.

On a clean install of N, I flashed twrp-3.0.0-1, rebooted straight to recovery to patch the system from overwriting it, then flashed the SuperSU-v2.69. Like chainfire said, there are some issues with apps writing to /system, specifically AdAway.
[SuperSU] dtroup64:
Hence the CF-Auto root at the beginning of the Zip... I'm a completely moron.

Thanks!
[SuperSU] Zer0_Cool:
I have adaway working on my device

http://xdaforums.com/showthread.php?t=2190753

​
[SuperSU] sauntimo:
I was getting this error too when I ran root-windows.bat, however when I manually booted the image from fastboot it was fine.

fastboot boot c:\path\to\stuff\CF-Auto-Root-shamu-shamu-nexus6-NPC56P\image\CF-Auto-Root-shamu-shamu-nexus6.img

Hope that's helpful!
[SuperSU] dgk823:
This worked for Adaway, THANK YOU!!
[SuperSU] snowrelyt:
I'm running the batch file in bootloader mode, that's what's giving me the error.
[SuperSU] jcrompton:
Any ideas on how I can get M to boot from secondary after flashing this 2.69 SuperSU? I got the ROM to boot nicely with the unencrypted version of the not image ..... But no root
[SuperSU] RandomPooka:
Just to be sure I'm not missing anything here coming from PureNexus ..

Reboot to TWRP 3.0.0-1 and perform nandroid backup

Wipe all (except my SDcard containing pics, downloads, and such)

reboot to bootloader

fastboot flash bootloader and modem from N preview zip

reboot to bootloader again

fastboot flash system.img and boot.img (and optionally cache, userdata? I'm assuming that the wipe in TWRP would be sufficient)

fastboot flash TWRP in this same session

reboot to recovery immediately to allow self-protection

reboot to ROM and run the CF auto-root script (Will this wipe my sdcard, or leave it alone?)

--OR--

reboot to bootloader AGAIN and run: fastboot boot image\CF-Auto-Root-shamu-shamu-nexus6.img (with the proper path to the image, of course)

Am I making this needlessly complicated? Do I need to unlock the device again to flash TWRP on the updated bootloader? If it isn't painfully obvious, I'm concerned that my internal SD is gonna get blasted, but I really don't want to take forever backing it up if it ISN'T going to be at risk
[SuperSU] cocchiararo:
if i am not mistaken, what is happening is that either from sometime before, or from when they started using the N preview, people used those alternative methods that remove the enforce encription, and for some reason thought that supersu did that.

as far as i know, you never removed that, or did you?
[SuperSU] gammaxgoblin:
what does CFAR do that flashing the SU zip in twrp does not?
[SuperSU] Zer0_Cool:
Edit: No you do not need to re-unlock your bootloader. Once you unlock the bootloader, it stays unlocked, even after updating to a newer version. You need to explicitly use fastboot to re-lock it, that is the only way to the best of my knowledge, and I would highly suggest never doing so, as you're stuck without recourse if certain software issues arise.

Yes, you are making it needlessly complicated. I am comfortable with fastboot and didn't need to preserve any data on my phone (I use google photos to back up pictures and stream music with play music), so I like a fresh start. I cannot speak for trying to preserve data, to ensure everything works properly

I would recommend flashing all the images from the preview which will wipe your device and sd.

Here is how I would do it, start to finish, on the Nexus 6 (I'm not sure if TWRP plays nice on N with other devices yet):

Download the factory image tar.gz and check the md5sum to ensure the download was not corrupted. Extract all the files and put them in the platform-tools directory of your android sdk. Fire up your terminal.

Downloads required:

N Factory Images for Nexus 6

http://developer.android.com/preview/download.html#top

TWRP 3.0.0-1

https://dl.twrp.me/shamu/twrp-3.0.0-1-shamu.img.html

SuperSU Recovery flashable .zip

https://download.chainfire.eu/926/SuperSU/RC-SuperSU-v2.69-20160313161431.zip

adb reboot bootloader

fastboot devices

(make sure that fastboot recognizes your device)

fastboot flash bootloader bootloader-shamu-moto-apq8084-71.16.img

fastboot reboot-bootloader

fastboot flash radio radio-shamu-d4.01-9625-05.34+fsg-9625-02.111.img

fastboot reboot-bootloader

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash boot boot.img

fastboot flash recovery twrp-3.0.0-1-shamu.img

fastboot erase cache

fastboot flash cache cache.img

reboot to recovery (I use the hardware keys)

Swipe to allow TWRP to patch the system to prevent the recovery from being written over

Now you can either adb push the SuperSU recovery flashable zip, or boot the phone up and download it or drag and drop it to your internal storage.

Then,

using TWRP,

flash RC-SuperSU-v2.69-20160313161431.zip with the recovery just like you would any other ROM and reboot. Done.

I have no experience using the autoroot programs, this method avoids that.
[SuperSU] mAineAc:
Holy ****. I had to enable OEM unlock to install. Went through installation and rebooted and everything just like it was before. No wipe. This is awesome and rooted as expected. Everything works.
[SuperSU] jcrompton:
No ideas how to make this boot after flashing in multirom secondary slot?
[SuperSU] osm0sis:
Working great on my N5 on the latest stock Marshmallow. :good: :)
[SuperSU] Zlatty:
How can you get this to work. My TWRP does not seem to stick.