yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Hashcode:
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.

BE WARNED: INITIAL TESTS CAN BE BUGGY AND CAN CAUSE YOUR STOCK INSTALLATION TO BE SCREWED UP. ONLY ADVANCED TESTERS SHOULD TRY THE FOLLOWING TESTS.

Here's the first proof of concept build.

Safestrap 3.5x for jfltevzw.

Installation instructions are very simple:

Make sure you're rooted

Download the APK installer here: http://goo.im/devs/Hashcode/jfltevzw/Safestrap-JFLTEVZW-3.5x.B02.apk

Check md5sum: 1e03735791979cc378b9a6b7247c6239

Use a root explorer or some other tool to install the APK

Once it's open you need to allow root access and then agree to the "Don't Hate Me" clause

Use the "Install Recovery" button

TEST #1: Basic recovery entry functionality (the HIJACK)

Shutdown normally and reboot.

You *should* see the Safestrap splash screen and be able to tap on the "Recovery" button on the lower left corner to enter recovery.

If you don't tap the "Recovery" button, then the boot should proceed normally and every day function of the stock ROM should be normal.

If you enter recovery, don't do anything other than navigate around if you like. To leave recovery, tap "Reboot" -> "System" from the Main menu and you'll reboot.

TEST #2: Reboot to recovery functionality

While in the stock ROM, open the Safestrap APK and use "Reboot to Recovery" button

You should reboot and automatically enter recovery without seeing the splash menu

A NORMAL function of TWRP recovery is to blank the screen after a certain amount of time. By pressing the power button, it should turn the screen back on and show a "slide to unlock" page. The timing for the screen blank can be set under "Advanced" -> "Settings" -> "Screen"

YOU CAN AND WILL BRICK YOUR DEVICE IF YOU DO ANY OF THE FOLLOWING:

Attempt to install any ROMs -- there are no ROMs which will work with this yet. That comes in phase 2.

Backup -- The /data/media store is being counted as part of /data and you'll create a humongous useless backup.

Restore -- This needs to be tested once the other bugs are fixed on an unlocked device where ODIN restore isn't a big deal.

Remember this is a "PROOF OF CONCEPT", however, it's also a full blown recovery and you can do damage to your installation with it fairly easily at this stage.

The reason this is fairly untested at the moment:

Version 3.5x was a complete re-write from the previous version of Safestrap and I have a few bugs left to work out on newer devices w/ /data/media mounts for internal storage.

It's the proof of concept.. and you have to start somewhere. I don't have the device for testing, so you get to be my eyes and ears.

Handling of /data/media where the user can switch between various ROMs is the main buggy portion. You'll notice that the internal storage space is being added to /data in the "Backup" screen sizes for /data. I'll work through each of the screens and fix them up.
[Verizon Samsung Galaxy S 4] Lagoria:
Incredible.
[Verizon Samsung Galaxy S 4] iwearthebelt:
Although I'm still on MDK I've been following your work and am very impressed, especially since you don't even own the device. Great work!
[Verizon Samsung Galaxy S 4] cgdoc519:
Your the best!
[Verizon Samsung Galaxy S 4] Andrew149:
Your awesome! Will this work for us att users?
[Verizon Samsung Galaxy S 4] Hashcode:
This *should* work for ATT users as a proof of concept. However, the final builds will be different as they have the device names and build info embedded into the default.prop for flashing roms that check build.props, etc.
[Verizon Samsung Galaxy S 4] Blue:
Okay so I followed the steps and installed recovery then powered off and started the phone up again and I did NOT see a splash screen. Phone booted up like usual.

---------- Post added at 01:54 AM ---------- Previous post was at 01:49 AM ----------

Test 2, I pressed reboot to recovery and it DID enter recovery. After some time the screen went black and I was not able to anything. After some time then slide to unlock and recovery showed up again and I was able to browse around and shut down my phone with the options.

