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.
Related
SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** 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:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Targa" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7.0.0 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.
SElinux support in recovery (1st boot won't take so long)
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/20] (3.60) update to TWRP 2.6.3.0 base recovery
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[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.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
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/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[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!
SCREENSHOTS (showing slightly older TWRP base)
First! Thanks Hash!
Nice one. Will be checking all this out later just got a free bionic
Sent from my DROID BIONIC using XDA App
What's the correct procedure for updating versions of Safestrap? Do I need to be in unsafe system or uninstall first or ?
Awesome, Thanks!
Love this app/recovery. Thanks!
Sent from my BIONIC using Tapatalk
Does anyone have suggestions for when switching back to the primary, and it errors out on original data restore?
I did do the proper backups and normal toggle. The original back up refused to boot. Even initiate boot.
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Suggestions on what I may have done wrong, or a less time consuming remedy should it happen again?
Apologies if I left something out.. typed while putting the mag stripes on iTunes cards... only 600,000 to go... weeeeeee
And thanks fir your hard work and great tool for the bionic, Hash.
Sent from my DROID BIONIC using xda premium
I've never had that problem. Are you using your internal or external sd card for safe mode? The internal is faster and less likely to have problems.
Sent from my DROID BIONIC using Tapatalk
Does Bionic Bootstrap have to be removed/uninstalled before installing Safestrap? Can BB just be frozen?
Thanks.
EDIT: Okay, I see it does need to be removed.
cappiez said:
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Click to expand...
Click to collapse
I've seen this happen a handfull of times, most of which were due to a nearly full /emmc partition (internal SD card).
When you hard toggle and restore the Eclipse back up here's what happened:
- The "/system" backup goes back onto your /preinstall partition (where it also lives in 2nd-system) -- The only item which will get restored to your primay system is a backup of "/systemorig". And that's important because if you were to restore the 2nd-system back to the original system.. You'd brick because of partition renaming, etc.
- /data and /cache are restored normally.
You did the right thing in hard toggling and then advanced restore your data from a previous backup. Just know that your 2nd-system data wasn't stashed when you do the hard toggle. So there may be an issue when you want to go back to the 2nd-system.
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
JohnnyAn said:
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
Click to expand...
Click to collapse
I've seen this happen when Superuser has just been updated. It's like Safestrap thinks it has su priv, but Superuser never gives it out. Or something odd. I would try removing and reinstalling Safestrap so that Superuser can re-add it to the "allowed" list.
waffleb051 said:
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
Click to expand...
Click to collapse
Safestrap is the recovery system that lets Bionic users utilize an alternate recovery firmware to install alternate ROMs. That's what this entire thread is about.
It almost sounds like you trying to make your backup through ROM Manager. ROM Manager looks for Clockwork Recovery (that gets installed with Bionic Bootstrap and not Safestrap). Safestrap is an entirely different system that ROM Manager won't recognize.
Make sure you reboot your phone and manually enter into Safestrap so that you can make a backup. It will work properly that way.
http://youtu.be/UbGE_xxWSZ4
if it helps anyone, here's a video i made installing Safestrap 1.7 and ICS4Bionic.
Thanks Hashcode for all you've done!
I am wondering if i safestrap and want to go back to koush's bootstrap how do i go about it and can i recover the space used for the 2nd system?
Never mind i figured it out.
Would it somehow be possible to load a stock 5.5.886 image with kernel and everything stock like using the full 5.5.1_84_DBN-55 image? Then being able to update it through the upgrade path then flash it to the normal phone system? I mean using the 2nd partition created by safe strap to do all the steps before flashing to the normal phone partition.
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
twinkyz1979 said:
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
Click to expand...
Click to collapse
Safestrap does not interact with CWM backups from the other bootstrapper.
projektorboy said:
Safestrap does not interact with CWM backups from the other bootstrapper.
Click to expand...
Click to collapse
Although you can still copy the backup from CWM to safestrap and still restore it and it will work. i have done this.
I Loose boot after safe mode enabled
I rooted the .886, then used the OTA and lost root.
I had to factory reset so i could R3L3AS3dRoot and 4ever root, I then used the OTA to come from .886 system to the .893 system.
I am rooted and have the recovery state installed.
When I install the safe strap I loose the ability to boot, I then have to uninstall it to gain boot once again.
EDIT:
Safe strap enabled, had to flash a custom rom over the one which wouldn't boot. I'm sure it would work if i reflashed stock over the safestrap.
Thank you!
SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** 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:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Maserati" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.*
SElinux support in recovery
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[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.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
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/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[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!
SCREENSHOTS (showing slightly older TWRP base)
do i need to be rooted?
Sweet. Let the ics based roms begin.
Sent from my DROID4 using Tapatalk
pimpsalot69 said:
do i need to be rooted?
Click to expand...
Click to collapse
Yes. There is no way to get Safestrap installed w/o being rooted.
Tol flash the leak or to not flash the leak
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
kwyrt said:
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Click to expand...
Click to collapse
I don't recommend people jump on the ICS leaks just yet. But, if you do and are looking to make backups etc, then Safestrap is probably what you need. Just make sure to do the initial backup of your non-safe system (don't need webtop) so that you can put everything back the way you found it.
bdsullivan said:
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Ah the haptic feedback. Yes, I probably should add that back in. As it is, I'm not super thrilled w/ the touch response in the new Safestrap. I probably need to work on it as well. There are times when touches are "lost" and then double up (for 2 touches at once). But hey, it's better than nothing.
I could not agree with you more. I am ecstatic that i was able to make a backup. Now i can work on getting rid of some of this bloat without sacrificing the ability to update again.
Sent from my DROID4 using Tapatalk
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Here is the link for detailed instructions. If you have to the fastboot route than it is about an hour long process so my advice is start with a fully charged battery.
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my DROID4
bonesjones said:
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Follow the instructions posted but the basic rundown will be..
1. Fastboot .219 images
2. Re root phone with motofail.
3. UPDATE SUPERUSER BINARY!!!
4. Use Voodoo rootkeeper to backup root, temp unroot, and restore root.
5. Install .206 ICS leak with stock recovery
6. Use Voodoo Rootkeeper to restore root.
7. Install Safestrap 2.0
Done, and pretty sweet.
No more data issues!
No more not being able to do video!
No more not being able to use flash!
No more weird youtube glitch!
Now to wait to wait for an AOKP port and I'll be perfectly happy!
...Until the next android comes along...
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
strakajagr said:
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
Click to expand...
Click to collapse
I know your questions was not directed towards me but I used Titanium Backup to freeze all of the bloatware, then realized you can do this within the OS under the APPS list. There is a disable button in each app details screen. I froze almost EVERYTHING, except for the My Gallery/music apps. I pretty much did the same thing when I was running GB...was worried that something would cause a bootloop but was very careful I guess. Battery is MUCH better now!!!
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
strakajagr said:
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
Click to expand...
Click to collapse
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
flamefangahs said:
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
+1 on that... I just really didn't want to purchase the galaxy nexus just to get a vanilla android experience.
Sent from my DROID4 using XDA
Any word on when it will be available to 208 users?
Not working for Newest ICS Leak 6.16.208
gdeeble said:
Any word on when it will be available to 208 users?
Click to expand...
Click to collapse
Good question, I can confirm this new Safestrap does not work for 208. When you push install recovery, it loads and obtains root rights, but it never changes from not installed/not active.
Actually I fixed mine. Make sure you install busybox when you root your phone. I just used the free busybox installer and it fixed it where Safe Strap installed on 208. Woo Hoo! My data from 206 also restored. Thank you god for Hashcode and this wonderful tool. :-D
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
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.
SAFESTRAP FOR THE KINDLE FIRE HDX 8.9" (APOLLO)
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.
THANKS TO MY TESTERS:
Scepterr (Who I bricked during testing and had to replace his device)
Gamma-X
GSLEON
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.1.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 8.9" (APOLLO)
[14.3.2.1 and earlier] LATEST FILE: Safestrap-Apollo-3.72.apk
[14.3.2.3.2 and later] LATEST FILE: Safestrap-Apollo-3.75-os3.2.4-B02.apk
Mirror 1: Crackflasher Download
Mirror 2: Goo.im Download
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.75, Safestrap Recovery is now based on TWRP 2.7.1.x. 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]TWRP 2.7.1.0 update + display fix for 14.3.2.3.2/14.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.71-B05]New QCOM recovery graphics patch to fix devices with larger than 2048 width
[v3.71-B05]Fixed touchscreen rotation (off by 90 degrees)
[v3.71-B05]WIP adb access in recovery (may only work on Linux for now)
[v3.71-B05]Initial release for Apollo (Kindle HDX 8.9")
Nice.
Hashcode said:
SAFESTRAP FOR THE KINDLE FIRE HDX 8.9" (APOLLO)
*** 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.
THANKS TO MY TESTERS:
Scepterr (Who I bricked during testing and had to replace his device)
Gamma-X
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.
CURRENT PROJECT STATUS:
ALPHA
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.6.3.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 THAT YOU ARE USING THE KINDLE FIRE HDX 8.9" (APOLLO)
LATEST FILE: Safestrap-Apollo-3.71-B06.apk
Mirror 1: Goo.im Download
Mirror 2: Crackflasher Download
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.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. 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
Click to expand...
Click to collapse
Thank you
Sent from my KFAPWI using xda premium
Hashcode said:
SAFESTRAP FOR THE KINDLE FIRE HDX 8.9" (APOLLO)
Click to expand...
Click to collapse
thanks a bunch mate! you rock!!
Hashcode said:
SAFESTRAP FOR THE KINDLE FIRE HDX 8.9" (APOLLO)
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.
Click to expand...
Click to collapse
For us noobs, where is the "ENCRYPTION" selection referenced above enabled so I can make sure it is NOT before I start ??
Thanks for all your hard work !!
Mark J Culross
KD5RXT
Alrighty then! I guess you had it covered! I wondered why I never got a response. At any rate, if anyone has any issues or if you need any further bug testing, feel free to let me know @Hashcode .
As I dig further into the HDX framework, bootloader & kernel it seems like I find some new roadblock that Lab126/Amazon has thrown into the mix.
One last question. I am unfamiliar, totally unfamiliar, with Safestrap. I assume it lives in it's own partition, & recovery calls are redirected there? Does that mean I can remove it & restore the main partition to default size, then use the build.prop hack to return to stock? Or is safestrap modification to partitions semi-permanent?
EDIT: Nevermind, I did a little reversing & checked out your blog. Needless to say, I answered my own question.
mjculross said:
For us noobs, where is the "ENCRYPTION" selection referenced above enabled so I can make sure it is NOT before I start ??
Thanks for all your hard work !!
Mark J Culross
KD5RXT
Click to expand...
Click to collapse
When you make a rom slot. You can't miss it. So hands off.
What are the optimum partition values to use when creating a rom slot. Are there values that are usafe to use at this point. By the way thanks @Hashcode for bringing this to the 8.9.
kingpin32 said:
What are the optimum partition values to use when creating a rom slot. Are there values that are usafe to use at this point. By the way thanks @Hashcode for bringing this to the 8.9.
Click to expand...
Click to collapse
If at any point you decide you need a larger userdata or cache partition, you can:
- run a backup of the rom-slot
- delete it
- then create a new rom-slot w/ the right sizes
- and finally restore the backup to it (after making sure it's active)
So short answer: no real "wrong" sizes. Can stick w/ the defaults if unsure.
mjculross said:
For us noobs, where is the "ENCRYPTION" selection referenced above enabled so I can make sure it is NOT before I start ??
Thanks for all your hard work !!
Mark J Culross
KD5RXT
Click to expand...
Click to collapse
Actually, the ENCRYPTION reference I'm talking about is when you turn on Android OS level encryption for the userdata partition. I'm not finding that setting in the Kindle OS Settings anywhere. So we might be ok on that.
Installed. All went well. Now, I wait for a reason to use it lol.
How long until we have safestrap on Soho?
Sent from my rooted 2013 Kindle Fire HD with Tapatalk
as of now there is no rom to load in a rom slot, correct???
No there is no custom ROM to load right now.
As far as I know, you could just load the stock ROM into the rom slot #1 and play around to your heart content without fearing you will brick your device since all you mess around is just a copy of the original one only.
So before this was available or before knew it existed I installed gapps. With it losing amazon shop etc as expected. Point is I would like to get a stock Rom into a Rom slot to recover to now that my stock Rom,is not so stock. Where can I find or get a stock Rom from?
Thanks
krypted said:
So before this was available or before knew it existed I installed gapps. With it losing amazon shop etc as expected. Point is I would like to get a stock Rom into a Rom slot to recover to now that my stock Rom,is not so stock. Where can I find or get a stock Rom from?
Thanks
Click to expand...
Click to collapse
[HowTo] Fully restore to stock rom to fix some problem! http://forum.xda-developers.com/showthread.php?t=2582773
Sent from my iPhone using Tapatalk
rcartaz09 said:
[HowTo] Fully restore to stock rom to fix some problem! http://forum.xda-developers.com/showthread.php?t=2582773
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thanks!
So I tried installing ancestral but when I click install recovery from the app it goes through the motions but state never changes. Remains at not installed. Rebooting doesn't bring up the recovery menu.
Going to try to go back to stock and start from beginning. It was awesome using play store!
Trying to install but I'm getting a parse error??
Sent from my KFAPWI using xda premium
---------- Post added at 01:16 AM ---------- Previous post was at 12:56 AM ----------
Figured it out
Sent from my KFAPWI using xda premium
New update up in the OP (B07)
Mainly changes fixing UI issues in recovery (button placements, etc).
More changes coming Trying to fix adb in recovery for windows users.
Sent from my SM-N900V using Tapatalk