Database Develop

N960U AT&T USERDATA Links and Flashing Discussion

For those who aren't already aware, N960U is the model number of all of the US carrier versions of the Note 9. The N960U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit the firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=282951
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to a Note 9, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another carrier's firmware 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

Bootloader 2 added - build SGA

iBowToAndroid said:
Bootloader 2 added - build SGA
Click to expand...
Click to collapse
Thank you, thank you! Now, is it possible to just flash the user data? Or do I need to flash everything again?

rygaul44 said:
Thank you, thank you! Now, is it possible to just flash the user data? Or do I need to flash everything again?
Click to expand...
Click to collapse
That's not enough information. I would need to know what firmware you have now, and what firmware you're trying to go to

iBowToAndroid said:
That's not enough information. I would need to know what firmware you have now, and what firmware you're trying to go to
Click to expand...
Click to collapse
I'm currently on N960USQS2CSGB with my phone being on AT&T's network. Originally it was a Verizon note 9 and I swapped the SIM card. I then flashed the unlocked firmware to it to try to get VoLTE to work, but that didn't work so I flashed N960USQS2CSGA to the phone in hopes that I could get AT&T's firmware working. If I'm understanding correctly the USERDATA is where all the AT&T specific software and code is, so I'm wondering if I flash just the USERDATA, could I get the AT&T specific features to work. I got the OTA update to N960USQS2CSGB but that didn't fix the issue.

rygaul44 said:
I'm currently on N960USQS2CSGB with my phone being on AT&T's network. Originally it was a Verizon note 9 and I swapped the SIM card. I then flashed the unlocked firmware to it to try to get VoLTE to work, but that didn't work so I flashed N960USQS2CSGA to the phone in hopes that I could get AT&T's firmware working. If I'm understanding correctly the USERDATA is where all the AT&T specific software and code is, so I'm wondering if I flash just the USERDATA, could I get the AT&T specific features to work. I got the OTA update to N960USQS2CSGB but that didn't fix the issue.
Click to expand...
Click to collapse
Well, whose firmware/bloat do you have right now?

iBowToAndroid said:
Well, whose firmware/bloat do you have right now?
Click to expand...
Click to collapse
I'm assuming AT&T since some of their apps installed themselves and I have an AT&T boot logo, but I didn't flash the USERDATA when I flashed it back to the N960U firmware from the N960U1.

rygaul44 said:
I'm assuming AT&T since some of their apps installed themselves and I have an AT&T boot logo, but I didn't flash the USERDATA when I flashed it back to the N960U firmware from the N960U1.
Click to expand...
Click to collapse
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference

iBowToAndroid said:
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference
Click to expand...
Click to collapse
Thanks! I guess I'll be buying a new phone then, because I'm missing calls. The phone has to drop down from LTE to make or receive a call and it takes several seconds. I've had people call me and it ring all the way through before my phone steps down. When I make a call it takes about 10-15 seconds before it rings out. Oh well, I appreciate your help and quick replies!

rygaul44 said:
Thanks! I guess I'll be buying a new phone then, because I'm missing calls. The phone has to drop down from LTE to make or receive a call and it takes several seconds. I've had people call me and it ring all the way through before my phone steps down. When I make a call it takes about 10-15 seconds before it rings out. Oh well, I appreciate your help and quick replies!
Click to expand...
Click to collapse
Then that probably means that you don't have VoLTE in your area, or that you have poor signal in your area. I'm not sure that changing phones is going to help

iBowToAndroid said:
Then that probably means that you don't have VoLTE in your area, or that you have poor signal in your area. I'm not sure that changing phones is going to help
Click to expand...
Click to collapse
That was my original thought, but my wife has an AT&T branded note 9 that she bought direct from AT&T and hers works correctly. I'm trying to hold out for the Galaxy Fold, but I may end up going ahead and getting an AT&T note 10

rygaul44 said:
That was my original thought, but my wife has an AT&T branded note 9 that she bought direct from AT&T and hers works correctly. I'm trying to hold out for the Galaxy Fold, but I may end up going ahead and getting an AT&T note 10
Click to expand...
Click to collapse
Then maybe they won't provision your IMEI for VoLTE because they know it's not originally their device. They do that with wifi calling

Up
iBowToAndroid said:
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference
Click to expand...
Click to collapse
Before you buy a new phone, try flashing the latest AT&T update from here along with the user data from this thread if that download doesn't contain it. (It should). I'm trying to download to verify but it's only downloading at 1 MB/s for me.

