Database Info

Hard Bricked Oneplus 8

Hello XDA Members,
Please help me i have hard bricked oneplus 8 IN2017 Tmobile while installing Custom pixel Experience ROM
and now MSM tool Unbrick tool not working its shows download complete but phone is not booting after showing oneplus logo phone goes to EDL mode.
also i am not able to flash stock fastboot rom because bootloader is locked. Please help me how to unbrick this phone

Try MSM again, on a different PC and with a different USB cable *if* you can.
Aside from that contact OnePlus.
Was this your first time using MS download tool? Have you succesfully flashed to stock with MSM before?

yes i have used msm many times and tried on different PCs nothing is working
msm tool shows successfully download complete and now i am receiving this error (PIC attached)
i think i have messed up partitions.

Question Downgrade to oos 11 from custom rom without msm

Hello!
For some reason msm connects and disconnects shortly after displaying connected on msm.
Is there any other way to downgrade to oos 11 from custom roms?

Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com

Diaze said:
Hello!
For some reason msm connects and disconnects shortly after displaying connected on msm.
Is there any other way to downgrade to oos 11 from custom roms?
Click to expand...
Click to collapse
If you can't get the fastboot thing to work (I bricked my phone three times with fastboot flashing because sometimes fastbootd doesn't seem to want to flash correctly), open up the MSM Tool, click lite firehose, click Start, and *then* put the device in EDL and plug it in. If you do it this way, the software grabs it as soon as EDL comes up and it's more likely to succeed in the handshake and successfully flash. I have noticed that the phone doesn't stay in EDL for long before it tries to reboot for some reason.

EtherealRemnant said:
If you can't get the fastboot thing to work (I bricked my phone three times with fastboot flashing because sometimes fastbootd doesn't seem to want to flash correctly), open up the MSM Tool, click lite firehose, click Start, and *then* put the device in EDL and plug it in. If you do it this way, the software grabs it as soon as EDL comes up and it's more likely to succeed in the handshake and successfully flash. I have noticed that the phone doesn't stay in EDL for long before it tries to reboot for some reason.
Click to expand...
Click to collapse
It's a safety feature to keep it from getting stuck in edl. I second the start thing. I open msm tool. Click target op and start then plug device . I understand the lite Firehose deal though.

mattie_49 said:
It's a safety feature to keep it from getting stuck in edl. I second the start thing. I open msm tool. Click target op and start then plug device . I understand the lite Firehose deal though.
Click to expand...
Click to collapse
You would think that it would stop trying to reboot once a connection is established to the software though but obviously this is meant to be a factory flashing thing where they just leave it running and just plug and unplug nonstop so it wasn't important to implement anything better.

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.

Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient

Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore

The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers

you should be able to repair preloader from bootrom mode (BROM)

How to enter bootrom mode. I am sorry if it is a noob question

Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html

Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved

you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.

OnePlus 8T TMO | KB2007 | A12 to A11 Issues

Hello,
I recently upgrade to A12 it has caused a bunch of problems with gaming and general performance. I have tried following several guides to rollback using the MSM Tool to no avail.
What I have done is download the MSM Tool. Install the QUALCOMM driver. Everything seemed to be working, but the tool had an error bout "DDR detection failed" or something. Another user said to check Windows updates for a QUALCOMM device driver, so I did that. Now the phone is detected as MTP USB device when in EDL mode and I cant uninstall the driver.
I'm at a loss here. I do see that the guides don't mention KB2007, so I'm not sure if it's even supported>? I also tried downloading the A11 image and using the APK MyApplication2 to rollback, but that gave an error as well. Am I just screwed?

Felblood said:
Hello,
I recently upgrade to A12 it has caused a bunch of problems with gaming and general performance. I have tried following several guides to rollback using the MSM Tool to no avail.
What I have done is download the MSM Tool. Install the QUALCOMM driver. Everything seemed to be working, but the tool had an error bout "DDR detection failed" or something. Another user said to check Windows updates for a QUALCOMM device driver, so I did that. Now the phone is detected as MTP USB device when in EDL mode and I cant uninstall the driver.
I'm at a loss here. I do see that the guides don't mention KB2007, so I'm not sure if it's even supported>? I also tried downloading the A11 image and using the APK MyApplication2 to rollback, but that gave an error as well. Am I just screwed?
Click to expand...
Click to collapse
Check this thread.
[OP8T][OOS TMO KB09CB] 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

[SOLVED] Unbrick hard-bricked OP 8T

Hello people, unfortunately, I bricked my phone and am stuck trying to unbrick it.
How the bricking happened:
I bricked my OP 8T when I tried to update my OS from Lineage OS 18.1 (Android 11) to 19.1 (Android 12) following this guide: Official Upgrade Guide, I installed the firmware according to Firmware Upgrade Guide.
I can access neither recovery mode nor fast boot mode, adb doesn't work anymore, and I can't boot into Lineage either.
So the bricking occurred at step 7 in the first guide when rebooting to recovery. Note: I was surprised that the guide does not mention also flashing the recovery image in step 6 (it is an .img file not .zip). So I didn't flash the 19.1 recovery image but only the Lineage OS. Maybe that was a mistake.
Unbricking steps I tried:
I followed this guide for the unbricking procedure and this guide for installing the Qualcomm driver.
In the device manager, my device is correctly shown under ports as Qualcomm HS-USB QLoader 9008 (COM3).
I put my phone into EDL mode and it says connected in the MSMDownload Tool. When I now press "start" it says "Open Serial Device Failed". Edit: after rebooting pressing the start button now gets me "Sahara Communication Failed, Please try again after power off phone (PBL:6)"
I tried different versions of the MSM Download tool (the Europe versions, the global versions, and even the newer one of the TMobile versions from the above link), all with the same error message "Open Serial Device Failed".
I tried many different USB ports USB 2 and 3 under Windows 10.
Now I'm out of ideas on what to try.
Can anyone help me?
Cheers,
Alex

Yeah, that happened to me too. Obviously the LOS guides are missing something.
The only way out is to abandon all the data and Msm to stock...
You don't have to try different versions of MsmTools, you can only use the one which matches your hardware.
Pick yours from these:
[OP8T][OOS KB05AA/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
[OP8T][OOS TMO KB09CB] 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
About your Sahara error, try these steps:
1. Uninstall any driver completely you've installed manually;
2. Plug-in your device while it's under EDL mode, and ask Windows to check for update;
3. Install the driver from Windows update from "Advance Options" - "Optional Updates";
(Or from here [ https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ])
4. Press phone power button for over 1 minute and try to reboot it into EDL mode again;
5. Try EDL flash again.

My phone is now unbricked again. I used a friend's computer and followed some scattered hints. I used another USB cable, a USB 2 slot on a 64bit Windows with an Intel processor. There the MSM Download tool worked without a problem.