Develop Bugs

need help with adb

so after i used the unrevoked recovery flasher every time i go to adb and type 'adb devices' it does not see the phone, if i type 'adb shell' it says "error device not found"
so i am guessing when i changed the driver for the hboot driver per the instructions with the unrevoked recovery flasher something got messed up and i dont know how to fix it..
any help would be appreciated!

are u in recovery mode and have you mounted the partitions ?

it doesnt matter where i am, it wont see the phone booted up, or in recovery with or without any partitions mounted, i have tried to reinstal the adb drivers, when i plug in the phone the device manager says "android composite adb interface" under android phone. and looks like all is working ok but then when i open adb in cmd it wont see it

You have to mount partitions in recovery before running adb shell

Studmf said:
You have to mount partitions in recovery before running adb shell
Click to expand...
Click to collapse
nope it says error device not found, i close adb in task manager, when i type adb shell or adb devices it is says daemon started successfully

did the recovery flasher finish correctly?

yojoe600 said:
did the recovery flasher finish correctly?
Click to expand...
Click to collapse
yeah everything worked great, i did one phone last night, i am able to get to recovery flash any .zip, have adfree working and did a second incredible this morning but just after the second went through successfully, i was trying to set up adfree on that one, went into recovery, mounted the partitions and then typed adb shell and got device not found, and for the past few hours i have been trying to get it to work again with either phone but no dice...

make sure usb debugging is back on

What do you see in the Device Manager?

doug piston said:
make sure usb debugging is back on
Click to expand...
Click to collapse
i have checked and it is on

elborak said:
What do you see in the Device Manager?
Click to expand...
Click to collapse
i see "android phone", when i expand that i see "android composite adb interface" no exclamation mark

ok first i want to thank everyone for them trying to help.
i finally solved the problem. again i dont know how this happened but this is what i did to fix it.
i made sure to download the latest drivers, then i edited the android winusb file with the following lines
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
i got this from someone named blue45 on the other forum while searching, then i unistalled the drivers in the device manager, then plugged in the phone again i showed it the driver i just edited, it asked what device it was for i chose android adb interface, not composite device like it had, and it asked me for a file, that i happened to know was in the windows\system32 folder, and it installed fine, i started up adb and bam all is good again!
man that was stressful!

glad you fixed it.

[N2E] Nook ADB over USB on linux.

Hey all,
another member just sent this to me regarding JesusFreke's work on adb usb:
mdall said:
This might interest someone : http://pastebin.com/jAV9ixNx (about adb over usb)
Click to expand...
Click to collapse
But the conversation segement is incomplete. I'd really appreciate knowing if anyone ever got ADB USB working with the nook, and if so how we can get it working.
I'm on amd64 debian based linux so I don't get to use the fancy looking windows driver package . And im sure this would help others.
BTW Nookdevs ADB over USB instructions for nook color do not work with the touch.
Thank you,
Endor

I have made a uRamdisk removing the service.adb.tcp.port property in default.prop and I have installed it but adb can't see my device over usb ...
Does anyone know what should I do to have adb over usb ?

Here are the steps I've taken to enable ADB over USB on the NST 1.0.0 (noogied+gapps).
Prerequisites:
SuperUser, I used 2.3.6.3
adbWireless, I used 1.4.1
1. Boot NST to your launcher, with USB cable plugged in
The computer may show "volume NOOK mounted"
2. Unmount the NOOK volume from the computer to get rid of the "USB Mode" dialog on the Nook
3. On NST, start adbWireless
If asked, grant SU
You should see a message like "adbWireless is on!"
4. Now stop adbWireless
USB debugging is still enabled!
The computer may show "volume NOOK mounted"
5. Unmount the NOOK volume just to avoid a "not cleanly unmounted" warning after the next step
6. On the computer, enter the command "adb usb"
You should see a message like "restarting in usb mode" or "daemon not running. starting it now..."
To verify, enter the command "adb devices" and you should see your plugged-in device.
Good luck!

