G981U and G981U1 Firmware Links and Flashing Discussion Here - Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News

For those who aren't already aware, G981U is the model number of all of the US carrier versions of the S20. The G981U1 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 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 SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also 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 SamFirm/Frija.
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=305577
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305578
(Quebec tends to be the fastest download mirror, if it gives you that option)
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 S20, 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
- 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 SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, 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

Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc

So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here https://www.youtube.com/watch?v=ZPSWEL6-gWg&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.

I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released

jameslee2 said:
I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released
Click to expand...
Click to collapse
If you're saying that you want AT&T apps and bloatware and features, then all the files that you need are already linked in the OP

I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!

tijsva said:
I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!
Click to expand...
Click to collapse
I'm assuming the flash would fail. But there's only one way to know for sure

I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...

tijsva said:
I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...
Click to expand...
Click to collapse
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk

Bee101 said:
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk
Click to expand...
Click to collapse
I don't understand what you're asking

Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?

SM-G981U Carrier Aggregation for Europe
I have S20 SM-G981U1 that i flashed with SM-G981U with no problems but is there any way to make CA to work in Europe?
Any help will be greatly appreciated because i have way lower mobile data speed in EU with my US unlocked phone...

tijsva said:
Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?
Click to expand...
Click to collapse
For U and U1 firmware, yes. You'll have to look elsewhere for discussions on Korean firmware

So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?

Any firmware (compatible with U1) that has CSC feature enabled for native call recording?

tijsva said:
So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?
Click to expand...
Click to collapse
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.

tijsva said:
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.
Click to expand...
Click to collapse
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7

iBowToAndroid said:
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7
Click to expand...
Click to collapse
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.

dtothesquare said:
So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here
&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.
Click to expand...
Click to collapse
i got advanced messaging by just inserting a T-Mobile SIM into my unlocked s20, it restarted the phone and i even have the wifi calling too

tijsva said:
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.
Click to expand...
Click to collapse
The proof is already here in the thread. Many users have already done it

Related

[Q] G930V to G930U Conversion (Explain please)

