Unable to unlock bootloader on Android 10 - Realme 3 Pro Questions & Answers

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

Related

I can't unlock bootloader Moto E7 Power

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

I Need Help Unlocking My Bootloader On A Alcatel U5 4047X, I Keep Getting The Message FAILED (remote: 'unknown command') fastboot: error: Command fail

Hi, I Have A Alcatel U5 4047X And I Bought It In 2018. And I Am Having Problems Unlocking The Bootloader. I Turned On USB Debugging And OEM Unlock, Then I Went Into Fastboot Mode, And Plugged It Into My PC. i tried (Fastboot oem get_unlock_data) (fastboot oem unlock) (fastboot flashing unlock) but nothing works, i tried Different USB Ports, Different Cables, But I Still Get The Message FAILED (remote: 'unknown command') fastboot: error: Command failed, Can Someone Help Me?
How to Unlock Bootloader On TCT Alcatel 4047X U5 3G - TweakDroid
tweakdroid.com
joke19 said:
How to Unlock Bootloader On TCT Alcatel 4047X U5 3G - TweakDroid
tweakdroid.com
Click to expand...
Click to collapse
this doesnt help, tried everything, still get the same error. thanks for trying to help though.

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)

Fastboot not working

Hi, i have a Moto G9 Power and recently i decided to unlock the device bootloader.
There's a problem, ADB works well, but when i restart the device to bootloader, the phone disconnect from my computer and the bootloader say "Connect USB Data Cable".
If i enter the recovery and open the fastboot menu, my computer detect the phone and try to get the unlock info, but i recive this error:
fastboot oem get_unlock_data
< waiting for any device >
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
I don't know what to do as the ADB and the recovery fastboot works, but the fastboot that i need don't work
Note: i tried with another USB C cable (that i know it does not support data transfer) and at the bootloader the message changed to "Transfer Mode: USB Connected" it doesn"t make sense
Please can anyone help me?
Is there an option on this phone to unlock the bootloader in developer mode?
Adrrrrien said:
Hi, i have a Moto G9 Power and recently i decided to unlock the device bootloader.
There's a problem, ADB works well, but when i restart the device to bootloader, the phone disconnect from my computer and the bootloader say "Connect USB Data Cable".
If i enter the recovery and open the fastboot menu, my computer detect the phone and try to get the unlock info, but i recive this error:
fastboot oem get_unlock_data
< waiting for any device >
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
I don't know what to do as the ADB and the recovery fastboot works, but the fastboot that i need don't work
Note: i tried with another USB C cable (that i know it does not support data transfer) and at the bootloader the message changed to "Transfer Mode: USB Connected" it doesn"t make sense
Please can anyone help me?
Click to expand...
Click to collapse
Try a different PC
Try on another USB 2.0 port, it should not be blue.
Solution: try with another PC.

Nokia C100

So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient

Categories

Resources