Related
I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Geekser said:
I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Click to expand...
Click to collapse
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
d.cortez said:
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
Click to expand...
Click to collapse
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
michelino159 said:
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Click to expand...
Click to collapse
Neither Option worked for me - ODIN Flashes got stuck halfway thru the flash - and Smart Switch just didn't work
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
d.cortez said:
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
Click to expand...
Click to collapse
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Geekser said:
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Click to expand...
Click to collapse
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
d.cortez said:
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
Click to expand...
Click to collapse
I have an IMEI number from a Note 9 that was an aTT Phone - I had purchased the snapdragon varient at Best buy and then returned it when I got the N960F . I copied the IMEI number before I turned it in - I suppose I could use that. Can you offer a link to the thread you are referring to?
thanks for the tip my friend.
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
dev base is Alexander rom in the development section.
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
If I am not mistaken, it was something like this https://forum.xda-developers.com/galaxy-note-9/development/test-s2arh6-devbase-v5-9-encryption-t3847061
you do need to have TWRP installed in order to flash
hope that helps
still need help
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
Do you still need help here is the link to the firmware that I used to flash stock ROM make sure you read what and how it is to be done the first time i flashed it i got stuck in bootloop and then i read it again and got it right now my phone works and is fine hope you have your phone working https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
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?
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?
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.