fastboot oem get_unlock_code FAILED - OnePlus 8 Questions & Answers

fastboot oem get_unlock_code
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
Why is this happening?
I am using ubuntu 22.04 and have installed platform -tools _r33.0.2-linux.zip
Also attempted in Windows 10 with all the drivers with the same failure.
It is the t-mobile version and my sim card is unlocked.
Developer options, usb debugging on , oem unlocking toggled on.
the only thing that doesn't work in bootloader is oem commands.
I bought the phone from ONePlus.
It is a model IN2015

use MSM tool to revert then try again

Related

fastboot unknown command

Hey, I have an alcatel 3 and I wanna see how I can root it. I'm trying to root it using magisk but fastboot keeps returning the error unknown command all the time.
when I do
fastboot flash ...
it sends the file but then writing produces an error.
I know that I can root it and that I've done it before using magisk. but now it doesn't work. btw i don't think i fully unrooted my device so that may be the issue.
Fastboot deals with phone's bootloader where it doesn't matter whether phone's Android got rooted or not.
If you get shown
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
or
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
means the bootloader wasn't unlocked properly.
Try this command sequence
Code:
fastboot devices
fastboot flashing unlock
fastboot flashing unlock_critical
What if
fastboot flashing unlock.
Returns command not found
If "command not found" is returned by Fastboot when trying to unlock bootloader then unlocking phone's bootloader is denied.
what if i have to run sudo to use fastboot could that be the problem
Fastboot deals with Android device's bootloader: So it's irrelevant whether Android is rooted or not.
Take note that Fastboot isn't Fastboot hence not all Fastboot commands do necessarily work as expected: it depends on how OEM implements Fastboot.
having the same problem with my qlink tablet but when using command fastboot flashing unlock
it returned fastboot oem operation fail: unknown cmd' : error: command failed This is my first time rooting anything help please?
hellp me ty pls!
Have you turned on "allow OEM to be unlocked" in developers option

Trouble with G110A (NOT Verizon) bootloader

Trying to root my phone to flash Alexndr ROM. Phone is Google purchased (NOT verizon) pixel 2 G011A . USB Debug and OEM unlocking are toggled "on."
From the bootloader screen, and connected to the computer, this is the result from the following commands:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed') fastboot: error: Command failed
Click to expand...
Click to collapse
fastboot flashing unlock_critical
FAILED (remote: 'unknown command') fastboot: error: Command failed
Click to expand...
Click to collapse
It is communicating with the device:
fastboot devices
{{device serial number}} fastboot
Click to expand...
Click to collapse
and unlocking the bootloader seems to be enabled on the phone
fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total Time: 0.000s
Click to expand...
Click to collapse
I've tried all the USB ports on several computers with both Win10 and linux, with the same result.
On the phone itself, developer options are enabled, USB debugging is enabled, and OEM unlocking is enabled. Curiously, OEM unlocking becomes grayed out and disabled after enough failed attempts, but I've been fixing this with a factory reset.
The Android version is 11, build RP1A.201005.004A1
What am I missing here? Why wont this bootloader unlock? Thanks!
I have the same problem. Can someone please explain how to fix this?

Question Boot-Image?

I need the boot.img for the EU-Version. Can someone please help me? Thx in forward.
Here are both magisk patched and stock boot.img files
Using latest magisk 25.1 stable
Stock
Magisk Patched
Thank you. I've now read rooting is not possible because Mediatek. Is it true please? Will not break it.
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
I'm not able to boot correct in bootloader. There is written at the display extreme small "Fastboot Mode". If I set command "fastboot oem unlock" there is no reaction and nothing written. Changing with up/down is nothing doing.
Pushing Vol- and Powerbutton ends in recovery. There it is only possible to choose language and then wipe, reboot and power off.
My firmware is: CPH2399_11_A.09
Wrong code not
Code:
fastboot oem unlock
The correct command is
Code:
fastboot flashing unlock
Sorry, can not unlock the bootloader
Both commands failed
PS C:\adb2> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb2> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\adb2>
Try using a different ADB and fastboot. I use official platform tools from here
Also what comes up when you type
Code:
fastboot devices
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
I had the same problem while opening Bootloader...Tried everything - Windows 10
I did the same on Windows 7 and immidiately bootloader open.
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
Did you enable developer options and select Enable OEM unlock first?
garylawwd said:
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
Click to expand...
Click to collapse
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
It will if you flash kdragon safetynet fix in magisk
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
Don't rush and don't do it like me. Here boot images are for 09. So upgrade first.
Safety net passes with magisk module
Root easily hidden with lsposed and shamiko module.
Riski3Run said:
Did you enable developer options and select Enable OEM unlock first?
Click to expand...
Click to collapse
Yes
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
u should not be in fastbootd mode in adb type adb reboot bootloader
then type
fastboot flashing unlock
this should unlock your bootloader

Question OPPO A54 5G - Fastboot Commands dont work

I try to root the OPPO A54 5G. I got into the fastbootd mode and i want to unlock the bootloader.
I have no PIN or something, OEM Unlocking is activated and Developer Options are activated too.
If i execute the command fastboot devices
it shows my device.
If i execute the command fastboot flashing unlock
it says: FAILED (remote: 'Unrecognized command flashing unlock')
but if i execute the command fastboot oem unlock
it says: FAILED (remote: 'Command not supported in default implementation')
Can anyone help me?

Huawei Mediapad T5 stuck in eRecovery

Hi everyone,
i have a Mediapad T5 that it's unable to boot into OS. if i try to turn it on the tablet goes directly into the huawei eRecovery, and trying all the factory solutions (download and update, factory reset or anything else), just won't help and the tablet just goes back to the recovery.
I tried to use the HiSuite from huawei but once i got it in fastboot&rescue mode i receive the messagge that the device it's not supported.
Also while i'm here i also tried to unlock the bootloader but both PHONE and FRP are locked, so i just get errors.
I tried
fastboot flashing unlock
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
fastboot oem frp-unlock
FAILED (remote: 'oem_frp_check_password failed! Error = -1')
fastboot: error: Command failed
fastboot oem frp-erase
FAILED (remote: 'Command not allowed!')
fastboot: error: Command failed
PS C:\platform-tools>
Obviously i can't get into the system and enable the OEM unlock since the tablet doesn't boot into it.
Is there anything else i can try?

Categories

Resources