Database Develop

Flashing TMO firmware onto Verizon Note 8 - Need help identifying correct firmware.

I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!

leprkon said:
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
Click to expand...
Click to collapse
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.

Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
Thanks for the prompt reply! I am downloading the file right now from sammobile. Let's hope it has everything needed! Thanks again!

Please let me know what worked, didn't. I may be doing the same very soon.

Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.

leprkon said:
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
Click to expand...
Click to collapse
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better

BlueFox721 said:
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
Click to expand...
Click to collapse
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.

I failed to mention that you needed the modified Odin. I think it is normal for it to stop at 32% and then start erasing. It did the same when I went from unlocked variant to vzw. Keep us updated on your progress.

leprkon said:
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
Click to expand...
Click to collapse
The boot to bootloader is In the main recovery menu, but yeah...you need to use the modified odin

Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
Support SINGLE-SKU
Supported API: 3
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
-- Installing package...
Finding update package...
opening update package...
Verifying update package...
Update package verification took 1.1 s (result 2).
Installing update...
Successfully installed package.
-- Resizing data...
E:failed to mount /data (Invalid Argument) can't mount '/data', rc = '-1'(Invalid Argument)
E:failed the resizing-data-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- amazon_symlink_vze...
-- Deleting VZW's apn file
Successfully deleted VZW's apn file
Successfully verify for dmverity hash tree.
Click to expand...
Click to collapse
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.

leprkon said:
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
Click to expand...
Click to collapse
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator

BlueFox721 said:
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
Click to expand...
Click to collapse
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.

leprkon said:
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
Click to expand...
Click to collapse
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck

BlueFox721 said:
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
Click to expand...
Click to collapse
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.

leprkon said:
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
Click to expand...
Click to collapse
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...

BlueFox721 said:
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
Click to expand...
Click to collapse
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?

leprkon said:
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
Click to expand...
Click to collapse
Good to know....I try to use updato when available...how is that one?

BlueFox721 said:
Good to know....I try to use updato when available...how is that one?
Click to expand...
Click to collapse
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?

leprkon said:
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
Click to expand...
Click to collapse
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...sorry I didn't think of it sooner...hope it helps.
Looks like we need factory binary and Canadian firmware...

BlueFox721 said:
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...
Click to expand...
Click to collapse
I've done version 3.12.7 and PC 3.12+
I'll try the carrier switching instructions again, but I couldn't get it to work properly. I'll let you know how it goes.
Edit -
It looks like those instructions require a factory binary firmware flash. Is there a way of doing it without that?

Desperately Need Help - Samsung SM-N960F/DS + T-mobile PUK and other issues.....

Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".​
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.

orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.

bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.

orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker

bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.

orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?

bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM

bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it

bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.

I went to a site with all "official" downloads and I don't see anything for ZBDMYM........

orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links

bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.

orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck

bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.

orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar

bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......

orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ

I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4

If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......

orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?

SM-N960U Stuck In Roaming After Moving From Sprint To Verizon

Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?

quackmaster said:
Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
Click to expand...
Click to collapse
Since you've already done a factory reset I would think the next logical step is to flash the Verizon or the unlocked firmware. What about the SIM card, did they try a new one?

They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?

quackmaster said:
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
Click to expand...
Click to collapse
There is a thread somewhere in the guide section I recall seeing before from daillcyruz (I think was the OP). Search it and you will find instructions on how to install the VZ firmware.

I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.

quackmaster said:
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
Click to expand...
Click to collapse
Maybe try using Odin?

BladeRunner said:
Maybe try using Odin?
Click to expand...
Click to collapse
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.

quackmaster said:
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
Click to expand...
Click to collapse
I ran across a thread where someone had posted a version of Odin that ran on Linux.
Here's one: https://forum.xda-developers.com/android/general/utility-odin-linux-jodin3-casual-t3777030
and another: https://forum.xda-developers.com/android/general/odin4-v1-0-linux-t3782930

None of these work. I am not able to get the PIT from device.

