Related
SYMPTOM: can't see any mobile networks
BACKGROUND: I've been using htc one x for a month now. Initially on three, but their signal was unusable at home, so sim-unlocked and switched a couple of weeks ago to giffgaff ( a virtual network on top of the UK o2 network).
All has been fine, until today. I sent a few texts & calls in the morning, and mobile data was working. Since then, I can't see any mobile network.
wifi is fine.
Search Networks pops up "Error while searching for networks" and finds none.
No software changes of any sort since last successful call. No changes at all today, at least until I tried to diagnose the problem.
Running stock rom, with the WW update of a couple of weeks ago (1.28.771.9.CL56522 release-keys) -- neither S-OFF nor unlocked bootloader.
Nothing obvious to me in the normal or radio logcat logs.
The only thing I did after the last successful call was to run sensorly to try and map a trip. I've used this before without any problems. It got no connection but I thought nothing of that. I've since uninstalled it just in case it could somehow be interfering with the radio.
THINGS I'VE TRIED:
No, the airplane mode isn't on, and mobile is. I've toggled airplane from settings and power switch, many times
recreated the APN
checked other phones - yes there are a number of networks visible
tried the original o2 sim - same problem
safe mode
cold boot
reboot, reboot, reboot
obviously I haven't pulled the battery...
turned off wifi, in case it was somehow interfering
HTC diagnostic tool
factory reset
confirmed imei is not blocked
Any ideas? Bearing in mind that I'm looking for something which can happen spontaneously.
Interestingly, while writing this I've just noticed that Baseband version shows as Unknown. That worries me - is it possible that my radio partition has spontaneously corrupted itself?
I did speak to 02 support - they said to take it into a shop for warranty repair. I don't want to try a custom ROM just yet -- not when I might have to use the warranty. But is there any way to force it to reinstall the stock rom (preferably not involving windows)?
I have the same problem as well and flashing custom roms did not solve it for me. But for me even the IMEI number is shown as UNKNOWN...I haven't done anything special to get this issue, one day when I woke up the phone could not connect to any network.
I have tried a lot of different methods but with no success. I don't think we can do anything about the baseband without S-OFF.
If a hard reset fails, then it's time to think about returning the unit. Either get a refund or get it replaced.
This may be irrelevant; but I've had this happen to me on my GNexus. I solved it by going back to stock and it just fixed itself overnight.....
my HTC One X did the same after about 2 weeks. Gave it back to supplier, waiting my replacement.
Even tested with a different SIM card, did a hard reset. Problem stayed the same.
Im curious did any of you find a resolution to this? it happened to me a while ago but yet to fing a solution. HTC refuse to fix under warranty because it is unlocked.. i am currently waiting for the next official update to see if that fixes anything but the way things are looking that could be a while..
Hi
stout0_0 said:
Im curious did any of you find a resolution to this? it happened to me a while ago but yet to fing a solution. HTC refuse to fix under warranty because it is unlocked.. i am currently waiting for the next official update to see if that fixes anything but the way things are looking that could be a while..
Click to expand...
Click to collapse
It sounds like a fault, probably the radio chip has just stopped working, no software is going to repair that. If it was a software problem, there would be hundreds or thousands of people all having the same issue.
Regards
Phil
From time to time I cannot connect to mobile data, even though 3G shows above the signal triangle. A few solutions that randomly work are to toggle the radio from LTE/CDMA to CDMA only (and then back to LTE), toggle in and out of airplane mode, and the last resort of rebooting. The only method that works consistently is rebooting. Happened again today, and I noticed a few oddities on the phone status page in settings:
- Both IMEI and MEID were shown as "unknown"
- Phone number was visible
- Mobile status shows "connected"
- IP addresses (both IPV4/IPV6) were assigned
Prior to this (for the past 108 or so hours of uptime) all was fine, but in the midst of playing Words with Friends the signal bars grayed out and would not resume the connection. After several trials of my "solutions", I had to reboot. Sure enough, after reboot all was well again, and the IMEI and MEID were again displayed correctly in the phone status page.
As my signature shows, I am stock unrooted. While I have seen that a few individuals somehow wiped out their efs partition during a flash, that doesn't seem to be the case here since all of my info came back upon reboot.
Thoughts?
Sent from my Xoom using xda premium
Since you're completely stock, try exchanging for a referb with Verizon?
Will the next nexus have a longer screen?
I found that reseating the SIM card fixed my triangle (Roaming) issue. May be worth a shot.
I had this same issue. Sudden loss of service. IMEI: unknwon, Phone Number: unknown, etc...
I brought it to VZW to try a new sim. No go. They told be to call Samsung.
They verified that I actually had tried the idiot proof stuff, and confirmed its dead. Still under 1 year manufacturer's warranty. They're paying to mail it back and say they'll repair it, and send it back to me. Here's hoping they don't care that I've been flashing it like crazy for the past 5 months.
myriad46 said:
I had this same issue. Sudden loss of service. IMEI: unknwon, Phone Number: unknown, etc...
I brought it to VZW to try a new sim. No go. They told be to call Samsung.
They verified that I actually had tried the idiot proof stuff, and confirmed its dead. Still under 1 year manufacturer's warranty. They're paying to mail it back and say they'll repair it, and send it back to me. Here's hoping they don't care that I've been flashing it like crazy for the past 5 months.
Click to expand...
Click to collapse
Hard to say our problems are related. I am stock unrooted, and as stated in the OP only my IMEI and MEID were unknown. Also came back on reboot. Chances are you killed your efs partition during one of your flashing sessions.
Sent from my Xoom using xda premium
In the future, if anyones IMEI/MEID is perm-disabled due to whatever reason... my thread found here(Post #2) has info on repairing the Gnex MEID/ESN/IMEI.
This has happened to me recently. I've been flashing *safely* since the G1. Since Jelly Bean flasshing removed my network access. I went through a warranty repair and upon unlocking same problem. If my MEID or ESN is corrupt, I have not figured out how to repair it using Prime's instructions. That's a new world to me.
autoprime said:
In the future, if anyones IMEI/MEID is perm-disabled due to whatever reason... my thread found here(Post #2) has info on repairing the Gnex MEID/ESN/IMEI.
Click to expand...
Click to collapse
Autoprime, I did find that thread in my frenzied search to fix my phone. I downloaded the tool in post #2 but was confused how to get my phone connected as a COM port, or converserly, it would not recognize it when I changed the setting to USB. Do I need to put my phone in a particular mode, before that utility will recognize it? Do I have to go through the setup in Post #1 (ETS) prior to using the IMIE writing utility? Thanks.
myriad46 said:
Autoprime, I did find that thread in my frenzied search to fix my phone. I downloaded the tool in post #2 but was confused how to get my phone connected as a COM port, or converserly, it would not recognize it when I changed the setting to USB. Do I need to put my phone in a particular mode, before that utility will recognize it? Do I have to go through the setup in Post #1 (ETS) prior to using the IMIE writing utility? Thanks.
Click to expand...
Click to collapse
as u said in last sentence... you will have to go thru post 1 steps(only some of them!) to connect to meid tool.
since you guys are on a verizon gnex.. you would need to flash a Sprint rom in order to set the phone into diag mode. i believe most vzw roms have these options left out.. at least stock did.
2 things are required for a successful Ets Diag connection...
1. setting diag mode... this is the *#*#DIAG#*#* menu
2. setting Ets Channel mode to "USB" . This is done in the *#*#DATA#*#* > More > Ets Channel settings.
It MAY be possible to stick with the Verizon rom and use the Sprint Diagnostics App: http://forum.xda-developers.com/showthread.php?t=1774503
not sure if it works with VZW roms tho(im a sprint user).
The VIA Ets tool is the equivalent to messing with QPST/QXDM on Qualcomm phones. Just like Qualcomm phones have to be put into diag mode first before connecting to QPST, the Galaxy Nexus has to be set in the right mode as well.
autoprime said:
as u said in last sentence... you will have to go thru post 1 steps(only some of them!) to connect to meid tool.
since you guys are on a verizon gnex.. you would need to flash a Sprint rom in order to set the phone into diag mode. i believe most vzw roms have these options left out.. at least stock did.
2 things are required for a successful Ets Diag connection...
1. setting diag mode... this is the *#*#DIAG#*#* menu
2. setting Ets Channel mode to "USB" . This is done in the *#*#DATA#*#* > More > Ets Channel settings.
It MAY be possible to stick with the Verizon rom and use the Sprint Diagnostics App: http://forum.xda-developers.com/showthread.php?t=1774503
not sure if it works with VZW roms tho(im a sprint user).
The VIA Ets tool is the equivalent to messing with QPST/QXDM on Qualcomm phones. Just like Qualcomm phones have to be put into diag mode first before connecting to QPST, the Galaxy Nexus has to be set in the right mode as well.
Click to expand...
Click to collapse
Thanks very much for laying that out. Is this something that "just happens"? It seems like (over several months) I flashed 50 - 60 times, radio a few times, changed from CWM to TWRP with no problems and then in the middle of the day, I just lose signal.
Could it be a hardware issue? I read somewhere that a modem in a phone got fried and caused the same thing.
myriad46 said:
Thanks very much for laying that out. Is this something that "just happens"? It seems like (over several months) I flashed 50 - 60 times, radio a few times, changed from CWM to TWRP with no problems and then in the middle of the day, I just lose signal.
Could it be a hardware issue? I read somewhere that a modem in a phone got fried and caused the same thing.
Click to expand...
Click to collapse
i mean.. in my experience it comes with messing with the phone.. the EFS etc. could be from a bad flash.. but yes it could be hardware... or theres even a small chance its just random. youd have to look at the factors leading up to the issue for the best guess.
overall tho.. outside of messing with the efs/NV.. its kinda weird for it just just to happen.. id consider that very rare.
UPDATE: sent back to Samsung. They replace the main board under warranty. Works like a charm now.
Sent from my Galaxy Nexus using Tapatalk 2
Missing MEID/IMEI no service but internet is working.
I've been searching high and low and have came across various forums that are related to my problem but I'm still not sure if its the problem I have
or what to do exactly. I have a Samsung Galaxy Nexus with VZW, rooted, running a custom ROM (CM10), Android version 4.1.2 JZO54K. My
service got disconnected and when I paid to get it reconnected I get an empty signal triangle and sometimes an R above it (roaming). My internet
works oddly enough but I'm unable to receive/make calls or text messages. My status reflects; Network: searching for service; Service state: out of
service; Mobile network state: disconnected; MEID: unknown; IMEI: unknown. Before my phone was disconnected it was working fine, please
help!!!
If you did some backups time to time and if you have backup of data folder, inside of data folder you should have folder radio. Inside the radio folder should have data.bin file and data.md5. In my case they was original data files of my phone and after their copy to factory folder ot restore my IMEI.
I hope that helps.
Sent from my Galaxy Nexus using xda app-developers app
Yeah unfortunately I never did... any other suggestions??? Or am I at a lost???
Sent from my Galaxy Nexus using xda app-developers app
Howdy,
About 3 weeks ago, I bought two refurbished SGH-M919 phones off eBay to replace mine and my wife's broken/old phones. Her phone was worse off, so the first one I set up was to be hers. Rooted, installed TWRP, and flashed Mokee with no issues. Put her SIM in, put her data back on, she's good to go.
I go to set the next one up for myself, do everything the exact same way, and came to realize after I put my SIM in that the phone is not connecting to LTE. Call/SMS/Wifi all work fine. I didn't notice whether or not it was doing this before rooting, recovery, and ROM.
It's giving me a "Sign-in to network" notification. I tap it, it takes me to a T-Mobile ConnectMe screen. It gives me a "Get Started" button, which I tap, and it says "We're sorry, you have switched your SIM card between different devices, so you will need to manage your account through My T-Mobile or the MyAccount app. Once you have replaced the original SIM card, you may resume managing your account through on-device account maintenance." I can only tap close. My wife's phone didn't give me this "error". I made sure the APN settings were identical between the phones, they were.
I called T-Mobile, they gave me a bit of runaround, said everything looked fine from their end, and "rebooted the connection" which didn't improve anything. They also had me verify my APN settings with them. They had me enter some different values, but it didn't change anything. They also advised me against purchasing phones from less than reputable sources. Great, thanks, that was helpful.
I switched the SIM cards between the two phones and this one is still not connecting to LTE, the other phone is. This led me to think maybe it was a hardware issue, and looked into the modem as a possibility. I found that T-Mobile updated the baseband last month on the stock 4.4.4 ROM, so I flashed that baseband and no change. Both phones were on NH7 when I received them.
I happened to notice on my T-Mobile account page that the device status is listed as "locked/unknown." So, I called T-Mobile twice today for an unlock code. The first guy was less than helpful but the second person did enter an unlock request for me, theoretically, I am currently waiting for that email to show up sometime in the next 24 hrs. But, the phone so far has not given me an unlock prompt so I'm not quite sure what I'm going to do with that unlock code once I get it. I'm also not 100% clear on whether the code is for a SIM unlock (which I shouldn't need) or what exactly. It is just the next in a series of ideas which I'm rapidly running out of. A check of the IMEI number revealed it was clean on all US carriers, with the exception of T-Mobile and Sprint which both come up as "unknown." Don't know if that means anything or not.
I'm getting ready to jam this eBay store up, but I'd really rather the phone just start working. I've been dinking with this for weeks and my frustration is mounting, especially since I can't seem to find anyone else who has had/posted about this problem before. I'm not a cell phone hobbyist or anything, and I'm just going off what I can find on Google and places like this. Any ideas/help would be appreciated.
Thanks,
Tony
I am not familiar with the issue, just some extra troubleshooting ideas...
Have you checked under the battery and confirmed the model number is SGH-M919 and the IMEI matches matches what is on the phone?
Have you checked your APN settings?
Have you tried flashing a complete full stock firmware -
http://forum.xda-developers.com/showthread.php?p=64431358
lumin30 said:
I am not familiar with the issue, just some extra troubleshooting ideas...
Have you checked under the battery and confirmed the model number is SGH-M919 and the IMEI matches matches what is on the phone?
Have you checked your APN settings?
Have you tried flashing a complete full stock firmware -
http://forum.xda-developers.com/showthread.php?p=64431358
Click to expand...
Click to collapse
IMEI under the battery matches what comes up with *#06#.
I did check on the APN settings, forgot to mention that. I edited it into the first post, added text in red:
dauntless89 said:
It's giving me a "Sign-in to network" notification. I tap it, it takes me to a T-Mobile ConnectMe screen. It gives me a "Get Started" button, which I tap, and it says "We're sorry, you have switched your SIM card between different devices, so you will need to manage your account through My T-Mobile or the MyAccount app. Once you have replaced the original SIM card, you may resume managing your account through on-device account maintenance." I can only tap close. My wife's phone didn't give me this "error". I made sure the APN settings were identical between the phones, they were.
I called T-Mobile, they gave me a bit of runaround, said everything looked fine from their end, and "rebooted the connection" which didn't improve anything. They also had me verify my APN settings with them. They had me enter some different values, but it didn't change anything. They also advised me against purchasing phones from less than reputable sources. Great, thanks, that was helpful.
Click to expand...
Click to collapse
I didn't flash a full stock firmware. I had issues flashing the non-hlos.bin to the phone, which as I understand it is the more important of the two files for my issue since it does the LTE. However, Wifi works perfect with transfer rates equal to the other phone. So, I don't know.
I'm downloading OK3 now. I read about a guy updating his modem by backing up his custom ROM, flashing a stock rom, and restoring his custom ROM. Will TWRP back up my current NH7 non-hlos.bin? If so, can I manually remove it from the recovery image without borking anything?
For your situation, just flash the full firmware. Don't remove anything from the tar. OK3 is the newest modem. Get your phone working and go from there.
Yeah, I think I'll do that when I get home, unless someone has a better idea. :fingers-crossed:
dauntless89 said:
Yeah, I think I'll do that when I get home, unless someone has a better idea. :fingers-crossed:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3276231
Try to flash the latest stock... Before flashing reset your device (take data/photo etc backup).... Hope that should resolve the issue....
Also what is it showing in settings > network? Is it LTE or 2G or 3G???
Sent from my SGH-M919 using Tapatalk
Thanks, that's the one I'm downloading and I'll try flashing it when I get home. It looks like it will replace TWRP and everything, bringing the phone completely back to stock?
In the mobile network settings > mobile network menu, it shows the preferred network as LTE.
Yes. It will be completely stock. If it works, you can then root and put TWRP on and go from there.
Alright, flashed the afore-linked OH3 ROM and the LTE is still broken. The phone shows up as connected to LTE, but nothing works. Play Store times out, both stock internet browsers time out. I still get the same T-Mobile nag that I got before and it still doesn't let me do anything.
Also got the unlock email from T-Mobile:
[FONT="]Thank you for taking the time to contact T-Mobile. We have received your SIM Unlock Request. Unfortunately, we are unable to process your request at this time because we are only able to provide unlock codes for T-Mobile USA handsets. Please refer your unlock request for this equipment directly to the carrier that the handset was purchased from.[/FONT]
Click to expand...
Click to collapse
Is there anything left to troubleshoot, or do I return it as defective?
If data works for your sim card in your wife's phone and not for your sim card in your phone, it would have to be a phone issue. You can double check if data works with your wife's sim card in your phone.
If your APN settings match your wife's phone with her data working, the last thing I can think of to try is go to Settings, under Connections go to More networks > Mobile networks and check Data roaming just in case your phone is roaming for whatever reason.
If your phone was locked on a different carrier, I don't think you would have cell service. If your IMEI was blacklisted or borked, I don't think you would have cell service.
I'd return the phone.
lumin30 said:
If data works for your sim card in your wife's phone and not for your sim card in your phone, it would have to be a phone issue. You can double check if data works with your wife's sim card in your phone.
If your APN settings match your wife's phone with her data working, the last thing I can think of to try is go to Settings, under Connections go to More networks > Mobile networks and check Data roaming just in case your phone is roaming for whatever reason.
If your phone was locked on a different carrier, I don't think you would have cell service. If your IMEI was blacklisted or borked, I don't think you would have cell service.
I'd return the phone.
Click to expand...
Click to collapse
I will check on those two things when I get home, but my thought process was similar to yours. Both my wife's new phone and the LTE Wifi hotspot we use for our internet service have full signal on LTE everywhere in the house, so my best guess at this point is there's a hardware issue with the modem in the phone. I might look into replacing whatever board the modem is on. If it's relatively cheap, I'd rather just pay for the part instead of waiting 2-3 weeks for turnaround on the return/exchange, but I think that's probably what we're gonna end up doing.
Thanks for the help, fellas. I appreciate it.
I had 4G before this update, but nothing I do, no matter how many different APN settings I try, no dice.
I'll tell you where I've been. Have had the phone at least a year and it came with Nougat.
As soon as I got it, I got a Total Wireless SIM (owned by Tracfone and running on Verizon's network) and activated it with no problems. Had full service. 4g, mms, etc. All was great.
Even when I got the 8.0 notification and I updated to Oreo, all worked fine.
A few months back, I got the 8.1 notification. I allowed it to install and when It booted back up, I had no service at all.
Found this thread, Android 8-1 - How to Edit Cellular APN, and one post in there got me with the phone setup and connected to my computer running ADB commands, which allowed me to at least add an APN.
Adding the standard TRACFONE.VZWENTP apn you can easily find via Google searching fixed the problem. (Had to add mms port of 80 but otherwise, all was perfect)
About a week back I get the 8.1 notification again, which i thought was weird since I was already running 8.1
Turns out it was the April Security Patch for 8.1 (i suppose as that's the only reasoning that makes sense to me right now).
After it installed and did it's thing, I only had 3G service, which around here is prone to many interruptions, aside from the slow speed.
I checked, and it's still using the APN I set up. Nothing has changed on that APN, nor anywhere else I can see.
I even added a new one with the same data, and same thing, 3G.
I've searched the threads here, tried some of the other suggestions but none have worked.
I've even went as far as to get Smail to unlock my bootloader (it's a verizon Pixel XL) and from there I've rooted installed twrp and rooted etc, all in hopes that I could try another method listed in that thread i linked above, using an adb shell with root permissions to view the "default" apn data, thinking maybe something in there is messing it all up.
I had no luck there because even though the phone is rooted now, there was something else I have to do to run an adb shell with root permission and seems the easiest way to get that done is just install a custom rom.
Still, what baffles me is, isn't this what the SIM card is partly for?
And why would software updates disable service, or parts of service?
Seems odd that a software upgrade would effect how the phone uses the service, especially when a custom apn is setup and unchanged.
I have scanned these forums for hours over the past few days and I would really love some direction on what to try next.
Any ideas are appreciated. Thanks!
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
DR3W5K1 said:
Play around in the *#*#4636#*#* dialer menu just don't hit the update button beside the smsc input field
Click to expand...
Click to collapse
Oh wow, never knew about this. Brought up all kinds of options. Will mess around and see if I can find something useful.
acters said:
Sometimes, the best thing to do is to go to total wireless and ***** at them till they deal with it. I don't think its something you need to stress over. It's Verizon's and Total Wireless's responsibility to get your 4g LTE back. I just dealt with T-Mobile with the same issue. no 4G but call and texting worked. APN set right but they did something on their side and got me back on track after handing them my phone.(in store)
Click to expand...
Click to collapse
I would but Total Wireless doesn't have a store front or even a kiosk. They're kinda like Straight Talk, but just for Verizon phones. Verizon naturally won't have anything to do with it since I'm paying their competition to use their network.
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was, and it has been until this update.
I've considered flashing 8.0 and see if that lets it work again, but I don't like the thought of not being to update my phone or i'll lose parts of my service.
Thanks for the suggestions yall. Will repost if the dialer code leads me somewhere helpful.
kamikazeedriver said:
I had thought about going through the activation again, but when i put my IMEI # on their website now, it says my phone is not compatible. A year ago it said it was...
Click to expand...
Click to collapse
Oh my, can you confirm if your IMEI is the same one as the one as last year?
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
DR3W5K1 said:
They are probably getting money hungry and want people to buy phones from them. There is a big chance that hidden menu could solve your problem though. Regarding the imei the only way that could be a problem is if yours was somehow stolen
Click to expand...
Click to collapse
I think it shows up as an issue because I'm currently using it. I just tried it again and it said "there was an error." When I tried it a few days ago it had said the same, "there was an error, contact customer support"
It's possible that time it showed up as incompatible i had punched a number in wrong.
Can't confirm if it's the same IMEI i had a year ago but it would be weird if that changed.
Couldn't find anything in the hidden menu except when I checked "Carrier Provisioning Info" showed up that it last attempted it yesterday and had failed.
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
DR3W5K1 said:
Well as a last ditch .. just a thought here. Pull the sim power on your phone delete the apn. Perform a reboot insert sim and wait. Still nothing? Check apn add if necessary and reboot. Profit?
Click to expand...
Click to collapse
I did try that after the april update.
With no APN, I get no service, which first happened right after the first 8.1 update. That lead me to adding the APN.
I haven't tried it since I've unlocked the bootloader.
I will try again before flashing back to 8.0.
8.0 was the last time my phone worked just fine with no custom APNs or anything.
I thank y'all for the ideas.
I would like to know if I'm the only one with this specific problem.
Is anyone else experiencing this issue with the 8.1 updates using a Verizon MVNO?
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
DR3W5K1 said:
For future reference that provisional menu will be populated with answers other than no. If you have the proper apn etc..
Click to expand...
Click to collapse
Want me to take a screenshot of the provisional menu? I don't know what I'm looking for in that menu.
As far as APN, it never needed to make one until the first 8.1 update but all worked fine afterwards. It's only since the April update that I have issues.
Will report back after trying to reset without the sim again
If a fresh image+apn doesn't fix it the only other thing that "you” could try would be replacing the Sim. Sometimes the Sim can fry. Could also be as easy as reseating it.
It's fixed
Here's what I had to do.
I did a wipe install (flash all.bat) of an 8.0 Oreo image as it was the last time I had LTE without even having to do anything (like setup a custom APN etc)
After that was successful, I did a no-wipe install of the 8.1 (April 2018) image, and afterwards, and once it was booted, all was well, I have LTE and everything with no custom APNs needed.
Thanks to everyone who offered help in getting me in the right direction.
In addition to what I previously mentioned that I had tried, I also tried:
-I did try a wipe install of 8.1 a few days ago but still with no success. Even with tweaking APN settings.
-I messed around with the carrier provisioning menu and could see I was not getting LTE and when I told the phone LTE only, then no service at all, so I set it back to LTE/CDMA/UMTS (that's what it was already on.)
-Tried dialer code *228 to "activate" my service, but that had no change.
I went back, this morning, to the thread I first looked at after the first 8.1 update I had which disrupted my service completely and ended up with me using an adb shell to do something that allowed me to add APNs and subsequently setup an APN that worked for me until the 8.1 April security update.
Noticed this post:
ThePhoneGeek said:
I have this same issue and the only solution I've found is to full wipe go back to 8.0 activate on Verizon's network (I too use a VZN MVNO) and then flash the full 8.1 package without wipe.
Click to expand...
Click to collapse
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
kamikazeedriver said:
Noticed this post:
I can't say I understand why that worked when a completely fresh wiped install of 8.1 didn't, but it did so I'll take it.
The next thing I was going to try, if it hadn't worked, was changing the radio band in the provisioning menu as that seemed to work for another person.
Either way, all is well for now. Thanks for all the advice!
Click to expand...
Click to collapse
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
ThePhoneGeek said:
The only thing I've come up with is that starting on 8.1 flashing full wipe for VZN users (or perhaps limited to VZN MVNO's) with unlocked bootloaders is not allowing the device to activate on the network. I suspect VZN hanky panky at work but I am generally a skeptic that way. Once you get it the way you want it you can update each month with the full firmware but remove the -w in the flash-all.bat file and you should be good.
Click to expand...
Click to collapse
My bootloader was still locked when these issues began with the first 8.1 update (which adding an APN fixed), and culminated in 3G only after the 8.1 April update.
I only unlocked it so I could hopefully find a solution, which thankfully was a success.
I'm just as skeptic as you are when it comes to VZN though. They have the best coverage in this area, and that's the only positive thing I have to say about them.
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE