Database Users

device not unlocked cannot install image oneplus 2

Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help

http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257

I have tried all those methods and none of them worked for me

pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.

I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem

Can anyone please help me with this?? :'(

pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008

eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down

pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.

eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj

pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??

eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?

pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password

eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953

pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me

Problem Solved

Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...

CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.

CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.

Phone stuck in boot loop (bootloader locked)

So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!

Galrash said:
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?

Heisenberg said:
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Click to expand...
Click to collapse
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store

Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
I'm not entirely sure how it works but I believe you'll need to contact Best Buy. Even so it should be covered by warranty.

Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
In my experience, Best Buy will not honor manufacturer warranties on smartphones; So unless you bought their Geek Squad coverage, they will tell you to contact Huawei for a warranty RMA.
Contact Info for Warranty RMA:
Huawei Device USA
1-888-548-2934 (1-888-5HUAWEI)

Got ahold of Huawei and it was surprisingly easy and fast. They emailed me a shipping label I just have to drop my phone in the mail and send it to them and it will be covered under warranty. Luckily I have my old Nexus 6 to use until they get it back to me

Bootloop Problem on nexus 6p [remote: device is locked. Cannot flash images]

Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.

sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: CVH7N15C14001695
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk

sumitpetal said:
... can you guys help me to overcome this problem and install the new android os. Looking for your response.
Click to expand...
Click to collapse
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.

SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.

v12xke said:
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.
Click to expand...
Click to collapse
Hello v12xke,
Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ?
Thank You so much.

sumitpetal said:
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.
Click to expand...
Click to collapse
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.

sumitpetal said:
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.
Click to expand...
Click to collapse
I'm at work so I can't watch your video. I don't recommend opening up a device if you aren't technically sound enough to follow whatever the instructions are. So, try at your own risk and loss of warranty.
Sent from my Nexus 5X using Tapatalk

Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.

boeder9 said:
Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.
Click to expand...
Click to collapse
Hello boeder9,
Thanks for reply.
my device is not rooted and unlocked but let me try it, hope it works...!!
Thank you

sumitpetal said:
Hello v12xke, Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ? Thank You so much.
Click to expand...
Click to collapse
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!

v12xke said:
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!
Click to expand...
Click to collapse
Hi v12xke,
Thanks for the details, Let me try with hairdryer. Hope it works...!!!
Thank You so much once again.

SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!

moshu_fc said:
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!
Click to expand...
Click to collapse
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.

sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Hello, you describe a cluster A57 failure, to fix it you need to boot into your phone enough time to enable USB debugging and OEM unlock then flash a modified kernel or a modified ramdisk
See this thread : https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/
To boot into your device you need to overheat the CPU so the software will shutdown the faulty A57 clusters to cool down the device as soon as it boot up enable USB debugging and OEM unlock before the A57 clusters goes online (because it will shutdown your device) once you succeed enable USB debugging and OEM unlock flash modified files and enjoy your working (but slower) N6P
I had that problem too, but wasn't able to live thinking that my phone was working with CPU issues, so I bought an other Nexus 6P from a guy on the internet, he was selling it because the screen was broken, I got it for real cheap ! I swapped the screen of my BLOD N6P to the one from the guy, it cost me 60$ to completely fix my phone (way less than buying a new phone or buying a new microprocessor)

Exodusche said:
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.
Click to expand...
Click to collapse
Hy!
Already done that... Today It comes back from service, they told me they replaced the PCB ... so... it could be a hardware problem or a malware of some kind that ruins the memory... that's what i think about those problem, but i suspect google has something to do whit it!
So... i'll get back to you when I will have IT! :fingers-crossed:

bootloop can't unlock device
I have had exactly the same problem. I tried in vain using heat or cold to get the thing to boot, but independently found the method of leaving it on charge for a few days, occasionally it will get into the O/S.
So while in the O/S I enabled developer options and adb too (the second time) and unlocked the bootloader.
However it still claims to be "device is LOCKED" in recovery mode. This is really weird. I have also factory reset the phone but that hasn't helped.
Luckily I have read the other posts about power saving mode so I'll try that next, it will save having to flash a non-stock OS.

