Hello all,
I have an S21 Ultra that was originally a T-Mobile device, was unlocked, and then flashed to "factory unlocked" 998U1 firmware as found on this forum, and used with AT&T. Since the shutdown of their 3G network, however, I have been unable to make or receive calls and the "Enhanced LTE Services" option under Network Settings is unavailable to me. After a ton of fruitless troubleshooting, AT&T says I need new firmware. I was going to install the AT&T-branded U1 firmware from SamMobile in hopes that would solve my issue, but whenever I try to go to the bootloader to flash the new firmware, the phone just boots normally instead. I can't seem to access the bootloader, even after factory resetting the device.
Samsung has offered to reflash the device back to factory settings, which would make it a T-Mobile device (unlocked, presumably?) again. Does anybody know if the AT&T firmware linked above will work with VoLTE on their network? Would I be able to flash to that again to get the bloatware-and-branding-free experience while still having the device work as a phone?
Thanks for any knowledge or help, I've been beating my head against this thing for nearly a month now.
I may have solved my issue! Fingers crossed, will confirm tomorrow once I'm sure, but so far, here's what it looks like:
I had installed what I believed to be standard Samsung U1 firmware which I assumed would work regardless of carrier - I believe from this thread but don't quote me on that. Regardless, it was unbranded. When AT&T shut down their 3G network, I was hosed because the U1 firmware I'd installed did not have VoLTE/"Enhanced LTE Services" or anything like that as an option I could enable. After a ton of time, I finally figured out that it was a firmware/baseband issue.
So I downloaded the AT&T "branded" U1 firmware from SamMobile but the recovery menu wouldn't let me access the bootloader for as-yet-unknown reasons. The instructions to hold volume-down+power got me into the recovery menu, but that was as far as I could get. However, Iater discovered that with the device plugged into my computer, I could boot it directly into the bootloader by holding volume-down+volume-up. With that accomplished, I installed the AT&T U1 firmware and viola! VoLTE options were available, and with my SIM card installed I could finally make calls again!
Will use it all day tomorrow, see how things go and report back.
Could you help me i am basically in the same boat! What firmware for at&t did you download and where? Thanks!
I used the firmware at this link: https://www.sammobile.com/samsung/g...M-G998U1/ATT/download/G998U1UES5CVCB/1627452/
I couldn't get to the bootloader from the recovery menu, but could by using both volume keys simultaneously while the phone was powered off and plugged into the computer. Good luck!
There's a good thread on Reddit regarding CSC issues when flashing branded S21 devices to U1 firmware. Essentially, on the S21 series, particularly for TMB CSCs, it tends to be difficult to get the correct CSC software for VZW and ATT, particularly after flashing to U1 from U firmware. See this,
https://www.reddit.com/r/GalaxyS21/comments/roqwkc
Related
I have done quite a lot of searching and it appears that what I am trying to accomplish should be possbile but I have had no luck.
I am trying to move an SM-N960U from AT&T over to Verizon using my Verizon SIM. As far as I can tell this model is compatible on both networks, but if someone could clarify why I am having issues, I would be grateful. Here is what I have going so far:
The SM-N960U is unlocked. I can confirm this on the AT&T site as well the phone as the unlocked animation plays every time.
When I insert the Verizon SIM (which is the correct SIM format, brand new even), the phone sees the number but will not connect to the Verizon network for data/calling
I have Odined the latest stock official Verizon ROM onto the phone, but this changes nothing for some reason. The AT&T software still persists after I install all of updated Verizon files through Odin (The AP, BL, CP, userdata etc). The install is always a success, and shows the loading bar etc, but nothing changes. It's as if nothing is installed.
I have used both regular Odin and the custom 3B Odin
I have factory reset the phone after the install as well, but the AT&T ROM remains.
I am out of ideas on how to get the phone to work on Verizon. Does anyone have an other ideas or see something I missed? Or is it just not possible?
thanks for any help
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
ww007 said:
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
bober10113 said:
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
Click to expand...
Click to collapse
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
ww007 said:
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
Click to expand...
Click to collapse
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
bober10113 said:
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
Click to expand...
Click to collapse
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
ww007 said:
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
Click to expand...
Click to collapse
just use samfirm tool or frija to dl firmware.
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?
I just swapped carriers to Mint Mobile from Verizon. I noticed my Google and Samsung cloud backups were not working and found out it was because Verizon blocks them, so you have to buy their cloud service. I decided to flash the Samsung stock unlocked firmware (G973U1) to my Verizon firmware S10 (G973U). That fixed that problem, but when I check for software updates, it says the security update from January 1st 2022 is the newest update, but I know I got a security update around April 4th when I had the Verizon firmware. None of the firmware on sammobile for the G973U1 says it is newer than this. All the carriers listed here are the same. I don't know why you need different carriers selected here because it should be the same Samsung firmware right? I flashed the T-Mobile one because Mint Mobile uses T-Mobile network and Mint Mobile wasn't listed. Should I flash another carriers version of the locked (G973U) firmware and see if that works? Or should I just flash the Verizon firmware back on it? I also called Mint Mobile tech support and asked them if there was a way for them to push the update to my phone, or if that hadn't released that update on their netork yet, but they said that they don't do anything with the software updates and those come from Samsung.
U1 is an "unlocked" phone that can change carriers via CSC changes. In theory, just swapping SIMs should have switched you over to the new carrier (sometimes this doesn't work).
Flashing the U-version means it may not be the universal version that U! is... so it may not switch over properly. That's the first issue. But now that you've done that, it's kinda moot.
I'm not sure why you put a Verizon FW onto a Mint/TMO carrier at all? I would suggest a U1 TMO or Mint firmware to start with, and see if the CSC updates properly. When that happens, and if it switches properly, then the updates should work normally.
But, even beyond that, you could have just flashed an upgraded version of your ROM to get the update, saving yourself from all of this hassle anyway. Sure, it's not "coming from" the carrier (it never does - it's coming from Samsung usually, as Mint noted)... so you'd just bypass their issues.
Lastly, I will warn you about getting the latest (March) update, as this is Android 12. Many people have had issues with A12 on their phones due to incompatibilities, battery drain, etc. Personally, I'd hold off updating to A12 as long as possible (my and my-wife's phones are both still on A11 for this reason... January update). I just posted on a thread where a user lost GearVR compatibility on A12, and was asking how to downgrade... there are lots of such posts here...
schwinn8 said:
U1 is an "unlocked" phone that can change carriers via CSC changes. In theory, just swapping SIMs should have switched you over to the new carrier (sometimes this doesn't work).
Flashing the U-version means it may not be the universal version that U! is... so it may not switch over properly. That's the first issue. But now that you've done that, it's kinda moot.
I'm not sure why you put a Verizon FW onto a Mint/TMO carrier at all? I would suggest a U1 TMO or Mint firmware to start with, and see if the CSC updates properly. When that happens, and if it switches properly, then the updates should work normally.
But, even beyond that, you could have just flashed an upgraded version of your ROM to get the update, saving yourself from all of this hassle anyway. Sure, it's not "coming from" the carrier (it never does - it's coming from Samsung usually, as Mint noted)... so you'd just bypass their issues.
Lastly, I will warn you about getting the latest (March) update, as this is Android 12. Many people have had issues with A12 on their phones due to incompatibilities, battery drain, etc. Personally, I'd hold off updating to A12 as long as possible (my and my-wife's phones are both still on A11 for this reason... January update). I just posted on a thread where a user lost GearVR compatibility on A12, and was asking how to downgrade... there are lots of such posts here...
Click to expand...
Click to collapse
I didn't flash the verizon U version firmware that was what came on my phone when I bought it. I flashed the T-mobile U1 firmware and it still didn't work. There is no Mint Mobile firmware. Where would I get the upgraded version of the rom? Most people I saw were recomending sammobile.com and the newest U1 firmware only had the January 1 security update. I had android 12 on my S10 before I flashed any firmware, and I didn't have any issues so don't mind running it.
You can get ODIN ROMs from many places. Sammobile is one, Samfw is another. To get latest firmwares, Frija or other such tools are faster because they can download directly from Samsung servers. The limitation is that those can only get the latest versions, not past ones.
Correct, there is no Mint firmware that I am aware of. Yes you should be able to get the TMO firmware, which is actually a TMB CSC. You can see that here: https://samfw.com/firmware/SM-G973U1/TMB/G973U1UEU6HVB2
With that in mind, you'll also see that the CSC version shows "OYM" which is actually a multi-CSC USA firmware. Again, these firmwares should change CSC based on the one shown by your SIM. For example, mine is an OYM ROM, which shows a CSC of TFN/TFN/SPR (first is what carrier the phone is on (Tracfone in my case... I'm using Total Wireless), second is what the SIM is, and last is what the phone was "born" with... that cannot be changed).
If you're running an OYM now (likely you are) then check the CSC... see if it's switch to TMB/TMB/xxx. If that hasn't happened, then that could be part of the reason you're not getting updates. Sometimes phones don't change (one of the 2 phones I got originally would not change, so I had to return it and get another... no idea why).
Note, to change CSC, you need to flash the "CSC" ODIN file, and not the Home_CSC file, as the latter will keep the existing setup of your phone. You can see more info on the difference here: https://www.getdroidtips.com/know-about-csc-home_csc/#CSC-vs-Home-CSC-the-difference
Bottom line, start by checking your current CSC... it should be TMB. If not, you can ODIN flash, with CSC (not HOME_CSC) and that hopefully will get you on the correct CSC. Note that this will erase the phone.
Alternatively, as I mentioned, you can download the latest FW, and just HOME_CSC flash that with ODIN to get you on the latest without waiting for the carrier to push it.
I have some experience in flashing via Odin having done it on previous Samsung devices but I am having all sorts of issues with trying to do this.
I have a Tmobile S21 Ultra 5g and just switched to Verizon. I am trying to flash the firmware to unbranded (XAA if I have read correctly) but I am getting errors. The first error was SHA256 which I read was because I needed a patched Odin. When I switch to the patched Odin, and I have tried both 3.13.1 and 3.14.1, it goes for awhile and fails. I am unsure whether I need to root the device to switch between carriers or try something else. I am unsure if I want to root it as I may eventually want to trade in the phone.
Do I have any options? My main issue is with wifi calling as I am at times in areas where the signal is terrible but may need to make calls. With the switch from Tmobile to Verizon it appears that is not working.