Database Develop

[SOLVED] Network Location (unavailable) on Rogers [multiple devices affected]

Solution 2010.12.04
Thanks to Rumball who found a solution to this problem.
http://forum.xda-developers.com/showpost.php?p=9576852&postcount=108
Update: 2010.11.29
This issue appears to affect all unlocked Froyo devices on the Rogers network. It MAY affect all Froyo devices, regardless of network lock status, but we have been unable to confirm this (yet) on the only Froyo device locked to Rogers - The Acer Liquid e.
There are currently 4 threads (that I am aware of) scattered around XDA. As this problem affects multiple devices I will start posting updates in the General Discussion/Q&A thread, and will stop posting updates here. If you are looking for more information, please refer to:
Main Thread: http://forum.xda-developers.com/showthread.php?t=845152
Other Device Specific Threads:
N1: http://forum.xda-developers.com/showthread.php?t=849969
DZ: http://forum.xda-developers.com/showthread.php?t=848793
SGS: http://forum.xda-developers.com/showthread.php?t=850784
--------------------------------------------------
Greetings.
Sometime about two weeks ago my i9000m began to fail to find my location using the Rogers network. WiFi and GPS location both still work.
The phone is able to find my location using the network for a brief time after flashing a ROM, but then, sometimes after one restart, sometimes after an hour, and sometimes after approx. 24 hours, it is unable to find the location any more. If I am a little vague about the precise events after which the phone ceases to find locations it is because:
1. As long as I don't change location, the phone reports that it has found the location, so I have to move some distance to diagnose failure.
2. Some time or event has to elapse/occur before failure. I don't think that it's app installation, and I know that it's not system modification (deletion of apps in /system/app or adding/deleting files in /system/media/audio). It MIGHT be phone restart.
3. This is my primary phone, so I can't afford to take it out of service for extended periods of time for testing.
I don't have a logcat yet, but one is included in this thread (in a place where it likely isn't getting much attention):http://forum.xda-developers.com/showthread.php?t=845152
I THINK that Bell SIM cards work (it worked first time when i popped it in my unlocked i9000M - after Rogers failed), but I haven't been able to conduct a long trial.
Rogers SIM cards do not work: not the old one, and not the one that I got an hour ago.
I haven't yet been able to try the new Rogers SIM in the phone after a flashing a clean OS.
Is anyone else experiencing network location problems (on Rogers or another network)?
Does anyone have any idea how to correct the problem?

Not sure what it can be
but I'm on FIDO and network location still works fine.
try wiping the phone in Recovery Mode
both data and cache (factory reset format)

Here's an update:
i9000M + Rogers SIM + wipe (cache, factory, dalvik) = fail to find location
i9000M + Rogers SIM + wipe + flash Doc_V1.1_Bell I9000UGJK3 = finds and tracks location
BUT... fails (network location temporarily unavailable) after first restart (absolutely nothing else changed)
Bold 9000 + Rogers SIM = success
i9000M + Bell SIM = success, every time (app installs, restarts, etc.)
Colour me baffled. It's as if the phone itself doesn't want to work with Rogers (or vice versa).
logcat(s) attached for a failed Rogers attempt and a successful Bell attempt. I think that there's a key entry in the Bell logcat at line 9651, but I couldn't find anything obvious in the Rogers output. Does anyone know how to use this stuff to diagnose the problem? I'm almost ready to ditch this phone.

And one more bit of information...
For some reason, when I flash back to UGJG8 or UGJH2 I lose the ability to connect to ANY network, no matter what SIM card I use.
*#*#4636#*#* indicates that the radio is on, though the network type is usually set to unknown.
None of the other service menus seem to work properly - black screen, or data fields are empty.
Unless someone helpful has a bright idea, it looks like I'm taking this phone back to Bell for service (or to the garbage).

Bumping and updating.
This may be important to others. It appears that the network location failure is related to the combination of Rogers' network and either (or both) Froyo and network unlocked phones. There is a functional workaround (stopping google framework services and clearing data and caches), but it's really kinda crappy if you have to repeat it frequently.
Anyway, anyone thinking to use an unlocked or Froyo android device on Rogers' network beware; if you want to use network location, anyway.

Well, I know there is a fair-sized community of i9000m users using Rogers on these forums. No one else currently has this issue?
Can we get anyone to confirm that they are using an unlocked Froyo phone on Rogers and do have network location capability?

