I have an old Pixel 1 that I got a long time ago that I was looking into rooting but the OEM unlocking slider is grayed out/disabled for me.
I've come across dozens of posts with various methods of getting this toggle enabled for Verizon/Non-Verizon phones but many seem to be patched or not working - and then rest I haven't had success with.
To be honest, I'm not even sure which edition I have - I've seen various methods of checking:
My IMEI starts with 35 which I've heard indicates Verizon
When googling something, there is a client string in the URL indicating it is a verizon phone
There seems to be some Verizon apps pre-installed when checking through adb
Checking the Google repair site though, there seems to be no indication that it's a Verizon phone
This leads me to believe it's probably a Verizon phone, but I've seen various threads that it should be possible to unlock any edition at this point - but I haven't had any success, and the threads aren't the most up to date at this point. Curious if anyone has current knowledge on unlocking a Pixel 1 (Verizon or otherwise) in 2022 on the latest/last firmware update.
Thanks!
Related
So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota
My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?
Background: my wife arrived home yesterday with a Samsung Galaxy Tab A 10.1 2016 model (SM-P585) that had been written off by her company due to lockscreen protection being enabled and no one knowing who the last person was that it was issued to.
I kid you not.
Anyhow, one quick Odin flash later and it's booting up happily. However, FRP was enabled and now requires sign-in from the last person to have signed in on it, which is unknown. So I find myself one last step away from an awesome - and surprisingly well looked after - tablet but with no idea of what to do about FRP.
I've done a fair amount of reading and, outside of all those sites that seem to be run by the same Asian gent who is adamant I can only do it with his absolutely-not-suspicious-at-all application, understand that I can either flash 1) a combination file or 2) an old firmware in which the old workarounds are still effective, both of which will allow me to bypass it, but neither of which will work without USB debugging enabled and that can only be done via the developer options. And obviously I can't get to that.
If anyone has any advice on how I can make this work in my favour without having to get rid of it, I would sincerely appreciate it.
Alternatively, if this is the wrong place to post this question, a quick point and a kick in the ass in the right direction.
[Quick edit] I have no issues with rooting if that's what's required. Again, requires developer tools so...
Hint: Add " SM-P585 " to front of this thread's titel thus mainly people who owns such device get addressed, too.
I thought of that, but I don't believe this is an issue limited to my specific device model. I think it could apply to most, if not all, Android devices at some point.
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
andrepd said:
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
Click to expand...
Click to collapse
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
dcarvil said:
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
Click to expand...
Click to collapse
Thanks, I tried that, it is indeed a Verizon model. Do you know if there is any way around this to unlock the bootloader? I guess I'll have to google around a bit to figure out if it's hopeless or not x)
There is no way to unlock a Verizon phone.
Hmm well I'm getting quite mixed signals here:
- imei.info says "Pixel 3 128GB, US VZ, Just Black"
however:
- ro.oem_unlock_supported is 1
- and bootloader screen says "Product revision: MP1.0(ROW)", not "(VZW)"
- box says "ESIM" rather than "SIM"
and also in some threads users report being able to unlock verizon phones... So it's all very strange x)
Pretty much same here. Did you figure out something?
me too
Ok, so a brief update here, the results of my search over the last couple of days:
Most likely, your Pixel 3 cannot be unlocked, it has been locked by Verizon when activated on their network and we don't have a way to undo this OEM lock. If you bought it re-furbished or second hand, and OEM Unlocking is grayed out, the most likely is that there is nothing to do.
Relevant / connected threads:
- https://forum.xda-developers.com/t/oem-unlocking-grayed-out.3860023/page-21
- It can be unlocked before it has activated on verizon: https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
- Some (unsuccessful) attempts are discussed at https://forum.xda-developers.com/t/bounty-unlock-bootloader-vzw-pixel-3-xl.3856605/page-113 and
Use 'fastboot oem citadel' to unlock bootloader? (Verizon Pixel 3)
I unfortunately have a Pixel 3, from Verizon (when I bought it it was not described as a phone issued by Verizon had I known it I wouldn't have bought it). I'm trying to accomplish The impossible by finding some way to unlock the bootloader...
forum.xda-developers.com
- This post pretends that it can be undone, but this has not been confirmed / applies only to very speecific cases:
https://www.reddit.com/r/GooglePixel/comments/sc2w1r
- https://support.google.com/pixelpho...ixel-3-verizon-flashed-3xl-system-image?hl=en
-
https://www.reddit.com/r/GooglePixel/comments/rsrnu0
Hey all,
I work in E-waste (mostly laptops) and I have a few phones I've come across that I've unlocked. I had 3 or 4 Samsung S20 FE 5Gs (ATT) I got my hands on that I used UnlockGo (Android) with and it worked just fine. UnlockGo seems similar to the SamFW software often recommended here on XDA in that you type the USSD code *#0*# and it enables USB debugging to push its payload. It usually goes something like this:
I factory reset via recovery mode
On emergency call menu I type the secret code
it enables USB debugging and resets. It usually works great.
This Samsung S22 Ultra is different. Verizon has explicitly blocked the secret code I need for this software to work, as well as all the rest of them. The UnlockGo software has alternative methods, but none of them are working at the moment. Via those methods:
I added my Samsung account on the phone and attempted to "recover" (smart switch) using another device and that didn't work.
I got into the Samsung store to install software but installation is currently disabled from the Samsung store.
Does anyone have software they would recommend that would work or has worked for them?
I emailed the developer of the UnlockGo software but their responses have been mostly unhelpful. However, I did get a partial refund, so there's that. I imagine FRP unlock is possible because I was solicited by a few individuals on Reddit when I posted there asking the same question as posed above. I'm hoping someone here knows what I should be doing or can point me in the right direction.
It's a shame, as this one was actually in decent condition and I was hoping to give my wife an upgrade.
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
whiggs2 said:
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Click to expand...
Click to collapse
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
jwoegerbauer said:
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
Click to expand...
Click to collapse
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
whiggs2 said:
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
Click to expand...
Click to collapse
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
SubwayChamp said:
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
Click to expand...
Click to collapse
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Droidriven said:
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
Click to expand...
Click to collapse
This - The 'U' devices do not have OEM unlock by default.
whiggs2 said:
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Click to expand...
Click to collapse
This may be just a kind of starting point, to have in mind, but that need more research though, I did it in my GN8 but with your device, things may be different.
There are some things you have to check, in the download screen, KG has to be completed, not prenormal or checking, also search for the CSCs that are compatible for your device, this is one of the tutorial, kind of, that I followed https://www.getdroidtips.com/guide-...ocked-firmware-galaxy-note-8-sm-n950u-n950u1/