Updated the OP with pointers to tools to tell the bootloader version and to mention the developer edition.
Updated the OP with pointers to tools to tell the bootloader version and to mention the developer edition.
Once rooted can the stock MK2 ROM be backed up like normal and reinstalled because its not a custom ROM or am I completely locked into doing the ODIN Recovery. I looked and cannot seem to find an answer for this.
On my Samsung tablet I have used cwm but since this phone has a locked boot loader I am assuming I can't back it up before I start to modify anything.
Once rooted can the stock MK2 ROM be backed up like normal and reinstalled because its not a custom ROM or am I completely locked into doing the ODIN Recovery. I looked and cannot seem to find an answer for this.
As decaturbob said, you can install Safestrap recovery and back it up using that. Then, if you need to, you can re-flash to stock using ODIN, re-root, install Safestrap, then restore the backup. It may be easier, however, to restore apps using something like Titanium Backup.
If I use safe strap is there any chance that I could trigger knox?
Using Safestrap won't set the Knox Warranty Void flag. However, you need to understand what DOES set the flag: attempting to flash either an unsigned kernel or recovery, or flashing an older recovery.
So, if you root with Saferoot, then install Rom Manager and try to flash CWM on a Knox-enabled device, that will probably trip the Knox Warranty Void flag. That's not Saferoot's fault.
If you install Safestrap on MK2 and try to use it to restore a MDK nandroid backup, it'll also probably trip the flag. That's not Safestrap's fault.
I say "probably" above because I think in both of these cases, the flash will fail but not set the flag. It appears that only using ODIN to try to flash unapproved firmware actually trips the flag. However, I'm not going to experiment with my phone.
You have to be aware of what can and can't be done. There's a lot of misinformation and incomplete information out there, particularly you tube videos explaining how to install CWM on a "Galaxy S4" that NEVER mention that it's an unlocked Sprint phone. Or that it only works on MDK bootloaders. There's rooting techniques here on XDA for MDK that say "Not for ME7" when they should say "Not for anything past MDK". So, it's kind of a minefield. Read, learn, and be careful what you do. At the very least, you're risking a soft brick by messing about too much.
[B I really don't need to install a different ROM at this time but I am wanting to remove some of the Bloat, Seems safe to say If I "screw up" I can use ODIN and reinstall the OEM MK2 and be safe?
Thanks for all your help.
Yup, there's always the stock ROM to recover from if you mistakenly remove too much.
One last Question: If I have read correctly flashing a stock MK2 ROM with ODIN will NOT trigger a KNOX 0x1 flag?
Is there a way to flash modems on At&t SGS4 that has mf3 bootloader??
I couldn't find any thread on xda about.. Very sorry to post this here.
How the hell does this thread only have 6 pages? And why have only 26 users thanked this extremely helpful member?:fingers-crossed::good::good::good:
THANKS
THANKS
THANKS
THANKS
THANKS
THANKS
THANKS!!! If I could hit the Thanks button that many times, I would!
Thanks.
I tried to sticky this, but as there's a similar thread in the General forum already stickied, it would be redundant.
Thanks.
I tried to sticky this, but as there's a similar thread in the General forum already stickied, it would be redundant.
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is the original MDK baseband. Not checking first before flashing will often break your phone.
If you need to know what baseband you're on, use "Settings", "More", "About phone" and scroll down to the "Baseband Version".
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're on the MDK baseband. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
many guides and threads that everyone needs to read to understand the process of what they are getting into before they brick their phone and it costs themselves some money.