Related
Hello. I received the OTA update, install it pressed and then I have not loaded tablet.
What should I do?
I Tried:
- wipe data/cache
- charge device
Unlock OEM is not allow (in setting). And I can't unlock bootloader
I dot no my friend but, ota today ? New ota ?
Or it this your first boot on new tablet?
Anyway good luck, wait for pro advice , maybe with PC/cable.
Nothing new Snegovik for your problem ?
xennos said:
Nothing new Snegovik for your problem ?
Click to expand...
Click to collapse
No, I have not solved the problem. The tablet is not loaded, and I can't flast it.
My advice: Allow OEM unlocking the bootloader in the Setting
sad...
I need to find an OTA update on flash recovery. But I can not find it ((
are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.
dkryder said:
are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.
Click to expand...
Click to collapse
What you mean?)
Who can get OTA link?
Please see:
http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/
I want a try flash a OTA from adb sideload)
SnegovikRZN said:
What you mean?)
Click to expand...
Click to collapse
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.
dkryder said:
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.
Click to expand...
Click to collapse
Unfortunately this does not work (
Maybe you need to install ADB USB driver manually.
Once fastboot is working .. fastboot flashing unlock
generally that message is shown when the allow oem unlock switch in developer options is not set on.
dkryder said:
generally that message is shown when the allow oem unlock switch in developer options is not set on.
Click to expand...
Click to collapse
yes...
but I can not set it in Setting, because my device is not bott
well, if you still have the device then one possibility is to post your issue to this group,
https://groups.google.com/a/chromium.org/forum/#!forum/chromium-os-discuss
to see if there is a flag in the vbnv that can be set with fwtool. [similar to fastboot issue] to get it to boot.
Pixel C bootloop[
SnegovikRZN said:
yes...
but I can not set it in Setting, because my device is not bott
Click to expand...
Click to collapse
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?
vtirugudu said:
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?
Click to expand...
Click to collapse
Yes you can unlock same as you would a Nexus device.
bill3508 said:
Yes you can unlock same as you would a Nexus device.
Click to expand...
Click to collapse
How to unlock the device?
HI there,
I get same problem, not possible to active Debug & Dev on android setting, because the tablet dosnt load to android !
I tried with Nexus Root Toolkit no success also
My non-Verizon Pixel XL is stuck with a locked bootloader, OEM Unlocking Disabled, and is unable to boot to recovery, or the system (thus I cannot enable OEM unlocking). When I try to boot, it has the red message stating that my device is corrupt, then it turns off and does not boot.
How can I fix this?
I has AOSPA installed before this all went down, but I agree I made some dumb moves, and I am hoping someone here can help me out of this hole.
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
-Maverick- said:
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
Click to expand...
Click to collapse
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
3aucla1r3 said:
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
Click to expand...
Click to collapse
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
-Maverick- said:
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
Click to expand...
Click to collapse
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
gettingerr said:
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
Click to expand...
Click to collapse
Unlikely. Are they going to attempt a repair, or just outright replace the phone?
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
You have to have to unlock your bootloader to install any custom rom on the pixel.
Hey did you ever solve this? im in a similar prediciment. My phone keeps bootlopping, trying to flash an older ROM but bootloader is locked and none of the fastboot oem unlock commands work.
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
Do it now!
@t4nks120
The bootloader unlock for the Verizon Pixel/Pixel XL is working. Go here to unlock it.
EDIT: Solution: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
frap129 said:
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
Click to expand...
Click to collapse
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Sent from my MHA-L29 using Tapatalk
danon.brown said:
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Click to expand...
Click to collapse
I already tried that command as I said in my post (unless there's one other than "fastboot flashing unlock" that I'm not seeing in the essential forum)
Can you see your phone with fastboot devices?
Sent from my MHA-L29 using Tapatalk
A few others with the phone have reported the same issue in the "rooting" thread...not sure what's going on!
I had the essential phone and had to get a more current Version of adb.
Sent from my MHA-L29 using Tapatalk
did you enable developer settings and see if there is a setting to allow OEM unlock?
Code:
fastboot flashing unlock
will unlock it
When I first booted the phone and enabled USB debugging, the OEM Unlock was greyed out. I had to put my sim card in for it to allow me to enable it. Then using the fastboot flashing unlock worked from bootloader.
fastboot flashing unlock worked for me.
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
@frap129 hope you get it sorted. Glad to see you got a 2 XL as well! Would love to eventually see Carbon and Electron on the 2 XL. Have been missing them since I RMA'd my 6P for an XL. :good:
What is the point if the stock android phone has locked bootloader!
I miss NEXUS phones
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Thanks for all the responses, I guess it's just my fastboot version. I have the latest that's on the aur, but I'll try manually downloading from Google's site.
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
cryppie said:
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Click to expand...
Click to collapse
Disagreed. This was not necessary with the OG Pixel.
Further, I think most people here know that the chances of unlocking a Verizon bought Pixel are slim to none.
dirtyfingers said:
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
Click to expand...
Click to collapse
Ive been using adb reboot the whole time and can't get it to work, thanks for the heads up!
UPDATE: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Sorry for the double post, I just wanted to make sure anyone following this with the same issue gets the solution.
cwalker0906 said:
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
Click to expand...
Click to collapse
You could have also used the sdk manager to update the platform-tools.
I am not able to flash anything via fastboot.
i tried every way to flash via fastboot mode but nothing works.
I am on 9.2.7.0 rom.'
I really need any solution.
looks like my fastboot is broken.
while trying to work fastboot, I mistakely locked my bootloader
and now when i go to fastboot mode.
my pc shows its fastboot but in miunlock tool
itdoesnt show my device.
If anyone one can help or experienced this issue , kindle please help
I have same sitauation like this:
https://forum.xda-developers.com/redmi-note-5-pro/help/error-flashing-twrp-pc-t3786357
so if this issued is solved tell me the solution
Rohan_sadhwani said:
I am not able to flash anything via fastboot.
i tried every way to flash via fastboot mode but nothing works.
I am on 9.2.7.0 rom.'
I really need any solution.
looks like my fastboot is broken.
while trying to work fastboot, I mistakely locked my bootloader
and now when i go to fastboot mode.
my pc shows its fastboot but in miunlock tool
itdoesnt show my device.
If anyone one can help or experienced this issue , kindle please help
I have same sitauation like this:
https://forum.xda-developers.com/redmi-note-5-pro/help/error-flashing-twrp-pc-t3786357
so if this issued is solved tell me the solution
Click to expand...
Click to collapse
Did you try a different PC/ USB cable? seems like driver issue to me.
while trying to work fastboot, I mistakely locked my bootloader
Click to expand...
Click to collapse
Did you unlock it again with the Mi Unlock tool?
Make sure to enable USB debug in developer options again.
And did you turn on OEM unlock in developer options again also.
ecrum said:
Did you try a different PC/ USB cable? seems like driver issue to me.
Click to expand...
Click to collapse
Yes i tried all. But no luck. Even now it doesn't unlocking. I am traped
corkiejp said:
Did you unlock it again with the Mi Unlock tool?
Make sure to enable USB debug in developer options again.
And did you turn on OEM unlock in developer options again also.
Click to expand...
Click to collapse
Yes, i did all the steps properly. But it even not showing anything
Rohan_sadhwani said:
Yes, i did all the steps properly. But it even not showing anything
Click to expand...
Click to collapse
I know you probably enabled the options when you first unlocked. But did you enable them again after your device was wipe from the unlocking process?
Can you boot the current rom on your device?
If the rom is not booting, you may need to try and flash stock fastboot rom in EDL Mode (If that is still an option for this device).
Edit: - As you locked the bootloader with fastboot command, have you tried the fastboot unlock command
Code:
fastboot oem unlock
What response are you getting from "fastboot devices" while in fastboot.
also what is "fastboot oem device-info" reporting?
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Don't Ask said:
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Click to expand...
Click to collapse
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
liam_davenport said:
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
Click to expand...
Click to collapse
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Don't Ask said:
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Click to expand...
Click to collapse
Sorry missread... My bad Contact Google sounds like an RMA job for this one
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
khoanguyen96 said:
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
Click to expand...
Click to collapse
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Don't Ask said:
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Click to expand...
Click to collapse
Hey, yeah I looked into EDL mode. No luck unfortunately, looks like it requires special files manufacturers only have access to. Is there any way you can do a RMA?