- Using Usb For Debugging Waiting To Reconnect Windows 10
- Using Usb For Debugging Waiting To Reconnect Computer
- Using Usb For Debugging Waiting To Reconnect Iphone
If you’ve ever tried to do anything advanced on your Android phone, you’ve likely heard (or read) the term “USB Debugging.” This is a commonly-used option that’s tucked away neatly under Android’s Developer Options menu, but it’s still something that many users enable without giving it a second thought–and without knowing what it really does.
For example, if you’ve ever had to use ADB (the Android Debugging Bridge) to do things like flash a Factory Image on a Nexus device or root a device, then you’ve already used USB Debugging, whether you realized it or not.
In short, USB Debugging is a way for an Android device to communicate with the Android SDK (Software Developer Kit) over a USB connection. It allows an Android device to receive commands, files, and the like from the PC, and allows the PC to pull crucial information like log files from the Android device. And all you have to do is tick a button to make it happen. Neat, right?
Of course, everything has a downside, and for USB Debugging, it’s security. Basically, leaving USB debugging enabled keeps the device exposed when it’s plugged in over USB. Under most circumstances, this isn’t a problem—if you’re plugging the phone into your personal computer or you have the intention of using the debugging bridge, then it makes sense to leave it enabled all the time. The problem comes into play if you need to plug your phone into an unfamiliar USB port—like a public charging station. In theory, if someone had access to the charging station, they could use USB debugging to effectively steal private information from the device, or push some sort of malware onto it.
The good news is that Google has a built-in safety net here: per-PC authorization for USB Debugging access. When you plug the Android device into a new PC, it will prompt you to approve a USB debugging connection. If you deny access, the connection is never opened. It’s a great failsafe, but users who may not know what it is may just approve the connection all willy-nilly, which is a bad thing.
RELATED:The Case Against Root: Why Android Devices Don’t Come Rooted
The other thing to consider is device security should it get lost or stolen. With USB Debugging enabled, any would-be wrong-doer could effectively have access to everything on the device--even if it has a protected lock screen. And if the device is rooted, you might as well give it up: there’s really nothing to stop them at that point. In fact, you should probably make sure you have the Android Device Manager installed on every device you own, that way if it does get lost or stolen you can remotely wipe your data.
Honestly, unless you’re a developer, you probably don’t need to leave USB Debugging enabled all the time. Enable it when you need to use it, then disable it when you’re finished. That’s the safest way to handle it. Sure, it’s slightly inconvenient. but it’s worth the trade-off.
READ NEXT- › How to Speed Up Your PlayStation 4’s Downloads
- › How to Disable the Login Screen’s Background Blur on Windows 10
- › How to Use All Linux’s Search Commands
- › How to See All Your Saved Wi-Fi Passwords on Windows 10
- › How Do Bone Conduction Headphones Work?
I am trying to do Windows kernel debugging so I have set up two machines for this purpose:
- HOST - DEBUGGER - The computer that runs the windbg debugger
- TARGET - DEBUGEE - The computer being debugged
Both HOST and TARGET runs Windows 7 32 bit and both have Windows Driver Kit 8.0 installed. I did the following steps:
On TARGET I've enabled kernel debugging with following commands:
Then I've started HOST and did the following steps:
- start windbg
- File->Kernel Debug->COM
- Baud Rate: 115200, Port: COM1, Pipe: Unchecked, Reconnect:Unchecked, Resets: 0
- OK
After this my windbg command window on HOST looks like this:
Then I've restarted TARGET and choose 'Windows 7 with debug' from the boot menu.
After this my windbg command window on HOST looks like this:
But instead of prompt where usually commands are typed I get:
Debuggee not connected.
The TARGET system started as usual and I was able to use it.Few things I've noticed:
- COM1 port was missing on TARGET machine in Device Manager afterabove steps.
- After closing windb on HOST machine and attempting to restart the TARGET it get stuck with 'Shutting Down' message so I have to do a force power off.
- After booting TARGET to 'old' kernel without debugging enabled serial port is available in Device Manager.
- After booting TARGET to 'new' kernel with debugging enabled (and without HOST listening) serial port is unavailable in Device Manager.
What i am doing wrong?
PS: Both machines are virtual guests on XEN.PPS: Connection is 100% working, tested on kernel with no debugging enabled and with putty
EDIT:
Title changed.
According to this article My Kernel Debugger Won't Connect it is OK that COM1 is missing:
By checking Device Manager I was able to confirm that there was a problem with the configuration of the OS running in the VM. The bcdedit settings were configured to use COM1, and this should make COM1 unavailable in the OS, however, COM1 was present in device manager. For some reason the debugger was not capturing COM1 on boot as it was configured to.
I've also checked the settings described in mentioned article but they seems to be OK also:
EDIT2
Based on this SO answer I've tried issue
kd -kl
command. I suppose it should be issued only on target but to be sure I've tried both machines. You can see that there is an error regarding symbols but I think debugging should be working without them also.HOST:
TARGET:
There are also some recommendations about setting printer sharing etc. are they worth trying?
Community♦
Wakan TankaWakan Tanka2,63655 gold badges3434 silver badges7676 bronze badges
2 Answers
It looks like you got the debugger attached to the target. (1) Ignore WinDbg status message. The best way to see if you're connected to the target is to try a few commands. (2) When I debug a virtual machine, the serial port that I'm using also goes missing, but it looks like you figured that out (good job).
In order to issue commands you need to break into the kernel. Click 'Debug->Break' and try the following commands:
That should give you the target system computer name.
If you want to learn more about kernel debugging, I would check out TheSourceLens on YouTube. As for literature, I can't recommend any books, because most information I find are online. However, I would recommend checking out OSR Online. Happy debugging.
tchau.devtchau.dev
You can try Bellavista.exe to create a new debug entry and look for the differences.
zapadorzapador40711 gold badge88 silver badges1717 bronze badges
Not the answer you're looking for? Browse other questions tagged windowsdebuggingkernelwindbg or ask your own question.
-->There are two ways you can use WinDbg to initiate a live kernel-mode debugging session.
WinDbg Menu
When WinDbg is in dormant mode, you can begin a kernel debugging session by choosing Kernel Debug from the File menu or by pressing CTRL+K. When the Kernel Debugging dialog box appears, click the appropriate tab: NET, 1394, USB, COM, or Local. Each tab specifies a different connection method. For more information about the dialog box and its entries, see File | Kernel Debug.
Command Prompt
In a Command Prompt window, you can initiate a kernel-mode debugging session when you launch WinDbg. Enter one of the following commands:
windbg [-y SymbolPath] -k net:port=PortNumber,key=Key[,target=TargetIPAddress|TargetMachineName]
windbg [-y SymbolPath] -k 1394:channel=1394Channel[,symlink=1394Protocol]
windbg [-y SymbolPath] -k usb:targetname=USBString
windbg [-y SymbolPath] -k com:port=ComPort,baud=BaudRate
windbg [-y SymbolPath] -k com:pipe,port=VMHostpipePipeName[,resets=0][,reconnect]
windbg [-y SymbolPath] -k com:modem
windbg [-y SymbolPath] -kl
windbg [-y SymbolPath] -k
For more information, see WinDbg Command-Line Options.
Environment Variables
For debugging over a serial (COM port) or 1394 connection, you can use environment variables to specify the connection settings.
Use the following variables to specify a serial connection.
set _NT_DEBUG_PORT = ComPort
set _NT_DEBUG_BAUD_RATE = BaudRate
Use the following variables to specify a 1394 connection.
set _NT_DEBUG_BUS = 1394
set _NT_DEBUG_1394_CHANNEL = 1394Channel
set _NT_DEBUG_1394_SYMLINK = 1394Protocol
For more information, see Kernel-Mode Environment Variables.
Parameters
SymbolPath
A list of directories where symbol files are located. Directories in the list are separated by semicolons. For more information, see Symbol Path.
A list of directories where symbol files are located. Directories in the list are separated by semicolons. For more information, see Symbol Path.
PortNumber
A port number to use for network debugging. You can choose any number from 49152 through 65535. For more information, see Setting Up a Network Connection Manually.
A port number to use for network debugging. You can choose any number from 49152 through 65535. For more information, see Setting Up a Network Connection Manually.
Key
The encryption key to use for network debugging. We recommend that you use an automatically generated key, which is provided by bcdedit when you configure the target computer. For more information, see Setting Up a Network Connection Manually.
The encryption key to use for network debugging. We recommend that you use an automatically generated key, which is provided by bcdedit when you configure the target computer. For more information, see Setting Up a Network Connection Manually.
TargetIPAddress
The IPv4 address of the target machine.
The IPv4 address of the target machine.
When the target= IP address is specified, this causes the debugger to initiate a connection to the specified target machine, by sending a special packet to the target, that will cause it to attempt to connect with that debugger. The debugger will send packets to the target repeatedly approximately every half second, attempting to connect. If the connection is successful, the target will drop any existing connection, and communicate only with this instance of the debugger. This allows you to take control of the debugging session away from an existing debugging connection.
When the target is configured with a host IP address, and the debugger is being run on the machine with the configured host IP address, there is no need to specify the target= IP address parameter. When the target is configured with a host IP address, it will send OFFER packets to the host every three seconds. The OFFER packets allow the debugger to connect to the host when no target= IP address is specified.
For more information on configuring the host IP address on the target, see Setting Up KDNET Network Kernel Debugging Automatically and Setting Up KDNET Network Kernel Debugging Manually.
TargetMachineName
The machine name of the target PC. To use the machine name, the DNS system on the network must have the machine name associated with the IP address of the target PC.
The machine name of the target PC. To use the machine name, the DNS system on the network must have the machine name associated with the IP address of the target PC.
1394Channel
The 1394 channel number. Valid channel numbers are any integer between 0 and 62, inclusive. 1394Channel must match the number used by the target computer, but does not depend on the physical 1394 port chosen on the adapter. For more information, see Setting Up a 1394 Connection Manually.
The 1394 channel number. Valid channel numbers are any integer between 0 and 62, inclusive. 1394Channel must match the number used by the target computer, but does not depend on the physical 1394 port chosen on the adapter. For more information, see Setting Up a 1394 Connection Manually.
1394Protocol
The connection protocol to be used for the 1394 kernel connection. This can almost always be omitted, because the debugger will automatically choose the correct protocol. If you wish to set this manually, and the target computer is running Windows XP, 1394Protocol should be set equal to 'channel'. If the target computer is running Windows Server 2003 or later, 1394Protocol should be set equal to 'instance'. If it is omitted, the debugger will default to the protocol appropriate for the current target computer. This can only be specified through the command line or the environment variables, not through the WinDbg graphical interface.
The connection protocol to be used for the 1394 kernel connection. This can almost always be omitted, because the debugger will automatically choose the correct protocol. If you wish to set this manually, and the target computer is running Windows XP, 1394Protocol should be set equal to 'channel'. If the target computer is running Windows Server 2003 or later, 1394Protocol should be set equal to 'instance'. If it is omitted, the debugger will default to the protocol appropriate for the current target computer. This can only be specified through the command line or the environment variables, not through the WinDbg graphical interface.
USBString
A USB connection string. This must match the string specified with the /targetname boot option. For more information, see Setting Up a USB 3.0 Connection Manually and Setting Up a USB 2.0 Connection Manually.
A USB connection string. This must match the string specified with the /targetname boot option. For more information, see Setting Up a USB 3.0 Connection Manually and Setting Up a USB 2.0 Connection Manually.
ComPort
The name of the COM port. This can be in the format 'com2' or in the format '.com2', but should not simply be a number. For more information, see Setting Up a Serial Connection Manually.
The name of the COM port. This can be in the format 'com2' or in the format '.com2', but should not simply be a number. For more information, see Setting Up a Serial Connection Manually.
BaudRate
The baud rate. This can be 9600, 19200, 38400, 57600, or 115200.
The baud rate. This can be 9600, 19200, 38400, 57600, or 115200.
VMHost
When debugging a virtual machine, VMHost specifies the name of the physical computer on which the virtual machine is running. If the virtual machine is running on the same computer as the kernel debugger itself, use a single period (.) for VMHost. For more information, see Setting Up a Connection to a Virtual Machine.
When debugging a virtual machine, VMHost specifies the name of the physical computer on which the virtual machine is running. If the virtual machine is running on the same computer as the kernel debugger itself, use a single period (.) for VMHost. For more information, see Setting Up a Connection to a Virtual Machine.
PipeName
The name of the pipe created by the virtual machine for the debugging connection.
The name of the pipe created by the virtual machine for the debugging connection.
resets=0
Specifies that an unlimited number of reset packets can be sent to the target when the host and target are synchronizing. This parameter is only needed when debugging certain kinds of virtual machines.
Specifies that an unlimited number of reset packets can be sent to the target when the host and target are synchronizing. This parameter is only needed when debugging certain kinds of virtual machines.
reconnect
Causes the debugger to automatically disconnect and reconnect the pipe if a read/write failure occurs. Additionally, if the named pipe is not found when the debugger is started, the reconnect parameter will cause it to wait for a pipe of this name to appear. This parameter is only needed when debugging certain kinds of virtual machines.
Causes the debugger to automatically disconnect and reconnect the pipe if a read/write failure occurs. Additionally, if the named pipe is not found when the debugger is started, the reconnect parameter will cause it to wait for a pipe of this name to appear. This parameter is only needed when debugging certain kinds of virtual machines.
-kl
Causes the debugger to perform local kernel-mode debugging. For more information, see Local Kernel-Mode Debugging.
Causes the debugger to perform local kernel-mode debugging. For more information, see Local Kernel-Mode Debugging.
Examples
The following batch file could be used to set up and start a debugging session over a COM port connection.
The following batch file could be used to set up and start a debugging session over a 1394 connection.
The following command lines could be used to start WinDbg without any environment variables.
windbg -y d:mysymbols -k com:port=com2,baud=57600
windbg -y d:mysymbols -k com:port=.com2,baud=115200
windbg -y d:mysymbols -k 1394:channel=20,symlink=instance
windbg -y d:mysymbols -k net:port=50000,key=AutoGeneratedKey
windbg -y d:mysymbols -k net:port=50000,key=AutoGeneratedKey,target=TargetIPAddress
Related topics
My mouse will reconnect/disconnect (will even hear the sounds from Windows), and the light on the bottom of the mouse will turn off/turn on as it starts working again.
It really sucks to be playing a game (and happens on desktop as well) for the mouse to just die out for a few seconds and come back. Sometimes it will not happen for days and other times it will do it two or more times within 15 seconds.
I tried two different wired mice, tried multiple USB ports (on the front of the computer, back of the computer, used a USB hub and plugged in a card that connects to the USB connectors on the motherboard and adds a few USB ports to the back of the computer, and I also bought a USB 2.0 PCI card and that did not help).
Nothing else seems to reconnect like this, my USB keyboard has never once cut out like the mouse does and neither have any of the other devices I have connected (webcam, USB hub, various devices sometimes connected through USB cables, and IR receiver for windows Media Center remote). I have disconnected all USB devices except for my keyboard and mouse and the problem still occurs.
I guess it could be something wrong with my motherboard but since no other devices behave similarly I'm just hoping that it is some kind of driver conflict. Installing Logitech's drivers has had no effect. It seemed at first that if I go to Device Manager and uninstall HID-compliant mouse (that and Logitech mx518 are listed) that would fix it, but it doesn't seem to work anymore or at least not every time (it keeps re-installing).
I have googled 'USB mouse disconnects and reconnects', and it seems to be fairly common but none of those were resolved.
To stick some easy steps:
- It happens with or without the drivers installed
- It has happened with multiple mice on the same computer
- The BIOS is the latest version (P08)
- Motherboard drivers are the latest version
- Device Manager isn't listing any problems on any USB devices
- Happens with every USB port, even addon USB cards
- Happens when all USB devices aside from mouse and keyboard are unplugged
I read that maybe it is an IRQ conflict, and I tried to look into that but did not really know what was going on, but didn't see anything obviously wrong.
Specifications:
- Q6600 CPU
- EVGA 780I SLI motherboard
- 4 GB RAM
- Logitech MX-518 mouse
- Windows 7 64-bit
- EVGA GTX 260 screen card
- 650 W power supply (single rail).
69.3k5050 gold badges236236 silver badges288288 bronze badges
Marc
8 Answers
If you're experiencing mouse lockups or failures, it may be because your computer is automatically turning off the power to a USB Root Hub.
- Go to your Control Panel > System > Hardware tab > and click on the 'Device Manager' button.
- In the Device Manager window, find the item or items labeled 'Universal Serial Bus controllers.' Open it, and double-click the first item called 'USB Root Hub.'The Windtunnel, along with Autosculpt, can affect a car's performance. It is not available on Wii and PlayStation 2 versions. Many of the races take place on well-known roads. Need for speed pro street pc direct download link.
- In the USB Root Hub Properties dialog, click on the 'Power Management' tab.
- 'Allow the computer to turn off this device to save power' is checked by default. Uncheck this box, and click 'OK.'
If this does not work, do the same for the USB Input Device - uncheck the box 'allow the computer to turn off this device to save power. (this worked for me) and stopped the annoying way the mouse would go in and out.
Supposedly this can be caused by registry corruption:
This issue can occur when the device enumerator located at HKEY_LOCAL_MACHINESYSTEMCurrentControlSet gets corrupted. As a result, the mouse attached to the USB controller is duplicated and the system gets confused. Periodical attemtps to remove the dupe are discarded after re-detecting the mouse attached to the controller.
That page recommends a system restore or uninstalling the USB device in Device Manager.
In addition to uninstalling the device itself, you can uninstall all the USB root hubs on your machine, and they will be reinstalled after a reboot, as recommended in this HP article USB devices are detected by Windows but are not working properly:
..
5.Double-click Universal Serial Bus Controllers to expand the list.
6.Right-click the first USB Root Hub in the list and then select Uninstall . Continue uninstalling all USB Root Hubs.
..
5.Double-click Universal Serial Bus Controllers to expand the list.
6.Right-click the first USB Root Hub in the list and then select Uninstall . Continue uninstalling all USB Root Hubs.
..
You can also uninstall all previous instances of the device (and the root hubs) using a tool like USBDeview. It will show you all devices that have ever been installed, even if they aren't currently plugged in, and you can uninstall them from there, so the 'detected new hardware' thing will pop up the next time you plug it in. Sort them by vendor ID, select everything related to that product, right click, and uninstall them all.
I'm not sure if the registry corruption is truly the cause, and I'm not sure if this actually fixes it, but it's worth a try. It seems to be working for my most recent experience with this problem.
endolithendolith3,3341919 gold badges6262 silver badges107107 bronze badges
From what you describe, nothing immediately comes to mind what the cause of the issue you are observing might be.
A few things to keep in mind:
- The longer it takes to reproduce the failure, the longer it'll take to debug unless you are lucky. Your best bet is to try to find a way to reproduce the failure as quickly as possible.
- You can count on experience and a consistent method of debugging (i.e. the 'shotgun' debugging approach rarely produces the expected results -- not that I'm saying that is what you are using).
Typically, I would start with a minimum system setup to rule out the variables (1 CPU, 1 CPU Fan, 1 DIMM, 1 Video Card, 1 Hard Drive, 1 Power Supply, etc.). It is best if you have all 'known good' components. Then, try to rule out subsystems. Unfortunately, at home you likely have limited tools and resources, so you have to improvise smartly.
Rule out the OS/drivers (easy if you have spare CD's & hard drives):
- Does this happen when you run the system from a Linux boot CD?
- Does this happen with any other OS installed?
- Does this happen with a clean install of your current OS?
Rule out the keyboard and mouse:
- Do your keyboard and mouse/mice always work on a another system?
Rule out the motherboard power rails:
- Does the 5V rail at the USB slots stay near 5V or does it dip (a meter may tell you this, but an oscilloscope can give you a better idea if the power rail dips)?
- What does the 5V rail look like on the PCI USB card?
This answer might now solve your problem, but hopefully it'll move you towards finding the cause of the issue.
You can try to uninstall the mouse completely and let Windows re-install it.
Go to Control Panel and into Mouse → Hardware Tab → Properties → Hardware Tab >Uninstall
This will make your mouse stop working, so use your keyboard to restart your computer.When it loads, your mouse should be working fine.
If it happens with several mice and several USB interfaces, that leaves software. Are you using the Windows default HID driver for mice? You might try installing the latest software from Microsoft: http://www.microsoft.com/hardware/windows7/support.mspx
This is a regular USB mouse, not a wireless one, right?
How does it behave after a clean boot?http://support.microsoft.com/kb/929135
I had the exact same problem with two 1600 MX-518 mice.
After the first one did that that I called Logitech support and they asked me the problem, asked for the serial number and then shipped me a new one free of charge. This happened again with my second one, but I did same thing and they shipped me a new 1800 DPI MX518. This is the mouse I am using now for over two years and it's been great.
Using Usb For Debugging Waiting To Reconnect Windows 10
I know I applied a lot of pressure to the cord of my mouse, and that could be the reason for it.
Here is Logitech's support website, and if your mouse is still under warranty, I highly recommend Logitech support.
- Look at the Windows event logs to see if there is any indication of a service/driver failure.
- Look at the motherboard settings for integrated peripherals.
Check the setting for USB on chip support. The manual is not clear on the meaning, however, I did have a system that when legacy (1.1 & 2) was enabled, USB devices would disconnect.From the manual I cant tell for sure what the setting on this motherboard means. If you disable on chip the keyboard and mouse are forced to enabled (according to manual) this would seem to imply the enabled setting allows access to other USB devices outside of windows (like boot from USB).
In my case, the problem became less severe when I started using a different USB slot.
William JockuschWilliam Jockusch1,32377 gold badges2121 silver badges4040 bronze badges
protected by BinaryMisfitNov 26 '10 at 8:23
Using Usb For Debugging Waiting To Reconnect Computer
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Would you like to answer one of these unanswered questions instead?
Using Usb For Debugging Waiting To Reconnect Iphone
- STOREProduct FamilyTop Products
- DATA RECOVERY SOFTWARE
- Windows Data Recovery Software »
- MS SQL RecoveryBuyTry
- Exchange Recovery Download
- Mac Data Recovery Software »
- iOS Data Recovery Software »
- Android Data Recovery Software »
- Android Data Recovery App
Fast, complete and safe hard drive data recovery software to recover your data in easy steps.Best Mac data recovery software recovers whatever you lost from Mac machines & storage devices. - PARTITION MANAGER
- For Business »
- For Home & Home Office »
- For Service Provider »
- Editions Comparison »
All-in-one partition manager software can safely and simply resize partitions for PC.Professional server partition software for Windows Server system. - BACKUP & RESTOREWindows Backup Software
- For Home & Home Office »
- For Business »
- For Service Provider »
- Management & Deployment
- Backup CenterBuyTry(Central Management Console)
- Business Backup Solution
- Customize your backup and central management solutions to enjoy the maximum discount.Learn More
- Editions Comparison »
Mac Backup SoftwareSmall business backup solution to protect your PC, laptop or workstation from disaster.Windows server, exchange and SQL Server backup solution to ensure business continuity. - DATA TRANSFER
- PC Transfer »
- Phone Transfer »
- iPhone Data Transfer Free
- iPhone Data Transfer Pro
Transfer and manage photos, music, videos, contacts and other files on iOS 11/10/9/8 devices easily.Need easy iPhone data transfer software? EaseUS MobiMover Free - Transfer and manage your iPhone dataLEARN MORE - UTILITIES
- Disk/Partition Copy »
- System Optimization
- File Sync
The best disk/partition clone solution helps to copy your disk/partition within a few clicks