Develop Bugs

[Q] [DEV] Debugging on Kindle Fire via ADB?

Just hooked this baby up. Amazon, of course, doesn't provide any information on USB drivers or on how to enable debugging on the device. Probably one of their attempts at "security".
Anyway, looking for two things:
1. Any leads on drivers for windows. I could also do this on a Mac
2. How to enable debug mode so that I can actually test my damn apps on the device.

Everyone keeps talking about how they suspect this is running on cheapened-up BB Playbook hardware... not sure that would help at all...

breon said:
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Click to expand...
Click to collapse
keyesdav, this should help. Thought I'd cross-post (cross-quote?) it over here in case you didn't see / haven't found it yet.

I was able to use the google adb driver on win7 x64, but you have to add the device id to the ini file.
Edit %androidsdkdir%\google-usb_driver\android_winusb.inf
Try adding the following lines under [Google.NTx86] AND [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01

Still unable to get Kindle Fire to attach to Win 7 x64
I have a Lenovo W520 laptop. I've made these changes, however the Kindle Fire still comes up unrecognized in the Device Manager.
adb devices shows nothing
repeated adb kill-server, adb start-server no change
Help!
BTW, my "google_usb_driver" directory is in C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
Did they move it recently?

Did you go to Device Manager on your PC and then select the Kindle 'Unknown Device' and update the driver by selecting the Inf file you had edited? After updating the driver the system will then show the ADB connection. This is the same process to go through when doing the Root.

That worked!! Thanks!
(I didn't have to do this when I rooted my Galaxy Tab. Samsung provided a driver.)

[ADB/FB/APX Driver] Universal Naked Driver 0.72

Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!

Very good idea
Thanks

Your welcome, this was a semi-confusing download at first every package I found just looked like a mess or didn't work with fastboot for some reason.
Then I installed PDAnet and that worked right away but I wanted to use the offical Samsung drivers.
Enjoy!

trouble with XP
I am having a lot of trouble getting this to work with XP at work, anybody had any luck?
No problem with win7 at home though ...

Just wanted to mention that the .dlls in this driver package seem to be more recent (1.9 vs. 1.7):
http://dl.dropbox.com/u/4174784/usb_driver.zip

Valynor said:
Just wanted to mention that the .dlls in this driver package seem to be more recent (1.9 vs. 1.7):
http://dl.dropbox.com/u/4174784/usb_driver.zip
Click to expand...
Click to collapse
I used these as well. None of the Samsung driver packages would work with fastboot on my xp x64 machine. Someone had modified the adb source drivers to work with the GNex and these work great.

Valynor said:
Just wanted to mention that the .dlls in this driver package seem to be more recent (1.9 vs. 1.7):
http://dl.dropbox.com/u/4174784/usb_driver.zip
Click to expand...
Click to collapse
thanks for the drivers, worked great but when on boot loader ADB does not recognize the device
using windows 7 64

adb = Android Debug Bridge! only use on running Android system or recovery!
in bootloader use "fastboot"
use "fastboot devices" instead of "adb devices"

I will check out the XP issue it should be easy to resolve. I didnt test it out on XP sorry bout that. I will update the OP in the mean time.

Valynor said:
Just wanted to mention that the .dlls in this driver package seem to be more recent (1.9 vs. 1.7):
http://dl.dropbox.com/u/4174784/usb_driver.zip
Click to expand...
Click to collapse
Thanks but these are not the Samsung drivers which is why the version number is so different. I extracted these from the most recent package from Samsung that I found.
That being said the drivers you linked will probably work fine but are more generic.

got the drivers to work in XP
I removed all USB drivers from the XP and started to reinstall drivers as needed. Now it works in XP, thanks.

dmue said:
adb = Android Debug Bridge! only use on running Android system or recovery!
in bootloader use "fastboot"
use "fastboot devices" instead of "adb devices"
Click to expand...
Click to collapse
Can't believe i missed that -_-
Thanks dmue
Confirmed to work on Windows 7 x64bit

bandur said:
I removed all USB drivers from the XP and started to reinstall drivers as needed. Now it works in XP, thanks.
Click to expand...
Click to collapse
Thanks for confirming the XP install. I will update the OP again. =)

1wayjonny said:
Thanks but these are not the Samsung drivers which is why the version number is so different. I extracted these from the most recent package from Samsung that I found.
That being said the drivers you linked will probably work fine but are more generic.
Click to expand...
Click to collapse
Those drivers are modified from the ADB source drivers that are downloaded by the SDK to support the GNex in fastboot. I havent tried your download yet but i installed the full 1.4.8.0 .exe package i downloaded from Samsung. Those worked except for fastboot which this download worked for me on XP x64. This phone was a PITA to get fastboot working on my laptop.

Where do I unzip the files to?

Anywhere, then when Windows asks where the drivers are point it to the folder where you extracted them to

sabooher said:
Those drivers are modified from the ADB source drivers that are downloaded by the SDK to support the GNex in fastboot. I havent tried your download yet but i installed the full 1.4.8.0 .exe package i downloaded from Samsung. Those worked except for fastboot which this download worked for me on XP x64. This phone was a PITA to get fastboot working on my laptop.
Click to expand...
Click to collapse
Correct I had the same issue, when modifying the *.inf I was able to get them working with ADB. Give them a whirl when you get a chance and let me know what you think.
*EDIT* These are not fully working with fast-boot yet but I update as soon as possible.
luffyp said:
Where do I unzip the files to?
Click to expand...
Click to collapse
Any where but in your device manager you will find your phone with no driver, just right click "Update Driver" and point it to where you unzipped it.
It will install the driver for you.

Valynor said:
Just wanted to mention that the .dlls in this driver package seem to be more recent (1.9 vs. 1.7):
http://dl.dropbox.com/u/4174784/usb_driver.zip
Click to expand...
Click to collapse
Hello I understand what you mean by 1.7 vs. 1.9 now
**Update**
I have found the fastboot issue and will update v2 soon I just tested on a fwe system with no prior drivers working with ADB and fastboot.
The first set of drivers did not work with fastboot as an FYI. v2 will be the same files just the *.inf will be updated.
Should have it up in a few.

1wayjonny said:
Hello I understand what you mean by 1.7 vs. 1.9 now
Click to expand...
Click to collapse
Glad I could help you out. My Nexus Prime should be here tomorrow, the wait is killing me.

so out of all these which one works with fastboot?
Sent from my Galaxy Nexus using Tapatalk

[Q] Usb Debugging drivers not working after flashing custom ROM

Hi After flashing this ROM my usb debugging driver stop working....
I've Flash this rom http://forum.xda-developers.com/showthread.php?t=1766829
I need them to use with eclipse and I am using Windows 7 32bit
Any one knows about it?
Thanks

Google usbdeview.exe un install all moto drivers reboot computer. Plug phone in let computer reload all the drivers.
http://www.nirsoft.net/utils/usb_devices_view.html.
Sent from my MB855 using xda premium

Try going to settings and developer options and enabling it. There's a switch at the top to turn on developer options and make sure android debugging is checked. As well there was a moderate driver change with jelly bean. I added these 2 lines to the already long list of ids saved the win_usb file then reinstalled the driver now adb works
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
to [Google.NTamd64] and [Google.NTx86] in android_winusb.inf before it would recognize the drivers, but after that it worked.

[Q] Ouya Toolbox can't detect my ouya...

I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick

Rick7C2 said:
I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick
Click to expand...
Click to collapse
There's a "test" version, try it.

ElMeteK said:
There's a "test" version, try it.
Click to expand...
Click to collapse
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.

Rick7C2 said:
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.
Click to expand...
Click to collapse
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.

Rick7C2 said:
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.
Click to expand...
Click to collapse
Well I figured out how to bypass needing fastboot drivers and I am now in recovery only to find out I NEED a USB Keyboard well fml... I guess I gotta go buy a keyboard to flash my new rom.
Anyways I guess this can be closed/deleted.

could you please share how you got around needing fastboot drivers?

the ouya has a different hardware id when it is in fastboot mode. In fact, normal operation, recovery, and fastboot are all different hardware ids.
connect the ouya, adb fastboot, then go to the device manager, find the device and notice the hardware id change.
gotta go to the android_winusb.inf and edit it to match the new hardware id.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_***&PID_****
^^^^ fill in the blanks.
OR!!! just separate the 3 different ids by commas.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01, USB\VID_****&PID****, USB\VID_****&PID_****
see what i did there?

WooHoo!!
Finally got it
About time! Thanks guys

ADB not working

I for the life of me can't figure out why my computer won't recognise my Pixel C for ADB.
Bit of background, using Win 7 64 bit. Never had a problem with this computer recognising phones for ADB (including various Nexus phones/tablets and Sony Xperia Z3 Dual).
My computer recognises the Pixel C as a device, and I've read through the various other posts of people having these problems, including:
http://forum.xda-developers.com/pixel-c/help/help-getting-pixel-c-recognized-adb-t3268991 and installing the adb installer suggested in that thread. I normally use Wug's Nexus toolkit and I don't think I've got a problem with the ADB drivers on my computer. I've tried to uninstall and then reinstall adb drivers a few times, but that doesn't work either.
I don't think its the cable I bought as well, because I have used the cable on another computer (borrowed) and ADB worked fine on that computer.
Any suggestions, or am I missing something?

Does it show up but can't find the driver? I have this issue with Windows 10 (currently fighting with it, that's how I found this thread). You need to add these device strings to android_winusb.inf for it to install the drivers, but it keeps telling me the correct hash isn't there, this is how I fixed it before.
Code:
;Google Pixel C
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_5201
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_5201
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_5201&MI_01
Edit: Just remembered an easier way: if the driver isn't installed, try to install it manually and select it from the list and select "Android Devices" then "ADB interface", and it should work.

Hi sorry, no-one every responded to the thread, so I didn't update it. I actually got it to work. Basically I deleted all my ADB drivers (and I had a lot, from all the various devices I have had over the years). I then plugged the pixel c in and boom it installed the driver correctly.