Database Users

Very confused about MF3

I just bought the HTC One for $200, but then I saw that Best Buy had the Samsung Galaxy s4 on sale for $50. I did not know which one I wanted and was truly torn between the two and ended up buying the HTC but if I can save $150 I will gladly get the s4. My only problem is that as I've been reading up on cs4 forums to make sure that I would be able to unlock root and flash custom roms I had came across what seems to be the problem with an AT&T firmware update known as mf3. If I cannot root and flash custom kernels and roms I do not think I will take advantage of the offer from Best Buy. My problem is that even after all the reading I cannot figure out whether it is possible to root and flash custom ROMs and kernels to the new version from AT&T, known as mf3, or if it is still not possible, or if it will be possible very soon so that I'm may use Android 4.4 Kit Kat on the phone or any custom Rom I wish. Can someone please clarify this for me as soon as possible because my time to return the HTC One to AT&T is coming close to its end?
Sent from my HTC One using Tapatalk

You can root and flash some roms using safestrap. But it's very limited. Imo I'd stay away from the s4

It's there any progress toward cracking MF3? I've had a one x for pat year and kinda wanted a change and I love the screen on the s4. If you had to choose between the s4 and the HTC one taking into consideration the mf3 problem, which would you choose? And which would you choose if there was no mf3 problem?
Sent from my HTC One X using xda app-developers app

If you can find a S4 with MDL or earlier firmware it's a excellent phone. Personally if it has MF3 or later I wouldn't bother. But that's just my opinion.

You might as well get rid of the One as well. It's just as locked down.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Untrue, about HTCone being just as locked down. It can have it's boatload unlocked quiet easily and if you want to, although it's not necessary, you can even do s-off to get full unbridled access. I previously had a HTC one x and also from everything I've read it seems AT&T went out of there way to lock down s4 tight , just like they did to the one x but eventually the devs got it. I do want the s4 though,even though this phone is awesome(HTC One), and I can live with no custom Rom for a while but I can't go without root. So if I get a s4 with mf3 will it still be able to be rooted ? I've read up on it but don't understand what everyone is talking about when they say if the phone is encrypted or notand it seems to be random.
Sent from my HTC One using Tapatalk

So sick and tired of reading about MF3, or MK2 constantly on these forums. If you want to buy an S4 on AT&T look for an MDL one on eBay. It's not that hard, really.
Or buy the T-Mobile variant or International version.

Thanks for your kind response to my honest question mattmjb0188. I can't get a t mobile or international variant bc I'm on a budget. I will use my upgrade to get the phone at best buy for $50, and the condition of this price is that it must be a contract renewal/upgrade, which is another reason I can't get diff version of the phone. Did you even read the op? I would love to get one brand new out of the box with mdl but the odds of that are slim hence why I asked the question in the 1st place. So if you can't help or don't like the question then don't respond, but I do thank you for your info about the other variants that don't have issues, it just doesn't help me.
Sent from my HTC One X using Tapatalk

Rad ryan said:
Thanks for your kind response to my honest question mattmjb0188. I can't get a t mobile or international variant bc I'm on a budget. I will use my upgrade to get the phone at best buy for $50, and the condition of this price is that it must be a contract renewal/upgrade, which is another reason I can't get diff version of the phone. Did you even read the op? I would love to get one brand new out of the box with mdl but the odds of that are slim hence why I asked the question in the 1st place. So if you can't help or don't like the question then don't respond, but I do thank you for your info about the other variants that don't have issues, it just doesn't help me.
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Anyone new on these forums just asks over and over about MF3 and the Android 4.3 update. Basically, if you get an S4 with Mf3 or later firmware, you are pretty much stuck on stock. Then we have noobs who don't read and attempt to root their MF3 phones and brick them.
On pure stock, the S4 is a bad phone. The software is very laggy and needs a lot of improvement. I was one of the early adapters when it first came out. The phone was a nightmare with MDB and MDL firmware. Mf3 made slight improvements, but not enough.
I would not even invest in buying this phone right now. Most development for it has died down because of the restrictions. Developers are moving on. Those of us with MDL firmware (like myself) won't see much continued support for Loki nowadays anyway. If the bootloader could be unlocked, I believe it would have been unlocked by now. All these workarounds are very limited, and dangerous.
Personally, I wouldn't even buy the phone at this point. Scrape the funds together for either the T-Mobile S4 or Note 3.

