yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] u89taper:
Not during this process but I had already done it. I accidentally flashed the userdata.img file which is a big no-no for 64gb+ versions of the phone (it shows you having less storage than you actually have).

Before you format, you keep mentioning /sdcard... Have you:

A) downloaded SuperSU in chrome on your phone

B) looked in /storage/emulated/0/download for the SuperSU file rather than /sdcard

The thing is... In flashing and doing all of this stuff, you may have screwed something up. My philosophy is that if I've screwed something up good, I'd rather start fresh.

It seems to me, in reading your posts that you've already spent hours working on this. What's a few more hours to be totally done with it. If you follow exactly what I posted, exactly how I've told you, you "should" be totally good to go.

I only wrote these steps after doing a lot of reading of things written by people much smarter than me. Maybe you'll want to let others chime in, but again, I've updated 3 different phones to 6.0.1 (I actually am giving my Nexus 5 to a friend so I locked the bootloader) and have switched 2 from old school root to systemless root without any problems.

My 6p is rock solid and running 100% how I want (stock, systemless root with a few bells and whistles). The Nexus 6 sits in my car as a navigation/entertainment system.
[Nexus 6P General] hosmsdos:
Guys i unlocked and installed TWRP following this guide but i forgot to turn USB Debugging, it worked without debugging, anyway i now have this message annoying message every time i boot the phone

Your device software can't be checked for corruption please lock the bootloader.

Did i do something wrong or this is normal?

can i get rid of this message?

Also my bank app no longer works with root, i get can't run on rooted devices message. can i bypass that?

I am using Nexus 6p Global Model 6.0.1

Thank you so much for this wonderful guide.
[Nexus 6P General] Badger50:
That is normal. We all have it.
[Nexus 6P General] goddammit:
Thanks for all the advice. Couple questions though.

When I'm in TWRP I do not see /storage/ folder. All I see is a bunch of folders I normally see in a linux / directory. Most of the folders are empty. /root folder is empty. From TWRP I can't access anything useful. This is why I upload SuperSu with adb to /sdcard/ folder which by the way is also empty.

I completely understand wiping everything approach, although if in couple of weeks 6.0.2 comes out and I have to wipe again - this will be unsustainable for me.

Another thing - the only difference from tutorial 10 and tutorial 11 is wiping user data which makes it kind of hard to believe that it would solve my problem. Of course, I may have to do that as the last resort, although this is not just my play phone and any significant downtime counts.
[Nexus 6P General] u89taper:
Going forward, you won't have to touch userdata, it will stay in place.

You'll notice here that there is no mention of touching userdata: http://xdaforums.com/showpost.php?p=64280720&postcount=1551

When I updated versions of 6.0.0, I formatted userdata once or twice because I had done things wrong somewhere along the way. When I updated from 6.0.0 to 6.0.1, I didn't touch userdata as I had already remedied any issues I had. Following the steps in the original post/tutorial I made where I didn't touch userdata will keep everything in place. All of my apps, music, photos, etc were right where they were supposed to be after upgrading and switching root styles.

Personally, if I were in a situation where I couldn't figure out what the f is going on, I would start over. This 6p is my, for all intents and purposes, only phone and I also don't have time to be without it. I'm over flashing ROMs and doing mods. Stock Android is all I need.
[Nexus 6P General] AndroidPurity:
1 quick question, will the boot.img for the angler build number mdb08k work with mmb29m (6.0.1)?

I literally just booted into the boot loader to do this so can someone please confirm? The only boot.img chain fire has on his forum is the one for the mdb08k build number and not the newest update. Don't want anything going one. Please advise, thank you in advanced!
[Nexus 6P General] u89taper:
If you're switching to systemless root (2.60+), SuperSU no longer requires a modified boot image. It patches the stock boot image.
[Nexus 6P General] AndroidPurity:
Hey, thanks for the quick reply! I know, I saw the second post in his thread. However I was not doing that method since it has the huge warning of still lots of bugs. Also still my same question still stands with the system less zip says with the old previous build number. So does anyone know if either of those zips can be used with the newest build mmb29m?

