Need help unbricking OnePlus 2 - OnePlus 2 Q&A, Help & Troubleshooting

Need help unbricking OnePlus 2 - OnePlus 2 Q&A, Help & Troubleshooting

Accidentally bricked my phone while trying to unlock the bootloader on my phone. I was doing this in an attempt to root my phone again after removing the root in an attempt to update Oxygen OS. After TWRP was unable to flash the update I gave up and tried to root the phone again using kingo root but kept failing. I checked whether or not the bootloader was locked and sure enough it was but after attempting to unlock it again, the phone was bricked and could only go into fastboot mode. Flashing the stock OS didnt work since the bootloader was locked. I tried using a unbricking method posted to oneplus forums that invloves downloading qualcomm diagnostic drivers and using a unreadable download tool but couldn't find the driver the method mentioned Qualcomm 9008. After some more searching other methods were similar but used the driver Qualcomm HS-USB Diagnostic 9006. Once that driver was installed i launched the MSMdownload tool which was taking hours with no progress bar whatsoever so i decided to go to sleep. I woke up to an unreadable notification from the download tool and my phone's battery was dead. The phone wouldn't go into fastboot mode but was still being detected in device manager. All the phone responds to is the power button and volume down button being pressed which just causes the phone to display a low battery notification and then stops charging a minute later. I then tried using an unbricking method that involves installing the qdloader 9008 driver and running a program called QFIL but this method failed to unbrick the phone. Is there any way to factory reset my oneplus 2 and put the stock OS back on to it? please keep in mind that the bootloader is locked. i cant post links to the methods i used as the site wont let me

Related

[Solved] A2017G totally Bricked

First of all, i live in Bangladesh. I asked a relative of mine who lives in Sweden to buy me this phone. So, there is no way for me to send this phone back to ZTE.
Now let me explain how i got into this huge mess. I installed twrp successfully using this post - https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
i only followed part A of this post. Then i needed to root. so i tried to flash supersu 2.79 first but failed. Then i tried to flash supersu 2.65 as someone commented that they failed with 2.79 but succeeded with 2.65. However, after flashing supersu 2.65 i soft bricked my phone. i could still access twrp 3.0.2. After a while, i downloaded b08 update.zip and tried to flash it through twrp but failed. then i saw this post - https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
and this post - https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And tried to update twrp to 3.03. which then hard bricked my phone. now i cannot access anything. when i try to start my phone it shows the zte logo for a second and the whole screen goes blank with the red led.
same thing happens with volume up+power and volume down+power. And there is no way to turn the phone off. So, i waited a whole day for the phone to empty it's battery and tried to boot to edl mode using volume up+down but Qualcomm HS-USB QDLoader does not appear. The only thing i can get to connecting to my computer is handset diagnostic interface.
Now only a brilliant dev can help me. So can someone PLEASE Help me.
Also i've found this post is very similar to my problem https://forum.xda-developers.com/axon-7/help/bricked-a2017g-b03-help-please-t3487635
Update: Fixed using this post >> https://forum.xda-developers.com/ax...ory-brick-repair-manual-t3585898#post71764940
& this >> http://4pda.ru/forum/index.php?showtopic=814221&st=0#entry60102671

Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...

Abiram26 said:
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Click to expand...
Click to collapse
yes i have. but in the device manager, instead of Qualcomm HS-USB QDLoader, Handset Diagnostic Interface appears.
Furthermore, computers does not recognize any adb device when i connect my axon 7
what do i do???
Edit: when i uninstall Handset Diagnostic Interface from device manager and then connect my phone with both volume keys pressed, at first qusb_bulk appears but after automatic installation of hardware software it's Handset Diagnostic Interface all over again

Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7

Abiram26 said:
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Click to expand...
Click to collapse
:crying::crying::crying::crying:
if only i could boot into edl mode

I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?

Send me a PM with your Hangouts, let's see if I can help.

Controllerboy said:
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Click to expand...
Click to collapse
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help

nsabir said:
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
Click to expand...
Click to collapse
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.

Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??

nsabir said:
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Click to expand...
Click to collapse
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.

Oki said:
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Click to expand...
Click to collapse
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only old ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.

nsabir said:
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
Click to expand...
Click to collapse
Can you boot into the bootloader by pressing the button combination?

