Cowon J3: Trying to fix on Linux Mint with TCCtool, need instruction

[ormus]

Hello,

I'm not especially tech savvy but have reason to believe that someone here might be in a position to help me. I already sent a PM to linuxstb, but heard back so far.

Problem:

I managed to do something that caused the contents of my J3 storage to not show up at all on the player when I turn it on. My extra SD card does, fortunately, still work as normal, otherwise I'd be very troubled by this point.

I still get to see the contents of both when I plug the player into my computer. Seemingly randomly, the contents of the original storage toggles between being read-only and not.

Other symptoms of this are that some folders I deleted from the original part stayed in the wastebasket for ages before disappearing; they have now gone from the wastebasket but are still in the .Trash-1000 and . folders..

However when I try to delete them I'm unable to, even when the read only is off (Error when getting information for file '/media/adam/COWON J3/.Trash-1000/expunged/938689970/EtP [1983-1984-1985]': Input/output error)

Seems it's hard to reformat a FAT32 drive using Linux, which I understand would be one option.

But I gather that this ought to be possible using TCCtool that works on Linux, am just trying to find some instructions for the J3 which despite searching, I couldn't find on this forum.

Would be grateful for any advice.

[saratoga]

tcctool is a tool for uploading a firmware file onto a bricked player.  It basically lets you boot even if you screw up the firmware file.  From what you've said, you can already boot the player right?  I don't think tcctool is needed. 

[[Saint]]

It is actually incredibly trivial to format a partition as FAT32 in Linux, but honestly, I'm not certain that is the issue here.

The original firmware _should_ offer some form of onboard file system management, if I'm not mistaken (its been years since I've owned one of these), if it can't recover itself, it is unlikely (but not impossible) that anything else will have any more luck.

This sounds rather like defective hardware, but, file system issues can indeed manifest themselves in strange ways.


[Saint]