I just unboxed my G955FD and put my cricket SIM in and have no response from the network other than pushing an APN and my phone number. I tried manually selecting carrier networks and it listed 5 different "cricket" to attempt to connect to. At one point it showed signal bars in the status area, but no network connectivity. When I automatically connect to the network it responds saying I am registered but no signal bars in status and no activity. I appreciate the help.
Can anyone offer some tips before I call it a lost cause? The phone is out of its return period and probably broken since it will now receive a cricket badge and bars and LTE service but will not make calls or go online
Hey, are you on stock ROM. My 955F works just fine on Cricket, though compared to my daughters AT&T setup, her data is much faster. just discovered this today, and tomorrow will visit Cricket and AT&T to find out why...
Jan 9, 2108 update. I discovered Cricket is limited to about 5-6 Mps. I'm now on AT&T, for a few dollars more for two lines, and can get up to about 40-60 Mps in town.
What region CSC are you using?
---------- Post added at 07:59 AM ---------- Previous post was at 07:35 AM ----------
Here are my apn settings
Name: any but I input Internet or Cricket, I think it will work with whatever you like.
APN: ndo
MMSC: http://mmsc.aiowireless.net
MMSC proxy: proxy.aiowireless.net
multimedia message port: 80
mcc: 310
mnc: 150
apn type: default,mms,fota,hipri,supl
I know when I've setup APs on other phones there have been times that I will first do a 'reset' of my network settings on the phone, then reboot. Sometimes that will help. After that I will enter new APN settings and reboot.
On this 955F, with a viable CSC my phone just finds Cricket and works. With a bad CSC, it may list/show the cricket or AT&T networks, and will not register, no matter what I do, and for how long.
For example, my phone initially had a stock F ROM and a Panama region for the CSC. It worked with Cricket straight away. I changed the CSC to XAA using AT&T, and would find the towers, but would absolutely not register/work.
I ended up installing CarHDROM - a Note 8 OS ported for the 8+, and It took me a bit to find a CSC package that was meant for the ROM (Note 8) I was using, meaning I had to use a Note 8 CSC, even though my phone was an 8+ 955. Once that installed, Cricket started right away.
The CSC that came with CarHDROM I don't think worked straight out, but I can't recall for sure. I did end up using a XAA CSC, for the Note 8, non-AT&Tand that solved my connection issue after I had installed the CarHDROM.
CSC and phone wise, the ROM takes precedent, and the CSC must match the ROM (model). Seems that way to me, anyway.
Hope his helps.
There is another post about a FD phone that won't connect up, as well.
https://forum.xda-developers.com/galaxy-s8+/help/original-firmware-t3725472
I am on stock ROM. I guess I will root today and change CSC and hopefully that fixes whatever issue is going on. I have seen the cricket badge and LTE bars recently but no registration on network. If not, the eBay seller said they will take the phone back I'd it's indeed broken.
Ok so far no luck changing the CSC on stock ROM. I am going to try a couple different ROM and CSC combos tonight. Once again I am showing bars and cricket badge but not connecting data or voice on the phone, after root, and changing CSCs. I feel like Im so close and passed up my last day to return to eBay seller so I hope it truly is software and not hardware related. Im thinking of going by AT&T to act like a potential customer and see if its cricket messing up. Any other suggestions to try before I go crazy and use this phone for target practice?
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
ChikhaiBardo said:
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
Click to expand...
Click to collapse
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
JeffDC said:
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
Click to expand...
Click to collapse
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC? Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
ChikhaiBardo said:
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC?
Yes
Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
Click to expand...
Click to collapse
Just flash the CSC that comes 'stock'/with the rest of the full, stock firmware set, Odin will work. Have the SIM in the phone before you reboot, as for me it seems to help.
I haven't found a difference, for me yet, just flashing the exact CSC through Odin or TWRP. As I'm now on a custom ROM, I'm usually flashing via TWRP with a CSC that is supplied by an Aroma setup. Aroma is very handy.
Yes, flash your full stock via Odin. If you have TWRP you will lose it. You can re-flash TWRP from Odin. I typically flash TWRP all by itself, but I don't think that is really necessary. Maybe someone will come along and let us know.
As an aside I always keep a copy of zips/installs of TWRP, re-verity and SU on my SD card.
So after the stock full flash, I reboot into download mode and Odin flash TWRP, and follow that by a direct 3 key reboot into recovery, and TWRP will load. If you are going to root then flash re-verity, then SU/Magisk. You could then flash your CSC, but with the issues you've been having, I'd then boot to system, do the initial setup of the phone, and then boot back to recovery/TWRP, backup the phone.
Then TWRP flash the CSC Aroma package, making sure you have the SIM in the phone and reboot to system. I've been using XAA as my CSC with my custom ROM, within that is AT&T, T-Mobile, etc for US phones. I select the main XAA CSC from Aroma. Next I select the unbranded XAA as my more specific/local package, instead of AT&T, for example.
My 955F, stock worked just fine on it's 'stock' CSC (China region). I only had to change the CSC when I flashed a custom ROM, and that ROM did not have the ROM's (model) of XAA, so I had to find a CSC, which had XAA, that 'matched' the ROM I had flashed. I had flashed a Note 8 ROM, CarHDROM,v8 initially. Again, that ROM was largely meant for Europe and Exynos phones, so I had to be pointed to a Note 8 CSC that was compatible with the Note 8 custom ROM.
Yes, Odin is where you would flash stock firmware/stock CSC (not in an Aroma package) for your SM-G955FD. It is my understanding that all non-US phones, eg the G955's, are mechanically the same, so flashing 'any' Exynos ROM, G955FD ROM should work via Odin. You can also flash CSC packages via Odin as well, but there is no Aroma process, to my knowledge/experience. So have the specific and correct CSC to flash via Odin, if you go that route. It sounds like you are aware your phone is Exynos? A non-US phone?
I specifically bought my G955 (8+) as non-US so it could take root smoothly/easily, and work great world wide, including working great here in the US. Sometimes the U.S. does not seem a part of the world.
As I've been messing about with S7's/8s, there have been times that the phone did not grab onto AT&T, for example, and i would then 'reset' the network and reboot, with the SIM in the phone, then do a search for phone networks/services. That usually solved it, but when it did not, and I know I have the right CSC, I would then input/create a new APN, with AT&T, Cricket, Sprint, or what-ever service I needed, then reboot.
The only times I've not gotten the phone/s to grab the networks after that is when I've had the incorrect CSC.
Again, on my stock what-ever country G955F, stock G930S, etc, all Exynos, with the same stock (non-US) CSC that come in the firmware package, the phones have grabbed AT&T/T-Mobile just fine. If it would not, I would have reset the network, rebooted and entered the APN, and then rebooted (with the SIM in the phone). Done a network search after that, if necessary.
Hope this helps.
So today I stopped by TMOBILE and the store clerk popped a SIM card in and it fired up 4G LTE immediately and made calls. I then decided to stop by AT&T and it showed bars but refused to register or do anything even with the APN settings being pushed through from AT&T and Cricket. I am finally happy to realize that my phone is not defective (which I had feared before) and that it must be this service area and the bands on the G955FD. I have wanted to switch to TMOBILE for awhile now anyway so this is my chance to have an excuse to do it. Any input on why it won't access AT&T through an AT&T or Cricket SIM? I'm curious now more than anything. It must be missing a band that this area uses correct? The phone is clearly unlocked and functioning correctly.
What local CSC r u using?
Did you have AT&T check the APN?
T-Mobile and AT&T work on S8+ just fine, but need appropriate APNs.
Head back to the AT&T, if you want AT&T, and see if they will reset and or reinstall AT&T CSC/OS on your phone. XAA/ATT will have the AT&T boot logo. XAA/XAA (generic US use, ATT/T-Mobile compatible) will not.
One ringy dingy, two ringy dingy's...
Related
How do I incorporate [tmk ] csc from a 955u1 firmware multi-csc into my 955u T-Mobile firmware? Can I just flash the csc_home in odin from the 955u1? On first boot with the sim card inserted it cannot find necessary Files to load features.
Sent from my BTV-W09 using Tapatalk
tdamocles said:
How do I incorporate [tmk ] csc from a 955u1 firmware multi-csc into my 955u T-Mobile firmware? Can I just flash the csc_home in odin from the 955u1? On first boot with the sim card inserted it cannot find necessary Files to load features.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
Flashing Home will leave your CSC at what ever it was before the flash, I believe. It's meant, near as I understand, to leave your 'home' settings alone.
Find a CSC that matches you ROM, 'U' as you've indicated, that has XAA CSC within it, and has the Aroma installer built into the CSC package..
Once you start the install, select XAA at the first opportunity, then on the next 'page' you will have choices for ATT, T-Mobile, etc. You should also see another 'XAA' option to select, which is a 'generic' selection. I use that. I believe the generic selection works for all US GSM phones, without bloat. Make sure your SIM card is in the phone when booting into System.
You may have to input the T-Mobile APN if the phone does not find the carrier, so if the system does not pick up your T-Mobile network right away. If not try a network search. If that fails, reset the network, reboot and see if T-Mobile is grabbed. If not, input a new, correct T-Mobile APN, and reboot.
Should work as long as all other things are OK.
JeffDC said:
Flashing Home will leave your CSC at what ever it was before the flash, I believe. It's meant, near as I understand, to leave your 'home' settings alone.
Find a CSC that matches you ROM, 'U' as you've indicated, that has XAA CSC within it, and has the Aroma installer built into the CSC package..
Once you start the install, select XAA at the first opportunity, then on the next 'page' you will have choices for ATT, T-Mobile, etc. You should also see another 'XAA' option to select, which is a 'generic' selection. I use that. I believe the generic selection works for all US GSM phones, without bloat. Make sure your SIM card is in the phone when booting into System.
You may have to input the T-Mobile APN if the phone does not find the carrier, so if the system does not pick up your T-Mobile network right away. If not try a network search. If that fails, reset the network, reboot and see if T-Mobile is grabbed. If not, input a new, correct T-Mobile APN, and reboot.
Should work as long as all other things are OK.
Click to expand...
Click to collapse
I am not rooted and was refering to flashing in Odin. By what means do you achieve your method, I'm truly misinterpreting what you are trying to tell me. I can get features like volte and WiFi calling to work in the unlocked u1 tmk firmware but with the new information out about bl3 I switched to carrier "u" firmware(tmb) because I have an original Xfinity "u" phone but carrier "u" firmware isn't loading necessary stuff.
Trying to acheive this for MetroPCS.
Sent from my SM-G955U using Tapatalk
I flashed the T-Mobile firmware bql1 but it ended up not giving me any bloatware except Facebook and no T-Mobile boot screen and xaa/xaa/cct in about phone. Can not get MetroPCS volte and WiFi calling working on the 955 "u" firmware. Any guidance would be much appreciated.
Sent from my SM-G955U using Tapatalk
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
JohnAtlas said:
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
Click to expand...
Click to collapse
If your current firmware has WiFi calling (Volte) You can only use Volte if the network supports it. There are however many apps you can use for WiFi calling look on the play store.
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
JohnAtlas said:
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
Click to expand...
Click to collapse
Volte is wi fi calling over a network which the network operator supports without the need for a specific app.
Please tell me exactly what you are trying to do
What network are both phones using?
Which networks were the phones on initially?
Have you modified the phones in any way? Root? or TWRP?
What firmware are both phones currently using? Go to Settings>about phone>software information>baseband version G930A????
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
JohnAtlas said:
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
Click to expand...
Click to collapse
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
cooltt said:
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
Click to expand...
Click to collapse
Ok, If you think unbranded is the best way to go can you point me in the right direction
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Beanvee7 said:
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Click to expand...
Click to collapse
What beanvee has said but I think it's worth mentioning I find Sam Firm tool pretty straight forward to use and you'll always get the firmware in separate parts which can be useful.
I found a link for the G930A here
I'm not really understanding the differences in firmware. How is flashing with this firmware
any different than what's on the phone right now?
I am just trying to get the wifi calling to work, How is flashing it with at&t version firmware going
to help me on the tmobile network.
I guess I don't know what I need, stock, unbranded, official or custom rom.
I checked all sites listed and there is no firmware for the J727a, alternative?
I would rather someone more knowledgeable guess what I need to do, if that is what is
necessary because the phones are no good to me without that feature. Any suggestions
would be appreciated.
Each carrier deploys their own CSC file, which contains carrier specific configurations, and its this file that determines if VoLTE or VoWIFI is enabled and how it connects.
AT&T may have different VoWIFI settings to TMobile, which is why using AT&T firmware it doesn't work. Some carriers outright disable it since they don't offer it.
Your best bet would be G930T firmware https://updato.com/firmware-archive-select-model?q=SM-G930T&rpp=15&order=date&dir=desc&exact=1
However unbranded G930U should also work because the unbranded firmware is meant to work on all cariers. G930A would likely get you no where since it'll be AT&T specific
The phones in the USA are all identical hardware under the hood, the only difference is the carrier branding and firmware.
But that's only for the S7, I'm not familiar with the J7.
And it's not through lack of knowledge @JohnAtlas, US phones are a nightmare to do anything with. There are several options available but it's difficult to explain what to do and how to do if you are not familiar with how the software works.
There are many guides on how to unlock the software on all US networks, and depending on the network can include multiple steps to complete, you just have to search and read.
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
JohnAtlas said:
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
Click to expand...
Click to collapse
All files in correct slots and use this Odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
JohnAtlas said:
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
Click to expand...
Click to collapse
That is the system recovery and when you flash with Odin you need to put your phone in download mode first press volume down+home+power. The phone should not go to that screen you have posted either before or after Odin, its a completely different recovery mode.
Get your firmware from updato. Com or sammobile
G930U, filter by USA and choose the latest XAA or USC and use the modified version of Odin. We know this works because thousands of people have used it to do what you are trying to do.
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
JohnAtlas said:
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
Click to expand...
Click to collapse
That's brilliant , glad your up and running.
So the letter "U"after the "G930" denotes the region of the world the device is build to operate in, the Americas just happens to be U. The unbranded firmware is the one that has a region but no network assigned to it, so a 3 letter code is used instead, in your case its USC, or XAA.
Europe is G930"F" or "FD" and the 3 letter code for unbranded is BTU & XEA.
Anyway if your phone is running great on T Mobile then don't update it anymore, turn auto update off. The advantage of keeping it T Mobile is you have the wifi calling, the unbranded firmware needs more fiddling around with the get the wifi calling working on the network your using, so best to stick with what works.
I will have a look for firmware for the J7 you have to see if i can recommend doing something with it to get the wifi calling working.
*update*
So it seems the J727 is the same as the J7 in terms of the internal components, everything is the same in both models so that's great news. I think the "27" bit is just a marketing thing.
In theory you should be able to flash the latest T Mobile Oreo to your device from this link https://www.sammobile.com/firmwares/galaxy-j7-pop/SM-J727T/TMB/download/J727TUVS4BRK1/249137/
Now before we start please check / do the following to avoid further problems.
1. Save everything you need from the phone to your pc.
2. Check that you have OEM unlocked in "developer settings" and "USB debug" enabled.
3. developer setting menu is, settings>about phone>software and information>build number>tap 7 or 8 times, developer menu should now appear. (Sometimes it's somewhere else but build number is what you want to find and tap on 7-8 times).
4. To avoid any issues with device FRP lock, delete your google account off the phone., settings>accounts>google. delete it. When successfully flashed you just add the account again when the phone starts for the first time by signing in.
5. Use the same version of Odin you used to flash your S7.
you can also use updato.com (i think it's slightly faster than sammobile.)
Let me know how you get on.
Remember J727T (TMB) is the firmware you want.
HI all,
With CSC change not possible using codes with latest UI 3.1 update what are options to change CSC?
For ex. I have SM-N986U unlocked Tmobile device but i changed CSC to ATT as im currently using ATT Prepaid and I'm on latest Apr update for ATT
How can i revert back to Tmobile CSC?
Do i need to flash Tmobile firmware using ODIN by first flashing to U1 firmware then Tmobile firmware or can i directly flash Tmobile latest firmware with Apr update using ODIN?
Will i be able to retain my app and data if I flash Tmobile firmware?
Any help will be appreciated.
Thanks
So you state csc change not possible then ask how to change it? lol.. and if it were as easy to just flash firmware in odin tgen that wouldve been the way to do it to begin with I would think lol
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
mindseye0803 said:
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
Click to expand...
Click to collapse
thats the normal process.. that firmware is same for each carrier.. firmware is multi csc which changes based on sim inserted.. shouldnt have to go through all of that really.. i think most ppl who have issues are trying to change csc without a active sim card or on carrier locked devices etc.
glad u figured it out tho!
elliwigy said:
thats the normal process.. that firmware is same for each carrier.. firmware is multi csc which changes based on sim inserted.. shouldnt have to go through all of that really.. i think most ppl who have issues are trying to change csc without a active sim card or on carrier locked devices etc.
glad u figured it out tho!
Click to expand...
Click to collapse
Well, the confusion for most ppl who are new to Samsung and CSC, like me , is that we could change CSC with code earlier and now cannot. Didn't have these issues with pixel and iPhone.
mindseye0803 said:
Well, the confusion for most ppl who are new to Samsung and CSC, like me , is that we could change CSC with code earlier and now cannot. Didn't have these issues with pixel and iPhone.
Click to expand...
Click to collapse
pixel and iphone dont have multi csc like samsung does.. just curious, when were u able to change csc with code earlier if ur new to samsung? lol
elliwigy said:
pixel and iphone dont have multi csc like samsung does.. just curious, when were u able to change csc with code earlier if ur new to samsung? lol
Click to expand...
Click to collapse
Yes, I was able to change CSC to ATT from TMobile, enable all LTE/5G bands before One UI update.Not, sure what u find so funny .
Yes, I'm aware that there is no CSC concept in pixel or iPhone or any other other manufacturer that I'm aware nor they are crippled in terms of hardware capability from carrier software like Samsung. LTE/5G bands not being enabled , esim not being enabled etc.
mindseye0803 said:
Yes, I was able to change CSC to ATT from TMobile, enable all LTE/5G bands before One UI update.Not, sure what u find so funny .
Yes, I'm aware that there is no CSC concept in pixel or iPhone or any other other manufacturer that I'm aware nor they are crippled in terms of hardware capability from carrier software like Samsung. LTE/5G bands not being enabled , esim not being enabled etc.
Click to expand...
Click to collapse
actually other devices are crippled in some cased disabled entirely.. for example u cant get a tmb oneplus 9 pro 5g and use it on verizon to get 5g bcuz vzw 5g bands are disabled in tmb variant..
its really the carriers to be honest..
and I say LOL all the time even in normal convo so not actually laughing sometimes, just say it out of habit
elliwigy said:
actually other devices are crippled in some cased disabled entirely.. for example u cant get a tmb oneplus 9 pro 5g and use it on verizon to get 5g bcuz vzw 5g bands are disabled in tmb variant..
its really the carriers to be honest..
and I say LOL all the time even in normal convo so not actually laughing sometimes, just say it out of habit
Click to expand...
Click to collapse
I have phones such as Z Flip3 5G and other models that do not change CSC like older models when following the flash procedure starting with U1, but the phones never prompt a restart. I have noticed it seems to be with TMB or VZW units. Any suggestion on how to actually get the CSC to change properly or is this something they are doing with new phones to avoid being able to use them fully on other carriers?
yygemmi770 said:
I have phones such as Z Flip3 5G and other models that do not change CSC like older models when following the flash procedure starting with U1, but the phones never prompt a restart. I have noticed it seems to be with TMB or VZW units. Any suggestion on how to actually get the CSC to change properly or is this something they are doing with new phones to avoid being able to use them fully on other carriers?
Click to expand...
Click to collapse
SamKey.org
Go to the page, download theirs Samkey app, buy few credits on Ebay and you can change the CSC as you wish in a minute, the phone will reboot without loosing your data, it's the easiest way as far as I know
Hi, I have yhe following issue and I need your thoughts please.
I have a Telus plan, canadian with US roaming option.
I am traveling in US alot. I have a Note 20 Ultra U1 from Samsung USA. When in US I can only register on Tmobile and I can get 5G icon too. Won't let me on ATT or Verizon.
With same sim card in Note20 Ultra "W" variant, canadian one, it wil register on all 3 major networks in US. No issues with the sim, I guess.
Also in Canada won't get 5G ever.
My provider said nothing to do with them, Samsung told me the same.
I reseted all network setings my APN is ok. VOLTE on. Only getting acces to Tmobile.
Any ideea how I can fix this ? Is it related to CSC ? Mine is XAA.
mindseye0803 said:
Update:
I was able to change CSC(ATT/ATT/TMB) to TMB/TMB/TMB but it was long and winded way. Just flashing firmware was not enough , need Tmobile sim to install carrier service and change CSC.
I followed the steps below:-
1) Did backup of my device using Smart Switch and removed my ATT sim.
2) Flashed latest T-Mobile firmware( N986USQU2DUC8 ) using instructions from post - https://forum.xda-developers.com/t/ota-and-non-ota-firmware-for-n986u-and-n986u1.4143833/ . Also, downloaded the ODIN (patched version) and T-Mobile firmware from links in the post. Flashed HOME_CSC too.
3) After rebooting phone with new firmware , the boot up screen was still ATT and CSC was still ATT/ATT/TMB.
4)Shut down phone and inserted Tmobile SIM i had lying around.
5) On reboot, i was asked to install Tmobile carrier services and on restart , Tmobile logo came on boot up with CSC changed to TMB/TMB/TMB.
6) Now, i have esim enabled and SIM manager showing up too.
Click to expand...
Click to collapse
So I have a Verizon phone and I switched to t-mobile. If I use this method to switch my csc would that lock my phone or would it stay unlocked?
Stevieboy02008 said:
So I have a Verizon phone and I switched to t-mobile. If I use this method to switch my csc would that lock my phone or would it stay unlocked?
Click to expand...
Click to collapse
Unlocked. Phone once unlocked will not lock to any carrier.
dadmi said:
Unlocked. Phone once unlocked will not lock to any carrier.
Click to expand...
Click to collapse
Thank you
I'm using a G930F with stock ROM, on Tmobile, and the January '21 update.
I'm using the UK BTU CSC. Been using this phone since 2018,; the first two years it worked fine, didn't get this error. Tmobile says my SIM card isn't the issue, and their tech support just has me do standard stuff like wiping data etc. Same issue even if I do a full factory reset.
I've noticed sometime nearly a year ago, my G930F started giving me a "Not registered on network" error msg when I tried to make a call, and SMS texts wouldn't go through, but internet was fine.
Toggling airplane mode on/off temporarily fixes this. (the phone will eventually log off so that I have to redo the airplane mode toggle or reboot.
Does anyone know what the issue is?
Is it just only certain G930F users that experience this on tmobile in the US, or is it all users?
Thanks.
I'm having a similar problem on AT&T. I also use a G930F (exynos) S7. Mine is rooted and flashed with LightROM, which is based on stock firmware. CSC is OXM/XEU. As you may know, AT&T is phasing out 3G, and my phone can't make calls in LTE only mode. I've been on chat with their customer service for an hour, and they have no idea why it isn't working. Can someone explain what I need to do to get this phone working?
It's an international version phone, so I wonder if the CSC is incompatible with AT&T. I understand that it is possible (in some cases) to change the CSC code, but I don't know how. The only methods I've found required me to install a stock USA firmware, but I haven't been able to find one. I think I'd need the ATT, XAA, or XAS firmware, but I'm not even sure that the CSC is the problem. But I'd expect the phone's VoLTE/HD voice capabilities to work because it has the stock drivers from Samsung in this ROM.
Ritor said:
I'm using a G930F with stock ROM, on Tmobile, and the January '21 update.
I'm using the UK BTU CSC. Been using this phone since 2018,; the first two years it worked fine, didn't get this error. Tmobile says my SIM card isn't the issue, and their tech support just has me do standard stuff like wiping data etc. Same issue even if I do a full factory reset.
I've noticed sometime nearly a year ago, my G930F started giving me a "Not registered on network" error msg when I tried to make a call, and SMS texts wouldn't go through, but internet was fine.
Toggling airplane mode on/off temporarily fixes this. (the phone will eventually log off so that I have to redo the airplane mode toggle or reboot.
Does anyone know what the issue is?
Is it just only certain G930F users that experience this on tmobile in the US, or is it all users?
Thanks.
Click to expand...
Click to collapse
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Samfirm", and then use it to download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThundeRStormS kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Droiderat said:
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE;; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Sanfirm", and then use it download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThuneRStorM kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Click to expand...
Click to collapse
Will these instructions work for AT&T also? What is the correct site for downloading SamFirm?
Feenix0 said:
Will these instructions work for AT&T also? What is the correct site for downloading SamFirm?
Click to expand...
Click to collapse
They likely will (but I don't use AT&T, so I can't confirm).
Droiderat said:
They likely will (but I don't use AT&T, so I can't confirm). It is SanFirm, not SamFirm. Google is your friend.
Click to expand...
Click to collapse
Thanks! Actually, duckduckgo is my friend , but I only saw results for SamFirm, but there were several different ones and I don't want to use a copycat site that may have tampered with something. I think I'm safer trusting info I get on xda.
Feenix0 said:
Thanks! Actually, duckduckgo is my friend , but I only saw results for SamFirm, but there were several different ones and I don't want to use a copycat site that may have tampered with something. I think I'm safer trusting info I get on xda.
Click to expand...
Click to collapse
DuckDuckGo uses the Microsoft Bing search engine. My version of SamFirm is 0.3.7.1. I don't know which site I got it from.
When I open my SamFirm app, there is now a notice which tells me there is a newer version of the software, called SamUpdate.. See https://kfhost.net/firmware/samupdate I haven't yet tried the new download method, as the SamFirm tool still works.
Droiderat said:
Your problem is a consequence of the T-Mo acquisition of Sprint, and the resulting network reconfiguration which occurred in early 2021. The legacy Sprint bands (25, 26 and 41) do not support voice calls when connected to LTE;; when connected to one of these bands, you must use VoLTE (which is different from LTE-Voice). And, therefore, when connected to one of the these bands, you will see "Not registered on network", although data will still work.
You can verify which bands you are connecting to by using the apps LTE Discovery or Signal Spy.
The solution is to enable the SM-G930F to use VoLTE.
-- Backup the data on your phone (you will lose it)
-- Download the Windows software "Sanfirm", and then use it download the official Samsung ROM for "EVR", and install it using Odin.
-- Install TWRP (I use twrp-3.5.2_9-MoRo-1.6-herolte)
-- I suggest following that by immediately installing the Alexndr ROM: https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/ This is a debloated version of the official ROM, so everything works properly. Be sure to follow the instructions for keeping your CSC (in this case, EVR). Root the phone using Magisk.
-- I suggest using the ThuneRStorM kernel, which is MUCH more stable than the kernel in the Alexndr ROM (the stock kernel reboots randomly; the TS kernel does not).
-- Reinstall your data; reconfigure phone.
-- Download the app IMS Settings to enable VoLTE (you will need to re-implement these settings whenever you reboot).
You will find after doing this that VoLTE (and T-Mo or, in my case, Mint) works perfectly, and you will be able to connect to all of the bands now supported by T-Mo and the SM-G930F without issue.
Click to expand...
Click to collapse
Thanks for the thorough response! I actually used to use the EVR csc in years prior, but switched to BTU due to the EVR bloatware. Does it really make a difference ?
Ritor said:
Thanks for the thorough response! I actually used to use the EVR csc in years prior, but switched to BTU due to the EVR bloatware. Does it really make a difference ?
Click to expand...
Click to collapse
I don't actually know. I researched VoLTE, and the suggestion I found was to use EVR. I didn't try using the IMS Settings app with BTU (my original CSC). I am not aware of any bloatware in EVR, but I immediately overwrote EVR with the Alexndr ROM, retaining only the EVR CSC. So, if EVR had bloatware, I wouldn't know.
I recorded the steps I followed, and I can attest that it works. There may be other solutions.
Droiderat said:
I don't actually know. I researched VoLTE, and the suggestion I found was to use EVR. I didn't try using the IMS Settings app with BTU (my original CSC). I am not aware of any bloatware in EVR, but I immediately overwrote EVR with the Alexndr ROM, retaining only the EVR CSC. So, if EVR had bloatware, I wouldn't know.
I recorded the steps I followed, and I can attest that it works. There may be other solutions.
Click to expand...
Click to collapse
I understand. When I originally bought my G930F, it had a latin american CSC. I first tried EVR from SamMobile, and it came with a bunch of uk carrier specific bloatware. I later installed BTU after reading it was the generic UK csc for non carrier branded phones.
[deleted]
Finally digging into this process now that I have a temp phone.
After Odin failing to flash with either the BTU and EVR, I started writing this post and took a picture of the download mode screen. Contrary to everything I saw in my phone's status and information apps, the download screen showed:
PRODUCT NAME: SM-G930W8
I guess it's no wonder it didn't work!!!!! I'm just glad the flashing TWRP and LightROM for the wrong model didn't ruin my device.
Edit: Turns out that the hardware in these two models is the same, so no surprise it didn't cause trouble.
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
samirski said:
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
Click to expand...
Click to collapse
In theory, flashing the correct firmware (VERIZON) should work. I would honestly first wipe the device, then flash (clean, not dirty) the Verizon firmware and setup accordingly. I had a similar case with a TMBILE unit (I had changed carriers) and I had managed to use XAA CSC and then when I reverted to TMOBILE SIM it would not "restart and install carrier updates". I had to basically switch the unit to U1 and then revert to U and it finally pulled all the TMO crap.
I may be mistaken since I haven't done this type stuff since S10, but I think you need to first reset the device and flash the unlocked version then when you put the verizon sim in it should provision it. Then you can flash the verizon package if you want the bloat apps. The features may be hit or miss. You may need to activate the features on the verizon website. Some features may never work as the carrier wont push them to IMEI not in their database of branded phones. There may be things you can do in hidden settings with "Activity Launcher" or other methods.
I'm here trying to figure out the same things for Tmobile and a factory Unlocked phone, before I buy.
Thanks a lot for your suggestions guys! I managed to do what I wanted. This is what I ended up doing, first flashed the unbranded U1 version on my phone and on the first boot Verizon sim was provisioned. Then I flashed Verizon firmware and it worked!