yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Hashcode:
I've been keeping a list of open issues in the #2 post so that users can see what I'm working on before the next test.

http://xdaforums.com/showthread.php?p=45185931
[Verizon Samsung Galaxy S 4] kwelch08:
On a Att I337 running MF3 confirming it works the same as everyone has stated.
[Verizon Samsung Galaxy S 4] Little Bigboy:
I'm reading thru this thread but still dont understand what this does. Maybe im a little slow ?
[Verizon Samsung Galaxy S 4] haremmon:
http://xdaforums.com/showpost.php?p=45185924&postcount=1

Under "WHAT IS SAFESTRAP?"
[Verizon Samsung Galaxy S 4] baling:
Recovery reboot works for me! Love the progression. Keep up the good work hashcode!
[Verizon Samsung Galaxy S 4] thunderbls:
Its a christmas miracle! : )
[Verizon Samsung Galaxy S 4] darkuni:
I see "Encryption Enabled" ... so I guess I don't get to play?

How does one turn that off? I'm VERY interested in playing :)
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Frankly, there isn't much you can do with SS at the moment as there aren't any ROMs available and the apk is still in early stages. At this point, you'd be better off to stay encrypted (assuming your device is that way for a reason), leave SS alone, and wait for a future release. Hopefully Hashcode will have a fix for SS by then. But that's just my 2 cents.
[Verizon Samsung Galaxy S 4] thunderbls:
Ageed... its exciting but no need to rush.
[Verizon Samsung Galaxy S 4] ups2525:
thanks Hash!!!!!!!!!!!!!

I have been glued to this thread, what a relief to see you at work on the S4, thanks Hash!!!!!!!!!!!!!
[Verizon Samsung Galaxy S 4] HORiZUN:
Me too! Installed Safestrap on an AT&T S4 with MF3 firmware. Bring on the ROMS and make HashCode president!

Today was a great day for the S4. Thanks, Hash!
[Verizon Samsung Galaxy S 4] warchyld77:
So you need special roms for this?
[Verizon Samsung Galaxy S 4] killajoe:
I'm guessing if you are encrypted then there has to be a password and if you didn't encrypt it. I can only assume one it is a work phone or two you didn't buy your phone brand new or three it's not your phone. My phone asks me for a password to encrypt and I can only assume if I choose to unencrypt my phone I would need that password.
[Verizon Samsung Galaxy S 4] HORiZUN:
Thanked the post?

Yes, roms will need to be ported to work with safestrap. Porting is pretty straight forward. The forums are about to explode with roms for safestrap. Mark my words. There WILL be roms.
[Verizon Samsung Galaxy S 4] warchyld77:
Thanks HORiZUN
[Verizon Samsung Galaxy S 4] ups2525:
Yes...Welcome to these United States of HashCode... LMFAO!
[Verizon Samsung Galaxy S 4] HORiZUN:
This is the biggest breakthrough in development we've seen in months... Well, since they patched loki. I'm so glad we have such a talented coder working so hard on this. HashCode, did you manage to get your hands on an S4, yet? I'll send you mine (seriously) for your developing.
[Verizon Samsung Galaxy S 4] blackra1n:
Is this what its suppose to look like when its not encrypted?
[Verizon Samsung Galaxy S 4] yankeesfan714:
This will work for i537 as well right?

Thanks guys n gals

Sent from my SAMSUNG-SGH-I537
[Verizon Samsung Galaxy S 4] Protibus:
Yes to decrypt the phone you will need to know the password.
[Verizon Samsung Galaxy S 4] killajoe:
I wasn't asking a question.. I know that and stated that in y post. Sorry if didn't say it right and that was misunderstood
[Verizon Samsung Galaxy S 4] DxGxL:
kexec

