My phone goes crazy and start to do random reboots, so I want to reset to the factory default, but then shows a "no command" screen with a dead andy, so I try to flash the factory image from google.
The problem starts when the rebooting of fastboot after opening the bootloader, because the bootloader becomes closed again, so I can't flash anithing.
My device is a Galaxy Nexus GSM yakju with stock Android 4.3
Any help would be grateful.
I have a 32gig flo, I was running 4.4.4 with TWRP and ElementalX kernel. I tried to flash 5.02 with NRT and it all went wrong. First, while flashing it got stuck at the bootloader screen - pics / screenshots here. Then I realized the bootloader was locked, so I tried to unlock the bootloader with NRT and it got stuck in a boot loop. I pulled battery and tried the “Flash Stock + Unroot” feature to go back to stock 4.4 and the command prompt came up and said it was successful, but it's stuck in another bootloop, and now I can't even get back to the bootloader menu. I didn't use force flash mode and it said to try that but i can't get to that point. am I screwed? :crying:
edit: got into bootloader menu, used force flash mode and it's stuck in a boot loop again.
I just realized there were some text documents in Simple Notepad that i would have liked to keep. Is there any way I can recover them?
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.
Hi.
My Nexus 5X was rooted, unlocked and with the last security update (N2G47Z)
I was using it this after-noon and it freeze and then reboot twice in 15/20 minutes. But now, it's bootloop with the warning about unlock bootloader.
I'm able to put my phone on fastboot mode so I relock bootloader but it's still bootloop
I have try reflash latest 7.1.2 image but still bootloop
Is there something I can do ??
Thanks for your help
mikebzh44 said:
Hi.
My Nexus 5X was rooted, unlocked and with the last security update (N2G47Z)
I was using it this after-noon and it freeze and then reboot twice in 15/20 minutes. But now, it's bootloop with the warning about unlock bootloader.
I'm able to put my phone on fastboot mode so I relock bootloader but it's still bootloop
I have try reflash latest 7.1.2 image but still bootloop
Is there something I can do ??
Thanks for your help
Click to expand...
Click to collapse
try re-open bootloader and flash last image(or try with old verrsion like MM)
I try but flashing the first 7.1.2 image but the phone still bootlooping so I let it bootloop all night long and this morning, I'm able to configure it (because of the factory reset).
I hope I have fix the problem.
Bad luck. After setting Android (email, Wi-Fi, ...), the phone start to download apps and then reboot and bootloop
I have flash Marshmallow 6.0.1 but still bootloop.
And I can't enter download mode to try flashing TOT file.
Don't know what to do, apart buying a new phone.
I recently installed Evolution X 4.1.69 after unlocking my bootloader in my Pixel XL. After installing the custom ROM, I found that the OEM locking has been greyed out in the developer option.
Since the built of the custom ROM wasn't stable at that time, I decided to revert back to stock ROM. Unfortunately, I relocked my bootloader before recovering the factory image of the stock ROM.
After that, my phone screen starts flashing with the Google sign and keeps rebooting. I am able to access fast boot but I cannot access recovery mode from there. Pressing the recovery option from there will still lead me to a continuous boot loop, similar to what happen whenever I boot the phone.
I have tried these attempts with no avail.
1. fastboot oem unlock, failed since my bootloader is locked.
2. fastboot oem reboot-download, it causes continuous bootloop.
3. adb sideload bootloader.img, since I cannot access recovery mode, sideloading the factory image doesn't work as well.
4. flash factory image, failed as it still requires me to have an unlocked bootloader in order to do so.
Any suggestions on what I should do besides replacing the motherboard or RMA is greatly appreciated! Thanks!
you relocked your bootloader.
user error.
You sound pretty sure that you locked your bootloader. Did you actually go through steps to do so? Or was it just the grayed out option in developer settings? Have you tried to boot to TWRP or Lineage Recovery from fastboot?