Database Develop

Need adb setup help

I am trying to get adb setup so I can root my NC and install some apps. The problem i'm having is I don't think I can get the proper drivers to install. I am following these steps ADB SETUP but when I get to step 3
My computer doesn't see "Android Composite ADB Device". It sees "Android adb interface". When I go to step 4
IV. Verify that everything worked
Start > Run > cmd > Enter
cd\
cd android-sdk-windows\platform-tools
adb kill-server
adb devices
If you get output that looks like the following you have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device
If you did not succeed, identify each nook entry in device manager (each device with a Hardware ID of USB\VID_2080&..., right click and uninstall it. There may be several. Uninstall all of them. Unplug the nookColor, replug it, and restart from Section III.
Further debugging: If you have an Android ADB composit interface and you still do not get your serial number listed, please repeat section 2, step 2, then verify that the file \users\yourname\.android\adb_usb.ini is exactly six characters long, and contains exactly 0x2080
I don't get my device listed. What have I done wrong?
Also when I uninstall all the drivers to start over if I connect the NC and look under device manager "NOOK" pops up for just a min then goes away and then its listed "under universal serial bus controllers"
I may have just figured it out. Do I have to do the whole sdcard boot thing before I can enable adb?

Uninstall the "android adb interface" then plug your nook to a USB port that is on the back of your computer, not from the front panel.

I hadn't done the root process before trying to setup adb but I got it now. Thanks for the help

[Q] ADB drivers?

I installed the usb drivers for my nook as per the instuctions in this guide: http://nookdevs.com/NookColor_USB_ADB#Windows_XP.2C_Vista_and_7
It seems to have worked and in device manager "ANdroid composite ADB device" shows up under Android Phone.
But when i type adb devices when my nook is plugged in, i still dont get and devices there.
Im running 64 bit Windows 7 on an Intel Core i7 machine.

I couldn't get the ADB drivers to work via those instructions either. Luckily we have people around here that are MUCH smarter than I am.
http://forum.xda-developers.com/showthread.php?t=910008&highlight=adb+driver+install
Follow the instructions and install the software from that thread, worked for me great.

I am having the same problem here. It seems like everything is installing fine. I deleted the old usb mass storage device, installed everything, but then when I try to do adb devices, I get a blank line. No serial number. I then tried adb wireless, I connected using adb connect 192.168.2.4 and it said connect it was connected. I then ran adb devices and it spit back that it was connected to that ip address but it still doesn't give me a serial number.

This is what I get:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>

Sorry for the multiple posts.
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.

Kindle Fire No Drivers TWRP Installed no Drivers/ADB

I have a Kindle Fire 2 (I assume its Kindle 2nd Gen) / It has no camera its 7"s
It has 2nd Bootloader and TWRP (v2.3.3.0) on it
I had a Cyanogenmod ROM on it but decided it needed something new
I can boot into TWRP
I cannot get it to mount as USB
Windows 8 Device Manager shows it as Kindle Fire 2 -- but has no drivers installed
I cannot get a ROM onto this
I run ADB from the KFF Package
ADB kill-server
ADB start-server
ADB Device.......
Nothing....
Ive tried a million drivers, including the ones in the KFF package, nothing.
I have JDK and Dev Kit installed
I have the custom amazon repository added in the dev kit with suggested packages
Still no Amazon Kindle Fire2 drivers installed
I am in Windows Test Mode and do not require signatures in my OS.
Windows 8, not 8.1
Any suggestions?

Finally Progress!
C:\KFFirstAide>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\KFFirstAide>adb devices
List of devices attached
0123456789ABCDEF recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Now I can sideload.

cnewman402 said:
Finally Progress!
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Now I can sideload.
Click to expand...
Click to collapse
Did you get where you need to be then? Windows 8 driver enforcement has to be disabled as well http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/ Go Big Red

[Q] minSdk(API 8) > deviceSdk(API 1)

Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.

It appears to be FIXED! I confirmed the functionality only yesterday.
Not sure exactly what the issue was, but I noticed that jre1.8.0_31 kept wanting to load an update. Apparently the JDK/JRE pairing was in error.
Removed JDK/JRE7; reinstalled JDK/JRE8 for Win64.
Environment Variables
ANDROID_SDK_ROOT
C:\Users\<name>\AppData\Local\Android\sdk
JAVA_HOME
C:\Program Files\Java\jdk1.8.0_25
With this configuration I can now use an AVD and can use the Debug facilities (Breakpoint, Step, StepOver).
caprock said:
Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.
Click to expand...
Click to collapse

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!