If you want me to do anything else let me know and I will help you fast.
[Verizon Samsung Galaxy S 4] black_label:
Exactly same results on my device. Both test.
[Verizon Samsung Galaxy S 4] rebel1699:
Same results on AT&T I337. Test 1 failed due to no safestrap splashscreen on multiple manual reboots. Test 2 Success. Rebooted to recovery correctly via safestrap button. Also rebooted normally with recovery menu. Status from safestrap app- "Recovery State: Installed" and "Safe System: Not Active".

Awesome progress Hashcode.
[Verizon Samsung Galaxy S 4] camden07:
Hashcode you are the man

First thing i did this morning. Way to make my day. After install shutdown and reboot does not go to splashscreen or recovery. But from SS apk boot to recovery works perfectly. If you let screen time-out SS locks up a little but it came back right as i almost did a battery pull. There is a light at the end of the tunnle after all.:good:
[Verizon Samsung Galaxy S 4] Anfield8:
Looking at the posts... very encouraging results. Thank you Hashcode for working the ME7 build.

Traveling for work, but looking forward to trying this out.
[Verizon Samsung Galaxy S 4] mmw68666:
Same here but I have hope
[Verizon Samsung Galaxy S 4] roboots21:
Same result as other testers. Shutdown and reboot did not enter recovery. Reboot to recovery from Safestrap entered directly into recovery.
[Verizon Samsung Galaxy S 4] killajoe:
Same results as everyone else. Noticed the back button isn't functional or present. I clicked on advanced and I had to pull the battery to get out. Still awesome work [MENTION=4243514]Hashcode[/MENTION] !! Thank you so!! much
[Verizon Samsung Galaxy S 4] trueagle:
I also had same results
[Verizon Samsung Galaxy S 4] mmw68666:
The back button worked for me
[Verizon Samsung Galaxy S 4] mad3963:
Same results here. No SS splash screen, but boot to recovery works fine.

Back button works here as well.
[Verizon Samsung Galaxy S 4] Roland_D:
I guess nobody looked at the video hash posted a few pages ago.... I'm pretty sure you must install the apk to pass test 1... and reboot in recovery from the app itself to pass test 2...
[Verizon Samsung Galaxy S 4] mad3963:
Uuummm...are you referring to the SS apk? Can't speak for anyone else, but I did install it. Otherwise, I wouldn't have been able to boot to recovery from within SS.

Are you saying you see the SS splash screen, after powering down, then powering back up?
[Verizon Samsung Galaxy S 4] mrjinglesusa:
Same results as others. No SS screen on reboot after shutdown.

Great progress though!!
[Verizon Samsung Galaxy S 4] Roland_D:
Oh then my bad if you installed it... I just tried it no splash scree on test 1 and no splash screen on test 2 but I could access the recovery after black screen like you. From what I was reading it sounded like people just downloaded the apk and tried to reboot their phone! lol

EDIT: I must also add that the Recovery is not uninstallable from SS app... It says uninstalling and all but than it shows as installed anyways.
[Verizon Samsung Galaxy S 4] jlopez1286:
is this only for the Verizon version or can this be use tested on the AT&T version?? Thanks for all your hard work... ;)
[Verizon Samsung Galaxy S 4] SamuriHL:
http://xdaforums.com/showpost.php?p=45311016&postcount=222
[Verizon Samsung Galaxy S 4] Obsidian...:
Read 1 page back. Proof of concept so you can try it out but there's no reason to. Also he said should so no guarantees

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] mmw68666:
All they have to do is read read and read again
[Verizon Samsung Galaxy S 4] jlopez1286:
How did I miss that post?? Ok, thanks.
[Verizon Samsung Galaxy S 4] Obsidian...:
True Story

Who knows? No harm, no foul.

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2

---------- Post added at 10:42 AM ---------- Previous post was at 10:38 AM ----------

