[Android Software/Hacking General [Developers Only]] Savrik:
Hi! I continue to work with the phone.

Now I have two devices Motorola Admiral, one fully working, and the second was the donor (since the brick itself - on the Motorola logo is not loaded). Online firmware on it is not present, so carefully study the working staff - I hope to restore the "brick."

So, what was done:

1. Defined sections (on working device):

cat /proc/partitions
major minor #blocks name alias
179 0 3864576 mmcblk0
179 1 512 mmcblk0p1 p1
179 2 500 mmcblk0p2 p2
179 3 1500 mmcblk0p3 p3
179 4 1 mmcblk0p4 p4
179 5 65024 mmcblk0p5 p5
179 6 47000 mmcblk0p6 fat
179 7 1024 mmcblk0p7 appsbl
179 8 3072 mmcblk0p8 modem_bkp
179 9 7000 mmcblk0p9 adsp
179 10 3072 mmcblk0p10 modem_st1
179 11 3072 mmcblk0p11 modem_st2
179 12 768 mmcblk0p12 hob
179 13 4096 mmcblk0p13 pds
179 14 512 mmcblk0p14 dev_tree
179 15 5120 mmcblk0p15 apps
179 16 460800 mmcblk0p16 system
179 17 1055744 mmcblk0p17 userdata
179 18 406528 mmcblk0p18 cache
179 19 7168 mmcblk0p19 recovery
179 20 512 mmcblk0p20 misc
179 21 1024 mmcblk0p21 logo
179 22 2048 mmcblk0p22 kpanic
179 23 20480 mmcblk0p23 cdrom
179 24 2048 mmcblk0p24 bpanic
179 25 1373184 mmcblk0p25 sdcard
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1

2. Made a backup via adb (on working device, write files to external SDCARD):

dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard-ext/recovery/pds_block13.ext3
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard-ext/recovery/boot_apps_block15.img
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard-ext/recovery/system_block16.ext3
dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard-ext/recovery/userdata_block17.ext3
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard-ext/recovery/cache_block18.ext3
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard-ext/recovery/recovery_block19.img

3. "Brick" has translated into fastboot, it's OK

4. "Brick" accept fastboot commands, but when trying to write system.ext3 an error (on different versions of fastboot different errors):

These two versions immediately return errors:

C:\ADB\NEW\recovery>fastboot flash system system.ext3
sending 'system' (460800 KB)...
FAILED (remote: ERROR: 0000000E 000004B6)
finished. total time: 0.006s

C:\ADB\NEW\recovery>mfastboot flash system system.ext3
sending 'system' (460800 KB)...
FAILED (remote: ERROR: 0000000E 000004B6)
finished. total time: 0.001s

This version sends differrent file size and then after many minutes an error:

C:\ADB\NEW\recovery>moto-fastboot flash system system.ext3
sending 'system' (262144 KB)... OKAY [ 33.650s]
writing 'system'... FAILED (status read failed (Too many links))

Here, when you send the whole file at once an error when trying to send chunks of 8MB gives another error and the phone screen falls message Err: 0x000A:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe flash system c:\adb
\new\recovery\system.ext3
sending 'system' (460800 KB)...
FAILED (remote: ERROR: 0000000E 000004B6)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe -S 8M flash system
c:\adb\new\recovery\system.ext3
Invalid sparse file format at header magi
sending sparse 'system' (8180 KB)...
OKAY [ 0.765s]
writing 'system'...
FAILED (remote: ERROR: 00000002 0000026A)
finished. total time: 0.872s

When lights logo, sometimes the phone a short time (a few seconds, on device manager windows) is put ADB (I still can not understand how this happens).

Can anybody tell me why I can not burn the image via fastboot?