Database Develop

Adding scripts/commands to recovery?

I posted a while back about the different recovery images here and have since been using Darch_RA-1.7 for everything (Firerat, GB ROMS, etc.).
When I change my custom partitions, there are two times when I need to ADB (one is arguable). I have to reboot into recovery during one point of modifying mtd partitions with Firerat Recovery, which can be accomplished by pulling the battery and just booting with HOME+POWER keys. It would be super handy though if there was a reboot into recovery command in my recovery image. I know this is in CW 3.x.
Secondly, and more important, is that to limit hickups in google restoring my settings when I load a new ROM, I need to apply s0be's fix before my first boot, which essentially is just making a dir /cache/download and then fixing the permissions for it.
I would love it if these commands could be apart of Darch's 1.7 recovery so that I could re-flash on the go without a computer for ADB shell. I am not completely sure how to do this (modifying the recovery binary), and moreover if I need to find the original source or just unpack and use the binaries. This little conversation was somewhat helpful.
Thoughts? Help?

Replying to my own post, but I had an idea that to address s0be's fix, I could possibly make it into a signed zip, of course assuming that would work (permissions?). Just a thought.

If your using Ra1.7 you don't have to pull the battery when using fr. Just choose the power off option and reboot with home+power. I know its off your op topic but I'd figure I'd post incase you were still using fr.
#Root/Hack-Mod_Always*

And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App

So that's why people have an 18mb cache.
The Fer-Shiz-Nizzle said:
And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Well that explains why I see a bunch of folks using 18 as the cache size, but didn't see that in the thread. My most recent repart with with 128 and 18, which although is a bit excessive for the cache (only using 4 of 18), will eliminate the need for s0be's fix.
For the record, I went ahead and did it anyways. Also, you can definitely just use the power off function (or battery pull) in Darch's 1.7 to get reboot to recovery.
Bottomline: I would say this is solved for my specific issues with Firerat MTD. Also, Darch's 1.7 is perfectly capable of installing GB ROMs.

Streak 7 Dell 3.2 Recovery Image (Official non-modified dell image)

For those of you who got stuck after having a MOD version of the streak 7 running 3.2 and still have yet to succeed in restoring your 2.2 image so you can do the dell update I announce to you an easier way. After all this time utilizing community resources I feel it is my time to give back.
Below is the link to the nvidia flash utility, the nvidia boot recovery drivers and image file p2 through p24 that will provide recovery to your Dell streak 7 tablet to the latest 3.2 unmodified image.
The link will have to be pasted since although I have visited often, I have yet to post very much, apparently 8 posts are required for a link and 10 posts to post to the developer page, thus you find my copy and paste link below removing the spaces between the ws' and the coms'.....
w w w .sicksubstance. c o m/Files/Streak7_3.2-Dell_img.rar
Download from the above link and extract.
-Place the nvflash folder into the root of your c drive
-Place the tablet in boot recovery mode (vol down and vol up while plugging in the tablet while it is turned off)
-Open up a command shell (if using vista or later make sure to run the shell as administrator)
-cd c:\nvflash
-restore.bat
The restore takes a bit, once it is complete power down the tablet via the pin hole, power back up and enjoy!
NOTE: If running windows vista or windows 7 be sure to boot your computer in the unsigned drivers disabled state. During boot up before the windows logo appears press F8 and choose disable unsigned driver requirement option.
I hope this helps some of you!
-redistribut(e)r
Fellow Android Developer

You should remove p23/23 unless your intention is to have everyone using the same service tag as whoever's device that came from

Recovery Image
This is directed at TheManii, on your wiki for the S7 the link is broken for the recovery image for the 506 package for the US 4G version... reason I think I need it is I'm getting gapps force closes as of last night, sure it was something I installed, but i wanted to try flashing the HC package rather than the HC zip, unless you think flashing the zip will have the same effect... I'm basing myself on experience using the Streak 5, that flashing packages is necessary to get things back in order