quackmaster said:
None of these work. I am not able to get the PIT from device.
Click to expand...
Click to collapse
you might be able to use odin in wine.. i never tried it tho.. heimdall i havent got to work either..
what firmware are you on? pie is pretty good at switchin csc based on sim inserted.. also crk3 i think it is you can access the csc.apk and change csc easily to any csc.. i havent found any other firmware it works on tho besides crk3..
if u can manage that, theres update.zips you can adb sideload but u need to b on specific firmware versions to update to certain firmwares..
i was messin around with firmwares and changed my csc to sprint.. i have vzw.. although it says roaming i am connected to verizon network so dont think its actually roaming but im not 100% sure

OK
Thanks everyone for help!
I was able to successfully flash using a Windows 10 VM running in Oracle VirtualBox VM. I used Odin v3.13_B. I did not re-partition.
I used this firmware:
https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U/VZW/download/N960USQS1ARJ9/242777/
There were no errors though after the phone rebooted it said there was an "unauthorized attempt" to install software.
It then tells me to connect to Wifi in order to verify my identity.
I cannot skip this process.
The Sprint firmware still seems to be present as I see Sprint applications. I am still roaming on Verizon though the port request was completed at least that's what they said at the store.
Interestingly the Sprint logo does not appear upon booting phone. Only the Samsung logo.
To remove Sprint firmware do I need to flash to the non-carrier firmware first before trying Verizon?

I sounds like someone else had the same problem with the SM-N960U.
The solution in that thread seems to be using the SM-N960U1 firmware.
Can anyone confirm this would be a safe fix to try?

SamMobile is a horrible website
I paid the 8 euro fee and the download for https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/VZW/download/N960U1UES1ARJ9/244757/ still takes like an hour.

It seems there's some Google phone protection targeted to deter thieves. That could be why it requires me to sign into the previous Google account after flashing.
I am removing my Google account from the phone, doing factory reset, then will try to flash Verizon firmware.

After flashing again it looks like some software called "Sprint OMDAM" still present on the phone. This loads after flashing. When I try to activate on network it comes up while the phone remains in roaming. Again Sprint unlocked the phone.
Should I re-partition?

OK
I wiped the cache partition and did factory reset.
I will yet again try another flash.

The Sprint logo is gone but Sprint apps still remain.
Should I try to re-partition the phone? I don't understand why Sprint applications are showing up when I flash Verizon firmware using Odin.

Make sure you have a Verizon SIM card in the phone.
1. Remove your accounts (Google and Samsung) under settings.
2. Factory reset under settings.
3. Download the U1 firmware using the SamFirm tool
4. Using modded ODIN 3.13.1B flash all four files (use CSC_OYN not the HOME_CSC file).
Optional, if you want WiFi calling and VoLTE:
Download the VZW N960U firmware using the SamFirm tool and flash it the same way using modded ODIN, but this time include the USERDATA file as well.

I think now on Verizon network after using U1 firmware!

Having trouble converting unlocked Note 9 to AT&T firmware

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.

Successfully forced October update on Unlocked S20FE 5G on TMobile by changing CSC

