[Samsung Galaxy Note 9 Questions & Answers] bober10113:
to my knowledge bands are hardware dictated. if device supports a particular set of bands then its up to what the carrier can offer that matters. the exchange between carrier and phone capabilities is in efs/nv_data.bin i believe.

why i believe this is that my korean exyno n960n device originally did not support carrier aggregation. that being said all single hardware bands that my device was physically capable of, was connecting to my canadian provider. (only 2 bands were not supported). but i could not achieve CA. which sould have let me connect to multiple bands at once to help out signal strength / bandwidth .

i eventually was able to get it working. during my tests i narrowed it down to the nv_data.bin file. i had 2 backups of the efs directory with 2 different states of this file. one prior CA capability and one with it. i can go back and forth between the two states. this proves to me that csc does not contain any band capabilities and that if physically a devices hardware specs is rated to be capable then inevitably it can do it. in my case the device now acts as if it was its north americain snapdragon counterpart. since both are gsm it was to be expected. i can also acheive all carrier specific options like wifi calling, volte, call recording ...etc which are software. manualy editing and coping over the Canadian csc from the snapdragon made it so that my exynos is almost undistinguishable from a Canadian one. the only problem is evil carriers that whitelist their phones. meaning that BYOD are black listed for certain features. especially for wifi calling. this is not something the end user can ever get around. its company policy and managed on their side. i switched carriers because of this. to one that does not practice this criminal behavior. i know for a fact that in the US this is also common amongst certain carriers.

in your case n9600 has CDMA capabilities just like the americain Qualcomm snapgragon. what makes your situation even more likely to succeed is that the hardware is extremely similar. unlike me both south American and north americain devices are snapdragon based. so i suspect that right off the bat for cell and data connection you should have 100% compatibility bandwise. now for carrier features, i believe volte should work without doing anything. call recording might even work on pie since that region might not have had any new restrictions. americian call recording is a politics thing and i really believe it was pressure from the government and or FCC that made android remove it. since these features are software, i have no trouble believing that they will be either working by default whether it maybe be in oreo or pie or by manually editing the system via root. moreover with a rooted device you will get to choose exactly if and when your device should stay on oreo or go ahead with pie.( again, pie has nothing to do with not being able to achieve or be able to acheive native call recording or gain access to americain carrier features. its all software and and politics. and carriers black listing non carrier bough pone imei's)

the proof is my device which is dissimilar in hardware and yet now has the exact same features thanks to rooting and a little tinkering.

plus i have been maintaining a csc pack that includes:

canadian

americain

european

multi csc firmwares.

this is based on tkkg1994 and djb77 work. i simply added note 9 and note 8 compatibility in 1 package for international F and korean N devices and am curious to see if down the road i can add something for the n9600 as well and get you to root your device and help out testing...lol

i use it to flash over custom roms to get back my carrier features. it would also work on stock rooted firmware aswell.

so if ever you do buy a n9600 device and root it then i hope you are willing to test out some stuff....for science! and of course day to day needs. also tekhd's pack is also a good solid option and had been tested and proved. i might have a look under the hood at how he made his.