Will this also include a kexec method to boot custom kernels or is that a development item for the future?
[Verizon Samsung Galaxy S 4] HORiZUN:
I'm just going to stay away from encryption till SS works with it.. Hell, I may never use it.
[Verizon Samsung Galaxy S 4] mmw68666:
Amen my brother from another mother
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
There are some things that are a bit different and some changes will need to be made. We are hoping that Hashcode will be willing to help us out.
[Verizon Samsung Galaxy S 4] yankeesfan714:
If he is willing to do it and he needs one to mess with I can send him mine on a loan maybe

Sent from my SAMSUNG-SGH-I537
[Verizon Samsung Galaxy S 4] sokrboot:
That's a future possibility...no kexec yet.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
We have a bounty going in the S4 Active forum. You can post your offer there.
[Verizon Samsung Galaxy S 4] HORiZUN:
Lol the active finally got its own forum?
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Yeah, it's been a minute. The AT&T version and the international version are grouped in the same forum, but we'll take it lol
[Verizon Samsung Galaxy S 4] AndroidGraphix:
I read the OP. Awesome proof of concept. A couple questions..

1) upon hijacking, does our ram stay the same and processor speed?

2) is the stock system running in the background?

3)what will be different about ROMs installed on your system vs stock builds? I'm assuming they'll be relatively the same with minor tweaks.

4)will this new system use the stock kernel? Can kernels even be installed since we still have a locked bootloader?
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
It's my understanding that, at least currently, no custom kernels because of the bootloader. Someone much smarter than I am can answer the rest...
[Verizon Samsung Galaxy S 4] DeadlySin9:
1) Hijack should not affect performance. I never noticed it on the Bionic anyways.

2) The stock system is not running, but all files for it are kept in place.

3) ROM's for safestrap i believe just have changes to work correctly in different slots, and possibly since it's loaded from .img files.

4) At first, only the stock kernel will be available. Later however, kexec support will probably be available (running a kernel over the stock one) and allow us to use other kernels that are built for kexec.

Also, for anyone who is curious, ROM slots are successfully created in /data/media/safestrap with this build. No clue if flashing to them writes to them yet, and doubt it's bootable.

EDIT: Slot is safely erased also. Can't wait to create it again when I can actually get a new ROM :)
[Verizon Samsung Galaxy S 4] Obsidian...:
Chill guys Hash's phone just got to sound-mind and is being forwarded on to Hash so it'll be there soon. Hash will be able to debug this damn thing finally. He'll post a new version once it's ready. The proof of concept test is over. No more 1 fail 2 pass needed. Get ready boys

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] Hashcode:
Over the last 2 days I've been ironing out the basic functions of the 3.5x Safestrap update with regard to internal data/media storage. After upgrading to the TWRP 2.6.1.x base (a complete re-write basically), I was noticing a lot of handling issues where calculations were done wrong, or backups included the internal "sdcard" area when they shouldn't have, etc.

On my RAZR-HD (a msm8960-common) currently running stock software and using a hijack similar to the S4, I've fixed the majority of the issues I was seeing:

- Can create / delete rom-slots

- Backup / Restore rom-slots correctly (w/o copying over the sd card in the backup)

- File selectors are working correctly for internal and external SD cards as well as showing the correct free MB

- Etc.

Basically, I need to debug the following on an actual device:

- Touchscreen

- Screen blank issues where splash screen and initial recovery aren't showing up till the screen is actively refreshed in some way

- Uninstall issues

- Adb shell issues

That would = a usable recovery on the S4.

I'll be watching for the loaner device in the mail.
[Verizon Samsung Galaxy S 4] rebel1699:
You gotta do what you gotta do. Its worth the wait.
[Verizon Samsung Galaxy S 4] jova33:
Dope. Keep up the tinkering hash. Btw, what's your day job, and how'd you get into this stuff?