EDIT: Nevermind, I got it worked out. I just did the systemless with TWRP and SuperSU only. Thanks!
[Nexus 6P General] runawaybayeh:
when I went to my apps, and there was a SuperSu installer, I should have ignored this as well?
[Nexus 6P General] Heisenberg:
You mean the SuperSU app? It's normal to have that. Are your root apps working?
[Nexus 6P General] force70:
I know you got it sorted but if anyone else has the same question just know that any 6.0 boot img will break the camera on 6.0.1

Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[Nexus 6P General] Krunk83:
Right now I am wishing there was a guide on how to get Android Pay working with systemless root. Right now everything I've tried isn't working. I guess my next step is to flash the system.img then SuperSU 2.61 and start over. UGH!
[Nexus 6P General] bouchigo:
You don't need to do anything special to get Android Pay working with systemeless root. If you flashed anything later than chainfire's SuperSU v2.6.1 then just go into /su and delete the xbin_bind folder, reboot the phone, and you should be fine.

Run this app to test that all SafetyNet tests pass: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
[Nexus 6P General] Krunk83:
I don't have that folder.

Ran the test and it says "CTS Profile Match: False". Everything else was a success.

---------- Post added at 07:20 PM ---------- Previous post was at 07:07 PM ----------

Wow I feel like a complete moron. I had my DPI changed to 520 instead of stock 560, change it back to stock and its working. Thank you for the help.

Sent from my Nexus 6P
[Nexus 6P General] bouchigo:
Yeah, build.prop edits will cause Android Pay to fail the SafetyNet tests...leading to Android Pay not working.
[Nexus 6P General] Pzyborg:
Please help. I installed supersu through trwp and now my nexus 6p wont boot. It just stays at the google logo screen.
[Nexus 6P General] runawaybayeh:
#11 per Heisenbergs instructions. I think you're going to have to start over. Thats what I had to do. :( If someone knows better please step in.
[Nexus 6P General] troymz1:
ok here goes. i was on 6.0.1 stock image cataclysm rom, systemless root 2.62 and franco kernel r2. i was having the lte connectivity issue many are reporting. i thought i would try to re-flash 6.0.1 and re-do everything except userdata. now im stuck in bootloops no matter what i flash. i tried going back to 6.0.0 and it bootloops. i got into system once and a whole bunch of things crashed. and i had no sim card. and im doing as per step 10 of [MENTION=4153349]Heisenberg[/MENTION] guide. sometimes, only sometimes im getting the red bootloader warning saying my device is corrupt. how do i fix this. do i need to wipe userdata? please help.
[Nexus 6P General] Heisenberg:
You mean you installed the one that TWRP offers to install for you? Boot into TWRP and wipe the caches (in the advanced wipe menu), then boot into the bootloader and flash the system.img from the factory images for your current build.

Boot into TWRP and wipe only data (using the advanced wipe menu), then boot into the bootloader and flash the factory images for your current build. There should be no need to format your userdata.
[Nexus 6P General] troymz1:
Thanks for the quick reply! ok. i wiped data. i flashed everything in order in step 10 except twrp. i booted to twrp so i wouldnt lose it. then i rebooted to system. first reboot to twrp had the normal bootloader is unlocked we cannot check for corruption. but when i rebooted to system. it was the red warning saying my device IS corrupt. but it actually booted. im just going through the setup process now. hopefully it works.

but why the red corrupt warning?
[Nexus 6P General] Heisenberg:
I had the same problem the other day when I was setting up my fourth Nexus 6P (long story, many defective devices, this one is faulty too so I'll be getting a fifth). I couldn't pinpoint the cause, because I didn't really have time to so I just ended up flashing Pure Nexus (I was planning to anyway) and moved on. When you booted TWRP it should have asked you if you wanted to allow system modifications or keep it read-only, what did you choose? And did you flash SuperSU while booted into TWRP?
[Nexus 6P General] troymz1:
It did not ask me. and i flashed nothing because i wanted to see if it would boot first.
[Nexus 6P General] effraie:
Tell me if i'm wrong : if i'm planning to root/flash /custom recovery, i should unlock the bootloader before setup anything, cause of the wipe of all data? Even if there is still no root/TWRP / rom for now?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 6P General] Heisenberg:
Yep, best to do it before you commit much data to the device.
[Nexus 6P General] Hilbe:
Do you have to boot it once to "Enable OEM Unlock" or can you immediately hit the bootloader right out of the box and unlock?
[Nexus 6P General] just4747:
Maybe I missed something but why did this thread get locked: http://xdaforums.com/nexus-6p/general/root-available-t3235179 for being a "duplicate" of this one if this thread does not yet have the root info?
[Nexus 6P General] efrant:
If it is anything like the Nexus 6, if you boot into the bootloader right out of the box (i.e., before you ever boot into Android), you should be able to unlock without enabling that setting.
[Nexus 6P General] designgears:
There is root info and this thread was last edited at 01:58 AM.

