Related
Hey there,
I try to synch my PC with my tp2. I own a PC with Vista and I plugged the TP2 on it. Bute the winmo device center can't find the tp2, so I can't put any files on my phone. The phone is charged via USB, so there should be a connection, but I can't find it in the explorer as a mass storage device...
Is it possible I did something wrong or can you help me fix this problem?
Bye,
Christopher
Bueggi said:
Hey there,
I try to synch my PC with my tp2. I own a PC with Vista and I plugged the TP2 on it. Bute the winmo device center can't find the tp2, so I can't put any files on my phone. The phone is charged via USB, so there should be a connection, but I can't find it in the explorer as a mass storage device...
Is it possible I did something wrong or can you help me fix this problem?
Bye,
Christopher
Click to expand...
Click to collapse
In connection settings do you have the option to "Allow USB Connections" enabled? make sure that box is ticked.
connect the device first and then open up the winmo device center. it's the only way it works for me.
Swith this checkbox off in the settings: Advanced connections.
When you connect your phone to your pc, open up the device manager and you should find an unknown device in the list. If oyu right click on it, go to update drivers, and then when the wizard comes up, you need to point it to a specific location...
If you then point it to the folder where the mobile device center is installed then it should find the necessary drivers and suddenly your pc will have found your phone
Certainly, this is how I have to do it with active sync on my pc at work (for some reason since connecting my TP2 - previously it had my TyTNII connected - it doesn't automatically recognise the device in terms of using the right drivers).
i had a similar issue, it was zonealarm. Try it with firewall turned off.
Hi all,
I have the same Active Sync connectivity issues, and they happen quite often, I should say... I did some investigation on my own, and after some digging (and talking to some friends), I managed to discover where the problem lies.
It seems that Windows Vista's Active Sync service get's kinda "numb" sometimes... and to "wake" it up, we have to start and stop the service. Here's my workarround:
Before we start, and since you may need use "start" and "stop" the Active Sync service quite often, I suggest you create a batch file (just create a normal text file and rename it to .bat after saving it) containing the following:
net stop rapimgr
net start rapimgr
With this file you'll be able to restart the service with just 2 clicks (followed by a "Y" and the Enter key).
Here are 5 simple steps:
1. After a failed connection attempt, close Windows Mobile Device Center and disconnect your TP2 from USB;
2. Run the batch file you created previously, and wait a couple of seconds after the DOS window disappears;
3. Reconnect the TP2 to USB and wait a few seconds (considering all the TP2 drivers were already automatically installed, if not, wait for them to install);
4. On your TP2, select the Active Sync option. On your PC, open My Computer and you should see your TP2 appear (if not already there ). At this point the Active Sync connection is already established;
5. Open Windows Mobile Device Center and wait a few seconds for the software to "wake up". The software should Connect to your TP2 successfully.
Et voilá. You're all set to replicate via Active Sync, and to transfer files to and from your device via Windows Explorer.
Repeat the process everytime the connection fails (which in my case, it happens quite often ). If it doesn't work the first time, try again, and if it's still not working... there's not much you can do besides restarting your PC and try all over again (blame Microsoft, not me ).
For the Disk Drive not connecting issue, you might want to to take a look into your Windows Device Manager > Storage > Disk Management and check if you can see your memory card in there.
When connected using the Disk Drive option on your TP2, it behaves like any other USB disk/pen drive, and it can be conflicting with another drive letter that already exists on the system (it's stupid but it happens quite often). To solve this particular issue, just change the drive letter associated with the TP2 memory card (it should have no drive letter associated if conflicting) to an available drive letter (right after your CD/DVD-ROM drives). Click OK ando this issue is solved.
Hope it helped...
P.S.: I also have ZoneAlarm (latest version - original copy) with max security definitions, and I can assure you that it has nothing to do with this issue.
It's terrible - tried every suggestion mentionned, but it just won't help.
When trying to update the driver, I can point to c:\windows\WindowsMobile\Drivers, but it won't find a suitable driver.
(I think the driver in Serial should be used, but it won't let me!)
Tried removing and installing WinMobile many times, removing the 'Unknown device' etc., but it just won't help!
This is a problem on every computer I tried with several cables.
However, the device did connect correctly when I still had WM6 on it. Flashed various ROMs from Miri, but for every ROM it's the same problem...
be sure you have checked the "synchronize all computers with connection" and drop down menu "usb" in active sync in your PDA (located in settings tab / active sync - menu/connections)
the naming can warry cause i don't use english wm
spyrox04 said:
be sure you have checked the "synchronize all computers with connection" and drop down menu "usb" in active sync in your PDA (located in settings tab / active sync - menu/connections)
the naming can warry cause i don't use english wm
Click to expand...
Click to collapse
Thanks, but of cause I already checked this.
Besides, this should not change the useage of the device as remote disc.
Also, I noticed with the ROM from Atom that the device stops charging as soon as the PC sees something is connected to the USB post. (I only get an unknown device message and that's the only device that is 'installed')
Trouble syncing Tilt and Tilt 2 with Windows Mobile Device Center
I have two laptops and two cell phones. I can sync with the Windows XP laptop with no problem, however, I can't sync with the Vista computer at all. I've even tried reformatting the Vista laptop, but can't get it to sync. I've tried uninstalling the driver for the connection through the Device Manager as well as the Windows Mobile Device Center. Then reinstalling Windows Mobile Device Center and the driver. I've checked the cable and USB port. They work for everything else I can throw at them, but can't get them to sync. Windows Mobile Device Center does not show any devices connected (either Tilt or Tilt2). Any advice?
Laptop 1
Windows XP SP3
Activesync version 4.5
Microsoft Outlook 2007
Laptop 2
Windows Vista Home Premium SP1
Windows Mobile Device Center
Outlook 2007
Cell phone 1
AT&T Tilt
Windows Mobile version 6.1
AT&T Tilt 2
Windows Mobile version 6.5
Any update for the connection problems?
Here it still does not work; the device is still not seen as mobile device, but as 'unknown device'.
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
:::Edited:::
Try killing any adb running in the background first
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Another option is to use updated flasher attached. I found it on russian forum.
hlvl said:
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Click to expand...
Click to collapse
Meh... I can't read. For some reason I read that you were talking about connecting your phone to the PC, i.e. within android, for USB mass storage etc....
Even the topic of the thread says otherwise. I'll go get my eyes tested...
Sometimes it's because ADB still in your PC memery, just force close it and everything will be fine.
As I said I tried to reboot PC but it didn't help. I doubt ADB start with Windows but rather only when you start using it.
hlvl said:
Another option is to use updated flasher attached. I found it on russian forum.
Click to expand...
Click to collapse
Do you mean that this is MAGLDR 1.13!?!?
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Thanks man. I was already freaking out because of this.
I'm going to try this on my desktop, that's why I stopped using it lol
Sent from my HD2 using xda premium
Thanks! It worked very well!!
PG
Really thank you, you saved my phone
Mine has always done that. I just have to wait until the flasher program gets to the Looking for USB step and disconnect/reconnect the USB cable.
Or get a new cable. I had the same issue but even this guide didnt work. My cable needed replacing, luckily I had a spare in my closet. Tried it and bingo all the drivers installed. If it just wont find it, get a new USB cable.
I have the same problem but in bootloader my usb connection works...when i try to flash recovery with usb flasher mode in magdlr doesnt.
Wait for usb............and is stuck like that.So its not the cable..i tried to install new driver..i tried with command prompt....im freaking out!!
Installing WMDC 6.1 worked for me
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Had same problem getting PC to recognize HD2 in order to Task29, etc...
I downloaded/installed WMDC 6.1 (for Vista, but works with W7) and walla... fixed! Link HERE.
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
You may not want to try this either but try a system restore
Sent from my SPH-L710...if some one helps you press the thanks button
Volknochi said:
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
Click to expand...
Click to collapse
I had the same issue what ended up fixing it for me was watching when I plugged the phone in after a clean driver install and stopping Windows from downloading and installing an updated driver. Dont know if its the same for you but that fixed it for me. I was really frustrated by it and found no help either.
probably an easy fix
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
I won't do a system restore, that won't do anything. Not to mention it would erase some programs that were installed (not related to phone). So, not doing that. Also, my computer will not automatically update any drivers or any thing else, as I have it set to manual mode.
And, I do not have Kies installed. It never worked for me properly, when it came to driver installation. I've done the "go into device manager" bit many times before, it still likes to play the "Hardware ID doesn't match" card. Drivers won't install either. I don't know what it is, but damn this is the most stubborn thing I've ever encountered.
i've post this in other forums today. what i do to get it working is i toggle USB debugging and try it out, then start toggling the ptp and mtp until it works. the combo that works for me is turn on debug, plug in computer, unplug, turn off debug, plug in. if it doesnt work then i toggle back and forth MTP and PTP. 5 tries at most, for me. Also, i did a nandroid back to my oem ICS that was 2 weeks old and just rooted. the problem is worse there. i'm using freegsmr6 with trinity kernel on Tmo. hope it helps.
Ditto
Yeah that whole "Hardware ID missing" was an irritating situation. This is what I recommend as far as making it work.
1. Plug in.
2. When you get the error message, I think its because of a conflict with the ADB interface. Go to Settings, Developer Options, and check off USB Debugging.
3. Plug in once again and it should work. If not, try toggling between Camera and MTP.
I have Windows 7 Ultimate and it works fine for me
I always get that error as well with my SGS 3. I have to reinstall Kies everytime it does that which is annoying.. ANyone has a permanent solution about this?
Fix for me was...
1-plug in phone. Get the hardware ID message. Leave phone plugged in.
2- open device manager. Click on. Android Phone and Uninstall Samsung Android ADB Interface. Also check the "delete software driver" when the dialog box shows.
3-still in device manager. Scroll down to Universal Serial Bus Controllers. Uninstall Samsung Mobile USB Composite Device.
4-unplug phone.
5-reboot pc.
6-install SAMSUNG USB drivers from their site or from here
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
7-reboot or not. Plug in phone.
This worked for me and no issues for the last 6 days. YMMV..
this works!
stevounit said:
yeah that whole "hardware id missing" was an irritating situation. This is what i recommend as far as making it work.
1. Plug in.
2. When you get the error message, i think its because of a conflict with the adb interface. Go to settings, developer options, and check off usb debugging.
3. Plug in once again and it should work. If not, try toggling between camera and mtp.
I have windows 7 ultimate and it works fine for me :d
Click to expand...
Click to collapse
But why this problem now out of nowhere when everything worked fine before.
Sent from my SPH-L710 using xda app-developers app
Hardware ID missing - SOLVED!!
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
UPDATE!! (Oct.11.2012)
After a few Kies updates and going through various ROM's:
- the procedure listed above works 100% but a few steps are just not needed (redundant) - see bellow
- the problem is mostly caused by Windows "forcefully" trying to install its own drivers, rather than allowing Samsung's suggested.
- Samsung's fault is providing "updated" drivers that don't always work (hence, use the suggested 1.4.6.0 drivers)
- Following EVERY Kies update, DISCONNECT from internet before plugging your phone (otherwise you'll have to go through this, AGAIN).
Some suggested here that plugging the phone into a different USB port (without disconnecting from internet) would be the culprit - which happens to be true, but as a mere effect, not the cause: every time an unknown device is plugged into a different USB port, Windows is trying to download/install the appropriate drivers if it doesn't recognize the hardware - and there you are again.
So, the simplified procedure becomes:
1. Not needed - leave Kies installed, as is - no harm at all
2. N/A
3. YES
4. Not (always) required
5. MUST
6. MUST
7. MUST
8. Yes
Furthermore, if still interested in connecting your I747(M) as UMS (USB mass storage) the solution presented here works. I tested it myself - read my comment on this post for the very few existing hiccups.
- while installing the USB mass storage device drivers you don't have to disconnect from the internet
Install Drivers
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
For someone experiencing the "hardware ID missing" error, just reinstalling the drivers won't do anything. Like many others, I've been banging my head trying to solve this for quite some time; the suggested steps are truly a compilation of successful ideas and trials mingled with tons of frustration, coming from my own experience as well as from many different people and forums.
If, on the other hand, you had a different type of connectivity issues - without this error, then, yes, reinstalling the drivers is Samsung's recommendation.
billard412 said:
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
Click to expand...
Click to collapse
Just wanted to say thank you. Did this and the last 2 days, works everytime. I made sure that after the first time I plugged the phone in after doing all this, and the screen pops up asking what I wanted to do, made sure to check the box for "do this everytime" and then choose the view folder option or whatever that is.
Thank you again,
Whiteice
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thank you so much for this. This solution worked for me.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thanks for this i will try it tomorrow as still new to these tabs.
For moment i change to camera PTP and it pops up, so at least i can use it for now.
Will let you know how i get on.
Best wishes :good:
adamspud said:
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
Click to expand...
Click to collapse
The Android Developers toolkit DOES install the USB drivers 1.4.6.0 - which seems to be the ONLY one that works, BUT the rest of the steps suggested in my previous post are needed in order to get rid of the problem - otherwise the fix is just temporary.
Re-loading OS drivers corrected issue.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
I removed the updates to Kies on my Note and uninstalled the Kies update on the PC which is what started this issue of the OS not recognizing the device and then a fresh driver load for my phone from the Samsung site. Worked Perfectly, Thanks!
Cowoholy
Hello guys
I have a problem with my HTC 10 : I cannot connect it to the computer. I am using the original cable that came in the box but is not working. When I connect the phone to the computer, I can hear the sound that a device was connected but then nothing happens: I cannot see any usb device on the windows tray, I cannot even see it in Device Manager. There is nothing. -this is what happens on the computer . On my phone, after I connect it to the pc, it starts charging, then after 5 seconds it disconnects and connects again to the pc and I get the Slow Charging error on the screen.
This is what I tried so far:
-restart the phone
-restart the computer
-install the htc usb drivers
-install htc sync
-install android sdk dev kit
-enabled usb debugging
-enable oem unlock
-uninstalled udates from gplay and gplay services, restart and try again
-use another cable
All these steps did not changed anything. Still nothing in windows tray, and nothing in device manager.
I did not tried to reset to factory settings tho' . This might be the last resort
I am running Android 7.0, Stock ROM, Neverlocked device.
I am using Windows 8.1 x64 with latest updates.
Is this the first time you connected to the pc?
There seemed to be an issue with HTC driver & Windows 10 (what I am on), but may apply to 8.1 as well. <I got the same problems you had when I first tried messing with an HTC phone a couple years back ..... It is possible Windows or HTC had got this sorted out since.>
What I had to do (a couple years ago now) to get HTC drivers working was this:
1. Install HTC sync, then uninstall it. This leaves the HTC driver on the pc, but without HTC software. HTC sync + android dev kit (adb & fastboot) seemed to cause problems.
2. There was an issue with HTC phone being recognized over USB in Win 10. I have to edit the registry by adding this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
<Open RegEdit, navigate to folder 0BB40FF00100 using path in square brackets, then add the key in second line with the proper hex value. You might want to make a copy of the registry and set a restore point before you mess with the Registry in case things got messed up.>
This had worked for me ever since. <Did that to connect the original ONE, and the 10 connected without any change to the pc.>
Thanks for the answer man. I tried to follow your steps but it seems that I do not have the folder 0BB40FF00100 in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflag
I do not really know how to proceed next.
Sorry, I missed a step. I have to go back to my old post to figure out what I did.
My problem was Win 10 not recognizing HTC devices in fastboot without a registry change. This may or may not be related to your problem.
Since you cannot see the phone in device manager, there may be a broader USB issue. Before you go down my route, I would suggest that:
1. If possible see if you can connect with another computer.
2. Try Windows USB troubleshooter, and uninstalling Window USB driver and reinstalling.
3. Try uninstalling all HTC drivers, and reinstalling using just HTC sync. <Installing HTC sync should install the drivers as well, without having to install some standalone HTC drivers from unknown source.> See if you can see the 10 from HTC sync.
The Registry change idea comes from : https://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
which does mention that this is a Win 8.1 problem, but not a problem in win 8.0
The thread points to the instructions here: https://www.android-hilfe.de/forum/...windows-ab-version-8-1-aktivieren.601686.html
This is in German, and a similar xda thread here: https://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
To edit the registry, you navigate to ....\usbflag,
then you create a key 0BB40FF00100 [ Edit -> New-> Key ]
That creates the key folder, then within the folder, you create a new entry as per the 2nd line. [ Edit -> New -> Binary Value ]
When I connect my Note10+ to my Windows 7 pc, I don't get ANY acknowledgement a device is connected. No beep, popup.. nothing. I did install the Samsung USB drivers, but that's not the issue because there is absolutely no unrecognized devices in the device manager. NO reaction from the PC. Are there any windows services that need to be enabled? Because I do have minimal services enabled.
I can connect a thumb drive thru the same 6ft cable which is kind of old. But not the phone. Could the cable still be bad or not new enough, or short enough? Tried the rear ports also. I don't have any other cables at the moment.
USB debugging is enabled and the phone is set to Transfer Files. Restarted the phone and PC.
Just no beep or popup or anything when I connect the phone. However the phone does charge. The phone is only a month old. Maybe a bad phone port? Is the Note10 USB-C port generally kind of stiff when you first connect the supplied power cable? I never tried to connect it to the PC before.
Thanks.
Try another cable/port.
See if it shows in disk management, hit rescan drives.
Try reloading the drivers manually or automatically depending which you tried first.
If you have SmartSwitch loaded on the PC you should already have the drivers.
Closely review what you disabled and their dependencies!!!
Check Event Viewer for errors.
I have a PC running on W7, my 10+ pops up effortlessly. It could be the C port PCB but don't jump to that conclusion yet. Try a flash stick in it.
Thanks. I have to borrow one. The thumb drive works with the cable, but not the phone. Strange. Connect a thumb drive to the phone??
Going thru my services now. I should get a beep or something.... then I worry about drivers if need be. I scanned for new hardware in device mgr and expanded all trees anyway... nothing. Scanned drives in Disk Mgt... nothing.
If I go to the Samsung desk at BestBuy, will they help free of charge?
Connected thumb drive to phone THRU THE SAME CABLE... Notification says USB Storage Connected, and I can browse through those files.
How do you unmount the thumb drive.. just disconnect the device? EDIT: I got it... "Unmount" in Notif shade.
So the phone port should be good then? Thx.
All I want to do is some ADB commands to disable Doze and remove bloat.
wgraz said:
Connected thumb drive to phone THRU THE SAME CABLE... Notification says USB Storage Connected, and I can browse through those files.
How do you unmount the thumb drive.. just disconnect the device? EDIT: I got it... "Unmount" in Notif shade.
So the phone port should be good then? Thx.
Click to expand...
Click to collapse
I just pull it, the SD card I unmount first.
I don't think it's a port issue.
Try disabling ie turn off Developer options.
The issue seems to be on the PC side.
Services can have a lot of dependencies with far reaching consequences if disabled.
If in doubt renable, reboot, try again.
Something should be logged in Event Viewer when you try to connect.
Could be a driver issue.
On the 10+ you should get a popup asking if you wish to connect if not the 10+ isn't seeing the PC.
Try another PC if possible.
blackhawk said:
I just pull it, the SD card I unmount first.
I don't think it's a port issue.
Try disabling ie turn off Developer options.
The issue seems to be on the PC side.
Services can have a lot of dependencies with far reaching consequences if disabled.
If in doubt renable, reboot, try again.
Something should be logged in Event Viewer when you try to connect.
Could be a driver issue.
On the 10+ you should get a popup asking if you wish to connect if not the 10+ isn't seeing the PC.
Try another PC if possible.
Click to expand...
Click to collapse
OK. Thanks. When I connect, I just get a small silent notif "Chaging connected device via USB" and when I click on it, it says: "USB Controlled by Connected Device" and then "Transferring Files Android / Auto" is greyed out. No popup asking if I wish to connect.
Nothing in Event Viewer. Cleared the Event Viewer, connected the USB, and refreshed the Even Viewer.. Nothing.
wgraz said:
OK. Thanks. When I connect, I just get a small notification: "USB Controlled by Connected Device" and then "Transferring Files Android / Auto" is greyed out. No popup asking if I wish to connect.
Click to expand...
Click to collapse
Never saw that on mine.
Clear the 10+'s system cache.
You disable Developer options?
Try enabling it again.
Hard a reboot (not factory reset!) on the 10+
A settings issue on the PC? Event Viewer, security.
blackhawk said:
Never saw that on mine.
Clear the 10+'s system cache.
You disable Developer options?
Try enabling it again.
Hard a reboot (not factory reset!) on the 10+
A settings issue on the PC? Event Viewer, security.
Click to expand...
Click to collapse
Yes. I tried disabling/enabling Dev. Options. I did a reboot.
wgraz said:
Yes. I tried disabling/enabling Dev. Options. I did a reboot.
Click to expand...
Click to collapse
Try the rest. Hard reboot simulates pulling the battery. Clear the system cache on the boot menu.
I wiped cache partition. nothing.
I should have described the silent notif better. When I connect the cable to the phone (even if not yet connected to PC) the silent notif says:
"Charging connected device via USB" and when I click on it, there's two menus with radio buttons.
First menu: "USB Controlled by:"
1) USB Controlled by Connected Device <--THIS ONE IS SELECTED
2) This Phone.
The second menu: "The USB is for:"
1) Transferring Files Android / Auto <--THIS ONE IS SELECTED but entire menu is greyed out. Controlled in dev. options
2) USB Tethering
3) MIDI
4) Transferring Images
5) Charging Phone only
Factory Unlocked Note 10+ Android 11
Borrowed a cable from my neighbor.. It worked. But it's one thing after another.
Does ADB tools require Microsoft Visual C++ 2015 redist.
Keep getting error: "api-ms-win-crt-runtime-l1-1-0.dll is missing error" when I type adb devices
And to install Microsoft Visual C++ 2015 redist, I need to install Windows6.1-KB2999226-x64.msu and that will not install.
First time ever feeling the pain of still using Windows 7.
wgraz said:
I wiped cache partition. nothing.
I should have described it better.. when I connect, the silent notif says:
"Charging connected device via USB" and when I click on it, there's two menus with radio buttons.
First menu: "USB Controlled by"
1) USB Controlled by Connected Device <--this one is selected
2) This Phone.
The second menu says "The USB is for"
1) Transferring Files Android / Auto <---- this one is selected but the entire menu is greyed out.
2) USB Tethering
3) Midi
4) Transferring Images
5) Charging Phone only This second menu is greyed out and "Transferring Files Android / Auto" is selected.
Click to expand...
Click to collapse
It's grayed out because of the Developer options think.
I'm using the "transfer files" option. I don't get those options, it just asks if I want to connect.
My 10+ is a stock AT&T variant running on Pie.
I haven't used ADB so not sure. If Event Viewer is showing it as missing... you probably need the library. Side by side errors used to be common on x64 machines, missing MS library.
Canon did that. The Developers already had it on their PCs and forgot to include it in the install bundle
blackhawk said:
It's grayed out because of the Developer options think.
I'm using the "transfer files" option. I don't get those options, it just asks if I want to connect.
My 10+ is a stock AT&T variant running on Pie.
I haven't used ADB so not sure. If Event Viewer is showing it as missing... you probably need the library. Side by side errors used to be common on x64 machines, missing MS library.
Canon did that. The Developers already had it on their PCs and forgot to include it in the install bundle
Click to expand...
Click to collapse
Can't use ADB because I need to install one thing after another and I don't have the patience to sit here for hours.
Platform tools requires Microsoft Visual C++ 2015 redist because I'm getting "api-ms-win-crt-runtime-l1-1-0.dll is missing error" when I type adb devices
Microsoft Visual C++ 2015 Redist requires KB2999226 and that won't install either.
I'm going to see if I can brorrow a laptop with win 10.
wgraz said:
Can't use ADB because I need to install one thing after another and I don't have the patience to sit here for hours.
Platform tools requires Microsoft Visual C++ 2015 redist because I'm getting "api-ms-win-crt-runtime-l1-1-0.dll is missing error" when I type adb devices
Microsoft Visual C++ 2015 Redist requires KB2999226 and that won't install either.
I'm going to see if I can brorrow a laptop with win 10.
Click to expand...
Click to collapse
W10 is a dud. W7 should work fine; it shouldn't need any of that to transfer files.
Android 11 may be the perp... I don't know, sorry.
SUCCESS! I used the 15 Seconds ADB Installer as describe here: https://www.droidthunder.com/adb-installer/ Worked like a charm.
The manual ADB platform tools did not work (api-ms-win-crt-runtime-l1-1-0.dll is missing error) probably because I didn't keepup with my win 7 pro system updates. Always hated MS updates because when you reboot, there's other issues you didn't have before or there was more unessessary BS running in the background..
I know windows 10 is a dud. That's why I'm STILL on 7. It's poorly designed and not a true desktop OS. Thanks for all of your help. Wasted a whole day on this.