Oki said:
Can you boot into the bootloader by pressing the button combination?
Click to expand...
Click to collapse
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G

nsabir said:
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
Click to expand...
Click to collapse
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/

Altomugriento said:
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Click to expand...
Click to collapse
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.

nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
Do you find something useful? I think I find someone in that forum, exactly in your position, all the answers pointing to RMA for the fix, sorry, maybe later can take another look and search for a solution.
Enviado desde mi ZTE A2017U mediante Tapatalk

nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk

Altomugriento said:
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
Thank you for the link. But i tried this miflash tools weeks ago.
Here is the full guide in my opinion for the mi flash tool.
http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Unfortunately, the A2017G does not have 9008 port. It has ZTE's own Handset Diagnostic Interface (DFU) (ComX) for which i need the latest version of ZTE firmware flasher. At the moment only ZTE have this. So, my bricked phone is a lost cause.

Chinese Axon 7 is not seen in ADB or MiFlash..Bricked??

After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514

cozzysa said:
After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck

Choose an username... said:
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck
Click to expand...
Click to collapse
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.

cozzysa said:
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.
Click to expand...
Click to collapse
well that's the other way lol
I had to follow the guide, and it fixed my phone, so be assured that you can fix it if they send it back

It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.

cozzysa said:
It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.
Click to expand...
Click to collapse
Usually you can't enter Factory Test Mode when on a DFU brick. The known procedure to do that is to discharge the phone, then put it into FTM somehow and then using ADB to get to EDL. It's really weird that you've been able to pull that off that way
Could you tell us how you got into FTM? Just by vol down and power? It would be a nice addition to the brick guide, before attempting to take the phone apart

Yeah, it was just by power + volume down.

assistance needed

i attempted to root my zte maven 3 with zpst for at&t and when the device went to restart the screen stayed black and no matter what key combinations i try i cannot get the screen to turn on. The only thing the phone does is connect to the pc and makes that connection noise. it connects as Qualcomm HS-USB QDLoader 9008. does anyone have any advice or suggestions that might help

Did you make any partition backups in QFIL by any chance? If not, I have no idea how one would go about fixing it. What's your bootloader version? I can try to give you my partition backups and you can try flashing it and seeing if it'll boot.
Tbh I should write my own rooting guide, because the existing methods are, quite frankly, ****ty and dangerous. To anyone reading this, please open QFIL and make a backup of all of your device partitions before messing with anything; this is basically creating a bit-for-bit backup of the storage itself, such as the persist partition, userdata, system, etc. I had to buy a for-parts Maven 3 from eBay because I bricked my Maven 3 using the same guide...
And don't use ZPST from now on. You don't need it. Everything can literally be flashed as a partition in QFIL easily. This is how I safely flashed a Magisk boot image (partition) and half-working TWRP recovery partition.

maxwelldad90 said:
i attempted to root my zte maven 3 with zpst for at&t and when the device went to restart the screen stayed black and no matter what key combinations i try i cannot get the screen to turn on. The only thing the phone does is connect to the pc and makes that connection noise. it connects as Qualcomm HS-USB QDLoader 9008. does anyone have any advice or suggestions that might help
Click to expand...
Click to collapse
Your device is in EDL mode. It's the only mode that connects as Qualcomm HS-USB QDLoader 9008, and EDL mode doesn't display anything on your device screen. Just take the battery out for a second and you should be able to boot normally.
I'm going to post a new thread in this forum as soon as I send this, where I'll run down the steps I took to achieve root on my Maven 3 just this morning. I've powered off and booted up about 5 times since rooting and it's still rooted.

I have edl mode no boot no screen no lights, what do do next. I tried removing battery no luck

xecutionkrk said:
I have edl mode no boot no screen no lights, what do do next. I tried removing battery no luck
Click to expand...
Click to collapse
I am unsure of what you can do because iirc i faced the same issue. I have full partition dumps for my current maven 3, some of which (except for example persist) I can send and you can try flashing it using QFIL since your device sounds like it's in EDL mode

[solved]Bricked my OP6t on A11 while tinkering, stuck in boot loop (?hard bricked), windows 7 doesn’t detect Device as Qualcomm device

I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.