Get the nexus 5, you'll be very happy

Thank you very much for that answer, that was an excellent answer. Although I'm not a noob bc I've been doing this stuff for years and been a member for years.I did the trading but I am not familiar with Samsung at all bc the last Samsung I had was a captivate. It's there a lot of active development for the t mobile variant? I'm guessing it's probably around $600, right? Lastly do you think that there will be a solution to the lock down of mf3 and later in the next few months?
Again thanks for your very helpful answer.
Sent from my HTC One X using Tapatalk

Rad ryan said:
Thank you very much for that answer, that was an excellent answer. Although I'm not a noob bc I've been doing this stuff for years and been a member for years.I did the trading but I am not familiar with Samsung at all bc the last Samsung I had was a captivate. It's there a lot of active development for the t mobile variant? I'm guessing it's probably around $600, right? Lastly do you think that there will be a solution to the lock down of mf3 and later in the next few months?
Again thanks for your very helpful answer.
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
The development for the AT&T S4 has died down. In my opinion, no one will ever unlock the bootloader for it. Maybe someday with some future device, but not this device. The closest we got was with the loki method, which was great. But that's long gone now.
Look on negri for the T-Mobile variant. I think its M919. I'm not sure. T-Mobile developers have been able to make great roms for the device, instead of wasting so much time to find a workaround. Maybe even try T-Mobile out and see if they've improved in your area. They got a lot better in my area, but still a lot of EDGE.
If I were you, I'd go for the Nexus 5.

Rad ryan said:
Thanks for your kind response to my honest question mattmjb0188. I can't get a t mobile or international variant bc I'm on a budget. I will use my upgrade to get the phone at best buy for $50, and the condition of this price is that it must be a contract renewal/upgrade, which is another reason I can't get diff version of the phone. Did you even read the op? I would love to get one brand new out of the box with mdl but the odds of that are slim hence why I asked the question in the 1st place. So if you can't help or don't like the question then don't respond, but I do thank you for your info about the other variants that don't have issues, it just doesn't help me.
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Heres my suggestion, if you want the s4, get it from best buy than sell it unopened for as much as you can and than with the money you get buy a tmobile or i9505 international variant...(not i9500 or the verizon or sprint one)
The tmobile variant is probably your best bet, the tmobile variant supports all of ATT service bands so youll have no issues with reception or internet. The tmobile variant can flash roms from any of the other s4 variants (verizon sprint att i9505...just not any roms from the i9500)
So in other words if you get the tmobile variant you dont have to worry about a dead dev scene as you can always flash roms from a differnt carrier...only thing is you will probably have to set up your apns for att rom flashes
Hope that helps you
And on another note if you decide to stick with the ATT s4, every firmware can be rooted
Mdb has real recoveries, so you can flash anything as long as you "loki" the kernel - Unfortunately I do not think there are any stores that are selling phones with this firmware
Mdl has real recoveries, so you can flash anything as long as you "loki" the kernel...Unfortunately it is pretty much impossible to find a phone with this firmware in any store now
Mf3 has safestrap which is kinda like a recovery, with it you can flash any touchwiz based 4.2.2 rom (stock roms) or any 4.2.2 Google Phone Edition (aka GPE, which is an aosp experience S4, no bloatware no samsung features, its like having a nexus in the body of an s4) rom...NO CUSTOM KERNELS, NO AOSP ROMS (no cyanogenmod) - this is the firmware most phones come with
Mk2 (latest firmware) recently got a beta safestrap...as of now you can flash some 4.3 touchwiz stock based roms, alot dont boot yet, and the GPE 4.3 rom doesn't boot with it either. As it becomes stable it should work identical to the one for mf3 - phones will probably start coming with this one soon
In other words, safestrap allows you to run roms that are built off the same firmware version as your stock rom, safestrap flashes no kernel, so whatever rom you flash has to be compatible with the stock kernel of your current firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk
---------- Post added at 08:44 PM ---------- Previous post was at 08:40 PM ----------
Rad ryan said:
Thank you very much for that answer, that was an excellent answer. Although I'm not a noob bc I've been doing this stuff for years and been a member for years.I did the trading but I am not familiar with Samsung at all bc the last Samsung I had was a captivate. It's there a lot of active development for the t mobile variant? I'm guessing it's probably around $600, right? Lastly do you think that there will be a solution to the lock down of mf3 and later in the next few months?
Again thanks for your very helpful answer.
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
They actually seem to be getting close to another work around which will allow you to flash any rom or kernel using safestrap...turns out theres a feature in the 4.3 mk2 kernel which allows unsigned drivers to run, in theory they can compile a kexec driver for the kernel which would allow you to use any kernel thus allowing the flash of any rom...theres a how-to thread in the original development section with more info, however...its not a guarentee we will see this anytime soon, as you never know what issues they may run into...but something to look into if your interested
EDIT: actually heres a post from the thread i mentioned which pretty much sums up how we hope this "exploit" will work as far as kernel flashing goes http://forum.xda-developers.com/showpost.php?p=48703510&postcount=10
Sent from my SAMSUNG-SGH-I337 using Tapatalk

