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.

You device has been unlocked and cannot be trusted (Bootloop)

I just got a moto z play today and the first thing I did was try to root it so I could work with TitaniumBackup. After unlocking the bootloader and booting into TWRP (Not installing it, just booting) I realized that I forgot to transfer my files to the phone. Derp. So I tried to restart my phone and now the only thing that pops up is a message saying
"Your device has been unlocked and can't be trusted. To learn more visit Motorola.com/unlockbootloader. ID: bad key. Your device will boot in 5 seconds." Then it loops. Endlessly, with the exception of occasionally going a screen with a circle which says "Erasing". I really wanted to stay on the stock rom, is there any way to fix this without installing a custom recovery or ROM?

GIR385 said:
I just got a moto z play today and the first thing I did was try to root it so I could work with TitaniumBackup. After unlocking the bootloader and booting into TWRP (Not installing it, just booting) I realized that I forgot to transfer my files to the phone. Derp. So I tried to restart my phone and now the only thing that pops up is a message saying
"Your device has been unlocked and can't be trusted. To learn more visit Motorola.com/unlockbootloader. ID: bad key. Your device will boot in 5 seconds." Then it loops. Endlessly, with the exception of occasionally going a screen with a circle which says "Erasing". I really wanted to stay on the stock rom, is there any way to fix this without installing a custom recovery or ROM?
Click to expand...
Click to collapse
Mine did this once. I ended up having to do a full restore to stock to fix it. It did though. I believe I flashed the Addison firmware.
Sent from my XT1635-02 using Tapatalk

PhilD41 said:
Mine did this once. I ended up having to do a full restore to stock to fix it. It did though. I believe I flashed the Addison firmware.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
Thanks for your response, sorry for taking so long.
When you say you did a full restore using Addison firmware, how did you do it? I thought that the stock firmware wasn't available. Did you perform a factory data reset through the recovery?

GIR385 said:
Thanks for your response, sorry for taking so long.
When you say you did a full restore using Addison firmware, how did you do it? I thought that the stock firmware wasn't available. Did you perform a factory data reset through the recovery?
Click to expand...
Click to collapse
Sorry for the long delay in response. My family and I have been on vacation for the last two weeks. I pulled the files for the FW from one of the forums here. I would have to go back searching for which one. The process I used is posted below. It was a full rewrite of the device so yes, I lost all my user data. I did not do a factory reset after flashing though, just booted it up. I also keep the stock recovery. I use fastboot to boot into TWRP. When I need to. For these instructions you don't need recovery, just fastboot.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash system system.img_sparsechunk.6
sudo fastboot flash system system.img_sparsechunk.7
sudo fastboot flash system system.img_sparsechunk.8
sudo fastboot flash system system.img_sparsechunk.9
sudo fastboot flash oem oem.img
sudo fastboot erase carrier
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
The full file name for the FW I used is "ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" Not sure if that helps any or not.

[Help] Moto G5 won't turn on and restarts constantly

Hello people! I hope you are well
First of all, sorry if the English I write with is not good, I am using Google translator (I am from Argentina)
I want to ask for your help (and I apologize in advance if this is not the correct section, it is my first post)
I have a motorola moto G5 xt1670 which restarts without stopping. I tell you; Friday it started with constant reboots and it did not allow me to use the device correctly. On Saturday morning I reinstalled the operating system (android 8.1 stock) using ADB and fastboot commands, so far so great. I walked for a couple of hours correctly, however, after a few hours the phone restarts and stays in a kind of Bootloop which I can NOT remove. It restarts 5 or 6 times in a row, once it is turned on, I can use it for no more than 5 minutes and it restarts again and so on.
I tried installing the operating system through fastboot, through recovery, I did a thousand wipes, from the same recovery I tried to repair the files, I deleted the original rom and I tried installing an alternative rom (lineage OS and pixel experience), and I can swear that the phone does not rips me off.
In fact, after installing pixel experience, the cell phone sends me a message that says the following: "Android system, there is an internal problem with your device, contact the manufacturer for instructions"
The truth is that I don't know what to try now, reinstall the stock firmware more than 5 times, try to downgrade, and the same thing happens. The phone passes the initial configuration, I move it for two minutes on the desktop and it restarts without end.
If anyone has an idea what it might be, I would greatly appreciate your help!
Thank you!

The message you get on pixel experience about an internal problem contact the manufacturer is normal - this is because the system and vendor fingerprint do not match in a hack to pass safetynet
Anyway going back to your problem
If you have downloaded firmware from
https://mirrors.lolinet.com/firmware/moto/cedric/official/
I recommend using the latest retail version
And installed it using these commands in order
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Without any errors (eg validation error security downgrade error etc)
Then you may have a hardware fault - anything from the battery to the main board or other components
Take it to a repair shop for testing
You can also run an adb logcat but this has to be running at the exact moment the reboot happens & it may show why the phone the restarted
And remove the sdcard if you have one inserted or format it to make sure it's not causing any issues

Question For those who have flashed International ROM but NFC not working

PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone

Ehh it works, thanks brother!

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
What Rom are you using?
Do you have any bugs on it?
Android auto works?

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
Is it possible to use this method to change touchscreen drivers? Do you know where it is stored at?
I was having a weird touch screen problem with virtual buttons with an international modified Rom and this touchscreen problem was not present on Chinese stock Rom...

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
what img files are excluded in AP flashing process?

doesnt worked for me

How big should the file be "vendor.img"? My has 1,13GB
I try flash it, but get error.
Code:
C:\Users\snego\Downloads\tools_r33.0.2-windows>fastboot erase vendor_a
Erasing 'vendor_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\Users\snego\Downloads\tools_r33.0.2-windows>fastboot flash vendor_a vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: '')
fastboot: error: Command failed
1. Go in fastboot mode
2. fastboot reboot fastboot
3. flash vendor in fastbootD mode.
but still it didn't help. phone won't boot after vendor.img flash

Question [SOLVED]Mi 11 lte 5g ne bricked(?)

after an unsuccessful firmware of my device, it started to boot constantly in fastboot mode. when I try to restore via miflash and xiaomi tool v2, I get the error "Flash super error". how to solve this problem?
P.S. : sorry if something is written incorrectly, I wrote through a translator

Hi,
did you look at this topic ?

newbie_or_not_newbie said:
Hi,
did you look at this topic ?
Click to expand...
Click to collapse
yes, they advised me to install the xiaomi.eu firmware, but I get the error of flashing the partition (?) "super"
Sending sparse 'super' 1/9 (729624 KB) OKAY [ 16.439s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed

try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom

WaldoVM said:
try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom
Click to expand...
Click to collapse
thats work!!
thanks bro