Hi all! I'll start by saying this, I'm not a COMPLETE noob here. I have had a fair share of experience with rooting and flashing roms; However when i got my new S4 i stepped up in the world of android and am sorta lost now lol. Currently I'm stock MF3 with AT&T, and in a bit I will flash the MK2 update.zip and root then. Well, my understanding of SafeStrap is that it uses the phones memory to make virtual slots for roms, therefor (correct me if I'm wrong) the current system doesn't get wiped. Now I have searched, searched, searched, read, read, AND read, multiple threads trying to find my answers and I've just ended up with confusuion. If my understanding off SS is correct I want a rom that is Stock 4.4.2, Fast, battery enhancing, and most importantly Stable. I saw on in Particular that stood out to me and that was Vision-X but the post to me confused me whether i could use it on the NB1 build. Another question I have: Is NC1 worth it? I've seen that I could do a work around to keep root from NB1 and go to NC1, And Finally my last question (thus far): Can I flash themes i whip up myself with Universal online Theme Kitchen? Is that compatible? I hope that the XDA community can help me once again with my questions and guide me onto the right track. Thanks in advance XDA!!!
DroidWizzy said:
Hi all! I'll start by saying this, I'm not a COMPLETE noob here. I have had a fair share of experience with rooting and flashing roms; However when i got my new S4 i stepped up in the world of android and am sorta lost now lol. Currently I'm stock MF3 with AT&T, and in a bit I will flash the MK2 update.zip and root then. Well, my understanding of SafeStrap is that it uses the phones memory to make virtual slots for roms, therefor (correct me if I'm wrong) the current system doesn't get wiped. Now I have searched, searched, searched, read, read, AND read, multiple threads trying to find my answers and I've just ended up with confusuion. If my understanding off SS is correct I want a rom that is Stock 4.4.2, Fast, battery enhancing, and most importantly Stable. I saw on in Particular that stood out to me and that was Vision-X but the post to me confused me whether i could use it on the NB1 build. Another question I have: Is NC1 worth it? I've seen that I could do a work around to keep root from NB1 and go to NC1, And Finally my last question (thus far): Can I flash themes i whip up myself with Universal online Theme Kitchen? Is that compatible? I hope that the XDA community can help me once again with my questions and guide me onto the right track. Thanks in advance XDA!!!
Click to expand...
Click to collapse
You don't have to upgrade past MK2, and it doesn't matter if you're just going to put a custom ROM on. I believe the ROM you mentioned is compatible, but you could always check the All Things MK2 & NB1 thread. With safestrap on MK2 you'll be able to run both 4.3 and 4.4.2 ROMs by using Om ODIN to switch kernels. As for themes, Safestrap allows all normally flashable zips, so it's a matter of whether the kitchen is compatible.
Thanks for the reply! Currently im Stock NB1 and rooted. I'm going to flash Skyfall.Ill see what happens.
Edit: Flashed Skyfall but for some reason after reboot i get stuck on the Samsung splash screen. I followed the installation guide, am i missing something?
Since i didn't update my bootoader when using the keep root method to NB1 i used Odin to get back to stock MK2. Which SS version should i use to try and flash skyfall?
Related
So, I'm new to the locked bootloader scene. The root & ROM threads, tutorials, and videos seem to root via a Terminal Emulator process, then install Safestrap. Those same sites and videos say that when you're flashing a ROM after selecting a new ROM Slot, you have to flash "whatever modules and packages are for your device", whatever that means. Since I can't find these packages anywhere, is it safe to assume that I can just root, install Safestrap, create a ROM Slot, and start flashing away as if nothing's up? Or do I need to worry about this boot patch and some "Loki Doki" thing I heard about. I'm sure these answers exist, and I've done my due diligence, but these threads have either been buried for good, or are such a common a knowledge subset that I can't find anything concrete. Even the videos I've seen talk about the "modules" you have to flash. I'm an experienced Androidist, tinkerer, and tweaker. The information I'm finding doesn't provide you with the big picture. It's all, "MJ2 read this, and follow these 9 steps", and "mk2 follow these 10 steps". But none of them tell you what to do in Safe strap recovery, and if you needs some Loki/module magic.
Help a brotha out? I'll return the favor 10-fold, I can promise you that much. I'll be quite active around here.
Thanks!
Sent from my Nexus 7 using XDA Premium HD app
First off you never said what baseband you were on but assuming that your on MK2 android 4.3 then let's start.
Use this method to root your device
http://forum.xda-developers.com/showthread.php?t=2569827
Since your on mk2 you can ONLY use safe strap 3.71 do not attempt to install safe strap 3.65 AND SAFE STRAP WILL BE THE ONLY RECOVERY YOU CAN INSTALL!
http://forum.xda-developers.com/showthread.php?t=2448925
And note that 3.71 is still in beta as of right now there are still bugs and YOU CAN ONLY FLASH A COUPLE OF ROMS.
From the same thread cause I know your not going to go through the forums and read, download the attmk2module.zip that ted77usa posted
http://forum.xda-developers.com/showthread.php?t=2448925
Root your device
Install safestrap after install, install recovery in safestrap apk.
There's only a few Roms you can flash
Darthstalker x in the att android development forum
Hyperdrive 12 in the Verizon android development forum download the one that says safestrap
A few have noted that some other Roms work but I haven't tested it out do some more reading.
After you download a rom
Reboot your device and go into safestrap recovery
Create a ROM slot ON ROM SLOT 1
DO NOT MESS WITH YOUR STOCK SLOT!
After creating a ROM slot go to install and install your rom.
After successfully installing a ROM reboot then go back into recovery and install the attmk2module.zip
Reboot and instead of going into recovery this time continue
It will take awhile to load its normal.
Now you should have a ROM.
Now go tinker with that.
AT&T SGH-I337 RUNNING HYPERDRIVE 12
ATTMK2kernelmodules Original Post i don't think u would like to go over 1000 post on that thread..... and at the bottom there is SHOstock_v3.0_Safestrap_Ready link that also confirmed work by several people.......hope this help u to get start it..... .
Bootloader:................Use:...................Custom Rom:
MDL/MDB.......................LOKI.....................4.2.2......4.3.....4.4 ALL WORK (....LUCKY U....)
MF3................................SS-v3.65................ONLY FLASH 4.2.2 ROM (Slot1,Slot2 and Stock ALL WORK)
MK2................................SS-v3.71................SOME 4.3 ROM WORK (Slot1,Slot2 and Stock ALL WORK (confirmed))
[email protected] said:
First off you never said what baseband you were on but assuming that your on MK2 android 4.3 then let's start.
Use this method to root your device
http://forum.xda-developers.com/showthread.php?t=2569827
Since your on mk2 you can ONLY use safe strap 3.71 do not attempt to install safe strap 3.65 AND SAFE STRAP WILL BE THE ONLY RECOVERY YOU CAN INSTALL!
http://forum.xda-developers.com/showthread.php?t=2448925
And note that 3.71 is still in beta as of right now there are still bugs and YOU CAN ONLY FLASH A COUPLE OF ROMS.
From the same thread cause I know your not going to go through the forums and read, download the attmk2module.zip that ted77usa posted
http://forum.xda-developers.com/showthread.php?t=2448925
Root your device
Install safestrap after install, install recovery in safestrap apk.
There's only a few Roms you can flash
Darthstalker x in the att android development forum
Hyperdrive 12 in the Verizon android development forum download the one that says safestrap
A few have noted that some other Roms work but I haven't tested it out do some more reading.
After you download a rom
Reboot your device and go into safestrap recovery
Create a ROM slot ON ROM SLOT 1
DO NOT MESS WITH YOUR STOCK SLOT!
After creating a ROM slot go to install and install your rom.
After successfully installing a ROM reboot then go back into recovery and install the attmk2module.zip
Reboot and instead of going into recovery this time continue
It will take awhile to load its normal.
Now you should have a ROM.
Now go tinker with that.
AT&T SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
You're perfect in every way. ? Bromance FTW
You even answer threads like me. This helped a TON! I owe ya one.
Edit: last question. The instructions say to install the ROM, reboot, then install the modules. I assume that the reboot instruction means that we should reboot, boot into the ROM for the first time, then boot back into recovery and install the modules?
Or should I flash the ROM, power down, then boot into recovery (ensuring that the ROM is never booted before the modules are installed)-- I suppose I could just use the reboot recovery option in the Safestrap TWRP.
Sent from my Nexus 7 using XDA Premium HD app
ted77usa said:
ATTMK2kernelmodules Original Post i don't think u would like to go over 1000 post on that thread..... and the on the bottom is SHOstock_v3.0_Safestrap_Ready link that also confirmed work by several people.......hope this help u to get start it..... .
Bootloader:................Use:...................Custom Rom:
MDL/MDB.......................LOKI.....................4.2.2......4.3.....4.4 ALL WORK (....LUCKY U....)
MF3................................SS-v3.65................ONLY FLASH 4.2.2 ROM (Slot1,Slot2 and Stock ALL WORK)
MK2................................SS-v3.71................SOME 4.3 ROM WORK (Slot1,Slot2 and Stock ALL WORK (confirmed))
Click to expand...
Click to collapse
What's SHOStock? An alternative to the ATTMK2Module?
<3 I can see that this is a bangin' start to an awesome and new relationship, between me, my S4, and my new home...the S4 community.
Sent from my Nexus 7 using XDA Premium HD app
By the way...since the ROM selection is limited, I assume heavy XPosed use is okay, and quite common?
Which ROM do you guys prefer?
I assume that sites and articles like this one: http://www.droidviews.com/best-custom-roms-for-att-samsung-galaxy-s4-sgh-i337/
aren't reliable sources--they probably don't take into account the the ATT S4 compatibility issues. This is showing CM11, Carbon, KangaBean, Infamous...am I correct in my assumption that those are for the lucky birdies that had MDL/MDB, and didn't need Safestrap?
Has someone put together a compatibility/guide megathread? I think I will if it hasn't been done.
Sent from my Nexus 7 using XDA Premium HD app
Jamesyboy said:
What's SHOStock? An alternative to the ATTMK2Module?
<3 I can see that this is a bangin' start to an awesome and new relationship, between me, my S4, and my new home...the S4 community.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Welcome aboard!!!! Firstable are u on MF3 firmware or MK2 frimware......? both are using SafeStrap (SS) as custom recovery as of right now. Like i said on previous post MF3 use SS-v3.65 so that u able to install only 4.2.2 TW custom rom or 4.2.2 Google Play Edition (GPE) rom. If u are on MK2 firmware u can only use SS-v3.71 and able to install some of 4.3 custom rom (SHOstock-v3.0-Safestrap-Ready) is one of them that worked......Hyperdrive-RL12 from verizon thread also seem pretty good but u need to add your APN manually if u are on ATT network. Both firmware MF3 and MK2 are use different kernel modules, so after flashing custom Rom you NEED to flash your current firmware kernel modules also, otherwise u won't be able to connect to WiFi,bluetooth,gps etc..... hope this make sense to you......i know is kinda confusing ......but the more u read is the more it would make sense.... Check this thread for list of compatible rom Official AT&T S4 Safestrap Discussion Q/A
One more thing. My S4 will be here tomorrow. Let's say I get lucky and find MDL/MDB on my device. Do I need to hurry and avoid a software update, or avoid a data connection? Or do the updates proceed only with user interaction? The rooting is the same for all 3 devices, but if I do get MDL/MDB or the next one, I'll have to update the baseband before flashing newer ROMs, right?
Sent from my Nexus 7 using XDA Premium HD app
ted77usa said:
Welcome aboard!!!! Firstable are u on MF3 firmware or MK2 frimware......? both are using SafeStrap (SS) as custom recovery as of right now. Like i said on previous post MF3 use SS-v3.65 so that u able to install only 4.2.2 TW custom rom or 4.2.2 Google Play Edition (GPE) rom. If u are on MK2 firmware u can only use SS-v3.71 and able to install some of 4.3 custom rom (SHOstock-v3.0-Safestrap-Ready) is one of them......Hyperdrive-RL12 from verizon thread also seem pretty good but u need to add your APN manually if u are on ATT network. Both firmware MF3 and MK2 are use different kernel modules, so after flashing custom Rom you NEED to flash your cureent firmware kernel modules also otherwise u won't be able to connect to WiFi,bluetooth,gps etc..... hope this make sense to you......i know is kinda confusing ......but the more u read is the more it would make sense....
Click to expand...
Click to collapse
It makes sense, I'm mostly just unfamiliar, as opposed to being completely useless, but you guys have been amazing...you've already shot me up to about 80% on a distribution curve.
Why would anyone stick with MF3? MK2 is an update for MF3, right? Why don't those users update, then safestrap 3.71 it, so they can use 4.3 roms? It'd seem kinda funky to me to be stuck with a 4-2 ROM by choice, unless they're doing it solely for the GPE ROM.
These firmware kernel modules...I'll have the same modules for each ROM I flash right? Or are these modules a .zip that I'll find in each ROM thread, for each carrier.
By the way, APN settings don't scare me. Here, you might actually appreciate this work--done right after ATT's LTE network came online (I believe the Note was the first device that utilized it?...If it wasn't, it was definitely the first to tax the network.)::
http://forum.xda-developers.com/showthread.php?p=26877683
Edit: the Q&A thread for Safe strap was reasonable...but it still talks about kernel flashes, and blown QFusee (har?)
I guess I mainly need to come to grips with the kernel situation. The Q&A says that you can't use custom kernels if you've updated to OTA, but doesn't mention factory MF3 builds, and it isn't really very clear about the module/kernel module situation.
You said I need to flags my **current** firmware kernel modules: are those different if I get a device with MF3 than those for MK2? Or are these just modules that I create myself (based upon whatever's in my stock ROM slot maybe?) in recovery?
Sent from my Nexus 7 using XDA Premium HD app
Jamesyboy said:
One more thing. My S4 will be here tomorrow. Let's say I get lucky and find MDL/MDB on my device. Do I need to hurry and avoid a software update, or avoid a data connection? Or do the updates proceed only with user interaction? The rooting is the same for all 3 devices, but if I do get MDL/MDB or the next one, I'll have to update the baseband before flashing newer ROMs, right?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I dont think u can get MDB/MDL firmware again these days.....but if u do....damn u are pretty lucky....my suggestion is Do Not insert your ATT sim card yet ....since they can do OTA update ( On The Air ).....and check your baseband....IF u do ....root it right away....install titanium back up and freeze/uninstall ATT software update.apk......install custom recovery CWM or TWRP ..... and make sure u have auto loki recovery....if not save loki.doki patch on your Sd Card....PM me for the link and all the files .....i still have the files since i used to have MDB firmware and got replacement phone from ATT when my son broke the screen....:crying:
Jamesyboy said:
It makes sense, I'm mostly just unfamiliar, as opposed to being completely useless, but you guys have been amazing...you've already shot me up to about 80% on a distribution curve.
Why would anyone stick with MF3? MK2 is an update for MF3, right? Why don't those users update, then safestrap 3.71 it, so they can use 4.3 roms? It'd seem kinda funky to me to be stuck with a 4-2 ROM by choice, unless they're doing it solely for the GPE ROM.
These firmware kernel modules...I'll have the same modules for each ROM I flash right? Or are these modules a .zip that I'll find in each ROM thread, for each carrier.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
MDB>MDL>MF3>MJ6>Mj9>MK2.......the reason of the update is ATT trying to lock bootloader so we won't be able to install custom rom or do what ever we want to the phone.......but either way.....XDA member always found away to cracked it....so some people have to upgrade not by choice.....most of them by accident....like me ( cracked my screen ) or they install wrong recovery.....(bricked) so be careful when installing custom recovery.....like i said....we need to know what kinda firmware that u have so we can help u.....LOL now i got it why u dont know yet....since u dont have the phone yet.......... but is ok.....that's the right thing to do.....get to know your stuff first before u brick your phone.....:good: so basically u need to match your kernel modules with your firmware otherwise it won't be able to connect to Wifi,bluetooth,gps,etc it doesn't matter if u OTA to MF3 or MK2.....or it come with MF3 or MK2....
ted77usa said:
I dont think u can get MDB/MDL firmware again these days.....but if u do....damn u are pretty lucky....my suggestion is Do Not insert your ATT sim card yet ....since they can do OTA update ( On The Air ).....and check your baseband....IF u do ....root it right away....install titanium back up and freeze/uninstall ATT software update.apk......install custom recovery CWM or TWRP ..... and make sure u have auto loki recovery....if not save loki.doki patch on your Sd Card....PM me for the link and all the files .....i still have the files since i used to have MDB firmware and got replacement phone from ATT when my son broke the screen....:crying:
MDB>MDL>MF3>MJ6>Mj9>MK2.......the reason of the update is ATT trying to lock bootloader so we won't be able to install custom rom or do what ever we want to the phone.......but either way.....XDA member always found away to cracked it....so some people have to upgrade not by choice.....most of them by accident....like me ( cracked my screen ) or they install wrong recovery.....(bricked) so be careful when installing custom recovery.....like i said....we need to know what kinda firmware that u have so we can help u.....LOL now i got it why u dont know yet....since u dont have the phone yet.......... but is ok.....that's the right thing to do.....get to know your stuff first before u brick your phone.....:good:
Click to expand...
Click to collapse
Groovy! I'll check back in tomorrow! Happy New Years!
(Sent you a PM, as well.)
Sent from my Nexus 7 using XDA Premium HD app
I am really new to this, so I apologize if I seem ignorant. Last time I went down this road, I didn't do my research and accidentally messed up the stock recovery. I am now unrooted and running the following:
AT&T Galaxy S4
Android 4.4.2
Build: KOT49H.I337UCUFNC1
Here's what I want to do:
Root my device
Install SafeStrap recovery (I don't know if this is still compatible since the KitKat update)
Use SafeStrap to run a custom ROM that's closer to stock android. Maybe CM or something AOSP based. Like I said, I don't know much about this.
Please let me know if I'm barking up the wrong tree. I'm just getting really tired of TouchWiz. Up until now I've just been sideloading Google Now Launcher and some other stock apps like the Clock and Calculator. Once again, I apologize for my ignorance - I'm still working on learning more about this. Thanks in advance!
go4bacon said:
I am really new to this, so I apologize if I seem ignorant. Last time I went down this road, I didn't do my research and accidentally messed up the stock recovery. I am now unrooted and running the following:
AT&T Galaxy S4
Android 4.4.2
Build: KOT49H.I337UCUFNC1
Here's what I want to do:
Root my device
Install SafeStrap recovery (I don't know if this is still compatible since the KitKat update)
Use SafeStrap to run a custom ROM that's closer to stock android. Maybe CM or something AOSP based. Like I said, I don't know much about this.
Please let me know if I'm barking up the wrong tree. I'm just getting really tired of TouchWiz. Up until now I've just been sideloading Google Now Launcher and some other stock apps like the Clock and Calculator. Once again, I apologize for my ignorance - I'm still working on learning more about this. Thanks in advance!
Click to expand...
Click to collapse
I don't know if you went down this road before since your questions don't show.
1. You can't install custom recoveries or roms on the build you have.
2. You can only downgrade to Mk2 to root since it's imposible to root on your present build.
On the general section there are a few threads that guide you to downgrade ,root, and flash compatible roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
go4bacon said:
Maybe CM or something AOSP based. Like I said, I don't know much about this.
Click to expand...
Click to collapse
Not gonna happen, at least for now. The best you could do is PurifieD which completely trashes TouchWiz's theme. You'd also have to follow the steps here to get root on NC1. I'd advise against taking the bootloader but I believe you already have it if you took NC1 OTA. Then you could flash PurifieD over your stock slot in Safestrap 3.72.
Basically:
Root via downgrading to MK2
Flash rooted NC1 (no BL)
Install and boot into Safestrap 3.72, flash PurifieD (wipe not necessary)
If you wish to keep Knox happy with 0x0, do not let PurifieD modify the kernel during the Aroma installer
Flash an i337 build.prop in order to get 4G LTE working again (you have service without this, but this lets you access LTE again) (you can find this here!)
Flash the WiFi module in order to get wifi working again (WiFi will NOT work unless you flash this) (you can find this here!)
(Optional, I had to do this as I had issues with keeping root on PurifieD, though you might not!) Flash SuperSU again (you can find this here!
Feel free to ask for more help if anything was not clear!
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
nola mike said:
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
Click to expand...
Click to collapse
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
nola mike said:
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
Click to expand...
Click to collapse
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
jmjoyas said:
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
Click to expand...
Click to collapse
Thanks for that, very enlightening.
nola mike said:
Thanks for that, very enlightening.
Click to expand...
Click to collapse
Just as an update, seems there's a workaround for Odin called heimdall, which is cross platform. . Haven't tried it, but looks like it should work.
Okay, so I'm almost positive there is probably a thread for this, but I'm having trouble finding exactly what I'm looking for and very new to doing all of this on my own. I usually have a buddy help me out (aka he does it all).
I am running 4.4.2 Kit Kat on NC1 and I was finally able to root my device using TowelRoot. I've been trying for days now to install ClockworkMod custom recovery, but to no avail. Odin has failed, the command prompt method has failed, and Rom Manager app has failed. Is there just no compatible builds for any of this? I'm not entirely sure how this all works or why any of it is failing. What can I do to install CWM or TWRP and get CM11 back on? I need all kinds of explanation, so don't skimp on the details! Thanks guys!
You can't install clockwork. You have to use safestrap. Read the all things mk2, nc1 thread. It will tell you just about everything you need to know. Is an awesome thread and how I learned everything about this phone.
bweekzzzz said:
You can't install clockwork. You have to use safestrap. Read the all things mk2, nc1 thread. It will tell you just about everything you need to know. Is an awesome thread and how I learned everything about this phone.
Click to expand...
Click to collapse
Awesome! That's exactly the direction I'm looking for! Thank you so much.
No problem at all. We've all needed help on here from time to time. Good luck.
Great advice above. To add to it you will NOT be able to use CM11 on your device at this time or probably ever. Also you will NOT be able to ever flash CWM or TWRP recoveries.
You can ONLY use safestrap recovery which ONLY allows flashing Touchwiz based Roms.
You can ONLY flash Touchwiz based Roms because with Safestrap it will NOT flash any custom kernels. A custom Kernel is need to flash CM11, AOKP, and other AOSP Based roms.
You also CANNOT downgrade your bootloader as it is locked down hard. The locked down boot loader is why all above cannot work for your device. ONLY the original phones that came with MDB or MDL firmwares were able to use the Loki Bootloader Bypass, which allowed for flashing CWM or TWRP recoveries and then allow ANYTHING like any custom Roms (also based or Touchwiz based), flash custom kernels, flash anything. But any phone updated to the MF3 firmware or newer the boot loader was locked down too much to do much.
Sent fron I337 Red BadAss Themed ShoStock 7.0
Ok, I have been running an OLD version of SACs custom ROM for a while (Pre Kitkat I think).
I am considering going back to stock Rooted with the Hotspot mod only.
I've been out of the "flashing" scene for a while, so what's the easiest way to go back to current stock w/ rooted & hotspot mod? If you could point me in the right direction, I would appreciate it!
1. Please don't post questions in the development forum.
2. Find Unknownforce's stock rooted NAE thread.
3. Read and follow his directions.
frostedunit said:
1. Please don't post questions in the development forum.
2. Find Unknownforce's stock rooted NAE thread.
3. Read and follow his directions.
Click to expand...
Click to collapse
Ahh... Sorry. I was looking at this forum and the Q&A forum at the same time. Thought I was posting in there.
Thanks, I'll look up his.
Been reading different threads. So if I just flash i Rooted NAE ROM I should be ok? I just want to make sure since I am coming from an OLD version of SACS.
AzWizzard said:
Been reading different threads. So if I just flash i Rooted NAE ROM I should be ok? I just want to make sure since I am coming from an OLD version of SACS.
Click to expand...
Click to collapse
You'll probably have to Odin the NAE modem as well. Somewhere in unknown's thread are the instructions to do and keep a pre Knox bootloader
Ok, 1 more question...
If I want to go back to complete stock from the old SACS Rom...
Could I just flash a stock MDL to my phone and then tell the phone to update it's self and let it OTA update to current version?
Would there possible be any problems with that?
Just curious as I have an old stock MDL already on my computer from when I was flash long ago.
I know this way I would have KNOX but I honestly don't really care too much.
That will take a bit, but will work for sure.
AzWizzard said:
Ok, 1 more question...
If I want to go back to complete stock from the old SACS Rom...
Could I just flash a stock MDL to my phone and then tell the phone to update it's self and let it OTA update to current version?
Would there possible be any problems with that?
Just curious as I have an old stock MDL already on my computer from when I was flash long ago.
I know this way I would have KNOX but I honestly don't really care too much.
Click to expand...
Click to collapse
You should not do this! If you have a newer bootloader than the MDL install will fail. All you need to do is download the full NAE tar file and install it. You will be updated in one step and you won't lose data. you can get the full NAE tar from here: http://forum.xda-developers.com/showthread.php?t=2663619