yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] JohnMcW:
Yes, there is no sound on Slot 1 for the rom I installed, after rebooting.

Primary Rom Sound works fine.
[AT&T Samsung Galaxy S 4 Android Development] nightmare4321:
Guys noob question but what size partition do I choose 1 2 3 gb?
[AT&T Samsung Galaxy S 4 Android Development] zeyoner:
Well that mostly depends on how much space you think you use for data. Also if you're planning to setup other ROMs in the other available slots. I went with 1gb. As I'm just testing, if I need more space I'll just recreate.
[AT&T Samsung Galaxy S 4 Android Development] nightmare4321:
Thank you for helping me so there is no way of using all my storage just up to 3gb for now? Still this guy is a genius for getting around the bootloader thank u so much.
[AT&T Samsung Galaxy S 4 Android Development] nativesmiley:
im trying to remove safestrap, im following the method thats in the first post. but it isnt working for me. anyone know another way to remove it? i get a "no such file directory" after typing in the 3rd line.
[AT&T Samsung Galaxy S 4 Android Development] zeyoner:
It's case sensitive. Please make sure you're typing everything exactly the same way that's instructed.
[AT&T Samsung Galaxy S 4 Android Development] nativesmiley:
That's what I did. Just copied the text and paste
[AT&T Samsung Galaxy S 4 Android Development] jball:
I thought so myself with 3.65 I read it in the change log

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] davenger1:
To remove Safestrap update to 3.65 then uninstall it in the app! Works perfectly have done many times!
[AT&T Samsung Galaxy S 4 Android Development] New2ThaDroid:
Ok it worked. Thank you!
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
If you have the newest safestrap apk then you don't need to run the commands.
[AT&T Samsung Galaxy S 4 Android Development] RockRatt:
Looks like Safestrap for 4.3 is getting closer. He is working on a Verizon firmware now and hasn't tested it on Verizon MK2 yet from what I gather. You can see his Beta here http://xdaforums.com/showpost.php?p=48531807&postcount=967

AGAIN THIS IS ONLY FOR VERIZON SO FAR. SO DO NOT TRY TO USE IT. HOPEFULLY HE CAN GET IT TO WORK WITH MK2 FOR YOU ALL AT SOME POINT.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T Samsung Galaxy S 4 Android Development] NighthawkXL:
Great to hear, been holding on 4.2 for obvious reasons.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
I uninstalled ATT update software. ... from TB and how do I get MK2 firmware update in order to use newer MK2 SS recovery in the near future? Can't really find the MK2 firmware any where yet. ....Or can I stay on 4.2.2 and update to 4.3 MK2 SS recovery only? Btw I'm on custom deadly Venom Rom Android 4.2.2 MF3 right now... work like a champ. ..... and like in the past on mdl or mdb firmware we are able to by pass bootloader by using loki patch or CWM with auto loki. .... do u think this would possible with the same way if we have boot. Lok instead of boot.img to by pass lock bootloader or using custom recovery that auto lokied ....in this case SS with auto loki patch? Just some thought. ....:D

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] Black6spdZ:
a bit OT but as far as all this locked boot loader and safestrap stuff is concerned I want to say F U Samsung for locking these boot loaders just to protect sales on your overpriced dev/google edition phones.. all I can say is I will stop recommending all Samsung phones to everyone that asks my opinion.. see how you like that for your sales quota!
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
The .tar files for MK2 are available here on the forum. When the time comes for SS 4.3, you can use Odin to flash stock MK2 (4.3).

As far as the Loki idea goes, the developers here will eventually find a way, as long as they don't move to another device first. There's really no suggestion that non-devs like ourselves could come up with and expect to work. I mean no offense, you just kinda have to be a dev to understand how these things really work. It just doesn't work the way we'd think.

Your anger is misdirected. As has been stated, it is not SAMSUNG that's locking the bootloaders, it's AT&T & Verizon.

Also, the GPE devices aren't terribly overpriced, they're just unsubsidized. You get a "discount" on devices when agreeing to sign a contract, and they aren't available from carriers like AT&T & Verizon.

