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.
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
EDITED: (The whole process was done on a laptop with windows 11 and usb 3.0 ports)
I solved it by doing the following:
What I did was use the msm tool for the indian op9 pro with the option "sha256 check" unchecked and the option "Use lite firehose" checked. Doing these steps the msm tool did not give any failure. Following this I loaded the device and even started it with the op9 pro india rom to test it (it is not recommended to leave this rom because it has certain errors in the image).
Finally I turned off the device and I did the same process with the msm tool for the global op9 normal, but with the default options.
Use this thread. Thread '# Solved # Global MSM op9 Flashing' https://forum.xda-developers.com/t/solved-global-msm-op9-flashing.4373511/
mattie_49 said:
Use this thread. Thread '# Solved # Global MSM op9 Flashing' https://forum.xda-developers.com/t/solved-global-msm-op9-flashing.4373511/
Click to expand...
Click to collapse
Ok, after trying what one of the answers in that thread says (disabling the "Sha256 check" box and activating the "Use Lite Firehose" box) I have managed to switch to "Param preload" and the error it returns is the next:
The device does not match the image
For what it's worth my device is the LE2110 model with gloval rom.
Thank you for your time and for responding so quickly.
Angel Cubero said:
Ok, after trying what one of the answers in that thread says (disabling the "Sha256 check" box and activating the "Use Lite Firehose" box) I have managed to switch to "Param preload" and the error it returns is the next:
The device does not match the image
For what it's worth my device is the LE2110 model with gloval rom.
Thank you for your time and for responding so quickly.
Click to expand...
Click to collapse
You have to do that with the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
mattie_49 said:
You have to do those on the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
Click to expand...
Click to collapse
Testing with the version of the msm tool for the oneplus 9 pro india returns the error:
Unsupported Target O2
So I will try the version for the oneplus 9 pro global.
mattie_49 said:
You have to do that with the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
Click to expand...
Click to collapse
I have not been able to do anything with the Indian op9 pro msm tool version or with the global version. In the Indian version the aforementioned error appears and in the global one the error "Devices not match image" appears.
I can't think of what else to do.
Angel Cubero said:
I have not been able to do anything with the Indian op9 pro msm tool version or with the global version. In the Indian version the aforementioned error appears and in the global one the error "Devices not match image" appears.
I can't think of what else to do.
Click to expand...
Click to collapse
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/India_LE15DA/R%20(11)/OnePlus_9_Pro_India_OxygenOS_11.2.4.4.zip
Use this one and try to untic sha-256 check and tic use lite-firehose.
mattie_49 said:
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/India_LE15DA/R%20(11)/OnePlus_9_Pro_India_OxygenOS_11.2.4.4.zip
Use this one and try to untic sha-256 check and tic use lite-firehose.
Click to expand...
Click to collapse
Again "Unsupported Target O2".
Angel Cubero said:
Again "Unsupported Target O2".
Click to expand...
Click to collapse
OnePlus customer support and get a remote session. They will msm for you
mattie_49 said:
OnePlus customer support and get a remote session. They will msm for you
Click to expand...
Click to collapse
Obviously that will cost money, right?
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
Click to expand...
Click to collapse
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
Click to expand...
Click to collapse
hi bro , i have the same issue like you , did you found a solution , can you help me plz
thanks
best regard
You can try this and see if it works: (last post)
Display becomes unresponsive after OOS 12 update
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever. I upgraded from OOS 11.2.10.10 to OOS...
forum.xda-developers.com
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
EDITED: (The whole process was done on a laptop with windows 11 and usb 3.0 ports)
I solved it by doing the following:
What I did was use the msm tool for the indian op9 pro with the option "sha256 check" unchecked and the option "Use lite firehose" checked. Doing these steps the msm tool did not give any failure. Following this I loaded the device and even started it with the op9 pro india rom to test it (it is not recommended to leave this rom because it has certain errors in the image).
Finally I turned off the device and I did the same process with the msm tool for the global op9 pro, but with the default options.
Click to expand...
Click to collapse
You have, single-handedly, saved me from having to send my phone into OnePlus for repair. I was getting the same error where the global MSM tool would not work. I downloaded the Indian version, unchecked sha256, and checked use Lite firehose. It restored my phone on the first try.
Once my phone booted, I went back into EDL mode by powering off my phone fully, plugging it back into the computer, and holding the power + vol up + vol down buttons. I was then able to use the Global MSM tool to restore the Global ROM.
THANK YOU SOO MUCH!!!!
LE2125
Hi, this thread seems to be kinda old but I am trying this on my LE2110 and it always fails at Downloading super.img..
I actually tried a different MSM (OnePlus 9 EU) one month ago and it worked but now it does not
Hope that it works soon i guess
CitaroSR said:
Hi, this thread seems to be kinda old but I am trying this on my LE2110 and it always fails at Downloading super.img..
I actually tried a different MSM (OnePlus 9 EU) one month ago and it worked but now it does not
Hope that it works soon i guess
Click to expand...
Click to collapse
Is the pc plugged into the internet? It can aquire the needed files to fix device if it's connected to data.
mattie_49 said:
Is the pc plugged into the internet? It can aquire the needed files to fix device if it's connected to data.
Click to expand...
Click to collapse
yes it is connected to the internet
This MSM Tool worked (it worked last time too but it did not work since yesterday for me, until now)
thank you for your reply anyway. My phone is restored!
I tried following the "Global/US OnePlus 9 Unbricking Guide" but I get stuck at the drivers part and while I can see that my phone is connected as a device to my PC I cant seem to install the drivers or get access to root folders (which I assume is connected). Ive tried using software to download the drivers for me and I've tried following the notes that came with the qualcom drivers file. The only thing I can do is boot my phone into fast boot but every option from there just leads to "phone corrupt... cant boot" error message
casualBricker said:
I tried following the "Global/US OnePlus 9 Unbricking Guide" but I get stuck at the drivers part and while I can see that my phone is connected as a device to my PC I cant seem to install the drivers or get access to root folders (which I assume is connected). Ive tried using software to download the drivers for me and I've tried following the notes that came with the qualcom drivers file. The only thing I can do is boot my phone into fast boot but every option from there just leads to "phone corrupt... cant boot" error message
Click to expand...
Click to collapse
use msm download tool to unbrick your phone
just follow the instructions its works i used it 3 times for my 9
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
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!
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
riva! said:
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Click to expand...
Click to collapse
Are you TMobile or global 9?
Frosthaxx said:
Are you TMobile or global 9?
Click to expand...
Click to collapse
tmobile
posar said:
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
Click to expand...
Click to collapse
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
riva! said:
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
Click to expand...
Click to collapse
Indian msm tool works on lite Firehose. Then use TMobile India mod and you can from there do what you need to do. Caution however. Doing the Indian trick makes your bootloader to the Indian bootloader but all functions will still work. You just can't use normal msms anymore
Unfortunately the bricking your describing is what happened to me because I goofed something. But I was able to get back using this to TMobile India after Indian. Then using the bootloader unlock guide in TMobile.a few update scenarios, then eventually evolution x. Unless someone has a better way there's not much written about this situation. I had to figure it out myself
IF ANYONE needs info on how i managed to fix this, please dm me or add my socials. If you flashed the wrong xbl/xbl_config files and now your sahara/firehose doesnt work, feel free to reach out. it took me 4 days straight of surfing and downloading and trial and error.
Unfortunately I don't think my issue can be fixed. There isn't anything specifically on fixing Indian region bootloader. Once that's done I think it's sol but it still works normal. I had to however because my brick also wasn't reading the USB either. It was a very odd situation. And I've modded and given advice on multiple phones. I'm glad you got yours working though. Doesn't bother me though
Phone works and the India mod get me back where needed. But others that haven't flashed the Indian msm tool could benefit from your find