yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] losl1946:
I flashed the TWRP recovery to my Nexus 6p after unlocking the bootloader following your steps. I used the volume keys to scroll and power key to select rebooting to bootloader and then to recovery. The TWRP Recovery was successfully flashed and working properly. After that I rebooted the system and booted to recovery again using the normal way, the TWRP recovery disappeared and it was reverted back to the stock Android recovery. Did I miss some things? Please help, thank you.

SLo
[Nexus 6P General] jimbomodder:
Did you flash root? Also are you still encrypted as some times that puts stock recovery back on
[Nexus 6P General] losl1946:
I only finished flashing the TWRP recovery and did not install root yet. Now it was replaced by the stock Android recovery, I have to flash TWRP again and make a backup before install custom from and root.

I don't know about this.
[Nexus 6P General] shaemasa:
Have you tried this?

Fastboot to twrp and flash the recovery file (.img) again through twrp.
[Nexus 6P General] losl1946:
Tried, the TWRP recovery was replaced by the stock Android recovery again after rebooting to the system.
[Nexus 6P General] shaemasa:
Download twrp again and give it a try.
[Nexus 6P General] SubwayChamp:
In Nougat you need to root it in order to preserve TWRP. Probably decrypting can do the job too, for this you should need to format data after to boot to TWRP.
[Nexus 6P General] edolf:
This one?

https://dl.twrp.me/angler/twrp-3.5.1_9-0-angler.img.html
[Nexus 6P General] shaemasa:
Should work but there is 3.5.2 as well.
[Nexus 6P General] shaemasa:
I used this https://dl.twrp.me/angler/twrp-3.5.2_9-0-angler.img.html
[Nexus 6P General] edolf:
After flashing twrp ask for a password.
[Nexus 6P General] shaemasa:
Format data
[Nexus 6P General] Aridon:
Remove both and only use the main app without the root companion. If you don't remove both you can get wake locks. Especially if you leave the root app on there. I had issues with this.

Just the normal app seems to work fine.
[Nexus 6P General] Heisenberg:
Flash everything in the factory images except for recovery, and without formatting userdata. Flash the modified boot.img again. Flash SuperSU again.
[Nexus 6P General] adrman:
Well, userdata will wipe your internal and cache you can wipe from TWRP before you reboot. If you flash boot, you'll just have to flash Chainfire's modified image or another kernel again. However, new builds have the potential to introduce some compatibility problems with older kernels, so it's something to keep an eye on. Bootloader and radio remain unchanged, although again, for future updates, that might not hold true.

I was using ElX kernel when I updated yesterday and I've had no problems. As expected, I did have to reinstall Adaway and Busybox again though.
[Nexus 6P General] efrant:
Just to add to this (as an aside), the userdata.img should never be flashed. Even if you want to wipe. You should always use "fastboot format userdata" instead of "fastboot flash userdata userdata.img".
[Nexus 6P General] Big Cam:
So I've hit a major roadblock.

I downloaded the SDk from the link provided in the first post, extracted it and whenever i open the SDK manager, a box opens for a split second and then closes and nothing ever opens.

What am I doing wrong?
[Nexus 6P General] tcat007:
Do you have latest java installed?
[Nexus 6P General] galaxys:
Kinda happened to me on Windows 7 because Java wasn't installed. Worked after updating Java...
[Nexus 6P General] Big Cam:
Thank you both, that was it. I use this laptop so rarely I am not surprised it was out of date.

Thanks again!

---------- Post added at 07:18 PM ---------- Previous post was at 07:09 PM ----------

Sine I am on MDA89D, I know I need to update my firmware before installing TWRP, but does it matter which I take? The instructions only say at least MDB08K, but there are 2 more after that, is the last one the latest?

MDA89D

MDB08K

MDB08L

MDB08M

What is different between K/L/M ??

EDIT: A bit of googling told me it is the November update, so I'm going with M

---------- Post added at 07:53 PM ---------- Previous post was at 07:18 PM ----------

So I downloaded the latest MDB08M

But then I copied and pasted this from the guide.

fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img

fastboot reboot-bootloader

fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img

fastboot reboot-bootloader

fastboot flash boot C:\angler\images\boot.img