voluntarytestsubject said:
Here are the steps I've taken to enable ADB over USB on the NST 1.0.0 (noogied+gapps).
6. On the computer, enter the command "adb usb"
You should see a message like "restarting in usb mode" or "daemon not running. starting it now..."
To verify, enter the command "adb devices" and you should see your plugged-in device.
Good luck!
Click to expand...
Click to collapse
hi,
i tried your guide to use ADB over USB, but i got stuck at step 6. In fact, when i run "adb usb" i got the error: "error: device not found". And "adb device" returns an empty list.
Do you have any clue?
Thanks

You need the adb drivers for adb over USB, there's multiple guides on how to get ADB over USB for the nook color, if I remember correctly from my conversation with JesusFreke it's basically the same drivers/setup.

mdall said:
I have made a uRamdisk removing the service.adb.tcp.port property in default.prop and I have installed it but adb can't see my device over usb ...
Click to expand...
Click to collapse
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
On the Linux side, I only have the 0x2080 line in ~/.android/adb_usb.ini,
and a standard udev-rule like this:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", ATTRS{idProduct}=="0003", MODE="0666", OWNER="xor"
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"
I'm attaching my uRamdisk file. Just rename to uRamdisk, and use at your own risk, obviously. Works fine here.

xor_ said:
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
Click to expand...
Click to collapse
hi,
i did exactly the same (rebuild uRamdisk) and it works also for me.
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Regards

xor_ said:
I did exactly that, and it works for me.
Commented out that line in /default.prop, rebuilt the uRamdisk, copied it over the one in the /boot partition.
On the Linux side, I only have the 0x2080 line in ~/.android/adb_usb.ini,
and a standard udev-rule like this:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", ATTRS{idProduct}=="0003", MODE="0666", OWNER="xor"
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"
I'm attaching my uRamdisk file. Just rename to uRamdisk, and use at your own risk, obviously. Works fine here.
Click to expand...
Click to collapse
Thank you
That is what I did and it didn't work but strangely I have done it again with your uRamdisk and following http://nookdevs.com/NookColor_USB_ADB and now it works

traycold said:
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Click to expand...
Click to collapse
hmm can someone try if it will work on windows with the following driver (from xboxexpert)?
http://forum.xda-developers.com/showthread.php?t=1125094

