I have an unlocked and rooted Samsung Galaxy phone.
Everything was working fine for a year.
Randomly, I lost connection today, and it says that it is not registered on the Network anymore. I tried taking the battery out and re starting the phone and taking out the Sim card, but no luck.
Any suggestions? If I were to install a new rom or the old one, do you think that would fix it?
I was thinking maybe its a problem with Fido, which is my provider, over a unpaid bill or something. I am not sure. Everything was working fine until like 9pm tonight, and then I lost connection.
Or do you think I have to use Odin to put it back to the original factory rom?
If I put it back to the original factory rom, would it become locked again?
This phone was very complicated to unlock, as when I tried the normal method to unlock it, it just gave me zeros.
I bought my phone originally off ebay about 8 months ago.
Everything worked fine pretty much up until tonight.
Do you think this means my phone is black listed? And I will have to change IMEI?
I am going to call my service provider here, but is unlocked, its a T-Mobile phone, but I am using Fido as a provider.
I got a vibrant t959 but some one updated it on i9000 rome by odin and unlocked as i9000. it unlocked but signal up and down always. now i updated it again on t959 original rom and rooted it, recovery and download mode came back again now its normal. but still signal problem. when check status typing *#7465625# it show all locks off position, but still have signal problem. pls any body help me if can.
regards
I was just wondering if I reset everything back to stock/original, will I have to unlock the phone again?
Or will it stay unlocked?
Check your APN settings first try googling your carriers proper APN and make sure its set properly. If thats not it, try reflashing your rom make a backup first.. I'm not sure about having to reunlock your phone you'll have to search XDA. That is a curious problem. Hopefully its not a stolen phone if so they may have blocked the IMEI number the only way to tell is to call the carrier if your paying your bill hey should be willing to answer your question. I recommend buying phones from someone you know and not online.
The phone actually worked today.
I am living in a basement, and I guess one of the towers went down or the reception is just gone bad.
When I went outside 30 minutes later I was getting full signal and everything worked.
Then I went back in the basement, it went back to searching for signal and provider.
Very strange, as I always use to receive signal in the past.
This same thing happened to me last night. I bought my phone a year ago outright. I downloaded sgs unlock app and unlocked the phone. It has worked fine until last night. I have tried entering the unlock code again and it says network unlock sim unsuccessful. I went to the att store and got a new sim thinking maybe the sim card quit working and this did not help. Seems like this has happened to a few people last night. Can anyone help?
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.
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.
Just picked up one of these phones. Really like it so far! One issue I've noticed though, after a few days of ownership, it's randomly dropping/not detecting the sim card? It's happened at least twice where I've left it to charge over night and woke up to the no sim icon, and yesterday at some point while I was watching YouTube videos in full screen (in my hands, off charger, no notice of the drop either whenever it actually occurred). Quickly popping the sim tray out and in resolves the issue. At first I thought it was because I was using a manually cut sim card, so I've since replaced the sim but the problem persists.
Anyone else have this issue? Should I have the device exchanged?
Thanks
First the phone froze and after restart dropped sim
I just had the same issue occur just now. The phone had frozen for over an hour before I did a forced reset and now when it started back it shows no SIMCARD and no connectivity. I am like you, I really like this phone but hopefully this isn't a permanent issue.
Watched it happen just now. Goes from bars to no sim icon without error or notice. Resetting the network settings, resetting the phone, and powering it off/on won't fix it. Literally have to pop the sim in and out and its recognized right away.
I lost sim recognition after I flashed to LOS 11/30 and no matter what I tried, phone would not recognize the sim. Once I flashed back to stock, it came back. Hopefully this was due to the rom and the problem won't come back.
I am not sure if I lose the SIM, but I will say that when I am driving around with Android Auto, I constantly see the cell signal go from LTE to no signal every couple minutes...
blakeatl said:
I lost sim recognition after I flashed to LOS 11/30 and no matter what I tried, phone would not recognize the sim. Once I flashed back to stock, it came back. Hopefully this was due to the rom and the problem won't come back.
Click to expand...
Click to collapse
Had same issues when I flashed back to stock I actually have better signal than when I got it out of the box.... Almost as if the software wasn't installed correctly or something
Same here I'm on the stock room. I'm wondering if it is an app I downloaded. Any idea how to wipe cashe not the apps but system.
This is happening at least twice a day now. It seems to be software related. Power off and on without taking out sim fixes it.
I have S10 bought in UK dual sim. I have two sim inserted slot one UK and slot two foreign sim. They both were working fine until recently.
For the last two weeks both have started loosing connection to network. It is for few seconds 5-10 times a day. Initially this was with foreign sim and this morning the same happened with the UK sim.
I have tried all options in sim card manager, mobile networks and to restart the phone. Still the same.
I have dropped phone twice but this was some time ago so I do not think this is related.
Anyone have experienced something similar on any suggestions how to fix it?
Many thanks
Please delete posted in wrong section.
Sent from my SM-G965F using Tapatalk
Well, I think you should perform a factory reset and if problem persist, I advise you return to the Vendor as you have warranty. So you should get it replaced.
I have the same problem.. after factory reset things are a little better..
As Im using Android Auto on a daily basis, loosing the signal was very bad - as the application crashed every time that happened.. now, after factory reset and latest version of AA, I dont have any issues. Hopefully it will stay that way or Im going to ask for new one.
I was decided to do factory reset as a last resort but I thought that maybe I will start with other options and I did the Reset network settings.
So far all good. For the last two days no single issue with loosing network connection.
Sent from my SM-G965F using Tapatalk
Mine was doing this too. Had to send it back and get a new one. Must've been hardware.
Same here. Unlocked usa version. Tried 2 different carriers, keeps losing network for no reason. Factory reset and flashing august 1 security patch didn't help either. On T-Movile forum, users that mailed it to samsung for warranty repair had motherboard replaced and issue is now fixed.