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.
Related
Hi guys,
My phone won't get past the google logo anymore. I can get into bootloader mode, but now it says my phone is locked.
I can't unlock it via the "fastboot oem unlock" command. When I do that, I get a Erase fail. I can get into CWM, but I cannot restore any nandroid or flash an update.zip.
I also can't flash any file with fastboot, when I do I get "write fail". So I think the filesystem is somehow corrupt.
I tried to get into download mode via the Unbrickable Ressurector, but then I get the screen on my phone to unlock the bootloader (which doesn't work).
Anybody got an idea?
Bricked Pixel 2 - locked bootloader & no access to developer options - please help
Hello guys, I just bought myself a Pixel 2 device today and decided to have a go at some changes: I've unlocked my bootloader of my Pixel 2 to perform TWRP flashing & Magisk installation and afterwards I decided to revert to stock.
The first step that I did when trying to revert to stock was to relock the bootloader via adb because I thought (big mistake) this will also revert everything to the factory image. Problem is right now the device isn't booting anymore (so I cannot change anything in developer settings and the bootloader is locked).
Fastboot does work now (I get an "FA8271A02780 fastboot" message when typing fastboot devices) but I cannot flash anything (it always says FAILED: remote Flashing unlock is not allowed.
I tried the Deuces script and UAF but they don't work (because my bootloader is locked). Given that I cannot unlock it, is there any way of flashing the stock image on my device? Any help is appreciated. Thanks a lot.
Sadly I don't believe so. Google doesn't allow us to flash anything without bootloader being unlocked. Other OEMs either have a program or allow you flash signed roms with a locked bootloader. For the trouble iTunes is at least you flash firmware through in the event of a Brick
I've tried online guides to unlock bootloader, but messed up in some point and now I'm stuck.
1st. Download indepth test and reboot to bootloader within the app.
2nd. Tried adb devices successfully
3rd. Fastboot oem unlock nor Fastboot flashing unlock run (output: fastboot oem unlock failed "remote unknown command")
4th. Decided to make a factory reset (just becase I had to make an stupid desition)
Now I can reboot into fastboot again, because in depth test app won't install anymore. Installer says "Installation failed -An app with the same signature has already been installed"
I've unsuccessfully tried to flash stock rom from recovery but thein depth test seems to be "installed" without front user interface, also fasboot reboot bootloader get stuck in waiting for any device.
Can someone have a solution I already tried anything that comes to my mind.
Thanks.
I was able to solve the problem installing extractly the same apk.
The "fastboot oem unlock" dont work for me
What work on me 5pro is "fastboot flashing unlock"
Then flash twrp and vbmeta
To relock bootloader "fastboot flashing lock"
Source https://forum.xda-developers.com/realme-5-pro/how-to/bootloader-unlock-tutorial-t3985003
Other, might helpful source:
https://forum.xda-developers.com/realme-5-pro/development/rom-pixel-experience-t4053357
"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
Recently rooted my new Zenfone 7. Is it possible to remove Bootloader unlocked Warning message at the start up of the system? Thanks for an answer.
re-lock the bootloader
Boot into fastboot, then send this command from your pc.
fastboot oem asus-lock
how did you get root to work? I followed the instructions listed and it would not work for me.
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Jkm15 said:
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Click to expand...
Click to collapse
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Jkm15 said:
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Click to expand...
Click to collapse
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Joeb2000 said:
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Click to expand...
Click to collapse
Had locked bootloader on device with magisk. Result is fastboot loop =|
Same wish here. that warning screen is ugly....