Database Develop

[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] Safestrap Recovery v3.7x [05/15/2014 V3.73 - TWRP 2.7.0.0]

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!

[RECOVERY] Safestrap Recovery v3.7x [05/15/2014 V3.73 - TWRP 2.7]

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 - Toggle SAFE BOOT MENU

hi to everyone!
I need your help to resolve a simple issue.
I'm using Safe Boot Menu, I've installed safestrap recovery v2.10 on my Droid 3, the phone have SAFE BOOT MENU enabled, I've installed AOKPS ICS on secondary filesystem and I want to toggle SAFE BOOT MENU and replace the original stock filesystem with the secondary partition.
How can I do it?
I need some solucions to commit the changes mades on secondary filesystem.
Thanks to everybody!

padevoto said:
hi to everyone!
I need your help to resolve a simple issue.
I'm using Safe Boot Menu, I've installed safestrap recovery v2.10 on my Droid 3, the phone have SAFE BOOT MENU enabled, I've installed AOKPS ICS on secondary filesystem and I want to toggle SAFE BOOT MENU and replace the original stock filesystem with the secondary partition.
How can I do it?
I need some solucions to commit the changes mades on secondary filesystem.
Thanks to everybody!
Click to expand...
Click to collapse
Safestrap is not designed to "commit" changes as you are looking to do. Rather it keeps two seporate file systems in place and allows you to change between them via the Safe Boot Menu (Safe Mode Enabled being your secondary OS, Safe Mode Disabled being your primary OS).
From the posts I have seen from Hashcode the new version will allow you to overwrite your Non-Safe OS (Safe Mode Disabled). At this point you may be able to do something similar to what you want by creating a backup, then applying the backup to the Non-Safe OS. However that is just me speculating, until we see the new version only Hash would be able to answer that.
So for now you cannot do what you are looking to do.

Just switch to the nonsafe system, uninstall the Safestrap bootloader, load the regular CWM recovery that came out before Safestrap (forget name), flash or backup or whatever you need to do, uninstall that, then reinstall Safestrap, switch to safe system, and done.

[HOW TO] DUAL BOOT for P990 & SU660 on BOTH Bootloaders v5.0

Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.​
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread

Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.​
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!

Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....

This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post

This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job

Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate

Nice ! Trying soon... :fingers-crossed:

SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.

i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?

what about ics and gingerbread on dual boot!?

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)

Nice man" I ll try it soon!

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.

I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!

Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:

And what about dual boot with linux?

tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.

sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).

tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...

How about flashing the second rom that have aroma installer??