yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Heisenberg:
Why did you only flash those images, and not the bootloader and radio as well? The bootloader and radio usually need to be flashed first because they're prerequisites for the other images. That's why my instructions are written the way they are, if you stray from the carefully prepared instructions you can end up in trouble like this. That's one possible scenario. Another possible cause is that you were decrypted beforehand and the phone was performing a forced encryption on the first boot, you interrupted this process which causes a loss of all data.
[Nexus 6P General] mobileman88:
I did a md5sum of the bootloader and radio as they had the same filenames . They are exactly the same for this release.

I understand from [MENTION=4684315]flar2[/MENTION] that I should not have rebooted to system as I was using a custom kernel. Realized it too late. Phone was somehow doing encryption of the SD (I don't recall decrypting it at any point in time, all I did was systemless root+xposed79+ex1.03 kernel).

Does the phone perform forced encryption upon each rom update?

Flar2's instructions is to do the following :

1. Flash boot, vendor, system

2. reboot to recovery

3. flash supersu

4. wipe cache+dalvik

5. boot into system

6. install ex kernel

Flar2's post at http://xdaforums.com/showpost.php?p=64648031&postcount=2504

Bleeding edge always bleeds. :eek:
[Nexus 6P General] adrman:
The bootloader and radio are identical on these two builds. I updated in much the same way: flash boot, system, vendor, recovery, format cache, boot twrp and install SuperSU, however I was encrypted and wasn't using xposed or Ex kernel. [MENTION=1306570]mobileman88[/MENTION] must have been unencrypted before booting the new stock kernel.
[Nexus 6P General] mobileman88:
Possibly but I never did any encryption or decryption prior to today. All I did was unlock, root and install ex kernel. Should I have performed the steps below to prevent this from ever happening again :

http://xdaforums.com/showpost.php?p=64648031&postcount=2504

This is a really painful episode. Is there any way I can check if I am encrypted? I just used the stock rom.
[Nexus 6P General] mobileman88:
In Settings -> Security -> Encrypt Phone , the setting says "Encrypted" so does it mean the device is encrypted? When I flashed system+vendor+boot+cache, during the first boot, it tried to re-encrypt the entire device yet again? It seemed very hot for 30 minutes without any status shown swhich is why I rebooted the device. I should have gone into recovery and flashed supersu before rebooting unfortunately.
[Nexus 6P General] adrman:
Yes. You're encrypted now. Personally, I don't see any performance gain from decrypting, so I stay encrypted. Flashing SuperSU before rebooting wouldn't have helped, but Flar2's instructions would have kept you unencrypted. That's because ElX doesn't force encryption, but the stock kernel does. The moment you booted into Android with it, it started the encryption process.
[Nexus 6P General] mobileman88:
Shouldn't it have been encrypted before too since I did not do anything to stop it?
[Nexus 6P General] adrman:
That one I can't answer for you. Sorry. I can only assume that if the device encrypted itself after flashing and booting the stock kernel, it was decrypted prior. I've seen some reports about devices that somehow unencrypted without wiping userdata in fastboot or recovery, but never witnessed it firsthand.
[Nexus 6P General] blazecap:
So to update from MMB29M to MMB29P with an unlocked bootloader, and root, should I follow the instructions below? I am looking to preserve my internal storage (music, videos, pictures, etc.), and my apps.

Do I do this?

1) Download full factory image of MMB29P

2) Extract the contents of the MMB29P factory image.

3) Perform the steps below to flash the latest images (correct me if I am wrong in having to flash all of these).

fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.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

From doing the above, would I need to re-root?

Thanks
[Nexus 6P General] mobileman88:
Well.. it's quite an experience I must say. Learnt to be much more careful next time.

---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------

fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.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 system C:\angler\images\system.img

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

You can skip

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

After vendor.img, please boot into recovery. Then do the following which I did not do and nuked my device.

- Boot into TWRP recovery

- Install supersu 2.66

- Clear cache

- Clear Dalvik

- Reboot system

Add the 5 steps above and you are good to go. <<Do not flash recovery.img >>
[Nexus 6P General] blazecap:
Perfect! Worked liked a charm.