Also get magisk to root rather than SuperSU. You can install twrp from magisk in oos with the correct installer but first you have to root correctly with modded boot.img. Can make your own or get from the one post in here. I'd suggest getting the newest oos also.

Brettroth said:
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Click to expand...
Click to collapse
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.

Brettroth said:
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Click to expand...
Click to collapse
Couldn’t fastboot into twrp, since device got corrupted while trying to flash multiple things. Thankfully while tinkering, my desktop recognised my device as qhusb qloader 9008, and all I had to do was boot my device into edl mode (which was also a pain tbh!). After trying numerous key combinations and timing it perfectly, device booted into edl and I could use the msm download tool to unbrick my device. Now device has rebooted into iOS 10.3.5 (same version as msm tool version) and I have somehow breathed a huge sigh of relief that my device could be resuscitated. Will be updating to 11.1.1.1 now (I see the latest is 11.1.2.2) and setting up my device now.
Thank you a lot for looking into my issue and suggesting solutions. In my younger years, I was a technology enthusiast and often rooted/flashed, but have pursued medicine since then. Now am out of touch completely to the tech scene and it was a grave blunder on my part to have used my primary driver to try and root/flash again.
Have a great day, my friend and please know that it means a lot to me to have received help from the community.

Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
This happen to me several times and the first time it happened I thought my phone would not be unbricked after numerous attempts with the msm tool!
My issue was that my phone was a renewed amazon phone and amazon listed it as a unlocked international but it actually was a t-mobile variant and when i downloaded the correct msm tool with firmware it worked!
You need to get the phone into edl mode. For edl, when phone off press both volume buttons and plug in the usb while connected to your pc and the qualcom driver should pop up in device manager. After that finding the right msm firmware will be your next issue but with enough searching you should find it!
Let me know your progress with the driver and I can try and post some links to different msm firmware for the oneplus 6t!

[Help] oneplus 8 pro, OEM Locked, Bootloop

Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread

Ezzell said:
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Click to expand...
Click to collapse
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.

HolyHog said:
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
Click to expand...
Click to collapse
This just boots to bootloader, from power off, any other combination instantly boots to same error page

Ezzell said:
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Click to expand...
Click to collapse
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.

HolyHog said:
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
Click to expand...
Click to collapse
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though

Ezzell said:
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Click to expand...
Click to collapse
If MSM does not recognize your phone there is something wrong with your PC.
Make sure that you read the full post:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use another USB Port and/ or another USB cable.
Dont use Windows11
Install latest Universal ADB Driver
Install latest Qualcomm Drivers
Install latest OnePlus drivers.
In fact the last thing that will NOT work is MSM. If MSM does not work your phone is completly dead. (Which yours is obviously not because it boots into bootloader) This means if MSM does not work, there is something wrong on your end.
Talking about dead devices, be etremly careful what you do in Fastboot mode!
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com

Anything you do in the OS, like allowing OEM unlocking has **nothing** to do with MSM. In fact, a MSM flash will relock the bootloader. You will have to unlock again if you want to run anything except stock.
You have to boot the phone into EDL mode. Start MSM, then while holding the volume bar down, (UP and down, the entire button) plug into usb. Dont use the power button. (You may let volume keys go once done) There will be a dark screen, the only way to tell if in EDL mode is to check your device manager for the correct device. If you see anything on the screen you are not in EDL mode. I did use USB 2.0, do not use a hub.
I ask to start MSM first because on my Oneplus8, the EDL mode wont stay active for too long, unless MSM finds the phone.
If that does not work, put the phone into EDL mode and check your device manager (ports COM anf LPT) for QDLOADER 9008. Anything else, and the driver is not installed correctly and MSM won't work, If adb is working you can issue "adb reboot download" but the button press seems more applicable in your case.
There is a lot in the link below, it is for A10, I believe there is now a MSM for A11 but I have no experience with them.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/

I have tried all these and msm will not recognize the device in any state so Iv reverted to using a repair shop msm was successful in making the device stock the problem came from rebooting the device while msm was still connected and running. Pressing any button would lead to the download failed screen where the device is not recognized or into bootloader where oem is locked and even though before boot I checked unlocking enabled the fastboot command would not unlock the bootloader, if the store fix it I will try get details on what they did

Database Users

welcome