Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end saying
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike
vr4mike said:
Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end saying View attachment 5563423
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike
Click to expand...
Click to collapse
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries
GbnrVR said:
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries
Click to expand...
Click to collapse
well I tried to install a rom from this section, and need some form of recovery, so I figured the people here would likely be able to help. I will gladly post in another section if I have to...
Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.
psi.singh03 said:
Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.
Click to expand...
Click to collapse
I just searched qualcomm hs-usb, and found a download for the computer. After installing it, I rebooted my computer, and device installer now finds the phone listed as Qualcomm HS-USB QDLoader 9008 and assigned it to COM3. I have not had luck yet finding a working version of the MSM Download Tool. Every version I find and download says "packed image does not exist"
Can somebody give me the msm download tool? I have downloaded 4.0 from a few places and can not get it to work. Most downloads say package does not exist as the above screenshot shows. Others seem to work, and give a message that msm tool is running, but no windows ever pop up to log in or anything.
Am I doing something wrong trying to use the tool?
Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly
mortazanabin said:
Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly
Click to expand...
Click to collapse
Same thing. I keep getting this message when I try to open it. I tried double clicking the exe and also tried right click/run as administrator. Both give the same result.
try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....
mortazanabin said:
try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....
Click to expand...
Click to collapse
It did not detect as a virus, but how do I run/install a .rar file?
Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore
kirankowshik said:
Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore
Click to expand...
Click to collapse
I can not get into fastboot. I believe the phone is stuck in EDL mode. I have gotten MSM Download tool to open, but it will not flash to device. The tool knows that my phone is connected to COM3, but the MSM tool says waiting for device after clicking start, and never goes any further.
If anyone has experience with the MSM Downloading Tool and can help out, please chime in.
Thanks for the help everyone. I'm slowly getting there.
So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?
try this method...
i thik this will help you to unbrick your device...
mortazanabin said:
try this method...
i thik this will help you to unbrick your device...
Click to expand...
Click to collapse
I can follow that exactly. The problem comes down to when connecting to USB cable and pressing start, the tool always says waiting for device, as if my device is not in EDL mode. I really think the issue is coming down to drivers for the phone to communicate with the tool. I do not think there should not be a caution symbol in device installer (as noted above) when the driver is properly installed. (even tho windows says I have the latest qualcomm driver for the device)
Does anyone have an updated driver in case I have an incorrect version? I am using the below. It says from 2014, so Im not sure that it is the correct driver. I got the link from a oneplus 8T post somewhere. I do not recall exactly which post it was.
your windows version? windows 10 or 11?
mortazanabin said:
your windows version? windows 10 or 11?
Click to expand...
Click to collapse
windows 10
I uninstalled and tried reinstalling the drivers, and now I can't get any of them to install. Device installer is back to saying QUSB_BULK for the device.
Disable windows dirver signature enforcement check
=========
Try this driver
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
=========
Try this msm tool
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
thanks me later if successful....
vr4mike said:
So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?
View attachment 5563605
Click to expand...
Click to collapse
You have a yellow triangle there disable the driver signature in windows the MSN tool should be work properly
I got it to work!!!!
It was the driver signature enforcement.
However, that was not the only issue. After disabling the signature enforement, it was connecting to the device, but still not working. The stsus in the configuration panel started to connect, but then failed in red. I tried it a few times with the same result. I tried holding the 2 volume buttons while plugging in the USB, that didn't change anything either.
What ended up working was holding all 3 buttons while the tool was connected. It caused the device to momentarily disconnect and reconnect to the USB (via disappearing and reappearing in device installer, as well as the laptop making the disconnected and connected sounds) As soon as it reconnected and the laptop made the sound, the tool instantly started transmitting data and functioning.
My phone boots up as it did stock now, and does not even tell me that the bootloader is locked anymore upon first power up. It is 100% functioning just as it came out of the box!!!
I CAN NOT THANK THIS FORUM ENOUGH!!!!!
I have been using information here for years since I rooted my first Galaxy S3. This is the first time I have had to make an account and post.
You guys are the best, and were my only saving grace. Oneplus doesn't even have a working phone number anymore. All support must go thru email.
THANK YOU ALL SO MUCH!!!
I hope this information helps somebody else.
I am trying to use the msm tool to unroot my OnePlus 8t tmobile variant. Using the MSM tool I have run into a few different problems.
1. Drivers. When my phone is in edl mode plugged in to my computer, device manager recognizes it as usb_bulk. I tried using the provided .cab file to update windows Qualcomm drivers but windows could not ever find the files when updating. I found on another forum a automatic installer.
2. Although it now says Qualcomm 9008 windows says that driver digital signature is not recognized or corrupted. However the MSM tool does finally show COM 5 and when I plug in my device is stuck at waiting for device.
I'm pretty stuck right now and any information to help me out would be appreciated.
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
mreese14 said:
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
Click to expand...
Click to collapse
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
gforceriders said:
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
Click to expand...
Click to collapse
Worked for me, thank you!
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.
Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?
Reo0o said:
Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?
Click to expand...
Click to collapse
Install all the necessary drivers and use MSM tool to restore your phone.
[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
P.S: Don't use fastboot enhance app, as it wasn't updated for quite some time and was reason of bricking several phones after flashing.
If you used Fastboot Enhance it could have flashed the wrong xbl file for your RAM type. If is it so, the only thing you can try is a deep flash cable or shorting the test pins on the motherboard.