I bricked my phone one day and found myself without a computer that could use the MSM Download Tool. I kept getting connection errors or
the good 'ol Param Preload error on Windows 11. I eventually found a way to use MSM reliably using a virtual machine and a copy of Windows 7/8.
This isn't a guide on how to use MSM. There are plenty of guides that go into depth as to how to use this.
Assuming that you have the VM all set up and the appropriate drivers installed; do the following:
1. Make sure the device is in EDL mode and connected via USB and virtual machine first. (Side note: You may have to set your VM to capture the device every time it's connected.)
2. Start up MSM, status should say COM(whatever) connected.
3. Reset the device by holding the Power Off and Vol Up button.
4. While it's resetting, hold down Vol Down + Vol Up + Power until device shows it's connected again.
5. Press start.
chrisyroid said:
I bricked my phone one day and found myself without a computer that could use the MSM Download Tool. I kept getting connection errors or
the good 'ol Param Preload error on Windows 11. I eventually found a way to use MSM reliably using a virtual machine and a copy of Windows 7/8.
This isn't a guide on how to use MSM. There are plenty of guides that go into depth as to how to use this.
Assuming that you have the VM all set up and the appropriate drivers installed; do the following:
1. Make sure the device is in EDL mode and connected via USB and virtual machine first. (Side note: You may have to set your VM to capture the device every time it's connected.)
2. Start up MSM, status should say COM(whatever) connected.
3. Reset the device by holding the Power Off and Vol Up button.
4. While it's resetting, hold down Vol Down + Vol Up + Power until device shows it's connected again.
5. Press start.
Click to expand...
Click to collapse
How did you got edl to recognize your device? I am stuck there. Adb and fastboot works fine though. Oh, btw I use linux as main so that might be the issue
I'm interested as well. Tried with Parallel Desktop on MacOS but couldn't recognize the device.
If you want to try a native solution that works on Windows 10 (and has not been tested on Windows 11) you can try this.
It does not use the Qualcomm virtual com port drivers, it uses the generic WinUsb Zadig drivers.
So there's no mucking about with Com27.
http://www.temblast.com/edl.htm
I'd be grateful for somebody to confirm correct operation in Windows 11.
Related
Okay im running windows xp, and i have all those drivers installed...
http://www.userdrivers.com/PDA-Mobil...dows-XP-Vista/
and http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
so what am i missing to get my vibrant to be recognised by odin in download mode????
What are you running currently?
simply honey 3.6..... gingerbread
By chance did you forget to enable usb debugging?
idk, i flashed from a 2.2.1 rom to simply honey 3.6 through rom manager, but i did have it enabled through before i flashed for sure.... And usb debugging is not required for download mode as (i think) thats a whole different thing???
It needs to be enabled to use Odin. Also, sometimes for Odin to see my phone I have to unplug my phone and open Odin a few times before I finally get Odin to see my phone. It's very finicky for me, always has been
Sent from my SGH-T959 using XDA Premium App
helikido said:
Okay im running windows xp, and i have all those drivers installed...
http://www.userdrivers.com/PDA-Mobil...dows-XP-Vista/
and http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
so what am i missing to get my vibrant to be recognised by odin in download mode????
Click to expand...
Click to collapse
Go into windows device manager. Make sure that your computer is even seeing the device and that it has recognized the drivers for it. If it recognizes it, try rebooting computer then restart the process. Also make sure your phone is actually in DOWNLOAD mode. Not Recovery mode.
If you do not know the difference between the two, let us now and we'll assist further.
Happy hacking!
I use to always have trouble with Odin..then one day someone mentioned they always right clicked on Odin and chose "run as Administrator", I have never done that because I figured I was the administrator....but once I did it, never had a problem since.
Another problem I run into (well not anymore) is the USB port I plugged into. If I was on a hub or something it wouldn't work. If I plug right into my computer it works properly.
I also use adb commands to get into download and recovery when I'm Odin'ing. It also let's me know if my phone is detected by the OS.
#adb devices (should show your phone listed)
#adb reboot download (reboots your phone into download mode)
#adb reboot recovery (reboots your phone into recovery mode)
You'll need the SDK installed for adb to work.
Since I started doing these things, I have had ZERO problems with Odin and flashing my phone.
ay.. usb debuging was enabled before i flashed... now if my turn turns on it goee onto a bootloop... so everytime i cinnect my phone to the computer it says device not recognised. ohh and one thing to mention is that my computer doesnt have a highspeed usb port
Three button to download mode - power+vol up+vol down and see if you can get it into download mode then plug in usb (1.0 should work), then run odin...
otherwise i think you're looking at trying to make one of those jigs or replacing your phone...
try
1. Start Odin
2. Plug USB cable into pc
3. Power off the Phone.
3. Pull the Battery.
5. Plug USB cable into Phone.
6. Press and Hold: Volume UP + Volume DOWN + Power, all at the same time.
7. Re-insert the battery.
8. The phone will power now, when the screen starts a cycle of going to a BLACK screen, release ONLY the POWER button.
9. When you see the download icon release the volume buttons,
10. Odin back to stock by putting the PIT file into the appropriate area and the .tar in the PDA area.
Afaik the three button combo is for
Recovery mode. Follow the above directions up to the power button part. While holding both volume buttons, it should go directly into download mode when the usb us plugged in
Try removing all drivers then reinstall if xp doesn't pick it up
Beware of angry gingerbread man
power off phone
pull out battery
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
Enjoy and also make sure u have the proper samsung drivers
Install samsung kies mini. It gives you the correct drivers. I once installed those and it messed it up. So install kies mini.
adamcooks said:
Afaik the three button combo is for
Recovery mode. Follow the above directions up to the power button part. While holding both volume buttons, it should go directly into download mode when the usb us plugged in
Try removing all drivers then reinstall if xp doesn't pick it up
Beware of angry gingerbread man
Click to expand...
Click to collapse
This is what happens when you do it a certain way for a long time, you forget certain things...lol
try another computer?
goodluck
So I have bought a L7 and when I have it the phone is not working, the seller doesnt want to take my money back so I need help with this :S!
No appears to do anything when connected to charger
No led
No vibrates
No emergency mode
When I connect it to my PC it recognizes it as QHSUSB_DLOAD, but neither KDZ or LG update program recognize it :S!!
Someone know how to reinstall OS I think is software issue but I dont know how fix it
Thanks!
Try following the instruction I got from a website.
What is 'qhsusb_dolad' ?It is the situation when you can't boot into your phone,recovery mode and any other visible interface. When you connected your phone to the PC, the LED will flash and your PC will show that they were searching for the drivers needed(win7/8) but they couldn't find .......If it is commom for you to remove the battery when the phone did not shutdown completely or when you ran into 'No-Response' , as time goes by ,it will be inevitable that you come across the 'QHSUSB_DLOAD' situation .
But from now on ,you needn't worry about that for I have found a way out.
Tools needed:
Hardware: A PC running XP and higher (win7/8 recommended) and your usb cable
Software : MIflash and MIAssistent and a certain mi update rom(It is a *.exe file---fastboot file)
Steps :
1. Install the first two softwares described above(Run as administrator) in your PC (You need to disable the enforcement of digital signature while on win8 in the advanced startup (press 7 or F7)
2.Boot into fastboot mode(you just need to do with your two buttons and usually you cann't see the interface for your screen just won't show in this situation) before connecting to PC
3.Connect you MI2/S to your PC via the usb cable and the pc will recongnise it in the device manager panel(if not, update its driver in the unknown device---qhsusb_dload)
4.Open the miflash and click fresh to load your phone's serial number
5.Flash the update rom(the self-extracted-to folder) into your phone and reboot .
Explanations:
Miassistant contains the 'qhsusb_dload' driver for any phone and it enables the PC(Miflash) to recongnise your CPU serial which is the key part of updating by wire.
Tips:
Try this with your other phone, I believe it will work ,too.
I'm supposed to just copy/paste the link.. but the protocol won't let me since I still don't have more than 10 posts. I just want to help. Try this
The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.
its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.
Background:
OnePlus 8 Pro IN2020
Original OS version is OxygenOS 12 Android 12
How my phone turned into brick:
Try flashboot unsupported TWRP and other third party recoveries.
After a few tries, eventually causing my phone turning into a brick
What my error looks like:
Not able to boot into system
Showing "the current image(boot/recovery) have been destroyed"
Can access fastboot and detect by system
Method:
Follow the steps in How to UNBRICK OnePlus 8 or 8 Pro! by Max Lee (Thank you my man, Max, for this video)
Pitfalls in 2022 (IMPORTANT before UNBRICK!):A USB 2.0 and Third-party USB cable are highly recommendedI was unable to boot into Quadcomm EDL mode while using the stock cable and USB 3.0 connector. Pressing the correct Volumn Up & Volumn Down and Power Button will boot the phone to fastboot in no time.
I successfully got into the EDL mode and finished flashing the phone using my iPad Pro Type-C charging cable which is an USB 2.0 one.
Use a newer version of the Qualcomm driver if you find the device not correctly detectedUse Qualcomm HS-USB QDLoader 9008 driver.
A new Quadcomm driver will help you flash your device correctly the first time!!!
Windows 11 won't let you install unsigned driver by default, but there's a way round
Press Shift key while click Reboot in start menu to enter Advanced Options
Click Trouble shoot in Advanced Options
Click Advanced options, click Startup Settings then click Restart
After restart press 7 when required
If your computer won't restart, just unplug your phone temporarily
after this your device will detect by your computer correctly.
Pressing buttons requires special timing and preconditions and a few more tries
To fully power off your phone, press Volume up and Power button for 10 seconds. Release immediately after the screen turns black.
Your phone is in the state of powered off even your screen displaying error message or charging animation, just make sure it's not in fastboot, recovery or booting animations.
Connect your phone to your computer before press Volume up and down and Power Button all at the same time to enter EDL mode.
Prepare yourself with Device Manager and MSM tool open and configured correctly before your phone enter EDL mode. There's a about 10 second window for you to start flashing.
Fail amid your MSM flash process:Don't panic if you see error message saying you didn't finish flashing
You can flash it anytime just make sure checking all the things above and enter EDL mode
Check these things：
Check your Windows can install the unsigned driver correctly
Check Device Manger in Control Panel if your device is correctly detected as a COM device as Qualcomm HS-USB QDLoader 9008 or something like this
Use administrator privilege to open the MSM software
Check your cable connection is stable or not.
Finally, thanks Dr.E (Max Lee) for your help. Without your video instructions, I won't revive my phone. It spares my pain to ask my dad for money for a new phone I don't actually need.
Hope everyone could find some helpful information in this post and flash your phone like a champ.
A even better way to enter EDL mode is power off and unplug your device, and after hold volume up and down at the same time, plug in the USB 2.0 cable to the computer. It works every time!!
i cant join rdl mode always restarting fastboot mode