So I set out to root my phone and am in the process to trying to install the USB drivers so i can use ADB. At first, windows installed it's own drivers, which obviously didn't work. I tried to update the drivers in the device manager to the ones located in the google-usb directory, but it said i already had the latest installed.
Next i decided to uninstall the current drivers completely and start over. I then told it to install the drivers that were located the in the google-usb directory. It said no drivers were found. They were obviously there, so i manually gave it the "android_winusb.inf" driver as per the cyanogen mod wiki page instructions on installing the drivers. It then said that "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I'm new to this so thanks for any help at all. I really want to learn my way around this kind of stuff.
Try it with your phone in mass storage mode with debugging on.
Still no luck. I've had it in debugging mode and charge only. Switched to disk drive mode and no change
Just download HTC Sync and use the drivers it provides. Should work for using adb.
Sent from my ADR6400L using XDA App
Now it can't even find HTC Sync on my computer... It's installed and i just used it the other day. Maybe it's something to do with the fact that i uninstalled the drivers it had? It can't communicate now?
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
setexascustoms said:
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
Click to expand...
Click to collapse
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
jwa0042 said:
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
Click to expand...
Click to collapse
You're more than welcome. You might re-title the post with [Solved] at the beginning so anyone with the same problem know to look here.
Just wanted to mention here that this was noted a while back and the CM Wiki will be updated with an easy way to correct this for Thunderbolt as well as other devices soon.
what's the solve?
Error device offline
It only says this on one computer. The rest are fine. What do I do? I've already installed the drivers.
ssojyeti2 said:
Error device offline
It only says this on one computer. The rest are fine. What do I do? I've already installed the drivers.
Click to expand...
Click to collapse
It is most likely a confliction from a program on your computer, such as easy.tether, pdanet, doubletwist, HTC sync, or anti virus. I get device offline if something is interfering with the phone when trying to use adb.
Sent from my PG86100 using XDA App
I'm getting the same error running Win7 64bit. Tried installing HTC Sync, uninstalling it, disabling antivirus, and using the "auto-detect" windows drivers. I'm not sure what else to try. Any ideas?
Fixed the problem. For those of us with newer motherboards you may want to make sure you have your phone connected to a USB 2.0 and not 3.0. 3.0 will cause it to become unstable and crash your pc. Moved it to a 2.0 slot and it worked perfectly, go figure.
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
Hi all,
I have an Aria running CM 7.2
I have a PC with Win XP SP3 where I am not able to connect my Aria because of lack of drivers.
I don't want to download and install HTC sync (pay-per-use plan).
Is there a standalone driver pack for Aria which I can use for:
ADB: VID_0BB4&PID_0C92&MI_01
Android Phone: VID_0BB4&PID_0C92&MI_00
Also there are other hardware IDs which I don't have right now, like fastboot etc.
I searched the internet and could not find any helpful drivers.
Can anyone help regarding this?
You can get the drivers here:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
File size: 13.1 MB
Thanks for the above. I installed it.
But I still get error messages saying hardware not recognized.
The (new!) hardware IDs are:
Without ADB
Android Phone : VID_0BB4&PID_0FF9
With ADB
Mass Storage : VID_0BB4&PID_0C92&MI_00
and still cannot connect the phone.
I tried specifying the path to the actual drivers in the HTC program folder, but no help.
Any solutions?
plade said:
Thanks for the above. I installed it.
But I still get error messages saying hardware not recognized.
The (new!) hardware IDs are:
Without ADB
Android Phone : VID_0BB4&PID_0FF9
With ADB
Mass Storage : VID_0BB4&PID_0C92&MI_00
and still cannot connect the phone.
I tried specifying the path to the actual drivers in the HTC program folder, but no help.
Any solutions?
Click to expand...
Click to collapse
I tested my Aria with an old PC and it worked. Try installing the latest version of HTC Sync: http://dl3.htc.com/application/sync/htc_sync_3.0.5617_us.exe.
Can you explain how you are attempting to connect the phone? Are you just trying to use the RUU? Are you trying to use adb?
The drivers I linked to should allow you to do both.
Here's what I did.
I tried to connect the phone (normal working condition running CM7) without any drivers installed.
The missing hardware IDs were the ones in the first post.
Then I tried to install the drivers from the link.
The installer did not work, some trouble with the MSI Package.
I went to temp folder and ran the MSI package by itself. This time it ran.
Then when I tried to connect the phone (running, with ADB on), it detected drivers like Android Phone, USB Composite Device, ADB.
But got stuck when Mass Storage was to be installed. Threw a 'new hardware found' window at me.
I disconnected and connected without ADB this time.
This time it got stuck on Android Phone.
Can you verify the file's MD5 sum? It should be:
HTCDriver3.0.0.007.exe
f60771a86c4ad69c8c9c1d158e60e850
I'm not sure what else could be the issue unless some old drivers are interfering or something.
drumist said:
Can you verify the file's MD5 sum? It should be:
HTCDriver3.0.0.007.exe
f60771a86c4ad69c8c9c1d158e60e850
I'm not sure what else could be the issue unless some old drivers are interfering or something.
Click to expand...
Click to collapse
Well the MD5 is all good. Probably the machine is messed up.
Other USB devices do work though, without a problem.
Anyway, this is only a spare machine. Just was wondering why it would not work here. I might try installing HTC Sync later, but I highly doubt it will work.
Thanks a lot for the help.
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)