fastboot erase cache

fastboot flash cache C:\angler\images\cache.img

fastboot flash recovery C:\angler\images\recovery.img

fastboot flash system C:\angler\images\system.img

fastboot flash vendor C:\angler\images\vendor.img

fastboot format userdata

So of course I don't have the 2 bolded files. i thought I could edit it, but the damn thins just went off as soon as I pates it. So am I F'd or can I fix this?

I really wish the guide would have been updated with the latest build.
[Nexus 6P General] Heisenberg:
The guide clearly states that those two filenames will change with each build. All you need to do is change the command you enter to suit the filenames you actually have, there's nothing wrong with the guide.
[Nexus 6P General] Big Cam:
I was worried I borked it since I ran the command with the wrong file name, I'm not much of a command line user, so I was a little freaked out.
[Nexus 6P General] Heisenberg:
[MENTION=3918558]Big Cam[/MENTION]

Nah, executing the command with the wrong filename will just result in a failed attempt because fastboot isn't able to locate the file.
[Nexus 6P General] Heisenberg:
XDA is playing up, double post.
[Nexus 6P General] Big Cam:
[MENTION=4153349]Heisenberg[/MENTION]

Not sure why I can't quote you, but as long as you are here, is it ok to use the angler-mdb08k-boot with the MDB08M firmware? I just chose the latest, but now I see the modified boot image hasn't been updated since mdb08k.
[Nexus 6P General] Heisenberg:
XDA is playing up a little at the moment. I can't even see this post of yours via Chrome but am able to view and quote it via the app. Anyway, yes the modified K boot.img is compatible with the M build.
[Nexus 6P General] Big Cam:
Thanks a bunch, sorry for freaking out, I thoguht i had messed up my phone ad I've only had it for like 2 hours.

Haha, but I'm now set. unlocked bootloader, TWRP installed, and root on the way, just waiting for my phone to restore.:good:
[Nexus 6P General] gnikoli:
So I complete step 4 and everything is great. I click to reboot system and it tells me that I haven't rooted yet. I ignore and do not install SuperSU because that is not what step 4 says to do. Bootloop. I have to reinstall factory image to get back to square one. This time, I swipe to install SuperSU at the end of step 4 and no diff, boot loop again.

Any ideas?
[Nexus 6P General] johnhazelwood:
Would accepting the over the air update work, then flash the modified boot, twrp, and SuperSU work?
[Nexus 6P General] Heisenberg:
What build are you on? Did you flash the modified boot.img? What version of SuperSU did you flash?

Yep.
[Nexus 6P General] johnhazelwood:
Man you're quick. Thanks!
[Nexus 6P General] gnikoli:
Current build: MDA89D

Flashed angler-mdb08k-boot.zip from provided link.

Flashed twrp-2.8.7.2-angler.img from provided link.

I've tried it three different ways and all result in bootloop: 1) Ignore TWRP prompt at reboot to install SuperSU and root. 2) Accept TWRP prompt to install SuperSU and root. 3) Before leaving recovery after making Nandroid, go back to main menu and install SuperSU.
[Nexus 6P General] johnhazelwood:
Read Step 2. You need to update your build first.
[Nexus 6P General] gnikoli:
I see, just did that (to 08M) and was going to try again. In my pea brain I thought flashing angler-mdb08k-boot.zip satisfied that. So now that I am on MDB08M, do I still need to flash angler-mdb08k-boot.zip?

---------- Post added at 10:01 PM ---------- Previous post was at 09:47 PM ----------

I course you don't you twit, I says to myself, it's a "modified" bootloader.
[Nexus 6P General] johnhazelwood:
Yeah follow the remaining steps and you should be good (including the modified boot needed for root). You'll likely need to fastboot TWRP to recovery too.

---------- Post added at 07:07 AM ---------- Previous post was at 07:02 AM ----------

Oops it didn't work (the update didn't). I'm stupid, realized I probably need stock recovery to install the patch. So presumably the steps would be, go back to stock recovery, install OTA patch, apply modified boot image, install TWRP, then flash SuperSU.
[Nexus 6P General] Heisenberg:
You need to follow the instructions, they're written here for a reason. If you don't follow the instructions you end up in this situation that you're in. Great care has gone into writing this guide to ensure that everything works as it should. Pretty much every person who's posting about having an issue has failed to follow the very clear directions, it's becoming pretty frustrating after putting so much effort into this guide.