Hashcode's phone will be shipped out to him on Friday. So everyone make sure you thank [MENTION=335907]sound-mind[/MENTION] for providing the testing phone for Hash. After I see that the splash screen is working I'll start collecting donations to pay for the device. Cool?

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] bobosir:
Yes. I am reading reading and reading again
[Verizon Samsung Galaxy S 4] mad3963:
No worries. I'm new to SS and TWRP so just wanting to make sure I have all the facts.
[Verizon Samsung Galaxy S 4] jlopez1286:
just installed and can confirm with everyone one else that Test 1 failed but Test 2 was good.. recovery was able to boot..
[Verizon Samsung Galaxy S 4] dadsterflip:
It begins.

On mdk or I would test this also.
[Verizon Samsung Galaxy S 4] Obsidian...:
You can test on mdk

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] dadsterflip:
Hell. Don't have to tell me twice. Lol
[Verizon Samsung Galaxy S 4] Alxoom33:
Houston we've got problems!

Have an encrypted phone. Installed APK reebooted, never saw SS screen saw black Samsung screen and white Verizon screen where it appears to be bootlooping. Never saw andy asking me for decryption code. Tried battery pull, same thing. Help please!!!
[Verizon Samsung Galaxy S 4] SamuriHL:
Oh hell. Only thing I can think of is to restore the system partition through heimdall or ODIN unless someone has a better idea. This will allow a normal boot and should not impact your data partition if done right.
[Verizon Samsung Galaxy S 4] ztkryan:
Restore to stock with odin
[Verizon Samsung Galaxy S 4] equake:
Maybe we should get this guy a S4 for testing. How do we donate to that cause?

I have both the RAZR and BIONIC and have used SS since day one and it is a great thing indeed.
[Verizon Samsung Galaxy S 4] bfmetcalf:
Installed wonderfully!!! Awesome work Hash! Now I just need to know how to build a ROM for it and I'll be set!!
[Verizon Samsung Galaxy S 4] lazer9:
I think that has already in transition via Obsidian's post above...
[Verizon Samsung Galaxy S 4] killajoe:
Absolutely!! I got twenty on it
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
[MENTION=4243514]Hashcode[/MENTION] I tried it on my S4 Active (SGH-I537). I can confirm that Test 1 failed, but Test 2 passed.
[Verizon Samsung Galaxy S 4] bfmetcalf:
This happens on my verizon S4 as well, if i just reboot it doesn't show a splash screen, but i can reboot to recovery through the app
[Verizon Samsung Galaxy S 4] deadenz:
Has this been confirmed working on at&t sgh I337 with mf3 update?
[Verizon Samsung Galaxy S 4] manbat:
From my understanding this is only a "proof of concept" test...not fully functional. Just a boot test...
[Verizon Samsung Galaxy S 4] SamuriHL:
This. And Hashcode is aware of the results. Give the man time to work on it. :)
[Verizon Samsung Galaxy S 4] mbaran:
Confirming that test 1 did not work, but test 2 worked flawlessly. I did notice though on test 2 my screen went dark and I had to hit Power On to see the TWRP screen.
[Verizon Samsung Galaxy S 4] mad3963:
Same here, regarding the screen going dark and having to hit the power button. Forgot to mention that.
[Verizon Samsung Galaxy S 4] rebel1699:
Yes. Tested it myself. Results for AT&T variation are perfectly in line with the verizon model.
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Here is video of it on the SGH-I537: http://www.youtube.com/watch?v=FVm5fJq5RuI
[Verizon Samsung Galaxy S 4] :
Let Hash do his thing. I'm sure he already knows what's wrong with the "proof of concept," chill people, please.
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
Close

Sent from my SAMSUNG-SGH-I337
[Verizon Samsung Galaxy S 4] :
Similar results with the Verizon variant.
[Verizon Samsung Galaxy S 4] Hashcode:
OK! I have the proof of concept ISSUES list on POST #2:

http://xdaforums.com/showpost.php?p=45185931&postcount=2

