MTP issue after UE40 update - Onetouch Idol 3 Q&A, Help & Troubleshooting

I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?

What app/method are you using to access it as a mtp device?
KashRaman said:
I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?
Click to expand...
Click to collapse

KashRaman said:
I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?
Click to expand...
Click to collapse
Did you try with Windows ? Personnaly, I can't get any android device recognized with Ubuntu (latest version ) and any of its variants (Lubuntu, Kubuntu, Xubuntu) when using MTP mode. I do think there is a missing driver or something like. UMS will work, but not avaible on our idol 3. PTP works also, but so so...
Fortunately adb works like a charm with Ubuntu.

famewolf said:
What app/method are you using to access it as a mtp device?
Click to expand...
Click to collapse
I'm connected to the device thru USB. tried mounting thru Nautilus. It used to work before the update.
frankee207 said:
Did you try with Windows ? Personnaly, I can't get any android device recognized with Ubuntu (latest version ) and any of its variants (Lubuntu, Kubuntu, Xubuntu) when using MTP mode. I do think there is a missing driver or something like. UMS will work, but not avaible on our idol 3. PTP works also, but so so...
Fortunately adb works like a charm with Ubuntu.
Click to expand...
Click to collapse
Same machine is picking up my other devices (S3/ Nexus 4) using MTP. I will try in windows and mac and let know how it goes...

That's kind of weird, I'm using Linux Mint 17.2 and it works with no issues. Though oddly, my SD Card works in Android and mounts via MTP, but TWRP can't see it at all

linux:~$ mtp-detect | grep idVendor
Device 0 (VID=1bbb and PID=af2b) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
libusb_open() failed!: No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0

Related

[Q] MTP File Transfer Not Working

Hi All,
I have a One plus one & using Windows 7 64bit
Since the last few days i have lost USB Transfer between my device and windows and cant transfer anything.
I enabled PTP and checked ADB is working showing my device in the command prompt and fast boot is also detecting my device on the command prompt.
But whenever i enable MTP to transfer files between my PC & Device, it detects my device as MTP USB Device but is unable to install any driver and i get the prompt as Driver installation failed.
Could someone please advise a workaround.
PS: Running stock rooted 44S
Thanks
I would try to uninstall drivers on win7, then connect OPO to pc and see what happens.
You can uninstall drivers on device manager in win7.
Kurtsi said:
I would try to uninstall drivers on win7, then connect OPO to pc and see what happens.
You can uninstall drivers on device manager in win7.
Click to expand...
Click to collapse
Have done that multiple times, and again installed ADB & Fastboot Drivers which are working fine, but MTP is not working and Windows fails do install MTP drivers, thus i am unable to access the USB storage
Have you tried with another pc?

[Q] [CM11] Can't find my Moto G via USB, ADB, Fastboot

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

Adb devices show blank after Twrp wipe

I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!

USB debugging not working properly (on Ubuntu)

Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).
Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!
Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk
drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?
spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.
File transfer and fastboot don't work on my Ubuntu either.
spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked
I have same problem with Windows 10 64Bit.
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
I have solved my problem. I have install Windows 10 new and now all working.
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.

My redmi note 5 pro is not at all detected by my system

windows 10 is showing
Unknown USB Device (Device Descriptor Request Failed ) in device manager​when I connect windows prompts this message -"the last usb device you connected to this computer malfunctioned and windows does not recognize it"
I enabled USB debugging and changed default USB config to MTP
installed drivers again and again in both Linux and windows
I switched operating systems (windows, ubuntu and kali )
I switched laptops and tried every single port of both laptops
I tried miui USB settings app from playstore
I tried using ADB commands from the terminal but no device detected
I entered fastboot mode on phone and then run fastboot devices but still no device found
I used GMTP in ubuntu which worked fine on another phone having somewhat similar issue but it also didn't work
I changed 4 USB cables (3 of them were original mi cables )
I tried using Pendrive using otg but it also didn't work
My laptop worked fine with other phone
I also hard reset my RN5 Pro
I basically tried every fix shown on youtube and XDA threads as well as random google search websites
Please help me what should I do ..
please ....
Download Miflash 2021 version.
Run it and install driver.
Then reboot PC.
pl1992aw said:
Download Miflash 2021 version.
Run it and install driver.
Then reboot PC.
Click to expand...
Click to collapse
are u saying should I flash the stock miui again in my phone using mi flash ??
shaurya_needs_help said:
are u saying should I flash the stock miui again in my phone using mi flash ??
Click to expand...
Click to collapse
No, the driver probably did not installed correctly.
Install the driver. Miflash has the driver needed.
shaurya_needs_help said:
windows 10 is showing
Unknown USB Device (Device Descriptor Request Failed ) in device manager​when I connect windows prompts this message -"the last usb device you connected to this computer malfunctioned and windows does not recognize it"
I enabled USB debugging and changed default USB config to MTP
installed drivers again and again in both Linux and windows
I switched operating systems (windows, ubuntu and kali )
I switched laptops and tried every single port of both laptops
I tried miui USB settings app from playstore
I tried using ADB commands from the terminal but no device detected
I entered fastboot mode on phone and then run fastboot devices but still no device found
I used GMTP in ubuntu which worked fine on another phone having somewhat similar issue but it also didn't work
I changed 4 USB cables (3 of them were original mi cables )
I tried using Pendrive using otg but it also didn't work
My laptop worked fine with other phone
I also hard reset my RN5 Pro
I basically tried every fix shown on youtube and XDA threads as well as random google search websites
Please help me what should I do ..
please ....
Click to expand...
Click to collapse
hi, @shaurya_needs_help, did you solve the issue?.

Categories

Resources