Thank you very much, good instructions.
[Nexus 6P General] Big Cam:
[MENTION=4153349]Heisenberg[/MENTION] Hey I am still on 6.0, I've been delaying upgrading to 6.0.1, and I've finally got time, I know the steps, going to follow step #10 of the first post in this thread.

My only 2 questions are this, since 6.0.1 has come out, there are now 2 images on Googles site, can I just take the newest which I assume is the one with the P

6.0.1 (MMB29M)

6.0.1 (MMB29P)

Also thanks to [MENTION=1306570]mobileman88[/MENTION] the post directly above mine answered my second question.
[Nexus 6P General] mobileman88:
Take the latest
[Nexus 6P General] mobileman88:
You got to thank [MENTION=4153349]Heisenberg[/MENTION] and [MENTION=4684315]flar2[/MENTION] too. I learnt much from them.
[Nexus 6P General] runawaybayeh:
I'm trying to update to the latest variant of 6.01 as well, but keep getting 'unable to load... I have the file unzipped, and the proper files in folder' angler/images in c drive.

"error:cannot load 'C:\angler\images\radio-angler-angler-02.45.img"

I probably am missing something basic, any ideas?

Ok,I think I see what Im missing.....
[Nexus 6P General] Vref:
I have Windows XP sp2 on my Macbook running through VM fusion. Does anyone think running something so out of date will be a problem when rooting the 6P?

Ive tried rooting devices in the past just using the Mac terminal but I'm not a super computer guy. I can follow directions and I rooted my old Incredible and Rezound so I have rooting experience but not recently.
[Nexus 6P General] SlimSnoopOS:
Just use OSX to do everything. I'm using MBP on OSX 10.10.5 and didn't run into any issues. The only thing is, you will likely need a program to open the factory image file (.tgz), I use Keka. I'm a first time user of terminal on OSX. Every command just needs to begin with this "./" without quotes. So, open terminal and instead of writing "adb command " then hit enter, on OSX we begin each command like so:

./adb

or

./fastboot

Edit: Just to add an example, I store my Nexus 5X files on my desktop in its own folder. If I had a 6P, this is how I would flash any .img:

./fastboot flash boot /users/Myusername/desktop/angler/boot.img

I used this guide as my guide to use for OSX and terminal. I write out each command though, I did not do the bash or export stuff.
[Nexus 6P General] Heisenberg:
Just use the latest, which is MMB29P.

Do you have file extensions turned on or off in Windows Explorer?
[Nexus 6P General] runawaybayeh:
I now have it on.thanks

also, i see that mobilman doesn't include the bootloader for angler,is that alright?
[Nexus 6P General] VanGolfer:
So these steps give you a system with encryption disable, right? Could you please confirm? Thanks
[Nexus 6P General] mobileman88:
The bootloader and radio for this build is the same as the earlier 601 build. But if you are coming from 600 then you need to flash the 2 files

---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------

Yes. If you do not not system after flashing it. Go to twrp and flash supersu then boot
[Nexus 6P General] jsc10:
Cannot flash

Hi there,

I'm stuck on step 2, I get an error on platform tools when trying to flash the recovery, it says that cannot load the image. Any help?
[Nexus 6P General] azsl1326:
Just flashed the lastest security update MMB29P - system.img / vendor.img and then flashed the latest ElementalX-N6P-1.04 along with root and get the following error: "There’s an internal problem with your device. Contact your manufacturer for details."

Phone seems to be working okay, but I get that message everytime I restart. I have a nandroid and can revert but wanted to know if this error is correctable?

Thanks, in advance.
[Nexus 6P General] mobileman88:
Did you unlock your bootloader? [MENTION=4153349]Heisenberg[/MENTION] has great instructions for it in the OP

---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------

If it is the bootloader message, it's normal since your bootloader is unlocked
[Nexus 6P General] mbutandola:
[MENTION=4153349]Heisenberg[/MENTION], first thank you for this very useful guide. I've got a question and hope you might enlighten me on this.

You say "Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).

Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:...

Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:..."

Would it not be simpler if we just unzipped the .tgz then the .tar files and just move all the necessary files to the appropriate folders ?

