Related
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.
There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.
plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.
Hey all,
Picked up a Pixel 2 back in August from the Verizon Store. November OTA came through and it went bad - real bad. Bricked the device. I contacted Google and they confirmed it was indeed a brick. So I RMA'd it.
They replaced it with what seems like a brand new Pixel 2. Black 128GB. Same phone.
I didn't hook it up to WiFi. I didn't pop in my old SIM. Powered it up and enabled Developer Options.
Unlock Bootloader is NOT greyed out! :good:
I understand people can get lucky and cop an older VZW Pixel 2, not hook it to WiFi or mobile and sideload the stock image, but here's the deal with this RMA'd device:
Android Version: 8.1.0
Android Security Patch Level: May 5, 2018
Build Number: OPM2.17019.029.B1
Isn't that build too high to be a VZW phone w/ that unlockable bootloader option toggle? Shouldn't VZW have patched the developer option by now? Shouldn't Unlock Bootloader be greyed out if this was a VZW phone? Did I get an unlocked, Play Store Pixel 2 in return?
How else can I verify? If I run the bootloader, it does say:
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Is this okay?
How do I make sure I keep it unlocked if it still could become a VZW phone? Should I flash the latest stock image from Google or is that overkill?
Thanks very much for your help in advance.
-D
dbilodeau said:
Hey all,
Picked up a Pixel 2 back in August from the Verizon Store. November OTA came through and it went bad - real bad. Bricked the device. I contacted Google and they confirmed it was indeed a brick. So I RMA'd it.
They replaced it with what seems like a brand new Pixel 2. Black 128GB. Same phone.
I didn't hook it up to WiFi. I didn't pop in my old SIM. Powered it up and enabled Developer Options.
Unlock Bootloader is NOT greyed out! :good:
I understand people can get lucky and cop an older VZW Pixel 2, not hook it to WiFi or mobile and sideload the stock image, but here's the deal with this RMA'd device:
Android Version: 8.1.0
Android Security Patch Level: May 5, 2018
Build Number: OPM2.17019.029.B1
Isn't that build too high to be a VZW phone w/ that unlockable bootloader option toggle? Shouldn't VZW have patched the developer option by now? Shouldn't Unlock Bootloader be greyed out if this was a VZW phone? Did I get an unlocked, Play Store Pixel 2 in return?
How else can I verify? If I run the bootloader, it does say:
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Is this okay?
How do I make sure I keep it unlocked if it still could become a VZW phone? Should I flash the latest stock image from Google or is that overkill?
Thanks very much for your help in advance.
-D
Click to expand...
Click to collapse
Don't get too excited, my pixel 2 was RMA'd 2x and can not unlock bootloader. By all accounts I should be able too. I am able to toggle oem unlock, and everything else indicates that I can...however, once I try it fails and on developer settings it's greyed out. Only way to know for sure is to try
AsuraDas said:
Don't get too excited, my pixel 2 was RMA'd 2x and can not unlock bootloader. By all accounts I should be able too. I am able to toggle oem unlock, and everything else indicates that I can...however, once I try it fails and on developer settings it's greyed out. Only way to know for sure is to try
Click to expand...
Click to collapse
Thanks for the reply, AsuraDas. That's disappointing. I'm going to give this a go today. I'll let you know what I find.
I'm debating on what stock image I should push. The same one that's on the device? The newest? What did you do? I see another thread that is similar to mine - I'm going to poke around that one and wing it if I don't hear from anyone more familiar with this than I.
NOPE!
Ha. I definitely have a locked bootloader. How deceptive.
I tried to flash the stock google image, same build that's on there now. No luck.
Tried to fastboot and unlock bootloader. Not allowed.
Oh well!
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
What is DePixel?
DePixel8
Who-Lep said:
What is DePixel?
Click to expand...
Click to collapse
It was software that would unlock the bootloader of the Google Pixel and Google Pixel XL that had the bootloader locked to Verizon. The catch was it only worked on Android 7.1.0 I believe. It was patched shortly after so if you updated your device, no luck.
KillerBytes said:
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Click to expand...
Click to collapse
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Kool19 said:
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Click to expand...
Click to collapse
Model number is G020J as well.
got mine from vzw and was able to unlock bootloader as well, removed sim before turning on, set up phone on wifi and check oem unlocking in dev settings before popping in sim card
I am hoping I am in the same boat. I couldn't pass up getting 450 for a pixel xl so I bought the verizon variant it's coming Monday. I have seen where this has worked in the past with the pixel 2. Here is hoping the toggle gets grayed out when it's sees your on verizon's network. I plan on removing sim booting up and getting to developer options taking the least path of resistance and then trying to unlock. If I am successful I will report back.
Well I'm beat my is locked
bigv5150 said:
Well I'm beat my is locked
Click to expand...
Click to collapse
I'm waiting on a 128 GB white from Verizon, but I tried it on my dad's black 64 GB. His is locked as well unfortunately.
I can run adb reboot edl, and it works.
from there I don't know what to do, but I would like to unlock the bootloader, but the option is grayed out like it is for all verizon P3s.
I'm on SW version a2.
I can still return the phone, and I will if I can't unlock the bootloader, but it seems no one has figured out how yet, and I was reading that people were trying to get to EDL mode and couldn't. for some reason mine does EDL fine.
Thanks for any input.
other small question, if I return this pixel 3, what should I look for on ebay or elsewhere to find an unlockable P3.
I understand that the imei number that starts with 35 is verizon. what Imei should I look for to find a unlockable p3?
The MEID on my unlocked P3 bought from Google starts with 99.
dcarvil said:
The MEID on my unlocked P3 bought from Google starts with 99.
Click to expand...
Click to collapse
Thank you so much for the info. I'll see if I can track one down.
Is the Motorola website not working properly for unlocking the bootloader on devices? Every time i try to request the unlock key for it a page that only says "There has been an error with your request." appears. What can i do to unlock the bootloader even with this error?
Where did you get your phone? Some bootloaders are not unlockable.
RETIEF said:
Where did you get your phone? Some bootloaders are not unlockable.
Click to expand...
Click to collapse
Its a T-Mobile 5G ace and i bought it used
LazySomeguy said:
Its a T-Mobile 5G ace and i bought it used
Click to expand...
Click to collapse
If the previous owner possibly still owes money on it then you can't unlock the bootloader. You'd have to get the unlock app from TMO and they'd have to authorize it to make it unlockable bootloader, which TMO won't do if there's money owed on it.
You should be able to unlock it. The exception is if the previous owner relocked the bootloader. In that case, the bootloader cannot be reunlocked.
FoneWatcher said:
If the previous owner possibly still owes money on it then you can't unlock the bootloader. You'd have to get the unlock app from TMO and they'd have to authorize it to make it unlockable bootloader, which TMO won't do if there's money owed on it.
Click to expand...
Click to collapse
the Device Unlock app says that its permantly unlocked
Edit: the seller i bought it from said the IMEI associated with the phone was clean and said it had no problems having to do with not being paid off
I am also having a problem. This seems to be a problem with their website. I tried different browers, computers, and connections. Get that error every time after submitting the device key.
I tried with my new G100, and I have the same error. Any idea of a workaround?
I am having the same error with my Motorola G Stylus 2020 it has to be with their websites ive tried different browsers, computers, they need to solve this issue!!!
same error, i pray their system is down temporarily, G100 with different browsers.
I tried all methods that involve the motorola website I found on the forum but none work. I contacted motorola support, I'll keep you posted if I find anything.
Same here. I called and finally got level 2 support which said they couldn't help. They sent me to the motorola forums where I've asked about it. Will post if I get a reply as well.
Here is a link for the motorola unlock bootloader thread. Post your device ID there
English Community-Lenovo Community
I asked support and they told me the site was down and should be up in a few day. I re-tried now and it worked. I got my code. But the OEM unlock option in the developer settings is still grayed out. Apparently I have to wait which is stupid, I'm very close to just return the phone.
kuon-orochi said:
I asked support and they told me the site was down and should be up in a few day. I re-tried now and it worked. I got my code. But the OEM unlock option in the developer settings is still grayed out. Apparently I have to wait which is stupid, I'm very close to just return the phone.
Click to expand...
Click to collapse
Yep. i did it just now and the site seems to be working again
confirmed working again
Ok, for reference, as there are some different things scattered alongside the forum.
I have a G100, german model (I'm in switzerland, but it's considered german).
What I had to do:
- go here <https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a>
- contrary to what customer service told me, the global portal works, even with a german model
- the website was down, but it's up now, if it's down for you, I guess you'll have to try again, customer support did not help me
- BUT, to be able to use the unlock code with `fastboot oem unlock <code>` you need first to activate "OEM unlock" in the Developer settings.
- To access this settings, you need to activate the phone. Some says it works on wifi, but I used LTE for the initial setup, just to be sure. After the setup, I did a few calls, I don't know if this is significant, but the first call took like 5 minutes to connect (I say this because you might be tempted to turn the phone off right after the activation). I applied all the updates, left my phone on my desk, and after 72h this settings was accessible (not grayed).
- After toggling the setting, you can use `fastboot oem unlock` and proceed with lineage installation
I just successfully bootloader unlocked a Moto G 5G (2022) using the website. It took them about five minutes to email me the unlock code after I submitted the string on the website.
Keep in mind that you are referencing two different things: network locks, and bootloader locks. The device may have a clean IMEI and be network unlocked (you can use any carriers SIM in the SIM tray). This doesn't necessarily mean that the bootloader can be unlocked for purposes of flashing custom ROMS. You'll need a phone that is both network unlocked and has an unlockable bootloader.
that's why wiko is better........
I'm having the same issue but with my xt2131-1 model. I received the unique code via email and it says failed to validate code.