That other thread was created at 06:09 AM.

That means the other thread was 4hrs behind this thread in posting root, duplicate and locked.

RIF

Also, thanks [MENTION=4153349]Heisenberg[/MENTION] for a guide the explains how to do stuff instead of a sketchy kiddy script, much better that people learn and understand what they are doing. :D
[Nexus 6P General] just4747:
Maybe I'm still missing something but where is Root info in this thread? It just says this in the Root section: This section will be revisited when more information is available.
[Nexus 6P General] Born<ICs:
Not sure if helpful or accurate, correct me if I'm wrong please but............seems to me the OP should be revised to specify flashing Modified Boot Image before flashing TWRP in order to get root.

???

For example read on another guide................

Before you flash TWRP, it’s a must to flash modified boot image first. Otherwise, TWRP will remain encrypted and you won’t be able to use it to flash SuperSU to acquire root access on Nexus 6P.

TWRP

http://www.theandroidsoul.com/nexus-6p-twrp-recovery-85727/

Root

http://www.theandroidsoul.com/nexus-6p-root-85689/
[Nexus 6P General] powder_7:
Can't boot into twrp

Hi,

I just got nexus 6p and unlock bootloader and fastboot flash recovery twrp-2.8.7.0-angler.img. However, I can't boot into twrp. I hold the power and volume and scroll thru the option with up/down and select "Reboot bootloader" but I can't get into twrp.. I also get a warning message. "Your device software can't be checked for corruption. Please lock bootloader."

Thanks,

Nate.
[Nexus 6P General] Heisenberg:
Custom Recovery and Root sections of this guide have been updated. I've been waiting for the modified boot.img to become available, looks like it happened overnight while I was sleeping.
[Nexus 6P General] powder_7:
Hi,

I finally got root on nexus 6p. Yes, you need to flash boot.img before twpr.img from the link above. Also, I couldn't mount data, so I just reboot system and twpr will ask and install superuser that will root.

The step that I did different from video.

1.) I couldn't mount data partition, so I reboot system and pick to install root.

2.) I boot into android and twpr ask to install superuser and I install thru twpr option instead of playstore.

3.) I install root checker and it shows I am rooted.

Took a day but I am rooted and twpr is installed.

Thanks,

Nate.
[Nexus 6P General] Heisenberg:
You couldn't mount data because it's encrypted and TWRP is unable to decrypt it at this stage. The only issue with using the SuperSU that TWRP automatically flashes is that it's probably outdated. If you wish to flash the latest SuperSU now you'd need to format your data partition with TWRP which will remove encryption (so TWRP can read it and install from it), then you can place the latest SuperSU on it and flash with TWRP. These sections have all been updated now.

Can you please check which version of SuperSU you have installed now and report back?
[Nexus 6P General] powder_7:
Hi,

The SuperSU that twpr installed is SuperSU Free v2.46. by Chainfire.