Forewarning: I cannot guarantee this will work for everyone or that your data will not be wiped. Backup, backup, backup! This resulted in NO WIPE for me. All data was intact.
I just spent a long time trying to figure out why I cannot get the October updates on my Unlocked S20FE that is currently on T-Mobile. No matter what I did, I couldn't get it to give me an update option. I heard swapping SIMs with a non-TMo provider will do it, but I didn't have access to one.
This led me to learning about Samsung's CSC system. CSC is "Consumer Software Configuration" or "Country Specific Codes". These codes are locked in to the phone until a new SIM on a different carrier is inserted. I tried many network reset options with no luck. You have to force a reset of the CSC.
First, the initial CSC for my USA unlocked S20 FE 5G is XAA, which just tells the phone it's an Unlocked US model. You can see your CSC codes under Settings > About Phone > Software Information > Service provider SW ver. Look at the third line and see 3 codes like such "XXX/XXX/XXX". My understanding is Samsung saves a history of CSC codes: 1) The current 2) the previous and 3) the original. It can move back and forth between the first 2, but the will never resort back to the 3rd (original CSC) even if you remove the SIM. Before, I saw TMB/TMB/XAA. TMB is the T-Mobile CSC, and XAA is my original. So I needed to somehow overwrite the TMB codes to XAA.
How to:
1. Remove SIM and keep it out until the end.
2. Go to Settings > About Phone. Long press the 15-digit number next to IMEI to Copy it, or write it down.
3. Open Samsung Phone app, type *#272*(IMEI NUMBER)# <Paste your IMEI without the (), and Dial. You won't be able to dial this with a SIM in.
4. You will see a list of codes in a "preconfig" window with your 2 codes at the top. For Unlocked XAA models like myself, select XAA, (if you have a different original CSC, then use it). There are sites with lists of available CSC codes if you wanted to do different carriers/regions.
5. Click Install, and then select Sales & Network Code Change, (Network change only changes the 2nd CSC, you must select Sales & Network to change both 1st and 2nd CSCs), click Ok. and your phone will reboot. Once up, go back to Software Information, check the CSC codes are set to XAA/XAA/XAA, then you should be able to check for your software update.
6. Update Software, reboot, then insert SIM, and reboot again and you will be up to date and back on your network.
Essentially, you're just setting the phone as if no SIM card was ever inserted. Had you performed an update on a brand new phone over wi-fi before ever inserting your SIM, you would have the update the exact same way. After I got the update over Wi-Fi and my phone reset, I reinserted my SIM and my CSC codes are set back to TMB/TMB/XAA with the baseband version of G781U1UEU1ATJ5 and the October 1, 2020 Security Patch. Should this happen again where T-Mobile's updates are lacking behind, a simple CSC reset would do the trick again.
Good luck. Let me know how it works for you. Again, I'm not responsible for you messing anything up or losing data, but it worked perfectly for me. This could be used to change regions and carriers on your phone as well, not just for updates.
EDIT: I haven't been able to get back into the "preconfig" CSC change screen anymore. I've read that others have only been after to get back into the preconfig change screen after a factory reset. So it sounds like you can only modify the CSC once between factory resets.
EDIT 2: Of course, the day after I do this, T-Mobile finally pushes the update. I'll leave this information up for future usage.
EDIT 3 (07 Dec 20): Thanks to info from dopeyone2011, the dial code *#*#27262826#*# works to change CSC update multiple times after the original one. As of 07 Dec, I was still on the 01 Oct security patch on T-Mobile. December's isn't available, but I was able to get the 01 Nov patch. Hopefully T-MO gets their act together so this doesn't have to happen monthly.

Did this get you the ATJ5 firmware update with all of the supposed touchscreen fixes?
EDIT: Sorry, I see you mentioned that you now have ATJ5. Thanks! Doing this NOW.
EDIT 2: WORKED GREAT! Thanks for this great tutorial!!

Wondering if this would work on a Tmobile Locked phone

Sooo, after all this work, T-Mobile just released their update. FML! :laugh: I'll leave this information up for future usage, though.

Esormit88 said:
Sooo, after all this work, T-Mobile just released their update. FML! :laugh: I'll leave this information up for future usage, though.
Click to expand...
Click to collapse
Seriously? It must have been within the last hour or so because it wasn't available just prior to me using your instructions to update this morning.

