Hello guys. I have an a Verizon S7 currently being used on Metro PCS. I'm still running 6.0.1 Marshmallow and hoping I wouldn't have to do any software updates until a few days ago. I suddenly began getting a "sim card error" when I tried dialing out. I took out sim card, popped it back in and same issue. I even checked the sim and tray for any damage and there is none. Also, the phone has never been exposed to any liquid at all. I tried a soft reset, still same issue. Tried clearing cache in recovery, same issue still. Finally did a full wipe, set up as a new phone without doing the 7.0 update. That hasn't cleared the issue. I still can't dial out, HOWEVER people can still call me and the calls go through normally. I can also send texts. This isn't happening only in low signal areas as I initially thought. I'll have full bars in some places and not be able to call out. I don't really want the 7.0 update since I like the way my phone is now on MM. Are there any other options for me at this point? I did some research and it looks like people are relating this to a software issue which would mean I'd have to take the plunge into Nougat...
Unless anyone here can offer an alternative? :fingers-crossed:
As an added bonus, does anyone know if my mobile network settings (GSM/CDMA, GSM, UTS, etc) have something to do with this? Thank you for any suggestions!
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
Sorry for late reply. What's AP?
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
By the way I ended up taking my sim card out and put it back in. It worked fine. Just yesterday it did the sim error again so it reminded me of this thread
Try going into b recovery mode and wipe cache. I did that &it fixed my calling.
Related
I'm am so frustrated. Lol, I called verizon today and sat on the line waiting for what seemed like forever and after talking to someone I finally got transferred to "technical support." Well, lucky for me my home phone decided to die (about an hour after I pulled it off the charger to call them) and am now waiting to speak to another representative where I can once again be transferred to verizon's technical support. The reason I called them is because I get no mobile data. When I first got the phone it worked some of the time, but now I get nothing. Calls and texts come through fine, but after toggling mobile data, airplane mode, pulling the sim, restarting the phone, and numerous other things like clearing cache I still get nothing. The phone is stock and not rooted. The 4g lte logo shows at the top of the phone and everything, it even shows a little down arrow as if it's trying to get data, but nothing is coming through. Is there a good chance it's a bad sim or should I just go ahead and factory restore the device? I'll try putting the sim in my galaxy s3 and see if it works, but this sure has been a frustrating night.
Edit:I'm thinking it's the sim as mobile data does not work on my s3 either. I still have the sim from my galaxy s3, anyway I can set that up to work with my galaxy s5, or will some functionality be missing?
Just go into a vzw store and they will give you a new Sim card
Sent from my SM-G900V using Tapatalk
kingsley404 said:
Just go into a vzw store and they will give you a new Sim card
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Hey, it might be a problem with the sim / a problem on Verizon's end. But did you Odin a stock rom recently?
NotDavid said:
Hey, it might be a problem with the sim / a problem on Verizon's end. But did you Odin a stock rom recently?
Click to expand...
Click to collapse
yeah, looks like a problem on verizon's in. I got a new sim card and it still quits working at random times.
I'm running Clark stock 6.0 build MPH24.49-18/unlocked/rooted/xposed on Verizon. Build is fine, was fastboot installed direct from Moto's firmware package back in September and has been running flawlessly. All of a sudden I'm not able to receive any MMS messages. My primary SMS app is Signal so I tried Google Messenger and the stock messenger app and all of them are failing to download any MMS. This just started happening a couple weeks ago. I'm not convinced that this is a rom or any customization that I may have done issue, I think it's purely something with Verizon or maybe an APN issue? It's just weird that this just started happening out of the blue. Before I contact Verizon I figured I'd ask here if anyone has come across this.
I'm on Verizon n no problems.
annoyingduck said:
I'm running Clark stock 6.0 build MPH24.49-18/unlocked/rooted/xposed on Verizon. Build is fine, was fastboot installed direct from Moto's firmware package back in September and has been running flawlessly. All of a sudden I'm not able to receive any MMS messages. My primary SMS app is Signal so I tried Google Messenger and the stock messenger app and all of them are failing to download any MMS. This just started happening a couple weeks ago. I'm not convinced that this is a rom or any customization that I may have done issue, I think it's purely something with Verizon or maybe an APN issue? It's just weird that this just started happening out of the blue. Before I contact Verizon I figured I'd ask here if anyone has come across this.
Click to expand...
Click to collapse
Had this happen once about a year ago on the stock rom too. I hadn't made any major changes and the phone stopped receiving MMS. It had been working fine for at least a month prior. On AT&Ts network for me.
Restoring a nandroid backup fixed it, but I never did actually figure out what went wrong.
jason2678 said:
Had this happen once about a year ago on the stock rom too. I hadn't made any major changes and the phone stopped receiving MMS. It had been working fine for at least a month prior. On AT&Ts network for me.
Restoring a nandroid backup fixed it, but I never did actually figure out what went wrong.
Click to expand...
Click to collapse
So the backup restore fixed it...? So strange. Now I must figure out what is causing this.
Sent from my XT1575 using Tapatalk
annoyingduck said:
So the backup restore fixed it...? So strange. Now I must figure out what is causing this.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I was rooted with a custom kernel, but had been for weeks with no problems. Then mms just quit working.
Didn't do much troubleshooting, sorry. Restoring the backup fixed it and it's never happened again. Could be a coincidence, but sounds just like what you described.
I've had this happen a few times, a power off reboot usually fixes it. Verizon, true pure x. I've been to stubborn to reload to see if it fixes it permanently.
SOLVED
The issue is with the APN settings. 2 Lines were incorrect:
-MMS Port was set to "not set", it needed to be "80"
-APN Type was set to "default,dun,supl", it needed to be "default,dun,supl,mms"
Very strange that these configurations magically changed themselves. What's even funnier is that Verizon customer service told me that the issue is that it's a non-Verizon phone and the only thing they could recommend was a factory reset and/or a new sim card. They also would not give me the correct APN's, they said some nonsense about that information being unavailable to them. So Google fixed this issue for me. FU Verizon.
I have had mixed luck with different APN settings. The above worked for me for a while, and then inexplicably stopped. I tried a bunch of different configurations before sticking with the settings in the attached screenshot. These settings worked for me on Marshmallow and continue to work on Nougat (7.1.1). These are also the settings that appear after resetting my network settings from the Mobile Networks menu. I hope this can help someone out.
Phone is stock and not rooted.
This is extremely strange. I'm on Vodafone in the UK and I had installed the 7.0.1 update a few days ago. All was running fine.
Anyway, the Play Store issue had me confused, so instead of uninstalling updates, I decided to hard reset.
Did that and from that moment on the Sim card seems to have gone into a fit of turning itself off and on every 1-2 seconds.
I have reset a number of times and have now installed the 7.1.1 update, along with a hard reset and nothing has changed.
I have tried an EE Sim in the phone and this works fine. My voda sim I put in a Galaxy S 7 and that seemed fine too.
Yet when it is put back into my phone, it goes mad.
I only run one sim and have tried with SD Card in/out.
I am tempted to call it a faulty sim and go and get a new one, but thought I'd check here first.
Any experiences or ideas?
TIA
The plot thickens...a bit.
When I insert 2 vodafone sims, it works fine. Both sims are stable and I can make/receive calls as per normal.
As soon as I remove the one of the sims, it carries on as per usual constantly activating and deactivating sim.
Some more info...
Upon a hard reset the sim is stable and I can see data connection. I follow through the initial startup screen and skip as much as I can skip. Again, remains stable.
The last screen I get to is IZ location or something (can't remember) and asks whether you want to enable for h/w acceleration. I have tried this both on and off.
As soon as you click finish and it goes to the home screen for the first time, the sim immediately begins to fluctuate showing both signal bars empty, then one, then one with signal, then repeat.
Viewing from the dual sim settings page, you can see the sim activate, say it's vodafone, the disable as if it had been removed.
About as strange as it gets!!
Right, resolution in the hope that it helps someone else
After trying every conceivable way to sort this, it was time to downgrade.
Went back to B10 package from the German site:
http://www.ztemobile.de/support/downloads/?product_id=2100
Will install everything and upgrade to Nougat again...possibly!
Yep, just been through the exact same thing. I had to go back to b10, whatever you do don't factory reset in-between updates back to 7.1.1.
Don't do anything in fact, just upgrade.
I ended up losing my great battery life because of this, I wish I'd left alone.
Good luck.
Mike
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Ranny99 said:
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
I was trying to look for discrepancies between the B10 6.0.1 and the 7.0.1 but there were too many.
I'm quite tentative about moving off MM to nougat after the shenanigans the other day.
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Looloup said:
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Click to expand...
Click to collapse
I tried multiple vodafone sims and had the same problem. Like you both Voda sims worked fine in other phones.
I would have gone the local Voda store, but they were...let's say 'challenging' to say the very least!
Good to know that other providers are affected too
You have this problem because you most likely have unlocked your bootloader. ZTE know about this problem, the only way to solve this is to go back to marshmallow, lock your bootloader then go back to the nougat build.
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked.
I flashed several different images to no avail.
Advice?
locolbd said:
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked. I flashed several different images to no avail. Advice?
Click to expand...
Click to collapse
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
v12xke said:
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
Click to expand...
Click to collapse
Tried it all.
I installed several full factory image versions, locked the boot-loader and then started up the phone. With the boot-loader locked and phone not rooted Android Pay still gave me the error that my phone is running a custom ROM, the boot-loader is unlocked or the phone is rooted.
I have also installed several OTA images and none of the problems I mentioned in my earlier post went away. The only way for me to get Android pay to work is to unlock the boot-loader and root the phone with magisk. However, I still get intermittent Roaming notifications, intermittent signal lost and no LTE whatsoever.
Today:
I called Google and and did 45mins of troubleshooting, the final thing we did was reset my phone and then the agent acted helpless when nothing resolved the issue.
I called Verizon did 30 minutes of troubleshooting with them, reset network setting about 100 times, turned off my phone so that they could re-provision on their end. Turned the phone on and got LTE signal for approximately 60seconds. Then it went back to 3G, then no signal and then the dreadful roaming notification every few minutes.
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
mojorisin7178 said:
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
Click to expand...
Click to collapse
I wiped DATA so there were no files on my phone.
Downloaded july,august,september factory images and flashed, locked bootloader and tested each image to no avail. I saw the build on the google forum for 019 so i flashed that as well and same sh:silly:t different day.
Last thing I did was to flash 7.1.1 and that did not resolved my problems. Got the OTA notification to install 8.0 hoping all my problems might disappear but they did not.
It has been an hour and LTE seems to be working again
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Wow that is odd. The one thing I have noticed with 8.0 on my 6p on fi is sometimes I lose data when I'm out and the phone loses wifi and switches back to lte. I have to reset the phone to get lte back.
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Just my 2 centers here for anyone else in this quagmire...
I had same issue. I've got a Nexus 6p on which I dirty flashed an 8.1 update of ABC Rom over an earlier 8.1 version of ABC Rom. After that, the issues began. At boot, I'd be on 3g and if I toggled airplane mode off and then on, I could get LTE for about 10 seconds. However, it would then drop back to 3g. I tried everything, as is stated above: revert to stock, older radio images, different SIM... nothing worked. I read about people manually configuring their APNs. However, I've got a Verizon SIM, so that option was gone.
Anyway, after reading this post, I got the idea that I might be able to mimic the solution without buying a Project Fi SIM that I don't want.
Here's what I did:
Open the Phone's Testing Settings by dialing: *#*#4636#*#*
Tap "Phone Information"
Scroll down and set the "VoLTE Provisioned" toggle to the "on" position.
Then, toggle airplane mode on and off.
Profit!
I'm not sure if this solution has any parallels to the solution that uses a project Fi SIM for a brief moment. However, I speculate that it may.
At any rate, I hope this helps someone else with this issue.
UPDATE:
It turns out this method is more of a work around at best. At first I noticed that I had to toggle airplane mode once after a reboot. That didn't seem too difficult. However, I then discovered that I could no longer make calls. Switching the VoLTE Provisioned toggle back off fixes the calling issue, but puts me back on 3G.
Uggg.
locolbd said:
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Click to expand...
Click to collapse
Hey is ur 6p still running well with LTE? I did that with a att SIM card and my 6p read as a att SIM so I then put my Verizon Sim back in and it read Verizon LTE but then after like half an hour it changed back to roaming and 3g. I went to Verizon to get a new sim card but that didn't do any help at all. I would like ur feedback if possible. Thank you
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
j2t0621 said:
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Click to expand...
Click to collapse
Hey is the 6p still working well for you? LTE? I been following ur steps but I don't have project fi and I used my friends att SIM to kinda reset the network and I also reset the network too but it went back to 3g and roaming. Any help would be awesome. I don't want to have to get a new phone
Sent from my [device_name] using XDA-Developers Legacy app
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
j2t0621 said:
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
Click to expand...
Click to collapse
Tea I bought a new battery on eBay for 10 and got it replaced and it's running awesome. Are you on a custom rom? Just wondering what else I can try to fix this. It's weird while on the att it worked fine with LTE. I'm thinking about getting a fi acct thought
Sent from my [device_name] using XDA-Developers Legacy app
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
k1ll3ry0 said:
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
Click to expand...
Click to collapse
I will give this a try this evening
Sent from my [device_name] using XDA-Developers Legacy app
bleh im back to stock unrooted and locked and my signal is still crap. i guess i have to buy a new phone.... =*( i loved this 6P
Sorry to hear that. I'm just running stock android.
My phone worked perfectly for an entire year, I even rooted and switched roms often, but now I'm facing this issue where my mobile data doesn't work anymore.
Tried switching rom but the issue is still there, done a clean flash and formatted cache etc etc, but the issue never goes away.
I tried changing sim but no result, used my sim in another phone and it works.
Do you have any idea what it might be?
DLVittorio said:
My phone worked perfectly for an entire year, I even rooted and switched roms often, but now I'm facing this issue where my mobile data doesn't work anymore.
Tried switching rom but the issue is still there, done a clean flash and formatted cache etc etc, but the issue never goes away.
I tried changing sim but no result, used my sim in another phone and it works.
Do you have any idea what it might be?
Click to expand...
Click to collapse
Try to add APN(access point name) manually...see the carrier's apn settings from another device...