Develop Bugs

[Q] Sim Unlock for Travel with Rooted DINC 2

So I have been googling for answers for a few days now and I can't really seem to find a straight answer. I will be in Europe this summer and have a DINC2 that I am bringing with. In order to use a foreign (non-Verizon) SIM card I have to unlock my phone. For a DINC 2 stock ROM you can easily go into settings->security->unlock sim and type in the unlock code (which I have already received from Verizon). I have rooted though and am running Cyanogenmod 7. There is no option to unlock SIM in this ROM. I found an answer online that says if you flash a stock rom then you can unlock, I have not been able to find a stock rom for the DINC 2 though (http://forum.xda-developers.com/showthread.php?t=1678250).
So here are my questions:
1) Does anyone have a link to the stock rom?
2) If I flash this ROM and unlock my SIM can I restore Cyangogenmod without losing my unlock?
3) Has anyone used a rooted DINC 2 outside of the US that has been unlocked from Verizon? If so, can I simply wait until I arrive at my destination and pop in the SIM card and type in my code that way?
Any help would be appreciated!

1) Stock based ROM: http://forum.xda-developers.com/showthread.php?t=1219471
OR
Complete RUU: http://www.filefactory.com/file/c25....01.1111_NV_VZW1.92_release_225831_signed.exe
2) I think it'd work but you'll have to try it yourself. Do you have a friend on a GSM carrier?
3) I have no idea but if the unlock is permanent, I think that's what you'd do.

Flashed the stock rom, unlocked the sim, and reflashed cyanogen. Everything seems to have worked great. I guess we'll see in a week if I can connect to a GSM network! Thanks for your help

According to Verizon the SIM unlock is permanent and you will not have to enter the code again. Even after flashing roms, stock restore, etc.

In addition, andyBonestock's ROM and SkyRaider's Zeus v1.3 Sense ROM are based on stock and I can personally confirmed them to be working in a rooted & Sim unlocked DI2. As VZW customer in good standing, you call Global Support & within 5 to 10 minutes, CSR will find the 8 digits unlock code and walk you thru the steps - scroll thru the Settings and input it, press the Enter key and DI2 will reboot after showing it's unlocked (yes, it IS permanent)
For voice & SMS, AT&T and T-Mobile (and, China Mobile HK) Sim cards will work (power down, insert Sim, restart) - broadband/WiFi access will need proper APN settings, and, account will need to be provisioned for data access.
DI2 was in GSM mode, unlocked & worked fine when we're in Bermuda last month.

Letitride said:
In addition, andyBonestock's ROM and SkyRaider's Zeus v1.3 Sense ROM are based on stock and I can personally confirmed them to be working in a rooted & Sim unlocked DI2. As VZW customer in good standing, you call Global Support & within 5 to 10 minutes, CSR will find the 8 digits unlock code and walk you thru the steps - scroll thru the Settings and input it, press the Enter key and DI2 will reboot after showing it's unlocked (yes, it IS permanent)
For voice & SMS, AT&T and T-Mobile (and, China Mobile HK) Sim cards will work (power down, insert Sim, restart) - broadband/WiFi access will need proper APN settings, and, account will need to be provisioned for data access.
DI2 was in GSM mode, unlocked & worked fine when we're in Bermuda last month.
Click to expand...
Click to collapse
Thank you so much for your information. Just wondering, are you still able to use global sim? I use MROM and if I reboot my phone after flashing the SIM is back locked again