Yes you need stock recovery to install an OTA, and an unmodified system (no root).
[Nexus 6P General] gnikoli:
I can't argue with you. That one misunderstanding on my part was the problem. Just completed the process and it worked. Thanks.

I produce a lot of documentation for food safety programs. It's a constant struggle to get the language just right. What is obvious to me is not always obvious to others. I have found that the key is to write for others, not myself, but even then it can be frustrating. I also have the advantage of being able to review, respond to feedback and edit over a period of months in order to get things to a point where even the most obtuse employee can follow my written instructions. It's a process and you just have to realize that not everyone is as smart as you.

---------- Post added at 10:32 PM ---------- Previous post was at 10:26 PM ----------

30.00 AUD on the way
[Nexus 6P General] Heisenberg:
Whoa, that really isn't necessary at all! I appreciate the gesture very much but you don't have to do that. I understand what you mean, I'm constantly tweaking my guides in an effort to get them just right and easy for people to follow.
[Nexus 6P General] gnikoli:
You did a very good job with this one, one of the best I have seen.
[Nexus 6P General] Heisenberg:
Thankyou, I'm glad to help anyone tinker with their phone.
[Nexus 6P General] mousefai0922:
Hi guys, i m some questions in my mind

I will be getting my 6p. However, I am thinkgint to unlock the bootloader first since it require a format when doing so. But then my question is that does unlocking the bootloader erase the android M too?
[Nexus 6P General] harish_hpd:
everything worked fine.. installed twrp.. while booting into recovery twrp says

keep system read only? twrp can leave your system partition unmodified to make it easier for you to take official updates. twrp will be unable to prevent the stock rom from replacing twrp and will not offer to root your device.

Installing zips or adb operations may still modify the system partition.

i have 3 options here..

1 never show this screen during boot again.

2 keep read only

3 swipe to allow modifications

which one to select?

Another doubt .. On every reboot the phone says the device's software cant be checked for corruption.. please lock the device? is this because i have unlocked the boot loader right? and it is normal right? and i should not lock the bootloader unless i am not on stock recovery.. right?
[Nexus 6P General] dowlf:
Thanks for the concise guide. I was able to easily root my new phone after flashing mdb08m first.
[Nexus 6P General] pahardie:
Yes this thread is gold! Thanks a lot!
[Nexus 6P General] YandereSan:
Word of caution, after following this guide and installing the beta SuperSU, my device became soft-bricked.

I was only able to restore it using the official Google image. :/
[Nexus 6P General] SurenSeven:
I don't want to come off as rude but seriously? All the people who followed the guide RIGHT got it right. If you messed up that's probably because you didn't put in enough effort to understand the guide and get it right.
[Nexus 6P General] SurenSeven:
Hey I noticed that subtle 'wtf' you inserted in your quote :p
[Nexus 6P General] webmastir:
You were too nice. Had to change a small word :cool:
[Nexus 6P General] DrSeussFreak:
Thanks for this, followed step-by-step for root on stock ROM, worked without a hitch! Only issue I had was with Windows 10 and the ADB driver, but that took 2 seconds to resolve.
[Nexus 6P General] Heisenberg:
It's up to you, I chose to allow modifications. There's a beta version of SuperSU that roots without touching the system partition which would make taking an OTA a bit easier. As for the warning message, we can't do anything about that at this stage, but it's nothing to worry about.

You did something wrong then.
[Nexus 6P General] sirxdroid:
Finally opened the 6P box (I hate it when work gets in the way of my hobbies :) )

I'm on the D build out of the box with no sign of updates in sight, it claims I'm up to date. Oh well, so much for the prompt monthly security updates from Google :) No big deal, just playing with it for now and I'll flash the M build by hand at some point.

Unlocked bootloader, TWRP flashed, working with encryption. And I messed up and swiped on the prompt in TWRP to root it (I was not paying attention) and it was stuck on boot, but fixed it quickly by flashing system.img from the D official image.

