Database Info

Urgent! Help with the MSM tool (stuck in Param preload)

Hi
Please help! I have downloaded everything in this link:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
It contains "guacamole_21_O.07_190512_repack" and "L2 drivers"
I have followed the mega unbrick guide:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
So far the pc can find "Qualcomm HS-USB QDLoader 9008 (COM7).
But it stuck when I use MSM tool to unbrick it!
It keeps Param Preloading.
Please, any help will be really much appreciated!

I had a similar issue at first. Verify the drivers are good to go (it shows up as the right device in device manager) aside from that, try to boot into recovery or something to shut the phone down. Now hold down both volume buttons at the same time - followed by the power button. Immediately plug the phone in. Took me a couple tries but eventually you will succeed.

gh279760559 said:
Hi
Please help! I have downloaded everything in this link:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
It contains "guacamole_21_O.07_190512_repack" and "L2 drivers"
I have followed the mega unbrick guide:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
So far the pc can find "Qualcomm HS-USB QDLoader 9008 (COM7).
But it stuck when I use MSM tool to unbrick it!
It keeps Param Preloading..
Please, any help will be really much appreciated!
Click to expand...
Click to collapse
Try different drivers. When I ran into that issue I found different drivers on another website which ended up working.

thanks for your help. I have searched a lot and it seems it is the newest so far.

atrix4gtransamgta said:
I had a similar issue at first. Verify the drivers are good to go (it shows up as the right device in device manager) aside from that, try to boot into recovery or something to shut the phone down. Now hold down both volume buttons at the same time - followed by the power button. Immediately plug the phone in. Took me a couple tries but eventually you will succeed.
Click to expand...
Click to collapse
Thanks for your reply. I just did exactly as the instruction suggested. The device name in the manager was showed correctly. But still, the msm tool stucked at the param preprocessing stage.

Try installing Google's Android USB driver from Android studio, then try using the msmtool
Sent from my GM1915 using Tapatalk

D31337 said:
Try installing Google's Android USB driver from Android studio, then try using the msmtool
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Hi, I think it is not the adb side problem. Because when I use my laptop to connect to another phone, it works fine. Some one suggested the oneplus driver is not the latest. Actually I have checked the forum. It seems it is the newest one AFAIK.

Try to use the oneplus red USB cable if you arent already

Vanhoud said:
Try to use the oneplus red USB cable if you arent already
Click to expand...
Click to collapse
thanks, well, do you mean the oneplus driver? I have installed it already.

this took me a couple of hours to figure out so hopefully, it works for you all. I got a program from the xda forums called TOOL ALL IN ONE which can put your phone into edl mode at the click of a button. I also went to the device manager to make sure the phone was showing up as Qualcomm and not the QLK_ USB thing. if it shows up for you you have to download the drivers. I updated the drivers through the windows update > view optional updates > Drivers and install the Qualcomm one and restart pc. Then plug your phone in have the TOOL ALL IN ONE put it in edl mode then quickly open msm as administrator and uncheck Sha256 and press start. I think my Qualcomm driver was out of date and that might have been what caused me to have the param preload issue.

CookieMonster23 said:
this took me a couple of hours to figure out so hopefully, it works for you all. I got a program from the xda forums called TOOL ALL IN ONE which can put your phone into edl mode at the click of a button. I also went to the device manager to make sure the phone was showing up as Qualcomm and not the QLK_ USB thing. if it shows up for you you have to download the drivers. I updated the drivers through the windows update > view optional updates > Drivers and install the Qualcomm one and restart pc. Then plug your phone in have the TOOL ALL IN ONE put it in edl mode then quickly open msm as administrator and uncheck Sha256 and press start. I think my Qualcomm driver was out of date and that might have been what caused me to have the param preload issue.
Click to expand...
Click to collapse
Thanks but this does not work if you are stuck in Fastboot mode.

Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.

Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
Tried but not working. Tried 10 different drives, 3 different laptops with all the USB 2.0 ports but still no luck. Don't know what's the issue and why am keep getting stuck at param preload. What should I do?

umargillen said:
Tried but not working. Tried 10 different drives, 3 different laptops with all the USB 2.0 ports but still no luck. Don't know what's the issue and why am keep getting stuck at param preload. What should I do?
Click to expand...
Click to collapse
Are you making sure you are uninstalling any other drivers? You should only have installed the correct version.

Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
It's work, thank you

Rayan said:
Are you making sure you are uninstalling any other drivers? You should only have installed the correct version.
Click to expand...
Click to collapse
Yup. First uninstalled the other driver and installed this one again. Will give it one more go and share the outcome. But its very strange to me how confusing all this is. Can't get my head around why on Earth its not working. Am literally sick of not getting update. Badly want to flash the international rom to my Sprint OnePlus.

