Help: 'Flashing_locked' after successful Blankflash - Moto G8 Plus Questions & Answers

Moto G8 Plus doha XT2019-2 with bootloader unlocked but hardbricked; I now have "flashing_locked" even after a successful blankflash.
When trying to flash the firmware, I get "FAILED <remote failure>" after "flash" command on the computer.
"fastboot oem unlock XXXXXXXX" doesn't work (need to have enabled "allow OEM unlock" in developer options) and RSD Lite v5.6.4" or "Rescue and Smart Assistant" doesn't work either.
Is there any blankflash already with the "allow OEM unlock" option enabled?
Is there a way to activate developer options "allow OEM unlock" through fastboot?
Help me please...

Related

Huawei P10 cannot relock as OEM disabled and greyed out

Hi how can i toggle OEM when it has been disabled and greyed out? cannot use fastboot commands as OEM is disabled, and cannot flash? what can i do to re-lock bootloader, or enable OEM

OEM greyed out in developer options! HELP

Hi how can i toggle OEM when it has been disabled and greyed out? cannot use fastboot commands as OEM is disabled, and cannot flash? what can i do to re-lock bootloader, or enable OEM

Stuck after unlocking bootloader?

Hi everyone,
Today I decided to root my Mate 9.
I started out with turning 'OEM unlock' on and usb debugging. With ADB installed and the huawei drivers, I began to unlock my bootloader. On the 'EMUI Huawei' homepage I filled out my device details and obtained an unlock code. I opened ADB and checked with 'adb devices' if my device was there. It was. So I continued with typing 'adb reboot bootlader'. After that I typed 'fastboot devices'. My device was still showing up. I typed 'fastboot oem unlock CODE (with the code). On my screen I pressed 'Yes'. Bootloader unlocked.
After this step I tried to flash twrp with the command 'fastboot flash recovery xxxx.img'. I couldn't continue because every adb/fastboot command keeps failing (remote: command not allowed). Now when I boot up my phone it shows 'your device has been unlocked and can't be trusted'. Phone=unlocked, FRP=locked. I can't do anything.
Device: Mate 9 L29C432B198
What did I do wrong or what did I missed? :crying:
I had this issue at first to had to redownload the original rom via the phone recovery this will fix the frp lock then u have to unlock and flash twrp 3.1.01 that is linked in the threads on here
Did it format after it unlocked?
You can try fastboot oem relock UNLOCKCODE
Then go to Settings -> Dev options -> enable OEM Unlocking
Then unlock again.
It probably will fail though if FRP is locked, but worth a shot.
Edit: It's supposed to say
PHONE Unlocked FRP Unlock

Nokia 2 fastboot

I tried to flash custom recovery in Nokia 2 but I was not able to flash. When I tried to unlock bootloader with command in fastboot(CMD)
fastboot OEM unlock
With usb debugging and OEM unlock enabled in developer option.I got an error that OEM unlock is not allowed but I have enable OEM enabling in developer option.
Same problem
sushant1 said:
I tried to flash custom recovery in Nokia 2 but I was not able to flash. When I tried to unlock bootloader with command in fastboot(CMD)
fastboot OEM unlock
With usb debugging and OEM unlock enabled in developer option.I got an error that OEM unlock is not allowed but I have enable OEM enabling in developer option.
Click to expand...
Click to collapse
I also try with generate oem key... But can not unlock bootloader

LG Pheonix 5 (AT&T Unlocked) Fails to Load Bootloader

I would like to unlock the bootloader. I've enabled "Developer Mode" , "USB debugging", and "OEM unlocking". I also installed Minimal ADB and Fastboot on my Windows 10 PC. In the ADB and Fastboot terminal, it shows up as an adb device. "adb reboot bootloader" just causes the device to restart. I've only found 2 other guides, both of which are inconclusive. I've already unlocked the device with AT&T but that didn't solve my inability to unlock the bootloader. Any advice would be helpful.

Categories

Resources