Database Develop

[Q] Last ditch call for help. Bricked Nexus 6 and only fastboot accessible

Hi everyone,
Was running cm12.1 happily then put a different kernel which caused a boot loop so I thought I'd reflash the cm12.1 zip but must have been an older zip which tried to downgrade the bootloader because after that it wouldn't turn on or even get into bootloader or recovery mode.
Managed to get fastboot up and running using this guide: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
However now I think I'm officially screwed because I didn't check "allow OEM unlock" in developer options so I cannot successfully flash any partition and "oem unlock" command does not work obviously.
The only hope I can see is if I somehow circumvent that and unlock the bootloader from fastboot using a specific motorola code?
Just want to know if there is any chance of a fix? Can you pay motorola to fix this stuff at all?
Thanks

dazman22 said:
Hi everyone,
Was running cm12.1 happily then put a different kernel which caused a boot loop so I thought I'd reflash the cm12.1 zip but must have been an older zip which tried to downgrade the bootloader because after that it wouldn't turn on or even get into bootloader or recovery mode.
Managed to get fastboot up and running using this guide: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
However now I think I'm officially screwed because I didn't check "allow OEM unlock" in developer options so I cannot successfully flash any partition and "oem unlock" command does not work obviously.
The only hope I can see is if I somehow circumvent that and unlock the bootloader from fastboot using a specific motorola code?
Just want to know if there is any chance of a fix? Can you pay motorola to fix this stuff at all?
Thanks
Click to expand...
Click to collapse
Contact Motorola and request an RMA.

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

New Xiaomi A2 global bricked???

I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.

foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.

Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/

I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone

Your fault that you locked bootloader on a modified system. Do a research next time

After Locking in Fastboot, i Can´t Unlock again "Enable OEM Unlock"

I recently formatted the Moto Z3 Play, Brazil Version XT1929-5 2 chip, via PC.
Using flash firmware, I unlocked the bootloader and installed a RETAIL BR firmware.
The device lost the baseband, but you can still check IMEI via Fastboot, it no longer works with CHIP or WIFI.
I tried to Relock the Bootloader to use the motorola recovery program, but the program it didn't work.
I tried to unlock the bootloader again but the system says "Connect to the internet or contact the carrier"(OEM Unlock is Grayed Out, I Cannot enable it again), and I can only use the device in Reverse Tethering via PC gnirehtet.
I tried to update the device but the device does not enter recovery, he says he updated the version but the system does not enter recovery mode to update system, only in bootloader / fastboot mode, and then I cannot enable OEM unlocking, is grayed out (OBS: OEM UNLOCK in certain devices enable after system update, im "updating" system" if grayed option enable gain.
What can I do?

killerBRs said:
I recently formatted the Moto Z3 Play, Brazil Version XT1929-5 2 chip, via PC.
Using flash firmware, I unlocked the bootloader and installed a RETAIL BR firmware.
The device lost the baseband, but you can still check IMEI via Fastboot, it no longer works with CHIP or WIFI.
I tried to Relock the Bootloader to use the motorola recovery program, but the program it didn't work.
I tried to unlock the bootloader again but the system says "Connect to the internet or contact the carrier"(OEM Unlock is Grayed Out, I Cannot enable it again), and I can only use the device in Reverse Tethering via PC gnirehtet.
I tried to update the device but the device does not enter recovery, he says he updated the version but the system does not enter recovery mode to update system, only in bootloader / fastboot mode, and then I cannot enable OEM unlocking, is grayed out (OBS: OEM UNLOCK in certain devices enable after system update, im "updating" system" if grayed option enable gain.
What can I do?
Click to expand...
Click to collapse
You didn't need to lock bootloader to use motorola rescue and smart assistant (LMSA)
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my payton_sprout using XDA Labs

sd_shadow said:
You didn't need to lock bootloader to use motorola rescue and smart assistant (LMSA)
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my payton_sprout using XDA Labs
Click to expand...
Click to collapse
The program has a key error when searching for the device's firmware.
BTW, I Solved Wifi/Carrier problem after updating using system update in Reverse Tethering via PC. The baseband updated.
Ironically I thought it would not work, after all the recovery mode does not enter, in the update it goes into fastboot mode, After 4 Security Updates, wifi and chip back to work.
OEM Unlock is enabled to unlock again.

sd_shadow said:
You didn't need to lock bootloader to use motorola rescue and smart assistant (LMSA)
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my payton_sprout using XDA Labs
Click to expand...
Click to collapse
By the way, do you know of any way to make android accept to update system again? since after trying to update after the July 2020 security update, the system says "It was compromised" after Flash Stock ROM.

killerBRs said:
By the way, do you know of any way to make android accept to update system again? since after trying to update after the July 2020 security update, the system says "It was compromised" after Flash Stock ROM.
Click to expand...
Click to collapse
Use Lmsa flash update
Moto ota update has lots of problems.
Sent from my ocean using XDA Labs

How To Guide PSA: Fix for "Device Corrupted" when trying to relock bootloader.

plempereur said:
A few notes on my experience with this tablet : I got it with the global rom and I wished to flash the stock rom and re-lock the tablet after to restore it in the original factory state :
- Flashed the CN rom using this guide, it went fine. I used "adb oem edl" to enter EDL mode as the mehod with the buttons did not work for me
- Re locked using "fastboot flashing lock" from the bootloader menu (vol+up), not the fastboot menu. (this driver was needed to "see" the tablet with fastboot)
- The tablet was bricked (refused to boot after re-locking / some error messsage like "system corrupted / unable to boot" then after this it just kept going to the bootloader when turning on)
- Unlocked the bootloader using "fastboot oem unlock-go"
- Managed to flash again from EDL, to enter EDL again (took me a bit of time to figure this) I had to use "fastboot oem reboot-edl" from the bootloader
- Starting over I did all the OTA updates up to ZUI14 "14.0.255 ST" (I received the updates even if the tablet bootloader is unlocked), then did a "Factory data reset" from the settings menu.
- After this I attempted to lock again and... it worked. Not 100% sure if it's due to the Z14 OTA, the factory reset or both (I suspect the OTA).
(I am keeping the "OEM unlocking" (allows the unlocking of the bootloader) option enabled in the developper options just in case I need to re-flash for some reason in the future)
Hope this can help others,
Cheers
Click to expand...
Click to collapse
Reposting this guide from @plempereur as it deserves prominent attention.

OMGrant said:
Reposting this guide from @plempereur as it deserves prominent attention.
Click to expand...
Click to collapse
I used this guide mentioned in that post, but this post helped me solve some issues I had. We need a sticky with links to all the posts in that one long thread because there's so much information in there and its buried.