Wiki links are fixed now, as for the zips: the ones I have created are completely unmodified except that they remove the modem update and region checks.
It's not possible to flash the zips wrong, it's simply 2 large files that are written as-is, the update does not process them in any way at all. If anything at all goes wrong it simply wont boot at all.
Reason I supply the zips at all is because the 2xx recoveries wont load on 5xx and 5xx recoveries wont load on 2xx, due to 5xx having a bootloader update

TheManii said:
Wiki links are fixed now, as for the zips: the ones I have created are completely unmodified except that they remove the modem update and region checks.
It's not possible to flash the zips wrong, it's simply 2 large files that are written as-is, the update does not process them in any way at all. If anything at all goes wrong it simply wont boot at all.
Reason I supply the zips at all is because the 2xx recoveries wont load on 5xx and 5xx recoveries wont load on 2xx, due to 5xx having a bootloader update
Click to expand...
Click to collapse
Thanks TheManii, but before I take any drastic measures, I would like you opinion, what's the best flash on our Streak 7, to get things as they should... NVFlash, update.pkg, or update.zip?
And one more little question... the restore.bat file goes all the way to partition 24, should those last three (22,23 & 24) be deleted or just 22 & 23?
Thanks for your time in answering my questions and hookin us up with the links

Dell Streak 7 Partition Layout - xda wiki
22 is SDcard
23 is device IDs
24 is MAC address
Those should never be included in any uploaded dumps.
The install preference should go:
PKG
The zips I made
...
Using NVflash
On the EU3G i would recommend using the the pkg even after using the zip to get the correct modem update since mine has it removed

TheManii said:
Dell Streak 7 Partition Layout - xda wiki
22 is SDcard
23 is device IDs
24 is MAC address
Those should never be included in any uploaded dumps.
The install preference should go:
PKG
The zips I made
...
Using NVflash
On the EU3G i would recommend using the the pkg even after using the zip to get the correct modem update since mine has it removed
Click to expand...
Click to collapse
YOU THEMANIII, answers like that are priceless!! Thanks so much for your time

redistributer said:
NOTE: If running windows vista or windows 7 be sure to boot your computer in the unsigned drivers disabled state. During boot up before the windows logo appears press F8 and choose disable unsigned driver requirement option.
I hope this helps some of you!
-redistribut(e)r
Fellow Android Developer
Click to expand...
Click to collapse
This part really isn't necessary.
If you follow part 2 of my video series here, you just need to manually install the drivers.
http://tabletroms.com/forums/showwiki.php?title=DellStreakFAQ:How-to-Flash-your-Dell-Streak-7

This image (Only 2 to 14)can be applied to a 4G T-Mobile?

AdComa said:
This image (Only 2 to 14)can be applied to a 4G T-Mobile?
Click to expand...
Click to collapse
What you can do is modify the process so that your SD card is not rewritten and your Service tag number is not overwritten.
There is a partition.txt file, you delete the part that mentions partitions 22, 23 and 24.
There is also a restore.bat file, edit it also to not include those 3 partitions, and just to make sure, delete those 3 images from the folder, 22, 23 and 24.
Now, having said that, you are better off flashing the HC stock recovery.img via fastboot, loading the update.pkg to your EXTERNAL SD and flashing HC that way, which is the way I have had the best luck with. After flashing that, you then flash the CWM recovery for Honeycomb and then you can flash Superuser to have root, it takes all of about 20 minutes to have the cleanest install possible with that route. The NVFlash should only be used to get back to Froyo, and even still you would take the files and modify them in the same way to not flash partitions 22,23 and 24

[RECOVERY] Safestrap for Droid 3 [2012/10/17: Version 3.05 SD BUGFIX]