With all that said; how come I have the MF3 baseband my s4 (jflteatt), and I still have a custom recovery with the ability to flash different roms and kernels? Is it because I installed the custom recovery on an earlier baseband and then it got updated to a newer baseband but still kept recovery?
I only found out I had MF3 on my phone now because I couldn't flash a different recovery anymore.

Yes
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

noel_leon said:
With all that said; how come I have the MF3 baseband my s4 (jflteatt), and I still have a custom recovery with the ability to flash different roms and kernels? Is it because I installed the custom recovery on an earlier baseband and then it got updated to a newer baseband but still kept recovery?
I only found out I had MF3 on my phone now because I couldn't flash a different recovery anymore.
Click to expand...
Click to collapse
It is literally impossible to have officially updated through OTA while on a custom Recovery. What I suspect has been done is the same as my phone. I got an MDL device and quickly installed TWRP and a custom ROM. As new updates came out, I flashed just the baseband. So now, I have a 4.4 ROM with the MK2 baseband and am able to install anything I like.
If I were to have ever done an OTA, I would no longer be able to have a custom recovery because of a blown Qfuse.
Please don't try to say that what you have is the only phone with OTA MF3 and custom recovery.
The only way to have anything like that is through SS and that is not a true recovery. If you do have that, you can only install certain ROMs not including AOSP, AOKP, MIUI, or CM.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

When did I ever say I was the only one? I asked a simple question that I mostly had the answer to already; which in turn was answered by a simple "Yes" from HiTideBlastoise.
And I never said anything about OTA either. I said I had installed custom recovery on an earlier baseband and then my baseband was updated but recovery was still intact.

I never said you did say that. It was preemptive. Secondly, you make it out to seem like you did nothing to update your baseband. You are making it seem like it just happened. Well, that can't happen without either updating the entire phone or flashing it yourself. The funny thing is the baseband means nothing when it comes to recoveries and flashing ROMs. It can only be used as a possible sign on a stock device as to what version one is running. On a modified device, like yours, it is worthless information on the version of Android. Like I said before, I have 4.4 with MK2 as my baseband. How can I install ROMs. Not because it updated my baseband after I already have a custom recovery... But because I never took an OTA and made it do the stuff I wanted.
Basically what I am saying is that you need to be clear with what you say. Everything you said makes it sound like your phone did it all by itself without you or someone else making it the way it is. There is no other option. You have to have done something to have a custom recovery and an MF3 baseband with pre MF3 bootloaders.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