I understand your frustration, but it'd help to calm down, and properly direct your anger... at AT&T & Verizon. :)

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
so what i am wondering if 4.3 supports kernel memory overwriting, would it be possible to instill aosp based roms or just tw. i would think that we can flash custom kernels now. would be pretty sweet i also think we could instil 4.4 if all thats needed is the kernel to be changed or is there more to it then that.
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Do you have a link to the .tars?
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
I think the only way right now is flash to stock via Odin to MF3 firmware and take the OTA update for MK2 firmware.....I might be wrong. .... correct me if I'm wrong

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] jball:
That's what I did just to confirm one way to do it.i believe there is a sideload method as well if Odin don't work for you

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] brobinson2102:
Or ADB sideload the MK2 update.

Rooted but Knox'ed MK2 4.3
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
If the kernel memory overwrite allows a kexec exploit, I believe kernels will need to be written to be compatible with it and then we will be able to boot other AOSP ROMs. I have no clue how difficult making a kexec kernel is or isn't, nor whether the memory overwrite is enough to lead to an exploit in the first case.
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
He said .tars were available for MK2, I'm aware MF3 .tars. thought maybe someone uploaded new ones.
[AT&T Samsung Galaxy S 4 Android Development] jball:
Could have been a typing error. The #2 is close to the #3.

MF3 MK2

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] thepktrckt:
How is everyone dealing with the 4GB Data partition limit? I'm finding it's far too small for use and App2SD gets slow and messy.
[AT&T Samsung Galaxy S 4 Android Development] jball:
Are you using a class 10 micro SdCard

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Working on the VZW S4 update to safestrap for 4.3 support (selinux).

As soon as its decent, you can expect a new update here as well.

Sorry its taking a while. None of this has ever been done.
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Waiting won't kill any of us, Hash! You're the man!!!
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Well honestly I'm considering dumping my phone from this hassle... but then again moving to another without dealing with contact is also a huge hassle :(
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
that is some good news, lets just hope for the best safe strap plus aosp and TW rom support would be epic at this point

---------- Post added at 06:31 AM ---------- Previous post was at 06:29 AM ----------

no worries hash, you cant rush perfection :)
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
More a thinking error than a typo, but an error nonetheless! My apologies. :D

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jball:
OK Hashcode I have huge balls and downloaded the Safestrap 3.65 SELinux apk from your version thread and here is my findings.

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] jt1998:
So, what did your results show? Not sure I'm getting it from the screenshots:confused:
[AT&T Samsung Galaxy S 4 Android Development] dolph8886:
I believe he installed safestrap on MK2 and made a backup
[AT&T Samsung Galaxy S 4 Android Development] jt1998:
That's what I was hoping/thinking but unsure. So now we're hoping he can flash a custom 4.3 ROM with safestrap, right?
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Well that mounting /boot on safestrap issue may be a whole lot more complex than you think..just for the fact it hasn't loaded almost anything but the kernel..the drivers for safestrap needs updating to support mk2 kernel. He has a mf3 safestrap trying to communicate with mk2 kernel.. Yea that won't work..
[AT&T Samsung Galaxy S 4 Android Development] jball:
Yes a successful install of Safestrap with a successful backup. That's all it can be used for at this time according to the Verizon thread.

No modules to make ROMS work properly at this time according to the Verizon thread.

I was just letting Hashcode know that all screens boot 100% the way they should

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] thepktrckt:
It's not Samsung, it's AT&T. The international versions generally have bootloaders that can be unlocked and the Google Edition can be unlocked as well.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
I correct myself on my last post, to get as far as he did, he must have made the drivers himself for ss. Nice work! :)
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
Successfully got Hyperdrive 4.3 RLS11 Running on my AT&T GS4 with the VZW alpha safestrap flashed to the stock slot =]. I copied my modules from my original MK2 firmware and pasted it using a file explorer so Wifi and everything works! WARNING: when flashing to stock slot Safestrap gets deleted and needs to be reinstalled all over again. So if you mess this up. You brick.
[AT&T Samsung Galaxy S 4 Android Development] JohnMonsour:
It should only get deleted if you were to factory reset through the official recovery. But I have no idea about this new MK2 and 4.3 SS Alpha. All I can say is hash has been working his ass off! Enlighten me please.
[AT&T Samsung Galaxy S 4 Android Development] jball:
Copied and pasted using your phone? You didn't make a zip.

