yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 9 Guides, News, & Discussion] BigE:
That's probably because you try to 'update' rather than flash the whole deal. You can't update a U1 oreo to a U pie . You need to download a complete 4.6 gig of data and flash using Odin. All those 'OTA' smaller 1.8 gig packages will not work . Look for N960USQU1CSB3 for TMO , unzip on a computer and flash with ODIN.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tdewitt34:
THANK YOU.....no one explained that to me. Thanks
[Samsung Galaxy Note 9 Guides, News, & Discussion] BigE:
Just be aware what you risk.. I am not 100% sure we can go back to U1 when we wish for it. For sure not all U versions are downgrade able..

What I hate about the TMO version is they push their boot screen and annoying startup music. Just hate it. It was so much quieter originally out of the box from Samsung..
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Why wouldn't you be able to flash back? All of the firmware is still on the v1 bootloader. There is nothing stopping you from flashing back, if done properly. Going backwards from Pie to Oreo requires a wipe to ensure there are no issues.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tdewitt34:
So to be clear I can flash back to Oreo if I need to after flashing to Pie? Also is it the SM N-960U version I can flash right as mentioned before? I plan on doing this today since I've got time.
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Yes! Any U, U1, and W firmware device can be currently flashed back from Pie to Oreo if the bootloader version is the same as thebfirmware you are flashing back to, but you can't use the HOME_CSC. You need to use the proper CSC, which will wipe your device, to safely flash backwards to a previous major version of Android.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Mr. Orange 645:
Well I am 100% sure you can flash back to U1. All the U/U1/W models are still bootloader v1 so you can cross flash and downgrade. As long as they are on the same bootloader version you can cross flash between the three.

