Related
Previous "first try" threads are pretty old, I'm concerned that information is outdated.
First, I wouldn't have done it, but the Fire just cries out to be uncrippled. It is 6.3. I am pretty new to this. I stopped tearing into stuff about 11 years ago, I was OK with it then but I stopped caring about it and haven't paid attention since. But I know one thing, and that is how to ask for help.
I downloaded the SDK Manager and ran the installer, installing SDK Tools and SDK Platform-Tools, then tried to install the drivers from the Kindle Fire Utility; it is the most recent version, 9.5 I believe (from yesterday).
I got:
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Download successful.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
The system cannot find the path specified.
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Recovery Bootmode.
Please wait...
...And that's it, about half an hour ago. I know one thing, that when "NOT" is capitalized, you "don't touch the big, beautiful, shiny red button."
How long do I wait? What is going on, and if something is wrong, what do I do next?
Thanks for looking.
edited to add: I tried running install_drivers.bat; "UNC paths are not supported... Defaulting to Windows directory. The system cannot find the path specified."
Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547
kinfauns said:
Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.
M0sca said:
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.
Click to expand...
Click to collapse
All of those "The system cannot find the path specified." errors are because it can't find the directories within the KFU folder. Did you move the run.bat file or something? Within the KFU directory, you should have...
drivers
files
tools
install_drivers.bat
run.bat
Like the first 5 errors after "Activating Fastboot (4002)" it's looking for the tools directory. Most of the time this is caused by users who try to run the batch file from within the zip archive.
EDIT: I'm not a Windows guru by any means, but I was just looking at some docs about UNC paths. Do you have the KFU directory on some shared directory or mapped network drive or something? Try moving it to some place local like your user directory and run it from there.
kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.
M0sca said:
kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.
Click to expand...
Click to collapse
No, that's fine... no apologies necessary. It's good to step away from the situation for a while and regroup when things don't seem to go right. In the interest of full disclosure, Mac OS X Lion is my primary OS. All of this Windows stuff I do through Parallels Desktop VM and I don't have any problems with it. I don't know what you are using, but I'll warn you now that if you are trying to use Oracle's VirtualBox, it's not going to do the job for you. There seems to be some bug in their USB implementation that breaks adb and fastboot.
My guess right now is that you are trying to run KFU from a shared directory that resides on your Mac. If you look at post #2 of the guide I mentioned previously, I suggest putting everything in C:\kfu before running things. It doesn't necessarily have to be that directory, but you should trying putting it somewhere on the boot drive. The 2 minutes I spent looking at UNC paths seems to indicate cmd.exe doesn't like them and that might be the cause of your troubles. Good luck.
kinfauns, I followed the instructions better this time, downloading KFU in the Windows environment and extracting directly to C:, and everything proceeded perfectly. Thank you!
If this isnt in the right spot please move it there, but I ran across this issue and figured I'd share the fix.
I kept getting Device Not Found in ADB while booted into Recovery so I followed the steps here:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode
Problem is, if you're on Windows 8 editing that file will cause a hash mismatch not allowing you to install the driver.
To go around that, follow these steps here:
http://www.windows7hacker.com/index.php/2012/09/3-ways-to-fire-up-windows-8-advanced-boot-options/
Once inside the Advanced Startup menu, click Troubleshoot, then Advanced Options, then Windows Startup Settings. Hit Restart Now and when it reboots into those settings hit the number 7 to Disable Driver Signature Enforcment. Once you reboot try installing the modified driver again. Should work.
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Oh good to know.
Thanks! Feel free to delete this thread then.
graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
Not for me I had to use the ASUS files for ADB in Windows (yeah, 8 and 64bit), although I had the Univ. Naked Drivers installed already. But in fastboot Windows didnt want to recognize the device and it didnt let me install the ASUS r6, the Google original ones or the Univ. Naked (The last ones because of the hash), so I had to go into advanced startup and do the steps mentioned in the OP. (Damn Win 8 )
For fastboot/adb in fastboot mode you need to disable driver signing, this is an other way to do that :
Command Prompt (as admin!)
Disable driver signing :
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot
(on your desktop you see the watermark : 'Test mode' This is permanent, even after every reboot till :
Enable driver signing :
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Reboot
xXfuzzXx said:
Not for me I had to use the ASUS files for ADB in Windows (yeah, 8 and 64bit), although I had the Univ. Naked Drivers installed already. But in fastboot Windows didnt want to recognize the device and it didnt let me install the ASUS r6, the Google original ones or the Univ. Naked (The last ones because of the hash), so I had to go into advanced startup and do the steps mentioned in the OP. (Damn Win 8 )
Click to expand...
Click to collapse
hmm that's odd. I was having the issue with the normal driver (win 8 64bit) and the normal driver would fail to reinstall(as many reported). I downloaded the one I linked to and updated the driver in device manager and adb and fastboot worked without doing anything else.
graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
That driver worked perfectly, thanks! :good:
graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
Dude, thank you so much for that download link. I have been going out of my mind trying to get this device recognized in adb/fastboot on windows 8. Your tips/download worked perfectly. Thank you
I can choose only the MTB USB device when I try to update Nexus 7 driver
graffixnyc said:
hmm that's odd. I was having the issue with the normal driver (win 8 64bit) and the normal driver would fail to reinstall(as many reported). I downloaded the one I linked to and updated the driver in device manager and adb and fastboot worked without doing anything else.
Click to expand...
Click to collapse
I wanted to root my Nexus 7 device on the basis of a tutorial (links not allowwed yet )
Downloaded the Asus driver.
I choose the "Update Device Driver Software"option from Device Manager on Nexus 7, pointed to the installation folder on my computer ".. \android-sdk-windows\extras\google\usb\android_winusb.info" file, but the model window shows only the MTP USB Device, instead of the list of Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface.
The winusb.info file contains info for these drivers. If I point to this file, get an error message:
"The folder, You specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
The host computer able to connect to the device, and I can list the folders, but the fastboot doesn't work.
Does anybody has a solution?
Thanks in advance
Gabor
graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
BRAVO... :good:
II solved it in 1 second ...
thanks
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Path question
delete
Thanks a lot for this tutorial, i was searching for a way to root my kindle 2 (non HD) for the past 1 week and i almost felt like throwing it out of the window. Finally this helped me, installed SU successfully. Cheers!
Re-Rooted Kindle Fire 2 on Windows 7 X4-Bit
Finally, I'm going to bed!
Anyway, THIS is what I did.
BookCase said:
Finally, I'm going to bed!
Anyway, THIS is what I did.
Click to expand...
Click to collapse
Noobie question what do you actually type in when you add it to the path? Thanks
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
does this guide work to install a rom in Kindle Fire 2nd gen?
adisagio said:
does this guide work to install a rom in Kindle Fire 2nd gen?
Click to expand...
Click to collapse
No. It is a quick guide on how to root a 2nd gen
Recovery
Do we have KF2 recovery until now?
Follow Up - Feedback
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
bryanchapman9999,
Nice work bryanchapman9999, very solid How to.
when am trying to open the SDK manager nothing is happening. Can any1 help me ?
Open as admin ?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Thanks it worked!!
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.
Root the Kindle Fire 2 (non HD)
Divanus said:
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.
Click to expand...
Click to collapse
Divanus,
First, the Android SDK is completely independent of other services and is only required for developers. The package includes Eclipse which is a Programming platform that people like us use to develop software for Android. The software used in Root MANY ANDROID includes the adb.exe utility needed to Root the Kindle.
You only need four things to Root the Kindle:
1. Root MANY ANDROID: http://ubuntuone.com/6LfERbIVoLRh822wHFicgR
2. Android ADB Driver: http://ubuntuone.com/4UaHeEJBrh9PT87RFzYR19
3. Windows PC
4. Kindle Fire 2
Step 1: Install the ADB Driver while the Kindle is Unplugged from USB, then Reboot your PC.
Step 2: Plug the Kindle into USB, wait 2 minutes for the driver to initialize
Step 3: Unzip Root_with_Restore_by_Bin4ry_v18.5.1.zip as Root_with_Restore_by_Bin4ry_v17 to your desktop
Step 4: If you installed the SDK, you need to disable it, otherwise Root Many Android will fail. You can disable it by changing the platform-tools folder to platform-tools-temp. This can usually be found C:\Program Files\Android\sdk\platform-tools
Step 5: Run Root Many Android RunMe.bat
Step 6: You now have Root!
I cant do it
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"
I'm having problems
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.
Kindle Fire HD and 2 First Aide - 4.1.43-Beta - Dated 02/19/2013 at 22:15
Kusakus said:
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"
Click to expand...
Click to collapse
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus said:
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.
Click to expand...
Click to collapse
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Step 4: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888
Not trying to revive an old thread and I have been reading what I could find on the kindle fire 2. Recently got my daughter one and I'm not happy with the amazon store, etc. I would like to root and be able to use the playstore. Is this the best method? Is this what I need to do to accomplish this? She and her mother both like the stock ui and all, especially the carousel, so I have no intention of installing a different rom or launcher. So is it possible to simply root and get access to the google playstore? Thanks!
I used this thread recently and it worked fine
http://forum.xda-developers.com/showthread.php?p=36122126
Sent from my GT-P3110 using xda app-developers app
Hey It's me again
prokennexusa said:
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Step 4: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help
If you got it rooted, try to put on the recovery and flash a custom one (slimkat is pretty awesome). The amazon OS is terrible IMO.
Kusakus said:
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help
Click to expand...
Click to collapse
Has anyone been successful using adb commands from TWRP recovery? I have been unsuccessful getting it to connect.
What's the problem?
Do you have the yellow exclamation point next to the Samsung_android device in the device manager?
What OS?
---------- Post added at 11:51 AM ---------- Previous post was at 11:29 AM ----------
Went ahead and did a quick write up. This is from memory so wording might not be exact, but if you're familiar with Windows XP, it shouldn't be too hard to follow along.
1) Go the the directory (your android sdk directory)\extras\google\usb_driver
2) Look for the file called "android_winusb.inf"
3) Open it with an editor (i used wordpad).
4) Right under the section labeled [Google.NTx86] I added the following line: %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 (I would cut and paste this for syntax accuracy) Look at the other lines in the file to make sure it looks right.
5) save the file.
6) Put your phone in recovery, plug it in to your computer and wait for windows to try and install the driver.
7) Select "Do not search, I will choose the driver" (I'm doing this from memory, so wording might not be exact)
8) Get to where you tell it you have the disk, and point it to the usb_driver directory/file listed above. It should install it now.
This worked for me on my work Windows XP laptop. My home computers are Windows 8, and everything installed just fine on it's own.
fgr said:
What's the problem?
Do you have the yellow exclamation point next to the Samsung_android device in the device manager?
What OS?
---------- Post added at 11:51 AM ---------- Previous post was at 11:29 AM ----------
Went ahead and did a quick write up. This is from memory so wording might not be exact, but if you're familiar with Windows XP, it shouldn't be too hard to follow along.
1) Go the the directory (your android sdk directory)\extras\google\usb_driver
2) Look for the file called "android_winusb.inf"
3) Open it with an editor (i used wordpad).
4) Right under the section labeled [Google.NTx86] I added the following line: %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 (I would cut and paste this for syntax accuracy) Look at the other lines in the file to make sure it looks right.
5) save the file.
6) Put your phone in recovery, plug it in to your computer and wait for windows to try and install the driver.
7) Select "Do not search, I will choose the driver" (I'm doing this from memory, so wording might not be exact)
8) Get to where you tell it you have the disk, and point it to the usb_driver directory/file listed above. It should install it now.
This worked for me on my work Windows XP laptop. My home computers are Windows 8, and everything installed just fine on it's own.
Click to expand...
Click to collapse
Running Win8 and driver is installed and was without issue. OS sees device and mounts storage. However, when in TWRP cannot see device in order to start shell. Want to make sure it is not a limitation of the S4 TWRP.
Gotcha,
I'm currently not running TWRP, but I was and don't recall having this problem.
First and foremost I AM NOT RESPONSIBLE FOR ANY HARD BRICKS,etc ,etc(Really hard to hard brick a kindle doing this unless you flash a weird rom package)
Now that thats cleared up, I have been seeing too many recovery bootloop bricks lately because I think the main tutorials people use haven't been updated(to mention you need to put a rom on the kindle beforehand now), so I thought why not write a tutorial that explains how to fix this problem since there are so many posts, that way we can just put a link to the tutorial in the peoples threads. So here we go!
Things you need to do this:
a micro-usb cable
patience
minimal command prompt experience
Instructions:
Boot your kindle into twrp (it should do this on its own at this point)
Make sure you have the adb drivers installed(they will need to be installed again if you flashed an older version of twrp), if not, update your drivers in the device manager with the ones in my signature.(See below if you don't know how to update your drivers)
Download the attached file and extract it somewhere
Put the rom and gapps in the folder you extracted the files to
Open a command prompt with admin privileges(start>all programs>accessories right click command prompt, hit run as admin)
CD into the directory where the extracted files are
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
As I said in the filename put either the rom or the gapps, but send both in two commands
At this point once the transfer is done unplug your kindle
If you are going from amazon to a cm based rom, at this point you should wipe system, cache, dalvik cache, and do a factory reset. If not just goto step 11.
Hit install, browse to the /sdcard folder and choose the rom and gapps files and flash them
Reboot and profit!
For people with driver issues that don't know how to install my driver:
Open the device manager
Find the device with a triangle next to it
Right click it and hit update driver
Choose the option that lets you search a folder for drivers by browsing
Choose the folder you extracted my drivers to
Let it search and install the drivers
Profit!
Note: If adb isn't picking up the kindle in recovery, try uninstalling the current kindle devices it detects first and then updating the drivers
It's about time someone posted a tutorial for how to fix this. Great job! This should be a sticky.
thanks
I had the same problem... the looping thing... you're tutorial saved me! thanks a lot.
rom and gapps
sry for my ignorance, but what do you mean with "rom and gapps"?
i explain what i've done:
i did everything in the guide to install twrp and 2nd bootloader.
i can acces in the twrp, but if i enter the reboot menu, if i push the botton "System", i had the boot loop problem (Kindle logo became orange and then blue forever)
Now the question is: where i find the rom and the gapps you're talking about?
You choose a ROM from the android development section for your model kindle, usually it tells what version of gapps(google apps) you need to flash with it. If it doesn't tell what gapps you need its pretty easy to tell, goo.im has the gapps posted for all versions of android, and have a chart telling which version goes with what os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
*cannot read
When I go to push the file to the kindle I get a message in the command prompt saying *cannot stat 'rom.zip': no such file or directory.
I have the zip in the same folder as the adb file
Any suggestions?
Check the ROM name to make sure its not a typo? It should work. Make sure you didn't rename the ROM and add .zip because windows by default doesn't show extensions, so the filename might actually be ROM.zip.zip now if you did that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sigh, I was hoping my first post on XDA wouldn't be a help request, but here I am..
I agonized for hours over the directions in this tutorial, checked all the right boxes, but I ended up in the bootloop as described in the OP. I can get to TWRP fine, but nothing else. My ADB drivers along with the Android SDK package were installed and previously working fine. Now, of course, the device no longer has a driver in Windows. I followed the instructions here, carefully selecting the extracted folder containing the ADB files, and Device Manager tells me—
"Windows was unable to install your Kindle. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Click to expand...
Click to collapse
I tried a number of times to reboot both systems, uninstall the Kindle, try to pick it up again, etc., to no avail.
My device is a Kindle Fire HD 7" originally version 7.4.6. I made backups before I started as per the directions in the linked thread and I have my desired ROM and Gapp .zips all ready to go, I just can't get anything to the device. I'd prefer to avoid needing to get a factory cable, if possible.
Thanks for any help!
Edit: I've managed to get my .zip files to the /sdcard/ directory. For anyone stuck on the same problem I was, the instructions in this thread got my ADB drivers up and running again. The rest of the steps here worked fine at that point.
Oh good, someone finally made a tutorial for this.
Help please
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
CD means change directory, it does what it says, right now you are in your system32 folder so when you CD into the directory you extracted the zip file to you won't get that error. You should Google some command prompt basics.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks
Thank you for this guide, googled some basic CMD knowledge and now i have cyanogen. Cheers
gallowayj3 said:
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Extract the file in the first post to somewhere on your C drive. (I put it in the C drive directly so it was just c:\adb\.)
Check this: ht tp://coweb.cc.gatec h.edu/ice-gt/339 - remove the spaces.
That should help.
Do
cd..
until you have just c:/. Then type cd:/adb and it should put you in the right place. Then you can do adb push.
I just figured this out actually and did it.
HELP
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Sounds like an old twrp version I think, try downloading the latest twrp from android development for your device, It should have a flashable zip, just push it to your device and flash that, then reboot into recovery again and try flashing the ROM again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stuck
Hi guys .., when i typed adb push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard , it says
error: device not found.
i thing my pc didn't recognize my kindle. In device manager there ain't any devices not installed .
someone pls Help
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sorry for my stupid question. ) what is service manager?
stunts513 said:
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My bad I think my kindle autocorrected a word incorrectly. It was supposed to say device manager.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
i'm kind of newbie on rooting and installing ROMs.
http://www.youtube.com/watch?v=hUW6KARo8Y4
i tried this youtube instruction and after step 20 My kindle fire wouldn't start. Not even the kindle fire with blue color.
and also pc didn't recognize my kindle , maybe because of it won't power on.
/this instruction is for kindle fire HD 8.9 , i don't know my kindle is 7 inch/
In device manager can't find adb devices .. what should i do?