I agree with graydiggy that the only way to still have a custom recovery and mf3 baseband is that you either flashed an mf3 tw rom with a modem or a a standalone modem to your mdl software. If you took the "OTA" successfully, you will definitely have a locked down bootloader now.
Sent from my SCH-I545 using xda app-developers app

[Q] KIT KAT on contracted Samsung S4 AT&T i337?

I have had my S4 since switching to ATT in late November and have been following the XDA forums very closely since then. It was thanks to the XDA forums that I was able to root my S4.
However, no matter how far, wide, and meticulously I look on the site, there is no mention of the existence of running KIT-KAT on the i337 S4 for AT&T, save for the Google Play Edition and the version with the octacore etc.
I know these forums are strict (and should be) about questions being asked more than once, but I am not asking when KITKAT will be released through AT&T or even Samsung because I honestly don't care. I simply want to get KitKat on my device running with relative stability. I know there are custom roms out there, but most of them were released...a month ago or so? MAYBE I'm missing something, but if anyone here is in similar shoes, I would appreciate it if you'd echo my sentiments/request to find out if it can be done and how.
Anyone who knows how I can learn more about loading ASOP onto my i337 S4, I would greatly appreciate it. If the limitation is a locked boot loader that you CANNOT get around (excluding safestrap), do let me know! I'm sure a lot of people would benefit from the answer to this question.
Otherwise I'm going to go buy the Google Play Edition of one of the Android devices that has an unlocked boot loader.
Cheers,
Justin

justintime001 said:
I have had my S4 since switching to ATT in late November and have been following the XDA forums very closely since then. It was thanks to the XDA forums that I was able to root my S4.
However, no matter how far, wide, and meticulously I look on the site, there is no mention of the existence of running KIT-KAT on the i337 S4 for AT&T, save for the Google Play Edition and the version with the octacore etc.
I know these forums are strict (and should be) about questions being asked more than once, but I am not asking when KITKAT will be released through AT&T or even Samsung because I honestly don't care. I simply want to get KitKat on my device running with relative stability. I know there are custom roms out there, but most of them were released...a month ago or so? MAYBE I'm missing something, but if anyone here is in similar shoes, I would appreciate it if you'd echo my sentiments/request to find out if it can be done and how.
Anyone who knows how I can learn more about loading ASOP onto my i337 S4, I would greatly appreciate it. If the limitation is a locked boot loader that you CANNOT get around (excluding safestrap), do let me know! I'm sure a lot of people would benefit from the answer to this question.
Otherwise I'm going to go buy the Google Play Edition of one of the Android devices that has an unlocked boot loader.
Cheers,
Justin
Click to expand...
Click to collapse
What version are you currently running. Go to about phone and post your baseband version. If the 2nd to last digit is f or higher you can't get kit kat yet. If it is before f then you are free to do whatever you want., If you are rooted you can just download rom manager from the play store and flash a recovery the easy way. Then get cyanogenmod or something for your device.

failedjedi said:
What version are you currently running. Go to about phone and post your baseband version. If the 2nd to last digit is f or higher you can't get kit kat yet. If it is before f then you are free to do whatever you want., If you are rooted you can just download rom manager from the play store and flash a recovery the easy way. Then get cyanogenmod or something for your device.
Click to expand...
Click to collapse
Thank you for your reply!!!
That is most unfortunate, since it is i337UCUEMK2 - even if I did some crazy stuff to go back to MF3, I'd be right at f anyway. ROM Manager and flashing a recovery the easy way seemed simple enough and I was going to do that but it ended up not working, then I tried using Goo Manager and that soft-bricked my phone and I spent hours getting it back to MK2 again. It's back to the way it was, but I still want to update to Kit-Kat.
Btw, could you tell me why it isn't possible because of my baseband? Thanks failedjedi, and anyone else that can offer useful information.
Cheers,
J