umargillen said:
Yup. First uninstalled the other driver and installed this one again. Will give it one more go and share the outcome. But its very strange to me how confusing all this is. Can't get my head around why on Earth its not working. Am literally sick of not getting update. Badly want to flash the international rom to my Sprint OnePlus.
Click to expand...
Click to collapse
Remember to reboot between uninstalling and reinstalling drivers. Also try to use the OEM cable that came with the OnePlus.

Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
Thanks a lot! You saved my night 11pm here ^^.
{
"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"
}

Awesomeness

Rayan said:
Finally got it to work. Turns out the vast majority of problems people encounter while trying the MSM Tool is with the Qualcomm drivers.
I found the correct (and latest version) drivers.
Just unzip the CAB file, uninstall any old Qualcomm drivers you have tried, and then install this one. It should work!
Let me know if you need any assistance.
Click to expand...
Click to collapse
thank you! this really work.

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at 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"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port

[REQ] Unihertz Titan Stuck in Bootloop

Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!

DorkyDev said:
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
Click to expand...
Click to collapse
Are you needing help or you solved the bootloop?

I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.

DorkyDev said:
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
Click to expand...
Click to collapse
platform-tools-latest | drivers USB OEM | MTK USB driver
Obviusly you only need flash stock recovery.img as your device has A9.
For Custom Recovery like TWRP maybe I can ask my friend to help you. If - you still TWRP want?!

Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.
{
"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"
}

DorkyDev said:
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.View attachment 5518101
Click to expand...
Click to collapse
Search in the internet How install MTK drivers, specially in the Win7. Better in Win10 and if you as that so the drivers [link] is much better, You can try installing that file but need reboot your computer. After try flash with SPFT.
Don't choose FORMAT+ALL or any option with FORMAT+........
Win7 need more effort to start drivers for Mediatek devices!
You can try pressing constantly the VOL - button when put USB for SPFT work.

The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.

DorkyDev said:
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
Click to expand...
Click to collapse
We often don't realize that certain errors are normal on our machine. So the question is to test in others computers.
But there are possibilities of company blocks or even something that has happened on the phone without it really should happen.
Some interesting cases:
1- I noticed with the image you showed about trying to flash all the firmware.
** So even if you have tried the Download only or Firmware Upgrade options, the question remains if you tried to flash only the recovery.img file? Obviously you can have the same error in SPFT?!
2- Cases of hardware vs software that match the use and characteristics found such as restarting the PC and trying to flash in a different USB port. Same problem?!: Drivers are resolved?!
The biggest case of suggesting something or thinking that this or that is a problem wastes precious time. Confirm the main steps!:
1- Driver correctly installed and working;
2- Driver works: Different USB PORT tested;
3- SPFT version must be tested. Mainly previous versions to confirm the error message that persists or may disappear;
4- Phone particularities: pressing the VOL buttons for a while can trigger the preloader that is responsible for the connection between the SPFT and your phone on the computer. Switching to VOL+ or Power or VOL- with VOL+ or VOL+ VOL - and Power may solve or confirm the non-solution.
Best way: Win10 with driver updates. Find the way to disable unsigned driver installations. But you can use this driver and you must restart your computer for it to take effect.
Make sure the USB port has a speed feature for the flashing process. Example: All USB ports are 2.0 only and SPFT asks for a USB 3.0 port to make the connection.
With everything confirmed the rest is something to question in relation to having the correct firmware file or the device itself having blocked the installation process due to a drastic change in the preloader or something that has changed and is blocking it.
Look previous posts about that so all depends on what you have and how you use it.
Unfortunately everyone (including me) who went through bad times like the one you have now, has a headache because it's a simple process and doesn't know what to do. But on the other hand, it's a huge learning experience when we solve it.
But there is still a choice without a headache: take it to a technical assistance and pay for it!

No on drivers when it goes to do the typical windows installation with the installation boxes in the upper left corner, I keep getting red x's.
I'm letting it charge some more and tomorrow trying again on my windows 7 laptop, as I think I'm also getting hung up on disabling driver signatures on windows 10 laptop. IDK if it's cause I'm dual booting JingOS 0.9 and that cancels out F7 or what the hang up is on that part.

In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.

shivadow said:
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
Click to expand...
Click to collapse
Would that also be done in SP Flash Tool or another software? I've also got these MTK tools.

Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.

DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
Click to expand...
Click to collapse
If you have more drivers for others phones like samsumg, motorola, lg, etc so remove that's and reboot computer. Install again MTK Drivers, UAC permissions and reboot computer. Test SPFT.
But here a good video to see and may be can fix - confirm driver issue in Win7:
Drivers: https://drive.google.com/file/d/1V2FducGB4pNpbkJWVmk2sfRJpf4Q5Bth/view
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
Click to expand...
Click to collapse
Maybe corrupted zip file?

Question Help: Black Screen after trying to flash stock ROM onto OnePlus 9 Global

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.

Question Did i brick my OP9? (no MSM works) perm screen off/ 20-30 sec bootlooping)

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