Related
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.
I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks
you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com
thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.
if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?
I just wanted to install INIT.D HACK because I read that saves battery.
cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.
Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
It works 4 me
pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.
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
Hello all,
First of all, I'm not very familiar with recovery/rooting on phones. Although my daytime job is customizing embedded linux, so I have some knowledge
I got my hand on a few Alcatel 5033d devices, on which I want to run a software I created. However, this software needs access the notifications. And Android GO doesn't allow that. So I need to change the low-ram flag in build.prop. If possible I also want to remove the google apps from it and make my app a system app. But for the rest I'm happy, so don't need linageos or anything.
Is there a way to make a custom system.img, based on the original one, with only build.prop changed and load this complete firmware via the original recovery mode? I already saw you could load things via sdcard (adb doesn't work in stock recovery -> authentication required).
I already tried mtk-su (worked on a tablet before), but I guess that flaw is already patched
Something to try
This is from my head so if this doesnt work im sorry
1. install a custom rom.
2. install magisk onto the custom rom.
3. make a copy of the boot image
4. use "Mobile upgrade S" from alcatel to restore your phone
5. flash the backed up boot image from before.
6. if your lucky you may have root on the original system partition.
P.S i would use https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 rom because it doesnt touch the boot partition.