My Win 7x64 don't detect TPT while in debug mode.
Why is that? I think, all with adb driver should be OK!?!
Now I cannot root my TPT
Does anyone has the same problem?
Did you try a reboot. I had no issue with my w7x64.
Me neither. Switch USB cables and usb ports and computers
I think, problem is not at the PC/win7x64.
After update to OTA 2.5 and also to ICS - no more TPT in debug mode!?!
Before that i was able to view my TPT in recovery mode under MTP Devices, but not yet!?!?
Related
I have been trying to flash CW Recovery to my TPT for a few days now and I just figured out why I kept getting the "device not found" error in CMD.
I have the TPT ADB drivers installed. When my TPT is in storage mode when connected VIA USB, the drivers are there, but when I do charge only mode, device manager says that the drivers are not found and when I try to install them again from a specific folder, it can't.
Why is this happening?
R: [Q] ADB Drivers work only in storage mode, not charge mode.
Probably the reason is that "charge only" mode keeps only the power wiring of the circuit active, while all the logic is switch off, so you don't having any device connected but only a charging tablet. Why do you switch to charge only?
Sent from Lenovo Thinkpad Tablet on Koshu CM10 ROM 0.9.1
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
What does this mean? Bricked beyond repair?
- dd
ddbug said:
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
Click to expand...
Click to collapse
I'm assuming that you mean MTP (Media Transfer Protocol)?
I'm assuming this means that you are booting Android as I'm not aware of the device being represented as anything but an APX device (0955:7820) if you do not.
What is the problem?
ddbug said:
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
Click to expand...
Click to collapse
When in APX mode Android is not loaded so you cannot use ADB (Android Debug Bridge). It should not really matter as, from what I recall, PBJ20upgrade will only use ADB to reboot the device into AXP mode.
Thank you eppeP,
Yes, it was MTP.
So I'll try to proceed with PBJ20upgrade.
(am away now for a week or so ... )
-- dd
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Roland
Rolandh said:
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Click to expand...
Click to collapse
Look in your PC's Control Panel - do you see Portable Devices (it's most likely missing or not showing up)
Folks over at Nexus 5 (I owned both devices) are running into similar problems - long story short, it's corrupted and/or missing usb devices drivers. Simplistic solution, use the computer (assuming you are running Windows 7 or Vista and not Linux) SYSTEM RESTORE feature & roll back to last few days, it should be a successful effort & then reboot. Reconnect your device, let it sit & recognize the device, install drivers, etc. - do this with USB debugging OFF first, and when it is done - enable USB debugging, let it finish.
Now, reboot PC again to be sure, and connect. usb cable again - give it 3 to 5 seconds, your Auto Play should be popping up with prompt to open folders/files, etc.
Check your CP again, you should now see Portable Devices part of the hardware, and Google Nexus 4 (yes, that's what is on mine)
Let me know if this solution works for you - the alternative is to uninstall all usb drivers, reboot, install, etc. etc. Please post your results if you choose to follow this dummy's approach, thanks.
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
extremeinside said:
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
Click to expand...
Click to collapse
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Pieter20 said:
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Click to expand...
Click to collapse
I am also facing same problem...please help me
Does the stock recovery even have adb capabilities?
Windows 10 Pro X64
A2017U B19
OEM Unlock On
USB Debugging On
I've installed the Qualcomm drivers. Reboot into EDL Mode
Connect USB Cable
Shows up as Handset Diagnostic Mode DFU
Won't recognize the driver when I manually point it to the driver folder
If I unplug my ethernet cord things get interesting
Shows up as some unknown Qualcomm Device
Still won't take the drivers no matter what I do.
What the heck do I do!?!?!
kaivorth said:
Windows 10 Pro X64
A2017U B19
OEM Unlock On
USB Debugging On
I've installed the Qualcomm drivers. Reboot into EDL Mode
Connect USB Cable
Shows up as Handset Diagnostic Mode DFU
Won't recognize the driver when I manually point it to the driver folder
If I unplug my ethernet cord things get interesting
Shows up as some unknown Qualcomm Device
Still won't take the drivers no matter what I do.
What the heck do I do!?!?!
Click to expand...
Click to collapse
You are on DFU mode, installing that driver won't help. You have to disassemble the phone.
Follow my DFU Unbrick guide on the Guides section.