so i am trying to unlock bootloader in my device tecno spark 8c i enter the fastboot mode and tried the command fastboot oem unlock it say message ok but nothing happenes if i try to flash the vbmeta it says the bootloader locked and need to be unlocked how to unlock it?
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
no it didnt get unlock it only say message ok
i tried this command fastboot getvar unlocked
which give me message unlocked:no and i am running linux so i am using its commandline working with it and as i say it didnt get unlocked what is the problem i cant figure it out
jwoegerbauer said:
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
Click to expand...
Click to collapse
[[email protected]]-[~]
>>> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
[[email protected]]-[~]
>>> adb reboot bootloader
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
[[email protected]]-[~]
>>> adb reboot bootloader
[[email protected]]-[~]
>>> fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed
[[email protected]]-[~]
>>> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 17.010s
[[email protected]]-[~]
>>> fastboot oem unlock
OKAY [ 0.001s]
Finished. Total time: 0.001s
[[email protected]]-[~]
>>> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.001s
[[email protected]]-[~]
>>>
here is the commands and the output as u see and i already enabled oem in the developer options
Reboot Android to make changes permanent
jwoegerbauer said:
Reboot Android to make changes permanent
Click to expand...
Click to collapse
u mean reboot after i did the command?
i did it nothing change
try this method
https://forum.xda-developers.com/t/is-my-life-really-worth-it.4217751/post-84295797
fastboot flashing unlock
Related
Hello i have the Lg h340n and i am trying to unlock the bootloader but it fails i did install sdk tools and adb/fastboot and the commands work fine but this happens
When the phone is on i can find it with:
-adb devices
LGH340n1620e7f3
-adb reboot bootloader
Reboots me in to some wierd place with only commands on the top left :/
-fastboot devices
1620e7f3 Fastboot
-fastboot oem unlock
...
Failed <Remote:Unknown command>
finished. total time: 0.004s
and it sits there on bootloader doing nothing
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
getvar:all FAILED (remote: Command not allowed) it says command not allowed even in that command. and its bootloader lock is on any workaround so i can install update.zip without cmd says not enought space? or some workaround or command in fastboot to bootloader unlock with fastboot or any other idees?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36998 KB)...
OKAY [ 0.786s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.786s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ALWAYS GETTING FAILED (remote: Command not allowed)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
i think YOU ARE DOOMED??
only thing you can do is getting it back to the service center..gud luck buddy...
goran85 said:
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
Click to expand...
Click to collapse
same problem,, how to solve it??
writing 'recovery'...
FAILED (remote: Command not allowed)
sometime happenned to me and when installed the correct drivers in windows installed ok
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
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
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