After reading this thread and the wiki entry for the nook color i finally figured it out to obtain adb via usb:
1. install the uRamdisk created by xor_ from here
2. create ~/.android/adb_usb.ini with the line 0x2080 and restarted the adb server:
Code:
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb start-server
3. add a new udev rule to /etc/udev/rules.d/*-android.rules and reload the udev rules:
Code:
echo 'SUBSYSTEMS=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="plugdev"' | sudo tee -a /etc/udev/rules.d/*-android.rules && sudo udevadm control --reload-rules
4. connect the nook to usb
5. and finally you should see the nook
Code:
adb devices
Thank you xor_ and mdall.

traycold said:
hi,
i did exactly the same (rebuild uRamdisk) and it works also for me.
I'm running on a Windows box, so it was slightly more difficult with ADB driver installation, in my case helped the driver pack found on another Nook-Color thread (link).
I don't know why i had in any case to manually update a device driver afterward, in any case, after installing the correct drivers, this time using Nook Touch driver pack (Composite ADB device), now USB ADB works like a charm.
Regards
Click to expand...
Click to collapse
I installed USB driver on Windows XP using the driver pack from that same link and using the attached android_winusb.inf file which was modified adds NSTR PID (which is 0003) to the USB supported list.
Hope it helps

No need to use 3'rd party driver packages for this.
All that is needed is the standard USB driver that comes with the Android SDK and then edit android_winusb.inf and add the following to both [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
That's it

ros87 said:
No need to use 3'rd party driver packages for this.
All that is needed is the standard USB driver that comes with the Android SDK and then edit android_winusb.inf and add the following to both [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
That's it
Click to expand...
Click to collapse
That's exactly what that package does: install the standard USB driver that comes with Android SDK with a modified android_winusb.info and add that line to adb_USB.ini

Is it possible to have USB ADB and WiFi ADB at the same time?

zeepzorp said:
Is it possible to have USB ADB and WiFi ADB at the same time?
Click to expand...
Click to collapse
Yes, just use the uRamdisk with the USB-ADB and something like the adbWireless app for ADB over Wifi.

Has anyone experienced the issue that, despite the NST showing up as an ADB device under Windows, adb.exe doesn't list it as a device? The NST is also showing a "USB Mode" screen, but there's no NOOK drive to eject since there's no NOOK drive showing up.
EDIT: Scratch that. Windows needed a slap on the wrist, now it's all fine.

ros87 said:
And ofc edit adb_usb.ini in your .android folder and add:
Code:
0x2080
Click to expand...
Click to collapse
How do I add that?

using text editor?
or extract this archive into your home folder (e.g. under C:\Documents and Settings\<yourusername>\)

So I can't get this to work at all. I'm running Ubuntu 12.04, adb works fine on my nexus but I don't even get so much as a 'device not recognised' on my nook. I've copied over the pathed uRamdisk (thank you very much) and verified that after a reboot my default.prop contains the necessary lines. I've added the udev rules, modified with my username, and I've tried running adb as root (which I believe should sidestep any udev issues?). I've re-triggered udev, and restarted my PC. I've verified both my usb cable, and the port on both ends work, as I can see the nook from my PC if I have automount enabled. With automount disabled I don't see storage devices, but I still don't see anything with adb devices. I've tried adding the code to .android/adb_usb.ini (doesn't make a difference) and also tried 'android update adb' (interestingly, updates adb_usb.ini to an *empty* file).
I've also tried the suggested trick of toggling adb konnect on/off, and I've tried with the debugging menu's adb checkbox on and off.
Any other suggestions?
Edit: rooted using nookmanager, fw 1.2.0. The reason I want wired USB when wireless is working is that I have occasional soft-reboots and can't find anything relevant in the logcat. I'm hoping that maybe there is something last-minute that doesn't make it through the wireless adb tubes before the reboot happens, but which would show on wired.

[how to...] install cm7/twrp/firefirefire

Looks like a newb install how to is in order. There are about 20 different threads, all telling you go go here for this, or there for that, but not one that covers it all from stock to CM7 while making backups and restoring back to stock. Here is who this guide will accomplish, and which post will help you acomplish your goal:
1. An individual with a clean Amazon Kindle Fire running version 6.2. Located at Post 3
a. This means a clean, unmolested, unrooted Kindle Fire. To see what version you are running, turn on your fire, press on the time, then more, then Device. It will tell you there the version you are on. If you are on anything other than 6.2, use at your own risk.
2. A rooted user wanting to install TWRP to backup thier system so they can play with the settings (Fonts, Kernels, themes, etc) on thier stock Kindle OS
3. A rooted user that wants to install TWRP to move to a new OS, such as CM7.
4. A Rooted user that has put CM7 on thier device, and wants to move back to the stock Amazon OS.

Are you an individual with a clean Amazon Kindle Fire running version 6.2? If not, Go back to the beginning to start over.
To Root your Kindle Fire in Windows 7 (it does not matter the version) Complete the following steps exactly:
1. Download the android SDK, including the Java JDK, for your windows type from here: http://developer.android.com/sdk/index.htm
Once complete, be sure to install all the tools in the options menu. ESPECIALLY THE USB DRIVERS
2. Open your "MY COMPUTER". Navigate to the C:\Users\Your logon name here\.android.
You need to right click on the adb_usb.ini and select edit.
You then need to add the following to the end of the document:
0x1949
0x18D1
then save it.
a. Should there not be a /.android folder, Go to C:\Users\Your logon name here\ and create a .android folder.
b. Then, place this file in the folder http://www.mediafire.com/?18csj2j7k65j0sl,d43k5d1i006bhqq,sczh5bmn8dj4x9p
You must then modify the android drivers so that it will recognize the Kindle Fire.
Go to the location you installed the Android SDK,
Navigate to \android-sdk\extras\google\usb_driver\android_winusb.inf.
Edit the android_winusb.inf file by adding:
;
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
to BOTH the [Google.NTx86] and [Google.NTamd64] sections of the document
SAVE.
Download SuperOneClickv2.2-shortfuse.zip from http://forum.xda-developers.com/showthread.php?t=803682
Extract this to the same directory as ADB (If you have not moved it, it will be in the //android-sdk\platform-tools directory)
Plug in your Kindle Fire, and click on Disconnect when the Fire gives you the option.
Click on Super One Click Root
Click on Root then wait
Be sure to install Busy Box when prompted.
Once complete, Reboot Device.

More to follow after dinner....

Hints for using KFU on a stock KF1

Hi all,
Today I turned my KF1 into a stock JB 4.2.2 tablet.
I used KFU, but as soon as I tried to run the install, it hung on fastboot. Luckily for me, I also had created a Livelinux install on a USB drive and used Soupkit to get the unit back to normal. Here's what I did to get through the process
0. Build a livelinux install
1. Modify the install_drivers.bat program and add the "/lm" (legacy mode) switch on the 32- and 64-bit installs
2. Run the install_drivers program
3. Reboot the computer and attach the Kindle
4. Now, you should get an "Android Phone" device in your device manager. Open that up and you will see an "interface" line. Right-click on "Properties" and check the "Details" line - WRITE THIS DOWN AND DOUBLE CHECK
5. Run KFU and change into fastboot mode
6. Unplug the Kindle and plug it back in. Windows should try to install another device driver - don't worry if it fails. Do the same thing now for the "Composite" driver under the "Android Phone" as in step #4 above.
7. Uninstall the driver(s) and then go into your \windows\system32\drvrstore directory on your machine (you may have to turn hidden files on). Delete the directory that starts with "Android"
8. Go back into the \kfu\drivers\kindle directory on your PC and modify the android_winsub.inf file
Here's the trick:
Whatever you found in step #4 and #6, make sure that there is a matching line in the INF file. For me, I needed to add the lines:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006\0123456789ABCDEF
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01\7\&F7A5236&0&0001
Now, re-run "install_drivers" and reboot your machine again. Run KFU. You should be rooted, TWRP'ed and FFF'ed in no time!

[Q] TWRP Doesnt show my backed up to restore!

TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?

DSH said:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
Click to expand...
Click to collapse
i have figuerd out what must i do!
now i have ADB and ADB doesnt find my device to push the rom on it!
plz plz plz help me
i had Drivers installed but when in fastboot connected to pc windows cannt find JEM-Prod... (something like this)
i neeed your help im so confused

Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks for your help but adb doesnt recognize my kindle fire! when in CMD i type "ADB Devices" no devices showd up and when "ADB usb" error shows
i think this is the cuase why your tip doesnt work for me (
ive tried this but step 3 give an error
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
Click to expand...
Click to collapse

Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you very much, but how must i install that?
in device manager i select update driver and locate this folder and it says windows was unable to install you kindle fire HD
i put my kf in recovery mod and plug in the cable!
why have i these problems ?
but again i wanna say thank you bro:good:

So in the task manager is showing a device with an exclamation mark over it right? If so right click the device and hit properties, then goto the details tab, and choose hardware id's from the drop down menu and post them here, I'll see about modifying the driver if I can. Don't know why mine wouldn't work I had the old and new vendor id's for twrp in that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

When i connect to pc in fastboot, in device manager shows as Other devices "Jem-PVT-Prod-04" and the Hardware Ids is:
USB\VID_1949&PID_0008&REV0100
USB\VID_1949&PID_0008
and when just plug the usb cable in recovery mod task manager show it as Portable Device and "Amazon Kindle Fire HD" with a yellow mark! and the hardware Ids is:
USB\VID_1949&PID_0008&REV_0216
USB\VID_1949&PID_0008
thank you bro

ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,

stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
OMG OMG OMG you saved me and my KINDLE FIRE
i have best wishes for you bro best wishes :good::good::good::good::good::good:

Help!?!?!?
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
i flashed recovery.img to my kindle using flashify and than i rebooted it than it came up saying kindle fire than the red screen slides across the screen. the app says that you may see a red screen.so im stuck now.

You probably just need to reflash the recovery partition from fastboot.