Develop Bugs

Bad Key written in Bootloader warning screen.

I have unlocked bootloader. And flash the official recovery to get Naugat OTA but after updating. I am seeing "ID : bad key " instead of "ID : N/A" which is written in previous version of OS.
Any one know what it really meant.?

Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.

GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
I tried but still it shows bad key.. but it's ok until my device boots in system succesfully
.

GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?

S3V3N said:
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
Click to expand...
Click to collapse
Pretty sure everyone has this with an unlocked bootloader.

ok thx

xxBrun0xx said:
Pretty sure everyone has this with an unlocked bootloader.
Click to expand...
Click to collapse
definitely not.

Am facing same problem. Bad boot image.. Looking for stock boot image

kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
did you find the solution iused twrp and i had no problem after installing the Russian ROM im getting this message

kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.

G4liant said:
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
Click to expand...
Click to collapse
I mean 'bad key' instead of showing "N/A"

kdagia said:
I mean 'bad key' instead of showing "N/A"
Click to expand...
Click to collapse
You need to flash modified logo.bin ...That's it

Same, and cant seem to flash at all
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock

[email protected] said:
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
Click to expand...
Click to collapse
I have exactly the same problem, has it been able to solve it?
How to solve it?

Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.

thoros1179 said:
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
Click to expand...
Click to collapse
Try typing "fastboot oem fb_mode_clear" inside the bootloader.

Stuck in bootloader - no recovery - no system

Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?

Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?

Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."

xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!

Stucked in bootloader

Hi,
I was normally using my Moto G5S (XT192) when it turned off. Then I get stucked in bootloader screen, showing this message:
Failed to verify hab image boot
Failed to validade boot image
ERROR: Failed to pass validation, backup to fastboot
So I tried to run a stock ROM in it w/ ADB & fastboot.
I've tried all these ROMs:
MONTANA_RETAIL_7.1.1_NPPS26.102-49-8_cid50
MONTANA_RETAIL_7.1.1_NPP26.102-49_cid50
MONTANA_RETAIL_7.1.1_NPP26.102-16_cid50
MONTANA_NPP26.102-49_cid50
MONTANA_NPPS26.102-49-4_cid50
MONTANA_NPP26.102-16_cid50
MONTANA_NPPS26.102-49-8_cid50
CEDRIC_NPP25.137-33_cid50
But all of them get errors while flashing and I can't get off this.
Obs: my bootloader isn't unlocked. I can't turn on the phone, so I can't unlock it.
Can anyone help me, please?
Thx

brnstocco said:
Hi,
I was normally using my Moto G5S (XT192) when it turned off. Then I get stucked in bootloader screen, showing this message:
Failed to verify hab image boot
Failed to validade boot image
ERROR: Failed to pass validation, backup to fastboot
So I tried to run a stock ROM in it w/ ADB & fastboot.
I've tried all these ROMs:
MONTANA_RETAIL_7.1.1_NPPS26.102-49-8_cid50
MONTANA_RETAIL_7.1.1_NPP26.102-49_cid50
MONTANA_RETAIL_7.1.1_NPP26.102-16_cid50
MONTANA_NPP26.102-49_cid50
MONTANA_NPPS26.102-49-4_cid50
MONTANA_NPP26.102-16_cid50
MONTANA_NPPS26.102-49-8_cid50
CEDRIC_NPP25.137-33_cid50
But all of them get errors while flashing and I can't get off this.
Obs: my bootloader isn't unlocked. I can't turn on the phone, so I can't unlock it.
Can anyone help me, please?
Thx
Click to expand...
Click to collapse
Please do the following in fastboot mode and post it here.
Code:
fastboot getvar all
I doubt there is some issue with your CID. CID is a unique number to identify the device and is used for signing. HAB check would fail only if you have a wrong or 0xDEAD CID value. If that is the case, only option I could think about is to give it for servicing. If anyone has any ideas, please share.
Thanks
KS

fastboot loop

I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?

baudoux said:
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
Click to expand...
Click to collapse
How did you think to flash LineageOs in boot where TWRP used to be?
Anyway if you didn´t complete this disastrous attempt you could solve it restoring mdtp partition that is a kind of gpt for other devices.
Flash it in both slot using fastboot. Then you´ll can know which partition is active, if the system yet still alive you´ll can boot on it or boot temporarily to TWRP to do your stuff but if not then you´ll need to restore one or more partitions flashing again the whole stock rom through MiFlash tool.

SubwayChamp said:
How did you think to flash LineageOs in boot where TWRP used to be?
Click to expand...
Click to collapse
this was a typo, and I got lost in the process
SubwayChamp said:
Flash it in both slots using fastboot.
Click to expand...
Click to collapse
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?

baudoux said:
this was a typo, and I got lost in the process
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
Click to expand...
Click to collapse
Sorry for delay, yes, in both partitionn you have to flash mdtp, is to restore the table partition.
And about LOS I think you need to read a bit more or you'll have a thermonuclear reaction some day (just kidding) Custom roms come in form of zip and contain scripts that are prepared for developers to can unpack and flash files in the right place so don't worry about it.
First restore your partitions and the next is a ready-to-go.

SubwayChamp said:
yes, in both partitionn you have to flash mdtp, is to restore the table partition.
First restore your partitions and the next is a ready-to-go.
Click to expand...
Click to collapse
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file

baudoux said:
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
Click to expand...
Click to collapse
You´ll find it inside the stock rom.

SOLVED
flashing mtdp_a and mtdp_b did not help, I hat to flash the stock rom again and start the process from scratch
other problems showed up:
I had to downgrade twrp to 3.3.0 to avoid error 7 while flashing LINEAGE OS
and then upgrade it again to 3.3.1 fo avoid error 64 while flashing GAPPS

Question [Solved] Stuck in fastboot with locked bootloader

HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".

ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
please , i want to know , how can i give fastboot on my redmi7 device

H R Habib said:
please , i want to know , how can i give fastboot on my redmi7 device
Click to expand...
Click to collapse
This is a forum dedicated to the Poco F3 so I think you should ask it on the Redmi 7's forum

Use MiFlash to flash the fastboot Version of stock.

ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.

Phoost said:
Use MiFlash to flash the fastboot Version of stock.
Click to expand...
Click to collapse
I didn't find an official MiFlash tool and I don't trust closed-source tools for this kind of things.
avidduo said:
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Click to expand...
Click to collapse
I tried that but it didn't work.
EDIT: After re-trying several times, I was finally able to make it work by booting with ArrowOS' recovery. TWRP was not accepted, but ArrowOS' one was
So I've been able to flash the Xiaomi.EU rom, I'll stick with it for now.