Cheers
[Nexus 6P General] mobileman88:
There's a big zip file inside the. Tar. Gz file. Unzip it to get at the. Img files
[Nexus 6P General] azsl1326:
No, I get this message when the phone finished booting into Android. I can dismiss it - but clearly something isn't right.
[Nexus 6P General] Big Cam:
So I did this, exactly, except I re-flashed twrp after the vendor.img, since I've read you can loose your recovery, and then I booted into recovery, and flashed supersu, and then cleared the cache/dalvik.

I got the message that my device is corrupt upon reboot, and now I'm at the spinning colorful google logo for going on 5+ minutes. Did I somehow mess this up?

Going on 10+ minutes of the colorful google logo just doing it's animation.

15 minutes, how do I get out of this logo? Really missing removable batteries right now.
[Nexus 6P General] mbutandola:
I know. I didn't get into any issues. Just found it simpler to just unzip those files and of course unzip that big zip file in the end rather than opening the archive.

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] Big Cam:
This is the message I get when I turn it on, it then goes to the spinning colorful android logo endlessly.

What happened? I followed the directions above.

So I can get back into TWRP, I guess I could go to the backup I made right before, but I really want to get this upgraded and done.
[Nexus 6P General] jsc10:
Yeah, I already unlocked it and checked it in the bootloader, but the problem persists any idea? I tried with twrp 2.8.7.2 and also the 2.8.7.1 neither work
[Nexus 6P General] Big Cam:
Well I restored to my backup, this process failed me miserably. I'll check back in the morning, see if anyone has any ideas.
[Nexus 6P General] Big Cam:
And now I get this, WTH is going on, how can this happen from factory images.

EDIT: Sorry for the upside down pictures, using an old phone.
[Nexus 6P General] mbutandola:
Are you sure you flashed vendor.img?

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] Big Cam:
I am 99.9% positive I did the first time, in fact I know I did, because it is a separate "enter" after I copied and pasted what I had in my text file., pasted below.

regardless, I restored to my backup (thank god) and tried again, this time I did not flash TWRP after vendor, and just booted into TWRP through recovery and boom, recovery was there, I then flashed SuperSU 2.66 and it took forever to boot up, but it did, and the corrupt error is gone.

Now, when I check system, I am now on 6.0.1 but I still have the notification that the 6.0.1 upgrade is available.??????

What I flashed:

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

fastboot reboot-bootloader

fastboot flash radio C:\angler\images\radio-angler-angler-02.50.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 system C:\angler\images\system.img

fastboot flash vendor C:\angler\images\vendor.img
[Nexus 6P General] zer0se7en:
Updated and rooted. Thanks to this guide!
[Nexus 6P General] Big Cam:
Do you still have the notification that there is an update available?
[Nexus 6P General] zer0se7en:
None. Even the EX app stopped giving update.
[Nexus 6P General] HaXoReD:
Thanks!

Probably isn't necessary to back up the vendor image. I just do it because i'm new to nexus devices, coming over from usually rolling samsungs and vendor image is new to me so I treat it like EFS. I only do it for first nandroid just in case I need it. If concerned with space you can always through it on your PC or OTG flash drive or something.

Yes, in trying to restore my original nandroid that I made when I first got the 6p, I restored the boot.img in TWRP, but I kept having the problem with it saying bootloader corrupt and not going past the google screen with little unlocked padlock at bottom. This leads me to think that the boot.img that TWRP makes perhaps doesn't 'get it all' and the changes to the boot.img that supersu 2.62 made weren't 'un-done' by restoring the old, pre-modified boot.img in my original nandroid.

When I set off on this little test I was mainly just curious about how using a lockscreen protected phone would affect nandroids. I had in mind that I was going to dump everything (except internal data) anyways and reflash the latest factory 6.0.1 and use the newer supersu 2.66 to re-root so I wasn't too worried about getting my original nandroid to work or not.
[Nexus 6P General] rhys100:
I have brand new phone. Followed steps and have twrp-2.8.7.2-angler.img installed - However I can't boot, just get a boot loop with it loading... any tips to what I have missed?
[Nexus 6P General] Big Cam:
So if. I take the Ota with an unlocked bootloader and root, I'm assuming I'll lose root, but I can just re flash it afterwards right? Or will I lose twrp too.
[Nexus 6P General] mbutandola:
You'll loose twrp

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] Big Cam:
OK, but my bootloader will still be unlocked right? So I can just go flash it again via adb? Followed by root?
[Nexus 6P General] mbutandola:
It won't lock the bootloader. I prefer flashing the boot image manually though. Having a Nexus makes those things easy. ☺

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] Big Cam:
OK, all I want to do is get this notification to go away that says 6.0.1 is available.