The furthest I've delved was smali edits, and that was a pain.
[Verizon Samsung Galaxy S 4] Alxoom33:
Hey, you don't want to get bootlooped, like me. Better to wait until HC works out all the kinks. I'm going to try to Odin the System back this weekend. Lucky I still have my Bionic, which I reactivated. Now I'm back on my Lapdock, LOL. ;}
[Verizon Samsung Galaxy S 4] HORiZUN:
Alxoom33,

What device are you on?
[Verizon Samsung Galaxy S 4] Alxoom33:
Thanks HC for all of your efforts. Looking forward to S4 on SS.

---------- Post added at 12:43 PM ---------- Previous post was at 12:29 PM ----------

Only good reason to encrypt is data security. In my case it is required for our enterprise email system.

---------- Post added at 12:54 PM ---------- Previous post was at 12:43 PM ----------

I'm presently using my old Bionic, until I fix my S4. But I think that you were asking about the S4. It's an encrypted and rooted Verizon GS4 SCH-I545 ME 7.
[Verizon Samsung Galaxy S 4] HORiZUN:
Can you get your s4 into download mode?
[Verizon Samsung Galaxy S 4] Alxoom33:
Yes...
[Verizon Samsung Galaxy S 4] HORiZUN:
What happens when you power on with volume down, then press volume up at the custom os screen?
[Verizon Samsung Galaxy S 4] Alxoom33:
Goes into Downloading mode.
[Verizon Samsung Galaxy S 4] HORiZUN:
Won't factory reset?
[Verizon Samsung Galaxy S 4] Alxoom33:
Have not gotten to recover screen. Idk?
[Verizon Samsung Galaxy S 4] ahoslc:
How do you fully uninstall this?
[Verizon Samsung Galaxy S 4] Hashcode:
Later today, ill try and work out a new build with working uninstall.
[Verizon Samsung Galaxy S 4] ahoslc:
Have someone coming to grab this phone what can I do now?
[Verizon Samsung Galaxy S 4] Hashcode:
Give me few mins and ill write up a quick set of adb commands.
[Verizon Samsung Galaxy S 4] Alxoom33:
You can Odin back to Stock.
[Verizon Samsung Galaxy S 4] Hashcode:
TO REMOVE SAFESTRAP ON THE S4:

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

That should do it. However, I'm not sure if those commands will work with the native Samsung shell/toolbox installed on the S4. If you have busybox installed you can add "busybox " to the beginning of each of those lines and they'll be sure to work.
[Verizon Samsung Galaxy S 4] coryjohn87:
test

hc if you want me to test anything just let me no dont mind being a test dummy lol whatever helps
[Verizon Samsung Galaxy S 4] mmw68666:
Same here hash code
[Verizon Samsung Galaxy S 4] trook:
Well he seems to put out community test builds which is smart, I myself like many others owned the bionic.... If you didn't, please read everything you can and don't be afraid to ask questions after doing a search of course. Thanks for sticking with it hash, I know it's not easy.
[Verizon Samsung Galaxy S 4] coryjohn87:
i did alot of work with the original droid razr i purity familiar with ss
[Verizon Samsung Galaxy S 4] SamuriHL:
I'm reuploading it for you now. It'll be a while. I'll PM when it's done. I guess I should have kept it up there longer.
[Verizon Samsung Galaxy S 4] trook:
Oh my comment wasn't pointed at anyone but the few that have no idea what ss is/does, I just wanted to tell them to be careful, a locked bootloader phone as you know is very difficult to brick but there are those few...
[Verizon Samsung Galaxy S 4] Surge1223:
Im on mdk so is there a reason those of us on mdk should uninstall safestrap after reinstalling a different recovery? I just manually installed twrp using the following in terminal and im back on twrp.

su
dd if=/sdcard/download/recovery.img of=/dev/block/mmcblk0p21

Of course I did the following before hand (for the purposes of full disclosure):

1. downloaded the twrp file "openrecovery-twrp-2.5.0.2-jfltevzw.img"

2. renamed it to "recovery.img"

