yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] thump:
Downgrade to NE4, then root and install SS, then back to NG3. http://xdaforums.com/att-galaxy-s5/general/how-to-root-g870aucu1ang3-gs5-active-t2868776
[AT&T Samsung Galaxy S 5] Jbluedodge:
So the ne4 kernel will work to allow me to install safestrap, then i just put the ng3 kernel back on?
[AT&T Samsung Galaxy S 5] thump:
It worked for me. Mine came with NE4, but then OTA updated itself to NG3 before had a chance to root or install SS. Using NG3 towelroot wouldn't work so I followed the instructions from that post to downgrade, root and install SS, then update back to NG3 (then installed Unity anyway).

Just be aware that the firmware in the link I provided is for an S5 Active. You may need grab a different NE4 kernel image if you're using a regular S5.
[AT&T Samsung Galaxy S 5] Jbluedodge:
I'm already root on NG3 (regular s5), i've tried installing safestrap on with the kernel from the regular s5 ng3 root thread, you think it'll work if I install safestrap with the NE4 kernel?
[AT&T Samsung Galaxy S 5] thump:
No guarantee, but It did for me.
[AT&T Samsung Galaxy S 5] Jbluedodge:
Your using regular s5?
[AT&T Samsung Galaxy S 5] thump:
No.. an S5A, but they're identical phones except for the "active" button.
[AT&T Samsung Galaxy S 5] Jbluedodge:
Okay so I've tried unrooting and going to nc3 kernel rerooting and making sure busy box is installed, still can't get safestrap installed. Any other ideas?

---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------

Did you ever get safestrap installed?

---------- Post added at 03:25 AM ---------- Previous post was at 03:23 AM ----------

Did you ever get safestrap installed?
[AT&T Samsung Galaxy S 5] Darian71:
[MENTION=4243514]Hashcode[/MENTION]...THANK YOU SIR FOR YOUR DEDICATION AND HARD WORK DEVELOPING SS FOR MY AT&T G900A. Works amazing and am officially running my first custom ROM From Unity. [emoji2] [emoji106] [emoji106] [emoji106]
[AT&T Samsung Galaxy S 5] Simon Hammers:
When do you think there will be an update for rom slots to work
[AT&T Samsung Galaxy S 5] s8freak:
None Safestrap is no longer supported by Dev. Unless someone else has picked where Hashcode left off.

"You stay classy San Diego"

