Database Users

Nexus 6P (Stock MMB29P) Stuck on boot after OTA, fastboot locked, adb sideload fails.

Hi
Since Friday my Nexus 6P freezes on boot animation logo.
I never tried to root my phone, neither force an updated on it (First time I went in recovery/fastboot mode was this weekend).
Friday morning I received a notification for an OTA update, so I clicked on it to install it and from this point my phone never started up again.
I tried many solutions but none of them worked, so I deciced to ask here finally as my last resort..
What I've tried :
Fastboot flash fails "device is locked" (and fastboot flashing unlock fails aswell because "oem unlock is not allowed" in dev options)
Recovery wipe data/factory reset works but my phone won't boot either (waited for ~1h)
Adb sideload OTA.zip (MMB29P → MMB29Q) fails "Verifying current system... System partition has unexpected content"
Nexus Root Toolkit (Flash Stock + Unroot with options Soft-Bricked/Bootloop) doesn't work
I run out of options, does anyone have another solution ?
Thank you

sorry I don't have ansewer except call google play support 855 836 3987

benrospars said:
Hi
Since Friday my Nexus 6P freezes on boot animation logo.
I never tried to root my phone, neither force an updated on it (First time I went in recovery/fastboot mode was this weekend).
Friday morning I received a notification for an OTA update, so I clicked on it to install it and from this point my phone never started up again.
I tried many solutions but none of them worked, so I deciced to ask here finally as my last resort..
What I've tried :
Fastboot flash fails "device is locked" (and fastboot flashing unlock fails aswell because "oem unlock is not allowed" in dev options)
Recovery wipe data/factory reset works but my phone won't boot either (waited for ~1h)
Adb sideload OTA.zip (MMB29P → MMB29Q) fails "Verifying current system... System partition has unexpected content"
Nexus Root Toolkit (Flash Stock + Unroot with options Soft-Bricked/Bootloop) doesn't work
I run out of options, does anyone have another solution ?
Thank you
Click to expand...
Click to collapse
Get to stock recovery using this guide, once there wipe cache partition then wipe data/factory reset. If that doesn't work call Google or RMA like error629 said.
http://www.androidexplained.com/nexus-6p-recovery-mode/

Read this thread. If I didn't know better, Id say it was yours.
http://forum.xda-developers.com/nexus-6p/help/command-t3308390
if your bootloader is locked and you didnt enable ADB in developer settings, you're out of luck
Contact google.

Soulfly3 said:
Read this thread. If I didn't know better, Id say it was yours.
http://forum.xda-developers.com/nexus-6p/help/command-t3308390
if your bootloader is locked and you didnt enable ADB in developer settings, you're out of luck
Contact google.
Click to expand...
Click to collapse
Yes exact same problem. I'll try to contact Google or Huawei then..

