Related
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...
Hi folks,
I have the following problem. After rooting my SM-G930U (Galaxy S7 unbranded US version, i.e. snapdragon version), it has become super slow and the battery drain insane. So I have decided to revert to stock, not least to be able to update to the latest Android O, which is supposed to be released soon.
However, after downloading several XAA firmware packages (e.g. XAA-G930UUES4BRA1-20180125153850), I have the following problems:
Odin throws an error when I try to flash the firmware and
it might have to do with the fact that the firmware only includes the BL and AP files and not (as I would have hoped) the CSC file as well --> I accidentally flashed the Sprint Rom last time and it sucks, so I want the version with the least carrier customization and bloatware.
So I was hoping that you could help me by explaining whether or not I will need any other files than the BL/AP files and how I can make sure that the rom I install is free from any of the old Sprint customization and bloatware.
Further information: I am on Mint Sim prepaid (which runs on the T-Mobile network) and I have not tripped Knox and I would prefer to keep it this way
Thank you!
For those who aren't already aware, G996U is the model number of all of the US carrier versions of the S21+. The G996U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit the firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=322091
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322092
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to an S21, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
Initial U firmware and AT&T USERDATA are posted, along with U1 firmware. U firmware is not yet accessible in the firmware download tools like SamFirm and Frija, but if anyone wants a different carrier's USERDATA (for flashing bloatware to a U1 device or for converting a U device from one carrier's bloatware to a different one), let me know and I'll get it for you
Are the firmware in OP compatible for the S21 (Non-plus)?
craznazn said:
Are the firmware in OP compatible for the S21 (Non-plus)?
Click to expand...
Click to collapse
This thread is in the S21+ forum, not the S21 forum.
This thread is for model numbers G996U and G996U1, not G991U or G991U1.
If you're looking for S21 firmware, that will be found in the S21 forum
I agree with you
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
3BeersKen said:
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
Click to expand...
Click to collapse
SIM unlock always goes much deeper than firmware. Flashing U1 will never automatically unlock any model - the unlock has to be done separately. If desired, I can provide a recommendation for a professional 3rd party business to do the unlocking, for any interested users who may not meet the carrier's unlock requirement(s).
Thanks. That's what I figured, but wanted to make sure. I like to get off of the AT&T firmware as quickly as possible as you can't get their updates unless you have an active SIM in the phone.
3BeersKen said:
You can't get their updates unless you have an active SIM in the phone.
Click to expand...
Click to collapse
Correct. They're A-holes like that haha
iBowToAndroid said:
Correct. They're A-holes like that haha
Click to expand...
Click to collapse
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
yijinsa said:
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
Click to expand...
Click to collapse
3.14.1 patched
I don't have my S21+ yet but it will be here soon. I ordered from Samsung and selected the Verizon version as unlocked was considerably more expensive.
Does anyone know what Verizon specific bloatware the S21+ has?
Are there certain apps which can be uninstalled with the U1 version but not the Verizon U version?
Are there any potential speed benefits on the 5G network that would be lost using the U1 version, or features like tethering that won't work?
For updates in the future, would they arrive faster on the U1 version, slower, or the same?
My main purpose in flashing from U to U1 is to free up the maximum amount of space of the 128 GB while still retaining 100% of the speed and features I would have with the Verizon version.
Thank you for educating me! It's been a couple years since I flashed my Note 8.
I order a unlocked S21+ U1 version straight from Samsung and didn't have to put in any VZW info.
There is a buttload of Samsung bloatware but no VZW except fot MyVZX
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
iBowToAndroid said:
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
Click to expand...
Click to collapse
You think there will be a fix for this? It's weird that dialer codes also don't work.
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
I've got a T-Mobile locked that I was able to get flashed over to U1 without much trouble. Shows mode number SM-G996U1 now, build number shows same.
edit: Nevermind, I see the TMB/TMB/TMB
krisology said:
You think there will be a fix for this? It's weird that dialer codes also don't work.
Click to expand...
Click to collapse
Dialer codes don't work? On which firmware?
iBowToAndroid said:
Dialer codes don't work? On which firmware?
Click to expand...
Click to collapse
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
krisology said:
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
Click to expand...
Click to collapse
Dialer codes usually don't work on VZW firmware, whether U or U1. But they almost always work on TMB and all others.
Have you tried *#06# ?
I'm not too familiar with this community or android rooting in general but I still want to see what I can do. I want to know more than just the state of rooting, is there a way to unlock the boot loader, is there a way I can remove some (if not all) of the preinstalled spyware and replace it, what can I do to better protect my privacy? I figured I'd check out this community as this is where I was lead when I wanted to root my old Kindle Fire and since this community doesn't just direct to sketchy proprietary tools like kingroot (or maybe you all do, IDK I haven't been here very long). If I could remove alot of the spyware/bloatware I wouldn't be as concerned with rooting or flashing a custom rom as those would be just nice to have if I could get the preinstalled OS to be more privacy focused. I know I can't really escape google since they're embedded right into android but what can I do about Samsung? If I can't do anything on the device I would still like to know if there is a list of domains I could block using a pi-hole. Thanks if anyone has any info, also my phone is from the T-Mobile distribution, I feel like that probably matters.
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
LR7875 said:
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
Click to expand...
Click to collapse
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable
TheXGS said:
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable
Click to expand...
Click to collapse
(Sentence removed for stopping confusion)
Without TWRP, replacing the OS will be impossible.
Maybe downgrade to a older phone that has greater custom ROM support.
LR7875 said:
Too bad, Samsung is bricking every debloated device, which is quite horrible.
Without TWRP, replacing the OS will be impossible.
Maybe downgrade to a older phone that has greater custom ROM support.
Click to expand...
Click to collapse
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm
TheXGS said:
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm
Click to expand...
Click to collapse
Not fully bricked, but it can be semibricked, i.e. not completely working as a mobile phone.
Xiaomi boot loops when certain apps are disabled, which is nasty and needs a factory reset to 'unbrick' it. Not sure about Samsung.
TheXGS said:
The reason I specified replace is that I already tried this and it broke nearly everything, for example:
despite the fact I have a different keyboard, all keyboards broke, I couldn't get the keyboard to show up.
The entire OS became very unstable
Click to expand...
Click to collapse
I think you removed things that shouldn't have been, or you didn't have the alternate app (e.g. keyboard) set as default. If you look at my post history, you can find the debloat list that I posted, which is 100% safe to remove without affecting the usage in any way whatsoever.
More aggressive debloating is possible, sure, but you risk breaking some things. You can always reinstall whatever you removed with "pm install-existing" as long as you used -k when you removed.
TheXGS said:
Wait, de bloating can get the device bricked?
I was able to fix it by just reinstalling everything from pm
Click to expand...
Click to collapse
No , unless your rooted. whatever you debloat while unrooted can be fixed doing Factory Reset
TheXGS said:
I'm not too familiar with this community or android rooting in general but I still want to see what I can do. I want to know more than just the state of rooting, is there a way to unlock the boot loader, is there a way I can remove some (if not all) of the preinstalled spyware and replace it, what can I do to better protect my privacy? I figured I'd check out this community as this is where I was lead when I wanted to root my old Kindle Fire and since this community doesn't just direct to sketchy proprietary tools like kingroot (or maybe you all do, IDK I haven't been here very long). If I could remove alot of the spyware/bloatware I wouldn't be as concerned with rooting or flashing a custom rom as those would be just nice to have if I could get the preinstalled OS to be more privacy focused. I know I can't really escape google since they're embedded right into android but what can I do about Samsung? If I can't do anything on the device I would still like to know if there is a list of domains I could block using a pi-hole. Thanks if anyone has any info, also my phone is from the T-Mobile distribution, I feel like that probably matters.
Click to expand...
Click to collapse
It can be rooted with Magisk V23.0 but you need to unlock the bootloader first.
The bootloader is unlockable up to V3 but this is a paid service.
To get rid of this bloatware i would suggest you flash an unlocked firmware.
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.
tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.3 B3
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A-326U. The base band number will be the 5th to last number in on the About page under baseband.
Click to expand...
Click to collapse
Ill try this out i been using the USC FW no bloatware whatsoever
tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.
Click to expand...
Click to collapse
I...
Don't understand this lingo
can someone explain
tavella said:
You can always flash a SM-A326U1 XXA ROM (https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/) by using a patched version of ODIN 3.13.1 or later. I was able to do this using ODIN 3.1.4 3B
I now have a TMO SM-A326U without any preinstalled TMO bloat. The XAA rom did not install any TMO software that I noticed at a high level and seems like a plan stock A32 5G.
Just make sure the SM-A326U1 baseband is the same version or high than the installed SM-A326U. The base band number will be the 5th to last number in on the About page under baseband.
Edit * I was checking my computer and noticed I had the SM-A326U1 roms for XAA and TMK. I can’t recall if XAA gave me an issue during the flash and I needed to use TMK, but the end result is, my A32 5G has no TMO bloatware installed.
I hope this helps someone.
Click to expand...
Click to collapse
So I can flash a de-bloated version of the version of the OS?
TheXGS said:
So I can flash a de-bloated version of the version of the OS?
Click to expand...
Click to collapse
Yes i just flashed the XAA version and it gives the same bloat ( google bloatware ew ) as the USC version
TheXGS said:
So I can flash a de-bloated version of the version of the OS?
Click to expand...
Click to collapse
Example if the current version your on is A326USQU1AUCF then you can only flash the A326U1UEU1AUF2
TheXGS said:
I...
Don't understand this lingo
can someone explain
Click to expand...
Click to collapse
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.
tavella said:
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.
Click to expand...
Click to collapse
OEM unlock wont appear on the A326U.
The SM-A326U1 XAA & SM-A326U1 USC should be the debranded versions.
The XAA FW causes CSC to revert Whilst the USC doesnt.
Theres is NO XAS FW for this device.
tavella said:
The XAA and TMB are what are referrred to as CSC codes. Each carrier has their own:
ACG – Nextech/C Spire
ATT – AT&T
CCT – Comcast
LRA – Bluegrass Cellular
SPR – Sprint (CDMA)
TFN – Tracfone
TMB – T-Mobile
USC – US Cellular
VMU – Virgin Mobile USA
VZW – Verizon
XAA – USA (unbranded/unlocked/default)
XAS – USA (unbranded/unlocked)
ODIN is software used to flash firmware on to Samsung devices while in Download mode. I believe you need to use a patched version of ODIN to cross flash devices. Regular ODIN will most likely error out during the flashing process.
The SM-A326U is a carrier branded device which is why you will probably not find a ROM with a CSC code of XAA for these devies.
The SM-A326U1 I believe is the carrier unlocked version of the device. Regardless of the CSC you flash, don’t expect to get SM-A326U TMB flashed with the SM-A326U1 XAA firmware to enable OEM Unlock in the Developer Settings. It hasn’t appeared for me and I wouldn’t expect it to.
Please feel free to correct any of my assumptions above. I’m an iPhone guy using this phone with my ASUS router as a failover if my ISP goes down. Just tinkering with it from time to time.
Click to expand...
Click to collapse
So from my understanding:
There is a tool known as ODIN, this can be used to flash new roms
and from what I seem to know
I am most likely running a TMB version of the ROM as it was the default for my phone as it is a TMobile OEM version
So my question is now this:
How can I get a working version of ODIN
Where can I find a safe XAS rom to flash
I don't know if my phone is unlocked, if my phone is still locked to TMobile, could this mess with anything?
I am using SM-A326U not SM-A326U1, I assume the 1 version is unlocked?
TheXGS said:
So from my understanding:
There is a tool known as ODIN, this can be used to flash new roms
and from what I seem to know
I am most likely running a TMB version of the ROM as it was the default for my phone as it is a TMobile OEM version
So my question is now this:
How can I get a working version of ODIN
Where can I find a safe XAS rom to flash
I don't know if my phone is unlocked, if my phone is still locked to TMobile, could this mess with anything?
I am using SM-A326U not SM-A326U1, I assume the 1 version is unlocked?
Click to expand...
Click to collapse
ODIN is the software used to flash ROMS on to Samsung devices. You will want to look for ODIN 3.1.4 3B Patched On the forums or a search engine. The patched version of ODIN will allow you to flash ROMS with different CSC codes. It removes this restriction.
You are correct that the CSC code for your device is TMB. The CSC codes I listed above are some examples, not a complete list. There are no XAS CSC ROMs for this device that I am aware of, just as financeledger stated.
Your Samsung A32 5G is actually the SM-A326U model, but the SM-A326U1 roms also work on these phones, provided you use the patched ODIN. Only the SM-A326U1 has a XAA CSC rom which is bloat free. I have not tried the USC variant but I switched between the SM-A326U TMB and SM-326U1 XAA ROMs and back last night without any issues. You can find the ROMS at Sammobile.com SM-326U1 Roms it will be the third one in the list with the carrier name of Unknown https://www.sammobile.com/samsung/g...M-A326U1/XAA/download/A326U1UEU3AUF2/1558540/
VersionAndroid 11Changelist21672463Build dateThu, 03 Jun 2021 06:20:56 +0000Security Patch Level2021-05-01Product codeXAAPDAA326U1UEU3AUF2CSCA326U1OYM3AUF2
Doing this will not unlock the phone in any way, shape, or form. All this does is provides you with an A32 5G without any carrier bloat. The boot loader still cannot be unlocked and the sim will remain locked until you’ve met T-Mobile’s conditions for unlocking.
I’d recommend on reading up on how to use ODIN properly as you can brick your device if it is not used correctly. Feel free to reply back if you still have questions. I’m not knowledgable enough to understand what financeledger meant when they said the CSC gets reset using the XAA vs USC rom. Hopefully they can provide some additional details regarding that.
Ok
to be sure I get it right:
Here is what I shal do:
1: Download https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
2: Download the XAA ROM for the SM-A326U
3: Flash the ROM with ODIN
4: Hope I don't brick my phone
Is this right?
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!