Database Develop

Please help...big problem....

Big problem. Suddenly my phone will not turn on. Sits at the white Galaxy S GT-I9000 screen and does not boot. When I put it into download mode and plug it into computer, its suddenly saying "USB Device Not Recognized".
What do I do? PC won't recognize it, it wont boot. can't flash it.....I'm freaking out here...

Did you flash anything to it or root it?

riwarren said:
Big problem. Suddenly my phone will not turn on. Sits at the white Galaxy S GT-I9000 screen and does not boot. When I put it into download mode and plug it into computer, its suddenly saying "USB Device Not Recognized".
What do I do? PC won't recognize it, it wont boot. can't flash it.....I'm freaking out here...
Click to expand...
Click to collapse
Hi Rick. Try to re-install samsung usb drivers. during this time, take out the battery from the phone. once finished installing the drivers, put back the battery into the phone. Go into downloading mode. Fire up odin, put in the necessary firmwares + pit files. Once done, then CONNECT your phone to the usb port of your computer.
Hope it's okay.
Edit: Let's hope that it is the computer usb drivers are corrupted. Alterntively, if you still can't do it, try it on another pc.

Nope. I was rebooting it to flash XXJPC to it, but couldnt do so because it was saying that USB message and wouldnt detect it. So I went into recovery, did a factory reset, and now it wont boot.

Another computer does the same thing *tears*

*BUMP*
Lets try a different route. I will pay a generous sum of money to anyone who offers to and does manage to fix this for me?

rick, looking at this, if your usb is not recognised, it is either the pc or the phone usb port might be damaged.
if it is a hardware issue, then use the bounty to get it fix.

I was at that same point with my vibrant. After failed attempts of getting into download mode using buttons, here's what I did.
Download and install samsung usb drivers and android sdk.
Plug into the computer and use adb to get into download mode (adb reboot download).
Then flash with odin.
Doing that worked for me when nothing else would. Try it ?
Sent from my SGH-T959 using XDA App

richan90 said:
I was at that same point with my vibrant. After failed attempts of getting into download mode using buttons, here's what I did.
Download and install samsung usb drivers and android sdk.
Plug into the computer and use adb to get into download mode (adb reboot download).
Then flash with odin.
Doing that worked for me when nothing else would. Try it ?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I can get into download mode just fine.....my pc just doesnt recognize the usb device. tried 3 differente pc's, 2 running win7 and one running xp.

Did you install usb drivers on each of the machines?
Sent from my GT-I9000 using Tapatalk

I installed the samsung USB driver executable. and I also tried to use those drivers that it installs to manually update the "unknown USB device" in device manager, but they won't take.

Try uninstalling all drivers, then stick a MicroSD in your phone before plugging it into the usb.

Assuming you have Samsung Kies in your PC, try to upgrade it at 1.5.1.10074_45.
How long do you wait the boot?? The first boot after flash is very long, wait at least 5 minutes with flashing "S".

I did not just flash anything. My phone got really hot and laggy (as I was using it while charging it via USB port) and so I rebooted phone in an attempt to resolve the lag. when I did, it would not go past the WHITE Samsung Galaxy S I9000 screen, does not get to the flashing S screen.

bump
please anyone able to help?

