Question The current state of this device in the community - Samsung Galaxy A32 5G

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?

Related

How to enable VoLTE on SM-G930F?

I was wondering if it's possible to enable VoLTE on an SM-G930F running BTU firmware on an AT&T carrier. Is there any way to get things like WiFi Calling and VoLTE on it, or am I just screwed since I'm using the international variant of the phone?
When I first got it brand new from Wal-Mart, it was running TTT firmware (from Trinidad and Tobago for some reason) and showed normal 3G, 4G, and LTE symbols on my status bar. Since I wanted to get the Nougat update early, I flashed BTU which switched the symbols to H, H+, and 4G. Does that have anything to do with it?
Thanks.
You're certain it's a G930F? And from Walmart of all places? Exynos isn't meant to be sold in the US.
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
If it's a US snapdragon model you could flash the AT&T CSC via Odin without needing TWRP.
Beanvee7 said:
You're certain it's a G930F? And from Walmart of all places? Exynos isn't meant to be sold in the US.
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
If it's a US snapdragon model you could flash the AT&T CSC via Odin without needing TWRP.
Click to expand...
Click to collapse
If OP successfully flashed BTU then it has to be a Exynos G930F, but I agree, most phones sold in the US claiming to be the G930F are modded Snapdragons faked to look like it, but they obviously won't allow a Exynos ROM to be flashed to them, so in this case OP has got a real Exynos
Could be the modem (CP) part of the firmware controlling which carrier services you can receive in your region, not sure I'd recommend flashing a US modem to a UK firmware though, unsure what would happen, although the G930F is pretty straight forward to unbrick as long as you can get back into download mode
Beanvee7 said:
If it's a G930F and you have TWRP you can flash the CSC tool in the development section which has the US carriers, and CSC is what enables VoLTE.
Click to expand...
Click to collapse
Where is this CSC tool? I'm not sure what you mean by "development section". I have an Oreo G930F and I'm trying to get VoLTE to work with AT&T.
Feenix0 said:
Where is this CSC tool? I'm not sure what you mean by "development section". I have an Oreo G930F and I'm trying to get VoLTE to work with AT&T.
Click to expand...
Click to collapse
It hasn't been updated with the newer versions of Android so it's not really a thing anymore.
Next best thing is to download the entire firmware package for your carrier from somewhere like updato then flash only the home_CSC file. Although iirc this might now work if mixing and matching models, which is why the CSC flash tool was a thing.
Beanvee7 said:
It hasn't been updated with the newer versions of Android so it's not really a thing anymore.
Next best thing is to download the entire firmware package for your carrier from somewhere like updato then flash only the home_CSC file. Although iirc this might now work if mixing and matching models, which is why the CSC flash tool was a thing.
Click to expand...
Click to collapse
The trouble is that the G930F was never officially released on US markets, so I can't find a US firmware. I'd gladly use another market's firmware if I knew it would support AT&T VoLTE and "LTE only" mode, but I have no idea how to figure that out!
So it turns out that I have the Canadian SM-G930W8 (as shown on the download mode screen), not the G930F (as shown everywhere else). Identical hardware, but I can only flash Canadian firmware.

At&t branded phones on Tmobile network

