yashsingh1/xdaforums huggingface dataset:
[SuperSU] cocchiararo:
I flashed that (i booted twrp 3.0.0.0 with "fastboot boot twrp3.0.0.0.img",canceled the decryption password prompt, chose to keep /system readonly, and started adb sideload).

Flashed that zip, installed the newest adaway, and still, copying the hosts file failes.

could you provide me steps?

I have installed the N preview and the latest chainfire cfautoroot.
[SuperSU] Zer0_Cool:
You need to follow the proper flashing instructions from their website.

adb reboot bootloader

You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:

fastboot flash recovery twrp.img

fastboot reboot

Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
[SuperSU] Shanmukarajan:
Thanks for the First... One Doubt as a follower..

Assume If i root my Nexus 5x with Android N developer Preview, then i returned to my Factory Version, i mean flashed Stock Rom.

Does my Root Counter will changed to 0 ?

Can i receive Software Updates..

In another case, I rooted my Nexus 5X in Stock Rom..

So i re-flashed it with my Stock Rom. Will i be able to receive S/W Updates..

Thanks in advance..
[SuperSU] captainphoenixx:
Worked like a dream on N6P OTA N. Now that there is root, can flashfire flash TWRP?
[SuperSU] Darian71:
Doesn't seem to work on my 6p sir. I see others have had luck with the OTA however. I relfashed the entire preview image, tried with CFAR, with Super Su zip in TWRP and even extracted and fastboot flashed your image. At first try the phone loops as you stated it would, then goes off and stays off. On second attempt it loops, the makes it to the animation screen but no boot after 20 minutes. I believe it's close, just something not working with that new boot.img. I''ve been trying on and off with different boot.img from MCH and V but to no avail. Lol. Thanks so muich for your work!!

---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------

Hmmm. Interesting. I can't for the life of me get it to work on my 6p flashing the preview image. Wonder what is different with the OTA. Thanks for sharing
[SuperSU] stangri:
The latter -- I don't like custom recoveries flashed anymore (fewer things to reflash when it's OTA time) so I've done:

adb reboot bootloader

fastboot boot twrp-3.0.0-1-shamu.img

Once in recovery I flashed supersu from OP and cleaned cache/dalvik as per TWRP's suggestion.

I don't have my phone handy to check, but I believe it's been encrypted since day 1 of MM and is encrypted still.
[SuperSU] KenjiHannya:
Tnx ????
[SuperSU] killmastern3:
Flashed this on N6. Root seems to be working but titanium backup doesn't restore any apps. Just stuck at restoring. Any suggestions?
[SuperSU] :
i might be able to help you and maybe some others,

First, TWRP does work for some and doesnt for rest. for me, i just flashed it after flashing the whole N preview (after wipe) and it just worked with no issues. some say it will eventually work if you have reboot or bootloops, you just have to let it run for few minutes.

Second, if twrp doesnt work at all you can download the autoroot file for your device from the attached files in op TO YOUR COMPUTER and unzip it, boot your device into fastboot mode and run the .bat file on your computer (just like you do with the flash-all.bat inside the images provided by google) and it will flash all the necessary files. the difference is that this way it will delete your whole userdata partition !!!

hope that helps clear things up.
[SuperSU] Ja_som:
It will not, if bootloader is already unlocked. If is locked, then it will delete userdata...

TWRP does not work on N5X (encrypted), maybe on other devices it works...
[SuperSU] zzenyoo:
AdGuard? Works for me (different methods of filtering).
[SuperSU] mrbabyman:
Anyone out there looking for detailed tutorial to root Android N Preview
[SuperSU] bombadier:
I know the focus here is on N but just wanting to say 2.69 working fine on slimsaber 5.1.1 bacon

Tapatyping fae the bacon
[SuperSU] RandomPooka:
I'm quite comfortable with fastboot as well. My main concern was that the oem unlock commands in the CF autoroot script were going to wipe my SD. I was planning on using fastboot to push the .img files to the phone manually, because I didn't want the N preview's flash-all.sh doing a wipe with its -w flag. Not sure why Google feels the need to delete your SDcard with updates and the original OEM unlock, but whatever for them :)

