Boot up failed, Failed to validate boot image

[chetana22]

Dear Team, I have MotoG4 Plus (Model XT1643).

Post selecting the data migration from internal storage to SD card, the phone stopped booting.

[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode

Kindly suggest

 

[echo92]

Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?

Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.

You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?

 

[usha55]

Dear Team, I have MotoG4 Plus (Model XT1643).

Post selecting the data migration from internal storage to SD card, the phone stopped booting.

[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode

Kindly suggest

Are u using dummy bootloader I guess not orginal

---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------

No need to reflash u have to upgrade the bootloader then u have to flash the stock rom

 

[chetana22]

@ Echo

Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>

Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?

<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>


@ usha55

Are u using dummy bootloader I guess not orginal

<<<< I do not know >>>>

---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------

No need to reflash u have to upgrade the bootloader then u have to flash the stock rom

<<<< How do I upgrade? Please guide >>>>

 

[____Mdd]

@chetana22 thas makes confusion if you write post like that.

You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.

 

[chetana22]

@chetana22 thas makes confusion if you write post like that.

You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.

Hi.

Im not able to upload the image. Pl. find baseband details below.

Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST

Pls let me know steps to reflash boot.img

 

[____Mdd]

Hi.

Im not able to upload the image. Pl. find baseband details below.

Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST

Pls let me know steps to reflash boot.img

If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8

Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.

 

[chetana22]

Tried the method as given.

At the end ..it is repeatedly showing
FAILED (remote failure)

 

[echo92]

Tried the method as given.

At the end ..it is repeatedly showing
FAILED (remote failure)

Which stock firmware are you flashing that gives you this error? Please mention the build number.

You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Flash as per below commands if you want to save your data (no need to re-lock your bootloader).

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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot

 

[al3al3al3jandr0]

It does not work

Which stock firmware are you flashing that gives you this error? Please mention the build number.

You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Flash as per below commands if you want to save your data (no need to re-lock your bootloader).

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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot

It does not work

 

[echo92]

It does not work

What didn't work, please describe more about what happened?

From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.

 

[al3al3al3jandr0]

Now the error sends it to me in the boot.img

What didn't work, please describe more about what happened?

From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.

Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img

 

[echo92]

Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img

1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.

2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.

Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.

3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.

 

[al3al3al3jandr0]

thank you

1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.

2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.

Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.

3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.

ok thank you very much, you're right I'll have to wait

 

[Adityashankar]

Sir, how to fix no found bootimage in m0t0 g4plus XT1643

 

[echo92]

Sir, how to fix no found bootimage in m0t0 g4plus XT1643

Did this happen suddenly, and is this with the stock firmware or using a custom ROM?

You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

 

[CAKIROV]

Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help

 

[Shreyas17]

flash latest stock rom and skip the following instruction while flashing

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img

 

[moracarlos70]

MOTOROLA G5S PLUS - Start up failed

My phone is G5s PLUS ... Sorry