I also hate the T-Mobile boot jingle, but it's really the only bloat ware T-Mo pushes. You can silence it two ways. There's an app (sorry I can't remember the name) that silences your boot animation without root. Or you can just turn system volume all the way down. That just affects touch sounds, camera sounds, and boot animation.

Yes. As stated, as long as you're still on bootloader v1, you can downgrade. None of the US Note 9 models have upgraded bootloaders yet so you're safe.

Not sure I understand your last question, but if you're wanting the official Pie, you can use patched ODIN to flash N960USQU1CSB3 on any N960U/U1/W. Carrier doesn't matter.

Actually CSC_OYN no longer causes a factory reset, so you have to manually do a factory reset when downgrading to avoid a boot loop.
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
That's good to know. The last time I flashed back, the OYN CSC did the factory reset.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Mr. Orange 645:
Yeah..I usually do a factory reset anyway, so I didn't notice it. But several people reported it no longer causing the factory reset. I haven't personally tested it yet.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tonys.94:
Flashed this today not realizing it was the August of 2018 version. It went through fine, did a basic setup, then it kept updating/restarting until it got to the Dec 18 update as the last update. Which is where I was before mistakenly reflashing this August 18 one. Now, I can't flash anything else. Mines originally ATT, and I flashed this either August after it showed up, or a month or two later, and used it up till now. I've tried using Odin to flash the ATT Stock Oreo and the Unlocked. Both get stuck at Setup Connection in Odin, and now this ROM I just flashed not 2 hours ago, gets stuck in the same spot. I've tried multiple factory resets, booted into the OS and in recovery mode, clearing cache part first as well. Still gets stuck on Setup Connection.
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Do you have USB Debugging in Developer Options enabled? Are you using the modded or patched ODIN 3.13.3? Are you connecting the device to a USB 2.0 port in Download Mode before opening the modded or patched ODIN? Is the version of the firmware you are trying to flash the same bootloader version or newer?
[Samsung Galaxy Note 9 Guides, News, & Discussion] tdewitt34:
Sorry I'm following this thread what's the difference when using modded Odin?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Thebpatched and modded ODIN versions are used to convert the device from one firmware to a differemt firmware, but this can also allow flashing back from Pie to Oreo where some firmware versions try to block that from happening.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tdewitt34:
So if I encounter this problem then I need to make sure I use the same version of firmware and use the same Odin type.....is that correct?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Potentially. If done right, you shouldn't have any issues. Some systems have shared USB issues that might make it impossible to flash from that system,l.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tonys.94:
I originally flashed this August 18 version shortly after it's upload here. Then used it up till now with all the updates installed as they came OTA. Today I didn't realize it was the August 18 version before flashing it with Odin, however it went through just fine and I reinstalled all of the OTA updates up to the Dec 18 ARL1. After that I downloaded the stock ATT and unlocked ATT firmware's and attempted to flash via Odin. The unlocked ATT is also ARL1. Before flashing the first time I did not have USB Debugging enabled and subsequent flashes I did not have it enabled. I used the patched version of Odin supplied by the OP the first time I flashed today with no issues, subsequent flashes I tried the same patched Odin and a non patched Odin and both get stuck at Setup Connection. The first time I flashed and was successful, I was connected to a USB 3.0 port, subsequent flashes I was using the same USB 3.0 port as before, with the USB 3.0 cable that came with my Note 8, and using my brand new one that came with my Note 9 that was still in it's box. I've tried keeping it plugged in while booting to download mode, and waiting till it was at the continue screen, both ways provided the same Setup Connection. I have tried flashing the TMB ARH2 supplied by the OP, which the first flash today worked fine no issues, then I proceeded to update to Dec AR1L through OTA updates. The subsequent flashes that failed were ROM's ARG6 which is stock Dec ATT, the ATT unlocked version of ARL1, and then again the TMB ARH2 supplied by the OP. All of those ROM's use Bootloader V1 as far as I knew. I have not tried upgrading to Pie with this phone since I've had it either, and Pie is still bootloader V1 as well, from what I understand.
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
You keep mentioning the unlocked ATT version. There is no unlocked AT&T ifficial firmware! There is also no official unlocked TMB firmware. Any carrier apecific firmware with the U1 non-carrier specific base is a combination firmware.

When flashing backwards from Pie, you need to flash the firmware before Pie. Depending on the firmware, that could be ARL1, ARL3, or another.

Flashing carrier firmware, especially AT&T, requires the userdata that goes specifically with that firmware. Using an old version of the userdata with an updated firmware can cause issues agter flashing. When USB 3 doesn't work. USB 2 usually does.

You should not dirextly flash from one carrier firmware to another. Flash to the XAA U1 with the OYN CSC and wipe. If it doesn't wipe diring flash, then wipe rheough recovery if you get a bootloop. Then flash to the different carrier U firmware agter skipping through the setup to re-enabke USB Debugging. .
[Samsung Galaxy Note 9 Guides, News, & Discussion] graphilo:
i have a N960U AT&T locked it ask a network unlock code. if i flash the unlocked N960U1UEU1ARH2 will it accept any sim card?
[Samsung Galaxy Note 9 Guides, News, & Discussion] pcriz:
Nope
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
The non-carrier firmware does not alter or affect the SIM lock state of the device.
[Samsung Galaxy Note 9 Guides, News, & Discussion] oldmoney:
Can i flash usa unlocked version pie to my t mobile note 9 on official t mobile pie. Goal is to get rid of t mobile boot up logo and if so will i able to receive official ota from samsung?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
If U1 Pie is available, you can flash directly to it. I don't believe it is though, so you will have to flash backwards with wipe to TMB U 1ARL1, then flash with wipe to the XAA U1.
[Samsung Galaxy Note 9 Guides, News, & Discussion] oldmoney:
Thanks much. I believe its out already out upon typing this

With that said do you think i have to flash csc home or complete wipe? If update zip available can i just do that straight without odin? Thanks jcsww
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Never use the HOME_CSC when cross-flashing! It will cause the device to not convert properly, leaving bloatware, carrier branding, and so on behind, but will alao prevent the LTE band availabiliry from being properly changed.

An update.zip will not convert the device. You need to use a full firmware image, you need the modded or patched ODIN 3.13.3 to cross-flash, and factory reset after the flash if the device doesn't automatically.
[Samsung Galaxy Note 9 Guides, News, & Discussion] phat0074:
Will this allow you to use different carrier sim cards?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Changing firmware does not change the SIM lock status of your device. If your device is SIM locked to a specific carrier, it will remain SIM locked if you flash a different firmware to whatever carrier it was originally SIM locked to. If your device was not SIM locked, then it will remain that way regardless of which firmware you flash.
[Samsung Galaxy Note 9 Guides, News, & Discussion] phat0074:
So what's the point of this firmware, is it just for a different carrier's apps to be on your phone
[Samsung Galaxy Note 9 Guides, News, & Discussion] evnStevn:
Yep...pretty much! smh
[Samsung Galaxy Note 9 Guides, News, & Discussion] galdypr:
Hi.

Will be available for ONE UI Android Pie?

Thanks
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
I'm confused by the term "unlocked", because to me, an unlocked bootloader would mean having root, which has not been obtained yet: https://xdaforums.com/galaxy-note-9/how-to/n960u-u1-t3897797
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Unlocked should refer to the SIM status of the device. However, some people seem to refer to the non-carrier specific firmware (U1) as unlocked, because it originally comes loaded on a device that is not SIM locked to any carrier. The U1 firmware has absolutely nothing to do with and does not alter the SIM lock/unlock status of any device.
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
So the two downloads in the OP (original post) are for the complete "stock image" (AP,BL,CP,CSC,HOME_CSC) as if you had a:

T-Mobile N960USQU1ARH2:

A T-mobile secific phone (I guess that's what an N960U is, although there's a Sprint phone that has that model number as well**) at update level ARH2

T-Mobile Unlocked N960U1UEU1ARH2:

A U.S. non-carrier N960U1, that's had a T-mobile update to level ARH2

** to confuse things further, the N960U Sprint phone has the exact same hardware as the N960U1, where the difference in the model number is that it has a different "stock image"

I'm calling it a "stock image". Is there a better phrase or word for that?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
There is no T-Mobile U1 official firmware! The TMB U is the actual firmware, just like all US carrier firmware are U. The U1 non-carrier firmware is basically a generic firmware to try to be more compatible as best as possible with all carriers. The TMB U1 in the OP is a mix of the U1 base firmware with the CSC and userdata for T-Mobile.
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
Mr. Orange 645 wrote: "Whichever it is, you can just flash the ATT firmware, and it will work perfect on ATT. All the N960U and U1s are identical. Just different firmware."

But how can that be, if different models have different band support:

https://www.techwalls.com/samsung-galaxy-note-9-sm-n960-model-number-differences

"They do not only differ in chipsets but also in cellular bands."

I've also found reference to other model numbers:

Samsung,Galaxy Note9,crownlte,SM-N960F

Samsung,Galaxy Note9,crownlteks,SM-N960N

Samsung,Galaxy Note9,crownqltechn,SM-N9600

Samsung,Galaxy Note9,crownqltecs,SM-N960W

Samsung,Galaxy Note9,crownqltesq,SM-N960U

Samsung,Galaxy Note9,crownqlteue,SM-N960U1

The simplest idea, is that if it's the same chipset, it's all the same radio hardware. Then the carrier specific firmware disables the unused bands? What about roaming?

I wonder if the U1 firmware works just as well on the T-Mobile network, in terms of compatibility with T-Mobile towers (signal, tower switching, incorrect connection "I can hear you, can you hear me?", etc). Does T-Mobile just work on ironing out the bugs with their own firmware, and not so much the non-carrier firmware?

According to http://imeipro.info/samsung_imei_check.html

I have a SM-N960UZKASPR, which is a sprint phone. My "about phone" says it's a SM-N960U1. On the physical back-side of the phone, it's a SM-N960U. I've gotten some updates when I connected to T-Mobile with their SIM, and have baseband N960U1UES1ARH6.

There is A3LSMN960U, but no U1: https://fccid.io/A3L. In fact, there is only SMN960KOR, SMN9600, SMN960U, SMN960F.

If there is only 4 actual hardware models (at least with the FCC), then this page just confuses everyone: https://www.techwalls.com/samsung-galaxy-note-9-sm-n960-model-number-differences. Is there a page that is clearer, one that sorts by what the hardware actually is, rather than confusing model numbers?
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
To my knowledge and from actually flashing. The U, U1, and W are all cross-firmware compatible with each other. Flashing my W to U1 and then to TMB U gave me band 71, which is not included in the W firmware. I have tested band 71 to actually be working on my W model, but it only appears when the U1 or TMB U firmware are installed.

If you cross-flash properly, you will be able to get OTA updates for whatever firmware you are on. My TMB U firmware Canadian purchased Note 9 and S9 Plus all get OTA's for the TMB U firmware, which is what is installed on them. Flashing the TMB U1 will not get you OTA updates because all of the firmware components do not match up with their correct build numbers.

AT&T restricts their features (WiFi Calling, HD Voice, and so on) to devices only sold by them. If you purchase your device from another company and flash it correctly to the AT&T firmware. It does work, but only if your AT&T account is locked in with an IMEI of a device sold to you by AT&T. T-Mobile does not restrict network features in this way, so cross-flashing is much more friendlier for anyone on T-Mobile or switching to T-Mobile that hasn't purchased their device from T-Mobile.

All updates for all U, U1, and W firmware come from Samsung directly. The years of the carriers messing up firmware for their devices has been over for quite some time. Each carrier does do some testing with the firmware before it is released to fine tune their carrier aggregation, test their apps, etc., but the final testing process and push is done by Samsung.
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
AP: is your system partition with recovery and stuff.

BL: your bootloader

CP: your modem

CSC: this is what features you get in some countries or carriers like Wi-Fi Calling.

Questions by numbers:

1) In order to maintain the best compatibility with phone towers, you should have the latest baseband (CP), correct? At least, that's what makes sense to me.

