Locked Bootloader and I can't boot into Android - Moto Z Play Questions & Answers

Hi,
I think I bricked my Moto z play.
I Have undlocked the bootloader and flashed lineageos. Everything worked fine, but then I wanted to close the bootloader again because of the message at the bootup. Not I get the massage "Your device has failed verification and may not work properly". The Bootloader is now closed (flashing_locked).
Does anyone have a clue how to solve this problem? I can boot into fastboot, recovery and load TWRP via adb.
Thanks for your answers

Related

Locked bootloader - help needed

Hi all and thanks in advance, I appreciate your help a lot!
I've got a V500 with Android 5 and tried to install TWRP on it.
The phone was rooted already, but the TWRP apk app did not work, telling "flashing failed".
I then used the dd method getting root in adb shell, and flashed TWRP 3.1.
Unfortunately TWRP recovery does not boot with the following message:
Secure booting Error!
Cause : boot certification verify
I guess, this is due to the locked bootloader. I could not unlock, as adb reboot bootloader
boots through to the regular UI.
Now additionally to this problem I got a soft UI boot loop. After showing the swirling LG animation,
it boots to UI, shows the desktop, and loops to the LG animation again.
I still can reliably use adb, and be root on the device.
Could you, please, help me flash TWRP right in this situation?
You could try installing v500-20F bootloader and twrp 3.1 with root adb. Check this links:
https://forum.xda-developers.com/showpost.php?p=62050593&postcount=2
qutorial said:
Hi all and thanks in advance, I appreciate your help a lot!
I've got a V500 with Android 5 and tried to install TWRP on it.
The phone was rooted already, but the TWRP apk app did not work, telling "flashing failed".
I then used the dd method getting root in adb shell, and flashed TWRP 3.1.
Unfortunately TWRP recovery does not boot with the following message:
Secure booting Error!
Cause : boot certification verify
I guess, this is due to the locked bootloader. I could not unlock, as adb reboot bootloader
boots through to the regular UI.
Now additionally to this problem I got a soft UI boot loop. After showing the swirling LG animation,
it boots to UI, shows the desktop, and loops to the LG animation again.
I still can reliably use adb, and be root on the device.
Could you, please, help me flash TWRP right in this situation?
Click to expand...
Click to collapse

[8.0.0] Bootloop with locked bootloader. What can i do ?

Hi !
Before tonight, i was on a lineageOS 7.1 and i tried to flash the stock Oreo android that i downloaded on google websites. My bootloader was unlocked, so i just used fastboot and flashed all. I had TWRP installed.
It worked. Then i had the stock 8.0.0 with no TWRP anymore ( and i forgot to re-flash it ). Then, i dunno what passed in my head, after the first reboot, i decided to **lock my bootloader**.
And now i'm in a bootloop on the vendor image ("Google"), with a LOCKED bootloader ( so no fastboot anymore ) and i cant do anything. I forgot to go to paramters and allow the bootloader to be unlocked before rebooting...
The only access i got is via adb in the stock recovery mode, but i'm not enough aware of wath i could do with that. I tried abd sideload with the same .zip, but it didnt worked. I get stuck on the same Error when the phone tries to verify the conformity of the flash.
So :
1° Cant use fastboot to take me out of here because bootloader's locked.
2° No TWRP anymore, only the stock android recovery.
3° Bootloop so i cant launch the device.
4° My only in is adb fastboot.
5° My build number is OPR6.170623.013
What do you think i could / should do to take me out of here ? I'm taking anything that allows me to boot the phone.... For what i saw, i'm kinda thinking it's bricked, but i still got hope. I'm comming to you because i'm desperate
Thanks for your advices.
useful threads
that nobody ever bother checking out
Very usefull post. Thank you very much. I'm still stuck but i've posted there so i'll hope someone will come.
This post can be closed

Your device is corrupted and cannot be trusted and will not boot.

Hello. I've updated successful to Nougat Android 7.0 v29a
https://forum.xda-developers.com/g4/general/guide-upgrade-h815-locked-bootloader-to-t3684945.
Now I want to go back to MM. i'm trying to boot in download mode but I have a error in red "your device is corrupted and cannot be trusted and will not boot."
Which is the right way to get to MM?
I have the same message, I was on a custom rom (V30 porting) with TWRP and root, I tried to relock bootloader from fastboot and now I have that message, how can I fix it?

Vendor partition issues - z2 plus

Hello
I was trying to flash AEX 6.3 on z2 plus and i get the error " E20001: failed to update vendor image" and
updater process ended with error 7.
How can i resolve this problem?
Also i get the message " your device software can't be checked for corruption", please lock the boot loader.
This message comes after an update and prior to that it was working fine.
Phone is struck at ZUK logo and does not boot.
Any suggestion to solve this issue?
Thanks and much appreciated.
flash V2F .. reboot to recovery.. use compatible twrp.. or upgrade bootloader to 4.0 .. qpst to zui 4.0
sanjay.2704 said:
flash V2F .. reboot to recovery.. use compatible twrp.. or upgrade bootloader to 4.0 .. qpst to zui 4.0
Click to expand...
Click to collapse
did v2f. installed latest official twrp. same situation and no change.
did not do the second part.
the following message still appears.
" your device software can't be checked for corruption", please lock the boot loader.
It was a working device and this happened after an OTA update.
Don't understand why this happens? can you give more specific instructions and point me to any links that can help.
thanks.
" your device software can't be checked for corruption", please lock the boot loader. This is because you unlocked your bootloader and installed the custom recovery.
ramadurair said:
did v2f. installed latest official twrp. same situation and no change.
did not do the second part.
the following message still appears.
" your device software can't be checked for corruption", please lock the boot loader.
It was a working device and this happened after an OTA update.
Don't understand why this happens? can you give more specific instructions and point me to any links that can help.
thanks.
Click to expand...
Click to collapse

"Your device is corrupted and cannot be trusted" error. Nothing happens when connecting to PC

Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
This is for Google Pixel 2 XL.
SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.
Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.

Categories

Resources