Related
Hello,
I looked around a bit about finding the A-key. I just had my phone remotely fixed for the authentication problem, but they never told me the A-key even though I asked.. I was wondering if there was a way to pull it off the phone..
This is verizon, the akey is blank in EPST.. I tried CDMA Workshop and it got a bunch of crazy info but errored out on when getting the a-key. I also looked through qpst but it doesnt look like a-key is in there(under service programming).
Anyone have any ideas? Im about to start flashing and Id hate to be on the phone with verizon for another couple of hours every time this happens.
Before I called verizon I even tried generating my own Akey with that akey calculator but that didnt really work..
Thanks
some verizon service areas do not use an akey stored on the phone but instead they authorize in their sytem based on your esn and some identifier your radio sends them. This is the way it is in my area. the verizon tech told me all of their systems will be moving this way, supposed to help prevent phone cloning and some other security issues.
I was assured that all i would need to do is call if it tells me phone not authorized and they will correct it.
rmancl said:
some verizon service areas do not use an akey stored on the phone but instead they authorize in their sytem based on your esn and some identifier your radio sends them. This is the way it is in my area. the verizon tech told me all of their systems will be moving this way, supposed to help prevent phone cloning and some other security issues.
I was assured that all i would need to do is call if it tells me phone not authorized and they will correct it.
Click to expand...
Click to collapse
Ah I see so you're saying that it actually is blank not just hidden away..
Alright, thanks.
I gotta say im thinking this is true. I just flashed my phone to NexVisions rom and cant activate so im gunna have to wait till morning to get it activated because tech support stops working in the middle of the night i guess. If its as simple as it sounds, I will report back as such.
Soooo I left the phone plugged in on the otherside of the house (I figured I cant get calls why bother bringing it im my room) and it wasnt able to make calls i figured no out no in so i shouldnt be able to get calls. I wake up this morning to 16 missed calls because someone called in at work and Im the only one who can work.... it activated at some point in the night. *228 worked just fine... completely baffled... just worked out of the blue, does this have something to do with recieving calls? any ideas?
blksprk said:
Soooo I left the phone plugged in on the otherside of the house (I figured I cant get calls why bother bringing it im my room) and it wasnt able to make calls i figured no out no in so i shouldnt be able to get calls. I wake up this morning to 16 missed calls because someone called in at work and Im the only one who can work.... it activated at some point in the night. *228 worked just fine... completely baffled... just worked out of the blue, does this have something to do with recieving calls? any ideas?
Click to expand...
Click to collapse
When it wasnt authenticated before i called verizon I got the calls but I couldnt answer them and they would be missed calls after one ring or so.. Maybe thats what was happening in ur case..
Could be that verizons systems updated themselves or something..
Hey all I was given an Eris by a friend so I rooted it easy enough at 1.5 last August. Since then I have had a few different custom roms loaded and everyone of them that I tried to activate the phone on didn't work. This phone was not activated when I rooted it, and I have to take it to my local verizon shop to have them try to activate it after they deactivate my moto droid 1. I' ve been digging for awhile now trying to figure out if it's the baseband version or what. Can someone please help if at all possible.
Current phone info:
Firmware: 2.1
Baseband: 2.42.01.04.27
Kernel: 2.6.29,
Build: 2.36.605.1 case release-keys
Software 2.36.605.1
Browser WebKit 3.1
PRI: 2.11_002
PRL: 58003
ERI: 5
When the phone boots it shows the verizon logo which doesn't completely mean the radio is flashed for versions network, but I have no idea how to tell otherwise.
Thanks.
If you activate the phone with a stock, or near-stock ROM (let's say Ivanmmj's "Official 1.0"), then thereafter, nothing you do to the phone with dev ROMs from this site will change the phone's activation data (stored in the phone) afterward - not flashing a different radio, nor performing a "wipe/factory reset" (in Amon_RA), nor installing a different ROM will change that.
When it comes to deactivating the phone - or more precisely, clearing the activation state of the phone, the only thing that seems to accomplish that is one of the factory recoveries - Amon_RA does not touch it. This happens if you perform a "factory reset" in the regular OS, which actually causes a boot to the recovery, which does all the "dirty work". You can also manually boot the stock recovery, and use the wipe menu to achieve the same result.
You can see that this makes de-activation inconvenient for rooters - but most of them don't need to do that.
So I'm reluctant to conclude that the radio firmware is affecting your result.
What happens when you try dialing *228 option 1? The call goes through, but you get an error voice announcement after some delay?
I was under the impression that people that flip back and forth between two phones on the same service don't ever bother to de-activate the phone in use: they just make sure that current phone is turned off before they attempt to activate the next phone.
I suppose you could restore the phone back to complete stock (including the stock recovery) before activating it, and then re-root it and reload a nandroid backup... but that's sort of a pain in the neck if this is something you plan on doing regularly.
bftb0
PS I could swear I have activated my phone (*228 option 1) with a dev ROM on the phone, but don't remember the specific details.
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
RnkG said:
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
Click to expand...
Click to collapse
I just re-read your initial post and actually can't tell if the phone has ever been successfully activated since you received it. You mentioned taking it in to the Verizon store, but you didn't say what the outcome was - was the Verizon store unable to activate it?
Normally when you dial *228 it just sounds like a normal voice call - you hear audio, the recorded lady's voice provides a menu, etc. Since that needs to happen in order to activate the phone, it is fairly obvious that the cellular radio must be working completely for that to happen - so the fact that you don't hear any audio seems to indicate something is wrong.
Why don't you try and reflash the phone back to stock using the download from this thread which also flashes the radio:
[ROM][10/20/2010]FlashBack21 v1 -Return to Factory Stock - UPDATED
And see if that gets you any different result. That would eliminate any effect of "dev" software, and also reflashes the radio with the July 2010 version - the last one officially shipped by VZW/HTC for the Eris. If you can't get audio (and you are sure from playing music that there isn't a speaker problem), that would point to a hardware problem.
BTW - even if the phone is working completely, VZW needs to already be aware that it's ESN/MEID is associated to your account, and I think that your other phone needs to be turned off at the time you attempt activation.
cheers
Thanks again. I'll work through that and then post back here.
Thanks again!
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
RnkG said:
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
If they activated it I don't know how they could be blocking it. I would've checked to see if it was working before I left the store, and when it wasn't, would've brought this issue up with them.
Are you just going by their word that they activated it, or is there some other way you can tell that it's activated, even though you're not getting any service? What I mean is, if you're not getting any service, how can you be sure they activated it successfully?
RnkG said:
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
Other than bad hardware, the only thing which would cause this problem would be a "blacklisted ESN" - that would usually be a stolen phone, or a phone that was on a Verizon account that was abandoned by the subscriber with an unpaid balance. (Verizon doesn't want customers who cheat them to continue to cheat them by habitually opening new accounts under assumed identities, so they just blacklist the ESNs of phones that were used on abandoned accounts with unpaid balances)
Verizon won't activate phones with blacklisted ESNs - but if you walked in the phone store and asked them to activate it for you, I would presume that they would have told you straight up "We can't/won't activate this phone".
The radio does not use a separate technology for 911 calls, so, yeah - there is something odd going on here. Perhaps you had a "green" VZW customer assistant that isn't familiar with what happens when someone wants to activate a blacklisted phone, and simply didn't take notice when "something unusual" popped up on the computer they used to enter in your activation request.
You've got stock software on the phone now, so I wouldn't hesitate to pick their brains about it. Telling a VZW tech about the 911 call might convince them a little better - but just remember that you are admitting to a criminal activity (calling 911 without due cause).
Also - bear in mind that by law (in the US) every cell phone has an aGPS unit in it, precisely for the purpose of emergency services locating a cellular handset when the user is incapacitated. ( There is a small risk that if you make a 911 call, cops will end up at your door even if you hang up.)
Hi!
Rooted with cmahendra's offline Lelus method (and to anyone who's done that, my hat is off to you).
**SHORT VERSION**
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/receive phone calls.
**DETAILED VERSION**
Starts like this: I have my CM rooted Aria that works a-ok as far as the network. Phone message memory getting full all the time and incoming texts bounce back, with no way of knowing who sent them. Can't have that, so I buy a stock L9.
Sim works. I want to have Wi-Fi calling, which is the *only* reason I bought the L9. Wi-fi calling is not working: call up T-Mo and they say I need to give a 911 address and all will be well. Ok, done.
Sim works. But no Wi-Fi calling still. Call up T-Mo and they say "Ohhh! you need a "3G-B" (I don't think that stands for gigabyte) sim card" Ohhh and what's your phone model etc etc. I tell them "it's a no-brand phone I got overseas," they don't need to know the model: they didn't with the CM Aria. They're clicking settings on their screen other side of the phone while we're talking: I can feel it.
Sim *stops* working. Need a working phone, so let L9 aside and get a stock T-mo S2. Same issue, cell network not connecting.
Let me show THEM! Ha! I'll unlock it. Unlocked the S2.
Sim still doesn't work.
Put the Sim back in the rooted/unlocked Aria? Network works.
What settings do they have in their stock phones that disallow network connectivity, because in the CyanogenMod Aria I have the phone fully works, GPS, tether, etc etc. In their stock-from-T-Mobile phones, network = nada.
Thank you for reading.
imadiamond said:
Hi!
Rooted with cmahendra's offline Lelus method (and to anyone who's done that, my hat is off to you).
**SHORT VERSION**
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/receive phone calls.
**DETAILED VERSION**
Starts like this: I have my CM rooted Aria that works a-ok as far as the network. Phone message memory getting full all the time and incoming texts bounce back, with no way of knowing who sent them. Can't have that, so I buy a stock L9.
Sim works. I want to have Wi-Fi calling, which is the *only* reason I bought the L9. Wi-fi calling is not working: call up T-Mo and they say I need to give a 911 address and all will be well. Ok, done.
Sim works. But no Wi-Fi calling still. Call up T-Mo and they say "Ohhh! you need a "3G-B" (I don't think that stands for gigabyte) sim card" Ohhh and what's your phone model etc etc. I tell them "it's a no-brand phone I got overseas," they don't need to know the model: they didn't with the CM Aria. They're clicking settings on their screen other side of the phone while we're talking: I can feel it.
Sim *stops* working. Need a working phone, so let L9 aside and get a stock T-mo S2. Same issue, cell network not connecting.
Let me show THEM! Ha! I'll unlock it. Unlocked the S2.
Sim still doesn't work.
Put the Sim back in the rooted/unlocked Aria? Network works.
What settings do they have in their stock phones that disallow network connectivity, because in the CyanogenMod Aria I have the phone fully works, GPS, tether, etc etc. In their stock-from-T-Mobile phones, network = nada.
Thank you for reading.
Sim goes into the L9. I get bars that show network availability, however I am not able to connect/make/recieve phone calls.
Click to expand...
Click to collapse
What the heck are you asking? I don't see any understandable questions in your message. I see you blowing off steam.
It does look like T-Mobile cooked your sim. You may need a new one.
Call them again and ask for "Customer Retention" through the automated system. Those people are more knowledgeable. A new sim should be free if they killed it.
Also, a data plan is not required for wifi-calling.
T-Mobile will give you a SIM regardless. They are always free.
I'm not sure as I am unrooted, but most carriers block network access via files in the EFS folder. This folder is VERY delicate. Anything improperly changed here can render a phone useless. If the SIM works in another device, it's not the SIM. Have you tried a different SIM in your phone?
Also, if you're blocked from network access, when you make a call, you should be prompted with, "We're sorry, but this device has been blocked from network access." If you do not get that prompt, then there is something wrong with the phone itself, be it software or hardware.
Looks like the L9 isn't registering in their system. Where did you buy the phone, blacklisted perhaps?
As for fried your sim, why does it still work in the Aria.
As for 3G-B, you probably need a newer sim, others call it a 4G sim... They should send you one free or pick one up free at a local tmo..
Thanks so far folks...
clockcycle said:
Looks like the L9 isn't registering in their system. Where did you buy the phone, blacklisted perhaps?
As for fried your sim, why does it still work in the Aria.
As for 3G-B, you probably need a newer sim, others call it a 4G sim... They should send you one free or pick one up free at a local tmo..
Click to expand...
Click to collapse
You hit the nail on the head exactly clockcycle, it's not registering. Something *in* the phone is not letting it connect, because my sim works successfully in any and every other unlocked phone I have, blackberrys, GMS world phones, the rooted Aria, but in the two "newer-released phones-- the L9 and the S2-- it doesn't work.
Phones are legit. Craigslist and brand new. Worked perfectly until calling T-Mobile for "support". The sim is fine and the goal is to keep it and not get a new one. It works.
My strong guess is that if I put a different rom that is *not* stock, the phone will work fine. It worked fine in the beginning, until I called them to address the wi-fi calling issue and they started poking around in my account, asking questions and clicking on things. I didn't want to address the wifi-calling issue too much because we could go off on a tangent.
You're right kevev, it didn't look like there was a 100% clear question. A lot of story though, to make sure there aren't 50 posts of did you do this and id you do that. A full story gives everyone the most info they need to understand the situation instead of "yo! my phone is not connecting!" which we see sometimes .
So the more clear question is:
"I am experiencing carrier settings *in* my L9 that are blocking me from connecting fully to the network on a perfectly fine sim card, how can I get around these settings and what/where are they."
I think tribalartgod understands what I'm getting at most completely. The inside-the-phone-settings. When the sim is in the phone I have bars, but when going to make a call the screen message is "emegency only". Can't try different sims in the L9 because of the need to cut the sim down. Also the L9 is not unlocked, just rooted. My guess is a de-bloatwared rom is the fix. Looking for answers from people more knowledgeable than me which is most likely all of you. Thanks again!
Craigslist, new, boxed, doesn't gurranty they aren't blacklisted.
BUT, the Aria uses a miniSim, the L9 uses a microSim. Did you cut your Sim yourself? It might be misaligned, cut wrong.
It's less than $2 to get it unlocked..
It sounds like its IMEI blocked dude. This can happen with various insurance or installment plan scams, even to brand new devices. There are options to still use the phone, but you are hosed on T-mobile. I have a blacklisted L9 because the previous owner quit paying his EIP, but it's unlocked so I used it on an AT&T MVNO connected to an AT&T MicroCell (I wanted WiFi calling too, but that won't happen with a blacklisted IMEI). Until you've gone to T-Mobile's chat support and ask the if the IMEI is clean, writing long posts in this thread is futile, and it is pretty clear everybody in this thread THINKS they know what they are talking about, but nobody has simply asked T-Mobile about the status of the IMEI, which takes two seconds.
I have a ST T-mobile SIM, data has been, and was working, up until last night. I haven't changed any APN settings up until then, or any other settings on the phone. Since data has stopped working, I've reset the APNs, tried custom settings for straight talk and t-mobile, everything else I could think of.
The weird part is, it SAYS I am connected to Tmo's data services. I see the H/3G icon, it tells me I am connected under settings>about phone. The only thing that happens, is I now get a notification telling me to "Sign Into Network". Clicking this takes me to a website, which loads, for t-mobile, telling me that my data plan does not work on this device. Obviously, if I can access a webpage, data is working, to some extent. I have only ever used in excess of 2gigs of data once, which was a few months ago, outside of that I usually use around 350-500 mbs a month. I can't imagine they'd be throttling my data now, and even if they were, it shouldn't be completely cut off.
Any ideas/suggestions? I've tried everything I could think of (even resorted to chatting with ST's customer service....You can imagine how that went...)
greencow said:
I have a ST T-mobile SIM, data has been, and was working, up until last night. I haven't changed any APN settings up until then, or any other settings on the phone. Since data has stopped working, I've reset the APNs, tried custom settings for straight talk and t-mobile, everything else I could think of.
The weird part is, it SAYS I am connected to Tmo's data services. I see the H/3G icon, it tells me I am connected under settings>about phone. The only thing that happens, is I now get a notification telling me to "Sign Into Network". Clicking this takes me to a website, which loads, for t-mobile, telling me that my data plan does not work on this device. Obviously, if I can access a webpage, data is working, to some extent. I have only ever used in excess of 2gigs of data once, which was a few months ago, outside of that I usually use around 350-500 mbs a month. I can't imagine they'd be throttling my data now, and even if they were, it shouldn't be completely cut off.
Any ideas/suggestions? I've tried everything I could think of (even resorted to chatting with ST's customer service....You can imagine how that went...)
Click to expand...
Click to collapse
Did you figure this out? Same thing happened to me, straight talk customer service was no help
No, still hasn't been resolved. Contacted ST twice now, just got off the phone with them today, they think it might be my SIM card, so they're sending me a new one. I'll update when I get it, whether or not it works.
Weird thing I've noticed is, when I click the "sign into network" notification, and the webpage starts to load, if I quickly go back to the home screen, and try something that requires data, it usually works, in the time that it takes the site to load. After that, nothing. I don't believe it's my SIM, honestly, I think something is up on Tmo's end, but I keep getting these lackeys at ST, and after the usual run around of restarting my phone and trying new APN settings, they do this.
I have this exact problem. Started when my billing cycle turned over on the 10th and my reserve kicked in.
ST T-Mobile Sim on Samsung Nexus S. Worked just fine for 3 months.
I've talked with ST Customer Service 3 times. And they could not help me. I chatted over 10 times and they all say the same thing. Change your APN settings, pull SIM, Reboot.
I've tried every APN setting, Wiped my phone to stock and nothing works.
The last time I talked with ST, I got them to re-provision my ST account. He guaranteed this would fix the issue. It did not. They won't call T-mobile and open a ticket without you being on another phone.
I think this is on the T-mobile side of things. For some reason my SIM's Data Plan isn't or didn't transfer over to t-mobile when the new billing cycle started.
I'm changing to diff carrier this weekend. ST can kiss it.
I contacted Straight Talk again. They called T-Mobile and was told everything was fine with my account. They told me to refer to my MFG.
I've bought a T-Mobile Pre-paid and put it in the phone(Nexus S) and data works fine.
I put my Straight Talk sim in my Galaxy S and it can't get data and takes me to T-Mobiles site for an upsell...
Straight Talk Customer Support is useless, and does not care. Their terms of use states they don't guarantee data, and told me to call corporate 1-800-876-5753, as they won't refund my money.
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
Carrier texts should theoretically still work as they are "data". It's the "voice" part of VoLTE that won't work. That's why I can still receive carrier texts on my Galaxy Note 9 with AT&T -- which still has older firmware (so I can be rooted). A few months ago, I lost the ability to make/receive phone calls on my AT&T number when 3G towers were decommissioned in my area... But luckily I have Google Voice number, which also uses "data" (VoIP) so I make/receive all my Google Voice phone calls. (That's been my main phone number for years.)
However, I no longer can make/receive AT&T phone number calls -- which is fine. I switched Google Voice settings to data/Wi-Fi only instead of piggy backing on carrier phone number. Yet, I still receive AT&T texts, which is good because my bank insists on using a "real" (carrier) phone number for SMS security code confirmation.
Amer28 said:
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Click to expand...
Click to collapse
You are in Portland? What carrier are you using that still has 2G and Edge?
ChazzMatt said:
You are in Portland? What carrier are you using that still has 2G and Edge?
Click to expand...
Click to collapse
I'm with a company that uses T-Mobile towers. I connect just fine with 4G LTE, and get reasonably good speeds over it. But when I'm on 4G, I cannot make or receive calls or text. It says Emergency Calls Only.
So far, I've tried everything. I resettled network. I looked for different APN values that may fix the issue. When I couldn't think of anything else, I did a factory reset. (I mean, I wiped Data, and all other partitions in TWRP except for System and SD Card.) There have been no changes.
I'm starting to think the issue may be hardware, I did drop the phone a couple of times the day it stopped working. Though I usually end up dropping the phone once a day or every two days. I can't believe the screen hasn't cracked yet, at all. Could a drop from 3-4 feet on hard surface like tiles damage the antenna in such a way that only 4G data works?
I'm ready to give up and buy a new phone even though I can't really afford it. It would be awesome if I can get this to work.
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
I want to also mention that my carrier website has been talking about a data migration that would affect phones using their old SIM Card.
When I saw that, I called them and had them send me a new SIM. I thought surely this must be it, but the new SIM works exactly like the old one.
Perhaps the migration or whatever it is they did that required new SIM cards just doesn't work well with my phone? Even though, before putting the order in, the rep I spoke to did check my IMEI and said that my phone is compatible.
Agreed, it doesn't sound like an IMEI issue.
FWIW, I showed a 4G connection on a phone (I don't remember if it was my V30 or a Galaxy S10+ that I was going to replace it with). On that phone, at one point, but there was no actual connection. So, the indicators aren't always accurate. That's why I thought maybe the data isn't really working, and if data isn't working then VOLTE won't work... and with many of the carriers switching off non-VOLTE calling, that could kill the ability to make calls?
In your case, you said data worked... but if VOLTE was never enabled, and the carrier dropped non-VOLTE, then, again, you may lose calling.
In any case, these were my theories. I think you're on top of the situation but I don't have any other ideas for you to try...
Instead of buying a new phone, have you considered installing and setting up Google Voice, as ChazzMatt said? I recently had to do that because AT&T's 3G shutdown meant that I could no longer place or receive calls. My quick guide on doing that is here: https://forum.xda-developers.com/t/...-based-custom-roms-when.4138223/post-87342453
I don't know why you can't also send or receive texts, but the Google Voice app has the ability to do that, so maybe try using that after you've set it up.
Amer28 said:
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
Click to expand...
Click to collapse
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
ChazzMatt said:
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
Click to expand...
Click to collapse
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Amer28 said:
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Click to expand...
Click to collapse
tried a rom on a j7 2015 because android 6 is going to be left and I only get emergency calls on lte and on 3g, no problem. It's not imei problem maybe exynos processor. I went back to 6.0.1 and no problem with 4g lite. By the way, I'm not in the USA.