Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized,
all drivers installed correcly with hisuite , my cable usb is new,
i changed today the USB charging port of the phone at Huawei care service, and i reset factory the phone , still same problem.
I'm still having the same stock rom on the device,
is the "usb not recognized" problem can be a software problem in the phone? thank you for your experience.
chahine21 said:
Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized
Click to expand...
Click to collapse
I'll try to help you but I'm not an expert, and yet I've had EVERY problem you seem to be speaking about.
a. I have had broken USB ports
b. I have had broken USB cables
c. I have had the USB drivers not install on Windows
etc.
Given I've had some of the same problems, I feel for you, so my first advice is to simply give up on USB for everything that you can.
Specifically, if you can turn on USB debugging and Wireless debugging in the Developer options, you can operate the phone over Wi-Fi using the Windows monitor, keyboard and mouse as shown in my screenshots below.
You don't need anything installed on Android to use these FOSS solutions on Windows to operate the entire phone over Wi-Fi as of Android 12 (which eliminated the need for an initial USB connection to establish the Wi-Fi connection).
In summary, I have had similar problems with USB where I've given up on USB and switched to operating Android over Wi-Fi and even mounting the entire Android file system as a Windows drive letter over Wi-Fi using free software.
a. adb
b. scrcpy
c. vysor
d. webdav
Use Windows Event Viewer to check for error messages on the PC.
If the problem is the PC it will likely show up there and give you more troubleshooting clues.
Thread closed at OP's request.
Related
I have a stock Evo View running Honeycomb 3.2.1. Interestingly, neither of my computers, both mac and pc, will detect my tablet when I connect it by USB. This worked just a few weeks ago when I moved some files onto the device. The tablet charges through USB, but I do not get the notification option to use as USB storage. Within "settings > connect to pc" I've tried a number of configurations (default configuration type = disk drive, charge only) and I have also tried checking and unchecking "ask me about USB connection type whenever I connect my tablet to a PC." Nothing new happened.
Additionally, on the mac, I have the Android File Transfer app installed. When I open that i get a notification that says "No Android Device Found"
Coincidentally, I recently installed the Dropbox desktop beta for Mac which automatically detects pictures on a camera and uploads them to Dropbox. When I connected my device, Dropbox checked my device for pictures because it recognizes it as a camera. I instantly got a system error message saying that my device was not ejected properly. However, the mac never detected my device as a drive. Following that, I tried to connect to my PC and all it does is charge. My PC also does not detect my tablet as a drive. I'm thinking the new dropbox desktop client may have been the culprit for breaking my usb connection between my tablet and mac.
Has anyone else experience this problem? If not, is there a way to rebuild my usb connection between my tablet, mac, and pc?
well i would try uninstalling dropbox
Also in Settings/Applications/Development/Usb debugging should be checked.
Thanks. Appreciate the advice.
I did uninstall dropbox, on the View and on the Mac. That didn't help.
USB Debugging was checked. I can see my device in fastboot and adb. However, neither Mac nor PC will detect my tablet and allow me to mount as a hard drive.
I did a factory data reset and that worked. Both computers will recognize the View and I am receiving the notification "charge only, hard disk, htc sync, etc." again.
I wanted to break the usb connection again to confirm that it was in fact either dropbox's android beta, desktop beta, or a combination of the two. I am fairly certain that something broke the first time around because the desktop beta was able to scan my device for photos without my permission to mount the View as a hard disk. But now I'm having trouble proving this since I haven't been able to break the connection again.
Hi everyone,
I often transfer files between my Samsung S7 Edge and my Windows PC through USB cable. However, after (making the mistake of) letting it upgrade to Oreo (v8.0), this is no longer possible: connecting the phone via USB to my laptop only shows charging information in the swipe-down top menu, and I no longer get the prompt asking whether I want to allow access to the phone's contents. Consequently, the phone's internal&SD memory no longer shows up under Windows Explorer.
I've been searching for a fix/workaround for hours (thanks Google for this quality time!). Some of the things I've tried that didn't work:
- enable/disable USB debugging mode under developer options
- change "USB configuration" (under Developer Options) to "MTP" and to all other options there
- use a different USB cable and USB port on the laptop
- search for apps on the Play Store that can help with this (didn't find any that actually do the job)
Connecting Android phones to Windows laptops to access their internal memory through USB cable has (bemusingly!) been a problem with this ****ty OS as long as I can remember, so it doesn't surprise me that users are having to spend even more time now to get it to work again.
Any suggestions much appreciated!
longtalker said:
Hi everyone,
I often transfer files between my Samsung S7 Edge and my Windows PC through USB cable. However, after (making the mistake of) letting it upgrade to Oreo (v8.0), this is no longer possible: connecting the phone via USB to my laptop only shows charging information in the swipe-down top menu, and I no longer get the prompt asking whether I want to allow access to the phone's contents. Consequently, the phone's internal&SD memory no longer shows up under Windows Explorer.
I've been searching for a fix/workaround for hours (thanks Google for this quality time!). Some of the things I've tried that didn't work:
- enable/disable USB debugging mode under developer options
- change "USB configuration" (under Developer Options) to "MTP" and to all other options there
- use a different USB cable and USB port on the laptop
- search for apps on the Play Store that can help with this (didn't find any that actually do the job)
Connecting Android phones to Windows laptops to access their internal memory through USB cable has (bemusingly!) been a problem with this ****ty OS as long as I can remember, so it doesn't surprise me that users are having to spend even more time now to get it to work again.
Any suggestions much appreciated!
Click to expand...
Click to collapse
Hi friend just dial *#0808# choose MTP+ADB click OK and Reboot your device . Try to connect again with usb cable in PC . Good luck
Teddy Lo said:
Hi friend just dial *#0808# choose MTP+ADB click OK and Reboot your device . Try to connect again with usb cable in PC . Good luck
Click to expand...
Click to collapse
Thanks - I tried that, but I still don't see the phone's memory as a USB drive, nor any permission prompt on the phone once I connect it.
longtalker said:
Thanks - I tried that, but I still don't see the phone's memory as a USB drive, nor any permission prompt on the phone once I connect it.
Click to expand...
Click to collapse
Try to reinstall drivers ,uninstall all previously installed use USBDEVIEW tool .
https://www.nirsoft.net/utils/usb_devices_view.html
Before I do that, I should note that, when I tried on a different Win 10 PC, I get the USB drive back no problem, so the problem is Windows/PC-related, it seems?!
Turns out that, when using another USB cable, the phone is once again seen as a USB drive. I didn't think the cable could make a difference! Hope it helps others
I'm having error on Win10 when I connect my Mipad4 but it works well using the cable to charge. I've also tried a few cables. Is the port faulty?
Try another port.
Check connection settings in Developer options.
You need to authorize the connection first on the Adroid; a popup window will appear if connected*.
Go to Disk Management>scan drives, connect from here.
No joy? Check Event Viewer for error messages.
Try rolling back the driver in Hardware management, or updating it. No driver means no joy! Reboot, always reboot with Windows... it ain't no Android
*this is how a Samsung Android behaves... hopefully this will help; cross platforming.
Play with it...
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
That's strange, either your port is damaged or you don't have drivers installed. I've heard if this happening on Windows 11, never had a problem on Linux
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
Do you have the latest USB drivers installed?
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
The drivers are installed. My home pc is what I used to unlock/root the phone.
When I look at Show Hidden Icons -> Safely Remove Hardware and Eject Media, there is an option to remove Pixel 6. Yet it doesn't display under File Explorer or XYplorer.
If I start up my Arch (linux) vm with VMware Workstation Pro under Removeable Devices there is an entry for Google Pixel 6 with the option to Connect (Disconnect from Host). The contents can be under Arch.
Have you tried different cables & different ports? Sometimes the cable is the problem for me.
Different cables/ports had no effect.
I've got the same issue, what's weird is I can move files with ADB but can't in Windows.
If you figure anything out please hit this back up?
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
vandyman said:
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
Click to expand...
Click to collapse
Cables/drivers are good. ADB/fastboot work fine it's the transferring of file/recognision of device in windows explorer that is the issue.
thecdn said:
it's the transferring of file/recognision of device in windows explorer that is the issue.
Click to expand...
Click to collapse
Switching from charging mode to file transfer mode in the Connected devices/USB menu should give you access to Android's internal storage from Windows. USB debugging or other Dev options aren't necessary.
I had this same problem. Connecting to pc would show connection options but they were all greyed out and the phone would only charge. I couldn't find any option in the standard settings to change this.
Eventually I found 'default usb configuration' in dev options. Default was set to 'charge only'. You can sort it from there.
edit to add: although re-reading op you may have tried this already.
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
It's the stupid Windows drivers. There is an .inf file you need to either edit or delete but I forgot which. Might be wpdmtp.inf in the windows directory, right click and install. You might have to uninstall the driver in device manager first, the one with the exclamation mark if it's there. Sorry it's been about 3 or 4 years since I have done this but it's most likely a driver issue.
Mike Tanner said:
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
Click to expand...
Click to collapse
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
thecdn said:
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
Click to expand...
Click to collapse
I agree about drivers, that they're either corrupted or incomplete. What's going on in Windows Device Manager when the phone is in a certain state?
During normal operation I assume the general purpose driver is always visible.
Device Manager > Portable Devices > Pixel 6
In fastboot mode with USB debugging enabled, is this driver showing up?
Device Manager > Android Device > Android Bootloader Interface
While Android is running with USB debugging enabled, do you see an ADB driver (the daemon may need to be started)?
Device Manager > Android Device > Android Composite ADB Interface
I was wondering if anyone could help me with an issue I am having with Windows 11.
I have an old Samsung Galaxy Tablet (2013), the MicroUSB port had to be replaced as the port had broken. Before the repair, the tablet could connect to my Windows 11 PC with no problem, it showed up in Device Manager and File Explorer fine. After the repair, the Tablet will no longer connect and shows up as an "Unknown USB Device".
All methods I have tried, including installing new Drivers, have failed.
If anyone can help, I will really appreciate it!
Who did the repair? It seems whomever did the repair either didn't use the correct parts or installed them improperly.
A friend of mine did the repair. They are quite good at soldering, I will ask them to have another look at the port.
I know the correct part was used as we got the Port from another tablet of the same model.
Check for hardware issues
There’s a possibility that you’re unable to use your USB device due to a hardware issue, meaning that the problem lies within your computer and not the operating system. Here are two easy ways to test if this is the case, which can easily prove whether you need to look into getting your computer restored or can proceed with the methods below to fix system-originated issues.
Plug out your power supply
For some reason, temporarily unplugging your power supply and then connecting the problematic equipment into your computer may fix the Unknown USB device issue on Windows 10. Simply disconnect all charging cables from your laptop until your computer is only running on its integral battery. Then, plug in the USB device to see if your system recognizes it.
Uninstall the USB Driver in Device Manager
Press the Windows + R keys on your keyboard at the same time to bring up the Run utility.
Type in “devmgmt.msc” without the quotations marks, then hit the OK button. This is going to launch the Device Manager in a separate window.
Expand the Universal Serial Bus controllers section, then select the Unknown USB Device (Device Descriptor Request Failed) from the list.
Right-click on the selected USB device and choose Uninstall from the context menu. Follow any on-screen instructions to remove the device.
When the uninstallation is complete, reboot your system. It’ll automatically reinstall the drive correctly, which may help you get rid of the error you’ve been receiving.
Regards,
J Wick