Related
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.8.x.x 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/showpost.php?p=41199927&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 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" # 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 CM:
ON THE FOLLOWING DEV-HOST LINKS
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Stack override file:
Mirror 1: Download "stack" from Dev-Host
[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 "kfhd8-freedom-boot-8.4.6.img" from Dev-Host
md5sum: 8374cf88e75abda8c374044a1f0daa5f
[06/24] TWRP 2.8.7.0 recovery flash Image
Mirror 1: Download TWRP from Dev-Host
md5sum: a0c7533fd853849184850580350abd18
CM-12.1 for the Kindle Fire HD 8.9 (choose the latest version from):
Mirror 1: Downloads CM
Google Apps from Android File Host:
https://www.androidfilehost.com/?w=files&flid=25361 (Use 5.1 version!)
Download the older 8.1.4 bootloader file and flash to your device via fastboot:
Mirror 1: Download bootloader from Dev-Host
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Place the CM-12.1 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 su -c "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 su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "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.8.7.0-recovery.img
fastboot -i 0x1949 reboot
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CUSTOM ROMS -- 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-12.1 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 CM12.1 ZIP file in the list by touching it, then confirm it says the name of the CM-12.1 .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.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1: ** OR Follow this thread's instructions:
http://forum.xda-developers.com/showthread.php?t=2011126
**** 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 ****
Once you have these files (we'll name them boot.img/recovery.img and system.img for the purpose of these instructions, but they could be different on your system).
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot [B]boot.img[/B]
fastboot -i 0x1949 flash recovery [B]recovery.img[/B]
fastboot -i 0x1949 flash system [B]system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot
THANKS TO:
fattire for finding the original bootloader exploit
verygreen for doing some initial work on the 2nd-bootloader and fixing bugs (and letting me copy some of his bootloader installation instructions)
RESERVED
WOW.....
Finally. :laugh:
Hashcode said:
*** 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 (UNTESTED ON THE LTE VERSION). DO NOT ATTEMPT TO USE THESE FILES ON ANY OTHER DEVICE. **
** WHEN MODDING THE KFIRE HD YOU SHOULD HAVE A WORKING FASTBOOT CABLE + FASTBOOT DRIVERS/ACCESS ON YOUR PC. **
Q: How do I know if my fastboot works?
A: Plug the cable into your device and then reboot the Kindle. It *SHOULD* show a Fastboot screen.
Once at the screen use this command on your computer:
fastboot devices
You should see something like this:
0123456789ABCDEF fastboot
Q: How is this different than the 2nd-bootloader from verygreen's thread?
A: Verygreen's 2nd-bootloader was more of a proof of concept and doesn't allow for button entry into recovery and may have issues booting from custom sized boot.imgs. I've been using this one for about a month during my CM10.1 development.
** 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 pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # 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 CM10.1:
Stack override file: http://goo.im/devs/Hashcode/jem/stack
kfhd8-freedom-boot.img (USED ONLY THE FIRST TIME -- .zip files will have their own boot.img's from now on): http://goo.im/devs/Hashcode/jem/kfhd8-freedom-boot.img
TWRP Recovery: http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.3.3.0-recovery.img
CM-10.1 for the Kindle Fire HD 8.9 (choose the latest version from): http://goo.im/devs/Hashcode/jem/cm10.1
Google Apps from: http://goo.im/gapps (choose the top rom CM10.1 version)
Place the CM-10.1 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:
Code:
adb push stack /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
STEP 4. Connect fastboot cable OR if you have fastboot drivers setup correctly you can use a standard USB cable to issue the following commands. Start with the first command and press enter. This will show <waiting for device> and then power on the Kindle. Once the fastboot screen is shown and the first command completes you can enter the rest of the commands.
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM10.1 -- IT'S FOR STOCK AMAZON OS ONLY / FIRST INSTALL ONLY*
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot.img
fastboot -i 0x1949 flash recovery kdh8-twrp-2.3.3.0-recovery.img
fastboot -i 0x1949 reboot
** 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. **
CONGRATULATIONS YOU NOW HAVE THE ABILITY TO INSTALL CUSTOM KERNELS / RECOVERY AND ROMS.
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.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1: **
**** 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 ****
Once you have these files (we'll name them boot.img/recovery.img and system.img for the purpose of these instructions, but they could be different on your system).
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot [B]boot.img[/B]
fastboot -i 0x1949 flash recovery [B]recovery.img[/B]
fastboot -i 0x1949 flash system [B]system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot
THANKS TO:
fattire for finding the original bootloader exploit
verygreen for doing some initial work on the 2nd-bootloader and fixing bugs (and letting me copy some of his bootloader installation instructions)
Click to expand...
Click to collapse
Sweet! Can't wait to try. Just got my ebay fastboot cable last night. Time to finally open the KF.
supernoman said:
Sweet! Can't wait to try. Just got my ebay fastboot cable last night. Time to finally open the KF.
Click to expand...
Click to collapse
And of course, when I go to actually test a fastboot cable on the KFHD8: it does NOT automatically place you in fastboot mode. So you make sure you have the Android SDK installed:
http://developer.android.com/sdk/index.html
I added a missing step where the auto recovery updater runs in the OS on stock boot:
To disable this auto recovery installer do this via adb:
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9
Neat, gonna get around to this later on tomorrow. Thanks man!
Sent from my KFJWI
well, it was a three hour epic battle but I finally got the boot and recovery installed. getting into fastboot and having the device recognized was pretty darn hard. i found using the recovery tool found here: http://forum.xda-developers.com/showthread.php?t=2011126 to be invaluable for getting into fastboot with a non fastboot cable. Also, eveytime I tried to flash the recovery, i kept getting an error complaining about the file size being too big to upload to my device. oddly enough, I downloaded the TWRP recovery once more and renamed it "recovery.img" and was able to flash. not sure if that was coincidence. another trick is to keep device manager open, in fast boot, the kindle will show up as "Jem -XXX-XXX" and you need to use the "Android ADB Composite USB" driver. right now I'm in recovery and about to flash CM10.1 BUT, ONE IMPORTANT QUESTION - WILL WIPING PARTITIONS DO IRREVERSIBLE DAMAGE ? sorry for yelling and thanks so much for your hard work -it's greatly appreciated.
Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9
If you make a backup in TWRP, you can always restore it later.
Hold off on CM10.1, I'm rebuilding.
Sent from my DROID RAZR HD using Tapatalk 2
Can't get fastboot working...
Tried 2 different 8.9's, with 3 different USB cables on Windows 7 and Linux with each.
EDIT: Nevermind, finally got it working
Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9
FroyoShark said:
Can't get fastboot working...
Tried 2 different 8.9's, with 3 different USB cables on Windows 7 and Linux with each.
EDIT: Nevermind, finally got it working
Click to expand...
Click to collapse
Awesome, feel free to share any tips.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode said:
Awesome, feel free to share any tips.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Turns out I could only get it working on Linux using root shell, everything else failed.
Hashcode said:
If you make a backup in TWRP, you can always restore it later.
Hold off on CM10.1, I'm rebuilding.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
do you mean we can back up stock OS and flash it back later, without going through fastboot and keep TWRP with stock OS?
After installing CM10.1+ Gapps, it booted to a black screen, so I did a hard reset. Went back into TWRP, wiped system, and flashed just CM10.1. After that, it got stuck on the orange Kindle Fire logo (doesn't get to the blue one) and even reflashing the bootloader/recovery doesn't fix it.
EDIT: Tried restoring my system backup from the stock ROM, that didn't work either. Restoring the stock boot image makes it so I can boot into the stock ROM though.
EDIT 2: Must have done something wrong. It's working fine again, but CM10.1 still doesn't work.
FroyoShark said:
After installing CM10.1+ Gapps, it booted to a black screen, so I did a hard reset. Went back into TWRP, wiped system, and flashed just CM10.1. After that, it got stuck on the orange Kindle Fire logo (doesn't get to the blue one) and even reflashing the bootloader/recovery doesn't fix it.
EDIT: Tried restoring my system backup from the stock ROM, that didn't work either. Restoring the stock boot image makes it so I can boot into the stock ROM though.
EDIT 2: Must have done something wrong. It's working fine again, but CM10.1 still doesn't work.
Click to expand...
Click to collapse
When re-setting up the Kindle for the 2nd-bootloader, PLEASE re-review the steps in the OP, I added a missing step later after the original posting.
(It's the disabling of the "install-recovery.sh" file)
Hashcode said:
When re-setting up the Kindle for the 2nd-bootloader, PLEASE re-review the steps in the OP, I added a missing step later after the original posting.
(It's the disabling of the "install-recovery.sh" file)
Click to expand...
Click to collapse
Yeah, that's how I got it working. Also, there's a typo in the OP, you put "fastboot -i 0x1949 flash recovery kdh8-twrp-2.3.3.0-recovery.img" instead of "fastboot -i 0x1949 flash recovery kfhd8-twrp-2.3.3.0-recovery.img"
Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9
Guh. I actually fixed (or thought I did) that typo last night. Ah well, I re-editted it just now and it looks like it took.
Thanks for pointing that out.
Sent from my DROID RAZR HD using Tapatalk 2
Is TWRP extremely choppy for everyone else?
Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9
it is a little slow to respond. i built it with a custom kernel a while back.
i may try either an updated kernel or using stock kernel to see if it helps.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode said:
it is a little slow to respond. i built it with a custom kernel a while back.
i may try either an updated kernel or using stock kernel to see if it helps.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
That would be nice. It's not a big issue, but it's a bit annoying.
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
huntergero said:
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
Click to expand...
Click to collapse
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
LinearEquation said:
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
Click to expand...
Click to collapse
When it failed to boot in went into kindles reboot software and when i asked the individual i got this from he said he didnt install any recovery software.Can I install twerp now
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
Nope, it has to be a factory restore using your fastboot cord. I will list instructions.
---------- Post added at 09:50 PM ---------- Previous post was at 09:30 PM ----------
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Okay, I know this question has been asked quite a few times, but I'm really stuck here.
I was running CM10.2 on my KFHD, when I wanted to revert back to Stock OS for a while so I could test something I was working on. I created a full backup in TWRP so that once I was done I could go back. I then proceeded to wipe (factory reset) and flash the 7.4.3. I then rebooted. My Kindle won't get past the 2nd bootloader. It only show's the blue logo. I thought, "Okay, something's not right, I'll just restore from a backup. So I rebooted into TWRP, and proceeded to restore, only to be graced by big red letters that said, "Restore Failed." I rebooted the bootloader, putting it into fastboot mode, and tried to restore from some boot, recovery, and system images I had lying around on my hard drive somewhere. Still no dice. My Kindle just sits there, refusing to boot past the 2nd boot loader.
Any ideas out there?
Ph0enix_216 said:
Okay, I know this question has been asked quite a few times, but I'm really stuck here.
I was running CM10.2 on my KFHD, when I wanted to revert back to Stock OS for a while so I could test something I was working on. I created a full backup in TWRP so that once I was done I could go back. I then proceeded to wipe (factory reset) and flash the 7.4.3. I then rebooted. My Kindle won't get past the 2nd bootloader. It only show's the blue logo. I thought, "Okay, something's not right, I'll just restore from a backup. So I rebooted into TWRP, and proceeded to restore, only to be graced by big red letters that said, "Restore Failed." I rebooted the bootloader, putting it into fastboot mode, and tried to restore from some boot, recovery, and system images I had lying around on my hard drive somewhere. Still no dice. My Kindle just sits there, refusing to boot past the 2nd boot loader.
Any ideas out there?
Click to expand...
Click to collapse
You can try to adb sideload a factory image in TWRP if you have not tried that. Otherwise it's a factory reset.
Seems the flashing of the images did not take or you would not have the 2nd bootloader anymore. So first, check your drivers and make sure they are installed right. Also make sure you have adb.exe and fastboot.exe in the folder you are CD'ing from.
What I would do is download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and CD from inside that folder and push those images. I know that process will/should work.
Double check and make sure you have fastboot communication with your computer fastboot -i 0x1949 getvar
then from inside the folder hold shift and right click on mouse choosing open a command prompt here
Then type these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
LinearEquation said:
You can try to adb sideload a factory image in TWRP if you have not tried that. Otherwise it's a factory reset.
Seems the flashing of the images did not take or you would not have the 2nd bootloader anymore. So first, check your drivers and make sure they are installed right. Also make sure you have adb.exe and fastboot.exe in the folder you are CD'ing from.
What I would do is download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and CD from inside that folder and push those images. I know that process will/should work.
Double check and make sure you have fastboot communication with your computer fastboot -i 0x1949 getvar
then from inside the folder hold shift and right click on mouse choosing open a command prompt here
Then type these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Click to expand...
Click to collapse
I've got the correct drivers. I've had them for a couple of months--they're the ones from @stunts513. And Windows driver enforcement has been disabled for a while now, because signature enforcement is pretty annoying.
And I can't use the system restore tool. The download is just too big. My internet is just one step above dialup, just enough to watch videos on YouTube and "Doctor Who." A 1.1 GB file is just too big, and the script without the images is no longer available.
Still, thank you for responding.
I finally decided to root my daughters KFHD. I said, "Dont worry once Im done and install a custom ROM itll be 10x better than before." She reluctantly said okay only because shes seen me do the same thing to every phone and tablet Ive ever had. I knew from looking around and doing research here on XDA that there was a good chance something could go wrong and I could end up bricking her kindle. Ill cut to the chase.....Something went wrong with the install of the 2nd bootloader/recovery. I ended up with the lovely RSOD. So I proceded to make a fastboot/factory cable. Now Ive gotten rid of the RSOD but the kindle is stuck in bootloop and eventually itll go into the stock recovery saying blah blah blah kindle wont boot. Ive tried the factory reset option to no avail. One thing I find odd is this is the 2nd type of bootloop Ive seen, the 1st one would show the kindle logo for only a few seconds then it would do like the CRT animation does and bootloop from there, now tho, it actually shows the entire bootanimation, I know this because I can see the gradient color change that goes across the kindle fire logo. At this point Ive flashed everything from hashcodes thread, the 7.2.3 bootloader with the freedom 7.4.6 img and the twrp recovery several times. Ive flashed 2.7 and 2.3 recoveries along with a 7.2.3 boot img and 7.2.3 system img together with no luck. So heres where I need someone from within this wonderful open source community to help meh. Gimme a quick rundown of the kindle boot process with the 2nd bootloader including what boots when and where it boots from. Also when using fastboot whats the correct order to flash what? Should I only be trying to flash a recovery now? I shouldnt need to reflash the bootloader right? what about the boot and system img's do I flash those? This is where I need the help. Thanx in advance for taking the time to read my short novel and for helping me. Oh ya Im on linux so i havent been able to use any of the tools that are available for Winblows.
OK, from what I know you didn't install the stack override in the system partition. That's why its bootlooping.
Sent from my GT-i9100 running CM11
Thank you for the reply....after all the reading I've done I was kinda thinking that may be my problem. Is it possible that I did originally push it to my sdcard, then sometime in between then and now I erased it with the fastboot erase data command? There is no way to push anything to sdcard with fastboot, right?
Well from what I can tell the tablet is burnt. I will post pics after I smash it with a hammer and run it over with my car.
Burnt? Nononoo. Don't waste a device that is still "working". It is just bootlooping. Send it to a dev instead of breaking a good device.
No need to do that lol. Get yourself a fastboot cable and use the SRT or KFFA to restore system
Sent from my GT-i9100 running CM11
I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.
DowneyJM said:
I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.
Click to expand...
Click to collapse
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet
SafinWasi said:
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet
Click to expand...
Click to collapse
Thank you for taking the time to help me I really appreciate it.
DowneyJM said:
Thank you for taking the time to help me I really appreciate it.
Click to expand...
Click to collapse
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help
SafinWasi said:
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help
Click to expand...
Click to collapse
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.
DowneyJM said:
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.
Click to expand...
Click to collapse
No problem mate! Trust me,once we're done with it,both you and your daughter are gonna LOVE it.
OK,basically when the tablet turns on,it runs a binary called the u boot. Now this is Amazon stuff and can't be tampered with. But we have the source code due to GPL and what we do know is that a part in the code allows us to flash unsigned third party kernels,therefore a 2nd bootloader. But it can't just be any boot image,it must be patched with the Amazon u boot AND the stack override. Not only that,you must also have installed the stack override in a specific byte address of the system partition. Once we've done that, we can safely flash a recovery and thus,get the ability to install custom ROMs. Oh,another thing. Amazon patched the u boot on versions higher than 7.2.3,so the stack will cause it to crash and show the Red Screen if it's not 7.2.3
Sent from my GT-i9100 running CM11
Hi,
I updated my good old Kindle Fire HD 7 (tate) to cm 12.1 and because of problems with the Play store I made a factory reset. Since then it is in a bootloop showing only the blue teamwin screen with some flickering about every 5-6 seconds.
As I read here (http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html), I need to use fastboot.exe to start a new recovery but... fastboot does not recognize the device.
What is working?
adb status-window shows
...Android Debug Bridge
State: unknown (or recovery)
adb reboot revovery - reboots the device
adb reboot bootloader - reboots the device showing a "fastboot logo"
fastboot devices
< waiting for device > / or just no reaction
fastboot -i 0x1949 getvar product
TATE-PUT-08
Okay, after some research I updated my driver (as seen here http://forum.xda-developers.com/showthread.php?t=2271909) and they seem to be installed properly but nothing changes to the behaviour shown above.
What to do?
And thanks a lot!
My systems: Windows 7 Professional 64 bit or Windows 7 Home Premium 64 Bit
..getting creative, I tried
fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
creating boot image...
creating boot image - 8343552 bytes
downloading 'boot.img'...
OKAY [ 2.817s]
booting...
OKAY [ -0.000s]
finished. total time: 2.817s
..and it reboots into the same teamwin splash screen boot loop
...with adb status-window saying "recovery"
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Same problem! PLEASE HELP!
I'm stuck with THE EXACT same problem.
Please tell me how to go about this step-by-step?
I hope you reply asap..
TIA.
Diplominformatiker said:
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Click to expand...
Click to collapse
can you please do a step by step write-up please?
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Diplominformatiker said:
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Click to expand...
Click to collapse
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
hiii
Same situation , no solution until now
unimoose said:
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
Click to expand...
Click to collapse
In device managment, set to see the hidden devices, must appear as TATE-PVT-8, depending the version of Windows you're using must set the signed drivers to disable.
Then update the driver to tate with this controllers.
And use fatbootmode, can use: KFHD_SRTool_v1.2 to revert to completly stock.
Hopes works for you.
Enomaly said:
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
Click to expand...
Click to collapse
Are you saying that the above mentioned method will not work? So what is the possible solution?