Related
**Welcome to the Fox Den!**
This is a complete guide for flashing Unlocked Firmware, Carrier Firmware, and Carrier Switching for SM-N950U and SM-N950U1 (The guide can also be used for SM-N950W with appropriate files)
The firmware and files within this guide are hosted on various sites and I will try to keep updates available.
The steps in this guide require Samsung Drivers installed, adb setup, Odin & Odin (Prince Comsy), Download Mode, and Recovery Mode - Downloads are found below and are organized by guide used:
Before you proceed, I cannot be held liable for the damage or malfunction of your device using these files,
you proceed at your own risk and remove my liability by continuing to any portion of this thread! Flashing files from this thread will erase the internal storage so back up your files first!
***Note - Oreo releases on this thread will need to be flashed with New Odin3_v3.13.1 or Odin3_v3.13.1_3B_PatcheD - End Note***
!PLEASE BE SURE TO READ ALL THE INSTRUCTIONS THOROUGHLY AND SEARCH THE POSTS BEFORE ASKING QUESTIONS!
Prerequisites:
- Your Note 8 and PC ready to flash
- READ THE GUIDE YOU WISH TO FOLLOW!
- Remove Samsung Kies/Switch if installed on PC
- Download and extract all required files to convenient location, keeping all files organized, on PC
- Install Samsung Drivers if not installed
- Setup adb if not setup
- Edit the "UMS/PATCH" of Odin3.ini file for Odin and Modified Odins from "0" to "1" and save ("Ctrl S")
+Updated Odin Zips so are already edited so there is no confusion, but feel free to double check.-- I started packaging firmware in individual .rar files to save space so you will have to extract them to flash them, else you will get error...
Downloads:
Carrier Switching: Steps in Post 2
***Note - If you have updated to the V3 Bootloader, N950USQU3BRA?, for any carrier,Prince Comsy's Odin is not blocked - End Note***
TOOLS:
Samsung USB
Platform-Tools (adb)
WinRAR
ODIN VERSIONS:
3.13.1 for use with Oreo:
Odin3_v3.13.1
Odin3_v3.13.1_3B_PatcheD
3.12 for use with Nougat:
Odin3_v3.12.7
Odin3_v3.12 (PrinceComsy)
Mega Cloud Drive Mirror
Odin3_v3.12.7 / _v3.12 (PrinceComsy)
ODIN FILES TO FLASH (Combination Firmware and XAC HOME_CSC):
*Match with your intended Firmware...For example, If your Firmware ends with "AQH7", download and flash files from "For use with AQH7" section, Latest versions are always on top*
For use with BRA5/6/8/9 Firmwares
COMBINATION_FA71_N950USQU3ARA3
HOME_CSC_OYV_N950WOYV3BRA5 - *This is Canadian XAC HOME_CSC and can be flashed in Prince Comsy's Odin*
For use with BQL1/2/5/A Firmwares
COMBINATION_FA71_N950USQU2AQL1
*Sorry no BQL2 XAC HOME_CSC, use 2AQK3 instead*
HOME_CSC_OYV_N950WVLS2BQK1 - *This is Canadian XAC HOME_CSC and can be flashed in Prince Comsy's Odin*
*Older Versions*
For use with BQK1/2/3 Firmwares
N950USQU2AQK3_COMBINATION
HOME_CSC_OYV_N950WVLS2BQK1
For use with BQJA/B Firmwares
N950USQU2AQK2_COMBINATION
HOME_CSC_OYV_N950WOYV2BQJA
For use with AQH7 - AQI5/9/A Firmwares
N950USQU1AQH8_COMBINATION (Original)
HOME_CSC_OYV_N950WOYV1AQH7 (Original)
Flashing Carrier Firmware: Steps in Post 3
TOOLS:
Samsung USB
Platform-Tools (adb)
WinRAR
ODIN VERSIONS:
3.13.1 for use with Oreo:
Odin3_v3.13.1
Odin3_v3.13.1_3B_PatcheD
3.12 for use with Nougat:
Odin3_v3.12.7
Odin3_v3.12 (PrinceComsy)
Mega Cloud Drive Mirror
Odin3_v3.12.7 / _v3.12 (PrinceComsy)
ODIN FILES TO FLASH (Complete Carrier Firmware):
AT&T (ATT):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRA8 * Cannot be downgraded *
N950USQS2BQL5
Older Versions
N950USQS2BQK2
N950USQU2BQJA * Cannot be downgraded *
N950USQU1AQIA
N950USQU1AQH7
Mirrors:
norbarb - N950USQS2BQK2
norbarb - N950USQU2BQJA
Temp Link - N950USQU1AQIA
Sprint (SPR):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRB4
N950USQU3BRA6 * Cannot be downgraded *
N950USQS2BQL9
Older Versions
N950USQS2BQK3
N950USQU2BQJB * Cannot be downgraded *
N950USQU1AQI5
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7/AQI5/BQJB
Updato - N950USQU1AQH7/AQI5/BQJB
Team DevDigitel - N950USQU2BQJB
Team DevDigitel - N950USQU1AQI5
Team DevDigitel - N950USQU1AQH7
Sprint (XAS):
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7
Updato - N950USQU1AQH7
T-Mobile (TMB):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRA9 * Cannot be downgraded *
N950USQU2BQLA
Older Versions
N950USQU2BQJA * Cannot be downgraded *
N950USQU1AQI5
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7/AQI5/BQJA
Updato - N950USQU1AQH7/AQI5/BQJA
torreon901 - N950USQU1AQH7
U.S. Cellular (USC):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRA8 * Cannot be downgraded *
Older Versions
N950USQU2BQJA * Cannot be downgraded *
N950USQU1AQI9
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7/AQI9/BQJA
Updato - N950USQU1AQH7/AQI9/BQJA
Verizon (VZW):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRB1
N950USQU3BRA5 * Cannot be downgraded *
N950USQS2BQL5
Older Versions
N950USQS2BQK2 * Cannot be downgraded *
N950USQU1AQI5
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7/AQI5/BQK2
Updato - N950USQU1AQH7/AQI5/BQK2
Xfinity (CCT):
Oreo
N950USQU3CRC2
Nougat
N950USQU3BRA6 * Cannot be downgraded *
Older Versions
N950USQS2BQK2
N950USQU2BQJA * Cannot be downgraded *
N950USQU1AQI5
N950USQU1AQH7
Mirrors:
SamMobile - N950USQU1AQH7/AQI5/BQJA/BQK2
Updato - N950USQU1AQH7/AQI5/BQJA/BQK2
Jammol - N950USQS2BQK2
Jammol - N950USQU1AQI5
Flashing Unlocked Firmware: Steps in Post 4
TOOLS:
Samsung USB
Platform-Tools (adb)
WinRAR
ODIN VERSIONS:
3.13.1 for use with Oreo:
Odin3_v3.13.1
Odin3_v3.13.1_3B_PatcheD
3.12 for use with Nougat:
Odin3_v3.12.7
Odin3_v3.12 (PrinceComsy)
Mega Cloud Drive Mirror
Odin3_v3.12.7 / _v3.12 (PrinceComsy)
ODIN FILES TO FLASH (Unlocked Non-Carrier Firmware):
Unlocked XAA
*Any carrier can flash this version because your SIM and device CSC code will setup proper carrier info, but you can look below for the specific carrier branded version if you choose*
Oreo
N950U1UEU3CRC1
Nougat
N950U1UEU3BRA5 * Cannot be downgraded *
N950U1UEU2BQL2
Older Versions
N950U1UEU2BQK1 * Cannot be downgraded *
N950U1UEU1AQI5
N950U1UEU1AQH9
Mirrors
LMMT - N950U1UEU3CRC1
"Unlocked" Carrier Specific Links:
*CARRIER branded XAA Firmwares (Not Carrier Stock...located in Flashing Carrier)...little to no bloat*
*Same as XAA unlocked just with Carrier Settings and some Carrier files already added (not the same as full carrier firmware though)*
*Updato links and SamMobile links are mirrors of each other and are posted just to give you an option*
Updato:
(ACG) CSpire - N950U1UEU1AQI5/BQK1/BQL2
(AIO) Anritsu - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(ATT) AT&T - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(BST) Boost Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(CCT) Xfinity - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(LRA) Bluegrass Cellular - N950U1UEU1AQH9/AQI5/BQK1/BQL2
(SPR) Sprint - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TFN) Tracfone - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TMK) MetroPCS - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TMB) T-Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(USC) US Cellular - N950U1UEU1AQI5/BQK1/BQL2/BRA5
(VMU) Virgin Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(VZW) Verizon - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(XAA) Stock Universal - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(XAS) Sprint Non-Branded - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
SamMobile:
(ACG) CSpire - N950U1UEU1AQI5/BQK1/BQL2
(AIO) Anritsu - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(ATT) AT&T - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(BST) Boost Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(CCT) Xfinity - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(LRA) Bluegrass Cellular - N950U1UEU1AQH9/AQI5/BQK1/BQL2
(SPR) Sprint - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TFN) Tracfone - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TMK) MetroPCS - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(TMB) T-Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(USC) US Cellular - N950U1UEU1AQI5/BQK1/BQL2/BRA5
(VMU) Virgin Mobile - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(VZW) Verizon - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(XAA) Stock Universal - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
(XAS) Sprint Non-Branded - N950U1UEU1AQH9/AQI5/BQK1/BQL2/BRA5
** Special Thanks **
- @Mike15678 - Guide Template
- @chrisusa96 - Testing/Contributing
- @TonkaToy87 -Testing/Contributing
- @leprkon - Hosting Combo/Contributing
- @realbbb - Odin3_v3.13.1_3B_PatcheD
* Other Thanks *
- @Team DevDigitel - Hosting Sprint Firmware
- @torreon901 - Hosting T-Mobile Firmware
- @norbarb - Hosting AT&T Firmware
- @Jammol - Hosting Xfinity Firmware
- @LMMT - Hosting XAA Firmware
...more coming...
Other Links
*Culpeo ROM*
*Fennec ROM*
*SM-N950U1 XAA Stock Recovery Guide*
*Edit APN Settings & Native HotSpot Guide*
*SM-N950U/U1 Factory Binary, Combination Firmware*
*S Note & Working Action Memo*
*Free SIM Unlock Service by: @instrumentaly*
Switching Carrier:
Disclaimer - Switching Carrier will not carrier unlock your device. For carrier unlock, call carrier or pay for unlock service.
***Note - If you have updated to the V3 Bootloader, N950USQU3BRA?, for any carrier, Prince Comsy's Odin is not blocked - End Note***
Note - This guide uses adb, regular Odin, Prince Comsy's Odin, Canadian XAC Home_CSC, and Factory Binary.
Download Firmwares that match your intended carrier's product code, ATT, CCT, SPR, TMB, USC, VZW, XAA, or XAS.
Make note that Firmwares based on SM-N950U1 are Unlocked Firmwares and do not contain carrier files even though they have carrier code. For Carrier versions, download SM-N950U Firmwares.
Some carrier features may not work on different carrier devices without modifications or having IMEI added to intended carrier's whitelist.
**Note: This will NOT change the CSC Product Code of the device, it only allows you to change carrier Firmware effectively...for instance, XXX/XXX/SPR**
Match Binary version to your Firmware Version as older binaries do not work with newer firmware..
If you are just flashing Carrier Firmware on SM-N950U1, skip to Flashing Carrier guide. If you are just flashing Unlocked Firmware on SM-N950U, skip to Flashing Unlocked guide.
*Downloads are in OP*Steps:
Step 1 - Turn OFF your Galaxy Note 8.
Step 2 - Press and hold the Volume Down + Bixby + Power Buttons.
Step 3 - After the Samsung logo, you will see a screen with a warning sign. Proceed ahead by pressing the Volume Up button.
You are in the Download Mode. If you want to get out of it, simply hold the Volume Up and Power buttons for a few seconds (around 10 sec.) and your phone will reboot normally.
Step 4 – Navigate to extracted Regular Odin folder and right click on the .exe, select Run as administrator.
Step 5 – Connect your device via USB, Odin output should read "Added!!".
Step 6 – Add extracted Factory Binary file (COMBINATION file that matches your firmware, if you have updated to the latest then you need the latest) in the Odin section labeled AP by clicking AP in Odin and selecting COMBINATION file.
Step 7 – Ensure that only “Auto Reboot" and "F. Reset Time" are selected under the options tab.
Step 8 – Click log tab and then click the Start button on the bottom right.
Step 9 – Output should be shown in the log, take a break for a few….
Step 10 – If the flash is successful, the top left box will become green and will read PASS.
Leave your phone connected and let your it reboot into the Factory Binary homescreen..*IT WILL BE ERASED*.
If Factory Binary homescreen does not load or device is stuck on Boot, power off device with Volume Down + Power Button and boot into Revovery, Volume Up + Bixby + Power buttons and perform a Factory reset.
***It is best to perform a factory reset anyways***
Then choose Reboot device.
Step 11 - Navigate to extracted adb folder (platform-tools) and Shift+Right click on any blank space in file explorer with that folder open and select "Open command window here".
If the option is missing search for cmd via Windows Start Button or Cortana search and Right-Click the cmd.exe and select Run as administrator.
Step 12 - Type in:
Code:
adb reboot bootloader
Step 13 - Leave ADB open, your device will reboot into download mode and stay connected to adb.
Step 14 - Navigate to extracted Odin (Prince Comsy's) folder and right click on the .exe, select Run as administrator.
Step 15 - Odin output should read "Added!!".
Step 16 - Add extracted Canadian HOME_CSC file in the Odin section labled CSC by clicking CSC in Odin and selecting XAC_HOME_CSC file.
Step 17 - Ensure that only “Auto Reboot" and "F. Reset Time" are selected under the options tab.
Step 18 - Click log tab and then click the Start button on the bottom right.
Step 19 - Output should be shown in the log, should be quick.
Step 20 - If the flash is successful, the top left box will become green and will read PASS.
Step 21 - Once your phone reboots, you will see an "IME" button on the bottom of 'factory binary homescreen'.
Step 22 - Select the "IME" button and dial:
Code:
*#243203855#
Step 23 - After menu pops up, Scroll down until you find an "XAC" option. Select "XAC" and then select "Install".
Step 24 - Your phone will reboot. Once it reaches the 'Factory Binary homescreen', go back to command prompt on your computer and type in:
Code:
adb shell
Step 25 - In the cmd window type the following exactly, with XXX being replaced by intended CSC "code" below:
Code:
echo "XXX" > /efs/imei/mps_code.dat
Choose one of these CSC "codes" to replace XXX in the info above:
ACG - C Spire
AIO - Cricket
ATT - AT&T
BST - Boost
CCT - Xfinity
SPR - Sprint
TFN - Tracfone
TMB - T-Mobile
TMK - MetroPCS
USC - US Cellular
VMU - Virgin Mobile
VZW - Verizon
XAS - Sprint
XAA - US UnlockedStep 26 - In the cmd window, type in:
Code:
exitStep 27 - In the cmd window, type in:
Code:
adb reboot bootloaderStep 28 - Flash your desired Firmware by following the "Flashing Carrier Firmware" or "Flashing Unlocked Firmware" guides below.
Flashing Carrier Firmware:
Disclaimer - Flashing different Carrier Firmwares will not switch carrier.
***Note - Using Prince Comsy's Odin is not blocked - End Note***
Note - If you are flashing Carrier Firmware from Unlocked Firmware you can use regular Odin.
Download and flash SM-N950U Firmwares that match your carrier's product code, ATT, CCT, SPR, TMB, USC, VZW or XAS.
Firmwares based on SM-N950U1 are Unlocked Firmwares and do not contain carrier files even though they have carrier code.
Some carrier features may not work on Unlocked devices flashed to carrier Firmware without modifications or having IMEI added to carrier's whitelist.
*Downloads are in OP*Steps:
Step 1 - Turn OFF your Galaxy Note 8.
Step 2 - Press and hold the Volume Down + Bixby + Power Buttons.
Step 3 - After the Samsung logo, you will see a screen with a warning sign. Proceed ahead by pressing the Volume Up button.
You are in the Download Mode. If you want to get out of it, simply hold the Volume Up and Power buttons for a few seconds (around 10 sec.) and your phone will reboot normally.
Step 4 – Navigate to extracted Odin folder and right click on the .exe, select Run as administrator.
Step 5 – Connect your device via USB, Odin output should read "Added!!".
Step 6 – Add extracted firmware files (your carrier version, ATT, CCT, SPR, USC, or VZW) in the Odin sections appropriately, BL for BL, AP for AP, CP for CP, CSC for CSC (not HOME_CSC), and UMS for USERDATA.
Step 7 – Ensure that only “Auto Reboot" and "F. Reset Time" are selected under the options tab.
Step 8 – Click log tab and then click the Start button on the bottom right.
Step 9 – Output should be shown in the log, take a break for a few….
Step 10 – If the flash is successful, the top left box will become green and will read PASS.
Your Device can be disconnected..*IT WILL BE ERASED*.
Errors - Failed, SHA256? - Try again after editing config file for UMS/patch from 0 to 1 for USERDATA to write as well as using Prince Comsy's Odin. If it keeps failing, re-download Firmware and try again. You may also need to boot to Recovery and perform Factory Reset before trying again.
**If any functions or system apps seem glitchy, you may benefit from a factory reset**
Flashing Unlocked Firmware:
Disclaimer - Flashing Unlocked Firmwares will not unlock your device.
***Note - Using Prince Comsy's Odin is not blocked - End Note***
Note - If you are flashing Unlocked Firmware from Carrier Firmware you must use Prince Comsy Odin otherwise, use regular Odin.
All SM-N950U1 Firmwares are unlocked and you may have better connectivity by flashing your carrier's, ATT, CCT, SPR, TMB, USC, or VZW, version of Unlocked Firmware.
XAA is Factory Unlocked Firmware and will work on all US carriers.
Some carrier features may not work on Unlocked Firmware without modifications.
*Downloads are in OP*Steps:
Step 1 - Turn OFF your Galaxy Note 8.
Step 2 - Press and hold the Volume Down + Bixby + Power Buttons.
Step 3 - After the Samsung logo, you will see a screen with a warning sign. Proceed ahead by pressing the Volume Up button.
You are in the Download Mode. If you want to get out of it, simply hold the Volume Up and Power buttons for a few seconds (around 10 sec.) and your phone will reboot normally.
Step 4 – Navigate to extracted Odin or Prince Comsy Odin folder and right click on the .exe, select Run as administrator.
Step 5 – Connect your device via USB, Odin output should read "Added!!".
Step 6 – Add extracted firmware files (your carrier version of Unlocked or XAA) in the Odin sections appropriately, BL for BL, AP for AP, CP for CP, CSC for CSC (not HOME_CSC).
Step 7 – Ensure that only “Auto Reboot" and "F. Reset Time" are selected under the options tab.
Step 8 – Click log tab and then click the Start button on the bottom right.
Step 9 – Output should be shown in the log, take a break for a few….
Step 10 – If the flash is successful, the top left box will become green and will read PASS.
Your Device can be disconnected..*IT WILL BE ERASED*.
Errors - Failed, SHA256? - Try again after editing config file for UMS/patch from 0 to 1 for USERDATA to write as well as using Prince Comsy's Odin. If it keeps failing, re-download Firmware and try again. You may also need to boot to Recovery and perform Factory Reset before trying again.
*If you are going to proceed to flash carrier CSC and USERDATA files for carrier functions, please make sure that they are from the appropriate SM-N950U carrier before proceeding...*
**If any functions or system apps seem glitchy, you may benefit from a factory reset**
Switch from AT&T
So with this method, could I unlock my AT&T Galaxy note 8 and install the unlocked firmware, thus allowing me to install twrp and custom ROMS?
vsmendes76 said:
So with this method, could I unlock my AT&T Galaxy note 8 and install the unlocked firmware, thus allowing me to install twrp and custom ROMS?
Click to expand...
Click to collapse
This will NOT unlock your device...for that you need to call your carrier or pay for unlock service.
You can flash unlocked firmware on any U.S. snapdragon device even if it is carrier locked.
To root your device go to: https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
This does not unlock bootloader though, so no TWRP. You can, however use flashify from the app store to make recoveries, flash mods, and ROMs (once available)
You can also use this guide to switch carriers if you wish...
Note: if you root, you can change csc without this method to change carriers
BlueFox721 said:
Flashing Unlocked Firmware:
Disclaimer - Flashing Unlocked Firmwares will not unlock your device.
Note - If you are flashing Unlocked Firmware from Carrier Firmware you must use Prince Comsy Odin otherwise, use regular Odin.
All SM-N950U1 Firmwares are unlocked and you may have better connectivity by flashing your carrier's, ATT, CCT, SPR, TMB, USC, or VZW, version of Unlocked Firmware.
XAA is Factory Unlocked Firmware and will work on all US carriers.
Some carrier features may not work on Unlocked Firmware without modifications.
*Downloads are in OP*Steps:
Step 1 - Turn OFF your Galaxy Note 8.
Step 2 - Press and hold the Volume Down + Bixby + Power Buttons.
Step 3 - After the Samsung logo, you will see a screen with a warning sign. Proceed ahead by pressing the Volume Up button.
You are in the Download Mode. If you want to get out of it, simply hold the Volume Up and Power buttons for a few seconds (around 10 sec.) and your phone will reboot normally.
Step 4 – Navigate to extracted Odin or Prince Comsy Odin folder and right click on the .exe, select Run as administrator.
Step 5 – Connect your device via USB, Odin output should read "Added!!".
Step 6 – Add extracted firmware files (your carrier version of Unlocked or XAA) in the Odin sections appropriately, BL for BL, AP for AP, CP for CP, CSC for CSC (not HOME_CSC).
Step 7 – Ensure that only “Auto Reboot" and "F. Reset Time" are selected under the options tab.
Step 8 – Click log tab and then click the Start button on the bottom right.
Step 9 – Output should be shown in the log, take a break for a few….
Step 10 – If the flash is successful, the top left box will become green and will read PASS.
Your Device can be disconnected..*IT WILL BE ERASED*.
Errors - Failed, SHA256? - Try again after editing config file for UMS/patch from 0 to 1 for USERDATA to write as well as using Prince Comsy's Odin. If it keeps failing, re-download Firmware and try again. You may also need to boot to Recovery and perform Factory Reset before trying again.
**If any functions or system apps seem glitchy, you may benefit from a factory reset**
Click to expand...
Click to collapse
great guide bro !
you missed to write that the last CSC value can't be changed without root because is hard written in EFS config, es:
if you bought a TMO Note 8 ( for example ) and you want carrier switch to Unlocked Firmware following this guide you always have a device like this in "About Phone" :
XAA/XAA/TMB and never XAA/XAA/XAA
For sure the last third CSC code value is not relevant because it only specify which is the original Vendor and it doesn't impact at all in any aspect of new installed firmware
wolfgart said:
great guide bro !
you missed to write that the last CSC value can't be changed without root because is hard written in EFS config, es:
if you bought a TMO Note 8 and you want carrier switch to Unlocked Firmware following this guide you always have a device like this in "About Phone" :
XAA/XAA/TMB and never XAA/XAA/XAA
For sure the last CSC code is not relevant because it only specify which is the original Vendor and it doesn't impact in any aspect of new installed firmware
Click to expand...
Click to collapse
Right the last code requires root...but this guide is for changing carrier...for instance, if you attempt to install Verizon Firmware on T-MOBILE you will still have T-Mobile bloat...this changes T-Mobile csc to (for example) To Verizon so you can flash Verizon and have Verizon bloat...I will update to include that it does not change the device csc....thank you...
There is a root method on S8+ for doing this though, I may add it later in a new thread...but for our device...of course our root may not allow it...
I nave an N9500 (Snapdragon). Can I use these files to load AT&T Firmware? What is really the benefit of that?
delugeofspam said:
I nave an N9500 (Snapdragon). Can I use these files to load AT&T Firmware? What is really the benefit of that?
Click to expand...
Click to collapse
I am not sure...have you checked the S8 and S8+...they have had their devices longer...and might have discussed the same
Worked like a charm! Switched the phone from Verizon to TMO. I encountered one hiccup, but that was easily remedied. I got the '$ADB_VENDOR_KEYS is not set' error when I tried sending the reboot command through adb. I fixed this by deleting the adbkey and adbkey.pub files from in Users/YourSystemName/.android and then generating a new set of keys using
Code:
adb keygen C:\Users\YourSystemName\adbkey
and placing the newly generated keypair in the .android folder. You can try generating the keys in the .android folder directly, but I had some trouble with that (something about access and permission). Once you do this, try
Code:
adb reboot bootloader
again and it should work!
leprkon said:
Worked like a charm! Switched the phone from Verizon to TMO. I encountered one hiccup, but that was easily remedied. I got the '$ADB_VENDOR_KEYS is not set' error when I tried sending the reboot command through adb. I fixed this by deleting the adbkey and adbkey.pub files from in Users/YourSystemName/.android and then generating a new set of keys using and placing the newly generated keypair in the .android folder. You can try generating the keys in the .android folder directly, but I had some trouble with that (something about access and permission). Once you do this, try again and it should work!
Click to expand...
Click to collapse
Yeah...I just factory reset to solve it...but adb command is quicker...glad it worked..
BlueFox721 said:
Yeah...I just factory reset to solve it...but adb command is quicker...glad it worked..
Click to expand...
Click to collapse
The factory reset solution to getting Factory Binary to boot was so genius and obvious that I felt stupid for not thinking of it when I was troubleshooting. Good on you for getting this guide together! Thanks again!
If I clash the Verizon one will Verizon see a note 8 right now they see some Lame phone. Cause I got it from Samsung
For flashing unlocked firmware, I see
All SM-N950U1 Firmwares are unlocked and you may have better connectivity by flashing your carrier's, ATT, CCT, SPR, TMB, USC, or VZW, version of Unlocked Firmware.
XAA is Factory Unlocked Firmware and will work on all US carriers.
Click to expand...
Click to collapse
Will flashing carrier's unlocked firmware include all the bloatware? Or is it just different CSC files for connectivity?
bambam126 said:
If I clash the Verizon one will Verizon see a note 8 right now they see some Lame phone. Cause I got it from Samsung
Click to expand...
Click to collapse
For carriers to show the correct device on account...the imei must be in their list and provisioned correctly...each carrier is having issues with this, mostly with devices bought from Samsung...
datder said:
For flashing unlocked firmware, I see
Will flashing carrier's unlocked firmware include all the bloatware? Or is it just different CSC files for connectivity?
Click to expand...
Click to collapse
Connectivity info and required files that also set when you put your SIM in...
I flashed the ATT firmware to my unlocked SM-N950U1 this morning using your guide, and everything is working perfectly. No startup issues, no snags. Thanks for making it easy to follow along. VoLTE, Wi-Fi calling, Advanced Messaging, Video Calling, etc all are working perfectly without a call to AT&T. Lots of bloat, but I disabled the bulk of it with BK.
Thank you!
wolfgart said:
great guide bro !
if you bought a TMO Note 8 ( for example ) and you want carrier switch to Unlocked Firmware following this guide you always have a device like this in "About Phone" :
XAA/XAA/TMB and never XAA/XAA/XAA
For sure the last third CSC code value is not relevant because it only specify which is the original Vendor and it doesn't impact at all in any aspect of new installed firmware
Click to expand...
Click to collapse
I am exactly in this situation but could you please confirm that the CDMA freq /band will be working once we flash the CSC even with XAA/XAA/TMB?
Thank you
car2carl said:
I am exactly in this situation but could you please confirm that the CDMA freq /band will be working once we flash the CSC even with XAA/XAA/TMB?
Thank you
Click to expand...
Click to collapse
If you use carrier switching guide to change to the desired csc, for instance changing from TMB to SPR...you will then flash your intended firmware like SM-N950U SPR...as long as your device is carrier unlocked or factory unlocked...you should be able to insert desired carrier SIM, like Sprint, and activate...the last three of code are for product origination...your SIM and firmware control the connectability not the last three of product code...S8+ users have even stated they flashed on Canadian devices or Canadian firmware and connected...in other words, if you use CDMA SIM you will connect
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Have not heard before that people have gotten Knox tripped by flashing Samsung firmware, you could have by mistake flashed TWRP or an non Samsung partition file etc. But atleast try a factory reset. If that does not work, you tripped Knox:/
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Tuikelo said:
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Click to expand...
Click to collapse
Being that I'm in the US I can't say for sure what the issue is because I haven't gotten the official stable build yet.
I'd say just flash back to stock official 8 for your region and wait for the ota. Shouldn't be too much longer for you.
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I would double check to make sure you didn't trip knox... The following steps should help do this
Completely power off off your Galaxy S9+
Restart the phone in Download Mode
Once in download mode, visually search for the words "Warranty Void" and the numbers that are on the same line.
If the numbers show “0x0” knox has not been tripped.
If the numbers show “0x1” knox has been permanently (as in you can't fix it ever on that phone because an E-Fuse has been blown) tripped
Assuming that knox is still intact then I would believe the issue (I would say 80% if I had to guesstimate) due to the mismatch between the rom file you flashed and the existing bootloader, partition, csc, etc. that you didnt flash. For example if parts of the rom are from oreo and the android OS is the pie beta this could cause problems. I am not sure if they did this or not, but it would make sense that Samsung incorporated some sort of file/firmware/version integrity check
An easy way to tell if this is the case is to get all the firmware versions to come from the same release. In effect Can you restore it back to the way it was before you flashed the device? Or if possible can you update it fully so that all the files are the same firmware? Which ever route you go will be up to you, but overall if the files all come from the same firmware version if the apps in question work this will confirm the cause.
Also double check the firmware your flashing... If it is a release before the official beta's you may run into problems. Your gonna have to go ask in the board/forum you got the file from (in the respective thread) for help or check up on known issues. Otherwise if the use of Samsung pass and secure folders is of importance to you I would revert back to the firmware you were on (before you attempted to flash the beta) and wait for the official release.
The use of mismatched firmware parts can also cause you to not get any OTA updates, so your gonna have probably flash it again properly to correct that
Lastly if I recall correctly if you have enabled OEM unlock this can cause samsung pass and secure folders to not work.
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
The Google Pay thing is because Google Play Protect Certification Status has flagged the device as not certified. This is because we are currently using an unreleased (i.e. beta test from Samsung) firmware version. Once we are on an official release the Certification Status will revert to certified status and Google Pay will work.
The issue with Google Pay under the Android Pie beta does/should not effect Samsung Pass or Secure Folder at all. Currently on my install of the beta test version(s) Samsung Pass, Samsung Pay, Samsung Health and Secure Folder (all which rely on knox) work just fine. I am using them all the time without issue, with the exception of a few cosmetic aspects at first that have been resolved by Samsung.
he can also type "getprop" in adb shell or a terminal app and look for the warranty..
but as someone else already suggested, if you flashed a "beta" pie build that could absolutely cause it to read as custom (this wouldnt trip knox though) which would cause some issues with those apps..
if it is unnoficial/reading as custom, you should be able to check in settings > about phone > status then look for "Device Status".. I think its there in Pie..
to put into perspective, i simply disabled some apks.. im on a usa note 9 which means i couldnt root, unlock or trip knox if i wanted to but simply disabling some apps causedmine to show custom as u can see in my screenshot lol
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I flashed the stable Pie update (DBT) as well and I'm not receiving that notification/error when I open Samsung pass. Flash all of the files in the zip (use HOME_CSC if you want to keep your data) and see if that helps.
Solution
I did a reload of oreo on my s9+ after doing an update to android 9 (Australian versions ) which I didn't like. My
google and Samsung pay would not work until I switched back off "OEM unlock" in "Developer tools" which erases your phone again like it did when you turned it on to load firmware with odin. The option is locked out and takes a week of being turned on to come back up.
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.
I got tired of waiting for T-Mobile to push the newest OTA to my unlocked S10e and took matters into my hands. Now I'm running the most recent July 1st update before TMobile pushed it which is the one with night mode. Following is how I accomplished it. I'm keeping it somewhat vague as I believe if my steps aren't clear you're probably better off not doing so. I won't be able to assist you if this doesn't work or somehow you brick your device. In theory this should work for all S10s on any carrier. You'd just have to adjust the model and CSC. Again my instructions are for the Snapdragon Unlocked S10e Dislcaimer: This worked for me but proceed at your own risk.
First is the software you'll need. Which is Odin to flash update and Frija for downloading Firmware. You could also find the firmware on a few websites but I think Frija makes it less confusing. If you can't find these on your own you probably shouldn't proceed. Steps below.
1. Open Frija and for model use SM-G970U1 and for CSC use XAA. XAA is the unlocked and unbranded default CSC code for the unlocked USA snapdragon device. Adjust for your model and CSC if using a carrier variant. Utilize Google to find CSC value for yours.
2. After download completes unzip the firmware
3. Open ODIN and select the BL, AP and CP file in the folder you unzipped from Frija
4. For CSC select the Home_CSC. Very important to select this to preserve your setup. CSC_OMC will factory reset your device. If you want to start fresh choice so.
5. Turn off your device then enter download mode. Once in download mode plug the device into your computer.
6. Now on Odin hit start. Process takes 5-15 minutes.
7. Wait for it to complete. Phone will reboot. I think it did twice can't remember. FYI; I even got a brief screen that said erase. All was fine. May see otherwise if you factory reset.
8. After reboot Android will optimize apps. If you reset setup will begin. That's it you're good to go. Your device is now on the most recent update.
Again this should also work on all S10s and carriers regardless if the carrier variant or unlocked if you haven't received the OTA yet. You'd just need to adjust your model and CSC number to the correct ones. If you do have a carrier model do not attempt to use another carrier CSC. Proceed at your own risk and sorry I'm not available for troubleshooting.
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!!