You are a champion, thanks for this! I've been trying to figure out how to achieve exactly this. I still had not received the TMobile update as of 11:30am Central today. Did this and received the update immediately. Ran some of tests using Touch Screen Test and much better results (still not perfect). Will now try some gaming to see if it has fixed the intermittent unresponsiveness.
Esormit88 said:
Forewarning: I cannot guarantee this will work for everyone or that your data will not be wiped. Backup, backup, backup! This resulted in NO WIPE for me. All data was intact.
I just spent a long time trying to figure out why I cannot get the October updates on my Unlocked S20FE that is currently on T-Mobile. No matter what I did, I couldn't get it to give me an update option. I heard swapping SIMs with a non-TMo provider will do it, but I didn't have access to one.
This led me to learning about Samsung's CSC system. CSC is "Consumer Software Configuration" or "Country Specific Codes". These codes are locked in to the phone until a new SIM on a different carrier is inserted. I tried many network reset options with no luck. You have to force a reset of the CSC.
First, the initial CSC for my USA unlocked S20 FE 5G is XAA, which just tells the phone it's an Unlocked US model. You can see your CSC codes under Settings > About Phone > Software Information > Service provider SW ver. Look at the third line and see 3 codes like such "XXX/XXX/XXX". My understanding is Samsung saves a history of CSC codes: 1) The current 2) the previous and 3) the original. It can move back and forth between the first 2, but the will never resort back to the 3rd (original CSC) even if you remove the SIM. Before, I saw TMB/TMB/XAA. TMB is the T-Mobile CSC, and XAA is my original. So I needed to somehow overwrite the TMB codes to XAA.
How to:
1. Remove SIM and keep it out until the end.
2. Go to Settings > About Phone. Long press the 15-digit number next to IMEI to Copy it, or write it down.
3. Open Samsung Phone app, type *#272*(IMEI NUMBER)# <Paste your IMEI without the (), and Dial. You won't be able to dial this with a SIM in.
4. You will see a list of codes in a "preconfig" window with your 2 codes at the top. For Unlocked XAA models like myself, select XAA, (if you have a different original CSC, then use it). There are sites with lists of available CSC codes if you wanted to do different carriers/regions.
5. Click Install, and then select Sales & Network Code Change, (Network change only changes the 2nd CSC, you must select Sales & Network to change both 1st and 2nd CSCs), click Ok. and your phone will reboot. Once up, go back to Software Information, check the CSC codes are set to XAA/XAA/XAA, then you should be able to check for your software update.
6. Update Software, reboot, then insert SIM, and reboot again and you will be up to date and back on your network.
Essentially, you're just setting the phone as if no SIM card was ever inserted. Had you performed an update on a brand new phone over wi-fi before ever inserting your SIM, you would have the update the exact same way. After I got the update over Wi-Fi and my phone reset, I reinserted my SIM and my CSC codes are set back to TMB/TMB/XAA with the baseband version of G781U1UEU1ATJ5 and the October 1, 2020 Security Patch. Should this happen again where T-Mobile's updates are lacking behind, a simple CSC reset would do the trick again.
Good luck. Let me know how it works for you. Again, I'm not responsible for you messing anything up or losing data, but it worked perfectly for me. This could be used to change regions and carriers on your phone as well, not just for updates.
EDIT: I haven't been able to get back into the "preconfig" CSC change screen anymore. I've read that others have only been after to get back into the preconfig change screen after a factory reset. So it sounds like you can only modify the CSC once between factory resets.
EDIT 2: Of course, the day after I do this, T-Mobile finally pushes the update. I'll leave this information up for future usage.
Click to expand...
Click to collapse

I misspoke. T-Mobile locked phones got the update, but apparently Unlocked phones on T-Mobile have not yet.
So, I'm learning more about this system. (I've rooted and modded phones long ago, but gave it up on newer modern phones, so know my way around Android systems fairly well, just not Samsung). I now want to know WHY the 272IMEI dialing "preconfig" doesn't work anymore. Even though I don't need to, I'm very curious if I can figure out a wipe-free/root-free fix.
Dialing the 272IMEI number opens an .apk called Preconfig, which is a sub app of CIDManager. When I try to open preconfig using Activity Launcher, I get a long error that says Permission Denial... and "requires com.sec.permission.preconfig". I opened up a file manager and went to the root folder, found the CIDManager xml file, and looked at its text, it references the preconfig.apk and its permissions, but I've searched for the preconfig apk and it's just not on the phone anymore, or completely hidden. It appears that when you do this CSC change through preconfig, it removes the preconfig apk as part of the process. Not sure why. I'm going to continue investigating how to get preconfig apk back on the phone, or even if it's possible without root. I need someone with a bone-stock S20FE to see if I can copy their preconfig.apk files.
EDIT: I had someone who updated their U1 XAA Unlocked phone by the AT&T SIM trick, and he's locked out of 272IMEI and preconfig options. I'm beginning to think the AT5J firmware just locks out the preconfig app removing the option for CSC changes?

Finally got update today in usa on unlocked t-mobile. I guess we're going to be late which sucks

