Hey Everybody,
First off I'll start with what phones/firmware etc etc I have so that I don't need to be constantly writing it in the post.
My phone: i9505 W/ custom firmware, custom kernal etc (basically the custom phone of all phones...I'm a flashaholic...) 100% unlocked BTW
My bosses phone: i9500 W/ Omega v10? It's the latest Omage but I'm not too sure as I don't hang around the i9500 forums.. His is also 100% unlocked.
The other day I did some researching and looked into the 'Boost Mobile with Telstra SIM'....Glitch? I guess you could call it that?
Well anyway, I finally went ahead and did it.
I went up to Telstra and picked up 3 blank SIM's, one for myself, one for my boss, and one for spare.
I ported my number to one of the blank SIM's and, when I went to turn my phone on it came up with 'NO SIM'. I found this quite strange so I took a nandroid and re-flashed my rom.
Same thing... 'NO SIM'. I tried a whole heap of different combos (kernals, modems, firmwares) but finally had enough, so I went and put the SIM in my bosses phone...Long and behold it worked first time.
This confused me a lot considering it appeared as if my phone couldn't even recognize the SIM.
So, I got back on live chat with Boost and activated the spare blank Telstra SIM, and ported my number to that.
3 hours later, I got 3G signal on my phone...I waited for about 10 minutes before getting all excited, and it stayed! It looked as if it had worked!
My cheers were a bit pre-mature however...About an hour after that I got the 'NO SIM' error again.
I went through the same steps, and was up till late trying to figure it out but I ended up having enough and just going to sleep.
In the morning I got into work and the boss said just try re-flashing stock firmware through ODIN. I had tried this last night so I'm not too sure why this would work, but anyway I tried, and I got signal!
After my pre-mature excitement yesterday I wasn't too sure this would stay working..But throughout the day I received calls, texts and browsed the web and it didn't let me down!
I then started driving home...The minute that I got home, I received the dreaded 'NO SIM' error again.
I went through the same steps as before (flashing modems, firmware custom roms etc etc etc) and it still didn't work.
So anyway, I got onto Boost chat and, three hours later they came to the conclusion of sending me a blank SIM...A Telstra blank SIM...
This SIM is now in the mail and should be here mid next week. But if it's anything like my previous two blank SIMS then it won't work.
So..I'd just like to know, has anyone here got any ideas that could help me? The only way out of this that I can see is buying an Optus $2 sim, porting my number to Optus, then buying a Boost $2 SIM and porting my number back..But this will be a little tedious and they may have issues considering the ammount of blank SIMS I have been through.
I'm willing to try any ideas that you guys throw at me, and any input would be muchly appreciated
Cheers guys/girls,
PS, I have looked at this thread but it appears that they didn't find a fix other then sending it away: http://forum.xda-developers.com/showthread.php?t=2197422
Hello, First time poster, and quite frankly a noob at a lot of this. Here's my issue, i have a at&t Samsung Galaxy S4 that i recieved from a family member that was stuck in a serious boot loop. Only way i could get it to come back was to flash the stock firmware, which worked excellent....now my issue, it seems like about 98% of the time i have the "No Service" icon up top. I got the phone locked through at&t but have since unlocked it to use on Straight talk, as thats what i was originally advised to do by an at&t member (turns out I didnt even need to do this in the first place as ST is just using the at&t towers as a reseller). Unlocked phone, still no service. I had ST previously in a Galaxy S2 in my current location and service was superb, so i know its not a carrier issue. Is it possible that when i flashed stock rom, that i missed something? I checked around and it seems like my modem is updated to the latest setting. When i switched it to ST after about 30 minutes the signal popped up and it seems like as soon as it showed up, it was gone again. Since that point i've been able to make 1 call (I activated ST about 4 days ago) and that call was today, with only 1 bar of reception. Shortly after that call the signal dropped completely again. I am at a complete loss as to why it refuses to get any reception. I was thinking maybe the modem needs to be updated, but the wifi works perfect, and the reception seems to show up (just as 1 little bar) rarely. Anyone have any ideas?
Also, as a little side note, i have done a hard reset a few times and to no avail at fixing the issue. I assume since at certain times i do get the little "1 bar" connection that its not a hardware issue but a software issue thats withholding the phone from reaching potential reception. Any help would work wonders as i've paid the $60 for the BYOP Straight talk.
Which firmware did you flash as the latest firmware is 5.01 and there is no stock rom from att for this version.
Reynolds_____ said:
Hello, First time poster, and quite frankly a noob at a lot of this. Here's my issue, i have a at&t Samsung Galaxy S4 that i recieved from a family member that was stuck in a serious boot loop. Only way i could get it to come back was to flash the stock firmware, which worked excellent....now my issue, it seems like about 98% of the time i have the "No Service" icon up top. I got the phone locked through at&t but have since unlocked it to use on Straight talk, as thats what i was originally advised to do by an at&t member (turns out I didnt even need to do this in the first place as ST is just using the at&t towers as a reseller). Unlocked phone, still no service. I had ST previously in a Galaxy S2 in my current location and service was superb, so i know its not a carrier issue. Is it possible that when i flashed stock rom, that i missed something? I checked around and it seems like my modem is updated to the latest setting. When i switched it to ST after about 30 minutes the signal popped up and it seems like as soon as it showed up, it was gone again. Since that point i've been able to make 1 call (I activated ST about 4 days ago) and that call was today, with only 1 bar of reception. Shortly after that call the signal dropped completely again. I am at a complete loss as to why it refuses to get any reception. I was thinking maybe the modem needs to be updated, but the wifi works perfect, and the reception seems to show up (just as 1 little bar) rarely. Anyone have any ideas?
Click to expand...
Click to collapse
If your wifi is working perfect, then modem is not your problem. I have never used Straighttalk but you mentioned that ST is using the AT&T towers so there might be a problem in your simcard registration. Call the ST customer service, tell them your problem and ask them to reprogram your simcard with your phone IMEI. See that would solve your problem.
Hey xda techies and guru's, i need some major desperate help here...
This is going to be a long read, but its for the sake of understanding and what exactly is happening, I hope you read on and hopefully have an idea as to what's going on.
So i've been a Rogers customer for the past 7 years, i've been using the Galaxy S3 for 4 of those years using the same SIM card. Just recently, I decided to upgrade and purchased a Galaxy S5. I put my new sim card in the S5 and everything was working flawlessly for about 2 months and then one morning I was sending some texts out, and didn't receive any all day so i checked my texts and realized they did not send. I then tried to make a call and got a message stating "not registered on network". So being the troubleshooting/techy guy i think i am, i go to google and start trying every solution out there. I got so desperate at wanting to fix this issue i had eventually factory reset, and even stock rom flashed the phone...but nothing i tried or did seemed to fix this issue. I put my sim card back in my S3 and it seemed to work just fine, so I figured nothing was wrong with the sim card, it had to be the S5...so here i am out of solutions to try, i randomly grab my brothers sim card from his phone and put it in my S5, and to my surprise it worked! so i thought that maybe the sim card was actually at fault. so i go to my nearest rogers store and get a new sim card, low and behold it's fixed!!!
...a week later, my phone decides to repeat the same ordeal. "not registered on network", so i go back to rogers and get a new sim card again, seems like it fixed the issue once again. and then a week later, same thing happens yet again. at this point...my phone has a temporary fix, but is way to unreliable as i have no idea when this starts happening and can miss very important phone calls or texts. So now this happens again the other night, and i put the sim into my S3 for a couple hours, make some calls and then for the heck of it decide to try it in my S5 again, and it worked! but it worked for maybe 16 hours until repeating the same thing. so i pop it back into my S3 make some test calls, and put it back into my S5 and now it's working again...for how long, i have no idea...fact is it's unreliable and i hate always having to check my phone in paranoia that this may happen again.
what do you guys think is the problem here? Rogers is willing to help me get it serviced for free. but i feel like they won't find the issue with the time they are given with it...
desperate need of help/advice. thanks!
I've tried everything to get my phone to get network working again. I've re-flashed old and newer images, got a new sim, messed with the APN settings and I just can't get it to work since yesterday.
When it started, my phone was sitting on charge. It was working just fine before I had put it down for 30 minutes. Upon checking for any messages I saw it wasn't getting any service so I restarted the device and was greeted with the 7.1.2 july update installer. Waited for it to finish and once fully back onto the home screen for a few minutes service still never came back. Turned it off and on a few times and turned airplane mode on and off few times still never came back. Turned it off for the night till today when I started playing with it more, factory reset, flashed 6.0, 7.1.2 june, 7.1.2 july, O beta 3 and none of it was getting the network to work.
Went and got a new sim, guy at the store also tried a floor sim and none of them were working but both my old and new sim do work just fine in a backup phone. The 6P reads there is a sim in and it knows its AT&T, but it won't pick up signal at all.
Any help with this? There really isn't much on this topic, but I do see a sim card no installed issue which my phone knows there is a sim card in it.
that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..
i42o said:
that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..
Click to expand...
Click to collapse
I just checked to see if it was blacklisted and its good. Google & Huawei won't service it due to it being out of warranty so rn its pretty much a dead phone for me. Is there is any tests I can run to see if the network radios are working or even turned on?
I had this exact same problem a few months ago with my other 6P. Thankfully it was right before my warranty ran out so i was able to get a replacement, but as far as I know, there isn't much you can do with it network wise.
@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.
Exodusche said:
@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.
Click to expand...
Click to collapse
I really didn't want to go that far and I rather just dump it on craigslist for $250 if its just an issue with at&t. is there some sort of test to see if the antennas are working?
have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.
boxcar8028 said:
have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.
Click to expand...
Click to collapse
Dude... Not trying to be rude, but really?
Anyway I've been waiting for a response back from google. Huawei pretty much told me tough luck since I didn't have warranty left on it. Told google that I was pretty much shoved out by them and argued that a phone not even 2 years old can't get serviced by a multi billion dollar company is pretty embarrassing. Supposedly its being routed up but I was told that a couple days ago when it was going to take 24-48 hours to get back. Right now I'm trying last ditch effort to drain the battery completely and stick it in some rice to possibly suck any possible moisture out that maybe my butt sweat caused. If this doesn't work I'm going to go to other service's stores and ask to try their sims in the phone out.
Fun tip: My phone is been running in boot mode for almost an hour after it turning off from android os for battery being dead. I've been doing random stuff in boot mode trying to make it die completely and it doesn't want too.
So being back and fourth with google for almost a week I was pretty much told tough luck buddy. It fathoms me that a company who created the android OS doesn't even have a service center or require its manufacturers to provide a service center for phones that aren't even more than 2 years old.
My nexus 6p is posted on craigslist and I've bought myself a s8+. so word of warning to you all who buy any google product or from them, just don't. If you have any issues you'll just get a run around. I've had to tell my issue to google at least 20 times and they still didn't care and kept trying to push me to hauwei when neither of them wanted to help.
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.