Really all we need to confirm is:
Network?, OS?, Problem?
Rogers Tech support indicated that they have Froyo devices running without reported problems, but I have my doubts. As far as I know Rogers hasn't carried a device that will have an official Froyo build until the recent introduction of the Captivate and, as far as I know (again) none of the north american samsung galaxy S devices have an official Froyo build yet.
So, no official Froyo on Rogers, and until this month no high-end android devices. SO, any device with tis problem is likely to be unlocked.

I found a post on the following site regarding this issue. Can people with the issue make a post on that thread.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=310dd072d5f565ee&hl=en
Hopefully Google will see it and take action on their side.

Quantus said:
Really all we need to confirm is:
Network?, OS?, Problem?
Rogers Tech support indicated that they have Froyo devices running without reported problems, but I have my doubts. As far as I know Rogers hasn't carried a device that will have an official Froyo build until the recent introduction of the Captivate and, as far as I know (again) none of the north american samsung galaxy S devices have an official Froyo build yet.
So, no official Froyo on Rogers, and until this month no high-end android devices. SO, any device with tis problem is likely to be unlocked.
Click to expand...
Click to collapse
The Tab is out and it runs froyo...
Sent from my GT-I9000M using XDA App

Huh... I didn't think of that. I may have to eat my words.
Apparently the Acer Liquid e also runs Froyo. I guess that I now have two devices (locked to Rogers and running Froyo) I need to get my hands on.
Does anyone out there have access to either of those devices on Rogers? Can you test the network location?

Repost from another thread:
Someone from Rogers stated they have not blocked any location services on unbranded devices. In addition, some one stated their friend has problems on their Liquid E
http://communityforums.rogers.com/t5...message-id/342

Not just Rogers guys... using unbranded version in the US on AT&T. Location is absolutely hosed!
Will try the fix and report back.

[Q] Troubleshooting Mobile Data

Good night my fellow modders. Tonight i come with a particular query, mainly, how do i go about troubleshooting the 3G connection of the motorola razr i. Ever since i flashed Omar's Motorola 4.1.2 Rom from Jan-01-2014, i haven't been able to get internet access through my carrier (Not even through 2g) and ive already checked its not a carrier issue (Since i can use my simcard to browse the internet in another phone just fine), i even tried doing a nandroid restore from the stock firmware i had previous to starting this adventurous task to get things working again, but even then the mobile broadband service is a no-no.
I'm at a loss on what to do, since i've already tried reflashing the ROM, reset-ted the phones APN's, and i've also done the suggested file modification of the losialert timer to both, 1000 and 500 (as seen in the same thread). However those efforts have been to no avail and im quite at a loss on what to do.
Im sorry if my english isnt fully understandable (Its not my native languaje) and im also sorry if this isnt the righ section to post about it, but i cant post directly in the thread since I'm a new member. I thank you beforehand for any and all guidance or help you can offer me.

Don't worry, English is not native language for most of forum users.
First of all buy any pre-paid card from different carrier or borrow it sim-card from friend and test it.
I had similar situation with Virgin Mobile. We have quite few operators in my country and I tested all of them but for this I wasn't prepared. I had my new RAZR i and there was no option to use internet with Virgin Mobile.
After few days of fight with different ROM, modding system, installing apps to APN's I figured it was sim-card. Some carriers have old sim-cards which have something wrong with MCC and MNC code and all phones can work on it but not Android 4.1 and above caused APN automation.
I even called to Virgin to ask for changing sim-card but they said they don't have different version of sim-cards, so I asked "WHAT, so every people in Your network doesn't have internet on Android 4.1+??!!" and they said "Yes, it seems so".
And there was no other way but change carrier. Now I have fully working internet without any modifications.
Sorry for so long and boring reply but for my almost 10 years working with mobile phones it was first situation like this.

