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
Related
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
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
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Kindle Fire 7" HD ADB Driver
Krawdd said:
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Click to expand...
Click to collapse
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: Kindle Fire ADB drivers
If not, I have an alternative driver here: https://dl.dropbox.com/u/54456659/usb_driver.zip
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: https://developer.amazon.com/sdk/fire/connect-adb.html
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
prokennexusa said:
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: link that you provided
If not, I have an alternative driver here: link that you provided
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: link that you provided
Click to expand...
Click to collapse
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Android Composite ADB Interface
Krawdd said:
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Click to expand...
Click to collapse
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
prokennexusa said:
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
Click to expand...
Click to collapse
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Krawdd said:
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Click to expand...
Click to collapse
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
prokennexusa said:
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
Click to expand...
Click to collapse
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
ADB Communication Issues
Krawdd said:
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
Click to expand...
Click to collapse
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
prokennexusa said:
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
Click to expand...
Click to collapse
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
ADB Server Out of Date
Krawdd said:
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
Click to expand...
Click to collapse
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
prokennexusa said:
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
Click to expand...
Click to collapse
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
By the way, i just tried to install the adb drivers again and I got the same error... saying I have to install them manually. I ran both the bin4ry v18 and the qemuroot and both got stuck at "*daemon started successfully*" and they just sit there doing nothing...
ADB Driver Install
Krawdd said:
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
Click to expand...
Click to collapse
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
prokennexusa said:
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
Click to expand...
Click to collapse
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
ADB Communication Issues
Krawdd said:
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
Click to expand...
Click to collapse
We are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the Root_with_Restore_by_Bin4ry_v17 "Stuff" folder?
---------- Post added at 05:09 PM ---------- Previous post was at 04:20 PM ----------
For everyone having trouble with ADB, here is a video that you may find helpful:
ADB Driver Install Video
prokennexusa said:
we are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the root_with_restore_by_bin4ry_v17 "stuff" folder?
---------- post added at 05:09 pm ---------- previous post was at 04:20 pm ----------
for everyone having trouble with adb, here is a video that you may find helpful:
adb driver install video
Click to expand...
Click to collapse
1/13/2012 4:20 pm
ADB Server Out of Date
Krawdd said:
1/13/2012 4:20 pm
Click to expand...
Click to collapse
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
prokennexusa said:
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
Click to expand...
Click to collapse
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Initialize Superuser.apk
Krawdd said:
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Click to expand...
Click to collapse
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
prokennexusa said:
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
Click to expand...
Click to collapse
I guess it was too good to be true... there's no superuser.apk in the apps folder.. what to do? I already tried rooting it again and it said that i was rooted again
EDIT: I just woke up and tried again. Instead of usin first the root with restore and second the qemu, I used root with restore twice. Now I have a different app called SuperSU... It isn't Superuser though... It has a picture of the android robot wiith a cape flying... I opened but I have no idea what to do with it!
It worked for the error that you are having.
Hello i just read your post.. before continue sorry about my English is not perfect but i will try to to explain hot to explain the "solution"..
ok the first thing you need to do,is uninstall all the ADB drivers from the device manager.
after that you have to restart your PC..
when your pc is already started install de ADB drivers and then connect your kindle..! and let windows install the drivers again.
It worked for my so i hope it work for you.. =)
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?
did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!
In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2
the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command
Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium
The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.
Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB InterfaceThe system cannot find the file specifiedI have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse
I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.