Database Develop

[Q] Driver problems

Struggling with getting any computer to recognize my I9000. Both XP and Win7 fails to load MTP USB device. That said XP is not complaining, it loads something that seems generic, "MTP Device" along with Samsung Android USB Modem and Samsung Android USB Composite Device
MTP Device uses files wpdusb.sys and wudfrd.sys . Is this right, or should the device look for diffrent drivers and what files SHOULD it use?

On win7 it displays "Android MTP" as opposed to "I9000" the few time it used to work.
Tried the alternative drivers.
Tried the long file extensions tips.

Did you try disbaling launcher pro / launcher pro? So stock tw launcher is working? And wiping the internal sd? Had issues, but this worked first time on win7
Sent from my GT-I9000 using XDA App

TWlauncher/Launcherpro is checked from the list many days ago yes, had it working with Kies only a few days ago (granted after a lot of "tricks" and then suddenly working for no obvious reason).
Been holding off the internal sd format and factory reset. Thats my next step.

No luck. In XP it shows up as "MTP Device" under "Portable devices". Is this how its supposed to look like, or should it be recognized as "I9000"?

And finally. Trick this time was to have Kies running (win 7), also battery where taken out once (telephone locked trying it in XP). Internal SD unmounted, formated, remounter and then factory reset in "privacy".

Snuble said:
No luck. In XP it shows up as "MTP Device" under "Portable devices". Is this how its supposed to look like, or should it be recognized as "I9000"?
Click to expand...
Click to collapse
Just finally solved the same problem for Windows XP. Here the solution:
- uninstall MTP device driver
- I don't know if necessary but I did - remove from windows all related files : wpdmtp*.*
- !!! download Windows Media Player version 11. It contains updated drivers.
- install the player
- connect your device
Now it's recognized in the Device Manager as GT-I9000. And Kies immediately connects to it.

For future reference, how did you uninstall MTP device drivers?
We wont be the last to have trouble with this procedure...

while device is connected you can click right mouse button on it and choose "uninstall"

[Q] PC won't mount Nook/SD card

I don't know what happened but neither my Win7 x64 nor my Win7 x32 machines will mount my disks on the NC.
I am rooted with market access and I think it was working after I ran the "auto config script" but, not sure?
When I plug in to USB port the PC's load the drivers correctly and I see it in "adb devices" but the Nook never goes into USB MODE and no disks show in Explorer?
Any help on this before I do a full reset would be appreciated.

Try this:
http://forum.xda-developers.com/showthread.php?t=865345&highlight=usb

Thanks! moving to that thread

CM 11 and Windows 8 USB connection?

Can't seem to connect to Windows 8 through USB. It chimes and the Touchpad says connected as a media device. But I don't see it in Windows. Tried checking and unchecking MTP in storage settings and nothing.

BigB42078 said:
Can't seem to connect to Windows 8 through USB. It chimes and the Touchpad says connected as a media device. But I don't see it in Windows. Tried checking and unchecking MTP in storage settings and nothing.
Click to expand...
Click to collapse
Try this
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software.
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
The above is.courtesy of RolandDeschain79 install guide.
I've followed this and it worked for me.
Good luck and have fun.

hmmmmmm. Not showing up in portable devices?

OK it detected fine upstairs on a Win 7 machine must be WIn 8 problem, Anybody know how to make it work on Windows 8?

[Q] cant connect to pc in linux or windows

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.

Mi A2 mtp doesn't work in Linux

As the title suggests, I can not connect mtp to Linux, but it works in Windows. Other phones of mine do not have this problem under Linux. Does anyone have a solution or the same problem? I've already tried several versions of the stock rom and it also doesn't work in the pie beta either.

My A2 connected with mtp under Linux all the time. No issues.
I'd suggest turn on adb, keep the developer selections open, make the connection, then if no mtp, bring settings back up and in the usb settings section, select mtp.
It seems Linux has some built in detection's for devices, product ID's etc. Many times it results in a 'default' setting of 'charge only'. So you have to change it back after the connection.

What Linux distribution are you using? I have no problems whatsoever using Arch Linux + Nautilus inside i3wm Window manager.

AsItLies said:
My A2 connected with mtp under Linux all the time. No issues.
I'd suggest turn on adb, keep the developer selections open, make the connection, then if no mtp, bring settings back up and in the usb settings section, select mtp.
It seems Linux has some built in detection's for devices, product ID's etc. Many times it results in a 'default' setting of 'charge only'. So you have to change it back after the connection.
Click to expand...
Click to collapse
I already tried this. What I personally find the strangest thing is the file transfer via adb push / pull works but when I try in the file manager to open the phone comes the error that the device could not be mounted because of a udev error.
I tried it on 2 PC's one with Cinnamon and the other with xubuntu and it doesn't work.
My other phones (Xiaomi Mi5s and Mi A1) are working flawless on both PC's.

jigs4wkiller said:
I already tried this. What I personally find the strangest thing is the file transfer via adb push / pull works but when I try in the file manager to open the phone comes the error that the device could not be mounted because of a udev error.
I tried it on 2 PC's one with Cinnamon and the other with xubuntu and it doesn't work.
My other phones (Xiaomi Mi5s and Mi A1) are working flawless on both PC's.
Click to expand...
Click to collapse
Well, now you have a north to go.
Take a look at the DebuggingUdev wiki from Ubuntu.
Maybe it's just a missing udev rule. Execute
Code:
sudo udevadm monitor -e
After, connect your device and you should get better logs.

Ironmaniaco said:
Well, now you have a north to go.
Take a look at the DebuggingUdev wiki from Ubuntu.
Maybe it's just a missing udev rule. Execute After, connect your device and you should get better logs.
Click to expand...
Click to collapse
If I understand the log correctly, it tries the device instead of mtp with ptp to mount. But to be honest, I do not really understand what's there stand.
Here the output from the command:
UDEV [388.551499] bind /devices/pci0000:00/0000:00:15.0/usb1/1-2 (usb)
ACTION=bind
BUSNUM=001
COLORD_DEVICE=1
COLORD_KIND=camera
DEVNAME=/dev/bus/usb/001/011
DEVNUM=011
DEVPATH=/devices/pci0000:00/0000:00:15.0/usb1/1-2
DEVTYPE=usb_device
DRIVER=usb
GPHOTO2_DRIVER=PTP
ID_BUS=usb
ID_FOR_SEAT=usb-pci-0000_00_15_0-usb-0_2
ID_GPHOTO2=1
ID_MEDIA_PLAYER=1
ID_MODEL=SDM660-MTP__SN:07081BDD
ID_MODEL_ENC=SDM660-MTP\x20_SN:07081BDD
ID_MODEL_ID=ff48
ID_PATH=pci-0000:00:15.0-usb-0:2
ID_PATH_TAG=pci-0000_00_15_0-usb-0_2
ID_REVISION=0404
ID_SERIAL=Xiaomi_SDM660-MTP__SN:07081BDD_10fa792
ID_SERIAL_SHORT=10fa792
ID_USB_INTERFACES=:ffff00:ff4201:
ID_VENDOR=Xiaomi
ID_VENDOR_ENC=Xiaomi
ID_VENDOR_ID=2717
MAJOR=189
MINOR=10
PRODUCT=2717/ff48/404
SEQNUM=5817
SUBSYSTEM=usb
TAGS=:uaccess:seat:
TYPE=0/0/0
USEC_INITIALIZED=388518849
adb_user=yes