[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS

[2643625]

Thanks for your work.
I unpack the Zip file for the OP8T (OnePlus_8T_EU_OxygenOS_11.0.7.10) (EU)
I Scan the extracted folder with online service VIRUS TOTAL
Output of the scan is pretty desastrous (see attachment)... Are they all false positive?
I have to admit that Clamtk on my Linux box and Microsoft Secirity Essentials would not find anything wrong. But because some Virus and Malware can be really tricky to dtect and kill, I want to use caution...

If I really have to use MSMDownloadTool.exe to enventualy unbrick my OP8T, how safe would be to:

=> Create a restore point in Windows
=> Transfert *.zip to Win
=> Disconnect from network
=> Unzip the archive
=> Connect OP8T in EDL mode, check if the Qualcomm driver is loaded
=> Start MSMDownloadTool
=> After OP8T restored, delete *.zip and uninstall program all traces
=> Restore the System Restore point.

Thanks again.

 

[Rootk1t]

Thanks for your work.
I unpack the Zip file for the OP8T (OnePlus_8T_EU_OxygenOS_11.0.7.10) (EU)
I Scan the extracted folder with online service VIRUS TOTAL
Output of the scan is pretty desastrous (see attachment)... Are they all false positive?
I have to admit that Clamtk on my Linux box and Microsoft Secirity Essentials would not find anything wrong. But because some Virus and Malware can be really tricky to dtect and kill, I want to use caution...

If I really have to use MSMDownloadTool.exe to enventualy unbrick my OP8T, how safe would be to:

=> Create a restore point in Windows
=> Transfert *.zip to Win
=> Disconnect from network
=> Unzip the archive
=> Connect OP8T in EDL mode, check if the Qualcomm driver is loaded
=> Start MSMDownloadTool
=> After OP8T restored, delete *.zip and uninstall program all traces
=> Restore the System Restore point.

Thanks again.

Those are false positives.
If you're cautious, you can make backup of your system partition (and important files), perform the necessary actions with MSM tool, and after that restore your backup.
It will look like as you have never installed MSM.
I will not use restore points in Windows.

P.S: you can also use MSM in virtual machine envirinment, though you may have some problems with drivers accessing your phone from within VM.

 

[DroidFreak32]

If I lost a kilo every time this tool has saved me from a major heartbreak, I would probaby get a girlfriend by now.
I've run into all sorts of weird issues with my 8T, many times I thought there is no way Unbrixk guide can help, but it always does!

Although every time I faced some issue getting this tool to detect my device, From my experience, 3 things make sure everything goes smoothly.
1) Using a USB 2 port instead of Type C / 3
2) Disabling all anti virus before extracting and running the tool.
3) Not jumping to EDL directly after powering off, cooldown of a minute as mentioned in the OP seems to actually work.

Thanks for saving us all a ton of money!

 

[NewNoob911]

Hi,

Thank you so much for the MSM Tool!

I have downloaded it for my Eu version of the OnePlus 9 Pro. I tried to install Lineage OS, and managed to brick the phone. It is now stuck in Fastboot mode loop. I cannot access any other mode, nor can I get my laptop to connect to the phone. Bootloader unlocked. Any ideas please?

 

[NewNoob911]

Hi,

Thank you so much for the MSM Tool!

I have downloaded it for my Eu version of the OnePlus 9 Pro. I tried to install Lineage OS, and managed to brick the phone. It is now stuck in Fastboot mode loop. I cannot access any other mode, nor can I get my laptop to connect to the phone. Bootloader unlocked. Any ideas please?

 

[TheNewHEROBRINE]

Hi,

Thank you so much for the MSM Tool!

I have downloaded it for my Eu version of the OnePlus 9 Pro. I tried to install Lineage OS, and managed to brick the phone. It is now stuck in Fastboot mode loop. I cannot access any other mode, nor can I get my laptop to connect to the phone. Bootloader unlocked. Any ideas please?

Did you try to enter EDL mode?

 

[jv.batista]

Hello peeps,

