[Android Q&A, Help & Troubleshooting] indespair:
Greetings,

This issue occurred between Friday 7/26/2019 midnight and Saturday 7/27/2019 afternoon.

I found my nexus 6p in a boot loop at the 'Google' logo.

It's in a state where I can get to the boot loader with (power + vol down), but the only valid options, is a reboot (boot loops), reboot boot loader (works), recovery mode (boot loops)

I'm no stranger to tinkering with ads/fastboot, flashing other mobile (Samsung note , with odin, etc)

I'm aware of the main issues plaguing this mobile device (battery drain issue and the infinite boot loops - rampant 2017).

I've had the phone since 2015, and I don't remember honestly of flashing to factory and all of that -- probably did (as it was the reason to getting a nexus, rooting, loading custom roms, developer options, turning on debugging mode, etc).

I did replace my battery, I didn't really encountered the boot loop issue till now.

I don't know if the phone did an update or had an update pushed to it, but after going to bed Friday 7/26 (working phone) and when I woke up around noon on 7/27, I had a non-functional, google boot looping nexus 6p

I'm sure that the phone has been on developer mode, with oem unlocked settings, and other "settings" tweaked, such as the usb debugging option and how to handle connection (charging, media xfer, etc...)

Not sure if anyone else over the weekend had their Nexus 6P turn into a brick...

At this point, I would like to just be able to get to the point where I can connect via fastboot/adb (functionally) to pull off data, before any full wipe is done--if at all possible, else I will cut my losses...painfully as it may be. Yes, shame on me, should have backed up all of my pics/media files/contacts, etc...,

I do realize if the unlocking of the boot loader is done, it will also fully wipe system and user data, I've been googling all day and trying commands left and right.

the fastboot seems to be the only thing that connects...

the adb doesn't list any devices (went through kill-server, reconnect, etc...)

I will trying to provide whatever additional output that I'm able to get access to.

Last ditch effort, reach out to Huawei customer support and see if there's anything they can/will do.

If there's a chance to get it to a state where I can retrieve data off of it, I'm ok with moving on (abandoning nexus 6p) to another mobile device...

Willing to try and work with whomever and however long it takes if possible to recover...

==output

sh-3.2# ./fastboot devices

5VT7N15C03002060	fastboot

sh-3.2#

sh-3.2# ./fastboot getvar all

(bootloader) version:0.01

(bootloader) unlocked:no

(bootloader) hardware-revision:ANGLER-VN2

(bootloader) version-baseband:angler-03.88

(bootloader) version-bootloader:angler-03.84

(bootloader) display-panel:

(bootloader) charger-screen-enabled:0

(bootloader) max-download-size:	0x1d800000

(bootloader) partition-type:cache:ext4

(bootloader) partition-size:cache:	0x6400000

(bootloader) partition-type:userdata:ext4

(bootloader) partition-size:userdata:	0x1c3957ee00

(bootloader) partition-type:system:ext4

(bootloader) partition-size:system:	0xc0000000

(bootloader) serialno:5VT7N15C03002060

(bootloader) kernel:lk

(bootloader) product:angler

all:

Finished. Total time: 0.179s

sh-3.2# ./adb kill-server

sh-3.2# ./adb devices -l

* daemon not running; starting now at tcp:5037

* daemon started successfully

List of devices attached

sh-3.2# ./adb devices -l

List of devices attached

sh-3.2#

sh-3.2# ./adb reconnect

no devices/emulators found

sh-3.2#

sh-3.2# ./fastboot flashing unlock

FAILED (remote: 'oem unlock is not allowed')

fastboot: error: Command failed

sh-3.2#

==

sincerely

in despair