justintime001 said:
Thank you for your reply!!!
That is most unfortunate, since it is i337UCUEMK2 - even if I did some crazy stuff to go back to MF3, I'd be right at f anyway. ROM Manager and flashing a recovery the easy way seemed simple enough and I was going to do that but it ended up not working, then I tried using Goo Manager and that soft-bricked my phone and I spent hours getting it back to MK2 again. It's back to the way it was, but I still want to update to Kit-Kat.
Btw, could you tell me why it isn't possible because of my baseband? Thanks failedjedi, and anyone else that can offer useful information.
Cheers,
J
Click to expand...
Click to collapse
With mf3 they locked down the bootloader. So before mf3 you were able to put a custom recovery and custom roms. Since MF3 no one has figured out how to bypass it yet. With mf3 you can use safestrap to sort of get some custom roms, but it still needs to boot the stock kernel as you can't yet use a custom kernel. As a result you are limited to only 4.2.2 Touchwiz based roms working. Now safestrap has a beta for newer versions, not 100% sure what it does and does not support yet as I'm sticking with my mf3 and a 4.2.2 jellybean rom. But the beta is new and probably still buggy.
But basically since you need the stock kernel, you are limited to only the android version your current stock version is.

Yeah as an android developer, I accept that, but am not going to permit it to remain true. This might take awhile...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

If you are a developer there are bounties out for someone to get this working on mf3>
I don't have that issue but good luck if you try--:good:

Thanks! Didn't really know there were bounties for that - worthwhile ones anyway given that im dev apps and messing with AOSP and mainly my att s4 every chance I get.
Actually id be doing it for mk2, and if it becomes apparent that mf3 is easier to do it with ill do with that since I'd just DANGEROUSLY use Odin to go back, root, sideload titpro and block the sht out of the autoupdate. From what ive seen, the intermediary version between mf3 and mk2 might be most likely. This is all conjecture anyway. Sooner or later I will allow people to be free even with contracted or used phones.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Flash ROM & some crazy nintendo graphics

Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!

Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app

^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.

Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.

REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk

John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA

Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.

John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again

Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.

[Q]cm11 on mk2?

im driving myself insane reading threads and getting confused. i just got an s4 i337 and its running mk2. i really want to run cm11 or atleast a stock aosp rom. im not enjoying touchwiz at all. am i even able to do that? i got saferoot and safestrap but after that im confused.

The Jack of Clubs said:
im driving myself insane reading threads and getting confused. i just got an s4 i337 and its running mk2. i really want to run cm11 or atleast a stock aosp rom. im not enjoying touchwiz at all. am i even able to do that? i got saferoot and safestrap but after that im confused.
Click to expand...
Click to collapse
Negative. Only touchwiz based roms will work with 4.3 MK2.
Your best bet is using an AOSP themed ROM such as blackbox or purified. You can find some more info here... http://forum.xda-developers.com/showthread.php?t=2616221
Or, more simply, install a new launcher such as apex or nova and then you won't have to worry about touchwiz

That's extremely disappointing. I'm really starting to hate this phone and I think I'm going to call att tomorrow and see if I can get something else. Perhaps an htc one or lg g2. But this isn't going to work out. This is not the level of customization I want. Touch wiz goes deeper than just the launcher, and what happens in another year or two when att stops providing updates? No, I'm done and I don't want this thing anymore. Bad ATT and bad Samsung.
Sent from my TouchPad using XDA Premium 4 mobile app