My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
JohnAtlas said:
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
Click to expand...
Click to collapse
If your current firmware has WiFi calling (Volte) You can only use Volte if the network supports it. There are however many apps you can use for WiFi calling look on the play store.
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
JohnAtlas said:
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
Click to expand...
Click to collapse
Volte is wi fi calling over a network which the network operator supports without the need for a specific app.
Please tell me exactly what you are trying to do
What network are both phones using?
Which networks were the phones on initially?
Have you modified the phones in any way? Root? or TWRP?
What firmware are both phones currently using? Go to Settings>about phone>software information>baseband version G930A????
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
JohnAtlas said:
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
Click to expand...
Click to collapse
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
cooltt said:
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
Click to expand...
Click to collapse
Ok, If you think unbranded is the best way to go can you point me in the right direction
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Beanvee7 said:
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Click to expand...
Click to collapse
What beanvee has said but I think it's worth mentioning I find Sam Firm tool pretty straight forward to use and you'll always get the firmware in separate parts which can be useful.
I found a link for the G930A here
I'm not really understanding the differences in firmware. How is flashing with this firmware
any different than what's on the phone right now?
I am just trying to get the wifi calling to work, How is flashing it with at&t version firmware going
to help me on the tmobile network.
I guess I don't know what I need, stock, unbranded, official or custom rom.
I checked all sites listed and there is no firmware for the J727a, alternative?
I would rather someone more knowledgeable guess what I need to do, if that is what is
necessary because the phones are no good to me without that feature. Any suggestions
would be appreciated.
Each carrier deploys their own CSC file, which contains carrier specific configurations, and its this file that determines if VoLTE or VoWIFI is enabled and how it connects.
AT&T may have different VoWIFI settings to TMobile, which is why using AT&T firmware it doesn't work. Some carriers outright disable it since they don't offer it.
Your best bet would be G930T firmware https://updato.com/firmware-archive-select-model?q=SM-G930T&rpp=15&order=date&dir=desc&exact=1
However unbranded G930U should also work because the unbranded firmware is meant to work on all cariers. G930A would likely get you no where since it'll be AT&T specific
The phones in the USA are all identical hardware under the hood, the only difference is the carrier branding and firmware.
But that's only for the S7, I'm not familiar with the J7.
And it's not through lack of knowledge @JohnAtlas, US phones are a nightmare to do anything with. There are several options available but it's difficult to explain what to do and how to do if you are not familiar with how the software works.
There are many guides on how to unlock the software on all US networks, and depending on the network can include multiple steps to complete, you just have to search and read.
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
JohnAtlas said:
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
Click to expand...
Click to collapse
All files in correct slots and use this Odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
JohnAtlas said:
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
Click to expand...
Click to collapse
That is the system recovery and when you flash with Odin you need to put your phone in download mode first press volume down+home+power. The phone should not go to that screen you have posted either before or after Odin, its a completely different recovery mode.
Get your firmware from updato. Com or sammobile
G930U, filter by USA and choose the latest XAA or USC and use the modified version of Odin. We know this works because thousands of people have used it to do what you are trying to do.
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
JohnAtlas said:
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
Click to expand...
Click to collapse
That's brilliant , glad your up and running.
So the letter "U"after the "G930" denotes the region of the world the device is build to operate in, the Americas just happens to be U. The unbranded firmware is the one that has a region but no network assigned to it, so a 3 letter code is used instead, in your case its USC, or XAA.
Europe is G930"F" or "FD" and the 3 letter code for unbranded is BTU & XEA.
Anyway if your phone is running great on T Mobile then don't update it anymore, turn auto update off. The advantage of keeping it T Mobile is you have the wifi calling, the unbranded firmware needs more fiddling around with the get the wifi calling working on the network your using, so best to stick with what works.
I will have a look for firmware for the J7 you have to see if i can recommend doing something with it to get the wifi calling working.
*update*
So it seems the J727 is the same as the J7 in terms of the internal components, everything is the same in both models so that's great news. I think the "27" bit is just a marketing thing.
In theory you should be able to flash the latest T Mobile Oreo to your device from this link https://www.sammobile.com/firmwares/galaxy-j7-pop/SM-J727T/TMB/download/J727TUVS4BRK1/249137/
Now before we start please check / do the following to avoid further problems.
1. Save everything you need from the phone to your pc.
2. Check that you have OEM unlocked in "developer settings" and "USB debug" enabled.
3. developer setting menu is, settings>about phone>software and information>build number>tap 7 or 8 times, developer menu should now appear. (Sometimes it's somewhere else but build number is what you want to find and tap on 7-8 times).
4. To avoid any issues with device FRP lock, delete your google account off the phone., settings>accounts>google. delete it. When successfully flashed you just add the account again when the phone starts for the first time by signing in.
5. Use the same version of Odin you used to flash your S7.
you can also use updato.com (i think it's slightly faster than sammobile.)
Let me know how you get on.
Remember J727T (TMB) is the firmware you want.

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

Unlocked s10e from ATT (SM-G970U) - Can I flash G970U1?

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 .

How To Guide F711U and F711U1 Firmware Links and Flashing Discussion Here

(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 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 have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public 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=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
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, 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 flagship 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
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
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available

Categories

Resources