Related
SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the APK Installer:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Targa" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7.0.0 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.
SElinux support in recovery (1st boot won't take so long)
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/20] (3.60) update to TWRP 2.6.3.0 base recovery
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
SCREENSHOTS (showing slightly older TWRP base)
First! Thanks Hash!
Nice one. Will be checking all this out later just got a free bionic
Sent from my DROID BIONIC using XDA App
What's the correct procedure for updating versions of Safestrap? Do I need to be in unsafe system or uninstall first or ?
Awesome, Thanks!
Love this app/recovery. Thanks!
Sent from my BIONIC using Tapatalk
Does anyone have suggestions for when switching back to the primary, and it errors out on original data restore?
I did do the proper backups and normal toggle. The original back up refused to boot. Even initiate boot.
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Suggestions on what I may have done wrong, or a less time consuming remedy should it happen again?
Apologies if I left something out.. typed while putting the mag stripes on iTunes cards... only 600,000 to go... weeeeeee
And thanks fir your hard work and great tool for the bionic, Hash.
Sent from my DROID BIONIC using xda premium
I've never had that problem. Are you using your internal or external sd card for safe mode? The internal is faster and less likely to have problems.
Sent from my DROID BIONIC using Tapatalk
Does Bionic Bootstrap have to be removed/uninstalled before installing Safestrap? Can BB just be frozen?
Thanks.
EDIT: Okay, I see it does need to be removed.
cappiez said:
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Click to expand...
Click to collapse
I've seen this happen a handfull of times, most of which were due to a nearly full /emmc partition (internal SD card).
When you hard toggle and restore the Eclipse back up here's what happened:
- The "/system" backup goes back onto your /preinstall partition (where it also lives in 2nd-system) -- The only item which will get restored to your primay system is a backup of "/systemorig". And that's important because if you were to restore the 2nd-system back to the original system.. You'd brick because of partition renaming, etc.
- /data and /cache are restored normally.
You did the right thing in hard toggling and then advanced restore your data from a previous backup. Just know that your 2nd-system data wasn't stashed when you do the hard toggle. So there may be an issue when you want to go back to the 2nd-system.
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
JohnnyAn said:
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
Click to expand...
Click to collapse
I've seen this happen when Superuser has just been updated. It's like Safestrap thinks it has su priv, but Superuser never gives it out. Or something odd. I would try removing and reinstalling Safestrap so that Superuser can re-add it to the "allowed" list.
waffleb051 said:
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
Click to expand...
Click to collapse
Safestrap is the recovery system that lets Bionic users utilize an alternate recovery firmware to install alternate ROMs. That's what this entire thread is about.
It almost sounds like you trying to make your backup through ROM Manager. ROM Manager looks for Clockwork Recovery (that gets installed with Bionic Bootstrap and not Safestrap). Safestrap is an entirely different system that ROM Manager won't recognize.
Make sure you reboot your phone and manually enter into Safestrap so that you can make a backup. It will work properly that way.
http://youtu.be/UbGE_xxWSZ4
if it helps anyone, here's a video i made installing Safestrap 1.7 and ICS4Bionic.
Thanks Hashcode for all you've done!
I am wondering if i safestrap and want to go back to koush's bootstrap how do i go about it and can i recover the space used for the 2nd system?
Never mind i figured it out.
Would it somehow be possible to load a stock 5.5.886 image with kernel and everything stock like using the full 5.5.1_84_DBN-55 image? Then being able to update it through the upgrade path then flash it to the normal phone system? I mean using the 2nd partition created by safe strap to do all the steps before flashing to the normal phone partition.
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
twinkyz1979 said:
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
Click to expand...
Click to collapse
Safestrap does not interact with CWM backups from the other bootstrapper.
projektorboy said:
Safestrap does not interact with CWM backups from the other bootstrapper.
Click to expand...
Click to collapse
Although you can still copy the backup from CWM to safestrap and still restore it and it will work. i have done this.
I Loose boot after safe mode enabled
I rooted the .886, then used the OTA and lost root.
I had to factory reset so i could R3L3AS3dRoot and 4ever root, I then used the OTA to come from .886 system to the .893 system.
I am rooted and have the recovery state installed.
When I install the safe strap I loose the ability to boot, I then have to uninstall it to gain boot once again.
EDIT:
Safe strap enabled, had to flash a custom rom over the one which wouldn't boot. I'm sure it would work if i reflashed stock over the safestrap.
Thank you!
I'm finding Ultimate N7000 XXLSC slightly slow and buggish. I want to change to the ParanoidAndroid ROM, would this be a better move?
If so, what are the steps to changing to ParanoidAndroid from Ultimate N7000 XXLSC. I have the Philz Touch 4 kernel installed.
I have already downloaded: gapps-jb-20121011-signed and pa_n7000-2.21-13OCT2012-162120
Advice would be appreciated....
Backup the apps using titanium backup if you want them on pa too.. Go into recovery make a nandroid backup just in case no go into advance there is a option clean the phone for install new rom(i don't remember the exact name but by this you can address it correctly) now intall the paranoid and flash the gapps and you are done
Sent from my GT-N7000 using Tapatalk 2
Just to add to abhi... Ultimate rom has an older version of Philz kernel which may cause problems while installing the PA rom.. so either update the kernel to 4.35 version or use a CM kernel..
andrew.southafrica said:
I'm finding Ultimate N7000 XXLSC slightly slow and buggish. I want to change to the ParanoidAndroid ROM, would this be a better move?
If so, what are the steps to changing to ParanoidAndroid from Ultimate N7000 XXLSC. I have the Philz Touch 4 kernel installed.
I have already downloaded: gapps-jb-20121011-signed and pa_n7000-2.21-13OCT2012-162120
Advice would be appreciated....
Click to expand...
Click to collapse
I did just that last week. the steps i took were:
1- flash CM10 kernel (important. Philz can cause trouble)
2- reboot recovery, this will bring you right back to recovery. you won't have touch anymore (CM10 kernel comes with CWM 6 recovery)
3- factory restore
4- on mounts and storage, format /system /data and /preload
5- flash paranoidandroid
6- on advanced screen, wipe dalvik cache
7- reboot
8- restore user apps and data from titanium (you did a backup before starting, right ?)
9- DO NOT restore system apps or data, except call log, bookmarks and SMS messages, and this ones, restore from XML
10- DO NOT restore touchwiz apps, like SNote. Titanium will get stuck while doing it, and they won't work anyway.
Roagnow Global
Nerdeiro said:
I did just that last week. the steps i took were:
1- flash CM10 kernel (important. Philz can cause trouble)
2- reboot recovery, this will bring you right back to recovery. you won't have touch anymore (CM10 kernel comes with CWM 6 recovery)
3- factory restore
4- on mounts and storage, format /system /data and /preload
5- flash paranoidandroid
6- on advanced screen, wipe dalvik cache
7- reboot
8- restore user apps and data from titanium (you did a backup before starting, right ?)
9- DO NOT restore system apps or data, except call log, bookmarks and SMS messages, and this ones, restore from XML
10- DO NOT restore touchwiz apps, like SNote. Titanium will get stuck while doing it, and they won't work anyway.
Click to expand...
Click to collapse
Thanks, it worked. Now I'm having issues with the internet. It works via wifi but the modem (I think it is that) seems not to be working. The stock modem that came with Paranoid isn't working. I tried installing XXLSC and the XXLSO modens but none are connecting to the internet.
I make and recieve sms and calls? Is there something Im overlooking?
PA rom doesnot come with modem.. it used the modem already installed on the phone, check your APN settings,
Tried ROM Manager backup of factory ROM.
Now, I power on and get CWM recovery. Choosing reboot always returns me
to CWM recov. I read every thread in this forum that refers to
loop, brick, etc. I have various backups, but I don't know what they
are worth, best way to use them. How to get out of the boot loop?
Best outcome would be to recover my last stable state. Factory reset
would be ok. Hardbrick would be a drag.
* Bought factory unlocked G-ST6500D (no vendor) in Spain.
* Have current non-root backups of contacts, sms, media, calendar, etc. on
laptop.
* Installed CWM v5.0.2.8 with Odin (three yellow boxes appeared in odin,
FWIW), and rooted. Froze bloatware listed by some people as safe, but
did not delete any factory installed software.
* Wanted to have a stock ROM backup before I did anything else. It's
not clear to me whether it is best/possible to download one or create
an image from my device. Started reading/trying backup apps, but I
don't really know what each one does.
* Did a full backup, apps + data, to extSD, and copy to laptop with Titanium
backup (free). This wrote >1000 files.
* Did most complete (as best I could tell) backup to extSD and laptop
with Online Nandroid app. This wrote boot.img, cache.ext4.tar,
data.ext4.tar, nandroid.md5, recovery.img, system.ext4.tar. Can these
be used to restore ?
* Tried to backup the ROM with ROM Manager app, but could not find an
option to backup to ext SD, only int SD. There was only 200MB free, so
I knew this would fail. I choose this anyway, hoping it would realize
there is not enough space and offer to change the path. The phone
rebooted into CWM and began a backup. After a few minutes, it printed
an error message and told me where a log was written, and rebooted
into CWM recovery. I tried rebooting, holding buttons, removing
battery, etc. Always returns to CWM recovery. Tried the 'backup and
restore' menu hoping it would give info on the backup. Instead, it
immediately started another backup, this time showing 1GB intSD
free. This backup reported success, then reboot into CWM recov.
* Since then, from CWM, I did 'wipe cache partition' and 'wipe davlik
cache'. Did not yet try factory reset.
* Show log ends with
"skipping exectuion of extendedcommand, file not found"
I read that sometimes it is possible to exit a boot loop without
flashing anything. If that is not possible, I guess I should do
factory reset. If that does not work, then I guess I should try
restoring something somehow: Use CWM recovery to recover nandroid
backup from extSD? Or install something via Odin ? For any solutions,
I am more comfortable doing things from linux than MSWin, but I think
that is not possible. Do I have to race to solve this before the
battery runs out?
Thank you for reading.
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
midzan21 said:
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
Click to expand...
Click to collapse
Thanks. I just figured that out after a several hours of reading. Finally saw stories on the thread
introducing CWM 6.0.3.3 of people who never flashed a ROM and still had boot loops.
I was on the wrong track because I assumed it was the filled up int. SD causing the
problem. I still have to fix that, but my phone is running. It would be nice if ROM Manager or CWM calculated the space
needed and refused to start if insufficient. But, I understand that there are few good devs and much to do.
Hi all, I thought I understood rooting etc. when had my Samsung S5, HTC Desire etc. but a bit stumped here.
I have a rooted (rootgenius) Ascend P7 (Kernel - 3.0.8-00485-ge6e6a9b, EMUI 3.0) that I am happy with. Looking to use Xposed Installer to make some tweaks but cannot seem to backup beforehand...
I've backed up all apps in Titanium Backup. When I go to reboot into recovery (ROM manager) I get the EMUI screen with 3 options (Reboot System Now, Wipe data/Factory Reset, Wipe Cache Partition). ROM manager also allows me to backup, and says that there is a current backup (sdcard/TWRP/backup) but this is blank in a file explorer and when I click on it on the phone, it takes me to the same EMUI screen.
How do I install CWM or TWRP so I see them in recovery and can backup the system in a way that is restorable (guessing that Titanium Backup isn't that useful if stuck in bootloop for example).
Thanks
Any ideas on this as I would love to start using XposedInstaller etc. but only with this backup, many thanks.
Have you tried this yet?
http://forum.xda-developers.com/showthread.php?t=2793247
I would like to keep everything else the same on my phone.
- I don't know if that means I'll have to backup/reinstall everything, if that happens automatically, or what.
- I have the following installed: TWRP 3.4.0.0, Titanium Backup Pro, Frija, Odin, ADB (?)
I currently have "ALEXNDR.N960FXXU6FTJ5" that I got here (based on Android 10)
I think it was from this thread: https://forum.xda-developers.com/t/...ase-v7-4-dex-gear-encryption-support.3847061/
If I want to follow those instructions, should I:
1) do a complete TWRP backup *first*?
2) follow the instructions to update the ROM
3) then restore from Titanium Backup?
As I understand it, the TWRP backup is *ONLY* if I want to restore the entire "disk image" and revert back to the ROM I have now, right?
You can use TWRP restore only if you mess something while flashing kernels, magisk modules, Xposed modules, etc .. it is also useful in your first OEM unlock to preserve vendor and ODM images so that you won't have to flash stock ROM again if something go wrong.
If you are asking about restoring apps, SMS and call logs, I highly recommend swift backup. Not for settings though. Personally, I stopped using titanium backup years ago since it is deprecated and last update was in 2019.