My win 7 PC and laptop both refuse to let me change them. Is there any way around this. Have done the usual, delete nook tablet, offered it my driver but Win likes theirs better!!
Sent from my Nook Tablet
Hello claudiaa and welcome to the forum, there is a sticky FAQ where you will find a drivers issues section for troubleshoot. I recommend you to read the step by step tutorial.
~ Veronica
If you are trying to root your device, you can always try the sd card as well.
http://forum.xda-developers.com/showthread.php?t=1466583
I have done the sqlite3, the "install non-market apps" was already set to 1. Then I did ashell but it rejected me for not being rooted.
I searched again and cant find the section on drivers.
Sent from my Nook Tablet
Ohh trust me the section is there:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~ Veronica
I understand that you want to punish me for not searching. I have been on this forum searching and reading for more than a year and this is the first time I have ask a question.
Could you send me the link instead of a picture.
Sent from my Nook Tablet
claudiaa said:
I understand that you want to punish me for not searching. I have been on this forum searching and reading for more than a year and this is the first time I have ask a question.
Could you send me the link instead of a picture.
Sent from my Nook Tablet
Click to expand...
Click to collapse
Link for the FAQ is in my signature it is also stickied here is general forum. Have fun!
Sent from XDA premium using my Nook Tablet
Thanks for trying. I had already done three of your suggestions before I started asking for help. The usbdeview was hopeful. I went into Device installation settings and saved "Never install driver software from Windows Update" deinstalled all Nook ref. from both NC and NT. Plugged in the NT and my PC installed the wrong drivers AGAIN within 5 sec. Same with my laptop.
Is there any way to root if I can't get past this problem?
claudiaa said:
Thanks for trying. I had already done three of your suggestions before I started asking for help. The usbdeview was hopeful. I went into Device installation settings and saved "Never install driver software from Windows Update" deinstalled all Nook ref. from both NC and NT. Plugged in the NT and my PC installed the wrong drivers AGAIN within 5 sec. Same with my laptop.
Is there any way to root if I can't get past this problem?
Click to expand...
Click to collapse
What about deactivate windows update? if no go then your last hope is the sdcard method.
Edit: You don't have SDK installed, don't you?
~ Veronica
I've actually found that not plugging in the nook to your computer and then manually going in and adding a piece of hardware via the wizard tends to work. There should be an option to add an "Android Phone" to your computer. Then you just go through the process of selecting the drivers in c:\ntroot or whatever the file is. It should show up as Android Phone --> ADB device. Then you have to plug in the nook and update the driver for the Android phone and select the drivers in c:\ntroot. After you updated the drivers it should show up as Android Composite ADB Device, I believe.
Also, totally get rid of all the USB Mass Storage and Nook Devices w/ USBDev.
Try that and see if it works. I'm not really sure what I did to get the drivers to work on XP...at that point I was so frustrated that I as just doing things and not paying attention but I'm pretty sure that's how I did it.
No SDK.
Sent from my Nook Tablet
I'll try your suggestions as soon as I can tolerate my PC. I'm starting to take it personal when it flips me a message "Windows has determined that you don't know what you're doing".
Sent from my Nook Tablet
Claudiaa,
I believe i had the same problem that you are having. When your nook is plugged in go to your "usb mass storage device" drivers (i believe. It's the driver inherited by the drivers labeled "nook tablet"). Uninstall ALL OF THEM, unplug your nook, and reboot your computer. Log back in to the window showing the drivers for your computer, and an un-driver-ed device labeled as nook tablet and should show up with a little yellow /!\ in front of it. Right click on it and follow the driver installation instructions.
Hope it helps
Cheers!
Sent from my TARDIS.
claudiaa said:
I'll try your suggestions as soon as I can tolerate my PC. I'm starting to take it personal when it flips me a message "Windows has determined that you don't know what you're doing".
Sent from my Nook Tablet
Click to expand...
Click to collapse
This made me
Keep your sense of humor Claudia. The rest will get worked out!!
emfetz said:
Claudiaa,
I believe i had the same problem that you are having. When your nook is plugged in go to your "usb mass storage device" drivers (i believe. It's the driver inherited by the drivers labeled "nook tablet"). Uninstall ALL OF THEM, unplug your nook, and reboot your computer. Log back in to the window showing the drivers for your computer, and an un-driver-ed device labeled as nook tablet and should show up with a little yellow /!\ in front of it. Right click on it and follow the driver installation instructions.
Hope it helps
Cheers!
Sent from my TARDIS.
Click to expand...
Click to collapse
This worked for me as well. Had the same issue and this worked exactly the way stated.
Sent from my SGH-I997 using xda premium
I just tried all your suggestions. Windows 7 puts it's own drivers in no matter what I do.
Will have to find a ratty old computer that isn't so arrogant and rude!
Hi Claudiaa
What I did was use USBDeview to remove all references to USB Mass Storage Device. It seemed a bit extreme at the time but I was at my wits end and there were far fewer tools in Dec 2011. As I recall is took several attempts to pull it off.
Plop plop fizz fizz oh what a relief it was!
claudiaa said:
I just tried all your suggestions. Windows 7 puts it's own drivers in no matter what I do.
Will have to find a ratty old computer that isn't so arrogant and rude!
Click to expand...
Click to collapse
I'm on Windows XP and the only thing that worked for me was to go into device manager and delete any USB device shown that had a hardware id containing 0x2080 (or something like it -- the Nook's id). With Nook tablet attached I went through all the instances of USB mass storage or USB root hub and deleted anything Nookish
Device Manager > right click on, eg, USB root hub > properties > details > pull down menu Hardware IDs > uninstall any device with 0x2080
Then I reinstalled the drivers from
http://forum.xda-developers.com/showpost.php?p=19513995&postcount=1
And I was able to get ADB access. Not sure if this is similar for Win 7 - there should be a way to stop automatic driver install and direct the installer to your own INF file. Good luck.
.Claudia
Windows 7 after you get rid of all usb mass storage devices run diskpart in run window when you get the prompt enter disable automount after that scrub automount then exit. Check syntax first, it might be automount disable automount scrub. This will stop the automatic instalstion and drive letter assignment. Restart system. When the system is completley restarted and idle pluginnook with usb debug etc enabled make sure you are already in device manager on your laptop. As soon as see book come up right click on it and update driver using your drivers. My W7 would call it an android phone in device manager but it works. You may have to do this several times before you get the drivers to change. Hang in there you can do it. SORRY for spelling fat fingers and first reply
Thanks for all the suggestions, tomorrow I'm going to drag out my old XP and see if it will treat me better. It never met a Nook so it won't be so quick to mess it up.
If that fails, I'll be do what you said.
Sent from my Nook Tablet
Related
Alright. This is for people who have followed instructions EXACTLY and cannot see "Nook Tablet" when they plug it in with the little /!\ next to it.
First, make sure that it's not loaded as an android device because generic drivers have taken it over.
Next, be sure to check for USB Mass Storage in Universal Serial Bus controllers. This is where some people have difficulties so I took the liberty to snap a picture from my desktop with what you need to uninstall and put a border around it to get my point across.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All you need to do is uninstall those drivers and you should see "Nook Tablet" /!\ when you scan for hardware changes. I know this because I had to do it.
Actually added in the guide for you folks.
Doesn't work for me. Tried it on two systems.
Did you have the drivers for the Nook Color installed previous to installing the drivers for the Nook Tablet? Now about the development environment for ADK.
I have both of those on my system(s).
I think I will create a new VM and do a fresh install there. Thankfully with a USB install you can install Windows 7 64 in about 10 minutes.
I haven't had Nook Color drivers.
Jerry, when I tried this before I too had troubles. I had to do a System Restore to a state previous to my having plugged in my NT. My thinking was along the same line as yours - once you have any semblance of a "normal" Nook installation (even a Color, it seems) you have to find a way to completely back out of that state. Your VM approach should get the job done. Just be sure to do the runmefirst step and check to make sure the .Android stuff is all done before plugging in the NT.
Here's how i fixed this issue on my system. Download Usbview www.nirsoft.net/utils/usb_devices_view.html
Disconnect NT, open Usbview, remove all references to Nook and Android. Reconnect NT...as long as auto mount is off Windows will allow you to install the adb drivers.
yumms said:
Here's how i fixed this issue on my system. Download Usbview www.nirsoft.net/utils/usb_devices_view.html
Disconnect NT, open Usbview, remove all references to Nook and Android. Reconnect NT...as long as auto mount is off Windows will allow you to install the adb drivers.
Click to expand...
Click to collapse
in usbdview, do we "disconnect" or "uninstall" or "disable"? I'm going to try this method, if I can't get it all going I just realized I have a dual boot with WinXP on this machine so I will try doing it there.....Thanks to EVERYONE who has contributed to this issue, especially Indirect!!
You need to uninstall the drivers from Usbview.
yumms said:
Here's how i fixed this issue on my system. Download Usbview www.nirsoft.net/utils/usb_devices_view.html
Disconnect NT, open Usbview, remove all references to Nook and Android. Reconnect NT...as long as auto mount is off Windows will allow you to install the adb drivers.
Click to expand...
Click to collapse
Good find. I created a separate install and it worked fine.
That worked! In Usbview there were like 10 instances of various android and nook which I uninstalled. Also with Usbview, as soon as I connected the Nook Tablet, I could see which mass storage device it was I had to update the drivers on. Perfect. THanks again to everyone. Now I know I will keep the tablet. It is much better deal than the Kindle Fire which I also tried out.
Sorry, this is probably silly question, but how do I get Windows to recognize my newly rooted nook in explorer? It is connected and the nook says it is ok to move files to pc, but I can't find it in windows.....I'll try rebooting the pc....
OK, I rebooted pc but still not showing up in windows. I opened usbdviewer and there is an entry, actually 3 entries that seem to point to it, in fact one names it, says it is connected, and says it is drive letter u:. hmmmmm. The two other entries are "unknown" and also both "unconnected" and they refer to the same usb port that my nook tablet is plugged into. I suspect that they are the nook and its sd card and should be showing up as drive letters in windows, but they are not. I should be able to figure this out but I can't seem to.
GOT IT. Was in device manager as composite device (I could tell by the port) so I let windows automatically update the drivers and it reverted to a mass storage device and now is showing up in windows. Thank god.
I am trying to root my Nook Tablet, and seem to be stuck because my system is recognizing the preexisting Nook driver. I've used USBDeview to uninstall Android and Nook drivers, and tried (not sure if successfully) to disable automount. But every time I connect tablet, it automounts and installs drivers. So I'm not able to update driver to 'usbdrivers' that will enable me to root the device. I've looked online various places and cannot so far find a solution.
UPDATE: Every time I connect the nook tablet (after uninstalling drivers in USBDeview) win7 (64bit) says 'Installing Device Driver Software' and then installs tablet as 'USB Mass Storage Device' - I assume I need to turn something off to stop this from happening, so I can update the driver manually?
kreott said:
I am trying to root my Nook Tablet, and seem to be stuck because my system is recognizing the preexisting Nook driver. I've used USBDeview to uninstall Android and Nook drivers, and tried (not sure if successfully) to disable automount. But every time I connect tablet, it automounts and installs drivers. So I'm not able to update driver to 'usbdrivers' that will enable me to root the device. I've looked online various places and cannot so far find a solution.
UPDATE: Every time I connect the nook tablet (after uninstalling drivers in USBDeview) win7 (64bit) says 'Installing Device Driver Software' and then installs tablet as 'USB Mass Storage Device' - I assume I need to turn something off to stop this from happening, so I can update the driver manually?
Click to expand...
Click to collapse
Recheck to make sure that both USB debugging boxes are checked on and that the Auto-Mount is unchecked.
That was my first problem, and those boxes fixed it. Later on, I could install the drivers, but the nook and zergy script would never recognize my nook, so I used another computer that has never had android drivers. (I even used USBDeview to uninstallall android looking drivers.)
Later, I reset the nook to stock and then followed the "Troubleshooting" section at on the article: "How to root the NOOK Tablet, install the Android Market" at lilliputing.com
I was then able to recognize the nook on my original computer.
Good Luck.
Dfroelich said:
Recheck to make sure that both USB debugging boxes are checked on and that the Auto-Mount is unchecked.
That was my first problem, and those boxes fixed it. Later on, I could install the drivers, but the nook and zergy script would never recognize my nook, so I used another computer that has never had android drivers. (I even used USBDeview to uninstallall android looking drivers.)
Later, I reset the nook to stock and then followed the "Troubleshooting" section at on the article: "How to root the NOOK Tablet, install the Android Market" at lilliputing.com
I was then able to recognize the nook on my original computer.
Good Luck.
Click to expand...
Click to collapse
where do you set usb debuging and mount onte tablet?
Many Thanks!
Not to sound like a lot of others, but here goes anyways...
This site has helped me out more than a four-year degree in IT has! You all rock. Many thanks to everyone. I now like my new Nook. The B&N interface was way too limited.
I am absolutely a noob, but still learning.
Kevin
kdraw said:
Not to sound like a lot of others, but here goes anyways...
This site has helped me out more than a four-year degree in IT has! You all rock. Many thanks to everyone. I now like my new Nook. The B&N interface was way too limited.
I am absolutely a noob, but still learning.
Kevin
Click to expand...
Click to collapse
Same here. I've been digging in Windows and building computers for years, but as tablets go, I'm a noob. I've lurked here for a long time without joining, so I felt like it was time to signup and give my thanks to the folks that do the impossible here.
phil0sophic said:
where do you set usb debuging and mount onte tablet?
Click to expand...
Click to collapse
Did you download the apk for the tgps launcher app? When you open it with package manager, click start, then development. Those boxes are on the next screen.
I don't have enough posts to add links, but you can download (directly from your nook) that apk on the main root page under: "here is an app to pull up usb debugging menu"
OMFG! I am going to throw my laptop out the F***ing window!!
Every time I delete the drivers for Mass USB storage and the Nook, Vista just automatically reloads them as soon as I refresh the device list.
If I do not refresh the device list then there are no devices showing to update the drivers for.
If I try to install the drivers manually I get the infamous 'Windows has determined the driver software for your device is up to date'
If I try to force load the drivers by telling Windows I have a disk and point at the drivers provided it tells me it didn't find an appropriate driver.
6 hours straight - this is killing me!
Anyone?
Ok, I think I know what might be happening here.
There are 2 (yes two) "USB Debugging" settings in the settings on the Nook. I wasn't able to get the "Nook Tablet" to show in Device manager. I FINALLY went back in, and saw the second (well in my case the first) USB Debugging option. Originally, I checked the second USB Debugging option. I went back in, and saw the first one on the menu. Once I checked that I saw the Nook Tablet device in device manager.
Edit - Note of clarification. Yes, these two USB Debugging options are on the same settings screen. If you see one, you'll see the other.
FloridaPhil said:
OMFG! I am going to throw my laptop out the F***ing window!!
Every time I delete the drivers for Mass USB storage and the Nook, Vista just automatically reloads them as soon as I refresh the device list.
If I do not refresh the device list then there are no devices showing to update the drivers for.
If I try to install the drivers manually I get the infamous 'Windows has determined the driver software for your device is up to date'
If I try to force load the drivers by telling Windows I have a disk and point at the drivers provided it tells me it didn't find an appropriate driver.
6 hours straight - this is killing me!
Anyone?
Click to expand...
Click to collapse
if it were me i would try uninstalling the driver and clicking the box that says to also delete the driver from your computer so it wont auto install back.
(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!
Hello, ive faceed a problem after upgrading to 8.1
Phone doesnt showing in adb or fastboot.=(
Anyone got a drivers?
Thanks
olvrick said:
Hello, ive faceed a problem after upgrading to 8.1
Phone doesnt showing in adb or fastboot.=(
Anyone got a drivers?
Thanks
Click to expand...
Click to collapse
I am having the same issue...
olvrick said:
Hello, ive faceed a problem after upgrading to 8.1
Phone doesnt showing in adb or fastboot.=(
Anyone got a drivers?
Thanks
Click to expand...
Click to collapse
Same here.
Any solutions?
olvrick said:
Hello, ive faceed a problem after upgrading to 8.1
Phone doesnt showing in adb or fastboot.=(
Anyone got a drivers?
Thanks
Click to expand...
Click to collapse
killman2659 said:
I am having the same issue...
Click to expand...
Click to collapse
jimmydigital00 said:
Same here.
Any solutions?
Click to expand...
Click to collapse
I am find it
open device Manager
right click fastboot icon and then click update driver and software
Use a Drivers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've found a way to get ADB working on Windows 8.1. The trick is to use Intel's ADB drivers instead of Google's. We're going to need to manually extract the drivers from the installer because it doesn't recognize Windows 8.1 (ironic).
Bonus: This method of install ADB drivers doesn't require you to reboot without driver signature enforcement (because Intel signs their drivers like a good company should).
1) Download Intel's USB drivers from Intel's website (or my attachment). I don't have enough posts on XDA to be able to post the link but searching "intel usb driver for android devices" on Google has the correct webpage as the first result.
2) Download 7-zip to extract the drivers (if you don't already have it installed)
3) Right-click on the setup exe inside the zip file from Intel's webside and choose "Extract here" in the 7-zip menu. You'll probably get a warning about copying over files etc. just click yes to all.
4) Now open Device Manager and find the "USB Composite Device" that corresponds to the Android device. It may help to enter the "Devices by Connection" view (in the View menu). You'll want to keep expanding the device tree until you find the "USB Composite Device" that is the parent of your ADB device (and possibly the MTP device too). When you find that, right-click and "Update driver software". Click "Browse my computer for driver software" and click "Let me pick from a list of device drivers on my computer". Click the "Have Disk" button and browse to the directory that you extracted the drivers in step 3 then select "android_winusb.inf". You should see a single entry that says "Linux device with multiple configurations". Select that entry and click next.
5) After that installs, you should still see the exclamation mark by your ADB device (or you should see the ADB device with a non-working driver). Now you want to do the same steps as in step 4 except this time you should see 3 options when you select the inf. Click on the "Android ADB Interface" option and hit next.
6) You may need to reboot for ADB to pick up the device (or restart the ADB server)
Hopefully, this works for you guys. I did it successfully with my Ouya and Nexus 7.
Cybertron™ said:
I am find it
open device Manager
right click fastboot icon and then click update driver and software
Click to expand...
Click to collapse
still no luck
I get "device failed enumeration
aicom64 said:
I've found a way to get ADB working on Windows 8.1. The trick is to use Intel's ADB drivers instead of Google's. We're going to need to manually extract the drivers from the installer because it doesn't recognize Windows 8.1 (ironic).
Bonus: This method of install ADB drivers doesn't require you to reboot without driver signature enforcement (because Intel signs their drivers like a good company should).
1) Download Intel's USB drivers from Intel's website (or my attachment). I don't have enough posts on XDA to be able to post the link but searching "intel usb driver for android devices" on Google has the correct webpage as the first result.
2) Download 7-zip to extract the drivers (if you don't already have it installed)
3) Right-click on the setup exe inside the zip file from Intel's webside and choose "Extract here" in the 7-zip menu. You'll probably get a warning about copying over files etc. just click yes to all.
4) Now open Device Manager and find the "USB Composite Device" that corresponds to the Android device. It may help to enter the "Devices by Connection" view (in the View menu). You'll want to keep expanding the device tree until you find the "USB Composite Device" that is the parent of your ADB device (and possibly the MTP device too). When you find that, right-click and "Update driver software". Click "Browse my computer for driver software" and click "Let me pick from a list of device drivers on my computer". Click the "Have Disk" button and browse to the directory that you extracted the drivers in step 3 then select "android_winusb.inf". You should see a single entry that says "Linux device with multiple configurations". Select that entry and click next.
5) After that installs, you should still see the exclamation mark by your ADB device (or you should see the ADB device with a non-working driver). Now you want to do the same steps as in step 4 except this time you should see 3 options when you select the inf. Click on the "Android ADB Interface" option and hit next.
6) You may need to reboot for ADB to pick up the device (or restart the ADB server)
Hopefully, this works for you guys. I did it successfully with my Ouya and Nexus 7.
Click to expand...
Click to collapse
or without intel motherboard drivers...
---------- Post added at 11:55 AM ---------- Previous post was at 11:49 AM ----------
krzemyk1981 said:
still no luck
I get "device failed enumeration
Click to expand...
Click to collapse
that's no usb drivers it is fastboot driver 1st goto trun off your phone and goto fastboot mode then show your device manager fastboot icon then install drives...i hope install your drivers:good:
Cybertron™ said:
that's no usb drivers it is fastboot driver 1st goto trun off your phone and goto fastboot mode then show your device manager fastboot icon then install drives...i hope install your drivers:good:
Click to expand...
Click to collapse
no such icon
I tried all that it it still does not work for me.
Neither intel or any other driver works for me. It Installs it, sure, but Device enumeration still fails.
Running Windows 8.1 if that has any baring on the issue.
Solved problem by connecting into USB3.0. I have motherboard integrated Renesas USB3.0, first I had to update USB3.0 drivers to work Android ADB interface
The same for me, it was only working with my USB3 slot and also with windows booted without driver signature check.
Sined_ said:
The same for me, it was only working with my USB3 slot and also with windows booted without driver signature check.
Click to expand...
Click to collapse
Worked for me with they USB 3.0 port!
I'm having this problem as well. When USB Debugging is turned on adb will recognize my device in Camera (PTP) mode but it will not recognize it when it is plugged in as a Media device (MTP). Unfortunately I do not have any USB 3.0 ports on my machine. This has become very frustrating because I can't retrieve files off of my phone or test my android app anymore :crying: time to use the emulator in the mean time T_T
EDIT: If I put the files I want to transfer into the DCIM folder on my phone they will show up on the computer after I reboot the phone while Camera (PTP) file transfer mode is selected.
Same problem here, since I tried 8.1 preview. Works for adb, but not for fastboot.
bgcngm said:
Same problem here, since I tried 8.1 preview. Works for adb, but not for fastboot.
Click to expand...
Click to collapse
Same here, usb2/3 ports don't work for fatboot with windows 8.1 preview, I tried both xperia and htc,
olvrick said:
Hello, ive faceed a problem after upgrading to 8.1
Phone doesnt showing in adb or fastboot.=(
Anyone got a drivers?
Thanks
Click to expand...
Click to collapse
I am having the same issue, since I tried 8.1 preview. ...
Unfortunately I do not have any USB 3.0 ports on my machine.
Any new solutions ?
Fortunately both are running on my PC.
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...
ProgrammingExpert said:
Fortunately both are running on my PC.
Click to expand...
Click to collapse
You have using Windows 8.1 preview ???
Ultimo125 said:
You have using Windows 8.1 preview ???
Click to expand...
Click to collapse
Yes! Obviously a windows and android developer must have the latest updates.
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...
Please help! I have some important data that i want to get from my Pc to my S3 but everytime i connect the usb it tells me "SAMSUNG_android" doesn't have a driver as seen in screenshot taken
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what i tried doing to fix this...
*Uninstalling then re installing Kies
*Uninstalling then re installing Samsung drivers 1.5.5
*Tried changing ports of connecting usb in PC to phone
*Tried with another phone"S3 MINI" but it asked for "android" driver
*Made Windows search for that driver on Internet but it didn't find it
I don't know what that driver is......maybe can someone send me a link to that driver so i can download it ..Thanks in advance
try to copy to SD Card
but i don't have that thing where i put the Sd card in..
put it on another phone
or
download wifi file transfer pro
you will be able to manage files in your phone form browser
you can upload from pc to phone
or download to pc from the phone
Try updating Samsung kies with the latest driver and see if that helps.
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
Chrisamgad said:
Please help! I have some important data that i want to get from my Pc to my S3 but everytime i connect the usb it tells me "SAMSUNG_android" doesn't have a driver as seen in screenshot taken View attachment 2759410
Here is what i tried doing to fix this...
*Uninstalling then re installing Kies
*Uninstalling then re installing Samsung drivers 1.5.5
*Tried changing ports of connecting usb in PC to phone
*Tried with another phone"S3 MINI" but it asked for "android" driver
*Made Windows search for that driver on Internet but it didn't find it
I don't know what that driver is......maybe can someone send me a link to that driver so i can download it ..Thanks in advance
Click to expand...
Click to collapse
Try this link
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
bluinitro said:
Try updating Samsung kies with the latest driver and see if that helps.
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
Try this link
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
Click to expand...
Click to collapse
I already tried that :/............It gives me a non respond then it closes when install starts but it works with other versions
Chrisamgad said:
I already tried that
Click to expand...
Click to collapse
You could try installing the drivers manually so connect your phone to your PC via the USB directly to it, not through a USB connecter hub or any 3rd party connector
Right click on My Computer then click Manage
When the screen pops up on the left click Device Manager
You should find your mobile listed in three places
Expand Portable Devices you should have GT-i9300 listed
Expand Samsung Android Phone there should be an ADB interface option
Expand Universal Serial Bus there should be Samsung USB Composite device
They may not be exactly the same as these but you will recognise them
Right click on each one select Properties > click the Driver TAB > Update Driver
Click on Browse My Computer > Browse to C:\Windows\System32, make sure include Sub Folders is ticked. Once you have done each of the 3 connections unplug the phone, restart your PC then reconnect your phone, see if it works.
If that doesn’t work then follow the above process until you get to Browse My Computer but this time Click
Let me pick from a list and install the drivers listed there In each one you should get a list of driver options that will suit that connection.
Other option you have tried which is to uninstall Kies but when you uninstalled it did you restart your PC then completely delete the Program Folder Kies is put in before re-installing it, also the correct Kies version might help there is Kies and Kies3 but you probably know that.
When you install Kies then connect your phone it should install the drivers automatically but if you have a firewall that could be blocking the installation but not informing you that it is doing this so try turning that off temporarily as well.
ag4751 said:
You could try installing the drivers manually so connect your phone to your PC via the USB directly to it, not through a USB connecter hub or any 3rd party connector
Right click on My Computer then click Manage
When the screen pops up on the left click Device Manager
You should find your mobile listed in three places
Expand Portable Devices you should have GT-i9300 listed
Expand Samsung Android Phone there should be an ADB interface option
Expand Universal Serial Bus there should be Samsung USB Composite device
They may not be exactly the same as these but you will recognise them
Right click on each one select Properties > click the Driver TAB > Update Driver
Click on Browse My Computer > Browse to C:\Windows\System32, make sure include Sub Folders is ticked. Once you have done each of the 3 connections unplug the phone, restart your PC then reconnect your phone, see if it works.
If that doesn’t work then follow the above process until you get to Browse My Computer but this time Click
Let me pick from a list and install the drivers listed there In each one you should get a list of driver options that will suit that connection.
Other option you have tried which is to uninstall Kies but when you uninstalled it did you restart your PC then completely delete the Program Folder Kies is put in before re-installing it, also the correct Kies version might help there is Kies and Kies3 but you probably know that.
When you install Kies then connect your phone it should install the drivers automatically but if you have a firewall that could be blocking the installation but not informing you that it is doing this so try turning that off temporarily as well.
Click to expand...
Click to collapse
AS you can see that happened when i tried to find its driver manually as i also closed firewall , installed kies then restarted ...nothing happened :'(
EDIT:I managed to install the drivers but it gave me that error "Windows found driver software for your device but encountered an error while attempting to install it.Samsung Mobile USB compositive, Access is denied."
Chrisamgad said:
View attachment 2759724
AS you can see that happened when i tried to find its driver manually as i also closed firewall , installed kies then restarted ...nothing happened :'(
Click to expand...
Click to collapse
Might be worth looking at this http://digital.ni.com/public.nsf/allkb/1D52B53149DD637686256CAA00565E47
ag4751 said:
Might be worth looking at this http://digital.ni.com/public.nsf/allkb/1D52B53149DD637686256CAA00565E47
Click to expand...
Click to collapse
EDIT:I managed to install the drivers but it gave me that error "Windows found driver software for your device but encountered an error while attempting to install it.Samsung Mobile USB compositive, Access is denied."
ag4751 said:
Might be worth looking at this http://digital.ni.com/public.nsf/allkb/1D52B53149DD637686256CAA00565E47
Click to expand...
Click to collapse
Can you tell me what is the folder name in System32 which has the drivers so i can change its ownership and make myself admin on it...Maybe that will work then I will be able to upgrade it.
Oh I figured out the problem i have to give permissions to upgrade the driver,which is in system32, but I don't know how to do that...:crying:
Every time I connect the phone I have to go to USB settings, a PITA. Anyone fixed this?
grkn said:
Every time I connect the phone I have to go to USB settings, a PITA. Anyone fixed this?
Click to expand...
Click to collapse
You can change default in Developer Options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Perfect, thanks!
grkn said:
Perfect, thanks!
Click to expand...
Click to collapse
Keep in mind that if your phone gets stolen someone could get to your sensitive stuff with it set to file transfer by default. Pictures and documents would be accessible.
robn30 said:
Keep in mind that if your phone gets stolen someone could get to your sensitive stuff with it set to file transfer by default. Pictures and documents would be accessible.
Click to expand...
Click to collapse
but only if its unlocked
Xalies said:
but only if its unlocked
Click to expand...
Click to collapse
You are correct, just tried it. I wonder if it's been that way for all phones.
phaino00 said:
You can change default in Developer Options.
View attachment 5474511
Click to expand...
Click to collapse
Hmmmm .. is that Android 12?
I have a P6Pro and can't pull up 'Default USB ..." even with dev options open.
Lyphe416 said:
Hmmmm .. is that Android 12?
I have a P6Pro and can't pull up 'Default USB ..." even with dev options open.
Click to expand...
Click to collapse
It's a little lower than it used to be...
I can not change default USB in developer options either. When I attempt to run adb my device is not recognized. When I enable USB tethering the only popup I get on my phone is to turn off debugging. I can not accept connection to PC. I think this is why I am not seeing my Pixel 6 in adb. I have att variant( I know but it was the only one I could get) I will see if it changes next month when I pay it off and unlock.
travishanna522 said:
I can not change default USB in developer options either. When I attempt to run adb my device is not recognized. When I enable USB tethering the only popup I get on my phone is to turn off debugging. I can not accept connection to PC. I think this is why I am not seeing my Pixel 6 in adb. I have att variant( I know but it was the only one I could get) I will see if it changes next month when I pay it off and unlock.
Click to expand...
Click to collapse
Do you have the official Google usb driver installed on your PC.
Universal usb drivers will not work on Pixel 6 series.
I do. Android studio doesn't recognize the device either, in fact it crashed Google's Android Studio when I tried to access through it
travishanna522 said:
I do. Android studio doesn't recognize the device either, in fact it crashed Google's Android Studio when I tried to access through it
Click to expand...
Click to collapse
I also cleaned out all the unnecessary INF my PC and used a open third party app to make sure I didn't have a stray driver in the way.
Just a shot in the dark, but I can't help wondering if people with mysterious USB problems have AMD chipsets in common.
I am running an Intel core 17 hp laptop and an i5 6400 with Mint and Primeos dual boot
travishanna522 said:
I am running an Intel core 17 hp laptop and an i5 6400 with Mint and Primeos dual boot
Click to expand...
Click to collapse
I mention AMD because their USB controllers have problems with some peripherals. It's a documented issue and I had my own USB nightmares with a Ryzen laptop a couple years ago. Kernel panics from bootable USB sticks was one of the problems. Replacing the laptop with its i7 equivalent solved everything.
manjaroid said:
I mention AMD because their USB controllers have problems with some peripherals. It's a documented issue and I had my own USB nightmares with a Ryzen laptop a couple years ago. Kernel panics from bootable USB sticks was one of the problems. Replacing the laptop with its i7 equivalent solved everything.
Click to expand...
Click to collapse
I got persistent permission USB debugging for my computer and now stays in file transfer.
I went to dev options for default USB I selected USB tethering. USB default still greyed out can't toggle.
Then searched USB preferences in settings. I selected USB controlled by connected device. I immediately got permissions popup allowing me to give permission for USB debugging of my phone. I allowed always from this computer. I then changed to file transfer in USB preferences. Closed settings. Started adb and phone is now recognized with adb devices command.
travishanna522 said:
I got persistent permission USB debugging for my computer and now stays in file transfer.
I went to dev options for default USB I selected USB tethering. USB default still greyed out can't toggle.
Then searched USB preferences in settings. I selected USB controlled by connected device. I immediately got permissions popup allowing me to give permission for USB debugging of my phone. I allowed always from this computer. I then changed to file transfer in USB preferences. Closed settings. Started adb and phone is now recognized with adb devices command.
Click to expand...
Click to collapse
travishanna522 said:
I can not change default USB in developer options either. When I attempt to run adb my device is not recognized. When I enable USB tethering the only popup I get on my phone is to turn off debugging. I can not accept connection to PC. I think this is why I am not seeing my Pixel 6 in adb. I have att variant( I know but it was the only one I could get) I will see if it changes next month when I pay it off and unlock.
Click to expand...
Click to collapse
I got it .
Select USB tethering dev options
Search USB preferences in settings
Connect to computer
Selected controlled by connected device
Always allowed debugging from this computer in popup
Changed to file transfer in USB preferences.
Phone now recognized in adb with
Adb devices command
Automatically switches when I connect to my computer now
USB default still greyed out and won't toggle in dev options but adb works
I think I found a way around it with my ATT variant. Please let me know. I haven't posted anything anywhere before and may have forgotten a step in my excitement, or not been clear enough. Excuse any errors in terminology, I am new to this.
travishanna522 said:
I think I found a way around it with my ATT variant. Please let me know. I haven't posted anything anywhere before and may have forgotten a step in my excitement, or not been clear enough. Excuse any errors in terminology, I am new to this.
Click to expand...
Click to collapse
I'd say good progress as long as you're getting output from adb. fastboot should output too but it's not very useful without an unlocked bootloader.
Your descriptions make sense, I'm just short on suggestions because I'm not familiar with phones locked by AT&T except for the usual carrier barriers. Normally with phones that are carrier unlocked, no USB changes should be needed for file transfer mode other than selecting the option in Settings/Connected devices whenever the phone is connected. And for adb or fastboot only USB debugging needs to be enabled. For my Pixel and all phones before it, I've never had to tamper with USB settings in Dev options aside from enabling debugging to get it all working.
I agree. The bootloader will be unlocked in a couple weeks. Without adb it wouldn't matter if it was unlocked or not.
Now that permission has been given to my computer I don't have to mess with it. Wasn't about USB more about that certificate.
Sucks buying a Ferrari that Ferrari welded square wheels on.