Related
Hello all,
I bought a Verizon s5 on eBay for $250 the other day. From my reading other forums, I thought that I could just pop my straight talk sim in and it would work.
Apparently that is not the case.
After some reading, I used towel root and was able to get the hidden menus to work , but I really don't know what bands that I should try to enable?
I have a straight talk sim that is set up for an att phone (works perfectly in my S4).
Thus far the phone doesn't recognize my sim at all. It just has a circle where the signal indicator would be.
The phone arrived with a apalachian wireless sim installed and it gets full signal with that sim.
I checked the esn with swappa and it appears to be good.
Any insight would be great. I'm new to all of this and really don't know what I'm doing.
hphillips1 said:
Hello all,
I bought a Verizon s5 on eBay for $250 the other day. From my reading other forums, I thought that I could just pop my straight talk sim in and it would work.
Apparently that is not the case.
After some reading, I used towel root and was able to get the hidden menus to work , but I really don't know what bands that I should try to enable?
I have a straight talk sim that is set up for an att phone (works perfectly in my S4).
Thus far the phone doesn't recognize my sim at all. It just has a circle where the signal indicator would be.
The phone arrived with a apalachian wireless sim installed and it gets full signal with that sim.
I checked the esn with swappa and it appears to be good.
Any insight would be great. I'm new to all of this and really don't know what I'm doing.
Click to expand...
Click to collapse
What APN are you using?
I didnt bother changing the apn because it doesnt recognize my sim. It just has a circle where the signal indicator should be.
Global mode should work fine. The issue might have something to do with the Verizon system not recognizing the ST sim card. Even though the S5 is unlocked, you might have to call VZW to see if it's a privisioning issue. You can check ESN with them too because it could be bad. Good luck and post back if/when you fine the answer.
I am running the same exact setup. Works great for me. Including mms. U should have done a factory reset before rooting. Either way. ....make sure it's in global mode under settings more networks/ network mode. Then download using WiFi since u don't have data yet, straight talk data settings from Google play store. Hit home button open data settings, follow instructions. Good luck.
Verizon Booted me from the Network
4 Months ago I moved to Big Red with my N6.
The signal wasn't as strong as my other Verizon devices which I found odd. I lived about 2 miles away from a Verizon tower and on this device I was only connected 45-50% of the time while at home.
After the first 3 weeks I was still frustrated with the poor signal and I read online everyone cried foul on Google(or Motorola), so forced a PRL update to see if that would fix the issue:
I lost LTE connectivity.
I was connected to 3G but I had no service.
I re entered the APN, nothing.
I took the SIM out put it back in, nothing.
I read online that someone else had a similar issue with the Nexus 6 on Verizon and the only way to resolve the issue was to replace the SIM and that's what I did, LTE service was restored.
About 2 weeks ago I moved about a mile further away from my nearest Verizon tower, so I'm about 3 miles away from a Verizon tower and 80-85% of the time at home I'm not connected.
Today:
Around 3 PM I was in the city and my LTE was fine, I had bars, I had a signal, nothing had changed on my end but I was unable to send text messages, I kept getting this message "Can't send message with CARD 1 error 98" And when I spoke with my sister she said she had been trying to call me for the last 3 hours.
So I contacted Verizon and asked if there was an outage in my area, they said no so I went on to explain the issue(s), and I was told by the customer service rep that my phone wasn't making a connection to the Verizon network, they couldn't see my phone and I needed tech support. Which made sense because of the poor signal all of the time.
So I called Verizon tech support. And the service rep said that I need to enable roaming by entering
PHP:
*22898
This did not fix my issue but maybe it could benefit someone else on Big Red.
I told them the error code and Tech support said we need to check if your phone has dual SIM, I said no it is a Nexus 6 it does not have a second SIM slot I don't care what the error message said. Then I was directed to another tech rep and he said "your phone is NOT a Verizon Nexus 6 and we cannot find it on our network, your phone will not activate on our network, your IMEI is not available to activate on our network" I said wait a minute. I understand the whole FCC ruling and months ago this was suppose to be resolved(I read the post here on XDA). I went online activated the phone when I moved my Nexus 6 over to Verizon, it shows up as a Non Verizon Nexus 6. It allowed me to activate it. It took the IMEI and now they are telling me, NOT ANY MORE!?
I was transferred to a supervisor. He said the same thing, he said he would try to reset everything for my phone but still poor signal and still I have no idea what calls or messages I'm missing and a few text messages are not being sent. I'm on call 24/7 but it looks like I'm going to have to go back to AT&T or T-Mobile.
I believe the poor signal issue is not only Google but also Verizon is still keeping us off the network for the most part and only allowing us to piggyback the rest of the time. Maybe I'm wrong but I hope my 3 hours wasted helps someone else with a similar experience.
I thought I also read somewhere that T-Mobile shut off Band 12. Seriously what the hell is going on with these carriers.
The Closet Candian said:
Verizon Booted me from the Network
4 Months ago I moved to Big Red with my N6.
The signal wasn't as strong as my other Verizon devices which I found odd. I lived about 2 miles away from a Verizon tower and on this device I was only connected 45-50% of the time while at home.
After the first 3 weeks I was still frustrated with the poor signal and I read online everyone cried foul on Google(or Motorola), so forced a PRL update to see if that would fix the issue:
I lost LTE connectivity.
I was connected to 3G but I had no service.
I re entered the APN, nothing.
I took the SIM out put it back in, nothing.
I read online that someone else had a similar issue with the Nexus 6 on Verizon and the only way to resolve the issue was to replace the SIM and that's what I did, LTE service was restored.
About 2 weeks ago I moved about a mile further away from my nearest Verizon tower, so I'm about 3 miles away from a Verizon tower and 80-85% of the time at home I'm not connected.
Today:
Around 3 PM I was in the city and my LTE was fine, I had bars, I had a signal, nothing had changed on my end but I was unable to send text messages, I kept getting this message "Can't send message with CARD 1 error 98" And when I spoke with my sister she said she had been trying to call me for the last 3 hours.
So I contact Verizon and asked if there was an outage in my area, they said no so I went on to explain the issue(s), and I was told by the customer service rep that my phone wasn't making a connection to the Verizon network, they couldn't see my phone and I needed tech support. Which made sense because of the poor signal all of the time.
So I called Verizon tech support. And the service rep said that I need to enable roaming by entering
PHP:
*22898
This did not fix my issue but maybe it could benefit someone else on Big Red.
I told them the error code and Tech support said we need to check if your phone has dual SIM, I said no it is a Nexus 6 it does not have a second SIM slot I don't care what the error message said. Then I was directed to another tech rep and he said "your phone is NOT a Verizon Nexus 6 and we cannot find it on our network, your phone will not activate on our network, your IMEI is not available to activate on our network" I said wait a minute. I understand the whole FCC ruling and months ago this was suppose to be resolved(I read the post here on XDA). I went online activated the phone when I moved my Nexus 6 over to Verizon, it shows up as a Non Verizon Nexus 6. It allowed me to activate it. It took the IMEI and now they are telling me, NOT ANY MORE!?
I was transferred to a supervisor. He said the same thing, he said he would try to reset everything for my phone but still poor signal and still I have no idea what calls or messages I'm missing and a few text messages are not being sent. I'm on call 24/7 but it looks like I'm going to have to go back to AT&T or T-Mobile.
I believe the poor signal issue is not only Google but also Verizon is still keeping us off the network for the most part and only allowing us to piggyback the rest of the time. Maybe I'm wrong but I hope my 3 hours wasted helps someone else with a similar experience.
I thought I also read somewhere that T-Mobile shut off Band 12. Seriously what the hell is going on with these carriers.
Click to expand...
Click to collapse
T-Mobile has not shut band 12. They did it only for Project FI users.
Sent from my Nexus 6 using Tapatalk
The Closet Candian said:
Verizon Booted me from the Network
4 Months ago I moved to Big Red with my N6.
The signal wasn't as strong as my other Verizon devices which I found odd. I lived about 2 miles away from a Verizon tower and on this device I was only connected 45-50% of the time while at home.
After the first 3 weeks I was still frustrated with the poor signal and I read online everyone cried foul on Google(or Motorola), so forced a PRL update to see if that would fix the issue:
I lost LTE connectivity.
I was connected to 3G but I had no service.
I re entered the APN, nothing.
I took the SIM out put it back in, nothing.
I read online that someone else had a similar issue with the Nexus 6 on Verizon and the only way to resolve the issue was to replace the SIM and that's what I did, LTE service was restored.
About 2 weeks ago I moved about a mile further away from my nearest Verizon tower, so I'm about 3 miles away from a Verizon tower and 80-85% of the time at home I'm not connected.
Today:
Around 3 PM I was in the city and my LTE was fine, I had bars, I had a signal, nothing had changed on my end but I was unable to send text messages, I kept getting this message "Can't send message with CARD 1 error 98" And when I spoke with my sister she said she had been trying to call me for the last 3 hours.
So I contact Verizon and asked if there was an outage in my area, they said no so I went on to explain the issue(s), and I was told by the customer service rep that my phone wasn't making a connection to the Verizon network, they couldn't see my phone and I needed tech support. Which made sense because of the poor signal all of the time.
So I called Verizon tech support. And the service rep said that I need to enable roaming by entering
PHP:
*22898
This did not fix my issue but maybe it could benefit someone else on Big Red.
I told them the error code and Tech support said we need to check if your phone has dual SIM, I said no it is a Nexus 6 it does not have a second SIM slot I don't care what the error message said. Then I was directed to another tech rep and he said "your phone is NOT a Verizon Nexus 6 and we cannot find it on our network, your phone will not activate on our network, your IMEI is not available to activate on our network" I said wait a minute. I understand the whole FCC ruling and months ago this was suppose to be resolved(I read the post here on XDA). I went online activated the phone when I moved my Nexus 6 over to Verizon, it shows up as a Non Verizon Nexus 6. It allowed me to activate it. It took the IMEI and now they are telling me, NOT ANY MORE!?
I was transferred to a supervisor. He said the same thing, he said he would try to reset everything for my phone but still poor signal and still I have no idea what calls or messages I'm missing and a few text messages are not being sent. I'm on call 24/7 but it looks like I'm going to have to go back to AT&T or T-Mobile.
I believe the poor signal issue is not only Google but also Verizon is still keeping us off the network for the most part and only allowing us to piggyback the rest of the time. Maybe I'm wrong but I hope my 3 hours wasted helps someone else with a similar experience.
I thought I also read somewhere that T-Mobile shut off Band 12. Seriously what the hell is going on with these carriers.
Click to expand...
Click to collapse
I have VZW and I am not seeing any of the issues that occurred before VZM finally allowed the Non VZM N6s on Network.
- I can still make account changes
- I still have my monthly discount.
Those are typically the two easiest ways to see if you have a supported phone or not. I think you may have signal quality issues but I think those reps may have been wrong. I have a GPS N6 though what version do you have?
BigDig said:
T-Mobile has not shut band 12. They did it only for Project FI users.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks for the clarification.
GMoGoody said:
I have VZW and I am not seeing any of the issues that occurred before VZM finally allowed the Non VZM N6s on Network.
- I can still make account changes
- I still have my monthly discount.
Those are typically the two easiest ways to see if you have a supported phone or not. I think you may have signal quality issues but I think those reps may have been wrong. I have a GPS N6 though what version do you have?
Click to expand...
Click to collapse
My N6 was unlocked new from Google.
Zero problems after a year with the GPS N6 on verizon. What radio are you running?
Sent from my Nexus 6 using Tapatalk
bill3508 said:
Zero problems after a year with the GPS N6 on verizon. What radio are you running?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That I couldn't tell you, if you could explain or provide a link on how to check and select it would be greatly appreciated.
The Closet Candian said:
That I couldn't tell you, if you could explain or provide a link on how to check and select it would be greatly appreciated.
Click to expand...
Click to collapse
Settings > About phone > Baseband version
patmw123 said:
Settings > About phone > Baseband version
Click to expand...
Click to collapse
MDM9625_104662.22.05.27R
I thought you meant
PHP:
*#*#4636#*#*
It has an option to select band
The Closet Candian said:
MDM9625_104662.22.05.27R
I thought you meant
PHP:
*#*#4636#*#*
It has an option to select band
Click to expand...
Click to collapse
Are you 100% stock?
Even if you are, you might try flashing the latest factory image to restore phone to out of box settings.
The reason I am suggesting this is because I had the same issue on my previous phone(HTC M8) with Verizon. I tried everything you have tried and nothing worked until I RUU'd back to stock and it magically started working again.
I realize the M8 is a completely different phone, but if all else has failed it is worth a shot.
FYI, *228, *22898, & *22899 do not work on any LTE enabled VZW device. That is/was used on 3G devices for updating the PRL. In very early LTE devices, dialing that could have actually caused the phone to stop working. It's been fixed now so it doesn't do anything. With the SIM card, the PRL updates automatically when the device connects to the network, so you don't need to dial anything to get the latest PRL.
As for fixing your problem, the only other suggesting I'd say is to try just getting a new SIM card and see if the problem continues.
I find it odd that you are having all of these problems. I originally got my Nexus 6 from Sprint. I am now using Straight Talk. I bought the BYOP kit that came with 9 sim cards, a Verizon activation code, and the $45 monthly service card. The sim cards you get are for Verizon, AT&T, and T-Mobile. (Regular, Micro, Nano for each) I went the Verizon route for obvious reasons. I have had zero problems with service and my LTE is twice as fast as when I was on Sprint. When I look at my lock screen it even says "Verizon Wireless" in the top left corner.
I have yet to experience any of the issues you are having. I know I am not "directly" on Verizon like you are, but that is why I wanted to bring this to your attention. If you would like Verizon coverage on your Nexus 6 for $45 a month check out Straight Talk. You get unlimited talk, text, data. Data is 5GB of LTE then throttled. I have heard the only difference is that you can't quite roam / utilize the partner coverage that someone directly on Verizon can. I have yet to come across anywhere that I have not had signal though.
ldjr said:
Are you 100% stock?
Even if you are, you might try flashing the latest factory image to restore phone to out of box settings.
The reason I am suggesting this is because I had the same issue on my previous phone(HTC M8) with Verizon. I tried everything you have tried and nothing worked until I RUU'd back to stock and it magically started working again.
I realize the M8 is a completely different phone, but if all else has failed it is worth a shot.
Click to expand...
Click to collapse
100% Stock, locked bootloader, no root. I might try that if all else fails, I have an invite to project fi. I was thinking about trying it out even though sprint was horrible in my area and I doubt it has improved.
imnuts said:
FYI, *228, *22898, & *22899 do not work on any LTE enabled VZW device. That is/was used on 3G devices for updating the PRL. In very early LTE devices, dialing that could have actually caused the phone to stop working. It's been fixed now so it doesn't do anything. With the SIM card, the PRL updates automatically when the device connects to the network, so you don't need to dial anything to get the latest PRL.
As for fixing your problem, the only other suggesting I'd say is to try just getting a new SIM card and see if the problem continues.
Click to expand...
Click to collapse
This is my second Verizon SIM and I'm not impressed with the reception.
Rektifying said:
I find it odd that you are having all of these problems. I originally got my Nexus 6 from Sprint. I am now using Straight Talk. I bought the BYOP kit that came with 9 sim cards, a Verizon activation code, and the $45 monthly service card. The sim cards you get are for Verizon, AT&T, and T-Mobile. (Regular, Micro, Nano for each) I went the Verizon route for obvious reasons. I have had zero problems with service and my LTE is twice as fast as when I was on Sprint. When I look at my lock screen it even says "Verizon Wireless" in the top left corner.
I have yet to experience any of the issues you are having. I know I am not "directly" on Verizon like you are, but that is why I wanted to bring this to your attention. If you would like Verizon coverage on your Nexus 6 for $45 a month check out Straight Talk. You get unlimited talk, text, data. Data is 5GB of LTE then throttled. I have heard the only difference is that you can't quite roam / utilize the partner coverage that someone directly on Verizon can. I have yet to come across anywhere that I have not had signal though.
Click to expand...
Click to collapse
Wow I might give that a try. I might have been misinformed but I heard that prepaid plans didn't give you the full service as contract plans.
The Closet Candian said:
Wow I might give that a try. I might have been misinformed but I heard that prepaid plans didn't give you the full service as contact plans.
Click to expand...
Click to collapse
I have been running on straight talk for years across many devices. There is almost no difference. Yes they throttle you after like 4gb or something but I havew never reached that limit with wifi everywhere
The Closet Candian said:
This is my second Verizon SIM and I'm not impressed with the reception.
Click to expand...
Click to collapse
The SIM card has nothing to do with reception. Have you tried a new SIM since the problem started? I suggested it to fix your problem of having no service, not to get a better signal.
+1 on reflashing stock images.
Same problem I had with Verizon on straight talk. I went through so much bs with these people, with same issues you had. It seemed like it was still stuck in GSM or something, and the only band that would work was band 6 on 2g. I could send mms and browse the internet, but a phone call would hang up immediately. USA Band wouldn't work WHATSOEVER.
I called customer service and talked to about 6 different people, all who told me my phone wouldn't work on VZW. When I told them they were full of crap, they would transfer me to somebody else. I finally found someone who ended up changing my phone number on the spot and gave me 5 more gigs of data, but my n6 still wouldn't work; I could call out, but no data or MMS/internet.
I was on the verge of saying **** Verizon. I reflashed factory images and everything was smooth sailing and worked properly. I think there is a bug when you change your radios, something fudges up.
The Verizon straight talk plan is nice if you can get around the hurdles I faced. The only downside,besides what I have already mentioned, is they cap your max speed at 5 mb/s when downloading. I live in an area where ATT rules all, but Verizon picks up LTE in places ATT can't even get 2g (whereas ATT ST downloads around 20+mb/s)... so you'll have to compromise.
FWIW, if you ever hear a customer service rep tell you that they cannot change your phone number without sending you a new sim card, that's a damn lie.
Also, here are my apns to compare with yours. I did not touch these after flashing. I read somewhere that these were the old ones, but they work perfectly.
Using a non Verizon n6 with no issues. I had a local repair shop cut my micro Sim to a nano Sim,and I've been up and running since June. Too bad you are having issues.
Kroniq said:
+1 on reflashing stock images.
Same problem I had with Verizon on straight talk. I went through so much bs with these people, with same issues you had. It seemed like it was still stuck in GSM or something, and the only band that would work was band 6 on 2g. I could send mms and browse the internet, but a phone call would hang up immediately. USA Band wouldn't work WHATSOEVER.
I called customer service and talked to about 6 different people, all who told me my phone wouldn't work on VZW. When I told them they were full of crap, they would transfer me to somebody else. I finally found someone who ended up changing my phone number on the spot and gave me 5 more gigs of data, but my n6 still wouldn't work; I could call out, but no data or MMS/internet.
I was on the verge of saying **** Verizon. I reflashed factory images and everything was smooth sailing and worked properly. I think there is a bug when you change your radios, something fudges up.
The Verizon straight talk plan is nice if you can get around the hurdles I faced. The only downside,besides what I have already mentioned, is they cap your max speed at 5 mb/s when downloading. I live in an area where ATT rules all, but Verizon picks up LTE in places ATT can't even get 2g (whereas ATT ST downloads around 20+mb/s)... so you'll have to compromise.
FWIW, if you ever hear a customer service rep tell you that they cannot change your phone number without sending you a new sim card, that's a damn lie.
Also, here are my apns to compare with yours. I did not touch these after flashing. I read somewhere that these were the old ones, but they work perfectly.
Click to expand...
Click to collapse
The thread owner is on Verizon directly, not Straight Talk. I just offered him the idea. I am using Straight Talk (Verizon Sim Card) with my Nexus 6 and I have had zero issues. When you are on stock / flash stock images, when you boot up your phone, the proper APN settings will load right up and LTE will take off. Works great. Now, what you need to do is write these APN settings down, precisely. I have noticed that sometimes when you flash a custom ROM, the APN settings won't load automatically.
This just happened to me when I flashed "The Pure Nexus Project". I ended up with no data. I manually entered the APN settings and boom. Full data, LTE, MMS, etc
Hello,
I recently upgraded my Huawei Nexus 6P to 6.0.1 (dirty-flash, sideloaded).
I had trouble getting LTE to work at first (turning on/off Airplane Mode makes LTE work). I kept trying to change Field Test settings to make LTE work.
However, when I factory reset it the phone won't make or receive phone calls.
It sticks on "dialing..." and it just won't work. However, data and messaging work just fine.
I forgot to back up my EFS partition so it's partially my fault.
My IMEI number and MEID show correctly, however on the My Verizon website it shows a different MEID that's nothing close to the original one. The last 2 digits were different. Neither the MEID or IMEI were changed during the upgrade process, so it should have worked fine.
I recently called Verizon Tech Support about this and they said they'd change the MEID within 72 hours to 4 days. (I called Friday evening)
They kept having issues with the server rejecting the MEID and I checked, it's not blacklisted. They told me about a "wrong form" being filled out and ran some tests and nothing worked.
The phone MEID and Field Test menus showed properly though, just calling any other number (even Verizon's activation number) won't work.
I kept factory resetting, even downgraded to 6.0 (clean flash with recovery/radios, unrooting and all that), and LTE worked better, but STILL no phone calls!
Whenever I try to activate it on the website, it keeps telling me to contact their number. I'm not sure if I'll need a new SIM card because I've tried another SIM card and will also not make calls.
I'm not sure if calling has to do with the MEID or IMEI or anything else.
Do you have any tips/suggestions to fix this annoying issue?
Thank you,
Exec360
I've seen the issue going from Wireless to LTE and vice versa but I have no issue making or receiving calls. Texting and MMS work ok also. I went from 6.0 to 6.1 by doing a factory image flash. Now I'm Chroma and I'm curious if I would have this same issue on Stock so I will probably flash factory or a slim rom stock tonight. I'm on Verizon and had a nexus 6, I popped the sim in my 6p and it activated with no issue.
rsalas187 said:
I'm on Verizon and had a nexus 6, I popped the sim in my 6p and it activated with no issue.
Click to expand...
Click to collapse
Same here, except I popped out the SIM from my iPhone 5S.
Ironically, when I put the same SIM back into the 5S, calling and voicemail, in addition to data worked, even though the device was recently deactivated from Verizon.
I'd say the issue probably comes up from a corrupted IMEI/MEID or other identifier. (Not completely sure about this though — the IMEI/MEID was the same between popping in the SIM for the first time and after resetting...)
Verizon detected my device as a Huawei 1511 phone and thinks it's an old Samsung feature phone when I run it through support/help pages.
I have the exact same problem with my phone and I don't know what to do.
update: I just flashed the efs backup file and it worked again.
I forgot to back up my EFS partition and I had 2 chances to do so...
My IMEI, MEID and SIM ID show perfectly in the About section, even when factory reset and bootloader locked, but calls still don't work, very odd.
I used Wugfresh and just about every IMEI recovery tool I could find (EFS Professional) but it keeps giving me errors such as "Access Denied..." with BusyBox installed.
Still no email or response from Verizon techs tonight, expecting one tomorrow.
If not, I'll have to RMA.
More specifically, I cannot find an EFS folder or a nv_data.bin file in any file explorer — Root Explorer, Solid Explorer, TWRP, etc.
Alright, I've actually figured out that the problem is NOT the EFS after I sent it in to Verizon.
My IMEI and MEID number and everything else were actually just fine.
It wasn't flashing or anything that ruined my phone... I recently called Verizon one night on my phone about LTE issues on 6.0.1 and after that, the calls just stopped.
In fact, the problem IS on their end.
They gave me a new SIM card and it didn't work. They realized the phone was new on the network and that would cause incompatibility issues.
Now I have to ship my phone to their IT department which takes about 2 weeks.
If that is your case:
Verizon guide to getting your calling back:
First, I'd try flashing an old EFS backup when your phone was working. If that doesn't work, call their support number (1-800-922-0204) and select the tech support option or say it if it asks.
Give them your SIM card number to try activating the phone. If that doesn't work, you can still send in your phone — just ask them and a phone kit will ship.
Sending it in to the IT department will take around 1-2 weeks, so you should definitely have a backup phone or communication device on hand (you can also just use Google Voice from a PC which is a great temporary solution).
I'll say, BIG props to Verizon for giving us very good support.
Exec360 said:
Alright, I've actually figured out that the problem is NOT the EFS after I sent it in to Verizon.
My IMEI and MEID number and everything else were actually just fine.
It wasn't flashing or anything that ruined my phone... I recently called Verizon one night on my phone about LTE issues on 6.0.1 and after that, the calls just stopped.
In fact, the problem IS on their end.
They gave me a new SIM card and it didn't work. They realized the phone was new on the network and that would cause incompatibility issues.
Now I have to ship my phone to their IT department which takes about 2 weeks.
If that is your case:
Verizon guide to getting your calling back:
First, I'd try flashing an old EFS backup when your phone was working. If that doesn't work, call their support number (1-800-922-0204) and select the tech support option or say it if it asks.
Give them your SIM card number to try activating the phone. If that doesn't work, you can still send in your phone — just ask them and a phone kit will ship.
Sending it in to the IT department will take around 1-2 weeks, so you should definitely have a backup phone or communication device on hand (you can also just use Google Voice from a PC which is a great temporary solution).
I'll say, BIG props to Verizon for giving us very good support.
Click to expand...
Click to collapse
AN easier method is to use any Verizon phone with a microSIM and activate on their network.
Once the SIM is active, cut it down to a nanoSIM and put it into the Nexus 6P.
It just works. All this about sending your new phone to them for two weeks is crazy.
I pulled the SIM from my LG G3 and cut it. Up and running in minutes.
tech_head said:
AN easier method is to use any Verizon phone with a microSIM and activate on their network.
Once the SIM is active, cut it down to a nanoSIM and put it into the Nexus 6P.
It just works. All this about sending your new phone to them for two weeks is crazy.
I pulled the SIM from my LG G3 and cut it. Up and running in minutes.
Click to expand...
Click to collapse
Unfortunately, my other phone does not have a microSIM. NanoSIMs usually work with LTE connections.
Trimming a microSIM is dangerous and could actually damage your SIM card tray and your phone.
Thank you for the advice, but I should warn you taking that risk may actually damage or cause issues with the SIM card itself such as not being able to read its SIM card number.
EDIT:
After 5 days, 3 factory resets, and many flashes of the older radio, it has been SOLVED!!!!!
First, try disabling, reinstalling the factory version of Google Connectivity Services, then updating it in the Google Play Store.
Next, dial *#*#4636#*#* on your phone application to get to field test mode. This function will work no matter whether the phone is working or not — it's just an information screen.
Click the 3 dots and select "change radio band". Select Radio Band 6, NOT USA or Radio Band 7 — Verizon told me to try both of those and they are glitchy.
Source: "Attaching 2 screenshots. One with band 6 where calling works but data is 1x. Another with USA band where LTE data works but no calling. Looking closely it's set to emergency calls only." (http://forum.xda-developers.com/showpost.php?p=64149076&postcount=8)
Now my GSM service is working and calls work extremely well!
Glad it had nothing to do with EFS/IMEI numbers after all.
Make sure to set your APN to "VZWINTERNET" if it hasn't been set already.
I'm glad I can share this with XDADevelopers so that they can benefit from this information.
- Exec360
Exec360 said:
EDIT:
After 5 days, 3 factory resets, and many flashes of the older radio, it has been SOLVED!!!!!
First, try disabling, reinstalling the factory version of Google Connectivity Services, then updating it in the Google Play Store.
Next, dial *#*#4636#*#* on your phone application to get to field test mode. This function will work no matter whether the phone is working or not — it's just an information screen.
Click the 3 dots and select "change radio band". Select Radio Band 6, NOT USA or Radio Band 7 — Verizon told me to try both of those and they are glitchy.
Source: "Attaching 2 screenshots. One with band 6 where calling works but data is 1x. Another with USA band where LTE data works but no calling. Looking closely it's set to emergency calls only." (http://forum.xda-developers.com/showpost.php?p=64149076&postcount=8)
Now my GSM service is working and calls work extremely well!
Glad it had nothing to do with EFS/IMEI numbers after all.
Make sure to set your APN to "VZWINTERNET" if it hasn't been set already.
I'm glad I can share this with XDADevelopers so that they can benefit from this information.
- Exec360
Click to expand...
Click to collapse
I have the same issue with model h1511 and i bought the phone from Ebay but im living in Qatar .. i dunno what to do .. LTE data connection working fine .. sending and receiving sms is working ok .. only I can't make or receive calls. i'm not sure to whom I should report this issue
Exec360 said:
EDIT:
After 5 days, 3 factory resets, and many flashes of the older radio, it has been SOLVED!!!!!
First, try disabling, reinstalling the factory version of Google Connectivity Services, then updating it in the Google Play Store.
Next, dial *#*#4636#*#* on your phone application to get to field test mode. This function will work no matter whether the phone is working or not — it's just an information screen.
Click the 3 dots and select "change radio band". Select Radio Band 6, NOT USA or Radio Band 7 — Verizon told me to try both of those and they are glitchy.
Source: "Attaching 2 screenshots. One with band 6 where calling works but data is 1x. Another with USA band where LTE data works but no calling. Looking closely it's set to emergency calls only." (http://forum.xda-developers.com/showpost.php?p=64149076&postcount=8)
Now my GSM service is working and calls work extremely well!
Glad it had nothing to do with EFS/IMEI numbers after all.
Make sure to set your APN to "VZWINTERNET" if it hasn't been set already.
I'm glad I can share this with XDADevelopers so that they can benefit from this information.
- Exec360
Click to expand...
Click to collapse
Where was this thread yesterday when I needed it...lol I was messing with my radios and screwed my phone up. Please not this method may not work on a custom ROM I had to flash back to 6.0.0.
Exec360 said:
EDIT:
After 5 days, 3 factory resets, and many flashes of the older radio, it has been SOLVED!!!!!
First, try disabling, reinstalling the factory version of Google Connectivity Services, then updating it in the Google Play Store.
Next, dial *#*#4636#*#* on your phone application to get to field test mode. This function will work no matter whether the phone is working or not — it's just an information screen.
Click the 3 dots and select "change radio band". Select Radio Band 6, NOT USA or Radio Band 7 — Verizon told me to try both of those and they are glitchy.
Source: "Attaching 2 screenshots. One with band 6 where calling works but data is 1x. Another with USA band where LTE data works but no calling. Looking closely it's set to emergency calls only." (http://forum.xda-developers.com/showpost.php?p=64149076&postcount=8)
Now my GSM service is working and calls work extremely well!
Glad it had nothing to do with EFS/IMEI numbers after all.
Make sure to set your APN to "VZWINTERNET" if it hasn't been set already.
I'm glad I can share this with XDADevelopers so that they can benefit from this information.
- Exec360
Click to expand...
Click to collapse
I have the same issue but I live in Qatar. the thing is that my phone has the exact same issue urs. im glad you could solve it. Can you help me solve mine ??
mohawahba said:
I have the same issue but I live in Qatar. the thing is that my phone has the exact same issue urs. im glad you could solve it. Can you help me solve mine ??
Click to expand...
Click to collapse
In the US, all carriers are supported for Nexus 6P use. Since you live in Qatar, you may have a different carrier.
Here are a few other points or solutions for this issue:
If your carrier is not Verizon, does your carrier whitelist the Nexus 6P or only phones sold through them?
Do you get an IMEI number in the Settings application? (don't put it here for privacy reasons) If you don't, then your issue most likely has to do with accidentally deleting or modifying the EFS partition. Try restoring an EFS backup. ALWAYS back up your EFS before you install something else or root your phone — and keep it in a safe location! Alas, that was not the case for me.
Have you tried turning Roaming on inside your cellular network settings or have a specific roaming plan?
Do you get decent reception when making calls in Qatar? Where do you have this issue most, indoors or outdoors? You should get 1x at least.
Try the field test mode (*#*#4636#*#*) in the phone application. Go to "phone info".
If you see "GSM service: emergency calls only" on Verizon, the GSM band is not connected which makes phone calls. Switch to Band 6.
Otherwise, if you see the same thing for GPRS, try switching to another band. I'm not familiar with carriers except Verizon or other US carriers (AT&T, T-mobile, etc.)
I've emphasized this a lot, but try a factory reset. Lock the bootloader and remove your custom mods to the system. It may just work for you.
The case may be that the phone service does not work in Qatar, your reception is weak, or you have a specific phone plan. It may be your carrier not being compatible with certain bands, like GSM.
If that is the case, try calling their support and ask them for any possible solutions to the problem.
EDIT:
You also stated that you bought your 6P from Ebay. Many risks can come from buying used phones off of there rather than the official websites. It's likely that someone messed with the EFS and IMEI numbers.
It could be a stolen phone too... in those cases, it would be illegal (in some countries, not sure if in Qatar) to change the IMEI number unless you have an EFS backup. Sorry, you may just be out of luck. Try another solution like Google Voice or Skype (paid) for now until you get it fixed.
Thx bro
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
Exec360 said:
In the US, all carriers are supported for Nexus 6P use. Since you live in Qatar, you may have a different carrier.
Here are a few other points or solutions for this issue:
If your carrier is not Verizon, does your carrier whitelist the Nexus 6P or only phones sold through them?
Do you get an IMEI number in the Settings application? (don't put it here for privacy reasons) If you don't, then your issue most likely has to do with accidentally deleting or modifying the EFS partition. Try restoring an EFS backup. ALWAYS back up your EFS before you install something else or root your phone — and keep it in a safe location! Alas, that was not the case for me.
Have you tried turning Roaming on inside your cellular network settings or have a specific roaming plan?
Do you get decent reception when making calls in Qatar? Where do you have this issue most, indoors or outdoors? You should get 1x at least.
Try the field test mode (*#*#4636#*#*) in the phone application. Go to "phone info".
If you see "GSM service: emergency calls only" on Verizon, the GSM band is not connected which makes phone calls. Switch to Band 6.
Otherwise, if you see the same thing for GPRS, try switching to another band. I'm not familiar with carriers except Verizon or other US carriers (AT&T, T-mobile, etc.)
I've emphasized this a lot, but try a factory reset. Lock the bootloader and remove your custom mods to the system. It may just work for you.
The case may be that the phone service does not work in Qatar, your reception is weak, or you have a specific phone plan. It may be your carrier not being compatible with certain bands, like GSM.
If that is the case, try calling their support and ask them for any possible solutions to the problem.
EDIT:
You also stated that you bought your 6P from Ebay. Many risks can come from buying used phones off of there rather than the official websites. It's likely that someone messed with the EFS and IMEI numbers.
It could be a stolen phone too... in those cases, it would be illegal (in some countries, not sure if in Qatar) to change the IMEI number unless you have an EFS backup. Sorry, you may just be out of luck. Try another solution like Google Voice or Skype (paid) for now until you get it fixed.
Click to expand...
Click to collapse
Here in qatar, i have one friend having the same fone from amazon and it is working fine. Here no CDMA plus texting and data are working. If the efs is corrupt or as u say screwed, it would work data and text? Band USA and 6 re ok with data and text.. Band 7 dead.
In general, it may corrupt the phone function but texts/data may work fine.
Most carrier connectivity issues usually come up from a corrupt EFS or the service not being activated on your plan.
http://forums.androidcentral.com/ask-question/423732-understanding-cwm-backups-efs-partition-etc.html
For you, it seems like Band 6 is the correct one. No CDMA — and GSM is working again. Good job
Another method to try:
Update the Preferred Roaming List (PRL) - dial *228 on the phone app or figure out your carrier's PRL update number
That might work, didn't affect my calls since I don't use roaming services.
By "Band 7 dead", do you mean that the service just won't connect? My issue came from messing with the bands to fix the LTE issue and messing up my phone.
Try to call your carrier's support — try getting a new SIM card or collect information about the Nexus 6P compatibility, if they don't have it on their website.
Was the phone working since you first used it? Have you rooted or done any system-level modifications to it? Also is your carrier Verizon, because I don't think they have strong roaming service in Qatar... I am in the USA right now using Band 6, working fine.
https://community.verizonwireless.com/thread/494218
When you dial, do you get "Dialing..." and just have to wait until it hangs up, or is there static, or a carrier message? Does your friend have the same carrier (Verizon) as you do?
Sorry I'm asking so many questions. I just can't quite identify your issue very well.
Exec360 said:
In general, it may corrupt the phone function but texts/data may work fine.
Most carrier connectivity issues usually come up from a corrupt EFS or the service not being activated on your plan.
http://forums.androidcentral.com/ask-question/423732-understanding-cwm-backups-efs-partition-etc.html
For you, it seems like Band 6 is the correct one. No CDMA — and GSM is working again. Good job
Another method to try:
Update the Preferred Roaming List (PRL) - dial *228 on the phone app or figure out your carrier's PRL update number
That might work, didn't affect my calls since I don't use roaming services.
By "Band 7 dead", do you mean that the service just won't connect? My issue came from messing with the bands to fix the LTE issue and messing up my phone.
Try to call your carrier's support — try getting a new SIM card or collect information about the Nexus 6P compatibility, if they don't have it on their website.
Was the phone working since you first used it? Have you rooted or done any system-level modifications to it? Also is your carrier Verizon, because I don't think they have strong roaming service in Qatar... I am in the USA right now using Band 6, working fine.
https://community.verizonwireless.com/thread/494218
When you dial, do you get "Dialing..." and just have to wait until it hangs up, or is there static, or a carrier message? Does your friend have the same carrier (Verizon) as you do?
Sorry I'm asking so many questions. I just can't quite identify your issue very well.
Click to expand...
Click to collapse
Thanks for exerting all kind of possible solutions . really appreciated ... I ll explain next everything ..
First of all I'm no verizon subscriber .. I just got the phone from ebay shipped to qatar .. that's all international buyer ..
well secondly, the service is activated. here is different than yours in activation process. Plus my sim card is working on all other devices, opo, op2, opx, mi redmi n2, moto g ...
I believe the problem remains in the piece I have now (nexus 6p) because im used to buy phones from the US and they work fine expect some missing LTE bands that does not really interfere with calling service.
If the EFS/IMEI is corrupt, will it register on the network normally? will data and text still work?
Band 7 dead means no text no data and surely no calls ... plus when I chose it, i always get called ended right after i press Dial a number
experience with other bands:
band USA: text and data working fine ... calls: when dialing, it keeps dialing until the network fails and returns again like reconnect (the bars disappear and return again) and when i hang up, it respond quickly and execute the action but on,
Band 6: text ok data ok , calls no .. but when dialing, it keeps dialing normally till it gives me (call ended ) and if I try to hang up after few seconds, it freezes the phone for like 10 seconds till it execute the action of hanging up ...
so the USA band is the most responsive band in terms of hanging up ..
when I dial *#4636 .... , and access phone information to change preferred network, it is usually set to LTE/CDMA/GSM (PRL) >> if i try to change it to LTE/GSM (PRL) because no CDMA here, it usually return to the default after restarting the phone .. it does not really change the network if, for example, I choose GSM only .. I still see LTE on the bar .. moreover, when i try to choose 2g from cellular networks from settings, it does not reflect and I still get LTE working .. weird ..
** in all cases, FYI, I always see the carrier name in the top left corner of the screen.
*228 does not work as Im not verizon .. plus any USSDs are not going through as it gives error "connection problem or invalid MMI code"
when I try to access caller ID, it gives error " network or SIM card error".
I tried to call the carrier but they could not do anything. I'm still expecting a call from their back office team who ( i assume ) has more experience
getting a new sim would not help because I have tried different active sims different numbers and I also tried the second carrier here in Qatar (vodafone) and the problem persist.
the fone never worked since i reached Qatar. It was not rooted. I only unlocked BL and flashed the first factory stock rom (fully including the radio), yet nothing
wait wait please don't lose hope
one friend here is also giving me ideas and solutions to get over my isssue, he suggested i flash chroma rom bcz it has more bands. I will flash it and give a feedback.
I really appreciate your efforts and also his efforts @Soulfly3
pardon me if I wrote too many things and for giving all my trials not in order
Thanks
Thanks everyone for helping me resolve my issue. biggest thanks goes to @@scoobysnack who helped me greatly to get over it.
Installing Chroma ROM solved the issue because basically it was a problem of bands. Chroma had more bands that work in Qatar. and I could return back to stock rom again without any problems ( but don't mess up with bands in phone information )
Thanks @Exec360 for offering me your great support >>>
I told you chroma would solve your problems. it has different bands to select and I figured the "AUS" bands would work.
Any advice for those of us operating on Verizon's extended network? I'm using my device on the Appalachian wireless network (with whom Verizon has a network sharing agreement as part of it's LTE in Rural America program), and I'm constantly getting the roaming indicator, even though I know I'm not roaming. I've never dealt with this on any other device, and I've used 4 different devices encompassing both Windows Phone and Android. If I switch the CDMA roaming indicator to "Home", the roaming indicator disappears and the usual LTE indicator appears, but I'm unable to make voice calls. If I switch the roaming indicator to "Automatic", I can make voice calls but the roaming indicator returns and the device tells me I'm roaming inside the test menu, even though Verizon tells me I'm not incurring roaming charges. If that's true, then the roaming indicator is just an annoyance, but it's there constantly (even when on WiFi) and for me it's a significant annoyance. Is there anything I can do, or is this just something I'm going to have to live with?
Hey guys, I just saw a YouTube video that was posted yesterday where the guy shows that after the update he no longer could connect with his Verizon SIM card in the axon 7. Has anybody else run into this? Mine won't be here until Monday but if this is true I'm going to be sorely disappointed. Thanks for your input.
I am on verizon with no additional problems after the update. I am still always roaming, and my signal is the same (more bars but still the same reception). LTE, MMS, SMS, Cdma all work the same.
I'm really glad to hear that. I'm not so sure the guy knew what he was doing either... Lol :silly:
CaptainElwood said:
I am on verizon with no additional problems after the update. I am still always roaming, and my signal is the same (more bars but still the same reception). LTE, MMS, SMS, Cdma all work the same.
Click to expand...
Click to collapse
Quick question for you bud. I currently have the Moto Z-Force, but I want an unlocked phone that I can root and mess around with and unfortunately this phone doesn't have that capability. Would you say this is a great alternative in terms of functionality and specs? Tia
CaptainElwood said:
I am on verizon with no additional problems after the update. I am still always roaming, and my signal is the same (more bars but still the same reception). LTE, MMS, SMS, Cdma all work the same.
Click to expand...
Click to collapse
I second this. No issues on Verizon unlimited plan after update. Always showing roaming also. Mms, sms, calls work as suppose to. All out of the box settings.
Sent from my ZTE A2017U using XDA-Developers mobile app
tolymatev said:
I second this. No issues on Verizon unlimited plan after update. Always showing roaming also. Mms, sms, calls work as suppose to. All out of the box settings.
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
I can third it lol no issues here. Mine actually has better signal after update on verizon and sms/mms everything works still no issues anywhere
My VZW situation. Just an FYI post AND how to fix it.
I'm on Verizon, have had my Axon 7 for over a month now. No issues other than not having VoLTE, and the occasional software farts (Using Nova Launcher now). When I initially set-up my phone, I imported all previous apps directly from the Play Store. I should have known not to install the VZW apps that were previously installed on my HTC One M8 (purchased directly from VZW), but in my excitement for the new phone, it skipped my mind. Anyhow, no issues through 9/19. "Verizon" displayed as my carrier, and full access to the LTE network.
Fast forward to 9/20 (post B27 update) when one of the VZW updated automatically (I don't recall which of the 2 apps I had installed), and BAMM, "123456" displayed as my carrier and no more access to the LTE network (3G only). Later that evening, my VZW account showed my number with an "unauthorized, non-VZW device", whereas, before the VZW app update it showed my HTC one M8. I removed the SIM and shut down the phone, re-installed the SIM and re-booted....nada. Tried what seemed to be every permutation of replacing the SIM card, played around with APN settings...no dice.
My feeling is they booted me off 4G LTE once the app recognized I was using an unauthorized, non-VZW device. The steps below solved the issue (Provided by "vzwcdma" via the ZTE Community Forum).
"As for losing LTE connectivity, I've had a similar problem before, both on the A7 and other devices. On other devices, like Motorola devices, I could just boot into the bootloader and clear the modem state partitions via fastboot, but ZTE seems to have disabled that function in the A7's bootloader. So, for the A7, I had to mess around a bit with the modem mode. Download "Network" or "4G LTE Switch" from the Play Store. Open it and scroll down to "Set preferred network type", where it should say "LTE/GSM/CDMA auto (PRL)". There isn't really a set guide for what you have to do, but try switching into LTE-only mode, try hitting "Turn off radio" and "Turn on radio" (not Airplane Mode), maybe try "LTE/CDMA audo (PRL)", maybe turn off radio, switch to LTE-only mode, turn on radio, etc. At some point (I'm not sure what) the phone will reset its modem state, and should re-connect to Verizon LTE (and when it does, switch the network type back to LTE/GSM/CDMA auto PRL.
My Verizon account also shows "unauthorized, non-VZW device". Shouldn't affect anything. I've been using an unauthorized/non-VZW device prior to the A7 with no issues as well."
roseykr said:
My VZW situation. Just an FYI post AND how to fix it.
I'm on Verizon, have had my Axon 7 for over a month now. No issues other than not having VoLTE, and the occasional software farts (Using Nova Launcher now). When I initially set-up my phone, I imported all previous apps directly from the Play Store. I should have known not to install the VZW apps that were previously installed on my HTC One M8 (purchased directly from VZW), but in my excitement for the new phone, it skipped my mind. Anyhow, no issues through 9/19. "Verizon" displayed as my carrier, and full access to the LTE network.
Fast forward to 9/20 (post B27 update) when one of the VZW updated automatically (I don't recall which of the 2 apps I had installed), and BAMM, "123456" displayed as my carrier and no more access to the LTE network (3G only). Later that evening, my VZW account showed my number with an "unauthorized, non-VZW device", whereas, before the VZW app update it showed my HTC one M8. I removed the SIM and shut down the phone, re-installed the SIM and re-booted....nada. Tried what seemed to be every permutation of replacing the SIM card, played around with APN settings...no dice.
My feeling is they booted me off 4G LTE once the app recognized I was using an unauthorized, non-VZW device. The steps below solved the issue (Provided by "vzwcdma" via the ZTE Community Forum).
"As for losing LTE connectivity, I've had a similar problem before, both on the A7 and other devices. On other devices, like Motorola devices, I could just boot into the bootloader and clear the modem state partitions via fastboot, but ZTE seems to have disabled that function in the A7's bootloader. So, for the A7, I had to mess around a bit with the modem mode. Download "Network" or "4G LTE Switch" from the Play Store. Open it and scroll down to "Set preferred network type", where it should say "LTE/GSM/CDMA auto (PRL)". There isn't really a set guide for what you have to do, but try switching into LTE-only mode, try hitting "Turn off radio" and "Turn on radio" (not Airplane Mode), maybe try "LTE/CDMA audo (PRL)", maybe turn off radio, switch to LTE-only mode, turn on radio, etc. At some point (I'm not sure what) the phone will reset its modem state, and should re-connect to Verizon LTE (and when it does, switch the network type back to LTE/GSM/CDMA auto PRL.
My Verizon account also shows "unauthorized, non-VZW device". Shouldn't affect anything. I've been using an unauthorized/non-VZW device prior to the A7 with no issues as well."
Click to expand...
Click to collapse
Good to know! I've had so many phones and this hardware looks so awesome for the price, but of course vzw isn't gonna play nice with it without some work. Looking forward to getting mine
Verizon still working fine for me.
After the b27 update I saw improved signal strength. I'm on page plus mvno. After driving in a fringe reception area, I lost lte,and I showed as roaming. It seemed to be using boost Mobile from what the phones network menus displayed. Axon doesn't have a mobile network setting for 'system b', only auto & home only. Tried both, rebooting each time, no fix. I ended up resetting phone, fixed it all. I then switched mobile network to home only, and hoping that it's done.
PS-after b27 I had to re-enable a couple settings, pinch for screen shot, etc.
Edit: it's now been several weeks with it set to home network only. I daily drive in fringe reception areas and have better signal strength than ever, with any phone/carrier combo. All is great, no more issues. Great phone!
For reference, I'm on page plus mvno, dropped in my activated sim from my old phone into the right-side sim slot for CDMA services. Then set to home only. Done.
Sent from my Axon 7 using XDA Labs
Just wanted to see if anyone else had inputs of post update Verizon service, good and bad... hasn't been a ton of chatter in the last week. I have a phone on its way from the egg, trying to decide if it's worth starting a new sim card with Verizon and dealing with that work around... is getting the number off a display and ordering online still the easiest way to get activated?
Works great on VZW still. Love the phone.
methcat said:
Just wanted to see if anyone else had inputs of post update Verizon service, good and bad... hasn't been a ton of chatter in the last week. I have a phone on its way from the egg, trying to decide if it's worth starting a new sim card with Verizon and dealing with that work around... is getting the number off a display and ordering online still the easiest way to get activated?
Click to expand...
Click to collapse
I'd say that the Axon works just as well on Verizon as it did prior to the update, but with potentially better signal strength though I didn't really have a big issue with that prior to the update so I'm not sure (the T-Mobile SIM does seem to do a lot better post-update...but Verizon has always worked well).
I really doubt you'll have any substantive trouble with VZW on this device, especially if you're willing and able to mess a bit with some of the more advanced settings just in case a problem does arise. Here are the oddities, and I'm trying to list *all* of them!
1. No VoLTE or (I presume) HD calling
2. Voicemail appears to have to be accessed by dialing *86 as opposed to long-pressing the '1' key
3. Roaming icon is present intermittently
4. Data roaming *must* be enabled to ensure consistent and reliable data service
5. Verizon's website won't recognize the device at all in the Account Overview pages (mine still shows the last "approved" device I had with my VZW SIM - an iPhone 6S)
6. MMS *may* require a hack to get the proper APN, though I've had no trouble with this (I'm prepaid though); the hack requires a GSM SIM, so beware of this
7. 1X reception *seems* a tad weak in terms of dBm but functionally it almost seems better than my other Verizon phones (weird!)
8. Carrier label will be either '123456,' '002127' (EvDO only), or (I think?) '31000' when not using LTE (i.e., 1X or 3G). When on LTE the phone should show "Verizon Wireless" as normal
9. A SIM/modem reset may be necessary once in a great while it seems...so it's good to understand how to navigate to the "Phone Information" screen to toggle radio settings...also, I've found just SIM-cycling with a GSM SIM will often fix any connectivity problems as well...and sometimes just rebooting the phone with no SIM at all can help too (or a combo of all the above!)
If you can tolerate the above issues then the phone is great. I really enjoy it. I've found the Verizon side of things to be pretty reliable on the Axon 7, even with my endless tinkering with radio modes and other stuff, which has seemed to get me into (recoverable) trouble a few times.
Most importantly - the endless chatter on various forums that Verizon "blocks" the Axon 7 and other non-approved devices is total bunk. In every case where I've run into an issue it can be resolved on my side - Verizon is doing nothing whatsoever to inhibit the use of the Axon 7 on its network as far as I can tell (notwithstanding activation hurdles, admittedly)...many of the people making such claims seem to be speaking from a standpoint of total ignorance and it's kind of getting annoying, to be honest...it seems like the minute someone has an issue with the Axon 7, some ignoramus gets on the relevant forums/comments and claims that Verizon is "blocking" the device. Total BS IMO.
Good luck! As far as activation is concerned...I'd say it might be best to just go to Wal-Mart and buy a cheap prepaid phone or something (looks like the HTC Desire 526 has a nano-SIM and is only $37.49 on their website)...or maybe a cheap nano-SIM'd Verizon phone off of Swappa or eBay? That's probably what I'd do...But I know neither of those solutions are particularly helpful...VZW definitely makes it a bit of a pain.
flyer_andy said:
I'd say that the Axon works just as well on Verizon as it did prior to the update, but with potentially better signal strength though I didn't really have a big issue with that prior to the update so I'm not sure (the T-Mobile SIM does seem to do a lot better post-update...but Verizon has always worked well).
I really doubt you'll have any substantive trouble with VZW on this device, especially if you're willing and able to mess a bit with some of the more advanced settings just in case a problem does arise. Here are the oddities, and I'm trying to list *all* of them!
1. No VoLTE or (I presume) HD calling
2. Voicemail appears to have to be accessed by dialing *86 as opposed to long-pressing the '1' key
3. Roaming icon is present intermittently
4. Data roaming *must* be enabled to ensure consistent and reliable data service
5. Verizon's website won't recognize the device at all in the Account Overview pages (mine still shows the last "approved" device I had with my VZW SIM - an iPhone 6S)
6. MMS *may* require a hack to get the proper APN, though I've had no trouble with this (I'm prepaid though); the hack requires a GSM SIM, so beware of this
7. 1X reception *seems* a tad weak in terms of dBm but functionally it almost seems better than my other Verizon phones (weird!)
8. Carrier label will be either '123456,' '002127' (EvDO only), or (I think?) '31000' when not using LTE (i.e., 1X or 3G). When on LTE the phone should show "Verizon Wireless" as normal
9. A SIM/modem reset may be necessary once in a great while it seems...so it's good to understand how to navigate to the "Phone Information" screen to toggle radio settings...also, I've found just SIM-cycling with a GSM SIM will often fix any connectivity problems as well...and sometimes just rebooting the phone with no SIM at all can help too (or a combo of all the above!)
If you can tolerate the above issues then the phone is great. I really enjoy it. I've found the Verizon side of things to be pretty reliable on the Axon 7, even with my endless tinkering with radio modes and other stuff, which has seemed to get me into (recoverable) trouble a few times.
Most importantly - the endless chatter on various forums that Verizon "blocks" the Axon 7 and other non-approved devices is total bunk. In every case where I've run into an issue it can be resolved on my side - Verizon is doing nothing whatsoever to inhibit the use of the Axon 7 on its network as far as I can tell (notwithstanding activation hurdles, admittedly)...many of the people making such claims seem to be speaking from a standpoint of total ignorance and it's kind of getting annoying, to be honest...it seems like the minute someone has an issue with the Axon 7, some ignoramus gets on the relevant forums/comments and claims that Verizon is "blocking" the device. Total BS IMO.
Good luck! As far as activation is concerned...I'd say it might be best to just go to Wal-Mart and buy a cheap prepaid phone or something (looks like the HTC Desire 526 has a nano-SIM and is only $37.49 on their website)...or maybe a cheap nano-SIM'd Verizon phone off of Swappa or eBay? That's probably what I'd do...But I know neither of those solutions are particularly helpful...VZW definitely makes it a bit of a pain.
Click to expand...
Click to collapse
#6 might not need the GSM SIM workaround anymore after the B27 update. The + sign shows up for me all the time now, even if I only have a Verizon SIM inserted.
thanks for the list guys, i think i'll give it a shot. i'm going to try to add it as a second line to my wifes plan online. is borrowing a friends imei from a nano phone still the best way to get a new activated sim for this phone?
that 526 is a predaid, will verizon just switch that sim to plan if i call in? or are they different?
---------- Post added at 03:42 PM ---------- Previous post was at 03:18 PM ----------
methcat said:
that 526 is a predaid, will verizon just switch that sim to plan if i call in? or are they different?
Click to expand...
Click to collapse
found this, not sure if this is still the rule...
http://www.prepaidphonenews.com/2016/02/new-policy-may-require-verizon-prepaid.html
"It turns out that Verizon made a policy change effective 1/17/16 that requires Verizon Prepaid Phones to be activated on Verizon Prepaid and have at least $30 in airtime applied to them before they cam be used on Verizon postpaid. A Reddit user posted a copy of an internal Verizon document detailing the new rule:
Effective 1/17/2016, customers who purchase a Prepaid 4G device must activate on a $30, $45, or $60 Prepaid plan and make at least 1 monthly service payment before they are eligible to move the device to a new or active Postpay account .
Device remains locked until first month’s payment is made on their Prepaid plan.
Device is unlocked automatically upon successful first month’s payment and can be used on Postpaid plan (new SIM or SIM swap).
Attempting to use an active Postpay SIM Card with a new 4G LTE Prepaid PIB smartphone prior to making the required monthly payment, hotlines the Postpay MDN (SFO 83643) . The hotline remains until first month’s payment is made.
Customers who activate on the $45 or $60 Prepaid plans and enroll in Auto Pay, receive bonus 1GB data per month.
If account is hotlined:
Data access, outgoing calls, and text messaging do not work.
Text message is sent to smartphone.
*VZW FREE MSG: Phone must be activated on Verizon Wireless Prepaid service and first monthly payment must be made before it can be used with any other service. *
Auto-remark is placed on the customer's account.
*SIM Swap attempted: MDN Hotlined. Phone must be activated on VZW Prepaid service and first month paid before it can be activated as postpaid. *"
methcat said:
thanks for the list guys, i think i'll give it a shot. i'm going to try to add it as a second line to my wifes plan online. is borrowing a friends imei from a nano phone still the best way to get a new activated sim for this phone?
that 526 is a predaid, will verizon just switch that sim to plan if i call in? or are they different?
---------- Post added at 03:42 PM ---------- Previous post was at 03:18 PM ----------
found this, not sure if this is still the rule...
http://www.prepaidphonenews.com/2016/02/new-policy-may-require-verizon-prepaid.html
"It turns out that Verizon made a policy change effective 1/17/16 that requires Verizon Prepaid Phones to be activated on Verizon Prepaid and have at least $30 in airtime applied to them before they cam be used on Verizon postpaid. A Reddit user posted a copy of an internal Verizon document detailing the new rule:
Effective 1/17/2016, customers who purchase a Prepaid 4G device must activate on a $30, $45, or $60 Prepaid plan and make at least 1 monthly service payment before they are eligible to move the device to a new or active Postpay account .
Device remains locked until first month’s payment is made on their Prepaid plan.
Device is unlocked automatically upon successful first month’s payment and can be used on Postpaid plan (new SIM or SIM swap).
Attempting to use an active Postpay SIM Card with a new 4G LTE Prepaid PIB smartphone prior to making the required monthly payment, hotlines the Postpay MDN (SFO 83643) . The hotline remains until first month’s payment is made.
Customers who activate on the $45 or $60 Prepaid plans and enroll in Auto Pay, receive bonus 1GB data per month.
If account is hotlined:
Data access, outgoing calls, and text messaging do not work.
Text message is sent to smartphone.
*VZW FREE MSG: Phone must be activated on Verizon Wireless Prepaid service and first monthly payment must be made before it can be used with any other service. *
Auto-remark is placed on the customer's account.
*SIM Swap attempted: MDN Hotlined. Phone must be activated on VZW Prepaid service and first month paid before it can be activated as postpaid. *"
Click to expand...
Click to collapse
Dang...yeah I think you're right about this. My mistake...ugh I wish they'd just make it easy! In that case I'd say Swappa would be the best route...I've bought a few phones off of there and it's always been a great experience.
What are your APN settings? I'm having issues getting my data to work on Verizon.
Salmonella lolz said:
What are your APN settings? I'm having issues getting my data to work on Verizon.
Click to expand...
Click to collapse
Mine: http://forum.xda-developers.com/showpost.php?p=68263623&postcount=61
So frustrating. Before update used today Verizon in upper left corner. Switched to 123456 after update. Rebooted and it went back. After another reboot it only says 123456 and nothing I do will change it back. And now when I get an MMS hangouts tells me it needs to download it but nothing happens. I never get LTE anymore either.
Edit: not sure what I did but it's back now. Might have something to do with bearer in apn settings being lte.
KyJelly69 said:
So frustrating. Before update used today Verizon in upper left corner. Switched to 123456 after update. Rebooted and it went back. After another reboot it only says 123456 and nothing I do will change it back. And now when I get an MMS hangouts tells me it needs to download it but nothing happens. I never get LTE anymore either.
Edit: not sure what I did but it's back now. Might have something to do with bearer in apn settings being lte.
Click to expand...
Click to collapse
That's #9 in the above list that was posted. Need to cycle the modem state of the device.
so, can someone help me with a little clarification? did ZTE ever actually disable anything regarding Verizon on this phone? i know when people quote the webinar, it sounded like they were going to. i understand that the functionality is basically all still working, but i'm wondering if maybe i'm confused on the terminology.
in this post on reddit, i heard the same thing that has been repeated by some, and i am wondering if i have my band terminology confused. is the cdma part different from the 4g lte part(and that's why it's still working)?, or is sarah just incorrect?
SarahSchmera 3 points 9 hours ago
Axon 7
Doesn't work on Verizon yet. It supposedly has CDMA radios but the radio firmware has them disabled. ZTE can't by law enable the CDMA radios because they didn't get FCC approval for the CDMA radios. They would have to pay for the testing and then resubmit the device to the FCC to get approval before they turned on the CDMA radios through a software update.
And the device doesn't have the firmware for VoLTE, HD calling or WiFi calling on Verizon.
Click to expand...
Click to collapse
First thing first, I have sent the unlocked S8 (bought unlocked directly from Samsung) back to repair center for the issue. The phone was returned to me, claimed to be repaired, with the same issue. While I submitted another ticket to send it back again, I believe the devs here may have better solutions than the incompetent technicians at Samsung repair center. I need help!
Description of Issue
Before routine phone reboot
• AT&T compatible SIM (Cricket) worked on the S8.
• Verizon compatible SIM (Red Pocket) worked on the S8.
After routine phone reboot
• AT&T compatible SIM still worked on the S8.
• Verizon compatible SIM couldn’t register on Verizon’s network on the S8. However, the SIM could register on Verizon and make phone calls on another two phones.
• Verizon SIM worked on the S8.
I was instructed by a Samsung technician through chat to
a) do a network reset
b) enter safe mode
c) do a factory reset
None of the above worked. No setting (APN or whatnot) is required for the AT&T compatible or Verizon compatible SIM to work. In short, the Verizon compatible SIM is working properly and the S8 is not blacklisted by Verizon. The S8 just doesn’t work with the Verizon compatible SIM after a reboot.
After the repair
I just received the S8 from the repair center from the previous ticket. I inserted the Red Pocket SIM to S8 and the phone still couldn’t register it on Verizon’s network. I inserted the same SIM to another phone and the phone received messages from Red Pocket right away and showed it was on Verizon’s network. In short, the same issue remained.
Even though I'm sending the S8 back to Samsung for repair, given my first repair experience, I don't have much confidence in their technicians in fixing this. Any input is much appreciated!
Did you figure this out? I am having the exact identical issue and ready to go nuts trying to figure it out. Any help would be great!
willjob said:
Did you figure this out? I am having the exact identical issue and ready to go nuts trying to figure it out. Any help would be great!
Click to expand...
Click to collapse
Unfortunately, I haven't. But I do have updates. I sent the phone back for a second repair. The phone came back with the same problem. No surprise at all. One thing I noticed though, from the service record, the technician replaced a third component (the other two were the same as that of the first service). Not sure if this made a difference, I did see "Verizon Wireless" on the status bar when I turned the phone on with the Red Pocket SIM. This was the first time I saw the "Verizon Wireless" after the reboot. However, while I was turning it on, the S8 mandated a reboot to "get the SIM card ready." And man... that reboot just reverted everything to before.
I was on the phone with a Samsung representative and a supervisor after I discovered the phone was not fixed for the second time. While he promised to make a note to the repair center about my situation, the supervisor said the option of a replacement phone wouldn't kick in until 3 or 4 unsuccessful repairs. Frustrated as I was, I've got no choice but to send it back for a third repair.
Hope you have better luck with yours.
willjob said:
Did you figure this out? I am having the exact identical issue and ready to go nuts trying to figure it out. Any help would be great!
Click to expand...
Click to collapse
Unfortunately, I haven't. But I do have updates. I sent the phone back for a second repair. The phone came back with the same problem. No surprise at all. One thing I noticed though, from the service record, the technician replaced a third component (the other two were the same as that of the first service). Not sure if this made a difference, I did see "Verizon Wireless" on the status bar when I turned the phone on with the Red Pocket SIM. This was the first time I saw the "Verizon Wireless" after the reboot. However, while I was turning it on, the S8 mandated a reboot to "get the SIM card ready." And man... that reboot just reverted everything to before.
I was on the phone with a Samsung representative and a supervisor after I discovered the phone was not fixed for the second time. While he promised to make a note to the repair center about my situation, the supervisor said the option of a replacement phone wouldn't kick in until 3 or 4 unsuccessful repairs. Frustrated as I was, I've got no choice but to send it back for a third repair.
Hope you have better luck with yours.
Thanks for the reply. The phone I was having problems with was an S8+. My wife's phone is an s8. I didn't have any problems on Red Pocket CDMA for the first week of service. That was until this morning. Exact same thing on my S8+ and what you describe above. On another forum someone said this is a problem with Samsung devices on Verizon MVNOs.
I just switched both to GSMA for now until I figure out to switch from Red Pocket.
willjob said:
Thanks for the reply. The phone I was having problems with was an S8+. My wife's phone is an s8. I didn't have any problems on Red Pocket CDMA for the first week of service. That was until this morning. Exact same thing on my S8+ and what you describe above. On another forum someone said this is a problem with Samsung devices on Verizon MVNOs.
I just switched both to GSMA for now until I figure out to switch from Red Pocket.
Click to expand...
Click to collapse
Thanks for sharing, especially on Verizon MVNOs. GSM (Cricket) has no signal at all in many locations around where I live and work. If Samsung still couldn't fix my S8 after a couple more tries or even with a replacement phone, I will have to opt for the Verizon MVNO theory and buy a different phone. Heck, my $40 Moto E4 works just fine on both Cricket and CDMA Red Pocket.
I have the same issue my believe is red pocket does not have LTE/CDMA in their sim they have LTE/2g/3g 2g/3g and 2g only they should have LTE/CDMA instead of LTE/2g/3g to work,
xike17 said:
First thing first, I have sent the unlocked S8 (bought unlocked directly from Samsung) back to repair center for the issue. The phone was returned to me, claimed to be repaired, with the same issue. While I submitted another ticket to send it back again, I believe the devs here may have better solutions than the incompetent technicians at Samsung repair center. I need help!
Description of Issue
Before routine phone reboot
• AT&T compatible SIM (Cricket) worked on the S8.
• Verizon compatible SIM (Red Pocket) worked on the S8.
After routine phone reboot
• AT&T compatible SIM still worked on the S8.
• Verizon compatible SIM couldn’t register on Verizon’s network on the S8. However, the SIM could register on Verizon and make phone calls on another two phones.
• Verizon SIM worked on the S8.
I was instructed by a Samsung technician through chat to
a) do a network reset
b) enter safe mode
c) do a factory reset
None of the above worked. No setting (APN or whatnot) is required for the AT&T compatible or Verizon compatible SIM to work. In short, the Verizon compatible SIM is working properly and the S8 is not blacklisted by Verizon. The S8 just doesn’t work with the Verizon compatible SIM after a reboot.
After the repair
I just received the S8 from the repair center from the previous ticket. I inserted the Red Pocket SIM to S8 and the phone still couldn’t register it on Verizon’s network. I inserted the same SIM to another phone and the phone received messages from Red Pocket right away and showed it was on Verizon’s network. In short, the same issue remained.
Even though I'm sending the S8 back to Samsung for repair, given my first repair experience, I don't have much confidence in their technicians in fixing this. Any input is much appreciated!
Click to expand...
Click to collapse
Update:
No. This problem was not fixed by Samsung after three repairs.
I ordered a new Verizon SIM from Red Pocket during the third repair. Samsung didn't replace anything in the third. I received the phone and popped in the new SIM and the phone could register the SIM on Verizon! I even tried a couple of restarts (which caused the problem in the first place) and everything seemed fine. I even blamed myself for bashing Samsung technicians' incompetence. How stupid was I to blame myself and how naive was I to believe Samsung technician had actually delivered...
It's the fourth or fifth day I've been using the phone and the new SIM. The battery died after a long day. When I returned home and charged the phone, the S8 needed to "reconfigure" the SIM, which prompted for an automatic reboot. Voila! The same pesky unable-to-register-on-Verizon issue came right back. The phone is now in the process of a replacement. I honestly don't hold much hope for the replacement that I'm awaiting. Perhaps I should consider selling off the phone or asking Samsung for a refund.
Confirmed s8 doesn't work on the budget Verizon mnvo's
I just switched from the att sim on red pocket to the Verizon sim with no luck. I found a temporary fix. When prompt to restart to configure network, press the power button and go into emergency mode. Then restart from there. May take a couple of tries but the prompt disappeared. Then switch back to regular mode. I was able to use the phone on Verizon but can only get 3g speeds. This all goes away the moment you restart the phone as the moment the confirmation takes it won't recognize the Verizon networks. This is a cheap Verizon service. You can see your options for network mode are lte/3g/2g. Not the typical lte/cdma. Also tried boom mobile, and that sort of worked but my texts would not go out and again no fix. I'm convinced this is purely Verizon restricting needed services that the s8 requires. The att sim works perfectly. Most phones are fine, not the newer Galaxy.
nytq said:
I just switched from the att sim on red pocket to the Verizon sim with no luck. I found a temporary fix. When prompt to restart to configure network, press the power button and go into emergency mode. Then restart from there. May take a couple of tries but the prompt disappeared. Then switch back to regular mode. I was able to use the phone on Verizon but can only get 3g speeds. This all goes away the moment you restart the phone as the moment the confirmation takes it won't recognize the Verizon networks. This is a cheap Verizon service. You can see your options for network mode are lte/3g/2g. Not the typical lte/cdma. Also tried boom mobile, and that sort of worked but my texts would not go out and again no fix. I'm convinced this is purely Verizon restricting needed services that the s8 requires. The att sim works perfectly. Most phones are fine, not the newer Galaxy.
Click to expand...
Click to collapse
Thanks for the workaround. I'll give a shot when I receive the replacement. Meanwhile, I have been using an unlocked prepaid Verizon Moto E4 and everything works fine. I have 4G with the E4. I can also receive multimedia text. A $40 budget phone works better for my needs than a $700 factory unlocked premium phone. How ironic!
I have the same problem
I have a fully-paid-for Galaxy S8 from a Verizon account with good standing, and service on this particular line is ended. It worked on Redpocket until I took the sim out to insert an SD card. Afterwards it reconfigured the sim and lost network access. The sim works in my iPhone and the original Verizon sim works in the S8 and the phone states its ready to set up a Verizon account.
The third Redpocket support agent I contacted sent me a screenshot listing an error "DISCOUNT_4_ACCESS". He stated that means Verizon is blocking it for some reason but he doesn't have access to the reason. Two Verizon agents couldn't even tell if they were blocking it or not - but as far as they could tell everything was good.
According to an article on Whistleout, Verizon MVNO requirements are that the "phone must be network compatible, financially unencumbered, and not less than 12 months old (though this last policy changes from time to time)" Could our phones be blocked because they were sold less than 12 months ago?
Leecewest said:
I have a fully-paid-for Galaxy S8 from a Verizon account with good standing, and service on this particular line is ended. It worked on Redpocket until I took the sim out to insert an SD card. Afterwards it reconfigured the sim and lost network access. The sim works in my iPhone and the original Verizon sim works in the S8 and the phone states its ready to set up a Verizon account.
The third Redpocket support agent I contacted sent me a screenshot listing an error "DISCOUNT_4_ACCESS". He stated that means Verizon is blocking it for some reason but he doesn't have access to the reason. Two Verizon agents couldn't even tell if they were blocking it or not - but as far as they could tell everything was good.
According to an article on Whistleout, Verizon MVNO requirements are that the "phone must be network compatible, financially unencumbered, and not less than 12 months old (though this last policy changes from time to time)" Could our phones be blocked because they were sold less than 12 months ago?
Click to expand...
Click to collapse
Thanks for sharing this. I bought a Moto E4 around February, a Verizon postpaid (or prepaid?) from Walmart and got it unlocked through eBay. This is the phone I'm using with Red Pocket now. The phone is of course less than 12 months old. One thing to mention is when I asked Red Pocket support to activate a new SIM with the E4, I was told because the phone was Verizon branded (post/prepaid) they could not activate the phone with the SIM. Then I told them I had success before. The rep further said the service would be deactivated once their system detected the phone was Verizon branded. Well, it turned out this rep knew nothing. I ended up using IMEI of another phone to activate the line then inserted the SIM in the E4. And I have been using the E4 ever since without a single issue (network-wise).
Wow, so i wasn't the only one. Had the exact same problem. Ported my number from Red Pocket Verizon to Red Pocket AT&T. Now everything is fine.
When I switch from a Verizon SIM to my Red Pocket-Verizon SIM the phone comes up with "SIM card changed" but the phone receives incoming calls and notifications (wi-fi is off). Unfortunately, the only thing that I can do with the "SIM card changed" message showing is answer phone calls - I cant even turn "Emergency mode" on. Could it be that Red Pocket SIM messes up the configuration? One of the first things Red Pocket support wants to check is if the phone is in CDMA mode, but with the Red Pocket sim inserted modes are limited to LTE/3G/2G. The Verizon SIM gives CDMA options.
With the Verizon SIM in and configured, switch to "Emergency Mode". Replace the Verizon SIM with the Red Pocket SIM without turning the phone off. Turn "Emergency Mode" off. The phone doesn't detect the SIM change, but it shows the ICCID of the Red Pocket SIM and correct phone number. Data works, 4G LTE. Of course, the first power cycle it detects the SIM change and messes up the configuration.
Another update: Received an unlocked S9 (yes, because Samsung is out of unlocked S8 inventory) two days ago. Inserted Red Pocket Verizon... the phone couldn't register the SIM on Verizon at all in my first try. This is the end of my journey with Samsung phones. I hope one day this issue can be addressed and solved.
Am having the same red-pocket/Verizon/S8 problem. Too bad I did not see this first.
I have tried almost everything (barring having a different network Sim Card) to have my phone request me to restart the phone on inserting new sim. It appears the last network is saved somewhere and my unlocked/unbrand S8 does not seem to forget it.
Is there a way where I can force the phone to request a restart if I re-insert the Sim card. Thanks
fnkhan said:
Am having the same red-pocket/Verizon/S8 problem. Too bad I did not see this first.
I have tried almost everything (barring having a different network Sim Card) to have my phone request me to restart the phone on inserting new sim. It appears the last network is saved somewhere and my unlocked/unbrand S8 does not seem to forget it.
Is there a way where I can force the phone to request a restart if I re-insert the Sim card. Thanks
Click to expand...
Click to collapse
My understanding is that Galaxy S8s are configured wrong when Red-Pocket (and other Verizon MVNO) SIMs are inserted - they aren't fully set to the Verizon network and if your phone had, for example, and AT&T SIM, the phone stays AT&T branded when a Red-Pocket Verizon SIM is inserted.
The work-around:
1) Insert a Verizon SIM and let it setup everything and reboot when it wants.
2)Turn on "Emergency mode" (Hold down the power button and select "Emergency mode")
3)Insert Red-Rocket SIM
4)Turn "Emergency mode" off
*If you reboot after inserting the Red-Pocket SIM the phone will become wrongly-configured and you'll need to do the work-around again.
Leecewest said:
My understanding is that Galaxy S8s are configured wrong when Red-Pocket (and other Verizon MVNO) SIMs are inserted - they aren't fully set to the Verizon network and if your phone had, for example, and AT&T SIM, the phone stays AT&T branded when a Red-Pocket Verizon SIM is inserted.
The work-around:
1) Insert a Verizon SIM and let it setup everything and reboot when it wants.
2)Turn on "Emergency mode" (Hold down the power button and select "Emergency mode")
3)Insert Red-Rocket SIM
4)Turn "Emergency mode" off
*If you reboot after inserting the Red-Pocket SIM the phone will become wrongly-configured and you'll need to do the work-around again.
Click to expand...
Click to collapse
Thanks for the update. Yes - if I can only get hold of a non Red-pocket Sim, this can work. Since I don't have Verizon (or any other) Sim card, I was wondering if there is some other workaround to have the phone request me to restart. I suppose I would still need Verizon Sim since it uses that to configure the network.
Looking at another thread - it appears the 'configuration' that Verizon sim card does has to do with CSC codes. My phone is unbranded, so the codes are XAA (Firmware) and XAA (Network). I believe the latter has to be VZW and a Verizon Sim fixes that. Someone who has successfully used the workaround can confirm what codes are being displayed at their end. I am using 'phone info' app. Then maybe we can work to find another workaround ....
My S8 is Verizon branded. It CSC is currently VZW. Under "Service provider SW ver." its VZW/VZW/VZW.