Related
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
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Let me know if anyone runs into any issues. I know in the past, some have had great experience with the U-firmware and others had issues with no reception. I want to see if the same holds true for this build.
Is this update in January?
Update: Yup, I took it last month and everything was OK. I am on Verizon Rom now just expecting it receives Nougat earlier than U furmware, which updates quarterly.
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
torr310 said:
Is this update in January?
Update: Yup, I took it last month and everything was OK. I am on Verizon Rom now just expecting it receives Nougat earlier than U furmware, which updates quarterly.
Click to expand...
Click to collapse
I was hoping Verizon would see the official Nougat by this point. I liked the feel of the U-firmware, but reception was a problem for me on Verizon. I decided I'd give the latest U-firm a shot since waiting for official Verizon Nougat seems like a lost cause at this point. I'll stay with this until Nougat is officially released. This firmware is the December update, and since they update it quarterly, an update should be around the corner. Maybe the next U-firmware will be Nougat. I think Nougat-U would be damn near flawless lol.
I've been running it since beginning of January no Issues
What exactly are the benefits of flashing this? Do I get 7.0? How is the reception? What are the cons?
I have a pretty big problem. I attempted flashing the 4 files with Odin 3.09. After a couple of seconds the operation terminated and now my GS7 is stuck in a bootloop. Whats worse is that when i attempted to boot into recovery, now it shows a blue screen with the android logo that says "installing system update" for about 2 seconds then shuts off, then tries again. Does anyone know how to fix this, at least so I can flash stock back on it?
Update: Fixed it, was able to get into download mode and use odin to flash stock. The flash failed but it was able to trip the OS and recovery back to normal for some reason.
Nobiscis said:
What exactly are the benefits of flashing this? Do I get 7.0? How is the reception? What are the cons?
Click to expand...
Click to collapse
No carrier bloat and a very smooth OS. The reception is great. The cons are that you don't get any of the carrier features, like WiFi calling, visual voicemail, ect.
xlectik67 said:
I have a pretty big problem. I attempted flashing the 4 files with Odin 3.09. After a couple of seconds the operation terminated and now my GS7 is stuck in a bootloop. Whats worse is that when i attempted to boot into recovery, now it shows a blue screen with the android logo that says "installing system update" for about 2 seconds then shuts off, then tries again. Does anyone know how to fix this, at least so I can flash stock back on it?
Update: Fixed it, was able to get into download mode and use odin to flash stock. The flash failed but it was able to trip the OS and recovery back to normal for some reason.
Click to expand...
Click to collapse
Odin 3.9 might be too old. I've used Odin 3.11 or higher on the S7 and have never had any issues.
thanks to you it works perfectly but HOME_CSC failed and caused recovery bootloop after that i tried other CSC and it was successful. I've got very upset on V firmware because they deleted a lot of features on galaxy S7. they are worst
CVertigo1 said:
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Click to expand...
Click to collapse
I'm still having issues with this latest firmwire. I do get LTE but not network connection. I still have circle with a line through it indicating that I don't have service. the service will come on for a second and then cut out. Service is called "123456".
Did you choose the APN to use? If you are using a Verizon SIM card, then it should give you the option to use Verizon, but you need to select it.
CVertigo1 said:
Did you choose the APN to use? If you are using a Verizon SIM card, then it should give you the option to use Verizon, but you need to select it.
Click to expand...
Click to collapse
So there's APN settings and Network Operators. I'm actually using a verizon MVNO called boom mobile. If I selected "verizon" network, I get a notification that says " no service - selected netweork verizon not available". The other one's that show up from the selection are ATT, T mobile, and some 310830 thing. None of them work. I use automatic network detection.
As far as APN settings, I do use Verizon and I get LTE data from that. I just don't get the phone service connection.
matase said:
So there's APN settings and Network Operators. I'm actually using a verizon MVNO called boom mobile. If I selected "verizon" network, I get a notification that says " no service - selected netweork verizon not available". The other one's that show up from the selection are ATT, T mobile, and some 310830 thing. None of them work. I use automatic network detection.
As far as APN settings, I do use Verizon and I get LTE data from that. I just don't get the phone service connection.
Click to expand...
Click to collapse
Hmmm. This is passed my level of experience then. I'm only familiar with setting up and using authentic Verizon service. I can't speak for other services that use Verizon's network.
Install PL2 from PI3?
CVertigo1 said:
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Click to expand...
Click to collapse
Sorry for a newbie question. Can I install this firmware from a verizon PI3 firmware? Thanks in advance!
pboy said:
Sorry for a newbie question. Can I install this firmware from a verizon PI3 firmware? Thanks in advance!
Click to expand...
Click to collapse
Yes you can.
Thank you for sharing your experience. I was looking into flashing the U firmware for a while and I finally pulled a trigger after seeing this thread.
Everything works well on Verizon and it feels great to have a clean phone & freedom to switch. I think it's worth waiting a little more for Nougat.
p.s. Anyone has an idea on when official G930U Nougat will be released?
Will this work for my AT&T S7 on PJ4 firmware?
jOdin3
hey guys,
this is the first non-nexus phone i've used, and I am excited about flashing the U firmware to get a clean stock experience on my g930v. I was wondering what files i should input in jOdin under the PDA/Bootloader/CSC/Phone fields after I extract the zip file SM-G930U? I have searched tried to watch some insufferable youtube videos on the matter have had no luck finding an answer. Also since I'm asking, is it possible to flash this firmware with jOdin3, sorry for the newbie questions, didn't know where else to go.
Thanks in advance to any helpful replies.
Solved the above, no need for replies.
Next though is when I try and flash using Jodin3 the pit file is acquired, the phone reboots and then it stays disconnected and I am unable to start the process after the phone reboots. Any suggestions?
Solved the above by using heimdall to extact pit.
I am close to giving up and flashing anything via jOdin3 I have tried pretty much everything to flash new firmware with no success, latest error is that there is a corrupt file, need to use Odin file...
HAS ANYONE had success flashing a Verizon S7 on macOS? if so please tell me where to go.
How can I get 930u to 930v?
jerecole2378 said:
How can I get 930u to 930v?
Click to expand...
Click to collapse
Flash the Verizon firmware from the Verizon threads
Hey Guys, i totally messed up my phone. I've been using my U1 Unlocked S10+ in Bulgaria for a few months. The issue that kept bothering me is that i was down to LTE instead of LTE+ connection. I found that the Carrier aggregation is not properly working when using an US Phone in Europe. For the last couple of weeks i've been digging down the rabbit hole trying to figure out if there is a way to somehow make the CA actually working. I ended up in this thread https://forum.xda-developers.com/galaxy-s7/themes/snapdragon-carrier-aggregation-europe-t3888421 . Someone somehow managed to create this script for S7 that can actually turn CA on and use it to their full potential. All good but with my stupid head, i decided to run the script on mine and voala...... my network connection is gone. Further down the thread on a question of would it survive a Factory reset the answer was yes but not a full firmware reflash. So i downloaded my most current firmware from SamMobile and reflash the whole thing ( using CSC file for a full Wipe ) but that didn't do the job. On that same comment about wouldn't survive reflash was mentioned " especially for another carrier " so i downloaded G975U T-Mobile Branded Firmware and flashed it again with CSC and UserData files attached. Didn't do anything again. I Reflashed back to stock U1 but now i have fully unusable phone and i have no idea what to do to bring back the network connection. Is there anything that i am missing here and didn't already do to bring back my phone to life? Thanks in advance!
CuBG said:
Hey Guys, i totally messed up my phone. I've been using my U1 Unlocked S10+ in Bulgaria for a few months. The issue that kept bothering me is that i was down to LTE instead of LTE+ connection. I found that the Carrier aggregation is not properly working when using an US Phone in Europe. For the last couple of weeks i've been digging down the rabbit hole trying to figure out if there is a way to somehow make the CA actually working. I ended up in this thread https://forum.xda-developers.com/galaxy-s7/themes/snapdragon-carrier-aggregation-europe-t3888421 . Someone somehow managed to create this script for S7 that can actually turn CA on and use it to their full potential. All good but with my stupid head, i decided to run the script on mine and voala...... my network connection is gone. Further down the thread on a question of would it survive a Factory reset the answer was yes but not a full firmware reflash. So i downloaded my most current firmware from SamMobile and reflash the whole thing ( using CSC file for a full Wipe ) but that didn't do the job. On that same comment about wouldn't survive reflash was mentioned " especially for another carrier " so i downloaded G975U T-Mobile Branded Firmware and flashed it again with CSC and UserData files attached. Didn't do anything again. I Reflashed back to stock U1 but now i have fully unusable phone and i have no idea what to do to bring back the network connection. Is there anything that i am missing here and didn't already do to bring back my phone to life? Thanks in advance!
Click to expand...
Click to collapse
if you are SM-G975U OR U1
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
1. Download this patched version of Odin
2. Then grab this modem file.
https://drive.google.com/file/d/12JH7ObHxKTF3PBqyzh3Rqy7wvvJVg-o0/view?usp=drivesdk
3. The usual Samsung drivers installed, run admin privileges, download mode, yada,yada, flash in CP slot, when reboots it'll update your sim settings.
Supposed to be combo firmware but without token that's all it does although Odin claims success in flashing modem. It does not sim unlock the phone
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But for some reason, AT&T doesn't allow their firmware to be publicly available (for any of their devices). I pay for a subscription to a website that gets the official releases (usually) before they hit SamFirm/Frija, and also gives me access to AT&T firmware. So I'm providing it here as a favor to anyone who would make use of it.
Manual Odin flashing in this case would be designed for those of you who:
- want to flash AT&T firmware onto a T-Mobile or Metro device that has been SIM unlocked, in order to have AT&T's customizations and enhancements
- want to manually update to a newer version on your device, either because you don't want to wait for the OTA or because OTAs aren't working on their device (usually because you're using it on a different carrier because AT&T requires an active AT&T SIM to be inserted in order for their devices to successfully check for an OTA update)
This is not a "beginner's guide to Odin flashing"-type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware, I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=305872
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you.
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data
**I do not have one of these devices and this has not been 100% verified, until someone actually tries it. Until it's been verified, you're responsible for backing up your data, taking precautions to avoid an FRP lock, etc
- From what I've seen so far, there are some builds that only AT&T will get, some that only T-Mobile and Metro will get, and some that all 3 carries will get. Since T-Mobile (use region/CSC TMB) and Metro (use region/CSC TMK) firmware can be freely downloaded by anyone at any time from SamFirm/Frija, I won't be posting their unique builds here. I also won't be posting any builds that all 3 carriers get. U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside. So that means that any U firmware version (no matter the carrier) can be flashed to any U device (no matter which carrier's firmware it's running) at any time.
So I'll only be posting AT&T-exclusive builds and even then, I won't post every single one. I don't have unlimited bandwidth on my subscription site, and it takes a lot of time and effort to download the files, extract them, create the HOME CSC, zip them all back up, and upload them to AFH. I'll try to post at least one build per month though
- Switching from one carrier's firmware to another carrier's will require use of the USERDATA file, and also a factory reset. If you just want to manually update instead of waiting for an OTA, then you only need to flash the 4 base files (use HOME CSC if you want to avoid a factory reset).
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
I recently tried to install the tmb version of n976u att but when it starts it doesn't load that version and it still continues in ATT that I'm flashing bl, ap, cp, csc, what am I doing wrong?
dr.jonirafael said:
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
Click to expand...
Click to collapse
Not possible. No unbranded firmware exists for this model
Can I put the 976(5g) on the 975U?
JapAnEEzE said:
Can I put the 976(5g) on the 975U?
Click to expand...
Click to collapse
The answer hasn't changed since you last asked it.
(in other words it is still no)
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
fncd said:
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
Click to expand...
Click to collapse
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
iBowToAndroid said:
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
Click to expand...
Click to collapse
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
fncd said:
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
Click to expand...
Click to collapse
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
iBowToAndroid said:
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
Click to expand...
Click to collapse
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
fncd said:
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
Click to expand...
Click to collapse
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
iBowToAndroid said:
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
Click to expand...
Click to collapse
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
fncd said:
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
Click to expand...
Click to collapse
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
iBowToAndroid said:
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
Click to expand...
Click to collapse
So here's the thing. The first time I ever inserted my T-mo sim, I got a message about settings, and the phone restarted. It still wasn't T-mo branded, nor did it have any of the bloat (I think that is expected, no?). No other time did it ever ask me, even after being completely wiped. However, after the subsequent installs and wipes, I always had my sim in it.
Odin never threw an error, but of course, that doesn't stop me from potentially downloading the wrong firmware for my device, correct? But in reading your first post, the firmware should all be interchangeable, so I have no idea what caused it to want to see CDMA instead of GSM. Or the super wonky IMEI issue.
I'm on the way home now and will try it again, knowing that I still have the ATT firmware saved in case something goes wrong.
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
fncd said:
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
Click to expand...
Click to collapse
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
iBowToAndroid said:
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
Click to expand...
Click to collapse
When I first got the phone, it had the ATT ringtones on it, but I never noticed the boot screen being ATT. After the flash though, those were (and are) completely gone. And when I first put my sim in there, I didn't see any ATT apps on it at all.
Edit: Should have noted that I bought it used, but did confirm with AT&T that it was paid off and unlocked by them, but is it possible that the previous owner removed the apps with the *#2xxxxxx# code change? (he did claim to have worked for Samsung recently before moving to my area to another tech company...who knows if that's true or not). Unfortunately I couldn't get that code to do anything. Shrug.
---------- Post added at 12:09 AM ---------- Previous post was at 12:01 AM ----------
Looking at your page here: https://androidfilehost.com/?w=developers&did=4128
It looks like another user posted the T-Mobile flash for January. At least I know (or believe I know) that that will be another trusted source. I'm downloading that now in the hopes that it has the userdata and such in the zip as well. I will flash that over in just a few minutes and see what shakes out.
---------- Post added at 01:01 AM ---------- Previous post was at 12:09 AM ----------
Update: So here is where things get super weird and really have me wondering what is going on with this thing. If I try to flash the latest (march) TMB firmware, the phone boots and doesn't get signal (CDMA mode). If I reset the phone and then flash the latest ATT firmware (on AFH, I think it's February), the phone works perfectly, but still no ATT customization. So. If it holds true that the 4 base files are the same, then the only thing that can be causing that is something in the newer TMB userdata / csc files, right? As those are the only differences.
All of this being said and carrier bloat aside, the phone says it's on LTE+ right now, but the download speeds (according to ookla) are over 200mb (20Mb) / sec. Which, according to Venturebeat is the speed of T-Mobile's 600Mhz 5G service, which is plastered all over my area.
Long story short - As long as I'm flashing ATT Userdata / CSC, then the phone operates normally - though I won't get updates until I can get that XAA/XAA/ATT changed to ATT/ATT/ATT. Flashing any other Userdata / CSC after December 2019 causes issues with the radio.
I do appreciate all of your help, and while my post count is non-existent, I have done my homework as best I can before posting (constant lurker)
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
change csc
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
p3r1k0 said:
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
Click to expand...
Click to collapse
Was there anything that was broken or missing on the phone, after you changed it using the code? Were there any functions that did not work?
No luck for me
dr.jonirafael said:
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
Click to expand...
Click to collapse
For most devices, Tmobile even has in their forums how to flash to a different carrier. However, their directions require you to flash the "unlocked" version of the phone (XAA) first, then the carrier specific firmware to change it over. For the Note 10+ 5G, there is no unlocked version. Samkey lists the 5G as not supported. I have tried a flashing a few different ways to move my ATT version to Tmobile, and it always boots with ATT even after Odin saying it was flashed successfully.
Context: I have a Verizon branded Note 10+, trying to use a Mint mobile connection. Wi-fi calling doesn't work, connection speed is atrocious, but everything works swimmingly out of the box when I put the same SIM in my unlocked Pixel. I am quite sure my Note 10+ is unlocked because it is fully paid off and well past the 60 day period, and more importantly because the Mint SIM DOES work in it, just very poorly.
So it's quite evident that I have to flash TMB firmware to get a serviceable reception.
Trying to follow the steps outlined here - https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648
Based on what I understand I have to flash unbranded firmware first and then my desired carrier firmware which is T-Mobile. Can someone please help me understand what firmware I should be looking for?
My current baseband version N975USQU3CTE7.
My question is when downloading through Frija, should I be looking for SM-N975U1 (VZW) firmware or SM-N975U1 (XAA) firmware for the first step? Or can I use either?
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
TheXev said:
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
Click to expand...
Click to collapse
To anyone reading this in future, I followed this guide to the letter and worked flawlessly for me..every feature that I wanted now works without any additional configuration..signal quality has improved drastically..
Thanks for taking the time to write this..took me a couple of days to set everything up and prepare..I am glad I didn't rush it