Database Info

FRP Locked and Bootloader Locked, cannot boot into system

I tried to use this tool https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 to rebrand my mate 9 and I was able to unlock my bootloader before I started this tool and no problems there. Next I open the tool and went in and followed all the steps without problems all the way down past rebranding and to the step where I have to unlock my bootloader again. This time, FRP engaged and doesn't let me go past - I am stuck: i cannot reboot into the system to change any settings. At this point I tried a variety of methods, erecovery and funky huawei, they both end up saying getting package info failed. Now I am stuck. I cannot boot into the OS, it just kicks me straight into erecovery and erecovery isn't doing much recovery at all. Any help is greatly appreciated.

Billchen0014 said:
I tried to use this tool https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 to rebrand my mate 9 and I was able to unlock my bootloader before I started this tool and no problems there. Next I open the tool and went in and followed all the steps without problems all the way down past rebranding and to the step where I have to unlock my bootloader again. This time, FRP engaged and doesn't let me go past - I am stuck: i cannot reboot into the system to change any settings. At this point I tried a variety of methods, erecovery and funky huawei, they both end up saying getting package info failed. Now I am stuck. I cannot boot into the OS, it just kicks me straight into erecovery and erecovery isn't doing much recovery at all. Any help is greatly appreciated.
Click to expand...
Click to collapse
you need to relock bootloader, after it phone is resetting. then you need to unlock it, install TWRP , then you need to reflash a COMPLETE backup from MHA-AL00C00 or MHA-L29C626. Then restore to this. This is the only working solution. maybe i will create a backup from AL00

012345678 said:
you need to relock bootloader, after it phone is resetting. then you need to unlock it, install TWRP , then you need to reflash a COMPLETE backup from MHA-AL00C00 or MHA-L29C626. Then restore to this. This is the only working solution. maybe i will create a backup from AL00
Click to expand...
Click to collapse
the bootloader is locked, or so says the fastboot screen along with FRP which is why i cannot unlock the bootloader to install TWRP...

Need Warning
I think this thread (https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108) should add some warning.
I meet the same problem today.

wingkou said:
I think this thread (https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108) should add some warning.
I meet the same problem today.
Click to expand...
Click to collapse
That makes three of us. I ended up with the same problem after getting to step E in the rebranding. I'm no stuck not being able to unlock my bootloader as it says Phone locked in green and FRP lock in green. OEM unlocking option is greyed out in developer options

before i found a solution i hardbricked my mate 9, but it works for soft bricked mate 9 too https://forum.xda-developers.com/mate-9/help/solution-19-00-fix-hardbricked-huawei-t3750315 i was in the same situation, thats how i fixed it, just follow steps from how to use the DC-phoenix tool with Factory Firmware file, update.app and hw.app

Now I'm in the same situation
After rebranding my Honor View 10 BKL AL20 to BKL L04, it can't boot into system and frp locked oem locked. Erecovery says getting package info failed.

your device is corrupted and cannot be trusted.

Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command

OmanGhost said:
Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command
Click to expand...
Click to collapse
Sounds like the bootloader was modified, which breaks the digital signature.
Try unlocking the bootloader again and reboot. Go into developers options and turn usb debugging on. Then connect a cable between your computer and the phone. An RSA signature key should be presented. Check the box "always accept from this computer". Then try rebooting into fastboot and flashing stock.
Not sure of this will help but that's the best advice I can offer.
Cheers,
B.D.

"Can't find valid operating system" on bootup, bootloader is locked so I can't flash

"Can't find valid operating system" on bootup, bootloader is locked so I can't flash
I was locking my bootloader because I didn't want to have my phone rooted anymore. So, I factory reset it, set it up, and then went into the bootloader and typed "fastboot flashing lock". I selected yes to confirm the locking of my bootloader and then my phone rebooted. But now my phone says "Can't find valid operating system" and I can't boot into Android. I can't even flash a stock image, because I locked the bootloader. I can't unlock the bootloader, since I can't go into the OS and turn OEM Unlock on. Am I screwed?

Rafael112526 said:
I was locking my bootloader because I didn't want to have my phone rooted anymore. So, I factory reset it, set it up, and then went into the bootloader and typed "fastboot flashing lock". I selected yes to confirm the locking of my bootloader and then my phone rebooted. But now my phone says "Can't find valid operating system" and I can't boot into Android. I can't even flash a stock image, because I locked the bootloader. I can't unlock the bootloader, since I can't go into the OS and turn OEM Unlock on. Am I screwed?
Click to expand...
Click to collapse
Factory reset doesn't reverse changes made by rooting, you needed to reflash stock firmware before relocking.
Depending on the model it likely isn't good, every OEM does things a little different.
Sent from my Moto E (4) using Tapatalk

but I tried to install an update and not a flash that you are not allowed to install

Motorola Moto G8 "Your device is corrupt. It can't be trusted and will not boot."

