BTW, I was noticing in the u-boot usage doc that the write command automatically skips bad blocks. That would explain what we're seeing with those partial firmware writes on the affected boxes. If the same "bad blocks" are always skipped, they might retain their original contents from the factory firmware. Then only reflashing the original firmware would restore their integrity.
Code:
gxm_q20x u-boot Usage:
store store init flag
store read name addr off|partition size
read 'size' bytes starting at offset 'off'
to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
write 'size' bytes starting at offset 'off'
to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
write uboot to the boot device
store erase boot/data:
erase the area which is uboot or data
store erase partition <partition_name>:
erase the area which partition in u-boot
store erase dtb
store erase key
store disprotect key
store rom_protect on/off
store scrub off|partition size
scrub the area from offset and size
store dtb iread/read/write addr <size>
read/write dtb, size is optional
store key read/write addr <size>
read/write key, size is optional
store mbr addr
update mbr/partition table by dtb
.....is there a extra app to for mirroring? i have a Samsung A3 2016 with Marshmallow.gif "Bacon Dance")
Comment