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 Device Not Recognized

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.

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.

Thanks Haschode - worked first time
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Blimey - a little less aggressive would be good!
If adb is not recognising your device perhaps the drivers are not installed properly as it worked fine for me first time.
Assuming you have the android sdk installed, if you need help installing the drivers look at posts 7 and 8 in this thread.

Im still on stock rom rooted has 2nd bootloader and CCW
try to back up but I got this when i try to pull
D:\sdk\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
D:\sdk\sdk\platform-tools>adb pull /sdcard/boot0block.img
remote object '/sdcard/boot0block.img' does not exist
Any thing i did worng? and boot0block.img is not in my sdcard folder
Thanks advance

ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Depending on your setup & your environmental variable paths, you may have to launch the CMD window from your Android SDK folder. Depending on what version of the SDK you are using, it may be in platform tools for the older sdk, or in X:\Android\system\bin, where X equals whatever drive you installed the SDK on. It works from that folder every time for me & only sporadically from anywhere else.

Yes. Had same problem here.
I am on build 0511 at present and everything is good enough to me.
Since Hash reminded all of backup for one more image 0boot recently. Then I tried to connect to pc in ADB mode so I can backup it and push it to my pc in OS windows7. The enviroment for adb was good because I used same computer and system to install the second bootloader already.
At first I stuck with enabling ADB in my kindle but I eventually figure out how to do that. However, now when I hook my kindle to pc, the adb still doesn't work as a result adb.exe (command: adb devices) can not recognize my kindle device. At same time when my kindle connects to pc I found kindle is recognized as a removable device (MTP mode). And in kindle, in notification bar there are 2 items, one tells me that kindle is connect as Media Device and the other tells me ADB is enable. This is weird when both MTP and ADB are enabled at same time and I guess maybe this is the reason why pc can not see kindle in adb mode.
Then I tried to disable MTP (uncheck MTP in setting-storage-setting) to see whether ADB will work, I found I just can not do it, I can only switch between MTP and PTP rather than unselect both MTP and PTP.
Fastboot always works.
Appreciate if any help.
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire HD using Tapatalk 2

While you are figuring out the problem, you can still backup this boot0 by issuing the command from the kindle cmd terminal and copy it over to some place safe.

AlexAquarium said:
While you are figuring out the problem, you can still backup this boot0 by issuing the command from the kindle cmd terminal and copy it over to some place safe.
Click to expand...
Click to collapse
Did it as you said.
Thanks.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

CM10 cannot be detected with ADB devices
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
I am pretty sure the reason is that the Vendor ID in the Cm10 build is not 0x1949 (Kindle).
Before you flashed the Cm10. the Vendor ID was 0x1949 and after was not (Probably was google 0x18D1).
Unless your PC is setup to recognize the new Vendor ID, ADB and Fastboot will no longer work.
The good news is that if you loaded 2nd bootloader and TWRP, if you are in recovery, the recovery Vendor ID is 0x1949.
The solution is to wait until Hashcode modifies his CM10 builds to put the 0x1949 vendor ID back into the build.
This kind of thing happens more often than you would think and creates some issues after a ROM change.
Regards Jerry

@Hashcode
Just curious...is this something that was added to Amazon's code (intentionally, perhaps?), or is it just an unfortunate byproduct of making a mistake while attempting to modify the device?
Is it due to a recent update or had it always been the case?

soupmagnet said:
@Hashcode
Just curious...is this something that was added to Amazon's code (intentionally, perhaps?), or is it just an unfortunate byproduct of making a mistake while attempting to modify the device?
Is it due to a recent update or had it always been the case?
Click to expand...
Click to collapse
There is code in 1 of the bootloaders to erase the boot0 block and reset the info after many failed boots. And this info is so important that I felt it was worth keeping a backup of. Without it, you can never re-register the Kindle w/ Amazon services.
Sent from my XT894 using Tapatalk 2

So, apart from screwing people over, would there be any real need for such an addition?

Not to revive a old thread but how would one know if the boot0block had definitely been wiped or reset what can be done to check if it had been or not?

Device Offline Error on HTC One

Okay, I am trying to run the firewater script in order to get S-OFF. But I have run into the "device offline" error when I try to connect my Mac to my HTC One. I understand from reading why I am getting the error, and that it is due to a new "feature" of Android 4.2.2+ which gives us secure usb debugging.
Here is the rub, though: When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’.
But that is not what is happening! Whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization. The trick, according to this thread [http://forum.xda-developers.com/member.php?u=4159439] would seem to be to remove the
adb key from the device, so as to trigger the confirmation window to allow USB debugging. But I can not find the location of this file on my HTC One, so I have no way to remove it.
Please tell me where this file is located if you know it. I have ES File Explorer installed on my rooted HTC One, Dev. Edition, running Android 4.4.2. but that path nets me an empty folder.
Thank you for any and all assistance that you provide.
SOLUTION FOUND! - See my reply below.

Okay, typed into terminal:
cd Android/HTCOneRoot
./adb-mac version (This command gives the version of ADB that the Mac is using.)
Android Debug Bridge version 1.0.29 (Terminal returns this answer; ADB needs to be at least version 10.3.1 to properly work and fix the "device offline" error.)
Here are the steps I then followed to fix problem:
1. I unplugged my HTC One from the computer.
2. Downloaded and installed Android Studio from the Android Developers’ site into my Applications folder
3 Updated my Platform Tools, as follows:
Control-clicked on the Android Studio Application and selected “Show Package Contents” from the pulldown menu.
Followed this path to the platform tools: Android Studio/sdk folder/platform-tools folder/adb & fastboot
Option copied both adb and fastboot from platform tools to my user directory ~/Android/HTCOneRoot.
Closed Android Studio
4. Restarted the computer.
5. Launched Terminal and typed cd Android/HTCOneRoot( my user directory where my adb and fastboot are stored)
6. Typed into my terminal the command, “./adb version”
Following this command prompt, Terminal responded with “Android Debug Bridge version 1.0..3.1. (Yes!!)
7. Typed into Terminal, ./adb devices
My device did not show up right away!
8. So, I unplugged my device. Shut down my Mac and restarted it.
9. Relaunched Terminal and typed cd Android/HTCOneRoot
10. Typed ./adb kill-server
11. Then typed, .adb start-server
Terminal responded with: daemon not running. starting it now on port 5037 *
daemon started successfully *
12. Plugged in device again, and the device dialog about RSA appeared. (Whew!)
13. Clicked “OK” on the dialogue box.
14. Now typed ./adb devices and my device's serial number shows up, followed by the word "device" (not "device offline")
14 All done! No more device offline errors.

Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3

RickCov said:
Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3
Click to expand...
Click to collapse
mini-sdk-1.0.31-windows.rar
download and extract to a folder of your choice, that's all.

let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.

I was having the exact issue described by OP and simply by getting the newest version of ADB and unchecking and rechecking debugging I got the authorization. Thanks all who offered suggested and posted links to files.

and this helped as well
metropical said:
let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Click to expand...
Click to collapse
http://goo.gl/WyyzhX

[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!