Database Info

Charge won't connect to computer

I have uninstalled and reinstalled the drivers several times and I have made sure my computer is set to automatically download drives for new devices. But despite all this I can not get my computer to recognize my Droid Charge. Every time my computer tries to instal the drivers for the phone it either stops with out doing any thing or it ends with an error. It keeps saying that the device has malfunctioned and Windows can't recognize it.
I'm also getting a code 10 error - Windows says the device cannot start

Try the basic troubleshooting methods..
Try different cables, Try different computers/laptop, Try different drivers (i realized i had the wrong drivers the whole time)
Eliminate possible causes of the problem.

bomix said:
Try the basic troubleshooting methods..
Try different cables, Try different computers/laptop, Try different drivers (i realized i had the wrong drivers the whole time)
Eliminate possible causes of the problem.
Click to expand...
Click to collapse
I tried two different cables and three different USB ports and two different drivers and none of that helped.
I don't know what the problem was but it finally fixed itself. I booted into download mode and inserted the USB cable for about the 9000th time and it suddenly started working again.

No it started doing the same thing this morning. I tried connecting my Captivate & it's doing the same thing but my mp3 player connects fine. I think I might reinstall Windows and see if that fixes the problem.

I think you can only use the OEM USB to Odin the phone. I would also suggest using a USB port that is in the back of the computer. Make sure it's one of the motherboard mounted ones. Not an add on USB.
Also make sure the phone is in USB debugging mode. [settings/applications/development--usb debugging]
Also try installing the drivers as admin.
Sometimes virus scanner might interfere with software operation. Although I've never had to do this, try temporarily disabling it when trying to install drivers. Also when running Odin.

But what about download mode? Does Odin see it on a com port if you connect it?
Besides drivers did you install everything like the samsung utility? Did you check in device manager of windows to see if an error there appears and maybe a fix? Ive heard someone else post about this. Did you disable usb debug on the phone and make sure mass storage is set?
Instead of doing your computer it would be easier to do a factory reset on your phone or revert back to stock in recovery.
http://forum.xda-developers.com/showpost.php?p=14381603&postcount=1
OK and one last thing to try as it is easier than re installing windows. Wipe cache and dalvik, fix permissions. re start.
I have used different cables besides the samsung and it worked. Also my phone isnt working all of a sudden. In cwm I went and mounted system . wiped all cache, fixed permission. Re started and it worked.
LOL after typing all this I see it does it for all devices. Could you try and restore windows to a previous date that worked then re install the drivers and see if it works?

emtee_skull said:
I think you can only use the OEM USB to Odin the phone. I would also suggest using a USB port that is in the back of the computer. Make sure it's one of the motherboard mounted ones. Not an add on USB.
Also make sure the phone is in USB debugging mode. [settings/applications/development--usb debugging]
Also try installing the drivers as admin.
Sometimes virus scanner might interfere with software operation. Although I've never had to do this, try temporarily disabling it when trying to install drivers. Also when running Odin.
Click to expand...
Click to collapse
It was just working a few days ago and I was using a different cable.
I tried using one of the back USB ports and it worked once & then when I tried it again it had quit working again.
The phone's in USB debugging mode.
I install everything in administrator mode
I'm running without a virus scan app right now (Yeah I know I know...)
I was using Bit Defender but the piece of garbage deleted a few files that were completely harmless like one of the files to root the Epic 4G.
The one really strange thing is that every time I plug the phone into the computer it has to look for ,download ,and reinstall the drivers for the phone and most of the time it fails with an error. I'm not sure why it's doing this but I really think that's where the problem is. If I unplug my printer or scanner Windows doesn't have to reinstall the drivers for them when I plug them back in.
My Cowon mp3 player works perfectly fine using the same ports so the ports are working...

