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.
Related
Well guys there are over 9000 threads here on how to root the Nexus 4.
I thought I'd make one thread that says all this in simple English and makes it quick and simple for everybody.
CREDITS:
1wayjonny - Universal Naked Driver
Koushik Dutta (koush) - CWM
Chainfire - SuperSU
HQRaja - SU & Busybox package
Click to expand...
Click to collapse
DISCLAIMER:
UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. Therefore I HIGHLY suggest you do this before you start setting up the phone/installing apps so that you don't have to redo/reinstall much.
You can re-lock and unroot the phone, but I am still going to say that this voids the warranty.
I am not responsible for what you do to your device. This is for reference only.
Please follow each step carefully (ESPECIALLY make sure to read the part before step 14 VERY CAREFULLY.)
The CWM recovery may not be 100% functional yet, but you can install zips/roms and do backups for sure.
STEPS:
1 - Download this file and unzip it to C:\Nexus4
2 - Open a command prompt (On windows vista/7, go to Start menu and type cmd and press enter. On XP & below, go to Start > Run and type cmd and press enter.)
3 - In the command propmpt, run
Code:
cd C:\Nexus4 <press enter>
4 - On the phone, go to Settings > About phone. In the About phone menu, scroll down to "build number" and tap it until it says "You are now a Developer!"
5 - Go back to the main settings menu, and the Developer options tab should now be visible. Open that tab.
6 - In the Developer options menu, check USB debugging and Stay awake.
7 - Install the driver from here.
8 - Connect the device via USB.
9 - In the command prompt, run the command
Code:
adb devices <press enter>
and your serial number should pop up. If not, try unplugging the device, reinstalling the drivers, rebooting PC, and then retry.
10 - Now run the command
Code:
adb push SUBusybox.zip /sdcard/SUbusybox.zip <press enter>
It should say something like "XXXX KB/s (1191942 bytes in X.XXXs)"
11- If it said that, run the command
Code:
adb reboot-bootloader <press enter>
12 - The phone will show up in the bootloader. Now run the command
Code:
fastboot devices <press enter>
and your serial number should pop up.
13 - If your serial number popped up, run the command
Code:
fastboot oem unlock
and your phone will ask you if you want to unlock. Select yes with the volume buttons and press power.
13 - Your phone will go back to the bootloader screen, and at the bottom it will now say LOCK STATE - unlocked
****DO WHAT IS BETWEEN THESE RED DIVIDERS IF AND ONLY IF YOU WANT OTA UPDATES TO STILL WORK. IF YOU DON'T CARE, CONTINUE ON STEP 14 BELOW THE DIVIDERS.****
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
Run
Code:
fastboot boot CWMrecovery.img <press enter>
and it should say something like
Code:
downloading 'boot.img'... OKAY [ X.XXXs]
booting... OKAY [ X.XXXs]
and your phone will boot into CWM recovery.
NOW SKIP TO STEP 17. ON STEP 18 IF IT ASKS YOU TO DISABLE RECOVERY OVERWRITE, TAP NO. STEP 19 SAYS YOU WILL HAVE CWM INSTALLED. YOU WON'T.
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
14 - Now run the command
Code:
fastboot flash recovery CWMrecovery.img <press enter>
and it should say something like
Code:
sending 'recovery' (7754 KB)... OKAY [ X.XXXs]
writing 'recovery'... OKAY [ X.XXXs]
15 - If it said OKAY twice, then press the volume down key on the phone twice and it will say Recovery mode. Press the power key.
16 - Once in recovery mode, run the commands
Code:
adb shell mount system <press enter>
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak <press enter>
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak <press enter>
adb shell umount system <press enter>
the command prompt will say nothing back to you if there were no errors.
17 - On the phone, tap install zip from sdcard (NOT INSTALL ZIP FROM SIDELOAD), then tap choose zip from sdcard. Tap 0/. Now scroll down to SUBusybox.zip and tap it. Tap yes. It will then install.
18 - Now tap Go Back and then tap reboot system now. If it asks you to disable recovery overwrite tap yes.
19 - Once the phone boots back up it will be fully wiped and you will be rooted with CWM, SuperSU, and busybox installed
Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk
jimmyz said:
Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
It didn't work for me, so I put adb commands in there to do it manually just in case.
Sent from my Nexus 4 using Tapatalk 2
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.
Welcome to Flashe!:victory:
Flashe is basically an all-in-one installer which only requires a few clicks and you are root,unlocked(bootloader), and you can choose a recovery to install in the process. This is much easier than using ADB commands or fastboot.:good:
The program does included a feature that allows you to use a custom boot image and get rid of the "unlocked bootloader" screen.
WARNING: USE AT YOUR OWN RISK
Requirements:
-Atrix HD,Razr HD,Razr MAXX
- .bin logo file(rename to logo when put in flashe folder)
- .iso for your recovery(CWM,TWRP, or Philz)
Future Update:
-Downloads the required files from a server
-Menu(choose to install other things
-GUI, instead of text there is a actual button interface.
Errors:
You MUST allow the program to boot you into recovery otherwise the custom recovery is lost due to the android os overwriting it. If you have any other errors pm
me!
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Enjoy!
Alienware258 said:
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Click to expand...
Click to collapse
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I totally agree
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I looked at the threat, and it calls it a threat because it is a rooting tool.
Also,When I first started rooting I did not get how to use it at all(Mythtools).Instead I used programs on my android.So I made this to help new users coming to the atrix community once I finished learning ADB commands and some fastboot commands.
Here is the source:
Code:
adb kill-server
adb wait-for-device
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
adb reboot
adb wait-for-device
adb push unlock /data/local/tmp
adb shell chmod 755 /data/local/tmp/unlock
adb shell su -c /data/local/tmp/unlock
adb shell rm /data/local/tmp/unlock
adb reboot bootloader
fastboot getvar all
fastboot continue
adb wait-for-device
adb reboot bootloader
echo [-] To continue you will need a boot file which will
echo [-] replace the "Unlocked Bootloader" image. Name it:
echo [-] logo.bin
echo [-] Continue when you are in the bootloader and have the file.
pause
fastboot flash logo logo.bin
fastboot continue
echo [-] Processe complete!
echo [-] -Root installed
echo [-] -Bootloader unlocked
echo [-] ---------------------
echo [-] This next step will install a recovery.
echo [-] Recovery will allow you to install your own roms,etc(depending on the selected recovery)
echo [-] Rename your recovery image "rec" so it should be 'rec.img' then continue.
pause
adb reboot bootloader
echo [-] Continue once in bootloader
pause
fastboot devices
fastboot flash recovery rec.img
echo [-] Once finished flashing continue...
pause
adb reboot recovery
echo [-] Complete! You now should have recovery installed. Enjoy!
pause
READ THIIS!
*this thread is for desire 510. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or unlocked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
*i have tested this on my gsm cricket desire 510 variant(a11_ul). let me know if you try it on a different variant,or if youd like to dump partitions and have me take a look
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
remove your tampered banner: http://forum.xda-developers.com/desire-510/general/how-to-remove-tampered-banner-t3179866
mine too
Can fastboot be used to fully restore stock everything? Bootloader, Recovery, FireOS.
I tried to use Kingroot on my Kindle Fire HD 7" 3rd gen (Soho) and it softbricked it. I can't get past the white n orange "Kindle fire" logo screen.
I've tried the directions for putting twrp on and such but I still can't get past the logo. I followed the directions for restore on the TWRP Page but once I get to the last part right after the sideloading of the update.bin file I cant get past the logo screen.
adb sideload update.bin
adb reboot
THIS IS WHERE I CANT GET PAST. It stalls at the logo screen.
adb wait-for-device
adb shell su -c 'mount -o remount,rw /system && rm /system/etc/install-recovery.sh && mount -o remount,ro /system'
adb push recovery.img /sdcard/recovery.img
adb shell su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/omaphsmmc.1/by-name/recovery"
adb push exploit.img /sdcard/exploit.img
adb shell su -c "dd if=/sdcard/exploit.img of=/dev/block/platform/omaphsmmc.1/by-name/exploit"
adb shell rm /sdcard/recovery.img /sdcard/exploit.img
@spudowiar I know this device is really old and its likely youve forgotten how to do some things but I really need help with this. The directions on the TWRP page arent working, or well, they work but its not working. I have tried to sideload the latest amazon update file as update.bin, update.bin.zip, and update.zip. None of them work or it seems. After the sideload of the update and SuperSU I reboot the device and then it goes to the faint white kindle logo then the kindle fire logo in white and orange with the glimmer scrolling across the screen. Thats where it stops. I have left it on this screen for 2 hours or so and no change. I am at a loss of what to do to restore this device to working condition now.
cc: @sd_shadow