Yesterday I've moved from OOS to LOS but to be honest I'm not liking it that much and I want to go back to OOS. I've been trying to get this to work but I might have been doing something wrong cause I can't get the app to work.

I just read the steps again and let's see if I got this right:

1- Unplug phone from PC and turn it off
2- Open the application, select EU in my case and press Start
3- Make sure I've waited a minute
4- While holding both volume buttons plug the usb cable
5- Release buttons and something should start happening

Did I miss anything?

Thanks

Edit1: I think I did, qualcomm drivers...

Edit2:

From this point onwards I just need to set it do EDL Mode and it should be fine rigth?

 

[Rootk1t]

Hi,

Thank you so much for the MSM Tool!

I have downloaded it for my Eu version of the OnePlus 9 Pro. I tried to install Lineage OS, and managed to brick the phone. It is now stuck in Fastboot mode loop. I cannot access any other mode, nor can I get my laptop to connect to the phone. Bootloader unlocked. Any ideas please?

MSM in this thread is for 8T, not for 9 Pro.

 

[joker925]

Hi everyone,

I have made a huge mistake and I need your help...

Some context:
I have a OP8T EU version, I was on LOS20 but I wanted to come back to OOS13. Since I am a lazy boy and I was using a mac, I tried the fastboot commands reported in this post here in order to avoid having to go through MSM.

Long story short, I flashed the wrong xbl file (the one for DDR5 instead of DDR4X) and phone went dead. This happened two weeks ago, and since then, the phone does not charge, connect to pc or boot into any mode with any type of key combination.

I read about a procedure involving a special USB cable which should force the phone to boot into EDL mode and allow it to be recognized by MSM, you can find it in this post from OP8Pro community. I bought the cable and started trying.

The problem:
My problem is that my phone has never been in EDL before, nonetheless connected to a PC, therefore I do not have the entry in device manager, and nothing new appears when I connect the phone to the computer with the button of the cable pressed, no "QHUSB_BULK", no "Unknown device", no anything.

I have installed all the existing version of the Qualcomm Drivers QDLoader 9008. Nothing.
I have tried on two different PCs, running both Win10 and Win7. Nothing.
I have tried all the ports, USB2 and USB3. Nothing.

I am truly running out of options and I don't have a clue regarding why the PCs should not read the phone. There is anything else that I might try? My only guesses are that the cable or the USBc port on the phone might be damaged, but I do not want to give up.

In case nothing works, I have seen another post in which they say that it is possible to force EDL by opening up the phone and making contact between two pins on motherboard, but I want to keep this as a last resort.

Any suggestion will be greatly appreciated! Thanks!

 

[jv.batista]

@joker925