riwarren said:
bump
please anyone able to help?
Click to expand...
Click to collapse
if i understood you correctly, you have two separate problems:
a) your phone does not boot up
b) your phone is not recognized by any computer when plugged in
could be a coincidence, but probably is not. i'm guessing your bootloader got screwed up somehow. if it is a coincidence, it could be that your usb port on the phone is effed, or your usb cable is dead. try first using a different cable and see if your phone can be recognized by any computer. perhaps then you can go into download mode and reflash.
also, have a look at this post, might help you (although, if your usb is effed, there's not much point in trying any solution that involves your phone being connected to a computer): http://androidforums.com/780720-post3.html
EDIT: also, have your tried the obvious stuff, like pulling battery?

I ve seen many threads with the white screen problem ... it has in most cases been the drivers ... you desinstall all drivers from pc using Kies option for resinstall the drivers ... then you pull the battery off few sec (give it a min or two) then you get to download mode and you flash the beast ... dont connect your phone before launching odin or else it will not be recognized ...
for the few other people who didn't manage to fix it ... it was a hardware failure

That post you linked, is worth a try. But its for a motorola.....Where do I get my SGS bootloader to use instead?

ohh you were implying to try to use the motorola usb drivers?

bouzoubaa said:
I ve seen many threads with the white screen problem ... it has in most cases been the drivers ... you desinstall all drivers from pc using Kies option for resinstall the drivers ... then you pull the battery off few sec (give it a min or two) then you get to download mode and you flash the beast ... dont connect your phone before launching odin or else it will not be recognized ...
for the few other people who didn't manage to fix it ... it was a hardware failure
Click to expand...
Click to collapse
I never said anything about a white screen. and I am not uneducated on flashing SGS, or using Odin. Far from it. My phone was first showing USB symbol when it wasnt plugged into USB port, then phone started running really hot while charging and got really bloated like it was overheating. So I rebooted and its now force closing at the first boot animation. I can get into download mode and recovery, but will not recognize in any of the 3 computers all running different versions of windows on them, with either of my USB cables that I tried.

[Q] ODIN doesn't see my phone in download mode.

Phone is ATT captivate SGH-I897 1008
Had my phone for 4 months or so, most of the time with cognition 2.x on it. Tried to update to 3.02 yesterday, and it had an error in the middle, left me at a recovery screen of sorts, and I chose to reboot from the possible selections. It got stuck on the ATT worldcom splash screen.
I tried several things. First, I tried to boot into recovery mode (vol up+power, then release) stays on splash screen. However, in this mode, if I connect my phone via USB, an adb devices command shows as connected. From there I tried both an adb reboot recovery, and adb reboot download command. The adb reboot recovery reboots into the worldcom splash screen just like the key combo does. I can't recall what the download option did, though I think it worked.
Secondly, I realized I could reliably get the phone into download mode, so I decided I would try the download mode, and restore to stock. I found an ODIN on the seminal ODIN thread, downloaded it, and started it up. Put the phone into download mode (hold vol + and vol -, plug in the usb) and that worked fine, however, ODIN doesn't see my phone. I left the phone in this mode for a couple hours just to make sure, and tried disconnecting, and reconnecting, and initialized the procedure from the beginning several times -- no go.
So, I am stuck, and coming to the experts. Hopefully, someone has some good suggestions. I was unable to find someone in a similar predicament, so maybe I am SOL.
Thanks in advance for any help.
UPDATE:
I rebooted my laptop (windows XP) and when I plugged in my phone, it saw "new" hardware and the name of the hardware it sees is "gadget serial." This might explain, if it is not initializing the right drivers why ODIN can't see the phone. The only problem is I don't have any clue how to redirect it to see the right hardware now.
Success Update
After reading the seminal ODIN thread a bit more careful, I came across someone who had similar issues with the gadget serial device. Apparently the drivers I got (I think from the Samsung site) are not good enough to cover that aspect of use. I installed with the drivers from links on the ODIN post and my phone was recognized! As I type, I am installing back to stock.
Thanks everyone for their efforts, and I hope my experience could be useful.

Desk top or laptop, have you tried all the ports

I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App

mcord11758 said:
Desk top or laptop, have you tried all the ports
Click to expand...
Click to collapse
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)

trekie86 said:
I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I tried two differing cables, both of good quality. One was the cable that came with the phone, the other was a mini-usb cable with a micro adapter. Neither worked. I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.

jbwray said:
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)
Click to expand...
Click to collapse
Use rear usb ports on desktop. Make sure you are using original oem cord
Have you used odin before

jbwray said:
I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.
Click to expand...
Click to collapse
Sorry, didn't read your first post close enough. I'm not sure what you can do, someone suggested the battery pull method in another thread, but that was just to get their phone in Download mode. It had nothing to do with ODIN after it was in download mode. Hopefully someone will have a suggestion for you. Good luck.

I'm having a similar issue except that odin sees the phone when booted into the rom, which I find odd.
Would you be so kind as to link the drivers?

Q: Comp not recognizing hard bricked in download mode

My phone was hardbricked when i screwed up with the latest Serendipity install. It boot loops at the white AT&T world phone screen. I am unable to get it into download mode with out a jig. However, once i do have it in download mode, my computer will not recognize the phone. It keeps viewing it as an unknown device.
I dont know if this is related to it not showing up using Odin 3 one click downloader. Either way, i need to get it back to stock.
I have the drivers already, in fact ive reinstalled them once or twice trying to get this to work, any ideas?

That's not a hard brick. Search the already existing threads in the forums, of which there are many. No need to start another thread on it. Try a different USB port on your PC, make sure you're running Odin as an administrator before you put the phone in download mode and plug it into your PC.
Sent from my GT-I9000 using Tapatalk

Rhiannon224 said:
That's not a hard brick. Search the already existing threads in the forums, of which there are many. No need to start another thread on it. Try a different USB port on your PC, make sure you're running Odin as an administrator before you put the phone in download mode and plug it into your PC.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
sorry for not searching.
as for my problem. ive tried multiple ports and im running odin in admin mode. still no luck

icanhearpudding said:
sorry for not searching.
as for my problem. ive tried multiple ports and im running odin in admin mode. still no luck
Click to expand...
Click to collapse
Have you tried installing drivers and then reinstalling drivers manually from designgears thread in dev?
SIGNATURE : Life is like a box of captivates, you never know if your gps will work