I don't need a pristine or unmodified /system for any apps and don't take OTAs (usually I'm on a custom user built ROM), so I prefer to have the custom recovery available on demand without the PC. If there were a way to trigger that "fastboot boot twrp.img" from the phone with no PC involved, that would be awesome. I imagine that many a user would just keep their recovery on the SD and use it when necessary. Especially useful for secuirty when anyone that knows the key combination could boot into TWRP and get data over USB that would normally require you to unlock the phone and select the file transfer USB.

Have you tried installing apps from the store and just restoring the app data with TWRP? In the case of an app that was originally sideloaded, you could pull the APK from the TiBu apk.gz files that are in your sdcard's TitaniumBackup directory and try installing them manually before restoring their data. Sounds like it would work, as long as you have is set to allow app installs from "Unknown Sources".

I'm rather confused about why you linked to that article in the actual developer thread for the tools it referenced. Anyone who is already here can get more detailed information from the first few pages of posts than the article provides. You might do better to post it in the General Nexus 6 threads instead.
[SuperSU] magnamentis:
perhaps it was answered and i missed it, in my case it's systemless which causes some apps to misbehave but then perhaps that was the only way how to get root that quickly or perhaps it is the only way at all. things will settle soon and we'll know, i personally prefer system root, it has better compatibility or in other words, less apps make trouble with system root, tired systemless several times and always reverted back quickly, even though systemless might well be the only possible future, depending how even more restrictive thing will get.
[SuperSU] Chainfire:
Re: encryption

The next release will allow you to run unencrypted. Problem is found and fixed.

Re: apps not being able to write to /system

The next release partially mitigates this. It depends on how the app remounts /system as writable.

The mount command on N is pretty broken. Modifying the fstab to have read-only mounts use noatime instead of relatime allows some common forms of the mount command's usage to work.

It will probably not fix all apps, but it'll fix some.

Re: TWRP

TWRP only dies for me in encrypted mode. After removing encryption, TWRP works fine.

Re: CF-Auto-Root wiping ( [MENTION=3053466]RandomPooka[/MENTION] )

This only happens if your device's bootloader is locked. The unlock process triggers the wipe. With an unlocked bootloader, no wipe happens.

Re: testing on pre-N ( [MENTION=2714876]bombadier[/MENTION] )

This is actually useful for me to know.
[SuperSU] Chainfire:
SuperSU is always systemless by default on Samsing/5.1+ and everyone/6.0+

It might be useful if you post which apps are still being difficult to the BETA thread.
[SuperSU] cocchiararo:
Is there a "systemless" busybox app ? I have always used the "busybox pro" I bought, but[emoji14]

Edit: install to /su/bin

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] osm0sis:
Install to /su/xbin or it will break a lot of stuff.
[SuperSU] Help The Peace:
You are not quite right with that. It will JUST delete your data IF you have a locked bootloader. And I already flashed it that way, thank you[emoji14]
[SuperSU] magnamentis:
hope i got this right, else guide me for better input

ok, no problem to mentione the apps, let me know if you want logs, either kind logcats as well as kernel logs can be provided should you

prefer them over screenshots & simply explaining as i did below. many of those issues may require the app to be updated which is why i did not

report in detail before. didn't want to get OT or imply that it's root related.

apps with issues are:

- TiBu comes up with an error message about libraries

- TiBu does not restore system apps but has no problems to restore app data for user apps as well as accounts, gmail etc.

- Root Call Blocker is crashing (screenshot provided)

- BatteryMonitorWidget Pro cannot install helper app into system which would be necessary to provide proper statistics (screenshot provided)

- LMT opens and can be switched on but crashes thereafter

- SD Maid Pro same like LMT, opens and once scanning is activated will crash when it arrives on the app-cleaner and/or the database part

- Secure Settings

"System+"

tab cannot be activated, says it cannot acquire root which (screenshot provided)

- Terminal Emulator in

"Rom-Toolbox Pro"

app keeps crashing while "root browser of that app works unlike other root file browsers (screenshot provided)

- SELinux Mode Changer can't acquire root (screenshot provided)

- Layers app won't open after root has been granted and closes thereafter (screenshot provided)

- busy box on stock kernel could not be installed, now is installed after flashing elementalX kernel by [MENTION=4684315]flar2[/MENTION] [solved]

finally a bit of less specific observation that once some "working" root apps are open, there is a lag to use the navbar, i.e. to open recents, that's not very useful info

but who knows, else let me know what else you need to narrow this down
[SuperSU] Fvolfrine:
I'm with you on this one. Encrypted from day 1, no real desire to unencrypt. And I don't want the custom recovery installed, just booted from fastboot to flash zips. Too tedious to have to flash new roms every time an OTA is released.

