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.
Related
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Looking at the CSCVersion.txt File inside the ZIP shows that this is G930AATT4APJ4 for anyone wondering which version
elijahblake said:
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Click to expand...
Click to collapse
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
thelostsoul said:
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
Click to expand...
Click to collapse
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
KingOfTheNet said:
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
Click to expand...
Click to collapse
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
Most likely be Spring with AT&T and their release record.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
It's fine, I just flashed it to mine and it's just a security patch for MM. I will capture the official Nougat FOTA release once it comes out.
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Omar04 said:
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Click to expand...
Click to collapse
One issue with that... qa6 is feb update...
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Added screenshot
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Yeap it doesnt apply for Beta they are always ahead of time only official releases match. (There's always that one build that wants to break the rules, but only happen with unreleased builds mostly because they apply the security patch early for testing and compiler gives that build code.)
It always has been that way with Samsung since the OG Galaxy S.
Check my posts from several years ago on earlier galaxies and you'll notice.
KingOfTheNet said:
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
Click to expand...
Click to collapse
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
There was no compiling. You can flash the ota update files from stock recovery after renaming the file name extension from .cfg to .zip.
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
I didn't flash the update file itself, I had the ODIN files for it. They're the same thing.
When it comes to official updates, no signature modification should be necessary (Or possible, for that matter. I don't think there's a way to modify the signature. If there is, I don't know about it.). The only thing different between the 2 files is the file format.
Hope I answered your questions.
Cheers!
Can You Supply the Latest FOTA roms For.
G930AUCU4BQK2
G930AUCS4BQJ2
G930AUCS4BQH1
I have an Unlocked G930A (not really unlocked just using a cricket SIM) But I cannot Get the Software Updates For it because of AT&T. I have seen the information on reflashing it to the U software but i really dont want to have to restore everything to my phone unless i have to..
The Version currently running on my phone is vulnerable to the bluebourne exploit and im trying to get that patched. :/
On a side note. are you able to do a packet capture while scanning for the updates? There is one on the play store that will also let you perform a MITM on the application and you should be able to capture anything sent over SSL in plain text/hex/etc
I did Want to Ask you a quick question. How did you capture the FOTA package to begin with?
I wonder if it is possible to setup an Authoritative only dns server and then use it to spoof the location of the update servers. to create a DNS method that would allow the FOTA to be pushed to devices no longer on AT&T
Anywho if you can get those firmwares and get me full packet captures of just the update application while it is checking and downloading the update, i might be able to create a web application that is able to capture the headers sent by the phone that identify its model/fw version/etc and be able to push the firmware update Via the built in option in the settings, (although you may need to swap your dns settings for a moment and install a CA cert that allows validation of a connection. im not too sure if a CA cert will need to be installed because im not sure if they push the updates over a SSL/TLS connection. Using the data collected here may also pave the way to enable this to work with other models and carriers and manufacturers. (my hypothesis is that packet captures would be needed on any firmware updates "you" would want to push with this)
Basically Im thinking it might be possible to download those zip files along with the packet capture data to create a simple web application that is able to tell the phone there is a software update available. It would require using a 3rd party DNS server to "redirect" the connection to a server that doesnt care if your an at&t customer. It might also need a self signed CA cert installed into the device to Validate TLS/SSL. From there it might be possible to have the server 301 redirect the zipfile to another url that is behind a CDN to reduce the risk of ddos and keep the server(s) stable keeping the downloads reliable and fast.
Seeing how the Firmware update is already digitally signed by Samsung and/or AT&T it should probably install without an issue. I dont see the possibility of the wrong stock firmware being flashed on the wrong phone provided the manufactuer had a proper assert statement in place to verify the model and sw/hw versions, and im pretty sure a stock recovery wont accept a firmware signed by any key.
I might be Going off topic here, But one more question.
Do i actually need AT&T service to download the OTA updates from the Software update function in the phone settings.
What i mean by this is does the SIM card need to have an active plan on it? or can it just be provisioned to their network with out a phone plan and downloaded over wifi?
UPDATE: It Can Now be officially confirmed that Carriers and Samsung Deliberately block OTA updates when you unlock the device. there are thousands if not tens of thousands out there on a variety of devices as far back as the S4 that may not have been able to get updates. just because they used a Cricket Sim or unlocked the device. I also Spoke with AT&T customer support today and got told the blatant Lie that they push the same OTA updates through the cricket network to ensure that AT&T devices on it can be updates. I also went to samsung service center at bestbuy and they told me my phone was up to date when its not. Samsung Smart Switch Also Reports that my device is up to date when i know for a 900% fact it is not.
So it looks like Someone is going to have to write an app that Hijacks the Requests and replays a valid packet capture just to get the phone to update in its orignial intended built in method.
The sad part is the carriers would see this and just write a patch to prevent it rather then change their policies.
Basically The carrier has the right to deny you a software update because you left their network and leave you exposed to Critical Security Vulnerabilities.
That is their way of sticking up their Middle Finger at the FCC for mandating carriers unlock their devices and the end user who either met his/her contract obligation or outright paid for his/her device
[SARCASM] basically its like saying hey we know you paid for your device, but **** you, you left our network and even though the updates come from a samsung controlled server were going to ensure our middleware deliberately blocks your device from updating so you remain vulnerable and you information is stolen, That'l teach you for unlocking your device and leaving our network because we charge literally an arm and leg for service, how dare you as a customer go against our big monopoly that seeks to buy out every major ISP and cable provider in america but hey thats alright were still winning but because you left our network we will block these updates so we can further Sell your information and viewing browsing habits off to the NSA (Google TITANPOINTE tinfoil hatters!!!!) unless you want to send your phone off to one of our service centers where one of our butthurt technicians will see you rooted your phone and say it has damage and turn our free reflashing service into a paid repair and charge you through the ass for service, also did we mention were not going to update the software because our application is designed not to tell you there is an update available if you unlocked it or used our Subsidary cricket SIM in the device and didnt unlock it Or you can go on XDA and grab an odin package an potentially invalidate your warranty and then when your device comes to us for a cracked screen we can deny you the repair even though the modifcation wasnt a modifcation and has nothing to do with a cracked screen. [/SARCASM]
Anywho im going to Bite the Bullet and Grab an Assortment of AT&T contract Sims and Go Phone sims and Other Carriers, Im going to go to the local pawn shops and buy an assortment of devices and attempt to downgrade each and every single one of them back to their old original firmware versions, Dump all the FOTA updates and dump the packet captures and i guess i will have to research the possibility And be that asshole who gets sued for reverse engineering their software.
Hey guys,
Bought the galaxy s8 plus from a store thinking it was factory unlocked version directly from samsung, but it wasnt. Its the unlocked sprint version based on the radio, and it had a tmobile app or two already installed. I am using AT&T and would like to change the carrier to at&t so that I can get a few features for at&t (Mainly being able to send mms while on wifi). I updated to the latest online update (which im guessing i shouldnt have) and i would like to know if its possible to easily change the carrier still, and or if i can downgrade safely to change the carrier. If so, what files are the latest that I can get the ball rolling with? Using the AT&T version is completely fine.
I came across this youtube video that shows how to easily change carrier without flashing: https://www.youtube.com/watch?v=msAHhCVF-F8
Basically i am a bit lost and would like to know if anyone can help at this point. Here are my software information:
Bootloader Version: G955USQU1AQGL
Build number NRD90M.G955USQU1AQGL
Active CSC Code: XAS
Please advise, thanks guys!
jxs714 said:
Hey guys,
Bought the galaxy s8 plus from a store thinking it was factory unlocked version directly from samsung, but it wasnt. Its the unlocked sprint version based on the radio, and it had a tmobile app or two already installed. I am using AT&T and would like to change the carrier to at&t so that I can get a few features for at&t (Mainly being able to send mms while on wifi). I updated to the latest online update (which im guessing i shouldnt have) and i would like to know if its possible to easily change the carrier still, and or if i can downgrade safely to change the carrier. If so, what files are the latest that I can get the ball rolling with? Using the AT&T version is completely fine.
I came across this youtube video that shows how to easily change carrier without flashing: https://www.youtube.com/watch?v=msAHhCVF-F8
Basically i am a bit lost and would like to know if anyone can help at this point. Here are my software information:
Bootloader Version: G955USQU1AQGL
Build number NRD90M.G955USQU1AQGL
Active CSC Code: XAS
Please advise, thanks guys!
Click to expand...
Click to collapse
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Sorry, double post. Final below
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Hey my friend,
Thanks so much for reaching back with an update and for the support! Awesome! So, youre 100% sure downgrade procedure wont brick the device? Also, do you know if this will this trip knox? Last question: do you think this will solve the red tint on the edges of the phone? I heard this was supposedly a software issue, not hardware.
jxs714 said:
Hey my friend,
Thanks so much for reaching back with an update and for the support! Awesome! So, youre 100% sure downgrade procedure wont brick the device? Also, do you know if this will this trip knox? Last question: do you think this will solve the red tint on the edges of the phone? I heard this was supposedly a software issue, not hardware.
Click to expand...
Click to collapse
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
kleen3r said:
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
Click to expand...
Click to collapse
Hey Kleen3r,
Thanks for the update and support. Looks great. Going to try the downgrade and possibly also the link sent and reach back with an update in a few hours
kleen3r said:
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
Click to expand...
Click to collapse
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Ok, so I tried it and with the unbranded XAA version and I am getting a "FAIL! Model dismatch fail" in odin. Even tried renaming files to tar and removing md5 at the end.
I also noticed that when in download mode, there are no green words going across the screen like I see in youtube videos who get it after they connect it. Could it be i do not have specific drivers installed? I installed the samsung usb drivers.
EDIT: Scratch that, the odin PrinceComsy version (Has to have the banner at the top) seems to be working fine. I am currently flashing
jxs714 said:
Ok, so I tried it and with the unbranded XAA version and I am getting a "FAIL! Model dismatch fail" in odin. Even tried renaming files to tar and removing md5 at the end.
I also noticed that when in download mode, there are no green words going across the screen like I see in youtube videos who get it after they connect it. Could it be i do not have specific drivers installed? I installed the samsung usb drivers.
Click to expand...
Click to collapse
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Edif: Response below
kleen3r said:
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Click to expand...
Click to collapse
Awesome. ok, so i got it to work. But now when i reflash the rom back for sprint, the splash screen is stuck to AT&T and does not remove or go unbranded no matter what i do. It even has bloatware for att when the system starts. I never flashed att rom, only sprint unbranded XAS, not sure how this is happening. How can i get unlocked gsm and cdma back unbranded for sprint? I even formatted everything and flashed the user data, still the same. Its weird
Also, I am flashing it back to return the phone to store the way I received it. This red tint is just unacceptable.
jxs714 said:
Awesome. ok, so i got it to work. But now when i reflash the rom back for sprint, the splash screen is stuck to AT&T and does not remove or go unbranded no matter what i do. It even has bloatware for att when the system starts. I never flashed att rom, only sprint unbranded XAS, not sure how this is happening. How can i get unlocked gsm and cdma back unbranded for sprint? I even formatted everything and flashed the user data, still the same. Its weird
Also, I am flashing it back to return the phone to store the way I received it. This red tint is just unacceptable.
Click to expand...
Click to collapse
You need to flash the XAA not XAS U1 firmware.
kleen3r said:
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Click to expand...
Click to collapse
kleen3r said:
You need to flash the XAA not XAS U1 firmware.
Click to expand...
Click to collapse
Hey man, thanks for the update. So I should flash XAA to change splash screen to samsung and be able to have both sprint cdma and all bands of gsm enabled again?
jxs714 said:
Hey man, thanks for the update. So I should flash XAA to change splash screen to samsung and be able to have both sprint cdma and all bands of gsm enabled again?
Click to expand...
Click to collapse
Yes that firmware is unbranded. The CSC from XAA will automatically detect your carrier's sim and use that network.
kleen3r said:
Yes that firmware is unbranded. The CSC from XAA will automatically detect your carrier's sim and use that network.
Click to expand...
Click to collapse
Hey man,
Thanks for this! Also, do you know if it will allow you to choose cdma as an option as well?
jxs714 said:
Hey man,
Thanks for this! Also, do you know if it will allow you to choose cdma as an option as well?
Click to expand...
Click to collapse
Yes it will.
kleen3r said:
Yes it will.
Click to expand...
Click to collapse
Ok, so just tried it and the sprint CDMA is no longer available in the Mobile Networks menu., only the following:
Mobile Data
International Data Roamin
Disable 2G
Access Point Names
Network Operators (AT&T underneath)
There is no option to choose CDMA like there was before I just firmware changed. The XAS firmware that I had offered the option to choose automatic, LTE/3G, CDMA. Now its gone from the menu after the XAA flash.
jxs714 said:
Ok, so just tried it and the sprint CDMA is no longer available in the Mobile Networks menu., only the following:
Mobile Data
International Data Roamin
Disable 2G
Access Point Names
Network Operators (AT&T underneath)
There is no option to choose CDMA like there was before I just firmware changed. The XAS firmware that I had offered the option to choose automatic, LTE/3G, CDMA. Now its gone from the menu after the XAA flash.
Click to expand...
Click to collapse
I don't understand. Who is your carrier?
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
kleen3r said:
I don't understand. Who is your carrier?
Click to expand...
Click to collapse
Edit: Download Shortcut Master and open Preconfig. It will let you pick your carrier.
kleen3r said:
I don't understand. Who is your carrier?
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
Edit: Download Shortcut Master and open Preconfig. It will let you pick your carrier.
Click to expand...
Click to collapse
Hey bud,
Thanks for this. My actual carrier is AT&T, but id like to keep the option of having CDMA available if I ever decide to go with sprint. I have the app installed, When i tried to launch Preconfig (com.sec.android.Preconfig.Preconfig) and it gives an error "su: not found"
jxs714 said:
Hey bud,
Thanks for this. My actual carrier is AT&T, but id like to keep the option of having CDMA available if I ever decide to go with sprint. I have the app installed, When i tried to launch Preconfig (com.sec.android.Preconfig.Preconfig) and it gives an error "su: not found"
Click to expand...
Click to collapse
Forgot you have to be rooted use the app. There's an adb command you can use instead. Just do a search in xda for preconfig carrier switch.
I flashed my spring s8 plus with Odin and now I can't get it to read my sim at all ,says will not register on network , where the carrier usually is it says 12345 , I've tried to flash back to stock and nothing works ...im at a loss this is my only phone ,I've tried to do a stock reflash and still nothing , I even did a emergency recovery through smart switch and still ...please help
Does anyone have an idea when the unlocked US models will be getting the Pie update? I'm on Sprint if that makes a difference. Kind of sucks that everyone is getting the updates but unlocked phones are not.
Sent from my SM-G965U1 using Tapatalk
Sprint has already rolled out the carrier locked update. The u1 should be rolling out in the next day or two.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
I'm in the same boat. I'm with an mnvo and I have to stay on u1 firmware to retain VoLTE as they block simultaneous calls and data on BYOP plans.
For some reason u1 stayed on ark5 for me with Nov 1 patch. I have att phone where I loaded u1 before. No further updates. I saw posts that u1 has dec patch. Am I missing something?
I'm also waiting for ota to see when it hits my phone. Not in a hurry.
Hangoverr said:
For some reason u1 stayed on ark5 for me with Nov 1 patch. I have att phone where I loaded u1 before. No further updates. I saw posts that u1 has dec patch. Am I missing something?
I'm also waiting for ota to see when it hits my phone. Not in a hurry.
Click to expand...
Click to collapse
That's because the AT&T devices are locked. You can flash u1 firmware all day long, but you can't change the locked CSC (where the device looks for software updates). The phone is looking for u1 firmware from a carrier that doesn't provide firmware for the U1. If the device is paid off, ask AT&T to remove the Sim lock on the phone. You maybe able to change CSC forcibly, but I think you may trip the Knox counter.
hyperblu said:
That's because the AT&T devices are locked. You can flash u1 firmware all day long, but you can't change the locked CSC (where the device looks for software updates). The phone is looking for u1 firmware from a carrier that doesn't provide firmware for the U1. If the device is paid off, ask AT&T to remove the Sim lock on the phone. You maybe able to change CSC forcibly, but I think you may trip the Knox counter.
Click to expand...
Click to collapse
It was already unlocked which is how I was using it on T-Mobile. I did a weird thing in December. I updated to android pie beta and due to some issues with apps I tried reverting back to Oreo. But I did multiple tries using odin and didn't work. Then I read through online and found that to go from pie beta to Oreo we have to downgrade using samsung switch as bootloader is different. That's when things might have been messed up. Any suggestions or thoughts on how I can get it back to pure u1 with updates?
Attached my current software details
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
Edit: I see your screenshot. What is sticking out at me is your CSC. I see ATT/ATT/TMB. I'm not seeing XAA like an unlocked phone would have. If I'm not mistaken, once you attach your phone to ATT or TMB, you essentially lock your CSC to their network.
When you flashed back to u1 firmware from the pie beta, you didn't use Odin, correct? If you didn't use Odin. I don't think smart switch will reset your CSC to XAA.
My best advice would be to download the U1 ARL1 Odin firmware files and flash the CSC (Not HOME_CSC). You will have to wipe your phone, but that will put you to the latest U1 firmware and back to unlocked CSC and will point it in the right direction for future OTA updates.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Just an FYI, I flashed my phone from the pie beta to the U1 ARL1 odin file with no issues. Today I flashed my other s9 plus from brk2 (carrier) to u1 and had ODIN give me some fuss using the same method/firmware I used on my other phone. If Odin is failing, put the phone in download mode and connect it to ODIN, loaded and ready to flash... Hold power, volume down, and bixby until the phone reboots back into download mode, ODIN will connect again, unplug the phone and plug it back in, THEN flash. It's an odd sequence, but it works.
hyperblu said:
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
Edit: I see your screenshot. What is sticking out at me is your CSC. I see ATT/ATT/TMB. I'm not seeing XAA like an unlocked phone would have. If I'm not mistaken, once you attach your phone to ATT or TMB, you essentially lock your CSC to their network.
When you flashed back to u1 firmware from the pie beta, you didn't use Odin, correct? If you didn't use Odin. I don't think smart switch will reset your CSC to XAA.
My best advice would be to download the U1 ARL1 Odin firmware files and flash the CSC (Not HOME_CSC). You will have to wipe your phone, but that will put you to the latest U1 firmware and back to unlocked CSC and will point it in the right direction for future OTA updates.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Just an FYI, I flashed my phone from the pie beta to the U1 ARL1 odin file with no issues. Today I flashed my other s9 plus from brk2 (carrier) to u1 and had ODIN give me some fuss using the same method/firmware I used on my other phone. If Odin is failing, put the phone in download mode and connect it to ODIN, loaded and ready to flash... Hold power, volume down, and bixby until the phone reboots back into download mode, ODIN will connect again, unplug the phone and plug it back in, THEN flash. It's an odd sequence, but it works.
Click to expand...
Click to collapse
Thank you for detailed explanation and questions.
My phone is originally att which will be u device. If you remember or heard of it, back in April we had att phones in Samsung site for 650$ and that's where I bought it. I was never on att Network so I submitted for unlock and meanwhile installed u1 from xda
then I unlocked and used tmobile sim. It always got ota as expected. In November I signed up for Samsung pie beta and then did an ota to pie.
When I wanted to revert back, I downloaded latest u1 and installed through odin it didn't boot up. Then I tried multiple versions and didn't work. I again installed pie beta using odin from xda. Then I was able to boot it up again. That's when reading online and xda I think but don't recall exactly where I got suggestion to use smart switch to downgrade to Oreo. I think it took me to att version Oreo as my imei is for att phone. Then I again downloaded u1 from xda and installed.
Hopefully I was clear in explaining what I did. I can try arl1 and install csc. I'm ok with user data loss as I don't really have many apps or data. But can I install csc for my current ark5 and see if that gives me ota for arl1? I'm assuming arl1 is latest Oreo for s9 plus u1.
Thanks for your help.
hyperblu said:
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
I've never hear of needing to use smart switch to jump bootloaders as I don't think that's even possible on a locked bootloader. Once the bootloader changes, there is no going back.
So was your phone originally a U1 device or a U? What firmware are you currently on?
Edit: I see your screenshot. What is sticking out at me is your CSC. I see ATT/ATT/TMB. I'm not seeing XAA like an unlocked phone would have. If I'm not mistaken, once you attach your phone to ATT or TMB, you essentially lock your CSC to their network.
When you flashed back to u1 firmware from the pie beta, you didn't use Odin, correct? If you didn't use Odin. I don't think smart switch will reset your CSC to XAA.
My best advice would be to download the U1 ARL1 Odin firmware files and flash the CSC (Not HOME_CSC). You will have to wipe your phone, but that will put you to the latest U1 firmware and back to unlocked CSC and will point it in the right direction for future OTA updates.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Just an FYI, I flashed my phone from the pie beta to the U1 ARL1 odin file with no issues. Today I flashed my other s9 plus from brk2 (carrier) to u1 and had ODIN give me some fuss using the same method/firmware I used on my other phone. If Odin is failing, put the phone in download mode and connect it to ODIN, loaded and ready to flash... Hold power, volume down, and bixby until the phone reboots back into download mode, ODIN will connect again, unplug the phone and plug it back in, THEN flash. It's an odd sequence, but it works.
Click to expand...
Click to collapse
Thanks for all the feedback. I am on Sprint ad I have the U1. Do I have to worry about not being able to get the Pie update? I am on the Dec security patch so it does update.
Sent from my SM-G965U1 using Tapatalk
netengineer said:
Thanks for all the feedback. I am on Sprint ad I have the U1. Do I have to worry about not being able to get the Pie update? I am on the Dec security patch so it does update.
Sent from my SM-G965U1 using Tapatalk
Click to expand...
Click to collapse
You should get the official unlocked pie update from Samsung once it's released. If you were to flash the g965u firnware with Sprint userdata, you would receive the pie official w/carrier bloat that is currently being pushed right now.
hyperblu said:
You should get the official unlocked pie update from Samsung once it's released. If you were to flash the g965u firnware with Sprint userdata, you would receive the pie official w/carrier bloat that is currently being pushed right now.
Click to expand...
Click to collapse
So... Should I just wait or flash g656u? I can wait, but getting a whole new build is like Christmas for me. Lol
Thanks for your reply.
Sent from my SM-G965U1 using Tapatalk
Hangoverr said:
Thank you for detailed explanation and questions.
My phone is originally att which will be u device. If you remember or heard of it, back in April we had att phones in Samsung site for 650$ and that's where I bought it. I was never on att Network so I submitted for unlock and meanwhile installed u1 from xda
then I unlocked and used tmobile sim. It always got ota as expected. In November I signed up for Samsung pie beta and then did an ota to pie.
When I wanted to revert back, I downloaded latest u1 and installed through odin it didn't boot up. Then I tried multiple versions and didn't work. I again installed pie beta using odin from xda. Then I was able to boot it up again. That's when reading online and xda I think but don't recall exactly where I got suggestion to use smart switch to downgrade to Oreo. I think it took me to att version Oreo as my imei is for att phone. Then I again downloaded u1 from xda and installed.
Hopefully I was clear in explaining what I did. I can try arl1 and install csc. I'm ok with user data loss as I don't really have many apps or data. But can I install csc for my current ark5 and see if that gives me ota for arl1? I'm assuming arl1 is latest Oreo for s9 plus u1.
Thanks for your help.
Click to expand...
Click to collapse
I believe when the CSC is changed, it must be pushed with the bootloader, AP and everything else when using ODIN. It still wouldn't hurt to push the ARL1 firmware w/CSC to it and wait to hear when the official unlocked pie is available via OTA to make sure you're able to get the OTA push. And yes, ARL1 is the unlocked U1 final Oreo fw.
Also, when you flashed to the pie beta, were you using the official z builds or the leaked "c" carrier builds? That might explain why you had issues flashing back
---------- Post added at 04:22 PM ---------- Previous post was at 04:08 PM ----------
netengineer said:
So... Should I just wait or flash g656u? I can wait, but getting a whole new build is like Christmas for me. Lol
Thanks for your reply.
Sent from my SM-G965U1 using Tapatalk
Click to expand...
Click to collapse
Personally, I would wait. The unlocked build will be pushed in the next day or two once the majority of the carriers have pushed it. The only benefit you would gain from going ahead and flashing it would be to get carrier specific features like WiFi calling, but that also comes with the carrier bloat. Most carrier specific apps can be had from the play store anyway.
hyperblu said:
I believe when the CSC is changed, it must be pushed with the bootloader, AP and everything else when using ODIN. It still wouldn't hurt to push the ARL1 firmware w/CSC to it and wait to hear when the official unlocked pie is available via OTA to make sure you're able to get the OTA push. And yes, ARL1 is the unlocked U1 final Oreo fw.
Also, when you flashed to the pie beta, were you using the official z builds or the leaked "c" carrier builds? That might explain why you had issues flashing back
Click to expand...
Click to collapse
First pie beta was ota. Second one I believe it is c but don't recall exactly. I will try flashing arl1 and will see how it goes. Any suggestions on where to get it?
Hangoverr said:
Thank you for detailed explanation and questions.
My phone is originally att which will be u device. If you remember or heard of it, back in April we had att phones in Samsung site for 650$ and that's where I bought it. I was never on att Network so I submitted for unlock and meanwhile installed u1 from xda
then I unlocked and used tmobile sim. It always got ota as expected. In November I signed up for Samsung pie beta and then did an ota to pie.
When I wanted to revert back, I downloaded latest u1 and installed through odin it didn't boot up. Then I tried multiple versions and didn't work. I again installed pie beta using odin from xda. Then I was able to boot it up again. That's when reading online and xda I think but don't recall exactly where I got suggestion to use smart switch to downgrade to Oreo. I think it took me to att version Oreo as my imei is for att phone. Then I again downloaded u1 from xda and installed.
Hopefully I was clear in explaining what I did. I can try arl1 and install csc. I'm ok with user data loss as I don't really have many apps or data. But can I install csc for my current ark5 and see if that gives me ota for arl1? I'm assuming arl1 is latest Oreo for s9 plus u1.
Thanks for your help.
Click to expand...
Click to collapse
Hangoverr,
You maybe right about smart switch reverting you back to the u firmware based on your imei as it was originally a carrier device. From that point forward, if you flashed over to the u1 firmware and used CSC_Home to preserve userdata, that would explain the lack of OTA pushes as it's still tied to ATT/TMB CSC. Did you happen to flash home instead of csc when switching back over to u1 firmware?
hyperblu said:
Hangoverr,
You maybe right about smart switch reverting you back to the u firmware based on your imei as it was originally a carrier device. From that point forward, if you flashed over to the u1 firmware and used CSC_Home to preserve userdata, that would explain the lack of OTA pushes as it's still tied to ATT/TMB CSC. Did you happen to flash home instead of csc when switching back over to u1 firmware?
Click to expand...
Click to collapse
I might have flashed home. I will look over xda for arl1. Would you mind giving me the link if you already have it?
Hangoverr said:
First pie beta was ota. Second one I believe it is c but don't recall exactly. I will try flashing arl1 and will see how it goes. Any suggestions on where to get it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s9-plus/how-to/sm-g965u-g965usqs3ari6-sm-g965u1-t3853429
Use the latest U1 file in that root folder of androidfilehost and use the patched odin mentioned in the original post to ignore the hash check. Remember if it fails to flash, hold power, volume down, and bixby until it resets into download mode again, Odin connects again, unplug, and replug the phone back in, once Odin confirms connection, flash.
hyperblu said:
https://forum.xda-developers.com/galaxy-s9-plus/how-to/sm-g965u-g965usqs3ari6-sm-g965u1-t3853429
Use the latest U1 file in that root folder of androidfilehost and use the patched odin mentioned in the original post to ignore the hash check. Remember if it fails to flash, hold power, volume down, and bixby until it resets into download mode again, Odin connects again, unplug, and replug the phone back in, once Odin confirms connection, flash.
Click to expand...
Click to collapse
thank you .. appreciate your help. i will try that out today.
Here is what I'm talking about
Hangoverr said:
Thank you for detailed explanation and questions.
My phone is originally att which will be u device. If you remember or heard of it, back in April we had att phones in Samsung site for 650$ and that's where I bought it. I was never on att Network so I submitted for unlock and meanwhile installed u1 from xda
then I unlocked and used tmobile sim. It always got ota as expected. In November I signed up for Samsung pie beta and then did an ota to pie.
When I wanted to revert back, I downloaded latest u1 and installed through odin it didn't boot up. Then I tried multiple versions and didn't work. I again installed pie beta using odin from xda. Then I was able to boot it up again. That's when reading online and xda I think but don't recall exactly where I got suggestion to use smart switch to downgrade to Oreo. I think it took me to att version Oreo as my imei is for att phone. Then I again downloaded u1 from xda and installed.
Hopefully I was clear in explaining what I did. I can try arl1 and install csc. I'm ok with user data loss as I don't really have many apps or data. But can I install csc for my current ark5 and see if that gives me ota for arl1? I'm assuming arl1 is latest Oreo for s9 plus u1.
Thanks for your help.
Click to expand...
Click to collapse
Looking at your screenshot I think you might possibly be okay. Looks like you are on U1 ARK5 with a T-Mobile SIM? I have the exact same thing(except my phone was originally Verizon), and I was not getting the OTA for ARL1 either, so I Odin'd it. I later realized I don't think the OTA is even available for my phone configuration.... Check here on the phone info app, even though I am now on ARL1, the latest version is still showing as ARK5. I don't really understand how this all works, but also if you search U1 firmwares on SAMMOBILE labeled with product code TMO, it will also shown you ARK5 as the latest. If you select a different carrier in the drop-down menu, it will give ARL1 as the latest. I don't really understand how carriers are associated with U1 firmwares, but that is what I am seeing on SAMMOBILE.
YrrchSebor said:
Looking at your screenshot I think you might possibly be okay. Looks like you are on U1 ARK5 with a T-Mobile SIM? I have the exact same thing(except my phone was originally Verizon), and I was not getting the OTA for ARL1 either, so I Odin'd it. I later realized I don't think the OTA is even available for my phone configuration.... Check here on the phone info app, even though I am now on ARL1, the latest version is still showing as ARK5. I don't really understand how this all works, but also if you search U1 firmwares on SAMMOBILE labeled with TMO, it will also shown you ARK5 as the latest. If you select a different carrier in the drop-down menu, it will give ARL1 as the latest. I don't really understand how carriers are associated with U1 firmwares, but that is what I am seeing on SAMMOBILE.
Click to expand...
Click to collapse
The u1 firmware is still pushed OTA via your carrier. When you check for the latest update, your phone doesn't check Samsung's servers directly... Your phone queries your carrier. Whether your carrier is pushing Samsung's unlocked firmware updates or not is a different story. If your phone is saying you're up to date and you know that there is a more recent update, you will have to use smart switch or kies to directly contact Samsung's firmware servers, which may or may not be releasing to your time zone/region at that time.
Otherwise, you will have to wait for your carrier to push the OTA. Generally, carriers can release the unlocked firmware immediately as it doesn't require any additional modifications on their end before pushing it to Samsung's unlocked phones, but sometimes they get lazy or run into issues pushing it. After all, the carriers aren't making money off subsidizing unlocked phones, so why hurry to push firmware to them. Know what I mean?
hyperblu said:
The u1 firmware is still pushed OTA via your carrier. When you check for the latest update, your phone doesn't check Samsung's servers directly... Your phone queries your carrier. Whether your carrier is pushing Samsung's unlocked firmware updates or not is a different story. If your phone is saying you're up to date and you know that there is a more recent update, you will have to use smart switch or kies to directly contact Samsung's firmware servers, which may or may not be releasing to your time zone at that time.
Otherwise, you will have to wait for your carrier to push the OTA. Generally, carriers can release the unlocked firmware immediately as it doesn't require any additional modifications on their end before pushing it to Samsung's unlocked phones, but sometimes they get lazy or run into issues pushing it. After all, the carriers aren't making money off subsidizing unlocked phones, so why hurry to push firmware to them. Know what I mean?
Click to expand...
Click to collapse
Thanks for the explanation ? That explains the behavior I have seen, and I guess that's what those carrier designations mean on SAMMOBILE when I look for U1 firmwares. T-Mobile seems to be the slow one! I find it convenient enough just to Odin the ones that come out with XAA code.
I have a Samsung S9+ AT&T version bought locked from AT&T in the US. It is still stuck on Android 8.0.0 and not receiving any updates. None OTA and none by connected to Samsung app on Windows Desktop either.
* I would like to update to 9.0.0 or 10.0.0 if possible
* Current SW ver: SAOMC_SM_G965U_OYN_ATT_OO_78
* AP: G965USQS3BRK2
* CSC: G965UOYN3BRK2
I have tried removing the sim card but still said that software is up to date.. I have not tried to ever root the device or unlock it. Seems perhaps that the IMEI is bad perhaps in some Samsung/AT&T server that prevents the server from giving me updates (based on reading around the Internet).
Any hope for me? I am not good at these things but am willing to learn and try though there is way too much information so not sure where to start reading and understanding the root cause of the problem itself.
Its a easy fix you will need to download the update file then flash it using Odin Patched
Here's a video that will help out. https://youtu.be/SVhR0E9ACnY
I used it the other days when i flashed my S9+ Sprint running on Andriod 9.0 -------> To a S9+ Tmobile Andriod 10
I dont take credit on this but here is also a good write up
1) Download Odin
2) Extract the 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)
3) Add each file to it's respective field in Odin v3.13.1. Use CSC_OXM if you want to do a clean flash and HOME_CSC OXM if you want to keep your apps and data.
4) Reboot your phone in Download / Odin mode with the following button combo:
POWER + VOLUME DOWN + BIXBY
5) Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a blue box will show up with the COM port number.
6) Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
7) Click the start button, wait for Odin to say 'PASS'. Once the flash is complete, your phone will reboot.
Firmware screenshots, changelog, and download links will be in 2nd post of this thread.
Colombia81er said:
Its a easy fix you will need to download the update file then flash it using Odin Patched
Click to expand...
Click to collapse
I used the firmware from sammobile as I couldn't figure out where to get the binary for AT&T S9+. Even there they had for BST, Verizon, Comcast, Sprint. I tried the one called USC and it seems to work. I got the one labeled G965USQS7CSK5. I am now on 9.0.0 and so far looking good. Just finished. Thanks.
agaurav said:
I used the firmware from sammobile as I couldn't figure out where to get the binary for AT&T S9+. Even there they had for BST, Verizon, Comcast, Sprint. I tried the one called USC and it seems to work. I got the one labeled G965USQS7CSK5. I am now on 9.0.0 and so far looking good. Just finished. Thanks.
Click to expand...
Click to collapse
I used Frija to download lastest firmware but i see they dont have it.
Heres the file if you still want to update it to G965USQU7DTA5 which is there latest version.
Colombia81er said:
I used Frija to download lastest firmware but i see they dont have it.
Heres the file if you still want to update it to G965USQU7DTA5 which is there latest version.
Click to expand...
Click to collapse
Thanks, I decided to stick with 9.0 for now as my company doesn't allow 10.0 for their own apps. I managed to download something from sammobile and it is working out fine. Thanks a lot for your help!!
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
its a verizon tablet so thats normal.. u need to change csc is all
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
jmwfl2000 said:
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
Click to expand...
Click to collapse
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Gotcha, so change the CSC first, then flash the matching firmware? What's the best method for changing the CSC on the S7+? This process? https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
Any suggestions on how to change the CSC? I've hit a wall and haven't been able to find a way to change it and then flash the desired firmware.
elliwigy said:
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Click to expand...
Click to collapse
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
bs3pro said:
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
Click to expand...
Click to collapse
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
jmwfl2000 said:
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
Click to expand...
Click to collapse
jmwfl2000 said:
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
Click to expand...
Click to collapse
dunno wat ur flashing but all the firmware is the same.. theyre all multi csc.. so simply flashing different firmwares wont change csc lol
I don't know if this will help but on some samsung phones you can change the csc by opening the dailer and typing "*#272*IMEI number#"
edit: IMEI must me copied from the about tablet section in the settings. Press on the IMEI for a second and it will be copied to clipboard. Typing the IMEI will not likely not work.
After entering this in the dailer a menu pops up and you can select csc. Note this will usually factory reset the device.
Yes if you try this, please let me know if it works. I have the T878u 5g from Tmobile.
Any update on this? I purchased an SM-T978U (on Samsung website that is t-mobile S7+)
I expected it to not be carrier or network locked but it was locked to the t-mobile network.
Would love to flash an unlocked firmware but I can't find SM-T978U firmware, let alone U1 firmware...... I realize that flashing U1 firmware won't unlock the network but T-mobile support tells me the device can't possibly be truly carrier locked because the IMEI isn't even in their system. So I thought maybe the carrier lock is in their app tied to the system instead of the actual device??
Anyway has anyone found the firmware for these devices? Sammobile doesn't seem to list SM-T978 as a device
These devices don't have a dialer so entering the IMEI method mentioned above won't work unless there is a trick?
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
not sure y u tagged me lol.. i know hiw csc works.. in fact, in my last comment before this one you can see I clearly said just flashing firmware won't change the csc? seems like basically what you said but in a few words
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
Where is this U1 XAA firmware to download? Specifically for the SM-T978U?
RE: jmwfl2000 -I always untick the "Auto-Reboot" box when flashing new TWRP images to prevent stock recovery from being reapplied.After the first boot all should be well.
K3N422 said:
in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
I'm pretty stumped like OP. Where are you finding U1 XAA for Tab S7+? Doesn't seem to turn up anywhere. Would definitely appreciate it if you could provide a link. Thanks.
I tried resetting before flashing and unchecked the auto-reboot but mine still returns to Tmobile. I just want the call and text on other devices feature.
Edit: I go the feature to work without flashing a new firmware but I am still looking for U1 XAA for the tab if anyone found it.
jmwfl2000 said:
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
Click to expand...
Click to collapse
I bought an unlocked Verizon Tab S7, probably same seller. Its brand new, stil has plastic on it. Are you wanting to unlock Tmobile 5G bands?