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!
Related
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!đź¤
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps
I hard bricked my OnePlus 9 (LE2113) while I was trying to unlock the bootloader. I tried flashing with Global, EU and Indian variants of MSM Tools but none of them worked.
I'm holding Power and Vol Up to reboot, then I hold Up and Down Volume buttons, plug in with USB cable and start MSM Tool. Every time I try to flash with "Use LIte Firehose" unchecked I always get the "Sahara communication" error at exactly 18 seconds. With "Use LIte Firehose" checked however download completes normally but phone is still hard bricked. This happened on every MSM Tool I tried.
I tried this on two laptops (Win 10 with USB 2.0 ports & WIn 11 with USB 3.0 ports) but ended up with the same results. I'm also using official cable. I have Qualcomm drivers installed.
Can anyone help me? Phone is hard bricked. I can't access anything besides EDL.
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
applyscience said:
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
Click to expand...
Click to collapse
I managed to flash with Lite Firehose but phone is still dead. I had some issues with phone being recognized but it somehow connected. I have also noticed that device under Ports (COM & LPT) is being recognized even after unpluging the phone, weirdly.
deleted because double post sorry
your device is an eu model i would not answer it with the india msm tool or the modded msm tool, you should get it to work with the eu msm tool
I don't know to what extent the modded msm tool has been processed (my concern is that if certain data on the mobile phone is changed from eu to india, I am concerned that the eu msm tool will no longer work with the eu mobile phone afterwards because certain data now identify cell phone as india model)
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!
Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/
Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com
Trying to flash my friend's phone back to stock but having some issues, you might have seen twixyfig's post in the OnePlus 9 Pro threads, but it's a regular OP9 and not the Pro.
Anyways, I have been trying to flash to working condition but MSM won't help. It keeps saying "No valid trg ID" and "Param preload" for a while now. This happened because we tried to root the phone but failed. The bootloader is unlocked, and fastboot works too.
TIA.
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
shadabkiani said:
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
Click to expand...
Click to collapse
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
twixyfig said:
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
Click to expand...
Click to collapse
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
shadabkiani said:
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
Click to expand...
Click to collapse
Thanks! Im gonna try this today and give you an update when something happens
twixyfig said:
Thanks! Im gonna try this today and give you an update when something happens
Click to expand...
Click to collapse
I think you were trying Indian MSM Tool. That might be the problem.
When your open MSM Tool, choose Others as login.
Write me in dm and I will help you, I think I can solve your problem
you can download OP9PRO India MSM tool(OnePlus_9_Pro_India_OxygenOS_11.2.4.4) and
1.unzip OP9Pro India ROM and download to your phone(select the firhose chebox)
2.if you success to download it,your phone will restart to the OOS.
3.Login your Google account and unlock OEM,then reboot your phone
4. install "Oxygen Updater", VERSION 5.7.3，you can find it on github.
5.download OOS for OP9 , archive name is "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip"
6.enter the oxygen updater,and flash "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip" to your phone
7.reboot and fixed!
PS: my english is so suck,try to read it!
good luck!