Related
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.)
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
New to this, but I'll try to explain the best I can.
I've talked to tech support from my old carrier, my new carrier, and Samsung for about 15 hours total. I'm getting absolutely no where.
I purchased a Samsung Galaxy A20 from Spectrum mobile 3 months ago. I ended my service with them and switched to Red Pocket mobile when they had their black friday / cyber monday sim kit deal.
When I activated and ported my number over to Red Pocket I thought there was an issue with the number port.
But going back and forth with customer service they couldn't figure out what was wrong, as my account was activated and they confirmed that they now owned my phone number.
Eventually I realized my device was still locked with Spectrum. They provided me with an unlock code which did not work. They suggested using the unfreeze code which worked, my device said accepted/unlocked.
Phone works, can make calls and send text messages. However,I cannot access data.
My network operator still says Spectrum, and my Access Point name says charter (Spectrum's APN).
I cannot select the Add button, or the Reset to Default button in Access Point Names.
I took this to mean that my device was still locked since the unlock code did not work.
I thought the unfreeze code was specifically for if you attempt too many unlock codes and it locks you out of making more attempts.
That was my understanding, that the purpose of the unfreeze code is to enable you to make more attempts with the unlock code.
Again, I'm not really sure.
But regardless, Spectrum insists that despite it saying that my device is still locked according to their information, that the only way for it to say unlocked on their end is if i actually connect to my new provider, but that they have done everything on their end and that my device is unlocked and I should be able to connect to my new provider.
FUNNY right... in their records it says my device is still locked, but that that's not really accurate, and that it should be unlocked.
However, I have Red Pocket's SIM in my phone. And I can place and receive calls/texts. Spectrum and Red Pocket both use CDMA, so that makes sense to me. But since I am routing through Spectrum still, and I am unable to Add Red Pocket's Access Point Name in my phone, I cannot connect to Data / LTE.
From what I've explained here, do you all feel like my device is truly unlocked?
What is the best way for me to bypass this? How do I get my phone to switch from Spectrum's Access Point Name to Red Pocket's Access Point Name so that I can access Data/LTE ??
Thank you for taking the time to read my plight, and I appreciate any assistance anyone can give me with this.
I am not sure if attempting to root my phone or messing around with those kinds of settings will fix anything. I am not familiar with how to do that, but I will try anything at this point.
I have the A20 under MetroPCS still locked to their network. I can add APN's to it. So not sure why you are having this problem.
Medfordite said:
I have the A20 under MetroPCS still locked to their network. I can add APN's to it. So not sure why you are having this problem.
Click to expand...
Click to collapse
My thoughts exactly. Very strange why I am not able to add APNs.
I talked to a Samsung representative who suggested that it is probably either a software issue or the firmware installed by Spectrum.
When I told the Samsung representative that they assured me that my phone is unlocked (although I don't believe they even know what they're talking about since it is listed as locked in their system), he even went as far as to say that my device may be SIM unlocked, but they may have installed some sort of firmware on their phone that locks the Access Point Name to their server forcing the user to stay with them. Thus the phone will be able to take a new SIM, but it won't do the user any good since the firmware installed on the phone will not allow the user to connect to any other provider's Access Point.
I asked the Samsung representative if it was even legal for them to do that? He said it wouldn't surprise him as corporate giants such as Charter try to monopolize markets. He then went on to tell me that Charter took over as the internet provider in his area about a year ago and no longer has any other internet service providers in his area to choose from.
But again, I don't know if this is actually the case. But does anyone have any thoughts about what is going on or any suggestions as to what other things I can try to do to get connected to my new provider?
A quick update in case anyone in the future is wondering about my issue.
So after talking with another Spectrum customer service representative I have discovered that although my device was SIM unlocked over 2 weeks ago, my device is still carrier locked. They put an initial request for a carrier unlock over 2 weeks ago. Then after calling technical support a few days after that they had put in another request for the carrier unlock. A couple of days ago the representative I talked to went through all of the previous activity logs with my phone and discovered that the carrier unlock kept getting stuck on the end process of unlocking. He opened up another case for me (this will be the fifth ticket created for my account), but I expressed my concerns and doubts with him that it will accomplish anything.
I explained to him that if the issue can not be resolved on their end that I am pretty much out of luck. Since I have discovered on several forums that the Samsung A20 US version cannot be rooted, so there is no way to unlock the bootloader and install Samsung factory firmware to bypass the carrier locked APN on my own. I explained to him that if there was a way for me to do it I wouldn't even be calling, and I would have fixed the issue myself. However, since I am pretty much out of ideas to get my phone to work with my new carrier on my own and Spectrum can't seem to figure out how to carrier unlock my device even though they are LEGALLY REQUIRED to do so, that I am pretty much just about to give up and sell this device as a carrier locked phone on Swappa. He said yeah that's probably what I would do too at this point..
I said LOL, yeah but the problem there is I spent over $200 on this phone that I was only able to use for 2 months, and if I go that route I will likely only be able to get $50 for it.
He said yeah I can understand that that's frustrating, but I really don't see any other options you really have.
They also refuse to provide me with any sort of compensation even though clearly the mistake is on their end.
Bottom line.
NEVER BUY A PHONE FROM CHARTER / SPECTRUM.
Considering their business practices I would never buy phone service / internet service / any service they offer in the future, and would highly advise everyone else from ever purchasing anything from them in the future.
I'm pretty new to both rooting and this website, so I apologize in advance for any newbie mistakes I'm gonna make.
Background:
I have a VS-996 which frankensteined and unlocked by following this post . After doing that I flashed pie and then flashed lineage os from here . That rom wasn't very stable and kept crashing, so I tried others. I wound up going with Havoc OS. I believe it was in 3.4 when I first flashed it. I've kept up with the updates up to 3.7.
The Problems:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
What I've tried:
I've tried reinstalling the rom.
I've tried installing different Android 10 roms.
I've tried going through the process again starting at the the Frankenstein method and going from there.
I've tried messing with the apn
If I flash back to a stock pie ROM everything goes back to working perfectly, and I'm using my sim in my old V20 while I try to sort this out, so I know the SIM is not to blame.
I've been unable to find anybody else with this particular problem, though that could just be because the problems cover so many different aspects that I'm not sure exactly how to search for answers.
Any help is appreciated, thanks.
olliethehobo said:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
Click to expand...
Click to collapse
Are you Verizon customer? You say you have VS996.
There's an LOS ROM bug for Verizon SIM card users where upon rebooting the phone you have to make a phone call first to then receive texts. This phone call "registers" the SIM card or whatever. Many people call their voicemail number to satisfy this requirement.
This bug affects all LOS-based ROMs.
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
olliethehobo said:
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
Click to expand...
Click to collapse
Was noted extensively on LOS-16 ROMs, but not discussed as much with LOS-17 (Android 10) ROMs. But earlier this month someone in the Havoc 3.7 (LOS-17 based) thread did bring it up...
July 9, 2020
https://forum.xda-developers.com/lg-v30/development/rom-havoc-os-3-3-t4062657/page39
XxD34THxX said:
Would anyone happen to know a fix for the having to make a call on verizon to receive incoming calls/text messages-
It's the main thing preventing me from running any android 10 rom. Have an unlocked (True) US998
Click to expand...
Click to collapse
gimpy1 said:
I don't know of a fix, but, I always called my voice mail to get it to work. I haven't been on a custom room for a little while. I assume that still works, though.
Click to expand...
Click to collapse
However, the larger problem is in six months you will not be able to use LOS-based custom ROMs with V30 on Verizon.
* As of December 31, 2020 Verizon is dropping 3G CDMA to repurpose bandwidth for 5G.
After that date, to make any phone calls on Verizon you will need VoLTE. No LOS-based custom ROMs have VoLTE. You will need stock Verizon firmware. It can be rooted stock firmware; you can use Magisk modules to add features -- but needs to be Verizon firmware for VoLTE.
* T-mobile users are in the same predicament.
In January 2021, T-mobile will be dropping 3G HSPA for same reasons. T-mobile users will need VoLTE, which only comes with V30 stock firmware. However, T-mobile is less stingy. They also allow US998 firmware to have VoLTE and Wi-Fi calling with T-mobile SIM. Whereas Verizon requires Verizon stock firmware, and it needs to have been activated on a phone with Verizon IMEI at some point.
* AT&T will also eventually drop 3G HSPA -- but not until February 2022 (18 months from now).
So, for U.S. V30 owners who wish to run custom ROMs a little longer, you should check out AT&T Prepaid. It's a lot cheaper than "regular" AT&T, but is only for people who own their phones.
18 months is a long time. Anything can happen in 18 months!
AT&T only gives VoLTE to AT&T IMEI phones, as well as iPhones and some other phones I would never own. I've never used an AT&T branded phone on AT&T. I'm an AT&T customer with three native US998 for myself, my wife, my mother -- so I'll cross that bridge when I come to it in February 2022. Will probably give my mother an AT&T V35. Maybe my wife, too. Also, LG may get their act together and produce a good phone fro the LG V70 or LG V80.
Any Verizon, T-mobile (and Sprint), and AT&T MVNOs (Straight Talk, Ting, etc.) will also be affected by these decisions.
I have a more extensive discussion of this issue here:
All U.S. V30/V3O+/V30S will need stock firmware, not LOS-based custom ROMs. When?
https://forum.xda-developers.com/lg-v30/how-to/s-v30-v3o-v30s-stock-firmware-los-based-t4138223
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.