Related
We finally made the switch to Verizon back on Monday due to inconsistencies with US Cellular's local coverage in our area. Inconveniently, I had just upgraded to the USCC variant of the Note 9 in early September, so when the Verizon agent initially tried to change the phone over, I was informed that it was the outstanding balance that prevented him from doing so (which made sense at the time). Under the impression that this was all that would be required, I just zoomed over to the US Cellular store next door to pay off that $800 or so remaining on the line, thinking I was in the clear. Of course, it would only be after this that the agent finally realized that compatibility wasn't quite as clear-cut as they had initially thought...
So I apologize in advance for what I feel may be a stupid question, but I haven't been able to find a solid answer on this:
I (now) know that the US carrier-specific models of the Note 9 tend to only come preloaded with the CDMA/LTE frequency bands they use in their respective networks, and that while there is some overlap and crossover, just swapping out one carrier's SIM for that of another still limits you to the original spectrums that came on the phone. However — will the process of flashing the firmware to the correct corresponding carrier for the new SIM also change the frequency bands so everything matches up, or is this something that's entirely hardware related that can't be bypassed?
And to avoid anyone breaking things if this does turn out to be a feasible option, I would assume this would still only work for those in my situation, i.e. trying to flash from an already comparable CDMA capable version of the phone to another CDMA capable version with otherwise equivalent hardware specs and processor (so no GSM-only to CDMA, no Snapdragon to Exynos, etc.).
As has been discussed many times here...ALL the US Note 9s are identical. Same exact hardware. They all support the same bands. The only difference is firmware. And actually with Pie, they will all run the same firmware, just like the Note 8.
You have two options:
1. Carrier branded firmware which will keep WiFi calling and VOLTE working.
2. Unbranded U1 firmware, which is a clean bloat free firmware, but no Wifi calling or VoLTE (unless you're on T-Mobile)
To change firmware, download thr most recent firmware of your choice using the SamFirm tool. Then flash it with patched ODIN 3.13.1. This will wipe your device, so make a backup.
I'm novice to the whole rooting scene so please cope with me.
I found a good deal on almost new Lg v40 from a Sprint user.
We'll meet at Sprint store to verify device is paid off and unlock it.
Once Sprint unlocks it, can I just use this device on Tmobile with my Tmobile sim and will it have band 71 or do I need to have Tmobile fw on it to open band 71 ?
Lg website lists in specs for sprint model (model LM-V405UA) as having band 71.
Can anyone confirm ?
rdx2019 said:
I'm novice to the whole rooting scene so please cope with me.
I found a good deal on almost new Lg v40 from a Sprint user.
We'll meet at Sprint store to verify device is paid off and unlock it.
Once Sprint unlocks it, can I just use this device on Tmobile with my Tmobile sim and will it have band 71 or do I need to have Tmobile fw on it to open band 71 ?
Lg website lists in specs for sprint model (model LM-V405UA) as having band 71.
Can anyone confirm ?
Click to expand...
Click to collapse
I don't think Sprint uses the same LTE bands.
Mine works just fine on T-mobile as of a week or so ago when i got it .Mine is the Sprint version full network & Factory UNLOCKED.
To make sure your GSM unlocked go to system/system-updates--
Then look in the list UICC Unlock it should say -----( The Device is unlocked for any SIM card )
zxhwk said:
Mine works just fine on T-mobile as of a week or so ago when i got it .Mine is the Sprint version full network & Factory UNLOCKED.
To make sure your GSM unlocked go to system/system-updates--
Then look in the list UICC Unlock it should say -----( The Device is unlocked for any SIM card )
Click to expand...
Click to collapse
*Edit - confirmed band 71 is only active in the tmo model, I went with it vs an unlocked variant*
Are you able to use band 71/600mhz? I've seen comments suggesting band 71 isn't enabled in any other model besides tmo, even though specs show all variants having the same band capability.
I'm in the same boat, on tmo & tempted by the lower priced unlocked variant, but would like to confirm band 71 is usable before ordering one.
my sprint v40 was working on t mobile for about two weeks then it went dead and lost its network settings now i cant seem to get it back on tmobile some1 help ! i did the uicc unlock and enable oem unlock
brian9291 said:
my sprint v40 was working on t mobile for about two weeks then it went dead and lost its network settings now i cant seem to get it back on tmobile some1 help ! i did the uicc unlock and enable oem unlock
Click to expand...
Click to collapse
OEM unlock is specifically for bootloader unlocking not network unlocking..
I will be able to report back in about a week whether band 71 works.
I bought the Sprint version of the V40.
I am on Sprint now.
I am crossflashed to US.
I am switching to T-Mobile at the end of the week.
I live in a Band 71 market.
[NG]Owner
So I have switched to TMobile.
I used the hidden Service Menu ( *#546368#*405# ) to force the phone to Band 71. It did not connect to Band 71, instead to Band 2, as reported by LTE Discovery.
I then used the hidden Service Menu ( *#546368#*405# ) to force the phone to Band 12. It did connect to Band 12 as reported by LTE Discovery.
So either band 71 doesn't work, or I don't have access to Band 71 from my house. I have heard that there are confirmed Band 71 sightings in Kansas City, so I will go there to try. Once I do I'll report back.
Both VoWiFi and VoLTE are listed as provisioned.
[NG]Owner
Can somebody also confirm band 71 compatibility? I'm looking to get a Sprint V40 but I'm not sure if cross flashing will enable band 71. Also can somebody confirm if services such as VoLTE, HD Voice, and Wi-Fi calling will work on a cross flashed device? Also how exactly do you force gsm bands if it gives you a checklist? Do you just remove all the bands but one? Also will crossflashing to unlocked make OTA stop working? If so, why does it not work?
So I have to amend my previous post:
I can confirm the following:
Using the Hidden Service Menu from this post, and several apps out of the Play store, my phone sees T-Mobile bands 2, 4, 12 and 71 towers. And I have successfully been connected to a Band 71 tower.
Oddly enough, LTE Discovery still reports the connection as a different band. So I'm going with the Hidden Service Menu as definitive.
[NG]Owner
NGOwner said:
So I have to amend my previous post:
I can confirm the following:
Using the Hidden Service Menu from this post, and several apps out of the Play store, my phone sees T-Mobile bands 2, 4, 12 and 71 towers. And I have successfully been connected to a Band 71 tower.
Oddly enough, LTE Discovery still reports the connection as a different band. So I'm going with the Hidden Service Menu as definitive.
[NG]Owner
Click to expand...
Click to collapse
After you cross flashed, do services like VoLTE, HD Voice, and Wi-Fi calling still work?
---------- Post added at 09:59 PM ---------- Previous post was at 09:52 PM ----------
NGOwner said:
So I have to amend my previous post:
I can confirm the following:
Using the Hidden Service Menu from this post, and several apps out of the Play store, my phone sees T-Mobile bands 2, 4, 12 and 71 towers. And I have successfully been connected to a Band 71 tower.
Oddly enough, LTE Discovery still reports the connection as a different band. So I'm going with the Hidden Service Menu as definitive.
[NG]Owner
Click to expand...
Click to collapse
Also how were you able to open that hidden menu. I entered in the code and nothing happens.
jimmysofat6864 said:
After you cross flashed, do services like VoLTE, HD Voice, and Wi-Fi calling still work?
Click to expand...
Click to collapse
Not sure what you mean by still. I was on Sprint. Received Sprint v40. Immediately crossflashed to US version. Used phone on Sprint. Migrated to T-Mobile. VoLTE, HD Voice, and Wi-Fi calling work. That was the sequence. I have no idea if Sprint has those features or if they work on Sprint. But on T-Mobile with a cross flashed to US version v40, those services work just fine for me.
Now if you are thinking of crossflashing a T-Mobile v40, stop right now. You'll brick it. There is nothing you can do to a TMo v40.
jimmysofat6864 said:
Also how were you able to open that hidden menu. I entered in the code and nothing happens.
Click to expand...
Click to collapse
I assume you are also entering it into the phone dialer. I type in the code, and the hidden service menu appears. If it's not working for you, I don't know why not.
[NG]Owner
I was referring to a sprint model phone but was nice to know everything works. Just have to wait and see if OTA updates work.
So I got a Chinese edition phone with band 2, 4, 5, 12, and 17 to fully support both TMobile and ATT network. The Global edition was missing band 17 for ATT so I didnt want to go that route. Been going back and forth with ATT a bit for the past few days since my device came in. The phone shows up and an "unknown device" on their network when we tried adding the IEMI. It will get UMTS (2g) and HSPA+ (3Gish/4G), but will not connect to any LTE or GSM. The phone supports GSM fine, so its strange that it wont do normal cellular connection over that, it will only do cellular over UMTS. The device wont detect as an LTE device and so the sim wont activate LTE on it.
Anyone else with ATT have this issue? And were you able to resolve it somehow?
Or those with TMobile in the US, are you able to activate the phone fine and get full coverage and LTE working?
I messed around with the connection settings in the *#*#4636#*#* menu. Only the "LTE/TD-SCDMA/UMTS" and "LTE/TD-SCDMA/WCDMA" will work properly at all. Both options give me UMTS for cellular, and HSPA+ for data. Of the 4 APNs that ATT uses, only the "ATT Phone" will work at all. The standard LTE APN "NXTGENPHONE" will leave the phone with no data or cellular service. This is related to the phone not being detected as an LTE device and the SIM not activating as such.
I simply put my AT&T sim in my China version and it worked straightaway. I didn't have to do anything else.
I am on Cricket, which leases service from AT&T, so I should know if it works once it comes Tuesday.
Just for perspective, I got a EU version of the Mi 9. Popped in a T-Mobile sim and it worked out of the box. Try the other sim slot. Could be your sim card if not.
Try these codes in Dialer. See if that helps anything.
VoLTE *#*#86583#*#*
VoWIFI *#*#869434#*#*
I was just making an ATT account so no previous activations or sims. So that could be the issue. I will try activating a sim with an old phone and then move the sim over. Or since it is the same hardware as a Galaxy S10, ill see if I can find a store that will activate a sim with a floor model S10 and then let me swap the sim into my Mi 9
Straight talk (ATT sim) lte without issue. no programming necessary , I have the global model though
jvs60 said:
I simply put my AT&T sim in my China version and it worked straightaway. I didn't have to do anything else.
Click to expand...
Click to collapse
airwebber said:
I am on Cricket, which leases service from AT&T, so I should know if it works once it comes Tuesday.
Click to expand...
Click to collapse
MixEvo said:
Straight talk (ATT sim) lte without issue. no programming necessary , I have the global model though
Click to expand...
Click to collapse
Where did you guys buy the China version from?
US mobile white SIM from starter kit (T-Mobile) works well with LTE on Chinese model of Mi 9. Black one (Verizon) technically works, registers in the network and enables data, but Verizon refuses the IMEI as non-certified brand of the phone. Trick with activation on the iphone first and switching to xiaomi did not work, service gets cut off, when trying to make a call, it keeps dropping. AT&T based: Cricket and Straight Talk work just fine too.
---------- Post added at 06:15 AM ---------- Previous post was at 06:14 AM ----------
StDevious said:
Where did you guys buy the China version from?
Click to expand...
Click to collapse
Aliexpress https://www.aliexpress.com/item/Ori...222.html?spm=a2g0s.9042311.0.0.58b14c4dxws9df
You'r welcome =)
StDevious said:
Where did you guys buy the China version from?
Click to expand...
Click to collapse
I bought my Transparent Edition from Tradingshenzhen.com
Neolo said:
US mobile white SIM from starter kit (T-Mobile) works well with LTE on Chinese model of Mi 9. Black one (Verizon) technically works, registers in the network and enables data, but Verizon refuses the IMEI as non-certified brand of the phone. Trick with activation on the iphone first and switching to xiaomi did not work, service gets cut off, when trying to make a call, it keeps dropping. AT&T based: Cricket and Straight Talk work just fine too.
Click to expand...
Click to collapse
Thanks for the info.
I was wondering about Verizon, since it support some CDMA bands and support 2 out of 3 of the LTE bands they use (doesnt support B13). Unfortunately I never tried it myself since half the coverage near me uses the band this phone doesnt support on Verizon.
I went and got my ATT account updated to an old Nexus 6 IMEI number and it got LTE on the N6. I then took the sim and put it in my Mi 9 and now the Mi 9 has LTE. So for anyone just getting this phone, you must have an IMEI on your account that is recognized as an LTE phone. If you try to add the IMEI of the Mi9 it is not recognized by ATT and wont provision LTE.
IMEI spoofing does not work with Verizon, as they simply ban the device. They call it “non certified”. Bands are seem ok.
StDevious said:
Where did you guys buy the China version from?
Click to expand...
Click to collapse
I been purchasing from liaow. Never ran across a issue with them
I've been having the same issue, with a recently-bought (last week arrived) Mi 9 Global on AT&T postpaid. LTE showed up and worked fine day one, now network speeds are dropped down to 3.5G speeds. Anyone else have success with getting LTE on a fresh SIM?
EniGmA1987 said:
So I got a Chinese edition phone with band 2, 4, 5, 12, and 17 to fully support both TMobile and ATT network. The Global edition was missing band 17 for ATT so I didnt want to go that route. Been going back and forth with ATT a bit for the past few days since my device came in. The phone shows up and an "unknown device" on their network when we tried adding the IEMI. It will get UMTS (2g) and HSPA+ (3Gish/4G), but will not connect to any LTE or GSM. The phone supports GSM fine, so its strange that it wont do normal cellular connection over that, it will only do cellular over UMTS. The device wont detect as an LTE device and so the sim wont activate LTE on it.
Anyone else with ATT have this issue? And were you able to resolve it somehow?
Or those with TMobile in the US, are you able to activate the phone fine and get full coverage and LTE working?
I messed around with the connection settings in the *#*#4636#*#* menu. Only the "LTE/TD-SCDMA/UMTS" and "LTE/TD-SCDMA/WCDMA" will work properly at all. Both options give me UMTS for cellular, and HSPA+ for data. Of the 4 APNs that ATT uses, only the "ATT Phone" will work at all. The standard LTE APN "NXTGENPHONE" will leave the phone with no data or cellular service. This is related to the phone not being detected as an LTE device and the SIM not activating as such.
Click to expand...
Click to collapse
I got the Chinese version and I'm in the US. And I I have the straight talk T-Mobile sim and everything works like it is suppose to expect my internet. It says its 4g but it is very very slow. Any ideas?
Observations:
For any particular build generation:
1. Between the U and U1, none of the firmware files are the same, not AP, BL, CP or CSC.
2. Between the U firmwares, only the USERDATA changes. The others have the same name and SHA-512.
3. Between the U1 firmwares, ALL of the files have the same and SHA-512. This indicates SamMobile's different zip files for XAA, VZW, TMB, TMK, etc. are an "exercise". U1s are sold by non-carrier outlets who have no idea where the phone will be used.
4. Flash file size differences between the U and U1 are as follows:
AP - The Unlocked U1 flash is more than a gig larger than for the carrier U flash.
BL - They are very close to same size with the carrier version being 41K larger.
CP - They are very close to the same size with the carrier version being 327K larger.
CSC - The carrier U flash is about 20 megs larger than the Unlocked U1.
USERDATA - T-Mobile is 1.35 GB, Verizon: 1.76 GB. The US UNLOCKED U1 doesn't have a USERDATA flash file.
My Theory:
There are many theories swirling about that center on carriers restricting services when you don't buy your phone from them. My theory is much simpler. With all of the U carrier firmware, you will see a gig plus USERDATA flash file. The U1's firmware doesn't have a USERDATA flash file, but the U1's AP flash file is a gig plus larger than U's AP flash file. I also work in the UNIX world. Applications that are installed at the same time you install the operating system will be installed in the operating system area. If you install those same apps later, they will be installed in the user software area. My theory about the Note 9's firmware is that the U1 Firmware is Android+Samsung-specific software+Samsung specific hardware drivers+standards-based wireless network drivers+Samsung basic apps. Samsung gives wireless providers the same with standards-based wireless network drivers+Samsung basic apps in separate install. This could explain how the gig plus moved from the U1's APP to the U's USERDATA. It would also enable a consistent user interface for the same service across all wireless providers who may be providing the service using entirely different methods. This would explain why running the carrier-specific the U firmware vendors all support capabilities such as Wi-Fi calling and Video Calling, while when the same phones are running US Unlocked firmware, only some do. That would mean those with the services available have deployed them in a standards-compliant way. For instanced, for T-Mobile, Voice over LTE(VoLTE) and Voice over Wi-Fi(VoWiFi) work but USCC roaming doesn't. On Verizon, Voice over LTE(VoLTE) and Carrier Aggregation works, but NOT Voice over Wi-Fi(VoWiFi). With AT&T, neither work. So that likely means the Verizon does not support VoWiFi on their network while AT&T doesn't support VoLTE nor VoWiFi, and have proprietary implementations on their network that are only available if your flash their carrier-specific firmware. This would also explain why when a phone is running the US Unlocked U1 software with a Verizon SIM installed you will not have Wi-Fi calling available, and when you simply swap to the T-Mobile SIM, it will magically show up. This seems to me to simply be the U1 firmware responding to what it finds. It hasn't been that long since our phones would only work on one network. It hasn't been that long since the critical mass existed to migrate to the new LTE standard. The T-Mobile build-out only increased rapidly, and Sprint may not even be finished rolling out VoLTE yet, thus much less likely to have non-compliant systems in place. You could extend this reasoning to other wireless technologies as well. It also makes sense why the mechanism to prevent firmware upgrades to not be present in the U carrier-specific firmware, while it is present in the the standards-compliant U1 firmware. The U1 path adds support for new standards as it goes. The U path must replace proprietary methods for advantage or regulatory reasons. If this theory is correct, you would be better off with U1 firmware when traveling abroad. The name US Unlocked may have little to do with US, and a lot more to do with being standards-based, which is more likely what you would encounter in other countries where widespread deployment occurred later. The SM-N960U* already supports more bands than any phone I've found, and with US Unlocked U1 firmware, it may be the best world phone as well.
Why I believe this:
In an environment of democracy and capitalism, companies are free to make decisions that benefit themselves the most, and those who are stockholders appoint CEOs who know how to make that happen. They would get fired for not using other people's equipment and networks for free if they could. If they could make more money by getting rid of non-VoLTE devices to free up bands, they will, and the FCC is forcing it to happen. The fact that VoLTE is not controllable by the user interface, does not indicate it is not being used. Why would you give a user the option control VoLTE, Carrier Aggregation, etc.? Voice Over Wi-Fi VoWiFi employs SIP/VOIP technology, which predates smart phones. Towers and equipment are often not owned by the wireless providers because they are co-location sites that must be approved by local authorities. Standards-based equipment means it would be cheaper, you need less of it, you have more options with regard to inter-carrier agreements of which some are mandated by the FCC. Moreover, investments in non-standard methods and equipment devalues the company, and even determines how much they can leverage money. Holding out on people who do not buy their phones from them doesn't make sense because they are not denying these services to BYOD pre-pay users, or anyone who flashes their phones to their firmware. The FCC already forces them to unlock their phones before they are paid for, so it doesn't make sense to put themselves at a competitive disadvantage when it comes to acquiring users from other carriers. If carrier salesmen posts are true, they don't make much on phones anyway, and phones are more a vehicle to sell their services and accessories. They know that you know they don't have you over a barrel anymore and implementing interoperability is their new reality, and the reality of any maturing technology.
Surprises and Mysteries:
After I paid my premium membership for a month and went to SamMobile to download US Unlocked U1 firmware, I was surprised to find files for all different wireless network providers. Puzzled, I downloaded them all. SamMobile shows TMK as USA, so believing that I was getting US Unlocked, I downloaded it and flashed it. Booting up I got the Samsung Logo, which also made sense. I learned later that SamMobile has things mislabeled. TMK is MetroPCS, and XAA is the US Unlocked I should have flashed. However, then I noticed after the U1 files were unzipped that the flash files all had the same name. Then I tested their SHA-512 numbers and they were exactly the same, which means they are the same files. So, if they are the same files, why do they list the different wireless providers and put them in separate zip files with the carrier's extension on them? There isn't even an expectation of a difference because when they sell a U1 phone, they don't know which network it will be used on. What I do know is the Phone INFO app shows:
Firmware's CSC Code: XAA (I never flashed the XAA zip file. I flashed the TMK zip file, but since I found the flash files were the same for every U1 firmware zip file, seeing the US Unlocked code of XAA was not shocking.)
Active CSC Code: VZW (SIM installed)
Future
Great discussion .... Thanks
I've been down several roads with this including an S9 Exynos and then an S10
I then tried a One Plus 7 Pro and even switched to TMO because I couldn't get WiFi Calling with AT&T.
Currently am experimenting with a Note 9 that I believe was original sim locked to At&T but now unlocked and now with the most recent U1 firmware
Calling features work fine with TMO including WiFi Calling, but I'm looking to try AT&T as well (my reception is much better in my rural areas with att vs TMO).
Do you know if the calling features will work with the U1 firmware and ATT? ( If I get IMEI compatibility issues squared away with att)
Or do I have to flash U firmware?
I'm awaiting a Note 10 that is unlocked. Wondering if I can get ATT calling features to work on it?
jcrompton said:
Do you know if the calling features will work with the U1 firmware and ATT? ( If I get IMEI compatibility issues squared away with att) Or do I have to flash U firmware? I'm awaiting a Note 10 that is unlocked. Wondering if I can get ATT calling features to work on it?
Click to expand...
Click to collapse
I do not use AT&T. From what I've read, is no advanced features work with U1 on AT&T. With Verizon, VoLTE and Carrier Aggregation works fine, but ViLTE and VoWiFi does not.
I live in a T-Mobile fringe area that uses B71 exclusively (at least at my house). My experience with U vs U1 is that even though the signal is relatively weak, -118 dBm, the T-mobile branded U firmware holds the LTE signal fine. On the unlocked U1 firmware the signal is a tad weaker, plus it will drop the signal entirely and give me a no network error and/or it will roam on AT&T hspa. So clearly the Tmo software has optimizations for B71 at least over the unlocked U1.
I also have used a Pixel 3XL, an iPhone XR and a Moto G7 power in the same area. They do occasionally roam but I don't experience the loss of signal that I get with the Note 9 and the unlocked firmware.
BladeRunner said:
I live in a T-Mobile fringe area that uses B71 exclusively (at least at my house). My experience with U vs U1 is that even though the signal is relatively weak, -118 dBm, the T-mobile branded U firmware holds the LTE signal fine. On the unlocked U1 firmware the signal is a tad weaker, plus it will drop the signal entirely and give me a no network error and/or it will roam on AT&T hspa. So clearly the Tmo software has optimizations for B71 at least over the unlocked U1. I also have used a Pixel 3XL, an iPhone XR and a Moto G7 power in the same area. They do occasionally roam but I don't experience the loss of signal that I get with the Note 9 and the unlocked firmware.
Click to expand...
Click to collapse
This is very valuable information for a guy on the fence like me.
Thanks TONS!!!
BladeRunner said:
I live in a T-Mobile fringe area that uses B71 exclusively (at least at my house). My experience with U vs U1 is that even though the signal is relatively weak, -118 dBm, the T-mobile branded U firmware holds the LTE signal fine. On the unlocked U1 firmware the signal is a tad weaker, plus it will drop the signal entirely and give me a no network error and/or it will roam on AT&T hspa. So clearly the Tmo software has optimizations for B71 at least over the unlocked U1.
I also have used a Pixel 3XL, an iPhone XR and a Moto G7 power in the same area. They do occasionally roam but I don't experience the loss of signal that I get with the Note 9 and the unlocked firmware.
Click to expand...
Click to collapse
on U1 firmware, when you go to the phones dialer and dial:
*#2263#
do you get a hidden service mode menu like attached picture? if so then just force band 71 so that it dosen't switch. you can also disable other bands and leave only the ones you know work best so that device dosent try to switch to other weaker ones that you know will drop. also by setting to forcefully stay on LTE by selecting menu 4 in band selection and specifying the bands it should stop from reverting to hspa. but also might cause no signal. but again by selecting only the bands you know work i believe it should help. i have done many tests and what i do is to force bands one by one and check strength in a place where i know signal is poor. this way you weed out the bad bands. write it down somewhere and then go reactiavte all of them. then go to the disable band menu and remove everything except the ones listed previously and be left with only the stronger ones and stop fone from attempting to connect to random weaker ones.
So running the latest software it seems no need to flash firmware for carriers when you place an actual carrier sim in the splash screen and everything automatically switches to sim...I have a note 8 and a note 9 one cricket one metro since note 9 has band 71 I wanted to try metro in it and utilize that but ofcourse finding out metro locks service to imei unlike cricket does where any phone unlocked will work..but although I couldn't use my metro on my note 9 it did change splash screen and showed the wifi calling which I cant use wifi calling but i am able to hotspot again so that's the bonus for everyone on cricket needing hotspot again try popping in a tmobile or metro sim it holds even after restarting...correct me if I'm wrong on the firmware automatically switching cause the note 9 is a verizon bought phone and had been showing verizon splash screen....diagnose further when I buy new sim to tie note 9 to metro since they apparently pair sim and imei...
Terasman210 said:
So running the latest software it seems no need to flash firmware for carriers when you place an actual carrier sim in the splash screen and everything automatically switches to sim...I have a note 8 and a note 9 one cricket one metro since note 9 has band 71 I wanted to try metro in it and utilize that but ofcourse finding out metro locks service to imei unlike cricket does where any phone unlocked will work..but although I couldn't use my metro on my note 9 it did change splash screen and showed the wifi calling which I cant use wifi calling but i am able to hotspot again so that's the bonus for everyone on cricket needing hotspot again try popping in a tmobile or metro sim it holds even after restarting...correct me if I'm wrong on the firmware automatically switching cause the note 9 is a verizon bought phone and had been showing verizon splash screen....diagnose further when I buy new sim to tie note 9 to metro since they apparently pair sim and imei...
Click to expand...
Click to collapse
all us devices contain all carrier's csc.
bober10113 said:
all us devices contain all carrier's csc.
Click to expand...
Click to collapse
It's kind of new to me but I guess the take away for anyone is I've lost my hotspot capability on cricket when I switched to note 9 from note 8 cause changing the apn didn't work with new software like I did with note 8....and now i have regained that on note 9 which was bought through verizon also I'm able to utilize dialer codes again where I lost that too...so if your on cricket or something like that and lost those abilities then just pop in a metro or tmobile sim and restart phone then put your cricket sim back in and your good to go with hotspot and dialer codes again....I just wish cricket didn't whitelist phones capable of using volte where I could get that on my note 9 cause 3g calling has definitely went downhill with low to no coverage anymore on it...my real question is this everyone is talking about flashing the carrier csc to whatever carrier you going to so you have the best and all their perks just seems with latest updates there's no need for it like my note 9 has band 71 but while on verizon I'm sure they disable that band because it's not needed so it seems when you swap sims and forced to restart because new sim is detected and you put a tmobile sim in it automatically turns correct radio bands on for its network...correct or not because I want tmobile just need to know band 71 will be activated when I put a tmobile sim in this verizon bought note 9 and I'll be able to utilize their full network spectrum...cause metro by tmobile apparently only utilises band 2 and band 12 which cuts my coverage...sorry for the long read