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

[Q] Please Help!

So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.

khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?

Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.

khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723

Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??

khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876

Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha

khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?

Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol

khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558

Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?

khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.

"New" comer here, I need some help please

Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks

Arturofm2 said:
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Click to expand...
Click to collapse
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?

https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
follow this (use odin to flash rooted kernel) ......you should search before posting things like this.....google is your friend bro.
GOOD LUCK - BTW use flash fire app in play store to make backups and flash roms

Okay okay.
A quick glance at T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion would have led you to the "How to root the S7 EDGE" thread.
I'd take a look in there if I were you.

Binary100100 said:
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
Click to expand...
Click to collapse
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more

Arturofm2 said:
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
EDIT: I just checked and the root didn't go through... even though ODIN said it was successful
Click to expand...
Click to collapse
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.

Binary100100 said:
What you wrote above
Click to expand...
Click to collapse
So for what I understood the dev support for this phone is very limited... I know the issues I may encounter, I had them with the galaxy note. but any way... If something I'll unroot it but I want to try it out Thank for you time. I've rooted it.
EDIT: Damn... I really don't like the visual style of Echoe... is that one the only one I can flash??

Binary100100 said:
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Click to expand...
Click to collapse
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?

Arturofm2 said:
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Click to expand...
Click to collapse
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.

Binary100100 said:
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Click to expand...
Click to collapse
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T

Arturofm2 said:
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Click to expand...
Click to collapse
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?

Binary100100 said:
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Click to expand...
Click to collapse
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?

Arturofm2 said:
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Click to expand...
Click to collapse
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammmobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.

forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.

Binary100100 said:
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
Click to expand...
Click to collapse
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I didn't do it through that page. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?

tduquefjc said:
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Click to expand...
Click to collapse
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?

Arturofm2 said:
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I kept it. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
Click to expand...
Click to collapse
Arturofm2 said:
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Click to expand...
Click to collapse
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.

Binary100100 said:
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Click to expand...
Click to collapse
Perfect! All I did was reboot it, and the unlocked padlock went away, thank you very much for all your help! Happy new year!

What happens if I...?

