Database Users

[Q] Boot loader stuck on unlocking now

I cannot unlock my bootloader. I have a Nexus 16 wifi with 4.2.1 and no other hacks or mods applied. Bone stock.
When attempting this through the Nexus root toolkit or Nexus 7 tool kit or through a fastboot command line device says unlocking now but does not reboot afterwards. When manually rebooting device is not unlocked. I will also add that my device is encrypted through the software provided on the device. Also I cannot factory reset the device through the UI or through the bootloader. Again it says it's doing these tasks but upon boot up I am still asked for my storage unlock password and the device is still back the way it was pre wipe attempts.
Other strange behaviors indicating a wipe attempt are random reboots, Andriod OS process consuming > 40% of my battery. Also device installs the same app updates every time I reboot or if the device reboots on it's own.

I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7

No dice
duffieldj1 said:
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
Click to expand...
Click to collapse
Unfortunately the only way to un-encrypt device is to reset it to factory spec again which it will not do no matter the method tried. The drivers are correctly installed via the toolkit. The tool kit shows that device serial number. I have installed the SDK and have tryed that method via fastboot 'fastboot oem unlock'. I then follow the directions on device and press the power button. Device is stuck at 'Unlocking now.....' However nothing happens. It does not automatically rebooot or wipe device. When I push the power button the device boots normally as if nothing had happened. Also bootloader is still locked. If I can get it unlocked I think I should be able to wipe it.
Output from command:
C:\Users\Scot\Downloads\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platfo
rm-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 31.029s

Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.

bftb0 said:
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
Click to expand...
Click to collapse
Wondering too if this is an unintended consequence of encrypting the device. So now that it is encrypted if the device is lost or stolen it's no good to anyone as there is no way to reset it back to a functional device. There has got to be a way to around this. I travel quit a bit for work and that is the only reason I chose to encrypt was in the event it was lost or stolen.
I have an RMA number open with Asus in the event that this cannot be figured out. Really though it is not a hardware issue, it's definitely software related.

[Q] Nexus 7 doesn't boot

Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!

Nexus Tool Kit

rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?

swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.

swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.

ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.

swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?

ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.

Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.

Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.

device not unlocked cannot install image oneplus 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Problem Solved

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

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

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

Bricked New Moto g4 Play (Please Help)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oneplus 6T qualcomm crash dump error, recovery not working

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