Since there seems to be a number of people fighting to get ADB working with the NC on Win7-64 machines, I thought I'd start a dedicated thread to get to the bottom of this issue.
In my case, ADB is working from my laptop but not my desktop. At various stages I have different devices, including an "Android Composite ADB Interface" and and "Android ADB Interface". At no point does `adb devices` return anything.
Here's some bits that will hopefully be helpful in troubleshooting.
Without the drivers installed (more accurately, with them uninstalled and deleted), I have the following devices in Device Manager:
Code:
Other devices -> Nook
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_01
USB\VID_2080&PID_0002&MI_01[/INDENT]
Universal Serial Bus controllers -> USB Composite Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002[/INDENT]
Universal Serial Bus controllers -> USB Mass Storage Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_00
USB\VID_2080&PID_0002&MI_00[/INDENT]
Could someone with a working ADB under Win7-64 uninstall their drivers and post the above information? If it's the same, could you zip your usb_drivers dir and upload that?
ADB version from SDKr08:
Code:
C:\>adb version
Android Debug Bridge version 1.0.26
ADB logcat with debug all:
Code:
C:\>set ADB_TRACE=all
C:\>adb -d logcat
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4641494c FAIL
readx: 101 0x28dc57 4
readx: 101 ok: 30303130 0010
readx: 101 0x4221a0 16
readx: 101 ok: 646576696365206e6f7420666f756e64 device not found
adb_close: 101(lo-client:5037)
Switch transport failed
- waiting for device -
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 102
writex: 102 0x28baf7 4: 30303063 000c
writex: 102 ok
writex: 102 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 102 ok
readx: 102 0x28ba77 4
readx: 102 ok: 4f4b4159 OKAY
readx: 102 0x28bb34 4
readx: 102 ok: 30303034 0004
readx: 102 0x28bb34 4
readx: 102 ok: 30303161 001a
adb_close: 102(lo-client:5037)
_adb_connect: host-usb:wait-for-usb
socket_loopback_client: port 5037 type tcp => fd 103
writex: 103 0x28baf7 4: 30303135 0015
writex: 103 ok
writex: 103 0x28cc01 21: 686f73742d7573623a776169742d666f host-usb:wait-fo
writex: 103 ok
readx: 103 0x28ba77 4
readx: 103 ok: 4f4b4159 OKAY
readx: 103 0x28bb97 4
Again, if we can get a working environment's output, that would be great.
Those who are having the same problem, post the results of the above command here, too. Don't forget the `set ADB_TRACE=all`. We can see if there's any differences in the behavior in the non-working envs.
I should note that some people have been successful by removing and deleting the drivers, un/re-plugging the NC and letting Windows auto-install the drivers (if I'm understanding the process).
edison said:
Since there seems to be a number of people fighting to get ADB working with the NC on Win7-64 machines, I thought I'd start a dedicated thread to get to the bottom of this issue.
In my case, ADB is working from my laptop but not my desktop. At various stages I have different devices, including an "Android Composite ADB Interface" and and "Android ADB Interface". At no point does `adb devices` return anything.
Here's some bits that will hopefully be helpful in troubleshooting.
Without the drivers installed (more accurately, with them uninstalled and deleted), I have the following devices in Device Manager:
Code:
Other devices -> Nook
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_01
USB\VID_2080&PID_0002&MI_01[/INDENT]
Universal Serial Bus controllers -> USB Composite Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002[/INDENT]
Universal Serial Bus controllers -> USB Mass Storage Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_00
USB\VID_2080&PID_0002&MI_00[/INDENT]
Could someone with a working ADB under Win7-64 uninstall their drivers and post the above information? If it's the same, could you zip your usb_drivers dir and upload that?
ADB version from SDKr08:
Code:
C:\>adb version
Android Debug Bridge version 1.0.26
ADB logcat with debug all:
Code:
C:\>set ADB_TRACE=all
C:\>adb -d logcat
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4641494c FAIL
readx: 101 0x28dc57 4
readx: 101 ok: 30303130 0010
readx: 101 0x4221a0 16
readx: 101 ok: 646576696365206e6f7420666f756e64 device not found
adb_close: 101(lo-client:5037)
Switch transport failed
- waiting for device -
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 102
writex: 102 0x28baf7 4: 30303063 000c
writex: 102 ok
writex: 102 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 102 ok
readx: 102 0x28ba77 4
readx: 102 ok: 4f4b4159 OKAY
readx: 102 0x28bb34 4
readx: 102 ok: 30303034 0004
readx: 102 0x28bb34 4
readx: 102 ok: 30303161 001a
adb_close: 102(lo-client:5037)
_adb_connect: host-usb:wait-for-usb
socket_loopback_client: port 5037 type tcp => fd 103
writex: 103 0x28baf7 4: 30303135 0015
writex: 103 ok
writex: 103 0x28cc01 21: 686f73742d7573623a776169742d666f host-usb:wait-fo
writex: 103 ok
readx: 103 0x28ba77 4
readx: 103 ok: 4f4b4159 OKAY
readx: 103 0x28bb97 4
Again, if we can get a working environment's output, that would be great.
Those who are having the same problem, post the results of the above command here, too. Don't forget the `set ADB_TRACE=all`. We can see if there's any differences in the behavior in the non-working envs.
I should note that some people have been successful by removing and deleting the drivers, un/re-plugging the NC and letting Windows auto-install the drivers (if I'm understanding the process).
Click to expand...
Click to collapse
Attached is my usb_drivers folder from my working Windows 7 Pro x64 installation.
Note that this is the same usb driver zip from the nookcolor portal (http://nookdevs.com/NookColor_USB_ADB) under the 'windows' section, just with the necessary B&N product lines already added.
It's working!
Unfortunately, I'm not 100% sure which step I did make it work, but I list everything I can recall.
I'll first answer a few of my own questions in the hopes it'll help others.
Output of `adb -d logcat`:
Code:
C:\>adb -d logcat > logcat.txt
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4f4b4159 OKAY
Switch transport success
writex: 101 0x28dcd7 4: 30303265 002e
writex: 101 ok
writex: 101 0x28dde1 46: 7368656c6c3a6578706f727420414e44 shell:export AND
writex: 101 ok
readx: 101 0x28dc57 4
readx: 101 ok: 4f4b4159 OKAY
I had to redirect to the txt file because the screen was filled with a bunch of the following lines:
Code:
I/ActivityManager( 822): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.internal.app.UMSServerActivity }
D/DeviceManagerBroadcastReceiver( 1011): action (android.intent.action.BATTERY_CHANGED)
D/WifiService( 822): ACTION_BATTERY_CHANGED pluggedType: 0
I've attached the usb_drivers I used, although I can't see any difference in them and the ones I had before.
Now for the stuff I did in-between my first post and this one (from memory).
I plugged the USB cable directly into the ports on my motherboard, instead of my PCI-X internal USB2.0 card. This was in response to suggestions on the other Win7 thread that you remove USB hubs from the mix. I'll try again with it plugged into the card later and report back.
I should note that in order to do this, I had to unplug my HP Deskjet which has a card reader slot. I had two USB Mass Storage and USB Composite devices listed in Device Manager prior to removing this - one each for the NC and the HP. After the removal, only a single set. Dunno if it made any difference, but it's worth mentioning. I'll try it with that plugged in, too, and report back.
I uninstalled the 'Android Composite ADB Interface' from under 'Android phone' from Device Manager, without checking the "Delete driver software" box. Obviously at this point I had the drivers installed. To be honest, I can't recall which of the native (Nook, USB Composite Device, USB Mass Storage Device) I updated the drivers on, but I *believe* it was the "Nook".
After the above step, I unplugged the USB cable and plugged it back in. This was based on several suggestions to that effect. I repeated these two steps multiple times but nothing ever showed up in `adb devices`, so I tried rebooting.
During this and all subsequent reboots, I hit F8 on startup and selected the "Disable Driver Signature Enforcement".
Still nothing after the reboot, so I uninstalled the 'USB Composite Devices'. Windows informed me a reboot was required. Whoah! That was new!
After the 2nd reboot, Windows automatically installed drivers (presumably for the device I had just removed), but again required a reboot.
Since the required rebooting behavior was so different than previous attempts (none of which asked to boot), I tried `adb devices` again.
Nothing.
Drat!
Then I checked the c:\Users\edison\.android\adb_usb.ini file that I created yesterday. All it had was this!
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
I *know* I had inserted a single '0x2080' in the file with no spaces or CRs. I had double-, triple- and quadruple-checked that stinkin' file during the last two days of frustration and it always existed and contained the right string. Something had to have changed it, but I'm not sure what it was. At one point, I had run the SDK Manager (from \androidsdk) and removed the non-2.1-related packages, including the "USB drivers package, revision 4". That's my best guess for the culprit.
So I added the "0x2080" to the adb_usb.ini file (after the 3 existing commented lines) and `adb-remount` gave me the sought-after "remount failed: No such file or directory", after which `adb devices` listed my NC!
Woo.
Hoo.
FWIW, I don't know that `adb remount`, specifically, is necessary. I ran `adb kill-server`, then `adb start-server` afterwards and it worked that way as well. I think the key is restarting the server once everything else is in place.
Since there are SO many others having this exact problem, can those of you who are and who try these steps, record what you do and report back?
My guess is that rebooting without the signed drivers req, removing the 'USB Composite Device' and the subsequent reboots/auto driver installs is what worked.
I do want to clarify that I know my NC was properly rooted as I was able to sideload apks from my laptop. This was only an ADB issue on my PC. IMO, the best way to confirm your NC is rooted is to boot with the nooter SD card installed. If you get a standard nook boot process, it's not rooted. If the device shows up in Windows (as *anything*), but the screen stays blank, you're rooted. I was pretty careful on my SD boots, as per the guides, to wait long enough for the root to "take" (2 full mins).
I sincerely hope this helps as I've spent all of last night and today working on this and I hope to save as many others from the same rage-inducing frustrations as possible.
Thanks to everyone who has put in the effort to make this possible, and everyone who has stuck by the community and taken the time to help the rest of us out!
edison said:
It's working!
Unfortunately, I'm not 100% sure which step I did make it work
....
[*]Then I checked the c:\Users\edison\.android\adb_usb.ini file that I created yesterday. All it had was this!
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
I *know* I had inserted a single '0x2080' in the file with no spaces or CRs. I had double-, triple- and quadruple-checked that stinkin' file during the last two days of frustration and it always existed and contained the right string. Something had to have changed it, but I'm not sure what it was. At one point, I had run the SDK Manager (from \androidsdk) and removed the non-2.1-related packages, including the "USB drivers package, revision 4". That's my best guess for the culprit.
So I added the "0x2080" to the adb_usb.ini file (after the 3 existing commented lines) and `adb-remount` gave me the sought-after "remount failed: No such file or directory", after which `adb devices` listed my NC!
Woo.
Hoo.
[/B]
Click to expand...
Click to collapse
this is what fixed it, it is a known issue that when the sdk updates using the sdk manager it replaces the adb_usb.ini with this file. you can manually edit it or just run 'android update adb' in command prompt to fix it. just fyi
I've never had an issue with adb_usb.ini being altered. I always check it before another adb attempt.
I went through the lists posted in here and came up with the same result on my win 7 64 bit setup. Disabling driver signing, uninstalling usb composite as well as removing the android composite adb interface and reinstalling.
I still need a way to confirm my nooter img has written correctly. There is no way to confirm this other than following the steps very precisely.
It just gets me angry *kicks nook*.
I had the ini file get changed after I uninstalled the drivers and reinstalled them.
madsci73915 said:
I had the ini file get changed after I uninstalled the drivers and reinstalled them.
Click to expand...
Click to collapse
Un-/re-installed the drivers via Device Mangler or the SDK Manager?
moovius said:
I've never had an issue with adb_usb.ini being altered. I always check it before another adb attempt.
Click to expand...
Click to collapse
Same here. That's why I was so mystified when it changed this time.
moovius said:
I went through the lists posted in here and came up with the same result on my win 7 64 bit setup. Disabling driver signing, uninstalling usb composite as well as removing the android composite adb interface and reinstalling.
Click to expand...
Click to collapse
Remember, I was going from memory, which was pretty fried after the previous 12 hours of fiddling. There may be another combination or step I missed.
moovius said:
I still need a way to confirm my nooter img has written correctly. There is no way to confirm this other than following the steps very precisely.
Click to expand...
Click to collapse
Does your NC wake up to a blank screen when booting from the SD card?
To check the actual SD card, pop it back in your PC. It should have a regular 40MB FAT partition that Win7 can read. If you want, you can use DISKPART from the shell to verify the partition. It should go something like this:
Code:
C:\> DISKPART
DISKPART> list disk
DISKPART> select disk N <-- your SD card from the list above
DISKPART> list partition
You should see the 40MB partition listed, although I don't have a screen grab to show. I just reformatted my SD card 'cause the Kindle app requires one and I didn't have an extra spare, but I can either pick one up today or re-image it
moovius said:
It just gets me angry *kicks nook*.
Click to expand...
Click to collapse
Hang in there, moovius, we'll figure this out! I *completely* understand your frustration, but persistence and tenacity will pay off!
OOC, do you have another computer you can try this on?
edison said:
Hang in there, moovius, we'll figure this out! I *completely* understand your frustration, but persistence and tenacity will pay off!
OOC, do you have another computer you can try this on?
Click to expand...
Click to collapse
I had one of the guys from #nookdevs remoting my computer and even he was stumped.
I gave up on windows and downloaded Ubuntu Livecd:
1. From Ubuntu, I re-did the nooter img on the nook to make sure that it wasnt the issue behind all of this.
2. I spent 2-3 hours being instructed on how to work Ubuntu and run commands from the terminal. (That wiki really assumes a lot, it's hardly a step-by-step method, even this Linux expert was stumped with some of the instructions.)
3. Finally was able to see the nook with the adb device listing command.
4. Loaded z4 for Super User privileges, and added 5-6 more apps to test out.
5. Restarted my computer while playing around with the new programs on the nook.
6. Tried accessing the nook through win7 again, but no luck. Uninstalled the driver, etc, tried several things, still wouldnt work from windows. Tried from my win7 netbook also, but no dice.
Something either in my win7 installs or in my computer configurations is preventing communication between pc and nook color.
At least Ubuntu works.
pdanet
the drivers from pdanet seem to work just fine and will automatically install, never has used pdanet application though.
bg
http://www.junefabrics.com/android/
just download, don't buy, and install
moovius said:
3. Finally was able to see the nook with the adb device listing command.
Click to expand...
Click to collapse
Congrats! Glad to hear you were at least able to do it through Ubuntu. Would be nice to figure out your Win7 machine, but there may indeed be something funky with your install/machine.
moovius said:
At least Ubuntu works.
Click to expand...
Click to collapse
Hey Moovius, I just had something interesting happen.
I installed the NOOKdeveloper SDK and the android SDK Manager reported that ADP was updated and needed to be bounced. After that, I couldn't see or connect to my NC.
I ran the update again and it works. The Manager message mentioned updating ADB to support the device in the add-on package.
Might be worth a shot.
The SDK URL is http://www.barnesandnoble.com/nookcolor/developer/ - click on the "Add Add-on Site..." and slap it in there to get the SDK.
has anyone tried enabling the market with the autonook script? Im running Win7-64 and also had trouble rooting but got it to work. Cant figure this one out though. It either tells me I need to unmount my nook or that it can not write to the folder that the autonook file is in. Any help would be appreciated
jayman63 said:
has anyone tried enabling the market with the autonook script? Im running Win7-64 and also had trouble rooting but got it to work. Cant figure this one out though. It either tells me I need to unmount my nook or that it can not write to the folder that the autonook file is in. Any help would be appreciated
Click to expand...
Click to collapse
I've successfully run the autonook script over a dozen times under Win7-64. Other than a minor redirect issue (a ">" in the comments creates a "My" file), it's worked like a champ.
Have you ejected BOTH of the NC removable drives before running autonook? Have you tried running autonook as administrator?
Related
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
Yup. I have similar experiences on my linux box.
Try adb shell and see if you get a shell into the device.
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
the one time I had that problem, killing and starting adb fixed it, but it looks like you're already doing that.
Try launching Eclipse?
When I had the same setup as you (ubuntu 9.10 + Eclipse + all relevant parts), adb "just worked".
Running under Vista32bit though, adb only works when I have Eclipse running. Don't know why. Don't care why. Felt like banging my head into a wall when I realized that. (More specifically: under Vista32bit, my Vogue shows up with only one question mark, not a whole slew like you have.)
Anyway, try making sure Eclipse is running when you try to connect via adb. Who knows. Maybe it's a cross-platform issue.
Thanks for the reply. Everything works fine in Windows Vista 32bit, although the device serial number shows up as a question mark. I read somewhere that adb is broken for the 2.6.27+ kernels. There is a proposed fix:
review.source.android.com/#patch,sidebyside,10633,1,adb/usb_linux.c
I've compiled the source, tried the new adb and still not working... maybe the next official release will be better.
I shell access and can browse filesystem with adb shell, but ddms in Eclipse doesn't show much useful information.
Excellent work by the way! And thank you.
Found a compiled version of adb with the fix highlighted on code.google.com:
h t t p ://floe.butterbrot.org/external/adb.gz
Don't forget to make it executable.
That worked for me
This was hard to find. Thanks.
I just installed Android on my Sprint touch vogue. No luck using adb to get a shell on my phone.
My environments are Debian sid 2.6.32 and/or OS X Snow Leopard. I installed the r06 SDK and adb doesn't work under either OS. ./adb devices shows nothing, ./adb shell shows device not found. Under debian, I downloaded the recompiled version of adb linked above, no change
dmesg shows:
Code:
usb 1-3.2: USB disconnect, address 28
usb 1-3.2: new full speed USB device using ehci_hcd and address 31
usb 1-3.2: New USB device found, idVendor=0bb4, idProduct=0c02
usb 1-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
usb 1-3.2: Product: Android Phone
usb 1-3.2: Manufacturer: HTC
usb 1-3.2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 31
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk
Thanks for any help.
Might have figured something out that can help. uninstall the mass storage driver. I just did this and it connected right up.
1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Further info on problem:-
After cleaning up windows registry and driver remnants I noticed that very occasionally the adb devices command would actually return the connected device.
I did some tracing of adb actions by setting the adb_trace=all variable.
The traces at bottom of this post show a failed "adb devices" request and a successful one.
Interestingly I noticed that if adb server is started with trace mode on (see below) then subsequent "adb devices" commands will work correctly even if trace mode is turned off (set adb_trace=blank) straight after the start command has completed.
It would appear there is some sort of timing relate problem in adb which is masked when trace is on?
C:\>set adb_trace=all
C:\>set adb_trace=all
C:\>adb start-server
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>set adb_trace=
C:\>adb devices
List of devices attached
HT843KV06347 device
FAILED TRACE:-
C:\>adb devices
adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dce7 4: 30303063 000c
writex: 100 ok
writex: 100 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 100 ok
readx: 100 0x22dc67 4
readx: 100 0 No error
adb_close: 100(lo-client:5037)
error: protocol fault (no status)
SUCCESSUL TRACE:-
C:\>adb devices
adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dce7 4: 30303063 000c
writex: 100 ok
writex: 100 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 100 ok
readx: 100 0x22dc67 4
readx: 100 ok: 4f4b4159 OKAY
readx: 100 0x22dd24 4
readx: 100 ok: 30303034 0004
readx: 100 0x22dd24 4
readx: 100 ok: 30303161 001a
adb_close: 100(lo-client:5037)
_adb_connect: host:devices
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x22dce7 4: 30303063 000c
writex: 101 ok
writex: 101 0x22ee11 12: 686f73743a64657669636573 host:devices
writex: 101 ok
readx: 101 0x22dc67 4
readx: 101 ok: 4f4b4159 OKAY
readx: 101 0x22ddc7 4
readx: 101 ok: 30303134 0014
readx: 101 0x4c28c8 20
readx: 101 ok: 48543834334b56303633343709646576 HT843KV06347.dev
adb_close: 101(lo-client:5037)
List of devices attached
HT843KV06347 device
I had adb working fine before.
Now "adb devices" won't list my NC.
I have completely wiped/reinstalled CM7 and did a new install of Fedora but it still won't work.
I'm running CM7 nightly (177).
$ lsusb
Bus 004 Device 007: ID 2080:0002 Barnes & Noble NOOKcolor
Click to expand...
Click to collapse
Here is dmesg output after clearing (dmesg -c) and plugging in my NC:
$ dmesg
[36858.396242] usb 4-4: new high speed USB device number 7 using ehci_hcd
[36858.539784] scsi14 : usb-storage 4-4:1.0
[36859.539248] scsi 14:0:0:0: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.539472] sd 14:0:0:0: Attached scsi generic sg5 type 0
[36859.540895] scsi 14:0:0:1: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.540983] sd 14:0:0:1: Attached scsi generic sg6 type 0
[36859.551005] sd 14:0:0:0: [sde] Attached SCSI removable disk
[36859.552254] sd 14:0:0:1: [sdf] Attached SCSI removable disk
Click to expand...
Click to collapse
When I connect it my NC acknowledges the connection with "USB debugging connected" (I've made sure that USB debugging is enabled as well).
I have tried running everything as root but my NC is never listed by "adb devices":
$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ sudo adb devices
List of devices attached
(nothing...)
Click to expand...
Click to collapse
I should note that I'm using the USB cable from the car-charger kit (the original cable broke...). Is that known to be a problem?
I have had some success with adbWireless but I'd really like for USB to remain an option.
Hello,
I bricked my KFHD and it is in a reset loop right now. I got a factory cable and plan to try repairing it via fastboot. I need your kind assistance with the proper commands to flash the stock ROM and get out of fastboot if needed. I know that there are instructions for doing so in the original KF but I am not sure that it applies.
Thanks.
samio2 said:
Hello,
I bricked my KFHD and it is in a reset loop right now. I got a factory cable and plan to try repairing it via fastboot. I need your kind assistance with the proper commands to flash the stock ROM and get out of fastboot if needed. I know that there are instructions for doing so in the original KF but I am not sure that it applies.
Thanks.
Click to expand...
Click to collapse
Please describe the "reset loop" you are experiencing.
Well at boot it detects something wrong and it prompts me either to reset or reboot. Regardless of what I choose it always returns me to the same prompt. Meanwhile there is no usb connectivity what so ever. I tried the 20 second hold on the power button but nothing changed
samio2 said:
Well at boot it detects something wrong and it prompts me either to reset or reboot. Regardless of what I choose it always returns me to the same prompt. Meanwhile there is no usb connectivity what so ever. I tried the 20 second hold on the power button but nothing changed
Click to expand...
Click to collapse
When choosing "reset" does it look like its doing anything or does it just reboot?
Hello!
Ive got the same Q.
Messed up preinstalled keyboard, added some apk to /system/app folder. Now my kindle acts very bad....
Default settings in device section doesn't help. I tried to copy update....bin file to kindleupdate folder but it doesn't help, kindle won't flash (as i've already have last ver)
So, is there any way to flash KHD in fastboot mode, or using update.zip file? Mayby have someth like [UTILITY] Kindle Fire Unbrick Utility V1.1! ?
Thx a lot
It starts resetting and a progress bar shows and completes in a couple of seconds. Then it reboots back to the same prompt
I doubt factory reset would help. If my experience is any indication, factory reset will not undo any changes you did to /system. If you messed it up before resetting, you'll still be messed up after.
I think I messed up the /system and I want to try to reflash it
the good news is once you disconnect the cable the device exits fastboot also it shows up as android adb interface in device manager. but I could not get adb to see it. don't know why. I used the same PC that I used to root it and a mac but could not get adb to see it.
samio2 said:
I think I messed up the /system and I want to try to reflash it
Click to expand...
Click to collapse
What were you doing in /system before the problem started?
Was trying to install Google play. Not sure where i messed up
Do you still have adb access?
The device shows up in the device manager. But adb can't see them
samio2 said:
The device shows up in the device manager. But adb can't see them
Click to expand...
Click to collapse
What does your device manager say?
on windows it said android adb deive (or interface). as for the mac it is the same case and I used the usb probe and here is the output
Code:
High Speed device @ 2 (0x26200000): ............................................. Composite device: "Tate-PVT-08"
Port Information: 0x001f
Captive
Attached to Root Hub
Internal Device
Connected
Enabled
Device Descriptor
Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x1949/0x0007 (Lab126)
Device Version Number: 0x0100
Number of Configurations: 1
Manufacturer String: 5 "Texas Instruments"
Product String: 1 "Tate-PVT-08"
Serial Number String: 2 "XXX"
Configuration Descriptor: ....................................... "Android Fastboot"
Length (and contents): 32
Raw Descriptor (hex) 0000: 09 02 20 00 01 01 03 C0 32 09 04 00 00 02 FF 42
Raw Descriptor (hex) 0010: 03 04 07 05 81 02 00 02 00 07 05 01 02 00 02 00
Unknown Descriptor 0020:
Number of Interfaces: 1
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 100 ma
Interface #0 - Vendor-specific .............................................. "Android Fastboot"
Alternate Setting 0
Number of Endpoints 2
Interface Class: 255 (Vendor-specific)
Interface Subclass; 66 (Vendor-specific)
Interface Protocol: 3
Endpoint 0x81 - Bulk Input
Address: 0x81 (IN)
Attributes: 0x02 (Bulk no synchronization data endpoint)
Max Packet Size: 512
Polling Interval: 0 ( Endpoint never NAKs)
Endpoint 0x01 - Bulk Output
Address: 0x01 (OUT)
Attributes: 0x02 (Bulk no synchronization data endpoint)
Max Packet Size: 512
Polling Interval: 0 ( Endpoint never NAKs)
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 255 (Vendor-specific)
Device Subclass 255 (Vendor-specific)
Device Protocol 255
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Configuration Descriptor Device gave an error kIOReturnSuccess (0x0) when asked for first 4 bytes of descriptor
Configuration Descriptor Device gave an error kIOReturnSuccess (0x0) when asked for first 9 bytes of descriptor
Well, that's helpful. It says you're in fastboot. Try using fastboot to change your bootmode to either recovery or normal mode and see if you can get a different result.
Shouldn't adb recognize it to work with faatboot or are they separate?
how do change the bootmode? How to change it back?
I tried fastboot reboot but all i got is waiting for device message.
samio2 said:
Shouldn't adb recognize it to work with faatboot or are they separate?
how do change the bootmode? How to change it back?
I tried fastboot reboot but all i got is waiting for device message.
Click to expand...
Click to collapse
ADB and fastboot are completely separate.
Try "fastboot devices"
fastboot devices shows nothing for me
That's likely an issue with your drivers. Try reinstalling them. Or better yet, try the SoupKit and save yourself some hassle.
I've been trying this for most of the day, having read everything here about doing it, and even watching the video.
Unfortunately, I let the phone update to 14.1.G.2.257, but I found the instructions on how to flash back to the previous 1.534. The flashing worked perfectly.
I am trying to use Root_with_Restore_by_Bin4ry_v32 having read how to and watched the tutorial. USB debugging is enabled, as is Unknown Sources, and the 'adb devices' command in the stuff folder of the aforementioned program lists the phone.
However, it does not seem to work. I get the following output:
Code:
C:\xpe>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.11.2013) v32 =
======================================================================
Device type:
0) Xperia Z1 14.1.G.1.534 Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 0
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
error: protocol fault (no status)
2881 KB/s (2242263 bytes in 0.760s)
error: protocol fault (no status)
error: protocol fault (no status)
133 KB/s (1230 bytes in 0.009s)
error: protocol fault (no status)
Unable to chmod /data/local/tmp/busybox: No such file or directory
Running Exploit
error: protocol fault (no status)
rm failed for /data/local/tmp/getroot, No such file or directory
error: protocol fault (no status)
error: protocol fault (no status)
Rebooting now, after reboot all should be done!
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
The phone reboots, but there is no SuperUser app. I have re-run the program many times, reflashed the stock firmware again to make sure, and banged my head against my desktop several times to no avail.
Please help...
Rick.
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
gregbradley said:
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
Click to expand...
Click to collapse
Yes thanks, USB debugging and unknown sources are enabled. Is this the screenshot you need to see?
**Edit**
I got it to work!
I just pulled out my laptop which had a clean install of Windows 7 as of a few days ago, installed the above stuff (plus ADB drivers from pdanet) on that, and it worked.
Why it didn't work on my main PC I have no idea, but it is probably an issue with some driver somewhere messing things up. I did try reinstalling all of them, but to no avail.
Anyway, got it now. Thanks!