3. moved recovery. Img to /sdcard/download
[Verizon Samsung Galaxy S 4] trueagle:
If I Odin to stock does that remove ss
[Verizon Samsung Galaxy S 4] SamuriHL:
Yes.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
This is exciting. If CyanogenMod won't support this I'll build nightlies for you guys when its ready.
[Verizon Samsung Galaxy S 4] mmw68666:
Ok good
[Verizon Samsung Galaxy S 4] zerofighter1:
We would need kexec for that, but it would be awesome if you did once it became available
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
[MENTION=4243514]Hashcode[/MENTION] you said it's just a few file additions to compile a kexec kernel, right? I've taken a look at kexec tools and I'll keep reading up on everything. Please correct me if I'm way off.
[Verizon Samsung Galaxy S 4] Surge1223:
I'm glad compiling cm works for you. Some reason it always fails for me, even using my dedicated linux pc. Can I ask what os you're using to compile from cm from?
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
Ubuntu 13.04 on my personal laptop and 12.04 on my work machine. What kind of errors are you getting?
[Verizon Samsung Galaxy S 4] Surge1223:
Was usuing 12.04, just switched to 13.10 alot of repositories, etc aren't updated for compatibility yet so im thinking I might just go to 13.04 instead.

Anyways i get the type of errors that when googled show the "no results found" page. Even without quotes, lol. Next time I try ill post a new thread with my specific issues or pm you.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
Right on man. Just PM me if you need anything or G+/Hangouts 105636190961005756309
[Verizon Samsung Galaxy S 4] Tada10:
Can this be used to flash google wallet mod?

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Alxoom33:
Thanks Samuri, it worked!! Your a lifesaver. Now I need to reactivate my S4 and recover root from Voodoo/SuSu Pro...
[Verizon Samsung Galaxy S 4] Skitals:
Bravo! Thanks hashcode
[Verizon Samsung Galaxy S 4] jorgenask1986:
Correct me if im wrong here, but this will put any custom ROM on the phone without touching the "stock" at&t rom ?

Wouldnt this take up alot of space ?
[Verizon Samsung Galaxy S 4] Obsidian_soul:
Loved safe strap from my bionic days, can't wait for the multi boot goodness

Sent from my Chronic Hyper Driven SCH-1545

---------- Post added at 09:30 AM ---------- Previous post was at 09:24 AM ----------

This modified recovery it's superior to cwm in all ways

Sent from my Chronic Hyper Driven SCH-1545
[Verizon Samsung Galaxy S 4] brycekerr:
This makes me regret only getting the 16gb model :(

Sent from my SCH-I545 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S 4] greek6486:
Perfect timing, Ty Hash!

Sent from my SCH-I545 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S 4] roboots21:
Just move some stuff to an external SD. That is what I plan to do but then again I don't plan to have more than 1 or 2 ROM slots.
[Verizon Samsung Galaxy S 4] Metallice:
Even better would be to move some stuff to system... Remember Samsung gifted us with that massive waste of space :)
[Verizon Samsung Galaxy S 4] jaydubbs:
I just returned my 16 for a 32 for this very reason.
[Verizon Samsung Galaxy S 4] roboots21:
True Story.
[Verizon Samsung Galaxy S 4] jd07bos:
Just got a massive pants tent! Hope it doesn't last longer than 4 hours, put me down as a tester :D

Sent from my still locked down Galaxy S4 on Verizon
[Verizon Samsung Galaxy S 4] stricklerjosh:
Awesome! Looking forward to trying it out. Thanks for the hard work!
[Verizon Samsung Galaxy S 4] dadsterflip:
For a second there. I thought I went into the moto section lol. Glad to have you on board. You made my moto experience superb.
[Verizon Samsung Galaxy S 4] Devo7v:
Just a quick question, will this be able to share apps between ROMs, or will each ROM be completely independent of each other?
[Verizon Samsung Galaxy S 4] Obsidian...:
It used to be based on cwm but with the multiple rom slots it works much better with the Twrp ui. He has 5+ devices running on this format that he is able to update almost universally so I can almost guarantee he'll never go back to cwm.

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] Alxoom33:
HC, Thank you for your efforts. Loved 3.11 for the Bionic.