Nate.
[Nexus 6P General] Heisenberg:
Ok, thanks, that's definitely an older version. I'd suggest you go into the wipe menu in TWRP and format (not wipe) data. This will remove encryption and allow TWRP to access it so you can update SuperSU (and flash other zips in future). This will remove all user data from the device of course.
[Nexus 6P General] rgao007:
I just got my 6P and it's not letting me unlock the bootloader. When I type in "fastboot flashing unlock", it simply brings up all of the commands I can put in. I have enabled USB debugging and checked the "Enable OEM Unlock" option. Could this be because I purchased the device through a Google corporate account? Thanks in advance.
[Nexus 6P General] Heisenberg:
Interesting. Have you tried the fastboot oem unlock command at all?
[Nexus 6P General] rgao007:
Yes, I have.
[Nexus 6P General] Heisenberg:
Ok, how did you install adb/fastboot? Have you made sure it's fully updated?
[Nexus 6P General] rgao007:
I've had it on my computer (Windows 10) for a while and haven't had any issues. I've checked ADB for a version number and there is one. Should I reinstall it through the SDK?
[Nexus 6P General] Heisenberg:
It might be a good idea to update all relevant components via SDK Manager.exe and try fastboot flashing unlock again.
[Nexus 6P General] Heisenberg:
Ok, I'm guessing the data carried over because you didn't overwrite the recovery partition and you didn't wipe your internal storage. The phone should work but I'd still be worried about that message. I can only suggest you flash the system and stock recovery images again, then boot the phone and set it up. Delete the TWRP folder from your internal storage using a file manager (if you have any nandroid backups transfer them to another folder temporarily). Then boot back into the bootloader and flash TWRP again, if you plan on rooting flash SuperSU the first time you boot into TWRP. My theory is that this should get rid of the corruption message you're getting. I'm hoping so anyway.
[Nexus 6P General] troymz1:
worked thanks a lot!!
[Nexus 6P General] Heisenberg:
Excellent, no worries, glad to help.
[Nexus 6P General] kopkiwi:
So, I got finger happy and installed the root through TWRP, and of course nothing works. How do I undo my idiocy?
[Nexus 6P General] Pzyborg:
Thank you very much.
[Nexus 6P General] BladeRunner:
flash the stock system.img with fastboot.
[Nexus 6P General] TigerSoul925:
I'm curious about the vendor and other strange partitions I haven't seen before. What do I need to backup once and keep safe like the EFS partition and what do I need to backup every time to have a complete system backup?

---------- Post added at 02:18 PM ---------- Previous post was at 01:30 PM ----------

Please correct information as to lock not having to be disabled:

http://xdaforums.com/showpost.php?p=64321640&postcount=91
[Nexus 6P General] Heisenberg:
All I know about the vendor partition is that it contains proprietary files, Layers themes reside there, for example. It's up to you how often you create system backups, most people do it before flashing something so they have something to go back to if the flash goes wrong, or if they're not happy work what they've flashed. I usually recommend people keep at least one working backup on their phone as a, you know, backup.

I'm not sure what you're saying/asking in regards to the lock disabling, can you please elaborate?

Sent from my Nexus 6P
[Nexus 6P General] napes22:
Thanks for your help on this. I ended up doing the factory reset after flashing and everything seems to be working fine. I unfortunately didn't realize that the stock recovery wipes out the data partition as well and needed to start everything over.
[Nexus 6P General] TigerSoul925:
Since I've got the vendor partition already sorted out through another thread I'll head to the other part:

You're writing in the guide that it's important to remove any lock like fingerprint, pin etc before backing up as the backup won't restore correctly, i.e. can't login. It's possible to log in by removing a file after restore and I felt this should be added to the guide. It's a lot of work having to reset the fingerprints every backup if you tend to do them often ;)
[Nexus 6P General] TheDude:
So in reference to step 6. I am having trouble with writing to /system. Root Explorer says the system is mounted read only and I have to mount it r/w which works, but other file managers have trouble with this... great oh well. So it appears that the system boots read only. Is there a way to mount the system r/w on boot? For example Layer Manager is useless. It will not write to /vendor/overlays I assume because its read only. Am I missing something here. I see other people say that systemless root and Layers are working fine with AP etc... What gives? Does this below solve that issue?

su

