System Error 00000010 on Gigabeat F60

[ej0rge]

Yeah there's a flash bootloader but you really don't want to play with it too much - not with the tools we have right now anyway.

The CD restore isn't going to do you any good because that's going to give you the v2.0 gbsystem, and you probably have the v3.0 flash image.

It could be that you have a japanese flash image and need a japanese gbsystem - which i've acquired from another friendly rockboxer. I'll send you a url where you can download it in a PM in a couple hours.

[Plerg]

Got your PM. Thanks.

I ran the installer, and installed Gigabeat Room 3, but when I go to update the firmware, I'm getting an error box "There is no drive that allows transfer of the application. Connect Gigabeat to the PC." Formatting doesn't help.

I've found a US version of the installer (I'm in the UK), and it is also giving me the same error.

The computer is detecting the Gigabeat, as Gigabeat Room loads every time I plug it in.

Update:

I took the battery out, trying to find any way to get it working again. I've got it plugged in by the power supply, and it seems to be working fine now.

I've just put the battery back in, without the power supply and it still seems to be running fine. Does anybody have any idea what the problem could have been? I'll buy a new battery anyway just to be on the safe side.

I also lifted the screen up, and the black plastic appears to have melted from the heat of the CPU. Is this a known problem, or will it become a problem?

Thanks for all the help guys. I feel bad for wasting your time on what seems to be a simple problem, but I really appreciate your help, especially ej0rge. I'll donate something to the project, and hopefully be able to add to the code when I get better at programming.

[ej0rge]

That's very interesting. Maybe a short in the battery was dragging the voltage down far enough that the drive can't spin up properly without external power?

As for the heat from the cpu - no, as far as I know that's pretty unusual. hopefully not the cause of your battery issue.

[Plerg]

I've ordered a new battery, so I'll take the old one apart and have a better look when it arrives. I'm hoping the screen is something I can just leave, as the only ones I can see are quite expensive.

[ej0rge]

I just hope the situation isn't that you've got a failure or short somewhere on the board that loads down the battery so far that the hard drive can't spin up properly.

I'd much prefer to hear that it's just a failure in the battery or the protection circuit on the battery.

[GodEater]

I've ordered a new battery, so I'll take the old one apart and have a better look when it arrives. I'm hoping the screen is something I can just leave, as the only ones I can see are quite expensive.

Slightly offtopic, but where did you order the battery from? I've been trying to keep an eye out for places to get spares from in the event that I need one eventually.

[ej0rge]

i buy cameron-sino batteries from this guy:

http://licketysplit.ca/

iirc there's a 1000mAh that fits the F directly, but i usually just go for the 1200mAh g4 ipod battery and shave down the plastic on the inside of the front panel.

[GodEater]

I thought there was some daughterboard on the Gigabeat's battery that didn't appear on iPod replacement batteries ?

[Plerg]

I've bought one of the iPod 4G batteries too, planning to do the Gigabeat battery upgrade.

http://www.rockbox.org/twiki/bin/view/Main/GigabeatBatteryUpgrade

I bought one of these, but I'd have bought one of the cameron-sino batteries if I'd seen them.

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&ssPageName=STRK:MEWNX:IT&item=370129823197

[ej0rge]

I thought there was some daughterboard on the Gigabeat's battery that didn't appear on iPod replacement batteries ?

Nah, it's just on the long edge instead of the short edge. The soldering work shown in the wiki is just to put the appropriate wiring on the battery - I swap the plastic around instead and leave the unused wire in the 3-pin connector folded out of the way.

I haven't actually seen a li-poly pack without a factory-attached protection circuit yet. Not in a DAP anyway.

[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.