Related
Hello all, hopefully this will help give some clarification for users, especially ones who have a newer SGS3, who are experiencing issues trying to flash certain ROM's and are getting errors due to assert/bootloader checks.
There is a specific part of a ROM .zip file called the updater-script which contains a security feature known as the assert lines. These parts of the script look for a bootloader match prior to flashing to ensure the ROM is compatible with the phone. This is used when there are multiple variants of one phone, such as the SGS3, which is available from Sprint, AT&T, T-Mobile, and some international variants. Flashing a ROM meant for a different carrier can have disastrous consequences, so developers include this bootloader check as a CYA measure. Here is where a lot of newer users are running into trouble and are choosing a "fix" which is incorrect. If your phone has MK3 (Sprint) or MK5 (Virgin Mobile/Boost) as the bootloader (not the modem, will address that later), then you have a bootloader which is not recognized for 4.3.x or earlier builds of CyanogenMod or custom ROM's based on AOSP. The CM 11 builds do recognize MK3, so will flash fine with no modification needed for rooted users. More importantly though, if MK3 or MK5 is your bootloader, then you have Knox as well, and Knox will fight any attempt to replace it with another bootloader, as in it will brick your phone badly. Therefore, MK3 and MK5 users who think their flash has failed because they need a different bootloader and then proceed to change their firmware, either with a "return to stock" .tar file via Odin or a flashable .zip designed to change the firmware have just inadvertently bricked their phone.
Here are some rules of thumb:
1. Know what is on your phone! Be aware of what bootloader you have, specifically you need to know if you have Knox or are Knox-free. If you are Knox-free, congratulations, if you have Knox, my condolences. In the Knoxed-up situation NEVER EVER try to push, via Odin a .tar file designed to "return to stock" if the bootloader associated with that file is MD4 or earlier (Sprint users) or MG2 or earlier (VM/Boost). Sprint users also have .zip files available designed to do the same thing, avoid these as well if you have Knox. Flashing a ROM with an earlier Android build is just fine, there is no bootloader included in a custom ROM based on AOSP, contrary to what some people are posting. You can "downgrade" to an earlier build of Android if you wish, you absolutely CANNOT downgrade your bootloader if you already have Knox on your phone.
2. If you get an "assert failed" message, you just need to modify or delete the asserts to match your bootloader, you do not need to change the bootloader itself. DO NOT assume that changing your bootloader is a fix for anything without knowing what you are doing first.
3. Modem does not equal bootloader. We use the same nomenclature (MD4, MK3, etc.), which can be confusing, but modems are interchangeable, and there are .zip files available so that you can easily flash from one to another. Additionally, anybody who has an SPH-L710 can use any modem designed for Sprint, VM, or Boost. A lot of Sprint users actually achieved great signal/data results with the MG2 modem from VM/Boost, and I have used MK3 modem just fine myself (I am on VM). ROM .zip files don't care about your modem, only your bootloader.
I hope this helps, I am seeing way too many users asking why they bricked their phones when this information would have helped them in advance had they not just forged ahead and assumed the bootloader was the problem. If anyone would like to know how to safely modify or delete the assert lines please let me know via posting or PM.
Useful information.
One item that could use some clarification is how to know whether a package includes a bootloader, and whether the assert line in the script will work with the Knox bootloader?
poit said:
Useful information.
One item that could use some clarification is how to know whether a package includes a bootloader, and whether the assert line in the script will work with the Knox bootloader?
Click to expand...
Click to collapse
For the most part, as far as I know any custom ROM in the Original Android Development section, as well as anything AOSP based in the Android Development section will never contain a bootloader. The ROM's that do should be clearly (hopefully!) labeled as being "return to stock" (wording may vary), with the specific bootloader listed, and will almost always be a .tar file, not a .zip file. If it is a .zip, there should be some mention of "firmware" involved. This is not set in stone, just what I have seen in the various titles.
As to the assert lines, one of them just has to be an exact match for the bootloader designation, Knox or otherwise. If you have managed to install custom recovery and root post-Knox (it is possible, just can be a little bit of a headache), then Knox is a non-issue in terms of the assert lines and the bootloader check, the check is not looking for Knox, it is looking to see if any one of the several bootloaders listed in the asserts is present on the phone before proceeding.
using sprint stock rom on boost mobile s3
Mr. Struck said:
Hello all, hopefully this will help give some clarification for users, especially ones who have a newer SGS3, who are experiencing issues trying to flash certain ROM's and are getting errors due to assert/bootloader checks.
There is a specific part of a ROM .zip file called the updater-script which contains a security feature known as the assert lines. These parts of the script look for a bootloader match prior to flashing to ensure the ROM is compatible with the phone. This is used when there are multiple variants of one phone, such as the SGS3, which is available from Sprint, AT&T, T-Mobile, and some international variants. Flashing a ROM meant for a different carrier can have disastrous consequences, so developers include this bootloader check as a CYA measure. Here is where a lot of newer users are running into trouble and are choosing a "fix" which is incorrect. If your phone has MK3 (Sprint) or MK5 (Virgin Mobile/Boost) as the bootloader (not the modem, will address that later), then you have a bootloader which is not recognized for 4.3.x or earlier builds of CyanogenMod or custom ROM's based on AOSP. The CM 11 builds do recognize MK3, so will flash fine with no modification needed for rooted users. More importantly though, if MK3 or MK5 is your bootloader, then you have Knox as well, and Knox will fight any attempt to replace it with another bootloader, as in it will brick your phone badly. Therefore, MK3 and MK5 users who think their flash has failed because they need a different bootloader and then proceed to change their firmware, either with a "return to stock" .tar file via Odin or a flashable .zip designed to change the firmware have just inadvertently bricked their phone.
Here are some rules of thumb:
1. Know what is on your phone! Be aware of what bootloader you have, specifically you need to know if you have Knox or are Knox-free. If you are Knox-free, congratulations, if you have Knox, my condolences. In the Knoxed-up situation NEVER EVER try to push, via Odin a .tar file designed to "return to stock" if the bootloader associated with that file is MD4 or earlier (Sprint users) or MG2 or earlier (VM/Boost). Sprint users also have .zip files available designed to do the same thing, avoid these as well if you have Knox. Flashing a ROM with an earlier Android build is just fine, there is no bootloader included in a custom ROM based on AOSP, contrary to what some people are posting. You can "downgrade" to an earlier build of Android if you wish, you absolutely CANNOT downgrade your bootloader if you already have Knox on your phone.
2. If you get an "assert failed" message, you just need to modify or delete the asserts to match your bootloader, you do not need to change the bootloader itself. DO NOT assume that changing your bootloader is a fix for anything without knowing what you are doing first.
3. Modem does not equal bootloader. We use the same nomenclature (MD4, MK3, etc.), which can be confusing, but modems are interchangeable, and there are .zip files available so that you can easily flash from one to another. Additionally, anybody who has an SPH-L710 can use any modem designed for Sprint, VM, or Boost. A lot of Sprint users actually achieved great signal/data results with the MG2 modem from VM/Boost, and I have used MK3 modem just fine myself (I am on VM). ROM .zip files don't care about your modem, only your bootloader.
I hope this helps, I am seeing way too many users asking why they bricked their phones when this information would have helped them in advance had they not just forged ahead and assumed the bootloader was the problem. If anyone would like to know how to safely modify or delete the assert lines please let me know via posting or PM.
Click to expand...
Click to collapse
Can i use a return to stock of Sprint S3 "L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar" on a Boost mobile with bsaeband version L710VPUBMk5???
alemosman said:
Can i use a return to stock of Sprint S3 "L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar" on a Boost mobile with bsaeband version L710VPUBMk5???
Click to expand...
Click to collapse
No, you will want a return to stock tar meant specifically for Boost. There is one available on the Android Forums Boost subforum, give me a minute and I will get you a link.
Edit: Can't find the specific post right now, I would suggest going to the Boost subforum and starting a thread or contacting either @jdsingle76 or @wetbiker7 (they are both active here on XDA as well) as they are probably the two most knowledgeable Boost users of this phone that I know.
http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/
Mr. Struck said:
No, you will want a return to stock tar meant specifically for Boost. There is one available on the Android Forums Boost subforum, give me a minute and I will get you a link.
Edit: Can't find the specific post right now, I would suggest going to the Boost subforum and starting a thread or contacting either @jdsingle76 or @wetbiker7 (they are both active here on XDA as well) as they are probably the two most knowledgeable Boost users of this phone that I know.
http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/
Click to expand...
Click to collapse
@Mr. Struck is right, MK3 is for the Sprint version of the S3. If you want to go back completely stock MK5, at this time, the only way I can think of to do that, is to Odin flash back to MG2, and then do OTA to get MK5. Two things here to remember, as Mr. Struck pointed out. First, DO NOT DO THIS if you have the Knox bootloader on your phone. Flashing back to 4.1.2 will hard brick your phone. Secondly, if you don't have the Knox, and flash back to MG2, and then OTA MK5, you WILL get the Knox bootloader. Your call...here's the link for MG2 tar. Good luck!
http://www.androidfilehost.com/?fid=23212708291678209
Hey guys...I hope you can help me out here. After days of searching this thread is the closest I've come to some clarification but I'm still a little confused.
My brother bought an AT&T i747 S3 (d2att) off of a coworker the other day. When I started to look through it I noticed it has SuperUser installed so I downloaded root checker and sure enough the guy that sold it had already rooted it. I thought to myself "great", mind you it was running 4.1.1. So in decided to throw some kitkat on it! Before doing that I thought it wise to update the recovery to the latest. So I went and found a "d2att philz touch cwm" and began the update process only to receive a status 7 error informing me that the package was for a d2att device (which I knew) and I was using a d2spr (which I'm not). So I went and downloaded the d2spr recovery and it updated allowing me to install a d2lte ROM. Everything works but I can not get an LTE signal at all.
My question is...is there anything I can do to make this work? My brother would love to have LTE connectivity but if we can't do anything we'll probably just sell it to a pawn shop. They probably won't know diddly squat.
Anyone still following this thread? I wanted to change roms from LiquidSmooth to MOAR 9.0.1. I have MD4 radio installed and have read that installing MK3 will put the dreaded KNOX bootloader lock on our phones? I thought this was just when we updated to 4.3? Thanks in advance
mcc23 said:
Anyone still following this thread? I wanted to change roms from LiquidSmooth to MOAR 9.0.1. I have MD4 radio installed and have read that installing MK3 will put the dreaded KNOX bootloader lock on our phones? I thought this was just when we updated to 4.3? Thanks in advance
Click to expand...
Click to collapse
Part three of the OP: modem does not equal bootloader.
Bootloader, Modem and a new ROM (S4)
Mr. Struck said:
Here are some rules of thumb:
1. Know what is on your phone! Be aware of what bootloader you have, specifically you need to know if you have Knox or are Knox-free. If you are Knox-free, congratulations, if you have Knox, my condolences. In the Knoxed-up situation NEVER EVER try to push, via Odin a .tar file designed to "return to stock" if the bootloader associated with that file is MD4 or earlier (Sprint users) or MG2 or earlier (VM/Boost). Sprint users also have .zip files available designed to do the same thing, avoid these as well if you have Knox. Flashing a ROM with an earlier Android build is just fine, there is no bootloader included in a custom ROM based on AOSP, contrary to what some people are posting. You can "downgrade" to an earlier build of Android if you wish, you absolutely CANNOT downgrade your bootloader if you already have Knox on your phone.
2. If you get an "assert failed" message, you just need to modify or delete the asserts to match your bootloader, you do not need to change the bootloader itself. DO NOT assume that changing your bootloader is a fix for anything without knowing what you are doing first.
3. Modem does not equal bootloader. We use the same nomenclature (MD4, MK3, etc.), which can be confusing, but modems are interchangeable, and there are .zip files available so that you can easily flash from one to another. Additionally, anybody who has an SPH-L710 can use any modem designed for Sprint, VM, or Boost. A lot of Sprint users actually achieved great signal/data results with the MG2 modem from VM/Boost, and I have used MK3 modem just fine myself (I am on VM). ROM .zip files don't care about your modem, only your bootloader.
Click to expand...
Click to collapse
I am glad to have found this post as I have been struggling with the decision to update my ROM from 4.3 (old bootloader and modem) to 4.4.2 on my S4 GT-i9505. With a lot of discussion about Knox I was very uncertain whether I could leave the BL and Modem as they were and merely update the ROM. I am pleased to say you can but now I am trying to understand the value of upgrading the BL +/- Modem as new Official products have been released. This thread is very useful but I thought I'd add a few more links to it in case others are also interested in this topic.
Here's a description of the purpose of the modem I found in one of the links below. I think it helps me see why you may want or need to update it at some stage: •Baseband/Radio/Modem - radio[version].img - Is the firmware for the separate cell modem and is responsible for your cell phone signal and on older devices may control wifi, bluetooth, and GPS (on most newer devices, these are handled by the kernel and ROM). Upgrades may improve or diminish battery performance, network signal strength, and roaming capability. It is also sometimes required to have a minimum Baseband version to use a ROM so that the RIL will play nice with the Baseband.
Here's a description of what a radio/modem is:
http://www.reddit.com/r/AndroidQuestions/comments/1wzmp7/what_are_all_the_different_pieces_of_android/
http://androidforums.com/galaxy-s2-international-all-things-root/588852-modems-dummies-guide.html
Here's a link to whether you need to upgrade your modem and how to do it on an S4:
http://galaxys4root.com/galaxy-s4-radiomodems/
http://android.stackexchange.com/questions/63870/omega-rom-4-4-bootloader-modem-problems
Here's a link to Official modems for S4s [i9505/i9000]: http://forum.xda-developers.com/showthread.php?p=48113546
Discussion of Knox with new BL can be found here: http://forum.xda-developers.com/showthread.php?p=46189882
I am still searching for why one would want to update their BL and/or modem if their existing ones are working fine? I am also trying to understand why some ROM update the BL (and modem?) as part of their install processes.
So if you have any links or thoughts about these issues, please post here or drop me a line.
So, I was given a T-Mobile SGH-T999 that someone had found a while back, but was unable to get activated. It didn't have a SIM in it, and I think it may even have been used off T-Mobile at some point (based on evidence below). Checking the IMEI it seems that it's only blocked on T-Mobile (AT&T says they do not have a block against this IMEI, and it's not showing up in any lost/stolen databases), so I'm guessing non-payment or carrier unlock. I would like to SIM unlock it, but I'm not entirely sure what has been done to this phone. I've never owned or played with a Galaxy S3, so my only knowledge has been from digging around this forum for a couple hours. Here's what I can tell you from looking through this phone. I'm hoping to get some advice on my next course of action:
Model number SGH-T999
Android Version 4.1.2
Baseband version T999UVDMD5
Kernel version 3.0.31-1128078 [email protected] #2 SMP PREEMPT Mon Apr 15 11:59:10 KST
Build number JZO54K.T999UVDMD5
Device Status Modified
Odin Mode
Product name SGH-T999
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
I first tried SIM unlock, only to eventually find out that I would need to downgrade from 4.1.2 to 4.1.1. The threads I've read on downgrading indicate that to get back down to official 4.1.1 I need to be stock to begin with. I don't think this phone is rooted because I am unable to "su" when using adb shell or browse directories like /data. However, Odin saying it has a custom binary, and the device status saying modified makes me believe this phone was rooted at some point. Again, I have no experience with the GS3, so I may be way off base (I don't even know if Odin is the stock recovery).
So, before I can downgrade to 4.1.1 do I need to use Triangle Away, reset the flash counter, etc? Or, can I just use Odin to flash 4.1.1. Finally, will I also need to flash a different modem even after that?
I'd appreciate any advice and help you can give me. Thanks.
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Perseus71 said:
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
Click to expand...
Click to collapse
No problem. I work in IT, so I know the frustration of someone asking for help without even trying to do any basic research first
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
Click to expand...
Click to collapse
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Click to expand...
Click to collapse
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Click to expand...
Click to collapse
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Really everything Perseus said is on point, except you don't need to use triangle away because really that's just to reset the counter and its unnecessary for you.. You can either flash a custom recovery and flash the LJA or LJC modem to do the unlock, or Odin the LJA or LJC firmware and proceed with the unlock
Edit: and to answer how the counter was tripped, it looks like they may have rooted it at some point and then unrooted it and returned it to stock.. The counter does not change
Sent from my SGH-M919 using Tapatalk
YabosMcGee said:
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Click to expand...
Click to collapse
Yes that's stock recovery. You can't flash modems with it. If you have custom recovery then the flash counter will keep on tripping at every boot. Best if use ODIN to flash LJA or LJC firmware, do the unlock and then flash MD5 firmware so you are back to JB 4.2.1. Triangle Away's purpose is to reset that flash counter you saw. I do believe it needs Root. I don't remember since I did it so long ago. I just thought you will want to it after all this flashing is done so its all squeaky clean.
YabosMcGee said:
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Click to expand...
Click to collapse
Theoretically with android architecture, it could be done on any device. The trick lies in remounting that partition as read-write correctly. Have fun reading this.
YabosMcGee said:
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Click to expand...
Click to collapse
Looks like Serio beat me to it. He's spot on where the origins of the tripped counter is concerned.
Thanks Persus77 and serio22. Everything worked out great.
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Den Den said:
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Click to expand...
Click to collapse
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
lordcheeto03 said:
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
Click to expand...
Click to collapse
Should i keep the 4.4.2 kitkat thats not working with my usa sim card atm? Or should i flash it to 4.2.2. ADL? If having 4.2.2 is better doing that guide i put link to above, then give me a good tut on doing it, need to do it today xD THanks in Advance!
HampTheToker said:
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
Click to expand...
Click to collapse
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
lordcheeto03 said:
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Click to expand...
Click to collapse
That Makes sense...just trying to grasp info. on everything so it's more clearer ;p and thanks for correcting me, yea it was data lol.
HampTheToker said:
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
Click to expand...
Click to collapse
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Den Den said:
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Click to expand...
Click to collapse
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
lordcheeto03 said:
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
Click to expand...
Click to collapse
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Den Den said:
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Click to expand...
Click to collapse
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
lordcheeto03 said:
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
Click to expand...
Click to collapse
Flashed ADL using odin, somehow got the menu to work(couldnt budge for some reason to umts), went thru all the steps, it rebooted, put it back to download mode, and flashed it back to nb4. Put my simplemobile simcard in, still nothing, am I supposed to put a different sim card in like ATT or something for it to work? Confused why it didnt work, yet it still detects the MTC european version simcard(not in service, but it had a pin set on it, so it always asks you to unlock the sim with the sim pin u put on it to view ur files on it, etc). Am i doing something wrong? I could give you more info on the phone...
Edit: Just checked on Swappa.com of my imei and got this =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nvm, Looks like i think its blocked on Tmobiles network, but i put in the H2O sim and it worked.(under ATT) phew....
Its been awhile since I've done my firmware, but I'm giving my phone over to my sister soon and upgrading to a Note Edge.
I'm trying to get this phone on Likewise S5, but having a little difficulties with the older guilds to install various stuff, also all the warning on the Likewise S5 don't show up in the guide I was following for the actual installation, like stuff about bootloaders and modems (I don't know what these are), I am a techy just I'm not well versed in Cellphone Firmware talk at all, more of a PC person.
This was the guide I'm following well can't link it, its on Team android, for the likewise S5 for S3 i747
I'm Trying to install CWM Because I believe I don't have one currently installed, if I do is there a way I can find out? all I believe I have is just a oem 4.1.2 firmware that was rooted.
Almost all the CWM guides that are out have their own downloads that no longer work for the CWM that they provide, and honestly I don't wanna mess with it anymore and want to get the proper combination, I've downloaded the latest one for Samsung Galaxy S3 from the Official Clockwork mod website for Touch version, but I'm not sure how to flash "that" I know it says to use PDA on 1.85 Odin which i've tried but it just says
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1) (No pass or fail)
I'm not sure what I'm doing at this point and could really use some help, specific to what I'm doing.
And to be specific I have a Samsung Galaxy S3 i747 From Rogers Wireless in Canada (Sept 2012), and it isn't bricked have booted it up just fine.
Currently I am dealing with a finnicky USB port as well, need to get some alchohol and see if I can get a more reliable connection out of it. I got it to point now I feel like I'm comfortable flashing it just eh, could be better, long as its sitting generally its connected slight pressure in cord to be sure, usually charges no problem but USB connectivity is whats finnicky. I cleaned out the lint with a needle didn't really seem to help a whole lot but definetly lets the plug go in further now, even bought a new cord that gets a decent click but it still a little floppy side to side, feels like its the plug has room to move inside the female end of the plug, vs anything being "loose"
Any chance your phone is already rooted? Odin flashing anything with a flaky USB port would make me a little nervous.
If you're rooted, there's an app called flashify that makes updating recovery pretty simple and there is no USB connection needed.
Also in the Play store if you search for Samsung Phone Info you should find an app that will tell you what firmware you're on. Install it and report back what it tells you you're on for bootloader and baseband and someone here should be able to chime in on whether it will run newer roms ok, or how to proceed if its out of date.
jason2678 said:
Any chance your phone is already rooted? Odin flashing anything with a flaky USB port would make me a little nervous.
If you're rooted, there's an app called flashify that makes updating recovery pretty simple and there is no USB connection needed.
Also in the Play store if you search for Samsung Phone Info you should find an app that will tell you what firmware you're on. Install it and report back what it tells you you're on for bootloader and baseband and someone here should be able to chime in on whether it will run newer roms ok, or how to proceed if its out of date.
Click to expand...
Click to collapse
I am already rooted I know that I did the root myself, to get Super admin permissions for the Ps3 controller blutooth controller permissions.
I'll look into Flashify, I'll install phone info now
Ok here is from my Samsung phone info app;
DMF1 firmware is pretty out of date. Unless you pick an older build of a custom rom, you'll run into some issues.
The full Canadian carrier updates for i747m are all available for download from sammobile.com, but those will be really big files to flash with Odin. I wouldn't try that unless you're really confident in that USB port. This won't be a really quick flash and interrupting it could brick your phone.
The safest route might be to unroot the phone and take carrier OTAs until your firmware is up to date. You'll have to be on stock recovery for OTAs. Once you're unrooted if you power down and reboot your phone, I'm pretty sure the stock recovery will come back. If not, here's a link to a stock recovery: http://forum.xda-developers.com/showthread.php?t=2026751
To get going with rooting and custom roms again you'll have to flash a custom recovery in Odin once you get up to date on OTAs, but that will be a 5 - 10 MB file to flash as opposed to a 1 GB+ full system update. Don't worry about that until you get the bootloader and modem up to date, one step at a time. :good:
How do I perform an update though to manually update the phone, like to unroot it basically I'm Connecting it to USB getting it to recognize in Kies?
Like I have full USB access to my phone now, yes the port is flaky but it functions. Kies says my device is on latest firmware even though I know 4.4.2 was released by rogers for the device, i.e I don't understand how to unroot it and bring it up to date
I don't know what a OTA is, I don't understand what a modem/bootloader is etc.
I'm assuming what I have to do is update it to 4.4.2 via the normal firmware but currently it isn't giving me an option to
OTA is "over the air" updates. They are pushed to your phone and often update your phone's bootloader, modem, and rom to new versions. They'll download and install with wifi or cell data, no USB connection required. It is a very safe way to update your phone, but OTA updates will fail if you are rooted and have custom recovery (at least AT&T's will).
With android 4.1 and DMF1 firmware you're something like 2 or 3 updates out of date. Usually OTA notifications just pop up on their own, or you might have a "check for updates" option somewhere in your rom settings. Has this phone been off the grid for a while, update process frozen, or just declining OTAs for the last year and a half or so? Is it not tied to a carrier anymore?
I have updated bootloaders and modems outside of the OTA process, but only on the i747 AT&T variant. If OTA is not an option for some reason, I can't comment on what your safest route would be on the Canadian variant, but there are plenty of expert i747M users on here. Someone will chime in to help you out.
If OTA is an option, then the easiest way to unroot used to be to install SuperSU from the Play store, if you're not already using it. In SuperSU settings there used to be a "full unroot" option.
Ok So what do I need to do exactly I unrooted the phone no problem but it still doesn't recognize it as needing new firmware still so I'm still confused how to update it.
My understanding is I need to update this to latest base version which would be 4.4.2, but I'm not sure how to do that exactly since its not automatically doing it given the custom rom.
Confirm the bootloader on your phone and post it here.
It is the bootloader that will determine which stock firmware to flash from sammobile.com onto your i747m.
audit13 said:
Confirm the bootloader on your phone and post it here.
It is the bootloader that will determine which stock firmware to flash from sammobile.com onto your i747m.
Click to expand...
Click to collapse
Again, I'm not well versed in android terminology etc, I don't really know what a bootloader is, everything in those screen caps above is what I'm using
If you want to be on the latest stock, just use Odin to flash the stock Rogers 4.1.1 ROM from sammobile.com. Then use OTA updates to update the phone to the latest KK.
audit13 said:
If you want to be on the latest stock, just use Odin to flash the stock Rogers 4.1.1 ROM from sammobile.com. Then use OTA updates to update the phone to the latest KK.
Click to expand...
Click to collapse
Again, I Really Need more details Odin isn't so simple that its Oh Slot dis dat flash in der and poof completeo, if you read through the thread you'd you I have a flaky USB port that isn't 100% stable, flashing a 1gb rom through a iffy connection doesn't sound smart.
How do I flash this correctly from SD card if I can?
Please describe, Which App I need for it, what I need to do in app etc, cuz Odin is like AD AP DS WE aslaksd its all gibberish to me unforunately for different flashing locations
I know of no way to flash a completely stock ROM from an SD card.
If you wanted to flash it from an SD card, you would probably need to download the entire ROM, strip out the stock recovery, and re-pack the ROM into a zip file.
I'm still extremely confused, I need consise directions what I need to do, so far I haven't had solid details in this thread yet how to get my firmware installed :crying:
Evockzi said:
I'm still extremely confused, I need consise directions what I need to do, so far I haven't had solid details in this thread yet how to get my firmware installed :crying:
Click to expand...
Click to collapse
since youre computer literate , so to speak , perhaps this method would help/be more 'simple'. IDK , just a thought.
http://forum.xda-developers.com/showthread.php?t=2225405
"all i can really do , is stay out of my own way and let the will of heaven be done"
Is that method compatible with my device? before I've only been following ones that flash with odin.
The Reason why the isn't helpful immediately for me, I Do Not Know what I need to Do to achieve what I need.
Bootloader means almost nothing to me, I do Not know what I need to accomplish, No one has answered that question yet for me.
My Question is again, So, Do I need to install 4.4.2 Base as downloaded from that Samsmobile, and How Do I install Specifically that?
Beyond That my question expands into, Ok After I install that What do I need to do to install likewise.
I Do not know what I need to do so all these guides about doing specific tasks that you know what you need to do are useless to me at this moment I'm afraid.
I have enough of a stable USB connection I can Odin it Right now I just need to know what to select, etc
I yolo'd it with the connection, and flashed it with older odin 1.85 since I know PDA is the correct one idk what the hell it is in the new odin.
Passed, took almost 8 mintues to flash it, Now I just need to get back to original question of installing CWM Recovery and Getting Likewise S5 rom installed.
Do I have correct 4.3-4.4 Modem and boot loader that it spams in bright red on the likewise requirements?
Managed to finish all the installations without a hitch,
Followed a guide to CWM install and then root it through installing SuperSU, Then had everything to install Likewise which can be done on the device.
Everything installed perfect now I have a S5 to give to my sister cheers
@Evockzi glad you got it figured out.:victory:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Hi,
I know this information is probably available somewhere, but I have spent hours of reading, and still having some trouble getting my head around things. So I will try to be clear here as to what my issues are.
Firstly... I have Samsung Galaxy S-III, SGH-i747M, with virgin mobile canada. It started with android 4.1.2. I wanted to unlock it, and there was a way to do it with 4.1.1 (http://forum.xda-developers.com/showthread.php?t=2176719), so I used odin, with firmwares (found at SamMobile.com I think) to flash a 4.1.1 ROM, did the unlock procedure, and then used odin to flash stock firmware for 4.1.2 again. Seems to have all worked out ok.
Anyway, I want to try some custom roms, like cyanogenmod, as they are purported to improve battery life, speed, clearing off bloatware, giving me more control, etc.
However, I really want to maintain the ability to go back to how it is now, if I don't like the custom roms. (or if I need warranty help, though there's not much of that left).
The main thing that's concerning me is that while I was playing with this phone before, I read in a number of places that if I had updated to Android 4.3 or 4.4.2 when those had become available from my carrier, I would not have been able to downgrade to 4.1.1 (which I needed to be able to do to use the built-in unlock method). This is because of Knox, which would be installed, and gets "tripped." So now I'm scared: if I did that upgrade, I wouldn't have been able to revert; so now, if I flash a CGM ROM, will I also be unable to revert?
I think there are a few pieces of android to sort out in my mind... If I'm not mistaken, there's bootloader, there's recovery, and there's the ROM. Flashing a ROM with Odin apparently would restore recovery and the ROM? But not the bootloader (that's where knox is? though I still don't understand, if an upgrade can modify the bootloader and put knox there, where it wasn't before, shouldn't there be a way to put a pre-knox version back there?)
Oh, there's also EFS, which some say should be backed up before doing anything (though you need to root first, which in my mind counts as doing something before backing it up).
Anyway, please let me know if you can help clarify these issues, thanks!!
There is a lot to cover to address all that you bring up.
Regarding EFS, there are a number of ways to back it up. Use several. This thread is an excellent place to start for more info and several ways to make the backup. I was rooted, so I used A2 and B. I believe you can use A1 without being rooted, probably B as well. Long after that post was written wanam came out with two backup apps available in the PlayStore. One was specifically for EFS, but I do not think it is still supported. The other is a more comprehensive app, both require root.
As a rule, bootloaders and modems are not installed with custom ROMs. If you are flashing a stock ROM from these forums that is installed from within a custom recovery it probably does not install a bootloader and modem either, but read the relevant thread to be certain. Full stock ROMs flashed from with Odin, or Heimdall, almost certainly install a bootloader and modem.
Prior to 4.3 there was an ability to downgrade bootloaders and modems, nor were they required to match - be at the same version. Once you upgrade to the official 4.3 bootloader you can no longer downgrade it. Once you have upgraded to 4.4.x the bootloader and modem versions must always match. If they are mismatched you risk soft bricking your phone at a minimum. For the i747 there was an unofficial 4.3 release; ROM, bootloader, and modem. I do not recall seeing mention of an unofficial release for the i747M, so I will not go into the exceptions on the above the unofficial bootloader/modem introduced.
For TouchWiz ROMs, custom or stock, the bootloader (and modem) version should match or be more current than the ROM Android version. (One of the unofficial 4.3 release exceptions applies here, I make use of it.)
For CyanogenMod, CM based ROMs, AOSP ROMs, and their derivatives the bootloader and modem version can lag behind Android version of the ROM. With your 4.1.2 bootloader and modem you could run the earlier releases of 4.4.x CM and AOSP ROMs. Later in the 4.4.x development, around Oct or Nov 2014 IIRC, I began reading reports of needing to be on 4.3 or later, there were a few said the 4.1.2 firmware still worked for them. For the 5.x.x LP releases of CM and AOSP most report that they must be on a 4.4.x bootloader and modem.
Knox is in the ROM, not the bootloader and modem. It was introduced with the official 4.3 releases. It is not present in CM/AOSP nor most of the custom TW ROMs. It will be present in stock ROMs from official sources or sites like sammobile. Many of the stock ROM images/dumps have Knox disabled, especially those from enewman17, but read to make sure what you are getting.
I don't feel qualified to discuss tripping the Knox counter, I am still on the unofficial 4.3 bootloader, which has not kept me from running 4.4.x ROMs. I am not the only Luddite, but I feel we will all be updating bootloaders and modems due to the Stage Fright bug. I am long out of warranty so there is no loss.
ABOVE ALL, read thoroughly before taking any action. Keep in mind that I am on the i747 and not the i747M as you are, I am not be correct on all comments for your device. @audit13 should be able to clear any gaffs I have made.
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Ok, starting to feel a bit more comfortable with the whole system and relationships, thanks!
audit13 said:
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Click to expand...
Click to collapse
Thanks for verifying that. There could have easily been small, but very important, differences in the devices that had slipped my mind since I don't have the i747M.
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
canodroid15 said:
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
Click to expand...
Click to collapse
I would like to extend similar praise and thanks to @mrrocketdog and @audit13
more uncertainty
Hi,
I'm a lot more experienced now, having rooted (I flashed root66_BMC_I747MVLDMF1 by MrRobinson, since CF-autoroot just made the phone show "booting recovery" then blank screen indefinitely), I backed up EFS by a couple methods, flashed TWRP, did a nandroid backup, and flashed a couple versions of CM. Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem. In general, I see a lot of posts simply saying "update the modem." From what you've said though, that will create problems, unless I update the bootloader as well, correct? Just feels like the phrase "update the modem" is said so casually, without also mentioning the bootloader, and the inability to go back.
(an older CM 11 worked with data just fine)
(a big issue is that S3 is over 3 years old, so there are over 3 years of posts, so there's a lot of conflicting information, likely due to different versions, new discoveries, etc. )
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" There are a lot of "Never update to 4.3 (or above) because of knox!" comments. But also in general, it seems the only real issue with knox is that warranty bit, otherwise it doesn't have too big an impact on our lives? Seems the consensus is that we can still root, install custom roms, and everything else. (Do you know if this remains true with latest bootloaders and modems (OB3 for i747M). There are also "My battery life became way worse after the upgrade" or "more FCs" or other issues, which is a significant concern if my phone which currently comfortably lasts a day starts to not last a day after updating. Though it's likely a small percent noting that, while the quieter majority are fine. Meanwhile, by not updating, we may be missing out on features and security improvements (and maybe actually improved performance). What do you guys think? (I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
As for updating, I think somewhere one of you suggested the better (or at least safer) way is to use odin to flash stock ROM, then do the OTA updates, or, directly flash the latest stock ROM, rather than trying to flash modems and bootloaders directly?
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Thanks again!
I almost wish I'd just taken the blue pill at the start of all this
For XDA members that are new to rooting, flashing, etc., I always recommend the safest route which is to flash back to a completely stock ROM and just upgrade to the latest bootloader and modem via OTA updates. There's always a risk of something going wrong when flashing anything, be it a custom ROM, recovery, or OTA update.
If the phone still had warranty, I recommend not flashing any non-Samsung software until the warranty has expired. Once expired, flash away
Knox should not interfere with root if supersu is flashed from a custom recovery, regardless of the bootloader. I have used supersu to root the latest s3, s4, Note2, and Note3 ROMs without a problem.
Restoring old nandroid backups should not cause a brick as TWRP does not change the modem or bootloader.
sacrawfo said:
....Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem.....
(an older CM 11 worked with data just fine)
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" ....(I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Click to expand...
Click to collapse
I think the change date for CM11 requiring the newer bootloaders, at least NE4, is Nov 2014. Releases prior to that date would run fine on older bootloaders.
I have since updated to NE4 in order to run ROMs patched with the StageFright fixes, specifically CM11 20150831. Knox isn't installed on this ROM or even the newer custom TouchWiz based ROMs. I am not concerned about Warranty Bit being triggered. My device is long past being covered by any warranty and I have no intentions of using Knox features on this phone in a corporate environment.
Keep the EFS backups, those are from partitions not changed by flashing roms; stock or otherwise.
Finally went through the OTA updates, surprised how long it took but all done, at OB3.
Ok makes sense, restoring an old Nandroid would effectively result in a 4.1.2 OS with a 4.4.2 bootloader/modem, which != brick.
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Restoring a nandroid backup should not brick the phone brick the phone as twrp does not restore the modem or bootloader.
sacrawfo said:
...
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Click to expand...
Click to collapse
There are quite a few partitions not affected by flashing, not only the EFS partitions. IIRC there are secondary modem partitions, more than two extra bootloader partitions, etc.