Clip Zip probably bricked.

[lvrhs]

Hi, i tried to rockbox my zip. I done it, but when i removed from pc it still was running standart firmware. Then i tried to rockbox again, and now my zip doesnt even turn on.
Whats the problem. I was using automatic installation.

[saratoga]

You should give a lot more detail if you want help. But first I would hold power for one minute and try to reboot it.

[tent]

it happened to me as well when you rockbox it but having for accident the wrong destination drive selected (let's say the zip would be in drive h: but accidentaly you left drive d: selected) then when you reboot it it will brick in the booting up S logo.. so far I'm waiting for some hardware pin "last resort" unbrick procedure to show up...

[saratoga]

If you select the wrong drive the installer will simply do nothing to your player.

[tent]

well what happened to me is that I found on my "wrong" d: drive the content that should have been put on the sansa (stuff like .rockbox directory etc.), the sansa continued to work correctly until I rebootet it once and then it remained stuck in that situation I described. so far nothing helped to recover: holding any button for several minutes, even unsoldering the battery or connecting to usb like that while holding buttons, etc. as well as waiting months for battery to drain out.. again: my only possibility is to get some hint by somebody who did discovered the famous hardware pins that need to be shorted to recover other sansa drivers, so that maybe I can find them also on the zip and then eventually help the comunity with that information if it will succed. At the moment there appears to be nothing to lose, correct?

tent:wq

[saratoga]

If you haven't actually flashed anything to your player yet, the recovery procedure may or may not help you. Its for recovering from a bad flash that erased the disk. It won't fix a broken player in general. Since you never actually flashed anything I don't see why the flash memory would have been erased unless the chip died.

[tent]

Hello,
 why do you think I've never flashed the unit? It flashed for sure at least the bootloader, what failed was copying the content of filesystem to the flash since I found the content on the wrong drive afterwards. But what the fact is, after rebooting the sansa gets in such stuck situation where the "S" logo moves couple of times and then freezes. Whatever it is I belive my only chance is to try to get access to the flash and see what happens if I manually restore it's content. Otherwise I have impression that suggestions of everybody here is somethink like: "forget it and just thorw it away" like no further possibility is available. Eventually I have also a JTAG programmer, if that could be of any use I would be willing to try that as well if some instructions or hints are available for the clip zip.

tent:wq

[torne]

Flashing works by copying the new firmware file to the drive, and then when you disconnect the USB connection it detects the file and flashes itself. The rockbox installer cannot flash the player directly. So, if you never installed it to the right drive then it won't have flashed anything.

[[Saint]]

Is it under warranty still?

Your best bet, is to talk to SanDisk...since no Rockbox code ever actually touched the device, you would not have voided the warranty. It is rather a shame that such a length of time has passed, seeing the log of the installation and error logs from your machine may have helped, but that data has almost certainly been blown away by now. I rather suspect the only interesting logs would be from the host machine, all Rockbox Utility is likely to show is a "successful installation" - to the wrong disc altogether - but at least then there would be some clear evidence that Rockbox Utility never touched the device and didn't cause this issue.

The behaviour suggests the flash just...died.

Anyhoo...almost certainly too late now, so...yeah.

Talk to SanDisk, if you're under warranty still...great, if not, I'm really sorry but that is the limit of support that can be offered.

No one here is sitting on a recovery procedure for this device and keeping it to themselves, no one can give you that information because we simply just don't know it...we're just as in the dark as you are. You asked in the other thread how the AMS recovery was found, and, as far as I know it involved the complete destruction of at least one of each of the devices in question and following the traces on the board. There is no guarantee that the Clip Zip even has this "feature" (I am positive that it isn't deliberate) either.


[Saint]