Sent from my G900A powered by XKRom GoldLimiTed.
[AT&T Samsung Galaxy S 5] Khrimzunn:
So since there is safestrap does that mean I can flash cm11 as per this thread? http://xdaforums.com/galaxy-s5/unified-development/rom-cyanogenmod-11-0-android-4-4-4-t2864288
[AT&T Samsung Galaxy S 5] cstayton:
No you cannot flash CM,AOKP,AOSP ROMS the only roms you can flash are TouchWiz roms. in order to flash Non Touchwiz roms we would need an Unlocked BootLoader which we do not have.
[AT&T Samsung Galaxy S 5] Khrimzunn:
Thanks for the reply. I did just try to flash the cm11. It looks like it flashed it. It turns on but after the samsung screen it shows nothing. The orange indicating the device charging is working (cm11 uses that from what I gather because my wife's oneplus does that) but the screen does not turn on. The soft buttons are also nonresponsive. Is this an improper flash? (I wiped from safestrap and installed it from there. I will try Koolkit and visix.
[AT&T Samsung Galaxy S 5] gregsarg:
You cannot flash CM Roms...

Did you not see the post from cstayton ??

The phone will sit at boot forever if you try...

The bootloader is locked...and will not allow any other rom than a stock or modified stock rom...g
[AT&T Samsung Galaxy S 5] Khrimzunn:
I saw his post a little too late. I wasn't sure what my results meant if it meant anything other than the obvious. I just wanted to test to see if it works at all.
[AT&T Samsung Galaxy S 5] gregsarg:
Understandable...

But sadly it will never work unless we get a bootloader unlock...and that isn't looking like it's gonna happen anytime soon....g
[AT&T Samsung Galaxy S 5] Simon Hammers:
Is it possible for someone to create a program that can unlock our encrypted bootloaders? Or is AT&T the only ones that can unlock it?
[AT&T Samsung Galaxy S 5] s8freak:
There's been some brilliant minds working on that very problem for quite some time and from what understand a hefty bounty going to the person that breaks the bootloader.

That bring said I doubt that it's going to happen unfortunately.

"All we know is...He's called the Stig!"

Sent from my XKRom Gold LimiTed powered G900A
[AT&T Samsung Galaxy S 5] muniz_ri:
I was able to get rom slots working on both the ATT & Vz S4's and just picked up a new to me G900A and thought that I would take a crack at ROM slots on the S5. However I just successfully created rom slot-1 and successfully flashed and booted both Goldeneye and DynamicKat.

Is it already known that rom slots are working on the S5?
[AT&T Samsung Galaxy S 5] s8freak:
Wow outfrickenstanding [MENTION=4708661]muniz_ri[/MENTION] and no all of figured Rom slots were a no go I couldn't get it to work anytime I tried. Could you PM me how you got it to work?

"All we know is...He's called the Stig!"

Sent from my XKRom Gold LimiTed powered G900A
[AT&T Samsung Galaxy S 5] muniz_ri:
Thanks but I take zero credit for working rom slots on the S5. I didn't touch the apk. It's probably the new supersu that made the difference. I noticed chainfire made some changes to selinux policies.

---------- Post added at 10:19 PM ---------- Previous post was at 10:05 PM ----------

Really I did not do anything special. Try installing supersu v2.14 then make the slot and flash a rom.
[AT&T Samsung Galaxy S 5] s8freak:
Thanks for the info [MENTION=4708661]muniz_ri[/MENTION] I appreciate it very much

"All we know is...He's called the Stig!"

Sent from my XKRom Gold LimiTed powered G900A
[AT&T Samsung Galaxy S 5] muniz_ri:
No problem. Let everyone know if you are able to get the same result.
[AT&T Samsung Galaxy S 5] ted77usa:
[MENTION=4708661]muniz_ri[/MENTION]

Great Finding bud....i can confirmed Rom Slot 1 Created on ATT S5 SM-G900A.
[AT&T Samsung Galaxy S 5] s8freak:
Confirmed as well [MENTION=4708661]muniz_ri[/MENTION]

"All we know is...He's called the Stig!" Sent from my G900A powered by XKRom GoldLimiTed
[AT&T Samsung Galaxy S 5] muniz_ri:
Sweet. Everyone have at it! Lol. All props go to hashcode and [MENTION=631273]Chainfire[/MENTION].
[AT&T Samsung Galaxy S 5] FilthyFord:
Posting this message using Rom slot 1 on my G900a.
[AT&T Samsung Galaxy S 5] king200:
Is the most recent, SuperSU in both Stock and Slot1?

I'm wanting to try DKK v3 and v4 in different slots.

There was some success with the Note 3 and Slots but erratic problems were observed with use. The rebooting problem was consistent.

Please continue to report.
[AT&T Samsung Galaxy S 5] FilthyFord:
I was able to create aRom Slot and bit up fine as i am in Rom slot 1 right now. I am running Dynamic Kat 4.0. Since creating the slot my phone won't restart, fast reboot, or reboot in safestrap using the options from the reboot menu. I can use the power off option and then turn the phone back on to get to safestrap. Is this a slot issue maybe, or a Rom issue. I never had a problem in stock slot.

Thanks in advance.

I know there is a Q&A spot but i haven't had any success with replies or help using it.
[AT&T Samsung Galaxy S 5] muniz_ri:
S4 users are also having the rom slot reboot bug. This seems to be due to the 2nd init loaded with the rom flashed in the slot. Not rom related. I'm still trying to solve on the s4 but in the meantime some users have been able to reboot from the rom slot using Exposed installer framework. The reboot bug should not affect stock slot.
[AT&T Samsung Galaxy S 5] muniz_ri:
FYI......a long press of the "Volume Down" + "Power" + "Home" will reboot the phone while on a rom slot.
[AT&T Samsung Galaxy S 5] damosthated162:
Will this work with ng3?
[AT&T Samsung Galaxy S 5] Nucleartx:
Yes, just follow the root guide for ng3 in general and then this guide will get ss working for you.
[AT&T Samsung Galaxy S 5] damosthated162:
Thank you
[AT&T Samsung Galaxy S 5] FilthyFord:
I did this just now and when it rebooted a screen came up and said "Your data partition was damaged, a factory reset needs to be performed to reset it" it something like that. Any ideas. I was able to flash my backup with SS but still curious. I have a AT&T galaxy S5 on Dynamic Kat 4.0.
[AT&T Samsung Galaxy S 5] damosthated162:
Same thing happened to me and I had to reflash stock via Odin. Pain in the ass, I think Its best to bebloat your own stock ROM, and also theme your own with wanam. Takes a little bit more time but seems like SS has some issue. I rebooted mine normally and boom! Damaged lol [emoji1] good luck.
[AT&T Samsung Galaxy S 5] K-alz:
Anyone could hook me up with the latest version of SS, please? Neither of the links provided in op works. Just got my new S5 and wanna try something other than stock. Thanks ya'll.
[AT&T Samsung Galaxy S 5] sholsten:
Seems like the latest update stopped SS. I think you have to go backwards to a previous firmware. Hopefully someone more knowledgeable will help you.
[AT&T Samsung Galaxy S 5] FilthyFord:
http://download.chainfire.eu/supersu[/url]
[AT&T Samsung Galaxy S 5] K-alz:
I know he doesn't support it anymore, but I just need the one that is in the link in the op. 3.75 B03 if you have a copy of it.

---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------

That looks like supersu to me, not safestrap
[AT&T Samsung Galaxy S 5] s8freak:
Took 2 seconds of a search

http://xdaforums.com/showthread.php?t=2794087

Look for v 3.75

https://www.dropbox.com/s/lski57su8fd0eu3/Safestrap-KLTEATT-ND3-3.75-B03.apk?dl=0

"All we know is...He's called the Stig!"

Sent from my G900A powered by VisionX Rockin Blue XKRome
[AT&T Samsung Galaxy S 5] K-alz:
I've actually searched, but not too hard. Thanks and sorry for wasting 2 seconds of your life [emoji16]
[AT&T Samsung Galaxy S 5] s8freak:
Didn't waste my time

"And on that bombshell it's time to end the show!"

Sent from my VisionX powered G900A Rockin Blue XKRome
[AT&T Samsung Galaxy S 5] K-alz:
Was joking, man. It worked. Thank you kindly. This is my very first time coming to the S5 forums(not an excuse, I know lol). Just got my new s5 today.
[AT&T Samsung Galaxy S 5] s8freak:
No problem man I'm glad it's working for you...welcome to the S5 I personally think it's a monster device. I've had a Galaxy since the S2 and every model since. Looking forward to the S6

"And on that bombshell it's time to end the show!"

Sent from my VisionX powered G900A Rockin Blue XKRome
[AT&T Samsung Galaxy S 5] gregsarg:
That's 2 seconds I'll never get back...and at my age...they start to add up....so links are appreciated....LOL....g
[AT&T Samsung Galaxy S 5] K-alz:
Thanks bud. I have a total of 5 Samsung devices. 4 phones (2 note 3s, S4, S5) and a 48 inch TV. LOL

I like this phone a lot. Now what to flash. Any suggestions? You can PM me your opinion if you think it'd offend some devs.

What's up man. I remember you from the note 2 days. You might not remember me because I changed my username (it used to be k-alzwayed).
[AT&T Samsung Galaxy S 5] s8freak:
I'm 52 Greg seconds really count

"And on that bombshell it's time to end the show!"

Sent from my VisionX powered G900A Rockin Blue XKRome

---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------

I run ViSiX LimiTed and VisionX almost exclusively. Unity Rom is a very good Rom as well. But I guess I'm biased on the first two since I'm chief tester for both.

VisionX is a stockish Rom that's about as flawless as one can get. I flash that with XKRome blue or red theme. Have fun flashing man and if you have questions feel free to pm me I'll do my best to point you in the right direction if I don't know the answer.

"And on that bombshell it's time to end the show!"

Sent from my VisionX powered G900A Rockin Blue XKRome
[AT&T Samsung Galaxy S 5] K-alz:
Much appreciated, sir. Will check them out.
[AT&T Samsung Galaxy S 5] s8freak:
Any questions feel free to pm me I'll do what I can ??

"And on that bombshell it's time to end the show!"

Sent from my VisionX powered G900A Rockin Blue XKRome
[AT&T Samsung Galaxy S 5] FilthyFord:
Oops sorry had a brain fart. Ha
[AT&T Samsung Galaxy S 5] gregsarg:
Howdy brother...

I do remember !!.....(shocking that I remember anything these days)....LOL

Good to see ya in the S5 forums.....g
[AT&T Samsung Galaxy S 5] K-alz:
Thanks man. That bad? LOL

I don't know, man. I seem to like my note 3 a lot more than the S5. I'm trying to get used to it because I have to (got this phone for free from "Samsung Mobile insights" program and have to use it as my daily driver for 6 months or they'll take it back)
[AT&T Samsung Galaxy S 5] gregsarg:
The 5 is a fast and solid phone...

The bootloader is a drag...but it'll get figured out...and then beast mode....g
[AT&T Samsung Galaxy S 5] K-alz:
Yes it is, but I just don't like how small the screen is. Lol

From my Allianced/koffed S5!
[AT&T Samsung Galaxy S 5] isanchez340:
I intalled cm11 on slot 1 on my cricket s5 and and rebooted to se if it worked, the rom did boot as I was able to take screenshots and was able to raise and lower the volume, but sadly the screen didn't seem to work (only black screen) does anybody know something about this :confused:
[AT&T Samsung Galaxy S 5] zrzhu:
Any requirement for the SD card? What size should I get, at least 1 GB? What's the SD card for? Install SS on SD card?
[AT&T Samsung Galaxy S 5] gregsarg:
I believe cricket is an ATT operated company is it not ??

And you may have a locked bootloader anyway which won't allow kernel flashing...hence the reason that CM won't boot...g
[AT&T Samsung Galaxy S 5] isanchez340:
but it did boot is just the screen would stay off but the phone would respond to the lock button and and I was able to hear the sound when I took a screenshot
[AT&T Samsung Galaxy S 5] gregsarg:
Doesn't matter really if the screen won't work....

I'm pretty sure that T-Mobile is the only domestic carrier with an unlocked loader...g
[AT&T Samsung Galaxy S 5] FtaWolf:
Deleted.
[AT&T Samsung Galaxy S 5] muniz_ri:
**Updated** Safestrap-G900A-KitKat-3.75 w/Working ROM Slots

Here it is: Safestrap-G900A-KitKat-3.75.apk

All precautions, limitations, and known issues stated in the OP still apply! Proceed to install and use at your own risk!

Changelog:

1. Resolved "reboot from ROM-slot bug."

Instructions:

Make certain that you have BusyBox installed! (Make certain that you open the BusyBox app after downloading from the Play Store and actually install BusyBox!).

1. Uninstall previous Safestrap recovery version using the Safestrap app "Uninstall Recovery" function.

2. Uninstall the previous Safestrap app from your app drawer.

3. Go into SuperSu settings and "forget" the previous safestrap version's root privileges.

4. Place the new Safestrap.apk onto your sdcard or extsdcard.

5. Install the new Safestrap.apk.

6. Locate and open the new Safestrap app from your app drawer and press "Install Recovery." Done!

Known Issues:

None!...yet.

Please note: This is a Development Thread! Therefore, please do not post comments related to ROM specific issues, favorite ROM's, that weird rash that won't go away, etc., in this thread. Please use the following thread in the General section for non-development related discussion: http://xdaforums.com/att-galaxy-s5/general/updated-safestrap-g900a-kitkat-3-75-apk-t2938105

Credits:

Hashcode
[AT&T Samsung Galaxy S 5] s8freak:
[MENTION=4708661]muniz_ri[/MENTION] confirmed working you are the man and many MANY thanks my friend???????

G900A rockin
[AT&T Samsung Galaxy S 5] muniz_ri:
Thanks man! But hash is the man, I'm just trying to figure out how the heck he did it! Enjoy!
[AT&T Samsung Galaxy S 5] s8freak:
Yea he is but it looks like you're doing a great job taking over and there's gonna be a TON of happy flashers out there.

G900A rockin
[AT&T Samsung Galaxy S 5] Simon Hammers:
I thought the supersu update fixed ROM slots? I'm confused : /

---------- Post added at 06:21 AM ---------- Previous post was at 05:55 AM ----------

Either way thankyou so much bro. I didn't know there were any devs working on safestrap.
[AT&T Samsung Galaxy S 5] muniz_ri:
Thanks, it seems that you we were always able to create and flash to a ROM slot. The problem was you were unable to reboot or shut down from a slot. That's the problem that this latest update resolved.
[AT&T Samsung Galaxy S 5] Simon Hammers:
Oh awesome! So are you like taking over the safestrap project now and gonna keep updating it?
[AT&T Samsung Galaxy S 5] muniz_ri:
I will do what I can with my limited knowledge however 5.0 is going to be a game changer and it may mean the end of root for locked BL devices and the end of safestrap. But at least for the time being everyone can enjoy safestrap the way hash intended by leaving your stock system "pristine" while flashing custom rom's on slots!
[AT&T Samsung Galaxy S 5] ted77usa:
[MENTION=4708661]muniz_ri[/MENTION]

U and [MENTION=4939386]Surge1223[/MENTION] should team up and continue Safestrap legacy.....U both would rock Our Lock BL world .....I really appreciated what u guys did.
[AT&T Samsung Galaxy S 5] u1988:
[MENTION=4708661]muniz_ri[/MENTION] [MENTION=4939386]Surge1223[/MENTION]

or Anyone else...

Do you know how Continues the OP work/project?

Will anyone make "Safestrap Recovery" for note 4 for at&t +Version models?

Thank you!
[AT&T Samsung Galaxy S 5] ted77usa:
Not until root method achieve.
[AT&T Samsung Galaxy S 5] berniesteven:
Works on active. I also noticed that the date is correct on backups. Great job op.

SM-G870A Peace
[AT&T Samsung Galaxy S 5] Simon Hammers:
Yeah the galaxy S5 is still such a new phone, that would be awesome if you got a team going to improve our ROM flashing experience :D
[AT&T Samsung Galaxy S 5] draexo:
observation: I had to install recovery twice before it "took"
[AT&T Samsung Galaxy S 5] Joehen873:
Ok what safestrap do we install if we r ng3? The new that was posted a few pages back
[AT&T Samsung Galaxy S 5] cstayton:
that would be the one:good:
[AT&T Samsung Galaxy S 5] rock_box:
Anyone know if the encryption bootloop is still an issue in the new version?
[AT&T Samsung Galaxy S 5] thump:
I've been thinking about this and have a theory that I'm hoping someone with knowledge of SS code can confirm. The way Grub (the normal linux bootloader) works is that Grub is installed in the drive's MBR and is the first thing that boots. It then directly boots one of the kernels sitting on the /boot partition that contain all the bootstrap info to fire up the actual OS on the corresponding root partition. If you have an encrypted root partition (such as LUKS) then the kernel you install on the /boot partition will be built (via update-initramfs) with bootstrap support to include the modules needed to ask for a decryption key at boot and to decrypt the root partition before continuing the boot sequence.

When you "chainload" instead of directly firing up the OS like above, the primary MBR bootloader instead just boots a secondary bootloader that is contained at the base of the root partition, and then that bootloader fires up the actual OS. (This seems to be very much how SS functions.) The problem is you can't chainload to the root partition containing this secondary bootloader if that partition can't be read because it's still encrypted, and because the /boot partition is on these phones is locked, you can't modify the boot partition to include a kernel that contains decryption support.

What I would love for a Dev to confirm is if Safestrap actually installs itself to the boot sector of the root partition?

If that is the case, then the second question would be how does SS "intercept" the stock OS boot sequence to cause the chainload? The stock system does support device encryption (and so does TWRP when normally installed) so it should be able to decrypt the root partition and then SS could take over from there. What I'm wondering is if SS is intercepting the stock boot sequence before it has a chance to complete either setting up the encrypted loopback device or mounting the decrypted root filesystem. Either one would cause the boot loops that Hashcode describes.

Personally, lack of encryption is probably going to be the dealbreaker that has me sell this phone. I haven't ran an unencrypted desktop or laptop for many years and feel naked having the device that would be easiest to lose/steal being the one part of my data ecosystem that's most exposed.
[AT&T Samsung Galaxy S 5] thump:
I just started digging through the .apk and may have answered my own questions. From what I can tell (based on my very limited programming knowledge) it looks like SS jumps in right after the stock boot init sequence and essentially kills all file mounts and processes (hijack.killall script), then remounts and restarts them all with a secondary init. This would kill the decryption block device that was setup by the stock init and stop any further access to the encrypted /data parition. What I *think* I'm seeing is that this secondary SS init process doesn't anticipate encryption and doesn't make the appropriate calls to re-setup the /data decryption after killing the initial block device.

Based on my limited understanding, I would venture to guess that encryption could be supported in either 2 ways:

1) The user would need to enter their password twice to boot - once when the stock init decrypts and boots the /data partition, then again when the SS init kills the original decryption device and has to recreate it.

2) That SS could somehow preserve the original decrypted /data mount through the hijack process.