Lemme dig in and fix some of these before the next round.
[Verizon Samsung Galaxy S 4] Hashcode:
I wish you were on MDK so I could get a bootlog of what's going on. :/

If I can borrow a device, i'll enable encryption and see where it's failing. Sorry about that.

Adding to the OP for users w/ encryption to stay away for now.
[Verizon Samsung Galaxy S 4] Roland_D:
I don't want to be annoying... but it's the BOOTLOADER that won't uninstall... The APK uninstall normally.

If it was assumed I apologize. :P

Also the power button WORKS. After Samsung black screen the screen turns black because it's off... pushing power button turns it on and you are prompted to the bootloader with the 'slide to unlock' screen.

Back button works on and off for me...
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
I'll let you borrow my device but its AT&T MF3 baseband. I live out in the riverside area

Sent from my SAMSUNG-SGH-I337
[Verizon Samsung Galaxy S 4] Hashcode:
I'll clarify in my ISSUES list:

- "Uninstall Recovery" button doesn't complete as expected. Still shows: INSTALLED

The screen blanking feature in recovery is working as intended if the device can be woken w/ the power button and the "slide to unlock" screen is shown. I thought someone mentioned they had to battery pull because they couldn't re-wake the device.
[Verizon Samsung Galaxy S 4] killajoe:
I mentioned I had to pull the battery because the back button didn't work on one of the screens
[Verizon Samsung Galaxy S 4] kwelch08:
If this makes it to the Att devices I'll be more than happy to make a donation. Just need to know where to go to make it..
[Verizon Samsung Galaxy S 4] Hashcode:
When you say the "back" button are you referring to this in the lower right corner? Or are you referring to another button?
[Verizon Samsung Galaxy S 4] Hashcode:
Do you remember which screen? You can also use the "Home" button to go back to the main menu and then use "Reboot" from there.
[Verizon Samsung Galaxy S 4] Venom0642:
Confirmed as well works on AT&T MF3.

Sent From My Galaxy S 4 SAMSUNG-SGH-I337 Running On New Deadly Venom v8.0.0

---------- Post added at 11:08 AM ---------- Previous post was at 11:05 AM ----------

Opps my bad wrong Quote but does work on AT&T MF3

Sent From My Galaxy S 4 SAMSUNG-SGH-I337 Running On New Deadly Venom v8.0.0
[Verizon Samsung Galaxy S 4] TNS201:
Verizon on ME7

Test 1 Failed, no way to get in on boot

Test 2 Passed, "boot to recovery" works
[Verizon Samsung Galaxy S 4] Hashcode:
For the purposes of quick tests with direct users, I've established a channel: #safestrap on IRC freenode.net.

Feel free to jump in and discuss issues... I may or may not be at the keyboard tho.

I'll add the IRC channel to the OP.
[Verizon Samsung Galaxy S 4] twizzlejr:
How can I tell if my device is encyrpted or not
[Verizon Samsung Galaxy S 4] Hashcode:
Settings -> "Security" -> "Encrypt phone" is where you enable phone encryption.

Settings -> "Security" -> "Encrypt SD card" enables encryption for the SD card.

Not sure which setting (or both) is causing issues at the moment.
[Verizon Samsung Galaxy S 4] Inigo Montoya:
This is so exciting. Thanks for all the hard work Hashcode.
[Verizon Samsung Galaxy S 4] Surge1223:
I cant post on the irc channel since im not home anymore but im on mdk and got the same results as everyone else test 1 fails test 2 passes. A few observations, reboot menus' system button would only work if I hit the home button and went back into reboot options and hit system, it doesnt work on the first try. Also the black screen before reboot takes a few seconds longer than normal (this is from 3 or 4 reboots after initial safestral install) Im not complaining, just trying to help. Thanks Hash.
[Verizon Samsung Galaxy S 4] msterwolf:
[MENTION=4243514]Hashcode[/MENTION] I posted a video of me running test #2 on youtube. But since I'm a new user here on xda and I don't have more than 10 posts, I am not allowed to post any outside links. So if you go on youtube and search "reboot to recovery safestrap s4" my video will be the first one on the list.
[Verizon Samsung Galaxy S 4] stevey500:
Test-