The Jack of Clubs said:
im driving myself insane reading threads and getting confused. i just got an s4 i337 and its running mk2. i really want to run cm11 or atleast a stock aosp rom. im not enjoying touchwiz at all. am i even able to do that? i got saferoot and safestrap but after that im confused.
Click to expand...
Click to collapse
I'm no expert, but anything other than MDB and MDL means a locked bootloader. AFAIK that means, all safestrap does is let you load a different rom, but that rom has to be based on the touchwiz kernel. That means no AOSP and that means no CM11. I'm in the same boat.

Hello,
Sorry to revive this after several months of inactivity, but I have exactly the same problem and am confused by the information I have found on XDA, possibly a fault of my own. I have a Galaxy S4 AT&T i337 with MK2 4.3, and I want to run CM11.
A much much more tech savvy friend of mine setup my phone in January 2013 with CM11 using the TWRP recovery. It originally was just the AT&T stock everything. Unfortunately, I no longer have contact with him, and I have no idea how he did any of this . I was specifically running the build from here: http://forum.xda-developers.com/showthread.php?t=2383143, which is now here: http://www.handy-faq.de/forum/galax...h_app2sd_glove_mode_dual_boot_for_all_s4.html
Since then it updated automatically to the last nightlies without any issues. Two days ago, however, I updated, and my phone went into a boot loop. I booted into recovery and tried to flash the last version that worked, but that resulted in my phone staying in a boot loop without being able to boot into recovery. I then used Odin to flash the original firmware and stock ROM, and now it works fine, but I miss CM11 very badly (or more accurately I find the stock ROM annoying in comparison).
The previous posts here indicate that CM11 cannot be installed on the i337 MK2. Also, this thread http://forum.xda-developers.com/showpost.php?p=42320414&postcount=2 lead me to this thread http://forum.xda-developers.com/showthread.php?t=2428254 which says "Also, at this time, only TW based ROMs will work with SS. CM, AOSP, AOKP, MIUI, etc will not work." But I do not actually understand the difference between Safestrap and TWRP enough to know whether or not Safestrap not allowing CM11 means this model won't allow CM11 at all.
I would like to understand why there is indication that CM11 cannot be put on the i337 MK2 when my friend somehow succeeded. Then perhaps we can succeed in devising a method to install CM11 on this model. I apologize for not having any proof that it worked, but I swear I ran CM11 on this exact model and firmware build for many months very happily.
Does anyone have any thoughts on this discrepancy? Sorry if this is a naive/stupid post. Thanks in advance to anyone who chimes in.

[Q] Options with my new AT&T i337 and MF3

Long time XDA reader here and I am in a bit of a pickle here and I haven't been able to come across a difinitive answer. I apologize ahead of time if this question was answered elsewhere, but know that I have just become more confused as I continue to dig. I have some very basic experience with Odin, CWM, TWRP, Safestrap, from past modding/ROM loading. Please be gentle.
I've just recently finished my contract with Verizon, where I was running a Galaxy S3. I intended to hop over to Straight Talk but determined my S3 could only receive Edge data. So, off to sell my phone and buy something new. Swappa fulfilled both purposes easily and fast (shameless plug). I purchased an i337 and am running her on Straight Talk. So far, I am loving every second of the service and, most importantly, the phone.
My new i337 came loaded with the stock AT&T loadset, running 4.2.2, and the MF3 build. I immediately made my way to Cyanogenmod's (CM) site to take advantage of the new Installer. Much to my dismay, the i337 isn't compatible with the new installer. So, off to research and find out how to manually install CM. http://wiki.cyanogenmod.org/w/Install_CM_for_jflteatt I hit a wall with the Loki installer portion. I've done a lot of digging and find that AT&T has apparently locked us in a cage and has limited our recovery options.
I have successfully rooted and installed safestrap. I have used script manager to disable the updates that attempted to download while on wi-fi. For now, I am holding tight on 4.2.2 and MF3. If I understand correctly, I can only use safestrap and not TWRP or CWM. I have read that I can only run TouchWiz ROMs. I am also understanding that I will have to maintain all of the AT&T bloatware ROM on the stock partition (taking up storage space) and place any new TouchWiz-only ROM on a new partition. I am not dead set on Cyanogenmod, just looking to get away from TouchWiz and not have to partition to take up more storage space. I just want one ROM on my phone.
Can anyone please shed some light on any of the following:
1. Should I stay at MF3 or accept the OTA updates?
2.a. What is my best choice for ever running Cyanogenmod?
2.b. If not Cyanogen, what is the next best non-TouchWiz possibility?
Thanks in advance folks!

