Database Users

Unable to see phone when in download mode

I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I was having a similar issue with my MBpro, nothing would recognize my phone. Tried it on another comp and bingo. I think stuff is just finicky with USB ports. Lame-o.

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure so when u see its charging for 30 sec. Then put the cellphone into download mode... and that should work

maldito.boss said:
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure let it charge for 30 sec and the put it into load mode... that should work
Click to expand...
Click to collapse
Yea...this post made my brain hurt...and of course didn't change anything...but..thanks?

Here's another piece of info that may help nail down the problem...
Odin is able to see the phone if I boot into Clockwork recovery mode but because clockwork is up the phone can't receive a flash but Odin does see the phone with no problem. It just still won't see the phone when booted into download mode.

ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I use windows7 64 too. I encountered tons of problems when trying to flash my epic. first my computer doesn't recognize my phone in download mode. after i wipe out all the drivers and reinstall them. finally i get my computer recognize it under download mode, but Odin froze every time during the flash.
Finally, i tried on another desktop computer with windows XP. Everything went perfectly. So maybe you should try that too.

I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?

Pirate-M.Lifnen said:
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Click to expand...
Click to collapse
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.

Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
I had the same problem, I couldn't connect it to 3 of my pc's. 2 xp's and one windows 7. Turned out the port on the phone it self was broken, had to take it sprint and get it replaced.

Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.

i had an extremely similar issue as to what you are having. I have 3 win 7 machines and 1 xp, none worked. I went to a friends house he has 2 win 7s and an xp also didnt work. I did a general search and found all kinds of crap. One dude something about using his chicks blackberry usb cord and suddenly it worked on any and all of the machines it had previously not worked. so at the time im reading this on my chicks laptop which has a damn blackberry cord attached to it chargin her evo(go figure) ... anyway u didnt need the whole story but i have nothing to do right now.
Point is everyone says try different cords, i say try the damn blackberry cord if you happen to have one or a friend that has one.

Benjamin Dobell said:
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
Click to expand...
Click to collapse
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?

ldartez said:
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
Click to expand...
Click to collapse
In this particular instance Apple haven't done anything wrong at all, both their hardware and software is fine. The issue is that Samsung are distributing secondary bootloaders that aren't complaint with the USB specifications.
Whilst that is annoying, the good news for you is that you can simply install Linux (Ubuntu etc.) or Windows on your Macbook and you'll be able to flash just fine.

Windows doesn't recognize my phone

Alright, so I've been trying to figure out why Windows doesn't recognize my phone in Download Mode (attempting to get EB13) and I've now realized it doesn't even detect it in Mass Storage mode (Windows tells me a USB device was not recognized when I connect it)
Any ideas?
I'm stumped here...
Note: tried it on both x86 and x64 versions of Windows.

Download the latest drivers. As for download mode areu trying to use odin?
Sent from my EB13 Samsung Epic

Check the "teeth" in where the cable connects to your phone. Some people have had them bend out of place.

MedicStuder said:
Download the latest drivers. As for download mode areu trying to use odin?
Sent from my EB13 Samsung Epic
Click to expand...
Click to collapse
Just downloaded them onto my x86 machine, and even when connecting my phone in normal mode (when it's fully on) it tells me device not recognized.
So at this point, I'm not even focusing on Odin, because nothing seems to be able to see my phone over USB.
I've even tried a different cable, but to no avail.
And yeah, I tried the Samsung EB13 download and I tried Odin. Neither could see it (just like Windows).
Other then this, it works perfectly fine. So it's not like I bricked it or anything.

Having the same issue. Tried multiple computers, reinstalling the drivers, and multiple USB cables. No luck. Makes things tough trying to get EB 13.

tanmack33 said:
Having the same issue. Tried multiple computers, reinstalling the drivers, and multiple USB cables. No luck. Makes things tough trying to get EB 13.
Click to expand...
Click to collapse
Alright, so I'm not alone here...
Windows actually seems to have just recognized it while powered up fully (and is currently installing the drivers).
Figure I'll let that finish and then try Download Mode again.
And then hope for the best I guess.
EDIT: It seems to be working now.
The Samsung EB13 utility is doing its thing in Download Mode.
Crossing my fingers it finishes without incident.

Uninstall drivers then install then reboot pc and phone then try. If reboot didn't solve the problem reboot phone and try again.
Epic 4g

Well, it seemed to be working.
But now my phone has a green screen and the EB13 utility is stuck on "FACTORYFS" and the progress bar says "Elapsed Time: 18sec.... 4%"
I really hope this didn't brick my Epic

anyone know where the drivers are for the epic

shud be somewhere on this site.. or on samsungs website.. its easy to just google..

computer can't find phone in fastboot mode

Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon

Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net

Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.

What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).

kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.

Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!

Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.

i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you

mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.

glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?

also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on

http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode

mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App

which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?

mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.

Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers

noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?

deleted!!!!!!!!!!

I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.

Okay, so put it in fastboot mode and try to run a fastboot devices real quick.

Odin not recognising phone when in download mode

Ive been trying to root my phone using cf root but when i put my phone into download mode and connect it to the pc odin doesnt recognise it. However, when i reboot my galaxy s one of the bars at the top of odin turns yellow and in the message box it says "Added!!". Ive tried this on 2 different pc's and its still not working.
When i first connected the usb cable to the pc, a message came up saying if i wanted to install the software from a cd, but i dont have one so i couldnt. Then it said that the software couldnt be installed properly. How do i install it properly?

seeraj15 said:
Ive been trying to root my phone using cf root but when i put my phone into download mode and connect it to the pc odin doesnt recognise it. However, when i reboot my galaxy s one of the bars at the top of odin turns yellow and in the message box it says "Added!!". Ive tried this on 2 different pc's and its still not working.
When i first connected the usb cable to the pc, a message came up saying if i wanted to install the software from a cd, but i dont have one so i couldnt. Then it said that the software couldnt be installed properly. How do i install it properly?
Click to expand...
Click to collapse
Download the drivers from my signature & install them, make sure you haven't connected the phone while doing so. Restart windows, connect the phone. Windows will install the required drivers, & you are ready to go.

Do i install from setup.exe. Its asking for a password.

Ive extracted it all but i cannot set up.

My windows is 32bit. Can someone please tell me where i can the samsung usb 32 bit drivers please?
Ive managed to get the 32 bit drivers and it says that samsung usb modem and the samsung usb android composite device are ready to use. However, it says that no driver was found for the ethernet controller.

[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