so im pretty much able to get it into download mode any time i want. but i cannot get my computer to view it. No matter what USB port i use, it still says unknown/unrecognized device. I see you mentioned something about manually installing drivers, how would i do that?

Try a different PC. Although, it sounds like a driver issue. What version of windows are you on?
sent from my Gingerbread Cappy using Tapatalk from somewhere on AT&T's ****ty network.

I know others have had issues with i9000 ROMS not being recognized once their phone goes in download mode. Here is a whole thread about it.

yeah i checked through that whole thread, it wasnt any help.
My comp is 32 bit windows 7. ive tried to connect my phone to a 64 bit windows 7, and a mac, and still havnt gotten ****. Im getting really frustrated. What are my options when i simply cannot find a way to get Odin to view the phone? All it says is that my USB device has malfunctioned and it wont work.
EDIT1
okay. ive discovered that if i plug in my USB while the ATandT logo is looping, my computer will see it as an external storage device. THEN i jig it into download mode, and plug it into the same port, and it will no longer see the device as unknown, but instead calls it 'androidtest,' although it still doesnt show up in Odin3. hmmmmm could this be a lead into getting it to show up? Every other attempt ive done has ended up with it just calling it unknown device
EDIT2
Searching through the device manager shows that the phone no longer shows up under universal serial bus controllers, but instead 'libusb (WinUSB) devices', under the name Androidtest. But as i said before, still no luck getting it to show up with Odin, either the one click or the choose all the components version. Any thoughts?

icanhearpudding said:
yeah i checked through that whole thread, it wasnt any help.
My comp is 32 bit windows 7. ive tried to connect my phone to a 64 bit windows 7, and a mac, and still havnt gotten ****. Im getting really frustrated. What are my options when i simply cannot find a way to get Odin to view the phone? All it says is that my USB device has malfunctioned and it wont work.
Click to expand...
Click to collapse
It really sounds like a driver issue. Have u tried downloading I9000 drivers?

prbassplayer said:
It really sounds like a driver issue. Have u tried downloading I9000 drivers?
Click to expand...
Click to collapse
ive downloaded and uninstalled and redownloaded all sorts of different captivate drivers. it always still just said 'usb device malfunctioned.' i belive at this point, i have every driver uninstalled, hoping that windows itself would grab the right one. . ..
idea: ill reinstall captivate drivers. . . then ill do the usb while atandt is booting and THEN use the same usb port for the download mode. Without drivers, this is how i got to the 'androidtest' deal. perhaps with drivers installed, it will do something different.

icanhearpudding said:
ive downloaded and uninstalled and redownloaded all sorts of different captivate drivers. it always still just said 'usb device malfunctioned.' i belive at this point, i have every driver uninstalled, hoping that windows itself would grab the right one. . ..
idea: ill reinstall captivate drivers. . . then ill do the usb while atandt is booting and THEN use the same usb port for the download mode. Without drivers, this is how i got to the 'androidtest' deal. perhaps with drivers installed, it will do something different.
Click to expand...
Click to collapse
HOOOOOOOOOOOOOOOORAY. I did it! THis worked. I had to have the captivate drivers, installed, THEN plug it in during the at and t boot loop THEN plug it in after jigging download mode. Thanks so much for your help everybody!

[Q] Bricked Captivate -- Unique Situation?

I've flashed 6-8 ROMS on a couple different phones, so not a total noob, but I bow to the vastly superior knowledge here:
My Captivate was running CM7.1 stable from October with no further mods since. I hadn't flashed anything or really messed with the phone in awhile. I was just using the same phone in the same config I had been for 6 months.
A few days ago, CM7 started to force close all my programs. Annoying, but not a problem that rebooting wouldn't probably fix. Rebooted into bootloop (skater logo). 3 Button didn't put me into CWM Recovery, nor would any button combos get me to download mode.
Homemade a jig and got the phone into Download mode, with Odin One Click up and ready to flash to stock. Odin read the phone and I started the flash, but it hung at DO NOT TURN OFF TARGET for a couple hours. I checked on this forum to see what was next. All the previous posts just said to pull battery, re-jig, and start again.
This time, I didn't get the skater, I got the comp!phone. All button & USB combos I've read here bring me comp!phone (even the "hold until two blank screens" one). My PC won't recognize the phone now (so neither will Odin or Heimdall), even after I've reinstalled the Samsung drivers. I've read here that you can flash from the comp!phone screen, but the PC has to see your phone first, obviously.
So I guess I want to know how screwed I am. Magic tips on a easy fix would be just outstanding, too! Is the fact that I wasn't flashing or anything when it bombed interesting to anyone? Thanks in advance...

