yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I'd gotten curious last night and installed SS 3.70 for vzw, tried to flash Hyperdrive 11 to ROM slot 1, followed by AT&T modules, as expected the result was a bootloop.

Didn't have the balls to flash to stock slot. Though I'm still excited, this is progressing every day.

So far we've had 2 users claim Hyperdrive 11 works on stock slot, and 1 user found DarthStalker to work on ROM slot 1.

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
confirmed working on slot 1 safestrap for AT&T version 3.70 with Darth Stalker X 4.3 jb rom :) flashed the mk2 kernel module, all is well at the moment...Great job Hash!:good:

---------- Post added at 05:20 PM ---------- Previous post was at 04:55 PM ----------

Maybe it will work on slot 1 using the At&t version that Hash just posted a page back? Idk...good luck!
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
anyone want to try out this rom? http://xdaforums.com/showthread.php?t=2537682 im not updating to 4.3 till this is confirmed as working :P
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
I will let u know soon... downloading now.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Don't forget the i337 build.prop :)
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
hmmm, yes thank you for reminding me! but sorry, not working :( i get a black screen then it reboots into "stock" recovery...
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Dang I wonder what's going on :(
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
To all of us.. like myself..who used 3.70 Verizon and Uninstalled for the att update. ..my previous entry that wicked was not flashing was because I did not create a whole new rom slot partition using the aTt version after I installed it...The Verizon partition was still present.after I deleted and re partitioned with att..darthstaulker is up and running nice....wifi is not working good though yet.

---------- Post added at 06:25 PM ---------- Previous post was at 05:51 PM ----------

Not many 4.3 roms are working yet
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
So Wi-Fi isn't working even after flashing the modules?

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I actually have it working now with the mk2 module...it was a little temperamental. ..I flashed it a couple of times before the wifi really stuck.Ive been on it now for awhile with no issue.so, that's good.darthstaulker 10 is the only ROM I've gotten to work really well...actually to work period . I'm pretty happy with it..blows stock away.

I've tried golden eye,infamous s4, hyperdrive, wicked....no dice right now
[AT&T Samsung Galaxy S 4 Android Development] Galaxy*$4:
cant wait until this gets better and all 4.3 roms work (touch wiz) would make a great christmas present to myself. it seems like everybody is saying that aosp based roms may not work yet.
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
To update or not to update... That is the question.
[AT&T Samsung Galaxy S 4 Android Development] jball:
Another question could be.

What else can be done with MF3?

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Successfully used the Verizon version of SS to flash HyperDrive RLS 11 to Rom slot 1. Flashed kernel modules posted earlier and all is working perfectly.
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
That's just the mk2 module file right??
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Correct.
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I wonder if any one has tried slot 2 yet
[AT&T Samsung Galaxy S 4 Android Development] mjnbrn:
Has anyone tried this with an encrypted phone? Our Exchange Policy forces encryption, and I'd really like to use SafeStrap, but I had seen previously that encrypted phones would just boot loop.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I would assume that's the case until informed otherwise.

Safestrap AT&T is working great so far! Hashcode, you're awesome. I'm sending this from Hyperdrive RLS11 (ROM Slot-1) and so far everything seems to be working!

Sent from my Hyperdriven AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I have hyper drive now booting from slot 2...do you have data working??
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
This is a great point. I'm going to let this new ATT build sit out there another day or so. And I'd like to see the recovery.log of failed flashes.

To get this:

- Flash a TW 4.3 based ROM.zip as normal

- Go to Advanced

- Use "Copy Log to SD"

- Then try to boot the ROM.

- If it fails, pull /sdcard/recovery.log from Safestrap.

Then.. *cringe* PM it to me? I really don't want to get hammered with a 100 logs tho. So maybe post in the thread saying what you're sending me. And if you get a failed flash: do a quick search to make sure 2-3 others haven't already sent me logs for the same ROM.

Thanks
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
So.... My dumbas managed to break it... flashed goldeneye ML1 in stock slot, and it bootlooped. I read people could flash in stock slot, so i tried (i know its a big no no) . Anyways i had made a stock rom backup, but now that bootloops as well and just throws me in stock android recovery.

Im at a loss of what to do .... Please help
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
Input at&t apn settings?

---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------

does your sms work on LTE?
[AT&T Samsung Galaxy S 4 Android Development] phobia09:
Because I used to be a HyperDrive user on SS for mf3 and dealt with that, I've remedied that by using GSM/UMTS versus any LTE apn. I do this because LTE speeds in my city are garbage. So using this method gets me mobile data (H+) and sms.
[AT&T Samsung Galaxy S 4 Android Development] hovax615@hotmail.com:
Where'd you get the mk2 kernal? And darthstalker for at?
[AT&T Samsung Galaxy S 4 Android Development] sandman7793:
It was a few pages back.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I'm just curious, did you try flashing Goldeneye to the ROM Slot before taking a leap and flashing to stock, to ensure it'd even boot? As stated earlier, flashing to stock slot deletes Safestrap... so you need to know that it at least boots. Unfortunately, none if this helps you now... but this is why members scream "READ" so often.

Do some research on how to use Odin. It's mentioned in the OP, and it's your best bet.

Sent from my Hyperdriven AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] c_brown93:
Has anyone tried flashing GE 4.3 with new SS yet?
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Tried and failed. I'm about to see if an older version fixes the issue, but so far all it's done for anyone is give a black screen and reboot to recovery.
[AT&T Samsung Galaxy S 4 Android Development] hovax615@hotmail.com:
Was it called the at&tkernelmodules.zip?
[AT&T Samsung Galaxy S 4 Android Development] jball:
That's the one I used .