im only replying to this so that i can add nothing to this thread other than perhaps a smile. We all know we could use more of that nowadays.
EDIT 1: updated purpose of post
EDIT 2: Self realization of my true purpose on earth
(felt like i couldnt post in this thread without the requisite 2 edits)
joking aside, nice write-up man! keep up the good work!

Got the update for T-Mobile today. Touchscreen issues seem to be resolved now so that's nice.

So it looks like the last Unlocked update came out 20 Oct, but it took 2 weeks to get to everyone? That means the earlier October update took even longer.
Not sure what else we can do but continue to hound T-Mobile and Samsung to give us these patches. Unlocked phones should never be last.

Any way to restore preconfig.apk?
Esormit88 said:
Forewarning: I cannot guarantee this will work for everyone or that your data will not be wiped. Backup, backup, backup! This resulted in NO WIPE for me. All data was intact.
I just spent a long time trying to figure out why I cannot get the October updates on my Unlocked S20FE that is currently on T-Mobile. No matter what I did, I couldn't get it to give me an update option. I heard swapping SIMs with a non-TMo provider will do it, but I didn't have access to one.
This led me to learning about Samsung's CSC system. CSC is "Consumer Software Configuration" or "Country Specific Codes". These codes are locked in to the phone until a new SIM on a different carrier is inserted. I tried many network reset options with no luck. You have to force a reset of the CSC.
First, the initial CSC for my USA unlocked S20 FE 5G is XAA, which just tells the phone it's an Unlocked US model. You can see your CSC codes under Settings > About Phone > Software Information > Service provider SW ver. Look at the third line and see 3 codes like such "XXX/XXX/XXX". My understanding is Samsung saves a history of CSC codes: 1) The current 2) the previous and 3) the original. It can move back and forth between the first 2, but the will never resort back to the 3rd (original CSC) even if you remove the SIM. Before, I saw TMB/TMB/XAA. TMB is the T-Mobile CSC, and XAA is my original. So I needed to somehow overwrite the TMB codes to XAA.
How to:
1. Remove SIM and keep it out until the end.
2. Go to Settings > About Phone. Long press the 15-digit number next to IMEI to Copy it, or write it down.
3. Open Samsung Phone app, type *#272*(IMEI NUMBER)# <Paste your IMEI without the (), and Dial. You won't be able to dial this with a SIM in.
4. You will see a list of codes in a "preconfig" window with your 2 codes at the top. For Unlocked XAA models like myself, select XAA, (if you have a different original CSC, then use it). There are sites with lists of available CSC codes if you wanted to do different carriers/regions.
5. Click Install, and then select Sales & Network Code Change, (Network change only changes the 2nd CSC, you must select Sales & Network to change both 1st and 2nd CSCs), click Ok. and your phone will reboot. Once up, go back to Software Information, check the CSC codes are set to XAA/XAA/XAA, then you should be able to check for your software update.
6. Update Software, reboot, then insert SIM, and reboot again and you will be up to date and back on your network.
Essentially, you're just setting the phone as if no SIM card was ever inserted. Had you performed an update on a brand new phone over wi-fi before ever inserting your SIM, you would have the update the exact same way. After I got the update over Wi-Fi and my phone reset, I reinserted my SIM and my CSC codes are set back to TMB/TMB/XAA with the baseband version of G781U1UEU1ATJ5 and the October 1, 2020 Security Patch. Should this happen again where T-Mobile's updates are lacking behind, a simple CSC reset would do the trick again.
Good luck. Let me know how it works for you. Again, I'm not responsible for you messing anything up or losing data, but it worked perfectly for me. This could be used to change regions and carriers on your phone as well, not just for updates.
EDIT: I haven't been able to get back into the "preconfig" CSC change screen anymore. I've read that others have only been after to get back into the preconfig change screen after a factory reset. So it sounds like you can only modify the CSC once between factory resets.
EDIT 2: Of course, the day after I do this, T-Mobile finally pushes the update. I'll leave this information up for future usage.
Click to expand...
Click to collapse
Hi, Thank you so much for this method! Is there a way to restore the preconfig.apk after following the above method? should I have created a backup of the preconfig.apk file before following the above steps and restored it after, would that have worked?

