Low level diagnostics - Moto G6 Questions & Answers

Hi guys and possibly girls...(?)
Well as the title says i'm looking for some kind of tool that lets me discard hardware problems on my xt1925-1 moto G6.
The problem I'm having is that one day stopped booting to android. It was my brother's phone and asked me to fix it since i'm a programmer and a geek I had some experience flashing roms. Well the phone behaves really weird it boots to fastboot and I can't use any option. Almost every time tooks like 20 seconds to boot and the info in the phone is corrupted it shows "product variant: ali 000000000000" instead of the model xt1925 etc etc... and the imei its 00's too as well of the baseband and SKU. when I try to flash the very first command I try fails:
fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.032s
Click to expand...
Click to collapse
And every flash command and erase command gives me the "(bootloader) Invalid partition name".
The partition gpt.bin gives "Preflash validation failed"
I'll copy the text at the end of the post.
Well the funny thing is that some "sadly few" times boots in less than 5 seconds and the info isn't corrupted. The commands works OK, for a short time, didn't let me finish flashing system, it hangs for a while and fails then boots bad again. Someone told me that the imei and other information shows 0's when de partition table isn't present or is corrupted. This behavior lend me to think that is some kind of Hardware problem in the ROM that sometimes is accessible and sometimes not?.
And i'm looking for a low level diagnose tool that can be run on the pc via USB to tell me if there is some kind of hardware malfunction. I searched on google but didn't found anything please HELP!.
This is the results when I try to flash the stock firmware when the phone is "corrupted":
fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.001s
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.075s
fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.353s
fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62672 KB)...
OKAY [ 1.527s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 1.536s
fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.223s]
writing 'fsg'...
(bootloader) Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.230s
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.037s
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.422s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.447s
fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.069s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.092s
fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.612s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.635s
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (22628 KB)...
OKAY [ 0.603s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.631s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 6.313s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.335s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.464s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.486s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.027s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.048s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.444s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.463s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.419s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.442s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.468s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.477s
fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (261193 KB)...
OKAY [ 6.411s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.433s
fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.454s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.461s
fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.446s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.478s
fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (187636 KB)...
OKAY [ 4.657s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 4.679s
fastboot flash vendor vendor.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'vendor' (253727 KB)...
OKAY [ 6.229s]
writing 'vendor'...
(bootloader) Invalid partition name vendor
FAILED (remote failure)
finished. total time: 6.269s
fastboot flash vendor vendor.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'vendor' (196061 KB)...
OKAY [ 4.847s]
writing 'vendor'...
(bootloader) Invalid partition name vendor
FAILED (remote failure)
finished. total time: 4.868s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (153177 KB)...
OKAY [ 3.787s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 3.797s
fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.036s
fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.018s
fastboot reboot
rebooting...
finished. total time: 0.017s
Click to expand...
Click to collapse
bye

Some follow up...
I did manage to flash the stock ROM but when it rebooted went to fastboot again because it didn't find the boot partition. The process of flashing went .OKAY. on all the steps. This was when It booted to the "GOOD" fastboot the one that lets me use commands. I can tell the difference because it has a little android with the chest opened and more information:
Well I'm trying to post an image but failed with 2 different file host... -.-
I'll just type the text here:
AP Fasboot Flash Mode (Secure)
BL: MBM-2.1-ali_retail-c999d61-190930
Baseband: M450_21.29.10.88R ALI_LATAM_CUST
Product/Variant: ali XT1925-1 32GB PVT2
Serial Number: ZY322SLP2N
CPU: SDM450
.
.
.
Click to expand...
Click to collapse
And the "BAD" fastboot looks like this, and doesn't have the android and the text of the options are just plain red/green/whit colored text(the other shows the text in a globe). And this is what it shows:
AP Fasboot Flash Mode (Secure)
BL: MBM-2.1-ali_retail-c999d61-190930
Baseband:
Product/Variant: ali 000000000000000 32GB PVT2
Serial Number: 3a9ff2d0
CPU: SDM450
.
.
.
Click to expand...
Click to collapse
bye

facurdoy said:
Algunos siguen ...
Me las arreglé para actualizar la ROM estándar, pero cuando se reinició, volví a arrancar rápido porque no encontró la partición de arranque. El proceso de flasheo fue .OKAY. en todos los escalones. Fue entonces cuando arrancó con el fastboot "BUENO" el que me permite usar comandos. Puedo notar la diferencia porque tiene un pequeño androide con el cofre abierto y más información:
Bueno, estoy tratando de publicar una imagen pero fallé con 2 hosts de archivos diferentes ... -.-
Escribiré el texto aquí:
Y el fastboot "MALO" se ve así, y no tiene Android y el texto de las opciones es simplemente rojo / verde / con texto de color (el otro muestra el texto en un globo). Y esto es lo que muestra:
adiós
Click to expand...
Click to collapse
Hola, a mí me está pasando lo mismo que a ti al principio. ¿Puedes decirme cómo lo resolviste al menos para que aparezca el fastboot "BUENO", que me permite usar comandos. Entonces, para poder notar la diferencia del androide con el cofre abierto

Related

[Q] [Help] AT&T flashed with Rogers boot 30.B4

So I screwed up. I figured that I wouldn't update the boot loader and I should be good. Let me back up.
I started off with a locked and locked AT&T MotoX running 4.4. I got the Rogers 4.4.2 firmware figuring that I can have it working if I avoid the modem etc etc. In the back of my mind I was thinking locked bootloader, everything will fail.
I flashed the partition... it worked. ok, Let's avoid the boot loader too, just in case. Flashed the logo, that worked. Flashed the boot.img, failed. Flashed motoboot.img, passed. Then I tried to continue but all failed as you can imagine.
I was prepared fro that, so I went back to the folder with the AT&T rom and trying to flash them.... oh no. Oh dear. downgrade failed. I'm locked out! I just made a rookie mistake.
Help? I guess I want to know if there is anything I can do, other than waiting on AT&T to release a version with the 30.B4 bootloader....
So you flashed gpt.bin and motoboot.img and your bootloader is locked? Have you restarted your phone yet?
It did restart but only sits in the boot loader
Sent from my Nexus 5 using Tapatalk
OK, waiting for the full AT&T 4.4.2 flash is probably the safest option.
If you're feeling brave keep reading(I am not responsible if your phone turns into a pretty paperweight)
You can try flashing the AT&T 4.4 files one at a time, the gpt.bin will fail for sure with the downgraded version error. If the files do flash you will have the combo which has the potential to brick - older firmware with a newer bootloader. The phone should work though.
Taking the OTA update from 4.4 to 4.4.2 when released will brick it!!! However I believe you could then manually flash the full 4.4.2 file and it would be OK and you'd be back to a "normal" AT&T phone.
Well, nothing flashes actually. Everything gives the following:
Partition (x) Security Version Downgrade
bidyut said:
Well, nothing flashes actually. Everything gives the following:
Partition (x) Security Version Downgrade
Click to expand...
Click to collapse
Not even the system IMG ?
Sent on my Gummy running Lenoto X
System fails too. Here's the log of me trying them all:
Code:
$ ls -l
total 1783232
[email protected] 1 skhan staff 1757 Nov 14 14:01 ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml
[email protected] 1 skhan staff 55029760 Nov 13 00:58 NON-HLOS.bin
[email protected] 1 skhan staff 10485760 Nov 13 00:58 boot.img
[email protected] 1 skhan staff 1263616 Nov 13 00:58 fsg.mbn
[email protected] 1 skhan staff 32768 Nov 13 00:58 gpt.bin
[email protected] 1 skhan staff 634418 Nov 13 00:58 logo.bin
[email protected] 1 skhan staff 1643008 Nov 13 00:58 motoboot.img
[email protected] 1 skhan staff 10485760 Nov 13 00:58 recovery.img
[email protected] 1 skhan staff 833428668 Nov 13 00:58 system.img
$ fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.362s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.612s
$ fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.261s
$ fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'system' (777436 KB)...
OKAY [ 49.232s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.853s
$
bidyut said:
System fails too. Here's the log of me trying them all:
Code:
$ ls -l
total 1783232
[email protected] 1 skhan staff 1757 Nov 14 14:01 ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml
[email protected] 1 skhan staff 55029760 Nov 13 00:58 NON-HLOS.bin
[email protected] 1 skhan staff 10485760 Nov 13 00:58 boot.img
[email protected] 1 skhan staff 1263616 Nov 13 00:58 fsg.mbn
[email protected] 1 skhan staff 32768 Nov 13 00:58 gpt.bin
[email protected] 1 skhan staff 634418 Nov 13 00:58 logo.bin
[email protected] 1 skhan staff 1643008 Nov 13 00:58 motoboot.img
[email protected] 1 skhan staff 10485760 Nov 13 00:58 recovery.img
[email protected] 1 skhan staff 833428668 Nov 13 00:58 system.img
$ fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.362s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.612s
$ fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.261s
$ fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'system' (777436 KB)...
OKAY [ 49.232s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.853s
$
Click to expand...
Click to collapse
Did you manually flash it? Try mfastboot
Sent on my Gummy running Lenoto X
flashallthetime said:
Did you manually flash it? Try mfastboot
Click to expand...
Click to collapse
Yes. Manually flashing. Just tried it with mfastboot v2.
Code:
$ ../osx-fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ ../osx-fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.365s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.615s
$ ../osx-fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ ../osx-fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.963s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.163s
$ ../osx-fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.726s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.716s
bidyut said:
Yes. Manually flashing. Just tried it with mfastboot v2.
Code:
$ ../osx-fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ ../osx-fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.365s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.615s
$ ../osx-fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ ../osx-fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.963s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.163s
$ ../osx-fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.726s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.716s
Click to expand...
Click to collapse
Well you aren't hard bricked or soft bricked, I think we will call this f---ed up bricked. Man you're in between a rock and a hard place. Can you take it back?
Did you flash the system from your original ROM?
I don't know I'd its worth hard bricking it and trying the moto x resurrection method? Anyone else have a opinion?
Sent on my Gummy running Lenoto X
If nothing will flash then I see no options at all other then waiting for the AT&T 4.4.2 full build or having it replaced. Even then you gotta hope the AT&T build will flash properly when it is released.
It is definitely f-ed up. The only times I miss unlocked bootloader.
bidyut said:
It is definitely f-ed up. The only times I miss unlocked bootloader.
Click to expand...
Click to collapse
We already know that, unfortunately you found out the hard way. Like Steve x said, what for the 4.4.2 firmware for your carrier
Sent on my Gummy running Lenoto X
Well thanks for the help guys. At least now I have confirmation for what I knew last night.
Follow up question, any way to get the phone into an ADB accessible state that you know off? Would have been nice to get some files off the phone.
You are going to have to wait for the full 4.4.2 AT&T FXZ. Your mistake was flashing motoboot.IMG and gpt.bin. Motoboot is the bootloader and gpt.bin will define the partitions on the device. The 4.4.2 bootloader doesn't let you downgrade and the partitions may have been altered in 4.4.2.
Sent from my Moto X on KitKat
Yeah, my mistake was thinking that even those won't work.

Can´t install stock firmware or leave fastboot.

Hello,
last Christmas I bought two Moto G 2014 and they were working fine until Friday.
One has "died", or so it seems. It was showing the logo of android with red triangle, something usual. I tried to do a wipe / factory reset, but it´s impossible because I can´t get past the fastboot screen. If I click on "Factory" the screen turns black and I can´t do nothing, only hard reset and back to fastboot screen again.
I tried to re-install the firmware so many times and following other posts on the forum, but there is no way. All FAILED, as you can see here:
FIRMWARE Auto Restore Script by Gary J Wright a.k.a Reefuge
MOTO G 2nd GEN Lollipop 5.0.2 FIRMWARE Flasher
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Presione una tecla para continuar . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 3.135s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 0.330s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.004s]
finished. total time: 3.474s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.337s]
finished. total time: 0.386s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.129s]
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.240s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.057s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.075s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.372s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.395s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.385s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.413s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.333s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.402s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.306s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.401s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.314s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.388s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.440s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.476s
target max-sparse-size: 256MB
sending 'system' (44584 KB)...
OKAY [ 6.479s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.510s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.634s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.661s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.077s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.103s
ERASING CACHE ......
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
ERASING USERDATA.......
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
DONE!.........PRESS ANY KEY TO REBOOT
Click to expand...
Click to collapse
My phone model is:
22.21.28.titan_retaildsds.retaildsdsall.en.03
I´ve tried different firmware versions (always XT1068), but same problems.
And besides, I can not activate the "debug mode" because I can´t pass the fastboot screen.
I have Windows 8 64 bits, tried in different USB ports and in a computer with XP too.
Any ideas?
Thank you in advance.
The model is XT1068, Retaildsds.
I think its a edad nand,
Is your bootloader
fburgos said:
I think its a edad nand,
Is your bootloader
Click to expand...
Click to collapse
Do you mean it´s an outdated version or something similar?
Or drivers? :/ I think I have all of them.
My bootloader is 48.82
I´ve tried with a computer with Windows XP, but the same errors again
I´ll try with a W7 computer...
I'm really sorry I didn't finish my previous post,
I think it's a dead nand, is it your bootloader unlocked?
That might prevent you from installing any firmware I'm really not an expert just trying to help a little
Well I used the script on win 7 .. Worked fine for me .. Give it a try on win 7

Return to stock issues

Hello all,
I am attempting to reset my Nexus 6 XT1103 and I think I've tried everything.
I tried to run "flash-all.bat" and command shows:
Code:
C:\Users\Default.Default-PC>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.127s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.145s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (48360 KB)...
OKAY [ 1.595s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.616s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2004185752 bytes
error: update package missing system.img
Press any key to exit...
When I try and run a single file piece by piece it shows:
Code:
C:\Users\Default.Default-PC>fastboot flash bootloader bootloader-angler-angler-02.01.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.135s
I am running Windows 10 and all drivers up and operational. Has anyone ran into this before? I searched the forums but was unable to find the answer I needed.
Thanks in advance for your assistance!
Angler is code name for Nexus 6P. You are trying to flash wrong image.
https://developers.google.com/android/nexus/images#shamu
So I just happened to buy the 6P. Didn't even realize I was clicking it. Let's pretend this post was never here...
Sent from my Nexus 6P using Tapatalk

Moto x returning to stock

I Have Tried Everything But I Keep Getting This Failure In Flashing Partition . My Dad Is Getting Really Upset Reply Fast
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.248s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.117s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.379s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.215s]
finished. total time: 5.605s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.945s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.156s
G:\Moto X>mfastboot flash system system.img
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.674s]
writing 'modem'...
OKAY [ 3.582s]
finished. total time: 7.275s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.462s]
finished. total time: 0.473s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.488s]
finished. total time: 0.494s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.832s]
finished. total time: 1.183s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.019s]
finished. total time: 1.027s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.792s]
finished. total time: 0.797s
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.328s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.344s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.453s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.546s]
finished. total time: 6.006s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.142s
G:\Moto X>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394581432 bytes
error: cannot load 'system.img': Not enough space
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.666s]
writing 'modem'...
OKAY [ 3.596s]
finished. total time: 7.293s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.469s]
finished. total time: 0.484s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.469s]
finished. total time: 0.469s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.829s]
finished. total time: 1.190s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.031s]
finished. total time: 1.047s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.797s]
finished. total time: 0.813s
G:\Moto X>
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
YedanyXD said:
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
Click to expand...
Click to collapse
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
xXAmartyAXx said:
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
Click to expand...
Click to collapse
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
YedanyXD said:
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
Click to expand...
Click to collapse
Boot loader unlocked
First tried to install kk accidentally then installed 5.1 by cmd but it is stuck in boot loader unlocked screen