Hap hap happy

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] hovax615@hotmail.com:
Have you tried any other Roms besides darthstalker?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
A heads up guys with an issue I had with hyperdrive...at first it bootlooped with the kernel module and the att compatibility pack flashed after install completion...The problem I had was the compatibility pack didn't work for me.I copied and manually put in my APN info in settings..now lte is working good and so far it looks good.we shall see.
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
go to my view post history. It was my zip that I made for the kernel modules.

---------- Post added at 03:18 PM ---------- Previous post was at 03:13 PM ----------

Goldeneye bricked me as well with the stock slot and I went through hell trying to recover my phone. Hyperdrive will brick you if you flash to stock slot with AT&T build but it works well with the Verizon build. Hyperdrive also deletes safestrap entirely when you flash to the stock slot and I don't know why.

---------- Post added at 03:23 PM ---------- Previous post was at 03:18 PM ----------

My ROM slot sizes are stuck with system 2760MB and I cant change it. I have done full Nand Reset with Odin and I still have this issue. Is there anything I can do? This is both VZW and AT&T builds.
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Edit: disregard
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Hyperdrive works good on rom slot 1 with. Safe strap att 3.70..I am using it to.write this.this safe strap is beta so the system sizes seem locked but do you need a bigger system size..that seems pretty big as it is....If you're bricked after golden eye stock mistake..try flashing back to mf3 using the tar files and update again to mk2....don't write or adjust stock though.
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
Maybe not try that, as you'll be in deep doo doo... I tried that, and now I can't even get into recovery. It just says firmmware upgrade encountered an error. Following gtj0's guide now...
[AT&T Samsung Galaxy S 4 Android Development] dolph8886:
Attempted to flash SHOStock i4.0,Hyperdirve RLS11, and GOLDENEYE to stock slot with VZW-3.65-SELinux and all resulted in a bootloop except a deodexed stock rom "STOCKUP" but wifi was not working

Not sure why but as soon as I flash a zip to stock slot/stock rom I lose wifi and cannot seem to get it working again. did this 3 times with just vrtheme mods

gtj0's method works

you can use the MF3-MK2 update at the end

for now I am sticking with the stock rom with just a few mods I did manually

update

looks like wifi can be resurrected with a build.prop edit

ro.securestorage.support=0

not being content with stock I gave it another shot with Safestrap-JFLTEATT-3.70-B01

