Also stuck here at the KF logo. Awaiting my fastboot cable to arrive. Instructions were followed precariously, to a tee with no errors whatsoever.
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 8.9 [06/24 CM12.1/TWRP 2.8.x]
- Thread starter Hashcode
- Start date
Reflash your stock recovery. The fastboot cable doesn't work on the KFHD89 just use fastboot commands from adb.
I will almost bet your issue is busybox related, the one vital part to getting the recovery.sh command done correctly requires busybox. For some reason binr4y roots okay but I dont believe it installs busybox. I never had any issues after obtianing root and installing gplay busybox was the first thing I installed.
Sorry, I actually have a KFHD7 - the two almost identical posts are confusing. I followed the HD7 instructions, not these ones. But even if I was stuck in the same position on a 8.9, suggesting to use adb when someone is in a bootloop doesn't make sense to me. Can you explain that?
You said you were stuck at the logo technically that`s not a bootloop a bootloop actually is a physical loop from what I have seen. When your flashing a bootloader thats done in fastboot and that is different than adb in fact in fastboot adb is not functional. When your using the wrong instructions and files no wonder you are stuck at the logo. I was talking about busybox Im confused at what that has to do with adb in the first place.
Last edited:
Update TWRP 2.4.2.0
Thank you Hashcode for updating TWRP 2.4.2.0
Anyone who didn't update TWRP can follow the next link (http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.2.0-recovery.img)
Thank you Hashcode for updating TWRP 2.4.2.0
Anyone who didn't update TWRP can follow the next link (http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.2.0-recovery.img)
yes, in fastboot mode, "fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.2.0-recovery.img"
I have read that goo.im was having some trouble the last couple of days. That may be the cause of the trouble you are having.
Okay so, to make sure I understand correctly... The bootloader that comes with the latest update (8.3.0) has been patched, and the original instructions for installing the second bootloader will NOT WORK. And the potential fix for this is to flash a bootloader from a previously unpatched software version?
Are there any indications from the latest update that would suggest this would be dangerous to attempt or are you just being cautious? There seems to have been no real danger in flashing stock images before this. What would cause this situation to be any different? I am more than willing to put this to the test but if you have pertinent information that I'm not aware of, please let me know.
Right now, there is no indication that flashing back the 8.1.4 bootloader will have any adverse affects.
The justification: the MLO.bin (x-loader) component is EXACTLY the same in the 8.3.0 update. The md5sum matches to the file in the 8.1.4 release. This is the binary which loads and validates the bootloader.
I also compared sources from the older u-boot to the new u-boot and there were only 2 changes:
1. The security hole plugged:
Just the order in which the certificate/content is validated. The change was to validate the certificate itself first, then load the boot.img from the mmc and then run a hash check on the contents. Previously, they loaded the boot.img first, then checked the certificate / contents afterwards.
2. The initial charging loop check has some minor delay changes. I think they're allowing another second or 2 for the charger check to make sure there's enough juice to fully boot the device. A minor tweak at best.
The justification: the MLO.bin (x-loader) component is EXACTLY the same in the 8.3.0 update. The md5sum matches to the file in the 8.1.4 release. This is the binary which loads and validates the bootloader.
I also compared sources from the older u-boot to the new u-boot and there were only 2 changes:
1. The security hole plugged:
Just the order in which the certificate/content is validated. The change was to validate the certificate itself first, then load the boot.img from the mmc and then run a hash check on the contents. Previously, they loaded the boot.img first, then checked the certificate / contents afterwards.
2. The initial charging loop check has some minor delay changes. I think they're allowing another second or 2 for the charger check to make sure there's enough juice to fully boot the device. A minor tweak at best.
Good to know. I think I still have a backup of the original bootloader from sometime in early February. I'll flash it later today when I have time and see if all hell breaks loose. Do you happen to have an MD5sum for the old bootloader?
I have a link to the 8.1.4 u-boot (bootloader) file here:
http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
And this is flashed via fastboot with:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Still holding off on an OP update till we get a few confirmations that this works.
http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
md5sum a56f24c0c01aaea4bf408bc710faadaa
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
And this is flashed via fastboot with:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Still holding off on an OP update till we get a few confirmations that this works.
[EDIT:] CONFIRMED: Flashing the kfhd8-u-boot-prod-8.1.4.bin through ADB works just fine. No brick. I get the blue Kindle Fire logo as before after the stack override is installed. TWRP is installed and it works. Currently running CM10.1.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
91Introducing: 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://xdaforums.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:
Take those files and put them somewhere safe.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
**** 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)
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://xdaforums.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)
6Added a stock Amazon OS flash .zip (8.1.4) for use in TWRP here:
http://xdaforums.com/showthread.php?t=2142241
FOR USE ONCE 2ND-BOOTLOADER / TWRP ARE INSTALLED - Stack override file:
New posts
-
Question Do you still need a screen protector, is the 12 a scratch magnet?
- Latest: masondoctorjt
-
-