A couple of questions:

(1) fastboot flashing unlock_critical

Do we need to do it in order to flash newer bootloaders? If not, what is it for?

(2) What's the "BP Tools" menu in the bootloader? I don't think I've seen it before on any Nexus devices.
[Nexus 6P General] Heisenberg:
1. Never seen that, where'd you see it? The normal unlock method (fastboot flashing unlock) allows you to flash anything, including the bootloader.

2. I have no idea, haven't touched it.
[Nexus 6P General] sirxdroid:
From the fastboot command help:
[Nexus 6P General] Heisenberg:
Ah, cool. It isn't needed, the usual method of unlocking allows all flashing that we need to do.
[Nexus 6P General] YandereSan:
Yep, seriously. Anyhow, I tried a second time and it rooted successfully. Not sure what happened the first time.
[Nexus 6P General] b33zy682:
same problem as the previous dude. unlocked bootloader flashed twrp 2.8.7.2 and got the mount decrpyt message . ignored it but can nandroid obviously. tried to reboot phone after twrp prompted me to flash SU and bootloop city.....i thought the latest version of twrp was to remove the decrypt thing
[Nexus 6P General] Heisenberg:
Did you follow all instructions in the guide? What build are you on? Did you flash the modified boot.img?
[Nexus 6P General] dark_saint:
Updating Rooted Device

I have successfully unlocked and rooted my devise. This is my first rooted device and I'm wondering about updating.

- If an OTA update comes out and I update do I loose the root?

- Is there another way to update my phone when a update comes out?

- Is there a way where I can update without deleting all my photos, contacts, apps....?
[Nexus 6P General] Heisenberg:
You have to remove root before taking an update, so yes you'll lose root. You can either take the update via the built in updater, or by flashing the factory images. Updates don't wipe your data.
[Nexus 6P General] adrman:
Search back in this thread. Several, myself included, have done exactly that by flashing the relevant parts from the factory images. You won't lose anything as long as you don't format userdata or flash the userdata.img.
[Nexus 6P General] :
Does that include having mods in /system ? Do you not have to remove them before flashing a firmware update?
[Nexus 6P General] adrman:
You'll lose anything you installed to the system like Busybox or Adaway modified hosts file. Fastboot flashing a factory image is exactly that, an "image" of the partition. When you flash it it replaces what was there before it. Taking an OTA will just apply the changes, therefore the no modifications requirement.
[Nexus 6P General] :
So that means every time I update (monthly security updates) I will lose any mods that were written in /system and will have to reapply them after. Does that include root status? Do most mods require to be in /system ?

I'm trying to understand how much work I'll have to do after every monthly update.
[Nexus 6P General] adrman:
It depends on the mods. I think ones like 3minit, etc... would need to be reapplied. And yes, you would need to flash SuperSU again. I think if you're planning on great amounts of customization, this might not be the best way for you. It might be better to wait for some custom roms to start appearing or check out Stephen's AnglerM rom in N6P Android Development. For the moment, I'm very happy with stock, Adaway and ElX kernel. Updating with that setup, took about 5 minutes.
[Nexus 6P General] Pmmac:
I am having trouble on a Mac. When I enter the command prompt, "fastboot flashing unlock" I get this:

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format

if supported by partition type)

-u do not first erase partition before

formatting

-s <specific device> specify device serial number

or path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address. default: 0x10000000

-n <page size> specify the nand page size. default: 2048

-S <size>[K|M|G] automatically sparse files greater than

size. 0 to disable

Macintosh-3:Android paulmacleod$

Macintosh-3:Android paulmacleod$

Macintosh-3:Android paulmacleod$ fastboot flashing unlock

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format

if supported by partition type)

-u do not first erase partition before

formatting

-s <specific device> specify device serial number

or path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address. default: 0x10000000

-n <page size> specify the nand page size. default: 2048

-S <size>[K|M|G] automatically sparse files greater than

size. 0 to disable

And nothing shows up on my phone. Am I supposed to enter in an option? I don't recall having this issue with my Nexus 7.
[Nexus 6P General] effraie:
You probably didn't updated your Android sdk. Follow carefully the guide...
[Nexus 6P General] Pmmac:
It is updated. Tried re-downloading as well. Several restarts of my computer too. Not sure what it is.
[Nexus 6P General] fredphoesh:
bootloop - or stuck on animated balls

