Related
There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472
Since I got my Nexus 6P sometimes it could just hang and then restart, I thought this was nothing major so I did nothing about it. Today however, I got a couple of these restarts in one day and after the last one I can't boot. The unlocked bootloader message appears, then the Google logo and after that it keeps looping. I can get into bootloader, however when I try anything there (boot into recovery, BP tools or "factory") it just starts looping again. I have tried restoring nexus 6p system images with Google's "flash-all" bat file, and with Heisenberg's method on 2 different android versions and it goes through without problem, however I'm still stuck in a bootloop.
Any help would be appreciated.
Thanks.
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
RoyJ said:
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
Click to expand...
Click to collapse
I've been through 5 so far. I'll give them a call tomorrow morning and see how it goes. Hopefully the warranty still covers me. I've done some digging around, and what is happening to me is the exact same thing as what is happening to some people through the OTA nougat update, with the only solution being exactly what you said.
I just really hope I can actually get a replacement as I have done nothing wrong on my side, it seems to be purely Huawei's fault. Thanks anyway.
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
domdomrys said:
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
Click to expand...
Click to collapse
How did they saw if your phone was rooted? Did you told them?
GKti22 said:
How did they saw if your phone was rooted? Did you told them?
Click to expand...
Click to collapse
The guy at Huawei didn't really know what the warranty covers. I mentioned trying to restore from Google's factory images (implying that I unlocked the bootloader) and he said that this might have voided the warranty (which I'm pretty sure it hasn't) as it is a software modification in a sense, but he's not entirely sure. They're going to send me a box to send the phone to them, and through that they'll be able to tell that no modifications have happened I hope (it's technically all stock and unrooted now, it just doesn't boot up). If they do try and charge me, I'll call the actual repairs team (as they're not available today) and explain the situation. No way am I paying for something like this as it hasn't happened through my own fault.
Under Europe regulations THEY have to formally prove the software modifications lead to the hardware fault (if that's a hardware fault) and that would be really bad publicity for Huawei. Not sure how UK applies that to its local right.
Root may very well void the warranty based on an old thread on XDA here that's buried in the general section somewhere, but an unlocked bootloader absolutely will not void the warranty.
Hi, can someone please upload the build.prop for nexus 6p 7.1 dev preview, I did some changes and now stuck in boot loop, also the backed up copy that I have has previous version names and all according to 7.0 , I am stuck in twrp and don't have computer then how is it possible to make changes directly from twrp terminal, I tried "vi build.prop" and was able to see build.prop but couldn't edit, Thanks
Here you go https://paste.debian.net/897221
For anyone wondering, I got the phone the other day and they fixed it under warranty. No extra costs or anything (I enclosed a letter giving proof as to why I believe it should still be under warranty, and it worked fine). The serial number and IMEI has changed, so it leads me to think that it was indeed a motherboard failure. Thanks for the help!
From 4 days , I decided to root my device and I installed and flashed the latest releases of TWRP AND SU from this forum ..and I followed the steps carefully which ended up in wiping all the phone data + damage in software.. I took the phone to Huawai center to get it fixed .. They said that I have a virus that completely damaged the hard drive and some parts of the motherboard and EVEN they could not fix it and thanks god they gave me a new phone although I broke the insurance by unlocking the bootloader but they didnt notice. Finally, I would like to advice all people here who are looking for a root not to try anything at this forum because it is not explained properly and TWRP is not safe at all.
Moataz94 said:
From 4 days , I decided to root my device and I installed and flashed the latest releases of TWRP AND SU from this forum ..and I followed the steps carefully which ended up in wiping all the phone data + damage in software.. I took the phone to Huawai center to get it fixed .. They said that I have a virus that completely damaged the hard drive and some parts of the motherboard and EVEN they could not fix it and thanks god they gave me a new phone although I broke the insurance by unlocking the bootloader but they didnt notice. Finally, I would like to advice all people here who are looking for a root not to try anything at this forum because it is not explained properly and TWRP is not safe at all.
Click to expand...
Click to collapse
Don't believe in everything that people tell you!
What do you mean ? What zips/IMG/TWRP did you flash?
I rooted my phone based on instructions in XDA and everything is working as it should.
What type of virus is it? Can you be more specific please.
Moataz94 said:
From 4 days , I decided to root my device and I installed and flashed the latest releases of TWRP AND SU from this forum ..and I followed the steps carefully which ended up in wiping all the phone data + damage in software.. I took the phone to Huawai center to get it fixed .. They said that I have a virus that completely damaged the hard drive and some parts of the motherboard and EVEN they could not fix it and thanks god they gave me a new phone although I broke the insurance by unlocking the bootloader but they didnt notice. Finally, I would like to advice all people here who are looking for a root not to try anything at this forum because it is not explained properly and TWRP is not safe at all.
Click to expand...
Click to collapse
A virus which "damages" hard drive and motherboard, is new for me. Does the phone have an hard drive at all?
And they don't notice the unlocked bootloader, but they replaced the phone with void warranty.
Really?
mandelbort said:
A virus which "damages" hard drive and motherboard, is new for me. Does the phone have an hard drive at all?
And they don't notice the unlocked bootloader, but they replaced the phone with void warranty.
Really?
Click to expand...
Click to collapse
I mean the storage for the phone instead of 32 gb was 0 gb .. when I entered TWRP Recovery it showed me that .. and yes they replaced it for me .. My warranty appeared as active at their computers .. it didnt recognize that i unlocked the bootloader,, but i went to them on the same day so maybe that's why.
morpheus302 said:
What do you mean ? What zips/IMG/TWRP did you flash?
I rooted my phone based on instructions in XDA and everything is working as it should.
What type of virus is it? Can you be more specific please.
Click to expand...
Click to collapse
First of all , I downloaded the ADB drivers to my pc then I downloaded the TWRP 3.0.3 from the forums here.. then I flashed it to my device thru fast boot and then I added the SU 2.79 zip file which i downloaded from here as well then I went to TWRP Recovery and Pressed install on the SU , and what happened is that during the installation the device reboot immediately without installing which caused some sort of wiping data and staff which I did not understand.. and found my phone stuck at the screen which says this device is untrusted.
It showed 0 because of data encryption ¯\_(ツ)_/¯
Glad you have a new phone with no problem. If you want to avoid all this trouble in the future, keep your phone as stock as possible and wait for official updates for your model.
I told before and I say it again: Don't believe in everything that people tell you!
The "expert" in the technical center gave you very bad information, due to lack of knowledge (which is ok, normally they just know the necessary basics to make a quick diagnostic and later forward the phone for the repair center).
And you don't void warranty if you request the bootlader code from Huawei, they provide an official service for that! Also, even if you unlock your bootloader, Huawei is not informed about it! So no problem there.
I'm 99% sure that, following some tutorials that you can find in this same forum, you could get your phone back working again.
Nevertheless, good that you have a new one and I advise you to keep it stock.
Lol i can guarantee you this was no virus. Can you post a link to the guide you followed?
ViCioPT said:
I told before and I say it again: Don't believe in everything that people tell you!
The "expert" in the technical center gave you very bad information, due to lack of knowledge (which is ok, normally they just know the necessary basics to make a quick diagnostic and later forward the phone for the repair center).
And you don't void warranty if you request the bootlader code from Huawei, they provide an official service for that! Also, even if you unlock your bootloader, Huawei is not informed about it! So no problem there.
I'm 99% sure that, following some tutorials that you can find in this same forum, you could get your phone back working again.
Nevertheless, good that you have a new one and I advise you to keep it stock.
Click to expand...
Click to collapse
Some users voided warranty by unlocking bootloader. Service says unauthorized
interference in firmware by user
Should have read better the guides and threads Many people were in the same or similar situation including me but finally got their phones working with root
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:
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