Database Develop

Nexus 6 bricked after November Security OTA update?

Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!

Tomer Morad said:
Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!
Click to expand...
Click to collapse
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.

simms22 said:
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.
Click to expand...
Click to collapse
I think he is saying that the phone will not boot up. So he can't get to the dev options.

I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.

Rektifying said:
I think he is saying that the phone will not boot up. So he can't get to the dev options.
Click to expand...
Click to collapse
Quetzalcoalt_Lp said:
I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.
Click to expand...
Click to collapse
i wasnt even going to say repair center, as there isnt much they can try. an rma(factory replacement) might be your only option.

Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.

Quetzalcoalt_Lp said:
Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.
Click to expand...
Click to collapse
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck

simms22 said:
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck
Click to expand...
Click to collapse
Indeed I haven't found any key or menu combination that would allow me to boot and change this option
I hope T-Mobile will replace it under the warranty.
Thanks for the replies!

I know it doesn't help now... But for anyone reading this...
Unless your never going to attempt to fix anything, and will always just RMA...
ALWAYS ALWAYS ALWAYS unlock and leave your bootloader unlocked. By the time you decide otherwise, it may likely be too late.

Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?

While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6

MysticKing32 said:
Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?
Click to expand...
Click to collapse
Hi, I tried what you suggested and it had no effect - I still can't enter recovery mode (image is unverified).

imnuts said:
While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6
Click to expand...
Click to collapse
I would have loved to be able to do that, but I can't run any image on the device. I can't leave the fastboot menu.

Try a factory reset in the stock recovery: https://support.google.com/nexus/answer/4596836?hl=en

Moto Z3 play bootloop with bootloader locked

Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance

sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs

sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!

sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?

sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...

sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.

kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.

sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?

kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...

$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.

Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....

Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución

To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.

i bricked my moto

i tried to lock the bootloader to bring back the guarantee, but i ended up deleting the Operating system and locking the bootloader,
now when i try to turn up the phone it says "your device has loaded a different operating system" and im trying to unbrick, but i tried with the adb tools, using qualcomm drivers, motorolla drivers, even the rsd lite, but it says "access denied" every time i try to flash the stock rom to unbrick it, and i can't unlock the bootloader again because it says that i need to enable it in settings> unlock OEM, but as i said, i can't access to the phone because there is no OS, pls help

r2d2arturo said:
i tried to lock the bootloader to bring back the guarantee, but i ended up deleting the Operating system and locking the bootloader,
now when i try to turn up the phone it says "your device has loaded a different operating system" and im trying to unbrick, but i tried with the adb tools, using qualcomm drivers, motorolla drivers, even the rsd lite, but it says "access denied" every time i try to flash the stock rom to unbrick it, and i can't unlock the bootloader again because it says that i need to enable it in settings> unlock OEM, but as i said, i can't access to the phone because there is no OS, pls help
Click to expand...
Click to collapse
Once the bootloader is unlocked, the warranty is void you can't undo it.
If RSD lite doesn't work there's unlikely a fix.
RSD Lite doesn't work with most windows 10 machines, try windows 7.
Or LMSA's Flash Rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

r2d2arturo said:
i tried to lock the bootloader to bring back the guarantee, but i ended up deleting the Operating system and locking the bootloader,
now when i try to turn up the phone it says "your device has loaded a different operating system" and im trying to unbrick, but i tried with the adb tools, using qualcomm drivers, motorolla drivers, even the rsd lite, but it says "access denied" every time i try to flash the stock rom to unbrick it, and i can't unlock the bootloader again because it says that i need to enable it in settings> unlock OEM, but as i said, i can't access to the phone because there is no OS, pls help
Click to expand...
Click to collapse
Why do you lock the bootloader without an operating system while OEM unlock is disabled??
Did you want to brick your phone?

Question Unlock bootloader after relocking it

Hey!
I got a Zenfone 8 from a friend, and he told me that he tried to flash Lineage OS once, for some reason he got some errors and ended up going back to the stock ROM and relocking the bootloader.
Now I'm trying to unlock the bootloader again through the ASUS app, but it doesn't work. He tried to help me with some commands through fastboot mode and it also didn't work. There is any way to unlock it again after relocking it once?
He said he used the command 'fastboot oem asus-csc_lk' to relock it, don't know if it is hepful.
edit: We tried 'fastboot oem unlock' 'fastboot flashing unlock' (failed with permission error) and 'fastboot oem asus-unlock' (which resulted in FAILED (remote: 'Verify unlock token fail.')
Also AsusUnlock apk installs succesfully through ADB but fails to unlock with error 24802. Trying to install it through the phone doesn't work and gives me an error.

give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?

AJ205 said:
give more information please, from what build did your friend flash the lineageos? to what build did he go back to? did you install latest working ADB? are the drivers for the fastboot installed correctly? are you connected to the internet when trying to run the app on the phone?
Click to expand...
Click to collapse
He said he followed what was on the guide he found, first updated to Android 12, the latest on on asus website (WW-31.1004.0404.107), and then tried to flash LineageOS ROM, then he got some errors and went back to Android 12 and relocked the bootloader. He said he never tried anything again. When I got the phone it was on Android 12, I tried unlocking it as I said and it didn't work. Then I downgraded it to 11 using the firmware from asus website (Version Android 12 to Android 11), and tried to unlock it again using Android 11. Also didn't work.
About ADB and Fastboot drivers, they are correctly installed, tried some "standalone" versions and also the one that come with android SDK Platform Tools. Tested it on other devices and it worked well. And the phone was connected to the internet when I tried using the app, I'm sure because I downloaded it on the phone aswell, using the browser.
edit: Actually I'm not sure about the fastboot drivers, I've just downloaded the sdk tools from google website.

what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.

AJ205 said:
what lineageos did he flasah? if its 18.1 thats android 11... propably why he got the errors.
Click to expand...
Click to collapse
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?

Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
are you sure you are locked? do you get the warning screen when you boot up?

AJ205 said:
are you sure you are locked? do you get the warning screen when you boot up?
Click to expand...
Click to collapse
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false

Aodh said:
I do get the warning screen, but also when checking with fastboot oem device-info it returns this:
C:\Users\delci\Desktop\platform-tools>fastboot oem device-info
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
let me get this straight, your device is unlocked and you want to lock it? because:
Aodh said:
That's probably it. But there's any way to unlock the bootloader again so I can give it another try?
Click to expand...
Click to collapse
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk

AJ205 said:
let me get this straight, your device is unlocked and you want to lock it? because:
what are you trying to do? your device is unlocked. you cant unlock it again.... you can try to lock with : fastboot oem asus-csc_lk
Click to expand...
Click to collapse
The warning appears, but it is not unlocked. Every command fails, device-info says that my device is not unlocked., it is locked.
What I'm trying to do is unlock it.
Let me try to explain what happened again.
The phone has been unlocked to install LineageOS. It didn't work. The past owner then installed the stock rom and locked it using this command: 'fastboot oem asus-csc_lk'.
Then I bought the phone from him, and now I'm trying to unlock it again, but it doesn't work.
The question then is: Is it possible to unlock a phone that has previously been unlocked and then relocked?

Hey, did you got it to work ?

How to flash or close the bootloader on open pixel 5a ? g.co/ABH

Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy

Try installing the usb driver https://developer.android.com/studio/run/win-usb

billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.

Thank you both is was indeed the USB driver that needed the google update... All is well! thanks