Related
So I cannot unlock my Google Pixel every time I try the commands in ADB it gives me this error...
c:\adb>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.012s
I have tried a few other commands and they didn't work either. And before anyone asks YES it is from Google Store not from Verizon. If anyone has any ideas it would be greatly appreciated thanks!
Did you enable developer options and check allow bootloader unlocking?
Assuming OEM unlock toggle is active in Dev Options...
Replace "oem" with "flashing".
fastboot flashing unlock
fritzgerald said:
Assuming OEM unlock toggle is active in Dev Options...
Replace "oem" with "flashing".
fastboot flashing unlock
Click to expand...
Click to collapse
The settings toggle is greyed out...
DJ Josh N said:
Did you enable developer options and check allow bootloader unlocking?
Click to expand...
Click to collapse
That option in the dev settings is greyed out so I can't click it.
Jubbard said:
That option in the dev settings is greyed out so I can't click it.
Click to expand...
Click to collapse
connect ur phone to wifi and let it verify
Tech_Savvy said:
connect ur phone to wifi and let it verify
Click to expand...
Click to collapse
It is always connected to wifi
What are the last three digits of your device Serial number?
Jubbard said:
It is always connected to wifi
Click to expand...
Click to collapse
Jubbard said:
The settings toggle is greyed out...
Click to expand...
Click to collapse
Jubbard said:
That option in the dev settings is greyed out so I can't click it.
Click to expand...
Click to collapse
If it's connected to the internet and still greyed out, sad to say you most likely have a Verizon model.
Jubbard said:
That option in the dev settings is greyed out so I can't click it.
Click to expand...
Click to collapse
If oem unlocking is greyed out then unfortunately you are stuffed. You can't unlock your bootloader. Especially if you are already on Oreo. If you are on Nougat it's possible but don't know if you can downgrade and try. Maybe? You need search the forums for unlocking a verizon phone. You can't unlock on EE in the UK and possibly other carriers around the world too.
At this point if you bought it from Google call them. The either sent you a VZ phone or the one you got isn't in their database to allow unlocking. I suspect the latter.
I've got my Bootloader unlock password from the Huawei website.
When I use adb reboot bootloader the phone successfully reboots into fastboot.
But when I try to unlock my bootloader I get:
Code:
fastboot oem unlock my16digitBLcode
...
FAILED (remote: password wrong)
finished. total time: 0.014s
I have enabled OEM unlock and USB debugging
Model: BLN-L21
Build: BLN-L21C432B368
Android 7.0
I also get:
Code:
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
and:
Code:
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.003s]
finished. total time: 0.004s
Why does it say that my password is wrong?
I've checked the SN and IMEI many times - and even used the IMEI2 and MEID on the Huawei website but I get the exact same unlock password.
The german customer service sent me the same unlock password.
I'm thinking about using dc-unlocker but I don't want to spend 4€ just to find out that it will generate the same bootloader unlock password that I already have.
Would downgrading help?
Or can I use kingoroot to root it?
Maybe FRP is locked,take a look at fastboot mode.
Gesendet von meinem BLN-L21 mit Tapatalk
So weird that it keeps saying wrong password... Are you completely sure that it is correct? (I don't think that you can't read, it's just for being sure because that's what the command says)
FRP is unlocked when I have enabled OEM unlock in developer mode.
FRP is locked when I have disabled the OEM unlock option in developer mode.
I've tested it with both options but when I have disabled the OEM unlock it tells me that the command is not allowed.
I have checked the SN, IMEI and the unlock password many times.
I even used the IMEI2 and MEID on the Huawei website but I get the exact same unlock password.
Did you ever figure out what's wrong? I have the exact same problem.
No, unfortunately not.
I have the same problem
Venkat Bharadwaj said:
I have the same problem
Click to expand...
Click to collapse
same here
Same here, something wrong on Huawei calculator I think.
same issue but fixed
i had the same issue huawei gave me a password but did not work i tried hcu client it gave me a password and it successfully worked i dont know if bootloader password changes if i change oem info or something like that
kudo01 said:
i had the same issue huawei gave me a password but did not work i tried hcu client it gave me a password and it successfully worked i dont know if bootloader password changes if i change oem info or something like that
Click to expand...
Click to collapse
How much did you pay for it and are the 2 bootloader codes totally different from one another?
Can you check if there is a pattern between the two when you convert them to hex?
CryptLoad said:
How much did you pay for it and are the 2 bootloader codes totally different from one another?
Click to expand...
Click to collapse
i paid 5 usd and they are totally different its really different huawei gave me a code starting with 22 and hcu gave me a code that starts with 76
CryptLoad said:
Can you check if there is a pattern between the two when you convert them to hex?
Click to expand...
Click to collapse
if you tell me how to do it i can check
do you know if password changes if i flash any oem info or if i debrand ?
---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------
CryptLoad said:
I'm thinking about using dc-unlocker but I don't want to spend 4€ just to find out that it will generate the same bootloader unlock password that I already have.
Click to expand...
Click to collapse
i used hcu and code was different you should try if your phone still with bootloader locked if you cant unlock boot loader i'll give you the 4 euros i paid 5 usd because i paid by paypal
but i'm sure you will be able because i said the same that dc unlocker or hcu will give me the same code but was completelly different and it worked !
This is because honor has disabled bootloader unlocking in all its current phones.
you will no longer be able to unlock it anymore...
CryptLoad said:
I've got my Bootloader unlock password from the Huawei website.
When I use adb reboot bootloader the phone successfully reboots into fastboot.
But when I try to unlock my bootloader I get:
Code:
fastboot oem unlock my16digitBLcode
...
FAILED (remote: password wrong)
finished. total time: 0.014s
I have enabled OEM unlock and USB debugging
Model: BLN-L21
Build: BLN-L21C432B368
Android 7.0
I also get:
Code:
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
and:
Code:
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.003s]
finished. total time: 0.004s
Why does it say that my password is wrong?
I've checked the SN and IMEI many times - and even used the IMEI2 and MEID on the Huawei website but I get the exact same unlock password.
The german customer service sent me the same unlock password.
I'm thinking about using dc-unlocker but I don't want to spend 4€ just to find out that it will generate the same bootloader unlock password that I already have.
Would downgrading help?
Or can I use kingoroot to root it?
Click to expand...
Click to collapse
Request code once again code and cross check the code
Site is working and you still able to unlock bootloader
https://emui.huawei.com
Go to unlock section
use pc to request code to avoid mistake
Copy code from from browser and paste directly in cmd
pranacrockz said:
This is because honor has disabled bootloader unlocking in all its current phones.
you will no longer be able to unlock it anymore...
Click to expand...
Click to collapse
Nooe. Any phone purchased before 25th May will get it till 22nd july only. Post that no bootloader codes. Once you have the code, you can do it anytime
get eror (wrong password)unlock bootloader
when i unlock with huawei unlock code i got this eror in fastboot(unlock failed wrong password)
frp unlock
device locked
S/N:6AGDU17804001314
IMEI:864595034487391
PRO ID:21895633
this is my device info
please if anyone can help send me a unlock code here
or to my email.
[email protected]
majid.hashemi said:
when i unlock with huawei unlock code i got this eror in fastboot(unlock failed wrong password)
frp unlock
device locked
S/N:6AGDU17804001314
IMEI:864595034487391
PRO ID:21895633
this is my device info
please if anyone can help send me a unlock code here
or to my email.
[email protected]
Click to expand...
Click to collapse
Did you debrand or updated to oreo?
get eror (wrong password)unlock bootloader
7
shashank1320 said:
Did you debrand or updated to oreo?
Click to expand...
Click to collapse
android is 7.0 i want update with costom rom
actualy the code that i got from huawei website was wrong
i try 3 time but i got same code and dont work for me
i send my device info in first post
any help?
Don't type the password inside brackets when typing the command...
Mahitosh said:
Don't type the password inside brackets when typing the command...
Click to expand...
Click to collapse
Dear friend, I see this error when I write the unlock code in cmd.(fastboot oem unlock 16thdigit)
oem unlock failed.wrong password
If it is possible for you to get unlock code for me please help.the code I received is wrong.
EMUI 5.0.2
BLN-L21
S/N:6AGDU17804001314
IMEI:864595034487391
PRO ID:21895633
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
I'm shocked there is absolutely no discussion on the new method that just launced. Due to the lack of activity, it's not made clear if the bootloader unlock method unlocks the sim card as well.. I don't even know if the method is worth taking or has any significant issues in the longrun..
Convert to international and it bypasses it
Edit:
Nevermind didn't read it correctly
If you're talking about the q upgrade to get bootloader unlocked. I'm kind of surprised too.
I unlocked my bootloader via that method and it did not sim unlock my op7p. I dropped an at&t sim and it told me the phone is network locked and to use the Tmo unlock app.
Any method of getting it Sim unlocked if you are outside of the US?
flyhotstuff said:
Any method of getting it Sim unlocked if you are outside of the US?
Click to expand...
Click to collapse
None that I know of if you buy a network locked version like the GM1915 from TMobile. Have to go through the carrier for SIM unlock on those.
The guy that started the tmo to international conversion thread said it's possible, but complicated and would be release later. Hope they get it out soon.
The Q unlocks the bootloader but the GSM SIM is still locked. I tried this command and got this response
./fastboot erase modemst2
Erasing 'modemst2' FAILED (remote: 'Erase is not allowed for Critical Partitions
')
./fastboot reboot
Rebooting OKAY [ 0.002s]
Would be grateful to find someone with useful info on how to sim unlock this phone.
Thanks
man, would love to find a way to sim unlock this outside the US. sucks
If you have t-mobile version there are 2 guys on guide thread that unlock the phone through the t-mobile app. If your using t-mobile outside the carrier you will have to pay to a 3er party service eBay haves them
Do you know of any 3rd party service that can do this? Please let me know, thanks
---------- Post added at 07:35 AM ---------- Previous post was at 07:35 AM ----------
dami00976 said:
If you have t-mobile version there are 2 guys on guide thread that unlock the phone through the t-mobile app. If your using t-mobile outside the carrier you will have to pay to a 3er party service eBay haves them
Click to expand...
Click to collapse
Thanks but do you know of any 3rd party service that can do this? Please let me know, thanks
Same question. I bought one on eBay and I haven't been able to unlock it for free. Im outside US so I'm not able to activate phone on T-Mobile also.
LexApp said:
Do you know of any 3rd party service that can do this? Please let me know, thanks
---------- Post added at 07:35 AM ---------- Previous post was at 07:35 AM ----------
Thanks but do you know of any 3rd party service that can do this? Please let me know, thanks
Click to expand...
Click to collapse
Have you tried this first?
fastboot flashing unlock
then
fastboot flashing unlock_critical
LexApp said:
The Q unlocks the bootloader but the GSM SIM is still locked. I tried this command and got this response
./fastboot erase modemst2
Erasing 'modemst2' FAILED (remote: 'Erase is not allowed for Critical Partitions
')
./fastboot reboot
Rebooting OKAY [ 0.002s]
Would be grateful to find someone with useful info on how to sim unlock this phone.
Thanks
Click to expand...
Click to collapse
juanocastro813 said:
Have you tried this first?
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
No i haven't but tried it right away, didn't work. It returns already unlocked. Please see attached image. Any other idea?
Refer to my thread (https://forum.xda-developers.com/oneplus-7-pro/how-to/t-mobile-op7-pro-sim-unlock-t3957662) if you need your T-Mobile OP7 Pro SIM unlocked.
The issue is that I'm outside US. I bought my phone on eBay and it had outstanding balance. The seller didn't provide me with the information you need for unlocking.
mobbdeep said:
Refer to my thread (https://forum.xda-developers.com/oneplus-7-pro/how-to/t-mobile-op7-pro-sim-unlock-t3957662) if you need your T-Mobile OP7 Pro SIM unlocked.
Click to expand...
Click to collapse
I'm in the same boat
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
I'm in the same boat. Waiting for a solution outside the USA. Remote unlock etc
juanocastro813 said:
Have you tried this first?
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
i think this command is for unlocking your bootloader
flyhotstuff said:
i think this command is for unlocking your bootloader
Click to expand...
Click to collapse
No, these commands are for the dangerous ability to flash & erase criticals like modem.
The code to unlock BL is:
fastboot oem unlock
(Erases all data)
---------- Post added at 08:08 AM ---------- Previous post was at 07:53 AM ----------
I dunno if BL can be downgraded bc OP7P starts on android 9 rom which has security patches which prevent flashing to modem.
Found this thread for a different phone which has the same issue you guys are having:
https://forum.xda-developers.com/essential-phone/help/failed-remote-flashing-allowed-modem-t3924591
If BL can be modified, the perhaps you can erase/flash Modemst1 & 2. If anyone knows of someone who tinkers with BL, bring them here :fingers-crossed:
Moses M said:
No, these commands are for the dangerous ability to flash & erase criticals like modem.
The code to unlock BL is:
fastboot oem unlock
(Erases all data)
---------- Post added at 08:08 AM ---------- Previous post was at 07:53 AM ----------
I dunno if BL can be downgraded bc OP7P starts on android 9 rom which has security patches which prevent flashing to modem.
Found this thread for a different phone which has the same issue you guys are having:
https://forum.xda-developers.com/essential-phone/help/failed-remote-flashing-allowed-modem-t3924591
If BL can be modified, the perhaps you can erase/flash Modemst1 & 2. If anyone knows of someone who tinkers with BL, bring them here :fingers-crossed:
Click to expand...
Click to collapse
any advance whith this?
Lussardi said:
any advance whith this?
Click to expand...
Click to collapse
I used cellunlocker dot net and they got it unlocked in 7 days. It's about 45 bucks
so I have the following Scenario, I was able to use the temporary unlock on the Tmobile app, I put another sim and it works, I have read this is only for a month, but if I switch to the international version will the unlock stays? have anybpody tried that before?
I recently bought a refurbished pixel 2 from a phone repair shop and i went through the process to unlock the bootloader, enabling dev options, enabling oem unlocking and usb debugging, ect. but when i boot into the bootloader and run
Code:
fastboot flashing unlock
, it throws an error
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
but when i run fastboot flashing get_unlock_ability it returns
Code:
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
result of 'adb shell getprop sys.oem_unlock_allowed' is 1
result of 'adb shell getprop ro.boot.cid' is 00000000
im running linux and ive tried running the command as sudo and just launching a root terminal to no avail. If anyone can help, it would be very much appreciated
EDIT: Now im even a bit more confused. i ran
Code:
fastboot oem device_info
and it returns
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
[B](bootloader) Device critical unlocked: true[/B]
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
so if critical is unlocked why cant i just unlock the bootloader?
How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?
N5X_ita said:
How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?
Click to expand...
Click to collapse
any phone this old listed as new or brand new is 100% refurbished in china using the ****tiest parts and then boxed in a really poor recreation of the stock box and shipped off to a distributor in your country
Any update? Same issue here
maybe you need to use the "oem unlock" command instead of "flashing unlock".
#5
I also have the same problem
is it possible to unlock via some type of APK without PC
I know that the refurbished pixel 2s that Google sends as replacements have locked bootloaders.
Also the Verizon wireless variant of the pixel 2 has a locked bootloader
So it could be that who ever refurbished your device locked the bootloader permanently
Sent from my Pixel 3a XL
I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?
xp99 said:
I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?
Click to expand...
Click to collapse
Im fairly certain that you need to have unlocked bootloader to root the phone.
Sent from my Pixel 3a XL
eyeyousee said:
maybe you need to use the "oem unlock" command instead of "flashing unlock".
Click to expand...
Click to collapse
oem unlock gives the same error
I'm just grasping at straws here, but did you try *relocking* the device from the critical_unlock, and the unlocking it with the regular unlock command?
I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?
13kai13 said:
I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?
Click to expand...
Click to collapse
maybe there is some sort of failsafe in the kernel that stops it from being bootloader unlocked if a component on the board has been replaced? or maybe google just says "frick you, pay more money if you want root"
but that's just a theory.... A GAY THEORY
Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?
fc3211 said:
Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?
Click to expand...
Click to collapse
The refurbished units whether is a Google refurbished or Verizon unit all have locked bootloaders [emoji58]
Sent from my Pixel 3a XL
This is why I regret doing a warranty through Google Fi. I even had it replaced twice. Both times, the bootloader was locked. It appears to be unlock-able, but then this happens.
Does anyone know if this is limited to just the Pixel 2? I never had this problem with the Nexus 5X phones I had.