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.
Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my [device_name] using XDA-Developers Legacy app
jasonbiggs said:
Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Click to expand...
Click to collapse
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.
crixley said:
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.
Click to expand...
Click to collapse
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
I'm not advising anything here, but I'm not sure how they'd know. If you mention it straight off the bat I'm sure they aren't going to do anything for you.
Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help
bbacon said:
Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help
Click to expand...
Click to collapse
You can't switch slots with a locked bootloader.
I feel like we should be able to fastboot flash stock images even if bootloader locked, or at least separate the recovery from the boot image. Seems like a dumb idea how they have it currently, since if anything happens to the boot image you're stuck with a paperweight.
Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images
b00ster23 said:
Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.
crixley said:
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.
Click to expand...
Click to collapse
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota
b00ster23 said:
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.
b00ster23 said:
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.
Click to expand...
Click to collapse
Several people have sent back 3 or 4 and had the same thing happen every time. Unfortunately I can't go a week per time without a phone since I use mine for work, and they refuse to send me a new one.
crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
I have the same problem. My bootloader is unlocked. Can you please help me?
Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
Hi @Zilchary .
So, finally what have you did?
My Pixel 2 gets that same error after December 2018 Security Patch applied.
I bought my Pixel 2 directly from Google Store USA.
So I enter the CHAT for PIXEL SUPPORT (from Google REPAIR , then Contact US), And Explain I got stuck in Bootloader locked with Error: Slot Unbootable
They immediately understand the problem and tell me I need to RMA (Return merchandise authorization) the phone,
so the Information they ASK ME was :
1) My Phone IMEI, with that info they tell me That I had purchased the Phone in Google Store
2) So they ASK for the "ORDER ID" in my account in Google Store, And with that info they ask me to choose between two options:
3) a) Me to Send first my phone, wait for delivered to them (they need to check the phone) and then send me a REFURBISHED PHONE. or b) PRE-Charge my Credit Card with the price of a Pixel 2,
so They send right now a REFURBISHED phone and IF they don't get my Pixel 2 in "X" day they will actually apply the Charge to my Credit Card.
So the way I see the matters, PIXEL 2 phones has 24 months of warranty in countrys where Google sell it, but you will have problems if YOU DON`T HAVE the "ORDER ID" of the Google Store.
If you actually have this "ORDER ID" because the seller gave you that info when you Purchase, YOU can just tell the PIXEL SUPPORT to send you the FEDEX information (the FEDEX LABEL TO SEND THE PHONE) to your NEW EMAIL (your actual email)
But If you don't have the "ORDER ID" you will have to try to contact the seller to get that "ORDER ID" or you should explain to COSTUMER SERVICES that you don't have it but that will be messy.
and don`t even imagine if the PHONE has BAD IMEI report.
Let me know what happens with your phone
and Have you try this link to github ? (read section: "ERRORS" between sections "iYTBP" (Youtube) and "CameraNX")
Hi @sabrosolatino
The phone was actually my sister's, I asked her what she did and this was her response :
I called 866 246 6453 to the google support line.
The Android reboot system came up and I couldn't reboot or get out of the same screen. The first time I called they told me to click a combination of keys to try to reboot the system. Nothing worked. He told me he needs the order ID # to process the warranty to get a replacement phone. I didn't have the order ID # and told me to call back when I have it. He also said because I don't have the order ID #, I can call their partner repair centers and bring it in to get it fixed or have someone come to the house to fix it in real time. I called the 2nd time and spoke to a different rep, he told me I have a 2-year warranty if there are no physical damages to the phone (until 4/23/20) and the next step is to ship out my phone and get a replacement. They confirmed my email address and sent me the shipping labels. He didn't need an order ID # to process the replacement.
So yes, there was nothing we could do since we couldn't boot it into recovery, ended up shipping out the phone without an order ID #.
Hope everything goes well for you!
I was also told that after she got her phone RMA'd, the phone she got was a refurbished phone at the agent said "It's basically brand new".
This isn't a new issue, it typically happens with something doesn't flash right. Using this tool and applying the monthly update helps me out of this bind every time.
that did it, select reboot bootloader then fastboot --set-active=a in command prompt window, then use the flash-all.bat with "-w" removed in the extracted factory image. Profit!
Zilchary said:
Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
Click to expand...
Click to collapse
Oh, man. This is exactly what happened to my Pixel 2. I bought mine stock, new, from VZW in August 2018. November OTA came in and the phone didn't install the update properly and I landed on this screen. There was absolutely nothing I could do. A few fastboot commands would return some data but because of the locked bootloader I was SOL.
I RMA'd mine. Google didn't even ask questions. They just asked me to turn the phone in.
I'm sorry you can't RMA yours.
I don't know, friend. You might be looking at a paperweight.
I just recieved my phone and before I installed anything, I was going thru it and saw that it has the option to enable oem unlock? Anyone else get this or able to further a rooting process since it has it enabled?
OEM unlock in the settings just sets a bit in frp partition.
This would allow you to unlock the bootloader IF you could
1) access the bootloader in the first place
2) it would have the necessary commands available
2a) fastboot oem unlock (android standard)
2b) fastboot flash unlock unlock.bin (or so, for LG) with the unlock.bin provided by lg, generated by device id and imei (aka needs to be whitelisted by them)
on the sd845 devices, those that flash an engineering bootloader from someone with an octoplus box, use 2a because thats available there (after they had to wipe laf to enter fastboot)
but for that to try you would need
1) someone with an octoplux box, capable of flashing to sd855 LG devices
2) some leaked engineering bootloader (or create your own via reverse engineering, but one wrong step here, and brick basically)
I appreciate the return and detailed response. I am moving from the samsung galaxy s8 active to this V50. So I got excited about seeing the enable oem switch in developers mode, being that the s8 doesnt even display it. I miss being able to tinker with a device since the nexus 5x. This one is a beaut tho. So we'll see if life can adjust to it. the S8 was good, overall, for what it was. But having a secure, or at least ipi68+mil std, is not for one who enjoys to tinker. You mentioned about LG whitlisting it. Is there such a way to have that requested, or is it a result of a form of consequence?
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.
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.