Speaking of OTAs, back on Page 2 [MENTION=6095845]Help The Peace[/MENTION] asked about receiving OTAs after rooting, and then [MENTION=6345368]Displax[/MENTION] answered by saying these are full system images. But it is my understanding that by signing up for the N Dev program, we will receive OTAs for each new iteration. So if this is true, will we be able to install these OTAs if rooted?
[SuperSU] cocchiararo:
Is there a versión of twrp that can be booted but not flashed that will decrypt /data?

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] killmastern3:
Flashed the supersu v2.68 and restore worked fine. Needed v2.68 to make elite kernel to work too.
[SuperSU] elreydenj:
Elemental X kernel was updated to work with Android N?
[SuperSU] snowrelyt:
There's a 4.0 preview out right now
[SuperSU] magnamentis:
yes, obviously and it solved at least the busy box not installing issue, i have now stericson's busy box pro running as always.

you could head over to the nexus 6 elementalX thread where you will find the download link for an express version, didn't see an aroma version yet, hence it will

use you existing setup without issues.
[SuperSU] ohad129:
Link found thx
[SuperSU] elreydenj:
Thank you. I am using the 6P. Im sure hell have an N test build out for that device shortly.
[SuperSU] spupuz:
can be wise to not flash that on non N preview?
[SuperSU] zzenyoo:
- busy box on stock kernel could not be installed, now is installed after flashing elementalX kernel by [MENTION=4684315]flar2[/MENTION] [solved]

Busy Box Free installed successfully. N6, stock kernel, su/xbin
[SuperSU] magnamentis:
probably you're just right, when i tried i was not aware that i have systemless root (not used to it yet) and had i tried to install into su/xbin it would have worked most probably :) thanks for mentioning it, this will help to increase awareness.
[SuperSU] Zlatty:
Yup. That's how you get TWRP. Except that if you are encrypted TWRP 3.0.0-1 on 6P gets stuck on the decryption screen. I want to know if there is a way to not have to go through TWRP to get adaway to work on N preview. It looks like that the next update from Mr. Chainfire will address the issue with the currently installed AdAway.
[SuperSU] boxcar8028:
Just updated my stock N7 2013 and my N6p to SU-v2.69 this weekend with no issues. All is smooth and stable. All rooted apps are running fine.

Thanks for the update Chainfire, GREAT JOB! :good::good::good:
[SuperSU] Chainfire:
You should use:

supolicy --live "permissive *"

instead. However, this is currently broken. It'll work again next update, though.
[SuperSU] parthabhatta:
Notable to root Nexus 5X. Flashed original boot.img of N. Flashes CFAR. It bootlooped almost twenty times more than 10 mins and everytime it failed near some dm-verity patching saying "failed aborting". Anyway will wait.
[SuperSU] tuierfanzu:
Android n is cool
[SuperSU] flar2:
[MENTION=631273]Chainfire[/MENTION]

A lot of custom kernels (including elementalx) run startup scripts at boot time by declaring a service in init.rc and including the script in ramdisk. On the N preview, the service won't run (service "foo" does not have a selinux domain defined).

Currently on Marshmallow, such services will run if SuperSU is installed, but not without SuperSU. Is this something you have specifically patched in sepolicy on Marshmallow, and if so, will it be the same on N? Or do you advise a different method for reliably running boot scripts without touching /system?
[SuperSU] Paschfire:
Nexus 5 , ROM DU-6.0.1-MHC19J, Running SuperSUv2.69 seems to function fine on MM.
[SuperSU] Chainfire:
It has been known since 4.4 or so that this was going to happen, and services require a security label. Pre-N, SuperSU could easily patch this, but on N, you will need to explicitly either specify a security label (you can simply do "seclabel u:r:init:s0" like SuperSU's service does) or label the script with one of the _exec labels (how most Android services work).

At some point, I think the seclabel declaration will disappear from Android, which will be a gigantic hassle for everyone.
[SuperSU] piperx:
Works fine here, nexus 5, pure-nexus-m 6.0.1 SuperSU v2.70

======================================

Device ► Nexus 5 LG D820 ► 32gb, black

ROM ► Pure-Nexus M 6.0.1

Kernel ► Hellscore b17-M

Recovery ► TWRP - 3.0.0.

SuperSU ► v2.70

===============================================

proudly anti-micro$oft

apt-get into it | debian sid/siduction
[SuperSU] Chainfire:
v2.70 available from the first post. Re-read that post. Release notes coming in a few hours. Changelogs are on the first page of the stable thread.
[SuperSU] jatinarora:
I think it's a SELinux mode issue. It is set to enforcing by default and Tibu requires it to be set to permissive. I tried the SELinux Mode Changer app but the app cannot get root access. Stuck.
[SuperSU] osm0sis:
What TiBu requires is some updates. ;)

