Related
<<<<Problem resolved.>>>>
I have read around 25 forums about this, and still can't fix what they say can be fixed. During RSD my atrix failed and gave a screen with:
SVF message: 105:1:2 failed to boot
No OS detected, going to rsd mode in 5seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools"
I am a noob, and followed a sticky-ed xda guide, tried a lot, and don't know what do. Please break down any help given into something i understand, steps are great. I don't know how to program, or write script(which some forum posts suggested). Each time i select as the command fastboot, it says "starting fastboot protocol support" then does nothing. Forums posted a file to fix this, but megauploader is no longer with us.
Try to get into fastboot mode, and do the fastboot oem unlock command.
I'm on my phone so it's hard to find stuff, but i know there's a few copies of moto fastboot laying around the dev section, just search for them.
Sent from my MB860 using xda premium
Alcapone263 said:
Try to get into fastboot mode, and do the fastboot oem unlock command.
I'm on my phone so it's hard to find stuff, but i know there's a few copies of moto fastboot laying around the dev section, just search for them.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I went with first option on accident and then it started to run RSD again, but it goes all the way to "starting fastboot protocol" and nothing happens, i have a fastboot.exe, but when i try to run it a black box with text pops up for a millisecond.
"Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP pass through mode (0x70BE0); phone connected." is the RSD error.
Squalcloud said:
I went with first option on accident and then it started to run RSD again, but it goes all the way to "starting fastboot protocol" and nothing happens, i have a fastboot.exe, but when i try to run it a black box with text pops up for a millisecond.
Click to expand...
Click to collapse
do you know how to you use fastboot? you need to execute it in the command line.
honestly you say you read 25 forums but i think you need to re-read the entire pudding unlock thread word-by-word, familiarize yourself with the command line and also use search. this error has happened and has been posted on many many many times before on this forum.
you need to unlock your bootloader (if it isn't already), and flash a fruitcake ROM. as of right now you have no OS, so you need to flash a fruitcake in order to put an OS back on your phone.
Tgishappened to me2 days ago when a repacemenf atrix came in. The flash is succesful(rsd. Part).... turn ur phone on, waitress till u get the 0x1002 error...then let the boot up start, and when is says fastboot protocol then ur good to go. Go to your cmd fast boot dir. Then do the fastboot OEM unlock. Now this is the part that scared me. When I did the fastboot OEM unlock #### I kept getting error. THIS PART IS CASE SENSITIVE. I was putting in fe and when I put in FE as it showed it worked. Once u unlock just flash romracer recovery and flash a rom and u are good to go. Msg me with any questions. This just happened to me literally 2 days ago.
Sent from my MB860 using xda premium
ahjdmarchi said:
Tgishappened to me2 days ago when a repacemenf atrix came in. The flash is succesful(rsd. Part).... turn ur phone on, waitress till u get the 0x1002 error...then let the boot up start, and when is says fastboot protocol then ur good to go. Go to your cmd fast boot dir. Then do the fastboot OEM unlock. Now this is the part that scared me. When I did the fastboot OEM unlock #### I kept getting error. THIS PART IS CASE SENSITIVE. I was putting in fe and when I put in FE as it showed it worked. Once u unlock just flash romracer recovery and flash a rom and u are good to go. Msg me with any questions. This just happened to me literally 2 days ago.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Just did this, and typo's in cmd killed me so much on the inside.
Did u get it. Sorry I'm on my phone laying in bed. Why I'm not more in depth... too much to write on this screen lol
Sent from my MB860 using xda premium
Got it, unlocked now. But my titanium back up didn't work for some reason, no biggie. most i lost was progress in some games.
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?
C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird
zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon
well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..
my phone is everything first off and i cannot do any thing erecovery cant do anything because im on unoffical 90nrdm os when i try do anything i adb it cannot find my device and just says waiting for device when trying to lock bootloader in fastboot mode so i tried unlocking it (i got the code) but it says s"FAILED stat does not match" and i cannot flash anything to fix my phone and i cannot find the huawei page to unlock my bootloader because it keeps saying " this id is registered on the other site" but never tells me where to go or find the "other site" bootloader unlock page i really need my phone to work resetting it is fine i got back ups but i really need the phone to work all help is welcome, i have adb and fastboot installed i tried useing srk tools 2.0 lod-chong and also cmd to try fix my issue but i get no where. i have no recovery either it just wont boot into twrp it just goes straight to erecovery so i cannot do any dload method. also when i tried other methods it said password wrong for some reason.
i flashed oeminfo.bin and custom.bin to go back to offical nougat from somewhere after this update nougat didnt work (hisuite refused to install it) : http://ministryofsolutions.com/2017/03/huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe.html so i then looked into downgrading and got to this https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873 and i did the oem info flash and it like the person said on my previews post ( https://forum.xda-developers.com/huawei-p9lite/help/bricked-device-dont-how-to-fix-l31-t3617851) and it just like he said but i did it before he commented and now my phone wont boot and when i enter my bootloader code it says FAILED stat does not match and because i cannot re lock and unlock my boot loader i cannot flash anything to get my phone back, how can i fix this.
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.
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