Moto G5S Plus sanders 1802 in need of a mmcblk0 file ?

Hey guys, recently I hard bricked my sanders 1802 in way that everything I tried does not work.
After I flashed lineage 16.0, the fingerprint sensor and some other things were not working, then I tried downgrading it back to stock via fastboot, Sanders retail 8.1.
After that everthing went to hell. It got into bootloop. So i tried to restore it via Leonovo Moto Smart Assistant. Went back to bootloop and started showing some cache mount issues.
I tried over 10 different ROMs and every time it showed cache mout problems or ERROR 6, 7 and 1 in TWRP and sometimes kernel issues.
I've already tried flashing new kernels, tried every ERROR 6 and 7 solutions that are available online and nothing happens.
Right now I have it at the best shape possible, it has the latest TWRP installed (3.2.1 sanders r20), it does not show any cache nor kernel errors when I try to install a ROM, but it keeps giving me the ERROR 7 even when I delete the assert line on the updater-script file.
Searching the XDA foruns I found someone talking about getting a fresh start for the phone by flash the sdcard with mmcbk0.img. I'm not even sure if that's the right path to solve my problem, but I thought I give it a try since I have no idea what else to do.
I'm pretty noob on everything regarding android, just followed everything easily when it comes to tutorials.
Can someone please help me? Is the new mmcbk0.img file the right path or should I try somthing else? I talked to a "expert" guy here in my city and he said that the phone is gone and there's nothing I can do. Is it possible?
Have you tried TWRP 3.3
pradeeppk said:
Have you tried TWRP 3.3
Click to expand...
Click to collapse
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
voliveira92 said:
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
pradeeppk said:
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
Click to expand...
Click to collapse
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
voliveira92 said:
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
Click to expand...
Click to collapse
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
HTML:
pradeeppk said:
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
Click to expand...
Click to collapse
I'm pretty sure that I'm not missing anything.
I was able to flash Twrp 3.3.0 from this thread (https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-3-0-t3940378), but now it keeps giving me Error 7 and 'unable to mount system'.
Tried lineage and Havocs ROM. Tried altering the assert line again and no changes.
pradeeppk said:
Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there.
Click to expand...
Click to collapse
Wrong command format
voliveira92 said:
it gives me this error message:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
D302Thakur said:
Wrong command format
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
Click to expand...
Click to collapse
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
voliveira92 said:
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
Click to expand...
Click to collapse
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
pradeeppk said:
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
Click to expand...
Click to collapse
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
voliveira92 said:
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
Click to expand...
Click to collapse
Those are the lines that came with error. The phone went on a bootloop after clearing the cache and userdata.
platform-tools>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (504333 KB)...
OKAY [ 11.743s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.804s
platform-tools>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (495479 KB)...
OKAY [ 11.539s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 15.942s
platform-tools>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (65436 KB)...
OKAY [ 1.528s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.552s
platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (335882 KB)...
OKAY [ 7.802s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.841s
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
pradeeppk said:
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
Click to expand...
Click to collapse
Ok, so I repaired system file, formated data, cache and system and tried to flash from TWRP and fastboot.
On TWRP I got the same ERROR 7 as always (tried Pixel Experience and Havoc OS, as well stock firmware Sanders_NPS26.1):
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Tried again editing the assert line and the same ERROR 7 anyway.
And via fastboot (stock firmware) I got this and the phone went on bootloop after rebooting:
fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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 failure)
finished. total time: 0.073s
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.124s]
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.704s]
finished. total time: 0.828s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.163s
fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.419s]
finished. total time: 0.816s
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.511s]
finished. total time: 1.007s
fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.385s]
writing 'dsp'...
OKAY [ 0.286s]
finished. total time: 0.670s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 7.627s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.669s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 12.189s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.260s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 6.230s]
finished. total time: 18.391s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 7.196s]
finished. total time: 19.356s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 12.207s]
writing 'system'...
OKAY [ 6.143s]
finished. total time: 18.349s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 12.211s]
writing 'system'...
OKAY [ 6.929s]
finished. total time: 19.141s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 10.111s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.502s
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 1.758s]
writing 'modem'...
OKAY [ 1.088s]
finished. total time: 2.846s
fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 0.118s]
finished. total time: 0.178s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.018s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.334s]
finished. total time: 0.334s
fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot oem fb_mode_clear
...
OKAY [ 0.118s]
finished. total time: 0.118s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.185s
I have the option of switching the system file to another format on TWRP (EXT2, EXT3, EXT4, FAT, exFAT, F2Fs), could any of those help?
voliveira92 said:
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
D302Thakur said:
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Ok, so I tried the stock you recomended and used the codes you provided.
Here's what I got. Frozen at boot screen. Tried from -fastboot- and -minimal adb and fastboot-.
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
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 failure)
finished. total time: 0.057s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
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.519s]
finished. total time: 0.641s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71941 KB)...
OKAY [ 1.678s]
writing 'modem'...
OKAY [ 0.980s]
finished. total time: 2.658s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.071s]
writing 'fsg'...
OKAY [ 0.120s]
finished. total time: 0.191s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.382s]
writing 'dsp'...
OKAY [ 0.254s]
finished. total time: 0.637s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.150s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.396s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.357s]
finished. total time: 0.754s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.490s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.452s]
finished. total time: 0.942s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.097s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.099s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (249863 KB)...
OKAY [ 5.809s]
writing 'system'...
OKAY [ 2.935s]
finished. total time: 8.744s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (260323 KB)...
OKAY [ 6.091s]
writing 'system'...
OKAY [ 3.729s]
finished. total time: 9.820s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.105s]
writing 'system'...
OKAY [ 3.309s]
finished. total time: 9.414s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.098s]
writing 'system'...
OKAY [ 3.106s]
finished. total time: 9.203s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.097s]
writing 'system'...
OKAY [ 2.928s]
finished. total time: 9.025s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.104s]
writing 'system'...
OKAY [ 2.986s]
finished. total time: 9.090s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (255675 KB)...
OKAY [ 5.971s]
writing 'system'...
OKAY [ 3.487s]
finished. total time: 9.459s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (242629 KB)...
OKAY [ 5.647s]
writing 'system'...
OKAY [ 2.830s]
finished. total time: 8.478s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (239745 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.518s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.520s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135426 KB)...
OKAY [ 3.150s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.153s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.009s]
finished. total time: 0.009s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
voliveira92 said:
fastboot flash system system.img_sparsechunk.0
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.9
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.10
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash oem oem.img
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
D302Thakur said:
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
Click to expand...
Click to collapse
Brazil, model XT1802
voliveira92 said:
Brazil, model XT1802
Click to expand...
Click to collapse
Can anyone please help me with this? I'm almost giving up on this device but I can't accept that there's nothing else I can try.

Categories

Resources