G973U and G973U1 Firmware Links Here - Samsung Galaxy S10 Guides, News, & Discussion

(For those who don't know, G973U is the model number of all of the US carrier versions of the Galaxy S10. The G973U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among any of those models.)
The large files will be your 4 part firmware and then grab your desired USERDATA as well. I'll continue to add more versions and more USERDATAs over time.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=290645
U1 firmware: https://www.androidfilehost.com/?w=files&flid=290646
Notes:
- I compress extra small for space and bandwith savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- I remove the .md5 from each file solely for faster flashing (Odin won't check the file integrity without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for Android File Host folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and 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. Any zips with "wipe" in the title do not have a HOME CSC included.
- SamFirm still works, if you want to download them yourself. I pay for a subscription to a site that gets beta builds and also gets the official releases before they hit SamFirm, so that's where my files come from
- I have identical threads for the S10e and S10+ as well
- Post #173 has the correct procedure for changing from one U firmware to a different U firmware, with proper bloat and carrier features, etc.
- You can get USERDATAs from SamFirm for everything but AT&T and Cricket- those files will never be on SamFirm. So in addition to the 5 piece firmware, I'll try to always upload one USERDATA per bootloader increment for those carriers.
- For USERDATAS (all the others are self explanatory):
AIO = Cricket
CCT = Xfinity Mobile (Comcast)
CHA - Spectrum Mobile (Charter)
TMK = Metro PCS

The SM-G973U is the model number for the Samsung Galaxy S10. SM-G970U is the model number for the Galaxy S10e.

Drakoid said:
The SM-G973U is the model number for the Samsung Galaxy S10. SM-G970U is the model number for the Galaxy S10e.
Click to expand...
Click to collapse
Ughhh stupid new nomenclature. Thanks for catching that - gonna take some brain re-training to keep these all straight now haha

Build SBA added.
SPR is the only USERDATA for this build so far - not sure if it will stay a Sprint-exclusive release, or be more widely pushed out. But like with any other build, it can be flashed to any S10, regardless of which carrier it originally came from.
EDIT: Xfinity and Verizon USERDATAs added

G973U and G973U1 firmware is now live and downloadable in SamFirm. Getting U1 (at least for now) requires manual entry - Auto will not work. U firmware is up for these carriers:
Xfinity Mobile
Spectrum Mobile
Sprint
T-Mobile
US Cellular
Verizon (have to use Manual entry - Auto will not work)
So going forward, I'll only be adding full builds if I can get them before they hit SamFirm, and only if there isn't build for that month already (eg. I won't add any more February builds since SBA is already up.). I will try to stay up to date on USERDATAs for AT&T and Cricket, since AT&T won't let their firmware be put on SamFirm.

Will this work to remove the Verizon branding from my s10? I ask that as I purchased outright from Samsung and am running G973USQU1ASBA.
It appears when my phone activated with the Verizon SIM, it added their profile and I would prefer it to be unlocked as purchased so I can get features like smart call back. Thanks in advance.

iOSNick said:
Will this work to remove the Verizon branding from my s10?
Click to expand...
Click to collapse
Yep!

iBowToAndroid said:
Yep!
Click to expand...
Click to collapse
Awesome, thanks for the verification. As for the 5th file to flash 'userdata', would I opt to not do this for Verizon and just flash the first four files to go back to unlocked status?

iOSNick said:
Awesome, thanks for the verification. As for the 5th file to flash 'userdata', would I opt to not do this for Verizon and just flash the first four files to go back to unlocked status?
Click to expand...
Click to collapse
There is no USERDATA in U1 firmware

Ok, that clears it up, userdata is just for the U firmware. Is there something I should do to avoid Verizon from installing their profile? I am currently running the U1 firmware, but somehow have Verizon's branding attached to the phone, presumably from the SIM setup.
Or is there any way to just remove the Verizon branding while retaining the U1 firmware I'm on currently?

iOSNick said:
Ok, that clears it up, userdata is just for the U firmware. Is there something I should do to avoid Verizon from installing their profile? I am currently running the U1 firmware, but somehow have Verizon's branding attached to the phone, presumably from the SIM setup.
Or is there any way to just remove the Verizon branding while retaining the U1 firmware I'm on currently?
Click to expand...
Click to collapse
I define "branding" by a startup/shutdown logo, plus carrier apps installed. U1 firmware doesn't have any of that

iBowToAndroid said:
I define "branding" by a startup/shutdown logo, plus carrier apps installed. U1 firmware doesn't have any of that
Click to expand...
Click to collapse
Agreed, same thing I am referring to. My phone has the Verizon splash page on boot up/shut down and the My Verizon folder with their specific apps in the app drawer. Weird thing is, I am actually running the U1 software straight from my Samsung.com order.
I'm currently downloading the U1from this thread to flash to the phone in an effort to remove the Verizon bloatware, was just was curious if there was another way to remove Verizon without re-flashing U1. Appreciate your help with this and setting up these download links as well!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G973U using Tapatalk

iOSNick said:
Agreed, same thing I am referring to. My phone has the Verizon splash page on boot up/shut down and the My Verizon folder with their specific apps in the app drawer. Weird thing is, I am actually running the U1 software straight from my Samsung.com order.
I'm currently downloading the U1from this thread to flash to the phone in an effort to remove the Verizon bloatware, was just was curious if there was another way to remove Verizon without re-flashing U1. Appreciate your help with this and setting up these download links as well! View attachment 4721638
Sent from my SM-G973U using Tapatalk
Click to expand...
Click to collapse
It's impossible to have carrier bloat if you're running U1, and it's impossible to be running U1 if you have carrier bloat. You're not running U1. You're running U. Look at the picture you posted. You didn't order a Samsung unlocked model, you ordered a Verizon variant.
Flashing U1 is the only way to remove bloat.

Built-in Visual Voicemail 973U T-Mobile Not Working
Thanks for the links!
I flashed my U1 S10 over to U with TMo Userdata. I have the TMo pink splash screen and bloat installed, as well as the better reception gained from adding their firmware, but the Visual Voicemail that could be accessed by tapping the 3 dot menu in dialer, then selecting Visual Voicemail, is gone. The only option that shows is the regular voicemail. It worked perfectly on my Note 9 with the Pie Beta firmware, and I had switched it from U1 to U as well.
Does anyone have any idea what I might be doing wrong, or how to get stock VVM back? I've read that it's carrier dependent and all of that, but the conditions on my S10 are the same they were on my Note 9 from everything I can see, yet I don't have stock VVM. I am wondering if this might be something where TMo is just behind in adding support for the S10 to work with the stock VVM, but I have no clue how all that stuff works on the carrier side of things.
Any help with this would be greatly appreciated, so I can remove the vomit-spewed (just in appearance IMO) app that is TMo's Visual Voicemail app. I tend to obsess over things like this and it's driving me crazy. Lol, I know, it's nitpicky, but I shelled out almost $2K for mine and my wife's phones, so I just want it to work.

I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware? Verizon blocks SMART callerID unless someone knows an alternative.
That's the only reason I would move because I use Package Disabler to hide the bloat.

brian5259 said:
I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware?
Click to expand...
Click to collapse
The answer is found in the 2nd sentence of the OP

brian5259 said:
I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware? Verizon blocks SMART callerID unless someone knows an alternative.
That's the only reason I would move because I use Package Disabler to hide the bloat.
Click to expand...
Click to collapse
Technically, yes. The smart caller id function will be available after flashing the unlocked firmware, however it appears there is still some control, as the setting will keep toggling itself off. Since flashing, my caller id will stay enabled for about 48 hours max, then be automatically toggled off. Others are reporting the same thing, so something is still preventing it from staying enabled all the time. Quite annoying, as there is no way to tell when it is toggled off, aside from seeing a call without it or constantly checking settings.
Sent from my SM-G973U1 using Tapatalk

So I have the G973U1 phone, and want to flash the Verizon software for video calling, etc.
A few questions...
Am I correct that I down/flash the G973U firmware.
Do I really need the USERDATA package? What happens if I skip it?
When all is done will my phone show VZW/VZW/VZW or will it show VZW/VZW/XAA?
What is the impact if it stays XAA as opposed to VZW, or... do I want it to show VZW/VZW/VZW?
how do I change it to VZW/VZW/VZW (there was a thread I followed for my GS8, but starting with the GS9/Note9 it appears its either not needed, or not done the same way? or I just can't find the instructions)
Thanks!

Same Here! Anybody know?
KidJoe said:
So I have the G973U1 phone, and want to flash the Verizon software for video calling, etc.
A few questions...
Am I correct that I down/flash the G973U firmware.
Do I really need the USERDATA package? What happens if I skip it?
When all is done will my phone show VZW/VZW/VZW or will it show VZW/VZW/XAA?
What is the impact if it stays XAA as opposed to VZW, or... do I want it to show VZW/VZW/VZW?
how do I change it to VZW/VZW/VZW (there was a thread I followed for my GS8, but starting with the GS9/Note9 it appears its either not needed, or not done the same way? or I just can't find the instructions)
Thanks!
Click to expand...
Click to collapse
Same here!

i have chinese model G9730ZCU1ABA do you think firmware on this thread first link is compatible? just in case

Related

[Collection] Firmware/ROM Full File For Galaxy Note 8

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Soft brick
Failed to mount a partition: efs, data, system,...
Failed flash firmware via Odin (stop at a partition: HIDDEN, CACHE,...)
Bootloop
Factory reset
Mod Edit: * * * IT IS YOUR RESPONSIBILITY TO VERIFY WHAT YOU ARE FLASHING TO YOUR DEVICE IS SAFE AND FOR YOUR DEVICE * * *
Mod Edit
1. Samsung Galaxy Note 8 (SM-N950F)
VietNam: N950FXXU1AQI1_N950FOXM1AQHF_XXV_7.1.1_FULL.zip (3,6G)
UK: N950FXXU1AQI1_N950FOXM1AQHF_BTU_7.1.1_FULL.zip (3,6G)
2. Samsung Galaxy Note 8 (SM-N950N)
S: N950NKSU1AQI2_N950NOKR1AQI2_SKC_7.1.1_FULL.zip (3,1G)
L: N950NKSU1AQI2_N950NOKR1AQI2_LUC_7.1.1_FULL.zip (3,1G)
K: N950NKSU1AQI2_N950NOKR1AQI2_KTC_7.1.1_FULL.zip (3,1G)
3. Samsung Galaxy Note 8 (SM-N950U)
USA: N950USQU1AQI9_N950UOYN1AQI9_USC_7.1.1_FULL.zip (3,5G)
Verizon: N950USQU1AQI5_N950UOYN1AQI5_VZW_7.1.1_FULL.zip (3,6G)
T-Mobile: N950USQU1AQI5_N950UOYN1AQI5_TMB_7.1.1_FULL.zip (3,4G)
Sprint: N950USQU1AQH7_N950UOYN1AQH7_SPR_7.1.1_FULL.zip (3,5G)
4. Samsung Galaxy Note 8 (SM-N950U1)
AT&T: N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G)
5. Samsung Galaxy Note 8 (SM-N950W)
Canada: N950WVLU1AQI5_N950WOYV1AQI5_XAC_7.1.1_FULL.zip (3,6G)
6. Samsung Galaxy Note 8 (SM-N950X)
Updating…
Mod Edit
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
kt.thegioiso said:
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Click to expand...
Click to collapse
There's already a thread for the SM-N950F/DS Model:
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
The correct unlocked (SM-N950U1) version can be found here:
https://forum.xda-developers.com/ga...covery-odin-recovery-software-t3671615/page22
The carrier versions of the Unlocked (SM-N950U1) "aqh9"...only differ by including the product activation information that the SIM provides during provisioning. Flashing the XAA unlocked firmware and inserting SIM is the same as flashing any of the SM-N950U1 brand labeled firmware like SPR AQH9...
---------- Post added at 05:38 AM ---------- Previous post was at 05:33 AM ----------
car2carl said:
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U1 is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
Click to expand...
Click to collapse
...
Canada firmware link points to AT&T firmware. Could someone please update that link? I will be sending my phone in for refund (to get the N950F), and want to completely reset it.
Side note, anyone know how they check airtime usage to determine return eligibility? I'm well under 30 minutes, but I'm curious regardless.
https://www.sammobile.com/firmwares/SM-N950F/SWC/download/N950FXXU1AQI1/189026/
Is it possible that anyone can download this for me?
Edit: obsolet, retourned to shop with light bleeding on the hole left side.
I keep getting failed message when trying to flash the verizon firmware. any ideas.
thunderbread said:
I keep getting failed message when trying to flash the verizon firmware. any ideas.
Click to expand...
Click to collapse
Edit config file for UMS/patch from 0 to 1...and if regular Odin fails...use Prince Comsy's Odin...if still fail download firmware again...if still fail, boot to recovery and perform factory reset then flash again
Could I flash SM-N950F firmware on SM-N950N device? I need to change csc from Korea to Vietnam
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
D_Gabe said:
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
Click to expand...
Click to collapse
Sounds like you might not have re-partitioned it properly?
seandop said:
Sounds like you might not have re-partitioned it properly?
Click to expand...
Click to collapse
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
D_Gabe said:
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
Click to expand...
Click to collapse
Glad you figured it out! Welcome to Android.
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Croq360 said:
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Click to expand...
Click to collapse
Yes, download and flash the latest VZW firmware in Odin (all four files) and all will be well.
Deleted.
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
See mismatch
kirschdog1 said:
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
Click to expand...
Click to collapse
Use Prince Comsey Odin. You won't get the device mismatch errors.
sprint sm-N950USQU1AQI5 flashing to use on another carrier
I tried flashing with the zip file. But, I see invalid sim when I insert different carrier. Detailed desc would help me.
Or, is there any alternative to flash the sprint note 8(N950USQU1AQI5) to use different carrier.
Thanks in advance.

N970U and N970U1 Firmware Links Here

For those who aren't already aware, N970U is the model number of all of the US carrier versions of the Note 10. The N970U1 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.
This is not a "beginner's guide to Odin flashing" type post/thread, so I won't list basic, step-by-step instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware, I recommend you consult one of the "beginner's" posts/threads - there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=297977
U1 firmware: https://www.androidfilehost.com/?w=files&flid=297978
NOTES:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have an identical thread for the Note 10+
- 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
- I know AFH servers/mirrors can be wonky sometimes, so if you want to download the latest version of whatever firmware you're seeking yourself, you can do so via SamFirm or Frija (plenty of links and threads here on XDA). I pay for a subscription to a site that gets beta builds and also gets the official releases (usually) before they hit SamFirm, 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 update 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.
- You can get USERDATAs from SamFirm for everything but AT&T and Cricket- those files will never be on SamFirm. So I'll try to always upload at least one USERDATA per bootloader increment for those carriers, and 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 USERDATAS (all the others are self explanatory):
AIO = Cricket
CCT = Xfinity Mobile (Comcast)
CHA - Spectrum Mobile (Charter)
TMK = Metro PCS
- 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
Firmware is now available via SamFirm and Frija, but manual entry is required in a lot more cases than previous models. Hopefully that's just because the phone technically doesn't release until Friday, and that they change that on Friday or soon after.
Manual entry is currently required for VZW, CHA, and TMB U firmware, and for all carriers/regions/CSCs of U1 firmware
iBowToAndroid said:
Firmware is now available via SamFirm and Frija, but manual entry is required in a lot more cases than previous models. Hopefully that's just because the phone technically doesn't release until Friday, and that they change that on Friday or soon after.
Manual entry is currently required for VZW, CHA, and TMB U firmware, and for all carriers/regions/CSCs of U1 firmware
Click to expand...
Click to collapse
Thanks for the links. I wonder if my Note10 tomorrow will get a software update out of the box.
Charkatak said:
Thanks for the links. I wonder if my Note10 tomorrow will get a software update out of the box.
Click to expand...
Click to collapse
I only saw the news about the Verizon models getting updated. Theoretically that means that Xfinity and Charter should also have updates, since they all get the same updates at the same time. Not sure about any other models yet
iBowToAndroid said:
I only saw the news about the Verizon models getting updated. Theoretically that means that Xfinity and Charter should also have updates, since they all get the same updates at the same time. Not sure about any other models yet
Click to expand...
Click to collapse
By the way, I did use manual entry in SamFirm to find TMB firmware and download it. As a rule of thumb, I usually don't flash my phones right away after getting it, as I want to make sure that it isn't defective
Wonder if we need another Odin version or the regular 3.13/or Patched would work
Charkatak said:
Wonder if we need another Odin version or the regular 3.13/or Patched would work
Click to expand...
Click to collapse
Existing 3.13 3B Patched Odin will work fine
iBowToAndroid said:
Existing 3.13 3B Patched Odin will work fine
Click to expand...
Click to collapse
Cool, my PC is ready and setup for Note10 Any idea if XAA firmware and the carrier's firmware are within the range/build date to allowing flashing? As I know the downgrade usually fails.
Charkatak said:
Cool, my PC is ready and setup for Note10 Any idea if XAA firmware and the carrier's firmware are within the range/build date to allowing flashing? As I know the downgrade usually fails.
Click to expand...
Click to collapse
You can't downgrade if there's only one software version that's been released so far - there's nothing to downgrade to.
But even if it's months or years down the road, the flash will only fail if you're trying to downgrade bootloaders. As long as you operate within the same bootloader, you can flash anything you want
This is the one I'm getting direct from Samsung: SM-N970UZSAXAA. It is supposed to be unlocked. I asked for a Sprint sim Card. I hope it's not tied to Sprint, but can be moved to any US Carrier if I want to once the TMB-SPR merger completes.
SamFirm shows this firmware for TMB: N970USQU1ASH4 and I checked U1(XAA) as well and they are the same
iBowToAndroid said:
Firmware is now available via SamFirm and Frija, but manual entry is required in a lot more cases than previous models. Hopefully that's just because the phone technically doesn't release until Friday, and that they change that on Friday or soon after.
Manual entry is currently required for VZW, CHA, and TMB U firmware, and for all carriers/regions/CSCs of U1 firmware
Click to expand...
Click to collapse
Looks like everything is back to normal, in SamFirm. Manual entry is now only required for VZW U firmware, as has traditionally been the case. Also, if you type in an older version for VZW, it will automatically give you the newest version, if there is one. So you don't have to always know the exact newest version - entering in the correct details of any previous version should always trigger the newest one.
Also, SH4 is now showing as the newest build for U1, T-Mobile, and Verizon. Spectrum gets SH5 (no idea why), and Sprint is still back on SGO.
iBowToAndroid said:
Looks like everything is back to normal, in SamFirm. Manual entry is now only required for VZW U firmware, as has traditionally been the case. Also, if you type in an older version for VZW, it will automatically give you the newest version, if there is one. So you don't have to always know the exact newest version - entering in the correct details of any previous version should always trigger the newest one.
Also, SH4 is now showing as the newest build for U1, T-Mobile, and Verizon. Spectrum gets SH5 (no idea why), and Sprint is still back on SGO.
Click to expand...
Click to collapse
Received my Note 10 U1, tested it on original firmware XAA(build: ASGO) and just now completed flashing to T-MO without updating to ASH4 build and want the phone to find and update firmware to see if OTA works. To get to download mode, I needed to press Vol + and - and power and the same time.
Flashed 5 files: BL, AP, CP, regular CSC and USERDATA. Device shows T-Mobile logo at boot, has Advanced Messaging, Video Call and I don't see any bloatware except for couple of T-Mo apps.
Went through setup and was able to get new OTA with August 1 patch(screenshot)
Wow great job! Can I get the link for the 10+ ...
I have the unlocked one but I have att and the only way to get wifi calling is flashing the U firmware
cubano2031 said:
I have the unlocked one but I have att and the only way to get wifi calling is flashing the U firmware
Click to expand...
Click to collapse
You can go to my profile to find all of my threads. But flashing U probably won't give you wifi calling. It's been extensively discussed in my S10 threads, and it usually doesn't work if you have a U1 model
Charkatak said:
Received my Note 10 U1, tested it on original firmware XAA(build: ASGO) and just now completed flashing to T-MO without updating to ASH4 build and want the phone to find and update firmware to see if OTA works. To get to download mode, I needed to press Vol + and - and power and the same time.
Flashed 5 files: BL, AP, CP, regular CSC and USERDATA. Device shows T-Mobile logo at boot, has Advanced Messaging, Video Call and I don't see any bloatware except for couple of T-Mo apps.
Went through setup and was able to get new OTA with August 1 patch(screenshot)
Click to expand...
Click to collapse
Quick question, did your provider codes change? I flashed the Verizon files and am still stuck on XAA? Any help would be appreciated.
redneckben said:
Quick question, did your provider codes change? I flashed the Verizon files and am still stuck on XAA? Any help would be appreciated.
Click to expand...
Click to collapse
Initially, before I put in TMB sim, phone was on XAA/XAA/XAA. Now after all was said and done, my phone shows TMB/TMB/XAA. Make sure you put in the sim when you get the phone and when it has original firmware, so it can apply sim carrier's settings. Then you can flash and get the results that you need.
Charkatak said:
Initially, before I put in TMB sim, phone was on XAA/XAA/XAA. Now after all was said and done, my phone shows TMB/TMB/XAA. Make sure you put in the sim when you get the phone and when it has original firmware, so it can apply sim carrier's settings. Then you can flash and get the results that you need.
Click to expand...
Click to collapse
Thanks man I'll give that a shot.
@iBowToAndroid It states in the op that these models are all interchangeable. I have a U1 and flashed it to vzw U now when I try to Flash back to U1 it fails and says model mismatch???? Any help would be appreciated.
redneckben said:
@iBowToAndroid It states in the op that these models are all interchangeable. I have a U1 and flashed it to vzw U now when I try to Flash back to U1 it fails and says model mismatch???? Any help would be appreciated.
Click to expand...
Click to collapse
That's not much information.
1. What's the current U build?
2. Which U1 build are you trying to flash?
3. Where do you get that error exactly?
4. What Odin version are you using?
5. Do you get any other errors, either in Odin or on the phone itself?
iBowToAndroid said:
That's not much information.
1. What's the current U build?
2. Which U1 build are you trying to flash?
3. Where do you get that error exactly?
4. What Odin version are you using?
5. Do you get any other errors, either in Odin or on the phone itself?
Click to expand...
Click to collapse
Sorry, the phone was purchased as a unlocked version from samsung, model number SM-N970UZSAXAA/SM-970U1 is what the box says.
1. N970USQU1AHS4 is the build that I was able to flash. And the actual problem is that I had a brain fart and didn't read your simple instructions and instead of booting the phone first I opened the box and flashed the firmware. The issue I am having is my "Service provider SW ver. is stuck at XAA/XAA/XAA and I'm trying to get it to switch to VZW.
2. N970U1UEU1ASH4 I looked at all the n970u1 firmwares on samfirm and this was the only one that had XAA.
3. After I load the files into their locations and hit start it checks the files and the fails on the 4th step, I can run it again and find out exactly if you'd like.
4. 3.13.1 patched I believe.
5. None
I may be taking the wrong route to answer my problem. I really need help with getting it to show the right service provider code VZW.
Thank you for your help.

Switching versions of Pie - can I do it without erasing? (H930DS, AU)

Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge. It changed me from AU to HKG for reasons unknown to me.
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Wibble Wobble said:
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge.
It changed me from AU to HKG for reasons unknown to me.
Click to expand...
Click to collapse
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Wibble Wobble said:
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Click to expand...
Click to collapse
We haven't always had TWRP-flashable zips. Only thanks to generous, talented devs do we have the collection of TWRP flashable zips for US998, H931, H933, VS996, LS998, T-mobile H932, H930, India H930DS. That's only 8 of at least 20 variants and I'm not even counting all the different regional variants of H930DS...
So you will have to do what we all did before TWRP-flashable zips, and what we will have to do again when some of our TWRP flashable zip devs move onto other phones.
Method #1 -- Works some of the time on Oreo, not yet tried on Pie
This worked for many people in Oreo -- but some still had to reinstall TWRP, reformat data, reinstall the root files. Never could figure out the difference between success and not. Then we got TWRP-flashable zips and the issue became moot.
1) Make backup in TWRP AND make backup of all apps in Titanium Backup.
2) Flash new KDZ via Pie-compatible Dev Patched LGUP in Partition DL mode, but omit the Recovery partitions. Do NOT select "all partitions". This will let you keep TWRP.
3) Boot into TWRP via fastboot commands from your computer, just like when you first installed TWRP using the WTF instructions. (Best not to use the stupid hardware button dance.) Once in TWRP, then choose Reboot to Recovery (from within TWRP) to get the actual internal phone TWRP, instead of the PC TWRP.
4) Flash the Pie-compatible three root files (Magisk, encryption disabler, root check disabler, Magisk again). See attachments on this post to download those files.
5) Restore all Data from within TWRP. Do not choose any other categories.
6) Wipe all Caches.
7) Reboot
Restoring all TWRP data may or may not overcome the fact that you have re-flashed encrypted stock Pie on your phone. IF it does work, then after rebooting the phone if anything is still wonky, use Titanium Backup to restore all apps and data (this is in addition to the TWRP data restore you did).
Good luck.
Method #2 -- Works all the time, but yeah you have set up your phone again
1) Flash new KDZ via Pie-compatible Dev Patched LGUP in REFURBISH mode.
2) Your phone is now on the region KDZ you desire and you still have unlocked bootloader. You will need to reinstall TWRP, and then flash the three root files (Magisk, encryption disabler, root check disabler, Magisk again). This includes the step where you reformat all data with a "YES".
See instructions here:
REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
THAT POST ASSUMES YOU HAVE PREVIOUSLY UNLOCKED BOOTLOADER, AND THAT YOU HAVE NOW UPGRADED TO STOCK PIE KDZ. YOU HAVE UNLOCKED BOOTLOADER and are STILL on firmware which has FASTBOOT FLASH COMMANDS.
___________
Dev Patched LGUP
Dev Patched LGUP vs regular LGUP is necessary when cross flashing across regions or other variants. You will need this for either of the two methods above.
Here's how to flash with LGUP:
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open Dev Patched LGUP and flash PIE KDZ either via PARTITION DL MODE (but omit Recovery Partitions for your purpose in this thread) for Method #1 or via REFURBISH for Method #2.
Use the attached patched LGUP in this post. If you get a ".dll error" you either didn't install correctly or are using the wrong version of Dev Patched LGUP. Read the installation instructions carefully. Some people have used OTHER versions of LGUP before and ignore the installation instructions -- they think they know how to install and they do NOT --- then complain about .dll error, which is their fault.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" MODE IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader).
3) IF your bootloader is unlocked, it will remain unlocked after flashing KDZ.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. < READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
ChazzMatt said:
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Click to expand...
Click to collapse
Ahh thank you for explaining this. I imported mine from Hong Kong. As far as I know it was never sold new in AU.
I'm about to rush off to work for the day so I will have to try this when I get home tonight and let you know how it goes. Thank you so much for the detailed and fast response! This is much more than I was hoping for!
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Wibble Wobble said:
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Click to expand...
Click to collapse
Yes, I would do that.
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Wibble Wobble said:
As far as I know it was never sold new in AU.
Click to expand...
Click to collapse
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
ChazzMatt said:
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
Click to expand...
Click to collapse
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Redline said:
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Click to expand...
Click to collapse
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Wibble Wobble said:
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Click to expand...
Click to collapse
I could kind of answer is the question of if the hardware is otherwise the same, the rest might be a question for ChazzMatt.
AFAIK the modem on my H930DS was the same as other similar models, similar to the V20 you can flash a KDZ from another region if you wanted to (to for example, get less bloat or better coverage on a band you rely on for service). I remember on my V20 the region that had Claro-carrier firmware came with the least bloat out of the box vs other regions, but we also had KDZ Writer with the V20 that allowed us to flash specific parts of the KDZ *in* TWRP on the device itself, so you could have, say, Claro firmware with the AU modem.
As for what IMEIs do, they're similar to the MAC address on a piece of networking gear; it's a globally-unique identifier specific to your device, you can put it into IMEI lookup websites to get information about manufacture date, model etc.
If you have a carrier-model phone, they can also block your IMEI on their network if it is stolen and then attempted to be re-used.
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Wibble Wobble said:
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Click to expand...
Click to collapse
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
ChazzMatt said:
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
Click to expand...
Click to collapse
Out of frustration I started doing random things just to test there effect, much of it being in the hidden menu where I discovered VoLTE settings. Nothing was working until... I force stopped the carrier service and made a phone call. Presto! VoLTE now appears (though not listed under any setting in mobile networks, or in the drop down menu) and my calls say HD call. Finally to confirm 4G remains active and still works during a call!

