Before doing something harmful...

[mcc01]

Hi,

(I am doing all this on Linux.)

due to crahses/hangs the internal flash of my Sansa Clip ZIP becomes corrupted.
Fsck repairs the the logical structure of the filesystem but it cannot repair files,
which FAT-parts get screwed. Therefore the filesystem may be logically repaired
but the data get lost.

Currently, the OF get stuck in "Refreshing your data".

1) Here:
http://forums.sandisk.com/t5/Sansa-Clip-Zip/Stuck-on-Refreshing-your-Media/td-p/323002
I found the advice to reformat the internal flash.

2) Only with the OF the above mentioned posting seems valid to me...or?

3) Am I able to install the OF - my Sansa Clip ZIP hangs with "Refreshing you data"

4) So I need to (temporaryly) uninstall rockbox.

5) I read, that uninstallation of rockbox is done by installing the original firmware.

6) To close the recursion: GOTO Line 2

Stack overflow?

What is the correct way to handle this

Thank you very much in advance for any help!
Best regards,
mcc

[Serenity]

That's bizarre.  The process of installing the original firmware should fix most corruption in the Sansa's memory. I bought my (second) Clip Zip on eBay cheaply, due to it exhibiting the same behaviour you describe (I assumed it was a corrupted MP3).  I was not concerned with rescuing any data, so be warned you will lose the data currently on your player. 

If you're not worried about losing your data, follow "Method 2" here: http://kb.sandisk.com/app/answers/detail/a_id/300/~/updating-the-sansa-clip-zip-%2F-clip%2B-%2F-clips-firmware

This should give you a fresh start with the original firmware. Plugging the Sansa directly into your computer and dumping the firmware file on it should bypass any sort of data refresh.

Once that's done, feel free to run Fsck on the player, just in case.

From there, see how the OF behaves for a while. If it works smoothly, install Rockbox & enjoy.

It sounds like you've probably thought of all this already, but this is the procedure that fixed my eBay machine.

[[Saint]]

The process of installing the original firmware should fix most corruption in the Sansa's memory.

By my understanding, this is not the case at all.


Anyway...

As I understand it, the problem here revolves around the solution requiring the device to be mounted using the original firmware...which fails to boot completely, and therefore fails to mount. See the cyclical dependency that makes this an issue now?

OP - if you have removable storage in the device at present, you may try to eject it and hope that this makes the amount of media on the device small enough that it is able to commit its database in the internal storage, and in turn, complete the boot process.


[Saint]