Related
I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse
I cannot get ADB to recognize my Note 7. I've installed the ADB & FastBoot 15-second install from the XDA forum, but when I plug my N7 into the PC it only recognizes it as a USB drive.
Dev options enabled,
USB Debugging enabled
USB configuration (MTP mode)
The only entries under Other in Device Manager are CDC and MTP, no Android Device. The phone is also listed under Portable Devices. No USB mode brings up "Android" in the list of devices under Other.
Does anyone have any suggestions?
Do you have proper Samsung usb drivers installed? Check your device manager, just asking sometimes phones can be finicky when trying to get the PC to recognize devices.
Thanks carelockh! That did the trick. I looked in Device Manager and found that only the Windows USB device driver was installed. I downloaded and installed the Samsung driver and was able to connect over ADB.
No problem, anytime glad I could help.
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.
Hi guys,
I'm trying to connected to Nexus 6P (8.1) from my Pc
I connect it and it charges, but there's no ability to see its files. I've tried the following:
Changing USB Configuration in Developer Options to/from MTP.
Switching USB ports on computer (neither USB 2.0 / 3.0 Nothing)
Switching computers ( no luck)
Switching cables (no luck)
Switching Windows 10/7 (no luck)
Looking for the device manager on Windows- doesn't show up
Enabling/disabling USB debugging
Downloading Nexus Root Toolkit to download drivers (says "ADB device was not found." USB debugging has no effect)
Please help!
Hello,
I bought the android box 12 T95MAX H618, the box boot looped when I received it (it turns on and after 5 seconds restarts).
I managed to get the stock firmware and I reflash it with Pheonix card, but it continues, if I unplug the box or leave it off for more than 5 seconds it boots in a loop.
I tried to connect the ox to the pc with phoenix suit and phoenix USB pro but they do not detect my box, while in windows it detects the box but marks me as an unknown device.
Do you have a solution to stop restarting in a loop?
which Android version? can you show pictures of the tvbox?
donmega_icecube said:
which Android version? can you show pictures of the tvbox?
Click to expand...
Click to collapse
the T95MAX runs on android 12, and here is a photo of the model.
and the stock firmware link: https://mega.nz/file/Vpsl1RQQ#pwUFrrZOGTgvzjoUpuoOHiO9dG3UkwWRB5V7bBDaDVU
I can't connect the box to the pc, I use a usb A -> usb A cable.
1 I connect the usb port on the pc but not the boxing and I disconnect all the other cables.
2 I keep pressing the reset button in the AV port
3 I connect the usb port on the box
I hear a sound like what the box are plug and in the device manager I see this:
"Unknown USB device: Device descriptor request failed"
Everything I tried but didn't work.
- Connected turn on usb debugging mode
-All the usb ports of the pc
-Install drivers
Do you have a solution I'm desperate
johnjohn07 said:
I can't connect the box to the pc, I use a usb A -> usb A cable.
1 I connect the usb port on the pc but not the boxing and I disconnect all the other cables.
2 I keep pressing the reset button in the AV port
3 I connect the usb port on the box
I hear a sound like what the box are plug and in the device manager I see this:
"Unknown USB device: Device descriptor request failed"
Everything I tried but didn't work.
- Connected turn on usb debugging mode
-All the usb ports of the pc
-Install drivers
Do you have a solution I'm desperate
Click to expand...
Click to collapse
first thing you need plugin your box again to the computer, then you need to start to remove all unknown usb devices from your device manager, you may need to click on "view > show hidden devices" in device manager to see all unknown usb devices, remove them all, then disconnect your box.
if you have anything in your programs related to drivers for your box, uninstall them before you plug the box back in.
if this is a desktop computer, try to avoid front usb ports if possible.
if you have a second A-A USB cable, test with that if possible.
now before you plugin your box, you need to install the correct drivers, normally the manufacturer or your supplier can give you those, don't download any random T95Max drivers online because there are at least 3 different models of T95Max tvboxes as far as I know, and yours is a newer model.
after installing the drivers, then follow these steps exactly:
- unplug all cables from the tvbox
- plug in one end of the USB cable to the computer only
- have the firmware flashing software open
- press and hold the reset button which is usually placed inside the AV port in most boxes
- while holding the reset button, plugin only the USB cable, then release the reset button
if it's detected correctly, you can move on with the rest of the steps, if it's not detected, then unplug it and repeat the steps but this time plug the USB cable to a different port on the tv box, because not all ports support firmware flashing.
- i'm sure you know the remaining steps since you have the firmware and probably the software for flashing the firmware.
if you try all ports on the tv box and still not working, I would probably still try on a different computer, if that fails as well, then all I could say it might be a defective box, you could maybe try the sdcard method if possible on your tv box, or contact the supplier where you got it from
good luck
donmega_icecube said:
first thing you need plugin your box again to the computer, then you need to start to remove all unknown usb devices from your device manager, you may need to click on "view > show hidden devices" in device manager to see all unknown usb devices, remove them all, then disconnect your box.
if you have anything in your programs related to drivers for your box, uninstall them before you plug the box back in.
if this is a desktop computer, try to avoid front usb ports if possible.
if you have a second A-A USB cable, test with that if possible.
now before you plugin your box, you need to install the correct drivers, normally the manufacturer or your supplier can give you those, don't download any random T95Max drivers online because there are at least 3 different models of T95Max tvboxes as far as I know, and yours is a newer model.
after installing the drivers, then follow these steps exactly:
- unplug all cables from the tvbox
- plug in one end of the USB cable to the computer only
- have the firmware flashing software open
- press and hold the reset button which is usually placed inside the AV port in most boxes
- while holding the reset button, plugin only the USB cable, then release the reset button
if it's detected correctly, you can move on with the rest of the steps, if it's not detected, then unplug it and repeat the steps but this time plug the USB cable to a different port on the tv box, because not all ports support firmware flashing.
- i'm sure you know the remaining steps since you have the firmware and probably the software for flashing the firmware.
if you try all ports on the tv box and still not working, I would probably still try on a different computer, if that fails as well, then all I could say it might be a defective box, you could maybe try the sdcard method if possible on your tv box, or contact the supplier where you got it from
good luck
Click to expand...
Click to collapse
my box t95MAX is well detected by my pc but in the device manager there is written
"Unknown USB device: Device descriptor request failed"
How to solve this problem?
Maybe I need special drivers?
johnjohn07 said:
my box t95MAX is well detected by my pc but in the device manager there is written
"Unknown USB device: Device descriptor request failed"
How to solve this problem?
Maybe I need special drivers?
Click to expand...
Click to collapse
My friend, this exactly means it's the drivers aren't installed, that's why I sent you the steps you need to follow.
Also you can't say it's well detected if it shows unknown usb device in control panel, hearing your computer making a ding sound doesn't always mean it's a good thing
I bought this same exact box, but my issue has been not being able to install Teamviewer QS nor the Host file. I downloaded that stock firmware image and tried burning it onto a microSD card, but I kept getting failed to load error. After doing further research, it turns out you need to install MS Visual C++ Redistributal Runtimes. I downloaded the all in one file which installs all the Redistributal files.
Then using PhoenixCard Tool (v4.24), I burned the image onto the microSD card. BTW, when the process is done, you'll see many partitions were created on the card. I unplugged the power to the box, popped in the microSD card, plugged the power back in and upgrade process automatically started. It booted back up, screen loaded up all the software and all was running. Teamviewer apps still won't run though.
I wish there was a way to downgrade to Android 11, 10, or even 9. Good luck!