Device: AT&T Stock & rooted MF3 i337 S4

Boots to recovery without a problem when restarted from APK.

Shows no splash screen from a reboot or shutdown-power on what so ever.

Got risky and successfully completed a system-only backup and completed successfully.

I do confirm that internal storage is showing on "Data" partition. Data partition 8+gb

Navigating and touch response is a bit laggy and buggy.

Thanks for the really awesome work Hashcode.
[Verizon Samsung Galaxy S 4] kadoozie:
Test #1 and #2

Test #1 Fails when rebooting anywhere outside of the apk. Working every time I reboot from apk though.

Test #2 Passes without a problem.

Observations:

-Rebooting to recovery option from Safestrap takes to Samsung download mode not Safestrap, assuming this is intended although different than the typical TWRP.

-Rebooting to download option works correctly.

-As mentioned, from the apk, removing recovery does not toggle Recovery State from installed to uninstalled, nor does it actually remove the recovery. I can still restart to recovery after uninstall process.

-Time is offset although DST and Time zone is correctly set in recovery.

Thanks for your hard work Hashcode!
[Verizon Samsung Galaxy S 4] roboots21:
Is there a manual way to remove the recovery? I have a replacement device coming tomorrow and am going to Odin the current one back to stock when the new one arrives and want to make sure it is wiped clean of any and all root remnants before I ship it back.
[Verizon Samsung Galaxy S 4] bfmetcalf:
Played around with this a bit. It looks like reboot recovery from within safestrap takes you to the stock recovery. I also created a ROM Slot and it appeared it worked just fine, at least it said it created it successfully.
[Verizon Samsung Galaxy S 4] sokrboot:
FWIW I got the same results as most.

Test 1. Fail.

Test 2. Win.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] Hashcode:
If you Odin the current one back to stock, then recovery gets erased with it.

However, if you need to manually remove Safestrap (which is not working currently in the APK). Do the following from adb shell:

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

All set.
[Verizon Samsung Galaxy S 4] mrro82:
Works as intended on my AT&T S4. You're what xda is all about hash. Thanks again. Cant wait to flash a rom on this thing finally.

