Database Info

[Solved] 32B USB-->PC problems (ADP1 works great)

Hi all,
I'm having some strange difficulties with - what i think are - the drivers for the Magic (32B). I cannot for the life of me connect the darned device to my PC in any way (well, apart from the storage option)! My ADP1 works 100% with adb/fastboot and whatnot and i'd really like it if the Magic would as well.... Both phones run the same version CM and i use the same cables/computer every time, both phones are set up the same (USB debugging and such) and both have an engineering bootloader but the Magic will not be recognized by my computer!
I've tried all and every driver i could find incl. the drivers that came with adb and the latest drivers from HTC Sync but all fail bad (the 'Android Bootloader interface' and 'MyHTC' drivers both give me a 'This device cannot start. (Code 10)' error...).
Now, i got it all working.... once... about a month ago to root the device and all and i cant remember changing anything since then but for some reason it simply doesn't work anymore. Has anyone here had similar experiences or any insights on how to fix this?
Help would be very much appreciated!!

So nobody knows? Hrm, im still having these difficulties...

maarten82 said:
Hi all,
I'm having some strange difficulties with - what i think are - the drivers for the Magic (32B). I cannot for the life of me connect the darned device to my PC in any way (well, apart from the storage option)! My ADP1 works 100% with adb/fastboot and whatnot and i'd really like it if the Magic would as well.... Both phones run the same version CM and i use the same cables/computer every time, both phones are set up the same (USB debugging and such) and both have an engineering bootloader but the Magic will not be recognized by my computer!
I've tried all and every driver i could find incl. the drivers that came with adb and the latest drivers from HTC Sync but all fail bad (the 'Android Bootloader interface' and 'MyHTC' drivers both give me a 'This device cannot start. (Code 10)' error...).
Now, i got it all working.... once... about a month ago to root the device and all and i cant remember changing anything since then but for some reason it simply doesn't work anymore. Has anyone here had similar experiences or any insights on how to fix this?
Help would be very much appreciated!!
Click to expand...
Click to collapse
Is USB debug enabled?

alex___ said:
Is USB debug enabled?
Click to expand...
Click to collapse
Yes, like i said in my first post everything is setup the same (USB debugging and such).
Also, if im not mistaken it wouldn't matter if i enabled this or not when trying to get the phone hooked up in fastboot mode and that doesn't work either.

So i guess its quite a unique problem im having...... sucks