My phone says I'm on the latest, so I'm not sure what to do, that's why I was thinking about just taking the Ota, to shut the thing up.
[Nexus 6P General] mbutandola:
It should say that your system is up to date. Just a stupid question : you did flash the right image, didn't you?

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] Big Cam:
Ya, I just downloaded it last night from Google. Flashed exactly what was talked about above, and I now have this.

Also when I boot to recovery, or rather right before that at the green android, I ahve these for the top 3.

BL: angler-02.45

Baseband: angler-02.50

Product/variant: angler-vn2

The 02.45 and 02.50 were from the latest MMB29P zip
[Nexus 6P General] JoKe_42:
You could press long on the notification and block it.

Regards,
[Nexus 6P General] Big Cam:
I kind of went a different route but thank you for the suggestion, after long pressing it reminded me that this is google play services, so I went to the app and cleared all it's data and rebooted. When it started back up, it said the update was available again so I clicked on it, and it brought me to the software update page but then it took a second to load and it changed from saying their was an update with a restart required, to saying last check a minute ago, and that's it's up to date.

Not sure why I had to go through all that, but none the less I'm on 6.0.1 and that pesky message is gone.
[Nexus 6P General] swapgut:
We got our pair of 6P's and they're not cooperating yet. Spent frustrating time yesterday without getting adb or fastboot to work properly yet. Great guide Heisenberg, not new to unlocking or s-off something is just not right with either my pc or 6P now. I perused the first few pages from this thread and the q&a one. Going to try Koush's universal adb driver soon.

Our 6P's would not do a thing after charging and turning them on except update. Skipped the wifi setup `cause I didn't realize the Nexus showed the MAC addy at the bottom of that long list (nice) and I use a firewall whitelist. After that it was update or go back!

We're on MMB29M with Angler VN2's. In the bootloader I tried different choices with the "arrow" field start, reboot, recovery, factory and it made no difference. Tried different settings for the usb attachment too. First thought was use usb2 instead of usb3, adb version is all that worked here. If it's windows downgrades that won't let my win7 x64 rig do this I might even put together a recycled rig from the closet to get a virgin win7sp1 pc hooked up to the monitor.

First thing first....... read, ask, patience (gotta have AdAway at a minimum). Free from at&t's "clerical billing errors" at last!!! had them since 1998.....
[Nexus 6P General] kevwo:
hi all! quick question. my friends phone is bricked (stuck in a bootloop), and he said try and fix it. When i use "fastboot flashing unlock" I get a message "OEM Unlock is now allowed". I know that you have to check off the OEM Unlock option on the phone, but how can I go around that if the phone is stuck in a bootlop?
[Nexus 6P General] NPOA556:
You can't. If that option was not enabled, you will not be able to unlock the bootloader. Just curious, how did it get stuck in a bootloop if your friend never unlocked it and "messed" with it (flashed stuff)? I could be wrong, but that seems extremely unlikely to happen to a stock phone.
[Nexus 6P General] a1exus:
can't you bring it to stock by re-flashing everything and go from there...
[Nexus 6P General] bensf:
Great thread, extremely helpful. Will there be a modified boot image for MMB29P? I'm staying with traditional roots since systemless breaks wifi calling on T-mobile every time for me.
[Nexus 6P General] kevwo:
i have no idea what they did, honestly. but in the bootloader it shows :

BL: angler-02.01

Baseband: angler-02.15

Product Variant: ANGLER-VN1

Serial Number: yada yada

CPU: MSM8994 0x20001

32gb samsung

3072MB Samsung LPDDR4

Console: NULL

Battery is OK

Device is LOCKED

Qfuse Status: ENABLED

Off-mode-charge: ENABLED