startrek1312 said:
... are you still able to use global sim? I use MROM and if I reboot my phone after flashing the SIM is back locked again
Click to expand...
Click to collapse
Yes, affirmatively - Mrs. L has continuously run her red DI2 on SkyRaider Zeus and GSM mode is fine. I was running SR too - it had no problem when we're cruising down in the Caribbean islands - switched off CDMA to avoid roaming & data charges on the ship and on land, used my China Mobile prepaid Sim, great for voice and Int'l SMS - no data roaming as it is NOT provisioned for and tapped WiFi @ local Starbucks - locked onto a 3G AT&T tower in Old San Juan, PR. Every now & then, it might find & stay with a T-Mobile signal, but usually the Sim card settings prefer AT&T over T-Mo.
Currently, I'm running Nit's Stock Sense v5.0.m-ext4 Rom, it's global ready - works just as good - have played with all of the new custom Roms but always finding my way back to 1 of the 3 Roms mentioned here as the default. Have Currents, Google+, Play Magazine, Play Music & SoundHound, OneNote, QuickOffice and Wireless Tether running on mine - and I get to play the latest JB 4.2.2 on the Nexus 7 WiFi tablet, so this is fine for my needs.
Heading toward the end of our 2 year contract, main/primary line will be eligible for upgrade next month but I'm not in a hurry to let go of unlimited 3G data (although my usage has been consistently under 1GB/mo, mostly 500 MB or so. Already trying to re-sign me for another 24 months with an early upgrade Email offer that I must call in for ...

Verizon unlock code
Daveee6 said:
So I have been googling for answers for a few days now and I can't really seem to find a straight answer. I will be in Europe this summer and have a DINC2 that I am bringing with. In order to use a foreign (non-Verizon) SIM card I have to unlock my phone. For a DINC 2 stock ROM you can easily go into settings->security->unlock sim and type in the unlock code (which I have already received from Verizon). I have rooted though and am running Cyanogenmod 7. There is no option to unlock SIM in this ROM. I found an answer online that says if you flash a stock rom then you can unlock, I have not been able to find a stock rom for the DINC 2 though (http://forum.xda-developers.com/showthread.php?t=1678250).
So here are my questions:
1) Does anyone have a link to the stock rom?
2) If I flash this ROM and unlock my SIM can I restore Cyangogenmod without losing my unlock?
3) Has anyone used a rooted DINC 2 outside of the US that has been unlocked from Verizon? If so, can I simply wait until I arrive at my destination and pop in the SIM card and type in my code that way?
Any help would be appreciated!
Click to expand...
Click to collapse
I am planning the same thing: going to Europe next month with a recently rooted phone. Did you just call Verizon and they gave you a code? Did you tell them you were traveling or did you make up some sort of story? Thanks!
-Dave
---------- Post added at 02:05 PM ---------- Previous post was at 01:31 PM ----------
Also I am planning on flashing CyanogenMod very soon. I assume you would now recommend that I wait for the code and unlock the SIM before I do that, correct?

