Database Users

ODIN not recognizing phone

I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit

PC Not Recognizing Vibrant in Download Mode
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.

theorginazation said:
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
Click to expand...
Click to collapse
What version of Odin were you using 1.0 or 1.3?
ckalima said:
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
Click to expand...
Click to collapse
It's the Mac....sounds like you've done everything correctly. do you have the option for Parallels?

Download mode uses a different usb driver. If you are running in a vm you need to set the vm app to pass that usb device thru to the guest os.. i use odin in virtualbox on linux just fine. I haven't tried it on osx though. There's also an app in development in the i9000 dev forum that runs natively on osx.

@shinybuddha unfortunately parallels is not an option, but I could likely hunt down a PC
@ttabbal thanks for the tip, I've been suspicious of the drivers. Currently I have version 5.2.0.5 installed, and when connecting the Vibrant in download mode, a "Generic Serial Device" appears, but fails to connect.
Unfortunately the device exhibits the same behavior on the Mac side, and isn't being recognized in Download Mode, at least not by "adb devices".
Is there a specific driver I should install in the virtual XP os? Or could you provide a link to the osx app?

I think I need to find a PC. After scouring the forums it appears there has been no successful Odin use on a Mac via VM.
forum.xda-developers.com/showpost.php?p=7854560&postcount=12
Also discovered this interesting bit from the Heimdall developer:
After some serious investigation and a bit low-level debugging it appears as though there is very little I can do to correct the GT-I9000's lack of USB specification compliance when in download mode. When in download mode the GT-I9000 is using an embedded Gadget Serial driver and not the one provided by the linux kernel (zImage). As such I have made Samsung aware of the issue although I don't know if they will resolve it or how long it will take.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=755265&highlight=heimdall&page=16

Found a Windows Vista 64-bit installation and followed the directions on the following thread:
forum.xda-developers.com/showthread.php?t=803492
My Vibrant is back! Done in 30 minutes, after spending 3 days trying to get it to work via VM on a Mac. Sometimes iCan't.

Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.

Aerankas said:
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Click to expand...
Click to collapse
What drivers did you "point" too. Im having the same issue as you, except in my device manager is says "Gadget Serial." Either way, I need my PC to recognize my phone in download mode so please help!

I had the same proble. It showed Gadget serial in device manager. I uninstalled all other samsung and keis related drivers and installed 5.2.0.4 and it worked out fine. You can download them from here. Good luck.
http://forum.xda-developers.com/showthread.php?t=728929

omg thanks
ya, the other drivers were screwed somehow, switched to these and bam... odin sees the vibrant. Thanks in bunches, lifesaver move there

[Q] How to update drivers to Kindle Fire?????

So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.

Manually install the drivers by selecting them from the list (don't tell Windows to automatically search for them).

TheDoctor1177 said:
So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.
Click to expand...
Click to collapse
Here is the exact way to re-install the drivers again if you did not do so already...
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
You should be good now!!
Click that thanks if I helped ya
Big thanks to Jcase for Burrito Root

[Q] Windows doesn't recognize my A500 through usb

Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks

SolomonAiel said:
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
What state are you connecting it in (recovery, fastboot, normal boot)?

Moborobo test program

Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.

SolomonAiel said:
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
Click to expand...
Click to collapse
tick the usb debugging

and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.

SolomonAiel said:
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
Click to expand...
Click to collapse
Moborobo, download the program and try it. Ami has worked with me many android devices
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
Moborobo, download the program and try it. to me has run many android devices. sorry for my English

Your computer isn't detecting it at all, or is there an error while trying to identify it? Make sure you have the proper drivers for your device on your computer.

It's an error identifying it. I do have the correct drivers the a500 drivers from either the rooting guide or the Acer website neither has worked.

Moborobo does not work with the a500. I tried it and it still says to connect my device. which it is but it's just unrecognized.

If you have installed the driver correctly, AND you had administrator rights when you installed, should be no reason why you can't get the PC to recognize the device.
First, I would advise using a good USB cable. It's been known in the past, that some folks try to use a printer cable, and sometimes it doesn't work. If changing cables doesn't work, then do the following
1. In Device Manager, try loading the drivers manually. You should be able to have it search the windows system for the drivers. If it doesn't find it, then windows is being stupid. Try installing it manually (ignore the warning it may not be compatible,.....)
2. If that doesn't work, then you can use the Google USB drivers
http://www.redmondpie.com/android-u...r-samsung-htc-asus-sony-lg-and-other-devices/
Generally, we install the Android SDK first;
http://developer.android.com/sdk/index.html
And again, have Device manager look to that directory and manually select.
Either way, this should get you up and running.
And one more thing, turn on USB Debugging in your tablet's system properties.
MD

I've tried that. Didn't seem to work as windows would still not recognize the a500. And the usb debugging has been on since the beginning.

Okay i've gotten windows to the point of being able to install the drivers from the device manager but there is no clear option to choose. Here are the choices:
acer android communications port
acer android modem
acer hs-usb android diag
acer hs-usb diagnostics
acer composite adb interface
acer fastboot interface
acer picasso usb boot-recovery driver (google driver)
android bootloader interface (google driver)
So any suggestions cause I've tried installing the adb interface, fastboot interface and the android bootloader interface and haven't gotten any good results.
Thanks

Did you try a second PC? Sometimes a machine can get wonky if you've been using for years. Using a second machine or reinstalling Windows freshly would greatly increase the chances of detection.

Yep tried about 3 machines.

SolomonAiel said:
Yep tried about 3 machines.
Click to expand...
Click to collapse
I'm having the same issue with a bricked A500 I bought on ebay
Windows just recognizes it as an MTP USB device and fails to install the drivers
I have another A500 that comes up fine as an A500 on the same PC.

Try disabling the USB debugging in developer options I have the same issue with my Win 7 x64 system

Stuck on boot, can't access download mode, recovery crashes

I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".

I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.

Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.

no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.

FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.

ADB Drivers not working Windows FIX

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.