Chamelleon said:
Don't worry, English is not native language for most of forum users.
First of all buy any pre-paid card from different carrier or borrow it sim-card from friend and test it.
I had similar situation with Virgin Mobile. We have quite few operators in my country and I tested all of them but for this I wasn't prepared. I had my new RAZR i and there was no option to use internet with Virgin Mobile.
After few days of fight with different ROM, modding system, installing apps to APN's I figured it was sim-card. Some carriers have old sim-cards which have something wrong with MCC and MNC code and all phones can work on it but not Android 4.1 and above caused APN automation.
I even called to Virgin to ask for changing sim-card but they said they don't have different version of sim-cards, so I asked "WHAT, so every people in Your network doesn't have internet on Android 4.1+??!!" and they said "Yes, it seems so".
And there was no other way but change carrier. Now I have fully working internet without any modifications.
Sorry for so long and boring reply but for my almost 10 years working with mobile phones it was first situation like this.
Click to expand...
Click to collapse
Thank you for taking the time to answer my query. Unfortunately, i believe your case doesn't apply to me, since i had no issue using the internet with my operator (Telcel) before flashing the new ROM. I've also already called my operator and they made several procedures to try and reestablish my service, however none of them worked, but they assure me it's a problem with my device, since their service is working correctly.
I have no idea what to do now, but i hope can get the minimum required limit i need to ask for support directly on the thread ;(.

I don't know if this will help.
I had this problem with my brothers phone (galaxy s4 mini) last night. Data wouldn't turn on in anyway. Flash in new ROM from recovery didn't did the trick, nor a nandroid did. The only way I have got it to work was flashing a stock ROM through ODIN. In this case it would be RSD lite. Maybe it I'll work, but be aware of the flashing problems red lite can give. Read it a bit. Good luck!
Sent from my GT-P5110 using XDA Premium HD app

Do you have the correct APN entries?? You might need to add it manually...
That happens because it doesn't auto configure (correctly, or none at all) for some carriers because I don't have all the carriers in apn-config.xml -- while your specific carrier ROM might have had it already configured and a specific xml list for them.
If you reset APN's and see all the appropriate ones added it might be configuring a wrong ones by default according to the data from the apn-config.xml one in my ROM, just configure accordingly to your carrier information
Note 1: My ROM does not touch the radio, and since the radio images are international anyway it does not make sense to flash recovery images or anything ... the only problem (assuming you did not break anything in hardware during ROM flashing) comes from the android /system partition which is prone to have incorrect carrier settings for data configurations... any bad number or password updated on your carrier it would be configuring something else by doing "reset to default"...
Note 2: To save the APN entry don't exit ... press the options menu and hit save when done modifying -- else it won't remain saved!

The problem starts when You updated from 4.0.4 to 4.1.2??

Hazou said:
I don't know if this will help.
I had this problem with my brothers phone (galaxy s4 mini) last night. Data wouldn't turn on in anyway. Flash in new ROM from recovery didn't did the trick, nor a nandroid did. The only way I have got it to work was flashing a stock ROM through ODIN. In this case it would be RSD lite. Maybe it I'll work, but be aware of the flashing problems red lite can give. Read it a bit. Good luck!
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Did you try to change the APN settings before you tried this? I'm only asking because I'm considering this option, but i would like to rule it out as my final option, because since i started having this issue I've been reading a lot, and the way you fixed your problem sounds like the stock ROM corrected your issue by giving you the default APN's for your carrier.
Chamelleon said:
The problem starts when You updated from 4.0.4 to 4.1.2??
Click to expand...
Click to collapse
I'm afraid i was already on 4.1.2 by the time i installed Omar's custom ROM.
Omar-Avelar said:
Do you have the correct APN entries?? You might need to add it manually...
That happens because it doesn't auto configure (correctly, or none at all) for some carriers because I don't have all the carriers in apn-config.xml -- while your specific carrier ROM might have had it already configured and a specific xml list for them.
If you reset APN's and see all the appropriate ones added it might be configuring a wrong ones by default according to the data from the apn-config.xml one in my ROM, just configure accordingly to your carrier information
Note 1: My ROM does not touch the radio, and since the radio images are international anyway it does not make sense to flash recovery images or anything ... the only problem (assuming you did not break anything in hardware during ROM flashing) comes from the android /system partition which is prone to have incorrect carrier settings for data configurations... any bad number or password updated on your carrier it would be configuring something else by doing "reset to default"...
Note 2: To save the APN entry don't exit ... press the options menu and hit save when done modifying -- else it won't remain saved!
Click to expand...
Click to collapse
Thanks a lot for getting out of your way to help me Omar; After troubleshooting the device and several talks with my network carrier I've managed to get a so-so signal. I'm not sure if your ROM configures correctly or not the APN'S of my carrier (Telcel) because when i edited them everything was configured as it was supposed to be (I'm not sure about the password since i can't see it though), the only thing that was missing was the APN for GPRS, but I've been reading several forums and almost no android device needs this in addition to the 3G APN (I've added it nonetheless but the device isn't actively using it, my guess is that you've got to choose either 3g or GPRS); I also called my carrier, and the allegedly reset-ed my service.
I'm still not sure if the device is working properly, mainly because the internet access through the mobile network has become very unstable (Sometimes i get disconnected randomly, and turning on the Wi-Fi gets me disconnected automatically), and even though the radio almost always gets an H+ signal (Which is kinda funny, because i used to get 3G more consistently before) i don't think this is normal behavior. I think it may have to be with the los alert, because in my desperate attempts to get things working, i reflashed your ROM and it was set to 1000 once again and I also think that the hardware can't be broken because i wouldn't be able to connect to the data service otherwise.
Because of this i would like to ask two very specific queries, is there a way to flash this setting without flashing the entirety of the zip file?; And in case there isn't, if i flash the zip with the new configuration, and then proceed to perform a nandroid backup of my previous build, will i lose the new 00radio configuration?
I will be tinkering with the device this weekend and will report back if i can find whats wrong, just in case it's something else and somebody needs help troubleshooting this in the future. Thanks to everyone that has contributed so far, i wouldn't have learned so much in so little time without your help.

TemplarWithin said:
Did you try to change the APN settings before you tried this? I'm only asking because I'm considering this option, but i would like to rule it out as my final option, because since i started having this issue I've been reading a lot, and the way you fixed your problem sounds like the stock ROM corrected your issue by giving you the default APN's for your carrier.
Click to expand...
Click to collapse
Hmm, don't know for sure. I have made some changes within the APN list to get it working, didn't work. But the rare thing was that the cm11 one did have data and when he flashed his stock back with a nandroid or a stock zip file data wouldn't turn on anymore. So I can't rule out that it was the APN list that was making trouble, because even with stock it did not work. Only by flashing through Odin it worked. Radio hasn't been flashed in that process.
Sent from my GT-P5110 using XDA Premium HD app

Can't change the Service Provider CSC on my note SM-N960F

So I bought a brand new Sim-free sealed note 9 from eBay last week here in Germany. Take it from the box turn the phone on and see the OPTUS logo when I power it on and then I was thrilled like WTF is this a fake phone? (didn't know what that logo is) so I searched on google and found out that is just an Australian service provider so was relaxed and then I put different SIM card in the phone and I can do phone calls and use mobile data without any problems. The only problem is that the service provider SW is Locked on Optus Australia (OPS). I downloaded different stock firmware's from SamMobile for Germany (DBT), UK (BTU) Even Australia (XSA) and still in settings at the software info/service provider is shown: OPS/OPS,OPS/OPS and every time when I turn the Phone ON/OFF the annoying OPTUS logo is shown... I tried just only flashing the CSC in Odin but still no changes... I contact the buyer on eBay and he is willing to take the phone back and full refund me. But I want to keep the phone really like the Note 9. Please help me :angel:

You have to change the CSC using a combination file ROM, as they use a multi-CSC now. In some ways, it's better than the old system but in others, it's worse.
This took me ages to figure out but after finding a guide and the right combination ROM (must match the current bootloader version else it won't boot), it worked.
Here's the thread that helped me: https://forum.xda-developers.com/t/...9-s9-csc-only-same-model-numbers-csc.3870836/
Look through all the comments if you have issues. I believe I mentioned, somewhere in that thread, the exact steps I took to make it work.
Newer versions of SamFirm have a combination ROM download option to simplify finding one (new SamFirm builds don't seem to be on the website yet but the guy who maintains it now also has a YouTube channel where he posts links. Seems to be fine except the very latest version seems a bit ad-filled).
Just so you're aware, the N960F shouldn't be carrier-locked. You just can't change the CSC like older phones could. S7 and Note 7 were the last Samsung phones that used the old CSC system, if I remember correctly. Getting rid of the carrier logo is worth it, though, in my opinion.

Samsung Galaxy S10 - Unlocked Phone (AT&T Blocked Call Issue)

So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.

robertkjr3d said:
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
Click to expand...
Click to collapse
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.

robertkjr3d said:
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
Click to expand...
Click to collapse
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!

Agreed, I didn't know such a thing was possible, but I'd love to hear more about this!

skrapmetal said:
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Click to expand...
Click to collapse
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.

KennyG123 said:
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
Click to expand...
Click to collapse
I appreciate you getting back to me. Unfortunately I am still on android 11 with a custom ROM and also this is a global phone so that app didnt work for me. I dont receive OTA updatez. I'll update to a new ROM and see what happens. Thanks

SM-N910T on T-Mobile USA in 2023?

I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.

https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.

SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.

Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.

The N910T still supports VoLte.. It is still compatible with cellular networks.