So I contacted Huawei Support (since I didn't buy it from the Google Store) and they told me to bring my phone to a PSM. PSM took my phone in charge and now I have to wait ~2 weeks (they send it back to Huawei). I'll update the thread when I get it back, this might be useful to somebody.

were on the same boat..
i remember a mate of mine uncheck the oem unlocking in the dev option.. then an OTA update came out and i updated it.. now the phone is stock only in bootloader. i wish i could enable the oem unlock.. but the problem is the phone wont boot normal.. pls help
im getting frustrated with my phone.. im thinking of overvolting the usb port with 12V so the dealership wont know about the reflashing

jeremmie said:
were on the same boat..
i remember a mate of mine uncheck the oem unlocking in the dev option.. then an OTA update came out and i updated it.. now the phone is stock only in bootloader. i wish i could enable the oem unlock.. but the problem is the phone wont boot normal.. pls help
im getting frustrated with my phone.. im thinking of overvolting the usb port with 12V so the dealership wont know about the reflashing
Click to expand...
Click to collapse
That would be fraud. Have you tried adb sideload?

No not yet.. i tried researching about sideload.. but i cant seem to understand it.. perhaps do you have any guide on how to do it? Would be really happy if someone post a guide.
---------- Post added at 08:29 AM ---------- Previous post was at 08:16 AM ----------
Also my nexus 6p wont enter recovery mode. It can only access the bootloader
So i cant make adb sideload to work because i cant access my recovery mode. It can only enter bootloader and barcodes and thats it.. pls help.. sigh..

jeremmie said:
No not yet.. i tried researching about sideload.. but i cant seem to understand it.. perhaps do you have any guide on how to do it? Would be really happy if someone post a guide.
---------- Post added at 08:29 AM ---------- Previous post was at 08:16 AM ----------
Also my nexus 6p wont enter recovery mode. It can only access the bootloader
So i cant make adb sideload to work because i cant access my recovery mode. It can only enter bootloader and barcodes and thats it.. pls help.. sigh..
Click to expand...
Click to collapse
If that's the case there's nothing anyone here can do or say to help you, your only option is sending it back for repair. Hopefully a lesson has been learned here.

Good morning
We should make group called nexus 6p bricked devices since we all got same problem .
I read in Google forum that March update released and some users got same problem after flashing it
So we have to make topic also called ( warning read before flash your ota ) at least to help new n6p users .

Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk

jeremmie said:
Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am happy to hear that hope mine fixed too , I think first thing you have to do is to unlock your bootloader and that's enough ATM .

jeremmie said:
Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
atef79 said:
I am happy to hear that hope mine fixed too , I think first thing you have to do is to unlock your bootloader and that's enough ATM .
Click to expand...
Click to collapse
I agree with this. Having an unlocked bootloader is insurance in case anything goes wrong in future.

Successful Unlock Procedure...!!!! FULLY TESTED and Close to Perfect...!!!!

Pre-requesites ::fingers-crossed:
1- Unlock premission granted.
2- Proper drivers installed.
3- ADB console should be able to detect your device via "adb devices" command.
4- In Developers setting tick on 'OEM Unlock' and turn on 'USB Debugging'.....Turn on 'USB Debugging Security' (Not necessary only telling you because i did that)
5-Not mandatory to attach the account under Mi Unlock Status bcoz many tried (Me also) but failed so don't worry if it fails for you also but do try to attach first.
6- MOST IMPORTANT THING - WAITING/PATIENCE. Kindly wait for atleast 7-8 days before trying unlocking or else like many you'll get "couldn't verify device" etc etc.
Now after 7-8 days :
1- Use older version of Mi Unlock App (because i used older version myself).
2-Log in and connect the device in fastboot mode and hit unlock and VOILA. Unlocked successfully.:laugh::victory:
I have attached the screens where i got permission sms on 9th March and Unlocked on 15th March (Yes like many I've been a fool and tried many times unlocking before waiting 7-8 days and FAILED ofcourse)
And there is no thing such as Unlocked only on Developer ROM or Global Stable ROM, it will unlock in any MIUI version whether Global Stable or Developer Version, its just a matter of Waiting for some days. I was convinced that i have to switch to Dev ROM but i tried on stable V8.1.15 and it unlocked successfully.:good::highfive:

abhipanthi said:
Pre-requesites ::fingers-crossed:
1- Unlock premission granted.
2- Proper drivers installed.
3- ADB console should be able to detect your device via "adb devices" command.
4- In Developers setting tick on 'OEM Unlock' and turn on 'USB Debugging'.....Turn on 'USB Debugging Security' (Not necessary only telling you because i did that)
5-Not mandatory to attach the account under Mi Unlock Status bcoz many tried (Me also) but failed so don't worry if it fails for you also but do try to attach first.
6- MOST IMPORTANT THING - WAITING/PATIENCE. Kindly wait for atleast 7-8 days before trying unlocking or else like many you'll get "couldn't verify device" etc etc.
Now after 7-8 days :
1- Use older version of Mi Unlock App (because i used older version myself).
2-Log in and connect the device in fastboot mode and hit unlock and VOILA. Unlocked successfully.:laugh::victory:
I have attached the screens where i got permission sms on 9th March and Unlocked on 15th March (Yes like many I've been a fool and tried many times unlocking before waiting 7-8 days and FAILED ofcourse)
And there is no thing such as Unlocked only on Developer ROM or Global Stable ROM, it will unlock in any MIUI version whether Global Stable or Developer Version, its just a matter of Waiting for some days. I was convinced that i have to switch to Dev ROM but i tried on stable V8.1.15 and it unlocked successfully.:good::highfive:
Click to expand...
Click to collapse
What error were you getting when trying to attach account ? Something like 86012 with chinese text ?
Please provide link to drivers.

abhishekr700 said:
What error were you getting when trying to attach account ? Something like 86012 with chinese text ?
Please provide link to drivers.
Click to expand...
Click to collapse
Yes the same one 86012 with some Chinese text... And till the end of unlocking I got that so I skipped it altogether and unlocked successfully.

Had to wait 7-10 days after I got unlock code to work.
Prior attempts were all FAIL at 50%....

abhipanthi said:
Yes the same one 86012 with some Chinese text... And till the end of unlocking I got that so I skipped it altogether and unlocked successfully.
Click to expand...
Click to collapse
Okay, I thought the error is with my phone so I factory reset it lol.
vignesh1985 said:
Had to wait 7-10 days after I got unlock code to work.
Prior attempts were all FAIL at 50%....
Click to expand...
Click to collapse
Thanks bud, I will wait and retry.

abhishekr700 said:
Okay, I thought the error is with my phone so I factory reset it lol.
Thanks bud, I will wait and retry.
Click to expand...
Click to collapse
Same error I got multiple trials... Be patient, give try after 10+ days... Gud luk....
I tried all other differetn solutions, nothign worked.

Yes, the universal truth is Absolutely Nothing will work before the waiting period. If you got all the right things and still stuck on 50% then just wait and don't waste your energy and precious time doing things which are unnecessary and frustrating...

vignesh1985 said:
Same error I got multiple trials... Be patient, give try after 10+ days... Gud luk....
I tried all other differetn solutions, nothign worked.
Click to expand...
Click to collapse
Yeah, I'm waiting.
abhipanthi said:
Yes, the universal truth is Absolutely Nothing will work before the waiting period. If you got all the right things and still stuck on 50% then just wait and don't waste your energy and precious time doing things which are unnecessary and frustrating...
Click to expand...
Click to collapse
This is really really frustrating man

abhipanthi said:
Yes, the universal truth is Absolutely Nothing will work before the waiting period.
Click to expand...
Click to collapse
Speaking from my experience with the Redmi Note 3 SE (Kate): Sorry, no. In many cases, unlock was possible after 3 days. In many other cases, it did not work. My device included, I never managed to unlock the bootloader. Tried different computers, software, waiting, dancing around a camp fire. No success. Finally I sold the RN3 phone, and I hope you are right and it will be better with my soon arriving RN4X TW-Edition.

I know the feeling...
dieterhaack said:
Speaking from my experience with the Redmi Note 3 SE (Kate): Sorry, no. In many cases, unlock was possible after 3 days. In many other cases, it did not work. My device included, I never managed to unlock the bootloader. Tried different computers, software, waiting, dancing around a camp fire. No success. Finally I sold the RN3 phone, and I hope you are right and it will be better with my soon arriving RN4X TW-Edition.
Click to expand...
Click to collapse
The sole reason is to create this thread was only this that people (like myself) who love to mod their device don't waste their precious time and energy finding a way to achieve which can't be achieved without waiting enough. I know waiting is frustrating but it is the solution.
And Best of Luck for your new device and I'm sure you'll be able to do whatever you wish for.. :good:

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

oem unlock is not allowed

I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.

jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
Click to expand...
Click to collapse
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk

Minh Dao said:
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks, I saw this post and was trying to follow steps described there, but 9 steps is about unlocking bootloader and I cannot pass it...

Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.

redduc900 said:
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
Click to expand...
Click to collapse
in post I mention that it's phone with bootloop issue

And I told you why you can't unlock the bootloader.

redduc900 said:
And I told you why you can't unlock the bootloader.
Click to expand...
Click to collapse
so that's it - no way to make it work again at all? (

I tried this but I couldn't make it work.
rootmygalaxy.net/unlock-bootloader-on-huawei-devices/
which leads to
emui.huawei.com/en/plugin/unlock/detail
but no matter how hard I try, I keep getting:
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."

Try enabling OEM unlocking in developer options

Unfortunately can't when it's stuck bootlooping.

bcurran3 said:
Unfortunately can't when it's stuck bootlooping.
Click to expand...
Click to collapse
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Yeah, I tried the freezer trick. In fact I put it in there and forgot about it for a week! HA! Didn't work. I'll need to try the hairdryer trick.
I'm REALLY hoping Google responds to the boot.img signature files request....that would make life so much simpler. I'm probably going to shelve this project for the 4th or 5th time and wait a few weeks. (I've been dealing with this since Feb or March.)
I did put in another call to Huawei today. The next available representative was nice but told me that Huawei global unlocks the bootloader for people in China but not the US. I had him open a case to get the bootloader unlock code and pass it up the chain. I doubt it will result in anything...but at least the request is officially in.

OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too

draxz said:
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
Click to expand...
Click to collapse
I just fixed my phone and thought I would post my method:
For the people with boot loader locked (You CANNOT do anything with it being locked) I just revived my phone:
You need to heat the phone by using a blow drier for about 5-10 mins while in boot loop - in my case I don't have a blow drier so I turned the stove to medium heat and kept the phone about 10 centimeters above the heat. After 10 mins the phone miraculously booted up and went to "Setup as new phone" (I had wiped the device earlier) after setting it up, I immediately went into the setting to unlock OEM and after 15 mins the phone went into the boot loop again. I followed the instructions on this page https://www.xda-developers.com/nexus-6p-bootloop-fix/, a huge thank you to XCnathan32 and voila the phone works. Thank you XCnathan32 and other, please thank him by clicking the thank you button on his page or by making a donation as a gift.

I wish I was having luck.
Over the past two weeks we've had multiple 100+ degree days in Los Angeles. I threw my 6p on the charger in my OUTSIDE office. The phone got hot as hell. I tried for days to get it to boot up with no joy. I did get the NO COMMAND screen a couple times. One time I actually got to it fast enough to interact and hit the right keys to go and wipe it again. (I wiped it months ago too.) One time I accidently hit install update from SD card (always makes me laugh as there is no SD card) and I think it said it was installing the update from the SD card (again I laughed) but my guess is that's just the default graphic to display from the menu choice even if it doesn't do anything.
Anyways, for 3-4 days in 103-111 degree heat I tried for multiple multiple hours. The phone would never boot to the setup screen for me to go and turn off the OEM unlocking. I thought maybe the cores were still going full bore since it was sitting on the charger and I tried pulling it off a few times...but the battery was never charged enough to do anything.
I'm still at a loss.
Any new developments or suggestions?

unlocked oem problem. help!
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.

aphrodirish said:
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
Click to expand...
Click to collapse
If you bought your Nexus 6P via Google Store you can get a New Google Pixle XL even after the 1 Year device Guarantee
maybe your lucky enough
reddit.com/r/Nexus6P/comments/6y1tm2/official_6p_battery_shutdownbootloop_rma_thread

bcurran3 said:
I'm still at a loss. Any new developments or suggestions?
Click to expand...
Click to collapse
Get a good blow dryer or heat gun? A typical blow dryer will only reach ~140F on a good day. A decent heatgun will start around ~500F and go over 1000F. You're supposed to start with the device bootlooping and apply heat until the phone boots. My guess is you are not hot enough and/or not getting the heat to the right area on the back of the phone. Bear in mind this will just give you enough time to get into Dev Settings and toggle OEM Unlock so you can unlock your bootloader and flash a custom kernel like EX.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Update:
Based on "Google is replacing defective Nexus 6P units with Pixel XLs, but only in North America"
https://www.phonearena.com/news/Goo...h-Pixel-XLs-but-only-in-North-America_id98059
Just got off the phone with Google (10 hours ago) and confirmed they are replacing my dead/looping Nexus 6P out of warranty and swapping with a Pixel XL. It took me SIX MONTHS to get this resolved. I'm not happy about the time frame, but I guess I'm pseudo-satisfied with the end result.
For those who attempt a replacement, the KEY WORDS that seemed to make the customer service rep take notice was that mine started bootlooping after installing the 7.1.2 beta sometime in March. This is where her ears perked up and she started two "escalations" to get approval for "extend warranty" and replace my phone. Hope this helps you out.
The irony of this is, I'm going to give the Pixel XL to my wife, continue using my LG V20 for the moment, and try to determine if I want to spend the bucks on a Pixel 2 XL or a LG V30 later this year.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Try this
Try finding the OEM unlock code for your specific mobile from Huawei customer service site

[HELP] Unlock bootloader.

Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.

Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..