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.
Related
Hi, I am sure there are countless threads out there already talking about the inconveniences that 4.3 bring and the problem you get for trying to downgrade. I have read through many of them and I think I have the general idea of how to downgrade relatively safely without running into the problems I am currently aware of. I want to confirm what I know. I would like to be informed before I do anything, especially something as dangerous as a downgrade attempt.
So all that I am aware of right now is that 4.3 brings in a new bootloader, attempts on trying to change the bootloader will result in hard brick, so does that mean any previous firmware that does not flash a bootloader will be fine? will stock firmware from sammobile work? I am looking at this one right now,
http://www.sammobile.com/firmwares/3/?download=16006
Second problem is 4.3 also changes the efs format, any modem before I think MG4 won't be able to read it, and you won't get network, this should be easily fixed by flashing the latest modem here
http://forum.xda-developers.com/showthread.php?t=1831898
...right? also the modems are made custom recovery flashable, if I want to use odin instead, do I just unzip and put the modem.bin into odin?
Also plans to root first and backup efs, I hear you have to go through hell to get it back if you lose it...
Doing any of those should trigger the knox counter...so basically anyone that still have warranty left and plan to use it cannot do anything...even rooting...right?
But that should be the least of your worries if you are determined to downgrade...
I am not sure if that is all the trouble I will run into, I don't know what made samsung so confident that they can even say it is impossible to downgrade, they meant to say difficult but you can do it, right?
also I am on SGH i747m bell.
I never had any issues with my old M919, which is still sitting in a drawer awaiting a new display assembly I cannot afford. It was running CM 10 perfectly and no issues with HSPA or LTE. I was suffering for a while with an HTC Espresso which I could not S-OFF due to HBOOT being incompatible with AlphaRev. Anyway, I ended up with my old roomate's M919 about a week ago and have had nothing but issues getting mobile data to work properly.
It already had the MK2 Baseband installed-though I did not bother to check if it worked on the stock 4.3 ROM he had already installed. Nor did he ever say anything about issues. Anyway, I tried almost all of the Infamous ROM's(and all the kernels available with AROMA) as well as Cyanogenmod 10.2. All ROM's have major issues maintaining mobile data connection regardless of network mode or which cell I am on. Wi-Fi works flawlessly however. Also, to note, my fiance is running MK2 on her stock M919 so I have had a reference of which type of cell we are on and its signal strength.
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.
fallofredmond said:
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.
Click to expand...
Click to collapse
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.
xdapowerapps said:
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.
Click to expand...
Click to collapse
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel
POQbum said:
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel
Click to expand...
Click to collapse
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
EDIT: I am also using a 4.3 MK2 modem on 4.2.2 and have no issues.
xdapowerapps said:
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
Click to expand...
Click to collapse
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warranty anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar (with knox and the MK2 LTE included) out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers
POQbum said:
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warrantly anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers
Click to expand...
Click to collapse
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!
xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!
Click to expand...
Click to collapse
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it
POQbum said:
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it
Click to expand...
Click to collapse
Open up odin, select PDA, choose the tar file you just downloaded.
Then put your phone in download mode (vol down + home + power), then connect it to your computer.
Once odin detects your phone, press start. It will take 15 to 20 mins and it will restart by itself.
After it reboots and for some reason you get stuck on the tmobile screen for more than 10 mins, go into recovery and wipe/data factory reset and wipe cache. Then your phone will boot up fine. Enjoy ^_^
Sent from my SGH-M919 using XDA Premium 4 mobile app
xdapowerapps said:
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:
Click to expand...
Click to collapse
Both M919's are set to fast.t-mobile.com, although I haven't checked to see if the settings all match. I will definitely check that later.
As for threads here and elsewhere to solve the problem, I have tried pretty much everything I have seen. Most of what I have been reading on both CM and custom TW ROM threads is "me too" or "I don't have that problem".
POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
Ok, now I just got thrown for a loop. Please use Heimdall to print your PIT and post it. On my PIT there appears to be only one partition with a radio... not 2.
xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
Cheers mate!
Click to expand...
Click to collapse
I'm not waiting 4-8 hours to download a ROM. Yes, I understand those estimates are ads to try to get you to buy "premium membership" but still, do you have a legit mirror?
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .
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....
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.