SM-G965U1 - leaving AT&T - How to remove AT&T Bloatware / Image? Reset?

I bought an SM-G965U1 when they were first released. I was on the AT&T network, and their bloated image was installed. I'm switching to Xfinity - I have the SIM, and I am making the switch shortly. (Hoping for a reply / replies first.).
I want to get rid of the AT&T bloatware and restore the Samsung image. Is this as simple as performing a reset?
Is there an easier or better way?
Is it possible to install a different image altogether, or am I screwed by knox?
I'll remove my SD card and backup my files in advance, of course.
Thanks in advance!
Interesting, upon SIM card change, the AT&T software was removed. So, questions one and two have been self-answered.
Concerning ROMs, I have a Snapdragon processor, I presume, living in the USA. I'm a neophyte concerning mobile phone ROMs, but I do have some Linux experience (RHEL and various desktop distros.)
I have an old Note 3 to play with, are there ROMs for that so I can "practice"? I'd hate to brick my primary phone.
Cheers!
With the S9+ in the US, they're all the exact same hardware as far as I know. With patched Odin you can basically flash any stock firmware from any US carrier you want, so long as it's the same bootloader version (of the last 5 characters of your current version, it should be a number, and then other characters). If you're on the most recent update, it would likely be bootloader v7. My phone was purchased as an unlocked ATT device, but I flashed the US Unlocked version (XAA) which is the version that unbranded Samsung devices have. It's fully functional and there's zero carrier bloat. OTAs work and everything else as if it was that model originally.
But I guess the big question is why flash to something else if the bloat was auto removed? What's your current version?
Edit after reading again: the U1 software is the Samsung Unbranded firmware. Interesting that the seller put it on there already. So TLDR; you shouldn't need to do anything. Generally branded models wouldn't just remove their bloat when you change carriers (the S8 being an exception I believe), but it appears the unbranded version does to some extent.
Jessooca said:
Use the latest Odin: https://dl2018.sammobile.com/Odin3-v3.13.3.zip
--in CSC slot use CSC not home, and you will lose everything on your phone. If you don't want to do that, use Home in CSC.
Flash the latest U1 (unlocked variant Snapdragon version) firmware in Odin. Download it via Frija
*RUN AS ADMIN, in model it's SM-G965U1 CSC use XAA and be sure "auto" is Checked.
Frija: https://forum.xda-developers.com/attachment.php?attachmentid=4886005&d=1574653611
That's it. Use any carrier you want without issues.
Click to expand...
Click to collapse
Thank you, Jessooca. I may give this a shot next weekend. At the moment everything appears to be working properly, although it's slow.
ReapersDeath said:
With the S9+ in the US, they're all the exact same hardware as far as I know. With patched Odin you can basically flash any stock firmware from any US carrier you want, so long as it's the same bootloader version (of the last 5 characters of your current version, it should be a number, and then other characters). If you're on the most recent update, it would likely be bootloader v7. My phone was purchased as an unlocked ATT device, but I flashed the US Unlocked version (XAA) which is the version that unbranded Samsung devices have. It's fully functional and there's zero carrier bloat. OTAs work and everything else as if it was that model originally.
But I guess the big question is why flash to something else if the bloat was auto removed? What's your current version?
Edit after reading again: the U1 software is the Samsung Unbranded firmware. Interesting that the seller put it on there already. So TLDR; you shouldn't need to do anything. Generally branded models wouldn't just remove their bloat when you change carriers (the S8 being an exception I believe), but it appears the unbranded version does to some extent.
Click to expand...
Click to collapse
Yeah, I was surprised when I saw it happening. Happy too! Not only did it remove the AT&T crap, but it also restored some of the hidden Samsung apps, such as the Galaxy sensors and action dash that were hidden by AT&T.
I'm not sure which version you're asking about.
Kernel version is 4.9.112-17018887 (November update)
Baseband version is G965U1UEU7CSK1
Knox is at 3.2.1 API level 27, and TIMA is 4.0.0
Build number is PPR1.180610.011.G965U1EU7CSK1
Then there is a "Service provider SW version"which is about 50 characters in length and ends in 443098 CCT/CCT/XAA
Lastly, there's a Security software version which is 9 lines in length but ends with SMR Nov-2019 Release 1.
I appreciate your reply. As I said, I am a neophyte concerning smart phones, but I am interested in learning more since I retired a few weeks ago and have more free time now.
HyperPete said:
Yeah, I was surprised when I saw it happening. Happy too! Not only did it remove the AT&T crap, but it also restored some of the hidden Samsung apps, such as the Galaxy sensors and action dash that were hidden by AT&T.
I'm not sure which version you're asking about.
Kernel version is 4.9.112-17018887 (November update)
Baseband version is G965U1UEU7CSK1
Knox is at 3.2.1 API level 27, and TIMA is 4.0.0
Build number is PPR1.180610.011.G965U1EU7CSK1
Then there is a "Service provider SW version"which is about 50 characters in length and ends in 443098 CCT/CCT/XAA
Lastly, there's a Security software version which is 9 lines in length but ends with SMR Nov-2019 Release 1.
I appreciate your reply. As I said, I am a neophyte concerning smart phones, but I am interested in learning more since I retired a few weeks ago and have more free time now.
Click to expand...
Click to collapse
Baseband told me enough. You're already on the USA Unlocked version that phones bought straight from Samsung has. It has no carrier specific bloat.
My main question is still what your intentions are? You're already on the most neutral party software for the US and shouldn't have any issues. So I'm not sure what you would want to flash now.
SMG965U1 is what you're on. The carrier versions are just SMG965U (no 1 after the model)
ReapersDeath said:
Baseband told me enough. You're already on the USA Unlocked version that phones bought straight from Samsung has. It has no carrier specific bloat.
My main question is still what your intentions are? You're already on the most neutral party software for the US and shouldn't have any issues. So I'm not sure what you would want to flash now.
SMG965U1 is what you're on. The carrier versions are just SMG965U (no 1 after the model)
Click to expand...
Click to collapse
I considered playing with ROMs. However, I may just buy a used pixel for that. What I would really like is to be able to root it so I can run Titanium Backup and move apps to the SD card. I have not even tried since changing carriers. Perhaps I don't need root on the unlocked version.
HyperPete said:
I considered playing with ROMs. However, I may just buy a used pixel for that. What I would really like is to be able to root it so I can run Titanium Backup and move apps to the SD card. I have not even tried since changing carriers. Perhaps I don't need root on the unlocked version.
Click to expand...
Click to collapse
I've debated manyyyy times to root just for titanium backup, but losing some Samsung features for it isn't worth it.
Before reflashing, I used the built in Samsung backup (in Settings), and it did surprisingly well. It's like titanium backup in the sense it backs up app data just as you had it originally, but not for everything. Apparently it's dependent on the app developer to allow data to be backed up. So for a lot of stuff, it was like I never wiped my phone, but some of it I had to set up again. And it was all through the cloud which is nice.
ReapersDeath said:
I've debated manyyyy times to root just for titanium backup, but losing some Samsung features for it isn't worth it.
Before reflashing, I used the built in Samsung backup (in Settings), and it did surprisingly well. It's like titanium backup in the sense it backs up app data just as you had it originally, but not for everything. Apparently it's dependent on the app developer to allow data to be backed up. So for a lot of stuff, it was like I never wiped my phone, but some of it I had to set up again. And it was all through the cloud which is nice.
Click to expand...
Click to collapse
I will give that a shot. Thanks for the suggestion!

