Welcome back Its good to see you deving again Stop by the Pub some time.For a better experience, please enable JavaScript in your browser before proceeding.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isnt recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USBMSCOMPMTP when USB debugging is enabled and windows doesnt know to use the MTP drivers. I created the following driver.inf file to fix the problem so you can have usb debugging enabled and still have MTP working. This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED. If you cant get MTP working under any circumstance, you have some other problem. Try. This indicates there may be additional issues with the MTP support on the custom ROM side. ADB support (within Recovery) I wanted to get adb working in TWRP and adb sideload working in stock recovery but adb wasnt recognizing the device. The USB IDs for the ADB interface change when you are running Recovery and are no longer recognized by the driver. Youll notice that when you are running TWRP you will see an unknown device called flo. This is actually the ADB USB interfaced but windows doesnt know that. Un Mtp Usb Device Zip The GoogleUnzip the Google drivers and replace the androidwinusb.inf file in the Google drivers with the one in the attachment. ![]() Un Mtp Usb Device Driver Installation GuideFirst opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - 18d1 or. ![]() When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on. Let me know if there are any issues and Ill try to address. USB debugging enabled and stock ROM EDIT: I removed the following file since it appears the issue with MTP on Paranoid is on the ROM side. The USB IDs were different and the driver inf I provided was able to get the windows side to recognize the MTP device and associate the MTP drivers, but when the MTP driver tried to initialize the MTP device, it wasnt responding properly. There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions. Im a little suprised if your win8 install is showing MTP as a compatible driver, why it didnt just auto-install this from the beginning wo user intervention The problem some folks are encountering (at least on older windows) is that since the tablet no longer advertises USBMSCOMPMTP in the compatible ID list, windows doesnt know what type of device this is, thus it doesnt provide you with any device drivers to use.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |