• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY/BOOTSTRAP] Safestrap for Kindle Fire HD 7" (ON HOLD)

Search This thread

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
I've decided to put this project on hold as the bootloader has been fixed for the HD8.9/7 (and in theory can be fixed for the KFire2's)

SAFESTRAP v3.05 BETA (2nd-System Bootstrap / Recovery)

** DISCLAIMER: THIS IS A SERIOUS HACK YOU ARE ABOUT TO PERFORM TO THE DEVICE.
DUE TO THE WAY THIS BOOTSTRAP WORKS, THERE IS A POSSIBILITY OF SOFT-BRICKING.
I'M NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR KINDLE BY USING THIS TOOL.
YOU DO SO AT YOUR OWN RISK.


If you bypassed the BIG RED letters above, make sure you re-read it and understand that you're installing a hijack which affects the normal boot process of the Kindle Fire HD. If that process is changed in anyway it could lead to a soft-bricked device which will need to be fastboot restored.


FOR NOW THIS IS FOR THE KINDLE FIRE HD 7", LATER I ALSO HAVE A VERISON WHICH WILL WORK ON THE KFIRE2.

Download the APK Here
md5sum: 9e409cf3a9d7d510b5bf19262ecfb6d5

Brief Overview / Instructions for how to use Safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/

KNOWN ISSUES:
  • Currently there's a bug where when you create and activate a rom-slot, the /sdcard is pointed at the rom-slots "/data" partition. This of course won't have all of your content in it. I'll release an update once that's fixed.