dml5064 said:
... Did you just call Verizon and they gave you a code? Did you tell them you were traveling or did you make up some sort of story? ... Also I am planning on flashing CyanogenMod very soon. I assume you would now recommend that I wait for the code and unlock the SIM before I do that, correct?
Click to expand...
Click to collapse
Things might've changed a bit at Big Red with the unlocking code, but not by much. First, I would strongly recommend using a near stock global Rom (Andy Bone's - the difference being that it'll stayed unrooted and 99.5% stock basically - Superuser installed.
You need to be a Big Red customer in good standing (bills are paid/current & on account for 3 or 6 months continuously) - and have a non VZW-Vodafone Sim (known working prepaid Sim from AT&T Gophone, T-Mobile, or foreign Sim for test & verification afterward) - phone should be S-off and unlocked, CWM installed if possible (so that you can make a full backup copy of your Stock Rom with APN/PRL (save it to a HDD, USB or Cloud storage)
Call up VZW from another phone line (mobile, home/office, VOIP or whatever - that they can call you back from if necessary - ie. disconnected while on hold) - from among the automated Menu option & voice prompt, select Tech Support for smartphone and/or Global Support - if you get routed somewhere else, ask them to forward to Global Support.
Give them your account info & verify, passcode and/or Soc. Sec. etc. - tell them you need to unlock the DI2 for travel and to be able to use another prepaid Sim card. S/he will read their scripts and inform you that you are responsible for charges, damages and will have no access to support - acknowledge & agree, they will ask confirm your email address & send you the written disclaimers, etc. You might be put on hold for a few minutes, do NOT hang up - make sure they have your immediate call back # - as they will need to go into their database & look up your IMEI's unlock code. Once they have it, they will come back on and walk you steps-by-steps, to go to the Start Menu and submenu, and get to the unlock screen - input the code (I believe it was 8+ digits) - and as soon as the last correct digit is entered, the screen will refresh & say unlocked. Next, exit & close those submenu, turn off & reboot the phone - whatever instructions, just follow it.
With your own "foreign/non-VZW" Sim already installed, you should be able to switch to GSM mode under Wireless & networks / Mobile neworks - and see the new "Carrier's Name" displayed and likely an (E)dge symbol instead of 3G, that is your confirmation of a successful unlock. It is permanent, regardless of switch & flashing to other Rom, etc.
That's it. Copy & flash your choice of Global Roms, unless you are planning to use the DI2 overseas or elsewhere and not using CDMA again ever, I recommend staying with one of the proven ones here - ICS/JB or 4.x ones are cool to play, but battery life is average at best - trust me on this one from personal experience while traveling. Customize & configure the Rom to your own liking - plenty of Google Play (Store) update once it is up & running as many of the preloaded Apps have been revised/updated many times since - best/fastest over a good WiFi connection - then, make both a TB backup of the Apps and a full CWM Recovery backup image - save them both to HDD/USB and Cloud Storage - mission accomplished.
For use within USA, you will have 100% working voice calling & SMS/texting with AT&T and/or T-Mo's GSM network, and 2.5G data only if your plan has data bundled as add-on, and the APN settings are auto-updated/loaded. That's about it - for as little as $30/mo - you can use this device for unlimited calling and texting, and works great when you are on broadband over WiFi. Load an offline Map like Nav free USA with maps (16GB or 32GB mSD is recommended for storage) and you can maintain turn-by-turn navigation on the go.
Any other questions, please feel free to ask and/or leave me a PM - and will try to address them as best as I can on practical usage. For technical help on specific Roms, the developers are your best friends. Good luck, enjoy & have fun.

Can't fully install stock ROM with Odin - help please!

Hi, and firstly, thanks to any and all who offer their knowledge to assist my conundrum.
I recently purchased a Bell Canada version of the SG Note 2 (i317), I am on Telus so I attempted to Unlock the phone. I looked online and found people were having success unlocking these phones for free using the *#197327640# method, (whereby you go into the service mode, turn off the PERSHO_256 and then INITIALLIZ).
I tried this method and the phone then seemed to work with my telus sim, but only for voice, not data. When I put in a Bell SIM from a friend, both voice and data worked fine - which tells me its not a hardware (radio) issue. I also tried using another friends Telus SIM and had the same results as mine - which tells me it's not a SIM error. Also, all the settings in the mobile network area appeared to be correctly set up.
So, my next step was to try and reflash the phone to the stock Bell ROM and then just buy an Unlock code. I downloaded the stock ROM (2 different ones actually) and used Odin 3.07 to reload the ROM. I've tried it several times now, with both Bell ROMs and each time it says it's been successful, but the phone remains in the same, partially unlocked state.
It seems as though by using the PERSHO_256 method I have permanently, PARTIALLY unlocked the phone. I can't seem to re-lock it by installing the stock Bell ROM, and since it's unlocked, I can't get the foreign SIM error to come up to enable me to put in my purchased unlock code.
If anyone has any insights, it would be GREATLY appreciated. Thanks!
-Luke

did you check and/or setup the apn? it may be just the apn is not set correctly or you have to manually input hte apn

sounds like just APN needs setting...

APN?
How would I check/setup the APN? Is this to allow me to do a full reflash to a stock ROM or to access data with the phone in it's current state?

left ownsho
So I went into ACCES POINT NAMES and checked the sp.telus.net box, no change. Did a restart. No change Any ideas?

Wooooo Hooooo!!!
So, it's working now!!! I dug a little deeper and found the correct APN settings for TELUS. NOW IT F*@^&#*&@ING WORKS!
Thanks so much for pointing me in the right direction!!!

[Q] Device won't connect to any network

Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.

sgtcanadian said:
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
Click to expand...
Click to collapse
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?

Larry2999 said:
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Click to expand...
Click to collapse
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.

sgtcanadian said:
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
Click to expand...
Click to collapse
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated

Larry2999 said:
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Click to expand...
Click to collapse
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.

sgtcanadian said:
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
Click to expand...
Click to collapse
Please let me understand a few things ... when you first acquired the phone, was it working normally on Bell prior to the first unlock attempt or you never used it at all until you tried Koodo? Secondly, was the unlock code you got from Bell identical to the one you got from the online service?
I'm trying to establish if it is a case of hardware failure not reported by the previous user especially if you bought it pre-owned from the secondary market. If you are not sure of the previous usage history, it could be a faulty or disconnected antenna which may require professional service. On the other hand if you are sure it was working fine prior to the unlock attempt, try the following ...
1) From the dial pad, enter *#197328640#
2) [1] UMTS
3) [1] DEBUG SCREEN
4) [8] PHONE CONTROL
5) [6] NETWORK LOCK
6) [3] PERSO SHA256 OFF
7) Press Menu => Back button and go all the way back to Step 3) above
8) [6] COMMON
9) [6] NV REBUILD
10) [1] NV REBUILD
Reboot and restart and let's see if this does it.

