Every time I flash the HBoot I get these C:\Users\Chris\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fas
tboot flash zip PN0714000.zip
sending 'zip' (2080 KB)...
OKAY [ 0.446s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.855s
can some one help me on these
Related
please can someone help me restore my HTC one M7 UK
I accidently erased the system in recovery mode when i try to flash RUU firmware PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed
i get this message
sending 'zip' (1010379 KB)...
OKAY [ 42.988s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 148.844s
C:\One_All-In-One_Kit_v\data>
phone is running
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENDSP-V31.120.274.0617
OS-2.24.401.1
EMMC-BOOT 2048MB
phone doesnt boot up as there is nothing to boot up 2
please if anyone can give me a working solution i will donate generously
thanks
Because you're trying to flash an older base and hboot but you don't have the S-OFF..
Guich said:
Because you're trying to flash an older base and hboot but you don't have the S-OFF..
Click to expand...
Click to collapse
Ok thanks can you please give me step by step instructions how to fix this
Answered in pm
Sent from One with Tapa4
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Tüm haklari saklidir.
C:\Users\kayhann>cd c:\tools
c:\Tools>fastboot flash zip m7.zip
< waiting for device >
sending 'zip' (1178274 KB)...
OKAY [ 61.900s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILED (remote: not allowed)
finished. total time: 172.544s
c:\Tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s
c:\Tools>fastboot flash zip m7.zip
< waiting for device >
sending 'zip' (1178274 KB)...
OKAY [ 46.159s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 158.305s
c:\Tools>
Wrong thread thats for first. U should ask here http://forum.xda-developers.com/htc-one/help
Wysłane z mojego Nexus 4
blackie06 said:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Tüm haklari saklidir.
C:\Users\kayhann>cd c:\tools
c:\Tools>fastboot flash zip m7.zip
< waiting for device >
sending 'zip' (1178274 KB)...
OKAY [ 61.900s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILED (remote: not allowed)
finished. total time: 172.544s
c:\Tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s
c:\Tools>fastboot flash zip m7.zip
< waiting for device >
sending 'zip' (1178274 KB)...
OKAY [ 46.159s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 158.305s
c:\Tools>
Click to expand...
Click to collapse
You're supposed to fastboot flash zip twice. The first time will fail with remote: 90 hboot pre-update because it updates the hboot first. The second time will flash the RUU. Although I have no idea what you did, but given that you apparently have 0 clue to what you're doing (because you might be a monkey just punching keys) i say you're f*cked. It looks like you tried to flash a GSM zip onto your CDMA HTC One and succeeded in flashing hboot only. Since you're S-ON, you are royally screwed since I think the GSM hboot will not recognize your partition layout and will refuse to boot. Don't think you can revert back with an official RUU either (no downgrades). Have fun with your new paperweight.
@ghul21 He is able to flash while S-ON because it looks like the zip is properly signed (otherwise I'm sure hboot would not have been updated in the first place anyways).
I have s-off yapmýs gave an error while loading custom ROMs and somehow deleted the s-off and locked for the first time this problem has happened to me
gamer765 said:
You're supposed to fastboot flash zip twice. The first time will fail with remote: 90 hboot pre-update because it updates the hboot first. The second time will flash the RUU. Although I have no idea what you did, but given that you apparently have 0 clue to what you're doing (because you might be a monkey just punching keys) i say you're f*cked.
@ghul21 He is able to flash while S-ON because it looks like the zip is properly signed (otherwise I'm sure hboot would not have been updated in the first place anyways).
Click to expand...
Click to collapse
Yup, now i see.. :silly:
Can you help me what can I do so not in the riffjtag
blackie06 said:
Can you help me what can I do so not in the riffjtag
Click to expand...
Click to collapse
Sorry, there is nothing we can do to help you. You're on GSM hboot, S-ON and re-locked bootloader, you're locked tighter than fort knox.
There must be a solution, but if it's going to be trash
blackie06 said:
There must be a solution, but if it's going to be trash
Click to expand...
Click to collapse
take it back to the store and tell them when you woke up and it was like that
just play dumb. It's dishonest but you seem desperate.
I would just look for another phone myself and chalk one up to experience.
And sorry for your loss, I would be sick if anything happened to my One
but I can't guarantee that the u.s. statement device verizone Turkey
the original stock no ruu?
Info
C:\androidsdk\tools>fastboot getvar all
INFOversion-bootloader: 30B4
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Samsung S4 SDRAM DIE=4Gb
INFOemmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
INFOproduct: ghost
INFOrevision-hardware: 0x8300
INFOradio: 0x1
INFOsecure: yes
INFOmid: 026b
INFOserialno: T01130D03O
INFOqe: qe 0/0
INFOunlocked: no
INFOiswarrantyvoid: no
INFOmax-download-size: 805306368
INFOuid: 85828E040C000100000000000000
INFOimei: 000000000000000
INFOmeid:
INFOsku: 000000000000000
INFOcid: 0xff
INFOiccid: 89014103286406835591
INFOdate: 01-01-1970
INFOcust_md5:
INFOreason: Reboot to bootloader
INFOro.build.date: Mon Jul 15 17:06:36 CDT 2013
INFOro.build.id:
INFOro.build.tags: release-keys
INFOro.build.type: userdebug
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.incremental: 14
INFOro.build.version.release: 4.2.2
INFOro.mot.build.customerid: att
INFOro.product.name: factory_ghost
INFOro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
INFOro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-11/
INFOro.build.fingerprint[2]: 14:userdebug/release-keys
INFOro.build.version.full[0]: Blur_Version.139.9.51.ghost_att.
INFOro.build.version.full[1]: ATT.en.US
INFOkernel.version[0]: Linux version 3.4.42-xline-eng-g
INFOkernel.version[1]: fd1a699-00137-g677455b (hudsoncm
INFOkernel.version[2]: @il93lnxdroid48) (gcc version 4.
INFOkernel.version[3]: 6.x-google 20120106 (prerelease)
INFOkernel.version[4]: (GCC) ) #1 SMP PREEMPT Mon Jul
INFOkernel.version[5]: 15 17:32:37 CDT 2013
Error
Are you in bootloader or android?:bootloader
...
OKAY [ 0.109s]
finished. total time: 0.109s
sending 'partition' (32 KB)...
OKAY [ 0.234s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.453s]
finished. total time: 0.688s
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
flashing aboot ...
flashing sbl3 ...
flashing rpm ...
flashing tz ...
flashing sbl2 ...
flashing sbl1 ...
OKAY [ 4.875s]
finished. total time: 5.219s
sending 'logo' (636 KB)...
OKAY [ 0.313s]
writing 'logo'...
OKAY [ 0.891s]
finished. total time: 3.578s
sending 'boot' (10240 KB)...
OKAY [ 0.906s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.063s
sending 'recovery' (10240 KB)...
OKAY [ 0.922s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.094s
sending 'system' (786432 KB)...
OKAY [ 49.453s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 50.813s
Tried
ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-51_CFC_1FF.xml.zip
ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF.xml.zip
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip
One Phone screen ...
Failed to hab check for recovery: 0x56
preflash validation failed for recovery
Failed to hab check for recovery: 0x56
preflash validation failed for system failed
Invalid PIV image : system
In the output of fastboot getvar all it said your bootloader version was 30.B4, yet it said NFOro.build.version.release: 4.2.2
That is your problem. At some point that phone had 4.4.2 on it and was downgraded by skipping at least motoboot.img if not also skipping gpt.bin.
It has been advised MANY TIMES to not downgrade.
Further, the output says.. Blur_Version.139.9.51.ghost_att. that is the INITIAL SHIPPING ROM.. again, its been said that downgrading to that is an automatic brick.
AT this point, I hesitate to suggest anything. But AT YOUR OWN RISK!! you can try -> ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF.xml.zip unzip it, get the latest mFastboot and use the steps under OPTION 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
and hope it works. If it does not, then try it again with the 4.4.4 SBF.
ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF
C:\Moto>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.125s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.234s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.453s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.359s]
writing 'motoboot'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl1 ...
OKAY [ 5.016s]
finished. total time: 5.375s
C:\Moto>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.250s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.453s]
finished. total time: 0.703s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl1 ...
OKAY [ 4.953s]
finished. total time: 5.297s
C:\Moto>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (636 KB)...
OKAY [ 0.328s]
writing 'logo'...
OKAY [ 0.875s]
finished. total time: 1.219s
C:\Moto>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.938s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.094s
& same thing happening on ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
C:\Moto>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.125s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.266s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.422s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.391s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 4.938s]
finished. total time: 5.328s
C:\Moto>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.266s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.422s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.375s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 4.922s]
finished. total time: 6.266s
C:\Moto>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.328s]
writing 'logo'...
OKAY [ 0.891s]
finished. total time: 1.219s
C:\Moto>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.922s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.078s
Not sure what to suggest. Your phone isn't far enough gone to try this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
maybe we can get @samwathegreat to offer a few suggestions?
KidJoe said:
Not sure what to suggest. Your phone isn't far enough gone to try this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
maybe we can get @samwathegreat to offer a few suggestions?
Click to expand...
Click to collapse
Yikes! Looks like the method I *would have* suggested has already been tried and was unsuccessful.
The only way that I've found to recover a device once it starts failing validation checks on boot.img is to unlock the bootloader. After unlocking, it should be able to flash without error. Of course....middleman would have to be involved.
I don't see another option, sadly :/
samwathegreat said:
Yikes! Looks like the method I *would have* suggested has already been tried and was unsuccessful.
The only way that I've found to recover a device once it starts failing validation checks on boot.img is to unlock the bootloader. After unlocking, it should be able to flash without error. Of course....middleman would have to be involved.
I don't see another option, sadly :/
Click to expand...
Click to collapse
Yes ... i too was thinking about unlocking bootloader might solve the problem
How much $$ for a boot loader unlock ... any idea ?
aamszia said:
How much $$ for a boot loader unlock ... any idea ?
Click to expand...
Click to collapse
China Middleman thread in general section is $45, Jcase's yet to be released Sunshine tool $25. But we don't know the details of Sunshine yet, like if you must be on certain version, etc.
KidJoe said:
China Middleman thread in general section is $45, Jcase's yet to be released Sunshine tool $25. But we don't know the details of Sunshine yet, like if you must be on certain version, etc.
Click to expand...
Click to collapse
Sunshine might not work i updated it to 4.4.4 bootloaders ?
aamszia said:
Sunshine might not work i updated it to 4.4.4 bootloaders ?
Click to expand...
Click to collapse
We don't know if it will work on 4.4.4 devices.
BUT, sunshine is an **APP**. If you device can not boot into Android, well...............you can't run an app, can you?
Middleman will likely be your only option.
samwathegreat said:
We don't know if it will work on 4.4.4 devices.
BUT, sunshine is an **APP**. If you device can not boot into Android, well...............you can't run an app, can you?
Middleman will likely be your only option.
Click to expand...
Click to collapse
the phone is on .. and menu & settings all messed up .. but i think i can install an APP in this condition
DAM ... Xt907 bricked b me today .. & guess what ... the same error .. Prevalidation Failed .. .. Phone had 4.4.2 before .. I was just re-installing 4.4.2 again becasuse wifi was not working .. . Now got stuck in fastboot ..
I am UNLUCKY
What version were you coming from before you got the validation error for 4.4.2?
Sent from my XT1080 using XDA Free mobile app
Gtech145 said:
What version were you coming from before you got the validation error for 4.4.2?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
4.4.2 ........... it was the same versio i guess
yesterday i received Moto G UNLOCKED BOOTLOADER
same error PRE VALIDATION FAILED
:crying: Every time I try to install a different hboot I get this
Error writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.735s
gohanmoka said:
:crying: Every time I try to install a different hboot I get this
Error writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.735s
Click to expand...
Click to collapse
See I want to downgrade to to do a sim unlock plz I need some help
You have to be s-off to downgrade.
BD619 said:
You have to be s-off to downgrade.
Click to expand...
Click to collapse
I am s-off
M7_WLS PVT SHIP S-OFF RH
Hello
I have a big problem, at least I think so.
Trying to put Spanish language to an E5 Plus XT1924-9, use this firmware (XT1924-6_HANNAH_ATT_8.0.0_OCPS27.91-164-20_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml) and I was left with a black screen, I managed to put it in fastboot and did not accept the flash XT1924-9, it is logical, the flash of the XT1924-6 is a superior version.
I tried Rescue and Smart Assistant and I couldn't flash the older version of the XT1924-9 is OCP27.91_38_31_54_cid11.
What can I do to solve this problem?
Thank you for your time
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.172s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7483 KB) OKAY [ 0.539s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.380s]
Finished. Total time: 1.108s
(bootloader) is-logical:modem: not found
Sending 'modem' (68818 KB) OKAY [ 2.372s]
Writing 'modem' OKAY [ 0.468s]
Finished. Total time: 3.597s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (5584 KB) OKAY [ 1.218s]
Writing 'fsg' OKAY [ 0.069s]
Finished. Total time: 1.464s
Erasing 'modemst1' OKAY [ 0.016s]
fastboot: usage: unknown command E:\Motorola\XT1924-9\AHANNAH_RETCN_OCP27.91_38_31_54_cid11_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\fsg.mbn
Erasing 'modemst2' OKAY [ 0.016s]
fastboot: usage: unknown command E:\Motorola\XT1924-9\AHANNAH_RETCN_OCP27.91_38_31_54_cid11_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\fsg.mbn
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.777s]
Writing 'dsp' OKAY [ 0.119s]
Finished. Total time: 0.972s
(bootloader) is-logical:logo: not found
Sending 'logo' (1423 KB) OKAY [ 0.231s]
Writing 'logo' OKAY [ 0.042s]
Finished. Total time: 0.342s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.768s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.217s]
Finished. Total time: 1.034s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (24576 KB) OKAY [ 1.072s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.276s]
Finished. Total time: 1.389s
(bootloader) is-logical:system: not found
Sending 'system' (514035 KB) OKAY [ 16.565s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system: not found
Sending 'system' (520536 KB) OKAY [ 16.958s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system: not found
Sending 'system' (513624 KB) OKAY [ 16.514s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system: not found
Sending 'system' (501821 KB) OKAY [ 16.183s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system: not found
Sending 'system' (340876 KB) OKAY [ 11.040s]
Writing 'system' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:vendor: not found
Sending 'vendor' (405777 KB) OKAY [ 13.079s]
Writing 'vendor' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalem: not found
Sending 'oem' (511087 KB) OKAY [ 16.416s]
Writing 'oem' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalem: not found
Sending 'oem' (505190 KB) OKAY [ 16.253s]
Writing 'oem' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalem: not found
Sending 'oem' (389945 KB) OKAY [ 12.655s]
Writing 'oem' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'cache' OKAY [ 0.014s]
fastboot: usage: unknown command E:\Motorola\XT1924-9\AHANNAH_RETCN_OCP27.91_38_31_54_cid11_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\oem.img_sparsechunk.2
Erasing 'userdata' OKAY [ 0.057s]
fastboot: usage: unknown command E:\Motorola\XT1924-9\AHANNAH_RETCN_OCP27.91_38_31_54_cid11_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\oem.img_sparsechunk.2
Erasing 'DDR' OKAY [ 0.010s]
fastboot: usage: unknown command E:\Motorola\XT1924-9\AHANNAH_RETCN_OCP27.91_38_31_54_cid11_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\oem.img_sparsechunk.2
Click to expand...
Click to collapse
Please help me have Motorola x9124-9. I made a backup of it from TWRP, then I flashed the latest version of AHannah. Now I back up the main backup restore, then the process is successful, then the mobile is turned on, then the light is blinking. I am very worried. Help help help any xpert help plz