In my case phone wasn't showing up in MSM 'cause I had no line in that grid. After installing the drivers (and I don't remember where I got them from) I got it to work and it was pretty much painless after that.

From what I read the voltages for ddr4x are higher so you might have fried it.

If you get some sort of com to appear on the grid you'll only need to set the phone in EDL mode (both volume button pressed and plugging the cable to the pc).

If it doesn't work, time to buy a new one. Every month that goes by I get more and more the impression that OnePlus just abandoned it...

 

[TheNewHEROBRINE]

Hi everyone,

I have made a huge mistake and I need your help...

Some context:
I have a OP8T EU version, I was on LOS20 but I wanted to come back to OOS13. Since I am a lazy boy and I was using a mac, I tried the fastboot commands reported in this post here in order to avoid having to go through MSM.

Long story short, I flashed the wrong xbl file (the one for DDR5 instead of DDR4X) and phone went dead. This happened two weeks ago, and since then, the phone does not charge, connect to pc or boot into any mode with any type of key combination.

I read about a procedure involving a special USB cable which should force the phone to boot into EDL mode and allow it to be recognized by MSM, you can find it in this post from OP8Pro community. I bought the cable and started trying.

The problem:
My problem is that my phone has never been in EDL before, nonetheless connected to a PC, therefore I do not have the entry in device manager, and nothing new appears when I connect the phone to the computer with the button of the cable pressed, no "QHUSB_BULK", no "Unknown device", no anything.

I have installed all the existing version of the Qualcomm Drivers QDLoader 9008. Nothing.
I have tried on two different PCs, running both Win10 and Win7. Nothing.
I have tried all the ports, USB2 and USB3. Nothing.

I am truly running out of options and I don't have a clue regarding why the PCs should not read the phone. There is anything else that I might try? My only guesses are that the cable or the USBc port on the phone might be damaged, but I do not want to give up.

In case nothing works, I have seen another post in which they say that it is possible to force EDL by opening up the phone and making contact between two pins on motherboard, but I want to keep this as a last resort.

Any suggestion will be greatly appreciated! Thanks!

I think that if the phone was working (in edl mode at least) it would be recognized by Windows, at least as unknown device. To rule out the possibility of a driver problem you could try connecting to the computer any other Qualcomm smartphone (if you can get ahold of one) with the deep flash cable and see if it is recognized while in EDL mode.

 

[Rootk1t]

@joker925
Just a guess, maybe the cable you bought is the faulty one....

 

[joker925]

Hi everyone,

I have made a huge mistake and I need your help...

Some context:
I have a OP8T EU version, I was on LOS20 but I wanted to come back to OOS13. Since I am a lazy boy and I was using a mac, I tried the fastboot commands reported in this post here in order to avoid having to go through MSM.

Long story short, I flashed the wrong xbl file (the one for DDR5 instead of DDR4X) and phone went dead. This happened two weeks ago, and since then, the phone does not charge, connect to pc or boot into any mode with any type of key combination.

I read about a procedure involving a special USB cable which should force the phone to boot into EDL mode and allow it to be recognized by MSM, you can find it in this post from OP8Pro community. I bought the cable and started trying.

The problem:
My problem is that my phone has never been in EDL before, nonetheless connected to a PC, therefore I do not have the entry in device manager, and nothing new appears when I connect the phone to the computer with the button of the cable pressed, no "QHUSB_BULK", no "Unknown device", no anything.

I have installed all the existing version of the Qualcomm Drivers QDLoader 9008. Nothing.
I have tried on two different PCs, running both Win10 and Win7. Nothing.
I have tried all the ports, USB2 and USB3. Nothing.

I am truly running out of options and I don't have a clue regarding why the PCs should not read the phone. There is anything else that I might try? My only guesses are that the cable or the USBc port on the phone might be damaged, but I do not want to give up.

In case nothing works, I have seen another post in which they say that it is possible to force EDL by opening up the phone and making contact between two pins on motherboard, but I want to keep this as a last resort.

Any suggestion will be greatly appreciated! Thanks!

A quick follow up, I managed to get the phone into EDL and restore it through MSM! Thanks to everyone for your suggestions.

In case anyone is in the same situation, I'll briefly share the steps followed. Since nothing else was working, in the end I ended up trying the motherboard test points method. What I did was:

• I opened the back cover of the device.
• Disconnected the battery and the cameras.
• Fired up Device Manager and MSM tool on Windows 10.
• Set-up MSM and pressed start.
• Then shortcircuited the pins on the motherboard of my OP8T (picture can be found in the linked post in my previous reply) and subsequently plugged in the cable in the USB2.0 port.
• Phone was immediately recognized and the flashing process finished smoothly.

As I side note, at first I was having issues with connection resetting every 10 seconds, but changing the cable (I was using the EDL deep cable which therefore I now strongly believe to be faulty) with another (not original) did the trick. Hope this might help anyone in the same situation, cheers!

 

[sethukrishnan]

Can I flash the latest OOS 13 with fastboot directly??? I'm on Pixel extended 12.0. I've used payload dumper to get all files...using flash all.bat

 

[joe460]

This worked beautifully for me once I turned off the signed driver requirements in Windows (start-up option no.7) to install the Qualcomm drivers.

I thought EDL mode wasn't working, but it turned out the be the drivers not working the whole time. I used the OOS 11.0.7.9 version to restore the phone.

Finally got my bricked OP8T KB2005 going again!

It was stuck on the following screen:
"The current image(boot/recovery) have been destroyed and can not boot."
"Please flash the correct image or contact customer service to fix it."

Thank you to @Some_Random_Username & all the other lifesavers!

 

[sfoklus]

I followed the instructions from the 2020 initial post and my device is not detected in the msm tool (while under the device manager, under "ports", my device is detected, at least as "Qualcomm HS-USB Diagnostics 900E (COM8)). All I can see is "Waiting for device". Any help please?

[Edit: Every time I connected the phone to my pc it was restarting on its own. I had to make sure that after I turn it off from the fastboot mode that I should instantly connect it to the pc and press both volume buttons]

 

[TheNewHEROBRINE]

I followed the instructions from the 2020 initial post and my device is not detected in the msm tool (while under the device manager, under "ports", my device is detected, at least as "Qualcomm HS-USB Diagnostics 900E (COM8)). All I can see is "Waiting for device". Any help please?

You're in the wrong mode (900E instead of 9008), how did you enter it?

 

[sfoklus]

You're in the wrong mode (900E instead of 9008), how did you enter it?

I've no idea. I messed up what my twrp flashing and now I'm back to step 1 again, with a bricked kebab. Now I can't even make my pc detect and it says "Waiting for device". In order for me not to wait an hour of update installs after I succeed unbricking it, is there an equivalent msm tool for an OOS 12 firmware?

 

[joe460]

I've no idea. I messed up what my twrp flashing and now I'm back to step 1 again, with a bricked kebab. Now I can't even make my pc detect and it says "Waiting for device". In order for me not to wait an hour of update installs after I succeed unbricking it, is there an equivalent msm tool for an OOS 12 firmware?

I had to boot Windows using startup option No.7 to ignore unsigned drivers to get it to work. I also had the issue where the device would boot as soon as I connected it. I was using a USB 2.0 hub since everyone was saying USB 2.0 worked better. I got it to work directly connected to USB 3.0 on my laptop (no hub) with the original charge/data cable and once the drivers were correctly installed everything worked as expected. Just make sure the (Qualcomm HS-USB QLoader 9008) device is not showing any errors, such as exclamation symbol. You also need to ensure you use the same USB port everytime otherwise it will create another COM serial port each time and you'll need to ensure the drivers are setup correctly on that port too.
This is what is should look like.

I battled with the drivers and other issues for about 2 days before I figured it out. In device manager you can enable View - Show hidden devices to confirm the driver is installed correctly. The COM port settings should be left as default.

Once it is set up right, it's amazing how quick and easy the process is. Good luck.

Also, dont's stress about the firmware version you currently have installed. It will totally blow away what is there (or in my case, not there - since I destroyed everything including boot/recovery partitions) and it reloaded OOS11. That then allowed me to update from there. Easy!

 

[sfoklus]

I had to boot Windows using startup option No.7 to ignore unsigned drivers to get it to work. I also had the issue where the device would boot as soon as I connected it. I was using a USB 2.0 hub since everyone was saying USB 2.0 worked better. I got it to work directly connected to USB 3.0 on my laptop (no hub) with the original charge/data cable and once the drivers were correctly installed everything worked as expected. Just make sure the (Qualcomm HS-USB QLoader 9008) device is not showing any errors, such as exclamation symbol. You also need to ensure you use the same USB port everytime otherwise it will create another COM serial port each time and you'll need to ensure the drivers are setup correctly on that port too.
This is what is should look like.
View attachment 5874305

I battled with the drivers and other issues for about 2 days before I figured it out. In device manager you can enable View - Show hidden devices to confirm the driver is installed correctly. The COM port settings should be left as default.

Once it is set up right, it's amazing how quick and easy the process is. Good luck.

Also, dont's stress about the firmware version you currently have installed. It will totally blow away what is there (or in my case, not there - since I destroyed everything including boot/recovery partitions) and it reloaded OOS11. That then allowed me to update from there. Easy!

Somehow it worked. Guess it could be the USB 3.0 thing, since I tried a different one this time. Thanks.