Hello all,
I currently have a Blu Studio Mega 2019 android device with me. It is running android 9. I have spent the last 3 days trying my hardest and expending all resources to root the device. I have been unsuccessful every time and the main reason is that When I run the below command it always fails. I have tried "fastboot oem unlock" or "fastboot oem device-info" and it always returns command not valid.
fastboot flash recovery twrp.img
Sending 'recovery' (16356 KB) OKAY [ 0.527s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
Yes I do have usb debugging on, OEM unlock on, I have the android drivers for the "fastboot gadget installed". My device shows up when I type "fastboot devices" and will reboot with "fastboot reboot". I have not been able to find a solution to my 'Flashing Lock Flag is locked. Please unlock it first!' problem. I hope someone else has found the solution.
Related
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 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?
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?
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