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.
Hey guys so I decide to get the SGH-147 AT&T S3 off of ebay for MetroPCS which enabled me to get a 2 year squaretrade warranty. After looking back at it now, I feel it might have been a bad idea since Metro has a MIR 349.99 deal for their S3 version which would mean easier android update since it would be on Metro servers if I'm not mistaken. Anyway I can't return the ebay phone now unless there is some software or hardware problems within 30 days
So my problem
I am stuck on 4.1.1 on Kies and when I check for update, because the phone is based on AT&T servers, it won't work since I'm on Metro. I wanted to see if there is anyway for me to update my phone to 4.3 which is the current version. Although, I've heard some people have 4.3 problems?
If that's not advisable, could y'all tell me how I could atleast get to Android 4.1.2? Also is there a 4.4 update in the works?
I just got the phone today and would like to be running on something better than 4.1.1
should I flash the AT&T phone to a MetroPCS ROM lol, if any of those are actually available, or if I were to flash, should I flash it to Tmobile?
First off, if its I747, you MUST flash only those Roms. No others. Now, that's indeed a nice phone with LTE Antenna.
You really heard correct. The 4.3 upgrade from the carrier (ATT for you) /Samsung has a lot of issues. I wouldn't do it for any reason. Particularly on T-Mo network, you will have severe signal issues as reported by others. In addition, it now flashes an EFuse onto your phone along with locked bootloader and other scary stuff.I really would not do it.
Lastly, XDA is organized by devices. So even though you are a T-Mo/Metro PCS customer, you will have to post on AT&T SGS3 forum over there.
Speaking of Rom update, Please visit Root66 Thread for this device. You will find Rooted version of your Current Rom. Dunno why but he does not have 4.2.x for you. Please do your research someone else must have posted it.
Now speaking to 4.3, yes there is a way to get 4.3 on your phone without the issues I mentioned above. But first you will have to flash a Custom recovery such as CWM or TWRP with the help of ODIN on your phone. Again do your research well. Once those are in place, take a look at this thread. It will provide 4.3 experience without ANY concerns or issues. Read it carefully and then read some more. Good Luck.
Perseus71 said:
First off, if its I747, you MUST flash only those Roms. No others. Now, that's indeed a nice phone with LTE Antenna.
You really heard correct. The 4.3 upgrade from the carrier (ATT for you) /Samsung has a lot of issues. I wouldn't do it for any reason. Particularly on T-Mo network, you will have severe signal issues as reported by others. In addition, it now flashes an EFuse onto your phone along with locked bootloader and other scary stuff.I really would not do it.
Lastly, XDA is organized by devices. So even though you are a T-Mo/Metro PCS customer, you will have to post on AT&T SGS3 forum over there.
Speaking of Rom update, Please visit Root66 Thread for this device. You will find Rooted version of your Current Rom. Dunno why but he does not have 4.2.x for you. Please do your research someone else must have posted it.
Now speaking to 4.3, yes there is a way to get 4.3 on your phone without the issues I mentioned above. But first you will have to flash a Custom recovery such as CWM or TWRP with the help of ODIN on your phone. Again do your research well. Once those are in place, take a look at this thread. It will provide 4.3 experience without ANY concerns or issues. Read it carefully and then read some more. Good Luck.
Click to expand...
Click to collapse
THANK YOU! Looks like I got a lot of phone work to do over the weekend. SO do you think it was good/should I stick with this AT&T S3 or should I try to sell it for a discount and buy a Metro PCS S3? The ebay buyer won't take my phone back unless there is a hardware or software problem inherent to phone...unless I fake one ?
If it was me, I'd keep the phone. Metro's S3 does not have LTE Antenna. You'd have been stuck at lower speeds.
Perseus71 said:
If it was me, I'd keep the phone. Metro's S3 does not have LTE Antenna. You'd have been stuck at lower speeds.
Click to expand...
Click to collapse
Metro's s3 does have lte
As for the OP you can flash at&t or T-Mobile ROMs it really doesn't matter because they are backwards compatible (I have done it) and you can flash 4.3 ROMs if you don't want to take the official 4.3 update which you can easily do with Odin without the need for kies or ota.. Now, I suggest the first thing you do is flash a custom recovery and then experiment with 4.3 ROMs, if you keep having problems flash 4.1.2 roms.. There are some things you need to do though to get 4.3 up and running so I suggest you read up on it first. Good luck my friend!
Sent from my SGH-M919 using Tapatalk
It was my impression he wanted Stock Touchwiz Roms not AOSP.
Thanks for letting me know Metro has T999L
Perseus71 said:
It was my impression he wanted Stock Touchwiz Roms not AOSP.
Thanks for letting me know Metro has T999L
Click to expand...
Click to collapse
I did mean touchwiz ROMs.. And the metro model is t999n which is pretty much a t999l
Sent from my SGH-M919 using Tapatalk
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
abovenbeyond said:
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
Any M919 modem. MKL is the newest.
abovenbeyond said:
So I have am using already a T-Mobile S4 (m919) on At&t's network... I have already rooted it, flashed Hyperdrive, entered the correct APN, and it works basically well...
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
Glad someone asked that. I looked for a few hours last night and came up empty(been working an off shift so I might have missed it). I am on 4.2.2 MDL and signal is definitely much weaker than my Active on 4.3 . Has anyone compared modems to see which are better?
pahick said:
Glad someone asked that. I looked for a few hours last night and came up empty(been working an off shift so I might have missed it). I am on 4.2.2 MDL and signal is definitely much weaker than my Active on 4.3 . Has anyone compared modems to see which are better?
Click to expand...
Click to collapse
I can provide anecdotal evidence but nothing real...
MK2 is better.
Also, as for which modem to flash; T-Mobile's MK2 would be the one to flash. I've read you can flash other carrier's modems as long as they are the same version, i.e. AT&T MK2 or T-Mobile MK2... but that just doesn't make sense to me and I wouldn't recommend it. The modem you flash is independent of who your carrier is; you go by what brand of phone you have. If you have the M919 then you flash T-Mobile firmwares/modems/etc regardless of which carrier your bill comes from.
abovenbeyond said:
Here is what I am wondering, my signal strength seems to be not the best and it makes me wonder, is there a modem, baseband I can flash on the T-mobile version of the S4 that could possibly help it work better on the At&t network... and do so with out making my S4 a paper weight?
Click to expand...
Click to collapse
I've encountered the same thing with my M919. Switching between Android 4.3 and 4.4.2 modem.bin files made no difference.
I did notice that when I changed my network preference from 3G/2G to 2G-only, I gained about 10 dBa when the handset fell back to GSM-EDGE mode. It made a big difference. I verified that AT&T only uses band II (1900MHz) for GSM and UMTS in my county, so it wasn't because I switched to band V (850MHz) which seems to have better range. What I find annoying is that the handset isn't dropping down to 2G automatically when reception is poor. It'll stick with 3G even when the signal strength is as low as -107 dBa.
No LTE at the moment since my AT&T MNVO doesn't support it.
I'm thinking of buying an M919, carrier unlocked, to use on ATT, so that I can get a proper recovery and have full access to custom ROMs without the safestrap limitations.
Is it safe to say that:
1. If I buy a T-Mobile S4, and it comes carrier unlocked, it will work fine on the ATT network, including 4G / LTE? Lots of data points suggest this but I haven't heard it explicitly stated...
2. Though I could use the phone as identified as an M919, I really want Play Store to see it as an I337 (ATT version), so I can install some ATT specific apps. Is there any problem flashing a build.prop (available in the ATT threads) with the ATT identifiers & APN info, to enable this?
3. Are there any gotchas I should be aware of? Basically, I just want a phone with unlocked bootloader / kernel so I can play. Not too worried about Knox/warranty.
Any insights would be appreciated!
Marc
Frankenscript said:
I'm thinking of buying an M919, carrier unlocked, to use on ATT, so that I can get a proper recovery and have full access to custom ROMs without the safestrap limitations.
Is it safe to say that:
1. If I buy a T-Mobile S4, and it comes carrier unlocked, it will work fine on the ATT network, including 4G / LTE? Lots of data points suggest this but I haven't heard it explicitly stated...
2. Though I could use the phone as identified as an M919, I really want Play Store to see it as an I337 (ATT version), so I can install some ATT specific apps. Is there any problem flashing a build.prop (available in the ATT threads) with the ATT identifiers & APN info, to enable this?
3. Are there any gotchas I should be aware of? Basically, I just want a phone with unlocked bootloader / kernel so I can play. Not too worried about Knox/warranty.
Any insights would be appreciated!
Marc
Click to expand...
Click to collapse
Will the T-Mobile S4 work on the AT&T network; yes it will work if it's carrier unlocked. I purchased my M919 full price out of contract while I was still on AT&T service. Once I carrier-unlocked I was able to pick up AT&T's 4G/LTE and was even able to make use of the AT&T 3G Microcell device which transmits a 3G cell signal and runs over your WiFi. I now have Net10 Wireless with an AT&T SIM card and I still get 4G/LTE when it's around.
Your second question: I do believe that's all that would be required. I'm not 100% sure if just modifying the build.prop would allow you to use the AT&T-specific apps in the Play Store. I never used them to begin with so I never explored whether or not I could make them work on the T-Mobile firmware. Now, I know this involves more than just a build.prop edit, but a 100% sure way to get AT&T Apps working would be to flash a custom ROM based on AT&T firmware. Being that you have a T-Mobile device and are using it on another carrier's network, always remember; when it comes to Odin especially, flash things meant for the T-Mobile M919 ONLY. It doesn't matter that you use AT&T service, your device needs T-Mobile Modems/stock firmwares/etc.
As far as gotchas... not that I can think of. The M919 has an unlocked bootloader and even with KNOX is very easy to root and use custom ROMS on. If you're not concerned with KNOX then you really don't have to take into consideration any special rooting method, no safestrap junk, etc. Without root, just flash a recovery in Odin and flash away.
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
flroots said:
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
Click to expand...
Click to collapse
@flroots
Basically, you're best off bringing the phone to current M919 stock through ODIN. Is that NK2 or has there been a more recent version? I've lost track. But do the entire phone, and in fact as you will see from some threads it is often necessary to flash it twice in succession to get everything to stick. This will bring you to the latest modem. Remember, the modem is two parts: the modem.bin (also known as the gsm modem, which isn't specifically dependent on the bootloader version you have) and the LTE modem (non-hlos.bin, which is dependent on the firmware version, and bad things happen if you mismatch).
Since your phone is out of warranty, there's no downside to going to the latest, even if the phone arrives with 4.2.2 firmware (pre-knox). Tripping the knox bit is only a problem if you would be sending the phone in for warranty service.
I've got the M919 and am using it on ATT, with no problems. I've got the pre-knox firmware (MDL), and will be updating to the latest next time I flash.
Here is an old, but still relevant, thread about my experiences with M919 on ATT.
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
You will have to configure your APN to match your Cricket service. Sorry, can't help you with those settings but I'm sure they are on XDA somewhere!
Marc
Frankenscript said:
@flroots
Basically, you're best off bringing the phone to current M919 stock through ODIN. Is that NK2 or has there been a more recent version? I've lost track. But do the entire phone, and in fact as you will see from some threads it is often necessary to flash it twice in succession to get everything to stick. This will bring you to the latest modem. Remember, the modem is two parts: the modem.bin (also known as the gsm modem, which isn't specifically dependent on the bootloader version you have) and the LTE modem (non-hlos.bin, which is dependent on the firmware version, and bad things happen if you mismatch).
Since your phone is out of warranty, there's no downside to going to the latest, even if the phone arrives with 4.2.2 firmware (pre-knox). Tripping the knox bit is only a problem if you would be sending the phone in for warranty service.
I've got the M919 and am using it on ATT, with no problems. I've got the pre-knox firmware (MDL), and will be updating to the latest next time I flash.
Here is an old, but still relevant, thread about my experiences with M919 on ATT.
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
You will have to configure your APN to match your Cricket service. Sorry, can't help you with those settings but I'm sure they are on XDA somewhere!
Marc
Click to expand...
Click to collapse
Thanks a lot for that update. As I understand it, the current firmware is NB4 according to this site:
http://galaxys4root.com/galaxy-s4-stock-firmware/
Not sure what your reference to NK2 is? That doesn't seem to correspond to either 4.2.2 nor 4.4.2? I'm currently on Cricket with a S4 I337 and hope to move the SIM over as soon as my M919 arrives tomorrow.
I believe after NB4 there was NH7 then NK2. Check the firmware thread in the general section for details / links.
Sent from my SGH-M919 using Tapatalk
@flroots
How did this work out for you? I want to do the same thing you said you where going to do.
flroots said:
I know this thread is a bit old, but the situation is very relevant to me. I just won a S4 M919 on eBay which will be delivered tomorrow. T-mobile has agreed to send me an unlock code. My motivation is to install TWRP recovery which I can't do on the i337. I intend to activate it on Cricket (AT&T network). Is it still true that I should stick with firmware, ROMs, and modems designed for the M919? I don't care about AT&T or T-mobile apps so that's not an issue. Basically, I want the best data rates available. Any gotchas that I need to be aware of?
Click to expand...
Click to collapse
Robert417919 said:
@flroots
How did this work out for you? I want to do the same thing you said you where going to do.
Click to expand...
Click to collapse
Robert417919,
I use my SGH-M919 on an AT&T network also. I use the OK3 modem firmware and it seems to work great here. Although I am in Alaska, so top speeds of LTE are only about 6 Mbps where I live. Usually I can only get about 3 Mbps due to the lack of coverage around here.
You can either update to the latest OH3 firmware on your phone, or if you have an old model, with the MDL bootloader, you could also use this guide by lordodin912:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
Also, if you are looking for good roms, you can always check out SlimLP:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-slimlp-jfltetmo-t3377731
Or Resurrection Remix:
http://forum.xda-developers.com/gal...ent/rom-resurrection-lollipop-v5-4-5-t3115155
Hope that helps!
Thanks, this does help out, and another quick question. Are you able to use wifi calling?
AlaskaLinuxUser said:
Robert417919,
I use my SGH-M919 on an AT&T network also. I use the OK3 modem firmware and it seems to work great here. Although I am in Alaska, so top speeds of LTE are only about 6 Mbps where I live. Usually I can only get about 3 Mbps due to the lack of coverage around here.
You can either update to the latest OH3 firmware on your phone, or if you have an old model, with the MDL bootloader, you could also use this guide by lordodin912:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
Also, if you are looking for good roms, you can always check out SlimLP:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-slimlp-jfltetmo-t3377731
Or Resurrection Remix:
http://forum.xda-developers.com/gal...ent/rom-resurrection-lollipop-v5-4-5-t3115155
Hope that helps!
Click to expand...
Click to collapse
Robert417919 said:
Thanks, this does help out, and another quick question. Are you able to use wifi calling?
Click to expand...
Click to collapse
Glad to help, and no, unfortunately not.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
I just joined in the past few days because I decided to try different ROMs on my i747. This is my 1st ever post, and I thought I'd try out this rooting and flashing that I'm missing out on.
First of all, THANKS to EVERYONE that posts here for all of the help given to me and that others have used. Nice to see people helping out other people in such ways.
Second, I have successfully put a few different ROMs on my i747 over the past few days and can't believe how easy it was. I was always scared to do it. I decided since the thing was just sitting in a drawer not being used "What's the risk?"
Third, my actual issue...No matter what ROM I have on the i747, it will not connect to Wi-Fi at my work. FYI, I work (in IT ironically) in a very large company with hundreds of access points around the campus. So I know it is not the network, as we would have others with the same issue. It connects to all other (that I've tried so far) Wi-Fi networks with no issues.
I just don't understand all the terms bootloader, firmware, kernel, modem etc. I read decriptions (on here) trying to explain and I just can't grasp it.
I was on stock with whatever the last OTA update from AT&T was. I updated the boatloader (I believe) from NE4 to NJ1 to NJ2 using this thread. At least, I'm assuming I did it right. Nothing failed and the Phone Info app looks like it worked. https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Anyone can give me any tips on what I need to do to possible get this working? It's not really a huge deal breaker, it's just bugging me as to why it isn't working.
Thanks in advance!
You upgraded the modem/baseband software when updating the bootloader?
audit13 said:
You upgraded the modem/baseband software when updating the bootloader?
Click to expand...
Click to collapse
I'm guessing no. How do I do that? Don't want to brick it.
I found this link, but what firmware am I on? How do I tell?
https://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577
Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.
audit13 said:
Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.
Click to expand...
Click to collapse
I flashed the zip.
So an unrooted stock ROM also refuses to connect?
audit13 said:
So an unrooted stock ROM also refuses to connect?
Click to expand...
Click to collapse
I don't know how to go back to stock.