Hyperdrive RSL11 flashed successfully to stock slot, just not with the ATT Compatibility Pack
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I had that problem Benny too trying to go back to stock before the update to mk2 . dyslexic turtle in the help section uploaded GOOD tar files for mk3.it worked perfect for me where the mega link I had from another post had tar files that game me that error too.
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
U need MK2 tar ..... which is we don't have as far as i know but saw hashcode posted earlier he might have it.....i could be wrong. Coz I dont think we can downgrade to MF3 after upgraded ....maybe best bet is going to best buy..... and if help maybe ask for the files .... :D that's would be helpful for community

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Do we even know if the GPE is still compatible with the stock TW kernel? ive been digging through the multiple GPE threads and it seems everyone is either using the stock GPE kernel or the GPE edition of faux kernel.

I think we need someone on mdl to test a 4.3 GPE rom with the mk2 kernel. if it boots for them than we can go from there and figure out whats going wrong on our end. as i cant even get a logcat while the phone attempts to reboot.
[AT&T Samsung Galaxy S 4 Android Development] sykoj82:
IPBGHD rom works good, located in the i9505 forums.
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
It's true that you can't downgrade to a working mf3, but you can downgrade just enough to get the mk2 update again. I'll use best buy as last resort lol :)
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Downgrading is something I haven't looked Into so It could be true
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
How u do that to get to the point where we can restore and upgrade to mk2.....

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] HORiZUN:
Is there an MK2 tar file?

If we upgrade to MK2 from MF3, can we go back to MF3 wuth Odin?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
People are saying no...but why not?it sounds logical
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
http://xdaforums.com/showpost.php?p=47586777&postcount=135

http://xdaforums.com/showpost.php?p=48621760&postcount=18

This worked after bricking my phone on MK2... Im now back to a fully functioning phone!
[AT&T Samsung Galaxy S 4 Android Development] punkcell:
just installed OMEGA rom

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

odin MF3 > MK2 > saferoot > SS 3.70

working good so for.

notice a little battery drain
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
I can also confirm this method works...however I had to reflash the recovery at the end as I lost it after the second emergency flash.
[AT&T Samsung Galaxy S 4 Android Development] jball:
I use the Hyperdrive RLS11 with no problems at all.

Exposed and Wanam enabled.

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
because the bootloader stop you from doing so, There are efuses in the phone that everytime you update one fuse is blown so you cannot go back ever. ex. If the MF3 bootloader uses 4 efuses to boot and the MK2 uses 3 efuses. When you go back to MF3 you only have 3 fuses therefore the bootloader refuses to boot anything.
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
It could very well be that. I tried flashing Foxhound ROM which has a stock kernel option in Aroma and it didn't do that, just bootlooped.

Has anyone sent [MENTION=4243514]Hashcode[/MENTION] any logs yet? I've got the Foxhound Aroma log and the SS log on my SD right now.

Also, Hash, if you don't want too many PM's we could do attachments to our posts here and still search to make sure nobody else put them up.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
This also works.
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Alright. Since I don't believe anyone else has tried Foxhound, I've attached the logs from AROMA and the recovery log. What looks interesting it this in the Foxhound log:

>>> Mount partitions
mount: failed to mount /dev/block/mmcblk0p18 at /cache: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p29 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p16 at /system: Device or resource busy

But it seems like it still put out files just fine. Not sure what that's about.

Attached files are both logs, for Foxhound the log was big so i added .cab to the end, it's not an actual .cab so just remove the extension. Included it just in case.
[AT&T Samsung Galaxy S 4 Android Development] d-rail:
The regular one or the Google Edition one?
[AT&T Samsung Galaxy S 4 Android Development] punkcell:
the regular one

9505_Omega_v18_XXUEML1

but now i switched over to the hyperdragon rom.

