yashsingh1/xdaforums huggingface dataset:
[SuperSU] mils69:
Factory image worked fine for me...

download appropriate NPC56W...tgz from http://developer.android.com/preview/download.html (angler for me)

fastboot format cache

fastboot flash boot.img

fastboot flash vendor.img

fastboot flash system.img

boot into TWRP

install SuperSU 2.70

Wipe Dalvik, etc

Reboot

Profit
[SuperSU] Bexton:
EDIT: Solved

Which version (of TWRP)? Booting into TWRP 3.0.0-1 (latest) doesn't seem to work for me with the latest build for angler!?
[SuperSU] mils69:
twrp-3.0.0-1-angler.img
[SuperSU] Zlatty:
A restart worked. I've reflashed the stock boot.img so I'm hoping that it will stick this time.

EDIT: Seems that flashing the stock boot.img does not overwrite TWRP. Dang it.

Thanks. So just use flashfire to install it through the zip + ota feature?

---------- Post added at 07:26 PM ---------- Previous post was at 07:24 PM ----------

You encrypted?
[SuperSU] Corvida:
Make sure you have the latest SuperSU already installed (2.70). Then, using the latest version of FlashFire flash the OTA.
[SuperSU] mils69:
Nope (although I learned the hard way when 2.69 didn't actually set to no encrypt). Flashed completely back to 6.0.1 and started over.

Sent from my Nexus 6P
[SuperSU] Zlatty:
Reflashed system and recovery and now am stuck on an error screen. (android /!\) FML

EDIT: Now I get an error:

There's an internal problem with your device. Contact your manufacturer for details.

EDIT 2: vendor.img is culprit. Thanks, Obama. reflashed it and am good to go.

EDIT 3: fastboot boot CF-Auto-Root-angler-angler-nexus6p.img has got be rooted back again.

TL;DR -> Running NPC56W with 2.7 Super SU. Angler and encrypted.
[SuperSU] drewski_1:
Look at the build version

Sent from my Moto X
[SuperSU] :
Seems the OTA is a block level update so I couldn't FlashFire the OTA since I deleted all the system keyboards (except LatinIME) and replaced my NotoColorEmoji font file.

As a general rule of thumb, if you're going to tamper then don't take OTAs
[SuperSU] uraganone:
TWRP will not work (3.000-1) just sits on splash screen. BTW I am on today`s OTA. Any ideas?
[SuperSU] senthilrameshjv:
You are encrypted? Twrp won't work.. Use the cf auto root method.. It will wipe your data if you are not unlocked.
[SuperSU] uraganone:
Running N preview.

I did cf auto, yes I am unlocked. Not encrypted. Running N preview.
[SuperSU] yanleites:
Guys - I think it's best advice:

Wugfresh toolkit -> Boot into temporery recovery TWRP -> ADB sideload unofficial Root http://xdaforums.com/apps/supersu/unofficial-supersu-v2-68-android-n-t3333423 -> Boot -> Sideload this root. (only if you want...)

BTW - Use TWRP 3.0.0.0 !!!
[SuperSU] magnamentis:
i'm encrypted and twrp works flawlessly, can you elaborate what you mean or was it just an error ?
[SuperSU] DDHBanger:
Hmmm. On nexus 6p I get stuck at the Twrp splash screen. Using 3.0.01. When I use 3.0.0 Twrp loads but is unable to decrypt.
[SuperSU] Bexton:
I had the exact same issue. Here's what solved it for me:

NOTE: I'm using 3.0.0-0 here!

adb reboot bootloader
fastboot erase cache
fastboot boot twrp-3.0.0-0-angler.img

- When TWRP asks for a password, click "Cancel"

- Swipe to "Allow modifications"

- Go to "Advanced" > "Adb sideload"

- Check "Clear Dalvik Cache" and "Clear Cache"

adb sideload RC-SuperSU-v2.70-20160314191951.zip

Reboot System. Profit.

No need to decrypt. Just hit "Cancel" on password prompt and proceed via adb sideload as above. Worked fine for me, at least.

Hope it helps.
[SuperSU] Herr der Klinge:
But backup with TWRP is impossible, isn't it?
[SuperSU] yanleites:
If you are encrypted I think it's impossible...
[SuperSU] magnamentis:
i have backups, hence it' not impossible, matter of factly it took no special steps, was working even on first install when recovery somehow didn't stick, which has been solved long since.
[SuperSU] drewski_1:
Depends on the device. Decryption in TWRP is not working on Pixel C
[SuperSU] cocchiararo:
It is only possible if you are unencrypted on N for now.

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] magnamentis:
sure, no device was mentioned in the post i replied to, perhaps i missed it in an earlier post, pixel c is an exception in more than one way, hence

it was not the first coming into my mind, sorry if something evaded me but no matter what, you're right.
[SuperSU] WhammyDroid:
Will systemless SuperSU still work even though this was patched?

http://www.xda-developers.com/xda-e...dragon-vulnerability-that-allows-root-access/
[SuperSU] JimSmith94:
As your link says, the patches were in the February and March security updates. I have both patches on my Nexus 6 and have systemless root with SuperSU 2.70.
[SuperSU] infernape145:
Can't access app which needs root access

i checked with root checker and it says successfully rooted but even then i cant access the root explorer on nexus 6p
[SuperSU] uraganone:
For right now I am giving up on root or TWRP. I have tried everything that I can without bricking the device.

Even with TWRP 3.000 I can boot but i can not adb sideload. I will push through for right now until it gets ironed.
[SuperSU] Evanescent:
SuperSU 2.70 && TWRP 3.0.0.1 on decrypted Nexus 6P on N preview (obviously), apps eg. ES file manager or AdAway can't access in roots directory... waiting for a "patch" :)
[SuperSU] CroW_D:
Just install FX file manager with root Addon. Click on the overflow Buttons right. And Tick Mount read write and BAM you should have access to do what you want !

Gesendet von meinem Nexus 6 mit Tapatalk
[SuperSU] Evanescent:
after did it when i go to /system fx say "Access was denied" and other apps still cant access...

I remounted as READ/WRITE / and /system am I wrong something?

Thank you in advance!
[SuperSU] CroW_D:
Did you install the root Addon from FX ?

Gesendet von meinem Nexus 6 mit Tapatalk
[SuperSU] luckdog:
Encrypted Android N, can get root but never TWRP

I have tried numerous times to with the CF auto root method and while I get root, TWRP never holds, just get the little red android guy. Anyone know how I can get Android N working with root and TWRP starting while on Android N that is encrypted?

THanks,
[SuperSU] Evanescent:
yes, for sure!
[SuperSU] ManikandanGuru:
After flashing 2.70 zip phone is not booting stuck on Google bootloader logo.

Any help?
[SuperSU] yanleites:
http://xdaforums.com/showpost.php?p=65905618&postcount=285

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

http://xdaforums.com/showpost.php?p=65905618&postcount=285

---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------

Try to flash original boot.img
[SuperSU] ManikandanGuru:
Flashed original boot.img still not booting.
[SuperSU] yanleites:
Then the system.img too
[SuperSU] ManikandanGuru:
I am on a secondary rom usig multiROM.

Hope this supersu works in secondary rom

---------- Post added at 07:16 PM ---------- Previous post was at 06:54 PM ----------

Please do any one of you have Android N bootloader only image?

I messed up something.
[SuperSU] uraganone:
Done all of it without success. I am encrypted now. I tried the unofficial method, i tried the official method. Reverted back to stock MM. Got the N update and now I am encrypted. I can not find the solution.
[SuperSU] evildog1:
how about execute su and busybox from sdcard to have semi-root?

don't know if someone have done with that, but it would be great if su looks for busybox in sdcard instead in system
[SuperSU] magnamentis:
flash recovery via "fastboot flash recovery [twrp.img name]" and flash elementalX express version over it.

further flar2 will provide a new permissive.zip for us over the weekend (he scheduled, no guarantee though) which will solve 99% of all the other app related issues, while it is as chainy already stated, the apps should finally be brought up to speed with SELinux policy but the some of the apps are really good and essential and who knows why the devs didn't do that yet. there might be reasons, just to be fair.
[SuperSU] luckdog:
I did flash via fastboot the twmp latest 3001 I believe and it just hangs at the TWRP boot screen. Not sure what elemnetalX express is or where to get it. Thanks for your help, I may just wait until there is a .zip I can flash that does all of this.

Thanks,
[SuperSU] cocchiararo:
Twrp is useless in N if you are encrypted, 3.0.0.0 boots but cant decrypt, 3.0.0.1 hangs at boot screen.

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] parthabhatta:
This is the advise which helped me to flash the SuperSU in my Nexus 5X on my NPC56W. I ran the .bat file in Windows 10 after blocking the bootloader unlock related commands and everything went smoothly.

Thanked RandomPooka.
[SuperSU] magnamentis:
your choice but why asking if then you're not willing to follow advice, try it out, it works

posted already yesterday, my twrp 3.0.0.x stick and works without issues, makes and restores nandroids and survives reboots and all

follow the advice abobe mentined, flash EX kernel and all will be good as to twrp and once we get that permissive zip or follow chainy's advice for a workaround one can get most apps working as expected.
[SuperSU] yanleites:
Sorry
[SuperSU] cocchiararo:
Changing the kernel allows twrp 3.0.0.1 to decrypt? Cool (not gonna use it anyway, but cool for those that need it)

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] yanleites:
I won't be able to make TWRP backup on encrypted phone EVEN with ElementalX, right ?
[SuperSU] zzenyoo:
Please do any one of you have Android N bootloader only image?

Unpack from factory image: http://developer.android.com/preview/download.html#device-preview
[SuperSU] cocchiararo:
He says you will (I have not researched how or why)

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] yanleites:
The problem is you should format usedata to get unencrypted... is that what I have to do with EX or I can flash it and unencrypt without formatting ?
[SuperSU] cocchiararo:
He claimed that elemental x kernel allows you to use twrp with encryption +or so I understand).

He does not say how/why, and I am not gonna investigate[emoji14]

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] magnamentis:
that was quoting the wrong person hence this reply became obsolete, sincere appologies :angel:
[SuperSU] cocchiararo:
I lose/lost nothing, nor do I need anything related.

What I meant, is that I am not gonna investigate about something I don't need or intend to use, but explained what I think you said, cause the guy I was talking to DOES need/want twrp to work on N with encryption enabled, and you said it does with what you mentioned.

Edit:

I am currently back on Android 6.0.1 (but now unencrypted, just for testing). I went back when the W update was not released, cause I needed a fast phone for work, too impatient I guess.

If I were encrypted and needed to use twrp (it's been a while since I flashed it anyway, I only boot it sometimes), I would indeed research about your suggestion, but since it is not the case, I tried to explain/help the other guy with whatever info I had from your posts.

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] yanleites:
OK, So if I flash EX now, my 5X will be UNENCRYPED without formatting userdata ?!
[SuperSU] magnamentis:
i made a few screenshots for you and post the link to the kernel and to the kernel thread. it's the most renown kernel for nexii

and if you want to know more you should address flar2, the developer. he is the man who can elaborate which changes he made

that allow for twrp to stick ( no red triangle )

http://xdaforums.com/nexus-6/orig-development/kernel-elementalx-n6-0-01-alpha-t2954680

http://elementalx.org/devices/nexus-6/
[SuperSU] cocchiararo:
I know flar, I own his kernel app.

Do you still think that I do not believe you?

Cause, if that is the case, you did not provide a screenshot that shows that you are running unencrypted[emoji14]

Help the other guy, he needs help, bit me.

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] magnamentis:
sorry if i mixed something up, i thought the original issue was that twrp does not stick and no nandroids can be made if started to quote the wrong guy it was because it's sounded like the same ongoing conversation. nevertheless i think the input for those having trouble with twrp to stick and to make nands is useful.

so if i understand you now correctly you have another issue, you want to run decrypted. to this i cannot contribute since i changed back to encrypted long ago. so as it seems it was a misunderstanding or even more so, i switched the person i quoted, hence my bad.

---------- Post added at 07:26 PM ---------- Previous post was at 07:21 PM ----------

i removed that post and changed the quote in the post with the screenshots which were wrongly directed at you due to mixing you up with [MENTION=2168067]luckdog[/MENTION] who was the one with the twrp problem, not you. my appologies again for the mixup (lapsus) :o

being subsribed to 23 threads sometimes appears to be a bit much, 7 devices, 18 roms, 3 kernels + xposed LOL
[SuperSU] force70:
Umm,no..why would you assume that?

Kernels do not decrypt, they either force encryption or they do not.

Still have to format first. This is common knowledge.

If I were you I would be doing ALOT of reading before doing anything more with your device.

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[SuperSU] yanleites:
Belive me, I read a lot, and tried a lot... I just hoped EX can make magic ;)
[SuperSU] cocchiararo:
Even if I do not need anything, I did understand that with elemental x, twrp 3.0.0.1 was working on Android N and an encrypted data partition? If not, you quoted the wrong guy, I understood nothing and the user with the issue is totally lost xD

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] drewski_1:
i couldn't get Systemless to work on MM Secondary ROM. i had to use system root. guessing it would be similar for N-Preview

systemless installed fine on Primary
[SuperSU] force70:
Typical tapa app again not showing who I quoted lol...wasnt you. I quote the guy who is totally lost lol

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------

I've yet to see a kernel able to decrypt a device, would be great if I'm wrong though.

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[SuperSU] magnamentis:
hey there, try this in addition to the kernle i recommended, i'm talking about your twrp issue but this should solve more than that. good luck

http://xdaforums.com/showpost.php?p=65932881&postcount=6346
[SuperSU] cocchiararo:
Would be a huge security issue

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] force70:
And its highly unlikely it will ever happen lol.

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[SuperSU] mrsvhtrang:
goo
[SuperSU] johnlgalt:
[MENTION=631273]Chainfire[/MENTION] - Got a question. On a Nexus 6 running the N Preview. I live booted TWRP 3.0.0.1 to get RC 2.70 installed, and it worked. However, after performing a format userdata in fastboot, the phone is no longer rooted and I have to re-flash RC 2.70. Verified this three times.

Is this working as intended, a slight bug, or is something not right with my install of N on this phone?
[SuperSU] milojoseph:
[MENTION=631273]Chainfire[/MENTION] I have a issue with system not mounting to R/w I'm on a note 4 5.1.1 T-Mobile texkdous ROM and I know the RC2.70 was mainly for N preview but I'm just wondering if you can help
[SuperSU] belek1979:
Does RC-SuperSU-v2.70-20160314191951 disable force-encryption?

Nexus 6 with disabled force encryption
[SuperSU] drewski_1:
no. you will need to disable forced encryption through other methods.
[SuperSU] belek1979:
I checked it - SuperSU 2.70 modifies boot and let one stay unencrypted
[SuperSU] drewski_1:
My bad. Assumed since Chainfire runs encrypted, that SuperSU would leave that alone (to however the user set).

Sent from my Moto X
[SuperSU] skvalex:
[MENTION=631273]Chainfire[/MENTION]

Can you add the following policy to the future release, please:

supolicy --live "allow audioserver audioserver process execmem"

This is needed for call recording apps. In the previous versions of Android, all the things related to audio was done from within mediaserver process that already has this policy allowed. Now it's moved to audioserver where it's not allowed by default.
[SuperSU] johnlgalt:
I did the same thing. Took the N Preview, rebooted, encryption on. Flashed RC 2.70, rebooted, encryption on. Formatted userdata, rebooted, encryption off, but root lost. flashed RC 2.70, rebooted, encryption off, rooted. formatted userdata again (testing to see if I lose root), rebooted, encryption off, lost root.

So, yeah, it does allow us to remove the encryption, even if unintentionally.
[SuperSU] drewski_1:
i can see formatting userdata killing root as it probably wipes the /su directory, and, if forced-encryption is disabled, then you re-start with encryption off.

does trying to re-encrypt in the ROM (Settings->Security) fail?
[SuperSU] johnlgalt:
I did not try to re-encrypt. I have the option available to encrypt, but I am using N Preview, and thus I've left it un-encrypted. I bet, though, that the next OTA, if I were to take it, would encrypt the device.
[SuperSU] force70:
Upon reboot yes the stock kernel would force encryption.

I guess the trick in that case would be not to let the device boot into android and fast boot twrp and then the SU zip or something along those lines

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[SuperSU] Strephon Alkhalikoi:
As per mention from [MENTION=631273]Chainfire[/MENTION] in post #1 I tested this on an old tablet running Android 4.0.3. Installed and running perfectly without any apparent issues. Now to test it on my Nexus 6.
[SuperSU] Chainfire:
This is exactly why the supolicy tool exist - so apps can do this themselves if they need to.

Call recording is not basic root functionality, as such it's up to the app to make this call when it first launches, and not for SuperSU to enable by default.

Disabling of forced encryption is quite intentional. Formatting userdata unroots. The two are otherwise unrelated.
[SuperSU] skvalex:
Google doesn't allow to change anything related to SELinux. My app was removed from the Play Store when it used to use supolicy. So I hope you can add this policy.
[SuperSU] Chainfire:
There are many apps in the Play Store that use supolicy. Are you sure you weren't using setenforce ? That seems to be the primary reason for removal ...
[SuperSU] skvalex:
Yes, I'm sure: http://xdaforums.com/showpost.php?p=63627668&postcount=4744
[SuperSU] Chainfire:
Did you previously use setenforce ?
[SuperSU] skvalex:
Yes, but setenforce was removed from the app after the first removal from the Play Store: http://xdaforums.com/showpost.php?p=60276075&postcount=4355
[SuperSU] magnamentis:
that may bit it. i know from other apps, even very renown ones that remaind removed and had to be re-uploaded under a new label (name, package name) to be re-accepted. obviously or as it seems once a package name is flagged in their system there is almost no way to get it back once it was definitely removed. just my 2cts but something into that direction it will be.

should you need more sophisticated input on the matter, contact [MENTION=4684315]flar2[/MENTION] he went through all this and managed successfully to get things back on track.
[SuperSU] SamuriHL:
I thought the su binary was injected into the patched kernel, no? Or is it being stored in the userdata partition? The reason I ask is that I was confused about erasing userdata losing root. I wouldn't have thought that'd be the case if the kernel remained patched. However, if I'm wrong and it's not injecting the files into the patched kernel, then that completely makes sense. Thanks!
[SuperSU] osm0sis:
The ramdisk injection patches the sepolicy and then serves to mount the /su filesystem (containing the su binary, etc.) which is stored as su.img on userdata. The required su files would be too large to cram into many ramdisks.
[SuperSU] SamuriHL:
Got it. Thanks for the explanation. That makes perfect sense.
[SuperSU] JimSmith94:
Not sure if this is a 2.70 problem or not, but as I posted in the StickMount thread, I am getting this error trying to mount OTG:

sush: <stdin>[2]: /system/xbin/supolicy: not found

Supolicy does not exist there, it is in /su/bin/, so could it be that StickMount needs to be re-written to support systemless root? I am running RC-SuperSU-v2.70-20160314191951. I'm afraid that if I move supolicy to /system/xbin, that will make my SU not systemless anymore.
[SuperSU] corkiejp:
Maybe you should have installed busybox to /su/xbin/ to avoid conflicts with system apps.

Stericson Busybox can now be installed to /su/xbin/ as well, but not by default.

Clean up your previous install with @osm0sis installer
[SuperSU] johnlgalt:
Yup, that would probably do the trick. Meaning one would have to manually take an OTA or else manually flash the full system image and then boot right back to the bootloader to flash the SuperSU package.
[SuperSU] JimSmith94:
Thanks, I reinstalled Stericson Busybox Pro to su/xbin/ and that fixed that error message. However, my 128GB card still will not mount, and my 1GB card does. Now I guess it's more of a StickMount issue, so could you please look at my issue in the StickMount thread? http://xdaforums.com/showpost.php?p=65934389&postcount=1266
[SuperSU] devildogwillbur:
worked fine thanks! nexus 6 shamu
[SuperSU] magnamentis:
is TiBu working for you, i mean without warning ?
[SuperSU] devildogwillbur:
I just ran a backup no issues, what are you trying to do that gives a warning?
[SuperSU] Degenerator9000:
On a nexus 6P with the W build, 2.70 didn't work from the flashall.bat for some reason (bootlooped) but I was able to get it on by fastboot flash boot CFAR.img

as soon as TWRP is g2g and I can flash that adaway zip I'll be a happy camper
[SuperSU] Degenerator9000:
I went to the /system (root) file and clicked the lock to mount as read-write but it's still not letting me set up the adaway hosts, any tips?
[SuperSU] Evanescent:
here the same problem, and ES File manager fail the test of root access like the first marshmallow realese
[SuperSU] magnamentis:
backups are working great, restoring data works well, restoring apps+data does not work well and when opening the app it brings up a warning.

EDIT: i'm now permissive and flashing ElementalX kernel solved a few issues, what does not work now is root call blocker ( needs an update, no problem ) and

App restore, also not a big issue since i can install from PS and restore data, was just curious if others have TiBu running without that warning which indicates an issue.
[SuperSU] cocchiararo:
tibu is unable to restore apps (with or without data). What it can't do, basically, is installing or updating apps.
[SuperSU] magnamentis:
why post this again? it restores data for me btw but as you say not apps and not apps + data but data alone YES

which is exactly what i posted above
[SuperSU] cocchiararo:
i opened many tabs and went through the, reading/answering.

This one had as the last post, someone asking about tibu, so i thought it would be helpful to answer.

After i did, many more posts appeared :P
[SuperSU] magnamentis:
ok, perhaps i should add that it's userdata that work for me, system/gapps data i usually avoid restoring from TiBu except gmail and a few that are available in the playstore and version is identical. all good, sorry, my reply was not useful, just was cought by surprise :) :angel:
[SuperSU] Alxoom33:
I'm happy to report that I was finally able to root my Nexus 6 running N preview OTA. Apparently, my earlier attempts to root before 2.69 may have corrupted my System and/or bootloader. Flashed back and retook the N OTA, restored data and rooted in TWRP. Success!:victory::good:

Now rooted, and using EX 4.01 kernel. Modified build.prop with J Rummy's Root Toolkit:svetius:

Busybox Pro doesn't seem to work. Do I need it?
[SuperSU] johnlgalt:
Try changing busybox location to /SU/xbin