Related
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
chino0131 said:
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as how I got mine on 10OCT2013 at 10 am and it still hasn't activated, I think it's not going to at this point. I may sadly have to go back to my GN2 and return the GN3 altogehter. :crying:
Mine seemed stuck on activation, ended up using my old sim card, activated almost instantly.
Update: just got off phone with Big Red and they said that for some reason when I'm on my "home" towers, my activation has trouble letting go of the GN2?? Maybe it really is hard to say good-bye...
They are working on it now...
I've always had an issue activating my old number on a new phone with a new SIM.... I've always just switched my old SIM card in and it's worked perfectly lol
Make sure the SIM card has been linked correctly to your phone number. The easiest way is to look on the VZW paperwork that came with the phone and make sure it's your phone nbr and not another person's on your plan.
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
I had an activation problem in store yesterday when swapping my note 2 for note 3. The sales rep entered the sim card info that was on the sticker on the box for the sim card that comes with the phone.
It all ended up causing major activation / service connectivity issues because the sim card info on the box did Not match the actual sim card number for the sim pre-installed on the phone.
This is apparently an issues for some other people as well. If the sim card in the phone is not reconciled with the info on the box prior to entering the info into Verizon's system.... You will be in for a time consuming headache
Sent from my SM-N900V using xda app-developers app
urielsynthesis said:
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
Click to expand...
Click to collapse
Switching your device or SIM will not work. I have now gone through 6 GN3's and almost 20 different SIM cards. It's the towers/service from Verizon. They have noted that this is a problem and are working diligently to fix it...lol Meanwhile, I've returned my GN3 and will wait until they fix this disaster. This rollout is almost as bad as Obamacare...haha
dead batteries said:
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Click to expand...
Click to collapse
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
nimitch said:
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
Click to expand...
Click to collapse
Yeah I tried that as well. I'm not sure there is anything I haven't tried. I've returned my device and decided to stick with my Note 2. Maybe when Verizon gets their heads on right and fixes this, I'll come back.
Well...Making a long story short, a grandchild of mine played with the lockscreen on my Verizon S7 edge. And you know whats coming....a password was set, a password was forgotten, and a phone was reset. Now, Google's FRP lock is in action, and no matter what I do I can't get around it. My Google account information doesn't work on the phone now. I have searched for and tried everything to get around this, including using Odin to flash stock firmware using the method and firmware files here....<< Stock Firmware For Your Verizon S7 Edge and Quick Guide>> By Misterxtc, Recognized Contributor on 24th March 2016, 04:04 PM.
I guess I have a really nice looking paperweight, but maybe someone here has an idea? Another firmware? A backup someone is willing to share that may get me back into the phone? Anything????
Contact google
Can you change your password with Device Manafer?
Been busy with 4th stuff...but don't seem to be able to do what I need to through device manager...."yet"
Sent from my Nexus 6 using XDA-Developers mobile app
This sounds a bit sketchy. FRP only requires you to sign into the phone with the original Gmail account that the phone was set up with. That's it. So do you not know your Gmail account password that you used to set up the phone? Or did you change actual Gmail password first and then try setting up the phone within 72 hours of changing your account password? Something isn't making much sense. If you can log into your Google account on your computer, then you can log into it on your phone...
Sent from my SM-G935V using Tapatalk
This thing is there to prevent the phone being stolen and sold off to someone else. It's obviously imperative that your account details be noted in the event of this and/or OEM Unlock be selected in Developer Options.
I had this happen to me a week or so back, I was messing around with the phone trying to get ADB to authorise on my laptop, and somehow I must have disabled the OEM unlock. Next reboot, it refused point blank to boot into either Android or recovery (which was TWRP). Fortunately, I knew my Google credentials so I simply flashed stock, booted, logged into my Google account when it asked (after it made clear the phone wouldn't work if I didn't), turn OEM Unlock back on, flashed TWRP again and restored my Nandroid backup from a few days earlier. Crisis over. Obviously, without those credentials you potentially have a serious problem.
However, as suggested, contact Google. Providing you can prove you are the holder of the account (and I assume you can), then I imagine there would be ways around this. I'm also unsure why you mention the lockscreen. It has nothing to do with that. FRP lock is entirely down to the Google account on the phone when the FRP lock occurs.
droidnew said:
Well...Making a long story short, a grandchild of mine played with the lockscreen on my Verizon S7 edge. And you know whats coming....a password was set, a password was forgotten, and a phone was reset. Now, Google's FRP lock is in action, and no matter what I do I can't get around it. My Google account information doesn't work on the phone now. I have searched for and tried everything to get around this, including using Odin to flash stock firmware using the method and firmware files here....<< Stock Firmware For Your Verizon S7 Edge and Quick Guide>> By Misterxtc, Recognized Contributor on 24th March 2016, 04:04 PM.
I guess I have a really nice looking paperweight, but maybe someone here has an idea? Another firmware? A backup someone is willing to share that may get me back into the phone? Anything????
Click to expand...
Click to collapse
This is fairly easy to bypass, sadly enough. Hit me up on Hangouts and I'll be happy to walk you through if you still need help.
es0tericcha0s said:
This is fairly easy to bypass, sadly enough. Hit me up on Hangouts and I'll be happy to walk you through if you still need help.
Click to expand...
Click to collapse
Thank you!!!
Sent from my SM-G935V using XDA-Developers mobile app
My FRP method this:
Phone G935A, used Firmware G935U (not AT&T bloatware)
Insert prepaid sim 0$, and 0mb internet, but LTE network...
Personalise phone start, and wifi not turn on. Google verification fail, and NEXT button active...
Personalise finish, and turn dev.opt on, oem unlock on, and add the google account.
[emoji2]
Sent from my SM-G935U using Tapatalk
No, don't contact google. No don't bother with any of this bypass crap.
Contact samsung. Tell them you are the owner of the device and would like to get it unlocked. They will ask for a very detailed list of information to prove you are the owner of the device. Once they get this information from you they will send you an email and a Pre Paid label to mail it to them. Samsung will unlock it and mail it back to you.
Source: I work for a company who terminated an employee who had this protection enabled. This is what Samsung had me do.
i can do in 10 mints without contacting samsung via flexihub
Information is listed all over this forum on how to overcome this dude just research.
Sent from my SM-G935V using XDA-Developers mobile app
Hmm - Saumsung WOULD NOT reset my phone. I have a $200 Boat Anchor?
After 2 support "cases" closed with no notification to my *other* phone or my email, Samsung did send a shipping label, and I sent the phone. Upon arrival at their service center, they proposed a fee of about $70 to perform the re-initialization. I paid the fee with delight. They next advised me that they won't do the job. Perhaps it was because the phone is 8 months "out of warranty".
They did not dispute the validity of my purchase transaction. If this is their idea of "Support", I will not buy another Samsung phone again. Closing support incidents without notification to the problem reporter is garbage, and billing before refusing to do the work is worse than garbage.
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 friend said I could buy the ATT unlocked V20 so I can use it on Cricket which they've the same network. After setting up my Google account I come to this screen and it's trying to force me to sign in but I don't have an account with ATT. Does this mean it's not unlocked?
I assume that 3rd screen is what shows up when you hit skip?
Also, were you planning on rooting your phone? If so, you don't need to set it up, you can just root it and then you won't have any issues with their setup screen.
-- Brian
I figured it out. I removed the SIM card and turned off WiFi which the app requires to continue. Then it finally gave me the option to exit to the home screen. After that i was able to insert the SIM card again with no problem.
I'll see about rooting. I play Ingress and PoGo and its a hassle to trick SafetyNet. I think Android Pay didn't work the last time I tried Magisk. And ROMs screw up my GPS all the time.
So I got an Essential through the Sprint deal about 2 weeks back. Paid off the phone, got it unlocked then popped the Sprint SIM out and have been using it on Verizon. I originally did a factory reset with the Verizon Sim in thinking it would remove the Sprint OMA-DM app and the other associated ones. Unfortunately they are still there. If I pop my sim out to use in a different phone, I'll get a popup asking to check for an unlock but I just close it out.
Is there any way to get rid of those apps as the notifications are annoying as hell when I switch between phones?
takeclear said:
So I got an Essential through the Sprint deal about 2 weeks back. Paid off the phone, got it unlocked then popped the Sprint SIM out and have been using it on Verizon. I originally did a factory reset with the Verizon Sim in thinking it would remove the Sprint OMA-DM app and the other associated ones. Unfortunately they are still there. If I pop my sim out to use in a different phone, I'll get a popup asking to check for an unlock but I just close it out.
Is there any way to get rid of those apps as the notifications are annoying as hell when I switch between phones?
Click to expand...
Click to collapse
I get that pop up and I don't even have a sim in my phone and the app keeps crashing