How Can I Backup The Stock Rom Of The Kindle Fire HD?
I think kimdle fire first aid will do it for you, but if not you can always use this snippet of commands to back it up:
Code:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD7Backup
adb pull /sdcard/stock-boot.img /KFHD7Backup
adb pull /sdcard/stock-recovery.img /KFHD7Backup
adb pull /sdcard/stock-system.img /KFHD7Backup
Thanks to seokhun for these, I modified them a bit to my liking because what he originally put was making my PC tell me I had incorrect syntax or something, so I used the Linux form which assumes c:\=/
And u probably have no idea what that means so just ignore it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
You can also access your Backup Recover Kindle fire HD from TWRP recovery to PC Computer by mounting it as a USB Storage to the PC, and on the PC go to SDCARD\TWRP\BACKUPS\(YOUR BACKUP FILE WITH THE FILE EXTENSION BEING '.WIN' AT THE END)
download 'Winrar' and install it and rename the (WIN TO TAR) on your backup file so that Winrar can extact it to view rom folder and files
if your going to repack it you need to download '7z ' and achieve it for it to be used as a valid rom on your android device.
HAVE GOOD DAY
bramz said:
You can also access your Backup Recover Kindle fire HD from TWRP recovery to PC Computer by mounting it as a USB Storage to the PC, and on the PC go to SDCARD\TWRP\BACKUPS\(YOUR BACKUP FILE WITH THE FILE EXTENSION BEING '.WIN' AT THE END)
download 'Winrar' and install it and rename the (WIN TO TAR) on your backup file so that Winrar can extact it to view rom folder and files
if your going to repack it you need to download '7z ' and achieve it for it to be used as a valid rom on your android device.
HAVE GOOD DAY
Click to expand...
Click to collapse
It's better to use the fastboot flashable images method that @stunts513 posted above.
Related
The attached ZIP includes scripts for Windows and Linux to backup your Galaxy Tab.
Linux users will need to install 7zip
Code:
sudo apt-get install p7zip
May also work on OSX but you're on your own with 7zip
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Windows
Code:
skitzbackup.cmd
Linux / OSX
Code:
chmod a+x <folder where you extracted it>/skitzbackup/skitzbackup.sh
cd <folder where you extracted it>/skitzbackup
./skitzbackup.sh
The script will pull the following partitions and pack them in a 7zip archive for safe keeping:
efs
recovery
boot
system
radio
cache
misc
Before you ask, I have no idea what the 'misc' partition is. Haven't had time to explore that yet
I have NOT tested flashing these back as yet, except for boot and recovery so you use this entirely at your own risk.
DOWNLOAD HERE
View attachment skitzbackup.zip
Enjoy!
Code:
alias del=rm
mkdir skitzbackup
cd skitzbackup
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/cache.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/misc.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/radio.img bs=4096"
adb pull /sdcard/efs.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/cache.img
adb pull /sdcard/misc.img
adb pull /sdcard/radio.img
adb shell rm /sdcard/efs.img
adb shell rm /sdcard/recovery.img
adb shell rm /sdcard/boot.img
adb shell rm /sdcard/system.img
adb shell rm /sdcard/cache.img
adb shell rm /sdcard/misc.img
adb shell rm /sdcard/radio.img
7z a skitzbackup.7z *.img
del *.img
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
working perfectly!You're great
djmasque said:
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
Click to expand...
Click to collapse
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
bcmobile said:
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
Click to expand...
Click to collapse
Okay, good work nonetheless
Looks a lot like rotobackup, hehe.
Chainfire said:
Looks a lot like rotobackup, hehe.
Click to expand...
Click to collapse
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
bcmobile said:
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
Click to expand...
Click to collapse
Whats needed now is a kind of automated restore
bcmobile said:
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Click to expand...
Click to collapse
Sorry for the noob question but how do i do this true windows?
Will this work for me?
Hi bcmobile,
This looks excellent.
I'm currently running a P7100 (10.1v) with ISI-Galaxy 1.2.5v (HC3.2) but my baseband/modem is still P7100BUKE2.
I would like to get the GSM working (for sending USSD commands) but I would need to flash my modem, and I would like to backup the modem before I flash it with the P7500 modem.bin, if something goes wrong, I can always go back to the old one.
In your script, is radio.img the modem.bin?
Also is the "/dev/block/" always the same on all the different versions of the tablet? (in other words if I have a 10.1v will this backup my modem).
Thanks so much. You help is much appreciated.
seraphimserapis said:
Whats needed now is a kind of automated restore
Click to expand...
Click to collapse
/!\ IN THEORY /!\ you'd just have to copy the .img files back to the tab and switch the command line arguments for dd. (e.g. dd if=/path/to/file.img of=/path/to/directory)
soo i know this is kind of old but does this work for any device? if so what am i doing wrong? its stuck on deamon started successfully...
I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?
hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!
I used Qemu local.prop method to set /system/fonts folder as 766 and bricked my KFHD with the following steps:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo ‘ro.kernel.qemu=1′ > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push myfont.ttf /system/fonts
adb shell
cd /system/fonts
mv DroidSans.ttf DroidSans.ttf.bak
ln -s myfont.ttf DroidSans.ttf
chmod -R 06766 /system/fonts
rm /data/local.prop
exit
adb reboot
Click to expand...
Click to collapse
Now my KFHD does gets stucked in
"Your Kindle doesn't seem to be able to boot"
Is that because I changed the permission? Or is it because I did not reboot first after changing permission, and than delete local.prop? Which step was wrong? I am worried that doing that again would cause the same problem. I assume that the only way to recover from this would be to get into fastboot mode with factory cable. But I still want to keep fonts folder as writable.
When you edit files like this, with a device like a KFHD, odds are they deal with the framework-res.apk And if you mess with files that deal with framework-res.apk, your bound to get boot loop. But anyways, can you get adb? If not, fast boot might be your best friend. Cables are available that can boot to it, and if you see the system img. Files in the android development section, you can use fasboot to flash those. It's not the easiest solution, but it is something.
Sent from my Fire HD with root!
Hey guys!
So I decided to try my hand at Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial. On Step 2: Grabbing Files and Backing Up, when I plug the code to cmd, it says: error: device not found. Now, I have the Fastboot icon on the KF's screen and I have the factory cable connected. Also, android sdk is installed (as the tutorial said) on my Windows 7 machine. Any ideas? Thanks in advance!
Mustang37 said:
Hey guys!
So I decided to try my hand at Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial. On Step 2: Grabbing Files and Backing Up, when I plug the code to cmd, it says: error: device not found. Now, I have the Fastboot icon on the KF's screen and I have the factory cable connected. Also, android sdk is installed (as the tutorial said) on my Windows 7 machine. Any ideas? Thanks in advance!
Click to expand...
Click to collapse
You're in fastboot mode to do what? Are you restoring after a mistake? What command were you using before that error, and what was the code you used that returned with the error? For now, see if you can reboot using the following code:
Code:
fastboot -i 0x1949 reboot
You can also try doing the normal shutting down with the power button, but I've never tried that, so be careful.
seokhun said:
You're in fastboot mode to do what? Are you restoring after a mistake? What command were you using before that error, and what was the code you used that returned with the error? For now, see if you can reboot using the following code:
Code:
fastboot -i 0x1949 reboot
You can also try doing the normal shutting down with the power button, but I've never tried that, so be careful.
Click to expand...
Click to collapse
Ok, I know that I can shut down with the power button. My problem is backing up my current Amazon ROM.
CODE (found at http://forum.xda-developers.com/showthread.php?t=2271909):
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD7Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
Thanks for the quick reply.
Mustang37 said:
Ok, I know that I can shut down with the power button. My problem is backing up my current Amazon ROM.
CODE (found at http://forum.xda-developers.com/showthread.php?t=2271909):
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD7Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
Thanks for the quick reply.
Click to expand...
Click to collapse
You're trying to backup with ADB commands in fastboot mode? What are you doing in fastboot mode?
ADB is simply turning on the device, make sure ADB is on under Settings, and connect the device to the PC with the regular charging cable. That's it. Fastboot commands use "fastboot" at the beginning.
Ahhh, ok got it. One last question, when I add the following codes to backup, I get the remote object '/sdcard/stock-recovery.img/' does not exist ERROR. I've rooted it and followed the instructions.Thoughts?
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
Mustang37 said:
Ahhh, ok got it. One last question, when I add the following codes to backup, I get the remote object '/sdcard/stock-recovery.img/' does not exist ERROR. I've rooted it and followed the instructions.Thoughts?
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
Click to expand...
Click to collapse
Those commands tell the device to pull the images from the sdcard to the new directory, so if you have nothing on the sdcard for ADB to pull, it returns with that error. Do the first set again.
Ok, that still doesn't work, I do understand what you are saying though.
I apply these lines of codes:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
I still get the same error when apply these lines of codes after it:
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
remote object '/sdcard/stock-boot.img/' does not exist
The last line of code of the first set, nothing comes up after it.
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
Usually, it comes out like this:
C:\Users\Username>adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-n
ame/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 3.058 secs (2743168 bytes/sec)
Thanks for the quick replies guys! Appreciate it!
Mustang37 said:
Ok, that still doesn't work, I do understand what you are saying though.
I apply these lines of codes:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
I still get the same error when apply these lines of codes after it:
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
remote object '/sdcard/stock-boot.img/' does not exist
The last line of code of the first set, nothing comes up after it.
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
Usually, it comes out like this:
C:\Users\Username>adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-n
ame/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 3.058 secs (2743168 bytes/sec)
Thanks for the quick replies guys! Appreciate it!
Click to expand...
Click to collapse
Is there a folder called "KFHD7Backup" under the C: drive? Also, check your personal folder, some images might be in there.
ALRIGHT! Finally, I used hashcode's code and it worked. I also found it in my personal folder. Thanks a lot!
Mustang37 said:
ALRIGHT! Finally, I used hashcode's code and it worked. I also found it in my personal folder. Thanks a lot!
Click to expand...
Click to collapse
o.o
I'm lost and I need help. I copied my code from Hashcode, so...I'm lost. Anyway, complete the guide and get flashing.
Thank you for the tools you are developing here and the help you are giving.
My KFHD7 is rooted and adb works.
I apply these lines of code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
I checked on my Kindle with ESExplorer and I can see on the sdcard the 3 files: stock-boot.img, stock-recovery.img and stock-system.img.
But when I want to move them to C, I received the message
remote object '/sdcard/stock-boot.img/' does not exist
I can't see the files on the internal storage of the Kindle, via the computer. But I can see others files which are there.
Did I miss something?
Thank you in advance,
Jeanphi
I had issues with the syntax of that command at first too, try typing this instead:
"adb pull /sdcard/stock-boot.img ."
That should pull the file into the directory u have the command prompt cd'd into. Another note I couldn't get it to accept c:\ as a acceptable syntax, so being a Linux user I found on windows u can run "adb pull /sdcard/stock-boot.img /users/username/desktop" and basically / acts as c:\, if u want to put it in a specific place.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I had issues with the syntax of that command at first too, try typing this instead:
"adb pull /sdcard/stock-boot.img ."
That should pull the file into the directory u have the command prompt cd'd into. Another note I couldn't get it to accept c:\ as a acceptable syntax, so being a Linux user I found on windows u can run "adb pull /sdcard/stock-boot.img /users/username/desktop" and basically / acts as c:\, if u want to put it in a specific place.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for the quick reply.
I'm also using Linux, even if I'm a beginner.
So this not a problem of Windows.
Both OS show the same symptoms: the following error message and the fact that in both cases, I can't see the files on the sdcard when I look on the Internal storage of the Kindle, with the computer, even if can see other files (but not any file with an .img extension)
[email protected]:~$ adb pull /sdcard/stock-boot.img
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
5958 KB/s (8388608 bytes in 1.374s)
[email protected]:~$ adb pull /sdcard/stock-boot.img/
remote object '/sdcard/stock-boot.img/' does not exist
I copied with ESexplorer the three files (stock-boot.img, etc) on Download on the Kindle.
Then,
[email protected]:~$ adb pull /sdcard/Download/stock-boot.img/
remote object '/sdcard/Download/stock-boot.img/' does not exist
[email protected]:~$
(Download is with a capital D on the Kindle)
So the files are available on the Kindle. The problem is to find a way to put them on the computer.
Can I mail them to me ?
Jeanphi.
That's still the wrong syntax, don't put a / after the end of the filename, instead put a space and a period.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's still the wrong syntax, don't put a / after the end of the filename, instead put a space and a period.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Sorry. I haven't seen the new syntax.
It works perfectly with Linux (Ubuntu).
Thanks again.
I will try the following steps of your thread about the 2nd bootloader, but I might wait til I have a factory cable.
Jeanphi
---------- Post added at 10:19 AM ---------- Previous post was at 10:08 AM ----------
jeanphi506 said:
Sorry. I haven't seen the new syntax.
It worked perfectly with Linux (Ubuntu). I have now the three files on my computer.
Thanks again.
I will try the following steps of your thread about the 2nd bootloader, but I might wait till I have a factory cable.
Jeanphi
Click to expand...
Click to collapse
Spelling corrections
Same Problem.. can't fix
Mustang37 said:
ALRIGHT! Finally, I used hashcode's code and it worked. I also found it in my personal folder. Thanks a lot!
Click to expand...
Click to collapse
Hi,
I have same problem... but I didn't understand how did you fixed it.
what's the hashcode? how can I use it? could you please explain.
thanks in advance...
Once i fgured out that i could not use adb shell su -c but had to drop su -c from the commands the entire update proccess took no more than 20 minutes (i did not back up my old rom etc with back up prob take 40 minutes to a hour)
Any ways here it is again thanks to seokhun for his original guide i only modded the adb shell commands in this one.
Also thanks to every one who answered questions regarding this mess. Even answers that did not get it rerooted etc helped to find the answers that got this thing back to usable.
word to the wise do not buy display units or "refurbs" from bestbuy good chance a scammer returned it after adding insurance etc you will be left with something you can do nothing with in most cases. This type of scammy nonsense is very common here in northeast ohio at the very least
Taken from forums here most if not all from seokhun's guide "[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial"
located http://forum.xda-developers.com/showthread.php?t=2277105
again i had to remove su -c from the adb commands and that was really the only change. They may work on some if not most other kindle fire hd 8.9 with 8.4.9 software update
First step you need to enable fastboot (kfhd 8.9) using kindle fire srt ver 2.1 (option 1) you can test fast boot if you like with getvar etc etc
What i did notice was the commands from the instructions i pulled from the forums here that included adb shell su -c would not work as wrote i had to remove the su -c at that point they worked flawlessly. If i can find all the sources for the instructions ill give props where props are do. So if any of you all who wrote the guids see your stuff please do take credit where do. I spent hours sifting the forums for various guids etc.
After enabling fastboot go ahead and root with Root_with_Restore_by_Bin4ry option 1 your kfhd 8.9 with 8.4.9 is going to run stupid slow and painfully. Do not worry it works fine through adb and fastboot commands just dont freak out when it runs dead snail slow.
1
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.7.0.0 for the Kindle Fire HD
8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS,
I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES
YOUR DEVICE. ***
** THESE FILES WILL ONLY WORK ON A KINDLE FIRE HD 8.9. DO NOT ATTEMPT TO USE
THESE FILES ON ANY OTHER DEVICE. **
** WHEN MODDING THE KFIRE HD YOU SHOULD HAVE WORKING FASTBOOT DRIVERS ON YOUR
PC. **
FASTBOOT CABLES ARE NOT REQUIRED FOR USING FASTBOOT MODE ON THE KINDLE FIRE HD
8.9.
DOWNLOAD THE ANDROID SDK AND GO FROM THERE.
POSSIBLE ALSO THAT USING A FASTBOOT CABLE ON THE 8.9 WILL CAUSE DAMAGE.
http://developer.android.com/sdk/index.html
MAC USERS: USEFUL LINKS
http://forum.xda-developers.com/show...&postcount=230
Q: How do I know if my fastboot works?
A: With the Kindle powered down, type the following command into a cmd/terminal
window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and reboot. It *SHOULD* show a Fastboot screen
and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE
ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD
AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T
FIND THE ANSWER **
INSTRUCTIONS FOR INSTALLING A 2ND-BOOTLOADER TO LOAD CUSTOM KERNELS / ROMS /
RECOVERY:
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
STEP 1. Backup your stock partitions to your own HD for later if you need
disaster recovery:
Code:
adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
of=/sdcard/stock-boot.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
of=/sdcard/stock-recovery.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system
of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
**** MAC USERS MAY NEED TO SPARSE THE FILES FOR RE-FLASHING TO THE DEVICE. I
NEED A MAC USER TO PROBABLY WORK THROUGH THAT PROCESS AND I CAN POST BACKUP
COPIES OF THE STOCK PARTITIONS FOR DISASTER RECOVERY ****
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and
CM11.0:
Stack override file: http://goo.im/devs/Hashcode/jem/stack
[12/09] kfhd8-freedom-boot-8.4.6.img (USED ONLY THE FIRST TIME -- .zip files
will have their own boot.img's from now on):
Mirror 1: Download (Goo.im)
md5sum: 8374cf88e75abda8c374044a1f0daa5f
[04/16] TWRP Recovery 2.7.0.0:
Mirror 1: Download (Goo.im)
md5sum: a0c7533fd853849184850580350abd18
CM-11.0 for the Kindle Fire HD 8.9 (choose the latest version from):
Mirror 1: Browse (Goo.im)
Google Apps from:
http://www.androidfilehost.com/?fid=23311191640114013 (This version for CM-
11.0!)
Download the older 8.1.4 bootloader file and flash to your device via fastboot:
Mirror 1: Download (Goo.im)
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Place the CM-11.0 ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS --
May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to
permissions changes
Code:
adb push stack /sdcard/
adb shell "dd if=/sdcard/stack
of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
STEP 4. Stop the auto recovery update script (this file may or may not be
present):
Code:
adb shell "mount -o remount,rw ext4 /system"
adb shell "mv /system/etc/install-recovery.sh /system/etc/install-
recovery.sh.bak"
adb shell "mount -o remount,ro ext4 /system"
STEP 5:
[ With the device powered off: Issue the following commands into your
command/terminal window on your PC. Start with the first command and press
enter. Then connect USB to the Kindle and power on ]
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img
fastboot -i 0x1949 reboot
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM11.0 -- IT'S FOR STOCK
AMAZON OS ONLY / FIRST INSTALL ONLY*
** If everything was done correctly your Kindle will reboot and you will at
first see the normal Kindle Fire ORANGE logo and then it will fade and come
back as a BLUE logo. **
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and
keep pressing until the logo turns BLUE. Wait a moment and you should enter
recovery.
STEP 6:
CM-11.0 AND GAPPS INSTALLATION:
(OPTIONAL) Make a backup by selecting "Backup" and then slide your finger to
the right on the "Swipe to Back Up"
Once complete use the pentagon "Home" icon in the upper right corner of the
screen (next to the back arrow and terminal icon)
Now, select "Wipe"
Swipe the "Swipe to Factory Reset"
Use the "Home" icon
Select "Install"
Browse to the location on your device where you saved the CM-11.0 / GAPPS .ZIP
files
Select the CM11.0 .ZIP file in the list by touching it, then confirm it says
the name of the CM-11.0 .ZIP file on the next screen under "File to flash:"
Select "Add More Zips"
Select the GAPPS .ZIP file in the list by touching it -- make sure it says the
name of the .ZIP again under "File to flash:"
Swipe the "Swipe to Confirm Flash", and wait for it to finish.
If the screen is blank at any time you can hit the power button to "wake up"
the device
Once the flash is done, you'll see a "Home" and "Reboot" buttons at the bottom
of the screen
Select "Reboot"
CONGRATULATIONS YOU NOW HAVE THE ABILITY TO INSTALL CUSTOM KERNELS / RECOVERY
AND ROMS.
Nanaki-seto said:
Once i fgured out that i could not use adb shell su -c but had to drop su -c from the commands the entire update proccess took no more than 20 minutes (i did not back up my old rom etc with back up prob take 40 minutes to a hour)
Any ways here it is again thanks to seokhun for his original guide i only modded the adb shell commands in this one.
Also thanks to every one who answered questions regarding this mess. Even answers that did not get it rerooted etc helped to find the answers that got this thing back to usable.
word to the wise do not buy display units or "refurbs" from bestbuy good chance a scammer returned it after adding insurance etc you will be left with something you can do nothing with in most cases. This type of scammy nonsense is very common here in northeast ohio at the very least
Taken from forums here most if not all from seokhun's guide "[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial"
located http://forum.xda-developers.com/showthread.php?t=2277105
again i had to remove su -c from the adb commands and that was really the only change. They may work on some if not most other kindle fire hd 8.9 with 8.4.9 software update
First step you need to enable fastboot (kfhd 8.9) using kindle fire srt ver 2.1 (option 1) you can test fast boot if you like with getvar etc etc
What i did notice was the commands from the instructions i pulled from the forums here that included adb shell su -c would not work as wrote i had to remove the su -c at that point they worked flawlessly. If i can find all the sources for the instructions ill give props where props are do. So if any of you all who wrote the guids see your stuff please do take credit where do. I spent hours sifting the forums for various guids etc.
After enabling fastboot go ahead and root with Root_with_Restore_by_Bin4ry option 1 your kfhd 8.9 with 8.4.9 is going to run stupid slow and painfully. Do not worry it works fine through adb and fastboot commands just dont freak out when it runs dead snail slow.
1
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.7.0.0 for the Kindle Fire HD
8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS,
I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES
YOUR DEVICE. ***
** THESE FILES WILL ONLY WORK ON A KINDLE FIRE HD 8.9. DO NOT ATTEMPT TO USE
THESE FILES ON ANY OTHER DEVICE. **
** WHEN MODDING THE KFIRE HD YOU SHOULD HAVE WORKING FASTBOOT DRIVERS ON YOUR
PC. **
FASTBOOT CABLES ARE NOT REQUIRED FOR USING FASTBOOT MODE ON THE KINDLE FIRE HD
8.9.
DOWNLOAD THE ANDROID SDK AND GO FROM THERE.
POSSIBLE ALSO THAT USING A FASTBOOT CABLE ON THE 8.9 WILL CAUSE DAMAGE.
http://developer.android.com/sdk/index.html
MAC USERS: USEFUL LINKS
http://forum.xda-developers.com/show...&postcount=230
Q: How do I know if my fastboot works?
A: With the Kindle powered down, type the following command into a cmd/terminal
window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and reboot. It *SHOULD* show a Fastboot screen
and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE
ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD
AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T
FIND THE ANSWER **
INSTRUCTIONS FOR INSTALLING A 2ND-BOOTLOADER TO LOAD CUSTOM KERNELS / ROMS /
RECOVERY:
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
STEP 1. Backup your stock partitions to your own HD for later if you need
disaster recovery:
Code:
adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
of=/sdcard/stock-boot.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
of=/sdcard/stock-recovery.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system
of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
**** MAC USERS MAY NEED TO SPARSE THE FILES FOR RE-FLASHING TO THE DEVICE. I
NEED A MAC USER TO PROBABLY WORK THROUGH THAT PROCESS AND I CAN POST BACKUP
COPIES OF THE STOCK PARTITIONS FOR DISASTER RECOVERY ****
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and
CM11.0:
Stack override file: http://goo.im/devs/Hashcode/jem/stack
[12/09] kfhd8-freedom-boot-8.4.6.img (USED ONLY THE FIRST TIME -- .zip files
will have their own boot.img's from now on):
Mirror 1: Download (Goo.im)
md5sum: 8374cf88e75abda8c374044a1f0daa5f
[04/16] TWRP Recovery 2.7.0.0:
Mirror 1: Download (Goo.im)
md5sum: a0c7533fd853849184850580350abd18
CM-11.0 for the Kindle Fire HD 8.9 (choose the latest version from):
Mirror 1: Browse (Goo.im)
Google Apps from:
http://www.androidfilehost.com/?fid=23311191640114013 (This version for CM-
11.0!)
Download the older 8.1.4 bootloader file and flash to your device via fastboot:
Mirror 1: Download (Goo.im)
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Place the CM-11.0 ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS --
May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to
permissions changes
Code:
adb push stack /sdcard/
adb shell "dd if=/sdcard/stack
of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
STEP 4. Stop the auto recovery update script (this file may or may not be
present):
Code:
adb shell "mount -o remount,rw ext4 /system"
adb shell "mv /system/etc/install-recovery.sh /system/etc/install-
recovery.sh.bak"
adb shell "mount -o remount,ro ext4 /system"
STEP 5:
[ With the device powered off: Issue the following commands into your
command/terminal window on your PC. Start with the first command and press
enter. Then connect USB to the Kindle and power on ]
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img
fastboot -i 0x1949 reboot
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM11.0 -- IT'S FOR STOCK
AMAZON OS ONLY / FIRST INSTALL ONLY*
** If everything was done correctly your Kindle will reboot and you will at
first see the normal Kindle Fire ORANGE logo and then it will fade and come
back as a BLUE logo. **
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and
keep pressing until the logo turns BLUE. Wait a moment and you should enter
recovery.
STEP 6:
CM-11.0 AND GAPPS INSTALLATION:
(OPTIONAL) Make a backup by selecting "Backup" and then slide your finger to
the right on the "Swipe to Back Up"
Once complete use the pentagon "Home" icon in the upper right corner of the
screen (next to the back arrow and terminal icon)
Now, select "Wipe"
Swipe the "Swipe to Factory Reset"
Use the "Home" icon
Select "Install"
Browse to the location on your device where you saved the CM-11.0 / GAPPS .ZIP
files
Select the CM11.0 .ZIP file in the list by touching it, then confirm it says
the name of the CM-11.0 .ZIP file on the next screen under "File to flash:"
Select "Add More Zips"
Select the GAPPS .ZIP file in the list by touching it -- make sure it says the
name of the .ZIP again under "File to flash:"
Swipe the "Swipe to Confirm Flash", and wait for it to finish.
If the screen is blank at any time you can hit the power button to "wake up"
the device
Once the flash is done, you'll see a "Home" and "Reboot" buttons at the bottom
of the screen
Select "Reboot"
CONGRATULATIONS YOU NOW HAVE THE ABILITY TO INSTALL CUSTOM KERNELS / RECOVERY
AND ROMS.
Click to expand...
Click to collapse
Any update to this? Like for lineage 0s? and twrp 3.02????
Nanaki-seto said:
Once i fgured out that i could not use adb shell su -c but had to drop su -c from the commands the entire update proccess took no more than 20 minutes (i did not back up my old rom etc with back up prob take 40 minutes to a hour)
Any ways here it is again thanks to seokhun for his original guide i only modded the adb shell commands in this one.
Also thanks to every one who answered questions regarding this mess. Even answers that did not get it rerooted etc helped to find the answers that got this thing back to usable.
word to the wise do not buy display units or "refurbs" from bestbuy good chance a scammer returned it after adding insurance etc you will be left with something you can do nothing with in most cases. This type of scammy nonsense is very common here in northeast ohio at the very least
Taken from forums here most if not all from seokhun's guide "[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial"
located http://forum.xda-developers.com/showthread.php?t=2277105
again i had to remove su -c from the adb commands and that was really the only change. They may work on some if not most other kindle fire hd 8.9 with 8.4.9 software update
First step you need to enable fastboot (kfhd 8.9) using kindle fire srt ver 2.1 (option 1) you can test fast boot if you like with getvar etc etc
What i did notice was the commands from the instructions i pulled from the forums here that included adb shell su -c would not work as wrote i had to remove the su -c at that point they worked flawlessly. If i can find all the sources for the instructions ill give props where props are do. So if any of you all who wrote the guids see your stuff please do take credit where do. I spent hours sifting the forums for various guids etc.
After enabling fastboot go ahead and root with Root_with_Restore_by_Bin4ry option 1 your kfhd 8.9 with 8.4.9 is going to run stupid slow and painfully. Do not worry it works fine through adb and fastboot commands just dont freak out when it runs dead snail slow.
1
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.7.0.0 for the Kindle Fire HD
8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS,
I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES
YOUR DEVICE. ***
** THESE FILES WILL ONLY WORK ON A KINDLE FIRE HD 8.9. DO NOT ATTEMPT TO USE
THESE FILES ON ANY OTHER DEVICE. **
** WHEN MODDING THE KFIRE HD YOU SHOULD HAVE WORKING FASTBOOT DRIVERS ON YOUR
PC. **
FASTBOOT CABLES ARE NOT REQUIRED FOR USING FASTBOOT MODE ON THE KINDLE FIRE HD
8.9.
DOWNLOAD THE ANDROID SDK AND GO FROM THERE.
POSSIBLE ALSO THAT USING A FASTBOOT CABLE ON THE 8.9 WILL CAUSE DAMAGE.
http://developer.android.com/sdk/index.html
MAC USERS: USEFUL LINKS
http://forum.xda-developers.com/show...&postcount=230
Q: How do I know if my fastboot works?
A: With the Kindle powered down, type the following command into a cmd/terminal
window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and reboot. It *SHOULD* show a Fastboot screen
and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE
ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD
AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T
FIND THE ANSWER **
INSTRUCTIONS FOR INSTALLING A 2ND-BOOTLOADER TO LOAD CUSTOM KERNELS / ROMS /
RECOVERY:
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
STEP 1. Backup your stock partitions to your own HD for later if you need
disaster recovery:
Code:
adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
of=/sdcard/stock-boot.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
of=/sdcard/stock-recovery.img"
adb shell "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system
of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
**** MAC USERS MAY NEED TO SPARSE THE FILES FOR RE-FLASHING TO THE DEVICE. I
NEED A MAC USER TO PROBABLY WORK THROUGH THAT PROCESS AND I CAN POST BACKUP
COPIES OF THE STOCK PARTITIONS FOR DISASTER RECOVERY ****
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and
CM11.0:
Stack override file: http://goo.im/devs/Hashcode/jem/stack
[12/09] kfhd8-freedom-boot-8.4.6.img (USED ONLY THE FIRST TIME -- .zip files
will have their own boot.img's from now on):
Mirror 1: Download (Goo.im)
md5sum: 8374cf88e75abda8c374044a1f0daa5f
[04/16] TWRP Recovery 2.7.0.0:
Mirror 1: Download (Goo.im)
md5sum: a0c7533fd853849184850580350abd18
CM-11.0 for the Kindle Fire HD 8.9 (choose the latest version from):
Mirror 1: Browse (Goo.im)
Google Apps from:
http://www.androidfilehost.com/?fid=23311191640114013 (This version for CM-
11.0!)
Download the older 8.1.4 bootloader file and flash to your device via fastboot:
Mirror 1: Download (Goo.im)
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Place the CM-11.0 ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS --
May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to
permissions changes
Code:
adb push stack /sdcard/
adb shell "dd if=/sdcard/stack
of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
STEP 4. Stop the auto recovery update script (this file may or may not be
present):
Code:
adb shell "mount -o remount,rw ext4 /system"
adb shell "mv /system/etc/install-recovery.sh /system/etc/install-
recovery.sh.bak"
adb shell "mount -o remount,ro ext4 /system"
STEP 5:
[ With the device powered off: Issue the following commands into your
command/terminal window on your PC. Start with the first command and press
enter. Then connect USB to the Kindle and power on ]
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img
fastboot -i 0x1949 reboot
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM11.0 -- IT'S FOR STOCK
AMAZON OS ONLY / FIRST INSTALL ONLY*
** If everything was done correctly your Kindle will reboot and you will at
first see the normal Kindle Fire ORANGE logo and then it will fade and come
back as a BLUE logo. **
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and
keep pressing until the logo turns BLUE. Wait a moment and you should enter
recovery.
STEP 6:
CM-11.0 AND GAPPS INSTALLATION:
(OPTIONAL) Make a backup by selecting "Backup" and then slide your finger to
the right on the "Swipe to Back Up"
Once complete use the pentagon "Home" icon in the upper right corner of the
screen (next to the back arrow and terminal icon)
Now, select "Wipe"
Swipe the "Swipe to Factory Reset"
Use the "Home" icon
Select "Install"
Browse to the location on your device where you saved the CM-11.0 / GAPPS .ZIP
files
Select the CM11.0 .ZIP file in the list by touching it, then confirm it says
the name of the CM-11.0 .ZIP file on the next screen under "File to flash:"
Select "Add More Zips"
Select the GAPPS .ZIP file in the list by touching it -- make sure it says the
name of the .ZIP again under "File to flash:"
Swipe the "Swipe to Confirm Flash", and wait for it to finish.
If the screen is blank at any time you can hit the power button to "wake up"
the device
Once the flash is done, you'll see a "Home" and "Reboot" buttons at the bottom
of the screen
Select "Reboot"
CONGRATULATIONS YOU NOW HAVE THE ABILITY TO INSTALL CUSTOM KERNELS / RECOVERY
AND ROMS.
Click to expand...
Click to collapse
That don't work, followed step 5 to a T. Just stuck the tablet at kindle logo.