Database Users

[Q] Kindle Fire v7 cant Root :(

I have tried to root my kindle with the Kindle Fire v7 and have had no luck, It comes back with The system cannot find the path specified, I have installed the drivers and my kindle shows up as Android Composite ADB Interface. Thanks for any help in advance. I have also tried the burritoRoot with no luck. I am on version 6.2.1 I have never had problems with any android devises before but this seems alittle different.

i have the exact same problem. would really appreciate some help

I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me

I think for both us we already have the drivers installed. the problem is in running the actual bat for the utility. unless maybe we did something wrong in installing the drivers, but i don't think so. I actually used the exact same method to install the drivers as you did.

Check your system path for what the program is trying to run. If the path is there, make sure the file its calling is there. Google adding a path to windows for more info.

I think he problem has to do with the program not finding the kindle

claytybob said:
I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me
Click to expand...
Click to collapse
I am good all the way to "run.bat" and when i do i get (ADB Status: Online, ADB Rooted: No, Boot Status: Unknown, So i put in #3 and press enter withch is Install Perment Root with Superuser, that is when i get all The system cannot find the path specified.

alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...

Fairtrade128 said:
alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...
Click to expand...
Click to collapse
Well I guess im still not doing it right cause im still getting The devise not found.

I moved my install_drivers.bat file from the drivers folder to the same folder as run.bat and ran it (install_drivers.bat that is). It seemed to install correctly. Now, however, my kindle will not mount. So when I try to use the utility to install TWRP, it stops at "Installing TWRP... If we get stuck here for a while, power the kindle on and off a few times. < waiting for device >"
I have rebooted my device 6 times and it still does not work. My device no longer mounts, I can't even see it in device manager. I tried installing the drivers manually prior to moving install_drivers.bat. This seemed to work but I ran the install_drivers.bat after moving it anyway, maybe that makes me a noob.
Anyway, is there a way to fix this? I want root on my device!
EDIT: Here is the script I am getting in cmd when I run install_drivers.bat. I realize that the problem is I am running Windows 7 x86. But is there a way to run it for x86 instead of x64?
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
This version of C:\Users\Chris\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
This version of C:\Users\Chris\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
Click to expand...
Click to collapse

Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.

Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
Thank you, this is what finally got it working for me. I had tried everything; installed 3 different USB drivers, edited files, moved files around, all with no signs of progress. Finally this approach made everything work perfectly!

Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
THANKS, that worked like a champ. After I did that it work.
Sent from my SAMSUNG-SGH-I997 using XDA App

Kindle fire not seen

Ok so I am new hear and I was reading in THIS POST about installing TWRP using the Kindle Fire Utility. So I installed the drivers as directed and I see in my device manager "android ADB device" and in my taskbar I can eject the kindle. In File Manager I do not see the Kindle fire and the Kindle Fire Utility is not seeing my Kindle Fire. I am stuck and cannot post in the above forum because I have not made enough posts. Any help would be greatly appreciated. I would like to install Cynogen Mod to my Kindle fire to be able to access the full capabilities of this wonderful device.
Thank you

a good method to start is using kfu as you suggested but there are some tricks to get it running:
- place it to c:\ and rename it to "kfu" (it don't like spaces in pathname)
- try to install the correct drivers by running install_drivers.bat else install/update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
- pay attention on the driver verification level:
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
- the drivers are in c:\kfu\drivers\kindle
- right drivers for each mode:
normal & recovery boot -> android composite adb interface
fastboot -> android adb interface
once you got rid of the drivers you have to update the run.bat of kfu to work with burritoroot3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
now you should be good to go ...

Thank you BB3 I will give this a try later tonight. appreciate the help

man install buritoroot and TWRP(which installs and FireFireFire) by yourself when i tried with the kindle fire utility all got were errors, but when i installed it by myself everythink went smooth. Just find separate guide for every step
1.Root
2.TWRP and FireFireFire
3.CM7

I'm having the same problem as you and it sucks I just want to root it

Hate to necro post, but I'm having the same issue and none of the posted suggestions work. I have the ADB drivers installed (the Kindle is detected as "Android Composite ADB Interface"), but I did not install the drivers using the KFU batch file; I could never get it to stop producing the unsigned error, no matter what system settings I chose for unsigned drivers. I ended up doing a manual driver install and directing the installer at the driver files that came with KFU. Now KFU refuses to "see" the Kindle connected to my system and therefore I can't do a thing with it. I am able to browse the Kindle files in Windows Explorer (should I be able to? I've seen conflicting answers to this), but KFU always reports its ADB status as "Offline". Soft disconnecting the Kindle (hitting the "Disconnect" button on the Kindle) doesn't change anything, except removes my ability to browse the Knidle files (no surprise there).
This is a fully updated (6.3) Kindle and Windows XP. I did attempt to manually do what KFU does automagically prior to finding out about KFU, but that effort produced similar results; the Kindle was never detected by the SDK tools, despite the drivers loading properly. I have also tried multiple USB ports on my system, but they all produced the same results. About the only thing I haven't tried is a different USB cable, but if the Kindle is able to be "seen" by the OS correctly, I don't think the cable is a problem.

Have you tryed rebooting your computer? http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html or http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US nat3mil gives good instruction it helps to watch the video do the step while paused then move onto the next its how I did it the first time the second time I just used the utility was easy peasy cause drivers were already installed and functional

Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.

cogadh said:
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
Click to expand...
Click to collapse
If you followed the instructions to the t like not plugging in your device until you have the drivers installed .then you may have something on your computer preventing adb try the 6.2.2 method
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US or just keep looking for something that works cause people miss steps all the time sometimes its persistence or trial and error that gets results I'm very surprised your not seeing anything in device manager that applies to your kindle mine installed some drivers immediately when I connected it I had to change them to root it but it did show up in the list of devices as well as appearing next to my c drive as a kindle for SD card access but I'm on windows seven anything I connect does something.

No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.

cogadh said:
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
Click to expand...
Click to collapse
Could be your machine but don't use the utility and when you do put twrp on if ya get there use 2.0 the older version people are having trouble with the new one http://www.techtuple.com/477/how-to-root-kindle-fire-6-3-easily/ this is done through cmd without utility. Original thread here http://forum.xda-developers.com/showthread.php?t=1568340
About all the advice I can give you all else fails use another computer windows 7 machine things are more straight forward than xp
Edit: just a side note a lot of people are bricking their devices I keep remembering the Christmas story be careful you'll shoot your eye out also some people I believe are having success opening kfu attaching thier fire while off then powering up the kindle

I read somewhere that the utility doesn't work for xp wish I could find the post I think you need to push the files the old way using command prompt and you will get it sounds like your drivers are there but utility is useless

If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium

Thanx soup better said than what I was trying

if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.

First time i've ever rooted a kindle and i had the same problem.
To fix this just go to device manager and uninstall the driver and then unplug and replug in your kindle then run the utility.

oh no trouble at all rooting rooted rommed and rockin here took the 6.3 ota this morning with 5 mins I was rooted with fff twrp then went back to 1 of my restore points of cm7 after a backup of 6.3 thanx tho

soupmagnet said:
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
If all newbs do no other work but learn to use fastboot and adb it would save save a lot of grief for them and the ones helping them. jes sayin..

Thepooch said:
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
Click to expand...
Click to collapse
This will only work if the device is booted to a point where it will receive adb commands. Otherwise, use "fastboot devices". Sometimes if you are stuck at the bootloader it helps to shut your device down completely and restart before issuing fastboot commands.
Beyond that, it's a driver issue.
Sent from my Amazon Kindle Fire using xda premium

I had that same problem., but then I uninstalled the current drivers for my kindle altogether, and disabled them, then I ran install_drivers .bat again, then it worked.
Kindle Fire running KANG CM9
New developer, working on my own custom rom

[Q] Kindle has been wiped in TWRP and Windows only displays device as Unkown

My nephew managed to get into TWRP and somehow wiped the entire thing clean. I purposely keep a recovery .zip in there but even that's gone. When the Kindle is turned on it displays the Fire triangle but then the screen goes black and stays like that. I can boot into TWRP but can't use the mount option or adb because my computer, and the three others I've tried, refuses to recognize the Kindle. It shows up in Device Manager as Unknown and I can't manually install the driver. I've tried every combination of booting it with the computer off or on, uninstalling the Unknown driver, everything. Can you kind folks please save my butt? Thanks in advance for your responses.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Have you tried starting adb services and going back through the FireFireFire Utility, this has fixed a lot of boot errors that I had in the pass?
Let me know if you need help with starting adb services.
Thanks,
JohninLex

Thanks for your reply
Can you please elaborate on this a bit more? Maybe I'm not understanding correctly but I thought starting adb services wouldn't do anything in this instance since it wouldn't recognize the Kindle as being there at all? For instance, when I run Kindle Fire Utility it shows adb devices as being offline. If I could get the Kindle to show up as anything other than Unknown I'm certain I could just update the driver to an android device and have KFU take it over from there.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Did you root your Kindle "adb devices"
and the following commands?
adb shell chmod 777 /data/local/tmp
adb install Burritoroot3.apk
or did you download a file from the market to get root?
if you did it the above way with adb commands from a terminal would be great.
Either way lets set the driver, download the Kindle Fire Utility extract it to your desktop. or take note where you extracted it. Then go to your device manager and right click on the Kindle (unknown device) look for update driver and browse the the Kindle Fire Utility folder double click on the drivers folder and let it update the right driver you need for your OS (XP,Vista, 7 x86 or 64). Once it finds the right driver Open up a command prompt by going to start run and typing cmd and hitting enter. Once that is done download the KindleADB files and place them in the C:\ (drag and drop should be fine here ) go back to your command prompt and do the following commands:
** urname** C:\ " cd KindleADB " then hit enter
and then do " adb devices " it may or may not come back with your device sn but as long as it has started is what we are looking for.
Once that is done go back to your desktop leaving everything open and look through the Kindle Fire Utility until you find a file named Run.bat double click and hit run this will reinstall twrp and allow it to be remount-able. If you need a stock Kindle rom with update 6.2.2 I have a back up I can share with you.
I hope this helps but if it does not let me know and we can go back over the the driver section.
Thanks,
JohninLex

I've attempted installing the driver manually many times like you stated and on different PCs all containing KFU and the modified .ini file in the .android folder and the message I get when I attempt to manually update the driver is "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems." When I first got the message I attempted to do it in an x86 system and the driver would still not install. My inability to get ANY computer to read the kindle as anything other than Unknown is the main issue. Even if I could make it read as the default "kindle" with the exclamation point it would be enough for me to fix it. But if I can't get a driver to load I'm hopeless to fix it in any way.

Use Android composite driver on your PC to get adb working. Once the adb is working, there multiple ways to boot or install a new ROM. I recommend to start doing the following commands:
Fastboot mode.
Try these ADB commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Ng you have an Android phone, connect to you PC first to see if adb is working using composite ad driver for Windows operating system
Sent from my Amazon Kindle Fire using Tapatalk

I can't use android composite driver. Every time I attempt to install the driver manually I get the error listed above. No matter what I do I can't get the Kindle to be anything other than Unknown

i had a problem where i could only get the fire symbol screen computer would not recognize. I had to start the kindle fire utility plug my kindle into the computer then turn it off, then have kfu install latest twrp again when it says waiting for device turn device on and it will reinstall that and get you back to the recovery. so maybe you can do the same with obtain stock update. not really sure to the kindle. my computer would recognize kindle fire for a few seconds and thats how i could install new twrp

about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
if you can't get rid of the drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
nevertheless i would never install the original stock rom cause you loose fff,twrp and root
use one of the prerooted stock roms instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20

I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck

Help me save my kindle fire
I used KFU to install TWRP and up to CM9. But after that i restore to rom stock 6.2.
But after kindle start the error sorry loop in screen . I can not access to kindle.
process.android.acore force close
We try to connect and re install TWRP but not successfull. when i connect kindle to my pc (XP and window 7) it only recognize kindle as disk driver (athough i try to uninstall and setup manual driver )..
Help me urgent.
Thanks alot

http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

mhb1509 said:
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Click to expand...
Click to collapse
This comment gave a ton of hope since I have tried everything that has been mentioned already except for adding 0x006 but sadly it did not work. There's absolutely nothing I can do to get out of the Unknown state. I've never had my ass kicked this hard by a piece of hardware. I surrender.

maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
I was reading through that earlier and it was a little too intimidating. I'm just going to sit here and cry for a couple of minutes.

Kindle still recognize as disk driver
I try to do something but adb not working (device not found because it recognize as normal disk driver). My pc use window xp professional.
How can i solve this

My kindle still recognize as normal disk driver
I try to test on some computers (xp, win7) but unfortunately, my kindle still recognize as normal usb only. (not adb device).
So i don know how to fix this problem
Please help me, or give me a hint

xp is a good choice - you don't have to care about the uac (user acces control)
have you checked according to my post #12 above ?
to shorten things up i could take a look with teamviewer if you like
just gimme a pm ...

Have you added the second vendor and the second set of USB command lines in your google/extras folder? If not add those turn off the kindle then turn it back on do "fastboot devices" then put the update.zip in your platform-tools folder then push the update to your kindle to be flashed by twrp. The command for that would be "advt push update.zip /sdcard/update.zip" you can have the kindle already in twrp by this point. Also when all is over you will have to reroot and reinstall fff and twrp. If you need help send me a message.
Sent from my Kindle Fire using Tapatalk

Hard reset on main-board KF
My KF is frozen. I try to do hard reset by hold pw button 20s, but not effected.
So i've just open back-slide my KF, and see KF main-board.
Have hard reset trick on this main-board.
Help me please.

[Q] [ROOT] kindle fire hd rooting problem

hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!

Google Play Market Kindle 7" Software 7.2.3
diego_berta said:
hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!
Click to expand...
Click to collapse
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.

prokennexusa said:
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.
Click to expand...
Click to collapse
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed

diego_berta said:
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed
Click to expand...
Click to collapse
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first:
https://docs.google.com/folder/d/0B4lZEJI5lYeMdnFHeVRMQUtRYWc/edit
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
https://developer.amazon.com/sdk/fire/setup.html
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.

hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english

onemeila said:
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first: REMOVED : NEW USERS CAN'T LINKS
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
REMOVED : NEW USERS CAN'T LINKS
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.
Click to expand...
Click to collapse
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost

adb server is out of date. killing..
diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.

ADB driver
Raffo17 said:
hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english
Click to expand...
Click to collapse
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.

diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Open a cmd prompt and type this command:
Code:
android update adb
Then type these:
Code:
adb kill-server
adb start-server
adb devices
If all is working properly then you should see the device listed as a serial number

prokennexusa said:
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.
Click to expand...
Click to collapse
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.

Raffo17 said:
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.
Click to expand...
Click to collapse
Raffo17,
Unless you are going to do Android software development, you can do without the SDK. People like Bin4ry (Root MANY ANDROID!) and sparkym3 (Qemu automated root) have spent a lot of time to develop these tools so we can focus on other aspects of the Kindle.
Judging by your response, it looks like nothing should stop you from Rooting the Kindle. Go back to my original response in this Thread, download and extract to your desktop Root MANY ANDROID! and Qemu automated root. When you run Root MANY ANDROID! in Normal Mode, you will notice quite a few errors, ignore these errors. You will know that Root MANY ANDROID! has done its job when your Kindle asks to be Restored and then your Kindle will Reboot.
Go back to my instructions and remember, you are performing a risky upgrade(although it is worth it), so be careful.

prokennexusa said:
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.
Click to expand...
Click to collapse
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english

Update - Kindle Fire HD Root then install Google Play
diego_berta said:
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english
Click to expand...
Click to collapse
Diego_berta,
I will be available tomorrow, so I will watch for your response.

Rooting kindlefireHD 7.2.3
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?

prokennexusa said:
Diego_berta,
I will be available tomorrow, so I will watch for your response.
Click to expand...
Click to collapse
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english

diego_berta said:
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english
Click to expand...
Click to collapse
Diego_Berta,
Looks like you are at Step 2, proceed to Step 3 and now run Qemu automated root, the Kindle will return to normal speed once you have completed ALL the steps.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
The utility adb is used for Android Software development and advanced users. Sure you can root the Kindle using adb but you need to spend time learning the adb commands. I would recommend you download Root MANY ANDROID! and Qemu automated root, use these utilities to root your Kindle 7" Fire HD - they have adb embedded in each utility, so no need to install the SDK.
The following steps assume you have the Kindle plugged into USB, the driver is installed, you can see the adb driver in Windows Device Manager and adb is enabled on the Kindle (go back to the beginning of this tread for more details).
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete all the steps.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root!
---------- Post added at 12:25 PM ---------- Previous post was at 12:05 PM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
If you want to work with ADB, open a new Thread since this thread seems to be focusing on Rooting Kindle 7" Fire HD and then installing Google Play. I would be happy to try to help in the new thread, although since there are many capable people in this community so you will probably not need my help.
There can be many reasons for the missing device: Device driver problem, ADB out of date, ADB disabled on the Kindle, etc.
Send me a PM once you open the new thread.

no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!

diego_berta said:
no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!
Click to expand...
Click to collapse
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838 following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play

prokennexusa said:
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID!. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play
Click to expand...
Click to collapse
i moved vending.apk but the kindle is blocked again and gave me error. i had to restore all to factory settings... tomorrow i'll re-root the kindle but why it was blocked???

i try to root my kindle fire hd 7 7.2.3 using the tool Run Root MANY ANDROID! but nothing happens appear only :
If the device is not detected you may try to unplug it and reconnect it.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and other time appear:
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now

[GUIDE] Install Windows ADB Drivers for Fire HDs ("Newbie Friendly")

➜ No big ol’ SDK ➜ Latest Google drivers ➜ No messing with inf files ➜ ADB from any location ➜ Drag and drop files
Figured XDA needed a couple more ADB driver guides, so I'm bringing these down from Google drive where they've been getting a lot of use--with no complaints so far. :fingers-crossed:
Follow the steps below to install the Google ADB driver for "normal" (OS) mode.
Follow post #2 to install the driver for sideload mode. You must do this to sideload OS .bin files via stock recovery.
See post #3 for basic info/tips for using the command window and entering adb commands.
[EDIT September 21, 2015] If you're running Windows 10, read this:
At step 3 you install 15 Second ADB Installer. Some Win 10 users are reporting a problem. Please do this to help track it down:
- Be sure to run as Administrator.
- If you get an error, post the exact error and when it happens. Do not rerun Installer until someone replies to post.
- If you do not get an error, please post and say so and tell what type of Win 10 you have (home, pro, enterprise, etc.)
Thanks!
Install ADB Driver for "Normal" (OS) Mode
This uses @Snoop05's 15-Seconds ADB Installer. It provides the driver and software you need and puts the path to adb.exe into your PATH variable so you can run ADB commands from any folder.
Before you begin:
(1) Turn off anti-virus software
(2) Disconnect other physical devices that use adb and shut down any virtual ones. This can go very smoothly if you're not running anything that uses adb, including emulators, some photo-sync software, Gatesjr debloater, etc.
1. Make sure adb debugging is enabled on the the device. (Settings->My Device->Developer Options: Debugging)
To open Developer Options: In Settings -> My Device, tap on the serial number until Developer Options appears at bottom of screen.
2. If you've never connected Fire HD to computer, connect now and read this:
a. You may see a USB debugging message on tablet, tap "Always" and "Allow."
Even if you don't see message, Windows should try to install generic MTP drivers (not ADB!). Wait until you see success or failed message.
b. Unplug/replug and wait for Windows Explorer OR for message that prompts what to do when device is connected and choose Open window to Display Files, check Always do this and then OK.
c. Disconnect..
3. If you KNOW there’s no adb driver installed for the device, go to next step.
. . . If driver might already be installed, do hidden steps.
Connect to computer, open Device Manager (instructions below) and see if a driver is listed under Android Device.
- If a driver is NOT listed, go to next step.
- If a driver IS listed, open CMD window in folder containing adb.exe and run adb devices command (step 12).
* If adb devices DOES return an ID, this driver is working and you don’t need to install a different one.
* If adb devices does NOT return an ID:
a. In Device Manager, right-click the driver and choose Uninstall.
b. Unplug the device and restart Windows.​
4. Download the latest version, currently v. 1.4.3, of 15 seconds ADB Installer and run it as Administrator.
If you are not Administrator, right-click the file and choose “Run as Administrator“
Read all about 15-seconds Installer at the link.
Press Y to install ADB and Fastboot
Press Y to install ADB system-wide or N for current user onlyYou should see:
Installing ADB and Fastboot . . .
4 files(s) copied
If you see 0 files copied, post the error with your Windows version and the drive it's installed on.​
Press Y to install drivers
View attachment 3455788​
5. An Install Wizard will run. Look for it and install device software!
6. Connect the Fire to the computer and wait until you see it in Windows Explorer.
7. 6/3/2016 Update for Win 10: Your drivers might already be installed. Check for Allow USB Debugging on tablet. Go to step 12 and run the adb devices command.
. . . If it shows serial number and unauthorized, you need to enable USB debugging and run command again. It should then show serial number and "device." You're done!
. . .If it doesn't show serial number, continue the steps.
Win 7 and 8.1: Open Device Manager:
Win10: ? Win8: Right-click Start Button and choose Device Manager. Win7: Click Start button and type Device Man [enter]
8. Find Fire under Other Devices, right-click it, and choose Update Driver Software.
If you don't see Fire under Other Devices, disconnect/reconnect or try a different USB port, or try toggling Enable ADB in Developer Options. If nothing works, disconnect and reboot both Fire and computer and try again.
{
"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"
}
​
9. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
​
10. Find Android Device, click it and press Next.
. . . If Android Device is not listed, look here.
If you DID NOT run 15 Seconds ADB Installer, STOP, disconnect from PC and run it now.
If you DID run 15 Seconds ADB Installer:
a. Double-click Show All Devices.
b. Under Manufacturer, scroll to Google, Inc, click it and continue.
↠ If Google, Inc is not listed, the ADB drivers are not installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.
11. Select Google, Inc in left pane and then Android Composite ADB interface in right, and press Next.
If the screen you see only has the Model pane (on the right above), scroll down to Android Composite ADB.
↠ If the driver is not listed, drivers have not been installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.​ 12. At the warning screen, press Yes.
Driver is updated!
13. Run the adb devices command and confirm it returns a device id:
a. Open CMD window: Hold down the Shift key, right-click the desktop (or an empty space in a folder) and choose Open command window here.
b. Type: adb devices [enter]
View attachment 3467199
If you see an ID followed by “device,” the driver is installed correctly. DONE!
If you see an ID followed by “unauthorized,” look at the tablet for “Allow USB Debugging?” message and tap OK.
If debugging message disappears before you say “OK,” unplug/replug tablet to see it again.
Repeat the adb devices command and confirm it now looks like above. DONE!
If you do not see an ID, the driver may not be correctly installed or USB debugging might still be disabled on your tablet. Verify all connections and reboot tablet and PC and repeat this step. If adb devices still doesn’t return an ID, follow this guide from the beginning again.

Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.

Info and Tips for Using the Command (CMD) Window - for "Newbies"
Here's some basic info for using the CMD window and entering commands found in the guides.
Open CMD window
Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"
Give commands on-the-fly
If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."
Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.
Install an app (or sideload a bin file)
Open CMD window in the folder containing the file and enter the command: adb install filename.apk
If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"
Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"
Drag & drop files and copy/paste commands
To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.
Drag and Drop
Type: adb install <--type a space after "install"
. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.
Copy and Paste
Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.

Installing drivers for sideload
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?

rking38 said:
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
Click to expand...
Click to collapse
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)

DoLooper said:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
Click to expand...
Click to collapse
Wow...follow the instructions from step one! thanks for your patience

15 Second ADB problem
DoLooper said:
Installing Google ADB drivers for your Fire HD:
Click to expand...
Click to collapse
MRDirtyPixels said:
I followed a guide to install Lolipop on my device, I managed to get the 15 Second ADB Installer but could only get the 1.3 version to work.
When I try to do it now it states on the device that I need 1.3.2 or higher. The 1.4 download gives me an Access Denied message and installed 0 drivers.
Click to expand...
Click to collapse
Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?
Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?
Please let me know these things so I can try to find a fix. EDIT: @MRDirtyPixels I'll post how to update the driver when you reply. Thanks!

Fire HD 6 on 4.5.3
Win7 Ultimate x64
I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".
I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.
Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.
Any ideas would be greatly appreciated.
**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?

You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!

DoLooper said:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
Click to expand...
Click to collapse
Oh, great! I may have overlapped a guide or two. Thanks so much!
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?

jiznon said:
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
Click to expand...
Click to collapse
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/

jiznon said:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.

jiznon said:
. . . (it also states to install sideload drivers). Maybe it should be edited. http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Yes, I see I introduced some confusing info about drivers/versions in last update. I'll fix. thanks.

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
DoLooper said:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
Click to expand...
Click to collapse
Right. I'm still at "Before You Begin:
Install adb device drivers if you don't have them.
Here's an illustrated guide for Windows drivers. Install driver for both OS mode and sideload mode."
Wanted to make sure I don't miss anything. Looks like I'm on the right track. Thanks!
**EDIT: Everything went smooth. Thanks everyone!

Hi DoLooper, I'm currently following your [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") guide to root and update a Fire HD 7 and that's how I got here. I have successfully completed this guide, but only after I solved a problem that I ran into along the way. I solved it myself, so I want to share how I did it.
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Last but not least, thank you very much for spelling everything out step by step, it all seems like a doable task now.

podikan said:
. . .
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Click to expand...
Click to collapse
This is helpful and I'd like to add it, but I'm a little confused. Step 4 is just installing the 15-second Installer software. I don't think it asks anything. Could you please clarify the step where you got that prompt? Also, when it was listed under Samsung, you were able to right-clicking and choose Update and install the google drivers, right? Thanks.

Well, at the end of step 3 the program 15 Second ADB asks "Do you want to install device drivers?" and then a windows prompt appears. This is when I got the following prompt on top of that (only have it in German, sry): imageshack.com/a/img911/8983/bBg2q0.jpg I assume it's some kind of driver, as 15 Second ADB calls it. Is it really specific to a device?
As for your second question, if I remember correctly I was able to do that (I had to dig for it like you explain in step 9 after ". . . If Android Device is not listed, look here."). But afterwards it was still displayed as a (fully installed) Samsung portable device in my device manager. No chance I would go ahead and root from there. That's when I found and removed the Samsung drivers which came with Kies, rebooted, and started the procedure from the beginning.

ADB not cooperating
Ok. I am on a Fire HD 7 Gen 4 at OS 5.1.1, and attempting to downgrade to 4.5.3 for rooting purposes. (My eventual goal is to get CyanogenMod or another 'pure android' ROM on it, if you can help with that, great) When in sideload mode, Windows doesn't detect my device at all (no KFARWI or any other 6-letter combo) but ADB can detect it in both sideload and OS mode. My problem is this: Whenever I attempt to flash a .bin stock recovery, adb stalls for about a second, while on my Fire I only see:
Now send the package you want to apply to the device with "adb sideload <filename>"
Finding update package...
Opening update package...
Verifying update package...
before the device reboots. On adb I then see: "failed to read command: connection reset by peer" Any subsequent attempts without a manual reboot into sideload mode just instantly time out. I have a feeling this has something to do with the weird reboot, but how do I prevent it?

DoLooper said:
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Click to expand...
Click to collapse
thank you