Download Mode: DISABLED

---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------

I would definitely try that...would you mind pointing me in the direction of how to just reflashing without unlocking bootloader? im stumped
[Nexus 6P General] a1exus:
Try Step #11 in OP (just without "fastboot flashing lock" to lock bootloader since it's already locked)
[Nexus 6P General] belloni:
I've completely wiped everything, including internal storage to start fresh with the newest nexus image. Followed the guide, downloaded 2.66, flashed in TWRP, rebooted redownloaded all apps but no root? Not sure what to do, shall i flash UnSu and try again?
[Nexus 6P General] Big Cam:
Did you flash the supersu that you downloaded, or did you use the one that TWRP offers? That one they offer causes problems.
[Nexus 6P General] belloni:
Fixed it.
[Nexus 6P General] janedoesmith:
I'm on 29P with systemless 2.66 and WiFi calling on T-Mobile is working for me.
[Nexus 6P General] Flipnautic:
Hi everyone, quick question: "Will formatting my data partition to decrypt my phone, erase my current rom and downloads? Will I have to reflash the entire rom and Gapps? Thanks in advance.
[Nexus 6P General] bensf:
Don't know why but WiFi calling works on my phone with MDB08M, MMB29N and MMB29M but as soon as I install twrp 2.8.7.2 and flash SuperSU v2.62-3, 2.65 or 2.66, it goes away :crying: Spent some time trying out each combo yesterday, lol.

Currently I'm on MMB29M with traditional root with SuperSu v2.52 and WiFi calling works great. That's the reason I'm wondering if a modified boot.img is available for MMB29P.
[Nexus 6P General] Heisenberg:
You can't flash anything with a locked bootloader, it's impossible. You can't unlock the bootloader if the option isn't enabled in Developer Options. Unfortunately there's nothing you can do.
[Nexus 6P General] Heisenberg:
The bootloader is locked which means nothing can be flashed to the device, that's the point of bootloader security.
[Nexus 6P General] Heisenberg:
Formatting your data partition won't decrypt your phone, it's the userdata partition that you need to format in order to decrypt. Data and userdata are two different things. And no, you wouldn't need to reflash anything, your ROM/gapps reside in the system partition.
[Nexus 6P General] a1exus:
not even stock images?
[Nexus 6P General] Mesmurized:
Thanks for that, I'm still learning. Can you provide more details about the difference between data and userdata?
[Nexus 6P General] force70:
He did say nothing can be flashed....yes that includes factory images

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[Nexus 6P General] NotoriousBLT:
Would you mind telling how you fixed it? I'm having the same problem after stupidly installing the TWRP Super SU without reading the warning...
[Nexus 6P General] Heisenberg:
Nothing at all. Think of it like a door, if it's locked nothing can get through.

Without getting too technical, userdata encompasses all user data (apps, settings, plus your internal storage). Data contains only apps and settings. Data is found within userdata, so if you wipe userdata you wipe everything (apps, settings, photos, music, etc). If you wipe data your apps and settings are wiped, but not your photos, music, etc.
[Nexus 6P General] Mesmurized:
Thanks. That exactly what I needed. :)
[Nexus 6P General] swapgut:
Again , Thanks Heisenberg. Got it worked out per your directions except my pc refused to take the SDK right. Discovered Koush's universal adb driver, tried that and everything worked like it was supposed to.
[Nexus 6P General] mbutandola:
One thing doesn't sound right here. How do you manage to brick a nexus phone without unlocking the bootloader? The good news is, because the bootloader is locked, you can send the phone to customer service

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P General] ^tyrant^:
Looks like the monthly security update is out..
[Nexus 6P General] @home:
Yeah mine came up & downloaded but failed it install, I'm rooted but I have stock recovery.

Anyone know why it's failing?

Ta
[Nexus 6P General] Mesmurized:
The way I understand it. Any boot, recovery, or system changes will cause OTAs to fail.
[Nexus 6P General] ^tyrant^:
systemless root? i think i remember reading that root will cause it to fail.. but i dont remember for sure..

Ill be doing the manual update and reroot/recovery tomorrow
[Nexus 6P General] @home:
I thought as long as you had stock recovery updates wouldn't fail?