OK, forgive me, I'm new. How would we only downgrade the modem? And how would we know which bootloader is compatible to downgrade. Meaning if we have one firmware, how do we know if an older firmware has an older bootloader and it wouldn't work since you cannot go back? Lastly, what's the difference between bootloader and modem in these terms?
One other question. Can you not just completely wipe cache, and dalvik cache, and reformat, and erase everything so then start with any firmware you want? If not, how does it keep the bootloader and or modem info?
First off, this question does not belong in the Development section. That is what the Q&A (Question and Answer) section is for. You should ask an admin to move it.
Secondly, and I am not being rude here, you are asking questions that require complicated answers. I am going to answer, but understand that it is partial.
Firmware is the instruction set for your phone. It includes the operating system, the modem and more. The bootloader, often included in the download of the firmware, operates below that level and the bootloader determines which firmware you can load. Which is why people often have problems trying to downgrade a Samsung phone. New firmware is fine, older not so much.
Why you would want to downgrade your modem is beyond me. If a network (Sprint) has been updated to recognize newer modem sets, using an older modem seems like a bad idea.
I maintain a thread with the latest firmware available: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
It has instructions on how to flash.
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.
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.
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 .
Hi,
I just tried to install a 5.1.1 ROM on my i747M and noticed that it's not detecting my sim. Digging through all the threads indicate that I probably have an ancient firmware (LK4). Got a couple of questions hoping someone can help me answer so I don't mess up the firmware update and brick my phone
1. Do I need to install all the firmware updates from my current version (LK4) to the latest one (OB1)? I've been some threads mention that all the updates are incremental. So I would need to install MF1, MK5, NE6, etc.
2. I see a bunch of same firmware but different carriers on sammobile, Do I only need to install all the ones from my carrier (Rogers) or does it not matter and I can install the firmware of any carrier that is i747M?
3. Is there a site where I can find all the different modems or do I have to dig around the forums and google to find missing ones? The modem list in the sticky thread only goes up to ND3.
Thanks a bunch in advance for reading my questions and apologies if they sound too dumb
gewbutt said:
Hi,
I just tried to install a 5.1.1 ROM on my i747M and noticed that it's not detecting my sim. Digging through all the threads indicate that I probably have an ancient firmware (LK4). Got a couple of questions hoping someone can help me answer so I don't mess up the firmware update and brick my phone
1. Do I need to install all the firmware updates from my current version (LK4) to the latest one (OB1)? I've been some threads mention that all the updates are incremental. So I would need to install MF1, MK5, NE6, etc.
2. I see a bunch of same firmware but different carriers on sammobile, Do I only need to install all the ones from my carrier (Rogers) or does it not matter and I can install the firmware of any carrier that is i747M?
3. Is there a site where I can find all the different modems or do I have to dig around the forums and google to find missing ones? The modem list in the sticky thread only goes up to ND3.
Thanks a bunch in advance for reading my questions and apologies if they sound too dumb
Click to expand...
Click to collapse
maybe this thread would help , if you havent already seen it.
http://forum.xda-developers.com/showthread.php?t=1968625
1) yes , do the incrementals.
2) best guess is only install from your carrier or risk a brick (or at least thats true for the htc one m8).
no questions are dumb imho.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
You can probably flash directly to the latest firmware via Odin and Rogers firmware from sammobile as long as the firmware you are flashing is newer than the firmware on your phone. This will wipe all of your data so make sure you backup before flashing.
The i747m from Rogers, Bell and Telus are all the same. Since you will be replacing the stock ROM with CM, you may as well just flash the Rogers firmware.
The firmware from sammobile will include a modem and bootloader so there is no need to flash them separately.
Thanks a lot for the help guys. I flashed a copy of Rogers MK5 then did the incremental OTA updates from there. Took awhile but all is good now
Good to know that sammobile firmwares usually include modem + bootloader. Reading all the separate threads made me think I needed to go hunt matching copies down.
yay , glad you got it fixed. :thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Hey everyone,
Apologize if this is something that has been asked before, haven't been able to find much information on it using search. Also still a relative newbie to android, so hope you folks will bear with me. I'm seeing the OS version in download mode showing as OS-3.36.709.3, while the software number in software information shows 4.30.617.12. Is this considered normal, or did I mess something up?
I previously had Marshmallow on my phone, and used TWRP to install the developer edition of Nougat. Was trying to do OTA, which unsurprisingly didn't work with TWRP installed. My plan is to reflash the recovery.img, but I'm unsure whether I should be using the recovery.img for 4.30.617.12, or the one for 3.36.709.3? Is there something I should do to get the versions aligned properly? Trying to make sure I avoid bricking the phone
The easiest solution would be downloading the latest version of the rom that you installed in the past and flashing it via TWRP.
Some advices: Please read the ReadMe thread. It explains why the version numbers differ (e.g. in the RUU section). In addition it will explain to you, that installing OTAs with TWRP actually is possible (c.f. the OTA section) but not in your case. Even with the correct stock recovery for your phone (the 709 one) you wouldn't be able to achieve your goal. You're trying to install an update for a completely different firmware than the current one of your phone. That's not possible. OTAs are incremental. That means you need to be using the firmware that the OTA is supposed to update (4.30.617.12) and not 3.36.709.3. You would need to convert your phone if you want to install that update.
You might want to read the article that I called "the difference between rom and firmware" in the further reading section of the ReadMe thread, as well, after you finished reading the ReadMe thread itself.
Be aware that it's always best to use a system that has the same version (or at least the same mayor version - e.g. 3.x for marshmallow or 4.x for nougat) as your phone. This way you can be sure that system and firmware are optimized for each other. Mismatches can cause unforseen side effects like battery drainage, lags or bugs.
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
P.S. will make sure to put questions in the right forum in the future.
e1rond said:
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
Click to expand...
Click to collapse
Correct.
e1rond said:
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
Click to expand...
Click to collapse
Then the phone had been modified before you got it. Since android 5 google is using block-based OTAs. That means re-flashing the stock recovery isn't sufficent if you want to update your phone and modified it, beforehand. You need to restore a completely untouched system image.
Check the ReadMe thread. The RUU section as well as the TWRP section II should contain the files and instructions that you need for restoring the OTA function of your phone. It's up to you which of the methods you prefer to use.
Appreciate the information and the advice. Decided to RUU back to a 3.x version, and use OTA to upgrade to Nougat. Took a lot of updates to get it to the latest version, but everything is working well now