Related
Upon returning home from a business trip, the dreaded NO SIM error started creeping up on my phone again. 2.5 weeks in Salt Lake City, no issue. Back in TN, horrid NO SIM errors abound. I called Verizon tech support today, and he noticed I already exchanged the phone for a new one, along with a new SIM. One thing he mentioned, it looked like I was "roaming" in the system, so he reset some routers (his words) after having me pull the battery and wait a couple of minutes before powering the S3 back up. Sure enough, on the drive home from work, the phone had a NO SIM issue... so I unplugged the battery for the rest of the drive home. Once inside, I plugged the battery back into the phone, everything looked hunky dory, so I went about my business... and sure as s***, the phone gave me another NO SIM. So I contacted Verizon again, and she offered me any Android phone as a replacement. Now, I don't know if you guys have looked at the current line up for Verizon's Android based smartphones, but it's basically the Moto Razr or the Samsung Galaxy S3. I have not found a case that I absolutely love, so I have invested in quite a few so far, plus additional charging cradles, car mounts, etc... frustrating because I love this phone, but I use it for work, so I can't deal with this issue much longer.
If you had to select another phone to replace it, what would you go with? The new RAZR M? (lose NFC, smaller and crappier screen, etc) The RAZR Maxx?
Thanks, in advance.
No other phone on Verizon can touch the S3. Only phone that can be comparable is something that is not out yet.
Then when it comes out, they will tell you it is to new.
[email protected] said:
No other phone on Verizon can touch the S3. Only phone that can be comparable is something that is not out yet.
Then when it comes out, they will tell you it is to new.
Click to expand...
Click to collapse
Might hold out for the Note 2. Testing something currently... wondering if Go SMS is the issue, seeing as the problem seems to creep up with some sort of combination of texting and calls. Will update tomorrow.
Did you apply the latest update? It should have updated automatically OTA, unless you are running custom unlocked rooted whatever ROM. In that case go to dev section and download latest radio and flash it. Should fix that damn no SIM problem.
Sent from my SCH-I535 using Tapatalk 2
fearlesspaula said:
Did you apply the latest update? It should have updated automatically OTA, unless you are running custom unlocked rooted whatever ROM. In that case go to dev section and download latest radio and flash it. Should fix that damn no SIM problem.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yep, already flashed last week. Tech Support told me tonight they have been fielding calls post patch showing it didn't fix the issue. If they are offering me any android of my choice, they are probably as flustered as I am. Almost went to a Rezound, a step backwards, I know, but I am at wit's end. Will see how the next week goes.
Sorry to hear. Try and hold out for a fix. I came from a rezound, and while I loved my HTC phones, this s3 is great. Too different to compare.
Sent from my SCH-I535 using Tapatalk 2
mdt73 said:
Upon returning home from a business trip, the dreaded NO SIM error started creeping up on my phone again. 2.5 weeks in Salt Lake City, no issue. Back in TN, horrid NO SIM errors abound. I called Verizon tech support today, and he noticed I already exchanged the phone for a new one, along with a new SIM. One thing he mentioned, it looked like I was "roaming" in the system, so he reset some routers (his words) after having me pull the battery and wait a couple of minutes before powering the S3 back up. Sure enough, on the drive home from work, the phone had a NO SIM issue... so I unplugged the battery for the rest of the drive home. Once inside, I plugged the battery back into the phone, everything looked hunky dory, so I went about my business... and sure as s***, the phone gave me another NO SIM. So I contacted Verizon again, and she offered me any Android phone as a replacement. Now, I don't know if you guys have looked at the current line up for Verizon's Android based smartphones, but it's basically the Moto Razr or the Samsung Galaxy S3. I have not found a case that I absolutely love, so I have invested in quite a few so far, plus additional charging cradles, car mounts, etc... frustrating because I love this phone, but I use it for work, so I can't deal with this issue much longer.
If you had to select another phone to replace it, what would you go with? The new RAZR M? (lose NFC, smaller and crappier screen, etc) The RAZR Maxx?
Thanks, in advance.
Click to expand...
Click to collapse
A fix is being pushed out today to address this issue. S3 is bar far the best phone you will find out there...
do you have a source about that?
Verizon is super frustrating. I switched from Sprint and got the Gnex, along with the "mute issue" where all of a sudden your microphone stops working during a call and you have to hang up. I've had the phone replaced and the replacement still does it so they offered me an "early upgrade" if I buy the S3 for $200.00. I did some research and found out about the no sim issue on the S3 so when I called back to tell them I didn't want an S3 they offered a RAZR M at $99.00 :/
I'm really considering breaking my contract with them to get a phone I like that works as it's supposed to.
Ya. This issue is really bugging me. I honestly believe there is a hiccup between the phone and the tower when a text is sent. I noticed at home that when I have wifi connected, and then send a text, the S3 will connect to 4G to send the message. At that point, something triggers in the phone and it loses connectivity with the SIM.
Not that this helps much... I explained it to level 2 support and they kept telling me how it was a new to them issue.
Sent from my big red Samsung Galaxy S3 using XDA Premium.
Droid M is somewhat close. I'd stay with it or wait for the Razr HD
DertyDOH said:
Droid M is somewhat close. I'd stay with it or wait for the Razr HD
Click to expand...
Click to collapse
Hmm, I'll check it out. The M seems a downgrade at this point.
mdt73 said:
Ya. This issue is really bugging me. I honestly believe there is a hiccup between the phone and the tower when a text is sent. I noticed at home that when I have wifi connected, and then send a text, the S3 will connect to 4G to send the message. At that point, something triggers in the phone and it loses connectivity with the SIM.
Not that this helps much... I explained it to level 2 support and they kept telling me how it was a new to them issue.
Sent from my big red Samsung Galaxy S3 using XDA Premium.
Click to expand...
Click to collapse
You're not kidding. I don't know if they REALLY don't know about these issues or they are just lying.
Tier 2 was who was helping me with the replacement phone and when I mentioned the No Sim error they said they had never heard of it and the only problem he's ever seen with an S3 is when a user doesn't turn off their old phone when activating a new phone :/
joe_sun said:
You're not kidding. I don't know if they REALLY don't know about these issues or they are just lying.
Tier 2 was who was helping me with the replacement phone and when I mentioned the No Sim error they said they had never heard of it and the only problem he's ever seen with an S3 is when a user doesn't turn off their old phone when activating a new phone :/
Click to expand...
Click to collapse
Ya, it amazes me that their "level 2" support still tries this excuse. Every time they try this with me, I ask them to tell me what the latest S3 software update addresses, and then the phone gets quiet, followed by excuses and them never hearing about it... even tho Verizon put out a patch to fix the issue.
Keep documenting it, tis the only way it's going to get addressed, or at the very least you will have ammo to get a new phone.
mdt73 said:
Ya, it amazes me that their "level 2" support still tries this excuse. Every time they try this with me, I ask them to tell me what the latest S3 software update addresses, and then the phone gets quiet, followed by excuses and them never hearing about it... even tho Verizon put out a patch to fix the issue.
Keep documenting it, tis the only way it's going to get addressed, or at the very least you will have ammo to get a new phone.
Click to expand...
Click to collapse
I'm sooo close to just paying the etf and switching to a gsm provider.
Sent from my Galaxy Nexus using Tapatalk 2
joe_sun said:
I'm sooo close to just paying the etf and switching to a gsm provider.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Have you tried the new HD modem for S3 yet?
Following guidance from the 2nd level tech after calling tech support, I stopped by the local verizon store today to pick up a new SIM. This is my third SIM, but she assured me there was a bad batch floating around the stores. We'll see... fingers crossed.
mdt73 said:
Following guidance from the 2nd level tech after calling tech support, I stopped by the local verizon store today to pick up a new SIM. This is my third SIM, but she assured me there was a bad batch floating around the stores. We'll see... fingers crossed.
Click to expand...
Click to collapse
A friend of mine had the same issue, we both have the GS3 and live in the same area. She gets constant sim errors while I've never got one and I switch between 3G/4G frequently. She recieved a new sim a few weeks ago and hasn't had an error since. Seems a lot of sims are incorrectly configured with Verizon's network, just an educated guess.
Sent from my SCH-I535 using xda app-developers app
Shibby87 said:
A friend of mine had the same issue, we both have the GS3 and live in the same area. She gets constant sim errors while I've never got one and I switch between 3G/4G frequently. She recieved a new sim a few weeks ago and hasn't had an error since. Seems a lot of sims are incorrectly configured with Verizon's network, just an educated guess.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am amazed. 24 hours, not a single NO SIM error. Maybe I was un-lucky enough to get two bad SIMs the first time...
mdt73 said:
I am amazed. 24 hours, not a single NO SIM error. Maybe I was un-lucky enough to get two bad SIMs the first time...
Click to expand...
Click to collapse
Still not a single no sim error. I am about 24 hours from saying it was a bad batch of SIM cards... never thought I would say that.
I woke up this morning to a message on my screen saying that my UICC has been unlocked. I am stock unrooted. The only mod I have done was add ",dun" to unlock my hotspot. I wish I had taken a screenshot of the message before I cleared it, but I didn't. Has anyone else experienced this? Is it a problem for me?
Thanks for any input.
I'm not 100% sure but I think that's the message you get when your Note 5 is unlocked to be used on an international carrier.
DarkManX4lf said:
I'm not 100% sure but I think that's the message you get when your Note 5 is unlocked to be used on an international carrier.
Click to expand...
Click to collapse
Before I posted, I searched and saw similar results. But I haven't changed my plan nor have I contacted Sprint to make the request for international travel. I just wonder why it automatically did that. I am going to restart my phone and update profile to see if it resolves and/or happens again.
*** When I went into the settings to update the profile, I see UICC Unlock. Out of curiosity, I clicked it and got the same message as before. Must not be as big of a deal as I thought it would be. Still wonder why it did it on its own.
State sponsored hacking?
Sent from my SM-N920P using Tapatalk
Bdozier said:
Before I posted, I searched and saw similar results. But I haven't changed my plan nor have I contacted Sprint to make the request for international travel. I just wonder why it automatically did that. I am going to restart my phone and update profile to see if it resolves and/or happens again.
*** When I went into the settings to update the profile, I see UICC Unlock. Out of curiosity, I clicked it and got the same message as before. Must not be as big of a deal as I thought it would be. Still wonder why it did it on its own.
Click to expand...
Click to collapse
Mine did as well. A LEASE. But I have not paid the bill and quit ...I called them and have my reasons after 5 years of good payment. I won't send them a dime. Anyway I recieved un lock uicc auto 2 times. I'm using att straight talk 2 months now. Lol lte is good all works.
Sent from my SM-N920P using XDA-Developers mobile app
Mine did this today too. Not sure why.
Sent from my SM-N920P using Tapatalk
i think i have heard when your service agreement expires the phones automatically unlock. is that a possibility for you?
What the difference? I've heard people saying different apps installed but I have zero Verizon apps on my device even first boot didn't have them.
BlackKnight23 said:
What the difference? I've heard people saying different apps installed but I have zero Verizon apps on my device even first boot didn't have them.
Click to expand...
Click to collapse
Zero difference in software until you put a Verizon SIM in it. Then it downloads the VZ software. Google version does the same.
But after you let a VZ update to 7.1.1 you can no longer unlock the bootloader.
Sent from my Pixel XL using XDA Labs
To clarify @TonikJDK 's response, if you have a Verizon Pixel and it has a 7.1.0 build on it such as NDE63X, and if you put a non-Verizon SIM in, the phone then "updates" to the latest non-Verizon Pixel build, which at that time would've been NDE63V, and which would then not have the Verizon apps included.
Likewise, if you had the Google Edition on NDE63V, it was reported that if you put a Verizon SIM in, it would "update" to the latest Verizon image (again, at that time NDE63X). I can personally attest to this because I have a Verizon Pixel and I happened to 1. unlock my bootloader using DePixel8, 2. I flashed the NDE63V non-Verizon image, and 3. Re-inserted my Verizon SIM (which I'm actually using in an HTC 10 right now) and I mistook an update that was offered shortly after as being 7.1.1, but instead it was NDE63X, the Verizon build. I ended up taking the SIM back out and reflashing NDE63V, which has since updated to NMF26O and then NMF26Q.
One question I've been wondering about and haven't noticed if it's been addressed anywhere, the 7.1.1 builds are all the same for Verizon and non-Verizon. They're all NMF26O for the first release of 7.1.1 and NMF26Q for the second OTA of it.
So I'm wondering if putting a Verizon SIM in does anything anymore if you're on a stock 7.1.1 image. I could relatively easily find out, but it's not a huge priority.
Also, as long as you already unlocked the bootloader, nothing will re-lock it, even Verizon OTAs, unless you manually do so.
No idea if there'll be Verizon-specific builds again later.
Edit: Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pixel/how-to/verizon-update-nmf26u-t3527199/post70281819#post70281819
Reference for factory image revisions: https://developers.google.com/android/images
I'm on NMF26O
So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Sent from my Nexus 6 using Tapatalk
Bloodcrav said:
So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What do you mean screwed by Verizon? A Verizon phone and Google phone are different and the sim won't change that.
bobby janow said:
What do you mean screwed by Verizon? A Verizon phone and Google phone are different and the sim won't change that.
Click to expand...
Click to collapse
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Sent from my Nexus 6 using Tapatalk
Developer options, turn off automatic system updates. Install them yourself from Google's developer page.
Bloodcrav said:
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not sure that is true, but even so they are the same. The updates are not what defines the device. Something else does and no one is saying or perhaps know.
Bloodcrav said:
So if you buy a Google Play Pixel and use a Verizon SIM you risk the chance of being screwed by Verizon by getting their builds pushed?
Click to expand...
Click to collapse
Bloodcrav said:
If I get a Google Play Pixel and use my Verizon SIM I'll be getting Verizon OTAs instead of the Google version.
Click to expand...
Click to collapse
bobby janow said:
I'm not sure that is true, but even so they are the same. The updates are not what defines the device. Something else does and no one is saying or perhaps know.
Click to expand...
Click to collapse
You get the Verizon OTAs if you don't disable the option for automatic updates, but there's nothing screwing about it. The Google Play Pixel can be unlocked at any time so you can do anything you want to your phone. The only people screwed are those who are on 7.1.1 on a Verizon Pixel with a locked bootloader.
roirraW "edor" ehT said:
You get the Verizon OTAs if you don't disable the option for automatic updates, but there's nothing screwing about it. The Google Play Pixel can be unlocked at any time so you can do anything you want to your phone. The only people screwed are those who are on 7.1.1 on a Verizon Pixel with a locked bootloader.
Click to expand...
Click to collapse
That being said, when I first boot up my new Pixel XL 128 on Verizon, I need to immediately go to developer options and shut down auto updates. I'm assuming I'll have to activate developer mode with the multiple taps one the build or something like that in ABOUT.
They pre-installed a SIM. So, I assume I'll have to rush to developer mode before it connects to Verizon. Although, I think I may have to call Verizon to activate the new SIM first.
Am I on the right track to avoid having bootloader locked?
Sent from my Nexus 9 using Tapatalk
bigsyd said:
That being said, when I first boot up my new Pixel XL 128 on Verizon, I need to immediately go to developer options and shut down auto updates. I'm assuming I'll have to activate developer mode with the multiple taps one the build or something like that in ABOUT.
They pre-installed a SIM. So, I assume I'll have to rush to developer mode before it connects to Verizon. Although, I think I may have to call Verizon to activate the new SIM first.
Am I on the right track to avoid having bootloader locked?
Click to expand...
Click to collapse
You have to remove the SIM before bottling. Then skip connecting to wifi
So if I'm already on the 7.1.1 update, there is literally nothing I can do to revert back to 7.1?
I am from VZ
iamjerry123 said:
So if I'm already on the 7.1.1 update, there is literally nothing I can do to revert back to 7.1?
I am from VZ
Click to expand...
Click to collapse
If you have the Verizon Pixel and you didn't unlock your bootloader before you got on 7.1.1, then correct.
aholeinthewor1d said:
You have to remove the SIM before bottling. Then skip connecting to wifi
Click to expand...
Click to collapse
Thank you. I will give it a shot today.
Sent from my HTC6525LVW using Tapatalk
roirraW "edor" ehT said:
To clarify @TonikJDK 's response, if you have a Verizon Pixel and it has a 7.1.0 build on it such as NDE63X, and if you put a non-Verizon SIM in, the phone then "updates" to the latest non-Verizon Pixel build, which at that time would've been NDE63V, and which would then not have the Verizon apps included.
Likewise, if you had the Google Edition on NDE63V, it was reported that if you put a Verizon SIM in, it would "update" to the latest Verizon image (again, at that time NDE63X). I can personally attest to this because I have a Verizon Pixel and I happened to 1. unlock my bootloader using DePixel8, 2. I flashed the NDE63V non-Verizon image, and 3. Re-inserted my Verizon SIM (which I'm actually using in an HTC 10 right now) and I mistook an update that was offered shortly after as being 7.1.1, but instead it was NDE63X, the Verizon build. I ended up taking the SIM back out and reflashing NDE63V, which has since updated to NMF26O and then NMF26Q.
One question I've been wondering about and haven't noticed if it's been addressed anywhere, the 7.1.1 builds are all the same for Verizon and non-Verizon. They're all NMF26O for the first release of 7.1.1 and NMF26Q for the second OTA of it.
So I'm wondering if putting a Verizon SIM in does anything anymore if you're on a stock 7.1.1 image. I could relatively easily find out, but it's not a huge priority.
Also, as long as you already unlocked the bootloader, nothing will re-lock it, even Verizon OTAs, unless you manually do so.
No idea if there'll be Verizon-specific builds again later.
Edit: Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pixel/how-to/verizon-update-nmf26u-t3527199/post70281819#post70281819
Reference for factory image revisions: https://developers.google.com/android/images
Click to expand...
Click to collapse
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.
b00ster23 said:
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.
Click to expand...
Click to collapse
You know, I probably got the VZ apps because I have my Google account set to restore apps.... And I had them on my previous phone.
Not a big deal since any that are unwanted can be uninstalled.
b00ster23 said:
Just setup 2 phones without updating from current version (7.1) by using the remove SIM/Bypass WiFi method. Updated them directly to 7.1.1 NMF26O and activated. Was done last night, and haven't had and VZW apps pushed to this point. Both rooted with TWRP RC1. Wonder if the newest build will push the apps. For my first Pixel, I had dropped down X and allow VZW to push out apps, the side loaded up to NMF26O. Either way, all 3 pixels work flawlessly.
Click to expand...
Click to collapse
Hi, how's it going?
NMF26O and NMF26Q are used by both Google and Verizon, whereas there were Verizon-specific builds before NMF26O. It's rumored Verizon is going to have a NMF26U, and I have no idea if Google will have the same one or if Verizon's will once again be different than Google's. Also, if you have automatic updates turned off for OTAs in Developer Options, nothing will be forced on you. If NMF26U or a later build will be Verizon only, you could get OTA prompts unless you have that disabled.
roirraW "edor" ehT said:
Hi, how's it going?
NMF26O and NMF26Q are used by both Google and Verizon, whereas there were Verizon-specific builds before NMF26O. It's rumored Verizon is going to have a NMF26U, and I have no idea if Google will have the same one or if Verizon's will once again be different than Google's. Also, if you have automatic updates turned off for OTAs in Developer Options, nothing will be forced on you. If NMF26U or a later build will be Verizon only, you could get OTA prompts unless you have that disabled.
Click to expand...
Click to collapse
Going well "old" friend! Made the jump to the VZW variant while the jumping was good. FREE was a good price.
Spot on with the latest builds. I have APK backups of the VZW apps and can always add them into the other 2 phones, if needed.
Just fyi when I bought mine from Verizon it had 7.1. On it. I put SIM in it. I just made sure i didn't hit the new software update. I didn't have any problems. But it would be really easy to accidentally hit that update button
Hey everyone,
I wanted to share a bit of a test that I just did on three Verizon Pixels. Specifically, when I got them from Verizon I did so via direct fulfillment (not a retail store). Doing this method I was able to boot loader unlock all three Verizon Pixels out of the box. The last one was about five minutes ago.
Here's what you'll need:
A new, in box Verizon Pixel - Important: Must be new in box!
A non-Verizon SIM card.
A Laptop
So, here's the rub. With these tests I was able to confirm that the Pixel does in fact use the SIM inserted into the phone at initial boot to determine boot loader lock ability. Long story short, if the Pixel is booted the first time with a Verizon SIM then the phone will be boot loader locked, and the OEM Unlock Toggle grayed out.
To unlock each of them I did the following:
Take the phone out of the box and inserted a co-workers AT&T SIM.
Booted the phone for the first time, and skipped all of the setup steps.
Enabled Developer Options, USB Debugging, and OEM Unlocking.
Accepted the RSA key and issues the command "adb reboot bootloader".
In bootloader mode issued the command "fastboot oem unlocking".
Flashed TWRP, and root.
Profit
The key to success here is ensuring the phone never gets booted initially with a VZW SIM inserted. This isn't so much phone hack as really a life/policy/process hack. Hope this helps!
Update: I've talked to a few knowledgeable folks on the topic who think the phones I got may have been part of a batch that wasn't loaded correctly. Having said that, Im sharing my experiences and would be curious to see what everyone else's experiences are. I'd also be curious to see the following, if anyone wants to try:
Place a non VZW SIM in the phone, factory default it, and see if its enabled again.
Take a brand new out of box VZW phone and ensure it doesn't connect to ANY network, rather it be wifi or Cell. See if OEM unlock is enabled.
Also, another added benefit is that the phones don't auto-download the few Verizon turdware apps.
Interesting...
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
TonikJDK said:
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
Click to expand...
Click to collapse
What if you take a Google version, put in a VZW sim, connect, update. With it be grayed out? I doubt it.
Sent from my Pixel using XDA-Developers Legacy app
JAYNO20 said:
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
Click to expand...
Click to collapse
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
TCPDump said:
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
Click to expand...
Click to collapse
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
TonikJDK said:
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
Click to expand...
Click to collapse
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Either way, long story short - Always check your pixel.
TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Excellent thought. Maybe they are tired of VZ's too and are faking all these mistakes. That would be cool.
But yea, with the 2 comming this fall maybe they night be getting nervous.
TCPDump said:
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
Click to expand...
Click to collapse
Nope. Pulled the Sim before boot.
I had the exact same luck.
I had to sadly RMA my perfect rooted Pixel due to charger no longer functioning fully expecting a locked bootloader and 7.1.2. Verizon sent me one overnight. It had 7.1.2 but in developer options it had the same Allow OEM Unlocking slider NOT greyed out. I was then able to adb restart bootloader and adb bootloader unlocking and the phone prompted me and that was that. Adb booted to TWRP, installed RR Rom, vendor image, magick, TWRP, root. Can not believe the incredible luck.
Also wanted to say that I used my Verizon SIM card to do this and connected to WiFi on initial setup and I STILL managed to unlock it in time before anything locked itself.
deadlydecision said:
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
Click to expand...
Click to collapse
What does it say on your my Verizon account?
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.