Hi, I'm having trouble trying to convert a LG V40 from ATT to Verizon. Got the LG V40 on a trade, it's an ATT model and only Verizon works at our house. I figured it would be easy enough to flash over to Verizon software, but apparently I can't comprehend it. I read a bunch of articles on how to flash the phone over, downloaded the LG drivers, LG UP, and the KDZ file.
Every time I try to load up LG UP, it gives me the LGUP can't load the model error. I tried to download the Uppercut program and it will let LG UP come up and once I select the KDZ file, it gets to 4% and closes the LG UP program.
From what I've read (I've only got 2 hours a day before or after work other than sleep), I guess I don't have the model file that LG UP is looking for to run. Can anyone point me in the right direction? If there's anything I didn't explain or that needs cleared up I'd be happy to explain better.
Thanks
The LG UP version that works with the 40 hasn't been released yet. I thought all that was needed was to swap out the SIM card? You could download the verizon apps off the store, and snooze the ATT ones.
Sent from my LM-V405 using Tapatalk
AFAIK ATT is GSM, Verizon is not. So you cant use Verizon on ATT device even if you flash firmware.
We don't have a way to flash anything in any way yet, so, leave your phone alone before you brick it.
Craddock87 said:
Hi, I'm having trouble trying to convert a LG V40 from ATT to Verizon. Got the LG V40 on a trade, it's an ATT model and only Verizon works at our house. I figured it would be easy enough to flash over to Verizon software, but apparently I can't comprehend it. I read a bunch of articles on how to flash the phone over, downloaded the LG drivers, LG UP, and the KDZ file.
Every time I try to load up LG UP, it gives me the LGUP can't load the model error. I tried to download the Uppercut program and it will let LG UP come up and once I select the KDZ file, it gets to 4% and closes the LG UP program.
From what I've read (I've only got 2 hours a day before or after work other than sleep), I guess I don't have the model file that LG UP is looking for to run. Can anyone point me in the right direction? If there's anything I didn't explain or that needs cleared up I'd be happy to explain better.
Thanks
Click to expand...
Click to collapse
well where are you located?
i have a Verizon v40 i can trade,
i have service with t mobile crap my Verizon v40 works with my t mobile sim card i just keep getting a lot drop calls. I cannot make calls on 4GLTE.
Hey,
I just unlocked my ATT LG V40 using a Verizon sim card here in NYC and works just fine. Once the unlock pin was set in, the phone restarted and showed on the Verizon network with 4G LTE icon.
Ebay has an unlock code guy selling it for $7 buck if you rather not deal with the headaches of switching or whatnot.
I was also able to disable 80% of the ATT bloat that comes with the phone and ready to go.
kasey348 said:
well where are you located?
i have a Verizon v40 i can trade,
i have service with t mobile crap my Verizon v40 works with my t mobile sim card i just keep getting a lot drop calls. I cannot make calls on 4GLTE.
Click to expand...
Click to collapse
Southern WV. Would be willing to drive some distance to just get the correct one.
I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.
degarb said:
I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.
Click to expand...
Click to collapse
I understand why u think flashing t-mo would help, but unfortunately t-mo is the only one u can't flash, unless the original phone was t-mo.
That's because t-mo signs / encrypts the partitions and if u try to use them, u could brick any other phone (other than t-mo).
But to help with your problem, it's best to use the US Open rom (which I believe only came out up to a9, not a10).
Using that rom, you'll have volte, vowifi, and band 71. And, no specific carrier bloat. Some LG bloat, but not much.
cheers
What I am reading on other threads is that if I had a tmo firmware, I wouldn't be able to flash. Also, that no one made an open att firmware, much less with band 71.
I followed the instructions for cross flashing on https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/page-1
It failed, as others with att failed. Then one guy got the older lg command line to work. I followed those instructions (although the instruction page had 3 typos on it, after an hour and a half I found a youtube video without the typos). The command line failed, without any dialog. I assume more cross flashing prohibition.
I see att firmware, but it isn't open, and band 71 is missing. The only reason to flash is for band 71, otherwise my phone is carrier unlocked, but with band 71 disabled.
I am 97 percent sure I did everything right, including trying about 7 kdz's. I enabled oem unlocking, usb debugging. It is download mode, although the ui lgup is perfectly capable of putting the phone into download mode. I installed all the dlls, and other files.
However, lg up is compaining it can't load new file. I read it is no big deal, but I assume it has to do with the crossflashing config file, and perhaps this is the problem.
I see I can't dump with lgup, which I assume is something only paid up developers can do.
My phone wouldn't root, using any methods. So I am wondering if att has something locked down stopping root or this firmware flash. Maybe in the hidden settings (*#546368#*405#), but I can't make head or tails of anything in those cyptic service menus, even though I explored every menu in detail.
Threads on qfil look like they are written by very advanced cell programmers, and nothing makes any sense. I vaguely get the sense that in addition to the 3 or 4 android partitions (data, system, cache, user) there are scores of hidden phone partitions, which I could dump, if I had a patched version of lgup which probably only a few people have. qfil editing or saving looks linux based, and could take years to learn. And qfil editing probably would brick the phone since any experienced expert in any field has many botched jobs behind them. Of course this doesn't make sense, beyond partion resizing and cloning, to me.
The huge problem is that there are 6 variants of the phone and 4 carriers (formerly), so very few people like me have this variant, switched to tmobile, and realize that they are being screwed because the most important band (for traveling people and fringe area people) for tmobile is missing. My phone has mostly been using band 12, which I asssume is the second farthest reaching band. I thought I bought 4 lg v 40 phones with band 71, but I was mistaken.
I guess the only thing yet to try, is to uninstall all the lg up related stuff and reinstall. I have been searching so many threads, tying everything, maybe there is a sw conflict. Maybe an registry setting and malformed location pointer there to the config file? Who knows. Maybe, I am reading correctly, that if you have an att v40, you are stuck without band 71.
degarb said:
What I am reading on other threads is that if I had a tmo firmware, I wouldn't be able to flash. Also, that no one made an open att firmware, much less with band 71.
I followed the instructions for cross flashing on https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/page-1
It failed, as others with att failed. Then one guy got the older lg command line to work. I followed those instructions (although the instruction page had 3 typos on it, after an hour and a half I found a youtube video without the typos). The command line failed, without any dialog. I assume more cross flashing prohibition.
I see att firmware, but it isn't open, and band 71 is missing. The only reason to flash is for band 71, otherwise my phone is carrier unlocked, but with band 71 disabled.
I am 97 percent sure I did everything right, including trying about 7 kdz's. I enabled oem unlocking, usb debugging. It is download mode, although the ui lgup is perfectly capable of putting the phone into download mode. I installed all the dlls, and other files.
However, lg up is compaining it can't load new file. I read it is no big deal, but I assume it has to do with the crossflashing config file, and perhaps this is the problem.
I see I can't dump with lgup, which I assume is something only paid up developers can do.
My phone wouldn't root, using any methods. So I am wondering if att has something locked down stopping root or this firmware flash. Maybe in the hidden settings (*#546368#*405#), but I can't make head or tails of anything in those cyptic service menus, even though I explored every menu in detail.
Threads on qfil look like they are written by very advanced cell programmers, and nothing makes any sense. I vaguely get the sense that in addition to the 3 or 4 android partitions (data, system, cache, user) there are scores of hidden phone partitions, which I could dump, if I had a patched version of lgup which probably only a few people have. qfil editing or saving looks linux based, and could take years to learn. And qfil editing probably would brick the phone since any experienced expert in any field has many botched jobs behind them. Of course this doesn't make sense, beyond partion resizing and cloning, to me.
The huge problem is that there are 6 variants of the phone and 4 carriers (formerly), so very few people like me have this variant, switched to tmobile, and realize that they are being screwed because the most important band (for traveling people and fringe area people) for tmobile is missing. My phone has mostly been using band 12, which I asssume is the second farthest reaching band. I thought I bought 4 lg v 40 phones with band 71, but I was mistaken.
I guess the only thing yet to try, is to uninstall all the lg up related stuff and reinstall. I have been searching so many threads, tying everything, maybe there is a sw conflict. Maybe an registry setting and malformed location pointer there to the config file? Who knows. Maybe, I am reading correctly, that if you have an att v40, you are stuck without band 71.
Click to expand...
Click to collapse
As mentioned in my previous comment, to you, I can only assume you read, the easiest way for u to get band 71 would be to flash the US Open android 9 kdz.
AsItLies said:
As mentioned in my previous comment, to you, I can only assume you read, the easiest way for u to get band 71 would be to flash the US Open android 9 kdz.
Click to expand...
Click to collapse
This doesn't work, I am getting crossd error. Of course the error that it couldn't load new file doesn't make me confident in the accuracy of the guide, despite reading that we can ignore this error from lgup.
I am 100 percent I did everthing correctly, from enabling oem unlocking to debug mode. All drivers, com ports working. I tried about 9 kdz's or more. I obviously ignored any firmware without band 71.
I am reading that there is not any att open firmware anyway, because no one in the company leaks the code.
This phone apparently doesn't have a bootloader, and so the bootloader can't be unlocked. But that should only affect the rooting ability.
I can't see how att would have locked flashing from the bootloader, it seems to me that they would have had to do it deeper in the phone. so far, about the only hidden dialer code that work is *#546368#*405# (other than 2 others), this yield a very technical service menu that seems purposely obfuscated, so only a tech with an inhouse manual knows what these menus can do. I can only make out of few menu items' purpose. But nothing useful that I understand.
degarb said:
This doesn't work, I am getting crossd error. Of course the error that it couldn't load new file doesn't make me confident in the accuracy of the guide, despite reading that we can ignore this error from lgup.
I am 100 percent I did everthing correctly, from enabling oem unlocking to debug mode. All drivers, com ports working. I tried about 9 kdz's or more. I obviously ignored any firmware without band 71.
I am reading that there is not any att open firmware anyway, because no one in the company leaks the code.
This phone apparently doesn't have a bootloader, and so the bootloader can't be unlocked. But that should only affect the rooting ability.
I can't see how att would have locked flashing from the bootloader, it seems to me that they would have had to do it deeper in the phone. so far, about the only hidden dialer code that work is *#546368#*405# (other than 2 others), this yield a very technical service menu that seems purposely obfuscated, so only a tech with an inhouse manual knows what these menus can do. I can only make out of few menu items' purpose. But nothing useful that I understand.
Click to expand...
Click to collapse
If you read the comments in the Specific guide for doing this, you'll find where the 'crossd error' is resolved.
If u have trouble with that guide, ask questions in that guide. That's where the answers are and where people who have done it will answer. I can assure you it does work. I've done it.
Related
Like most Droid 3 owners I'm sure, I'm tired of paying ~$105 a month for cellphone service through Verizon that I could be paying ~$70 a month for through T-Mobile.
I've read the other thread here associated with unlocking the GSM portion of the Droid 3, but a lot of it seems to be shrouded in maybes and varied successes with a limited pool of test devices to draw on.
From what I gather thus far, the following is true:
- You can unlock the GSM capability of the Droid 3
- You can operate it on T-Mobile
- If you do, you will only get "Edge" connection speeds - No T-Mobile HSPA+ or 3G speeds. "Edge" only, at 512 kb or something like that.
Can anyone confirm this? Is there a way to get a Droid 3 to operate on T-Mobile's network at full speed?
Is there a more reliable and easier to use method to convert a stock VZW Droid 3 to something operable on T-Mobile?
Thanks in advance to anyone who can accurately answer these questions.
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Tutorial
note: This is not tied to any specific rom, it is not using the chinese rom it is simply taking the radio off the chinese rom which is all we need. It hasn't changed anything to me in user space that I have noticed.
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
gfunkmonk said:
All you have to do is flash the radio.img from SOLANA_SLNCT-57.1.60_Fastboot in fastboot mode
Code:
moto-fastboot flash radio radio.img
then add the following lines to the build.prop
Code:
persist.ril.rssi.enable.param6 = 1
persist.ril.baudrate=230400
I can confirm this works with an AT&T sim in an unlocked phone, tested with stock and liberty 2.0.
Click to expand...
Click to collapse
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Even if you go through all of that you I'll still have only EDGE because our radios don't use the 700 MHz. Just sell it and get a phone for T-Mobile.
Sent from my XT862 using XDA App
BenSWoodruff said:
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
go here http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Thanks for replying. That's where I wound up going on my own because I was trying to use his CM7 last night. Can't seem to get it to flash though. Backing up with Safestrap isn't working either...getting an error because /system won't backup for some reason.
I think I'm gonna flash everything back to stock, uninstall Safestrap, and try the above from the beginning. I'd like to see if I can at least get edge and below on T-Mobile using a US ROM.
Thanks again!
G2x with CM7
D3 stock for now, trying to get T-Mobile compatibility
anathema_forever said:
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Click to expand...
Click to collapse
So, I have a couple of lines on VZW, but they are all used by family members on my account, and I don't have a VZW SIM. The guy who sold me the phone said he already unlocked it, and I believe him, but is the SIM an issue and is there any way to know if the phone is still unlocked? Can an unlock be undone after wiping internal sd?
I'm asking because I think I can just not worry about that step, but I want to double check. I put it back to stock 2.3.4, now showing 5.6.890 xt862 instead of whatever the xt883 was. I did this to get rid of the previous owner's Google account. Edge, calling and text were working on T-Mo when I bought the D3 a few days ago. When I put my SIM in now, however, and change it to GSM/UMTS mode, there are no operators available when I tap on the list and of course it doesn't work yet. I understand this is due to putting it back on stock lol, but I'm gonna go ahead and try flashing the radio and seeing what happens.
It's already rooted using zergrush. Has safestrap and I can boot into it by rebooting/pressing menu, but my /system folder won't back up. That's the only sign that something is wrong other than the fact that no ROMs will flash in safe mode. I've already left comments on Hash's site, so I'm waiting over there too. Figured I'd pop in here again real quick
Thanks.
UPDATE (from the other forum):
My Droid 3 is working on T-Mobile for voice and text. This is exactly what I wanted. Got some great in-depth help on this one, especially from @tspx23. Thanks a ton! This will be my daily driver now until we switch to VZW, at which point this will turn into a back up, unless I fail to find something else worth a contract at that point lol.
I might write a guide later on if anyone wants it. The process is easier than it seems, as long as you have it in plain english lol.
Thanks to anyone who contributed to this!
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Tmo has horrible coverage and awful customer service. Cs is all nice to you but lies about everything constantly. They did nothing but screw me. That's the whole reason I'm on verizon now. At least now I have coverage and won't be lied to whether or not I have it, or be told to get wifi and then u can make calls since u don't have service.
Sent from my DROID3 using xda premium
I don't know of anyway besides a sim card to check if its unlocked and I am not sure a verizon one would ask for the sim unlock code even if it was locked but sim cards can be really cheap. If your phone was unlocked that will never be undone, if it was working on tmobile before you reverted to stock then it is unlocked, it would not have worked using tmobile otherwise.
are you using the latest version of safestrap, he released a bugfix version pretty recently? Could you be more descriptive of what you did while in safestrap?
It is not rom specific as far as I know, I am just using the stock one.
@Darksurf, I agree. I never had them but before I moved they didn't cover my old town. Verizon may be expensive but at least they tell you they will rape you at front and explain all charges.
Sent from my XT862 using XDA App
you can also try with at&t in full3g. As they have the same bands the d3 has
Enviado desde mi DROID3 usando Tapatalk
I will see tomorrow if this works with ICS
Radio and build prop edit
I'm staying on T-Mo till they go under. They are cheap and I have unlimited Edge, which is all I can get on this phone anyway lol. Only ten bucks a month for data, since I have an older package from before they tried to hike their rates.
My D3 is having some issues after I reboot, and sometimes just randomly, it will lose all signal and tell me that my preferred operator cannot be found or error connecting. I have been just rebooting and sometimes wiggling my SIM around to see if it fixes, and it does.
Only other thing that is a little weird is my phone thinks it's an xt883, even though I'm on the stock VZW ROM. I'm wondering if this is causing some issues that I'm not qualified to really diagnose lol. Usually after I reboot, I have some of my google apps' names in Chinese, but I'm not sure if that is from radio.img, new build.prop, or from changing my bloatware to .bak.
Also, be advised that if you remove bloat, conversations.apk breaks incoming text if it isn't seen by the system. I added .bak to the end of it and could send texts to my wife, but couldn't get any messages. I changed it back and texting works fine. I use Chomp SMS, but that didn't seem to matter.
Have fun
P/S: also, when choosing operators in settings, you have the option for T-Mobile 2G, AT&T 2G or 3G. Just to confirm ;-) probably because AT&T's 3G bands are the international standard, right?
when you flashed the stock rom back onto it did you delete the /system partition and do a factory reset on your device before you did it?
ericerk said:
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Click to expand...
Click to collapse
I'd love to see someone put these mods into a ROM, but I'm not sure if any of it is compatible with existing ROMs. I also accomplished this on stock. When I get around to flashing CM7 again (or trying to at least lol), I'll post about how it goes.
I'm thinking that when I wiped my phone, the unlock remained but the radio.img that was on the Chinese ROM was undone or lost. Flashing it was easy though, using cmd mentioned earlier in this thread. I just needed help figuring out how to set it up, since I'm a noob at command line lol.
After that, I downloaded adb and tried to use other commands I've found (which claimed to work, but didn't for me somehow) to change out the build.prop. This failure was likely my fault lol but I found it easier to just use Root Browser lite to back up my original build.prop then replace it with the modified one.
I figure that if my SIM doesn't work after flashing some other ROM, I'll just try the two main steps again and see if it works then. If anyone really wants to do this, it isn't too hard or not worth it in my mind. I also figure this phone will be relevant enough for a while longer, considering I am cool with Edge speeds, I certainly won't mind being stuck with VZW's 3G whenever we change over. I am in no hurry to get LTE battery suck or bulkiness either. I'll wait for a little more refining to be done on that end before I upgrade from this phone
I am interested in making the phone compatible on T-Mobile / ATT by flashing XT883 radio. I have one question: Will the "unlocking" turn the phone completely GSM phone so it can no longer work on CDMA network?
Thanks.
Probably until you flash the Verizon ROM back I would assume.
Sent from my XT862 using XDA App
No. XT883 is also CDMA compatible, so the ability to use CDMA should stay. You might need to do *228 though.
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
BenSWoodruff said:
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
Click to expand...
Click to collapse
i wasn't able to flash the chineese rom, idk why it just wouldn't let me :/
So as of saturday my unlocked TMobile Note 4 stopped working as a phone, and won't let me make calls.
Information:
-Was on Dr. Ketan L3 version of his rom when it stopped working
-Using the N910T on AT&T
-IMEI is fine and not damaged, both numbers match (using *#06#)
-It shows bars, but when I go to make a call "Not Registered On Network"
What I've Done:
-Flashed Stock Firmware via Odin (Autoboot, and F.Time Rest checked)
-Factory Reset after odin flash
-Checked APN
-Set on LTE/WCDMA/GSM
-Searched for Networks, finds them, but when I choose AT&T it takes forever and then finally kicks me out and then in notifications, I get the "Not Registered to Network"
-Did the remove the battery thing, and removed sim
-Went to AT&T and got a new sim, worked for 1hr (sporadically) and then went back to "Not Registered on Network"
-At the store I was on phone with AT&T tech trying to troubleshoot the problem and that is when it was working shortly
-Called T-Mobile and checked to see if they blocked my IMEI number, nope they didn't, couldn't help me out further than that
-AT&T was showing that it was a Note 4 so not having that coming up as a Blackberry issue that some reported, so that's not it
-*#0011# shows service limited, but it is unlocked and everything is fine, the IMEI is good, and all is well but the limited service
-Put it in Airplane mode and woke it back from there after 5+minutes
-cleaned the connectors on the sim (new sim anyways so shouldn't really need them)
I'm running out of options, the only thing I can think of being the problem is that I might have started out using this phone on COD2, and when I flashed a COG2 firmware it didn't like that and so my phone's account settings didn't fully transfer.
Also I was messing around with the bands settings (*#2263#) what should they be on? Automatic, LTE/GSM only, or what?
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
kabuk1 said:
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
Click to expand...
Click to collapse
Thanks, yeah it kicks in randomly for like a minute and then dies, I take it to my parent's house (about 10 miles away) and along the way I get a good signal, but then when I reach their house, back to nothing. I was using it just fine the week prior. I partially blame Dr. Ketan, ever since installing his rom, I had multiple issues. I since uninstalled it and tried going back to stock. Any idea on what a good "safe" band setting is? I have that settings set to automatic, but if there was a good "safe" band that would be great. A common LTE tower. Even when I do connect or get connected, I can't register on that network, my phone won't let me. I've tried that. The bars drop to zero. I damaged my antenna wire (white one) and I just replaced it with a new one I purchased, but the hacked together one seemed to be doing the same quality job as the new one is. It shows the signal, but as soon as you try tying it down to a network it rejects it. I was afraid that when I flashed the stock image via odin it removed the unlock, but it was still there. I just hate that now I have a $500 pda, when it was a phone and now i'm relegated to using a f*ing flip phone.
i think your antenna cable is damaged. the only way to know that is be close to a tower, and see if your work or not.
bought and replaced with new ones, I get full bars, in my bedroom, but apparently they're tied to Tmobile since when I try to register it to AT&T they magically disappear, but when I close the app, they come back at the same strength level. I can't register them to Tmo since the sim. Yet my phone is telling me it's unlocked (*#0011#), IMEI = PASS, 1;
I think the prob is due to the different frequencies.
Your baseband would not be tied to a rom(ie Dr Ketan) Unless that rom contains Modem.bin
Your apn needs to be att if that's your Sim obviously.
International version has a different chipset. .. I know it's not your case. .
But it's open to any Sim. ..
I can say this.. I have a N2 unlocked (tmob) I run an Att Sim it works but the sig is really spotty... COD6/ COG2 may not be lining up frequency wise with your att Sim. ..
Try rolling your baseband back even further. .
Flashvetrin
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
dcoke said:
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
Click to expand...
Click to collapse
Well I would think automatic is out for sure.. the other prob would be after reboot the chipset will search for the default.. but I could be wrong.
I do not know what the numbers would be for band identification.
You may get lucky when calling Att and ask for someone in a higher tier. To give you some numbers for frequincies .
But you have ruled out hardware correct??
By putting a tmob Sim in????
Cuz I know you posted you did antenna work..
And I do know you said you get bars then it fades..
The fact it fades and doesn't lock into even a G band for example. Just leads me to believe the apn can't lock down based on the frequincie and the built in lte chipset...
It would be nice to just flash an att modem wouldn't it?? But don't even think about it.. lol you'll soft brick..
I wish I had a better solid answer you. You may just start testing those different bands and see if you get closer to a lock.
Flashvetrin
U rock, lol. Thx man
My Tricked Out N910P
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
dcoke said:
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
Click to expand...
Click to collapse
Heres
A simple method for COD6
And try odin 3.07
I need to think about this some more and get back to you...
This is a partial firmware.. it consists of the modem and bootloader COD6.
Also to rule out damage if you can get a T Mobile Sim put it in the device and see if it locks down a signal....
Flashvetrin
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
dcoke said:
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
Click to expand...
Click to collapse
You are the first of this kind that I'm aware of.. in regards to this issue..
Make sure you read the detail in if your device bootloops, to reboot recovery and flash the Rom.. if you want flash the Rom in the op that I've linked you to.
Wipe sys/dal/cach/data..
And flash it can't hurt.. [emoji16]
I really hope a Tmob Sim and or COD6 gives you results...and good ones at that.. [emoji2] [emoji106]
Flashvetrin
Got the sim card, $65 for that crap, and it didn't work. Called T Mobile customer service, explained my situation and how I was calling on another phone on another carrier and they insisted on calling me back on the broken not working phone. I guess I'm just screwed, and lost $500, which like I said, I can't afford to have. It's just so frustrating. I also tried the COD6 partial firmware, and nothing there also. I'll try t-mobile again. The only and last option I have, if possible, is to try to relock my phone and re-unlock it since there isn't any real way to tell if my GSM is damaged. I think my unlocked status got damaged when my phone upgraded to COG2, and since it's in that weird limbo state I can't use my phone. Do you know how to relock it?
Edit: When I look at my IMEI Number through *#06# it shows that the last two digits (independent of the actual IMEI number, since that matches everywhere) to the right of the "/" as 14, yet through "about device" it shows my imei version as 10. I assume that the 14 in the "06" screen is the version it's reading off the phone, could that be causing the issue? How would you even fix that? I don't know. but thanks again, you've been helpful.
So, I've recently rooted and unlocked my device and I wanted to know if I can bring it to another carrier and still get data.? I'm using the LS991 Sprint version. I also wanted to know if there are any good CDMA Workshop alternatives; it's really expensive and I'm only gonna be using on a few devices.
Dfs
So you rooted (doesn't really matter with respect to carrier support) and you unlocked it (that's what matters with respect to carrier support) - so you put in a SIM card for the carrier you want, set the APN data (use Shortcut Master if needed, there's a version specifically modded for the LS991 directly available in my post HERE - might be a good idea to read that post as well since that's what I did myself.
Worse comes to worse if you have no luck because you unlocked your LS991, consider installing the global LS991 ROM (whether it's Lollipop ZV6 or Marshmallow ZV9 or ZVA - if you install ZVB you can never go back to anything prior so be aware of that) which will work much better for other carriers than using the unlock mod so many of us have done in the past.
Hindsight being what it is, if I knew about the global ROM when I got this G4 recently I wouldn't have mucked around with all the unlocking crap and the carrier partition at all for any reason because just installing the global ROM (or modifying build.prop to allow for global unlocked operation) is way more useful and less damaging to the phone. Modifying the build.prop isn't necessarily a cakewalk but, since someone else has already done it for others and posted the global ROM(s) for Lollipop and Marshmallow (as .img files you flash using the Send_Command.exe/dd method) it's really not a big thing anymore.
If you muck up flashing an .img file you can typically just use LGUP and a TOT file to get things working again so it's relatively safe overall, but if you muck up the unlock and trash the carrier partition content the phone will end up being pretty much useless unless you have that information safely backed up someplace (I'd say multiple backups in multiple locations, to be honest).
Anyway, if you truly want the phone to be capable of working on other carriers, my suggestion is go for the global ROM but that's just my own personal opinion on the matter. I'm using tabp0le's MellowMallow ZVB global ROM on my LS991 and T-Mobile LTE works just fine for me, for the record. It did take a little work - I wrote about how I got the full phone/data working in that post with Shortcut Master - but it does work.
Thanks for the help!
One last question, how did you get other carriers to let you activate the phone? Everytime I try they ask me imei then tell me my phone won't work on their network.
Well I've had service with T-Mobile in the past (not currently but will again soon), I have a bunch of T-Mobile microSIM cards because whenever they put the SIM card activation kits on sale for $.99 or sometimes even free (rare but it happens) I usually grab 3 at a time so I have 'em around for testing purposes. T-Mobile doesn't require me to provide any info to them, and even if I go to their website right now and input my IMEI number it'll say it's not recognized, etc but it's not relevant: it works, and that's what matters.
Most carriers don't actually require you to provide the IMEI for any reason as long as you can get one of their microSIM cards (or nanoSIM with adapter) and then get service without having to contact them. T-Mobile is somewhat unique in that process I suppose. With this SIM card I have (it's never been activated) I can go to their website and sign up for service right now and it'll be active in 10 minutes or less, sometimes when I've activated service (it's prepaid so I don't necessarily keep it month to month, sometimes I choose some other service for testing) it's done before I even sign out of their website, like 30 seconds or less and wham, the phone beeps telling me service is working.
So, the advice is: get a SIM card for the phone from the carrier you're interested in and go from there, not sure what else to suggest honestly.
br0adband said:
Well I've had service with T-Mobile in the past (not currently but will again soon), I have a bunch of T-Mobile microSIM cards because whenever they put the SIM card activation kits on sale for $.99 or sometimes even free (rare but it happens) I usually grab 3 at a time so I have 'em around for testing purposes. T-Mobile doesn't require me to provide any info to them, and even if I go to their website right now and input my IMEI number it'll say it's not recognized, etc but it's not relevant: it works, and that's what matters.
Most carriers don't actually require you to provide the IMEI for any reason as long as you can get one of their microSIM cards (or nanoSIM with adapter) and then get service without having to contact them. T-Mobile is somewhat unique in that process I suppose. With this SIM card I have (it's never been activated) I can go to their website and sign up for service right now and it'll be active in 10 minutes or less, sometimes when I've activated service (it's prepaid so I don't necessarily keep it month to month, sometimes I choose some other service for testing) it's done before I even sign out of their website, like 30 seconds or less and wham, the phone beeps telling me service is working.
So, the advice is: get a SIM card for the phone from the carrier you're interested in and go from there, not sure what else to suggest honestly.
Click to expand...
Click to collapse
You good sir are a god among men, phone and data are working like a charm. Now I can tell sprint to go **** themselves!
glad it worked for you. MY experiences with ls991, i am using it nvmode. zv6 rooted works for me with cdma data. but data doesnt work with zv9 or zva. global rom doesnt work unless, I edit build.prop target carrier to SPR . it is open to use it as global mode. I am using it in cdma nv mode.. not with any sim..
sunilromy said:
glad it worked for you. MY experiences with ls991, i am using it nvmode. zv6 rooted works for me with cdma data. but data doesnt work with zv9 or zva. global rom doesnt work unless, I edit build.prop target carrier to SPR . it is open to use it as global mode. I am using it in cdma nv mode.. not with any sim..
Click to expand...
Click to collapse
so in my case i use att on ls991. my build prop is ruim,sim i believe. now does that sound rite for gsm?
also another cdma workshop alt if qpst i used that one to rebuild my g2 a few years back
TheMadScientist420 said:
so in my case i use att on ls991. my build prop is ruim,sim i believe. now does that sound rite for gsm?
also another cdma workshop alt if qpst i used that one to rebuild my g2 a few years back
Click to expand...
Click to collapse
Ruim is basically used when it comes to cdma sim card.
"Removable User Identity Module (R-UIM) is a card developed for cdmaOne/CDMA2000 ("CDMA") handsets that extends the GSM SIM card to CDMA phones and networks. To work in CDMA networks, the R-UIM contains an early version of the CSIM application."
Your is at&t 4g gsm card. [emoji4]
Check your build.prop and search for
ro.build.target_operator: OPEN
Most probably for global mode open works
For making it work on cdma nv, i have set it to SPR
You can tweak with it by changing to options, it will also change signal bar and 4g symbol like at&t
These will show a Standered international 4G data icon for 3G/HSPA+ and LTE for LTE.
ro.build.target_county: CA
ro.build.target_operator: TLS
These will show a standered international 3G data Icon for 3G/HSPA+ and 4G for LTE (Messes up settings menu pretty bad)
ro.build.target_county: SK
ro.build.target_operator: SKT
If you want the AT&T 4G and 4G LTE Icons.
ro.build.target_county: US
ro.build.target_operator: ATT
Sent from my LGLS991 using Tapatalk
---------- Post added at 02:36 AM ---------- Previous post was at 02:26 AM ----------
My fav cdma tools are qpst, cdma workshop, dfs, revskill and bit advance is qxdm All are freely available. I cant say which one is best hahah. Trust me for me, all of them worked at some instance when i was stuck. Revskill is great with htc finding spc. Though i used dfs mostly.
Sent from my LGLS991 using Tapatalk
I recently bought an unlocked Galaxy S10 SM-G973U on Amazon. Got new SIM card from a Verizon MVNO and activated phone. The phone downloaded Android 12, One UI version 4.0. Firmware Build number SP1A210812.016.G973USQS6HVA1. Service provide Software version SAOMC_SM-G973U_OYN_SPR_12_0007 SPR/XAA/VZW. The problem is there is no menu option to activate/switch on VoLTE which means when I'm on a call there is no internet. I've talked to the MVNO tech support multiple times and was told they couldn't see any problems on their side, or that the SM-G973U does not support VoLTE which is not true. I found on one of AT&T's sites that the SM-G973U needs a software patch to enable VoLTE. I also found a couple of USSD codes but they either didn't work or didn't get me to the right setup screen to turn on VoLTE. I even stopped by a Samsung store and they weren't any help either. They said they could re-flash a stock firmware but it would revert to being locked to a carrier which is apparently also not true based on what I've read on this forum. Anyone know how I can turn on VoLTE or know of an apk file or software patch to enable VoLTE?? Does one of the firmware versions posted online have the patch to turn on VoLTE??
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Thanks. My carrier is Straight Talk which is now VZ. The SIM card they sent me has the wording "Verizon Compatible" written on it. I finally found a document that explains how to interpret the CSC codes and your explanation clarifies my understanding of it. Sound like I'll have to re-flash it. Since it was originally a VZW phone I'm thinking I should flash it back to VZW to see if that works before trying U1.
Dumb question as this is my first time flashing a phone. (I've flashed quite a few other things but never had to worry about CSC codes and bootloader versions, etc.) I don't see VZW firmware on samfirms or sammobile. I see Sprint, T-Mobile, and one listed as USA without carrier info but I don't see one for VZW. Can someone point me to the correct location to download SM-g973U and U1 firmware for VZW? Greatly appreciated and thanks for putting up with my lack of knowledge!
Edited: Found the files on sammobile. Will try the U1 (VZW) first. I'll keep my fingers crossed.
schwinn8 said:
I think the issue is that your phone is showing SPR/XAA/VZW. You say you're on a verizon MVNO (who, by the way?)... but your phone isn't seeing that. It's actually saying it's active for SPRint. The second one, XAA, means it's not able to detect the SIM type... and the third was that it was originally VZW, which you can't change and isn't really relevant. (That's just what the phone was "born" as).
Bottom line, your phone isn't seeing VZW or an MVNO as the active CSC nor the SIM card. In the past, the easy thing was to change the CSC to what you need, but I haven't found a way to do that actively. What's supposed to happen is that the CSC should update based on the SIM card and cell signal you're getting... but this doesn't always happen. I bought two phones - one switched with no issues, the other I could not get it to change no matter what I tried.
That said, the easiest thing is to clean flash the phone with ODIN to a VZW or your MVNO's ROM, so that (hopefully) the CSC updates automatically. You could also consider flashing a U1 (unlocked) ROM, as yours is not technically an unlocked ROM (U means it's a carrier ROM... which may be why it's not switching over?)
Again, I tried all of these on the second phone I bought, and nothing would switch it (my carrier is Total Wireless, which is a VZ MVNO, and actually shows up as Tracfone (TFN). I had to return that second phone and get another with TFN already activated, and that worked fine... so be sure you do this before you drop out of your return period.
Bottom line, you should be able to get this all working... my VOLTE/VOWIFI works fine... just a matter of getting you there.
Click to expand...
Click to collapse
Success! Was able to flash U1. VoLTE is now working. The CSC now shows TFN/TFN/VZW. Much appreciated!!!
Awesome, glad to hear that fixed it easily!
And TFN... I'm a fan there, too!
Hi! I'm having a similar issue with the same model and happy to see someone was able to enable VoLTE. However, most of what you said above is a foreign language to me. Would one of you be willing to give me a crash course in what you did?
Here's my specific situation. Last week (~1/4/23) Tracfone shutdown 3G. My Samsung Galaxy S10 (SM-G973U) says my network is set to LTE/3G/2G. I've read LTE is 4G, but still can't make or receive calls/texts, but data and 911 calls still work. Their tech support is no help.
From reading online it sounds like I may need VoLTE, not just LTE. Hence finding this thread. If one of you would be willing to spare some time to walk me through what you did I'd really appreciate it. In the mean time I'll try to figure out what "flashing" mean in a context that doesn't involve showing body parts
Thank you in advance!!
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
schwinn8 said:
I'm on Tracfone (they were bought out by Verizon, BTW) - I was on Total Wireless before, which is now Total by Verizon. You might try contacting support again, as they are now VZ, and may have more help to offer.
My S10+ is running 975U1 now, and it works for VOLTE/VOWIFI properly. You may consider getting a U1 ROM installed, and maybe even the VZW (or TFN) version if available - that may get you working.
Did VOLTE ever work for you before on this or any other carrier? What is your CSC right now?
Click to expand...
Click to collapse
Thanks for replying! I'm not entirely sure if VoLTE has worked previously. I bought this phone 6/2021 and have only haver had tracfone service for it. I did find in my setting that VoLTE calling is set to on so it seems like it should work. Of note, the 4Glte in my status bar has always been grayed out (I went back and looked at some old screenshots).
My current CSC is VZW/XAA/ATT.
I spoke with tracfone customer service yesterday and they had me reset my network setting and now I don't even have data and the 4Glte in my status bar that was previously gray has now completely disappeared.
Their customer service refuses to talk to me now (literally no one answers when it transfers to an agent) or they hang up on me, and no I haven't been rude, but I have told them I'm recording the call.
I bought a mint mobile package last night because I'm beyond frustrated with Tracfone. I'm worried I'll have the same problems with Mint. I'm not sure if my settings are screwed up or if it's just Tracfone. In any case things are worse now after talking to customer service yesterday.
I also notice there was no APN setting on my phone so I updated it today and restarted but no difference.
Thanks for any input!! Much appreciated. Sorry for the novel.
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
schwinn8 said:
Ok, so based on your CSC, the phone is not seeing the SIM's carrier - it's showing XAA which means it's using the default settings, which is probably why your not getting VOLTE. The active CSC of "VZW" may be ok... depends on which carrier you're on with Tracfone. I think they're VZW only, but I'm not completely sure.
You may want to just get a new SIM card and get that activated. HOWEVER, the problem you'll likely face is that the phone was born ATT (last CSC). This means the IMEI won't match a "compatible" phone to Verizon, and they will flat out refuse to activate it (even though WE al know it will work fine). If you still want to do that, you will have to activate the new SIM on a VZ "compatible" phone, then you can swap it to the S10. Note that VZ complains about this when you talk to them... so don't tell them you're doing this... but I've done it many times and it works fine.
If your actual behind-the-scenes carrier is ATT, then you can do the activation with your phone without issue.
If none of this works for you, you can switch carriers to an ATT MVNO and you should be good to go.
Click to expand...
Click to collapse
OK some of that was still over my head. I'll see what happens with the Mint Sim... one f/u question now though. You said the ATT means my phone was "born" ATT. I bought my phone off backmarket and it was sold as "unlocked". Was that not true? How can I be sure in the future if I buy a used phone that's not from my carrier that it will actually be compatible?
Unlocked just means it's not locked to a carrier. That is true in your case, otherwise you wouldn't have been able to install ANY non-ATT SIM. So, you did the right thing to get an unlocked phone, and that is what you got.
The issue with compatibility is just the asshole carriers spreading lies. They do this to try to get people to buy THEIR phones, for no reason other than to make money and confuse consumers. The "born" CSC has no bearing on anything, really... neither does the carrier-specified IMEI. In your case, the XAA is good, which means it's a multi-carrier ROM, which works with all USA carriers.
Mint is a good idea - being an ATT carrier (IIRC), that should work and they should help you get it up and running even if they have to activate it. Good luck!
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Goldie8709 said:
Awesome! Fingers crossed!! Thank you for your time and all the info❣
I'll try to remember to give an update in a few weeks for future readers
Click to expand...
Click to collapse
UPDATE: Switching to Mint worked like a charm! Once my number ported and I put the new SIM card in, service was instantaneous! I've had Mint for 3 weeks now and the service is so much better than with Tracfone! My calls go through nearly as soon as I hit call, the internet is faster.
I didn't need to do a thing either. No making APN settings, etc. I'm betting it has to do with what you said about my phone being born ATT. So funny because the software(?) is Verizon - shows the Verizon when I restart/power up. I still love my bastard phone
So thankful I didn't buy a different phone!!! Again thanks for all your help @schwinn8
Thanks for reporting back and letting us all know, and I'm glad it worked out well!
Yeah, the carriers pull this nonsense all the time... it's BS. The phones are all the same, only the ROM changes. If we can change ROMs (which we can) then there should be no reason to force users to specific IMEIs. But we know why they do this - follow the money. I encourage people to write to the FTC and FCC about this (I have).
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.