Hello, All!
I have a G930V (Verizon S7) Non-EDGE, and I wan't to convert it to a G930U Unbranded (Or at least bloat free).
## BY THE WAY ##
Yes, I have seen other threads on this topic. Doesn't answer my confusions though.
Threads by:
tvm2487 (G930U Firmware)
James.Markham0757 (Can someone send me in the right direction...)
DeathAngel66669 (Using SamFirm to download SM-G930U-G930UUEU2APG9...)
## BY THE WAY ##
So anyways here are my questions.
##
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
7. Chances of bricking the phone? Would it be reversible?
##
My current S7 VZW Details:
Model: SM-G930V
Ver: 6.0.1
Patch Level: October, 1, 2016
Baseband Ver: G930VVRU4API3
I appreciate the help and your time. Thanks !
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
I don’t think it would flash as it is bootloader 2(5th character from right) latest firmware is 4!
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
From what I understand all the USA variants of the Galaxy S7's are the same hardware
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
I have an AT&T branded S7 SM-G930A and have flashed the U firmware and used it for a while. I have now switched carriers to T-Mobile used the U firmware without issues and now flashed the T-Mobile firmware and it works fine. KNOW IS NOT TRIPPED.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
Not sure, Odin may just fail to complete install?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
I never had luck flashing the HOME-CSC file, had to use straight CSC.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
One thing I did notice is the visual voicemail app tends to work better when using the specific carrier firmware(both AT&T & T-Mobile).
I'm using T-Mobile and I don't see a need to go back to U at this time as their is not much bloat on the T-Mobile firmware.
7. Chances of bricking the phone? Would it be reversible?
##
I just installed T-Mobile Nougat on my phone and got the error on phone and it was stuck on “You will need to use Smart Switch Recovery” to fix phone! SCARY!!! I managed to finally get firmware installed and running!
Understood.
When I get home today I'll try to install a newer version from SamMobile.
Updato has older versions. Sammobile has the latest which is.
G930U with code (VZW) on
G930UOYM4APL2
(https://www.sammobile.com/firmwares/download/118975/G930UUEU4APL2_G930UOYM4APL2_VZW/)
Would this be compatible?
G930UUEU4APL2 is the latest U-firmware. Everything flashes correctly, it won't trip KNOX, and it is super easy to go back to G930V firmware if you decide you want to send it back for warranty. You can't brick the phone by flashing signed files with Odin. The bootloader won't allow Odin to flash anything that could brick it.
I had already started replying before you posted above me. I'd recommend using my link to the firmware, as Sammobile downloads take FOREVER.
I see, I'm glad.
So, What would i need to make sure to do and not do in Odin 3.11.1?
AP/BL/CP/CSC from your zip? Just flash everything or only certain things?
Re-partition tick box? yes or no?
Flash all four of those files and DON'T CHANGE ANY Odin settings.
Okay. I just flashed it and now my phone repeatedly keeps booting into recovery.
The recovery logs and the red text at the bottom says:
dm-verity verification failed
Need to check DRK first...
Any ideas?
##PREVIOUS##
I think it might have to be because I used HOME_CSC rather than CSC.
What's the difference between both? Can i revert later?
##PREVIOUS##
@CVertigo1
I reflashed with the CSC file rather than the HOME_CSC file as according to your instructions in your thread (Latest G930U Firmware) and it worked perfectly fine!
KNOX is still at 0x0 and warranty void is fine.
( https://forum.xda-developers.com/verizon-galaxy-s7/how-to/g930u-firmware-pl2-g930v-success-t3558214 )
No bloat, amazingly fast, and some features i like are present. I'll report back to your thread on the battery life when i get more time with it.
I appreciate your patience.
(Will post screenshots later).
Home_CSC doesn't wipe user data, which causes issues when swapping firmware. That's what caused your bootloop.
Followed this, today, was sick and tired of the damn Verizon bloat slowing the phone down.
The phone runs faster - notably faster.
After installing the SIM, the phone returns, "Your device will restart to configure features supported by the new SIM card."
And then" It's useless. If I hard-power reset it, and take out the SIM, it's viable - it's just useless otherwise.
Phone is a G930V, flashed to G930U.
Any Suggestions? The phone is *NOT* rooted, so I can't easily take out or rename the AutoPreconfig.apk package.. Argh.
Will I get the android nougat update on this ROM?
Just converted G930V to G930U, all 100% working here in the UK. Fully debranded and no verizon warning about sim change. perfect
Mind telling me what thread you used to find the latest firmware? This forum for the phone is so rarely used anymore, it's hard to tell what info to go even go on anymore.
Is PL2 the latest for 930U? I'm VZW but US, not UK

Galaxy s10+ SM-G975FDS samsung firmwares need help

When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
AlwaysPhresh said:
When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
Click to expand...
Click to collapse
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Cindysmith0994 said:
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Click to expand...
Click to collapse
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
AlwaysPhresh said:
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
Click to expand...
Click to collapse
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Cindysmith0994 said:
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Click to expand...
Click to collapse
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
AlwaysPhresh said:
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
Click to expand...
Click to collapse
Yes. Just follow the root instructions on the S10 forum.
Cindysmith0994 said:
Yes. Just follow the root instructions on the S10 forum.
Click to expand...
Click to collapse
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
AlwaysPhresh said:
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
Click to expand...
Click to collapse
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Cindysmith0994 said:
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Click to expand...
Click to collapse
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
AlwaysPhresh said:
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
Click to expand...
Click to collapse
If you flashed those files you should be back to stock. Start the process again. Try this video: https://m.youtube.com/watch?v=Mn4dTjxY89I
Also make sure your patched magisk file is not corrupted when transferred back to your PC.
If not, I'm out of suggestions...sorry.

Samsung galaxy tab s5e lte - flash different firmware

Hey i have samsung galaxy tab s5e lte (sm-t727v) it is unlocked verizon tab i want to flash samsung stock firmware to remove varizon boatload & pre-installed apps & also some features like call & message continuity are blocked by verizon. So can you please suggest which firmware stall i flash & how. I’ve tried flsahing sm-t727 & sm-t725 via odin but it gives error (secure check fail : Pit)
Im curious about tthis myself, but ive kind of resignes myself to the fact im probably goong to have to get an s6 directly from samsung that allows the option to unlock the bootloadr out of the box. There is a new "security update" from verizon though, im curious about what it actually patches before I update.
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
purplerose1414 said:
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
Click to expand...
Click to collapse
Where did you find the T727R4 firmware?
Ryche666 said:
Where did you find the T727R4 firmware?
Click to expand...
Click to collapse
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
anyone else have success with this? ive followed everything so far but i'm stuck trying to unlock bootloader. the option is there in developer options i can turn it on or off in there but when i power down and boot into download mode the option to unlock bootloader isnt there and it says OEM Lock On (u1)
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
It was cuz i was on a newer fw version for R4 (feb4) i downgraded to the Dec one and i now i have my bootloader unlocked (shows in dev settings, get notification at boot, and says oem lock off in download mode) but i keep getting a error about "only being able to flash official firmware versions (vbmeta)" . turns out this is from my KG Status being PRENORMAL instead of Checking. you can check this in download mode as well. did you have any issues with that or kknow what i'm talking about? there are guides that say to do things like roll the date back on your phone manually then check for updates but it doesnt work
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
also i'm a little confisued about the end of your directions. I am not a Verizon Subscriber i bought this 2nd hand for a deal i am on TMO (not planning on really using data on thin atm but still) Am i correct in thinking after you flashed R4 BL AP CP and CSC, then booted into the R4 firmware and went through initial setup, then reboot to recovery to unlock bootloader and then flashed the t727u AP, left the R4 bootloader, and flasshed VZW CP and CSC? i cant seem to get mine to boot if i do that i get hash check errors when it tries to boot and spits me out into download mode. if this is the case do you remember or can you check the exact versions of CP, AP, and CSC you flashed? right now what i did was flash all R4 tars to go from 727v to 727r4, went though setup and verified i have oem unlock option in dev options then rebooted to download mode and unlocked bootloader THEN i FLASHED 727u versions of AP CP and CSC since my error with the vzw ones i mentioned earlier. Last question. should i be putting my sim in? i notice when i flash the U firmware i get a message about carrier settings update and it makes it reboot
thanks for replying btw
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
albinoman887 said:
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
Click to expand...
Click to collapse
See, as soon as I switched from T727V to T727U I stopped even seeing kg status in download mode. In my original post in this thread I thought that meant I had tripped it. I really have no clue why just switching to unbranded firmware would make that difference either. I just lucked out on the magic cocktail to unlock Verizons bootloder, I was kind of hoping it would be easy peasy for others. Like, my poor tablet went through odin every day for a straight month.
E: Just saw your edit in your post. I'll have exact firmwares I used asap. In the meantime, my hotspot worked just fine on the unbranded CP and CSC, maybe try that?
ok let me know ill be up a few more hrs
---------- Post added March 10th, 2020 at 12:19 AM ---------- Previous post was March 9th, 2020 at 11:55 PM ----------
you didnt happen to do anything outlined in this thread did you?
https://forum.xda-developers.com/tab-s5e/how-to/samsung-galaxy-tab-s5e-debloat-root-info-t3935010
i wonder if you disabled a Knox apk at the right time to make KG status go away
I'm really scared of bricking my LTE AT&T tablet if I flash the only firmware I was able to grab.
Any way to find the specific stock firmware for my sm-t727A? I've tried Frija, and went all over google to no avail; I can only find other stock firmware.
If I just want to switch to sm-t727u firmware from sm-t727v firmware without rooting do I need to go through the extra step of flashing the us cellular version first?
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I get to the unlock the bootloader part but then when I go back in and try to flash the U software according to your instructions, it doesn't work. Could it be that the software has been updated since the instructions were written and it won't work now?
I have tried every version of Patched Odin and followed these directions to a T. I even went back and tried other things and can't get this to work. If someone can help me get the U software to flash on my SM-T727V, I got $20 I'll Venmo or Zelle you.
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I am trying to copy your process with a Tab A 2019 unlocked, but Sprint variant with no success so far. I have bricked it a lot, but it doesn't seem to want an unlocked firmware for the same model . I haven't tried flashing it's bootloader though, out of fear of bricking it ( I have unlocked its bootloader already).
Hey guys, just found the thread. Anyone know if an unlocked SM-T727A can be OEM unlocked? I mean the bootloader. The option is always missing no matter how many time I try according to the tutorials, which makes me doubt if a branded S5e doesn't even have this capabililty. Perhaps that's why I am here seeking a chance to flash it to an SM-T727U. Thanks for anyone who replies.
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Wieczorkiewicz said:
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Click to expand...
Click to collapse
Help me ola if u r there. I have same t727a of att live outside The US. I just want to skip Att block and use SMS app, so flash Usc t727r4 via Odin patched is enough for me? And if i want update from android 9 to 10 i just do same thing with Q firmware?
i try flash USC T727R4 on ATT T727A success for first time, but Massage app still require link other SamSung phone to use. I have full funtion simcard inserted but Google massage app cant recognize too.
Btw, convert to USC is good, no ATT bloatware and now have OTA outsite The US.

s5e T727A AT&T unlocked - won't flash on ODIN

Hi All,
Hate to be the newbie here but having trouble flashing a new ROM on my unlocked AT&T s5e T727a.
I followed the instructions for Odin and tried flashing the latest ROM, believe the carrier was for Turkey from Sammobile.
It won't setup a connection and tried the following:
1. Different ROMs
2. Two different computers
3. Different USB ports and cables
4. Different Odin versions
5. Did a reset for the tablet (tried again and same issue)
6. Tried the 4 file approach and the single AP file approach
I'm baffled at this point and can't get passed the setup connection. Goes without saying main reason doing this is I live overseas, don't have an AT&T sim and not getting updates.
I took it to the Samsung dealer here and they said they won't flash it with an official ROM for me which was disappointing.
It's safe to say I've gone through most threads on this, watched the YouTube videos and so on. Nothing works and never had this problem on other tablets before.
Thanks
I have new SM-T727A outsite the US, want to flash other rom to del Att block and i found this thread.
Maybe late for you but can have someone next.
Find and download rom USC SM-T7274R (US Cellular unlock).
Unzip and flash via Odin Patched (must be Odin Patched).
Then you will have almost full unlocked Att tablet ( no bloatware, no Att account anymore, and FOTA update )
But still cant use native call or sms like international version.
I think there's a typo in the previous comment, I could not find that ROM. What I ended up doing is downloading the SM-T727U ROM via Frija (CSC: USC) and flashing with Odin3 v3.14.1_3B_PatcheD.
The tablet got stuck on the Samsung logo but booted without issues after wiping the cache partition and doing a factory reset. (power + volume down to reboot / then power +volume up to get to recovery).
I now have Android 11 and no more AT&T junk anywhere.
Tablet recognizes a non-activated SIM card that I've put in (Virgin Canada) so I guess the LTE part works too.
Cheers!
Zachis said:
I think there's a typo in the previous comment, I could not find that ROM. What I ended up doing is downloading the SM-T727U ROM via Frija (CSC: USC) and flashing with Odin3 v3.14.1_3B_PatcheD.
The tablet got stuck on the Samsung logo but booted without issues after wiping the cache partition and doing a factory reset. (power + volume down to reboot / then power +volume up to get to recovery).
I now have Android 11 and no more AT&T junk anywhere.
Tablet recognizes a non-activated SIM card that I've put in (Virgin Canada) so I guess the LTE part works too.
Cheers!
Click to expand...
Click to collapse
CSC: USC still is US carrier rom. I tried flash SM-T727U CSC:XXA . Its full unlocked rom for US version.
Now my ATT tab (T727A) working like global version.
dangtoi1993 said:
CSC: USC still is US carrier rom. I tried flash SM-T727U CSC:XXA . Its full unlocked rom for US version.
Now my ATT tab (T727A) working like global version.
Click to expand...
Click to collapse
I can't find XXA. Do you mean XAA?
Zachis said:
I can't find XXA. Do you mean XAA?
Click to expand...
Click to collapse
Sorry my mistake, exactly XAA.

whats best way to flash unbranded SM-G715U1 to U for vzw?

So I will post this here for my Xcover pro with exynos9611
So both my phone and vzw branded version phone are same model, and android 11 firmware is out for verizon and i already got the U1 version on my phone G715U1UEU7BUC3 ota 11.
It looks like this Is the latest Odin 3.141 software and verizon G715USQU7BUC1 firmware to get it done?
Also, do i need to do the full flash or can i get by with just one file that includes all the vzw bloatware in the userdata file. Is that true?
Once complete ive also read i need to do a factory reset and that it can be done while in DL mode. Is that true?
Finally, can i leave my sim in for this or should it be out or not matter?

Categories

Resources