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.
Related
SOLVED - you have got to be kidding me though. i had 2 faulty cables, one was my original cable and another a brand new one. so i used one of my friends and it worked fine. I HATE ELECTRONICS
my drivers dont work and my phone is stuck in boot loop and i CANNOT get into recovery
i just need someone that can get me back to stock :[
PM ME if you can help
heres my problem thread
http://forum.xda-developers.com/showthread.php?t=1353314
VIDEO showing boot loop (same thing if i try 3 button recovery)
http://www.youtube.com/watch?v=n3ALNj5q-hY
VIDEO showing download mode + odin , USB NOT RECOGNIZED usb error 43 device has stopped working
http://www.youtube.com/watch?v=D4CnRnecNrQ
i have deleted all drives so someone can help me fresh
rsx19 said:
my drivers dont work and my phone is stuck in boot loop and i CANNOT get into recovery
i just need someone that can get me back to stock :[
Click to expand...
Click to collapse
Restart your computer and then pull the battery out of your phone and put it back in. Now on your computer open Odin and then hold vol+ and vol- and plug in the USB cord this will put you in downlaod mode. And use Odin to get you back to a stock rom
Currently Fusionized
Wdustin1 said:
Restart your computer and then pull the battery out of your phone and put it back in. Now on your computer open Odin and then hold vol+ and vol- and plug in the USB cord this will put you in downlaod mode. And use Odin to get you back to a stock rom
Currently Fusionized
Click to expand...
Click to collapse
ive had this problem for a week now, it doesnt seem to be that simple. installing new drivers doesnt work, using different usb ports dont work, going into download mode doesnt work, thats why i need someone to try it for me cause i just cant figure it out
there has to be somebody!
Have you read this post ?
studacris said:
Have you read this post ?
Click to expand...
Click to collapse
not related to my post. can anyone help me on teamviewer?
bump + op update
not sure what someone would be able to do remotely to help you with a device you hold in your hand......why havent you tried Heimdall method? ODIN sucks.
Pirateghost said:
not sure what someone would be able to do remotely to help you with a device you hold in your hand......why havent you tried Heimdall method? ODIN sucks.
Click to expand...
Click to collapse
doesnt work either cause my phone isnt recognized by the computer at all so ANYTHING usb based doesnt work and i cant get into recovery so that doesnt work either, i mean i have to be doing something wrong right? the phone cant be dead
Heimdall uses it's own driver so Jake you install that and uninstall all the others, SO that may help with the recognition issue, as the stock closed source driver can be a douche sometimes...like in your case.
studacris said:
Heimdall uses it's own driver so Jake you install that and uninstall all the others, SO that may help with the recognition issue, as the stock closed source driver can be a douche sometimes...like in your case.
Click to expand...
Click to collapse
there is nothing in the drop down menus
{
"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"
}
bump, would be great if someone could help me tomorrow night so i can use my phone in a presentation
rsx19 said:
bump, would be great if someone could help me tomorrow night so i can use my phone in a presentation
Click to expand...
Click to collapse
I've seen that error code 43 on my machine when there's a larger USB issue. Usually two things will correct that - a reboot and switching USB ports.
I would also suggest (if you haven't already) uninstalling all of the drivers you have installed - Samsung- or Heimdall-related, then reboot, then do the Heimdall again.
jmtheiss said:
I've seen that error code 43 on my machine when there's a larger USB issue. Usually two things will correct that - a reboot and switching USB ports.
I would also suggest (if you haven't already) uninstalling all of the drivers you have installed - Samsung- or Heimdall-related, then reboot, then do the Heimdall again.
Click to expand...
Click to collapse
ive tried reinstating and tried all 4 of my laptop ports and all 12 or 14 of my desktop ports. ive tried installing all the different drivers users gave me but that never helped. and as you can eee i cant even install the heimdall drivers
either both my desktop and laptop have something wrong with them or its a user error, thats why i want someone else to help me through team viewer, this thread is moving to slow for me to get anything done
I'll ask the obvious question, just to make sure - Have you tried a different cable?
jmtheiss said:
I'll ask the obvious question, just to make sure - Have you tried a different cable?
Click to expand...
Click to collapse
yup yup that i have done
Ok, I took a quick look at the videos in the OP. Two things I noticed:
- You have the phone plugged in prior to putting it into download mode. It's possible you're just keeping the plug in after putting it there (couldn't see in the video). Try putting the phone in download mode, unhook the cable, then rebooting the computer (leave the phone in DL mode), then hook it up again.
- I saw that you have an ICS build. Do any button combinations get you to recovery (V+/V-/Power, V+/Power)? If so, you might be able to flash another rom.
- You may also want to look for AdamOutler's One-click Unbrick. That might be of some use in your situation.
jmtheiss said:
Ok, I took a quick look at the videos in the OP. Two things I noticed:
- You have the phone plugged in prior to putting it into download mode. It's possible you're just keeping the plug in after putting it there (couldn't see in the video). Try putting the phone in download mode, unhook the cable, then rebooting the computer (leave the phone in DL mode), then hook it up again.
- I saw that you have an ICS build. Do any button combinations get you to recovery (V+/V-/Power, V+/Power)? If so, you might be able to flash another rom.
- You may also want to look for AdamOutler's One-click Unbrick. That might be of some use in your situation.
Click to expand...
Click to collapse
at school writing 2 papers so ill have to try these when i get home
i put the phone in download mode with vol + - while plugging in the cord but ill try the others
no none get me into recovery,
could you link me that one?
rsx19 said:
at school writing 2 papers so ill have to try these when i get home
i put the phone in download mode with vol + - while plugging in the cord but ill try the others
no none get me into recovery,
could you link me that one?
Click to expand...
Click to collapse
Ok, I looked a little more at the one click unbrick, and since you can get to download mode, it doesn't look like the right solution. So.. nevermind that one.
As far as removing the drivers, it's something of a two-step process.
Step one is to plug the phone in, let Windows see it (even if incorrectly), and then go to device manager. From there, find the phone, and uninstall it/remove drivers. Then unplug the phone.
Step two is to go to "Programs and Features" and remove any android/samsung drivers that show up there.
Once you've done that, check to make sure any folders that drivers would have been unpacked into (mine is in C:\usb_driver) has all the Samsung or Heimdall drivers removed (BE CAREFUL WHILE DOING THIS - ONLY REMOVE SAMSUNG/HEIMDALL DRIVERS IF YOU'RE 100% CERTAIN).
Then, reboot the computer, re-run Heimdall to get zadig.exe to do its thing, then connect the phone.
Also, have you considered dual-booting (or using a USB live drive) of Ubuntu? Heimdall seems to be a little happier in Linux, but you'll just need to make sure that Java installs with it.
There's also a really slim chance that if you hook the phone up in download mode, ADB might detect it enough to where you can give the "adb reboot recovery" command.
jmtheiss said:
Ok, I looked a little more at the one click unbrick, and since you can get to download mode, it doesn't look like the right solution. So.. nevermind that one.
As far as removing the drivers, it's something of a two-step process.
Step one is to plug the phone in, let Windows see it (even if incorrectly), and then go to device manager. From there, find the phone, and uninstall it/remove drivers. Then unplug the phone.
Step two is to go to "Programs and Features" and remove any android/samsung drivers that show up there.
Once you've done that, check to make sure any folders that drivers would have been unpacked into (mine is in C:\usb_driver) has all the Samsung or Heimdall drivers removed (BE CAREFUL WHILE DOING THIS - ONLY REMOVE SAMSUNG/HEIMDALL DRIVERS IF YOU'RE 100% CERTAIN).
Then, reboot the computer, re-run Heimdall to get zadig.exe to do its thing, then connect the phone.
Also, have you considered dual-booting (or using a USB live drive) of Ubuntu? Heimdall seems to be a little happier in Linux, but you'll just need to make sure that Java installs with it.
There's also a really slim chance that if you hook the phone up in download mode, ADB might detect it enough to where you can give the "adb reboot recovery" command.
Click to expand...
Click to collapse
ill also try ubuntu since i do have it on a usb drive. my paper isnt getting written well..ll sigh
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'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
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.