So. Here we are.
The Samsung Galaxy S9 and S9+ have been released, and many of us are just now hopping on the S8/+ bandwagon. I, very recently, purchased a SM-G955U model variant of the S8+ (hence the second 5 :silly and, like many of you, wanted to root it as soon as I got my hands on it.
I was happily impressed when I hopped on XDA and saw that there were at least *some* relatively updated custom ROMs and root methods. I tried out several using Odin3 (PCR.. and SamPWND... cuz those were the only two relatively popular threads that I found in my 2 minute search) and PCR struck my eye. I downloaded all the necessary files, taking well over 30 minutes on my potatonet, made sure I had both Odin3 and PrinceComsy Odin3 (and Kies... I think that's still relevant), setup the BootLoader, AP, whatever all the other buttons do, and clicked start.
Waited for a few seconds and... a (Succeed 0 / Failed 1) message appeared, as soon as it started.
Looked at my phone, the realization that it wasn't in Download mode kicked in and I smacked myself in the face.
Rebooted into Download mode, reset PrinceComsy Odin, smashed all the buttons again, clicked start and..
(Succeed 0 / Failed 1).
Great.
This has repeated for 3 days now, on all computers, 10s of different USB cables, well over 20 different USB ports (hubs not included).
So, I decided at a different approach. I'm sure we all know those "CLICK ME DOWNLOAD ME FOR FREE ROOT I-I CAN REALLYDO IT GUYS JU-JUST DOWNLOAD ME!* advertisements. One in particular struck my eye, no names will be given, and I tried it out.
Downloaded the Windows executable for the laughs and giggles (never thinking it would actually work) and whaddya know, right after telling me my device is rootable it's now asking me for 40$.
I figured, what the hell, I just got paid and sent the money over thinking I was about to get scammed. Hoped on live chat and setup everything the way they asked me to (taking even longer than a grandma driving because potatonet) and they start, and I'm not joking, REMOTE CONTROLLING my PC to root my phone (granted, the root method for my phone was advertised, blatantly stating they would have to control my PC but.. come on).
At this point all I can think about is how I'm lucky I have a throwaway PC and this phone doesn't mean my life or I would be really pissed when I start seeing a worm come out of my harddrive.
Needless to say the process took about an hour, maybe an hour and a half (much longer than their *15-20 minute* claim time, but not awful nonetheless) and I walked out of there with a non-bricked rooted S8+.
So.. what exactly went wrong with my setup, and how can you guys avoid spending 40$ just to ROOT YOUR PHONE.
I'm not a professional. I can't offer professional advice. But what I can tell you is I know exactly what went wrong for me in this case.
I never flashed the 7.0 stock android ROM. I was trying to flash PCR (which, ironically enough is what said company used.. yes.. they used PCR. Not a custom method. Not a custom ROM. They literally used PCR) over 8.0.
So, I'm out 40$, but walked out with a rooted S8+ and I'm fairly happy. Apparently those root programs aren't ALL bad.
But seriously.. why aren't there any 8.0 ROMs or root methods that actually work? Every method I've seen requires you to downgrade. I know Oreo only came out last month but there are some seriously talented people here on XDA and the fact that I had to downgrade just to have to reflash in about a month or twos time is frustrating to say the least. But, that's just venting and off-topic.
So, laugh at the idiotboy who couldn't figure out how to read instructions properly or setup his project right, but just know.. just know.. I spent 40$ to root my phone. And that, my friends, is an amazing feat.
(Also, I apologize if this isn't in the right section.. I feel like it's not but I have NO idea where else to post this. This is more of a story thread to make myself the eye of the public humiliation but it does also serve as a reminder to really check everything before you start rooting. I got lucky. I could have potentially hardbricked my brandnew s8+ simply because I didn't read the instructions properly, or plan correctly. This is something that a lot of new users fail to do, and then complain when *their phone is stuck in a bootloop*.
If you don't know what you're doing, there are plenty of people here on XDA and apparently all over the web who will be more than happy to take your money and root your phone, relatively safely, for you.)

well as jrkruse said
"root is not going to happen unless on of two things happen. Either we get combo oreo firmware so we have an oreo boot.img that is permissive or they event root that will work on stock enforcing boot.img for oreo because you can not modify the boot.img on a locked bootloader. Systemless root like on S7 will not work unless we have an eng boot.img with security set to 0 like the s7 has, so that scripts can execute at time of boot to allow a systemless type of supersu to run. I personally would not expect root anytime soon as if you look back at whats been released for combo firmware it only seems to be firmware for the original software that came on the phone. They just update the bootloaders to match the version number so that you can still flash the nougat combo firmware, but I doubt we see oreo combo firmware. It just has not happened on earlier models. The S7 has been lucky that eng boot.img have been released for nougat but the s8 would require also eng bootloaders to be released as you simply cant flash an eng boot.img on regular bootloaders like you can on the s7. There is always hope but in this case it is really dim but we do have some options with safestrap and modded system images but this part could come to an end at anytime if samsung patches the samfail method so enjoy what you have for now"

I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?

Ryan8675309 said:
I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?
Click to expand...
Click to collapse
there is only one rooted rom for 950/5 u do not flash f stuff on your phone not only will it fail in odin but if by some weird act of craziness and worked you would be probably near hardbricked

ghxstt said:
But seriously.. why aren't there any 8.0 ROMs or root methods that actually work? Every method I've seen requires you to downgrade. I know Oreo only came out last month but there are some seriously talented people here on XDA and the fact that I had to downgrade just to have to reflash in about a month or twos time is frustrating to say the least. But, that's just venting and off-topic.
Click to expand...
Click to collapse
There actually is a form of root for Oreo but it's not exactly root because you only have access to r/w in recovery/safestrap
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206/page1

Ryan8675309 said:
I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?
Click to expand...
Click to collapse
EDIT; I misread your thread. I thought you were saying you had a G95xF device you were going to throw a G95xU ROM on.
If you have a G95xU device, here is what I used to flash my ROM/root https://forum.xda-developers.com/ga...root-partcyborgrom-aqk3-samfail-odin-t3717702.
If you have a G95xF device, I cannot give you any links because I haven't done any research into that firmware.
EDIT 2; My points still stand. Do NOT flash custom ROMs on your phone that aren't for your phone model. You will ruin your phone.
Just don't. It's not worth it.