Cannot install romaster to vroot hdx8.9 - Kindle Fire HDX 7" & 8.9" General

Does anybody have the problem during installing Romaster_3.4.3.7593_Setup.exe, that the something with rootres.dll goes wrong? Since after ignoring this problem, the root method doesn't work with my hdx, e.g. an app is installed and shows green. However, the root processes terminates with an error
My enviroment:
Kindle HDX 8.9, 14.3.2.3.2
Win 8.1 64 bit, installed hdx driver, working adb
Romaster_3.4.3.7593_Setup.exe

Related

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] Lost Fire Drives in Explorer after root

Hello all Nob here...
Rooted my Fire using jcase's (THANKS jcase) Burrito Root 3, Then installed the Google Svcs., and the Market. Problem is that I can no longer see the Fire when I connect it to the computer (Win 7, 64), The Fire says it's connected and that files can be downloaded but the Fire does not show up in Explorer?
What's up?
check to make sure the drivers are correct. Most issues talking to the KF resolve around driver issues.
I agree, it sounds like a driver issue. Use Windows device manager and uninstall the kindle drivers, then reinstall them. Restart computer. Should be good to go.
Thanks guys...found the driver and all is we'll
Thanks again
Sent from my Kindle Fire using Tapatalk

[SOLVED] KF Driver Issue in Windows With Custom ROM

Greetings,
I am currently running my Kindle Fire with the an AOKP ICS based ROM. Everything is working fine, and when I connect the KF to a Windows computer I can see the SD storage fine as well. However, when I attempt to use adb or the Kindle Fire Utility to perform any actions against the Kindle Fire from Windows, I cannot get the device to be recognized properly once I plug it in. Because of this it is not detected by adb, and appears offline to the Kindle Fire Utility.
Before, when the KF was still on the stock ROM, it was recognized fine once I ran the driver installation included with the Kindle Fire Utility. But now the device is not recognized, and I only see a device called "Amazon" with an exclamation point next to it under Misc. devices in Device Manager.
I have tried to reinstall the driver included with the Kindle Fire Utility, install the Google USB drivers included with the Android SDK, and nothing has had any effect so far. If I boot into recovery the OS seems to recognize the device properly, but I can't do much else as once adb commands are sent to it (ie. via the Kindle Fire Utility) it doesn't have a response on the device itself, and just sits in recovery waiting for user input.
Wondering if anyone has had any experience with this thus far, and was able to resolve.
UPDATE: Resolved. Not sure how I missed this, but looks like user 'nathris' posted details and a fix in the following thread on AOKP:
http://forum.xda-developers.com/showpost.php?p=25271431&postcount=109
Device ID changed and the android_winusb.inf file needed to be modified with new ID strings. I updated the .inf file that was included in the drivers with the KFU. I then went to device manager, updated the driver, and pointed it to the KFU driver folder that included the modified .inf. Afterwards the driver installed and my KF was detected once again.
worked perfect I did it all without the kindle plugged in pasted the code into the inf file ran the driver install in KFU then plugged in my kindle walla adb online on the new milestone 5 kindle fire AOKP and my mass storage drivers remained intact. thanks for the research
shinji1225 said:
Greetings,
I am currently running my Kindle Fire with the an AOKP ICS based ROM. Everything is working fine, and when I connect the KF to a Windows computer I can see the SD storage fine as well. However, when I attempt to use adb or the Kindle Fire Utility to perform any actions against the Kindle Fire from Windows, I cannot get the device to be recognized properly once I plug it in. Because of this it is not detected by adb, and appears offline to the Kindle Fire Utility.
Before, when the KF was still on the stock ROM, it was recognized fine once I ran the driver installation included with the Kindle Fire Utility. But now the device is not recognized, and I only see a device called "Amazon" with an exclamation point next to it under Misc. devices in Device Manager.
I have tried to reinstall the driver included with the Kindle Fire Utility, install the Google USB drivers included with the Android SDK, and nothing has had any effect so far. If I boot into recovery the OS seems to recognize the device properly, but I can't do much else as once adb commands are sent to it (ie. via the Kindle Fire Utility) it doesn't have a response on the device itself, and just sits in recovery waiting for user input.
Wondering if anyone has had any experience with this thus far, and was able to resolve.
UPDATE: Resolved. Not sure how I missed this, but looks like user 'nathris' posted details and a fix in the following thread on AOKP:
http://forum.xda-developers.com/showpost.php?p=25271431&postcount=109
Device ID changed and the android_winusb.inf file needed to be modified with new ID strings. I updated the .inf file that was included in the drivers with the KFU. I then went to device manager, updated the driver, and pointed it to the KFU driver folder that included the modified .inf. Afterwards the driver installed and my KF was detected once again.
Click to expand...
Click to collapse
can u up the.inf file?

[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

Kindle Fire Utility 6.3.1 and drivers

I'd like to think that I'm not a totally clueless noob, but I sure feel like one. I've installed homebrew on Wii and stuff like that, but I simply can't get the Kindle Fire Utility to run on a first generation Kindle Fire, 6.3.1.
I have downloaded the utility and installed the drivers, they install correctly and all necessary permissions are allowed. However, when I plug in the Kindle, the computer beeps like a USB device has been added, but it doesn't recognize the Kindle and the Kindle Fire Utility opens, but doesn't run to the point where I get a menu.
I can use system restore to roll back the driver installation and then the Kindle is recognized. I've tried running Kindle Fire Utility to get boot menu, then installing the drivers, but that leaves me hanging at "waiting for device"
Any thoughts would be much appreciated!
I have a Toshiba Satellite L755 running Windows 7.
Thanks!

Categories

Resources