How big was the module file you copied.

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
it was really small, like 2 files. its in the system/lib/module folder
[AT&T Samsung Galaxy S 4 Android Development] jball:
Yes but did you make it a zip using es root explorer.

I do know how to find it, was asking cause when I zipped it up it was very small.

ROOTED ATT MK2 using Tapatalk
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
AT&TKERNELMODULES.ZIP kernel modules flashable.zip

https://www.dropbox.com/s/r5o3mz8gtyh6gmx/AT%26Tkernelmodules.zip
[AT&T Samsung Galaxy S 4 Android Development] rabshear:
Where did you find that alpha build? Can't seem to find it anywhere. Think I'd like to play with it!
[AT&T Samsung Galaxy S 4 Android Development] prisonnet:
Here: http://xdaforums.com/showpost.php?p=48531807&postcount=967

BUT if you hang tight a day or two, it sounds like hashcode is finishing up a new version.
[AT&T Samsung Galaxy S 4 Android Development] Black6spdZ:
I don't think AT&T itself creates the bootloaders...
[AT&T Samsung Galaxy S 4 Android Development] toxicpaulution:
They don't but they make Samsung put them locked by default on their phones as a "security measure"
[AT&T Samsung Galaxy S 4 Android Development] prisonnet:
Tried to flash GPE 4.3 here http://xdaforums.com/showthread.php?p=47718525#post47718525 because its 4.2.2 predecessor worked with SafeStrap, but only get bootloops. Restoring the backup should have worked but doesn't boot into anything....at least I still have safestrap so I can play around getting my phone un-bricked...

---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------

Is this the ROM you installed in stock: http://xdaforums.com/showthread.php?t=2301724? Want to make sure I flash the same one you did.
[AT&T Samsung Galaxy S 4 Android Development] smalis:
Great job on Safestrap guys, I am now running Hyperdrive flawlessly on Rom slot 1. But, I think I made the system partition too big (2800 MB) and the data partition too small (2500 MG), and I have less than 1 GB left on my SD card. /system has 1 GB free, so I can reduce it to 2200 and increade the data partition accordingly. Am I correct that the only way to do this is to nandroid Hyperdrive, delete Rom slot 1, recreate Rom slot 1 with the preferred sizes, and restore the nandroid?

UPDATE: I did the above successfully. Am now running Hyperdrive on ROM slot 1 with system at 2200 MB, data at 3100 MB, and cache at 300 MB. Superb!!
[AT&T Samsung Galaxy S 4 Android Development] dolph8886:
can anyone mount extsd?

64GB exfat mounted on previous versions
[AT&T Samsung Galaxy S 4 Android Development] thepktrckt:
AT&T sets the requirements, Samsung manages the bootloader. It still makes AT&T much more the evil as Samsung needs AT&T more than AT&T needs Samsung.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Hi Guys,

I've posted a BETA Safestrap v3.70 for the VZW variant that works for their SElinux=enforcing builds (as many of you already know).

I'd like to update the AT&T build as well but I need the following:

1. SElinux files from MK2 build ramdisk:

/file_contexts

/property_contexts

/seapp_contexts

/sepolicy

/sepolicy_version

2. I need to understand how EXFAT support is being done in 4.3. I'm not seeing the exfat_*.ko modules in the builds anymore, but I get a feeling from users that the SD cards can still be read while in the OS.

3. Possibly tomorrow night I may need a tester on IRC freenode.net #safestrap channel to run through the build and test flash ROMs.