the omega rom was running a bit too slow, and after doing a TB restore the apps started force closing.
[AT&T Samsung Galaxy S 4 Android Development] JohnMonsour:
Not quite a proper explanation of the q-fuse method that Samsung likes to incorporate in their major carrier variants. Anyways a q-fuse is an electronic signature if you will. Like after MDB and MFL for ATT variant's they implemented this method which patched the loki exploit and also no downgrading. Obviously frowned upon. Here is what happens. When you flash the OTA or a bootloader update through Odin/Heimdall than what happens is, it changes the binary code of the q-fuse current status. It is resettable it's not like these physical fuses in the phone that blow with every update.... It is software based and encrypted and matched by the public sammy key and they're own personal government level sig/flag checks, ram flushes and a very special key which is the "Golden key" "angles singing".... Anyways they're private 256-bit sha-1 hash is pretty much uncrackable with brute force tactics. Anyways bootloader MF3 blows a q-fuse changing it's status to 0X00001 so any bootloader preceding that in the encryption is unflashable due to sig checks. Is the key available? Has someone been working on this bootloader? We may never know....
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Tested a few different GPE 4.3 ROM's and they all gave a black screen and boot loops, but only the un modded GPE goes into recovery.
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
How did you guys run darthstalker? I tried in Rom slot 1 but it just bootlooped.... fully wiped too.
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Im thinking that gpe no longer supports stock kernel...I searched through the threads and have yet to find one person mention using stock mk2 kernel with gpe 4.3, they all seem to use the gpe kernel or gpe faux kernel, we need to get someone with mdl to try the 4.3 gpe rom with a stock mk2 kernel...if it works for them than we know its a problem on our end...if it doesnt, than we know the kernel is incompatible

This is just my theory, and I could have missed a post...so if anyone has any refrences to people using the mk2 kernel with a gpe rom please let us know...

Also I experienced the exact same results as you...only the unmodded one sent me to recovery, tried to get a logcat while booting but that was a no go :/ so cant see where its going wrong that way
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
It seems to almost be luck of the draw sometimes.i think the partition has to be high and what has worked for me is...delete the partition and reformat all over again and try flashing again . I've booted omega v 18 9505 which I was quite surprised at.i change apn manually in mobile data and it worked..runs well..darthstalker 10 I've ran a couple of times and loved it but for some reason the mp3 playback will shudder no matter the player I use.So presently I have hyperdrive in slot 1 and omega 18 in slot 2...Both flashed with module after and manual apn setting. Hyperdrive runs great for me.wicked 9.1 booted once never again . anyways there are a couple of other touch wiz I've gotten to work well...I'm just playing around right now but keeping hyperdrive. Delete and repartition and flash..
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Just wondering if anyone try this Graviton_v2.0_TW4.3_MKF or Deadly_Venom_v1.3.7_TW4.3_ML1yet on v3.70 rom slot1 ? since it use StockUp_kernel for JB 4.3 and flash ATT_MK2_MODULE.ZIP after.....
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
That's because Hyperdrive AT&T is 4.2.2, which can't be used with 4.3 kernel.

I noticed this as well, but I assumed it was either intentional or due to a lack of internal storage.

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
I tried the carnage 4.3 from venom...no.dice at all...downloading graviton now.
[AT&T Samsung Galaxy S 4 Android Development] ximaginex:
My phone is in a Bootloop after flashing a custom ROM. Tried to flash Dandroid 4.4.2 using the latest verion of Safestrap.

I have an ATT SGS4 i337 MF3, and this is how I flashed the rom:

1. Changed to ROM Slot 1

2. Flashed the Custom ROM

Starting getting bootloop from here.

3. Flashed Loki Doki

Still got bootloop.

4. Wiped Cache and Dalvik-cache

Still getting bootloop. Did I forget to do anything or should I be doing something differently?
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Stay away from the graviton...booted me into recovery....gez....one I did get to work really well was x note freedom rom..9505 I think...I might try that again it was Decent
[AT&T Samsung Galaxy S 4 Android Development] c0ldburn3r:
Correct me if I'm wrong but posting you're boot looping without posting a recovery log is a waste of thread space.

Get hashcode some useful info!
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Ur awesome bro .....:thumbup::thumbup: and just for clarification... that u flash on either rom -slot1 or rom slot2 right? and keep stock-slot for stock MK2 ?