TheLumpSum said:
Hi, Thank you so much for this method! Is there a way to restore the preconfig.apk after following the above method? should I have created a backup of the preconfig.apk file before following the above steps and restored it after, would that have worked?
Click to expand...
Click to collapse
I've found a method that works post firmware flash on my SM-G781U1 AIO/AIO/XAA ATJ5. Using this method, I have been able to alter my CSC as many times as I'd like, with the SIM card still inserted even. Not that that does a lot of good as it reboots to adjust for the carrier Sim directly after. First you download Phone by Google app. Set it as your default dialer. Next, you download phone info+the one that says Samsung underneath with a star on each side. Go to phone info plus and run the secret codes plugin. If you scroll down you will find a code that says CIDmanager. There are several instances of codes that say CID manager. The one that works for me is *#*#27262826#*#*. Entered in the phone by Google app with no need to use the dial button. I have been able to bring up the preconfig menu and change my CSC multiple times at will with this method.
---------- Post added at 05:23 PM ---------- Previous post was at 05:23 PM ----------
dopeyone2011 said:
I've found a method that works post firmware flash on my SM-G781U1 AIO/AIO/XAA ATJ5. Using this method, I have been able to alter my CSC as many times as I'd like, with the SIM card still inserted even. Not that that does a lot of good as it reboots to adjust for the carrier Sim directly after. First you download Phone by Google app. Set it as your default dialer. Next, you download phone info+the one that says Samsung underneath with a star on each side. Go to phone info plus and run the secret codes plugin. If you scroll down you will find a code that says CIDmanager. There are several instances of codes that say CID manager. The one that works for me is *#*#27262826#*#*. Entered in the phone by Google app with no need to use the dial button. I have been able to bring up the preconfig menu and change my CSC multiple times at will with this method.
Click to expand...
Click to collapse
I attempted to upload screenshots but it keeps telling me bad request

Yea, if you type this code "*#*#27262826#*#*" in the google app, then hit the "Don't change this carrier" option on the bottom, you can stay on XAA. I was just about to post about this since xaa and vzw both block the *272* code

Slightly off topic, but, theoretically, if I changed the CSC to a region that has OEM bootloader unlock, removed the sim, rebooted, and used a VPN to mask my IP as being from the aforementioned region, would I be able to unlock the bootloader and root without paying $100 and giving remote access to my machine to a random Chinese server?

rdeets said:
Slightly off topic, but, theoretically, if I changed the CSC to a region that has OEM bootloader unlock, removed the sim, rebooted, and used a VPN to mask my IP as being from the aforementioned region, would I be able to unlock the bootloader and root without paying $100 and giving remote access to my machine to a random Chinese server?
Click to expand...
Click to collapse
LMFAO, NO!

dopeyone2011 said:
I've found a method that works post firmware flash on my SM-G781U1 AIO/AIO/XAA ATJ5. Using this method, I have been able to alter my CSC as many times as I'd like, with the SIM card still inserted even. Not that that does a lot of good as it reboots to adjust for the carrier Sim directly after. First you download Phone by Google app. Set it as your default dialer. Next, you download phone info+the one that says Samsung underneath with a star on each side. Go to phone info plus and run the secret codes plugin. If you scroll down you will find a code that says CIDmanager. There are several instances of codes that say CID manager. The one that works for me is *#*#27262826#*#*. Entered in the phone by Google app with no need to use the dial button. I have been able to bring up the preconfig menu and change my CSC multiple times at will with this method.
---------- Post added at 05:23 PM ---------- Previous post was at 05:23 PM ----------
I attempted to upload screenshots but it keeps telling me bad request
Click to expand...
Click to collapse
Incredible! *#*#27262826#*# works for me!

