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
Related
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.
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 am trying to unlock my bootloader. I finally received my unlock token from OnePlus but for some reason i cant unlock the device. i have the unlock-bin file in the same folder as adb, i have usb debugging on, my device is in fastboot mode, but i keep getting this error (see attached picture). Can someone please help? Also, does unlocking the bootloader factory reset the device?
bigmikey307 said:
I am trying to unlock my bootloader. I finally received my unlock token from OnePlus but for some reason i cant unlock the device. i have the unlock-bin file in the same folder as adb, i have usb debugging on, my device is in fastboot mode, but i keep getting this error (see attached picture). Can someone please help? Also, does unlocking the bootloader factory reset the device?
Click to expand...
Click to collapse
Replace <unlock_token.bin> with the ACTUAL unlock token you got.
Yes, unlocking bootloader wipes the phone.
There are multiple forums on this.
While the phone is plugged in to the PC reboot it to fastboot again leaving it plugged in. ( Make sure you selected OEM unlock in developer options)
I managed to get it to work by using the ALL IN ONE tool
Just give the command, and drag and drop the unlockbbin. Should look like this: fastboot flash cust-unlock 23857363fbsndhdnd.bin. {for future reference, i have to reuse a couple times a week
Not unlock.bin
bigmikey307 said:
I managed to get it to work by using the ALL IN ONE tool
Click to expand...
Click to collapse
how bro can u explain ?
Same problem here
I think I've been out of the game for too long........ I was just too embarrassed to post the same question , ha! Well, at least the first part of the OP's question, about having the token in the correct path and it producing an error. If there's a step by step command by command walk-thru out there, I'd be grateful for the link. And yes I know how a search bar works, but all of the guides or whatever you want to call them seem to be missing a few steps....... Or maybe I should just go back to eating my butterscotch and yelling at kids to stay off my lawn ?
Hi, I need help with my evice, I used a script founded in a thread here to flash stock rom 8.0 oreo, but that locked the bootloader now I cant unlock it because when phone starts im stuck on oreo wizard with no wifi or data to acces oem unlock in developer settings, is there any way to skyp this wizar or to flash with locked bootloader, wherever i tried to flash another frimware i have the error mesage, Bootloader "Permission Denied".
Thanks in advance!
sorry bad spelling, is not my native lenguage.
You can skip the wizard with just giving it ok everywhere and it will eventually end
For the unlocking here's a tool to share internet from pc to your phone
https://github.com/Genymobile/gnirehtet
juampapo546 said:
You can skip the wizard with just giving it ok everywhere and it will eventually end
For the unlocking here's a tool to share internet from pc to your phone
Click to expand...
Click to collapse
Can't pass the wizard cuase it ask for internet and I can't use that tool cause it need debug to work wich I can't activate without passing the wizar, is there another way?
Thanks!
coredeing said:
Can't pass the wizard cuase it ask for internet and I can't use that tool cause it need debug to work wich I can't activate without passing the wizar, is there another way?
Thanks!
Click to expand...
Click to collapse
Did you try to unlock the bootloader via fastboot?
WoKoschekk said:
Did you try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Yes but it says that I need to turn oem unlock on the developer options since I cannot pass the wizard I cant tur the option on. =c
Coredesing said:
Hi, I need help with my evice, I used a script founded in a thread here to flash stock rom 8.0 oreo, but that locked the bootloader now I cant unlock it because when phone starts im stuck on oreo wizard with no wifi or data to acces oem unlock in developer settings, is there any way to skyp this wizar or to flash with locked bootloader, wherever i tried to flash another frimware i have the error mesage, Bootloader "Permission Denied".
Thanks in advance!
sorry bad spelling, is not my native lenguage.
Click to expand...
Click to collapse
Even if you get past the wizard, you still wouldn't be able to re-unlock the bootloader. It would stay gray forever. The only solution now is to get your phone hard bricked so you can enter edl mode and re-unlock it. You need either a deep flash cable, or short the 2 connection JTAG points from the motherboard. I'm on the same boat, but never got to do this to confirm if it works.
mrsiri said:
Even if you get past the wizard, you still wouldn't be able to re-unlock the bootloader. It would stay gray forever. The only solution now is to get your phone hard bricked so you can enter edl mode and re-unlock it. You need either a deep flash cable, or short the 2 connection JTAG points from the motherboard. I'm on the same boat, but never got to do this to confirm if it works.
Click to expand...
Click to collapse
NO, you can pass the wizard with no internet connection, I did it several times on my evert, just keep saying yes to everything (unless you frp locked which would be weird since is not by default enabled) Once you pass the wizard use the tool I provided previously to unlock bl
Hi,
I have oneplus 6T which has suddenly started giving qualcomm crash dump error after normal reboot. I have tried msm tool to flash. Tool shows success but when it boots the mobile at end , same crash dump appears again. have also tried multiple version of msm. Also visited service center but they are suggesting motherboard replacement.
Now i want to try manual flashing. Phone is in bootlocked state. also OEM is not unblocked. Is it possible tounlock OEM when my phone is not booting. also is it possible to change boothlocked state to unlock?
I can go to fastboot by pressing vol UP + DOWN and power button but on selecting recovery option it still goes to same crash dump state.
Please suggest what options do i have?is there any way to recover?
Thanks
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added: ?
Thanks for responding
yes device is global model of 6T.
I have not unlocked /locked bootloader in past.
"fastboot oem unlock" gives error as "FAILED (remote: Flashing unlock is not allowed)"
flash713 said:
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added:
Click to expand...
Click to collapse
Did you tried different older versions of MSM Tool?
Dafelleant said:
Did you tried different older versions of MSM Tool?
Click to expand...
Click to collapse
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
ms2020 said:
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
Click to expand...
Click to collapse
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
flash713 said:
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
Click to expand...
Click to collapse
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
ms2020 said:
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Click to expand...
Click to collapse
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
flash713 said:
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
Click to expand...
Click to collapse
ms2020 said:
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
Click to expand...
Click to collapse
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
tried the format with -w,
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
flash713 said:
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Click to expand...
Click to collapse
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
lilbrat said:
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
Click to expand...
Click to collapse
ms2020 said:
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
Click to expand...
Click to collapse
Well that's not good.. as flashing with msm wouldn't matter whether the bootloader is lock or not ... As it automatically relocks it anyways... Has me stumped..
Are you sure you didn't flash anything that wasn't specifically made for your model device? I mean after you started to fix the crashdump issue?
Want to hear something crazy.. Two days ago when we were first commenting about this crashdump deal, about an hour after we stopped chatting I took a shower, got out and went to grab my OnePlus 6t off the Dash ac charger and yep, you guessed it!!! Crashdump mode!!!! ?????
I swear man! And I wasn't messing with my device when it occurred either. I was not able to get out of it by manually holding power+ volume -&+ until I saw fastboot mode and then selecting start using power button like the three other times I've experienced this. So I went ahead and booted twrp, and did a clean install of OOS and formatted data and that worked. Is this **** contagious?! ? Tripped me out! Haha!!
I'd give the data format command: fastboot -w then run msm tool like the other user said to do. See if that works.
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
ms2020 said:
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
Click to expand...
Click to collapse
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.) ?
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
bro fixed aleady? i got fix for you.
i have tried the commnads you have stated earlier.. still giving output here.
fastboot oem device-info
output below
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.027s]
finished. total time: 0.028s
so it's locked
fastboot gatvar all gives the list of options that you can use with fastboot
most of the commands dont work and gives below error
FAILED (remote: Erase is not allowed in Lock State)
yes developer options and usb debugging was probably not flipped either
flash713 said:
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.)
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
Click to expand...
Click to collapse
not yet..
gazitonmoy said:
bro fixed aleady? i got fix for you.
Click to expand...
Click to collapse