Related
So, I think I broke my captivate. No, scratch that, I KNOW I broke my captivate. I think it's just software bricked but I'm not sure. Here's what's going on:
I rooted my captivate, and installed CWM. I flashed Serendipity 2.0 and that was fine. It booted, and I downloaded ROM Manager and went to partition the SD card. It rebooted, showed the AT&T screen, and froze on a black screen with white letters that says:
"GALAXY S
GT-I9000
SAMSUNG"
Holding down any combination of the volume buttons and turning on the phone does not go into recovery. It goes to the same screen as above.
The only way (via buttons) that i can get into download mode is to pull the battery and cable, put the battery back, hold down both volume buttons, and plug in the USB. However, when in download mode, windows says: "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."
On the other hand, if I plug USB in while it's frozen at the "GALAXY S GT-I9000" screen, windows and Odin DO recognize it. When I click start in odin, it gets stuck at "File Analysis..." though.
I would really appreciate any help getting this captivate running again. What can I do here?
Desk top or lap top, have you tried different ports, different drivers. You can recovery from where you are. Where did you get the drivers from? What ports are you using
scubabuddha said:
So, I think I broke my captivate. No, scratch that, I KNOW I broke my captivate. I think it's just software bricked but I'm not sure. Here's what's going on:
I rooted my captivate, and installed CWM. I flashed Serendipity 2.0 and that was fine. It booted, and I downloaded ROM Manager and went to partition the SD card. It rebooted, showed the AT&T screen, and froze on a black screen with white letters that says:
"GALAXY S
GT-I9000
SAMSUNG"
Holding down any combination of the volume buttons and turning on the phone does not go into recovery. It goes to the same screen as above.
The only way (via buttons) that i can get into download mode is to pull the battery and cable, put the battery back, hold down both volume buttons, and plug in the USB. However, when in download mode, windows says: "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."
On the other hand, if I plug USB in while it's frozen at the "GALAXY S GT-I9000" screen, windows and Odin DO recognize it. When I click start in odin, it gets stuck at "File Analysis..." though.
I would really appreciate any help getting this captivate running again. What can I do here?
Click to expand...
Click to collapse
Are you able to Open Odin, connect USB and check if Odin recognizes ur device?
mcord11758 said:
Desk top or lap top, have you tried different ports, different drivers. You can recovery from where you are. Where did you get the drivers from? What ports are you using
Click to expand...
Click to collapse
I got the drivers from the 32-bit link here. I've tried both on a windows desktop and a macbook pro using VMWare Fusion for virtualization. I've tried all the USB ports, including the ones on the back of the tower
rickysa2000 said:
Are you able to Open Odin, connect USB and check if Odin recognizes ur device?
Click to expand...
Click to collapse
I am able to open Odin. Odin (and Windows, for that matter) only recognizes my device when it's frozen at that black screen. I attached a picture of it. It does not recognize my device when it's in download mode
Try drivers from here
http://www.samsung.com/us/support/downloads/SGH-I897ZKAATT
Do not install save files to desktop. When your phone is in dl mode and plugged into the rear port of your pc click on the error message. Direct the computer to the driver files you just downloaded. This has worked for some
mcord11758 said:
Try drivers from here
...
Do not install save files to desktop. When your phone is in dl mode and plugged into the rear port of your pc click on the error message. Direct the computer to the driver files you just downloaded. This has worked for some
Click to expand...
Click to collapse
OK, got the new drivers and saved them to my desktop.
It's windows XP, and I can't for the life of me figure out how to point XP at those drivers. It pulls up the "Hardware Update Wizard" but it won't use the files. There are 3 .inf files, which is what the wizard wants. If I try to use any of them, it says: "The specified location does not contain information about your hardware"
scubabuddha said:
On the other hand, if I plug USB in while it's frozen at the "GALAXY S GT-I9000" screen, windows and Odin DO recognize it. When I click start in odin, it gets stuck at "File Analysis..." though.
Click to expand...
Click to collapse
Ok, I don't remember if Serendipity installs with debugging enabled, but when the phone is in the state above and recognized by Windows can you send adb commands to the phone? Particulary 'adb reboot recovery'.
opcow said:
Ok, I don't remember if Serendipity installs with debugging enabled, but when the phone is in the state above and recognized by Windows can you send adb commands to the phone? Particulary 'adb reboot recovery'.
Click to expand...
Click to collapse
I don't have the android SDK installed on that computer. Give me a minute and I'll find out
So, the phone does not respond to adb. "adb devices" returns a blank line. "adb reboot recovery" returns "error: device not found." I get the same result whether it's in download mode or frozen on the GALAXY S splash screen
Device manager shows the phone as "SAMSUNG Android USB Composite Device" when it's frozen at that screen, but as "Unknown Device" when it's in download mode.
How can I force XP to use specific drivers?
Edit: I just uninstalled the drivers and let windows find them on its own. It found and installed:
Driver Provider: SAMSUNG Electronics Co., Ltd.
Driver Date: 5/12/2010
Driver Version: 5.2.0.4
Is that the right driver version?
Its the right driver if odin recognizes you
mcord11758 said:
Its the right driver if odin recognizes you
Click to expand...
Click to collapse
even though odin (and windows) doesn't recognize the phone in download mode?
scubabuddha said:
even though odin (and windows) doesn't recognize the phone in download mode?
Click to expand...
Click to collapse
No, odin needs to see your phone.
What cord are you using, is it oem
it's the cable that came with the phone.
I don't think the cable's the problem though, because both odin and windows DO recognize the phone in its frozen state... i guess i could be wrong about that
Just a shot in the dark, but if inserting the battery with USB+vol-up-down gets into download mode, how about inserting the battery while the volume buttons + power are pressed.
Do you know what bulks you are on? Located under battery, I am 1008
opcow said:
Just a shot in the dark, but if inserting the battery with USB+vol-up-down gets into download mode, how about inserting the battery while the volume buttons + power are pressed.
Click to expand...
Click to collapse
yeah, that also gets it into download mode. It doesn't change how windows reacts to it though... "Unknown Device"
mcord11758 said:
Do you know what bulks you are on? Located under battery, I am 1008
Click to expand...
Click to collapse
Right underneath the serial number? Mine's 1009... why?
I am not sure if you mentioned this, but are you opening odin prior to plugging your phone in?
Have you used odin before?
mcord11758 said:
I am not sure if you mentioned this, but are you opening odin prior to plugging your phone in?
Click to expand...
Click to collapse
yes
mcord11758 said:
Have you used odin before?
Click to expand...
Click to collapse
no
Do you have access to any other windows pc? My first experience with odin I could bout get my phone recognized. Switched to another cpu, bam. I believe you have a mac as will but I an not sure that will work even with the vm
I asked about your build because 1010 has issues with the odin one click. Did not want to see you work for hours only to find port you need another program
Hello all, I am turning to the Forums since I have spent 5 hours trying to resolve my problem.
Earlier today I installed Kies Mini on my computer in anticipation of the official AT&T Froyo. However, now my computer no longer recognizes my phone at all. It does not show up in the Device Manager, or anywhere.
I tried Uninstalling Kies Mini, Uninstalling the Drivers, Rebooting my phone. etc, etc. But Windows still will not recognize the phone as attached. It worked in the past and I would like for it to work again.
I am currently running Windows 7 64 bit. My Captivate is running Cog 3.4.
Try this:
Uninstall Kies Mini and all Drivers
Reinstall Kies Mini
Once installed turn on USB debugging on your phone and then plug it in, let it install all of the drivers.
Unplug your phone and shut it down
Once shut down activate download mode (hold up and down volume and plug in the USB) again it will install more drivers.
Once this is done unplug your phone, remove the battery and turn it back on, then restart your computer.
Uninstalled Kies Mini, and Samsung Drivers. Reboot
Installed Kies Mini.
Attached Phone to Computer. Nothing.
Also, Tried to Just boot my phone into Recovery Mode. But only boots into Clockwork Recovery. Can't Log into Stock Recovery
Update: Tried hooking up the phone to my XP machine. No Joy. XP did not recognize the device or try to install drivers.
Did you enable debugging?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes, I placed it in Debug mode. When I plug in my Phone my Title Bar Shows the USB Debugging Android indicating that USB Debugging connected, the USB icon that says Copy files to From Computer. If I click on USB, it gives me the Green Connect Android, then the Orange One. But none of my computers recognize a USB device as connected.
I have tried it with Three different cables. I'm thinking that somehow the phone is not sending some message to Windows saying "Hey, I'm connected"
Did you use the correct drivers for the phone? Can't recall of the top of my head if I can use the standard captivate drivers for windows if your on cognition..
Sent from my SAMSUNG-SGH-I897 using XDA App
I am having this exact same issue - only I updated from JH7 to Official 2.2 (for ****s n giggles) and now pc no longer recognizes phone. Went through the uninstall and reinstall and reboot.... no luck. I've never had this issue before...... ever.
I have tried almost everything i can think of. Anyone have any suggestions?
Sent from my SAMSUNG-SGH-I897 using XDA App
Not in device manager
I have what appears to be a soft brick. I was running the i9000 drivers. I was trying to install the i897. At first Odin recognized my phone and I began to download. The Odin bootloader flash failed. No my computer (Win 7 64 bit) does not even see my phone. Nothing in device manager, not even an unrecognized device.
I can get my phone into download mode. Does anyone have an idea how I can get windows to see me again?
From my experience as long as you are in download mode and have odin opened up it when you connect it, odin should find the phone no problem for you to be able to flash something new to it.
davncari said:
I have what appears to be a soft brick. I was running the i9000 drivers. I was trying to install the i897. At first Odin recognized my phone and I began to download. The Odin bootloader flash failed. No my computer (Win 7 64 bit) does not even see my phone. Nothing in device manager, not even an unrecognized device.
I can get my phone into download mode. Does anyone have an idea how I can get windows to see me again?
Click to expand...
Click to collapse
Have you rebooted the PC? Try to reinstall the drivers again. I had to reinstall the nexus s drivers but I have read some need to reinstall kies to get the drivers to work. Just keep at it. Try other USB ports. My phone wouldn't be recognized for about two weeks with trying everything. I tried new USB cables, drivers and all. Then finally it kind of worked and I went from download mode with a jig to phone!PC and then it took another reboot of the laptop and phone was able to get flashed again via the phone!PC screen. Just keep trying is all I can say.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
ok. so I recently started using a different computer, it's windows vista. when I go to download mode, and plug the phone in the computer just says "usb device not recognized". I've got the latest drivers, and tried uninstalling then reinstalling again. any ideas as to what is going on?
Sent from my SGH-I897 using XDA App
Multiple ports?
CM7
I've tried front and back usb ports,
Sent from my SGH-I897 using XDA App
Try uninstall again.
Dl usb drivers but dont install. Save them to desktop
Plug in phone
Unknown device pops up, click on message. Click install custom drivers, navigate to where you saved uninstalled drivers are. Select
This has worked for some
CM7
Ok I uninstalled any versions of the drivers, when I plugged in my phone, the computer said unknown device as usual but it is automatically installing an "unknown device" driver. When I went to select the driver manually for it, it told me that there was no need to update and it didn't give me another option.
I should probably mention that originally, the computer recognized my internal sdcard when i mounted it. Now it isn't, and it won't recognize it in any mode.
Mik3D23 said:
I should probably mention that originally, the computer recognized my internal sdcard when i mounted it. Now it isn't, and it won't recognize it in any mode.
Click to expand...
Click to collapse
what rom are you using now? does the driver you installed came from the stock eclair or froyo. I get the same message after flashing from stock to custom roms. I just plug my phone again and the pc automatically searches and installs driver from gt i900 driver. My old PC is running win xp with android sdk manager in it aside from the kies mini it has which already has the samsung drivers which supports stock roms.
definitely wrong drivers...If your computer recognize it in normal mode as in to mount internal sd card, but says unknown device in download mode than try to download USB drivers from somewhere else...
I have noticed this that drivers from samsung website doesnt support the download mode...I have faced this problem...mine would ask for gadget serial..so i use this drivers...http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Hope this helps
I'm running perception 10.4. I've tried several different download sources, and it doesn't read when I mount the sd card anymore. On my windows 7 computer it worked no matter what rom I had, and I didn't have to change drivers at all. I'll try that link and see what happens
Still won't work...
This happens to me all the time when attempting to flash back to stock. What I do is just keep doing battery pulls and switching usb ports. Eventually, it works!
OBatRFan said:
This happens to me all the time when attempting to flash back to stock. What I do is just keep doing battery pulls and switching usb ports. Eventually, it works!
Click to expand...
Click to collapse
lol How long will that usually take until it works..
I've tried pulling the battery and switching ports at least 15 times.. nothing happens. windows installs an "unknown driver" automatically, and if I choose the galaxy s drivers for it, it says the driver isn't compatible for my device. It's not even recognizing it's a phone, or a mass storage device, or any other usb device it can be.
Unknown Device
Was this ever resolved? I have the same problem. Unknown Device in Download Mode. ADB works, PC recognizes phone in normal mode.
The phone shows up in Device Manager when in normal mode. If I use ADB to reboot download, the PC immediately drops the phone and displays unknown device in device manager.
Have tried complete uninstall/reinstall of drivers including regedit. NO JOY.
Running XP SP3. Any ideas?
after upgrading to gingerbread my pc thinks it is an i9000.
try those drivers.
i have no issues though.
Been looking for a while and can't find a solution on here. I am just about bricked, I can only get the phone-exclamation point-computer logo. Tab won't go to download mode, won't do anything but show that error screen in one minute intervals. I just got this thing and rooted it, then did GB update, and now it's toast.
Help appreciated, it's only 3 days old and I don't have any more in stock in my store.
If you are on a Screen that has "phone connected to a PC", That is essenutally DOwnload mode.
What you would need to do is use Heimdall command
"heimdal close-pc-screen"
Do you have heimdall and Android SDK installed on your computer?
Sent from my SCH-I800 using XDA App
ripjaw27 said:
If you are on a Screen that has "phone connected to a PC", That is essenutally DOwnload mode.
What you would need to do is use Heimdall command
"heimdal close-pc-screen"
Do you have heimdall and Android SDK installed on your computer?
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Yes I have both installed.
I plug the tab into the computer, it doesn't even make the connect device sound. Heimdall says 'Failed to detect compatible download-mode device.'
The only way I can seem to get the image to come on the tab is when I plug it into the factory charger only.
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this
got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked
Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.
This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!
A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.