This is great info! Used it a few days ago to update my USA unlocked version to ATK1 without having to wait for slow-ass T-Mobile to push it (I'm using a t-mobile sim). I'll use it again to immediately update to One UI 3.0 when it launches for the S20 FE at the end of this month.

Esormit88 said:
Forewarning: I cannot guarantee this will work for everyone or that your data will not be wiped. Backup, backup, backup! This resulted in NO WIPE for me. All data was intact.
I just spent a long time trying to figure out why I cannot get the October updates on my Unlocked S20FE that is currently on T-Mobile. No matter what I did, I couldn't get it to give me an update option. I heard swapping SIMs with a non-TMo provider will do it, but I didn't have access to one.
This led me to learning about Samsung's CSC system. CSC is "Consumer Software Configuration" or "Country Specific Codes". These codes are locked in to the phone until a new SIM on a different carrier is inserted. I tried many network reset options with no luck. You have to force a reset of the CSC.
First, the initial CSC for my USA unlocked S20 FE 5G is XAA, which just tells the phone it's an Unlocked US model. You can see your CSC codes under Settings > About Phone > Software Information > Service provider SW ver. Look at the third line and see 3 codes like such "XXX/XXX/XXX". My understanding is Samsung saves a history of CSC codes: 1) The current 2) the previous and 3) the original. It can move back and forth between the first 2, but the will never resort back to the 3rd (original CSC) even if you remove the SIM. Before, I saw TMB/TMB/XAA. TMB is the T-Mobile CSC, and XAA is my original. So I needed to somehow overwrite the TMB codes to XAA.
How to:
1. Remove SIM and keep it out until the end.
2. Go to Settings > About Phone. Long press the 15-digit number next to IMEI to Copy it, or write it down.
3. Open Samsung Phone app, type *#272*(IMEI NUMBER)# <Paste your IMEI without the (), and Dial. You won't be able to dial this with a SIM in.
4. You will see a list of codes in a "preconfig" window with your 2 codes at the top. For Unlocked XAA models like myself, select XAA, (if you have a different original CSC, then use it). There are sites with lists of available CSC codes if you wanted to do different carriers/regions.
5. Click Install, and then select Sales & Network Code Change, (Network change only changes the 2nd CSC, you must select Sales & Network to change both 1st and 2nd CSCs), click Ok. and your phone will reboot. Once up, go back to Software Information, check the CSC codes are set to XAA/XAA/XAA, then you should be able to check for your software update.
6. Update Software, reboot, then insert SIM, and reboot again and you will be up to date and back on your network.
Essentially, you're just setting the phone as if no SIM card was ever inserted. Had you performed an update on a brand new phone over wi-fi before ever inserting your SIM, you would have the update the exact same way. After I got the update over Wi-Fi and my phone reset, I reinserted my SIM and my CSC codes are set back to TMB/TMB/XAA with the baseband version of G781U1UEU1ATJ5 and the October 1, 2020 Security Patch. Should this happen again where T-Mobile's updates are lacking behind, a simple CSC reset would do the trick again.
Good luck. Let me know how it works for you. Again, I'm not responsible for you messing anything up or losing data, but it worked perfectly for me. This could be used to change regions and carriers on your phone as well, not just for updates.
EDIT: I haven't been able to get back into the "preconfig" CSC change screen anymore. I've read that others have only been after to get back into the preconfig change screen after a factory reset. So it sounds like you can only modify the CSC once between factory resets.
EDIT 2: Of course, the day after I do this, T-Mobile finally pushes the update. I'll leave this information up for future usage.
EDIT 3 (07 Dec 20): Thanks to info from dopeyone2011, the dial code *#*#27262826#*# works to change CSC update multiple times after the original one. As of 07 Dec, I was still on the 01 Oct security patch on T-Mobile. December's isn't available, but I was able to get the 01 Nov patch. Hopefully T-MO gets their act together so this doesn't have to happen monthly.
Click to expand...
Click to collapse
Question! I have an unlocked model (XAA) right now that I've been using on T-Mobile. Both ATT and now just yesterday Verizon has pushed the ONE UI 3.0 update. I've tried using the CSC change to go back to XAA to try and get the update but it's not there yet. Would it be possible to change to VZW instead of XAA using the above method to get the update from Verizon and then putting my T-Mobile sim back in after update to switch it back to TMB? Would getting the Verizon version of the ONE UI 3.0 update mess anything up on my unlocked device? I believe all carriers push the exact same version don't they?

Any confirmation of performing this procedure being able to wipe your device? Because I have an S20FE as well, but locked on TMobile

I'm updating this post to state that this method no longer works. It's been patched by Samsung. I used to use it all the time, but when you dial the number now, nothing happens. It used to bring up the CSC change menu.