One concern, when I was previously running TWRP 2.6.0 for the VZ S4, I noticed that the encryprion/decription support was not working. Don't know if that was fixed in 2.6.1 but hopefully it was. I do know that RNH developed a modified TWRP version for the Xoom (Wingray) that has working encryption support I believe the latest version is 2.6.1. Please let me know if I can help by testing on my encrypted Vz S4 ME 7 (rooted). Again, thank you for taking the reigns on this project. :cool:
[Verizon Samsung Galaxy S 4] ozzzzysh:
I think I need new pants.

Can't wait to be running the Google Play Edition ROM :)
[Verizon Samsung Galaxy S 4] DeadlySin9:
If it works like on the BIONIC, ROM files are put on the internal storage as images and then mounted, so as long as you have room there it's all good. Additionally, they are kept separate, as each is given its own data partition.
[Verizon Samsung Galaxy S 4] Skitals:
Can anyone shed light on how this will affect performance? I understand we will be limited to the stock kernel. If say you load completely stock ME7 to your Safestrap slot, would there be ANY performance difference versus the stock slot or not using Safestrap at all?

Not having custom kernels, we are essentially limited to TW mods. Being able to "flash" mods in recovery is convenient, but nothing you can't mod by hand. I'm just curious if there will be a performance hit for this convenience.
[Verizon Samsung Galaxy S 4] graydiggy:
Not really a performance hit, but our are limited by how much space you have available
[Verizon Samsung Galaxy S 4] epmacman:
is this accurate? Can you build traditional (aosp) roms and/or modifications that run on the factory kernel, in this scenario?
[Verizon Samsung Galaxy S 4] sound-mind:
Is someone looking at the kexec piece? Or more generally has someone managed to load custom kernel modules on the ME7?