(you'll need to grant Supersu access at this point)

mount -o remount,rw /system

touch /system/bin/su /system/xbin/su

mount -o remount,ro /system
[Nexus 6P General] elbel86:
I'm having the same issue with /system being mounted read only. Can't figure out what caused it, but this does not fix it as you need it to be r/w for the touch command to work and the remount command does not seem to change it to r/w.
[Nexus 6P General] bouchigo:
Yes, edit fstab.angler in boot.img to rw instead of ro then flash the boot.img back to your phone. If you don't know how to do that I suggest you do a lot of reading on how to modify boot.img's, or maybe someone that knows how to do it will do it for you if they aren't too busy.
[Nexus 6P General] napes22:
Has anyone run into issues with restoring nandroid backups? I had installed Cataclysm and flashed the vendor image (coming from 6.0.1), and then when I tried to restore my backup to stock, it completed successfully but hung at the Google Logo. The only way I was able to get my phone to boot was reflashing the Cataclysm rom.
[Nexus 6P General] Badger50:
Do not back up or restore the vendor partitions!! It'll boot loop you every time! =-O
[Nexus 6P General] napes22:
I only backed up System / Data / Cache. Is there a separate option to not backup the vendor partition?
[Nexus 6P General] goddammit:
I'd like to clarify something - when I'm in TWRP - I cannot access any files that I've downloaded while booted Android, can I? If I can then how exactly? I keep seeing people saying they've downloaded SuperSu and installed with TWRP, but the only way I managed to make TWRP see SuperSu zip is if I upload it with adb.

UPDATE: I was doing the wrong thing. I was not decrypting the data when launching TWRP and therefore couldn't access it, this time I did and installed SuperSu successfully. Perhaps a small thing, but worth mentioning in the tutorials? I spent literally days chasing this.
[Nexus 6P General] NPOA556:
I don't know about downloading directly to the phone, but I downloaded SuperSU on my PC then copied it over to the phone using MTP while booted into Android. I was able to flash that with TWRP just fine.
[Nexus 6P General] kopkiwi:
I can't open Android SDK.exe? A command prompt flashes quickly and that's it. NOthing
[Nexus 6P General] itsmejson:
Thank you for putting these instructions together. I just received my Nexus 6P and planning to unlock bootloader / root.

If we unlock bootloader and root - Will the screen at boot with the triangle on it always be present before the phone boots up?
[Nexus 6P General] Mesmurized:
Yes. We all have it.
[Nexus 6P General] Heisenberg:
I'm not adding those instructions to the guide, it's a lot easier to just set up fingerprint security again. Deleting those files would prove to be too complicated for some people.

I'm pretty sure I've backed up and restored the vendor partition. My memory could be wrong though.

Which package did you download from the Google site?

It'll always be there, It's normal for a phone with an unlocked bootloader.
[Nexus 6P General] kopkiwi:
All good. Turns out my phone is phucked anyway. Camera and flashlight/torch don't work.
[Nexus 6P General] Heisenberg:
Have you tried flashing the factory images? It could just be a software issue.

PS. Please don't use profanity on XDA, it isn't allowed.
[Nexus 6P General] kopkiwi:
Nah I can't even get the SDK manager running. Just going to take it back for a new one and start from scratch. They'll swap it on the spot. No harm no foul.
[Nexus 6P General] TigerSoul925:
You have a point there. Perhaps a note on "getting into the phone still possible if you forgot, see this post" ;)
[Nexus 6P General] RohanAJoshi:
i unlocked bootloader successfully.

but when I use "fastboot format userdata" is not decrypting userdata at all.

I checked in security settings and it's encrypted.

I am latest 6.0.1 build.

.

I know that its not necessary from twrp 2.8.7.1, but still wanting to do it.
[Nexus 6P General] bouchigo:
You most likely have a boot.img/kernel that isn't set up to be "encryptable" instead it's set to "force encrypt".
[Nexus 6P General] AndroidPurity:
Haha! I was sooo close to saying screw and trying it since I knew the cf auto root file worked on both 5.0 and 5.1. Until I realized 2.60+ Super SU rooted all by itself now, then I did that. Thank God I didnt. Lol. But then again if it booted could have always flashed back.
[Nexus 6P General] napes22:
Has anyone else had issues restoring a Nandroid backup? I backed up System / Data / Boot, and upon restore i couldn't get past the Google logo.
[Nexus 6P General] 220volt:
Did you disable fingerprint or any security before you did the backup? You must do that before backup in twrp.

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P General] Mesmurized:
Section 4 of Post #1 now contains workarounds for restoring Nanoid backups with the PIN/password enabled. Check it out :)
[Nexus 6P General] napes22:
Pin/Password wasn't my issue. It was that I couldn't get past the google boot logo. It wouldn't even attempt to load my OS.
[Nexus 6P General] Badger50:
Did you restore vendor partitions? That always bootloops me! Which is why I don't do that anymore.
[Nexus 6P General] napes22:
No, I didn't. It was a normal restore of system/data/boot and nothing else. I didn't even get a boot loop. It got stuck on the Google logo as if there was no OS.
[Nexus 6P General] mobileman88:
just need to delete /data/system/locksettings.db
[Nexus 6P General] Heisenberg:
The stock kernel forces encryption on boot so you'd need to use a kernel that disables that feature.
[Nexus 6P General] NotEaster:
So, it sounds like the yellow boot message (which annoys me greatly) won't go away as long as the bootloader is unlocked, and I can't re-lock the bootloader with a custom recovery or root? If there's a way around that, could a custom recovery install new updates to the OS even with the bootloader locked?

The last time I performed a root was on a nexus 4, and I didn't need to think about this. Any help would be appreciated.