Motorola Moto G7 Power unlock bootloader problem - Motorola Droid Bionic

Hi, I have problem with unlock bootloader in my moto G7 power because my firmware is broke I have Unlock Code from Motorola site when use command fastboot OEM unlock #code receives a message (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer but I can't enable developer options because my firmware not work, I can only enter fastboot mode. I tried to run developer option from ADB but I have empty list devices even though I have installed drivers Android ADB Interface. I tried to install stock firmware but I need to unlock bootloader first. Does someone have an idea for this problem??

Related

Relocking bootloader for sale

Hello hopefully someone can lend me a hand. I am trying to relock my bootloader on my moto x pure edition 2014. I have downloaded the correct recovery package from Motorola directly. I issue the commands that are needed fastboot oem lock begin and then flash the firmware and then fastboot oem lock. After fastboot oem lock I get SSL error you must enter fastboot oem lock begin before lock is what is shows on the terminal windows for fastboot. On the the device screen if shows cannot validate system image although it is the correct system image. I have tried using the fastboot directly out of the Motorola software I downloaded as suggested by another user and still get the same error. I have worked on this for hours with no avail. Does anyone have any experience in this with the same problem? Thanks
Did you try following the steps listed on Motorola's website?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I believe the "fastboot oem lock begin" was only needed for older devices.

oneplus 3t android 7.1.1 OS 4.5.1 unlock bootloader

Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
adb is working in your system but fastboot is not working.
Check your drivers properly, they are not installed properly.
search for how to install adb and fastboot drivers on windows. There is no problem in windows xp but in windows 10 as in my case, you need to activate the developer option in setting and manually install the drivers. Go to device manager and check if your device is showing as android device when you go to fastboot mode.
ismailf007 said:
Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
Click to expand...
Click to collapse
Did you type fastboot devices?
It should show you that your phone is connected.
Then you can run the unlock command.
Sent from my OnePlus3T using XDA Labs
ismailf007 said:
Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
Click to expand...
Click to collapse
the correct command is "fastboot oem unlock"
Hi Guys it was the fastboot drivers. After installing it correctly it worked 100%. Assistance is highly appreciated

Failed TWRP install on P10

Hi all,
I got problem installing TWRP recovery on P10 buil number VTR-L29C432B171.
First of all i unlocked bootloader with Minimal ADB an Fastboot. Now bootloader shows "Phone Unlocked" and "FRP lock".
When i try fastboot flash recovery... it shows FAILED (remote: command not allowed).
Any suggestions?
you have to activate OEM unlock in settings/developers options
virusdunil said:
you have to activate OEM unlock in settings/developers options
Click to expand...
Click to collapse
This setting is inactive (grayed out) after unlocking.
Finally problem solved.
There was somethig wrong with adb interface driver. After unlocking bootloader i have to reset developer settings to defaults to get usb debbuging work again. After this OEM unlock setting resets to, but because it stays inactive its imposible to turn it on. So i relocked bootloader and used Huawei Multitool drivers to unlock again and install TWRP.

Fake global rom from aliexpress

Hi,
I have bought redmi k20 pro from aliexpress in august, it came with 10.3.5.0 global rom and stuck on it. How can I update it manually or flash other rom without bricking it. It has unlocked bootloader. I have no experience in it so I need detail explanation.
need to check if the bootloader unlock is true or false
to do that you need to install minimal adb on your pc
activate usb debugging
connect phone in fastboot mode
open cmd on minimal adb folder
type fastboot oem device-info & check the result on unlocked section
In developer settings mi unluck status is unlocked but when I enter fastboot mode it always say 'waiting for device'
In developer options (use search) find oem unlock and see if it's on, as seen in the screenshot attached.
If developer options is not visible, enable by going:
Settings -> My Device -> All Specs -> Tap miui version until it unlocks developer mode.
could mean you haven't install the driver...
download PDAnet and install it

OEM_Locked and Can't Boot

Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Reznor7 said:
Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Click to expand...
Click to collapse
You can try LMSA's Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Or if you have a pc with windows 7 try
RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before.
Reznor7 said:
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
https://ibb.co/znCSvMR
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before. [emoji3525]
Click to expand...
Click to collapse
Blankflash only works if device is in EDL mode.
Sent from my Moto E (4) using Tapatalk
Edit: I think my issue is that I'm needing the latest firmware (including the May 2020 security update), and I can't find it anywhere. Trying to downgrade (even with an unlocked bootloader) is giving me the preflash validation error when trying to flash bootloader.img. Looks like I need ppws29.183-29-1-19
Final edit: I had to find the latest firmware for my device. Unfortunately, only a paid site had it, but after buying and installing everything is good again!

Categories

Resources