Thanks
[AT&T Samsung Galaxy S 4 Android Development] lanimul:
Sent file link in pm :)
[AT&T Samsung Galaxy S 4 Android Development] Black6spdZ:
AT&T can go back to selling just eyePhones as far as I'm concerned
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Has anyone attempted flashing the 3.7 safestrap beta??
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
just look 2 pages back...
[AT&T Samsung Galaxy S 4 Android Development] gj23:
I don't think it will do you any good,....... according to OP(Hashcode), there isn't a MK2 module zip yet
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
There is an mk2 module zip link in the verizon thread
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Didn't someone earlier in the thread just use the files located in /system/lib/modules/ ? Couldn't someone just zip those files up and upload it?
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
https://www.dropbox.com/s/r5o3mz8gtyh6gmx/AT&Tkernelmodules.zip
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I plan on trying tonight but if any of you try Please post.my understanding is make a backup of stock and flash a 4.3 rom on stock with module after . hyper drive 11 seems to work well
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I did install the Verizon safe strap 3.70 but was unable to get slot 1 to finish booting hyper drive 11... I'm electing to not flash over stock and I am going to wait for hash codes at t release...very unpatiently...haha hope it's soon
[AT&T Samsung Galaxy S 4 Android Development] mdaudioguy:
While I'm definitely anticipating running 4.3 (or beyond - is that wishful thinking?), I'm content waiting for things to stabilize a bit. At first, I thought SS was great, but a bit gimmicky with the limited space allocated for slots. However, with the ability to overwrite stock with a ROM like SHOStock, and then remove SS to boot directly into a decent custom 4.2 ROM (albeit with a stock kernel), things will have to be pretty smooth and stable before I move away from this. This has greatly exceeded my expectations after first hearing the words, "locked bootloader."
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I love safestrap...its awesome...
[AT&T Samsung Galaxy S 4 Android Development] jprattnu:
merry xmas!

Agreed. Got a replacement off ebay, said it was ucuamdl (even box), but alas, the dude ota'd it to mf3. if it were not for this program, i would have resold the POS on ebay... lol.. merry xmas all! :D
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I have an updated status with this...After deciding to wait....I figured WTF AND Tried one more time with a different 4.3 rom....darthstauker X 4.3 IS A GO....Also I have it flashed on rim slot 1 with stock perfectly in place.I flashed the mk2 module zip after aroma install...wifi and data work...typing from it now....no problems yet
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Hash, did you get what you needed?

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] yongsanghoon:
Can't boot into safestrap.

Hi guys,

I currently own an AT&T Samsung GS4 with a baseband of I337UCUEMK2. I successfully rooted my phone today using saferoot, and also successfully installed safestrap. However, I am not able to reboot into recovery via the safestrap app. Any ideas?

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
As of right now, Safestrap isn't officially supported for AT&T's version of MK2. Two users have reported successfully flashing ROMs, but it's still quite a risky process. This could easily brick your device if you try before it's actually ready.

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
For me, the only reason I want ss to update, is for GPE 4.3.. I seriously don't like touchwiz... I regret ever sending my phone into warranty and receiving mf3 back.... but I'm stuck with what I got, so at least I have gpe :) and 4.3 gpe sounds nice.. kexec support from updated supersu sounds even better :)
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Yeah, same here. I'd at least like to try the GPE version. MK2 is quite buggy.

Are there any recommendations for partition size?

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jt1998:
Make sure you just reboot if you want to get into safestrap, not reboot into recovery. Is that what you want?
[AT&T Samsung Galaxy S 4 Android Development] undecided323:
any idea why safestrap tells me i have 12mb of free space to make a new romslot but i know my storage has more than 8gb same as my sdcard
[AT&T Samsung Galaxy S 4 Android Development] TheEgonSpengler:
Because all the s4's are like that.
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
My friend. ..make sure you look up and install the recovery in the app when you open it....then reboot to recovery
[AT&T Samsung Galaxy S 4 Android Development] undecided323:
ive used safestrap before and creating romslots with no problem but now i cant make one :/
[AT&T Samsung Galaxy S 4 Android Development] Mr. SirPerson:
When this comes out, will we have to update our stock to 4.3 to get the kernal to be able to install 4.3 ROMS?

