Database Develop

[Q] Nook, ADB problems

For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud

Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080

anyone have problems in ubuntu 10.04 can't get it :'(

I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk

I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.

[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.

If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs

I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps

Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.

Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave

I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.

Honeycomb adb not recognizing my nook

installed easyadb, drivers seem fine but when I type "adb devices" I get nothing under devices listed. I've read a bunch and tried several different things concerning usb debugging and different drivers, nothing seems to be working.
Thanks.
EDIT - It finally connected but I have no idea why. Is there anything I can do to make this less of a PITA?

here is what worked for me
Had the same issue on windows 7.
Took days for me to figure this out.
Clue was one time when i connected the nook, the add hardware popup reported an error. I looked at the details, which by the way, showed up behind my other windows. It stated that B & N Nook Color..., USB Mass... and USB Composite... installed correctly, but a device named NookColor did not.
So the fix i figured out was to open the android_winusb.inf file in the C:\android-sdk-windows\usb_driver folder and add
;
;NookColor
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
;
under the [Google.NTx86] and [Google.NTamd64] sections.
Note: I don't believe that the lines with the single ; mean anything other then to make the file more readible. you should make every effort to keep the file neat, orderly and easy to read though. You should be able to figure out the simple patern in the ini file.
Make sure that you have the .android folder and adb_usb.ini file with the 0x2080 contents in your user directory. (easily found in windows explorer and adding it is detailed in almost all instructions to get ADB set up)
Next step was to connect the nook via usb if not connected. Delete all of the devices with HW id which have the first value of USB\VID_2030&PID_002&REV_0216&MI_00. There could be 1 to 3 listed as USB Composite Device, USB Mass Storage Device under Universal Serial Bus Controllers, and Android Coposit ADB Interface under Adroid Phone.
I ran adb kill-server from the cmd line at this point. this is a good trick if at any point your having a problem replacing or editing anything in the .android folder.
Unplug the nook usb and (i like to wait a few seconds) plug it back in. windows should start to reconize and add the device.
when windows is finished being windows, you can check if this succeded by runing adb devices from the cmd line. If it is successful your device serial number should be listed.
If not successful delete all of the devices mentioned above from device manager. unplug the nook and reboot. When windows finishes booting up, try to plug in the nook again.
If that doesn't work I suggest deleting the any of the 3 devices from device manager again, check that the .android folder is there and contents are correct, make sure the android_winusb.inf has the changes recommended above, disconnect nook, reboot and plug in nook again. As this is windows, rebooting often isn't a bad idea either.
Hope this helps the weary Nook HC nobe as i am one. Keep pluging away.
Also if you get this working check out the root forum. I'm still trying to figure the fax speak out myself but it looks like the next step.
http://forum.xda-developers.com/showthread.php?t=953110
Edit: above instructions worked for me. my faxspeak is getting better. errrermmmmmeerrebeeep.
Do the nebe group a favor as well and if you figure something out post it to the general forum.

After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?

Just Tested
doncaruana said:
After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?
Click to expand...
Click to collapse
I think your asking can you browse the nook HC folders from a PC the same way you can browse BN media folder when you connect the usb, so for instance you can drag and drop files onto your nook HC. i'm assuming your dual booting eggclair and HC.
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I did just test if i could use the same drivers to connect the rooted BN eclair and still access the drive from my pc and was successful. remember you have to unlock the BN eclair to access the drives.
ADB doesn't block access to the drives. you don't need to turn it off. HC v4 just doesn't have the right stuff yet to allow the mount. my guess is that it is mostly a linux filesystem, i'm guessing the media directory is a fat or windows filesystem and that is why you can mount and use from a PC.
i assume that if you just have rooted eggclair this ADB settup method should work, and it should still allow access to the BN media directory from your PC.

If that still doesn't work for you, I got mine to work under Win7x64 by removing everything with that VID in device manager and using the USB cable from my Evo. The Nook one had serious issues getting the composite ADB device.

Anyone found a solution for the Mac?
EDIT: Never mind. Found a solution here: http://nookdevs.com/NookColor_USB_ADB
Love the internet

My experiences with Adb has been a hit and miss kind of thing. Stopped trying to use it since there was not point in it.

I've been using the wireless adb app from the market without any issues.

I was having trouble setting up ADB but then just gave up via usb *being lazy that is all* and used the adbwireless app and had no problems at all

Solved [Q] How to copy files to my phone

Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud

When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste

L0rdNels0n said:
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
Click to expand...
Click to collapse
Thanks, but your explanation is for normal usage, as said, I had a read-only system, this did not work for me.
I understand that the command adb remount did the trick, after that at least adb was able to do its task.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Ruud Westerhout said:
Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
Click to expand...
Click to collapse
Do you have USB debugging mode activated when you connect to a PC?
Also you can adb sideload a rom when you are in recovery.

Thanks farang4u,
As I said, Matt helped me out and the last Wipe Data which I did this morning was also the trick, so now all seem fine with my phone again.
Thanks all.

solved - adb device not recognized

I I apologize if this has been answered somewhere else. I did a couple of searches without finding an answer.
I can not get my MotoX to be a recognized device via adb. I am running Windows8 and I'm trying to get adb access to my ATT MotoX (DAMN, I wish I had a dev verstion!).
- It shows up under "other devices" as XT1058.
- It will not show up as an adb device in win8 device manager.
- I have tried different usb cables with the same result (and, different usb ports)
- I have changed the settings on Win8 to allow unsigned drivers.
- I have installed Moto Device Manager - didn't help.
- I have installed the Universal Naked drivers and "latest_usb_drivers_windows"
- I have uninstalled the device in device manager and de-selected/selected usb de-bugging and still comes up under "other devices"
- I have entered the Windows/Inf folder and deleted several inf files in an attempt to remove references to other drivers to get win8 to access the correct ones... hasn't worked so far....
Can someone please assist me in getting this thing recognized via adb?
I know fastboot is a separate issue - but, I can access fastboot so I'm fairly certain it is not a hardware issue (cable/port/etc).
------------------------------------------
Ok, I entered the folder Windows/Inf and opened up every single "oemN" file (N being the number following "oem") and deleted every file which had Android drivers... I then re-installed the Moto drivers and it worked...
Now, it says the device is "offline" - I need to research how to change THAT!
--------------------------------------
Ok, solved the "offline" issue... Updated the adb in "platform-tools" manually to 1.0.31
This caused the MotoX to FINALLY provide the pop up window to verify access to my computer's identity (which it refused to do previously).
Used this file: http://forum.xda-developers.com/attachment.php?attachmentid=1724500&d=1360704125
and copy/pasted the zip contents into the "platform-tools" folder to update the adb files.

ADB Unauthorized

Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?

vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530

If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.