Related
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.
Okay a little backstory:
I was on an early version of CM9 but as i am selling the phone i decided to put a more stable version of it on there and downloaded CM7 -stable.
I flashed this in CWM and it worked fine.
I gave it a quick test and noticed all the google apps were missing, most importantly the market. So i booted into recovery and realised i had forgotten to put the zip on the SD card.
I then went into mounts and mounted USB, nothing happened...
From that point onwards the phone would not talk to the PC. even if i booted up into the phone, it would just show it as charging. I could not find any options in the menus for USB options.
After some extensive reading, i tried a few things, none of them had worked. I found a post mentioning some kernels have issues with USB, so i downloaded the recommended one and flashed it in CWM.
After rebooting, CWM was now orange and not blue and the option to flash from external card has gone.
I have also done some digging and there is a good posibility that the kernal that i flashed was for the GT I9000 (which is the american one, right?)
So as it is at the moment:-
I can get into CWM.
I can get into download mode through the 3 button combo.
I can get into download mode using home made jig.
I can boot the phone, but it boot loops.
I can not get the phone to be detected on the pc.
Things i have checked:
Cable will connect other phones.
Tried different cable to be sure.
Phone used to be detected, but downloaded drivers through kies again to be sure.
Closed Kies using task manager.
Nothing is coming up in network connections in device manager when phone is connected.
I'm out of ideas now, so £10 PayPal donation for anyone that comes up with the solution to fix it
If i can get it detected, i can use Odin to flash what i want.
Sounds like a drivers problem. You may need the 'Google driver' developer.android.com/sdk/win-usb.html
When I had bootloops when I first installed CM9 I used heimdall to flash a the stock CM9 kernel. This gave me back CWM.
heimdall flash --kernel 'kernel.zip'
In the commandline.
Thanks for that,
I already had the Google USB drivers from when i installed the SDK to make some apps.
So i then gave Heimdall a try (Graphical Version), it seemed to suffer the same problem.
Reporting "Failed to detect compatible download-mode device."
I seem to remember the GUI saying I didn't have the correct drivers and it downloaded them for me.
The other thing worth a try is changing the USB port and reinstalling the correct drivers on that port.
I've not seen anything like that, it has not asked me for any drivers.
It's like the phone is not connected at all. nothing will detect it, i have even tried it on another PC.
Sorry, I'm not sure what you mean by installing on a port.
Well sometimes changing USB port will allow you to install new drivers. Although if you've tried it in another computer and it doesn't work then changing port may not help.
Does the phone appear in device manager when it's connected and in download mode?
Nope. Not coming up at all in the device manager. It didn't when it was booting fine. And it still doesn't in download mode. :-( I'm thinking the usb connector on the phone might be faulty.
But it was working up until trying to mount the USB in CWM
Sent from my GT-N7000 using XDA App
I don't suppose you have access to a Linux PC do you? Windows USB drivers are notoriously sucky. If you could plug it into a Linux PC and type 'lsusb' at a command line, that would at least show you that the device is really there.
I think I have a spare pc kicking around that I could use. I'll give it a go when I get home tonight.
Sent from my GT-N7000 using XDA App
Remove all the drivers completely from device manager for Samsung, then install fresh drivers and connect the cable when in download mode, hopefully it will recognize it
Are you sure the connector is clean? e.g. maybe there's dust in it.
I had that problem once, the connector was full of fabric fibers from some coat's pocket I had the phone in.
Suggestion 1 (Linux): I installed ubuntu, did not detected anything to even install any drivers. Detected my new phone fine.
Suggestion 2 (Uninstall drivers from device manager): I could not find any drivers named with the name Samsung in there.
Suggestion 3 (Clean port): I have some compressed air that i sprayed inside, it does look pretty clean and will continue to charge but still not connection on the pc.
To install the drivers for heimdall you have to run zdiag from inside the driver folder. Had to do this earlier on, the phone the other appeared as something other than Samsung composite usb or whatever it normally says
I tried this, and it displayed 9 devices after selecting show all. I seemed to recognise all of the items in the menu.
To be sure, I then disconnected the phone and re ran it to see if one of the items were missing, but it was the same number.
I too had problem with the usb connection on my i9000, and I was pretty sure my usb connector on the phone is somewhat damaged since it sometimes can only go to charging mode without being detected by my pc as a usb device. CWM instal is fine but ODIN can only detect the phone without able to flash the rom to the phone. The flashing will always stuck at the message "Setting Up Connection", I waited for 15 minutes and the flashing will eventually died. I retry the odin flash for 40 to 50 times and eventually the flashing will go through one time. Tried heidmall command line and the result is the same.
I have problem with Odin in the past. I bought a new laptop, running Win7 64 bit. Installed Samsung Kies to install the correct USB drivers for the phone. Then made sure that Kies wasn't running in the background. So tried using Odin. Odin was detecting the phone, but it was hanging at initialising connection. Odin was working fine on my old laptop running Win7 32bit. Long story short, I was having a few issues with my new laptop, reinstalled Win7 64bit, now Odin is working fine, have flashed the phone a few times using the new computer.
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
lovedonator said:
After flashing which kernel you started facing this problem?
Wipe ur phone,re-flash CM7(flash the nightly 181,it's completely stable),uninstall KIES,uninstall old usb drivers,install these usb drivers http://forum.xda-developers.com/showthread.php?t=961956 ,check that USB storage mode is set as Mass Storage and then connect your phone. Also try enabling/disabling USB debugging
Click to expand...
Click to collapse
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Xyis said:
The point at which i could no longer mount the USB was when i selected "mount usb" from CWM. I later installed a new kernal which downgraded my CWM, removing the install from external SD option.
So I cant flash a re-flash a rom unless i can it onto the phone which without the USB working is near impossible.
Click to expand...
Click to collapse
You can directly download the ROM on your internal sd using dolphin browser or opera mobile
I can't do that either as the phone is currently boot looping.
Sent from my GT-N7000 using XDA App
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
Hello, my Samsung Galaxy S GT-i9003 was working fine yesterday, but now it stays stuck on the samsung logo when booting. I'm trying to flash it, the thing is, I can't get my computer to detect my phone, it shows up as an unkown device. I tried a factory reboot etc.. didn't work, and I can't even use it as a mass storage device since it's bricked. I used all the newest drivers, the newest version of kies but it still doesn't work.
I'm on windows 7/64 bit btw.
Thank you in advance.
Are you able to enter into download mode? (hold volume down + home + power)
If not, You can try to make (or buy) a JIG which will force download mode and you can flash a new ROM with Odin
Regards
I can enter in download mode, the thing is, my computer detects my phone as an "unknown device" and it isn't recognised by Odin either, which means I can't flash it.
are you sure the drivers are installed correctly? I recently had problems with the USB cable.. try another one and if possible, other PC....
I installed many times the drivers, using kies or without kies, the result is just the same, maybe it's the cable.
Try to change the cable and the USB port. Last week I tried to update a Motorola Atrix and the same thing happened, unknown device. Then I changed the USB Cable and voila... worked !
Let me know if it works....
Regards
just wondering if you have resolved this yet ? I have same problem tried all usb drivers i can find , 5 different computers , jig , odin still not detect and windows show unknown device detected.
Sent from my Dell Streak using XDA
Guys I had the same problem. After trying many pc, drivers, cables combinations I came to a conclusion that the usb port on the phone itself must be damaged. After taking a close look, I saw some of the gold contacts damaged/missing.. That might be the case with your phone aswell. Look at the pins and if yo usee some visual damage you know what the problem is. Even if you dont see it, it still might be a problem.
Hey there,
Just today I decided to download a new ROM for my LG Optimus 2x. I tried to install the ParanoidAndroid CM10 ROM via the CWM Recovery. (place files on SD card, reboot in recovery, wipe, install) But I accidentaly installed the version for the new bootloader instead of the old bootloader which I still have. So needless to say, that didn't work and I was stuck with a boot loop, the phone didn't get passed the LG animation screen. So I figured out that I needed the older bootloader version. I downloaded it, put it on my SD and tried to boot into CWM Recovery... nothing. It did not catch the Power + Volume-down combination and instead just continues its regular boot-loop with the LG animation.
I had flashed a ROM with nvflash before, so I installed the drivers (I tried this step on 2 PC's mind you) and put the phone in the desired state (battery out, usb cable connected, press volume-up and volume-down for a short while). But to my surprise, my computer did not recognise the phone. It doesn't even see it connected or anything! I did install the LG Mobile drivers beforehand, if that makes any difference, but nothing changed the situation, I couldn't get my PC to recognise my phone in NVFlash mode.
Okay. I'm a though guy so I figured I could still try and use the Smartflash method. So I install the drivers necessary, hook my phone up with the battery removed, hold the volume down-key and I see the "Upgrading software" screen, good! But again my computer did not recognise my phone just a little bit. It doesn't show up in the device manager and neither do I have an option to install additional drivers.
I'm baffled by all this since I did not think one ****-up would brick(?) my phone this bad. Is there any way that I could just get it working again? For now I really don't care what ROM version I have to install, I just want it functional again
Thanks!
Andorenan said:
Hey there,
It doesn't show up in the device manager and neither do I have an option to install additional drivers.
Thanks!
Click to expand...
Click to collapse
LG O2X is 99.99999999% is un brickable.....have you tried the AIOT kit by Sprosk or the Nvflash stuff by Progmaq....
In addition tho this: partitions changed normally with nvflash method.....is it done through CWM?
SREEPRAJAY said:
LG O2X is 99.99999999% is un brickable.....have you tried the AIOT kit by Sprosk or the Nvflash stuff by Progmaq....
In addition tho this: partitions changed normally with nvflash method.....is it done through CWM?
Click to expand...
Click to collapse
I did. I tried both the nvflash stuff and the smartflash method. But somehow my computer does not recognise the device while it's plugged in. It doesn't even see that something is plugged in.
I'm sorry but I'm not sure what you mean with the partitions changing through CWM. Could you please elaborate on that?
Andorenan said:
I did. I tried both the nvflash stuff and the smartflash method. But somehow my computer does not recognise the device while it's plugged in. It doesn't even see that something is plugged in.
I'm sorry but I'm not sure what you mean with the partitions changing through CWM. Could you please elaborate on that?
Click to expand...
Click to collapse
the old and new bootloader are different in partition layout and the size of partitions....this can be done through only the nvflash method, or kdz method.
look at the AIOT tool kit thread opening post for more information.....
The ROMs which are based on the old boot loaders are not compatible with the new bootloader.....vice versa
-have you tried to change your USB cable?
-tried changing the USB ports?
-using win8, then you need to do it differently.....so check that too
-try using ports directly connected to motherboard....not through any USB hubs
Hope this helps you
Andorenan said:
I had flashed a ROM with nvflash before, so I installed the drivers (I tried this step on 2 PC's mind you) and put the phone in the desired state (battery out, usb cable connected, press volume-up and volume-down for a short while). But to my surprise, my computer did not recognise the phone. It doesn't even see it connected or anything!.
Click to expand...
Click to collapse
Make sure you are pressing and holding both volume keys while you are plugging the USB cable in. Pressing them after plugging the cable in will not put the phone into APX mode.
Sent from my LG-P990 using Tapatalk 2