Related
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.6.3.0 for the Kindle Fire 2nd GEN
*** 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. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** 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 **
** WHEN MOVING FROM AMAZON OS TO CM10.1 IN TWRP: "WIPE" -> "SYSTEM" AND "FACTORY RESET" TO CLEAR SYSTEM/DATA/CACHE. YOUR APPS FROM AMAZON ICS AREN'T COMPATIBLE. IF NOT YOU'LL LOOP ON THE CM10.1 BOOT ANIMATION **
[03/27] NEW support thread for OFFICIAL CM on the Otter2 (Kindle Fire 2):
http://forum.xda-developers.com/showthread.php?t=2209995
** 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 the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Here's 1 website you can purchase a FASTBOOT adapter from (works with your normal USB cable)
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
** I don't make any commission or fee from the sales of these devices, I just know they have them on stock most of the time and ship in a reasonable time frame unlike the Chinese variants found on ebay.
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for fastboot on your PC before proceeding.
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
INITIAL SETUP INSTRUCTIONS (1st TIME ONLY) FOR 2ND-BOOTLOADER + TeamWinRecoveryProject INSTALL:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
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.
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and CM10.1:
Stack override file:
http://goo.im/devs/Hashcode/otter2/stack
[12/09] otter2-freedom-boot-10.4.6.img (USED ONLY THE FIRST TIME -- .zip files will have their own boot.img's from now on):
http://goo.im/devs/Hashcode/otter2/otter2-freedom-boot-10.4.6.img
md5sum: 80f9b9ba80910de361463560f86f315a
[09/03] TeamWin Recovery 2.6.3.0:
http://goo.im/devs/Hashcode/otter2/otter2-twrp-2.6.3.0-recovery.img
md5sum: a66a8cbab92fd5daaa85f6303e9cc0c3
older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check the MD5SUM before using fastboot -- downloads CAN be corrupted)
CM-10.1/CM-10.2 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the version: CM10.1 or CM10.2)
Place the 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"
[ Connect fastboot cable, and reboot the device so that "Fastboot" is showing ]
STEP 4.
Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery.[/B]
*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 bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1/CM-10.2 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1 OR DOWNLOAD NEW ONES FROM THE RECOVERY THREAD HERE: **
http://forum.xda-developers.com/showthread.php?t=2035047
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
Enjoy
THANKS TO:
fattire for finding the original bootloader exploit
TESTERS: powerpoint45 and FMKilo
Changelog: updated 2013-07-08
freedom boot.img (for use w/ stock Amazon OS + 2nd-bootloader):
[07/08] Updated w/ kernel from 10.4.3 release
TeamWin Recovery (TWRP) 2.6.0.0
[07/08] USB Vendor ID / Product ID in recovery now matches stock Amazon OS
[07/08] Based on 10.4.3 stock kernel
[07/08] Fixed recovery bootloop issue
[07/08] TWRP 2.6.0.0 update
one more reserved space
no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?
Hondologe said:
no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?
Click to expand...
Click to collapse
Yes, this would work, however if something goes wrong (and it frequently can during early development) you will have NO WAY of recovering the device without a fastboot cable. So I don't recommend this method currently.
Also, these instructions are BRAND NEW, and I understand if you really want to get this setup, but please let some users w/ fastboot cables run through the instructions to make sure I didn't typo something, etc.
Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I`m gonna try it later WITHoUT FB cable . If it fails i just have to wait a couple of days, so its worth it if i get CM onto my kindle
BTW If it fails, im gonna blame it on you (Just kidding...)
Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?
powerpoint45 said:
Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?
Click to expand...
Click to collapse
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.
Hashcode said:
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.
Click to expand...
Click to collapse
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet
i just ordered my factory cable... thanks hashcode and powerpoint45!
powerpoint45 said:
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet
Click to expand...
Click to collapse
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.
Hashcode said:
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.
Click to expand...
Click to collapse
OK. I will when I get home so I can check md5. Any ideas to fix ducati?
powerpoint45 said:
OK. I will when I get home so I can check md5. Any ideas to fix ducati?
Click to expand...
Click to collapse
If someone has the time to do a video guide for this that would be great.
Congrats!
(that's all I got)
Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!
Jowyn said:
Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!
Click to expand...
Click to collapse
You will probably need to install the Android SDK to get the fastboot command.
Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
And all the image files that need to be flashed via fastboot need to reside where fastboot.exe is just to clarify.
Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
If you follow the noob guide on rooting the kindle fire 2 it tells you to download two files, inside of either of those two files is adb and fastboot as well as all the needed drivers, if you place the files needed to do this process inside of either of those folders holding down control while right clicking inside of the folder ( making sure nothing is highlighte) select open command prompt here, that way you should be able to do this process without the sdk
Let me know how it turns out and hopefully that will save some people the headache of getting their environmental variables set up correctly ( my computer likes to play stupid )
and nobody mentioned me.. come on, I thought I was listed in credits as moral support, and kid who flashed without a fbcable.. I know how to do it, and you could too if you just read up enough on idme and bootmodes..
No more from me, I don't want to be the one who is in trouble for bricked non factory cable owning users..
Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD
I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.
I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.
probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP
htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)
thanx again..
ahahahha...what a beautifullll day....
skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???
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
I wanted to install Gapps to my Kindle since many of the apps including the web browser are coming up as unsupported. I have rooted my Kindle Fire HD 8.9 and installed TWRP. When I rebooted my kindle to enter the recover mode, it got stuck at logo screen.
At first, when it was logo was flashing if I plugged it in, ubuntu give an error message "unable to mount Jem PVT Prod 04". I discovered that holding the volume up button made the screen go blank but not off. You can plug the kindle in and Ubuntu will recognize the kindle and allow you to access the internal storage.
How can I fix and reboot the Kindle from Ubuntu?
I researched tons of solutions but most of them require Windows which I don't run or I tried the instruction and they don't work or our incomplete.
I received a fastboot cable from Amazon today. I'll see how it works. Any advice would be appreciated.
Okay, I fixed the problem with the Fastboot Cable. Here's the steps that I did to fix it. It was loading Twrp or the bootloader so I reinstall them. I have Android SDK on my computer and my Kindle is rooted.
Step 1.
The correct twrp was difficult to find. This forum offered a site to go to but I found the site was corrupted and the website was trying to download a virus.
I found the twrp and bootload file here.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet/
I placed the files in my android/sdk/platform-tools. (kfhd8-freedom-boot-8.4.3.img & kfhd8-twrp-2.6.0.0-recovery.img)
I typed into terminal "fastboot -i 0x1949 getvar product" without parenthesis. At the waiting for device command, I plugged in the Kindle with the Fastboot cable and held the Volume up button to go into fastboot mode.
I opened the android/sdk/platform-tools and right click the mouse and hit open in terminal
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
From the reboot, hit the volume up to get into twrp.
At this point, I still could go into the kindle so I thought the operating system may be corrupted.
Step 2
In twrp, I backed up the system. and rebooted into twrp.
In twrp, I hit wipe and rebooted back into twrp.
I downloaded CyanogenMod and Gapps to my platform-tools folder again.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet
Step 3
I couldn't access the internal drive so I used ADB to put the files on my kindle.
Here's a video of the instructions I used.
youtu.be/NaK5OxUeDKM
Open the support document for Ubuntu instructions.
First, open terminal in the Platform Tools file and type ADB Devices. When I pushed the two files, his instructions say to use command sudo ./adb-linux push filename /sdcard/. This didn't work. I used "./adb push [filename /sdcard/." without the quotes and it worked.
Step 4
Enter twrp and install the CyanogenMod and Gapps. Reboot
This got my operating system up and running perfectly.
Now bad for a complete Noob.