I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
oUkcpV9ykzUC said:
I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
Click to expand...
Click to collapse
Is it grayed out in the on or off position? Which is not uncommon on custom roms.
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
So you unlocked it and flashed a custom ROM and then reinstalled the stock recovery and locked it like that for Android pay? Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
nukeruss said:
Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
Click to expand...
Click to collapse
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Forgot to mention, this is NOT a ROM that uses TWRP, but its own recovery. Maybe I'm not understanding you right, but how do I flash a factory image if I can't OEM unlock?
gjkrisa said:
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's not a ROM that uses TWRP but its own recovery. Not sure what you mean by "if you have an issue just switch back if it will take at all".
sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Flashing the factory image using Deuce's script will fix this.
Don't skip any steps.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Larzzzz82 said:
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Click to expand...
Click to collapse
What do you get when you run...fastboot oem device-info...?
Is it grayed out in the on or off position?
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Have you tried adb reboot fastboot?
Larzzzz82 said:
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Have you tried adb reboot fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was no where near a computer... Is that a valid adb command? I go adb reboot- bootloader then fastboot devices before i do anything else.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
The get device-info returned:
Verity mode: true
Device unlocked: true
Charger screen enabled: true
Related
This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app
1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.
1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Fastboot flashing lock? Or oem lock?
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Fastboot flashing lock? Or oem lock?
Click to expand...
Click to collapse
It's that simple? Just run the fast lock command?
shibbnasty said:
It's that simple? Just run the fast lock command?
Click to expand...
Click to collapse
I think lol it's been awhile since I locked a phone
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
I think lol it's been awhile since I locked a phone
Click to expand...
Click to collapse
I guess I should have mentioned as well it's a Verizon pixel xl and I had to use depixel8 to unlock it
shibbnasty said:
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Click to expand...
Click to collapse
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
lyall29 said:
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
Click to expand...
Click to collapse
All I have done is unlock it. I have not flashed any kernels or mods or anything.
shibbnasty said:
All I have done is unlock it. I have not flashed any kernels or mods or anything.
Click to expand...
Click to collapse
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
lyall29 said:
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
Click to expand...
Click to collapse
Thank you very much!
@shibbnasty. Actually, relocking the bootloader may not wipe data. I can't remember. Let me know if it does or not.
Yes it does.
Rank N00b here... just getting that out of the way.
Device: Verizon Pixel XL
Build: NDE63X
Bootloader: unlocked via dePixel8 (done after Nov update)
So the phone is stock and I'm not really keen on modding right now. I don't want to use a alpha build of TWRP and SuperSU seems to be in flux too. These aren't criticisms by the way; I realize this a very new handset and those kinds of tools take time to develop. Nothing happens overnight.
So, anyway, my phone is currently unlocked and I'm wondering if I'm not better off relocking it? As a stock unit, it should still get OTA's, right? Like I said, total n00b here...
@loaba,
There's absolutely no reason to relock your bootloader, unless you are annoyed by the Google bootloader unlock warning during boot, or if you are planning on returning it or selling it. Otherwise, leave it unlocked. Gives you much greater flexibility to recover if something goes wrong.
@cam30era,
Thanks for the reassurance.
loaba said:
@cam30era,
Thanks for the reassurance.
Click to expand...
Click to collapse
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
michaelbsheldon said:
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
Click to expand...
Click to collapse
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
loaba said:
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
Click to expand...
Click to collapse
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
michaelbsheldon said:
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
Click to expand...
Click to collapse
About the OTA's - that was my big concern for now. Cool.
OP - thread derailed... sorry, man.
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Khanusma said:
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Click to expand...
Click to collapse
Most of the custom kernels fix that. Root is the hard one to hide.
So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?
Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?
Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.
cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?
Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased
pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
oliverfongftw said:
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
Click to expand...
Click to collapse
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
If you have the stock recovery and can boot into it you can adb sideload the most recent ota zip.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
ram4ufriends said:
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
Click to expand...
Click to collapse
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
You can get the bootloader lock status simply by booting into the bootloader. Locked or unlocked? You don't "think" it has a working recovery is not good enough to help you. If it does have a stable recovery, you can flash the OTA. If it does not and the bootloader is locked you are S.O.L. and the phone is dead. Follow this video and let us know.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
If you can hold down volume and hit power to get into bootloader and choose Recovery, you can fix this phone.
Go here: read instructions at top. You will be booting to bootloader, then to recovery, then choose Apply Update from ADB.
Then give adb OTA command as described. Don't skip or modify any step.
https://developers.google.com/android/ota
I am in this exact same situation. Did you ever figure it out? Or did anyone figure it out?
Got this exact problem with a locked bootloader and no recovery, any solution?
0x0null said:
Got this exact problem with a locked bootloader and no recovery, any solution?
Click to expand...
Click to collapse
How did you lose the recovery with a locked bootloader?
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
How did you lose the recovery with a locked bootloader?
Click to expand...
Click to collapse
Got it that way thinking i could use recovery to recover the phone
0x0null said:
Got it that way thinking i could use recovery to recover the phone
Click to expand...
Click to collapse
It came without a recovery.
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
mookiexl said:
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
Click to expand...
Click to collapse
Locked bootloader wont let me use the script.
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Strephon Alkhalikoi said:
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Click to expand...
Click to collapse
Yea, your on point. Only edl firehose may save me
0x0null said:
Locked bootloader wont let me use the script.
Click to expand...
Click to collapse
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
mookiexl said:
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
Click to expand...
Click to collapse
It Unlocks only if 'oem unlock' is engaged from the booted system.
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Which is exactly why it should never be in the locked position...
Sent from my Pixel 2 XL using XDA Labs
0x0null said:
Yea, your on point. Only edl firehose may save me
Click to expand...
Click to collapse
and save me to. I try to find firhose for my pixel 2xl but I didn't find it. Hope someone can provide QFIL Firmware to save as.
Sent from my MI 9 using Tapatalk
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Did you try? I used it with no 0S installed so oem unlock couldnt have been engaged.
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Contact Google if you have the packaging unless you bought it second hand. It's under warranty
Sent from my SM-G965U using Tapatalk
tylenol97 said:
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Click to expand...
Click to collapse
Just outa curiosity, was your bootloader locked or unlocked? Also, can you get into stock recovery and bootloader mode??
Badger50 said:
Just outa curiosity, was your bootloader locked or unlocked? Also, can you get into stock recovery and bootloader mode??
Click to expand...
Click to collapse
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
tylenol97 said:
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
Click to expand...
Click to collapse
Can you get into fastboot? Power and volume down?
tylenol97 said:
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
Click to expand...
Click to collapse
Whatever you did doesn't make you stupid my friend. I've bricked 2 phones myself on my android learning experience. If you can get into recovery, you should be able to side load an OTA. Then again, I bet you already tried that.
Badger50 said:
Whatever you did doesn't make you stupid my friend. I've bricked 2 phones myself on my android learning experience. If you can get into recovery, you should be able to side load an OTA. Then again, I bet you already tried that.
Click to expand...
Click to collapse
Thanks.. but i can not get into recovery mode. It just say 'Can't find valid os'
I should go to LG tomorrow.
Thank you for replying!
Goog1e Phone said:
Can you get into fastboot? Power and volume down?
Click to expand...
Click to collapse
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
Then you should at least try deuces recovery script. Who knows, it might work :good:
Or you can go to the proper people, aka google, stop doing whatever shady mess your doing and be careful next time.
Sent from my SM-G965U using Tapatalk
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
..
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
You can load the factory image from Google regardless if you're still OEM locked or not.
It's a signed image from Google... Signed images are accepted by the phone always.
The point of unlocking is to use unsigned images from developers other than google.
tylenol97 said:
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Click to expand...
Click to collapse
I did the same thing and returned and got new device from Google
ImWarped said:
You can load the factory image from Google regardless if you're still OEM locked or not.
It's a signed image from Google... Signed images are accepted by the phone always.
The point of unlocking is to use unsigned images from developers other than google.
Click to expand...
Click to collapse
No. Even google said if user want to flash factory images, whatever it is stock & signed, user should unlock OEM and even bootloader. (Reference : https://developers.google.com/android/images)
I did several times, it didn't work without it.
I sent LG, because i live in korea.
It will be fine.
Thanks!
tylenol97 said:
No. Even google said if user want to flash factory images, whatever it is stock & signed, user should unlock OEM and even bootloader. (Reference : https://developers.google.com/android/images)
I did several times, it didn't work without it.
I sent LG, because i live in korea.
It will be fine.
Thanks!
Click to expand...
Click to collapse
Hi, I also meet the same problem like you. How ur phone right now and how u figure out the solution? Thank.