Related
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
Hello, my moto g xt1068 was in a bootloop, I've tried to flash back a stock firmware but it always give me an error like this "(bootloader) | Failed to erase partition (bootloader) Failed to flash partition logo | FAILED (remote failure)" and now it has only the "AP fastboot flash mode", no system and no recovery.
Some more info:
- My bootloader is unlocked;
- I can't boot any recovery using fastboot boot command, I got the error "Incomplete boot image for booting" (cwm,twrp, stock)
- My partitions are "raw" I suspect this is the main problem
- I've tried using windows and osx
- I've tried using fastboot and mfastboot
- I'm not able to use RSD lite, it' doesn't recognize my device
- I've tried a lot of stock firmware, no difference
Please help me, there is anything else to try? Is my phone dead (maybe emmc failure)?
Here is the output of fastboot getvar all:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D223XTZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: 233A12050F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 353321068993768
(bootloader) meid:
(bootloader) date: 09-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 15:41:58 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.46-28.1/1:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.26.1.titan_retde.
(bootloader) ro.build.version.full[1]: retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 13:23:41 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D223XTZ
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.085s
This is technically not an answer....
Which ROM where you using when your phone began boot looping (stock or custom). What you should have done was try a complete factory reset(did this a couple of times to my xt1068 when it was in boot loop). Can i ask the names of the stock firmware you used (the full information about them) and the commands you used. Let me see if i can help you
sagar846 said:
Which ROM where you using when your phone began boot looping (stock or custom). What you should have done was try a complete factory reset(did this a couple of times to my xt1068 when it was in boot loop). Can i ask the names of the stock firmware you used (the full information about them) and the commands you used. Let me see if i can help you
Click to expand...
Click to collapse
Thank you for your answer.
I had a stock firmware 5.02 with stock recovery, can't remember the exact version but i guess it was the "retde" one
I tried to wipe cache and userdata but it won't get out of the boot loop (did you mean this by full factory reset?)
I've tried RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml,Retaildsdsall_XT1068_5.0.2_LXB22.99-16_Easy_Installer, RETAILDSDSALL_EU_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml, RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml, XT1068_4.4.4_DSDS_ALL.23_Easy_Installerand and even RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml
I tried also some variation on the fastboot commands but mainly like this:
HTML:
mfastboot.exe oem fb_mode_set
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem fb_mode_clear
mfastboot.exe reboot
kesy85 said:
Thank you for your answer.
I had a stock firmware 5.02 with stock recovery, can't remember the exact version but i guess it was the "retde" one
I tried to wipe cache and userdata but it won't get out of the boot loop (did you mean this by full factory reset?)
I've tried RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml,Retaildsdsall_XT1068_5.0.2_LXB22.99-16_Easy_Installer, RETAILDSDSALL_EU_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml, RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml, XT1068_4.4.4_DSDS_ALL.23_Easy_Installerand and even RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml
I tried also some variation on the fastboot commands but mainly like this:
HTML:
mfastboot.exe oem fb_mode_set
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem fb_mode_clear
mfastboot.exe reboot
Click to expand...
Click to collapse
when you type the fastboot comand: fastboot devices, what's written on the screen?
dani.galla said:
when you type the fastboot comand: fastboot devices, what's written on the screen?
Click to expand...
Click to collapse
Only the serial number followed by fastboot, but I think it's right, no?
ZX1D223XTZ fastboot
kesy85 said:
Only the serial number followed by fastboot, but I think it's right, no?
ZX1D223XTZ fastboot
Click to expand...
Click to collapse
Yes, right, means that the computer recognizes the phone.
When you flash stock via fastboot, gives you errors?
Have you tried with the easy installer tool? (this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612)
dani.galla said:
Yes, right, means that the computer recognizes the phone.
When you flash stock via fastboot, gives you errors?
Have you tried with the easy installer tool? (this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612)
Click to expand...
Click to collapse
yes to both the questions.
I've tried also using easy installer but it's simply a .bat file containing the same commands I manually use.
And i've got this errors while flashing stock firmware:
HTML:
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
OKAY [ 0.324s]
finished. total time: 0.351s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 100.186s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.028s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.988s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.325s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.344s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.334s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.358s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257619 KB)...
OKAY [ 13.069s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.137s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256618 KB)...
OKAY [ 13.045s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.140s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
^[[AOKAY [ 13.159s]
writing 'system'...
^[[A(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.237s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
OKAY [ 13.164s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.246s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (244081 KB)...
OKAY [ 12.647s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.689s
mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (36088 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.178s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.558s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.584s
mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
kesy85 said:
yes to both the questions.
I've tried also using easy installer but it's simply a .bat file containing the same commands I manually use.
And i've got this errors while flashing stock firmware:
HTML:
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
OKAY [ 0.324s]
finished. total time: 0.351s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 100.186s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.028s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.988s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.325s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.344s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.334s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.358s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257619 KB)...
OKAY [ 13.069s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.137s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256618 KB)...
OKAY [ 13.045s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.140s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
^[[AOKAY [ 13.159s]
writing 'system'...
^[[A(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.237s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
OKAY [ 13.164s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.246s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (244081 KB)...
OKAY [ 12.647s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.689s
mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (36088 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.178s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.558s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.584s
mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
Click to expand...
Click to collapse
Everything failed, very strange.
Try to update your drivers, and the try to flash again.
If you can, try with an other computer, and an other cable data.
dani.galla said:
Everything failed, very strange.
Try to update your drivers, and the try to flash again.
If you can, try with an other computer, and an other cable data.
Click to expand...
Click to collapse
Already did this, 1 windows 8.1 PC, 1 windows 10 PC, 1 virtual windows 7 pc, 1 mac book osx 10.10, drivers from motorola, multiple data cables, single adb and composite adb no difference
Small update, managed to get rsd lite to work but no difference, flash fails anyway.
and there is the full output of easy installer:
HTML:
FIRMWARE Auto Restore Script by Gary J Wright
MOTO G 2nd GEN Lollipop 5.0.2 FIRMWARE Flashe
Plug in USB CABLE and Put Phone in AP FASTBOO
Premere un tasto per continuare . . .
* server not running *
* daemon not running. starting it now on port
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 99.122s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 4.992s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition tabl
FAILED (remote failure)
finished. total time: 10.265s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.086s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.936s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.023s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.999s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.374s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.335s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recove
FAILED (remote failure)
finished. total time: 10.374s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.104s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.174s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.135s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.268s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.104s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.190s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.324s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.378s
target max-sparse-size: 256MB
sending 'system' (44584 KB)...
OKAY [ 6.614s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.435s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 7.067s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 12.106s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.031s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.070s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.109s
ERASING CACHE ......
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.031s
ERASING USERDATA.......
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.015s
DONE!.........PRESS ANY KEY TO REBOOT
Please help me :crying:
[/QUOTE]Please help me :crying:[/QUOTE]
Unfortunately this is an issue faced by a few users including myself, there is no solution at the moment and it seems that some people who have returned the phone to Motorola had to pay to have the motherboard replaced. Sorry
same problem here too, please Sir give solution
is there a solution yet? I have the same problem
Please help me :crying:[/QUOTE]
Unfortunately this is an issue faced by a few users including myself, there is no solution at the moment and it seems that some people who have returned the phone to Motorola had to pay to have the motherboard replaced. Sorry[/QUOTE]
Is there any solution for this thing till now?
---------- Post added at 11:34 AM ---------- Previous post was at 11:29 AM ----------
kesy85 said:
Hello, my moto g xt1068 was in a bootloop, I've tried to flash back a stock firmware but it always give me an error like this "(bootloader) | Failed to erase partition (bootloader) Failed to flash partition logo | FAILED (remote failure)" and now it has only the "AP fastboot flash mode", no system and no recovery.
Some more info:
- My bootloader is unlocked;
- I can't boot any recovery using fastboot boot command, I got the error "Incomplete boot image for booting" (cwm,twrp, stock)
- My partitions are "raw" I suspect this is the main problem
- I've tried using windows and osx
- I've tried using fastboot and mfastboot
- I'm not able to use RSD lite, it' doesn't recognize my device
- I've tried a lot of stock firmware, no difference
Please help me, there is anything else to try? Is my phone dead (maybe emmc failure)?
Here is the output of fastboot getvar all:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D223XTZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: 233A12050F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 353321068993768
(bootloader) meid:
(bootloader) date: 09-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 15:41:58 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.46-28.1/1:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.26.1.titan_retde.
(bootloader) ro.build.version.full[1]: retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 13:23:41 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D223XTZ
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.085s
Click to expand...
Click to collapse
Any update on this?
I have the same problem. Anybody solved it?
The first error appears, when flashing bootloader (motoboot.img). Your bootloader might prevent to be flashed or maybe downgraded?
Try flashing fastboot files and skip the motoboot.img step. I would recommend to flash in terminal step by step, don' t use this script. Flash files according to the content of Stock Rom folder.
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
RED files should be in your folder, sometimes there are less system.img_sparsechunk files
Go to terminal or power shell (as admin) and flash step by step
I did everything
mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 99.341s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 104.596s
mfastboot.exe format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.025s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.983s
mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.327s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.717s
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.343s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.741s
mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.378s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.916s
mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.694s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.725s
mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.991s
mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.044s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.063s
mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.003s
mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
But i get everything FAILED
Mayby i have problem with emmc?
please nothing solution? ita a hardware problem? not software problem?
cmcshm said:
please nothing solution? ita a hardware problem? not software problem?
Click to expand...
Click to collapse
If you connect the device to your PC as what is it shown? If not in Windows explorer in the control panel/device manager?
Sent from my Moto G 2014 using XDA Labs
So I got this (tried twice and re-downloaded the factory image)
ScorpioPro:shamu-MPZ44Q markbyrn$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing 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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.603s]
finished. total time: 0.723s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67556 KB)...
OKAY [ 2.116s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.954s]
finished. total time: 3.070s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(2641,0xa08c01d4) malloc: *** mach_vm_map(size=1981542400) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1979559444 bytes
error: update package missing system.img
ScorpioPro:shamu-MPZ44Q markbyrn$ fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
markbyrn said:
So I got this (tried twice and re-downloaded the factory image)
ScorpioPro:shamu-MPZ44Q markbyrn$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing 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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.603s]
finished. total time: 0.723s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67556 KB)...
OKAY [ 2.116s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.954s]
finished. total time: 3.070s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(2641,0xa08c01d4) malloc: *** mach_vm_map(size=1981542400) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1979559444 bytes
error: update package missing system.img
ScorpioPro:shamu-MPZ44Q markbyrn$ fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
Click to expand...
Click to collapse
Don't use flash-all. Flash the images separately.
Evolution_Tech said:
Don't use flash-all. Flash the images separately.
Click to expand...
Click to collapse
that worked:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
thanks
markbyrn said:
that worked:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
thanks
Click to expand...
Click to collapse
Flash-all hasn't worked since the L preview a year ago
Hello everbody
A a year ago I tried to install a stock rom on my XT1072, but accidentally used an XT1068 rom. When I used "mfastboot getvar all" my phone got recognized as a TITAN instead of a THEA. I managed to install Lineage, but now my phone is stuck and restarts after a few seconds while showing the "Warning Bootloader Unlocked" message.
I tried to flash the latest version of Lineage "lineage-14.1-20170728-nightly-thea" but it failed and the screen displayed the following message.
Updater process ended with ERROR: 7
Erorr installing Zip file 'sdcard1/lineage-14.1-20170728-nightly-thea-signed.zip'
Updating partition details. . .
Failed to mount '/data' (Invalid argument
. . .done
I googled this error and it appears that my device is incompatible with the OS. I think it's because of the mismatching info I highlighted in the seconds hidden part.
After this, I tried to install this (https://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075) stock rom, but most of the commands failed
C:\XT1072 - 6.0 Stock Rom>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.040s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.381s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error
C:\XT1072 - 6.0 Stock Rom>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.074s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.196s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.402s]
writing 'boot'...
OKAY [ 0.389s]
finished. total time: 0.800s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.403s]
finished. total time: 0.809s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256869 KB)...
OKAY [ 13.664s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.789s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257163 KB)...
OKAY [ 11.165s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.290s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261045 KB)...
OKAY [ 13.967s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 14.045s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (248543 KB)...
OKAY [ 13.439s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.501s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (83796 KB)...
OKAY [ 4.510s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.541s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60992 KB)...
OKAY [ 2.558s]
writing 'modem'...
OKAY [ 2.070s]
finished. total time: 4.637s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.027s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (320 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 0.213s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.166s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.108s]
finished. total time: 1.281s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.139s]
finished. total time: 0.142s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.463s]
finished. total time: 0.465s
All of the system.img_sparsechunk failed with an "Image is too large" message and gpt.bin failed with "version downgraded for primary_gpt". After this I did "mfastboot getvar all" after I noticed that the bootloader version changed from 48.21 to 48.22. The phone is now recognized as a THEA again, but some parts are still labeled TITAN instead of THEA
C:\XT1072 - 6.0 Stock Rom>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4822
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C22D9DG
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: DDF97E0215000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353310062384405
(bootloader) meid:
(bootloader) date: 07-03-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Aug 23 22:51:53 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.99-16/10:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retde
(bootloader) ro.build.version.full[1]: .retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.22-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.22-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.22-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.22-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.22-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C22D9DG
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.128s
Is there any way to fix my phone and install the Stock or Lineage Rom? Thanks for all kinds of advice or suggestions
I've just flash my nexus 6 back to factory image (the newest one) for an hour. When I go to Setting > About phone to check my Phone status, i see my IMEI is changed to 0. I also check by calling keyboard *#06#, it's still 0. So, I decide to restart to Bootloader > Barcode and lucky that all status is ok . I don't know what happened during it's being flashed . Here is output:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) flashing 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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.668s]
finished. total time: 0.807s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.067s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.629s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.615s]
finished. total time: 5.255s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.012s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-72.03
Baseband Version.....: D4.01-9625-05.45+FSG-9625-02.117
Serial Number........: ZX1G******
--------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.005s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (8505 KB)...
OKAY [ 0.273s]
writing 'boot'...
OKAY [ 0.158s]
sending 'recovery' (13895 KB)...
OKAY [ 0.457s]
writing 'recovery'...
OKAY [ 0.213s]
sending sparse 'system' 1/4 (522512 KB)...
OKAY [ 28.436s]
writing 'system' 1/4...
OKAY [ 7.450s]
sending sparse 'system' 2/4 (517601 KB)...
OKAY [ 27.651s]
writing 'system' 2/4...
OKAY [ 7.081s]
sending sparse 'system' 3/4 (508949 KB)...
OKAY [ 26.705s]
writing 'system' 3/4...
OKAY [ 7.078s]
sending sparse 'system' 4/4 (32756 KB)...
OKAY [ 1.364s]
writing 'system' 4/4...
OKAY [ 0.422s]
erasing 'userdata'...
OKAY [ 1.666s]
sending 'userdata' (141063 KB)...
OKAY [ 4.468s]
writing 'userdata'...
OKAY [ 3.721s]
erasing 'cache'...
OKAY [ 0.038s]
sending 'cache' (6248 KB)...
OKAY [ 0.201s]
writing 'cache'...
OKAY [ 0.131s]
rebooting...
finished. total time: 117.702s
Press any key to exit...
Can you guys help me for recover my IMEI in setting or we can call that is on Android system. Thanks for read.
p/s: Everything work perfectly included LTE and Network service, there is only 1 problem is IMEI 0. Sorry if my English is too bad
I'd get in touch with Google support. Did you buy the phone from them?
Also, I think any discussion of changing IMEI numbers is prohibited on this forum.
It is my old phone, i used it an year ago. After that, i buy a new phone, but i sold it yesterday, and bring Nexus 6 back to use. I upgrade the android from 6.0.1 to 7.1.1 and it happened.