Related
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?
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
SIGMAxB said:
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
Click to expand...
Click to collapse
Won't flash on T-Mobile - it expects AT&T firmware (SM-G930A) - not anything else. I tried it (SM-G930T) and got error 7 in second stage with that exact reference (expected SM-G930A; got SM-G930T). This would have to be edited to take that second-stage reference out to work.)
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Death Cookie Firmware in Non-DeathStar Phones - Yes; However
SIGMAxB said:
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Click to expand...
Click to collapse
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
PGHammer said:
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
Click to expand...
Click to collapse
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
SIGMAxB said:
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
Click to expand...
Click to collapse
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Beginning of Round Two - CRB6
PGHammer said:
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Click to expand...
Click to collapse
I reset the phone, and kicked off testing of CRB6, and I did one thing differently; I left the SIM in the phone. I had a purpose for that - I was looking for bugbears that apply to non-AT&T carriers (T-Mobile, VZW, Sprint, et. al.) Amusingly, there aren't any. I did the flush (U Firmware version of BRA1) then applied the AT&T version of BQL1 (back-to-back via ODIN). Then came the ADB via SD card single-file updates (recovery mode for these) and there are only two - BQL1 to BRA1 (from Round One) and the new CRB6 update (courtesy of Samsung Firmware Science) labeled update_2.zip. It replaces update.zip, and is not opened or extracted - apply it as-is. After this update applies, follow the new-customer steps as you did for Round One - no changes here.
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
bkup said:
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
Click to expand...
Click to collapse
Can I get a copy please
Why I Did It The Way I Did
SIGMAxB said:
Can I get a copy please
Click to expand...
Click to collapse
When someone gets a proper copy, link it to the thread - the very reason I did NOT do it that way was because a proper copy of AT&T BRA1 didn't exist. (You can't get it from SamMobile or UPDATO either - much to my frustration; the latest ODINable AT&T firmware was BQL1.)
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
finshan said:
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
Click to expand...
Click to collapse
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Youdoofus said:
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Click to expand...
Click to collapse
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
finshan said:
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
Click to expand...
Click to collapse
you cannot go backwards in bootloader revisions, but you can go backwards in android versions as long as theyre on the same BL revision(not likely, but who knows? I didnt look yet). Also, the worst thing that could happen if you try to flash an older BL version is that itll fail in Odin and will still allow the phone to boot normally (usually, and if it doesnt, its still fixable). The only issue with booting it after flashing new firmware with your current sim is that itll install the carrier specific stuff on the phone so long as the CSC needed for that is in the multi CSC pack you flashed on the phone, and if it does install the carrier crap you dont want, just factory reset it and reboot with the actual sim you want you use
no problem man, thats what we are here for
I purchased an "unlocked" S10e off Swappa. It works on my Mint Mobile account just fine. But, it has the ATT carrier branding and bloatware. And, it's stuck at Android 10/October 2020 Security Update/OneUI 2.5.
Can I Odin flash the U1 firmware without causing any problems? It's my understanding that the G970U1 is essentially the same device, but sold by Samsung as SIM unlocked and with no carrier branding/bloatware.
If I download the U1, would I / should I push BL, AP, CP, CSC *and* USERDATA?
Thanks.
dwcasey said:
I purchased an "unlocked" S10e off Swappa. It works on my Mint Mobile account just fine. But, it has the ATT carrier branding and bloatware. And, it's stuck at Android 10/October 2020 Security Update/OneUI 2.5.
Can I Odin flash the U1 firmware without causing any problems? It's my understanding that the G970U1 is essentially the same device, but sold by Samsung as SIM unlocked and with no carrier branding/bloatware.
If I download the U1, would I / should I push BL, AP, CP, CSC *and* USERDATA?
Thanks.
Click to expand...
Click to collapse
I ended up using the Samsung Firmware downloader from here
Samsung Firmware Downloader is a free cross-platform tool to download software updates for Galaxy devices
Looking to download software updates for your Samsung Galaxy device? Check out Samsung Firmware Downloader - it's free and open source!
www.xda-developers.com
Pulled down the latest G970U1 with region XAA. It handled the decryption.
But reading folks having issues going from a U to U1, vice versa, or separate carriers, I found this and downloaded the latest version (originally found linked from here https://forum.xda-developers.com/t/...-cant-flash-u1-with-odin-etc-att-s21.4238775/)
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I then extracted the five files and pulled them into the patcheD Odin. Powered off the phone. Started download mode (down vol+bixby button) and plugged in. Odin saw the phone, I clicked start and it finished in only a few minutes.
Is U1s bootloader locked like the u Version?
What about the Canada W?
dwcasey said:
I ended up using the Samsung Firmware downloader from here
Samsung Firmware Downloader is a free cross-platform tool to download software updates for Galaxy devices
Looking to download software updates for your Samsung Galaxy device? Check out Samsung Firmware Downloader - it's free and open source!
www.xda-developers.com
Pulled down the latest G970U1 with region XAA. It handled the decryption.
But reading folks having issues going from a U to U1, vice versa, or separate carriers, I found this and downloaded the latest version (originally found linked from here https://forum.xda-developers.com/t/...-cant-flash-u1-with-odin-etc-att-s21.4238775/)
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I then extracted the five files and pulled them into the patcheD Odin. Powered off the phone. Started download mode (down vol+bixby button) and plugged in. Odin saw the phone, I clicked start and it finished in only a few minutes.
Click to expand...
Click to collapse
Can we get an update? How did it turn out? Were you able to get OTA updates? Everything work okay?
I might try this at the library tomorrow. Downloading firmware really sucks without wifi.
supertac said:
Is U1s bootloader locked like the u Version?
What about the Canada W?
Click to expand...
Click to collapse
I don't believe this process provides an unlocked bootloader.
Nooblet1001 said:
Can we get an update? How did it turn out? Were you able to get OTA updates? Everything work okay?
I might try this at the library tomorrow. Downloading firmware really sucks without wifi.
Click to expand...
Click to collapse
A little scary process, but overall I'm happy and have had great success. I've received two monthly Security updates since flashing. All the branding/bloat is gone (well, still have Samsung bloat, but that is easily dealt with).
dwcasey said:
A little scary process, but overall I'm happy and have had great success. I've received two monthly Security updates since flashing. All the branding/bloat is gone (well, still have Samsung bloat, but that is easily dealt with).
Click to expand...
Click to collapse
IT WORKED!!! I can't believe it worked first try! Thank you so much for putting the guide out there, I'm so happy. Thanks a ton! You're awesome.
I have a mexican TCE type Eyxnos... I switch switching the firmware- the reception got weak if I switched it away from the TCE brand...so I had to switch back
lame
I have bought myself an s10e 256 GB from the US and i am stuck on Android 10 June 2020. ATT wont give me any Updates because i am i Germany and do not have an ATT sim card.
The phone is unlocked as my german sim works fine.
I have ATT bloatware on there ....
The phone tells me i am on TE8
SmartSwitch tells me it has the latest FW
So can someone point me to a newbie description how to to Flash Android 11 onto it.
Never done this before. Never rooted but jailbroken all my iPhones. Android is comlicated in this regard.
Thx
This is so effn confusing... samloader does not work.
freija has no firmware
Sammobile has 2 devices u and u1
Multiple firmwares to choose from ....
I am about to ditch samsung 4 good....
Figured it out and its working now XAA from the G970U1
dwcasey said:
I ended up using the Samsung Firmware downloader from here
Samsung Firmware Downloader is a free cross-platform tool to download software updates for Galaxy devices
Looking to download software updates for your Samsung Galaxy device? Check out Samsung Firmware Downloader - it's free and open source!
www.xda-developers.com
Pulled down the latest G970U1 with region XAA. It handled the decryption.
But reading folks having issues going from a U to U1, vice versa, or separate carriers, I found this and downloaded the latest version (originally found linked from here https://forum.xda-developers.com/t/...-cant-flash-u1-with-odin-etc-att-s21.4238775/)
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I then extracted the five files and pulled them into the patcheD Odin. Powered off the phone. Started download mode (down vol+bixby button) and plugged in. Odin saw the phone, I clicked start and it finished in only a few minutes.
Click to expand...
Click to collapse
hey, im using g970u from verizon, and im using it indonesia far from usa and it work with my carrier. But i want to change the firmware with the g970u1 for fast update and latest security patch. i Downloded the VZW g970u1 and trying to flashing with odin 3.14.4, 3.14.1, 3.13.1 (including Patched version) but nothing is work, it stuck at setup connection and ended up with fail. How i solve this? many thanks
Excellent share! I purchased an s10e snapdragon unlocked version SM-G970U.
The service provider/Carrier version was ATT/XAA/ATT.
It had all the AT&T bloatware, but my simcard worked fine in the phone (I am based in India)
Furthermore, it had Android 11 and I was not able to upgrade to 12 as it kept saying "phone is up to date" whenever I searched for new updates.
It also dint have that mobile data toggle switch in the drop down task bar.
I followed all the steps in the second post of this thread and I was able to upgrade it to Android 12!
Now the service provider/Carrier version shows as = XAA/XAA/ATT (SM-G970U1). All the ATT bloatware is gone and the mobile data toggle switch is now visible in the drop down task bar. My simcard works fine too!
Good stuff. Thank you @dwcasey .
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?