The device itself and the cable work because I've tested them on a Linux notebook and work as intended. When I connect the watch to my PC using Windows 10, I hear the disconnect and connect sound repeatedly, and the watch switches constantly from MTP device to Amazfit Pace on device manager. How can I fix this?
Update or rollback driver.
Check MS Event Viewer for error messages in the time index when the disconnects happen.
Hello, on my Stratos this issue is due to the fact that the watch is not well fitted in the charging cradle ( i lost some parts in the watch that make the watch a bit loose in the charging device).
Despite the watch saying it is charging it is not and it is nowhere to be seen in the file explorer. Only if i exercise some pressure on the watch then i see it in file explorer.
As you say that it works fine in Linux your issue might be different but it might be worth trying to put some more pressure on the watch when it is in the charging device.
Regards
froggyranita said:
Hello, on my Stratos this issue is due to the fact that the watch is not well fitted in the charging cradle ( i lost some parts in the watch that make the watch a bit loose in the charging device).
Despite the watch saying it is charging it is not and it is nowhere to be seen in the file explorer. Only if i exercise some pressure on the watch then i see it in file explorer.
As you say that it works fine in Linux your issue might be different but it might be worth trying to put some more pressure on the watch when it is in the charging device.
Regards
Click to expand...
Click to collapse
You might be right. After applying some pressure on the back of the cradle, it seems like it managed to stay connected and not disconnect and connect repeatedly. I think the issue lies on the connection. Will try cleaning the charging sockets on the watch.
Mwen Davo said:
You might be right. After applying some pressure on the back of the cradle, it seems like it managed to stay connected and not disconnect and connect repeatedly. I think the issue lies on the connection. Will try cleaning the charging sockets on the watch.
Click to expand...
Click to collapse
No luck, it's still doing the same. Linux works though, I can create files folders without it disconnecting.
blackhawk said:
Update or rollback driver.
Check MS Event Viewer for error messages in the time index when the disconnects happen.
Click to expand...
Click to collapse
Event viewer keeps repeating these:
Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24578 Driver Post-Install Configuration:
Drivers were successfully installed for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24577 Driver Post-Install Configuration
Media player and imaging program compatibility layers were successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00. Layer bits 0x00000003 were requested, layer bits 0x00000003 were registered.
Information 26-Jan-23 8:51:38 PM WPD-ClassInstaller 24576 Driver Installation
Autoplay was successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
Driver Management has concluded the process to add Service WinUsb for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
Driver Management has concluded the process to add Service WUDFWpdMtp for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10100 Installation or update of device drivers.
The driver package installation has succeeded.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10002 Installation or update of device drivers.
The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10000 Installation or update of device drivers.
A driver package which uses user-mode driver framework version 2.31.0 is being installed on device USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000.
The order is from bottom to top (Windows coppied it that way). It just keeps spamming those in that order.
Mwen Davo said:
Event viewer keeps repeating these:
Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24578 Driver Post-Install Configuration:
Drivers were successfully installed for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24577 Driver Post-Install Configuration
Media player and imaging program compatibility layers were successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00. Layer bits 0x00000003 were requested, layer bits 0x00000003 were registered.
Information 26-Jan-23 8:51:38 PM WPD-ClassInstaller 24576 Driver Installation
Autoplay was successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
Driver Management has concluded the process to add Service WinUsb for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
Driver Management has concluded the process to add Service WUDFWpdMtp for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10100 Installation or update of device drivers.
The driver package installation has succeeded.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10002 Installation or update of device drivers.
The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10000 Installation or update of device drivers.
A driver package which uses user-mode driver framework version 2.31.0 is being installed on device USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000.
The order is from bottom to top (Windows coppied it that way). It just keeps spamming those in that order.
Click to expand...
Click to collapse
It's not "spamming"; it's logging.
The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
What version of framework is it running?
blackhawk said:
It's not "spamming"; it's logging.
The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
What version of framework is it running?
Click to expand...
Click to collapse
I'm on Windows 10 22H2, which has UMDF 2.33 (source).
Mwen Davo said:
I'm on Windows 10 22H2, which has UMDF 2.33 (source).
Click to expand...
Click to collapse
Can you verify it's loaded on your PC?
Check all Event Viewer sections/messages in the relevant time index. Play with it...
blackhawk said:
Can you verify it's loaded on your PC?
Check all Event Viewer sections/messages in the relevant time index. Play with it...
Click to expand...
Click to collapse
Due to personal matters I had to switch to Windows 11, but unfortunately the problem still persists. The logs are the same as they were on Windows 10.
Mwen Davo said:
Due to personal matters I had to switch to Windows 11, but unfortunately the problem still persists. The logs are the same as they were on Windows 10.
Click to expand...
Click to collapse
I used to use the old Process Viewer to track things down. Don't think that tool works on newer versions but there's probably a similar one.
Play with it... do Google searches. 99.9% of the time that how I resolve issues.
I recently bought Amazfit Pace and had problem connecting it to PC. At first I was certain it was drivers problem, and/or Windows 11 problem. So I went to my parents home and tried there on Win 10 laptop. To my surprise had no luck either. So I ask my father to find a bag of old micro USB cables and out of 4 (counting the one I use previously) smartwatch didn't react at all or was shown in device menager as unknown device. On 5 cable my Pace was recognized by Windows and AMAZFIT Tool. Just like that! So I took that one home and on my regular PC it works as well - soo IMHO Amazfit Pace is apparently very picky about cables
kombajn2 said:
I recently bought Amazfit Pace and had problem connecting it to PC. At first I was certain it was drivers problem, and/or Windows 11 problem. So I went to my parents home and tried there on Win 10 laptop. To my surprise had no luck either. So I ask my father to find a bag of old micro USB cables and out of 4 (counting the one I use previously) smartwatch didn't react at all or was shown in device menager as unknown device. On 5 cable my Pace was recognized by Windows and AMAZFIT Tool. Just like that! So I took that one home and on my regular PC it works as well - soo IMHO Amazfit Pace is apparently very picky about cables
Click to expand...
Click to collapse
I'm using the cable that came with the watch, but I'll try with various Micro USB cables that I have laying around.
Related
Hi,
I've tried to pair my TP via bluetooth to my Windows 7 64Bit machine and two of the drivers failed to installed.
I am wondering if anybody out there successfully paired the prime with a windows 7 64 bit machine.
I have attached a screenshot.
I have a Windows 7 64bit computer and was able to successfully pair the TF201 via bluetooth. I send files to and from each device and all were successful.
Methaq
Hi There,
Actually your solution to your problem is simple, I was in the same situation few days ago, and i have managed to resolve the problem,
Please follow the steps below
Download the 'Windows Mobile Device Center' ( current version is 6.1 ) which you can download it from http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
this works for both Vista and Windows 7. I've tried it on both.
- Install the downloaded software but it may not look like it worked on Windows 7 PCs. Vista automatically configured the settings on the bluetooth devices but for those who have Windows 7, here are the things you should do:
- Go to 'Device Manager' from 'Control Panel' -Or- just right-click on Computer Icon and choose 'Properties' and then click on 'Device Manager'.
- You'll see an 'Unknown Device' named 'Bluetooth Peripheral Device'
- Right-Click it and click on "Update Driver Software" -Or- anyway you find it easy to bring up the Update driver window.
- Click "Browse My Computer
for Driver Software" button.
- Click "Let Me Pick from a List of Device Drivers on my computer".
- Select 'Bluetooth Radio' from the list if it asked you to select and then in the next window, it will show a list of drivers with Company Names in one list and Drivers in another. In the Company List choose 'Microsoft Corporation', not only Microsoft.
- From the drivers list there may be one or more drivers with the name "Windows Mobile-Based Device Support" with different driver versions. Select one or the latest.
- Ignore any warnings and keep pressing next and then Finish at last. If all goes well, the last screen will show the message that device driver is successfully installed.
Now, after manually updating the driver for your bluetooth device, in 'Device Manager' when you click on 'Bluetooth Radios', it should display one more item which will say 'Windows Mobile-based device support'.
There are few more things that you want to pay attention to. If you have already added the device in your 'bluetooth device list' that didn't work, then remove the device and add it again. After you add it, you might need to restart the computer if it gave you a connection problem error message.
Every PCs that had Windows 7 and Vista worked after installing this software and I hope it will work for you too.
Regards
Tech Faded
Tech Faded, before I opened this thread I found the same troubleshooting you suggested with your reply and after giving it a try it did not work for me, it is why I decided to go live on XDA, but thank you for your time a quick response.
Note: the download link you pasted is for "Windows Mobile Device Center 32bit"
The download link for the 64bit version is http://www.microsoft.com/download/en/details.aspx?id=3182
Problem solved (own troubleshooting)
I have pasted what I have to performed in order to fix my Bluetooth connection.
I hope it helps other users with similar problems. Maybe it can be done with fewer steps but this is exactly what I did...
Step 1
Removed the Bluetooth drivers from Windows 7 Device Manager and restarted laptop. Note: Uninstalled drivers (with the "delete driver" option).
Step 2
Unpaired all already paired devices (external BT GPS and Pioneer BT head unit) from the transformer prime.
Step 3
Restart laptop and restart T Prime
Step 4
Pair the Prime to my laptop. The process went smooth and as you can see on the attached screenshot of the paired results, the two 'Bluetooth Peripheral Device' with the X I did get previously to my troubleshooting did not show up this time.
After all these steps I was able to connect successfully.
I have also attached a screenshot of my T Prime successfully connected via BT to my laptop.
Thanks a lot for your replies!
I apologize for posting the 32bit version. Also, great work on your problem solving skills I am assuming that the peripherals belonged to another device which as you suggest you removed from device manager.
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Does anyone have this working? I am seeing no information about it, and ran into a road block when trying to do it myself. Something about failed to initialize the virtualization engine or something.
VirtualBox
JustusIV said:
Does anyone have this working? I am seeing no information about it, and ran into a road block when trying to do it myself. Something about failed to initialize the virtualization engine or something.
Click to expand...
Click to collapse
My problem is that I can't get VirtualBox to install. It gets 3/4 way through installing, then "rolls back" and tells me there was a fatal error.
The problem as of current is the install of network virtual adapters on non-beta in Virtualbox. As genymotion completes install with the no V.B. install. And I don't blame the folks for waiting for Windows 10 to be final and stable before tackling it. You are beta testing Windows 10, as am I, So there really isn't a proper channel to apeal too. You should never install a beta OS on your main machine, at least not as the main OS, and expect everything to work smoothly. Im afraid to say it, but there is nothing we can do yet, just wait for M$ to straighten their end out, as it worked via build 10056, but M$ broke it after that. I am currently trying to get the beta Virtualbox to install via editing ORCA. I'll update when I have more.
Update
Virtualbox 5.0 beta 4 installs, no problem. However Genymotion refuses to see it installed as it is a beta, so until V.B. is finalized for 5.0, and Windows has been closer to completion, well see more. Whatever I tried in ORCA, I had no success. Ironically when Genymotion broke in Windows 10 build 10056, so did my sound but the most recent build, 10122, brought my sound back and allows VB betas to work but not the stable version.
if you want to try the beta for virtualbox 5.0 Beta 4 resides here :
http://dlc-cdn.sun.com/virtualbox/5.0.0_BETA4/index.html
gargash said:
Virtualbox 5.0 beta 4 installs, no problem.
Click to expand...
Click to collapse
Hi,
does this mean you installed the beta 4 on TP 10122 *with* the virtual network adapter without rollback?
Yes, however Genymotion doesn't recognize it.
gargash said:
Yes, however Genymotion doesn't recognize it.
Click to expand...
Click to collapse
Thank you, I will try the new beta.
I miss Genymotion too but I have a installed Win10 guest where I need the virtual bridge network (NAT is running ofc).
---------- Post added at 09:14 AM ---------- Previous post was at 09:00 AM ----------
tramp20 said:
Thank you, I will try the new beta.
Click to expand...
Click to collapse
Sorry, but as expected the beta 4 wizard "ended prematurely" as before.
I had to reinstall VB without the virtual network bridge again.
For those interested, w10 build 10130 and genymotion (2.5 just launched today), still issues.
gargash said:
For those interested, w10 build 10130 and genymotion (2.5 just launched today), still issues.
Click to expand...
Click to collapse
I think this is VirtualBox issue, not Genymotion`s
Virtualbox runs fine on Windows 10 build 10130. However genymotion seems to have problems initializing it. I believe this is a genymotion problem.
grennis said:
Virtualbox runs fine on Windows 10 build 10130. However genymotion seems to have problems initializing it. I believe this is a genymotion problem.
Click to expand...
Click to collapse
Well, i have "virtualization plugin not found" issue. It comes because of virtualbox can`t properly install "Host-only network adapter" driver on win10.
Sorry you are right about that. The problem is Virtualbox and host-only network adapter. I had created a VM in vbox and ran it so I thought it wasn't the problem.
What is really annoying is that it actually does create the adapter. If you go to Device Manger -> Network Adapters -> you will see Virtual box host-only adapters listed there.
So it's really close to working just something fails at the end of the process.
I was able to get genymotion working in Windows 10.
It is failing trying to create the host-only adapter, so you must do it yourself manually, and then it will use that.
- Run virtualbox as administrator
- Go to File -> Preferences -> Network -> Host Only Networks
- Add a new network. IP address 192.168.1.201, mask 255.255.255.0. Go to DHCP server and enable it. IP address 192.168.1.100, mask 255.255.255.0, lower bound 192.168.1.101, upper bound 192.168.1.199
- Save all and exit
- Now run genymotion.
It works!
grennis said:
I was able to get genymotion working in Windows 10.
It is failing trying to create the host-only adapter, so you must do it yourself manually, and then it will use that.
- Run virtualbox as administrator
- Go to File -> Preferences -> Network -> Host Only Networks
- Add a new network. IP address 192.168.1.201, mask 255.255.255.0. Go to DHCP server and enable it. IP address 192.168.1.100, mask 255.255.255.0, lower bound 192.168.1.101, upper bound 192.168.1.199
- Save all and exit
- Now run genymotion.
It works!
Click to expand...
Click to collapse
Nope, it does not.
Alashe said:
Nope, it does not.
Click to expand...
Click to collapse
Does too.
Alashe said:
Nope, it does not.
Click to expand...
Click to collapse
Hello,
I can not add a new Host Only Networks on my PC. So I modified the existing network with same IP above but I can not run Genymotion.
I also tried to stop, start vboxdrv service (used sc.exe start vboxdrv on cmd) and it still was not success.
I restarted my PC many times and it still was not success too. But I saw that everytimes I run Genymotion, it had new network in Host Only Networks of VirtualBox. I think Genymotion didn't use my network that I configed before.
So I go to Control Panel -> Network and Sharing Center -> Change adapter settings. I saw 2 VirtualBox Ethenet. I disabled once and configed the remain likes network in Host Only Networks of VirtualBox.
I run Genymotion again and it's works. I use Windows 10 Build 10162, Genymotion 2.5.0, VirtualBox-5.0.0_RC2. Please see my picture.
Sorry my English. Hope this help.
Thanks grennis .
@nguyenthanhhai
Your solution sounds awesome but I can't figure out how to do it.
If you could please post a step by step instruction with screenshots (all the way from installing virtualbox). Or just record yourself doing it (screen recording), that would be purely amazing !!!
Thanks so much for your help
The idea is to setup a host-only network the way genymotion likes it whether you do it from vbox (run as administrator!) like I did, or from WIndows network settings like nguyenthanhhai did.. Then it won't try to create a new one. Give the adapter IP address 192.168.1.201, mask 255.255.255.0. Go to DHCP server and enable it. IP address 192.168.1.100, mask 255.255.255.0, lower bound 192.168.1.101, upper bound 192.168.1.199. I also have genymotion running just fine, this does work.
At last
Yep, win 10 build 10162 works fine
At least, Genymotion working on build 10162. Thank you very much grennis and nguyenthanhhai.
grennis said:
The idea is to setup a host-only network the way genymotion likes it whether you do it from vbox (run as administrator!) like I did, or from WIndows network settings like nguyenthanhhai did.. Then it won't try to create a new one. Give the adapter IP address 192.168.1.201, mask 255.255.255.0. Go to DHCP server and enable it. IP address 192.168.1.100, mask 255.255.255.0, lower bound 192.168.1.101, upper bound 192.168.1.199. I also have genymotion running just fine, this does work.
Click to expand...
Click to collapse
Thank you for your help.
Now I could at least start Genymotion player again and my virtual guests too.
But I have nowhere internet access.
How should I configure the Windows VirtualBox Host-Only Ethernet Adapter, especially DSN-server and gateway?
I cannot use DHCP because of VMWare installed with an own DHCP-server.
I am running VB 5.0 RC3 and Genymotion 2.50.
Thank you.
Hi, I'm new to the N9, have had the tablet about a week. I have tried connecting it to my windows 7 Pc and the N9 isn't recognized. I have tried all the basics, all drivers are current, set tablet to mtp, and not found. I have connected to a friend's Windows 10 PC and the N9 is found immediately. My N9 is a wifi only device, non rooted. I have 2 other Android devices that my W7 PC finds with no issue. Anyone else experience this, and or have any suggestions on how to fix this issue ? Not looking to root at this point. Any help and guidance would be greatly appreciated
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
In some cases, you need to enable ADB on your N9 before plugging it into your PC (Settings -> Developer Options -> Android Debugging).
peterk-1 said:
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
Click to expand...
Click to collapse
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
eckharttim said:
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
Click to expand...
Click to collapse
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
peterk-1 said:
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
Click to expand...
Click to collapse
Thank you for your help I greatly appreciated it. After trying pretty much everything, I decided to see if the ruu's for my two phones would run on W10. They did, so I then proceeded to update my W7 to W10. N9 communicates perfectly now with my PC. Thank you
i have tried all method
Solution #1: Check USB device & connection status
Solution #2: Use Hardware and Device troubleshooter
Solution #3: Uninstall and update the USB driver in Device Manager
Solution #4: Check and repair bad sectors for the malfunctioned USB device
Solution #5: Disable Fast Startup to fix USB device failure
Solution #6: Disable USB Selective Suspend Settings
Solution #7: Update driver software for Generic USB Hub
Solution #8: Recover lost / deleted files from USB flash drive
nothing working at any cost help me asap
What's the device?
You did reboot, again and again...?
Did you check Event viewer for error messages?
Try to directly load driver in hardware management?
Try a different port?
@insane_xd
look inside here:
3 Tips| Fix USB Error Code 43 in Windows 10 & Recover Data
If you check your USB properties and see your device status is: Windows has stopped this device because it has reported problems (code 43), you have encountered one of the commonest issues of hardware devices in Windows 10 - code 43 error. Luckily, we have provided all the possible solutions for...
www.easeus.com
blackhawk said:
What's the device?
You did reboot, again and again...?
Did you check Event viewer for error messages?
Try to directly load driver in hardware management?
Try a different port?
Click to expand...
Click to collapse
its mi note 7 pro i cheak doing reboot error massge is same
Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed. i cant even able to open my phon
blackhawk said:
What's the device?
You did reboot, again and again...?
Did you check Event viewer for error messages?
Try to directly load driver in hardware management?
Try a different port?
Click to expand...
Click to collapse
jwoegerbauer said:
@insane_xd
look inside here:
3 Tips| Fix USB Error Code 43 in Windows 10 & Recover Data
If you check your USB properties and see your device status is: Windows has stopped this device because it has reported problems (code 43), you have encountered one of the commonest issues of hardware devices in Windows 10 - code 43 error. Luckily, we have provided all the possible solutions for...
www.easeus.com
Click to expand...
Click to collapse
all done but still not able to fix
Driver error, uninstall and try again.
install the Samsung USB drivers and it should let you see/open your phone in windows.
My Pixel6 wouldnt be seen then I installed these and it worked
You can download the wushowhide.diagcab utility from the Microsoft Download Center
Run the wushowhide.diagcab tool and select the option “Hide Updates“;
In the list of the available Windows updates and drivers, check the drivers for which you want to disable the auto-update and click the Next button.
After that, the selected drivers will not be automatically updated by Windows.
This may help?
J wick
Unfortunately for you it is hardware issue. So port damaged or connector. Drivers install, uninstall will not help you. Need to vring it to service centre.