need instruction on career switching

hi i have a verizon tab s6 sm-t867v(lte version) the stock rom does not let you use phone app to do calls and messages app dont work. all the calls or messages should go throug the verizon propritory messages+ app ,where you need to add verizon number. . and the tablet is unlocked to any career. . I DONT WANT TO ROOT THE DEVICE. i did a career switch for my note 8 from att to tmobile without rooting so i thought i can do the same to tab s6. i have few questions
1. is there a way i can swap for another career rom
2. can i flash international rom just throug odin so that i dont deal with verizon bloatware.
can any one point me to the files and the thread.
is there a way i can use calling and texting on without going throug messages+ app. thanks for the help in advance. i am sorry if anythin i ask is silly. peace
shiva49 said:
hi i have a verizon tab s6 sm-t867v(lte version) the stock rom does not let you use phone app to do calls and messages app dont work. all the calls or messages should go throug the verizon propritory messages+ app ,where you need to add verizon number. . and the tablet is unlocked to any career. . I DONT WANT TO ROOT THE DEVICE. i did a career switch for my note 8 from att to tmobile without rooting so i thought i can do the same to tab s6. i have few questions
1. is there a way i can swap for another career rom
2. can i flash international rom just throug odin so that i dont deal with verizon bloatware.
can any one point me to the files and the thread.
is there a way i can use calling and texting on without going throug messages+ app. thanks for the help in advance. i am sorry if anythin i ask is silly. peace
Click to expand...
Click to collapse
Yes you can switch the firmware on the sm-t867v from Verizon to TMobile or Sprint. It keeps the bootloader locked down so root is still impossible but since you are not looking to root it just switching the firmware version should work just fine. I personally have metro pcs and their $15 unlimited tablet data plan on mine and I switched my firmware to TMobile so I could pick up the LTE bands it would not connect to with the Verizon firmware. All you need to do is download the modified Odin 3.14 and the firmware of the carrier you wish to switch to. It HAS to have the same base model. For example I went from the SM-T867V firmware and flashed the SM-T867U firmware to the device. So your firmware choice absolutely MUST have the SM-T867 in the beginning of it. Any other firmware will most likely brick your device if Odin even allows it to flash. The thing that makes the difference between Verizon and TMobile is the user userdata file. You must flash it with the rest of the firmware files, So BL, AP, CP, CSC, and Userdata. Don't worry, the stock firmware will come with the userdata file. Also its best that you don't flash the CSC-Home file but flash the regular CSC file as the home one will not delete your data and its probably best to do a full wipe when switching firmwares, so make sure you back up anything you don't wish to lose. When the flashing is finished it will boot and instead of the white screen with big red circle for Verizon you will get a pink TMobile screen and it will be model SM-T867U now. All OTA updates will still work without problem and you will get a functional dial pad which works for all the secret menus and all that fun stuff. BTW, I take absolutely no responsibility if for some reason it messes up or bricks your tab s6 lte. Goodluck and enjoy your non Verizon tablet.
Tofor said:
Yes you can switch the firmware on the sm-t867v from Verizon to TMobile or Sprint. It keeps the bootloader locked down so root is still impossible but since you are not looking to root it just switching the firmware version should work just fine. I personally have metro pcs and their $15 unlimited tablet data plan on mine and I switched my firmware to TMobile so I could pick up the LTE bands it would not connect to with the Verizon firmware. All you need to do is download the modified Odin 3.14 and the firmware of the carrier you wish to switch to. It HAS to have the same base model. For example I went from the SM-T867V firmware and flashed the SM-T867U firmware to the device. So your firmware choice absolutely MUST have the SM-T867 in the beginning of it. Any other firmware will most likely brick your device if Odin even allows it to flash. The thing that makes the difference between Verizon and TMobile is the user userdata file. You must flash it with the rest of the firmware files, So BL, AP, CP, CSC, and Userdata. Don't worry, the stock firmware will come with the userdata file. Also its best that you don't flash the CSC-Home file but flash the regular CSC file as the home one will not delete your data and its probably best to do a full wipe when switching firmwares, so make sure you back up anything you don't wish to lose. When the flashing is finished it will boot and instead of the white screen with big red circle for Verizon you will get a pink TMobile screen and it will be model SM-T867U now. All OTA updates will still work without problem and you will get a functional dial pad which works for all the secret menus and all that fun stuff. BTW, I take absolutely no responsibility if for some reason it messes up or bricks your tab s6 lte. Goodluck and enjoy your non Verizon tablet.
Click to expand...
Click to collapse
Followed instruction and successfully changed from V to T-mobile. Thankyou!
geoffwdixon said:
Followed instruction and successfully changed from V to T-mobile. Thankyou!
Click to expand...
Click to collapse
I'm glad it worked for you without any major issues. This was the first thread I've given any real instruction on. Hope your tab continues to work perfectly. I broke the screen on mine so the only thing it's really used for is an android PC. Thank God for the Tab S6`s ability to output video so easily and the Samsung DEX software.

Categories

Resources