Sorry for replying to myself but I got it working again:
I stumbled over an old thread (
http://forums.rockbox.org/index.php/topic,29115.msg185581.html#msg185581) wich refers to unsolder a cable inside my device to force it into a special mode. Actually, my device already behaved like it was in this special mode. And, as it couldn't get worse (and I'm confident with linux), I gave the mentioned commands a try:
root@phenom2:~# dd if=/home/errorsmith/clip/clpzV010121.bin of=/dev/sdd
30720+0 blocks in
30720+0 blocks out
15728640 Bytes (16 MB) copied, 72,1622 s, 218 kB/s
root@phenom2:~#
After powercycling the device (holding power and menukey again) I was greeted with the sansa-flower wich was a big success for me! After some time I got a message, telling me that the fat is corrupted and I need to connect the device to a computer. I did this happily (using a windows machine for this). Windows told me that I need to format the removable device wich I did. After this last step, I ejected and unplugged my clipzip and it booted just fine :-)
So, what I've learned from this:
- under special circumstances the clipzip goes into the special mode without unsoldering cables and/or shortening pins (might been one of the button combinations I tried. I can document these in this thread if requested)
- the firmware file is an uncompressed plain "diskimage" wich can be dd'ed to the storage (losing any files previously stored on the device)
Open questions for me:
- why/how could the filesystem became so destroyed that only the bootloader was left?
- how can I prevent this from happening again?
- why jumped the clipzip into special mode without shorting the pins?
- bonusquestion: is it likely that installing rockbox on the device prevents this from happening again or should I get a new device for rockbox?
While my initial problem is solved, it would be nice if someone might have an answer for this questions
kind and happy regards,
errorsmith