Related
Hi,
I have rooted my Captivate and now I cant get the device to be recognized in windows 7 (64-bit)
I have tried installing the "SGH-i897_Captivate_USB_Drivers_5_02_0_2" drivers for Win 7 (64-bit); enabled USB debugging on the phone and also selected USB Connected menu to copy files from/to the computer. The PC is able to recognize that a USB device is plugged in but detects it as a Unknown device.
When I manually attempt to install the drivers from device manager, it detects the device as for "Samsung Android USB Composite Device" but ends up saying that the device cannot be started (Code 10).
I have also tried plugging it into a different USB port just to check off a problem with the port.
Appreciate any pointers regarding this.
Thanks
Issue exists with WinXP
Update: I just tried the same on my WinXP (32bit) laptop and still the same issue. This is driving me nuts!
Check the port on your phone and make sure your cable is fully seated. I had an issue once with mine doing the same thing but it was just my cable getting caught on the little slide protector.
Sent from my SAMSUNG-SGH-I897 using XDA App
I did move it to a different port and also as I mentioned above tried it on a different PC. Both have the same problem.
Have you tried the galaxyS drivers?
Grr I cant put links in here for the wiki where its locked.
I installed the "usb_drivers_GalaxyS_x64" drivers and plugged in the phone. It recognized the device correctly and I am able to see the phone in Explorer. I didnt have to enable USB debugging as well.
Thanks for help.
Glad it worked. Watch out for the keys program as well. It we over write the drivers with ones that dont work.
Hey guys,
For some reason, my Windows 7 32bit laptop is not recognizing the Galaxy tab at all when in download mode. I have installed kies (which incidentally also doesn't recognize the tab), and installed the individual drivers, but cannot get my computer to even see the Tab.
When the Tab is in normal mode (debugging turned off), I can mount the Tab as a drive and it has no problems.
Has anybody else run into this issue? The Tab is not showing up in the device manager at all. I do have root, and my end desire is to connect with Heimdall, and continue to get the error message "Failed to detect compatible device."
Any help would be greatly appreciated.
Seth
Download and install drivers for your tab. Samsung website should have them, if not they shouldn't be too hard to find.
drivers
Hi,
Already tried that. Kies doesn't recognize the device at all (with USB debugging active and not active both), and the Device Manager doesn't show anything either. When I plug the tab in, it recognizes that it is connected, but mounting the SD card as a drive doesn't do anything either.
The worst part about it is that I'm not sure that I can even revert to stock without being able to get Heimdall working. I've searched a ton, and it seems to be the key to just about everything. Any other ideas?
Seth
have you tried to install the drivers that come with Heimdall? I've had to force install those a couple times to get my Tab recognized in download mode.
Heimdall drivers
pvtjoker42,
Can you explain a little about what you mean? I am running Heimdall 1.1.1 have done the following:
1. Browse from the main folder to the "Drivers" folder and run zadig as an Administrator.
2. Click on "Options" and select "List all devices"
3. Click on the dropdown menu and search for anything that might be related to Samsung Galaxy Tab or Android of which there are none.
Is there a different way to force the install of the Heimdall drivers that I'm unaware of?
Thanks for your help,
Seth
when you drop down the list of devices what all is listed? I've had it show up as just a serial device before, with no mention of samsung/tab/galaxy etc..
Devices
Cisco VT Camera II (Interface 0)
Cisco Microphone (VT Camera II) (Interface 2)
USB Receiver (Interface 0)
USB Receiver (Interface 1)
USB-Serial Controller D
Fingerprint Sensor
Optical Drive Controller
TOSHIBA Web Camera (Interface 0)
USB Multimedia Audio Device (Interface 0)
USB Multimedia Audio Device (Interface 3)
Those same entries can be found in Device Manager>Universal Serial Bus controllers even on first boot if the Tab is not connected. Even after connecting the Tab, this list does not change.
Thanks again for your help!
Seth
have you tried uninstalling everything related to the tab? Kies, the specific drivers etc, then trying the Heimdall drivers?
So all the devices listed above are there when the Tab isn't even plugged in? Odd.. I would have suggested trying it for the USB-Serial Controller D, but if it's there without the Tab plugged in it sound like a different system device.
Don't suppose you have access to a different pc to try it on? see if it even notices the Tab being plugged in and tries to install drivers..
Yeah, I have other computers to try. Tried plugging it in yesterday to a different computer (same brand and model) with no change. Computer didn't recognize the device at all and/or try to install drivers.
Usually when an unknown device is plugged into a computer, the computer registers that it's there - the Device Manager shows an "Unknown Device" somewhere in the list, but this isn't the case with this device. Not sure what happened, but it appears as though I goofed up the USB somehow in the rooting process or the port itself went bad.
I'll try other computers and write back.
Thanks again,
Seth
I've tried three different computers with the same outcome. They do not register the device at all, and I cannot mount the SD card to the computer. I'm definitely at a bit of a loss at this point. Without USB, I'm not sure how else to make this happen. Ideas?
Seth
Just to double check with hemidall ur opening the drivers folder and running zadig.exe in there going to options>list all devices
Yes, that is correct. I'm opening the Heimdall 1.1.1 folder, opening the drivers folder, and running zadig. Nothing pops up at all and nothing shows up in the device manager.
I cannot mount the SD card to my computer, but the Tab recognizes it when I plug it into the computer's USB port. That's as far as I can get, however, as the computer does not see the Tab at all.
Have you tried 'fix permisions' in recovery mode - usually under the advanced option?
Sent from my GT-P1000 using XDA App
There is no "Fix permissions" in this recovery mode. Tried to fix permissions from cwr (which only went through 2 lines), but it doesn't seem to make any difference. Still force closes Gallery when I try to mount the SD card. Also force closes gallery when I try to open gallery.
This is very strange. It continues to tell me that there is an update available. I might go ahead and take it to see if it takes me back to stock. I would be okay with this as long as I had USB connectivity again and could root.
Any other thoughts?
Seth
P.S. Tried to take the update, but it gets about 1/3 of the way through the install and fails.
Any other ideas on how to flash without Heimdall?
Seth, what about trying Odin3 and its drivers?
Sent from my GT-P1000 using XDA App
I'll look around and find Odin3 and give it a shot. I'm concerned that because my computer doesn't recognize it as a connected USB device, that no program will see it either. That said, it's worth the shot and I appreciate the suggestion.
Do you know whether I can use the same files for Odin that I would use with Heimdall? Do they need to be packaged differently?
Thanks in advance,
Seth
If you have GSM based tab you can try flashing Team Overcome's Kratos ROM (I had no issues with download mode following their excellent ROM flashing instruction here http://p1000.teamovercome.net/?page_id=64 ) which involves download mode + using Odin, which displayed that it's connected to a tab through a serial port emulation. At least you can confirm if your tab's download mode is working. I'm using Win 7 Home Premium 64 btw.
I downloaded Odin 3, but without knowing if I am able to flash a package designed for Heimdall, I'm not sure what Odin 3 would tell me. Thoughts? Can I use Odin3 to transfer one of the Heimdall-specific ROMs to the Tab?
I had this same problem some weeks back. I had to use the drivers that came with Heimdall, and most importantly, in order to get it to recognize in download mode, I had to install them while in download mode and plugged in.
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
wintel_mac said:
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
Click to expand...
Click to collapse
Hello,
I tried in both usb modes on Galaxy S+.
1) Mode when Galaxy S+ was in mass storage mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found 2 mass storage:
*Disk drives
- SAMSUNG GT-I9001 Card USB device
- SAMSUNG GT-I9001 Card USB device
2) Mode when Galaxy S+ was in Kies mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found:
*Modems
- SAMSUNG Android USB Modem
*Universal Serial Bus Controllers
- SAMSUNG Android USB Composite Device
So it seems that still adb drivers doesn't work for GT-I9001.
Kind regards,
Berislav
And USB Debugging is enabled on the phone? Settings - Applications Development - USB Debugging
It works fine for me on both XXKPS and XXKPU.
Hi,
thanks for support, but it seems I'm special case
I have 2.3.6 XXKPH version, maybe that can be the cause of problem.
I'm left without idea. I tried reinstallation of all drivers on my PS but nothing is working.
Never the less my friend have galaxy s plus with firmware 2.3.5 XXKPG (this is originally installed on phone when you buy it in Croatia) and have same problem.
Is it possible that someone who don't have problem test this versions of firmware for debugging?
KR,
Berislav
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Bad news
Plysovej_Kaktus said:
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Click to expand...
Click to collapse
I have some bad news about this. I tried another gt-i9001 and it was perfectly detected without doing anything special ( XXKPH ). Visually, this device differs from non working model by missing caption "with Google TM" on the backside and added sticker "DIGITAL BY QUALCOMM" on the top side between jack connector and usb connector. Below battery, both has same information:
MODEL: GT-I9001
SSN: -I9001GSMH
RATED: 3.7 V; 1000 mA
FCC ID: A3LGTI9001
MADE BY SAMSUNG
Non working device has note R176 on sdcard slot, properly working one has G140 there.
... so it seems, we are ****ed. This is something hardware-based.
Same problem here
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
Hello, I have a same problem, I ve opened back case and the number on sd card slot reads 512S. Could this really be the hardware issue?
I ve bought my phone in Serbia.
BR
Dragan
Hello
I have similar problem but I found that my computer see ”Samsung Android Composite ADB Interface” in device manager when phone is power off. So command ”adb devices” finds my device. But when I power my phone on, at the moment when Samsung logo is shown, my device manager detects change of hardware reloads and ADB interface is missing. It is the same behavior on other computers with Win 7 x64 and Ubuntu 32bit.
At Windows I tried both Google drivers from SDK and Samsung KIES which detects ADB as I wrote. By the way KIES normally detects my phone when the device is on. I have USB Debugging mode enabled, but it seems it doesn't work. I have i9001 European distribution and I'm using stock rom I9001XXKPK, before I was using I9001XXKI2 but the problem was the same.
Have you got any ideas what to do? Where is the problem? Is there any command to force enable USB debugging through ADB?
Thanks for advices.
Hello folks,
I'm facing this "please insert a disk" issue when connecting my Note to computer via USB Debugging mode / Mass Storage Mode.
I'll let screenshots in the attachment explain itself. #1 shows the screenshot of devices menu when the phone is plugged into the computer in DEBUG mode; #2 shows the screen after I've clicked "connect USB storage" from the drop-down list of the phone; #3 shows what happens when I try to open one of the two "removable disks".
MTP mode works fine, as well as Kies connection. As I finally started exploring the potential of Android platform, I realized that MTP and Kies connection are the most useless connection options for me, and I'd rather leave it in debug mode all day. So has anybody experienced this issue, or had any suggestion on the solution?
As always, many thanks in advance, and many thanks button clicks afterward!
p.s.,
Desktop OS: Win7 Pro X64 SP1
Note: 2.3.6 Stock LB1 Open Germany Firmware, CF rooted LB1 kernel.
Also, I should have all the latest official device driver from Samsung, as I have the latest version of Kies installed (and I discovered a driver folder under Kies' installed location). I'm not so sure about adb driver, but I was able to find the Note to be listed under devices by typing "adb devices". So.. I don't know where could've gone wrong.
Help anyone?
This really sounds weird... I was facing problems of the Galaxy Note not being detected on several Windows7 32/64-Bit SP1 computers as well but this was gone after I installed SAMSUNG_USB_Driver_for_Mobile_Phones.
You are right - from all that i know all required drivers should be available when KIES is installed on your system. Whatis even more strange is that your device seems to be detected as two partitions are available and are displayed in Explorer...
So I would test the following:
- check if your device manager lists any unknown devices
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
- check all available USB ports and see if this solves the problem
- try another USB cable
- make sure your (external) SD card is formatted with a Windows compatible file-system e.g. FAT32
Hope this is helpful and helps solving your problem.
Thanks for your reply!
My device manager basically listed all the drivers/devices associated with the phone:
My Device manager shows devices:
Samsung Android Composite ADB interface
Android UMS Composite USB device (x2)
SAMSUNG Android USB Modem
USB Mass Storage Device
USB Mass Storage Device (Android)
I've attached the screenshot when all the drivers being installed when the phone is firstly connected to the computer. Also in the device manager, everything shows "this device is working properly"
I then decided to test with another Note of my friend's (On the same computer). Her Note has no SD card in it, and is completely stock ROM non-rooted LA4 Open Germany firmware. The same thing happened.
One thing worth mentioning: Yesterday, this worked only for once. When I initially encountered this issue, I restarted my computer, and boom, my phone was connected in Debugging mode! However, once disconnected, and I tried to connect it to the computer again, this issue came back. And afterward, no matter how I restart my computer, the phone won't get connected.
I also tried all USB port (USB 2.0 and 3.0), three different cables (2 of them are Samsung OEMs) and failed to address the issue.
I'm nearly exhausted but I will never give up, as this is my only computer and my only phone (haha), and without solving this issue, I'm never gonna be able to view the phone as a USB storage and easily transfer the file from my computer to the phone.
I'm going to try the last thing that I haven't done from the list you posted:
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
I believe that I can keep the driver folder in the Kies' folder, as I believe those are the newest Samsung driver, given that the Kies was the latest release version.
So far, I can only conclude that this issue is not related to specific phone but the Windows 7.
And thank you for your help btotaku!
If anyone has any insight into this issue, please help me. Thumbs up for you!
BTW, I was able to extract both SAMSUNG_USB_Driver_for_Mobile_Phones.exe from under Kies' installation path under Program Files x86 folder, and an uncompressed folder of all kinds of drivers for Samsung device, called "USB Drivers".
And looks like I was wrong. The newest version of SAMSUNG_USB_Driver_for_Mobile_Phones I had was 1.4.8. While the driver that came with the newest Kies was 1.4.103
I'll post back soon
Reinstal Windows on your PC bro.
Problem fixed.
is that your internal memory or the sd card?
Same thing happens either with SD card in the phone or not
avetny said:
Reinstal Windows on your PC bro.
Problem fixed.
Click to expand...
Click to collapse
That's the last thing I would do
hello guys can you help me coz i cant connect my lg optimus 2x to my pc
when i connect my o2x is charging but my pc cant recognize it
i tried reinstalling drivers, change usb cable, change my OS from win7 to xp, flash stock rom ( cant flash because my pc cant recognize my o2x so i cant start flashing), use nvflash (my pc cant detect apx device)
brymarti said:
hello guys can you help me coz i cant connect my lg optimus 2x to my pc
when i connect my o2x is charging but my pc cant recognize it
i tried reinstalling drivers, change usb cable, change my OS from win7 to xp, flash stock rom ( cant flash because my pc cant recognize my o2x so i cant start flashing), use nvflash (my pc cant detect apx device)
Click to expand...
Click to collapse
please dont use any USB hubs...connect it to the USB port on the motherboard side....normally on the rear side for the Desk tops.....on the laptop all ports are directly connected normally...
secondly, what is your config? ROM?Kernel?please state your current configuration which can allow others to understand the situation.
Thanks
yeah i dont use usb hub i connect it directly i tried it on my laptop but its not working
my o2x dont say that usb debugging is connected it only charge
im on stock GB now 2.3.4 v20g
Don't want to hijack this thread, just got the same problem. (Not a complete noob here, rooted lots of different devices)
Bought a used 2x today. Froyo 2.2.2 german stock on it.
It just doesn't show the prompt that USB is connected
Tried:
- LG Mobile Driver from version 2.x.x up to 3.7.2
- on Win7 32 bit, Win7 64bit, Win XP 32 bit on various USB ports
- LG PC Suite obviously doesn't connect too
- checked/unchecked USB debugging, USB mass storage and all the obvious settings
- tried different cables
Would be really great if someone experienced could point us in the right direction.
EDIT:
After lots and lots of google I found out about a menu when dialing: 1809#*990#
With these options available:
CP Image Download
FET Disable
FET Enable
AP UART
CP UART
AP USB
CP USB
CP UART gave me at least a life sign once by saying that Windows wasn't able to recognize the device.
Is this issue really unsolvable?
Sorry for the bump, but I got some update.
when dialing the above mentioned 1809#*990# in the Port menu, switching from default AP USB to AP/CP UART gave me life signs.
After switching to AP UART I linked the Unknown device driver to lgusbdiag.inf located in C:/ProgramFiles(x86)/LG United Mobile Driver.
Suddenly it started installing it and is now recognized as: LGE Platform Android USB Device.
Once disconnected I lose USB again, I'm able to recreate the first steps though even in default AP USB mode by now.
The only thing I need USB for is for flashing a custom recovery but the only thing I don't have is ADB somehow : / Clockwork telling me: device not found.
Any help on this one?
any idea guys about my problem?
Have you tried my method?
After manually installing drivers with CP UART on, switching back to default permanently enabled access with default AP USB settings as well.
i tried that but it only charge
theres a weird thing in my cp when i switch to cp uart my o2x says it charging even i dont connect it to my pc or charge it
Ap uart - p990 / p999
I have LG P999. rooted and cyanogen.
None of the special DTMF dialing # codes is not working (also code changed from 990 to 999) (i sow some other in another posts)
is anybody know a way to change to AP UART by software (with eclipse...)
or with a special cable?
i need to use AP UART - meaning to have a serial com in AP(app).
Thanks,
Tamir
guys,
Have you tried to install MyPhone Explorer and try the same....it can connect your device via wifi,USB or Bluetooth....so some way should work....
any Android version above Froyo(included) should work....I use this always...one of very useful and bug free apps.
Try it