Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing “cmd” and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory you’ve placed your files in by entering “cd c:\androidsdk\” or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type “adb devices” to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying “permission denied,” it means that your tablet hasn’t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?
Capitan_Veshdoki said:
Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing â??cmdâ? and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory youâ??ve placed your files in by entering â??cd c:\androidsdk\â? or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type â??adb devicesâ? to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying â??permission denied,â? it means that your tablet hasnâ??t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/kindle-fire-hdx
Sent from my KFFOWI using XDA Labs
Related
hello,
this is a quick guide i made to help make it easier to install recovery tools and custom roms
I found that all the other guides were half correct and found myself referencing many different guides to figure it out
so after spending 5 hours doing my first kindle fire
about 1 hour on my second kindle fire
and about 5 mins on my third kindle fire
I think this guide should help some people out
thanks in advance to everyone and please leave constructive criticism or comments!!
//after rooting
---------------------------------
make sure you have in >C:\program files\android\android-sdk\platform-tools
---------------------------------
-log
-last log
-update.zip
-updaterecovery.img //if you are using Clockwork Mod
or
-twrp.img //if you are using TWRP recovery
---------------------------------
//cmd.exe
>cd C:\program files\android\android-sdk\platform-tools
>adb devices
//make sure device shows up
>adb shell
>cd cache
>mkdir recovery
>exit
>adb push log /cache/recovery/
>adb push last_log /cache/recovery/
>adb push update.zip /sdcard/
>adb push updaterecovery.img /sdcard/
>adb shell
>dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
>idme bootmode 0x5001
>reboot
//on kindle go through CM recovery and install update.zip
>adb reboot
>adb shell
>mount sdcard
>exit
>adb push stockrecovery.img /sbin/
>adb shell
>dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
>idme bootmode 0x5001
>exit
>adb reboot
follow this lower section if you are using TWRP 2.0
----------------------------------------------------------------
//if you are using twrp you need to change
//"updaterecovery.img" >to> "twrp.img" ---see below
// "dd if=/sdcard/twrp.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
//
>adb push twrp.img /sdcard/
// if you are using twrp.img and are stuck in bootloop
//you need to do the following commands after twrp 2.0 installs and reboots
>adb shell
>idme bootmode 4000
>reboot
----------------------------------------------------------------
//all done
Why not just use KFU? It does great with all this being scripted, etc.
---Saving For Later---
DeerSteak said:
Why not just use KFU? It does great with all this being scripted, etc.
Click to expand...
Click to collapse
Where might that be??
Sent from my ICS Captivate
The sticky at the top of the Kindle Fire forum?
Kindle Fire Utility...its in the very first post in this forum, stickied at the top.
It took me 5 minutes to root mine and that was before kfu was released. Biggest problem I had was when it was in fastboot mode, windows dropped the drivers. Only took a second to see the issue and correct it and finish it out. I did keep mine stock but rooted and no recovery till 6.2.1 came out. Then I installed twrp and installed pre-rooted 6.2.1. Now I'm running cm7 until ics is worked out.
Good option
Another good option over the KFU. If you want to play around yourself so you can learn more about adb and cmd prompts this is a good way to do things. This is way simpler than some of the old instructions, but more hands on than the KFU.
installing twrp thru this method won't work, twrp installs fff at the same time so
Sent from my HTC Glacier using xda premium
smirkis said:
installing twrp thru this method won't work, twrp installs fff at the same time so
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
then how do i have twrp and fff on my kindle fire?
1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.
Hi,
I recently got a new Kindle fire and tried to root it.
I followed the instructions given in this post.
http://forum.xda-developers.com/showthread.php?t=1568340
However, my kindle fire seems to be stuck in an infinite boot loop after first step itself.
Here are the step I followed (I am using Windows 7 32bit).
1. Installed android sdk.
2. Updated the Kindle driver to install "android abd composite interface"
3. Downloaded all the required files in the platform-tools folder
Required files:
fbmode.zip - http://forum.xda-developers.com/show....php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/show....php?t=1369405
fastboot + adb for your OS of choice.
4. Followed following commands:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
5. After this, my kindle fire seems to have stuck in an infinite boot loop.
- It starts up only when a USB cable is connected.
- Power light is orange and not green
- It starts up Kindle Fire logo comes up, then shuts down again
- My computer is not detecting any device, probably because KF is in an infinite boot loop
- When I run adb devices -- no devices show up
- When I run fastboot command [fastboot -i 0x1949 flash bootloader .....] it says "waiting for devices"
- When I remove the USB cable from KF, It doesn't powers on (even after long pressing the power button).
- I tried many things posted on different forums on two laptops (Windows 7 32 bit as well as 64 bit) and using different USB cables but nothing worked.
- Only thing I haven't tried is Factory cable as I don't have it and don't have money to buy it.
PLEASE HELP!!
http://forum.xda-developers.com/showthread.php?t=1623244
Superuser not working
Thanks for the help with the charging issue Kinfauns!!!
I charged my kindle fire using stock charger and finally rooted it.
However, I am still not able to install android market on my KF.
After rooting Kindle (followed all the steps given in the thread), I installed Superuser.apk.
Then to install android market, I installed root explorer and downloaded Kindle Fire android market zip file. (followed instructions from one of the NAT3MIL's video on youtube).
First step is to install googleServicesFramework.apk file, which I did.
The next step is to move market.apk file to system/apps folder. However, when I tried doing that, I got a warning:
"Your phone doesn't appear to be rooted. This is requires in order to change or delete protected files such as this ......"
I don't understand why is it saying so as I have followed all the steps in the thread to root my KF?
How to check if the KF is really rooted?
Are there any settings to be changed in the superUser.apk?
Please help!!
Thanks a ton!!
Superuser not working
One more thing.
when I tried to update SU binary file,
I got following:
Downloading manifest .. OKAY!
parsing manifest.. Okay!
Latest Version = 3.0.3.2
Checking installed version .. legacy
Fixing database .. okay!
checking for busybox .. not found
Downloading custom busybox .. okay!
checking md5sum ... okay!
checking current install path .. fail!
Failed to find current installed su binary. Update cannot continue.
Does this mean I have to re-root the KF or just install the su binary file? how to do that?
Thanks!
Download the latest kindle fire utility and rerun it for permanent root.
Known Tricks
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Please note: If your device can't be seen in fastboot mode, please make sure to install the drivers packaged with this, as it will show up afterwards. You can use the install_drivers.bat with the device plugged in for this.
Copied from the instructions of the kindle fire utility
Above are the tricks if you get stuck but after root install twrp then install fff
I would assume that your not rooted sounds that way to me.
By the way the yellow triangle will be replaced with the new bootloader a white kindle and a blue fire this will be considered the yellow triangle in the description. Good luck
Install permanent root
Install twrp
Install fff
All should be the newest at this point hopefully
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
I believe so the worst that could happen is it could fail if the file already exists but let's hope it goes fine
tanwar said:
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
Click to expand...
Click to collapse
You don't necessarily have to let KFU do its entire "rooting" process.
If you can get into recovery and you are comfortable with adb, you can follow the "Rooting the stock software" section in this guide...
http://forum.xda-developers.com/showthread.php?t=1638452
to push the 'su' binary into the /system partition and set ownership/permissions.
If you are not comfortable with that, you can use KFU, but it will be doing a lot of extraneous things that you probably don't need.
Under extras you will put on Google frame work and go launcher after you have confirmed bootloader recovery and root note that the market can only be seen using go launcher not the kindle one.
---------- Post added at 12:32 AM ---------- Previous post was at 12:13 AM ----------
The easiest way to test root is to download an app that will request root permissions like root explorer for instance if you open the app and you don't see a dialogue pop up requesting permission its very likely that it isn't rooted.
Read-Only file system
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
nevermind I see your on windows 7 like me. adb shell mount system will mount system to read/ write
its all in kinfauns post you just need to be it recovery to execute the commands I believe I would paste it here but its just as easy to read them from there
adb shell chmod 6755 /system/xbin/su not 755 you can probably safely copy and paste the commands from his post right into cmd he has it written up very nicely
tanwar said:
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
Click to expand...
Click to collapse
I think you may be trying to do this while booted into the system software. That won't work because you don't have root access there and you won't be able to mount (or remount) a partition without those privileges. The rest of it won't work without R/W access to the partition, as you've already seen.
To be clear, the device needs to be booted into recovery (TWRP or CWMR) where you do have root privileges. Make sure you start with step one to get the system partition mounted. If successful, "mount" will provide no output.
My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.
Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.
Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?
adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2
nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?
veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit
hello, after some trouble installing the bootloader, I finally got it!!
But I have another problem, I thought it would start no problem then, so here I have no rom in sd!! and now will not start!
I can go into recovery mode, go to the usb storage option, but it does not work, I get on the computer!!
some way to spend a rom to the sd from l recovery / TWRP??????
Put the ROM and gapps in the same folder as an adb command, open a command prompt and CD to the directory with adb, now type something along the lines of this: adb push romname.zip /sdcard/
That should put the ROM on the sdcard so you can flash, use same thing for gapps as well.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Put the ROM and gapps in the same folder as an adb command, open a command prompt and CD to the directory with adb, now type something along the lines of this: adb push romname.zip /sdcard/
That should put the ROM on the sdcard so you can flash, use same thing for gapps as well.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you!
the problem is that now ADB does not recognize the tablet.
In device manager, I get the yellow triangle on kindle fire.
Reinstall the SDK but nothing, still without recognizing
EDIT I finally got it! you saved my life!! thank you very much!!