When people ask why unlocking the bootloader is important to me, this specific situation comes to mind. If you had unlocked your device you could have fixed this easily, mind you you would lose 4 cores.

Nexus 6P Huawei H1511 Bootlooping fix with OEM Unlock off
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6P.
Can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
*** I ran into a similar catch-22 issue on my 6P (H1511) the dreaded bootlooping with OEM Unlock turned OFF. ***
*** Couldn't flash the phone because OEM Unlock was off, and couldn't turn OEM Unlock on because it was bootlooping. ***
*** You MUST be able to fix the bootlooping/freezing at least temporarily, in order to turn on OEM Unlock in Developer Options ***
I have tried the "squeezing" method to no avail.
Then tried the heating method, which worked to a point where it has reached the color circles while booting, but then it started looping again.
I figured there's nothing to loose, so I cranked up the heat on the digital heating plate to exactly 140 Celsius for about 10 minutes covered with a paper towel, with only the upper half of the phone's back touching the heating plate (no need to "cook" the lower part with the battery).
It was still looping after the circles appeared, BUT by leaving it to cool off for about an hour, it has finally booted up into the setup page, so I quickly went to Settings > About/Phone/Software Info > clicked the "Build" line 7 times to enable Developer Options, under which I enabled OEM Unlock and ADB Debug.
If it's still bootlooping, you may try to "freezing" method where you would put the phone into the deep freezer for about an hour.
However, heating has worked for me.
Following that, in FastBoot mode I entered the following 3 versions of the flash unlock commands (only one will work out of the 3 which is fine):
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
Downloaded the latest full stock firmware directly from Google.
https://dl.google.com/dl/android/aosp/angler-opm6.171019.030.b1-factory-ab13a98b.zip
Unzip it, and run flash-all.bat
Once the flashing has finished, DO NOT let it boot up, instead hold down the Volume Down as it's about to reboot, which will kick it into bootloader/fastboot mode.
I have tried flashing the Osmosis zip to patch the boot but it didn't work, it was still bootlooping.
So I have flashed a pre-patched 4-Core Boot kernel to fix the bootlooping issue permanently.
For Android 8.1 OPM6.171019.030 flash this 4-Core Boot with the commands below:
https://androidfilehost.com/?fid=13356325061477269711
fastboot flash boot Huawei_H1511_6P_OPM6.171019.030_Boot_4Core.IMG
fastboot reboot-bootloader
At this point flash a 4-Cores patched TWRP, go into TWRP recovery (hold down Volume Down + Power for 10 seconds, Volume Down to "Recovery", Power) and first "format" Data, then "wipe" Cache, Dalvik-Cache, and Data.
Note, all information on your phone will be lost by the above format/wipe operation.
All done, hope this method may help some of you.
And here are some interesting FastBoot commands I've come across....
C:\ADB>fastboot flashing get_unlock_ability
(bootloader) 1
OKAY [ 0.018s]
Finished. Total time: 0.019s
C:\ADB>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.87
(bootloader) version-bootloader:angler-03.79
(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: 0xdaa17ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:8XV5T15C11000453
(bootloader) kernel:lk
(bootloader) product:angler
all:
Finished. Total time: 0.172s
Instead of "fastboot getvar all", you can also use "fastboot getvar <variable>" (without the quotes and <>)
Any <variable> from the log above, between "(bootloader)" and the second ":"
For example:
fastboot getvar serialno
Enjoy!

My nexus 6P recently went through this bootloop,
Google screen coming up and stuck there, for 5 days, i was going through many possible solutions throughout the web, but they all said it must boot to OS to be able to unlock oem bootloader,
Finally stuck at extreme heat or cold, extreme heat did'nt work for me, but YES extreme cold did actually work, i kept it in the deep freezer for about half an hour, and then waited 2 min, and plugged the charging cable and powered ON the phone, to my astonishment, it did start and i was able to use the phone.
I have rebooted several times since then, it works fine for certain time, and then crashes and restarts all the time, i can still use th phone but its uncertain when it will restart again.
I tried to install new custom rom, but it still says DEVICE IS LOCKED and i cannot do anything else.

Bootloop Fixing

I ran into a bit of an issue and am stuck with a bootlooping G6 US997.
What got me into this pickle:
I unlocked the bootloader
I flashed TWRP successfully, by:
Running fastboot flash recovery TWRP.img
Unplugging USB and holding Vol- and Power from fastboot, then lifting and re-pressing Power when the LG logo appeared
Hitting Yes, Yes
Being in TWRP and allowing modification of System
Formatting Data (Wipe > Format Data > Yes)
I installed the DM verity and encryption file so that it would boot
I wiped Cache/Dalvik
I rebooted into System
It booted successfully so I went back to TWRP and installed Lineage OS, Open Google Apps, and the Lineage SU addon
This booted successfully, so I went and with OEM unlock disabled booted into fastboot to see if I could get rid of the annoying orange screen at the start saying that the bootloader was unlocked
To do this, I ran fastboot oem lock, not seeing/ignoring the red text at top telling me to Please check "Enable OEM unlock" in Developer options.
I then rebooted with fastboot reboot and I encountered a red warning: "Your device has failed a routine safety check and will not boot." It is now in a bootloop at that screen, cycling between black, the LG logo, and the warning.
I managed to enter recovery mode (with the key-combo) and got the stock recovery "factory reset and wipe" option, which I had been previously getting when entering TWRP, so I selected "Yes, Yes" and then it went back into the bootloop, completely avoiding TWRP.
Where I currently am:
I can get into fastboot mode (Vol- with usb plugged in) and I can get into the factory reset mode which is the gateway into TWRP. I cannot get into TWRP, and I cannot flash anything, boot into any images, or unlock the bootloader ( Please check "Enable OEM unlock" in Developer options). If I could do that I think I can get it fixed.
My questions:
How can I do the OEM unlock without access to Developer Options? (I have the unlock file to flash, just need access)
Or How can I bypass the red warning page and boot into Lineage OS?
Any help would be appreciated, I really would like to get this working.

Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?

Killua96 said:
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Click to expand...
Click to collapse
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? If there were a way to keep it in download mode longer, that would really help. Thank you for replying, I've seen your name around the forums!

mwsundberg said:
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. It looks like it might still be in download mode, but interrupted by the warning, the way the screens flash. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? Thank you for replying, I've seen your name around the forums!
Click to expand...
Click to collapse
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?

Killua96 said:
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Click to expand...
Click to collapse
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s​
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.

mwsundberg said:
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
Click to expand...
Click to collapse
You can't, fastboot is a mode that allows many things but it's not a God-like mode where you can do everything.
By locking the bootloader while having unsigned partions flashed you have essentially hard bricked the device, and if the only way to flash stock signed partitions (lgup+Uppercut) doesn't work it means that you have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.

Killua96 said:
You have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Click to expand...
Click to collapse
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.

Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?

mwsundberg said:
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
Click to expand...
Click to collapse
It depends on how much it'll cost to you a new G6, they could ask you maybe 200-250 bucks.
mwsundberg said:
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Click to expand...
Click to collapse
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously

Killua96 said:
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Click to expand...
Click to collapse
Managed to get a messed up G6 from a friend working again. Thanks. XDA forever

Guys, need help !!!
I have tried to install SEA oreo version on Indian phone via LGUP... Flash was successful (100%) but it got stuck on LG Logo..
Procedure followed for H870DS (IND)
1. Downloaded SEA Oreo KDZ File (H870DS20a_00_OPEN_SG_DS_OP_0518.kdz)
2. Installed LGUP... Made new Common folder inside C/Prog file/LG/Model
3. Extracted DLL file from KDZ & renamed it LGUP_Common.dll and kept in Common folder
4. Entered in download mode
5. Opened LGUP.. selected KDZ and Upgrade..
6. Boom.. 100% completed.. it has shown that phone is rebooting..
7. But then it got stuck on LG Screen
I cant access recovery now
I can open Hard Reset option (Vol down+Power) only.. Made hard reset but no use
I cant enter in download mode
I dont know if it is charging or not
It is not even switching off by pressing power button for long time
Pl help me...
---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------
it has anything to do with "Enable OEM unlock" in Developer options"

There is a way to enter download mode. Just hold down button and power button. Just when you see LG logo leave power button for a second. Push power button again and hold with down button. Now press yes twiche for the hard reset prompt. Now IMPORTANT, when screen goes black immediately press and hold up button. While holding up button plug usb cable into the PC. Now use Uppercut 1.0.0.0 and flash your kdz.

Same issue, Just that I was trying downgrade to Nougat. Oreo messed up my phone to the extent that, none of the sensors (including Fingerprint are not working). The load was a success, but after 1st restart it went into boot loop.
I only had USB Debug enabled in the DO before this issue, so it might work with the OEM unlock dissabled.
Software needed...
LG Bridge
Meathod...
Please charge the phone before this is done, at least 80%, will be better.
Connect the computer with LG G6 H870DS (Indian), might work for all models. "not tested"
If the USB debug is enabled, you will hear the USB disconnection and connection notification sound during bootloop
When you hear disconnection sound, press the "volume up key" until the Firmware Update mode appears
Once you are in Firmware Update mode, the USB connection will be stable (In bootloop, it keeps disconnecting)
Disconnect the USB cable
Start LG Bridge/Software Updates, connect when App asks to connect the phone
This will update you phone to the latest official software update..
This solution can work for all phones that have a hardware based menu to get into Firmware Update mode, definitely works on all LG phones to get out of bootloop. I have tested on LG G2, G4 and G6 Indian devices.
And a suggestion to all mates is, to enable USB debugging and the OEM unlock as soon as you get hands on your new devices. Always saves the hassle of running around the LG service center, its a big issue in India at-least. I love LG for its hardware quality but sadly LG smartphones have a bad history of software issues

Bricked New Moto g4 Play (Please Help)

I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected

Uio443 said:
I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected
Click to expand...
Click to collapse
Hi, I have exactly the same problem. Have you resolved it ? Ty

Uio443 said:
I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected
Click to expand...
Click to collapse
Did u try to request a bootloader unlock key at Moto's Website and try unlocking?
I know its sounds a bit stupid but sometimes it works. One of my friend said he did it so just give it a try!

TheWarrior01 said:
Did u try to request a bootloader unlock key at Moto's Website and try unlocking?
I know its sounds a bit stupid but sometimes it works. One of my friend said he did it so just give it a try!
Click to expand...
Click to collapse
Thanks for the response but here is what happens. When I try to get the key I need to run this command:
Code:
fastboot oem get_unlock_dat
I should get a bunch of numbers and letters and numbers in response which I then send to motorola which motorola analyzes and gives me the unlock key. But when I run this command I get this error:
Code:
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.120s
I am glad that you are trying to help but sadly it is not that simple.

TsiaoTai said:
Hi, I have exactly the same problem. Have you resolved it ? Ty
Click to expand...
Click to collapse
I have a suspision I need to somehow remove the bootloader and reinstall an unlocked one. That is my latest guess. But so far I haven't been able to fix it.

Uio443 said:
I have a suspision I need to somehow remove the bootloader and reinstall an unlocked one. That is my latest guess. But so far I haven't been able to fix it.
Click to expand...
Click to collapse
Good luck with that. If remediation were that simple device security would be a joke.
Given the oem unlock data responses you posted I'd say your device is toast. Hope I am wrong.

Davey126 said:
Good luck with that. If remediation were that simple device security would be a joke.
Given the oem unlock data responses you posted I'd say your device is toast. Hope I am wrong.
Click to expand...
Click to collapse
I hope so too.

Try Using a Different Cord. Also just for confirmation, You have Moto drivers Installed? Try using different PC + ADB.
Also see this thread and post your Info: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809 .
If that doesnt work, take it to service center and tell after update it happened. (Dont Mention you trying to blank flash) Also, Before hand, Tweet to Official moto and moto(country) specific page. Tell them your device aint working after update. They wil tell you mail them(most of the times) and then mail them. Wait for 1 Day for reply and then go to service Center.

Uio443 said:
I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected
Click to expand...
Click to collapse
Hi, I don't know if you solve your problem but I have the same and I thought about using an edl cable : https://www.amazon.com/cable-Qualcomm-phones-Flash-called/dp/B01NAMYW84 to go in edl mode and then flash the ROM with QFIL. Could be worth ?
Another question; is your phone is recognized by RSD Lite ? If yes, have you tried to flash stock ROM via RSD ?

TsiaoTai said:
Hi, I don't know if you solve your problem but I have the same and I thought about using an edl cable : https://www.amazon.com/cable-Qualcomm-phones-Flash-called/dp/B01NAMYW84 to go in edl mode and then flash the ROM with QFIL. Could be worth ?
Another question; is your phone is recognized by RSD Lite ? If yes, have you tried to flash stock ROM via RSD ?
Click to expand...
Click to collapse
The cable may be worth trying. I will so thanks for telling me. I have tried a few versions of RSD Lite but my phone is not recognized.
Is yours recognized by RSD Lite?

Uio443 said:
The cable may be worth trying. I will so thanks for telling me. I have tried a few versions of RSD Lite but my phone is not recognized.
Is yours recognized by RSD Lite?
Click to expand...
Click to collapse
Nope, mine not recognized either and I tried different versions of RSD on different supports ( Windows xp, 7, 10 and Linux )
I'll buy the cable tommorow, I'll tell you
Otherwise i try to find my Bootloader unlock code to re-unlock it but no trace of this code on my PC...
By the way, in order to Blank flash your bootloader, which file did you used ? I think the BlankFlash files we used were not adapted to our phone model

TsiaoTai said:
Nope, mine not recognized either and I tried different versions of RSD on different supports ( Windows xp, 7, 10 and Linux )
I'll buy the cable tommorow, I'll tell you
Otherwise i try to find my Bootloader unlock code to re-unlock it but no trace of this code on my PC...
By the way, in order to Blank flash your bootloader, which file did you used ? I think the BlankFlash files we used were not adapted to our phone model
Click to expand...
Click to collapse
Hello,
Did you get the cable, and if so then did anything work for you?
I have ordered the cable but it will take a very long time to ship (estimated oct9-dec4).
In other words, did anything work for you?

Uio443 said:
Hello,
Did you get the cable, and if so then did anything work for you?
I have ordered the cable but it will take a very long time to ship (estimated oct9-dec4).
In other words, did anything work for you?
Click to expand...
Click to collapse
Sorry, totally forgt the topic The cable didn't work for me, I hope you will get better results.
I'm done spending hours searching answers on google, I gave up
Good luck !

TsiaoTai said:
Sorry, totally forgt the topic The cable didn't work for me, I hope you will get better results.
I'm done spending hours searching answers on google, I gave up
Good luck !
Click to expand...
Click to collapse
Damn, that really sucks. I will let you know if I am able to fix it as soon as I get the cable.

Uio443 said:
I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected
Click to expand...
Click to collapse
Flash from fastboot gpt.bin and the rest oficina firmware stock for your phone, try whith Is info
https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797

Uio443 said:
I got this moto g4 play a few months ago. I decided to finally install this security update because I decided that nothing will go wrong. I clicked install and went to eat. When I came back the screen was block and no buttons worked. I figured out that I needed to blank flash this bootloader. After 2 hours of trying it worked. I got into the bootloader. The thing is that the bootloader came locked and I cannot access my recovery or android. To unlock the bootloader I need to check the "allow oem unlock" in developper settings on android. BUT I DO NOT HAVE ANDROID. Now I'm stuck. Can anyone please help! Thanks.
(By the way it is XT1601)
Log:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
CID Read Failure
Invalid CID status 0x69
USB connected
Click to expand...
Click to collapse
Take it to your service center