Database Info

MI4c unlocking hell!

Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply​>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s​
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?

Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn

Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s​

SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!

Bootloop after installing an Factory Image for Android 9.0

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…

Cannot unlock Flashing Lock Flag for Blu Studio Mega 2019

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.

FAILED (remote: 'Download is not allowed on locked devices')

i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

i also try
fastboot oem unlock
it show
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??

chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Rename the patched boot.img to "boot.img", then place the patched .img in your fastboot folder on PC then type:
fastboot flash boot boot.img
When you place the file in your fastboot folder, you don't need to include the path to the file in the command, it automatically looks for the file in the fastboot folder by default when you do not enter a path. Renaming the file to "boot.img" isn't necessarily required, but, it does simplify things for fastboot and makes the command easier to remember and type.
The same applies if you want to flash a system.img, recovery.img, etc.. Just change the name of the file to "system.img" or "recovery.img" and place it/them in your fastboot folder and it simplifies your commands to:
fastboot flash system system.img
And
fastboot flash recovery recovery.img
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com

now i got same message
D:\platform-tools>fastboot flash boot boot.img
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

Droidriven said:
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
Click to expand...
Click to collapse
im already try this verify cmd location, install fastboot driver & boot fastboot mode nothing change.
Code:
D:\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??

chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock

xXx yYy said:
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
Click to expand...
Click to collapse
when i try
D:\platform-tools>fastboot flashing unlock
it show
Code:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
i use https://developer.android.com/studio/releases/platform-tools
what should i do ??

The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.

xXx yYy said:
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
Click to expand...
Click to collapse
i use mtp driver
update Portable Devices to MTP USB Device
but when i enter fastboot mode
it become Android Device Android Bootloader Interface.

where is extracted the driver package folder ?? https://www.xda-developers.com/download-android-usb-drivers/

I'm having simular issue with my specter 8 tablet. I unlock the bootloader and give me the normal prompt. I go back do everything else and will execute reboot devices ect. However won't flash patch_boot.img brings up message
FAILED (remote: 'Download is not allowed on locked devices').

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?