CHANGES:
  • [11/14] Initial release for KFireHD7
  • [10/30] Begin testing tablet interface for Kindle Fire's
  • [10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
  • [10/17] (3.05) Fixed recovery installation/removal from ROM-slots
  • [10/14] Updated to v3.04 BETA.
  • [10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
  • [10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
  • [10/14] Nearly instant swapping from ROM to ROM
  • [10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
  • [10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
  • [10/14] Charging in recovery
  • [10/14] Supports "Reboot Recovery" from Android OS

Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the "Recovery" button, it takes you to Safestrap Recovery. You can skip the wait by touching the "Continue" button.


KNOWN ISSUES:
  • Stock flashing is currently disabled. And this will probably remain this way for the foreseeable future.

SPECIAL THANKS TO:
  • The entire TWRP team who has built an AMAZING recovery system.
  • The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.

[ SCREENSHOTS COMING SOON ]
 
Last edited:

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
I'll know more shortly once my tester gets back with me.

The proof of concept runs perfectly on my 1st gen KFire where I mocked up the hijack and was able to walk through it w/o fear of bricking.

Sent from my XT894 using Tapatalk 2
 

onemeila

Senior Member
Jan 2, 2012
320
269
Winchester
I'll know more shortly once my tester gets back with me.

The proof of concept runs perfectly on my 1st gen KFire where I mocked up the hijack and was able to walk through it w/o fear of bricking.

Sent from my XT894 using Tapatalk 2

Thank you for the hard work as I'm sure you have spent quite a bit of time on this.
 

shook187

Senior Member
Oct 1, 2010
3,564
1,073
Haverhill MA
For us non tech guys, exactly what is the purpose of this recovery be? To make a backup of what currently have? The ability to flash?

Sent from my SPH-L900 using xda premium
 

ci3hu1

Senior Member
Oct 3, 2009
82
4
This is the best news i ever heard since i bought my KFHD a week ago. I hope it passed the test.
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,991
2,574
Austin, TX
Just to reiterate...

Users cannot go and flash any ROM on their devices...ROMs must be made with the 2nd gen. kernels in mind and any attempt at flashing ROMs made for 1st gen. devices will most assuredly brick one's device, correct?
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
Just to reiterate...

Users cannot go and flash any ROM on their devices...ROMs must be made with the 2nd gen. kernels in mind and any attempt at flashing ROMs made for 1st gen. devices will most assuredly brick one's device, correct?

Yes. No flashing 1st gen device ROMs. Insta brick. Safestrap can't save you from that.

Good news and Bad news on the 1st tests:
1. Good: I found a better hijack point in the new 7.2.1 ramdisk. So I'm adjusting some things and doing some more tests.
2. Bad: The screen is rotated differently on the KFireHD, than it is on the KFire 1st gen. So my touch buttons and stuff aren't working correctly. The next few tests I do will be to show where and how the screen is rotated in relation to the touch controller.

So for now still nothing public.
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,991
2,574
Austin, TX
Yes. No flashing 1st gen device ROMs. Insta brick. Safestrap can't save you from that.

How hard would it be to add a check that makes sure no 1st gen. ROMs, or any ROMs that have modified files that would normally include signed headers, get accidentally installed?

For the most part I'm sure it wouldn't be a problem, but there are those who will try anyway, no matter how many warnings are given in bold red letters.

Not to mention there may be inexperienced (or heaven forbid, malicious) "devs" that might, inadvertantly or otherwise, modify a file with a signed header.
 
Last edited:

reverendkjr

Senior Member
Nov 7, 2009
891
849
Cincinnati, OH
www.youtube.com
How hard would it be to add a check that makes sure no 1st gen. ROMs, or any ROMs that have modified files that would normally include signed headers, get accidentally installed?

For the most part I'm sure it wouldn't be a problem, but there are those who will try anyway, no matter how many warnings are given in bold red letters.

Not to mention there may be inexperienced (or heaven forbid, malicious) "devs" that might, inadvertantly or otherwise, modify a file with a signed header.

I believe that the final product will have such a check.
 

craby1925

Senior Member
Nov 17, 2010
337
33
Well that idea sounds like something twrp would have to integrate. But all the same, hash code, do you have a donation button, you are clearly a valuable member of this device development.

Sent from my Fire HD with root!
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
Testing Update: We have a solid boot after Safestrap installation which is a plus since we're now injecting the recovery splashscreen into the boot process.

My last test (#3) didn't have a working touch controller during the splashscreen, but I have test #4 ready which *could* load the touch driver and allow for entry, but since it's Halloween and we all have families, I won't know how that works till later tonight.

TODO: I'm working on re-doing the Safestrap theme for 800x1280. I had previously been running a 1280x800 theme but the screen is vertical not horizontal. So the layout will be more phone-style than tablet looking.

But even if it's the default TWRP theme with a few missing images, I'll know if we're in a usable state soon.

Verifying Device: I think we can turn on asserts before flashing ROMs. However, it could be that every single Kindle Fire device is named "blaze_tablet" or "blaze" so that might be less than useful. It will take some testing probably to come up with a solution. The Safestrap APK performs a model check when you click "Install Recovery" (KFTT == KindleFireHD-7) and instantly bails if that's not true, so at least you can't install the wrong devices' recovery.

On the donations: There should be a button under my name on any post which links to my paypal.

However, let's hold off donations till we see some actual results and have a working stock-based ROM to flash which devs can tweak w/o fear of bricking. At that point I'll call it a successful bootstrap/recovery and we can move on to AOSP builds.

I'm not against donations (tho I don't do this for money obviously), I just feel you should already have something in your hands and be happy with it before you give any hard earned money to a dev.
 
Last edited:

jailuis

Senior Member
Oct 3, 2012
199
12
jlrcdevteam.blogspot.com
First of all, thanks a lot for your effort. Wish I could donate but Im a minor and live outside US... so its hard to ask for "dollars" here..

One question: this will allow OTG usb somehow or not?

Sent from my KFTT using xda premium
 
Last edited:

iaes

Member
Apr 12, 2010
21
0
Thanks a lot for working so hard, Hashcode. The updates are really appreciated and I really hope you are successful in opening up the Kindle Fire HD/2,
 

jacewt

Senior Member
Mar 7, 2009
354
82
Los Angeles
So you don't own the HD, hashcode? I will def. send a donation your way if you get this working!

I am trying to understand the way this will work. Is it a bit like a dual boot except with 4 roms? And one must always be running stock? And you can backup and restore all of them with twrp?
 

Tristanlogd

Senior Member
Jul 22, 2010
57
5
Richmond
Yes, on all of the above.

I should point out that you may not actually want to run 4 ROMs due to emmc size limits (especially KF2).

I keep the stock ROM pure to protect our path to recovery.

Sent from my XT894 using Tapatalk 2

Awesome work Hashcode. This sounds similar to how Android is run on the Touchpad. Keeps Webos in its own environment and dual boots Android. Can't wait! :good:
 
  • Like
Reactions: Shawn

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    I've decided to put this project on hold as the bootloader has been fixed for the HD8.9/7 (and in theory can be fixed for the KFire2's)

    SAFESTRAP v3.05 BETA (2nd-System Bootstrap / Recovery)

    ** DISCLAIMER: THIS IS A SERIOUS HACK YOU ARE ABOUT TO PERFORM TO THE DEVICE.
    DUE TO THE WAY THIS BOOTSTRAP WORKS, THERE IS A POSSIBILITY OF SOFT-BRICKING.
    I'M NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR KINDLE BY USING THIS TOOL.
    YOU DO SO AT YOUR OWN RISK.


    If you bypassed the BIG RED letters above, make sure you re-read it and understand that you're installing a hijack which affects the normal boot process of the Kindle Fire HD. If that process is changed in anyway it could lead to a soft-bricked device which will need to be fastboot restored.


    FOR NOW THIS IS FOR THE KINDLE FIRE HD 7", LATER I ALSO HAVE A VERISON WHICH WILL WORK ON THE KFIRE2.

    Download the APK Here
    md5sum: 9e409cf3a9d7d510b5bf19262ecfb6d5

    Brief Overview / Instructions for how to use Safestrap:
    http://blog.hash-of-codes.com/how-to-safestrap/

    KNOWN ISSUES:
    • Currently there's a bug where when you create and activate a rom-slot, the /sdcard is pointed at the rom-slots "/data" partition. This of course won't have all of your content in it. I'll release an update once that's fixed.

    CHANGES:
    • [11/14] Initial release for KFireHD7
    • [10/30] Begin testing tablet interface for Kindle Fire's
    • [10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
    • [10/17] (3.05) Fixed recovery installation/removal from ROM-slots
    • [10/14] Updated to v3.04 BETA.
    • [10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
    • [10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
    • [10/14] Nearly instant swapping from ROM to ROM
    • [10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
    • [10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
    • [10/14] Charging in recovery
    • [10/14] Supports "Reboot Recovery" from Android OS

    Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the "Recovery" button, it takes you to Safestrap Recovery. You can skip the wait by touching the "Continue" button.


    KNOWN ISSUES:
    • Stock flashing is currently disabled. And this will probably remain this way for the foreseeable future.

    SPECIAL THANKS TO:
    • The entire TWRP team who has built an AMAZING recovery system.
    • The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.

    [ SCREENSHOTS COMING SOON ]
    12
    Hello all,

    I know this thread has been quiet for a few days and it's mainly due to a big I'm trying to work around during the entry to recovery.

    What happens is the old init process is somehow still lingering long enough to trigger the "omap watchdog" driver in the kernel. it's a driver designed to reset the device when the process thinks it's hung up.

    Turns out we killed the old init process off on purpose, so that we can re-start it with new rootfs files. But, that doesn't change the fact that recovery reboots about 20 seconds after you enter.

    I'm tinkering with various solutions atm.
    11
    Testing Update: We have a solid boot after Safestrap installation which is a plus since we're now injecting the recovery splashscreen into the boot process.

    My last test (#3) didn't have a working touch controller during the splashscreen, but I have test #4 ready which *could* load the touch driver and allow for entry, but since it's Halloween and we all have families, I won't know how that works till later tonight.

    TODO: I'm working on re-doing the Safestrap theme for 800x1280. I had previously been running a 1280x800 theme but the screen is vertical not horizontal. So the layout will be more phone-style than tablet looking.

    But even if it's the default TWRP theme with a few missing images, I'll know if we're in a usable state soon.

    Verifying Device: I think we can turn on asserts before flashing ROMs. However, it could be that every single Kindle Fire device is named "blaze_tablet" or "blaze" so that might be less than useful. It will take some testing probably to come up with a solution. The Safestrap APK performs a model check when you click "Install Recovery" (KFTT == KindleFireHD-7) and instantly bails if that's not true, so at least you can't install the wrong devices' recovery.

    On the donations: There should be a button under my name on any post which links to my paypal.

    However, let's hold off donations till we see some actual results and have a working stock-based ROM to flash which devs can tweak w/o fear of bricking. At that point I'll call it a successful bootstrap/recovery and we can move on to AOSP builds.

    I'm not against donations (tho I don't do this for money obviously), I just feel you should already have something in your hands and be happy with it before you give any hard earned money to a dev.
    10
    Just a quick note....

    Progress has been made. Stuff is starting to work.

    Stay Tuned.

    :highfive:
    10
    OP updated with the beta APK.

    ** BECAREFUL **

    KNOWN ISSUES:
    • Currently there's a bug where when you create and activate a rom-slot, the /sdcard is pointed at the rom-slots "/data" partition. This of course won't have all of your content in it. I'll release an update once that's fixed.

    As with any locked device this tool allows you to mess up your stuff. Just use common sense for now, maybe make a backup and get used to Safestrap.

    Enjoy

    More to do, to get custom ROMs on their way. Thank you for being patient.