I've said it in other threads but I believe a kexec in this phone is possible but will be fairly difficult for numerous reasons. TIMA, signature verification on kmods, and a few other stepping stones are in the way. That said, we do have kernel-space exploits for elevating privilege on the ME7. That means we are in a fairly good place to stomp on the kernel functions performing the signature verification before loading modules. The function in question is lkmauth but the problem is that it is a static function and isn't an exported symbol so /proc/kallsyms (etc) aren't very helpful. I have been looking into it but got side-tracked. I think I can find the lkmauth address but it will take a little time and me not getting sidetracked.
[Verizon Samsung Galaxy S 4] DeadlySin9:
You can flash anything you flash in a normal recovery. However, you won't be able to flash it to the stock ROM until Hash gets that in later.
[Verizon Samsung Galaxy S 4] SamuriHL:
That's awesome! I'm glad I was able to help you out.
[Verizon Samsung Galaxy S 4] Easton999GS:
Are ROM devs going to have to build 2 seperate roms now? Because the loki approach is totally different than this. Or are us loki users supposed to update to this and use this method.
[Verizon Samsung Galaxy S 4] T3T3droid:
We will probably have to make both because some people are going to stay on twrp/cwm and others will go to safestrap... safestrap will take up more space with multiple ROMs loaded and some may not like that. I ran safestrap on my bionic forever and it was amazing but these ROMs are bigger, so who knows. I personally am excited about it! :D
[Verizon Samsung Galaxy S 4] HORiZUN:
Glad to hear you saved the phone. I was thinking yesterday that you could reset it.. Glad you got to the end of the tunnel.
[Verizon Samsung Galaxy S 4] Easton999GS:
I know I can say one thing. There is absolutely no chance in hell im ever updating my bootloader to MF3 which is the AT&T version of ME7 I don't care what's released now
[Verizon Samsung Galaxy S 4] T3T3droid:
Just hope you never need a replacement ;) this will be a good thing to fall back on if the unfortunate happens.
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Question: hypothetically say that down the road when SS is fully functional and I need to replace my phone or something. Will I be able to install SS on the new phone and flash a Nandroid backup of stock to the stock ROM slot?
[Verizon Samsung Galaxy S 4] SamuriHL:
I didn't want him to lose data. Just wanted to get him back to where he was before he started. Looks like we succeeded. Good lesson for others to be aware of. If for some reason SS causes your phone to not be able to boot, create a system only ODIN flash and try it before doing a full wipe. You never know and it could save you a lot of headache.
[Verizon Samsung Galaxy S 4] T3T3droid:
Should be able to restore... But I don't know if he can/will integrate flashing on unsafe side (ie. Stock) due to phone borking issues...
[Verizon Samsung Galaxy S 4] klick37:
Does Hash have an S4 yet?
[Verizon Samsung Galaxy S 4] Poofster:
I'm new here and learning.. can we keep this thread open for the actual work being done on SS and make a new thread for all the what ifs? Not to be a buzz kill but excited for the development of SS and not excited about reading the what ifs that can be discussed after safe strap is working. There's alot of "if" questions now..sorry just getting confused.:confused:
[Verizon Samsung Galaxy S 4] desantim:
Supposedly per his IRC channel it shipped to him on Friday.
[Verizon Samsung Galaxy S 4] Alxoom33:
Thanks, I appreciate your input. It was worth a try before Odin flash of the system tar.:sly:
[Verizon Samsung Galaxy S 4] anthony92170:
Not for anything if your new and learning then you shouldn't post like that. This a discussion thread and these what if questions are gonna help people to decide if they want SS, Stock, just root or even wait and hope for unlocked bootloader. And maybe next update will have a exploit.
[Verizon Samsung Galaxy S 4] Alxoom33:
HC, can it be done with Terminal Emulator on the S4?

Also, is it necessary for now if SS is inactivated and icon deleted from app drawer?
[Verizon Samsung Galaxy S 4] ShadyPossum:
so since test #4 says pass, does that mean theres a chance that using the given method, we can install and run custom roms?
[Verizon Samsung Galaxy S 4] HORiZUN:
Yes, but not yet. There are no roms for this safestrap, yet. This will be possible in a later build when HashCode decides it's ready. Patience.
[Verizon Samsung Galaxy S 4] ShadyPossum:
you cant just load up any rom into slot 1? like in other safestrap versions?
[Verizon Samsung Galaxy S 4] Poofster:
I apologize..just excited and keep checking the thread for a working SS and have to read pages of what ifs to see what I missed. Hoping to see a final SS somewhere and don't want to miss it...in some threads the updates are in later posts so I was hoping to not miss an important again I'm sorry just impatiant.:angel:
[Verizon Samsung Galaxy S 4] HORiZUN:
No roms have been created for this version of safestrap, yet. It specifically states not to flash any roms in the first post of this thread. Be patient. Roms will come. Let HashCode work his magic.
[Verizon Samsung Galaxy S 4] Volvogia:
I have a question. Is this basically a go around fix (in the works)? Meaning since the bootloader cant be unlocked yet, instead of trying to unlock it, we just go around it? Or is this going to turn into a way to unlock it with tests? Sorry Im just trying to figure it all out. I have a MDK version so Im glad i dont have to worry about this but I really feel for you all that cant flash ROMS. I check on these threads everyday hoping that someone has came up with a way to unlock this bootloader for you all on ME7. If I new more about this stuff I would help. If this is basically a way around a locked boot loader then Im all for it. If it leads to unlock it then great, Im all for that too. I have never heard of this method before but from comments I have read that the Bionic had this. It seems very interesting. No hate at all incase someone has takin it that way. Im all for all this. Just trying to figure out where it can/cant lead us on this ME7 deal. If that makes sense lol.