Android OS Forum banner
1 - 16 of 16 Posts

·
Developer
Joined
·
260 Posts
Discussion Starter · #1 ·
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.

CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.

CURRENT PROJECT STATUS:

Testing ROM boot from virtual slots

WHAT IS SAFESTRAP?

Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
  • Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
  • You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
  • Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/

HOW DO I INSTALL SAFESTRAP?
  • Requirement: Root
  • Requirement: Allow APK install from Unknown Sources
  • Download the Safestrap APK
  • Find the APK using a Filemanager tool and open it on your device, then click "Install".
  • (If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
  • Once installed, open up the Safestrap application as you would any other app.
  • Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
  • Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
  • From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
  • That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?

During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.

DOWNLOADS:

CONFIRM THAT YOU ARE USING AN VERIZON WIRELESS SAMSUNG GALAXY S4 (NOT THE ACTIVE MODEL)
LATEST FILE: Safestrap-JFLTEVZW-3.5x-B08.apk
Mirror 1: http://goo.im/devs/Hashcode/jfltevzw
Mirror 2: http://downloads.crackflasher.com/?dir=Devs/Hashcode0f/jfltevzw

ALSO DOWNLOAD THE ME7 KERNEL MODULE .ZIP (FLASH THIS AFTER THE ROM):

HOW TO MANUALLY REMOVE SAFESTRAP:

Enter adb shell from your pc:

su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system

As of version 3.5x, Safestrap Recovery is now based on TWRP 2.6.1.x. For more on TWRP you can visit their website: http://www.teamw.in/

WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.

CURRENT TESTS:

TEST #1: Hijack stability to enter recovery on every boot. RESULT: PASS
TEST #2: Reboot to recovery functionality RESULT: PASS
TEST #3: Recovery removal leaves device in clean state RESULT: FAIL
TEST #4: ADB access from recovery RESULT: PASS
TEST #5: ROM-slot creation RESULT: PASS
TEST #6: Backup stock ROM RESULT: PASS
TEST #7: Restore stock ROM RESULT: PASS
TEST #8: Initial 2nd-init ROM installation on rom-slot RESULT: PASS

For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
 

·
Developer
Joined
·
260 Posts
Discussion Starter · #2 ·
MAIN MENU:
  • Boot Options: This area is for managing your virtual ROM-slots. You create a new ROM-slot by clicking on one and if it doesn't exist you will be prompted to create it. Follow the on-screen guides. Once a ROM-slot is created you select that slot to activate or delete it. Under each ROM slot (once created) you can:
    • Activate: Makes the chosen ROM-slot the "current" one, where almost all of the features of TWRP affect that slot. This will also be the ROM that is booted.
    • Set Nickname: For convenience you can set a small name for each ROM-slot. This is limited to 10 characters as it will eventually be added to the beginning of backup names. This name is shown on the ROM-slot button once it is set.
    • Check FS: This performs a file system checks on the ROM-slot and fixes any errors found.
    • Delete: Delete the ROM-slot files (disabled if the ROM is active - please choose another ROM-slot to activate and then come back) USE WITH CAUTION, THERE'S NO GETTING THESE BACK UNLESS YOU HAVE BACKUPS.
  • Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
  • Backup / Restore: This should be self-explanitory, but you use these options for making backups of the currently selected system. Or restoring a previously made backup to the currently selected system (regardless of where you backed it up from). DON'T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
  • Mount: You can manually manage mounts here. NOTE: the "system", "data" and "cache" mounts will use the currently selected ROM-slot.
  • Wipe: Manually erase portions of the device. NOTE: You only have 1 internal and 1 external SD card. These are not "virtual" if you erase them. They are gone. Use with caution. Wiping the "system" when "stock" ROM is selected will try and keep the Safestrap hijack in place.
  • Advanced:
    • Copy Log to SD: Experienced something odd and want to report it? DO THIS and include the log when you send me the report. Otherwise, the recovery.log will disappear when you reboot.
    • Fix Permissions: This can fix up ROMs which are displaying odd force close issues, etc. You will probably never need to do this.
    • Partition SD Card: You can add ext3 partitions to the external SD card if you want. I'm not sure we have much of a need for this on our devices.
    • File Manager: This works like any other file manager inside Android. You can thank the TWRP people for this, because it is quite possibly one of the best features I've ever seen in a recovery.
    • Terminal Command: Also very handy for those once in a while moments when you have to do something via terminal but don't have adb handy. USE WITH CAUTION
    • Settings:
      • Here you can turn on and off signature verification of .zip files
      • Force MD5 sum checks on .zip files prior to flashing
      • "Use rm -rf instead of formatting" this may or may not be checked in Safestrap, but the key partitions which are signed and cannot be truely formatted will automatically use this feature
      • There are a few other checkbox options in here. Please know what you are doing.
      • Simulate most actions for theme testing. If you have this checked, Safestrap/TWRP will not perform most actions but show the dialog boxes so you can review theme elements. If you turn this on, it STAYS ON till you turn it off. And will show "SIMULATING ACTIONS" up top.
      • Set the Time Zone (use "Set Time Zone" button after choosing which time zone you want)
      • Restore Defaults. Use this to reset all options back to default as it came when you installed for the first time. Does not erase backups or ROM-slots, tho it might change the active slot.
  • Reboot: Choose from 2 options for rebooting "System" which performs a reset/reboot of the device and "Power Off" which turns the device off.
 

·
Developer
Joined
·
260 Posts
Discussion Starter · #3 ·
KNOWN ISSUES:
  • When doing a "Wipe" an error shows regarding /cache. Seems like /cache is wiped correctly, but the error has to do with SELinux [ WILL FIX LATER ]
  • Uninstall from APK isn't working correctly.
CHANGELOG:
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
 

·
Registered
Joined
·
136 Posts
So this means I can put roms on this useless ME7 phone?! A dream come true! Thank you! Thank you! Thank you! With that being said...

What ROMs work with bootstrap or is it safe to assume that all current Verizon ROMs will work?
 

·
Android Aficionado
Joined
·
196 Posts
How can I tell if I need to use this with my GS4 or if I can root with some other method to allow flashing ROMs?

I am switching from my Galaxy Nexus to a Verizon Galaxy S4 but want to ensure that I can root and flash ROMs before I make the switch.
 

·
The Dude
Joined
·
301 Posts
You'll need to use this if your GS4 is new & has updated OS. Be sure to get the 32GB GS4 as you'll need more room to install ROMs
 

·
Registered
Joined
·
2 Posts
I installed hyperdrive 9.1 final (stock kernel option) using safe strap. The only problems I've encountered were data drop outs when a call or text message is sent/received, and unable to toggle wifi. Im not sure if its a rom issue or not as safestrap is the only method I can use to install.

Sent from my SCH-I545 using Tapatalk 4
 

·
The Dude
Joined
·
301 Posts
Include every step you did to get to that point. Be detailed..

What program did you use? How did you do it, etc..
 

·
Registered
Joined
·
2 Posts
SOLVED - After many, many tries I was able to get past Odin mode and my phone rebooted. I still need to figure out how to correctly uninstall Safestrap and unroot, but I'm going to do some searching and hopefully I'll find instructions for that.

I have a Verizon Galaxy S4 ME7 build that has been rooted with Safestrap and has been working fine. Today I wanted to unroot it, so I mistakingly used Odin v. 3.07 to flash the No-Wipe factory image (I545VRUAME7.tar.md5). This failed in Odin, so I took out the battery and tried to turn the phone back on, and got the download screen with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Unfortunately, I did all of this before uninstalling safestrap and I don't know if that's the issue. I can still get into Odin mode, but don't know what to do from here. Please help! Thanks!
 

·
Registered
Joined
·
2 Posts
Can someone provide a link to complete, detailed instructions on how to unroot a verizon galaxy s4 (ME7 build) that has Safestrap installed? I tried flashing the ME7 factory image via Odin and that failed; however, I didn't uninstall Safestrap first, so I don't know if that was the issue or not; however, my phone was locked up for hours, so I don't want to try again until I'm sure I have all of the correct steps needed. I've spent the past 2 days searching forums and have found a lot of information, but haven't found complete start-to-finish instructions on the whole process. Would really appreciate if someone could point me in the right direction!

Thanks!!
 

·
The Dude
Joined
·
301 Posts
It's in beta phase right now. If or when it does become stable, you'll know :)
 
1 - 16 of 16 Posts
Top