Sent from the other side of the Milky Way with my S4.
[Verizon Samsung Galaxy S 4] scottusa2008:
Due to being over tired and formatting the wrong thing with TWRP (won't be doing that again while tired, lol) I had to completely restore my phone to stock.

All I did was flash the stock MDK image via Odin (this also removed the custom recovery). After that the only thing left to do would be a factory reset or two within the stock recovery and that should do the trick for ya.
[Verizon Samsung Galaxy S 4] Alxoom33:
Thanks, based on Obsidian'a kind advice and followup with HC and Sam, I started downloading the latest ME7 image for Odin 3. DL took a lot of time and failed, had to leave to visit family in Mass. So I activated my old Bionic, had to go to VZ store for a new sim card, and reactivated the old Bionic with FJ and SS 3.11, still have my car dock ;) Worked great, still encrypted...I'll try again with Odin this weekend, need to do more reading and find link to update Odin. have v 3.7? I saw there was a v 3.7z, but not sure if it the latest. If anyone can turn me on to some links, to read/dl, would greatly be appreciated. Should have been more careful testing with an encrypted phone. I guess the encryption prevented SS from starting up and the phone went into a bootloop at the Verizon splash screen (after the black unlock. Never got my encryption code screen with Andy.:(
[Verizon Samsung Galaxy S 4] SamuriHL:
ODIN failed?? What did it fail on if you remember? That seems....ungood.
[Verizon Samsung Galaxy S 4] Alxoom33:
You would know if you were encrypted. I had to encrypt because of the requirements for our Enterprise e mail service. Basically, the system administrators require the ability to have the phone encrypted and to be able to wipe it if it falls into the wrong hands...Muhhaha!!! Big Brother is watching.

---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------

---------- Post added at 09:09 PM ---------- Previous post was at 09:05 PM ----------

Thanks Sam, that certainly would not be good. No, No, no... the 1.4+Gig downloads of the ME 7 image failed. Not Odin!
[Verizon Samsung Galaxy S 4] SamuriHL:
OHHHHH. I misunderstood. Ok, well, can't help you on the download. LOL :) Too bad someone with the ME7 image couldn't make you just a system odin flash. Would save you a large download and would make it so you don't have to flash everything which shouldn't be necessary. Just the system img should suffice.

---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------

I'm downloading the ME7 factory image now. I'll see if I can extract the system img and make a new ODIN tar md5 for you and upload it to my MF account. Would that be helpful?
[Verizon Samsung Galaxy S 4] Alxoom33:
That would be awsome. I would need to figure out how to set up Odin to just flash the System partition. I looked around a bit this morning on google/xda, but was not satisfied I knew what I was doing, so decided to activate the old Bionic and wait until I have a bit more time to read and learn. Had to leave for Mass to visit my Mom in the Cape and needed a working phone for work. I will try to figure this out with a little more time, I don't want to make my soft brick a hard one ;)
[Verizon Samsung Galaxy S 4] SamuriHL:
Make sure the drivers are installed, boot up the S4 in ODIN mode, load up ODIN, make sure only auto-reboot is checked, hit the PDA button, load the tar md5 you're trying to flash, and have at it. I'm using ODIN 3.07 on my GPE and had to flash our handmade factory image a few days ago. Worked fine. Should work for you with the right tar md5. I'll get it created as soon as the factory me7 image is done downloading. 1.7 gigs? OMG. Bloat much? LMAO! :D 2 minutes to finish. I like fiber. :D
[Verizon Samsung Galaxy S 4] Alxoom33:
THANKS SAM, YOUR THE BEST. WILL DL NEW ODIN ON MY TRAVEL LAPTOP (V. 7 IS ON MY HOME COMPUTER.
[Verizon Samsung Galaxy S 4] SamuriHL:
The system img tar md5 is as big as the full firmware image. LOL. But's uploading to my MF account. I'll pm you a link when it's done. It's not quick.
[Verizon Samsung Galaxy S 4] Alxoom33:
Downloaded Odin v 3.09, unzipped and DL ME7.zip factory image. However, will wait for your TAR System file. Carfully, hopefully it will work. Thanks for your help and advice.
[Verizon Samsung Galaxy S 4] SamuriHL:
3.09 eh? Guess I need to upgrade. :)
[Verizon Samsung Galaxy S 4] Alxoom33:
Yes, LOL. I DL'd v. 3.07 in May!

Do you have my gmail address?
[Verizon Samsung Galaxy S 4] SamuriHL:
No I don't but I've got a pm ready to go to send you as soon as my upload is finished. It's my personal MF account so it should be pretty quick for you. Seriously hope this helps you out!
[Verizon Samsung Galaxy S 4] Alxoom33:
Thanks man, as always you are a lifesaver.

---------- Post added at 10:37 PM ---------- Previous post was at 10:28 PM ----------

Rearead your earlier post, bloat/Fiber, LOL :)
[Verizon Samsung Galaxy S 4] SamuriHL:
Just doing what I can to help. And yea, the GPE image is significantly....smaller. :D
[Verizon Samsung Galaxy S 4] corey6969:
Works on AT&T MF3

I to am just confirming it works on my sgh-i337 (Galaxy S4 AT&T), same as everyone else, no splash but reboot to recovery works!!:highfive: Even tho its been said it doesnt work im almost to tempted to start flashing roms and playing with the recovery even tho i'm told not to:D
[Verizon Samsung Galaxy S 4] Galaxys4bean:
Test 1 fail

Test 2 pass

Awesome work hash