I've got a similar symtom different scenario (sister in-laws phone). I was also only able to see Rogers network on a search. I've got Telus version. It was working fine until it was brought to the Philippines, got unlocked there and brought back to Canada.
I was only able to see Rogers network until I went into the Service Menu (similar to above) and found the option to change the band. I changed it to Automatic. After that I was able to see Telus network. When trying to connect/register it would take a long time and give me an error "Unable to connect, try again later". I still need to do more troubleshooting, but that might be something to look at.
Note: Phone has stock MOD ROM, rooted and unlocked.

Use Verizon note 4 on AT&T

I got Verizon Note 4.
Verified that it is unlocked. Not stolen. No contract binded from Verizon store and through phone (Clean phone)
Android Version : 5.0.1
Location: Las Vegas
Insert AT&T sim card. No signal.
Change APN setting following the information on AT&T website. Still not working. No signal.
At&t store rep. said I need to l unlock the phone ( I already check with Verizon via phone and store)
Verizon rep. on phone said: I should be able to use the phone with At&t sim card
Verizon Rep. in store said : Galaxy note 4 won't work on AT&T. It needs to be rooted by an expert. Only Galaxy S5 or later version will work.
I searched websites and many say that they are using Verizon Note 4 on AT&T network (At&t sim card)
I just need to use phone and text message. No data needed.
Anybody can help me?

I was able to use SIM from AT&T before yesterday, but after trying to update the firmware using Software Upgrade Assistant tool on Windows 10, it's now stuck at 'searching for service'.

Did you change the network settings from global to lte/GSM?

I am reading this. Maybe a solution.

Did you try to insert a different carrier sim card and entering the unlock code?
---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM ----------
After reading post i see you have a att sim sim on verizon phone. This could be a problem as verizon and att dont play nice. Stupid question is did you actually pay for service?

cozmohoot said:
Did you change the network settings from global to lte/GSM?
Click to expand...
Click to collapse
I did. Not working

It is not working. No verizon sim card message is gone but still no signal.
sam369 said:
I am reading this. Maybe a solution.
Click to expand...
Click to collapse

Yes I did. Not working
cozmohoot said:
Did you change the network settings from global to lte/GSM?
Click to expand...
Click to collapse

dayse said:
It is not working. No verizon sim card message is gone but still no signal.
Click to expand...
Click to collapse
Yeah. Me either.

Did you do a factory reset after software update. Usually helps. Also mess with APN settings. Reboot after changing APN.

Problem solved.
Changing APN settings and reboot did not work. I just inserted the Verizon SIM came with the phone and made a phone call. Of course it's not activated, so I hang up when it reached Verizon automated system. Guess what, now SIM from Lycomobile works. H2O Wireless SIM also works. It means that it now can work with AT&T and T-Mobile network.