I would upgrade to NB1 or NC1. More roms like 4.4's
You won't ever "probably" run CM or aosp roms.
No custom recoveries/kernels, only SafeStrap
There is a GPE rom here that is TW based so you can try it. Not perfect but gets you away from some TW. I forget name. Someone may have link.
If not already done, check out Genenal and Q&A for SafeStrap threads and All things MK2 etc. Also an MF3 upgrade thread. I am on MDL so don't need SafeStrap, hence don't have all the links handy.

First off, questions go in Q&A.
Best option would be to sell your device and get the T-Mobile version (bootloader is unlocked).
If you plan to keep this one, you may want to consider doing a carrier unlock while you still can.
Otherwise this guy ^^^ is correct.
Edit:
Two more things...
1) If you decide to sell this device (sell not return), it is worth more if you carrier unlock.
2) Pretty sure this device is no longer supported by CM (last update was February), so you are not missing anything.

rugmankc said:
I would upgrade to NB1 or NC1. More roms like 4.4's
You won't ever "probably" run CM or aosp roms.
No custom recoveries/kernels, only SafeStrap
There is a GPE rom here that is TW based so you can try it. Not perfect but gets you away from some TW. I forget name. Someone may have link.
If not already done, check out Genenal and Q&A for SafeStrap threads and All things MK2 etc. Also an MF3 upgrade thread. I am on MDL so don't need SafeStrap, hence don't have all the links handy.
Click to expand...
Click to collapse
If you are still here the GE rom is in General. Give Thanks to the OP jmsq--:good:

rugmankc said:
If you are still here the GE rom is in General. Give Thanks to the OP jmsq--:good:
Click to expand...
Click to collapse
I decided to take the plunge and accept my fate with this I337. I followed the great guide at the "[INDEX] All things AT&T MK2, NB1, and NC1 (including ROMs)" thread in the General Forum. I am now on NC1 and enjoying the Hyperdrive ROM. Took a little trial and error to get everything up and running (wi-fi in particular), but I'm happy to have dropped the AT&T baggage.
Thank you for the clear cut truth about my poor decision to trust that an AT&T S4 was going to be smooth sailing. If the great minds ever come up with a way to break the bootloader obstacle, I'll be ready to try something new. For now, I'm satisfied with what I have and I'll be trying out some of the other NC1 ROMS around here. I'll give the GE a go next!
Thanks again for the help!

kingamateur said:
I decided to take the plunge and accept my fate with this I337. I followed the great guide at the "[INDEX] All things AT&T MK2, NB1, and NC1 (including ROMs)" thread in the General Forum. I am now on NC1 and enjoying the Hyperdrive ROM. Took a little trial and error to get everything up and running (wi-fi in particular), but I'm happy to have dropped the AT&T baggage.
Thank you for the clear cut truth about my poor decision to trust that an AT&T S4 was going to be smooth sailing. If the great minds ever come up with a way to break the bootloader obstacle, I'll be ready to try something new. For now, I'm satisfied with what I have and I'll be trying out some of the other NC1 ROMS around here. I'll give the GE a go next!
Thanks again for the help!
Click to expand...
Click to collapse
Fantastic, glad you are up and running. The GE has some "not working" items. But, OP page spells that out. Personal choice, but I like reading last 20 pages of any thread I am going to be using, plus all of OP page.
Good Luck--:good: