[Samsung Galaxy Note 9 Guides, News, & Discussion] bober10113:
so i tested att and tmo detonator packs and it did not grant be any benefice in CA using

#*0011#

while i was on tekhd's site i notice that he released a rom for latest pie firmware. its 2 parts, one is the rom the other the carrier.

so i just aimlessly took tmo. so flashed both packages and after first boot, i noticed a + sign beside the 4g logo : 4g+

so i went and use the 0011 Dial code but it didint work at all. so i was about to go look up other dialer codes and for some reason i decided to open the camera app. it immediately crashed my phone and showed me the only official released binaries...etc message.

it dosent make one bit of sense.. lol, anyways recovery was not possible, it just throws that message back and phone is stuck in a loop.

so then i put it in dl mode and that got me out of the loop.

Ive read all about this issue in the past but i would have never thought it ever happening on a n960n. usualy it happens to people who have the 7 day time bomb on their n960f , where OEM unlock dosent appear.(which is available on a fresh stock flash for me.) anyways i think that even if i saw 4g+, im not too keen on the crash and subsequent flash back to stock i had to do.

not sure what happened but since i dont have 2 phones, i cant / dont really want to test more into depths..

but i could though... what would be the alternative method of looking up the CA entry ?

other thoughts:

so flashing the csc packs did not impede me to use the dialr codes, the new rom did. both rom i was on initially and tekhd's are 'F' based.

but since i know his rom/packs are aimed towards getting the most of USA carriers functionality , there are probably non csc system files that he uses. maybe the ims apk and other associated files are infact from U firmware. it might also explain the issue i got when the phone crashed, but then again it would happen to other users too... anyways the + sign was intriguing.... if only i could confirm it was actually doing carrier aggregation, id maybe invest more time and find out what actually is needed to make it work completely because csc is obviously not enough.

even more:

so i figured what happened is that tekhd's rom for some reason did not have the oem unlock set to disable. and since i did not reboot once yet, when the crash happened the phone went to 'panic' mode . so probably if i try again, i just need to go to dev options and unlock oem....

even even more

so flashing back stock got me into a usim lock. i couldn't do anything. not even access home screen nor do initial setup.

removed then sim and could access the phone again.

went to dev options and OEM unlock was not there.

played with the date a bit, rebooted a few time , then signed in over wifi to my google account and samsung and after a while OEM unlock appeared. went to dl mode flashed twrp(before i could not ). and was able to flash a rom. my main problem now is that damn usim block. since my phone is korean i think its basically a puk lock where u need to enther a 4 to 8 number. anyways i had a twrp backup on my ext sd card(thank god, and am gonna upload a backup of it somewhere else) so i restored carrier config and efs partitions and that did the trick.

so i think for now i will steer clear of tekhd's rom.

even more fun:

so after a reboot i got the custom binaries thing again... back to the drawing board it seems...

so since my phone contacted OEM aids, looks like ill have to flash ketans fix:

https://www.androidfilehost.com/?w=files&flid=281291

which i NEVER needed before...