Third Party > Repairing and Upgrading Rockbox Capable Players
System Error 00000010 on Gigabeat F60
Plerg:
Turns out the one I ordered was a Cameron-Sino. Boots up fine, but I haven't ran it properly yet to see if it's fully working.
KuzuRanger:
Hi. (I know this thread is old, but it's very similar to my problem)
I've had my Gigabeat MEGX30 (japanese model) for probably 8-9 years and had Rockbox running on it fine the whole time. Without changing anything (firmware, other settings), recently I got some checksum error message which auto shuts down my gigabeat after 2 seconds. I followed the instructions on this site to reformat the gigabeat, which lead me to the "00000010 System Error" message, which was to be expected. However at this stage, I can no longer get my gigabeat to show up as a G:/ drive on my PC. Now I can't load up any other firmware or GBSYSTEM files. I've lost the CD and tried using a firmware installer, which runs fine, but then doesn't detect my gigabeat when plugged in. Same as the OP. "There is no drive that allows transfer of the application. Connect Gigabeat to the PC." I do see the USB connection symbol on my screen though.
Also similar to the OP, I am thinking there may be battery issues. I noticed for that last few years that the battery life was quite low. I can listen for a few days, but always have to charge up again within the week. (ie, after about 4-5 hours of use the battery level (via speech announcer thing on Rockbox) indicates it's already 50% or less. To my understanding this is well below the standard expectancy, but I put up with it because it didn't affect anything else. (till now...)
I am currently using the AC adapter to get power (battery removed) but still cannot get the PC to detect the gigabeat. Now instead of 00000010, I am getting a 00000001 System Error. Does anyone have any advice for me? Would greatly appreciate your help!
burkjavier:
(I replied in the other thread you had, not sure if you had seen that)
I have an F series and I know the error 10 fairly well, over the years. Usually it's a problematic HDD, or that there's is no HDD connectivity at all. Going on what you've written so far (checksum error out of the blue / tried the HDD trick to get access but no drive letter coming up), it's what I would personally zone in on. Plus the two most likely issues with a device like this over time will be 1) the battery and 2) the HDD. I think you've got issues with both, that's my guess.
That's no guarantee of course. It could be the mainboard, there's no way to know until parts are tested and eliminated as factors.
Navigation
[0] Message Index
[*] Previous page
Go to full version