Related
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
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
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.
sorry double post
Same issue here. I've had no luck sorting it out.
Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?
ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.