Hello,

I followed the instructions:

unlocked bootloader

updated image contained in angler-mdb08k-boot.zip

rebooted to twrp

but then wanted to root, and saw I had to download su to my phone, so didn't want to boot it up again then download from the phone... (did not know how to sideload it to my phone) and saw I could install SU from TWRP, so did that (possibly the mistake)

Rebooted phone, and now it is in a loop, or rather, it is stuck showing the animated balls. It does not reboot as a normal boot loop does, it just gets stuck on the animation.

I subsequently learnt how to sideload the SuperSU file to my phone, so I did that and installed the zip using TWRP, but it still gets stuck, I also tried a factory reset, clear dalvik and cache, but no go.

Any tips other than to flash the stock rom back again?

Tx

Mark.
[Nexus 6P General] johnhazelwood:
I had the same issue when I did mine. You need the latest fastboot. What's the date stamp of your fastboot?

---------- Post added at 10:34 PM ---------- Previous post was at 10:30 PM ----------

I'm completely guessing at this, but since I believe SuperSU writes to system. You might try reflashing the system image from the factory image. (See section 8 of the awesome guide). Otherwise I'd reflash stock factory image completely and then go back to step 2.
[Nexus 6P General] Heisenberg:
I don't see you mentioning that you updated which is part of the instructions.
[Nexus 6P General] liquidicem:
I'm trying to update to 08M from 08K.

Bootloader is unlocked and everything worked great when I followed the guide, but now when trying to flash the new system.img file from the 08M build I get the following fastboot error:

load_file: could not allocate 2004185752 bytes

error: cannot load 'c:\angler\images\system.img'

Any thoughts? Thanks!
[Nexus 6P General] sirxdroid:
I lost track. Is there a MDB08M kernel modified for /system root that's hiding somewhere in some thread or modified K is still the one to use?
[Nexus 6P General] johnhazelwood:
Modified k works
[Nexus 6P General] Heisenberg:
Why though? That isn't an update, that's going backwards.
[Nexus 6P General] fredphoesh:
Yes, you are quite right!

I thought the installing of just the boot.img file from version MDB08M was enough... but reading the instructions again, it says to flash the entire new rom before proceeding to the next step...

I bet that is what most the bootloopers have omitted too. (BTW I used flash-all command to install the updated ROM, and that works fine... much easier than the step by step method).

Thanks for the help, now to restore all the stuff again - all this just to get the tap to wake working on my phone!

http://www.androidauthority.com/double-tap-to-wake-rooted-nexus-6p-653952/

Cheers,

Mark.
[Nexus 6P General] Heisenberg:
Well no, it says to update the build, not just the boot.img. Plus, updating just the boot.img would be pointless because you'd just overwrite it when you flash the modified K boot.img.
[Nexus 6P General] liquidicem:
I'm currently on K and trying to go to M.

Either way, any system img I try to flash is giving me the same error?
[Nexus 6P General] Heisenberg:
Oops, I read your post wrong. It looks like it can't locate the system.Img or something. Are you entering the path to the file correctly?
[Nexus 6P General] Kameechewa:
Can't Take Sccreenshots

I don't know if rooting caused the problem because I never tried to take a screenshot on vanilla but I am not able to now. Everytime I take a screenshot the phone vibrates and about 30 seconds later it gives me a bug report captured notification. I don't know how to read a bug report and it tells me not to share it with people I don't trust. What should I do? I've tried rebooting the phone but that did nothing.
[Nexus 6P General] Heisenberg:
I'm not sure why that's happening, I'm on the M build and rooted and can take screenshots fine.
[Nexus 6P General] Kameechewa:
Could you look at my bug report maybe? I don't really know how to resolve this or where else to go. I suppose I could unroot and reflash stock and what not but I'd rather not.
[Nexus 6P General] Heisenberg:
I wish I could help but I'm no good at reading those logs, they might as well be written in Klingon.
[Nexus 6P General] Kameechewa:
Same haha! So any suggestions on what I should do?