Implementing either are beyond my comprehension of the android init or partition setup and limited shell script hacking skills, but the decryption process that would need to be considered is here: https://source.android.com/devices/...n_encrypted_device_without_default_encryption

It appears this will quickly become a central issue as 5.0 will support /forceecrypt filesystem flags that can make encryption mandatory.
[AT&T Samsung Galaxy S 5] Simon Hammers:
Man i really wish someone could unlock our bootloaders :(
[AT&T Samsung Galaxy S 5] cstayton:
basically you have hit the nail on the head, your asumption is correct that is how SS works.
[AT&T Samsung Galaxy S 5] muniz_ri:
Encryption doesn't seem to be a huge concern for most safestrap users around here and based on what I have read about 5.0 only new devices shipping with 5.0 will have encryption enabled as default. In any case and IMO safestrap's days are numbered as android security is improved with every new update. E.g. the ATT Note 3 crowd was just updated to 4.4.4. I was able to get them root however safestrap, at least for now, no longer works.

You seem to be more knowledgeable than most around here now that hashcode has moved on so we welcome any input/contributions that you are able to make. Thanks,
[AT&T Samsung Galaxy S 5] thump:
Thank you for confirming.

Thanks, muniz_ri. I'm no coder, nor have a spend much time getting familiar with android details, but I've been running linux as my primary OS on everything since '03 so at least most the concepts seem to translate. If nothing else, I'm used to having to hack things up bit to get them working. I'm happy to contribute however it's useful.

What was concerning to me when reading the details of the 5.0 encryption scheme is that although they avoid explicitly stating it, they have implemented the technical capability that the OS could force encryption of currently unencrypted partitions on upgraded devices. The section titled "Encrypt an existing device - This is what happens when you encrypt an unencrypted Android K or earlier device that has been migrated to L." describes a method for encrypting upgraded devices that could be user-initiated, but could also be OS mandated. If the OS was to set the /forceencrypt flag on the filesystem then the phone is going "default encrypt" the partition, which means it would be encrypted without a password. While this provides no security when someone boots up the phone, it would render the filesystem unreadable and unwriteable when the OS is not running - essentially killing most Odin-style and other offline flashing hacks.