No, a backup made from a working box is not a problem.
We suspect (but have not proven it, nor did we receive feedback from VU+) that a boot image in the zip, larger than the boot partition, causes the issue, because the bootloader doesn't seem to check the size before it flashes.
We only find it weird that of all the users that have flashed 6.0-rc on their 1st generation VU+, only two users complained sofar. So it is still an option that clones are involved, although they stated that was not the case.
Exactly, I insist, the vusolo was bought in DE by a known online specialized shop.
I do have the receipt. I did open it
Proof is that I did flash the vusolo v2 bootloader and it did not brick...
Hey, I am developer, here the fault is mine: I was looking at the vusolo-6.0-rc since some weeks noticing the size was 78MB instead of 48 as the 4.0. Well, eventually I finally flashed it...
boot_cfe_auto.jffs2 │ 492│set 15 01:18│
kernel_cfe_auto.bin │3340453│set 15 01:18│
root_cfe_auto.jffs2 │ 82560K│set 15 01:18
I don't have it here but there is the output of cat /proc/mtd somewhere.
Any comment about partition boundaries is left to you :]
Cheers
A.A.
P.S. The uint was unused since the purchase of a duo2 so it is not big drama for me.