Also, is there any way AOSP/AOKP roms like CyanogenMod and PAC will be supported in this new update?
[AT&T Samsung Galaxy S 4 Android Development] rbedell:
Yes to the first and no to the second. SS needs to be able to kernel handoff and that never even got released for 4.2. Not likely that it would be ready right off the back with a new os and tighter bootloader...
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Just a thought ..... would we able to use loki. Doki like on previous mdb or mdl bootloader?

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] rbedell:
Nope.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
I have a v3.70 build of SS which works with MK2 (android 4.3 / SElinux=enforcing) for the ATT S4 here:

http://goo.im/devs/Hashcode/jflteatt/safestrap/Safestrap-JFLTEATT-3.70-B01.apk

(Users still on previous build should NOT install this, stick w/ v3.65)

I need JUST A FEW users (maybe those using the VZW BETA) to reinstall using that file and make sure everything works.

NOTE: EXFAT is still not fixed in this version

I HATE doing test builds this way as I prefer to work with 1-2 testers for early tests like this. But it seems like my testers are very busy with the holidays, etc.

HAVE THE MK2 ODIN FILE HANDY IF THIS BOOTLOOPS OR CREATES AN UNSTABLE SYSTEM
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
There's a odin file for mk2? Wow I most have been in the dark...

---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------

Does that build install if your still on mf3? Not that I want it, just curious. When you say it's stable enough and gpe is confirmed for ss, I'll update out of mf3.

---------- Post added at 11:14 AM ---------- Previous post was at 11:12 AM ----------

And I do want to point out, [MENTION=4243514]Hashcode[/MENTION], that wanam xposed has a beta toggle to set selinux to permissive. Does that change anything?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I just did an install after using the Verizon beta....so far so good
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
Coming from a FRESH MF3 restore with Odin:

Rooted with the new SafeRoot tool.

Installed 3.70 SS from your above post.

Wiped everything except ExtSD.

Started to install HyperDrive RLS11 to Stock ROM Slot.

Aroma installer worked as advertised.

Error at the end of the install saying there was a problem flashing the kernel. Tried to flash the kernel files someone posted a few posts back, error opening zip file.

Hit reboot, and custom lock shows up with the Samsung logo, then black screen with blinking notification LED.

I'll try with another 4.3 based stock ROM in a sec.

Hope this helps.

EDIT: My ExtSD is formatted ExFAT. Is this an issue for SafeStrap 3.7?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Quick update. ..tried using rom slot 1 to flash wicked 9.1 on new att safestrap after having flashed with success on Verizon build. ..negative on att.will try another soon.thanks for doing this hashcode
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
This new version is for MK2 users running 4.3. Sorry about the confusion.

Before going back to v3.65: Use the "Remove Recovery" button inside the v3.70 APK and then you can uninstall the APK.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
That apk is for the mk2 build for us.. not mf3.. (at least what I interpreted)

And the exfat would basically just prevent you from mounting your sd card in ss.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
The way SElinux works in the Samsung kernel, it cannot be disabled once it's turned on. SO that toggle won't work.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Well that sucks, but understandable..Thanks for work on this :)
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
So I need to install the 4.3 OTA to take advantage of the 3.70 SS? 4.2.2 is taking its toll on me, but I don't see myself updating from MF3 unless some serious exploits are found on a later firmware.

I do appreciate what you do, Hash.

Restoring back to stock with Odin. Will reinstall SS 3.65.

BTW, ExFAT worked fine on SS 3.70. Memory card mounting and reading worked great.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
do you remember when hash was saying when safestraped, you stay on the stock kernel? When you have mf3 kernel installed, mf3 based roms will work.. same with mk2.. but mk2 is really early build of ss right now.. and not really tested at all..
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Can you pull the /tmp/recovery.log for me after flashing wicked 9.1?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Sure...glad to help...I'm having an issue locating it? Could anyone point.me.in the right direction thanks
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
i just bricked/bootlooped while flashing on the AT&T build. the Verizon build however is fine.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
We still need mk2 kernel module right? I just downloaded a zip from another user, but was wondering if Hashcode posted one yet.