blueis300 said:
But what about download mode? Does Odin see it on a com port if you connect it?
Nope it isn't seen in download mode either
Besides drivers did you install everything like the samsung utility?
Haven't tried that yet
Did you check in device manager of windows to see if an error there appears and maybe a fix?
There's an exclamation mark in the device manager. I've tried telling it to update the drivers from there but Windows keeps telling me that the best driver is already installed
Ive heard someone else post about this. Did you disable usb debug on the phone and make sure mass storage is set?
I've tried disabling and re-enabling USB debugging more times than I can remember
Instead of doing your computer it would be easier to do a factory reset on your phone or revert back to stock in recovery.
http://forum.xda-developers.com/showpost.php?p=14381603&postcount=1
OK and one last thing to try as it is easier than re installing windows. Wipe cache and dalvik, fix permissions. re start.
I have used different cables besides the samsung and it worked. Also my phone isnt working all of a sudden. In cwm I went and mounted system . wiped all cache, fixed permission. Re started and it worked.
I'll try that one & report back
LOL after typing all this I see it does it for all devices. Could you try and restore windows to a previous date that worked then re install the drivers and see if it works?
I would rather not.That would delete some of the apps I just installed. If I'm gonna have to reinstall them any way I'd might as well just reinstall Windows. Also I might revert to a time when I still had Bit Defender installed and I would rather reinstall Windows than deal with that over paranoid crapware
Click to expand...
Click to collapse
***********************************************************

Tried wiping dalvic cache battery stats & fixed permissions and it still isn't working. I tried uninstalling it in device manager and scanned for hardware changes and it still comes up as an "unknown device"
The only thing that happened was that Microsoft offered to install the software for my mouse that I had never bothered to install.
I'm really thinking that there is some kind of problem with my Windows installation.Something has become corrupted or broken.
I don't usually use Windows update and I have been using it extensively this go-round. Maybe Windows Update broke something (Wouldn't be the first time!).

Ok one last idea and might be crazy. Didnt see if you tried it or not. Cant hurt but do phone as factory reset of the phone and wipe the cache. Could something be installed on the phone that makes it not be recognized for some reason? Really just throwing stuff out there as it is easier than installing windows again.
That or like you said virus scanner or something is screwing with your computer.

blueis300 said:
Ok one last idea and might be crazy. Didnt see if you tried it or not. Cant hurt but do phone as factory reset of the phone and wipe the cache. Could something be installed on the phone that makes it not be recognized for some reason? Really just throwing stuff out there as it is easier than installing windows again.
That or like you said virus scanner or something is screwing with your computer.
Click to expand...
Click to collapse
Nah didn't work. Looks like I get to reinstall Windows. I hope that fixes whatever it is cause I am fresh out of ideas.

Yeah all out of ideas. Atleast everybody tried.

This is almost related. I spent ten days trying to figure out how to make the AllShare app work. I finally got it done, but I tinkered with my computer so much that when I finished, I could no longer restore to a previous version.
I had never used that feature on this computer, but I figured that I could undo all the crap I did and start over from the day I started tinkering if I restored to the day I started. Every restore point failed!
I went to this forum and asked why restore did not work.
http://www.sevenforums.com/
I was ready, like you, to re-install Windows, but someone walked me through how to get it working correctly. I thought the phone was complicated, but Windows 7 leaves the phone in the dust when it comes to complicated.
Maybe if you go on there and post a thread about a device not being recognized you will get some help. Tons of good tutorials there too.

chrstdvd said:
This is almost related. I spent ten days trying to figure out how to make the AllShare app work. I finally got it done, but I tinkered with my computer so much that when I finished, I could no longer restore to a previous version.
I had never used that feature on this computer, but I figured that I could undo all the crap I did and start over from the day I started tinkering if I restored to the day I started. Every restore point failed!
I went to this forum and asked why restore did not work.
http://www.sevenforums.com/
I was ready, like you, to re-install Windows, but someone walked me through how to get it working correctly. I thought the phone was complicated, but Windows 7 leaves the phone in the dust when it comes to complicated.
Maybe if you go on there and post a thread about a device not being recognized you will get some help. Tons of good tutorials there too.
Click to expand...
Click to collapse
I feel the exact opposite. Most of Windows 7 is like an open book to me.In fact this is the first problem I've ever had with Windows 7 that I couldn't fix on my own
{
"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"
}
Dealing with rooting & installing ROMs on the Charge on the other hand had me shaking in my boots. Nowhere nearly as easy or simple as it is on the Epic 4G!

can anyone help me fix my phone with team viewer?

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

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are 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"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

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

Need help with hard bricked oneplus 8T

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.