iBowToAndroid said:
Then maybe they won't provision your IMEI for VoLTE because they know it's not originally their device. They do that with wifi calling
Click to expand...
Click to collapse
I figured as much, thought I'd try everything though. Again, thanks for your help!
---------- Post added at 06:58 PM ---------- Previous post was at 06:47 PM ----------
Bober_is_a_troll said:
Up
Before you buy a new phone, try flashing the latest AT&T update from here along with the user data from this thread if that download doesn't contain it. (It should). I'm trying to download to verify but it's only downloading at 1 MB/s for me.
Click to expand...
Click to collapse
I won't get my hopes up but I'll definitely try this.

rygaul44 said:
I figured as much, thought I'd try everything though. Again, thanks for your help!
---------- Post added at 06:58 PM ---------- Previous post was at 06:47 PM ----------
I won't get my hopes up but I'll definitely try this.
Click to expand...
Click to collapse
Worth a shot if the next step is an entirely new phone.
---------- Post added at 02:46 PM ---------- Previous post was at 01:59 PM ----------
iBowToAndroid said:
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. I know these are much tougher to find than other carriers' files - they can't be obtained from SamFirm or SamMobile. So I'll be uploading at least one for each bootloader version. Firmware is universal on U models so you can use the other 4 Odin files from any other firmware of the same build. Can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
- I remove the .md5 from each file solely for faster flashing (Odin won't check the hash without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
https://www.androidfilehost.com/?w=files&flid=282951
Click to expand...
Click to collapse
Do you ha e the user data for SGB-2? I saw that you have SGA-2. Interchangeable? Or if they are not, do you have SGB-2?

Noob question but if I do flash the N960USQU2CSGA firmware for AT&T with the USERDATA provided here, I should be good for my unlocked Note 9 which is on N960U1UES2CSF9 right?
Also I would be able to get future updates OTA since I have an AT&T sim, right?
Thanks!

xAliasx said:
Noob question but if I do flash the N960USQU2CSGA firmware for AT&T with the USERDATA provided here, I should be good for my unlocked Note 9 which is on N960U1UES2CSF9 right?
Also I would be able to get future updates OTA since I have an AT&T sim, right?
Thanks!
Click to expand...
Click to collapse
Yes, you should then be on AT&T's update schedule

iBowToAndroid said:
Yes, you should then be on AT&T's update schedule
Click to expand...
Click to collapse
Thanks a lot! Did the flash and the OTA for the August update worked on my unlocked Note 9. Bad news is that the Wifi calling doesnt work still.

xAliasx said:
Thanks a lot! Did the flash and the OTA for the August update worked on my unlocked Note 9. Bad news is that the Wifi calling doesnt work still.
Click to expand...
Click to collapse
Just a note, if you are in the us, Google voice offers native wifi calling, if you really need it. I've always had a Google voice number that I use and give out as opposed to my usual mobile number, so it works really well for me.

Please Help!!!
I have the samsung galaxy note 9 F/DS what file would I need to flash to make my phone an at&t phone. I really want the wifi calling and enhanced messaging features. I recently got an OTA update that allowed me to be able to do volte calls but still no video calling wifi calling or enhanced messaging. Please help.

[2022][ROOT] [Extreme Syndicate] [G960U/U1/W][G965U/U1/W][N960U/U1/W]

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Below Method is no longer supported if you choose to use the unstable method below you do so on your own
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It​
EXTREME SYNDICATE ROOT METHOD
​OEM Toggle Does Nothing On US Model Phones
This root method breaks things and most likely will not be able to be used as a daily driver
You can be on any version bootloader. This will update you to V9 bootloader
This method will work if you are on Android 10 or Android 9 Pie but will put you on Android 8 Oreo. There is no root for Android 10 or Android 9 Pie
You will not be able to use magisk
You will not be able to flash full custom rom like Lineage or any other AOSP roms however GSI system images can be used
You cannot flash custom boot images or recovery images such as regular TWRP
Odin does not work on some later computers with USB 3.1 chip controllers the only work around is using a USB 2.0 mini hub
It is your responsibility to make sure you can use adb properly
Root will break things such as safetynet so deal with it
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
Notes:
- Safestrap recovery is now available with working MTP while in Safestrap
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own download section. Download the right stuff!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working except while in Safestrap
- S9 and S9+ also might have some issues with the selfie cam.
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Downloads S9 Files:
Safestrap_S9_Cmd_Line.7z
Download S9+ Files:
Safestrap_S9_Plus_Cmd_Line.7z
Download Note9 Files: -- Only For Bit 8 Or Lower
Safestrap_N9_Cmd_Line_Bit8.7z
Instructions to Inject Safestrap:
1. Download and unzip Safestrap_S9__Cmd_Line.7z for your device
2. Plug phone into computer and run Safestrap.exe
3. Follow instructions on screen to enable USB Debugging
4. Then from there the process will be mostly automatic just follow prompts on screen
5. When done flashing BootSwap file you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
Instructions For Flash Rom:
1. Download below files and copy files for rom to phone system img and vendor img and odm zip
Downloads S9 Files:
Stock_Rom_G960.7z
GSI_Rom_G960.7z
Download S9+ Files:
Stock_Rom_G965.7z
GSI_Rom_G965.7z
2. In safestrap flash system img then vendor img and odm zip .
3. Choose data wipe and advance and check data
4.. Now reboot system you will have to hold buttons to reboot to recovery until you see safestrap splash then click continue. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
5. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
6. Biometrics do not work so don’t try to setup fingerprint or face recognition.
The GSI rom mtp works GSI rom is rooted already just flash phhsupersu.apk found in GSI_Rom zip
If using other GSI roms you have too choose A_Only ones and will probably need to flash the Sh_Remover.zip found in the GSI_Rom zip
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!

Mine

Wow, this is actually pretty good. S9 Snapdragon + treble enabled device? Man, this is going to change everything! I hope something good comes out of this

Does it work on the U/U1 variants of the S9+ as well?

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It’s confirmed working on both SM-G960U/U1 and SM-G965U/U1
Sent from some device I modified

Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.

Argyrus said:
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Click to expand...
Click to collapse
You cannot trip knox on a locked bootloader
Sent from some device I modified

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?

Argyrus said:
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Click to expand...
Click to collapse
Did you not read la couple post above yoir question
Sent from some device I modified

jrkruse said:
Did you not read la couple post above yoir question
Sent from some device I modified
Click to expand...
Click to collapse
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.

Argyrus said:
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Click to expand...
Click to collapse
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified

jrkruse said:
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
Click to expand...
Click to collapse
Awesome, sorry for any confusion.

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
jrkruse said:
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
Click to expand...
Click to collapse
That means I can have root and have Samsung pay? God damn that makes me wet

Dhdeanha said:
That means I can have root and have Samsung pay? God damn that makes me wet
Click to expand...
Click to collapse
As of right now it's still detecting su binaries. So Samsung Pay probably may not work.

On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?

elguy said:
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
Click to expand...
Click to collapse
Don't worry about it. It will work on it, it's been proven to work exactly on Android 9, Dec 2019 security patch.

Wow! that's exciting, I can't wait until this releases. Looks like I'm not updating my phone anymore until then. Especially exciting if it works on Android 9 December 2019 security patch

the question is how likely this will be patched in Samsung's next update and how much time this may cause them to delay their next security patch.

Extreme Syndicate Root for S9 is live!!

Is there any way on earth to rollback to oreo.

I am on binary 10.
Is there any possibility to revert back to oreo.
I hate everything about one UI Pie.
Soo this is my last try, never buying samsung phone ever again.
The question is, Why is it impossible to downgrade?
Is is encrypted or is it that there are not many developers to work on samsung devices?

Vivek Macha said:
I am on binary 10.
Is there any possibility to revert back to oreo.
I hate everything about one UI Pie.
Soo this is my last try, never buying samsung phone ever again.
The question is, Why is it impossible to downgrade?
Is is encrypted or is it that there are not many developers to work on samsung devices?
Click to expand...
Click to collapse
Simple answer, no.
I believe you can't downgrade due to security policy updates.

Vivek Macha said:
I am on binary 10.
Is there any possibility to revert back to oreo.
I hate everything about one UI Pie.
Soo this is my last try, never buying samsung phone ever again.
The question is, Why is it impossible to downgrade?
Is is encrypted or is it that there are not many developers to work on samsung devices?
Click to expand...
Click to collapse
No you can't!
Bootloader will check the version number and if it is 9 and below it will tell Odin to show FAIL CHECK Binary message and it won't continue to flash anything.
Even if you root your phone you can not downgrade your bootloader!
No one has found the keys or the info needed to make it downgrade. Samsung added self checks so that it doesn't downgrade due to security concerns!

How about if you flash a different firmware like Verizon firmware and your T-Mobile /MetroPCS for unlocking bootloader.

Googleme35 said:
How about if you flash a different firmware like Verizon firmware and your T-Mobile /MetroPCS for unlocking bootloader.
Click to expand...
Click to collapse
On SM-N950U/U1/W You CAN NOT UNLOCKED your bootloader period!
Doesn't matter what firmware from which Carrier it won't unlock bootloader since they are all the same firmware just with different CSC'S and No changing CSC'S won't unlock bootloader either so don't ask.
The ONLY note 8 phones that can be UNLOCKED are SM-N950F/ N/ F/DS exynos models and SM-N9500 Chinese snapdragon models and no you can not use SM-N9500 firmwares on SM-N950U/U1/W Samsung made enough changes that it would brick your phone.

Finally managed to get Android Oreo back on my samsung Note 8 N950F.
My device Info:- Samsung Galaxy note 8 SM-N950F
Unlocked the boot loader and flashed TWRP recovery, then installed OREO S9+ LIGHT ROM(LOV THIS ROM).
WOW I never thought i could run Oreo on a boot loader binary version 10.
Got my old camera back, & the device is fast just like new.
Only thing is tripped e-fuse and Warranty void= 1, which means Samsung pay and secure folder will not work forever.
Anyways did not use samsung pay or secure folder, So im not really bothered.
Link for custom ROM click here https://forum.xda-developers.com/galaxy-note-8/development/rom-lightrom-t3768385

Vivek Macha said:
My device Info:- Samsung Galaxy note 8 SM-N950F
Unlocked the boot loader and flashed TWRP recovery, then installed OREO S9+ LIGHT ROM(LOV THIS ROM).
WOW I never thought i could run Oreo on a boot loader binary version 10.
Got my old camera back, & the device is fast just like new.
Only thing is tripped e-fuse and Warranty void= 1, which means Samsung pay and secure folder will not work forever.
Anyways did not use samsung pay or secure folder, So im not really bothered.
Link for custom ROM click here https://forum.xda-developers.com/galaxy-note-8/development/rom-lightrom-t3768385
Click to expand...
Click to collapse
Read this thread to get secure folder working:
https://forum.xda-developers.com/galaxy-note-8/development/secure-folder-patch-custom-rom-t3949878
Hopefully it was added to lightrom but if not you can do it.
Good luck!

Vivek Macha said:
My device Info:- Samsung Galaxy note 8 SM-N950F
Unlocked the boot loader and flashed TWRP recovery, then installed OREO S9+ LIGHT ROM(LOV THIS ROM).
WOW I never thought i could run Oreo on a boot loader binary version 10.
Got my old camera back, & the device is fast just like new.
Only thing is tripped e-fuse and Warranty void= 1, which means Samsung pay and secure folder will not work forever.
Anyways did not use samsung pay or secure folder, So im not really bothered.
Link for custom ROM click here https://forum.xda-developers.com/galaxy-note-8/development/rom-lightrom-t3768385
Click to expand...
Click to collapse
I have a question, do you think that camera it's better on Oreo? I think that samsung with updates just destroied our camera!

Taking photos is quicker than my brother's Note 9.
zyxw-androidiani said:
I have a question, do you think that camera it's better on Oreo? I think that samsung with updates just destroied our camera!
Click to expand...
Click to collapse
The camera is very snappy now,Much cleaner photos ,Sharper, Quality of the photos is amazing, Just the way it was when i first got the phone. I even compared it with my brother's Samsung galaxy note 9 running on Android 10 One UI 2.0, My Note 8 is taking photos quicker than the Note 9 now(My bro was shocked). Samsung is deliberately slowing down phones via updates & even blocking ways to downgrade to previous stock official OS, just to keep us upgrading to their new phones.
I just downgraded to oreo because of the shutter button zoom feature, The feature which is not found in any phones currently.
Back to awesome photography again.

Vivek Macha said:
The camera is very snappy now,Much cleaner photos ,Sharper, Quality of the photos is amazing, Just the way it was when i first got the phone. I even compared it with my brother's Samsung galaxy note 9 running on Android 10 One UI 2.0, My Note 8 is taking photos quicker than the Note 9 now(My bro was shocked). Samsung is deliberately slowing down phones via updates & even blocking ways to downgrade to previous stock official OS, just to keep us upgrading to their new phones.
I just downgraded to oreo because of the shutter button zoom feature, The feature which is not found in any phones currently.
Back to awesome photography again.
Click to expand...
Click to collapse
That's great thank you for your answer. I just saw some old photos that I taked with my note 8 on Oreo and thay was great and now on Pie i treid to take same photos but it's like impossibile.

Vivek Macha said:
My device Info:- Samsung Galaxy note 8 SM-N950F
Unlocked the boot loader and flashed TWRP recovery, then installed OREO S9+ LIGHT ROM(LOV THIS ROM).
WOW I never thought i could run Oreo on a boot loader binary version 10.
Got my old camera back, & the device is fast just like new.
Only thing is tripped e-fuse and Warranty void= 1, which means Samsung pay and secure folder will not work forever.
Anyways did not use samsung pay or secure folder, So im not really bothered.
Link for custom ROM click here https://forum.xda-developers.com/galaxy-note-8/development/rom-lightrom-t3768385
Click to expand...
Click to collapse
So that's all you needed to do?
What version is the camera?

Camera version is 7.6.78.
MystaMagoo said:
So that's all you needed to do?
What version is the camera?
Click to expand...
Click to collapse
Yes that's all I did to go back to oreo.

Vivek Macha said:
Finally managed to get Android Oreo back on my samsung Note 8 N950F.
My device Info:- Samsung Galaxy note 8 SM-N950F
Unlocked the boot loader and flashed TWRP recovery, then installed OREO S9+ LIGHT ROM(LOV THIS ROM).
WOW I never thought i could run Oreo on a boot loader binary version 10.
Got my old camera back, & the device is fast just like new.
Only thing is tripped e-fuse and Warranty void= 1, which means Samsung pay and secure folder will not work forever.
Anyways did not use samsung pay or secure folder, So im not really bothered.
Link for custom ROM click here https://forum.xda-developers.com/galaxy-note-8/development/rom-lightrom-t3768385
Click to expand...
Click to collapse
I want to try rhis I updated and my camera takes **** photos and I cannot use scroll capture.
Any advice?

[S21 SM-G991U/U1/W_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]

Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-G991U/U1/W- Model
USERDATA_AIO_G991_FORCE_WIPE_NO_BL_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
G991USQU4AUFD_BIT1_SAFE.7z
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G991_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
S21+ SM-G996U/U1
S21 Ultra SM-G998U/U1
TWRP Recovery Provide by @Mentalmuso
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G99*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G99*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7

Hi @jrkruse I dont see anything in Post #2. Might you share "Info For Bootloader Unlocks Can Be Found In Post 2"

991U1 USA Snapdragon
I finished unlock with afaneh and then I flashed USERDATA_AIO_G991_FORCE_WIPE_NO_BL.tar.md5 but ended up with bootloop.
https://imgur.com/WG7uFma
I then went back to post to read. Was I supposed to flash both stockfirmware and the tar file? I only did the tar file in USERDATA slot.
EDIT: Nvm. The black download links download the S20 (981) tar file and that's what I ended up flashing. Fixed by flashing the orange links for the S21 (991).

So I was sent here from the unlocked samsung bootloader's group in telegram because someone's been helping me there for the last day and a half trying to get my Samsung Galaxy watch 3 to pair with my wearables app on my unlocked and rooted s21 ultra and we've had no luck so I guess my question is how does this work? and what do I need to do?

jmac052002 said:
So I was sent here from the unlocked samsung bootloader's group in telegram because someone's been helping me there for the last day and a half trying to get my Samsung Galaxy watch 3 to pair with my wearables app on my unlocked and rooted s21 ultra and we've had no luck so I guess my question is how does this work? and what do I need to do?
Click to expand...
Click to collapse
Were you successful pairing you galaxy watch? I was able to pair mine after receiving help from Ali. 3 files need to be modified. If you still need help I have the files and would be willing to share with you so you can see what needs to be edited.

Jnewell05 said:
Were you successful pairing you galaxy watch? I was able to pair mine after receiving help from Ali. 3 files need to be modified. If you still need help I have the files and would be willing to share with you so you can see what needs to be edited.
Click to expand...
Click to collapse
Man Ali helped me alot but still we aren't being able to connect yeah I would love the files...I'm willing to give anything a try at this point! Thanks for reaching out!

jmac052002 said:
Man Ali helped me alot but still we aren't being able to connect yeah I would love the files...I'm willing to give anything a try at this point! Thanks for reaching out!
Click to expand...
Click to collapse
There is a updated version of the galaxy wearable fix in the telegram chat. I am rooted with magisk so i used root explorer to navigate to vender/etc/vintf/ here are two files that need modifying called manifest_lahaina.xml and manifest_shima.xml. Following the guide from the telegram you can execute 3 a few commands in terminal. Or just replaced the files included in the zip and reset the permissions. Permissions need to be rw-r--r--.

Jnewell05 said:
There is a updated version of the galaxy wearable fix in the telegram chat. I am rooted with magisk so i used root explorer to navigate to vender/etc/vintf/ here are two files that need modifying called manifest_lahaina.xml and manifest_shima.xml. Following the guide from the telegram you can execute 3 a few commands in terminal. Or just replaced the files included in the zip and reset the permissions. Permissions need to be rw-r--r--.
Click to expand...
Click to collapse
Also shared by Ali was fix for smart view and shealth, it's not part of this flashable in OP but think gear fix should be at least discussed. You'll have to modify system/build.prop
Ali stated "For screen sharing and S health following need to be in build prop : ro.config.tima=0
ro.config.iccc_version=iccc_disabled
wlan.wfd.hdcp=disable"
I also edited ro.config.nox=v30 changed it from 30 to 00 so that secret mode works in the samsung browser. See screenshot. And again set permissions to rw-r--r--
Hope this helps!!

I don't suppose any of this watch trickery is in any way applicable to samsung pass?

Does not help samsung pass. I don't know exactly details but samsung pass looks at knox trip and will not work once tripped. Have looked around for a fix but have not had any luck.

Updated files in OP fixed sum bugs. Added new safetynet patch and I think wearable fix now works

Worked like a charm the 1st try. It feels good to be rooted on a Samsung device again. My previous Sammy with root was the s5. Thank you very much!

Are you going to update this to the June patch? I'm hoping to get the Heat issue fix which June addressed.

How do I check to see which bootloader version I have?

The link is incorrect in the OP and links to the SM-996U1. Does anyone have the updated link?

Can you or anyone confirm this works on already magisk rooted G9910?
I just finished setting up the phone and temporarily lost root when i renamed the Magisk app, had to reflash the patched IMG with HOME_CSC and thank god i didnt lose settings
My whole reason for TWRP is the backup/restore functions, so i never have to suffer this kind of heart attack again
I'm on OneUI 4.1 .. is that what "DONT MIX BIT 1" means? should i avoid?

Downgrade from Android12 possible?

I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?

on my s10+ i get se same Issue. According official samsung information, it seems that gear VR do not run on android 12. I did not find any solution for now.

Methanoid said:
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
Click to expand...
Click to collapse
Sorry don't know anything about gearVR, but no, if the bootloader version has increased, which I believe it does when going to A12, then you can't downgrade.
I'm pretty sure there is no xda 'work'a'round' for that, haven't seen one and everything I've read indicates not possible. Do some searching I guess to be positive, but one prereq to bootloader unlock is being on a specific BL version, and even their directions indicate if you're above that version, nothing you can do.
cheers

Thanks for replying... I guess I am boned

I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !

tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.

Yes.I think they left compatible downgradable bootloader for those users who didn't saw info about GearVR support as a last chance to revert.
I presume,as we learned from previous updates, in future releases of A12 downgrade will not be possible because of their privacy paranoia.

AsItLies said:
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Click to expand...
Click to collapse
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.

Johnm77 said:
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Click to expand...
Click to collapse
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck

AsItLies said:
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
Click to expand...
Click to collapse
Thank you for your help!
I figured the most recent update of A11 from
Galaxy Firmware - Samsung Galaxy S10 SM-G973U (CHA) | G973USQU6GUJ3
This Firmware flash for Samsung Galaxy S10 with the Phone Model Number SM-G973U for region 🇺🇸 United States with CSC code CHA and R(Android 11) OS.
galaxyfirmware.com
is what I would need.
The Baseband I have from A12 currently is G973USQU6HULD, so from what was said here the BL ver. 6 means I should be able to do it.
Model #, Country, region/carrier from the above link all match my specs. So if I'm to understand correctly all I should have to do is backup and then use the firmware with odin to flash to my device using tin2404's procedure from above? (Flash all A11 stock firmware package and choose CSC instead of Home_csc !)

tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?

Johnm77 said:
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Click to expand...
Click to collapse
Update:
Successfully used odin to revert to os11, had to factory reset after odin completed, then I just reloaded my backup.
After more research I decided to block all future updates using ADB and this method:
No more headaches with my software!

Actually, it is neccessery to choose clear CSC to erase leftovers..Choosing Home_CSC brings various of errors possible.
Workaround is doing TWRP backup on SD Card then after clear flashing restoring ONLY data partition.