So I am trying to do some Nook HD development in Linux and can't get adb to work.
First I tried listing devices in ADB and got no result. Continued further to find out that when I use lsusb command it is in fact connected. It does work on Wireless though.
Related
I'm a bit confused about getting my Auto-Nooted 1.0.1 NC visible to adb on my mac.
Situation: I have the NC as well as a T-Mobile G2. I also have a linux machine.
On the Mac, if I plugin the G2, it shows up under "adb devices". But if I plug in the NC, it doesn't.
However...
On the linux machine, the NC shows up just fine in "adb devices".
The fact that the G2 shows up on the Mac makes me think the mac is configured correctly.
The fact that the NC shows up on linux, makes me think the NC is configured correctly.
Why won't the NC show up under 'adb devices' on the Mac?
I should also point out that the NC does show up in System Profiler on the Mac when connected to USB:
Nook:
Product ID: 0x0002
Vendor ID: 0x2080
Version: 2.16
Serial Number: 2005210058833xx5
Speed: Up to 480 Mb/sec
Manufacturer: B&N
Location ID: 0x24110000
Current Available (mA): 500
Current Required (mA): 500
Weird. I use a Macbook for all my rooting and haven't seen that. Could it be your cable? Have you tried ADB Wireless to see if that'll work on your Mac?
I know that I had a crappy usb cable and had all sorts of issues but when I used a different cable, it was fine.
eyecrispy said:
Weird. I use a Macbook for all my rooting and haven't seen that. Could it be your cable? Have you tried ADB Wireless to see if that'll work on your Mac?
I know that I had a crappy usb cable and had all sorts of issues but when I used a different cable, it was fine.
Click to expand...
Click to collapse
I'm using the same B&N supplied cable on both linux (that works) and on Mac (which doesn't) so I kinda think it's probably OK. I've tried with it plugged into a hub and directly into the iMac with the same (bad) results.
I haven't tried adb wireless -- for the moment I'm doing everything on linux.
Thanks for the suggestions.
I have the exact same problem. ADB wireless works, but none of my 3 macs can use USB and ADB on my nook, either in Eclair or Froyo.
The problem now is that I have dualboot Eclair / Froyo, and Froyo is stock, so I can't do anything with it because Market isn't installed. Can't install ADB Wireless because I don't have Market, and can't install Market because ADB USB doesn't work... sigh.
Any ideas? thanks...
When I ran into this problem all you have to do after you install the SDK is connect your Nook to your Mac, then open terminal. Afterwards enter:
Code:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices
Then reboot your Nook and your set. You only have to do this once, after that. ADB works fine.
Hmm... Thanks for your response, I just tried that and all it gave me was a > prompt. I thought you might have missed the final " at the end, so I added it, but it reported back
error: protocol fault (no status)
EDIT: After rebooting from Eclair into Froyo, now it works! Thanks so much spyz88... This changes everything!
I have two Nook Colors auto-nooted with 1.0.1 and both are running fine. I used my Nook to install the Android SDK on my computer and enable Nook USB ADB. ADB is working great for my NC and I can do everything in the command line that I want.
However, I plug my brother's NC (rooted and worked like mine) into my computer and it doesn't show up in ADB ("adb devices"). I even tried rebooting, shutting down and restarting the Android SDK. I'm a noob and I'm wondering is there a setting in the SDK that only allows one Android device based on serial number to be connected with the SDK?
I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Chr0nos77 said:
I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Click to expand...
Click to collapse
Are you using the same cable?
Try going to the computers device manager and disabling the kindle uninstalling the driver reinstalling it then reenable the kindle. then try adb devices and see if that works
I am using the same cable. I reinstalled the drivers by uninstalling, and reinstalling in device manager. It worked thank you! I'm surprised that it had to be reinstalled for an identical device, but I'm happy it worked. Sorry about the slow response, I've been busy the last couple of days. Again, I really appreciate the help!
Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2
soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.
Hello everyone
I was wondering if someone can help me. I've been trying for a week to get my device recognized by the my Windows 10 PC, but it keeps coming up as unauthorized. I've seen all the posts:
https://forum.xda-developers.com/amazon-fire/help/help-thread-7th-gen-2017ask-question-t3636919
https://stackoverflow.com/questions/16256790/cannot-install-adb-for-kindle-fire-hd
https://theunlockr.com/how-to-unroot-the-amazon-kindle-fire/
https://www.howtodroid.com/2014/02/how-to-add-adb-command-prompt-windows.html
https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937
https://forum.xda-developers.com/showthread.php?t=1552547
Even the official Amazon website instructions
https://developer.amazon.com/docs/f...ice.html#install-the-usb-driver-windows-users
Sorry for all the links, just trying to prevent people saying i haven't tried everything. Even going to a new computer where i never plugged in the Fire 7 in said it was unauthorized. Here is the errors i get (i ran this in the folder itself using powershell and cmd as admin)
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb kill-server
D:\Fire 7\3rd attempt\platform-tools>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb usb
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I'm at a loss, i know it works sicne i've seen a bunch of people do it online, but for some reason i can't do it. Please help! Anything would be helpful! Thank you in advance!
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
srok.desarrollos said:
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
Click to expand...
Click to collapse
i had this on ubuntu from a command line, but abdlink said authorized (but nothing would install). I went to windows10 and i get the prompt on the tablet and no issues. I don't know if the ubuntu adb drivers don't work right or what. It seems to work fine in ADB on windows...
I have had to turn off adb usb on the fire before and remove authorizations to get it to prompt for adb.
I fixed it in Ubuntu by changing it to media device instead of charging only.
Edit - worked one time, then back to unauthorized....
next edit -
sudo adb kill-server
sudo adb devices
that prompted the authorization for me