yo xda.
USB file transfer is dead on my phone.
when i plug the phone to a computer, it charges, but i have no choice for USB file transfer (MTP or PTP) that was just there in the notifications bar.
i tried with 5 different computers (win7 and win10), and 2 usb-C cables (the xiaomi official one, and a brand new samsung usb-c one, no luck).
Is it possible the USB transfer stuff is broken in Android sofware-wise???
I have magisk only for systemless hosts, to suppress tha ads, nothing funkalistic . Stock rom, stock (unlocked) bootloader.
USB transfer just stopped working without warning.
I reinstalled drivers without effect. No USB file transfer thing in notifications .
One more very weird thing is that i can still fastboot to the phone. So i think the cable works as intended.
>>>C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
>>>2871d3b5 fastboot
How to reactivate the USB thing? Maybe i disactivated by error...no clue, really.
aaand flashed full stock funkelnagelneu fastboot rom.
i gained an OTA. but still; adios USB MTP or PTP. ftp, here i come.
why fastboot works, and not usb transfer, is a mystery.
Related
adb devices doesn't show anything. I have tried it with linux and windows (with Motorola drivers installed), it doesn't work. I can access the phone when I have enabled MTP, but it just won't show in adb. I have killed and started adb server so many times, it's frustrating.
The thing is, the first time (yesterday) it worked! I could reboot into fastboot with adb but then nothing worked anymore.
Any ideas?
Maybe silly question, but: is USB debugging activated on the phone? If yes, try to switch between MTP and Camera (PTP) under "USB computer connection" option. You should get the authorization prompt on your phone when everything is fine.
Yes, USB debugging is activated. I already tried both MTP, PTP, and neither, but I don't get any authorzation prompts. I revoked all previos prompts, but still nothing. Thanks for the suggestion though!
Are you on bootloader or recovery or normally on os
I tried all three.
Try playing with the USB cable - change it, change the USB slot on the PC that it's connected to, etc.
I only have one USB cable, but I already tried it on several USB slots.
It worked! I had to put sudo in front of my adb commands! Yay! :victory:
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 all,
Long time no post.
I have an issue with my grandparents' Slate 21. The bootloader doesn't boot into OS. I'm no super tech nerd, but I have done Android reinstalls on Xiaomi Pocophone F1 and Samsung Galaxy S4 I-9505 with TWRP.
To install TWRP on the Slate 21, all you need is a male-to-male USB A cable and ADB.
My issue. I have downloaded many drivers (ADB&Fastboot, Google USB driver) and used methods such as
updating "Fastboot" driver software via device manager to a specific driver
manually installing drivers (Right-click -> Install)
switching USB ports
When I type in
Code:
fastboot oem unlock
or ANY
Code:
fastboot
command I always get
Code:
<waiting for any device>
. I have tried everything, so I came here as a last attempt. I will give any info you need because my grandpa needs this Slate.
Some info:
I installed ADB and Fastboot via the "15-second installer"
Fastboot loads correctly on the device itself
I cannot access Developer options because it doesn't load to OS
I use Windows 10
Love,
Nerijus
Simply installing drivers you don't know what they are meant for makes no sense at all, IMO:
Google's USB driver you installed is only applicable for Google devices ( e.g. Pixel, Nexus ).
You have to install the "Android USB Driver" suitable to mentioned phone.
BTW: To get the most accurate ADB & Fastboot drivers use my tool what is linked to in my signature.
jwoegerbauer said:
Simply installing drivers you don't know what they are meant for makes no sense at all, IMO:
Google's USB driver you installed is only applicable for Google devices ( e.g. Pixel, Nexus ).
You have to install the "Android USB Driver" suitable to mentioned phone.
BTW: To get the most accurate ADB & Fastboot drivers use my tool what is linked to in my signature.
Click to expand...
Click to collapse
The issue might be USB 3.0 ports.
emperoringo said:
The issue might be USB 3.0 ports.
Click to expand...
Click to collapse
If you say so ...
IMO your issue has nothing to do with of what type an USB port is.
The differences between USB 2.0 and USB 3.0 are
You can transfer data at up to 4.8 GBit/s with USB 3.0. That is ten times faster than with USB 2.0, which has a maximum of 480 MBit/s.
USB 3.0 works full-duplex. This means that data can be transferred in both directions. With USB 2.0, you can only transfer data in one direction at a time.
The maximum cable length with USB 3.0 is limited to 3 meters. USB 2.0 cables can be up to 5 meters long.
Never heard / read that ADB & Fastboot drivers depend on type of USB port.
jwoegerbauer said:
If you say so ...
IMO your issue has nothing to do with of what type an USB port is.
The differences between USB 2.0 and USB 3.0 are
You can transfer data at up to 4.8 GBit/s with USB 3.0. That is ten times faster than with USB 2.0, which has a maximum of 480 MBit/s.
USB 3.0 works full-duplex. This means that data can be transferred in both directions. With USB 2.0, you can only transfer data in one direction at a time.
The maximum cable length with USB 3.0 is limited to 3 meters. USB 2.0 cables can be up to 5 meters long.
Never heard / read that ADB & Fastboot drivers depend on type of USB port.
Click to expand...
Click to collapse
My laptop's USB 3.0 ports completely failed to unlock Xiaomi Pocophone F1's bootloader. Meanwhile, my old PC did it easily on the first try and it has USB 2.0 ports. Weird. Might be the reason.
Hi,
For some reason I can no longer transfer files from my Android device to my Linux PC using Android File Transfer.
I can list the device:
sudo adb devices -l
List of devices attached
????????? device usb:1-4 product:OnePlus5T model:ONEPLUS_A5010 device:OnePlus5T transport_id:2
Click to expand...
Click to collapse
but Andorid File Transfer (version 4.2) wouldn't start with this phone. When I attach an older phone (Nexus 4) all is fine and I can transfer files without problem.
USB Debugging is enabled on the device.
On USB Preferences File Transfer is selected. Other options are USB tethering, MIDI, PTP, No data transfer.
Any help will be appreciated.
Update: problem solved - had to use root privilidges
Try another cable. Cliché but it's often the culprit. When you get the USB mode popup just cancel it and it'll decide on its own. Disable USB debugging as it doesn't need to be on. Try other USB ports, or the last one it was known working on. Failing that see if there's a proprietary software. Microsoft Your Phone Companion might help..
Hi,
After flashing a custom ROM, my GT-N8010 device is not recognised by my laptop. I think it was after I used Advanced Wipe in TWRP while my device was connected to my computer. Ever since then, I've been getting the "The last USB device you connected to this computer malfunctioned" error. Flashing custom ROMs with a Micro SD card works fine, but the device is still not recognised.
I've tried:
1. Selecting File Transfer as the default USB protocol
2. Enabling/Disabling the USB debugging function
3. Using the Mount option in TWRP
4. Connecting the device to multiple laptops
5. Reinstalling the Samsung USB driver for mobile phones
I thought flashing the stock ROM would be the best option, but I couldn't use Odin because my device is not recognised.
Also, the USB cable is an official cable, and charging works (through both the charger and the PC).
Would anyone happen to know how this could possibly be fixed? Or is there any other way to flash the stock ROM without a USB cable?
Thank you!
Use USbDev view on PC to delete hardware settings from USB port .
freeware utilities: password recovery, system utilities, desktop utilities - For Windows
Unique collection of freeware desktop utilities, system utilities, password recovery tools, and more
www.nirsoft.net
JJEgan said:
Use USbDev view on PC to delete hardware settings from USB port .
freeware utilities: password recovery, system utilities, desktop utilities - For Windows
Unique collection of freeware desktop utilities, system utilities, password recovery tools, and more
www.nirsoft.net
Click to expand...
Click to collapse
I removed the device and reconnected it, but it still doesn't work.
Need another PC/ Laptop .
JJEgan said:
Need another PC/ Laptop .
Click to expand...
Click to collapse
Tried it on a completely different PC, but the results are the same. I think there's a problem with the GT-N8010 device; I've tried changing the PC/laptop multiple times already.
Usual is USB cable then no Samsung USB Drivers .