Related
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
nectur said:
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
Click to expand...
Click to collapse
If the phone was used on another carrier it might be stuck in a non lte/CDMA mode. Flash stock vzw ruu. Do a factory reset. Go into mobile settings and make sure it's set to global. Then see if default network is set to vzw. Then check provisioning.
That did it. Thanks!
nectur said:
That did it. Thanks!
Click to expand...
Click to collapse
Np...bought an m8 for my dad a couple months back and same thing happened. I finally realized it was used on a different carrier.
I bought HTC U11 phone locked to sprint last week, unlocked and confirmed that it was unlocked.
Rooted the phone and installed VIPER ROM, I am presently using ATT in US, there is service, but mobile data shows disconnected.
I checked the access point details and discovered it was actually enabled.
I tried configuring it manually and no change at all
I tried with T-Mobile and shows connected.
I don't know why am having issue with ATT, I can make calls perfectly.
When you insert the sim card you should be prompted for network selection. Check you are using the correct apn settings as some carriers have different ones for different types of tarriff.
Failing that, speak to att. They might be aware of specific problems when migrating.
shivadow said:
When you insert the sim card you should be prompted for network selection. Check you are using the correct apn settings as some carriers have different ones for different types of tarriff.
Failing that, speak to att. They might be aware of specific problems when migrating.
Click to expand...
Click to collapse
Hello I am new to this forum. I did a search and your post was first I saw. I bought an HTC 10 from a girl and went to put my Verizon sim card in and it says to contact Sprint for unlock code. Well I can't reach the girl who sold me the phone I can't root it if u could please help any advice would be appreciated. I have a hand written receipt from the girl but her #s disconnected. I've downloaded the twrp and super something also kingo root and can't get it rooted or get the s off turned on as it says s on. My email is [email protected] I'll check back as I said I'm new to this forum so still learning to use it. Sigh I have 2 other phones that a friend wanted me to fix. They did a hard reset and don't remember there Gmail set up with the phones. Right now this HTC is my main concern
So what are you trying to do, unlock simlock or root it?..
To root the phone you need to start at htcdev website and follow unlock bootloader. Then flash twrp then supersu. Bin kingoroot. It's crap.
Not sure you can manually unlock simlock. Might have to get the code off sprint.
olalekanbabs said:
I bought HTC U11 phone locked to sprint last week, unlocked and confirmed that it was unlocked.
Rooted the phone and installed VIPER ROM, I am presently using ATT in US, there is service, but mobile data shows disconnected.
I checked the access point details and discovered it was actually enabled.
I tried configuring it manually and no change at all
I tried with T-Mobile and shows connected.
I don't know why am having issue with ATT, I can make calls perfectly.
Click to expand...
Click to collapse
Make sure roaming and digital roaming is off. I had the same issue.
I spent over 2 hours last nite with att reps trying to enable numbersync to work between the s3 and s8 phones.. the s8 phone is an unlocked phone (not bought through att), only to find out today via another rep that the phone must be bought via ATT or truly att branded.. which i find a bit absurd, as i think others have succeeded..
Is this really the case.. anyone know or have this same experience?
Specifically this error would appear after going through the get started via the watch then on the phone (after creating a seperate accessid):
Oh darn! We can't enable device syncing on this phone. Want to find out more? Call us at 800.331.0500 so we can help.
(MSSITWINREL12)
If this turns out to really be an unlocked phone issue (which is a bit ridiculous), i think i read that it might be possible to take my sim card out of that phone and put in another phone that is att branded, enable number sync then put the card back in my s8 and go from there
Thanks
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
pasco8525 said:
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
Click to expand...
Click to collapse
Thanks for the reply.. your saying you had an unlocked tmobile phone on att and it was working till a recent tizen update then?
The rep further told me to take the phone to the best buy samsung experience store and have it flashed with the att firmware to get around this issue.. maybe not needed then? (which i assume means a wipe and possibly lose my unlock)
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
karlkarloff said:
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
Click to expand...
Click to collapse
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
markm75 said:
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
Click to expand...
Click to collapse
.
When I first bought the watch it was for the numbersync feature. My first problem was even though the Samsung rep and the bestbuy rep said that it would work with my Note3, it did not. took several calls and many hours of trying to figure out the HD Voice (VOlte) provisioning. Bought a TMobile Note 4, rooted and rom'ed this worked to setup numbersync. the only problem was it would occasionally turn off numbersync, this occurred about once a month. Then if failed completely said that this line is not accceptabl;e for numbersync. this was after about six months. Discovered that it appeared to be age of firmware related, I was on a TM firmware that was several updates out of date. When I odin flashed the latest firmware numbersync worked again until the recent update to 3.0.0.1 on the gear firmware. Now I have the line not acceptable for numbersync again. I'm going to try to update firmware again to see if that works. If not I will probably look to change carriers to TM. will cost the price of a new watch, but will get me out of AT&Ts locked boot loader.
BTW, setting up numbersync on a different phone and switching back will not work, Tried several times and as soon as you turn on the phone that is not HD Voice capable with your SIM card in it the system sees it and turns off numbersync almost instantly. went throught that trying to get my Note 3 to work.
In all my experience the Samsung and AT&T reps were not a good resource. Numbersync does not appear to be a very popular feature and they do not know much about it.
pasco8525 said:
.
When I first bought the watch it was for the numbersync feature. .
Click to expand...
Click to collapse
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
markm75 said:
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
Click to expand...
Click to collapse
Yes, that is the whole point of numbersync. The watch uses the phones number not it's own.
Tried updating to the latest firmware and a ROM based on it. No luck still get a rather comical response "Oh darn! We can't enable device syncing on this phone. " worked until the tisen update.
There also seems to be confusion on numbersync with the att reps.. one person told me the watches dont need their own numbers.. that numbersync is all we need (but how would the watch make a call if the phone is off).. another said yes they need external numbers for number sync or solo
edit: i see your last post.. so the latest reps are correct then.... so they assigned us numbers and $10 access fees each with activation fees for no reason basically.. ugh
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Just a quick note...i too spent 3 hours in an AT&T store trying to get numbersync to work..., finally returned the S3 Frontier cancelled the number in it and left frustrated...i now have a GS8 unlocked on AT&T through my work...that is synced to a Verizon Gear S3 Classic lte and i simply use call forwarding with YouMail. If i do not answer my phone after 3 rings it gets sent to my watch and if I still do not answer then Youmail picks it up..If I call out or text with the watch separately then I just let my customers know that I have 2 numbers 1 for my cell and one for their watch. I just don't think AT&T is ready for the Numbnersync technology yet and they just don't care enough to train their own people on it, sad as it is a good promise...
Sent from my iPad using Tapatalk
pasco8525 said:
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Click to expand...
Click to collapse
I meant phone number.. are you saying phone number? After the rep said i didnt need a phone number for each watch, she credited me back the cost of the two lines and said just to contact them that they would enable the numbersync once i had the phones ready.. I'm assuming number means imei, which they still have in the system.
Yes each watch has to have it's own phone number. I believe this is another case of AT&T rep not understanding number sync.
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
markm75 said:
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
Click to expand...
Click to collapse
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
markm75 said:
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
Click to expand...
Click to collapse
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
eaglerugby04 said:
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
Click to expand...
Click to collapse
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
Thanks. It sounds like the latest firmware they did seems to fix some of the issues from bringing a non-ATT phone over but does not resolve everything. It looks like I won't be able to do this though. ATT and the ebay seller are unable to clear the ICCID on my watch, I have to sadly do a return now.
Kinda unrelated, yet ATT was horrible even for normal Sammy phone/watch. After dumping ATT service/hardware for various reasons a few moths back... Sammy watch/phone from Verizon hardware/service works flawlessly. Am carrier neutral, but one works reliably, one didn't.
BTW, Sammy pay via watch hiccuped via ATT at times, yet works flawless via Verizon.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
well 5 chat people later they finally fixed the unknown callerid issue.. apparently there is an internal back end feature for numbersync regarding it set to active and on.. both toggles were on.. the rep removed the "on" and now my callerid shows my number when calling from my phone (and from the watch when watch is in solo mode too).. everything works! :laugh:
If you're using either Straight Talk, or Tracfone with their Verizon SIM, I would avoid the Unlocked Pixel 7 & 7 Pro for right now. I'm not sure if it's the phones themselves, or an issue with the carrier, or a combination of both, but it seems they're not compatible. I got my 7 Pro on Wednesday and tried using my ST Verizon SIM and it wouldn't work. I'm coming from a Oneplus 9 Pro and the SIM works just fine.
I say it could be an issue with either the phone, or with ST/TF because when I contacted Google Support to initiate an exchange, the only phone they would let me order with my RMA was the Google Fi version. I contacted support again about not being able to order the Unlocked version. I sent them a screenshot of my order email and a picture of the phones box with the SKU, all of which pointed to the phone being the Unlocked version. They agreed and I'm now waiting for them to resolve the issue of me not being able to buy the Unlocked version through my RMA request. So maybe there could be an issue on Googles end with the Unlocked version of the pixel 7/7 Pro.
I also say it could be an issue with ST/TF, becasue Verizon has recently bought Tracfone and all of their subsidiaries, Straight Talk being one of them. Because of this, I'm not sure if they've basically merged the services to the point where you would need the Verizon version of the phone in order for it to work. This is just speculation on my part though. I did contact Straight Talk support first, where they checked my IMEI/ICCID numbers, which matched what they were seeing on their end. They also ran me through the usual troubleshooting list, with nothing fixing the issue.
Here's a link to a couple threads with people having the same issue. The first one is one I posted the other day:
https://reddit.com/r/GooglePixel/comments/y2erhe/is_anyone_else_using_a_straight_talk_verizon_sim/
https://reddit.com/r/StraightTalk/comments/y3cq9s/upgrading_to_pixel_7_byop/
If anyone is actually using a Straight Talk/Tracfone Verizon SIM in their P7/P7 Pro, please, leave a comment and let me know how you got it to work..
wellkevi01 said:
If you're using either Straight Talk, or Tracfone with their Verizon SIM, I would avoid the Unlocked Pixel 7 & 7 Pro for right now. I'm not sure if it's the phones themselves, or an issue with the carrier, or a combination of both, but it seems they're not compatible. I got my 7 Pro on Wednesday and tried using my ST Verizon SIM and it wouldn't work. I'm coming from a Oneplus 9 Pro and the SIM works just fine.
I say it could be an issue with either the phone, or with ST/TF because when I contacted Google Support to initiate an exchange, the only phone they would let me order with my RMA was the Google Fi version. I contacted support again about not being able to order the Unlocked version. I sent them a screenshot of my order email and a picture of the phones box with the SKU, all of which pointed to the phone being the Unlocked version. They agreed and I'm now waiting for them to resolve the issue of me not being able to buy the Unlocked version through my RMA request. So maybe there could be an issue on Googles end with the Unlocked version of the pixel 7/7 Pro.
I also say it could be an issue with ST/TF, becasue Verizon has recently bought Tracfone and all of their subsidiaries, Straight Talk being one of them. Because of this, I'm not sure if they've basically merged the services to the point where you would need the Verizon version of the phone in order for it to work. This is just speculation on my part though. I did contact Straight Talk support first, where they checked my IMEI/ICCID numbers, which matched what they were seeing on their end. They also ran me through the usual troubleshooting list, with nothing fixing the issue.
Here's a link to a couple threads with people having the same issue. The first one is one I posted the other day:
https://reddit.com/r/GooglePixel/comments/y2erhe/is_anyone_else_using_a_straight_talk_verizon_sim/
https://reddit.com/r/StraightTalk/comments/y3cq9s/upgrading_to_pixel_7_byop/
If anyone is actually using a Straight Talk/Tracfone Verizon SIM in their P7/P7 Pro, please, leave a comment and let me know how you got it to work..
Click to expand...
Click to collapse
I am having the same issue with the phone reading the SIM Data just fine but will not connect to any cell towers, I did a bunch of research and there are several people with this same issue and some report doing a software update on the phone resolved their problem. I have not been as lucky as these people as I still have the issue with my phone.
As for the "Verizon" version of the phone there is no such thing for the P7P as the unlocked version and verizon version are the same model number for the phone which includes the 5G mmWave.
The update takes over an hour so be prepared for that
Anubis366 said:
I am having the same issue with the phone reading the SIM Data just fine but will not connect to any cell towers, I did a bunch of research and there are several people with this same issue and some report doing a software update on the phone resolved their problem. I have not been as lucky as these people as I still have the issue with my phone.
As for the "Verizon" version of the phone there is no such thing for the P7P as the unlocked version and verizon version are the same model number for the phone which includes the 5G mmWave.
The update takes over an hour so be prepared for that
Click to expand...
Click to collapse
Oh yea, I already tried the update(didn't fix the issue) the other day, and yes, it took over an hour to install.
There are lots of compatibility issues. I tried signing up for eSIM on a bunch of MVNOs and prepaid plans last night and to my amazement the only one that worked was AT&T Prepaid -- and it's not supposed to work with Pixels on the activation portal.
wellkevi01 said:
If you're using either Straight Talk, or Tracfone with their Verizon SIM, I would avoid the Unlocked Pixel 7 & 7 Pro for right now. I'm not sure if it's the phones themselves, or an issue with the carrier, or a combination of both, but it seems they're not compatible. I got my 7 Pro on Wednesday and tried using my ST Verizon SIM and it wouldn't work. I'm coming from a Oneplus 9 Pro and the SIM works just fine.
I say it could be an issue with either the phone, or with ST/TF because when I contacted Google Support to initiate an exchange, the only phone they would let me order with my RMA was the Google Fi version. I contacted support again about not being able to order the Unlocked version. I sent them a screenshot of my order email and a picture of the phones box with the SKU, all of which pointed to the phone being the Unlocked version. They agreed and I'm now waiting for them to resolve the issue of me not being able to buy the Unlocked version through my RMA request. So maybe there could be an issue on Googles end with the Unlocked version of the pixel 7/7 Pro.
I also say it could be an issue with ST/TF, becasue Verizon has recently bought Tracfone and all of their subsidiaries, Straight Talk being one of them. Because of this, I'm not sure if they've basically merged the services to the point where you would need the Verizon version of the phone in order for it to work. This is just speculation on my part though. I did contact Straight Talk support first, where they checked my IMEI/ICCID numbers, which matched what they were seeing on their end. They also ran me through the usual troubleshooting list, with nothing fixing the issue.
Here's a link to a couple threads with people having the same issue. The first one is one I posted the other day:
https://reddit.com/r/GooglePixel/comments/y2erhe/is_anyone_else_using_a_straight_talk_verizon_sim/
https://reddit.com/r/StraightTalk/comments/y3cq9s/upgrading_to_pixel_7_byop/
If anyone is actually using a Straight Talk/Tracfone Verizon SIM in their P7/P7 Pro, please, leave a comment and let me know how you got it to work..
Click to expand...
Click to collapse
Pixel 7 with the Straight Talk Verizon SIM here. Works fine on my Pixel 6.
I also tried the latest Pixel 7 software update, and it did not resolve the issue.
For what it's worth, I just contacted Google support. The representative told me they did not have any reports of this issue yet. I directed them to this post as well as another under the GooglePixel subreddit and one under the StraightTalk subreddit. I submitted all of my information to them and sent screenshots of the SIM not connecting. They are escalating the issue.
jidoohanbaiki said:
Pixel 7 with the Straight Talk Verizon SIM here. Works fine on my Pixel 6.
I also tried the latest Pixel 7 software update, and it did not resolve the issue.
For what it's worth, I just contacted Google support. The representative told me they did not have any reports of this issue yet. I directed them to this post as well as another under the GooglePixel subreddit and one under the StraightTalk subreddit. I submitted all of my information to them and sent screenshots of the SIM not connecting. They are escalating the issue.
Click to expand...
Click to collapse
Just took my phone back to Best Buy. They had some more in stock so I tried another one straight out of the box without doing the update and that one is not reading my SIM and connecting to the towers either..
Google Fi sim has issues for me. Flashed latest Oct factory and BL unlock and root. Let sit overnight and installed sim. Looks like at moment of sim registration to cellular enabling it causes a reboot. Tried a few times and sometimes airplane mode would be on, and no sim (blank) or times just bootloop cycling. Removing sim, bootloop cycling stopped. Then airplane mode, but wifi can be on. So reflash latest again, no root. Same thing happening.
Support still clueless and escalation has begun.
Sim back in my 6a and all is fine.
I do know some data is pushed into system upon a Fi sim insertion been that way since my pixel 3. My local coverage is us cellular which requires a locked BL, but fortunately on Fi it works without a locked BL.
So thought to add, likely we need a immediate G side update...
https://www.reddit.com/r/TotalWireless/comments/xzfacx/pixel_7_pro/
https://www.reddit.com/r/TotalWireless/comments/y405wm/pixel_7_pro_issues/
Same issues with Total by Verizon (Total Wireless, another former tracfone) on my Pixel 7 as well as many others. Multiple sims and another carrier sim verified working in my phone.
Cross-posting this from reddit-
Brief update for everyone in the thread or lurking- Talked to Google support just now.
The tech I spoke explained that this is now a known widespread issue that has been escalated and is "top priority" (his words) for the engineers.
He documented my IMEI and added it to the ongoing ticket. I should be getting a follow-up email sometime in the future when a workaround is found.
I'd recommend calling to do the same ASAP to make sure that they are aware how widespread the issue is.
kkjb said:
Google Fi sim has issues for me. Flashed latest Oct factory and BL unlock and root. Let sit overnight and installed sim. Looks like at moment of sim registration to cellular enabling it causes a reboot. Tried a few times and sometimes airplane mode would be on, and no sim (blank) or times just bootloop cycling. Removing sim, bootloop cycling stopped. Then airplane mode, but wifi can be on. So reflash latest again, no root. Same thing happening.
Support still clueless and escalation has begun.
Sim back in my 6a and all is fine.
I do know some data is pushed into system upon a Fi sim insertion been that way since my pixel 3. My local coverage is us cellular which requires a locked BL, but fortunately on Fi it works without a locked BL.
So thought to add, likely we need a immediate G side update...
Click to expand...
Click to collapse
I am using it on Fi coming from my Pixel 4 XL. Instead of moving the sim card from my old phone I decided to use eSIM with this one and leave the card in the old one and it's working perfectly.
Excellent news ....for some.
I have many many devices on at any one moment and using the SIM vs eSIM allows me to keep the other non-phone devices on. Yes I could disable eSIM and still leave on. Unfortunately since I also reboot, flash different modules, roms, and in general leave only one as the sim activated device... Honestly if this is now a new thing, disclosure would be nice. No other pixel I've owned requires eSIM only. I will have to rethink my G. Fi future. Fortunately I'm now free of Fi device payments for purchase.
Edit update-- Seems on a Google Fi SIM that was used on my pixels 3, 4a, 4a5g, 6, 6a (2) working just fine...was the problem with 7 pro.
No good answer from Fi CS but they said to use a never used Fi sim. Which I had on hand.
Normal first SIM start and log in, works fine on 7 pro. Removed and now back on my 6a and working correctly. I guess... something is provisioned on carrier/sim/ install?
My answer is likely only helpful for Fi user base.
Total by Verizon (formerly total wireless). Having same issue. Pixel 7 won't connect to network, I've worked with their tech support for the past 18 hours with no luck. At this point I've reverted back to using my old phone and if this doesn't get resolved in the next week or so, I will be returning my pixel 7 as it's no use to me in its current form.
Semi-interesting thing.
I found an old straight talk AT&T SIM so I tried to activate that.
The Straight talk site accepted the SIM card number, but my IMEI was rejected. Either they are flat out saying it is incompatible now or ST has temporarily stopped Pixel 7 devices from attempting to activate until it's fixed. At least they seem to be aware?
Here's the message-
Our system shows that your phone will not work with Straight Talk’s service. Do you have another handset you would like to try? Or you can always check out our phone store to see what's available for purchase.
Click to expand...
Click to collapse
Go to prepaidcompare.net and find a new MVNO. All the TracFone brands have gone to hell since Verizon took them over.
I know some will not care to hear this, but it's probably worth posting (for the sake of those readers who might be wondering) that prepaid Verizon is indeed working without issue.
This isn't a vote or an ad for VZW.
I usually go with whatever is least expensive that meets my needs (Red Pocket, Straight Talk, Mint, Google Fi, Visible have all gotten my business at some point) but VZW is the only carrier with decent coverage at my current workplace.
I'm in the same boat of needing Verizon. I plan to check out US Mobile. Good pricing and esim capable (working with P7P, not with P7 right now) alont with a 10 day trial.
reaper000 said:
I know some will not care to hear this, but it's probably worth posting (for the sake of those readers who might be wondering) that prepaid Verizon is indeed working without issue.
This isn't a vote or an ad for VZW.
I usually go with whatever is least expensive that meets my needs (Red Pocket, Straight Talk, Mint, Google Fi, Visible have all gotten my business at some point) but VZW is the only carrier with decent coverage at my current workplace.
Click to expand...
Click to collapse
Are you locked or unlocked? Would be nice to know, unlockable device is my requirements. Having another good signal provider for my home would be nice, currently Verizon is one.
I couldn't in the past get Verizon because of the locked part...
reaper000 said:
I know some will not care to hear this, but it's probably worth posting (for the sake of those readers who might be wondering) that prepaid Verizon is indeed working without issue.
This isn't a vote or an ad for VZW.
I usually go with whatever is least expensive that meets my needs (Red Pocket, Straight Talk, Mint, Google Fi, Visible have all gotten my business at some point) but VZW is the only carrier with decent coverage at my current workplace.
Click to expand...
Click to collapse
FWIW, US Mobile Warp 5G SIM uses Verizon (and even gets the same priority Verizon postpaid customers get if you use a 5G device unlike Verizon prepaid which is deprioritized to last network priority) and I was even able to activate my eSIM on their service with no problem.
Unfortunately, Verizon sucks here, so the trial is going to go to waste, but I tried a bunch of MVNO and carrier prepaid options and only AT&T Prepaid and US Mobile worked.
kkjb said:
Are you locked or unlocked? Would be nice to know, unlockable device is my requirements. Having another good signal provider for my home would be nice, currently Verizon is one.
I couldn't in the past get Verizon because of the locked part...
Click to expand...
Click to collapse
The Pixel 7 Pro supports all of Verizon's bands including mmWave no matter if you get it locked from them or unlocked elsewhere. Verizon added the Pixel 7 Pro to their database from day one because of that mmWave support.
I might have used the wrong word, I meant can the bootloader be unlocked and multiple devices. My problem with Verizon was imei dependent. Could not use a Verizon sim on multiple devices.
Hi. I bought a new Pixel 7 Pro from Google store and tried using the hotspot on it with my AT&T carrier. I noticed that I do not get an IP address from the phone. I verified with the carrier that I have it on my plan and they told me it is because my phone is unlocked which seems like BS to me. I have not rooted it or changed from the factory ROM and was wondering if anyone had any ideas on getting this to work? I put my SIM into my old Pixel XL that has a custom ROM on and is unlocked and hotspot works fine on it.
Thanks
Anyone got any ideas?
Mine works just fine.... On at&t as well... Dunno what's going on with yours
Mine works as well w/AT&T - I would reach out to AT&T and they can double-check the settings for your device, shouldn't take long.
I called them today and actually got someone with a brain. Went through many settings and then said my hotspot limit was reached to 3GB even though I had not used it in a couple months and just started a new billing cycle. I added 12GB of hotspot to the plan and then it worked! I am so glad someone took the time to look over the account to realize this as when I logged into AT&T's website it showed I had not used any of the data of the hotspot. Who knows why the computer on one end was different then what I saw but this fixed it. I am very happy. Thanks All!
moonlite said:
Hi. I bought a new Pixel 7 Pro from Google store and tried using the hotspot on it with my AT&T carrier. I noticed that I do not get an IP address from the phone. I verified with the carrier that I have it on my plan and they told me it is because my phone is unlocked which seems like BS to me. I have not rooted it or changed from the factory ROM and was wondering if anyone had any ideas on getting this to work? I put my SIM into my old Pixel XL that has a custom ROM on and is unlocked and hotspot works fine on it.
Thanks
Click to expand...
Click to collapse
Lol You can't hotspot because your device is unlocked xD, she should be fired for making customers believe that bs
You say "AT&T carrier" - are you by chance referring to an MVNO? Cricket, for example? Cricket doesn't allow BYOD devices to use hotspot. Older devices can evade their detection but newer ones cannot.
@J0nhy, I bought a brand new Google Pixel 7 Pro unlocked from the Google store. It is for sure unlocked.
And yes, AT&T is my carrier (that is who the bill comes from and my SIM has their logo stamped on it), not Cricket.
Yeah if you have AT&T, just call tech support and hang up and call again until you get someone who can investigate why it doesn't work rather than blaming the unlocked device.
I tethered via USB just fine. I have an unlocked phone and I'm on AT&T as well.
Just customer service some don't know what they are doing and others are better at their job. I'm glad all it was, was a setting from the carrier and not my new phone. I love this new Pixel 7 Pro. The best phone I have ever owned.
Root the phone, install VPN Hotspot from play store... I go through 70gb+ a month. Not a single bit of hotspot data.
eloko said:
Root the phone, install VPN Hotspot from play store... I go through 70gb+ a month. Not a single bit of hotspot data.
Click to expand...
Click to collapse
I second this. I use VPN hotspot as well with a VPN. I've tried it on Verizon and T-Mobile but not AT&t. Having both VPN hotspot and a VPN on, the ISP as no idea that you're using hotspot and you can have unlimited hotspot.