Related
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.)
Hey all. I need some help because I fear that my lovely Kindle Fire is gone to heaven for good. I've read through so many threads and tried so many little tricks, it's really becoming frustrating.
So I was installing a ROM, and it didn't work out properly. My KF is stuck at the yellow triangle (fire fire fire) and will not budge no matter what I do. To make sure it wasn't an empty battery, I left the KF plugged in to my wall charger for many hours (both with the yellow triangle on screen and completely turned off). All that happened was it got really hot.
I've tried the following:
1. Kindle Fire Utility (recovery/fastboot) didn't work, just says device not found/offline
2. Kindle Fire Unbrick Utility (recovery loop/stuck at logo) didn't work, again device not found/waiting for device
3. Changing the bootmode via ADB
(fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot)
(fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot)
on both attempts, it just says waiting for device. Yes I tried shutting off the KF and then typing the commands and then plugging in the cable. Still nothing.
4. Reinstalling the drivers
I tried reinstalling the drivers using KFU drivers, but I could not remove the old drivers first because my KF is not showing up in my device manager, either as Kindle Fire or Unknown Device (exclamation point). I tried unplugging and reconnecting to see if anything popped up in device manager, but nothing changed.
The only thing I haven't tried is a factory cable because I don't have one and I don't have the money for one.
I'm using Windows 7 64-bit.
Any help would be greatly appreciated. I've been trying to get this working again for almost two weeks now. I'm off from work today, so i'd really like to get this fixed.
Thanks in advance.
1. Your KF is stuck at the yellow triangle, so fff is OK, fastboot mode is OK!
2. Confirm that your driver is OK, that will be "ADB Composite Device".
3. Power Off your KF.
4. fastboot oem idme bootmode 4000
5. Power On your KF.
6. fastboot reboot
sigporsson said:
1. Your KF is stuck at the yellow triangle, so fff is OK, fastboot mode is OK!
2. Confirm that your driver is OK, that will be "ADB Composite Device".
3. Power Off your KF.
4. fastboot oem idme bootmode 4000
5. Power On your KF.
6. fastboot reboot
Click to expand...
Click to collapse
My driver is NOT ok. I don't see Kindle Fire, Unknown Device, or ADB composite device in my device manager.
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Go to your device manager on your PC and uninstall all of you android/kindle related drivers, then install the drivers that came with kfu and reboot your pc
Sent from my LG-VM670 using Tapatalk
If you are using Win XP
Had a similar problem the first time I tried to work with my KF. This was on my Win XP computer (had no issues on my Win7 computer).
What fixed it came from this thread http://forum.xda-developers.com/archive/index.php/t-1479063.html. Basically this part:
the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section
After correcting those issues, and computer and KF reset, Adb recognized KF.
Hope that helps. Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.15 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
I also have the same problem (infinite bootloop). And I have also tried all the the solutions on this page. In OP and in the previous reply. Nothing worked. It still stuck in the infinite bootloop. FYI I tried flashing AOKP milestone 5 KF version and that's how I got here. Please help us!!!
king_xerxes said:
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Click to expand...
Click to collapse
I tried that previously. But just to make sure I tried it again a few times with different KFU commands. Still nothing. It never changes from "waiting for device" and nothing happens on the Kindle Fire.
pbailey212 said:
Go to your device manager on your PC and uninstall all of you android/kindle related drivers, then install the drivers that came with kfu and reboot your pc
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I also tried this previously. There are no android devices in my device manager. No android phones (even though I have a GS2), no ADB composite devices, no unknown devices. There is one USB composite device, but I don't think it's the Kindle Fire.
Docs009 said:
Had a similar problem the first time I tried to work with my KF. This was on my Win XP computer (had no issues on my Win7 computer).
What fixed it came from this thread http://forum.xda-developers.com/archive/index.php/t-1479063.html. Basically this part:
the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section
After correcting those issues, and computer and KF reset, Adb recognized KF.
Hope that helps. Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.15 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
I read through the thread, and yes, one of the adb_usb parts was missing. I added it in both the personal .android folder as well as in the KFU folder and the Kindle ADB folder. Didn't change anything. I retried the KFU as well as the adb fastboot commands. nada.
Thanks for all your replies. I know there are many threads saying that you can't brick the KF. I think I might be the exception to the rule.
I'll still try any other options that you guys can give me, but i'm kinda giving up at this point. Maybe i'll sell it for $75 bucks to whoever wants it and thinks they can fix it.
Before you give up, read this. http://forum.xda-developers.com/showthread.php?p=23747671
Your only problem is a driver issue and you are FAR from bricked, trust me.
[Edit:] Wait, I take that back...I'll buy your Fire for $75
Seriously though, read that guide from "What are drivers". The title may sound like its beneath you but I think there is some important information in that guide that you may have missed.
soupmagnet said:
Before you give up, read this. http://forum.xda-developers.com/showthread.php?p=23747671
Your only problem is a driver issue and you are FAR from bricked, trust me.
[Edit:] Wait, I take that back...I'll buy your Fire for $75
Seriously though, read that guide from "What are drivers". The title may sound like its beneath you but I think there is some important information in that guide that you may have missed.
Click to expand...
Click to collapse
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Techngro said:
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Click to expand...
Click to collapse
What you fail to realize is that the problem isn't your Kindle. It's doing exactly what it was programmed to do. I'm willing to bet the problem is your computer.
But it's your device. And if you want to sell it to me for $75, so be it. Who am I to stop you?
Techngro said:
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Click to expand...
Click to collapse
That's an oddball situation if Windows won't even detect the device. It might be something simple like a bad USB cable... I've seen more than a few people say swapping cables helped. Possibly a problem with Windows like...
http://support.microsoft.com/kb/314634
I don't know what version you are using, so I'm grasping at straws. If you've got spare hard/thumb drive, you could try Firekit and see if that helps. It might be the cure for your Windows blues...
http://forum.xda-developers.com/showthread.php?t=1430038
It might be a bit of a learning curve if you aren't familiar with Linux, but it's really not that bad. Linux seems much more robust when handling these devices... Firekit has a script to change the bootmode to normal, so that might fix it right up.
EDIT: Sorry, missed the part where you said you are using Win7 x64.
Troubleshoot the problem. Are your Windows USB drivers working? When you plug in a thumb drive does it show up? Is your mouse on USB? If so, plug your Kindle into the mouse port. Have you tried rebooting your computer? Do you have administrator privileges on your computer? Windows 7 right? Have you taken ownership of it?
[Edit:] You snuck that one in on me kinfauns. I didn't even think about this cable being bad, good call. That's probably it.
I am having the same issues. Never happened until today, i wasn't doing anything to my kindle fire came back to it being frozen with the Triangle with fire in the middle of it.
I can Normal boot it and it boots up, but then powers down and restarts and goes back to being frozen at the same image.
I installed FireFireFire and it changed nothing. I'm guessing my Kindle is messed up for good? I can't get it to stay booted up and it has Full charge too.
DarkenedMatter said:
I am having the same issues. Never happened until today, i wasn't doing anything to my kindle fire came back to it being frozen with the Triangle with fire in the middle of it.
I can Normal boot it and it boots up, but then powers down and restarts and goes back to being frozen at the same image.
I installed FireFireFire and it changed nothing. I'm guessing my Kindle is messed up for good? I can't get it to stay booted up and it has Full charge too.
Click to expand...
Click to collapse
I'm reasonably sure your situation is different than the OP...
http://forum.xda-developers.com/showthread.php?t=1623244
kinfauns said:
I'm reasonably sure your situation is different than the OP...
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
Alright, i'll go through trying out stuff in that thread. I really hope something fixes it because i know the thing was charged when it started acting up on me. I just get the Little android and the Kindle fire logo and the Light at the bottom on the kindle is orange instead of green.
/Edit
I flashed firefirefire 1.4a just now to see if it'd fix it. It didn't, also it's new battery feature doesn't say that my battery needs charged.
I don't know what to do now. I read something about getting the Stock boot .img file but i have no clue how to go about getting this.
/Edit
Stock boot.img did nothing.
I need to know how to wipe everything on the kindle and get it back to brand new, someone want to point me in the correct direction?
Or, if someone finds a fix to this problem let me know.
/Edit
I installed the latest twrp, Firefirefire, then booted it in recovery mode.
It did what it had to do and i got something telling me there was something wrong with the app storage i think and that it had to be completely wiped ( reset to factory.) I did that and it fixed it.
I now have to start all over with my root exc exc.
Same issue here, no power will go to the screen or USB or power button. I can't turn it on at all. Tried in Ubuntu, doing the short while running the script, nope. Nothing happens in Device manager when I plug it in. I'm getting one of those cables and hoping that might help for the future. Sucks. Also on x64 Win 7, but tried on Ubuntu as well. I'll try at work tomorrow on x32, but I doubt anything will happen.
Solved...kinda
Well, thanks for all the responses guys. Even though none of the suggestions proved fruitful i'm glad that people tried to help.
Anyway, I finally got my Kindle Fire working and I did it by removing the only variable that I could not before, my computer itself. I dug out my old laptop (keyboard doesn't even work so I used Synergy) and connected my KF. It registered as an ADB composite device, I installed the drivers via KFU and then booted into recovery and immediately wiped and installed a backup.
So my suggestion for anyone who has tried everything else is to try and start from scratch on a new computer. Use a friends computer if you have to, but I think being able to start from scratch with the new drivers was the key.
I hope this helps someone in the future.
Or just do a system restore on your computer before the point you messed up your drivers I have done it and it works .This was after a bad driver install just simply rolled my PC back a month.
can you please go into a little more detail
king_xerxes said:
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Click to expand...
Click to collapse
im having the same problem exept on the kindle fire screen. i want to try this but i cant understand what you mean. will you please explain a little more?? also twrp is gone so i have next to nothing i know how to do.
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!
been looking for something liek this. I have no idea how to even install the drivers for adb and stuff
any specific instructions to install/
or just plug and play?
thx!
Thanks for your drivers.
BTW, what's the APX mode for Nexus 10? How to access APX mode?
padest.com said:
Thanks for your drivers.
BTW, what's the APX mode for Nexus 10? How to access APX mode?
Click to expand...
Click to collapse
APX is for tegra devices, so you would not need this mode on nexus 10.
Megiddo2000 said:
been looking for something liek this. I have no idea how to even install the drivers for adb and stuff
any specific instructions to install/
or just plug and play?
thx!
Click to expand...
Click to collapse
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
1wayjonny said:
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
Click to expand...
Click to collapse
Hey mate,
Can you tell me the driver names (USB\VID_**) for the Nexus 10 so I can add them to the automatic install in the Toolkit. I looked in your inf file but couldnt seem to find a Nexus 10 section like the others you have added. I need the adb and fastboot driver names and download mode driver names if they are included in your pack.
If anyone else also knows this please let me know as soon as possible as I want to release the Toolkit tonight.
Mark.
mskip said:
Hey mate,
Can you tell me the driver names (USB\VID_**) for the Nexus 10 so I can add them to the automatic install in the Toolkit. I looked in your inf file but couldnt seem to find a Nexus 10 section like the others you have added. I need the adb and fastboot driver names and download mode driver names if they are included in your pack.
If anyone else also knows this please let me know as soon as possible as I want to release the Toolkit tonight.
Mark.
Click to expand...
Click to collapse
Hello mskip,
I know what you mean and its not listed separated in the INF from Google but I can tell you its one of these below for ADB but the only Bootloaders one is the fastboot. Google stuck it under the generic section, not sure why. I do not own one so I can not verify sorry.
Code:
;Google Nexus (generic)
%GoogleNexusBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE1
[B]%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01[/B]
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
1wayjonny said:
Hello mskip,
I know what you mean and its not listed separated in the INF from Google but I can tell you its one of these below for ADB but the only Bootloaders one is the fastboot. Google stuck it under the generic section, not sure why. I do not own one so I can not verify sorry.
Code:
;Google Nexus (generic)
%GoogleNexusBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
Click to expand...
Click to collapse
Thanks for the info I figured maybe it was those but needed to be sure as I dont have the device either yet (stupid google) and needed to be sure.
Mark.
These drivers are working for my N4, and were working for my N10 when inside Clockwork recovery, but they are not recognizing the device when it's booted. The drivers say they are updated, and when I try to uninstall them, there is no option for removing the driver software. The device is showing up in Portable Devices inside Device Manager.
Can I manually delete the driver software to try again?
Edit: I'm stupid. Didn't have USB debug enabled.
My nexus 10 said it was Nexus a Nexus 4 under devices
Maybe this is normal... anyhow great driver... works great updated from Samsung drivers I was using b4 :^}
What about the drivers installed by Kies.... Should I be deleting those as well?
Sent from my Nexus 10 using Tapatalk 2
detects my nexus 10 as a nexus 4
---------- Post added at 03:15 PM ---------- Previous post was at 03:08 PM ----------
nvm.... was able to root with Superboot regardless
Drivers work great thank you for your work. Was able to root with my Nexus 10 with Superboot without unlocking. Made the whole process way easier.
1wayjonny said:
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
Click to expand...
Click to collapse
Can you explain more details? I just have no idea how to use it.
I'm just very new to all these stuff.
Any help will be much appreciated.
How would I get the driver to work with my AT&T One X? Keeps saying the driver is up to date with the "MTP USB Device" driver.
Universal Naked Driver
Thank you very much for this!
Deleting old Drivers
I'm working on getting the naked drivers working on an Asus transformer prime but when I go to uninstall the old/automatic drivers there is no option to delete them so when I disconnect it from my laptop and reconnect it (offline) it still picks up the old drivers.
when I try to manually change the drivers (with the official one still installed) it tells me
" The software you selected does not contain a compatible software driver for this device. if the folder contains a driver make sure it is designed to work with windows for 32-bit systems."
help
no matter what i do i cant root my nexus 10, i had it rooted before the 4.2.2 update, doing it via my girlfriends laptop running but the laptop broke and cant get root access again because im running windows 8 and my days what a pain in the arse this is to do,
i see in device manager when nexus 10 is connected as followed:
Other devices:
! ADB interface with warning sign
! Unknown device
but no android phone or anything
portable devices
nexus 10
please help guys im just trying to do one of the simplest things here in rooting,, took 30secs on windows 7
Thanks! makes things a lot easier!:good::good:
whats the adb command to get the device bootloader version?
Hi Forum Users,
I rooted my Kindle Fire tablet, its now running the Jelly Bean ROM (4.2.2_r1 ROM here) without problems.
However, since that my (german) Windows 7 doesnt recognize the tablet anymore. It appears in the list of devices, but with a yellow exclamation mark. I deleted it, trying to reinstall the table drivers, without success.
This is for sure a newby question, but: How to I get a proper driver installation so that my Windows 7 works with my Kindle Fire that runs the Jelly Bean ROM?
Thanks
D-Ta
giggollo said:
Hi Forum Users,
I rooted my Kindle Fire tablet, its now running the Jelly Bean ROM (4.2.2_r1 ROM here) without problems.
However, since that my (german) Windows 7 doesnt recognize the tablet anymore. It appears in the list of devices, but with a yellow exclamation mark. I deleted it, trying to reinstall the table drivers, without success.
This is for sure a newby question, but: How to I get a proper driver installation so that my Windows 7 works with my Kindle Fire that runs the Jelly Bean ROM?
Thanks
D-Ta
Click to expand...
Click to collapse
http://db.tt/vXXeuL10 Try this replace that file with the one I have provided in the drivers folder for kfu. Rerun driver bat then plug your kindle in adb should be back online. Also make sure you have adb debugging enabled under settings/developer options.
...works only in debugging mode
Try this replace that file with the one I have provided in the drivers folder for kfu. Rerun driver bat then plug your kindle in adb should be back online. Also make sure you have adb debugging enabled under settings/developer options.[/QUOTE]
thanks, i can indeed get in online in KFU, but the tablet only connects to PC via USB if I run it in debugging mode. If I disable the debugging mode, I still see the Amazon Kindle Fire device in my device manager, however with a yellow exlamation mark and I dont have access to its storage any longer (i.e. its not properly recognized by my PC any more). This used to work before I put the Jelly Bean ROM on it. Is there a solution ?
When you go to the device in device manager. Go to driver. What does it say there?
tobiascuypers said:
When you go to the device in device manager. Go to driver. What does it say there?
Click to expand...
Click to collapse
that no driver is installed (only when debug mode is disabled though).
however, i did install the driver file that you post above using the KFU .bat file and it did do it
I tried many things, still doesnt work.
I can make Windows 7 work with the device in debugging mode, but not if debugging mode is switched off.
Plug your kindle in uninstall the driver with the exclamation point, unplug your kindle, rerun driver bat, then plug your kindle in and check device manager.
Thepooch said:
Plug your kindle in uninstall the driver with the exclamation point, unplug your kindle, rerun driver bat, then plug your kindle in and check device manager.
Click to expand...
Click to collapse
its still not working, unfortunately. it would recognize a new device, try to install the driver (but fail), and then show the kindle fire in the device manager list - again with the yellow exclamation mark. :crying:
http://forum.xda-developers.com/showthread.php?t=2167851
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2167851
Click to expand...
Click to collapse
amazing, the device is now properly listed in the device manager list - THANKS: for the suggestion ( i wasnt aware of the hardware-ID adjustments that are ROM specific and need to be done in the driver file.
BUT: i still dont see the kindle in the list of devices attached (after typing adb devices)... neither do I get the USB mass storage drive I used to get when I connect the tablet via USB to my PC. Still, I am doing all this in no-debugging mode.
How Do I get the mass storage mode back?
Halfway there ( i guess)
Okay, if you added the hardware ID for the device in mass storage mode on (debugging turned off) you need to remove it. Basically, if you have anything in the android_usb.inf with a PID of 0005, delete it.
However, if you want an ADB connection, you need to add the hardware ID of the device while debugging is turned on.
soupmagnet said:
Okay, if you added the hardware ID for the device in mass storage mode on (debugging turned off) you need to remove it. Basically, if you have anything in the android_usb.inf with a PID of 0005, delete it.
However, if you want an ADB connection, you need to add the hardware ID of the device while debugging is turned on.
Click to expand...
Click to collapse
;Kindle Fire
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0005&REV_0216
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
...thats what i have in my android_usb.inf and that what it shows me as the hardware-ID. Are you saying I should delete that? ... and then what?
giggollo said:
;Kindle Fire
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0005&REV_0216
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
...thats what i have in my android_usb.inf and that what it shows me as the hardware-ID. Are you saying I should delete that? ... and then what?
Click to expand...
Click to collapse
Yeah, that's the PID for the device in MTP. Delete those lines, and reinstall your drivers.
You can find more information here:
http://forum.xda-developers.com/showthread.php?t=2179748
I am trying to run CWM recovery to backup my OUYA OS. When i go to fastboot the .img, the command prompt says everything was fine but I have a black screen with my PC detecting a new device called OUYA_1_1 and its asking for drivers.
I have looked all over the Forums and Google and saw people talking about it but no one addressed the issue.
is there a driver i am missing or something i need to add to the android_winusb.inf file?
Many thanks in advanced
GarbageGamer said:
I am trying to run CWM recovery to backup my OUYA OS. When i go to fastboot the .img, the command prompt says everything was fine but I have a black screen with my PC detecting a new device called OUYA_1_1 and its asking for drivers.
I have looked all over the Forums and Google and saw people talking about it but no one addressed the issue.
is there a driver i am missing or something i need to add to the android_winusb.inf file?
Many thanks in advanced
Click to expand...
Click to collapse
When you are asked for a driver go to find it on your computer.
Then go to your android sdk install folder.
Then extras.
Then google
and then usb_driver.
and stay in this folder for your driver, don't search further on AMD64 or i386.
Have you modified the android_winusb.inf ?
ElMeteK said:
When you are asked for a driver go to find it on your computer.
Then go to your android sdk install folder.
Then extras.
Then google
and then usb_driver.
and stay in this folder for your driver, don't search further on AMD64 or i386.
Have you modified the android_winusb.inf ?
Click to expand...
Click to collapse
I tried what you said and it did not work . Yes i have modified it based on the tutorials adding the following
[Google.NTx86]
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
Click to expand...
Click to collapse
Still cant find ANY info on OUYA_1_1, no drivers no nothing, for such a *easy to hack* system it sure is not easy to hack lol
hmm
try the test version of the OUYATOOLBOX, some people were having an issue with the actual releases...
try adding the OUYA code to the X64(I think thats what its called) part of the winsub. Also are you X64 bit system? if so try this code, if your system is stuck in recovery...http://forum.xda-developers.com/showthread.php?t=2352658
i had that issue when stuck in recovery and system as seen as a MTP USB device..
Lastcaress09 said:
try the test version of the OUYATOOLBOX, some people were having an issue with the actual releases...
try adding the OUYA code to the X64(I think thats what its called) part of the winsub. Also are you X64 bit system? if so try this code, if your system is stuck in recovery...http://forum.xda-developers.com/showthread.php?t=2352658
i had that issue when stuck in recovery and system as seen as a MTP USB device..
Click to expand...
Click to collapse
Went back and tried the test version of OUYATOOLBOX and tried the link both did not work , What am i missing ???? is it because im on windows 7 x64? everything els works except CWM recovery
:crying:
Are you in "none signed drivers" mode in windows ?
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4 Beta
ElMeteK said:
Are you in "none signed drivers" mode in windows ?
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4 Beta
Click to expand...
Click to collapse
it's telling me there are no drivers at all, but yes
I am having this exact same problem and I cant for the life of me figure out how to get past this to install recovery
try this
DrROBschiz said:
I am having this exact same problem and I cant for the life of me figure out how to get past this to install recovery
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2295645
GarbageGamer said:
it's telling me there are no drivers at all, but yes
Click to expand...
Click to collapse
I have had nothing but problems with setting up OUYA drivers on two different Windows 7 home premium 64 bit systems. Two months ago on my laptop after the SDK drivers didn't work I was able to use Samsung adb drivers. I have a new to me Acer PC that I am using as a htpc. It's a new install and I tried the Samsung drivers again, but it changed the device name to Samsung mobile phone. After hours of system restores and multiple driver configuration attempts, I finally got the SDK drivers to work by adding
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
To both [Google.NTx86] and the amd64 section,
BUT no matter what I do it still changes the device name. Now it says something like adb composite device, but the OUYA toolbox test version got everything installed. I only needed su and CWM, my existing supersu and BusyBox updated perfectly.
Here is exactly what i see after i fastboot the recovery image using the ouya tool box
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah
Me and Garbage Gamer are basically in the exact same position
Whatever we did wrong... its preventing us from pushing the boot img with fastboot
I DID IT !!!!!!! i am currently doing a backup as we speak, only problem is i am not sure what i did differently except switch to my laptop to start fresh. I loaded the android SDK and made the changes based on the tutorial except the only thing is i did the recovery install and fast boot using the OUYA Tool kit. it still came up with the device looking for drivers but it let me install recovery and make a backup which is all i needed. i am so happy lol but sad as i wish i knew what i did wrong initially , my best advice would be to start fresh on a new PC if you can
CMW and stock recovery both reassign the device different hardware ids. so, yes, in normal operation it is pid_7100&Mi_01, but put it in recovery (of any kind) then right click the device in the device manager, then go to details (xp, sorry) and the hardware id will be different.
you have to get the hardware id for ouya_1_1 and put it in where you would put pid_7100&Mi_01, then direct the device to the driver. then echo the driver again in terminal.
hope that helps. i can try to explain it a different way if you're unsure.
Ugh Guess ill try the entire process on my laptop and see if it helps
incase you didnt try the link Lastcaress09 posted earlier (its irrelevant if your on a x64 or x86 OS, the procedure is the same):
\/ propably the solution \/
ArdDarvis said:
CMW and stock recovery both reassign the device different hardware ids. so, yes, in normal operation it is pid_7100&Mi_01, but put it in recovery (of any kind) then right click the device in the device manager, then go to details (xp, sorry) and the hardware id will be different.
you have to get the hardware id for ouya_1_1 and put it in where you would put pid_7100&Mi_01, then direct the device to the driver. then echo the driver again in terminal.
hope that helps. i can try to explain it a different way if you're unsure.
Click to expand...
Click to collapse
\/ tutorial \/
iAmSmokey said:
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf, open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
now you should be able to continue the driver installation.
Click to expand...
Click to collapse
if that didnt help or you have a problem with the procedure, report back or ask.
also: in case you come up with a different solution, post it, somebody WILL have the same problem sooner or later.
Smokey! i looked for your link, but apparently i didn't look very hard. thanks for stepping in and finishing what i started.
also, thanks for the write up.
because i HATE going and getting the ID, putting in the inf, directing the hardware to the driver, yada yada, i just seperated the 3 hardware IDs (normal oppuration, recovery mode/CWM recovey, and fastboot) with commas. it works well so far. maybe try it out.
glad i could help
your right! seperating the ID's with commas seems to work so far, but im not really experienced in all this developement stuff, i rarely even used the cmd before i got my ouya, so somebody else has to do further testing.
I just found a relatively simple way to get a clean install of the universal adb drivers. I bought a Nexus 7 on Friday and rooted it using the Nexus Root ToolKit from WugFresh.com (also on xda).
The tool kit has a driver install wizard that includes a program "abdevoid" to help find and remove all adb drivers before installing new ones. There are four different sets of drivers to choose from as well. I used this utility to root and install recovery on my Nexus, then rebooted the PC to be overly cautious. I connected the OUYA and it installed automatically. I ran the adb devices command to be sure it was there and then proceeded to install su binaries and recovery using the test version of Foil's toolkit.
This is on a Windows 7 64bit home premium that is a very new install, but has had a ridiculous amount of adb drivers installed, including those from Kies, CWM Helium, and the Android SDK. Device manager lists the drivers as unsigned Google drivers version 7.something for adv. I could see the Windows driver wizard opening at every step and it all went off without a hitch. I highly recommend this method.
Sent from my SCH-I535 using Tapatalk 4 Beta