With some of the continuing fixes Chainfire makes functionality may be restored, but switching to permissive isn't a good solution.
[SuperSU] yanleites:
The new version works great on 5X - installed busybox fine!
[SuperSU] RandomPooka:
2.70 safe to just flash over 2.69?

TiBu didn't require permissive on M, FWIW
[SuperSU] KenjiHannya:
Works fine in OnePlus One and Darkobas rom

Tnx ?

https://plus.google.com/+JPKenji/posts/NurDC3d7524
[SuperSU] CrazyPeter:
Is there a cf autoroot boot image for pixelc? (ryu)?? It's the only N device not listed :(

Thanks!!!
[SuperSU] corkiejp:
I think chainfire once mentioned that he does not have/want a Pixel C device, so it would be difficult for him to create one.
[SuperSU] MSF Jarvis:
Available for Second gen Android one devices as well
[SuperSU] Ja_som:
On my N5X is 2.70 same as 2.69, I still can´t install BusyBox to /system/xbin, also I can´t install AdAway and Total Commander can´t write to system. I tried to reflash boot and system.

[MENTION=5009022]yanleites[/MENTION] to which path you installed BusyBox?
[SuperSU] Chainfire:
Actually, I do have a Pixel C. However, the ryu uses ChromeOS bootloaders, and supporting those with SuperSU would be an enormous task. The ryu is currently the only device in the world using this system, and it might remain so forever. So at this point it isn't worth the effort for me.

Both from terminal emulator and adb shell I can call su, remount /system writable with "mount -o rw,remount /system", and make changes to the system partition. If at that point your apps still don't work, they need an update.

As for busybox, install it to /su/xbin.
[SuperSU] jcrompton:
Not sure if this had been answered or not but why does 2.68 work on N without any problem ..... That is for TiBu restoration
[SuperSU] osm0sis:
Definitely the SELinux changes.

Edit: Er, wait, 2.68 works on N somehow? That IS interesting!
[SuperSU] xela92:
2.70 CFAR is working perfectly on Nexus6P with N Preview :D chainfire you're the best :D
[SuperSU] jcrompton:
There is a special 2.68N version out there

TiBu works great with it
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] thanks for your answer, now with Root Browser I can write to system, Total Commander and ES File Explorer can't. BusyBox installed...
[SuperSU] Chainfire:
It has all security disabled.

I might need to fix something on my end with SuperSU, but much more likely TiBu just needs an update.
[SuperSU] jcrompton:
I realize kinda stupid question ..... But is that a problem?
[SuperSU] RandomPooka:
It has all security disabled.

That sounds like a problem.
[SuperSU] H4X0R46:
Anyone get TWRP to work on Nexus 6 with N preview yet? I haven't tried it myself yet, just wanna know how that's working for you guys! On a Shamu!
[SuperSU] ohad129:
Difined work twrp? I can flash through it so the answer is yes
[SuperSU] jcrompton:
I understand your response and I probably understand the push for the manufacturers to "force" security with locked bootloader and otherwise. I guess they don't want to be responsible. But I believe it should be our choice ....

But surely most people who are on XDA flashing God knows what, day in and day out, surely aren't that worried about security ?
[SuperSU] Chainfire:
Release notes for v2.70: https://plus.google.com/+Chainfire/posts/cX2eLb4fkTB
[SuperSU] Chainfire:
It's a different level of security than locked bootloaders.

An enforcing SELinux system decimates the chances of rogue apps being able to exploit security holes in the system to gain full access to the device without your knowledge.

You can protect your assets by putting them in your garage, or you can put them in a vault with an alarm, a guard, and the army on speed-dial. One is much more likely to stop your nosy neighbor than the other.

Of course, what you use is your choice. You wouldn't be the first to disable this security, you wont be the last, and the real world risk (if you know what you are doing) isn't all that big.

However, SuperSU tries to keep the security system workable as best as it can, and so do many root apps. This is good, so we don't have to fully disable this security if we don't want to - and many do not want to. Of course, new Android version, it always takes a while for devs to catch up. Heck, a lot of root apps aren't even fully Marshmallow compatible yet.
[SuperSU] jcrompton:
Understood