2) Do any of the other components have to match in build number, like the BL or CSC? Is it just the baseband and Android build number that need to match up?

In the future, if I wanted to stay on Oreo, but wanted to have the latest baseband, then I understand I would lose OTA updates because all the "components do not match up with their correct build numbers". In "about phone" -> "software information", I see that the baseband and build version numbers match up. I assume the build number means the Android build number.

3) I could always keep my baseband up to date by manually flashing the latest, right? The older Android will be able to communicate fine with the newer baseband?

Before my Note 9, I had a Note 3 with SlimKat custom rom running with the latest 2017 T-Mobile baseband. I don't know that I could tell, if the radio service was inferior, since I didn't have a stock and modern phone sitting next to me. I did have some issues with SMS not coming through, until I updated to the latest baseband.
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
Phonemore.com says there are just 3 hardware variants (not counting the differences in RAM):

https://www.phonemore.com/samsung-galaxy-note-9/models/1868

I think phonemore isn't counting the Korean version SM-N960N, which I guess the FCC calls SMN960KOR

I feel less freaked out. I also found this in another thread, about the meaning of "about phone" -> "Software Information" -> "Service Provider SW version":
[Samsung Galaxy Note 9 Guides, News, & Discussion] BladeRunner:
MY experience with U1 firmware on T-Mobile has been less than spectacular. At my house I have Band 71 only and on U1 my Note 9 will either roam on AT&T or drop the signal all together (I get a "no network" or somesuch, message) while on the U firmware it holds the signal, doesn't roam and I always have a data connection. U1 works perfectly if I am at work where I am connected to a strong Band 4 signal.

I have also had issues with a Pixel 3XL and an iPhone XR roaming on AT&T at my home location and my google fi SIM has been wonky at times about connecting to Band 71 if it has another option.

So it seems to me that T-Mobile has something optimized in their firmware settings that plays better with Band 71.

Just my personal experience YMMV.
[Samsung Galaxy Note 9 Guides, News, & Discussion] tone417:
u1 april patch.
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
Thanks for your response. You probably already know this, but I find this app useful in comparing the signal strength of available bands (not a strong recommendation, as it's the only way I've done it): https://play.google.com/store/apps/details?id=net.simplyadvanced.ltediscovery

I'm curious if your phone ignores (or gets ignored by) band 71 on U1 firmware, or doesn't even see it.
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
LTE Discovery has issues with band 71. Use Cell Mapper if you want correct readings and information.
[Samsung Galaxy Note 9 Guides, News, & Discussion] adibeckett:
Hi everyone, so my dad has a note 9 phone that was bought on eBay that says its 960U1 but in looking at its imei, its actually an AT&T (UZBATT) phone that the seller just flashed the firmware to U1?

I've gotten all the OTA updates and have been able to enable WiFi calling but I don't have the option for Volte. Should I flash the tmobile firmware since my dad is on Metropcs or AT&T since that is the "original" firmware? Will he get OTA updates on either firmware or will we have to update manually through Odin each time?

Oh and is there a guide to flash through Odin for the first time?

Thanks everyone!
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
Yes

Check your "Service provider SW ver." (settings -> about phone -> software information). You will see TMB / TMB / ATT or something like that. Find out what it should be for your carrier. Only the first two matter: it doesn't matter that the last one will always be ATT.

I know it's a lot of posts that you didn't read in this thread (I did the same thing), but if you do read them, your questions will be answered, and they'll be answered better than my response.
[Samsung Galaxy Note 9 Guides, News, & Discussion] adibeckett:
Thanks for the fast reply!

Just checked the "Service provider SW ver" and it says: TMK/TMK/ATT

After some googling: TMK is Metropcs and I would need metro firmware or Tmobile would be fine?
[Samsung Galaxy Note 9 Guides, News, & Discussion] mraeryceos:
I think the OTA updates from having the Metropcs sim card took care of everything for you.
[Samsung Galaxy Note 9 Guides, News, & Discussion] adibeckett:
I see, to be honest the reason why I wanted to flash tmobile firmware was to get Volte but when I was activating the metro sim card for this phone they said I should have that option in Mobile Network setting but it's not showing.

Maybe I need to visit a Metropcs store...
[Samsung Galaxy Note 9 Guides, News, & Discussion] jcsww:
Samsung hides their settings in stupid places! Go to the Dialer, tap the 3 dots in the top right corner, go to Settings, and it should be in there somewhere along with WiFi Calling.
[Samsung Galaxy Note 9 Guides, News, & Discussion] adibeckett:
I tried looking there and in Mobile Network Settings and the Volte option isn't in either of those places :(. Thanks for the reply though!
[Samsung Galaxy Note 9 Guides, News, & Discussion] BladeRunner:
It's not that the U1 firmware doesn't see band 71, it does. It won't hold on to a weak signal and stay connected to Band 71 like the U firmware does.
[Samsung Galaxy Note 9 Guides, News, & Discussion] ILuvRice:
I just flashed the cd1 firmware on my unlocked note 9 and it definitely shows as a AT&T note 9 but wifi calling doesnt work and phone calls still drop to 4G. Anyone have any ideas. I thought it would work?
[Samsung Galaxy Note 9 Guides, News, & Discussion] evnStevn:
May Security Patch/Update For Note9 Unlocked(SM-N960U1):

It finally got here....CSE3 is being released via OTA with all major carriers(except mine, tmobile, at present)!?

Weighing-in at 600 mg,, I grabbed this a.m. via samfirm(tool, 3.6 zip) and took care of myself(NO WAITING)!!

Rumor has tit, it has some of those earlier promised enhancements from mother-Samsung (that the int'l. folks received in early-may), but haven't had a minute to verify!

Safe Journeys to all!
[Samsung Galaxy Note 9 Guides, News, & Discussion] pTeronaut:
This is not it. CSE3 is the May security update, not CSF1 which is the June security update with the camera improvement.
[Samsung Galaxy Note 9 Guides, News, & Discussion] evnStevn:
Yes, your correct...what's odd, is that I corrected my post an hour or so later and it's nowhere to be seen!?

Thanks for getting the correction out there...I obviously did not and didn't check! Sorry folks, chalk it up to "newbie-ism"...idk.
[Samsung Galaxy Note 9 Guides, News, & Discussion] carrilloevo:
Just receiving the update with the June patch, tought it was a 700+mb update....... View attachment 4781830
[Samsung Galaxy Note 9 Guides, News, & Discussion] boomny:
No camera improvements on latest tmobile update. Typical tmo
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
AT&T Note9 is rolling out live 1CSF1 as well.

June patch.
[Samsung Galaxy Note 9 Guides, News, & Discussion] carrilloevo:
Does it comes with the camera update?
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
No unfortunately USA hasn't got it yet.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
Here's Link For June Patch N960USQS1CSF1 Odin Files https://androidfilehost.com/?fid=6006931924117902468
[Samsung Galaxy Note 9 Guides, News, & Discussion] g1-and-only:
Thank you. Are there any camera improvements. In still on 8.1 because the camera seems a little faster.
[Samsung Galaxy Note 9 Guides, News, & Discussion] Venom0642:
USA hasn't yet got the camera night mode, only Exynos has it atm.