Was on Nameless 12 (based on OOS 11) but noticed everyone saying you needed to officially convert over to OOS 12. well nothing would allow me to install OOS and i mean nothing. the flushable zip from fastboot, zip variants for recovery flashing,, nothing. I even tried 2 previous msm toolkits i know worked before and a brand new one from recent treads here.
Nothing. my phone will just boot loop over and over about every 15-30 seconds, (based on the usb connection sounds, screen is off all the time. , while showing this
{
"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"
}
. i tried every combination of drivers with it (removing OOS official driver, as well as google and every variation of them)
but never showing up in any version of msm. now with the phone boot looping, i fear i am screwed. ive tried 4 separate pcs, all with 3 separate confirmed msms, , held every button combo in hopes of kicking it back into fastboot or anything else.
as for any MSM, it will reflect the proper Com port number but status of connection will always be N/A,
ive tried everything i know of. Please let this be a stupid fix i am just missing.
Which model do you have? My one is LE2110 also don't have a suitable msm tool, now get sucks in bootloader, even can't enter to recovery
tunglim said:
Which model do you have? My one is LE2110 also don't have a suitable msm tool, now get sucks in bootloader, even can't enter to recovery
Click to expand...
Click to collapse
Recovery is in boot.img on 9 series not separate partition. So inevitably if you loose boot on this device you loose recovery. Kinda ****ty but how it is.
It is going into EDL because it shows the 9008 port. Either you're not connecting the cable fast enough or it's a driver issue (the fact it says Quectel tells me that your drivers aren't right because it should say Qualcomm).
The phone doesn't stay in EDL mode for long, it tries to reboot normally every so many seconds. What I found is you have to click the Start button on the MSM Tool before the device is connected so it's looking for it (the MSM Tool is set up to continuously flash devices), do the button combo, and connect the USB cable.
First thing is first though, you need to fix your drivers. In device manager, right click the EDL listing, hit uninstall, and check the option to delete the driver from the computer.
Try the 64-bit drivers from here first (and follow the instructions to turn off signature enforcement). If it doesn't work, delete it in the same way and try the 32-bit version because that seems to work for others.
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
It is going into edl so it can be recovered, it's just a matter of finding the right drivers and possibly the right USB port/cable too because MSM Tool is really finicky.
mattie_49 said:
Recovery is in boot.img on 9 series not separate partition. So inevitably if you loose boot on this device you loose recovery. Kinda ****ty but how it is.
Click to expand...
Click to collapse
Lineage os was installed before the bricking, although I reflashed Lineage's recovery but it didn't work. Is there any other way besides restoring the stock image?
tunglim said:
Lineage os was installed before the bricking, although I reflashed Lineage's recovery but it didn't work. Is there any other way besides restoring the stock image?
Click to expand...
Click to collapse
Not that I'm aware of. Look at above post Ethereal answered your question and sees your issue.
tunglim said:
Lineage os was installed before the bricking, although I reflashed Lineage's recovery but it didn't work. Is there any other way besides restoring the stock image?
Click to expand...
Click to collapse
msm oneplus 9 pro indian variant tool. uncheck sha-check and click on lite firehose. make sure qualcom drivers are installed. press and hold both volumes and power like you're going to the bootloader and after a few seconds let go of the power and plug it in to the pc (still holding both volumes) until it connects. once connected start.
EtherealRemnant said:
It is going into EDL because it shows the 9008 port. Either you're not connecting the cable fast enough or it's a driver issue (the fact it says Quectel tells me that your drivers aren't right because it should say Qualcomm).
The phone doesn't stay in EDL mode for long, it tries to reboot normally every so many seconds. What I found is you have to click the Start button on the MSM Tool before the device is connected so it's looking for it (the MSM Tool is set up to continuously flash devices), do the button combo, and connect the USB cable.
First thing is first though, you need to fix your drivers. In device manager, right click the EDL listing, hit uninstall, and check the option to delete the driver from the computer.
Try the 64-bit drivers from here first (and follow the instructions to turn off signature enforcement). If it doesn't work, delete it in the same way and try the 32-bit version because that seems to work for others.
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
It is going into edl so it can be recovered, it's just a matter of finding the right drivers and possibly the right USB port/cable too because MSM Tool is really finicky.
Click to expand...
Click to collapse
That is the exact driver I am using and used when I msm'd my op9 on may 31st. The device title is for sure confusing though. I will just try removing and reattempting.
That ks
applyscience said:
That is the exact driver I am using and used when I msm'd my op9 on may 31st. The device title is for sure confusing though. I will just try removing and reattempting.
That ks
Click to expand...
Click to collapse
Quectel is another company altogether, they seem to specialize in IoT devices, so something is definitely not right.
Here is someone who managed to fix it that tells how they did it -> https://forum.xda-developers.com/t/...your-device-to-oxygenos.4085877/post-86267755
If you want to get more advanced with it and can't get it working any other way you can try the Linux edl command line tools.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
It's not that difficult to make an Ubuntu live USB.
EtherealRemnant said:
Quectel is another company altogether, they seem to specialize in IoT devices, so something is definitely not right.
Here is someone who managed to fix it that tells how they did it -> https://forum.xda-developers.com/t/...your-device-to-oxygenos.4085877/post-86267755
If you want to get more advanced with it and can't get it working any other way you can try the Linux edl command line tools.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
It's not that difficult to make an Ubuntu live USB
Click to expand...
Click to collapse
yeah, i honestly thought msm was a windows requirement. i am very comfortable in linux, especially anything debain based. thats being said, python is another story but can follow directions. (usually)
i uninstalled the qualtec and just refreshed devices and qual showed up. i can now get connected to but the log below is habitually on any device i attempt it on.
i tried this on 4 computers and they all end up with this in their msm log, regaurdless of which version i tried
6600][06-23 19:46:00.029]<4> Tool version verified! (V5.1.89)
[6600][06-23 19:46:00.029]<4> project 20853 not support boot mode feature
[6600][06-23 19:46:00.029]<4> project 20853 enable fuse
[6600][06-23 19:46:00.052]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[6600][06-23 19:46:00.057]<4> Skip multi-image identify: 0
[8304][06-23 19:46:01.688]<4> [0] SetComStep: 1
[8304][06-23 19:46:01.688]<4> [0] GetComStep: 1
[8304][06-23 19:46:01.689]<4> CID = -1
[8304][06-23 19:46:01.689]<4> Non TMO group
[8304][06-23 19:46:01.692]<4> [1] Set device as UFS
[8304][06-23 19:46:01.928]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[8304][06-23 19:46:04.140]<4> [1] [SP][195] Check cmd done status failed. 1
[10188][06-23 19:46:33.297]<4> [0] SetComStep: 1
[10188][06-23 19:46:33.297]<4> [0] GetComStep: 1
[10188][06-23 19:46:33.298]<4> CID = -1
[10188][06-23 19:46:33.298]<4> Non TMO group
[10188][06-23 19:46:33.299]<4> [1] Set device as UFS
[10188][06-23 19:46:43.547]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[10188][06-23 19:46:43.703]<4> [1] Get PBL Info failed (6).
[10188][06-23 19:46:43.703]<4> [1] Failed to get PBL info. (6)
[7460][06-23 19:46:50.201]<4> [0] SetComStep: 1
[8204][06-23 19:46:52.785]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&1a60d403&0&2#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[8204][06-23 19:47:20.989]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&1a60d403&0&2#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[7460][06-23 19:47:20.991]<4> [0] GetComStep: 1
[7460][06-23 19:47:20.992]<4> CID = -1
[7460][06-23 19:47:20.992]<4> Non TMO group
[7460][06-23 19:47:20.993]<4> [1] Set device as UFS
[7460][06-23 19:47:21.220]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[7460][06-23 19:47:23.392]<4> [1] [SP][195] Check cmd done status failed. 1
Click to expand...
Click to collapse
applyscience said:
yeah, i honestly thought msm was a windows requirement. i am very comfortable in linux, especially anything debain based. thats being said, python is another story but can follow directions. (usually)
i uninstalled the qualtec and just refreshed devices and qual showed up. i can now get connected to but the log below is habitually on any device i attempt it on.
i tried this on 4 computers and they all end up with this in their msm log, regaurdless of which version i tried
Click to expand...
Click to collapse
Ignore the log, what is the error the MSM Tool is giving?
EtherealRemnant said:
Ignore the log, what is the error the MSM Tool is giving?
Click to expand...
Click to collapse
its always that. spends about 10 seconds saying its "downloading" then that. 4 version of msmtoolkit and 3 seperate pcs. man i suck.
applyscience said:
View attachment 5644033
its always that. spends about 10 seconds saying its "downloading" then that. 4 version of msmtoolkit and 3 seperate pcs. man i suck.
Click to expand...
Click to collapse
Check use lite firehose and then click Start on the MSM Tool with the phone not connected (this makes it look for the phone automatically), press and hold both volume buttons, and connect the USB cable. If you do it right, the MSM Tool will grab the phone the second it connects and it will flash properly.
The phone doesn't stay in EDL mode for long, it keeps trying to reboot normally, so you have to be lightning quick with getting the phone and MSM communicating.
EtherealRemnant said:
Check use lite firehose and then click Start on the MSM Tool with the phone not connected (this makes it look for the phone automatically), press and hold both volume buttons, and connect the USB cable. If you do it right, the MSM Tool will grab the phone the second it connects and it will flash properly.
The phone doesn't stay in EDL mode for long, it keeps trying to reboot normally, so you have to be lightning quick with getting the phone and MSM communicating.
Click to expand...
Click to collapse
ive flashed my 9 a lot. im really hoping i am just ****ing it up but i also get this on every system haf the time too, and ive never seen it before.
Device USB\VID_0000&PID_0002\5&1a60d403&0&2 was configured.
Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.488
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\DEVICE_DESCRIPTOR_FAILURE
Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\4&73f3995&0&0
Click to expand...
Click to collapse
applyscience said:
ive flashed my 9 a lot. im really hoping i am just ****ing it up but i also get this on every system haf the time too, and ive never seen it before.
View attachment 5644035
Click to expand...
Click to collapse
I mean it's certainly possible that you have screwed the device up more than it can be recovered. At this point it sounds like trying to do it in Linux is your last shot before sending your phone to OnePlus. With the endless communications errors though, I'm not confident that Linux will work any better.
EtherealRemnant said:
I mean it's certainly possible that you have screwed the device up more than it can be recovered. At this point it sounds like trying to do it in Linux is your last shot before sending your phone to OnePlus. With the endless communications errors though, I'm not confident that Linux will work any better.
Click to expand...
Click to collapse
this is as close as it gets. the weird part is the flashable zips also said "expected one pl[us 9" as the error for them not working, which is why i attempted msm.
the fact i got that on the msm tool i used weeks ago is pretty bad....fudge.
so my phone USES t mobile, but is not from tmobile. it was a global device, but i could try the tmboile for the hell of it.
Device not match image happens when you super brick, the MSM can't match the device anymore because it's too corrupted. Try Indian 9 Pro MSM as it doesn't seem to perform the device checks.
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you get that working, I'll tell you how to use fastboot enhance to get back to global firmware.
EtherealRemnant said:
Device not match image happens when you super brick, the MSM can't match the device anymore because it's too corrupted. Try Indian 9 Pro MSM as it doesn't seem to perform the device checks.
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you get that working, I'll tell you how to use fastboot enhance to get back to global firmware.
Click to expand...
Click to collapse
its going.....you genius of vast knowledge.
what would be your suggestion to get it back to 9 non pro NA or global?
applyscience said:
its going.....you genius of vast knowledge.
what would be your suggestion to get it back to 9 non pro NA or global?
Click to expand...
Click to collapse
Follow this guide I just posted.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
Related
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.
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
Update drivers on PC
For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.
EtherealRemnant said:
For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.
Click to expand...
Click to collapse
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!
MacroWolf said:
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!
Click to expand...
Click to collapse
Unfortunately when that happens things get a lot more complicated which is why I personally think we should not encourage people to try to flash with fastboot, it messes up more often than it works, and now the device isn't recognized by the MSM.
Go download the Indian 9 Pro MSM Tool and flash that. Then download the global 11.2.10.10 full update from the pinned post and flash that from the local upgrade menu to get a working phone. From there you can either unlock the bootloader and go to a custom ROM or you can continue on to flash the global OOS 12 update.
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Qualcomm drivers.7z
drive.google.com
JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.
JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
EtherealRemnant said:
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.
Click to expand...
Click to collapse
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.
MacroWolf said:
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.
Click to expand...
Click to collapse
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).
EtherealRemnant said:
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).
Click to expand...
Click to collapse
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.
MacroWolf said:
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.
Click to expand...
Click to collapse
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.
EtherealRemnant said:
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.
Click to expand...
Click to collapse
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
Awesome, glad that you got it sorted.
MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
I'm having a similar issue. Black screen. I can get it to start the process in the MSM tool (after some trial and error) but it now tells me "Device not match image". I've downloaded the Global tool ( and my device is a OnePlus 9 5G LE2115). OnePlus wants me to send in the device. I'd rather not if I don't have to.
MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
It's from not restarting after installing drivers
EtherealRemnant said:
Awesome, glad that you got it sorted.
Click to expand...
Click to collapse
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
{
"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"
}
Does that look right?
Also as far as I can tell I have all the proper drivers. Windows seems to agree when trying to update them in device manager.
What is it I'm missing? Any advice would be amazing.
shadowofdeth said:
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
View attachment 5634873
Does that look right?
What is it I'm missing? Any advice would be amazing.
Click to expand...
Click to collapse
Update the driver.
Unbrick OnePlus 9, 9 Pro Using EDL Firmware With MSM Download Tool
OnePlus has finally launched its OnePlus 8 series successor known as OnePlus 9 and 9 Pro with a much-upgraded camera, processor, display, refresh rate,
www.getdroidtips.com
Mate. Where were you the other day!
I'm actually embarrassed it was that easy. All day I've been on this. All. Day.
I swear I installed those drivers the first time as well. Windows confirmed everything was legit too but failed anyway.
Seriously thank you.
Glad that you got it fixed now. I have bricked my phone enough times messing with custom ROMs that I have the whole restoration process to a refined science at this point lol.
I was try to, unlock my phone from t-mobile (https://forum.xda-developers.com/t/convert-t-mobile-oneplus-9-to-global-or-other-firmware.4277169/), everything was fine.
i unlock my bootloader and SIM, but when i use the "flash_all.bat" and that finish, i have to Reboot into recovery and wipe everything, but the phone don't turn on.
This never happened to me, so i don't know what to do.
Nothing appears, any logo or battery icon.
when i conect the phone to the pc i heard the sound but seconds later is disconected
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
Run the tool as other and click start before hooking up the phone while holding both volume buttons.
AtoZ0to9 said:
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
Run the tool as other and click start before hooking up the phone while holding both volume buttons.
Click to expand...
Click to collapse
{
"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"
}
Idk if im doing something wrong but nothing happens
Ok, so if the MSM tool never shows any indication that it has seen the phone in EDL mode, doesn't start the flashing, etc, but you hear the computer noise when you plug it in, you should investigate your drivers.
Open up the Device Manager and then plug the phone up in EDL mode. EDL mode is achieved by holding both volume buttons while plugging in the phone. Look in the device manager and see what comes up. Somewhere around here are the correct drivers. Look at all of the unbrick / msm threads and one of them will have a driver download for you.
It sounds like a brick, and you are only getting into EDL mode, the mode used to flash back to stock with the MSM tool. So. Drivers. Check them out, and get that sorted and I believe you will be able to revive it.
AtoZ0to9 said:
Ok, so if the MSM tool never shows any indication that it has seen the phone in EDL mode, doesn't start the flashing, etc, but you hear the computer noise when you plug it in, you should investigate your drivers.
Open up the Device Manager and then plug the phone up in EDL mode. EDL mode is achieved by holding both volume buttons while plugging in the phone. Look in the device manager and see what comes up. Somewhere around here are the correct drivers. Look at all of the unbrick / msm threads and one of them will have a driver download for you.
It sounds like a brick, and you are only getting into EDL mode, the mode used to flash back to stock with the MSM tool. So. Drivers. Check them out, and get that sorted and I believe you will be able to revive it.
Click to expand...
Click to collapse
My computer detects my iphone, but when i connect the oneplus phone in my order pc is detectect like this
Delete that driver (check the box to permanently delete) and install this one:
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
Try the process again.
Loshim said:
View attachment 5655997
My computer detects my iphone, but when i connect the oneplus phone in my order pc is detectect like this
Click to expand...
Click to collapse
The TMobile msm might work but most likely won't if it doesn't use the OnePlus 9 pro msm and you need to install the driver that @AtoZ0to9 has mentioned
AtoZ0to9 said:
Delete that driver (check the box to permanently delete) and install this one:
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
Try the process again.
Click to expand...
Click to collapse
i did, i unnistall everything and install again, is the same, i connect my moms phone and is detecting my iphone to, idk what to do
Loshim said:
i did, i unnistall everything and install again, is the same, i connect my moms phone and is detecting my iphone to, idk what to do
Click to expand...
Click to collapse
Does it connect to the msm now also calm down same thing was happening to my phone and it's working fine now you'll be fine
I remember that I did something with the drivers in the process, since the abd bootloader was not detecting it for me, I really do not know if it influences.
this is the driver "android_winusb.inf"
Loshim said:
I remember that I did something with the drivers in the process, since the abd bootloader was not detecting it for me, I really do not know if it influences.
this is the driver "android_winusb.inf"
Click to expand...
Click to collapse
Did you install the driver that @AtoZ0to9 linked
stez827 said:
Does it connect to the msm now also calm down same thing was happening to my phone and it's working fine now you'll be fine
Click to expand...
Click to collapse
When you connected it did you just connect it and try or did you put in edl mode
stez827 said:
Did you install the driver that @AtoZ0to9 linked
Click to expand...
Click to collapse
yes i did
stez827 said:
When you connected it did you just connect it and try or did you put in edl mode
Click to expand...
Click to collapse
i put with edl mode
Ok well you need to download the OnePlus 9 pro msm tool
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
stez827 said:
Ok well you need to download the OnePlus 9 pro msm tool
Click to expand...
Click to collapse
Also 100% download this. Be prepared for everything.
AtoZ0to9 said:
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
Click to expand...
Click to collapse
Dude the TMobile msm is absolute dog**** and when I bricked my phone using the same guide he did I had to use the India OnePlus 9 pro msm tool as it was the only msm that worked so no it's not a problem with USB ports or drivers I had literally the same exact error and I ****ed my phone the same exact way so while there may be a extremely small chance that this fixes it it's still extremely unlikely that it will fix it
AtoZ0to9 said:
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
Click to expand...
Click to collapse
so, i connect the phone with edl and without edl, but in the devices manager nothings happens nothings appears, i heard the sound but i dont see nothing
you guys recommend me using another computer?
stez827 said:
Dude the TMobile msm is absolute dog**** and when I bricked my phone using the same guide he did I had to use the India OnePlus 9 pro msm tool as it was the only msm that worked so no it's not a problem with USB ports or drivers I had literally the same exact error and I ****ed my phone the same exact way so while there may be a extremely small chance that this fixes it it's still extremely unlikely that it will fix it
Click to expand...
Click to collapse
Kinda makes sense since the service is too. Thanks for the clarification, that the conversion guide does weird **** sometimes that makes the regular MSM not work?
I'm lucky to have the NA model which isn't as much dog ****, or just a smaller dog anyways. Seems the carrier variants suck more.
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.
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!