Well, after some heavy duty searching/experimenting i found that it was a driver problem (windows XP's driver handling REALLY sucks)!
If anyone else is having problems, here's how i fixed it:
Disconnect phone from PC
Download USBDeview and run it
From within this program remove ALL non-Mass Storage drivers for Android and/or HTC (unlike XP this DOES actually remove em)
Reconnect phone with debugging enabled and install drivers from SDK (in my case r3 drivers)
This fixed it for me!

maarten82 said:
Well, after some heavy duty searching/experimenting i found that it was a driver problem (windows XP's driver handling REALLY sucks)!
If anyone else is having problems, here's how i fixed it:
Disconnect phone from PC
Download USBDeview and run it
From within this program remove ALL non-Mass Storage drivers for Android and/or HTC (unlike XP this DOES actually remove em)
Reconnect phone with debugging enabled and install drivers from SDK (in my case r3 drivers)
This fixed it for me!
Click to expand...
Click to collapse
I am having the same problem, do you mind sending me the link to download the drivers

deb82swearingen said:
I am having the same problem, do you mind sending me the link to download the drivers
Click to expand...
Click to collapse
The 'new' SDK works different from the old one, you actually need to install a bunch of stuff....
Get the package here, and read up on how to get the drivers with this package here!

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] Nexus S Root-Windows requests 'Android 1.0' hardware driver (and other weirdness)

Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.

Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928

webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!

haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!

bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders

The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.

jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.

I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid

I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!

Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!

Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S

Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App

Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"

When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work

matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!

thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App

matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!

I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box

[FIX][Win 8.1][UPDATED 30/8/2014] Fastboot on ALL PCs

Do not use these instructions anymore, Microsoft FINALLY fixed it, look here

....
HTC Driver Install Instructions
Go to Desktop, press Windows key + R, type in "shutdown.exe /r /o /f /t 00" and click OK.
Now click on Troubleshoot, then click Advanced Options then Start Up Settings.
Now click Restart. Let the PC restart and press either the number 7 or F7.
Download this and install it.
Wait for it to finish and then reboot and enjoy
Make sure you plug your phone into a USB 3.0 port EVERY Time when using Fastboot​

....
If you have any problems with your USB 3.0 port afterwards and want to return it to original driver, follow these steps to return to your original driver​
Press Windows key + R, type in "devmgmt.msc" and click OK.
Expand Universal Serial Bus Controllers.
The USB 3.0 port is listed as "AMD USB 3.0 Host Controller", double-click on it and select the Driver tab, click "Roll back driver" and select Yes.
Restart your computer​

Thanks for sharing
Sent from my HTC One S using xda app-developers app

dd98 said:
Today I present to you a fix for fastboot on Windows 8.1 x64 on Intel and AMD machines with USB 3.0. This will NOT work on USB 2.0. This should work if you follow instructions exactly. I am not responsible if anything goes wrong and/or breaks. The Intel fix is NOT mine I'm just posting it here for convenience (Original Intel tutorial here)
All credits for the Intel solution go to the people here
Please hit the thanks button if it helped​
Click to expand...
Click to collapse
im getting an error when extracting the amd fix zip

try 7zip or winrar to extract

dd98 said:
try 7zip or winrar to extract
Click to expand...
Click to collapse
Went nuclear and am installing Ubuntu as we speak... But as soon as it's done I'm going back to try this... I simply used whatever decompressor is in win explorer, even though I have both 7zip and winrar..... (Forehead smack) :silly:

i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA

dd98 said:
i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA
Click to expand...
Click to collapse
i truly appreciate you taking the time to do that for me.. truly!
however, since going to dualboot linux ive solved all those problems... have new ones now though
No radio, no firmware it seems... have a rom that boots but no way to connect..
Achieved S-OFF trying to fix it but no... nothing works... should i be using a sense rom?
thanks again!

you shouldnt need a sense rom, why dont you download amd fix.zip in ubuntu, extract it and move the files to your windows partition and then try to fix your usb then try running an ruu
try to fix adb on linux try this
1. Open terminal
2. type this: sudo gedit /etc/udev/rules.d/51-android.rules and hit enter
3. considering your phone is htc type in the following on the text editor window: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
4. save the file and restart your computer
or if this didnt work try this: http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/

Morning gents,
Got my ONE yesterday and obviously trying to unlock when I hit this roadblock. I tried the intel fix above earlier this morning and last night. I was able to get the intel drivers to take, but lost all of my usb ports in the process and had to roll back. As soon as I accept the first intel driver for the eXtensible controller, all peripherals are dead. Am I missing the obvious here??
I've spent more time trying to get my old pc (with Win 7) up and going than trying to fight 8.1 into submission. Naturally the HDD on that unit is dead now. CURSES!
What is the forecast for a solution on this? Is it a windows update or just waiting for an HTC driver update?
Thanks for any guidance.

thanks a ton worked wonders :laugh:

Microsoft knows about this, but doesn't seem willing to provide a general fix. Ultimately the problem is that Microsoft added an extra validation to device registration that HTC devices don't seem to honor. They're releasing an update to fix particular devices, but we don't yet know if end users will be able to edit the white list.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Sent from my One S using xda app-developers app

I have windows 8 32 bit. I would like to know if i will have problem when i will update windows to 8.1 32 bit. My computer have only usb2.0 ports
The problem exist only with usb3.0 port or i wil have it also with 2.0?
thanks

The problem exists with USB 2.0 ports as well. The reason that the "fix" posted works for USB 3.0 ports is because it uses Intel's USB 3.0 drivers for Windows 8 to work around the problem. There's also "fixes" floating around that involve rolling back to Microsoft's Windows 8 USB drivers to make it work.
If you don't have another PC that you can use to do things in fastboot, stick with Windows 8 until a proper fix is available.

Thanks... Finally I can Fastboot on Win 8.1... :good:

I can't install the driver update...getting an error that states "The system cannot find the file specified".

are you sure you read the note at the start and followed the instructions EXACTLY

dd98 said:
are you sure you read the note at the start and followed the instructions EXACTLY
Click to expand...
Click to collapse
The only thing I did any differently was to download the files before the reboot. I can't imagine that makes a difference but please correct me if I'm wrong. I validated all aspects of the initial note, still no luck. Again, I'm trying the AMD fix.

Likeachampion3 said:
I can't install the driver update...getting an error that states "The system cannot find the file specified".
Click to expand...
Click to collapse
Same problem here

[Guide] HKC P771A-P776A Root!

(WORKING ON WINDOWS XP 100% WINDOWS 7 DOESN'T SEEM TO WORK, IF NEED USE A VIRTUAL MACHINE)
Seeing as it was REALLY hard to find out how to root a HKC Tablet, I'll make a simple yet clear guide for all P77 models ranging from P771A through P776A.
First you will need the rockchip drivers (http://forum.xda-developers.com/attachment.php?attachmentid=1468367&d=1352441606) After you download them extract the folder, inside right click the files for your OS and click install.
After you install the correct one for your OS reboot your computer.
Once it has restarted on your tablet go to settings and on the left bar at the bottom click Developer options > on the top now click the sliding bar that says off until it says on and click the little check box next to usb debugging, now plug your device into your computer via the usb wire and set your tablet down.
Now install kingo root (http://download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html) After it is installed open the program and follow the on screen directions, if all goes well your device will reboot and kingo will say it was rooted successfully, do NOT unplug your device during this phase.
Once it has rebooted and kingo says that it was rooted you may remove the device and now you have a fully rooted HKC tablet

didn't work
RawX said:
Seeing as it was REALLY hard to find out how to root a HKC Tablet, I'll make a simple yet clear guide for all P77 models ranging from P771A through P776A.
First you will need the rockchip drivers (http://forum.xda-developers.com/attachment.php?attachmentid=1468367&d=1352441606) After you download them extract the folder, inside right click the files for your OS and click install.
After you install the correct one for your OS reboot your computer.
Once it has restarted on your tablet go to settings and on the left bar at the bottom click Developer options > on the top now click the sliding bar that says off until it says on and click the little check box next to usb debugging, now plug your device into your computer via the usb wire and set your tablet down.
Now install kingo root (http://download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html) After it is installed open the program and follow the on screen directions, if all goes well your device will reboot and kingo will say it was rooted successfully, do NOT unplug your device during this phase.
Once it has rebooted and kingo says that it was rooted you may remove the device and now you have a fully rooted HKC tablet
Click to expand...
Click to collapse
couldn't get driver to install. But first, what is the point of the Elijah drivers if my windows 7 of akready reccognizes the give as the p771a mobile device?
Can't install USB drivers with right click or with win7 device manager?
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
Then king application doesn't connect

I'm guessing that the driver is for the USB debug mode but I sure can't install it

The drivers were hard to install on windows 7 I've been hearing, you can try to install them via device manager and then click search online then have cd and navigate to the folder and choose the right driver.

This is how you do it

RawX said:
This is how you do it
Click to expand...
Click to collapse
I appreciate your effort in providing this answer. Unfortunately, after
some web research, it's exactly what I tried to no avail. The
driver would just not load and I couldn't even remove whatever
driver it thought was there in usb debug mode. I tried vista also.
same no result. I bought this cheap tablet just to play around
with rooting. I'll just chalk it up ti a failed experiment. The tablet
isn't bad as is considering its cheap price. I have other better ones.
Agaun, thank you for The answer.

RawX said:
This is how you do it
Click to expand...
Click to collapse
a final word. looking at the reply i didn''t do exactly what the responder recommended. I actually did a shorter version where i browsed the computer for drivers in just 4 steps. when i did exactly what the response recommended and arrived at step 6, hit next, i got a new screen listing rockchip device types, rk27, rk28, rk29, etc.. all double listed for some reason. I think the hkc p771a is a rockchip 29xx single core device so I tried the two rk29 listings. when those didn't work i tried all the others. none worked. always said driver was not for this device. Thank you bill gates for your incomprehensible os. but, really, than you again to the responder.

New RockUsb 3.7 Drivers Working
I too had no luck with the drivers offered with the guide short install or long i got no where so i went on a search and found these drivers do work just install with have disk,
now if i only can get kingo to connect any help would be great thx

nice try
Sounds like terrenInc is saying this driver will install but kingo still won't connect. Probably not the right driver for this function. Nice try though.

about this new driver
rombuster said:
Sounds like terrenInc is saying this driver will install but kingo still won't connect. Probably not the right driver for this function. Nice try though.
Click to expand...
Click to collapse
If that iis a correct adb driver (I couldn't get it to install), responder might try one of the other 1 click root apps out there like srss ti see if it will connect/work.

correct driver
rombuster said:
If that iis a correct adb driver (I couldn't get it to install), responder might try one of the other 1 click root apps out there like srss ti see if it will connect/work.
Click to expand...
Click to collapse
it was the correct driver it installed where all of didn't. I've been searching since my last post to no avail for a 1 click root that works

too bad nuthin works
TerrenInc said:
it was the correct driver it installed where all of didn't. I've been searching since my last post to no avail for a 1 click root that works
Click to expand...
Click to collapse
I tried the default google driver that adb uses and I could install it but no luck with kingo attaching.
There are several sites where people discuss rooting from the pt of view of the chip set
rk29xx (rk2918 to be exact) and they had success with a few other tablets with same chip
Set. To be frank it was over my head.

I've been having personal issues, sorry for the late reply, drivers I provided have only been tested on windows xp and windows 8 using them along with kingo root was a simple process, I have not been able to get the drivers working on windows 7 after a fresh install, I'm not entirely sure why but the rockchip drivers don't allow the connection via debug on windows 7, I've tested this method 3 times and its worked 2 out of 3 windows 7 being the failure. installing the drivers on windows 8 was as simple as right click install reboot, windows xp were the same way, using the windows 7 method on fresh install however proved to be more complex, I've had it working on the old install of win7 but haven't been able to on my fresh install.

To make this simpler, I'll edit into the main post (KNOWN WORKING ON WINDOWS XP) if you can try windows xp it is a sure proof method I just tested on a new tablet since my last post using my guide, working 100% with the drivers I linked, on a side note if you can't get ahold on a windows xp computer use a virtual machine to install windows xp then just remove it once you're rooted

Cydia Impactor will root this device. Trying to install a custom recovery (CWM) right now. The tablet is not playing fair.
And I used Windows 7.

rombuster said:
couldn't get driver to install. But first, what is the point of the Elijah drivers if my windows 7 of akready reccognizes the give as the p771a mobile device?
Can't install USB drivers with right click or with win7 device manager?
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
Then king application doesn't connect
Click to expand...
Click to collapse
I didn't mean to post this here sorry

Won't install usb drivers
I have the hkc p776a tablet and I have done every thing this guide says and it won't work I have tried it on a Xp PC and a vista pc also and neither one works when I tried to install it on vista it says "this .inf file is not meant to be installed this way" and on Xp it does nothing. Could you do pics on how you went though the process of doing it. I know it is a lot to ask but if you did it would help me a lot. Thx and is there any other way of getting the usb drivers.

Finally! I got root! I realized my problem on XP. I need USB debugguing off to install tablet correctly, then turned on for rooting program to connect. Now kingo didn't work for me. It made screen go crazy until all I could do is reboot. But cydia impactor did it! Happy days. Good-bye Korean keyboard!
Sent from my cheapo Rooted P771A (Finally!)

Installing the drivers worked for me on the first try (with no problems) on Vista with the usb debugging turned off.
Now How do I go about installing cwm recovery ? I am kinda stuck at that point now ;(
Sent from my HKC P776A tablet using Tapatalk Pro

So has anyone found a recovery for this tablet yet ...?
Sent from my HKC P776A tablet using Tapatalk Pro