SAFESTRAP v3.05 (2nd-System Bootstrap / Recovery)
PRIOR TO UPGRADING TO V3.x FROM V2.x MOVE THE /sdcard/safestrap FOLDER FROM YOUR /sdcard TO THE /sdcard-ext. THIS OPENS UP VALUABLE INTERNAL EMMC SPACE WHERE ROM SLOTS ARE CREATED. AND KEEPS YOUR V2 BACKUPS SAFE IN CASE YOU WANT TO REVERT TO V2 AND USE THEM TO RESTORE.
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the "Droid3Safestrap-3.05.apk" Installer Here for "DROID 3"
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the DROID3 VERSION ]
CHANGES:
[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 menu button, it takes you to Safestrap Recovery.
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.
As always, let me know what you think!

A quick note about why I made a MotoBlur 5.6.890 ROM .zip for Safestrap:
1. This is the stock version of our Phone's software. If you want to swap back and forth between CM7 and the standard software, but NOT turn off "Safe System" then you need a stock ROM to use. This is it.
2. Devs can use this ROM as a sort of base for making their skinned ROMs without fear of bootlooping into an SBF. Feel free to tweak and hack away.. nothing you can do to the ROM will force you to fastboot restore. At worst you're looking at a battery pull -> bp-tools -> recovery -> restore.
3. I know some people are checking dev servers for future Moto updates. In theory I will pull the /system images from those updates and put out updated MotoBlur ROMs in the future as a way of test driving upcoming Moto patches w/o fear of leaving yourself stranded on an upgrade path that won't be supported.

So, im just curious, if I wanted to...
I could run say steel droid, then install safestrap, flash cm7,
And by turning safestrap off/on, I could technequally go back and forth
between 2 custom roms? Or do I have to keep the /system partition clean?
Sent from my DROID3 using Tapatalk

Actually the idea for Safestrap is to keep the main system clean.
I'm working with ChevyCam to get a Safestrap version of SteelDroid. Then you can use Safestrap exactly like regular recovery where you would swap from ROM to rom via backup and restore. The advantage being your method of recovery entry and ROM booting is always protected.

Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.

Thanks so much for clarifying, and thanks a million times over for all the great work you've selflessly done for the Droid3 community. I look forward to future CM7 updates.

hey hashcode, just a clarification, we can use safestrap like koush's bootstrap, but we just must turn safe system off right? cause your post makes it seem as if we cant do this

Right now, zips applied with Safestrap are applied to the 2nd-system only. In theory I could make some adjustments to allow for applying zips to the original system as well.. and while I understand the idea of "dual booting" a phone seems fantastic, it's really just an unrecoverable bootloop waiting to happen.
I'd rather that Droid 3 users turn on "Safe System" and never turn it off again (or need to). If all of our ROMs were installable via Safestrap I really feel that we would see alot less "I've bootlooped" postings on the boards.
For the recovery portion of Safestrap: it does NOT backup the original system. Only the 2nd-system, data and cache partitions. (Remember the idea is that you basically root your original system, toss on Safestrap and then enter recovery and toss a .zip onto your 2nd system)
I'm considering changing this in the next version of Safestrap so that backups from Safestrap can be used for full system recovery.

Another question with which to bother you...
When you have the option to do a backup, will you have the ability to choose the destination where the backup is stored as well as the location from where the backup can be restored (either internal or external storage)?
Thank you for your time.

Excellent work, I think this is a fabulous idea and should be the de facto standard for these locked devices. Were you still thinking about using a 2nd data/cache partition as well?
I think it would be pretty sweet if you could loopback mount file system images stored on internal storage for the system/data/cache partitions to implement a proper and safe multiboot system. I don't know how much of a performance hit this would take though.
Anyway, the one suggestion I would make about backing up the original system is to not do it as part of the regular backup/restore. Since system should rarely change, it'd be a waste of time and storage space to back it up every time. Could you either make it a separate option, or perhaps only back it up if the partition's checksum changed?
Besides, if you hose your system and need to restore it, you're probably not going to be using this recovery anyway.

The Solutor said:
Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.
Click to expand...
Click to collapse
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...

So in order to switch to another ROM (from CM7), that is not Safestrap compatible, I just need to toggle safe mode in recovery?
Sent from my DROID3 using XDA App

Yes. But beware of bootloops caused by not wiping your data between ROM switches.
To prevent that from happening you currently need to maintain copies of your data via backup/restore.. This will get addressed in the next version of Safestrap.

I have a version of Steel Droid that is supposed to be safestrap compatible. Im uploading it now. Will test it really quick, to be sure, and if its all good, will post a link!

The Solutor said:
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...
Click to expand...
Click to collapse
Ok I spoke too soon, backup and restore doesn't works on XT883
The backup folder is created correctly on the SDcard, the backup process starts normally with the /system partitons and then the process fails telling that there was an error while backing up the system partition.
Hashcode do you have any idea ?
The only differences in the partitioning between the two systems are the mount options
this is the 862
/dev/block/system on /system type ext3 (ro,noatime,nodiratime,barrier=1,data=ordered)
and this the 883
/dev/block/system on /system type ext3 (rw,relatime,barrier=1,data=ordered)

Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App

I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?

Just a few short hours later I'm feeling adventurous, but the backup step indicates the MD5 generation failed. Any ideas?
Sent from my DROID3 using XDA App

LaZiODROID said:
I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?
Click to expand...
Click to collapse
There would probably be radio issues.

Joe.cotto said:
Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This MotoBlur ROM is specifically for Safestrap to run as 2nd-system.

[Recovery] [Locked Bootloader Only] Safestrap Recovery V3.1 [01/04 3.12]

SAFESTRAP v3.12 (2nd-System Bootstrap / Recovery)
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the APK Installer Here for "RAZR-HD/ATRIX-HD"
md5sum: 9b3d75e84c06d1e71af1bf1bad57faf3
FOLLOW THESE INSTRUCTIONS: How to Safestrap
NOTES:
ROMS based on Android 4.2.1 *MUST* go into rom-slot1 currently. This will be fixed in the future.
CHANGES:
[01/04] (3.12) Fix initial file selector location for backup/restore
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions. * STILL TESTING -- BUGGY*
[12/29] (3.10) Enable flashing to stock ROM
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
[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 menu button, it takes you to Safestrap Recovery.
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.
As always, let me know what you think!

Thank you!!!!
Sent from my MB886 using xda app-developers app

Wonderful. Now let the games begin.

S#!T just got REALLY REAL! HOORAY HASHCODE AND ALL WHO HELPED!
Deep rooted in the mAtrix HD...
http://android-gz.com

Amazing! :")
Sent from that dude with that one phone

Just did a backup of my system and data partitions. Super :thumbup:

love you hash no h0mo

Thanks Hash!
Can we backup and restore "data" yet along with "system"?

ATGAdmin said:
Thanks Hash!
Can we backup and restore "data" yet along with "system"?
Click to expand...
Click to collapse
Just did a backup myself

SirHoover2010 said:
Just did a backup myself
Click to expand...
Click to collapse
Yes but restore of data was still broke last I knew.
Sent from my A200 using xda premium
---------- Post added at 12:22 AM ---------- Previous post was at 12:12 AM ----------
Hash said no data restore as of yet, but he's working on it. So DO NOT RESTORE DATA!!
Sent from my A200 using xda premium

You're amazing,Hashcode!!! You're the saviour.

When I try to open safe strap I keep getting unfortunately safe strap has stopped could this be because I lost root?
Sent from my MB886 using xda app-developers app

wildchild048 said:
When I try to open safe strap I keep getting unfortunately safe strap has stopped could this be because I lost root?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
You'll need root to install safestrap as it needs permissions to write the recovery on the device.
Sent from my Jellybeaned Motorola Atrix HD MAXX

So this will allow us to make custom roms with out the need of a signature on is?

I would assume so lol. After all, it's a custom recovery but without the need for an unlocked bootloader.
Sent from my Jellybeaned Motorola Atrix HD MAXX

So how do I combine and or remap the partitions so that I only have one internal storage and have my mirco SD card actually functions as a normal micro SD card the same way they work on the atrix 4g and atrix2?

Shouldn't need to do anything special to the SD cards. Just go into "Boot Options" select a rom-slot and follow the creation instructions.
Choose 1GB data for now unless you're a heavy app users and need more space (100+ apps).

Neroga said:
I would assume so lol. After all, it's a custom recovery but without the need for an unlocked bootloader.
Sent from my Jellybeaned Motorola Atrix HD MAXX
Click to expand...
Click to collapse
Actually you can't install custom ROMs as of yet. That feature is not working at this time. The only thing you can do is backup and restore your /system. Do not attempt to backup and restore data!
Sent from my A200 using xda premium

Hashcode said:
Shouldn't need to do anything special to the SD cards. Just go into "Boot Options" select a rom-slot and follow the creation instructions.
Choose 1GB data for now unless you're a heavy app users and need more space (100+ apps).
Click to expand...
Click to collapse
Slow down lil daddy cause we might be talking about two different things....
this is what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=1944053

Damn dude, you are the freaking man... Thank you

[THOR/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]

ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!
WARNING: THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
UNKNOWN ISSUE: If you try and start Wifi and the device crashes/reboots, try turning on bluetooth prior to enabling wifi and see if that works.
CURRENT PROJECT STATUS:
BETA-STABLE
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.x.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Rooted w/ SuperSU installed
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
Open an "explorer" of some sort (ESFileExplorer, etc)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
DOWNLOADS:
CONFIRM YOUR STOCK OS VERSION BELOW AND THAT YOU ARE USING THE KINDLE FIRE HDX 7" (THOR)
[13.3.2.1 and earlier] LATEST FILE: Safestrap-Thor-3.72.apk
[13.3.2.3.2 and later] LATEST FILE: Safestrap-Thor-3.75-os3.2.4-B02.apk
Mirror 1: Crackflasher Download
Mirror 2: Goo.im Download
Here's an amazon-os .zip that can be used on rom-slots for re-flashing the OS -- MUST MATCH STOCK ROM:
THOR ONLY (HDX 7") 13.3.1.0: Download from goo.im
md5sum: 24fee10d8c6b0dbf583465baa938e842
It's the straight Amazon OS:
not DeOdexed
will not stop OTAs
is not rooted
the only changes I made, were to strip out the boot.img or modem.img flashing stuff.
To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:
http://download.chainfire.eu/supersu
As of version 3.x, Safestrap Recovery is now based on TWRP. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
Special Thanks To
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery

For those that missed it in the 1st post:
PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!
KNOWN ISSUES WHEN USING ROM-SLOTS (The ROMs are kept on loop device mounted partitions)
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.
CHANGELOG:
[v3.75-B02]Bugfix rom-slot booting
[v3.75-B01]TWRP 2.7.1.0 update + display fix for 13.3.2.3.2/13.3.2.4
[v3.72]TWRP 2.7.0.0 update. *** This includes a bugfix for backup time showing correctly ***
[v3.72]Raised /data partition size to 16gb
[v3.72]Swapped "Reboot" -> "Download" mode to "Reboot" -> "Bootloader" (places you in fastboot mode)
[v3.70-B01]Seems like I have a solid fix for the "snow" effect when getting into Safestrap sometimes
[v3.70-B01]System partition now matches stock EXACTLY. You can't even change it in the settings due to the way I'm creating it during rom-slot creation. It's not a bug, that's on purpose. That being said, there should be plenty of room in that space to do what we want.
[v3.70-B01]Battery % now being displayed correctly in recovery
[v3.70-B01]Updated to latest Safestrap sources
[v3.65-B01]Initial release for Thor (Kindle HDX 7")

Congrats, Hash!
Sent from my iPod touch using Tapatalk

Nice, just got my my hdx last night. Will let you know my results once I'm not at work .
Thanks!
Sent from my Nexus 4 using Tapatalk

things are moving well, many thanks for your efforts!

I'm new to safestrap world. Can you tell me if there are downside of any sort using safestrap?
I mean, are roms installed via safestrap slower or limited under any aspect? I know it's the only way atm, but just asking...

zooster said:
I'm new to safestrap world. Can you tell me if there are downside of any sort using safestrap?
I mean, are roms installed via safestrap slower or limited under any aspect? I know it's the only way atm, but just asking...
Click to expand...
Click to collapse
GOOD QUESTION!
The ROMs are kept on loop device mounted partitions. This causes a few known issues:
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.

Hashcode said:
GOOD QUESTION!
The ROMs are kept on loop device mounted partitions. This causes a few known issues:
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.
Click to expand...
Click to collapse
Thank you for the answer.
I'm not yet an owner of this tab. I'd really want to buy this beast (8.9), but the fireOS is stopping me. So I'm eagerly awaiting for a custom rom. Locked bootloader "turned me off"
So, 1) do you think safestrap can be a solution for a real daily driving custom rom (I guess CM)? Or just something to try/play with?
2) is there any chance/hope to unlock that armored bootloader?

Awesome work Hashcode. You've made two of my devices bearable to live with.

Thanks so much Hashcode!!

zooster said:
Thank you for the answer.
I'm not yet an owner of this tab. I'd really want to buy this beast (8.9), but the fireOS is stopping me. So I'm eagerly awaiting for a custom rom. Locked bootloader "turned me off"
So, 1) do you think safestrap can be a solution for a real daily driving custom rom (I guess CM)? Or just something to try/play with?
2) is there any chance/hope to unlock that armored bootloader?
Click to expand...
Click to collapse
Sorry, but not yet. I talked to Hashcode and he was saying that since we can't use custom kernels yet, we can't use AOSP (Paranoid Android, Cyanogenmod, AOKP, CarbonROM, etc.) roms. It's okay, though. I plan on making a rom that will give you as close to CM experience as possible while still staying on an Amazon ROM.
As for the question regarding bootloader unlock, I'm not sure. I'm still in the process of experimenting with different things. I haven't had time recently though.
Sent from my iPod touch using Tapatalk