SWYPED_FROM_S4_MF3_REDVENOM
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
I would recommend reading the last 5 or so pages of a given thread as well as the OP in the future. This bootloader is LOCKED, so you must use a ROM that uses the STOCK kernel, and those modules must be reflashed after the ROM. So that means whatever version of Android you're on and it has to be TouchWiz based (because of the kernel.)

I'm aware the OP doesn't state all of this outright, but most of this information is all over thread, especially last several pages. Also, Loki doesn't work for MF3 or MK2, and I don't think it's mentioned anywhere in this thread to Loki anything... I'm pretty sure that's why this thread was created in the first place.

So, in short:

No Loki

4.2.2 goes with 4.2.2

4.3 goes with 4.3

4.4 isn't even released yet for TouchWiz based S4's

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
To top it off....:

Bootloader:................Use:...................Custom Rom:

MDL/MDB.......................LOKI.....................4.2.2......4.3.....4.4 ALL WORK (....LUCKY U....)

MF3................................SS-v3.65................ONLY FLASH 4.2.2 ROM (Slot1,Slot2 and Stock ALL WORK)

MK2................................SS-v3.70................SOME 4.3 ROM WORK (Slot1,Slot2 and Stock ALL WORK (one confirmed))
[AT&T Samsung Galaxy S 4 Android Development] jee'sgalaxy:
im just patiently waiting for 3.7 to come out :D

hope it will equal 4.3 GE ROMs for me!
[AT&T Samsung Galaxy S 4 Android Development] jball:
It's out and have been running roms.

Look at the tail end of the Safestrap MF3 forum

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
Unfortunately, to my knowledge the GPE ROMs don't use the stock TW kernel, so as of now... no go.

I was really hoping to be able to flash one as well.

Slightly OT, are most of you on 32 GB versions of the S4? I ask because I can barely install half of my usual apps on ROM Slot 1 without running very low on storage. I do have a 16 GB SD card, but it's got about 13 GB of music and my stock backup, so short of flashing in the stock slot, I'm not sure how I'm going to be able to fit it all on 16 GB of internal storage.

Also, both times I've attempted to backup the stock ROM, everything seems to go fine, yet I get this error: E: Unable to locate ' /boot' partition for backup

I can't claim to know enough to be able to discern if this is an issue or not, but any advice is welcome.

Sent from my AT&T Samsung S4 (MK2)
[AT&T Samsung Galaxy S 4 Android Development] jasas212:
Thanks my friend. ..yes,rom slot 1 I have hyperdrive and rom slot 2 has been experimental.I don't touch the stock..:)
[AT&T Samsung Galaxy S 4 Android Development] rabshear:
I am running Hyperdrive 11 in my STOCK slot. And everything appears to be working fine. So, it's not a true statement that only slot1 or 2 works for now. And I don't think I did anything special to make this happen. I am on MK2 and I came from a rooted stock ROM. I installed SS 3.7. First I tested that the rom would work at all by flashing it to slot 1. Once I felt confident that it was good to go, I flashed it to the stock slot. I wouldn't recommend some of the newer folks messing with their stock slot, but I chose to, and can verify that it does indeed work.
[AT&T Samsung Galaxy S 4 Android Development] DevilDog512:
Try running the file system check/repair in recovery then switching to stock then back to ROM slot 1

Sent from my SAMSUNG-SGH-I337

---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
[AT&T Samsung Galaxy S 4 Android Development] ted77usa:
Alright then. .... Good to know ..... Glad that u confirmed. .....when I said for now by mean no one confirm to work on Stock slot yet and couples people tried but no go (Bootlooped) and I'm thinking maybe the Rom itself not the SS-v3.70 or I might have missed that. ..... updated my statement...... :good: and just to confirm when u said Hyperdrive 11 is it from VERIZON forum right? coz for our forum is still 10.2 w/4.2.2 base .....★[ROM][4.2.2][Nov 9] Hyperdrive RLS10.2 ¯`•._ ║ TW Re-imagined ║Multicarrier ║★

SWYPED_FROM_S4_MF3_REDVENOM