I can't unlock bootloader Moto E7 Power - Moto E7 Questions & Answers

When I type fastboot oem get_unlock_data in fastboot I gets FAILED (remote: 'unknown command') fastboot: error: Command failed.

Bartus0 said:
When I type fastboot oem get_unlock_data in fastboot I gets FAILED (remote: 'unknown command') fastboot: error: Command failed.
Click to expand...
Click to collapse
Some things to try
Different PC
Different USB port on pc
Different USB cable
Different version of SDK Platform-Tools
ReFlash firmware with LSMA's Rescue or manually with fastboot.exe

this is a mediatek phone, apparently bootloader unlocking is different process or not officially supported
still looking into how to get mtkclient working with my mtk motos to unlock them

luridphantom said:
this is a mediatek phone, apparently bootloader unlocking is different process or not officially supported
still looking into how to get mtkclient working with my mtk motos to unlock them
Click to expand...
Click to collapse
I have Moto e7 Power and is impossible to unlock bootloader.Can I root this device whitout unlock the bootloader?

Kiki46 said:
I have Moto e7 Power and is impossible to unlock bootloader.Can I root this device whitout unlock the bootloader?
Click to expand...
Click to collapse
not unless you can use mtk-su

Help me how to unlock bootloader Moto e7 Power

sd_shadow said:
Some things to try
Different PC
Different USB port on pc
Different USB cable
Different version of SDK Platform-Tools
ReFlash firmware with LSMA's Rescue or manually with fastboot.exe
Click to expand...
Click to collapse

Related

Bootloader unlock error????

Hey guys, I Need some help, I'm trying to unlock bootloader, but my device doesn't recognize fastboot commands like "fastboot oem get_unlock_data" Or "fastboot oem flashing_unlock", why?
Ps: Motorola drivers ok, usb cable ok, oem unlock and usb debugging ok
Error: FAILED (remote: 'unknown command' )
raffinnga said:
Hey guys, I Need some help, I'm trying to unlock bootloader, but my device doesn't recognize fastboot commands like "fastboot oem get_unlock_data" Or "fastboot oem flashing_unlock", why?
Ps: Motorola drivers ok, usb cable ok, oem unlock and usb debugging ok
Error: FAILED (remote: 'unknown command' )
Click to expand...
Click to collapse
There is a way, but you have to wait for Motorola to make this year's USB drivers available: this is how you enter the adb folder and rename the incone mfastboot to fastboot done this in the control panel Or on powershel you put it
.\fastboot oem get_unlock_data.
This appears on my <waiting for device> even though I installed the drivers But last year, so I think we should expect Motorola to make this year's USB drivers available
I'm having trouble even getting it to prompt for usb debugging authorisation. I'v got adb &fastboot, I've enabled dev options and usb debugging but when I connect it via data cable it doesn't prompt for authorisation.
I am thinking maybe a driver issue but I can't seem to find the drivers anywhere.
Any ideas/help? would be much appreciated.
According to this
https://old.reddit.com/r/androidroot/comments/f6c5k5/unlock_bootloader_moto_e6_plus/fupyalw/
this commnad
fastboot flashing unlock_critical
will unlock. Is this true?
RubenGreg said:
this commnad
fastboot flashing unlock_critical
will unlock. Is this true?
Click to expand...
Click to collapse
short anwer: no
long answer: maybe?
for that i read you might want to proceed with a factory-reset and block any update. in this way, that command will work. honestly i gave a try to it, but nothing changed. the smartphone is pretty good, why the hell did Motorola want to prevent such actions? i don't understand that yet.

Unable to unlock bootloader on Android 10

I have been trying to unlock bootloader on my Realme 3 Pro, but as soon as I enter the command in fastboot mode, it shows the following error:
PS D:\realme\platform-tools_r29.0.6-windows\platform-tools> ./fastboot flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
But the device is being detected by my laptop..
PS D:\realme\platform-tools_r29.0.6-windows\platform-tools> ./fastboot devices
51a8ba49 fastboot
The customer service team is also unable to sort it out.
Your help will be truly appreciated!
doperthancoke said:
fastboot isnt compatible with USB 3.0 ports. You have to plug the cable into USB 2.0 ports.
Click to expand...
Click to collapse
Yes I did that on 2.0

root alcaltel 1b

hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Hello and good morning, @roberto167
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Is that your phone? https://forum.xda-developers.com/c/alcatel-1.8103/
joke19 said:
È il tuo telefono? https://forum.xda-developers.com/c/alcatel-1.8103/
Click to expand...
Click to collapse
mine is model 1b with 2gb ram and android 11
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
aIecxs said:
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
Click to expand...
Click to collapse
as said already done and gives me the said error, enter fastboot mode
fastboot oem unlock
FAILED (remote: 'unknown command')
did you actually notice the difference between what I wrote and what you did?
aIecxs said:
did you actually notice the difference between what I wrote and what you did?
Click to expand...
Click to collapse
also given that command and also
fastboot flashing unlock
so what was the error message then
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
aIecxs said:
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
Click to expand...
Click to collapse
it seems very complicated as a procedure, being never done
usual error message looks like this
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
Click to expand...
Click to collapse
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
aIecxs said:
usual error message looks like this
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
Click to expand...
Click to collapse
even if it appears with the command fastboot devices, with these commands it remains waiting for any devices
Alcatel 1B Stock ROM / SIM unlock / etc....
ALCATEL 1B MEGATHREAD ( veken/seoul/TCL L7)...
forum.xda-developers.com
"UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock...."

Question How to lock the bootloader

I bought the Asus ZenFone 8 Flip with the bootloader unlocked, it is not running a custom ROM. How do I lock the bootloader? Thank you
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
maicol07 said:
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
Click to expand...
Click to collapse
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Kiribro02 said:
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Click to expand...
Click to collapse
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
maicol07 said:
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
Click to expand...
Click to collapse
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Kiribro02 said:
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Click to expand...
Click to collapse
No, just follow these steps:
Make a backup of your phone!! Unlocking/Locking the bootloader erases all your data partition (so all your stuff will be gone!)
Install ADB on your PC if you don't have it (check how to install it: https://www.xda-developers.com/install-adb-windows-macos-linux/).
Plug in your device via USB with Debug USB setting enabled (in Developer Settings)
Open a terminal prompt on your PC
In the terminal run adb devices. If you see your device I the list then you're fine. Otherwise, you have mistaken something in the previous steps.
Run adb reboot fastboot (or adb reboot bootloader if it doesn't work) to reboot into fastboot mode
Run fastboot oem lock to lock the bootloader
Run fastboot reboot to reboot the system
Your device is now locked!
DISCLAIMER:
I'm not responsible of any data loss, damages and/or bricks you make to your device(s) by following this guide!
Click to expand...
Click to collapse
To update the system when a new version is out, since you won't receive OTAs:
Go to Zenfone 8 Flip support page: https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8-Flip/HelpDesk_Download/
Choose Android as OS and scroll down to "Firmware"
Download the latest zip
Put it in the internal storage (in the root directory, not inside another folder!)
Two paths:
If you put the zip from PC via USB simply unplug the USB cable
If you downloaded the zip and put it manually via file manager from the phone reboot the system
A notification should pop out, notifying you there is a firmware package to install!
Just follow the notification message and you'll be done!
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Kiribro02 said:
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Click to expand...
Click to collapse
Oh that's an issue I have all the times with Asus devices. There's a simple one-time fix though: just install the official Asus ADB drivers.
Download them from this page (I know it's the smaller Zenfone 8 page, but they work with every Asus device): https://www.asus.com/it/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Download/
Choose your windows version (for 10 and 11 choose 8.1)
Download the USB driver
Extract the archive somewhere in your PC
Open Device manager in your PC (search it in start menu) while the phone is connected via USB and in fastboot mode
You'll notice an unknown device with a yellow/orange warning icon at the top of the devices list. Right click on it and choose Update drivers.
Choose "Search driver in the PC" (the second option (don't choose the first one since it searches the driver automatically on Windows update))
Choose the folder you extracted
Click "Next"
Drivers should be installed and fastboot should recognize your device (to test run the command: fastboot devices)
Sorry for the late reply, but I didn't get any notification from XDA
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Kiribro02 said:
When I try to update the drivers it says that windows was unable to install your and then it says the device.
Click to expand...
Click to collapse
Do you installed the drivers when the phone is in fastboot mode?
Also, I've noticed some steps are not clear (and one is doubled), I'll clean it
Kiribro02 said:
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Click to expand...
Click to collapse
Try all the two, I don't remember which one works (I think the Composite worked for me), but try also with the other ones
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
b4rbaar said:
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
Click to expand...
Click to collapse
Hi, yes you should create a new thread since it's a different topic
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
wyktron said:
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
Click to expand...
Click to collapse
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
maicol07 said:
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
Click to expand...
Click to collapse
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
wyktron said:
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
Click to expand...
Click to collapse
Try this one:
Code:
fastboot oem asus-csc_lk
maicol07 said:
Try this one:
Code:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
wyktron said:
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
Click to expand...
Click to collapse
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
maicol07 said:
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
Click to expand...
Click to collapse
@maicol07 there's no OEM unlock in my developer options, only the USB debugging (which is already on)
besides this oem method, is there another way to lock it? perhaps through the zenfone flash tool (I have it installed and it detects my phone, but never used it)

Cat s31 oem (bootloader) unlock

first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery

Categories

Resources