Reporting back - Safestrap worked fine for me. Haven't done anything but make a backup of stock yet, but everything seems to be in order. Looking forward to have something to flash .
Thanks again.
Sent from my Nexus 4 using Tapatalk

Gotta love this guy
Sent from my XT926 using Tapatalk
---------- Post added at 11:55 PM ---------- Previous post was at 11:29 PM ----------
HASHCODE I mean. Of course. I'm so giddy...oops I fell off my chair.
Sent from my KFTHWI using XDA Premium 4 mobile app

i dont own one and prob never will but awesome work as always bro!!

Installed and currently running a backup. Would it be a good idea once we get a flashable rom to uninstall all apps from stock to make as much free space as possible? Thanks again Hash for your hard work on this next best thing to an unlocked bootloader.

Noticed that there is some graphics driver issues leaving static / snow on occasion. Other than that, great tool, it saved me once already. Thanks Hashcode!

_Alex_ said:
Noticed that there is some graphics driver issues leaving static / snow on occasion. Other than that, great tool, it saved me once already. Thanks Hashcode!
Click to expand...
Click to collapse
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk

Hashcode said:
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
This happens to me as well. But only if i start recovery by pressing the button on boot. If i start it from the "reboot to recovery" button in the app, it looks fine.

Sent from my KFTHWI using XDA Premium 4 mobile app

Hashcode said:
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
If I go into the safestrap app then reboot into recover everything works fine and looks fine. If I shutdown the hdx then enter the recovery on power up it looks snowy BUT is still usable. Check it out.