I have a phone (Moto G8), I wanted to get rid of TWRP and I thought that just locking the bootloader will do it.
I only after saw that if you lock the bootloader with TWRP flashed you get into a boot-loop.
I found out that I can only use "fastboot boot" to boot into stuff because of the error stating: "Your device is corrupt. It can't be trusted and will not boot.".
Even if I go into the recovery mode the same error message would appear.
I know that by unlocking the bootloader I could get rid of that error but I don't have an unlocked bootloader and,
as most of you already know, after relocking the bootloader you need to enable OEM unlocking from developer options.
That was a huge problem since I couldn't access the phone at all besides the
bootloader, TWRP (although limited by the locked bootloader), and the default recovery.
That way I got into TWRP but I couldn't do much because of the locked bootloader.
Even if I had a full backup (which I didn't have) I couldn't do much.
I also tried downloading the full OTA image of an updated version of Android (I had Android 10 and I tried to go to Android 11)
to sideload but I couldn't find it. I found one but it was not a full OTA image (with bootloader, recovery, etc.) and I got an error message saying:
"Invalid zip verification signature" or something like that. Also, the error was happening at the start of the ADB sideload, I didn't know what else I could try.
So I have a question: Since I can use "fastboot boot" to bypass the error message,
is there maybe a bootable .img file that I can use to boot directly into the system and enable OEM unlocking?
Any help would be highly appreciated as well any other way to enable OEM unlocking through the bootloader or somehow ADB.

How to relock bootloader?

I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.

As long as you remain unlocked you will not get updates. Just download the 11 stock ROM and fastboot it. You will be updated.

boltjuice said:
I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.
Click to expand...
Click to collapse
You can get the firmware with LSMA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

I just downloaded it and ran the rescue but it just flashed the rom and is still unlocked.
Is there an option to re-lock bootloader with that tool?

What is your carrier and where did you get your phone? Not every bootloader can be unlocked.

Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?

boltjuice said:
Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?
Click to expand...
Click to collapse
Re locking is not advisable, can be tricky with Moto devices

Re-Locking see Post #4

I'm a little unclear what state your device is in atm.
I just downloaded it and ran the rescue but it just flashed the rom
Click to expand...
Click to collapse
but then you write
I just want to re-lock it and revert it back to stock.
Click to expand...
Click to collapse
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH

notmyrealhandle said:
I'm a little unclear what state your device is in atm.
but then you write
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH
Click to expand...
Click to collapse
I factory reset the phone. Everything gets reset except for the unlocked bootloader does not re-lock... which prevents me from OTA update to Android 11.

Ok. If I understand correctly, your post with "it just flashed the rom" means a factory reset (and no flashing an image via moto's rescue tool or fastboot) - my misunderstanding.
As I mentioned to you in my reply to your PM, I don't use stock other than to initially get the bootloader unlocked, test a few things, and occasionally verify that my device still works on stock.
Others posting in this thread have offered helpful and safe suggestions - consider following these. I do a fair amount of "risky" tweaking with custom roms so please be cautious about the following suggestions/observations. (Apologies if my comments below seem basic - it looks like you've tried some fairly sophisticated tweaking of your own but it's hard to judge others skill level in a forum.)
Based on your comment:
made my phone not boot with error "no valid operating system could be found."
Click to expand...
Click to collapse
I suspect your phone wont boot after re-locking due to prior modifications to it's OS, the evidence of which can survive a factory reset. Re-locking enables android to verify that certain parts of the OS have not been modified and if it detects a difference, the device won't boot.
If you insist on re-locking your device now, I think the only way to accomplish that is to re-flash your device with the correct factory (aka stock) image some of which are available on lolinet. This is much more than a "factory reset." The instructions linked by sd_shawdow above should help with this:
Re-Locking see Post #4
Click to expand...
Click to collapse
Choosing the correct factory image is important. For example, I have a XT2113-2 RETUS. At one point early on when I was playing with this device, I tried flashing the TMO variant which is also a XT2113-2 model. My device did not boot until I re-flashed a RETUS variant. It's possible I just made a mistake while trying to flash the TMO variant I can't be certain at this point. If your phone was originaly (meaning new out of the box) a MetroPCS variant, make sure you flash a MetroPCS image.
Android also has roll back protection to prevent reverting to an older image that might have security flaws. The roll back "index" can be written to persistent storage on your phone that not only will survive factory resets but likely also survives flashing factory images. Motorola's implementation of roll back protection does not seem consistent with what I've read online from android/google. I'm pretty sure I had the most recent Android 10 RETUS bootloader on my device but I was able to flash an older factory image and then relock the device while on stock. (As I mentioned in my PM, I have not tried re-locking stock android 11). This observation may be the result of a motorola bug specific to RETUS so don't count on this working for you. Flash an image that is the same as or newer than the newest factory image you've ever had on the device.
Moto's rescue tool apparently can select and download an image for you making the process of image selection easier. I have not used this tool so I don't know how smart it is. Trust your knowledge about what you've done with the device since you owned it.
Lastly, it looks like the OEM unlocking toggle issue I and others have observed upon upgrading to Android 11 is resolved by connecting the device to your carrier and waiting several days. If you don't mind the wait, it's probably safe to flash android 11 (by using an image form lolinet and fastboot or by using the moto rescue tool - not via ota) while the device is unlocked and then re-locking the device.
Sorry about the long post.
HTH.
EDIT: I prefer not to be PM'd. Please just communicate (with me) in the open.

I was on Lineage 19.1 on my 5g ace. When I heard about the version 11 software for Retail US, I went to the lolinet mirrors to download the firmware for my phone.
Make sure oem unlocking in the developer options menu is off. If you can't turn it off you will need to root your phone.
Make sure USB debugging is on and you allow access for the pc your using.
Start adb and verify it sees your phone. If so, type...
reboot bootloader
Verify fastboot is authorized
Use Motoflash Pro to flash the version 11 firmware to my phone. Motoflash can be downloaded from the one 5g ace telegram channel. When it is done close Motoflash Pro and then from your pc use adb to run:
fastboot oem lock
Your phone will ask you if you want to relock bootloader. Choose Yes
Now reboot to the stock recovery and then use power + Volume up to access the recovery menu.
Navigate down to factory reset and select. It will warn you ... Blah blah blah. Now choose reboot system.
Moto boot logo should appear and then setup should begin.
Hopefully this helps someone.