[Q] Problem with usb debugging galaxy s I9001 - Galaxy S I9000 Q&A, Help & Troubleshooting

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.

Related

Need Help with ADB

ADB stopped working on my desktop suddenly (It still works on my laptop) adb devices show nothing, and adb shell brings "error: device not found."
I've uninstalled the drivers and reinstalled many times, going over the process outlined here: http://forum.xda-developers.com/showthread.php?t=532719&highlight=adb+noobs
Running KingxKxRom 2.2 (Hero rom)
I've looked on the forums for people with the same problem, but their solutions didn't work for me. Example: stopping the adb.exe process, etc
USB debugging is checked.
Device manager shows:
Android Phone:
Android Composite ADB Interface
USBDeview shows:
Android Phone: HTC Android Phone USB Device
Android Phone: USB Mass Storage Device
Android Phone: Android Composite ADB Interface
Any ideas how to fix this?
What OS are you running?
On my computer?
Windows XP
Have you tried removing your usb drivers in the device manager?
This same thing happened to me. I just uninstalled all of the usb ports, and when I reset my computer it recognized the ports, and everything seemed to work again.

PC not recognizing Captivate after Root

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.

[Q] ADB drivers?

I installed the usb drivers for my nook as per the instuctions in this guide: http://nookdevs.com/NookColor_USB_ADB#Windows_XP.2C_Vista_and_7
It seems to have worked and in device manager "ANdroid composite ADB device" shows up under Android Phone.
But when i type adb devices when my nook is plugged in, i still dont get and devices there.
Im running 64 bit Windows 7 on an Intel Core i7 machine.
I couldn't get the ADB drivers to work via those instructions either. Luckily we have people around here that are MUCH smarter than I am.
http://forum.xda-developers.com/showthread.php?t=910008&highlight=adb+driver+install
Follow the instructions and install the software from that thread, worked for me great.
I am having the same problem here. It seems like everything is installing fine. I deleted the old usb mass storage device, installed everything, but then when I try to do adb devices, I get a blank line. No serial number. I then tried adb wireless, I connected using adb connect 192.168.2.4 and it said connect it was connected. I then ran adb devices and it spit back that it was connected to that ip address but it still doesn't give me a serial number.
This is what I get:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Sorry for the multiple posts.
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.

[Q] USB Debugging/Mass Storage Mode connection to computer issue

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

Fastboot USB error: A request for the USB BOS descriptor failed

Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
SOLVED...sort of...
I used a workaround. I used a Windows 7 computer and there it worked perfect.
roel1976 said:
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
Click to expand...
Click to collapse
hi, i had same USB problem, windows7 worked for this old phone

Categories

Resources