Hello, I have tried everything, to connect my pc with USB ... Downloaded SDK packages and drivers Sammsung but nothing.
Enabled and disabled debug mode.
Basically I see it as a removable disk but can not open it, green bar load at the top but nothing! Sometimes the icon of the disk (H) is transparent.
Please help me :-(
I'm running on windows 7 32b
I hate to ask this, but just to get the obvious out of the way, you have the phone in mass storage mode and mounted, right?
Related
I installed the Samsung USB drivers on my Win 7 64-bit laptop. I have ADB installed, and have used it for other devices, no problem. I can still use it to connect to my Color Nook.
I kill-server; start-server, and look for devices - nothing. But I can see the USB installer and those other few files on the phone, and I can see everything on the sdcard.
Any ideas? I'm going crazy here.
Do you have USB debugging on?
Sent from my SCH-I510 using XDA App
I had this problem as well.
First see if you have the "SAMSUNG usb driver" installed in control panel programs.
If not, take off usb debug and connect phone to computer. Then you should get a "install verizon software" option once you plug it in. Install software .. Then, enable "usb debuging" try it again, if that doesn't work .. remove verizon software, not usb drivers. This is basically what i did, and it started working
Bought this Galaxy S USED yesterday
I cant get it to connect to my pc
i have done the following.
-installed and reinstalled Kies several times
-Installed and reinstalled drivers several times
-Tried 4 different usb cables
-Tried in USB debugging mode
My phone connects to the pc and then i get a message that my phone is not recognized (windows error 43)
The phone does charge . I have tried all of the options like Samsung Kies , Mass storage , Media player
Nothing seems to work when i select media player option the mpt application starts to crash , i have read on forums that if the mtp crashes i can just select mass storage mode but when i select mass storage mode my pc says device not recognized
When i checked the Build info it says on Kernel Version 2.6.29 [email protected] #4
Firmware version is 2.1-update-1
Build number is Eclair.XWJM2
Please help me with this , i thought maybe there if i flash everything but in order to flash it i need to connect it to my pc which is becoming impossible
have you installed the usb drivers for it? What windows you running?
installed drivers several times but it doesnt seem to help
windows 7 32 bit
You can try using a program called usbdeview. Google it and download it. It shows you all of the drivers installed on your computer. Delete all of the drivers affiliated with your phone. Make sure USB Debugging is checked and connect your phone and allow it to install the drivers automatically. It might work, either way, worth a try.
Hi, I'm having an extremly annoyning issue with my S8530. I can't seem to make Windows XP SP3 32-bit recognize properly my phone. I have install all the drivers I could find (old, new, from official site, from the undergorund of the internet) and it still gets stuck on detectic USB Serial Port giving just the message that something went wrong and it can't install driver (from auto-detecting devices from Windows). It did install Composit and Modem parts of the drivers but it allways stuck at that part no matter what driver I pre-install, how many restart I do to the PC, how many USB ports I keep chainging, how many USB cables I swap, how many restart I give to the phone. I'm starting going bananananananananananananananananananas.
Any ideeas are greatly apriciated.
Respect Ovidiu
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Renate NST said:
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Click to expand...
Click to collapse
ADB over USB so I can make Kies recognize my phone, wich won't work in Mass Storage. And it should be plug and play (after installing Kies wich installs the drivers or by just intalling the drivers alone). I don't have other machines to trie with Windows 7 (wich allways worked before) and my current PC barelly handles 5 open tabs of Chrome so no Windows 7 options here.
Plug your phone into the Windows box.
Go to Device Manager and find under Properties the VID/PID.
Check the INF file for the ADB driver and see if your IDs are in there.
If not, make a section like all the other sections with your VID/PID in it.
Install the driver.
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all
BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.
follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",