General Variants - Samsung Galaxy A32 5G

SM-A326BSaudi ArabiaSM-A326B/DSSaudi Arabia/ Dual SIMSM-A326BRHong KongSM-A326BR/DSHong Kong / Dual SIMSM-A326UT-Mobile (US), Sprint, MetroPCS, CricketSM-A326U1US UnlockedSM-A326WCanada

I got the SM-A326B/DS in EU too.

Anyone know differences in network bands? Got T-mobile to unlock my A326U, will it work on VZW?

trix4rix said:
Anyone know differences in network bands? Got T-mobile to unlock my A326U, will it work on VZW?
Click to expand...
Click to collapse
Can you get the bootloader partition and post? It might be able to work.. I'll test on A326W
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com

Related

[DEV] - A call for all devs: help to add dual SIM support on ROMs

I know that the Moto G is a recent phone, and because of this, we don't have much devs working on ROMs or something. But I follow all topics on the Android Development section and I observed one thing: almost nothing released yet (like alternative ROMs or the US update to Kit Kat) is compatible with the dual SIM variant of the phone.
I know that this variation won't be sold in a lot of markets, but here in Brazil, we almost encounter only the dual SIM version on the local and online stores. 'Cause here, dual SIM phones are really popular and necessary (let's say that our network operators isn't that good).
So, let's talk about what cares: I'm here to request to you guys to support the dual SIM on your ROMs. I know that is easy to do a request like these... so, I'm here to help and test together with the devs. I think it's important to develop a way to include the Dual SIM support on the future ROMs. So, everyone with a Moto G will be able to install the ROMs, independent of the variant of your phone.
My phone is a brazilian XT1033 16GB Dual Sim, with stock Android 4.3, unlocked bootloader, root and ClockworkMod Recovery running fine.
I installed the Infusion ROM, the Kit Kat repack and the Kit Kat US Stock ROM (yeah, I'm hungry for Kit Kat) and the results are the same: only one SIM are showed on the notification bar and we can't get any signal from the operator. Otherwise, everything works fine: wifi, apps, the general system...
You guys can ask me anything about the phone or give me instructions to extract certain files from system that you need or commands on adb/fastboot to get details of this variant. Remember: I'm here to help. :good:
marcuzvolk said:
I know that the Moto G is a recent phone, and because of this, we don't have much devs working on ROMs or something. But I follow all topics on the Android Development section and I observed one thing: almost nothing released yet (like alternative ROMs or the US update to Kit Kat) is compatible with the dual SIM variant of the phone.
I know that this variation won't be sold in a lot of markets, but here in Brazil, we almost encounter only the dual SIM version on the local and online stores. 'Cause here, dual SIM phones are really popular and necessary (let's say that our network operators isn't that good).
So, let's talk about what cares: I'm here to request to you guys to support the dual SIM on your ROMs. I know that is easy to do a request like these... so, I'm here to help and test together with the devs. I think it's important to develop a way to include the Dual SIM support on the future ROMs. So, everyone with a Moto G will be able to install the ROMs, independent of the variant of your phone.
My phone is a brazilian XT1033 16GB Dual Sim, with stock Android 4.3, unlocked bootloader, root and ClockworkMod Recovery running fine.
I installed the Infusion ROM, the Kit Kat repack and the Kit Kat US Stock ROM (yeah, I'm hungry for Kit Kat) and the results are the same: only one SIM are showed on the notification bar and we can't get any signal from the operator. Otherwise, everything works fine: wifi, apps, the general system...
You guys can ask me anything about the phone or give me instructions to extract certain files from system that you need or commands on adb/fastboot to get details of this variant. Remember: I'm here to help. :good:
Click to expand...
Click to collapse
I believe that for KitKat you'll have to wait for Motorola Brazil to release the update.
OP, can you pull me some things from the stock brazil 4.3 rom?
i need
system/vendor/lib/libril-qc-qmi-1.so
system/lib/libreference-ril.so
also what happens when you flash the GSM US 4.4 factory image ? does data still not work?
http://www.modaco.com/topic/367402-...lobal-gsm-442-rom-to-your-unlocked-uk-device/
tillaz said:
OP, can you pull me some things from the stock brazil 4.3 rom?
i need
system/vendor/lib/libril-qc-qmi-1.so
system/lib/libreference-ril.so
also what happens when you flash the GSM US 4.4 factory image ? does data still not work?
http://www.modaco.com/topic/367402-...lobal-gsm-442-rom-to-your-unlocked-uk-device/
Click to expand...
Click to collapse
Of course! Attached to my reply.
When I flash the 4.4 factory image, I get the same issue: one SIM showed on the notification bar, without data/signal.
tillaz said:
OP, can you pull me some things from the stock brazil 4.3 rom?
i need
system/vendor/lib/libril-qc-qmi-1.so
system/lib/libreference-ril.so
also what happens when you flash the GSM US 4.4 factory image ? does data still not work?
http://www.modaco.com/topic/367402-...lobal-gsm-442-rom-to-your-unlocked-uk-device/
Click to expand...
Click to collapse
I've also got the very same model as well, initionally I thought like oh ok imma just flash 4.4 US retail with modem files from stock Brazilian firmware but what seem pretty straightforward turned out the total opposite way when it comes to carrier signal. Do those files you requested have anything to do with radio?
I am on "Oi" and it's based on GSM network.
actually i need a few more
system/vendor/lib/libril-qc-qmi-1.so
system/vendor/lib/libril-qcril-hook-oem.so
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilutils.so
system/bin/rild
system/bin/pppd
system/etc/ppp/ip-up-vpn
system/etc/apns-conf
system/etc/permissions/android.hardware.telephony.gsm
and the boot.img
tillaz said:
actually i need a few more
system/vendor/lib/libril-qc-qmi-1.so
system/vendor/lib/libril-qcril-hook-oem.so
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilutils.so
system/bin/rild
system/bin/pppd
system/etc/ppp/ip-up-vpn
system/etc/apns-conf
system/etc/permissions/android.hardware.telephony.gsm
and the boot.img
Click to expand...
Click to collapse
You know what?
It's better if you have access to the entire system folder so there it is.
https://drive.google.com/file/d/0ByxU3I4dCrUrS2lKWGg0NUNESDg/edit?usp=sharing
Enjoy.
tillaz said:
actually i need a few more
system/vendor/lib/libril-qc-qmi-1.so
system/vendor/lib/libril-qcril-hook-oem.so
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilutils.so
system/bin/rild
system/bin/pppd
system/etc/ppp/ip-up-vpn
system/etc/apns-conf
system/etc/permissions/android.hardware.telephony.gsm
and the boot.img
Click to expand...
Click to collapse
Requested files attached.
The problem with dual sim is that today Android does not support dual sim! Each Dual sim phone use a propriatary software to use dual sim. Maybe we can"hack" the software in order to make your phone a singlesim, but it will be very difficult to support dualsim phones... For your information, CyanogenMod does not support any dual sim phone...
Sorry...
SouSoulebarbu said:
For your information, CyanogenMod does not support any dual sim phone...
Sorry...
Click to expand...
Click to collapse
THAT is more a result of most dual SIM phones being based on MTK SOCs for which no sources are available (similar story for other Chinese SOCs, BTW, but MTK is the worst offender)...
Dual sim support isn't critical, I suppose most of Dualsim owners would be happy with at least one sim working properly.
nupi said:
THAT is more a result of most dual SIM phones being based on MTK SOCs for which no sources are available (similar story for other Chinese SOCs, BTW, but MTK is the worst offender)...
Click to expand...
Click to collapse
Considering that the new Motorola is more "open" and friendly for the devs now, maybe we can ask they for release the dual sim specific sources...
Doublepranks said:
Dual sim support isn't critical, I suppose most of Dualsim owners would be happy with at least one sim working properly.
Click to expand...
Click to collapse
No way. If someone buys a dual sim phone, It's supposed to have both working fine.
Like I said, to me is totally indispensable: I have one SIM from a local operator, to make calls (with this SIM, local calls are REALLY cheap) and another, with a unlimited data plan (that I use on university to connect my laptop to the Internet).
I'm just and simply saying it's better have one than no Simcard working at all I don't know about you but I'm looking foreword to get Cyanogenmod and as been said before there's no dualSim sources available and highly doubt there will ever be.
Well I only using 1 Sim right now, but my mom bought me the dual SIM, she didn't even think about that, and I think is the only only she founds.
If at least one works, is definitely better then no one working, like KitKat is right now for me.
can you post output of thi command
adb shell
su
getprop ro.baseband
thanks
vocoderism said:
can you post output of thi command
adb shell
su
getprop ro.baseband
thanks
Click to expand...
Click to collapse
The output was:
getprop ro.baseband
msm
Verify init.MMI.radio.sh in /
Inviato dal mio XT1034 utilizzando Tapatalk
Try this
execute nandroid backup from recovery cwm or twrp
reboot
set on build.prop in /system this to parameters
ro.boot.radio=0x5
persist.radio.multisim.config=dsds
persist.dsds.enabled=true
ro.multi.rild=true
reboot and verify
:crying:
vocoderism said:
Try this
execute nandroid backup from recovery cwm or twrp
reboot
set on build.prop in /system this to parameters
ro.boot.radio=0x5
persist.radio.multisim.config=dsds
persist.dsds.enabled=true
ro.multi.rild=true
reboot and verify
:crying:
Click to expand...
Click to collapse
Should I install US global kitkat repack before trying this method?

Convert SM-G930T to SM-G930A so I can use AT&T LTE bands.

Hi All, I want to continue using my AT&T prepaid plan but I recently bought a locked T-Mobile Galaxy S7 SM-G930T (I'm going to try to unlock it - if that doesn't work this is all moot). I would like to flash AT&T firmware so I can use the AT&T LTE bands. Can I follow the instructions in the link below once I've unlocked a T-Mobile SM-G930T and turn it into a SM-G930A?
http://www.droidviews.com/nougat-firmware-on-att-galaxy-s7s7-edge-sm-g930a-g935a/
I've read the link below... but it seems to be only if you want to continue using T-Mobile service which I don't.
https://forum.xda-developers.com/tm...w-to-flash-att-nougat-to-t-mobile-s7-t3553610
Changing firmware doesn't have anything to do with what bands the hardware supports. Unlock it and throw the ATT SIM in. Only difference is carrier supported features and software (wifi calling, etc). Flashing ATT modem might improve coverage but all S7 support the same bands.
Thanks buddy for the reply. I'm used to using a custom ROM on my Android phones so this is new. Mostly CyanogenMod.
That's good to know I don't need to flash in order to get the bands but I understand I need to if I want OTA updates from at&t. It seems relatively simple that you just flash the AT&T ROM over the T-Mobile with Odin and then use some update file. It doesn't even effect Samsung pay and Knox which is great.
Stupid question: is the AT&T modem included with the AT&T rom? Also, with regards to the 2nd link in the OP what is the update file that you put on the sdcard to use in recovery - is that an OTA update because your ROM is different from your carrier?
madadhd said:
Thanks buddy for the reply. I'm used to using a custom ROM on my Android phones so this is new. Mostly CyanogenMod.
That's good to know I don't need to flash in order to get the bands but I understand I need to if I want OTA updates from at&t. It seems relatively simple that you just flash the AT&T ROM over the T-Mobile with Odin and then use some update file. It doesn't even effect Samsung pay and Knox which is great.
Stupid question: is the AT&T modem included with the AT&T rom? Also, with regards to the 2nd link in the OP what is the update file that you put on the sdcard to use in recovery - is that an OTA update because your ROM is different from your carrier?
Click to expand...
Click to collapse
The following is the latest G930A Android 7.0 firmware file. All you need to do is flash it with Odin's AP slot to completely convert your G930T to a G930A. No other steps or files are required: G930AUCS4BQC2_CL10280464_QB12904132_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
EDIT: Corrected the linked file
muniz_ri said:
The following is the latest G930A Android 7.0 firmware file. All you need to do is flash it with Odin's AP slot to completely convert your G930T to a G930A. No other steps or files are required: G930AUCS4BQC2_CL10280464_QB12904132_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
EDIT: Corrected the linked file
Click to expand...
Click to collapse
i have METROPCS Phone SM-G930T1 Nougat, already unlocked since i live in mexico...is there a international rom to flash?? i wanna convert my s7 to a non carrier rom IN ADVANCE THANKS 4 YOUR HELP!
muniz_ri said:
The following is the latest G930A Android 7.0 firmware file. All you need to do is flash it with Odin's AP slot to completely convert your G930T to a G930A. No other steps or files are required: G930AUCS4BQC2_CL10280464_QB12904132_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
EDIT: Corrected the linked file
Click to expand...
Click to collapse
I don't get why you would do this other than to have ATT bloat over TMO bloat (IMHO TMO has less bloat than ATT). There's no technical advantage. Am I missing something?
A0425A said:
I don't get why you would do this other than to have ATT bloat over TMO bloat (IMHO TMO has less bloat than ATT). There's no technical advantage. Am I missing something?
Click to expand...
Click to collapse
The amount of bloatware is irrelevant since you can freeze all bloatware on either build. I experienced many issues on the TMo version including issues with Android Auto, Google Assistant, and Tasker. I thought these apps were buggy but all of those issues were resolved on the AT&T version. The AT&T version seems to be a better, bug-free build.
muniz_ri said:
The amount of bloatware is irrelevant since you can freeze all bloatware on either build. I experienced many issues on the TMo version including issues with Android Auto, Google Assistant, and Tasker. I thought these apps were buggy but all of those issues were resolved on the AT&T version. The AT&T version seems to be a better, bug-free build.
Click to expand...
Click to collapse
Read that in a different thread you posted to after I responded. I think it's very YMMV though. But if you saw improvement then ??
Hi, did anyone ever complete this flash from SM-G930T to SM-G930A? I'd like to do this solely to try and get the wifi calling feature since my workplace has poor cell service but great wifi. I bought the T-Mobile phone, unlocked it, put the ATT sim in and everything but wifi calling works fine. I appreciate the reply!
This is much later in the year (11-8-2021) and ATT has posted the list of phone they say will work and it only shows G930A. It seems their test of working means it must have been sold by ATT. They say My G930T won't work. So Will ATT continue to use customer's unlocked phones it they were not orginally sold by ATT. They have the records. Will ATT refuse to use one of their SIMs even if the phone is Flashed to ATT logo. I do not want to throw away my G930T phone.
muniz_ri said:
The following is the latest G930A Android 7.0 firmware file. All you need to do is flash it with Odin's AP slot to completely convert your G930T to a G930A. No other steps or files are required: G930AUCS4BQC2_CL10280464_QB12904132_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
EDIT: Corrected the linked file
Click to expand...
Click to collapse
Hello and thank you. You posted this information and link back in 2017 and so much has changed. Mostly ATT is now working hard to get rid of all 3G towers and firing up 5G. They said my Galaxy S7-GM930T would not work so I think they link you posted will help me convert the phone back to a GM930A or U or U1. My question is,..Has anything in your post changed since 2017 and if so could you please advise me of what I need to do. Thanks very much.
trigger1937 said:
Hello and thank you. You posted this information and link back in 2017 and so much has changed. Mostly ATT is now working hard to get rid of all 3G towers and firing up 5G. They said my Galaxy S7-GM930T would not work so I think they link you posted will help me convert the phone back to a GM930A or U or U1. My question is,..Has anything in your post changed since 2017 and if so could you please advise me of what I need to do. Thanks very much.
Click to expand...
Click to collapse
They sent you a message saying the phone won't work?

Links for AT&T and Cricket USERDATAs

I know these are much tougher to find - can't be obtained from SamFirm or SamMobile. So I'll be uploading one for each carrier, for each bootloader version. Firmware is universal on U models so you can use the other 4 files from any other matching collection. Can probably even mix and match builds, if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
You'll need 7-zip to extract.
https://www.androidfilehost.com/?w=files&flid=283166
SC1 USERDATA was added a few days ago, for anyone wanting to jump to Pie
ATT USERDATA added for bootloader 6
bootloader 6 userdata
Sorry if I am posting in the wrong spot I am new to this forum but I was wondering if someone can extract AT&T userdata for Odin Product code ATT
PDA G950U1UES6DSG1
CSC G950U1OYM6DSG1
I had it for 5 and didn't realize that this upgrade was 6. I need my wifi calling because I am in the hospital a lot and don't have reception. Please help I would really appreciate it!
Jaldrich1992 said:
Sorry if I am posting in the wrong spot I am new to this forum but I was wondering if someone can extract AT&T userdata for Odin Product code ATT
PDA G950U1UES6DSG1
CSC G950U1OYM6DSG1
I had it for 5 and didn't realize that this upgrade was 6. I need my wifi calling because I am in the hospital a lot and don't have reception. Please help I would really appreciate it!
Click to expand...
Click to collapse
USERDATA only applies to U firmware, not to U1. If you don't have wifi calling while on U1 firmware, then you need to change to U firmware, with all of your carrier's bloatware
Cricket USERDATA added for bootloader 6
iBowToAndroid said:
ATT USERDATA added for bootloader 6
Click to expand...
Click to collapse
Thanks! I am not on AT&T but used this to enable future OTA upgrades. Other than the bloat (expected), it worked well.
rexian said:
Thanks! I am not on AT&T but used this to enable future OTA upgrades. Other than the bloat (expected), it worked well.
Click to expand...
Click to collapse
AT&T puts blocks in their firmware so that OTAs don't work if you're not using AT&T service - even if it's one of their own MVNOs. So if you're not an AT&T customer, you do NOT want to be on their firmware
What are the restrictions on userdata? I assume that the userdata should much the security level? Is there any other restriction
prince_72 said:
What are the restrictions on userdata? I assume that the userdata should much the security level? Is there any other restriction
Click to expand...
Click to collapse
It at least has to match the bootloader version. YMMV if the USERDATA isn't the exact same build as the base files
Sorry if this is a stupid question, but I have a SM-G950U1 (unlocked Galaxy S8). Can I use this to flash it to make it a SM-950U (ATT locked Galaxy S8)? I want to get the official ATT firmware to be able to use Wi-Fi calling and other ATT features.
chuckguy17 said:
Sorry if this is a stupid question, but I have a SM-G950U1 (unlocked Galaxy S8). Can I use this to flash it to make it a SM-950U (ATT locked Galaxy S8)? I want to get the official ATT firmware to be able to use Wi-Fi calling and other ATT features.
Click to expand...
Click to collapse
It won't SIM lock it. And you won't get wifi calling. But you'll get most of the rest of their features
iBowToAndroid said:
It won't SIM lock it. And you won't get wifi calling. But you'll get most of the rest of their features
Click to expand...
Click to collapse
By chance you don't know where I can find a rev 7 for cricket. Our a user data at least?
TheMadScientist said:
By chance you don't know where I can find a rev 7 for cricket. Our a user data at least?
Click to expand...
Click to collapse
Hasn't been released yet. T-Mo and Metro are the only ones who have actually gotten a rev 7 OTA so far. But i'll definitely post them when I get access to them.
I did just notice that I had never uploaded the rev 6 Cricket USERDATA, so that is done now
iBowToAndroid said:
Hasn't been released yet. T-Mo and Metro are the only ones who have actually gotten a rev 7 OTA so far. But i'll definitely post them when I get access to them.
I did just notice that I had never uploaded the rev 6 Cricket USERDATA, so that is done now
Click to expand...
Click to collapse
That's weird. I'm on revision 7 and supposedly on aio
I'm trying to get my wifi calling to work. Cricket says it will even on byod after like blq1 or some oreo firmware. On the u model. All I found was a u1
https://www.reddit.com/r/CricketWir..._source=amp&utm_medium=&utm_content=post_body
TheMadScientist said:
That's weird. I'm on revision 7 and supposedly on aio
I'm trying to get my wifi calling to work. Cricket says it will even on byod after like blq1 or some oreo firmware. On the u model. All I found was a u1
Click to expand...
Click to collapse
U1 has gotten rev 7, yes. When I said that "T-Mo and Metro are the only ones" that have gotten it, I was referring to the carriers themselves, which is U firmware.
iBowToAndroid said:
U1 has gotten rev 7, yes. When I said that "T-Mo and Metro are the only ones" that have gotten it, I was referring to the carriers themselves, which is U firmware.
Click to expand...
Click to collapse
I never could find a u firmware for cricket. I only assumed u1 existed
TheMadScientist said:
I never could find a u firmware for cricket. I only assumed u1 existed
Click to expand...
Click to collapse
Well firmware is universal - there is no such thing as "Cricket firmware". But there are Cricket USERDATAs, yes. Only thing is that their S8 hasn't gotten the rev 7 OTA yet, so the Odin files haven't been published yet either
iBowToAndroid said:
Well firmware is universal - there is no such thing as "Cricket firmware". But there are Cricket USERDATAs, yes. Only thing is that their S8 hasn't gotten the rev 7 OTA yet, so the Odin files haven't been published yet either
Click to expand...
Click to collapse
Dont know if the rev 7 is out yet do ya?
TheMadScientist said:
Dont know if the rev 7 is out yet do ya?
Click to expand...
Click to collapse
No, no rev 7 update for the AT&T or Cricket models yet

General G996U and G996U1 Firmware Links and Flashing Discussion Here

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# ?

Question Any chance that a phone like this can get aosp?

I'm trying to use this phone for its 5g modem for tethering but since it comes with a T-mobile rom I think it phones home when tethering is enabled. The usual iptable mangle in openwrt doesnt work.
I'm wanting to do the same. Haven't gotten the phone yet.
Can Magisk be installed? Or are Samsung's Locked down these days? Then you could just use the prop config to add the tethering line.
gullzway said:
I'm wanting to do the same. Haven't gotten the phone yet.
Can Magisk be installed? Or are Samsung's Locked down these days? Then you could just use the prop config to add the tethering line.
Click to expand...
Click to collapse
Knox is active, also T-Mobile disabled OEM Unlocking.
IceNova said:
I'm trying to use this phone for its 5g modem for tethering but since it comes with a T-mobile rom I think it phones home when tethering is enabled. The usual iptable mangle in openwrt doesnt work.
Click to expand...
Click to collapse
Unfortunatly, this variant has been extra locked down by T-Mobile so it cant be rooted. T-Mobile branded phones are know for having extra security measures that make it even harder to root or flash the phone.
omega552003 said:
Knox is active, also T-Mobile disabled OEM Unlocking.
Unfortunatly, this variant has been extra locked down by T-Mobile so it cant be rooted. T-Mobile branded phones are know for having extra security measures that make it even harder to root or flash the phone.
Click to expand...
Click to collapse
Is this a Tmobile branded phone? They are offering this model for 'free' but it doesn't appear to be branded like Revvl. But maybe it is...
xenokc said:
Is this a Tmobile branded phone? They are offering this model for 'free' but it doesn't appear to be branded like Revvl. But maybe it is...
Click to expand...
Click to collapse
Branded as in Software
It will never happen
US Samsh*t bootloader is completely dead locked
what about other variants? can they be rooted? unlocked?
nikosrs4 said:
what about other variants? can they be rooted? unlocked?
Click to expand...
Click to collapse
ALL US variants are dead locked
I honestly don't know. The fact that this is not a snapdragon phone makes it a better candidate than other U.S. Samsungs.
If we can get it unlocked and rooted... I'd love to help development of AOSP for it.
xenokc said:
Is this a Tmobile branded phone? They are offering this model for 'free' but it doesn't appear to be branded like Revvl. But maybe it is...
Click to expand...
Click to collapse
You might be able to try the combo Firmware I posted, or if that doesn't work another us carrier Firmware
I would recommend downloading with Frija and flashing with Odin3B modded (lastest version)
TypicalGellert said:
You might be able to try the combo Firmware I posted, or if that doesn't work another us carrier Firmware
I would recommend downloading with Frija and flashing with Odin3B modded (lastest version)
Click to expand...
Click to collapse
I tried to no success
I've managed to build PithBlack CWM recovery as well as AOSP Android R/11 today using extracted OTA kernel, but I'm not going to post it just yet, since this is first build that I've technically done "on my own" I want to find someone knowlageable to look through my out images and sources that I've used to build them.
Edit: Also, I'm pretty sure A326U/A326U1 will need new build.
NetBos said:
I've managed to build PithBlack CWM recovery as well as AOSP Android R/11 today using extracted OTA kernel, but I'm not going to post it just yet, since this is first build that I've technically done "on my own" I want to find someone knowlageable to look through my out images and sources that I've used to build them.
Edit: Also, I'm pretty sure A326U/A326U1 will need new build.
Click to expand...
Click to collapse
Im interessted in this! If you need testers let me know, only thing i need is recovery as it seems the recovery thread here is for the "U" varient and mine is A326B (Nordic), but i am rooted with magisk.

Categories

Resources