not sure it's identical but this worked for me: http://forum.xda-developers.com/showthread.php?p=15330252#post15330252

OP,
Check out the "Connection Issues..." Stickied Thread in this forum.
Sent from my SAMSUNG-SGH-I777 using xda premium

Zadig won't load drivers for Heimdall 1-click
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.

macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
If you are still stuck...
Did you actually load a full version of Heimdall? Once I used unbrick as a mini-program. Another time I had to install a full version on my computer in order to get my phone and computer to communicate (that may be the missing driver step).
I know you have probably already done so but search the threads for AdamOutler and his work with Heimdall.

If you're using windows, windows update might be installing the drivers automatically. You might want to disable this feature, uninstall the current drivers and install new ones.
You can also try another pc that doesn't have any installed drivers - just to make sure...
Sent from a Captivate using XDA

macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
Did you try manually installing the Samsung/Google usb drivers ? That's the usual culprit since stock are Samsung drivers and roms ( if its Aosp/Cyanogen) the Google drivers prime in that case.

Nearly Identical Problem
I've got the same problem with my Captivate...tried everything I've found in the forums but nothing works.
Background:
I had connection issues before trying to flash, but thought it was a driver issue with my Windows 7 machine. Which is why I had loaded the file onto the SD card when I attempted to upgrade to ICS. During the flash the phone hung and I eventually removed the plug and battery to see if I could reboot. I can get up to the Galaxy S I9000 screen, or the "Downloading..." screen, but I cannot get to the recovery menu or past the initial boot screen. My wife's captivate (same batch) IS recognized by the computer in "download mode" and in the USB transfer mode.
Attempts:
- Installed/uninstalled Kies many times
- Bought and tried a new data cable
- Installed/uninstalled the Galaxy S driver and the Captivate driver many times
- Tried Zadig, Odin, Heimdale, and Adb
- Used programs to remove USB devices and clean registry
- Installed Linux and tried within that OS
- Re-installed Windows 7
- Tried most of the above on my Windows XP system
Has anyone been successful in getting the computer to recognize a Captivate in this circumstance?

macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
if u r still facing the problem..and problem isnt solved then just clean the pin of usb connector pin of ur phone...with a thin metal pin..or something like that...
and then u r good to go...

If all else fails...
I managed to brick my Captivate trying to get MUIU off my phone and flash back to Cognition. After many frustrating hours, I contacted Josh at mobiletechvideos.com. He fixed my phone and upgraded me to ICS for $50.00. I mailed my phone to him on a Thursday and received it back the following Friday.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

Bricked and solution seeking

After sifting through tons of sites, articles, threads and suggestions on the many ways to unbrick a Samsung Captivate I am nearly ready to throw in the towel. I bricked my phone by accidentally knocking the wire out while flashing a ROM. After a few attempts to correct the problem, it only progressively got worse.
I CAN get to download mode (vol up/down + attach usb). I have the correct drivers, I've tried Odin, Heimdall was a total failure for me (the one-click solution required drivers that required administrator permissions that I, even in the Administrator account, seemed unable to provide) and I've also tried a few different drivers. I'm hesitant to use a jig because I am able to get to download mode.
When I attempt to use Odin, it sees the device, it starts everything fine and dandy, until the factoryfs.fs part. It freezes usually after one bar of progress. Sometimes I get a progress bar on the phone, sometimes I don't.
Any thoughts?

Try a different micro usb/usb cable. Use a usb port in the back of the pc...don't use a hub.
Sent from my SGH-I897 using xda premium

4-2ndtwin said:
Try a different micro usb/usb cable. Use a usb port in the back of the pc...don't use a hub.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I'm speechless... I can't believe it. That worked! I spent hours and hours trying to resolve this... Thank you so much 4-2ndtwin! Thank you!!

aravens said:
After sifting through tons of sites, articles, threads and suggestions on the many ways to unbrick a Samsung Captivate I am nearly ready to throw in the towel. I bricked my phone by accidentally knocking the wire out while flashing a ROM. After a few attempts to correct the problem, it only progressively got worse.
I CAN get to download mode (vol up/down + attach usb). I have the correct drivers, I've tried Odin, Heimdall was a total failure for me (the one-click solution required drivers that required administrator permissions that I, even in the Administrator account, seemed unable to provide) and I've also tried a few different drivers. I'm hesitant to use a jig because I am able to get to download mode.
When I attempt to use Odin, it sees the device, it starts everything fine and dandy, until the factoryfs.fs part. It freezes usually after one bar of progress. Sometimes I get a progress bar on the phone, sometimes I don't.
Any thoughts?
Click to expand...
Click to collapse
You have to select "show all" from the menu in the driver installer.
--the developer of Heimdall One-Click.