sam369 said:
Problem solved.
Changing APN settings and reboot did not work. I just inserted the Verizon SIM came with the phone and made a phone call. Of course it's not activated, so I hang up when it reached Verizon automated system. Guess what, now SIM from Lycomobile works. H2O Wireless SIM also works. It means that it now can work with AT&T and T-Mobile network.
Click to expand...
Click to collapse
I'm in a similar boat as you (4.4.4 on Cricket Wireless, wanting to upgrade to 5.1.1). I just want to make sure I understand what you did to restore service:
1. You had phone working on AT&T with an older Android version (KK?)
2. You upgraded to a newer version via the Verizon upgrade tool (I assume 5.0.1 since 5.1.1 is not yet available via the tool)
3. You lost AT&T service after upgrade
4. You were able to restore AT&T service by using an inactive Verizon SIM and making a phone call
Is this correct? TIA

ftkftw said:
I'm in a similar boat as you (4.4.4 on Cricket Wireless, wanting to upgrade to 5.1.1). I just want to make sure I understand what you did to restore service:
1. You had phone working on AT&T with an older Android version (KK?)
2. You upgraded to a newer version via the Verizon upgrade tool (I assume 5.0.1 since 5.1.1 is not yet available via the tool)
3. You lost AT&T service after upgrade
4. You were able to restore AT&T service by using an inactive Verizon SIM and making a phone call
Is this correct? TIA
Click to expand...
Click to collapse
Mostly, except that I tried to upgrade from 5.0.1 to 5.1.1, but found that 5.1.1 was not yet available via the tool, but the process of installing the software on windows 10 and maybe I also used the Verizon SIM during the process which might have messed something up. I updated the firmware to 5.1.1 by downloading the zip file in a thread here and flashed it through recovery. The network connection problem was then solved by making a phone call with the SIM came with the phone.

sam369 said:
Mostly, except that I tried to upgrade from 5.0.1 to 5.1.1, but found that 5.1.1 was not yet available via the tool, but the process of installing the software on windows 10 and maybe I also used the Verizon SIM during the process which might have messed something up. I updated the firmware to 5.1.1 by downloading the zip file in a thread here and flashed it through recovery. The network connection problem was then solved by making a phone call with the SIM came with the phone.
Click to expand...
Click to collapse
I just updated via the Verizon tool (BPA1 finally showed up) and it was, surprisingly, perfectly fine. I first backed up as much as I can (via Smart Switch and Helium app), then pulled my mSD card, left my SIM card in the phone, and proceeded to update. After the first boot stuff (app optimization, etc.) I soon saw the AT&T sign in the notification bar, and I was able to make a phone call without doing anything else. With all the reports of SIM card locking after updating I was worried that I might run into the same issue, but was pleasantly surprised that I didn't. I had to re-enter the APN setting as the upgrade seemed to have removed it, but after re-adding Cricket's APN I was able to get cellular data as well.
Thanks again for your help

You need to access the hidden menu and change your radio and modem protocols. There's a forum on XDA called domestic and internation sim or network unlock for spring but should work the same on verizon

fyi, i got my note 4 working on gsm using 2 different freedompop sims-the at&t lte sim gets lte via band 4.
the global sim based on t-mobile did get hpsda+
just change the apn

OEM Unlock greyed out on Developer Options?

Hey guys. I just got a new Pixel 2 XL from a European seller (Alza) and my GPS isn't working (it can see the satellites but cannot lock onto any). I've seen that flashing a factory image solves this problem.
However, I can't unlock my boot loader. On developer options the option is greyed out and says "Connect to the internet or contact your carrier".
I've seen people mention that if it's locked it's Verizon... However, I'm in Europe? Also I'm using a European SIM card just fine? Would this phone still have any chance of being a Verizon somehow? Lol.
Please help. Thanks.

SOLVED:
I reset the phone. Still greyed out. I inserted my country's SIM card for the first time just now. Still greyed out. Finally, I did another reset (from the settings menu, always) and the phone when setting up was already in my language, and the OEM unlock option was now available. Dunno what happened but yeah, if someone in the future is in this situation, there you go.