Since I always seem to be learning ..... Is what you are talking about the same as setting a kernel to permissive, since many (if not most) custom kernels are made permissive out of the box ?
[SuperSU] boxcar8028:
Just updated my stock N6p SU from v2.69 to v.270 and all is running smooth and stable. All root apps are working fine including Viper. Thanks again Chainfire!:good::good::good:
[SuperSU] RandomPooka:
Ok, So I was intending to flash the ElementalX kernel and SuperSU 2.70.

The way I read it, I shold flash the kernel second, but now I'm wondering if that's going to overwrite the changes that were made in SuperSU 2.70

[MENTION=4684315]flar2[/MENTION] and [MENTION=631273]Chainfire[/MENTION] .. any insight here? Should I hold off on EX, or will it not be an issue?
[SuperSU] Chainfire:
Yes, what I was talking about is exactly setting SELinux to permissive mode. (Setting a kernel to permissive is technically the wrong expression, but the same thing is meant)
[SuperSU] pahlerc1:
Dang I'm jealous haha tried installing busybox to su/xbin and then tried flashing V4A 4.7.1 stock but didn't work.. Any insight? All other root apps working for me thus far
[SuperSU] boxcar8028:
I use this zip on my 6p. I have my busybox installed to /su/xbin and flashed this zip and it works great. Good Luck.

BTW: make sure to delete all old viper stuff first.

SEE POST#325

http://xdaforums.com/nexus-6p/general/guide-installing-viper4android-t3250579/page33
[SuperSU] kevdog98:
I installed Super SU 2.70 first and the EX 4.00. That worked great for me.
[SuperSU] flar2:
Adding the security label "seclabel u:r:init:s0" works, thank you.
[SuperSU] H4X0R46:
Cool thanks! Just heard that TWRP wasn't booting for everyone who had N preview installed. Thanks for the response!
[SuperSU] Chainfire:
For root app devs and interested users: N Preview: Surviving Your Trip To Mount Doom - https://plus.google.com/+Chainfire/posts/dGPQytapwe3
[SuperSU] jerickjose:
I get bootloop in cm 13 temasek i9300 s3 please help
[SuperSU] yweiqiang:
Thanks Chainfire
[SuperSU] jtwebfusion:
I did the opposite and installed EX 4.01 first, then SuperSU 2.70. Its all working great for me on my N6. Thanks!
[SuperSU] kevdog98:
Yep, that is what I did and meant to type, I typed it backwards by mistake.

Thanks.

Kevin
[SuperSU] RandomPooka:
Oops. Deleted
[SuperSU] yanleites:
Su/xbin
[SuperSU] LN490547946:
Support for a look
[SuperSU] tom1807:
Installed RC-SuperSU-v2.70 after updating my Nexus 6 and Nexus 9 to Marshmallow 6.0.1-mmb29v with TWRP 3.0.0-1 and 3.0.0-2 respectively.

All went fine, no issues at all, all my root applications work without problems
[SuperSU] magnamentis:
since this is the WIP for "N Preview" and that said, CM13 is not a "N preview" so i'm not sure whether help is possible or planned. you can use 2.68 beta or 2.65 stable for cm13 and cm13 based roms
[SuperSU] osm0sis:
From the OP:
[SuperSU] Chainfire:
Unfortunately it is unclear if its v2.70 specifically that isn't working for him, or SuperSU in general...
[SuperSU] magnamentis:
sure, but since he has a bootloop this invitation to flash does obviously not mean that it always works, i did not say don't flash but replied to his having a bootloop and recommended the variants that would work with his configuration. anything wrong with that ?
[SuperSU] pahlerc1:
Thanks for the link but still couldn't get V4A running right.. Kept asking to install drivers lol oh well can't have it all :)
[SuperSU] jesssiii:
Try:

rename /vendor/etc/audio_effects.conf

Then reboot.
[SuperSU] loof13:
I flashed this V4A zip on my Nexus 5X. It tells me to install drivers every time I open the app even after I've installed and reboot. I'm running Android N rooted with v2.70
[SuperSU] pahlerc1:
Damn, I went to rename and just noticed that ES File Explorer doesn't recognize my root with 2.70 but other apps do.. weird

Update: Downloaded root browser and it recognized root
[SuperSU] loof13:
Tried this on my 5X. Still doesn't work :crying: