Database Develop

[Q] kindle fire Hd 7

I recently purchased a kindle fire hd 7 version 7.3.1 which i am looking to install cm10.1 on. i have read through many threads and have download all the needed files to undertake this project. the only problem that i have encountered which proves to be very troublesome is loading my kindle into fastboot mode. can any one help me with this problem? thank you.

Why are u trying to get into fast boot mode? You should only need adb to back it up then use fire flash to put 2nd bootloader and twrp on it, then transfer over the cm 10.1 images for flashing from twrp. That's it in a nutshell. Fast boot it only for if you brick it in the process, which in most cases you will need a factory cable to get it into fast boot mode.
To be more specific about this read seokhuns awesome guide, but follow it to the tee or u may get a red screen on your bootloader to which you will need a factory cable to fix.
http://forum.xda-developers.com/showthread.php?t=2271909
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why are u trying to get into fast boot mode? You should only need adb to back it up then use fire flash to put 2nd bootloader and twrp on it, then transfer over the cm 10.1 images for flashing from twrp. That's it in a nutshell. Fast boot it only for if you brick it in the process, which in most cases you will need a factory cable to get it into fast boot mode.
To be more specific about this read seokhuns awesome guide, but follow it to the tee or u may get a red screen on your bootloader to which you will need a factory cable to fix.
http://forum.xda-developers.com/showthread.php?t=2271909
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you. i have done some reading and it says that fire flash supports 7.3.0 but i am running 7.3.1 ... will this work properly or will it brick my device?

kodie. said:
thank you. i have done some reading and it says that fire flash supports 7.3.0 but i am running 7.3.1 ... will this work properly or will it brick my device?
Click to expand...
Click to collapse
i did take the risk and try it and it did work twrp in successfully installed now im trying to install cm10.1 after i wipe the system, factory reset cache, Dalvik cache and proceed to installing cm10.1 it says failed.. can you help me? thanks

After u have the zip file on your sdcard I suggest using es file explorer to check the files properties and calculate its md5sum and compare it to the md5sum on the download link. If they match up then it should be working, if not it just didn't probably transfer or DL right.
U will probably need to flash a modded stock image of kindle os if you didn't back up your os first, so your kindle has an os to boot into. By modded stock image I mean that on the kindle android development forums there are a few modded stocks that come rooted without reflashing the stock boot loader and recovery plus have ota disabled. Makes things easier so you don't need to reflash the boot loader and twrp and reroot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
After u have the zip file on your sdcard I suggest using es file explorer to check the files properties and calculate its md5sum and compare it to the md5sum on the download link. If they match up then it should be working, if not it just didn't probably transfer or DL right.
U will probably need to flash a modded stock image of kindle os if you didn't back up your os first, so your kindle has an os to boot into. By modded stock image I mean that on the kindle android development forums there are a few modded stocks that come rooted without reflashing the stock boot loader and recovery plus have ota disabled. Makes things easier so you don't need to reflash the boot loader and twrp and reroot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks kindle fire up and running cm10.1 and google appps .. i change my usb cable and re downloaded the files and then it worked

Many work with cm10.1 kfhd7 of Hashcode .

I installed 2nd bootloader on 7.3.1 but I forgot to disable auto-updates and I woke up to 7.4.3 and lost root and 2nd boot. I managed to root It again but i'm kinda scared to install the bootloader. I think I'm gonna wait until someone verifies and it's ok.

Bootloop After Flashing Freedom Bootloader

I'm on version 7.4.6 and I flashed the 7.2.3 bootloader, followed by the Freedom Boot 7.4.3 and TWRP 2.6.0.0 - Followed instructions to the T in HashCode's how-to thread. I ended up in a constant reboot to TWRP. I restored back to the images I made in fastboot without a hitch, and now I'm left wondering what could have happened. Any ideas? I did apply the override stack and all of those other things mentioned beforehand.

Well I think I read something about the latest os detecting twrp and not wanting to let you boot I to it but I am not positive if that's what happened.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

For some reason, it appears that the device disagrees to boot onto the stock ROM after you flash a custom recovery (As you said above). My solution was simply to flash a ROM
I'm left feeling kind of dumb for posting this thread haha

I'm starting to wonder if they are must wanting us to brick our kindles at this point, I mean having twrp doesn't mean that we are definitely going to flash a custom ROM, it could mean we want to have insurance against a brick by making a backup, don't know why they see the need to not boot up if we have twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Well I think I read something about the latest os detecting twrp and not wanting to let you boot I to it but I am not positive if that's what happened.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I believe the existence of Kinology should pretty much disprove this theory.

[Q] Seeking Amazon Stock OS for Kindle Fire HD 7" 7.4.6-7 for TWRP

Need Amazon Stock OS for Kindle Fire HD 7" 7.4.6 or 7.4.7, for TWRP (zip). It would be wonderful if the firmware will be with root access and Fix wallpaper. Tnx. :good:

Well the latest version hasn't been released for twrp yet, by new I mean 7.4.7. I can see a reason why 7.4.6 went released,, but its doable atleast. The boot loader has to be updated on every amazon update or it will boot loop into recovery. There happens to be a 7.4.6 freedom boot IMG available in kinology's zip for flashing, but the latest official update hasn't been zipped for twrp with that freedom boot. You could update your is manually, reroot it, apply wallpaper fix, and disable ota's and dd and image and upload it somewhere and I could put together a system update for that or someone else could, but other wise you have to use an older version.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Amazon 7.4.6 OS.zip
stunts513 said:
Well the latest version hasn't been released for twrp yet, by new I mean 7.4.7. I can see a reason why 7.4.6 went released,, but its doable atleast. The boot loader has to be updated on every amazon update or it will boot loop into recovery. There happens to be a 7.4.6 freedom boot IMG available in kinology's zip for flashing, but the latest official update hasn't been zipped for twrp with that freedom boot. You could update your is manually, reroot it, apply wallpaper fix, and disable ota's and dd and image and upload it somewhere and I could put together a system update for that or someone else could, but other wise you have to use an older version.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunts: What do you need to create a zipped 7.4.6 or 8.4.6 OS.zip file that is pre-rooted, OTA block applied that does not flash the bootloader,anr or recovery just like the Hashcode X.4.3 versions?
It might be handy to be able to flash back to the Kindle OS and be at the latest version rather than a couple of versions behind.
I received a tablet from Amazon last week that was 8.4.5 so, there appears to be more than just 8.4.3 and 8.4.6.
I can upload the images that are needed to you and or, you could post how to do this?
I am presuming you need the X.46 freedom boot.img, bootloader, and, system.img files?
Questions: Don't feel obligated to answer...
I have always been confused about how 2nd bootloader works.
Once 2nd boot loader is installed, you can then install a custom ROM which replaces much of what was done to get 2nd boot?
When you install a custom ROM, what images from the 2ndboot install are left on the tablet or included with the custom ROM?
For the 2nd boot install, TWRP recovery, old bootloader and, modified boot image is installed then stack override is pushed to the system image ( read from an old Hashcode post).
However, once the custom ROM is installed, the boot image and the system image at least have been replaced so what happened to the original boot image and stack override?
Does the stack override stay in the ROM system image?
Does the boot image included in the custom ROM include the freedom boot modifications?
It does not look like the bootloader image is part of a custom ROM?
Regards

galearned said:
Stunts: What do you need to create a zipped 7.4.6 or 8.4.6 OS.zip file that is pre-rooted, OTA block applied that does not flash the bootloader,anr or recovery just like the Hashcode X.4.3 versions?
It might be handy to be able to flash back to the Kindle OS and be at the latest version rather than a couple of versions behind.
I received a tablet from Amazon last week that was 8.4.5 so, there appears to be more than just 8.4.3 and 8.4.6.
I can upload the images that are needed to you and or, you could post how to do this?
I am presuming you need the X.46 freedom boot.img, bootloader, and, system.img files?
Questions: Don't feel obligated to answer...
I have always been confused about how 2nd bootloader works.
Once 2nd boot loader is installed, you can then install a custom ROM which replaces much of what was done to get 2nd boot?
When you install a custom ROM, what images from the 2ndboot install are left on the tablet or included with the custom ROM?
For the 2nd boot install, TWRP recovery, old bootloader and, modified boot image is installed then stack override is pushed to the system image ( read from an old Hashcode post).
However, once the custom ROM is installed, the boot image and the system image at least have been replaced so what happened to the original boot image and stack override?
Does the stack override stay in the ROM system image?
Does the boot image included in the custom ROM include the freedom boot modifications?
It does not look like the bootloader image is part of a custom ROM?
Regards
Click to expand...
Click to collapse
I started pre-rooting the update file for 7.4.6, as well as adding some essential features such as voice search, live wallpapers picker, the stock Android browser, OTA disabled, etc, but I could never get it to properly boot. It would just send me back into TWRP no matter how I adjusted it or recompiled it.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

galearned said:
Stunts: What do you need to create a zipped 7.4.6 or 8.4.6 OS.zip file that is pre-rooted, OTA block applied that does not flash the bootloader,anr or recovery just like the Hashcode X.4.3 versions?
It might be handy to be able to flash back to the Kindle OS and be at the latest version rather than a couple of versions behind.
I received a tablet from Amazon last week that was 8.4.5 so, there appears to be more than just 8.4.3 and 8.4.6.
I can upload the images that are needed to you and or, you could post how to do this?
I am presuming you need the X.46 freedom boot.img, bootloader, and, system.img files?
Questions: Don't feel obligated to answer...
I have always been confused about how 2nd bootloader works.
Once 2nd boot loader is installed, you can then install a custom ROM which replaces much of what was done to get 2nd boot?
When you install a custom ROM, what images from the 2ndboot install are left on the tablet or included with the custom ROM?
For the 2nd boot install, TWRP recovery, old bootloader and, modified boot image is installed then stack override is pushed to the system image ( read from an old Hashcode post).
However, once the custom ROM is installed, the boot image and the system image at least have been replaced so what happened to the original boot image and stack override?
Does the stack override stay in the ROM system image?
Does the boot image included in the custom ROM include the freedom boot modifications?
It does not look like the bootloader image is part of a custom ROM?
Regards
Click to expand...
Click to collapse
Long story short the custom recovery, and the old bootloader stay the same, technically while the stack override looks like it does, it doesnt, the stack override is reapplied everytime a rom is flashed, its in the update-tools script in the rom, i found this out the hardway while porting b2g. As far as i know the 2nd bootloader is basically added to the kernel, so when we reflash a new rom with its own boot.img it would have to have 2nd bootloader in it, least thats how i'm seeing it if i remember right.
Now for the first part of the question, normally i would dd it, but since your making a rom i guess you would prefer the standard flashing format thats a pita to do... I think titanium backup has a flashable zip generator that makes a zip out of your own system image, though i think its in the paid version. If thats the case you could simply modify the os how you want it with root and such and such system apps and disable OTAs, then make a flashable zip, but you will need to make sure to add the stack overide part to the script so it doesnt hang on the bootloader. If you understand update-tools scripting style you should be able to pick the section out you need, if not i can just post it. Just look at the update-tools script in a cm11 zip file and you should ge tthe idea. its in the meta/google/android folder if i remeber right.

stunts513 said:
Long story short the custom recovery, and the old bootloader stay the same, technically while the stack override looks like it does, it doesnt, the stack override is reapplied everytime a rom is flashed, its in the update-tools script in the rom, i found this out the hardway while porting b2g. As far as i know the 2nd bootloader is basically added to the kernel, so when we reflash a new rom with its own boot.img it would have to have 2nd bootloader in it, least thats how i'm seeing it if i remember right.
Now for the first part of the question, normally i would dd it, but since your making a rom i guess you would prefer the standard flashing format thats a pita to do... I think titanium backup has a flashable zip generator that makes a zip out of your own system image, though i think its in the paid version. If thats the case you could simply modify the os how you want it with root and such and such system apps and disable OTAs, then make a flashable zip, but you will need to make sure to add the stack overide part to the script so it doesnt hang on the bootloader. If you understand update-tools scripting style you should be able to pick the section out you need, if not i can just post it. Just look at the update-tools script in a cm11 zip file and you should ge tthe idea. its in the meta/google/android folder if i remember right.
Click to expand...
Click to collapse
Thanks Stunts: I will look at the tools and cm11.zip for some details. I should learn how to remake these things but, not knowing fully about the signed partition pitfalls, I really would be hesitant to try it. It seems that unzipping, modifying and then rezipping would be risky when there has been so much said about the Kindle images being signed? How do they get resigned if not by Amazon?
I am not actually making a rom.
I do a lot of converting tablets back and forth between Kindle OS and other custom ROMs (mostly CM roms) and to do that, I often need to flash the Kindle OS to get back. If for instance I want to change a tablet back to Kindle, I need to flash X.743, then do an update to get to X.46.
If the X.46 was done up as a zip, my work would be cut in half.
Additionally, I need to be aware of which Freedom boot is running when I am flashing partitions.
If I could stay at X.46, it would avoid a lot of hassles.
I was asking for the X.46 zip as much for the xda audience at large as myself.
If you are running the Kindle OS with root and 2nd boot loader and happen to mess up the tablet, it would be nice to flash it back but, you end up a version or two behind and still need to then do an update. The alternative is to flash individual partitions using fastboot but, flashing in recovery is much quicker and safer.
Regards

galearned said:
Thanks Stunts: I will look at the tools and cm11.zip for some details. I should learn how to remake these things but, not knowing fully about the signed partition pitfalls, I really would be hesitant to try it. It seems that unzipping, modifying and then rezipping would be risky when there has been so much said about the Kindle images being signed? How do they get resigned if not by Amazon?
I am not actually making a rom.
I do a lot of converting tablets back and forth between Kindle OS and other custom ROMs (mostly CM roms) and to do that, I often need to flash the Kindle OS to get back. If for instance I want to change a tablet back to Kindle, I need to flash X.743, then do an update to get to X.46.
If the X.46 was done up as a zip, my work would be cut in half.
Additionally, I need to be aware of which Freedom boot is running when I am flashing partitions.
If I could stay at X.46, it would avoid a lot of hassles.
I was asking for the X.46 zip as much for the xda audience at large as myself.
If you are running the Kindle OS with root and 2nd boot loader and happen to mess up the tablet, it would be nice to flash it back but, you end up a version or two behind and still need to then do an update. The alternative is to flash individual partitions using fastboot but, flashing in recovery is much quicker and safer.
Regards
Click to expand...
Click to collapse
I would disregard the signing in this instance, the signature on the zip file is only really used for checking its integrity as untampered with by otas and such, the only thing that has to be signed is the bootloader and technically the boot.img but thats only when you don't have 2nd bootloader installed. If you are unaware of what fredomboot you have just flash the latest one on top of it i suppose, or one equivelent to that verison of the os. All in all if you mess up any signing in the rom the worst thats going to happen is twrp erroring out telling you the signature isnt valid, might only be a warning though, and theres a way to bypass it in twrp if i remeber right. Thats why i always resign my builds of b2g manually after adding the data folder.

[Q] Trying to downgrade

Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.

Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.

Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app

cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app

Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.

LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.

Did you try downloading the original 7.2.3 from the thread and try flashing them ?

Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!

cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.

I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.

greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!

[Q&A] [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWR

[Q&A] [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWR
Q&A for [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWRP 2.7.x.x]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWRP 2.7.x.x]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Do I have to install the CM 11?

stuck after TWRP
I've run into a wall. I can get the Kindle to boot with stock OS with TWRP 1.7.0.0 installed but when I try to flash CM11 and GAPPS the kindle crashes. It will boot with the blue logo, then 1 of 2 things happen. Either in just hangs indefinately or after about 2-3 minutes the screen turns to "snow". When i reboot into TWRP, I find that all my data is gone. I flashed the system.img with the stock img and upon booting it says data corrupt and the kindle doesn't respond to adb. I then fastboot with the Skorpn cable, reflash the boot, recovery, system images, and i will go into a bootloop (stock logo, screenflash, stock logo, screen flash, and so on). So I then go through the steps of http://forum.xda-developers.com/showthread.php?t=2128848 by flashing u-boot-prod-7.2.3, freedom-boot-7.2.3, twrp-2.7.0.0. And then i believe I reflashed the stock boot, recovery, system images again which got me back to booting up into stock os (no blue logo when booting). I have gone through this process a few times with minor tweaks like going through the steps of the above thread using freedom-boot-7.4.6, and trying the freedom-boot and twrp-2.3.3.0 that came with KFFirstAide. All to no avail, and I go throught the long and seemingly redundant steps to get back to 7.2.3 stock-ish.
More background info if it helps:
I have the kindle fire HD 7" tate. It is rooted, and currently running on 7.2.3 (downgraded from 7.5.1). The boot, recovery, and system images i'm using came from the KFHD_SRT_v1.3.0 download.
When I try to flash the TWRP-2.3.3.0 that came with KFF, I can't seem to boot into the TWRP interface.
The CM version i've been trying is cm-11-20150112-NIGHTLY-tate with gapps-kk-20140105-signed. This is the step that kills my kindle.
According to TitaniumBackupPro I have only 43.1MB free in system ROM which may be an issue. I believe the low ROM space attributed to issues I had earlier in trying to downgrade via the KFF application. The script would error when trying to flash the images saying something of a max download size and would not flash. I was able to manually flash SRT v1.3.0 images via fastboot commands.
All help would be much appreciated. If there is any other info you need, I will be sure to do my best in providing it. I like tinkering, but am the type of person who learns by screwing things up haha.
EDIT: Also another thing that I have noticed when i get to the step just before trying to install cm11. When starting the kindle up after flashing u-boot.bin, freedom-7.2.3, TWRP-2.7.0.0... When i boot, the starting fire logo starts orange, goes blue, then turns orange again. I can enter TWRP from boot with the vol down button, and stock OS runs fine. I don't know if the orange > blue > orange is common or an indicator of anything. Downloading the newer cm-11-20140606 now and I am probably going to give that a go soon. Fingers crossed.

Kindle Fire "Tate" 2nd Bootloader plus TWRP issues
Hello,
first post, so i'll shoot away instantly I'm about to proceed with 2nd bootloader install (freedom boot) and TWRP. But: The files in user Hashcode's original post seem to be gone. Anyone ideas? Which leads to my second question: I'm on system version 7.4.5. - is it ok to use the 7.4.6 freedom bootloader, or should I do something different?
Thanks, much appreciated!

I have a similar question to the post above.
I have all the files needed to install the 2nd bootloader on 7.4.6, but my kindle is on 7.2.3 (rooted). Goo.im is down so i have no access to any of Hashcodes other files, i cant find a 7.2.3 freedom image.
If i were to go ahead and install (via fireflash) the 2nd bootloader with 7.4.6 files on my 7.2.3 kindle, i assume that it will not boot, but will twrp be installed properly?? If it does, i can forego booting into stock and go straight to installing a custom rom.

Jaa-Yoo said:
I have a similar question to the post above.
I have all the files needed to install the 2nd bootloader on 7.4.6, but my kindle is on 7.2.3 (rooted). Goo.im is down so i have no access to any of Hashcodes other files, i cant find a 7.2.3 freedom image.
If i were to go ahead and install (via fireflash) the 2nd bootloader with 7.4.6 files on my 7.2.3 kindle, i assume that it will not boot, but will twrp be installed properly?? If it does, i can forego booting into stock and go straight to installing a custom rom.
Click to expand...
Click to collapse
in the meantime, a member in the main thread posted files, which are 7.4.6 freedom boot and twrp 2.8.something. i just took these 2 files and flashed them right away via fireflash 1.1. after that flashing the latest CM11 nightly build was a normal go, without any issues. google apps can be flashed too, all at once out from TWRP. I read here, that your original system version should be equal OR lower than the version of freedom boot. Again as always: your choice, your responsibility

Thanks, i went ahead with installing the 2nd bootloader along with twrp. Rebooted into recovery and installed cm11, all went well.

2nd-bootloader for Custom ROMs on KFireHD 7" - Goo.im File Missing
Thank you only1kowalski and Jaa-Yoo

Jaa-Yoo said:
Thanks, i went ahead with installing the 2nd bootloader along with twrp. Rebooted into recovery and installed cm11, all went well.
Click to expand...
Click to collapse
no probs
---------- Post added at 08:37 AM ---------- Previous post was at 08:28 AM ----------
N3OMOD said:
Thank you only1kowalski and Jaa-Yoo
Click to expand...
Click to collapse
Did it work for you, as well? Glad to hear! If I'm correct, there may be issues, if the original system version on the KFHD7 is higher than the freedom boot one. Again, I also read somewhere here on the site, that somebody was successful in flashing with a lower version of the 2nd bootloader.

I've managed to successfully downgrade from OS 7.5.1 to OS 7.2.3 on a Kindle Fire HD 7" (2012 edition) prior to installing CM 11 with the following files:
kfhd7-freedom-boot-7.4.6.img
kfhd7-twrp-2.8.3.0-recovery.img
kfhd7-u-boot-prod-7.2.3.bin
fireflash11.apk
Just one side-note: TWRP 2.8.3.0 has a minor "graphical glich" on boot leading to grey area above the KindleFire logo (the blue one to be exact, the one leading to recovery) which appears for a few seconds before the device actually enters the TWRP. After that everything works correctly, but at first boot one might get "scared" by this thing.
Also please consider that after installing TWRP for the first time the loading time is significantly higher than what described on tutorials: my device took 9 minutes to first-boot into TWRP. But again, this happens only on first time.

Fine it worked out for you. BTW, I got this strange glitch at startup as well, when booting into TWRP. At first, I thought to myself "nice buddy, 1st brick". But then again, it would be intrresting to know what is causing this. Maybe the different system version to the freedom boot version?

only1kowalski said:
At first, I thought to myself "nice buddy, 1st brick".
Click to expand...
Click to collapse
This was exactly my first thought too! But luckly everything went well.
I suppose this may be due to the new version of TWRP or, ad you suggested, to the different freedom bot. Apart from being fastidious tough it did not compromise the functionality.
It would be nice to find the previous version of freedom bot just to verify if the problem was still present.

yeah, you're right. but since the site hosting these files is seemingly down and will be from what i can see, we might not get a hand on this so quick. nevertheless, the kfhd7 runs like an arrow with this os and i'm glad i did the switch from its original os. kudos to the developer(s) !

I've had my kfhd 7 for a few years. It is a tate device and rooted already, version shows 7.2.3. I've finally decided to install a custom rom but discovered goo.im is down and I can't get the kfhd7-u-boot-prod-7.2.3.bin file. Based on prior device modding experience I'm assuming this is meant to downgrade higher version software to this point in order to install twrp. Is that correct? Do I not need that file since I"m already on 7.2.3?
edit: looked through Q&A and found my answer. I should probably get better at using xda...

Bump on the request for a kfhd7-freedom-boot-7.2.3.img mirror, as goo.im is still down, please!
All i need is that file!

Sorry - google translate ))
Tell me how to set the custom 2nd bootloader to kindle fire hd 7 1gen (7,5,1 firmware, Root)? I always catch a red screen and have to constantly rebuild the boot
Sequence:
I downloaded the files 7,4,6 boot, 2,8,3,0 recovery files and the file 'stack'. Then, I put them in a directory with adb.
I launch a cmd and start typing commands:
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"
_________________________________________________________
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" (here the periods that the device gives busy with something, and only a reboot helps
____________________________________________________________
adb shell
su
reboot bootloader
_____________________
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.3.0-recovery.img
fastboot -i 0x1949 reboot
___________________________________________
and after all the red screen and hi-service cable ((
6th point missed as there is no where to download from and the possible need to downgrade the firmware.
Please write how to do for firmware 7.5.1 and please give links to the necessary files.

Update TWRP
Hello
Im trying to udate twrp from 2.6.3.1. to this version (2.7.0). Im guessing that 2.7.0. is ther version to install the cm12.1 nighty.
From another topic of the forum I have read that I could use fireflash to do that. Could you tell me where could I get the twrp files and where should I place it to use fireflash?Do I need to use a fastboot cable, adb... or just fireflash to update it? All the instructions will be well received.
Thanks a lot!
Regards

Possibly bricked my tablet... rooted it and then used the fastboot instructions in this thread to install the stack overflow, the kfhd7-freedom-boot-7.4.6.img, kfhd7-freedom-boot-7.4.6.img, kfhd7-freedom-boot-7.4.6.img. The fastboot on the device showed that it was working and it appeared to be just fine until i rebooted it and now it won't turn on. Any advice on how to begin troubleshooting it?

Anyone looking for fireflash apk file could try:http://www.tekify.co.uk, he has a video on how to install twrp using fireflash on YouTube.This is for the kindle fire HD 2012 model
If you want to update twrp using fireflash,you have to be on the kindle stock OS ,to change the twrp version you have to tap on recovery image not flashed grey button and go to where you have your twrp IMG downloaded,tap on it, and the not flashed button should change to details about your twrp update, you must tick the button Disable recovery update before pressing the flash,install script button,I used fireflash to update twrp, but I couldn't use the swipe function, so I used fireflash to switch back to an earlier version of twrp.

Kindle Fire HD bricked to Fastboot only.
Hey I was told to post here. I am visiting a member of my family and their Kindle Fire "Broke". It seems as if its bricked to fastboot mode only, as when you power it on, the kindle fire logo shows up and then very quickly swaps to the Fastboot logo. Im not too big on kindle stuff so so far I havent gotten anywhere and am having trouble. They wouldnt have rooted, enabled ADB, or done anything beyond vanilla kindle stuff. ADB wont recognize the device on my computer and nothing works on the device to get it into recovery or anything besides fastboot. I am using the stock cable but I have also tried multiple cables and USB ports and restarting computer and kindle. Not sure how to proceed as it seems like theres no way I can communicate with the device.