Relock Verizon pixel without brick - Google Pixel XL Questions & Answers

How do I relock my verizon pixel bootloader without bricking it? I'm 100% on stock X rom anyway, radios and all. I never rooted or ROM'd.
reason behind it, is I want android pay and other things to work like the android lock so if you lose your phone, kind of like icloud lock I assume?. I don't root or rom my phone anymore since galaxy nexus days, I like the stock ROM... and if Verizon is on PAR with giving OTAs immediately as google says they will be controlling OTAs, there isnt a reason for me to unlock this thing anymore. I only unlocked it strictly if Verizon was going to delay stuff.

adb reboot bootloader
fastboot flashing lock

deuce_biggins said:
adb reboot bootloader
fastboot flashing lock
Click to expand...
Click to collapse
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.

imablackhat said:
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.
Click to expand...
Click to collapse
Two things:
1) If your system is normally booting and stock 100%, relock should be fine. in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
2) Do a back up. Boot into OS. Turn on USB debugging and turn on your home screen. Then:
adb backup -all -apk -shared -f backup-Dec1.ab
And restore after locking bootloader. The reason for this is that locking bootloader will probably wipe your device just like unlocking it.
Sent from my sailfish using XDA Labs

nednednerb said:
in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
Click to expand...
Click to collapse
I never hear of this. Can you tell me more?

cam30era said:
I never hear of this. Can you tell me more?
Click to expand...
Click to collapse
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs

nednednerb said:
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?

Tisch22 said:
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?
Click to expand...
Click to collapse
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs

nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Fastboot continue does load up the OS, however once it starts optimizing the apps it goes to a black screen.

nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Scratch that, I was able to get back into the OS via "Fastboot continue" however unlocking the bootloader again to reflash the img is becoming quite troublesome.

Related

Device Bricked

Hi,
I had unlocked my boot loader to flash TRWP. But after unsuccessful attempt of H2OS installation I tried relocking my boot loader. Now device is not starting and its just showing blank screen. White Notification LED is there but nothing on screen. Need urgent help.
You...locked it with H2OS and...what recovery? What did you even do
ming3r said:
You...locked it with H2OS and...what recovery? What did you even do
Click to expand...
Click to collapse
I had official TWRP installed. I booted device into Fastboot mode and run "oem bootloader lock" command
Why? there is no real disadvantage to having unlocked bootloader and relocking often results in problems,. I have read of people recovering from this after contacting opo CS so that would be my advice
nileshwagholikar said:
Hi,
I had unlocked my boot loader to flash TRWP. But after unsuccessful attempt of H2OS installation I tried relocking my boot loader. Now device is not starting and its just showing blank screen. White Notification LED is there but nothing on screen. Need urgent help.
Click to expand...
Click to collapse
Hi, this is my first post but I had a similar problem after flashing H2OS and relocking bootloader. I solved it by holding down the power button until the white LED went out and then I booted into fastboot (power + Vol up) . from there I unlocked the bootloader and since then the phone seems to be working fine.
I hope that helps, at least in the short term
I am using OnePlus 3 with TWRP recovery and H2OS.
Hi, There http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 is the method to unbrick.
Method 2 i have used and it works.
Here https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/ method to restock the phone.
Best Regards.

Unrooted Nexus 5x stuck in bootloop

Hi my nexus 5x has started bootlooping on the google screen for no apparent reason. I have not rooted the device and it's bootloader is locked. I'm able to fastboot but selecting recovery mode returns me to the loop. I've tried using wugs nexus toolkit to flash stock but the it just returns me to the loop as the boot loader is locked. Is there any way to unlock the bootloader or return to factory settings/get out of the loop?
There is literally like five threads describing the same issue. Take a look in the Q&A forum
helpmynexuspls said:
Hi my nexus 5x has started bootlooping on the google screen for no apparent reason. I have not rooted the device and it's bootloader is locked. I'm able to fastboot but selecting recovery mode returns me to the loop. I've tried using wugs nexus toolkit to flash stock but the it just returns me to the loop as the boot loader is locked. Is there any way to unlock the bootloader or return to factory settings/get out of the loop?
Click to expand...
Click to collapse
I think you probably have failing EMMC. Sometimes if you keep playing with it or let the battery drain, it eventually boots once or twice before going bad again. If this happens you should immediately go into developer options and enable OEM unlocking.
If for some reason you can reinstall factory images and that works great. If not you probably need to try the LGUP method with the TOT file. Search and you'll find it.
If that fails, you probably need to get a new phone.

Bootlooped 30min, then came back. Memory corrupted? How do I check?

Okay, today evening, my Nexus 5X rebootet already 5 times while I was using it just as every evening (browsing web, watching youtube, nothing special).
After the second reboot, it actually vibrated two times during the boot animation (after entering the decryption pin) like it usually only does when powering it up.
After the third reboot, it bootlooped for more than 30min (!!) ... Just the bootloader (white google logo), then ~3s black screen, then vibrating and Google Logo again!
Entering boot menu was possible... I used it to power off and reboot, but didn't help. I was just letting it bootloop while I searched my old Nexus 4 to reactivate it
After the 30min or more bootlooping (by the time I already found my Nexus 4 and reinstalled its battery ) the Nexus 5X asked for decryption pin.... I entered it, it rebootet. It asked again. If finally bootet.
After ~3min of use (just enough for a whatsapp backup) it rebootet again and bootlooped again for ~15min. And same again.
Now it is back once again - for the moment.
I need help, what can I do now, except backing up all relevant data?
It is stock android, not rooted, bootloader locked
Can I somehow test the memory? See why it rebooted?
It NEVER rebooted before since I own it...
Thx
The device rebooted after few minutes yesterday... It still overcomes the first bootloop from time to time after dozens of bootloops but then crashes most of the time after I was able to enter the pin. Since yesterday, it only managed to finish booting two times but always rebooted after few minutes.
Is this the famous BLOD? Haven't heard of it until today (sorry) ...
I actually had OEM unlock enabled in the developer menu, so I could actually unlock the bootloader...
Can I verify that it actually is the BLOD by unlocking the bootloader and temporary booting the modified boot image using fastboot? I don't want to flash something at the moment, because I might get it replaced... I can lock the bootloader again afterwards, right?
I think it might be possible to use "fastboot boot boot.img" (using the 4-core kernel image) from the bootloader screen. That won't install anything.
Thx. However, it requires me to unlock the bootloader and delete all data, since there is no 4-core kernel provided/signed by google, right? I will be able to lock the bootloader again afterwards, as long as I won't flash a different kernel (or reflash the stock kernel), right?
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
caifaz said:
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
Click to expand...
Click to collapse
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
RFZ said:
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
Click to expand...
Click to collapse
you're welcome, there is no need to flash a bootloader, just flash the TWRP recovery (modded for 4 cores), restart to recovery and then flash EX kernel (modded for 4 cores) according to you SO version.
I have fixed a phone 2 years ago using this instructions
Okay, I just verified it... The device boots fine with the 4 core kernel. I then reflashed the stock image, locked the bootloader, and it bootloops again. Will send it back to the store now and hope I'll get a refund/replacement :fingers-crossed:

Pixel XL stuck in Boot Loop after PPP5 installed

My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
pamack said:
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
Click to expand...
Click to collapse
You didn't relock the bootloader did you? After unlocking it?
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
pamack said:
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Click to expand...
Click to collapse
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
pamack said:
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
Click to expand...
Click to collapse
Still probably worth flashing via adb to check?
mikefnz said:
Still probably worth flashing via adb to check?
Click to expand...
Click to collapse
He means fastboot.

Missing Recovery on Android 10

I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.

Categories

Resources