Hi Guys
I am from India and i have AT&T Note 3 unlocked variant.
I took a new connection- Reliance JIO. I am sure most of you guys must not be aware about it but it only works on VOLTE.
Inserted the sim today and found that data (Internet) is working fine but unable to make incoming and outgoing calls.
Reliance JIO uses a app called JioJoin which actually makes calls through VoLTE.
I tried going to *#*#4636#*#* and i have selected LTE/GSM but still unable to make outgoing calls.
Is there any rom which i can install where VoLTE is working fine?
I am using [ROM]AryaMod V8.3 TW Lollipop For ATT [Port] and developer has clearly mentioned that VOLTE is not working.
Please help.
Does VoLTE work on a stock rom? The 900a supports the carrier lte frequencies?
How do you got jio sim for N900A
After installing myjio app I'm not getting get new sim option
Plzz help
hy hi im looking for the same....if u already fix d problem ..please help me too.
thank you
Yes. Same. Problem solve my problem. Plz
I don't think custom ROMs on N900A support VoLTE. You can use Jio 4G voice though...
I have Sm-N900S with arya mode Note 7 v2.1 custom rom how to get volte in this rom for jio sim I am using jio voice for call but this is irritating app
Hi
rocky_pratik said:
Hi Guys
I am from India and i have AT&T Note 3 unlocked variant.
I took a new connection- Reliance JIO. I am sure most of you guys must not be aware about it but it only works on VOLTE.
Inserted the sim today and found that data (Internet) is working fine but unable to make incoming and outgoing calls.
Reliance JIO uses a app called JioJoin which actually makes calls through VoLTE.
I tried going to *#*#4636#*#* and i have selected LTE/GSM but still unable to make outgoing calls.
Is there any rom which i can install where VoLTE is working fine?
I am using [ROM]AryaMod V8.3 TW Lollipop For ATT [Port] and developer has clearly mentioned that VOLTE is not working.
Please help.
Click to expand...
Click to collapse
Hi,
I dont have solution for your query. But i am in need to root & load custom rom on to my SM_N900A. Do you have instructions and files needed for this? I had some issues in the past as listed below:
I earlier installed lollipop and i experienced signaling related issues as most of the time the phone says "emergency calls only"....so i flashed it back to 4.4.2 based on the instructions listed in XDA. still i am experiencing same calling issues.
so, i thought may be i should flash a custom rom which might fix these issues and tried this tutorial and got following error:
Error flashing zip '/external_sd/Download/AllianceROM_N900A_1_v12.zip'
Updating partition details...
Failed
after this, my phone stuck at boot logo, so used ODIN again to restore back to 4.4.2, but this time i see a "custom rom" logo in addition.
Now, what i need help is, can i fix this issue of "emergency calls only" at most of the times? if the signal is too good, then the phone works!!! appreciate any help.
-sekhar.
sekhar, you can't flash a custom ROM to a 900A, only a modified Samsung 900A ROM.
Second, you flash a ROM first, then you root it. Rooting first, then flashing a ROM, flashes an unrooted ROM (unless it's rooted, in which case you didn't have to root it first). It's the ROM that's rooted, not the hardware.
The "custom ROM" issue is because there are still signs in the phone that there had been a custom ROM in it. You could install Xposed, then install the Wanam Xposed app, and set the ROM to "normal".
Update (2018-06-13): This project is discontinued. I no longer have any interest in debugging device-specific issues related to this CSC (like the modem sometimes failing to initialize on the SM-G955F). In addition, the risk of emergency calls not working is too great for me.
With the release of the Nougat beta for the S7 Edge, Samsung finally upgraded their IMS framework from 5.0 to 6.0 in the international ROMs. This gives the international ROMs almost all the functionality needed to support WiFi calling, VoLTE, RCS, and other carrier features on the SM-G935F. This project provides a flashable support package to add the T-Mobile specific components.
Enjoy!
---
NOTE: Because the telephony stack is modified, please ensure that emergency/E911 calls still work. Contact your local authorities to find out how to test emergency calls. Even though modding your device may be fun, a phone is still a phone, and you'll never know if you'll need it in an emergency situation.
---
Current versions:
T-Mobile components:
System: G935TUVS4BQC1
CSC: G935TTMB4BQC1
Flashing instructions
Back up the EFS partition and save it outside of the device. This zip will modify the EFS partition in order to switch to the "TMB" CSC.
Flash TMoblify. This includes the files necessary for the T-Mobile carrier features. It includes a modified copy of the T-Mobile CSC where the network lock is removed.
Reboot.
Downloads:
All downloads are available at: https://mega.nz/#F!VxZhHSiY!MU4N3wk3OFOqvWTJsExZGw
---
All of the files are signed and can be verified with the .asc signature files. To verify the signatures, use your favorite PGP tool or run:
Code:
gpg --recv-key 2233C479609BDCEC43BE9232F6A3B19090EFF32C
gpg --verify filename.zip.asc filename.zip
If the file is valid, a message similar to the following will be printed:
Code:
gpg: Signature made Wed 07 Dec 2016 01:09:33 AM UTC
gpg: using RSA key [b]2233C479609BDCEC43BE9232F6A3B19090EFF32C[/b]
gpg: [b]Good signature from "Xiao-Long Chen <[email protected]>"[/b] [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: [b]2233 C479 609B DCEC 43BE 9232 F6A3 B190 90EF F32C[/b]
XDA:DevDB Information
TMoblify, ROM for the Samsung Galaxy S7 Edge
Contributors
chenxiaolong
ROM OS Version: 7.x Nougat
Based On: TouchWiz
Version Information
Status: Testing
Created 2016-12-07
Last Updated 2018-06-13
Reserved
Reserved
can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??
Nice work :good:
Will this work with 930P sprint variant?
N4MI21 said:
can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??
Click to expand...
Click to collapse
I'm currently waiting for my AndroidFileHost dev account request to be approved. Once that happens, I'll will mirror the files.
As far as VoLTE goes, this is meant for people using the SM-G935F on T-Mobile (USA) only. It will not enable any network features for other carriers.
jkhan49 said:
Nice work :good:
Will this work with 930P sprint variant?
Click to expand...
Click to collapse
Thanks! This will not work with any of the US models, like the SM-G930P (it's a ROM for the Exynos models). However, if I remember correctly, I thought all the US models were compatible and you could simply flash the SM-G935T or SM-G935U firmware.
TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks
A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?
rp3 said:
A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
Click to expand...
Click to collapse
I personally don't know the answer to this. I haven't looked into the differences between the Flat and Edge variants.
rp3 said:
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
Click to expand...
Click to collapse
You should be able to use this in other TW 7.0 ROMs (both odexed and deodexed). The files are from the SM-G935T ROM, but are not device-specific.
rp3 said:
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?
Click to expand...
Click to collapse
SuperSU is currently broken with TW 7.0 due it's method of handling SELinux. You'll need to use Magisk + phh Superuser.
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Superuser: http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
It might be easiest to flash the T-Mobile support package on top of your existing ROM if you're already running TW 7.0.
cstark27 said:
TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks
Click to expand...
Click to collapse
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH
Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?
hollisnh said:
Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?
Click to expand...
Click to collapse
If the ROM is not modified too drastically, I'd imagine it would work just fine.
Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !
Sunnyschlecht said:
Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !
Click to expand...
Click to collapse
Yes, absolutely! I'll update to the latest beta either today or tomorrow. I'll check on the Samsung Cloud backup/restore with the new update.
Thank you so much. Just a heads up the WiFi calling gives me ER08 when trying to connect, so I'm hoping for your magical work.
chenxiaolong said:
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH
Click to expand...
Click to collapse
I haven't tried with Nougat, but that hasn't been an issue for MM.
I'm also using a G935FD with wifi-calling, VoLTE, etc. on T-mobile using Superman 1.17 and TMB CSC via CSC selector (1.8).
From what I've experienced, the second sim slot doesn't come into play unless you're actually using two sims; otherwise it just functions as an SD slot.
I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?
I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
aaronc_98 said:
I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?
Click to expand...
Click to collapse
rp3 said:
I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
Click to expand...
Click to collapse
I will give it a try... I believe that you said you flashed another rom with their default CSC then flashed the TMB support package, but I dont believe that you are saying you got it working with this ROM, is that correct?
Firstly I own a Samsung note 9 Unlocked SM-N960U1
I saw some threads about using the IMS menu to change it
But I couldn't open it as I was on oreo
I saw an app and was able to open the following:
[LINK]https://i.imgur.com/HHniykj.jpg[/LINK]
Is it the IMS menu?
Then when I checked my phones IMS Service status
It showed the following:
[LINK]https://i.imgur.com/97IfSn0.jpg[/LINK]
When I checked the IMS Status of a phone that supports VoLTE
It says that IMS is registered and all others are unavailable except VoLTE and video calling
When I talked with customer care that volte doesn't work but you can use Airtel or other ISP than jio to make calls
I need a way to use VoLTE on my phone without root and bootloader unlock (as it is not possible to do both on a snapdragon Samsung device)
I have kept the image links like above as this is my first post and I am not able to add attachments
DivyatejaPasupuleti said:
Firstly I own a Samsung note 9 Unlocked SM-N960U1
I saw some threads about using the IMS menu to change it
But I couldn't open it as I was on oreo
I saw an app and was able to open the following:
[LINK]https://i.imgur.com/HHniykj.jpg[/LINK]
Is it the IMS menu?
Then when I checked my phones IMS Service status
It showed the following:
[LINK]https://i.imgur.com/97IfSn0.jpg[/LINK]
When I checked the IMS Status of a phone that supports VoLTE
It says that IMS is registered and all others are unavailable except VoLTE and video calling
When I talked with customer care that volte doesn't work but you can use Airtel or other ISP than jio to make calls
I need a way to use VoLTE on my phone without root and bootloader unlock (as it is not possible to do both on a snapdragon Samsung device)
I have kept the image links like above as this is my first post and I am not able to add attachments
Click to expand...
Click to collapse
You need to flash carrier firmware to get WiFi calling and VoLTE working. The only carrier that supports WiFi calling and VoLTE on the U1 firmware is T-Mobile. I'm assuming you're on Verizon or ATT?
I am in India and I have an N960U1
So flashing is also not possible
DivyatejaPasupuleti said:
I am in India and I have an N960U1
So flashing is also not possible
Click to expand...
Click to collapse
Ok then it probably won't work in India. You need the international N960F model.
Mr. Orange 645 said:
Ok then it probably won't work in India. You need the international N960F model.
Click to expand...
Click to collapse
Even with the f model I seem to be unable to get this working. Says 'permission denied'. I have root as well and have done the firmware flash obv..
If you have an f model why did u have to root it.It is supposed to work directly also
I'm in the same situation now. Not able to use Jio. Were you able to fix this issue?
I own a N960U1 and I'm in south America, I can use VoLTE with my current network provider with no issue. Only problem is the VoLTE option disappears whenever I get updates here in south America. Last update I was in Canada connected to Tellus network and the option appeared back. Same happened in past December when I was in US connected to ATT network, VoLTE appeared back in settings after update, next update I was back in home and no VoLTE after. How do I keep that option whenever I update phone in south America? I've already tried updating with no sim, no network connection, airplane mode ON and location disabled, it didn't work. My guesses are phone takes info from last network it was connected to and then enables/disables options based on this.
Vinu198 said:
I'm in the same situation now. Not able to use Jio. Were you able to fix this issue?
Click to expand...
Click to collapse
In fact i kept the phone aside for 2 months as it wasn't compatible with Jio.
I started using with Jio using jio voice calling app 2days ago.
I was on April security patch.
I've updated it to May version last night, after updating, VoLTE started working. I was surprised.
Now there's another update showing up but am hesitant to update.
Check my screenshot i posted as attachment.
Flash April version, start using via jiocall app then update to May version if you are still having issues.
Thanks for the response. With lost of research I found a solution which worked for me.
Just changed the country in Google play store to India and restarted my phone and Voila, there appeared my VoLTE sign on top and able to use it like a regular sim card. I'm going with all the updates and no issues.
Hey,
As per the image image attached, the firmware you are talking about is U1 ATT May Update . Is that correct ?
Currently I am on April U1 update without carrier and going through the same problem(Jio Sim and No VOLTE , so cannot make voice calls)
Where can I get May Firmware for U1 ATT .
Thanks in Advance.
nimms said:
In fact i kept the phone aside for 2 months as it wasn't compatible with Jio.
I started using with Jio using jio voice calling app 2days ago.
I was on April security patch.
I've updated it to May version last night, after updating, VoLTE started working. I was surprised.
Now there's another update showing up but am hesitant to update.
Check my screenshot i posted as attachment.
Flash April version, start using via jiocall app then update to May version if you are still having issues.
Click to expand...
Click to collapse
shahpratik said:
Hey,
As per the image image attached, the firmware you are talking about is U1 ATT May Update . Is that correct ?
Currently I am on April U1 update without carrier and going through the same problem(Jio Sim and No VOLTE , so cannot make voice calls)
Where can I get May Firmware for U1 ATT .
Thanks in Advance.
Click to expand...
Click to collapse
Am on U1 (unlocked firmware not ATT)
https://samdb.org/model/SM-N960U1/region/XAA/ download here
nimms said:
Am on U1 (unlocked firmware not ATT)
https://samdb.org/model/SM-N960U1/region/XAA/ download here
Click to expand...
Click to collapse
Hey, so my phone was in April update U1 Unlocked , and upon checking for updates it showed me 800MB of update of N960U1EU2CSH2 . After a more researching , I just took the leap of faith and updated the phone and wolah, VOLTE and WIFI Calling Enabled. So I Guess the later updates after May are working well and they have not removed the functionality.
I can also conclude this carrier bloat slowed down the phone like crazy with the Lag and now the phone is soo smooth and responsive without it.
Thank You again for the Prompt Reply.
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.