Gigabeat F firmware hacking information

[samamanjaro]

When I open fwupdecrypt.exe it plays a system beep that closes, I caught a screenshot of when it was closingand it said nothing about errors;

Gigabeat F/X Flash image enctiptor/decryptor tool
Copyright (c) shoora@gmail.com
Usage: fwupDecrypt [-e] file_in [file_out]
Options:
-e - encode

[elborak]

It is a command line tool.  You have to run it from a command window, not the GUI.

[samamanjaro]

God, I feel like an idiot now!

Thanks!

[Mad Cow]

Just a little bug report, I noticed that the power button delay doesn't change when it's charging (When the power plug animation plays)

[samamanjaro]

Damn, something screwy happened, I replaced the system firmware and placed update into the root dictionary, So I rebooted the Gigabeat and it goes to a white screen, then the old loading clock symbol come up, then a black screen with the text

Firmware updated
PUSH POWER BUTTON.

Then it reboots and the same thing happens.

Any help?

[shoora]

Damn, something screwy happened, I replaced the system firmware and placed update into the root dictionary, So I rebooted the Gigabeat and it goes to a white screen, then the old loading clock symbol come up, then a black screen with the text

Firmware updated
PUSH POWER BUTTON.

Then it reboots and the same thing happens.

Any help?

Look at http://www.rockbox.org/twiki/bin/view/Main/GigabeatFXPort section  Gigabeat Recovery Procedures.
possibly update script just can not find original firmware file. Because, first thing this script does is replaces images for firmware update with normal firmware files.

[samamanjaro]

Ok, recovered it!

Yours, Sam.

[johnson4]

Just a little bug report, I noticed that the power button delay doesn't change when it's charging (When the power plug animation plays)

Is this bug still out there or has it been overcome?

[Mad Cow]

Just a little bug report, I noticed that the power button delay doesn't change when it's charging (When the power plug animation plays)

Is this bug still out there or has it been overcome?

I'm guessing not since nobody has posted here for a while.

[themrcul]

Hi everyone.
I'm a new rockbox user and I love it.
I recently upgraded my player from an iaudio m5 to a gigabeat x30.
I also just stumbled on this thread, and was really excited because I wanted to change the official firmware's splash screen to something else.
I tried to use the programs linked to on the first page of this thread.

I'd like to ask for some help because I was unsuccessful in changing the splash screen.
When I viewed the hd-graphic+crc.bin file with the gigabeatbmpview  program I couldn't find the splash screen image. The only full screen images were a green floral design, my x30 has a pink coloured (rainbow like?) design. There were three images that only showed gibberish, one 167x1, another 3072x1 and the other one was 1000x1 (or thereabouts).
All the other bin files in the update directory wouldn't load until I decrypted them, but when I loaded the decrypted versions they only showed gibberish as well. Decrypting the hd-graphic+crc.bin file made no difference to it.

So I don't know how to change the splash screen, because I can't find the original image to replace it with!
Can someone please help me with this?
Thanks!

--

edit:
I tried patching the files with the quicker turn on button and the turn on when insert power cable, and it asked me if I wanted a new time stamp, so I said yes for both, and then it told me the CRC was invalid, would I like to fix?, so I said yes (for both). Then I tried copying the update directory with the new firmware files (replacing the old ones) and tried switching on my Gigabeat X.
It started up, and loaded a little bit, then said "Can Not Update", and restarted, trying to update again, and failing each time, in a cycle. Holding Menu when I switched it on didn't work, and you can't open gigabeat X's without running the risk of breaking something, so I got it replaced for a new one at the store. I won't try patching it again until I know exactly how to do it without stuffing it up.

Could someone who's done it before please explain to me:

How to find the splash screen in the update files and replace it with something else. (Do I have to decrypt a file, if so, which one?)
How to apply the patches (do I ignore the time stamp and crc warnings? Do I decrypt the patches first, or just patch the encrypted ones?)

Thankyou.

[Mad Cow]

This is for the F-series firmware. The X-series are a bit different, so they probably have a different firmware, or they use different parts of the same firmware. Either way there's nothing you can do unless you know as much about the firmware(s) as shoora.

[Job Van Dam]

Okay I'm a little apprehensive here because I edited the bootsplash properly, uploaded it to the Gigabeat but got a system error which forced me to do the Gigabeat Recovery Procedure (something I don't want to do again). Weird thing is the image I made is currently the bootsplash...
I really would like this to work so I have a few questions:

1) Where does the update folder go exactly?
I originally placed it in the root, I think, but it seems like it goes in the GBSYSTEM folder.

2) Do I just copy-paste the update folder as is (according to gigabeatF_firmware_hacks_V3.zip), along with the edited hd-graphic+crc and the rest of those other files?
Or do I just have to copy-paste the update folder with only the edited hd-graphic+crc inside?

Thank you.

[Mad Cow]

What I did was place the update folder in the root with all the files intact. It didn't update the first time, but after a restart and a long time waiting it updated with a custom bootsplash and a lower power button holding time.

[Job Van Dam]

What I did was place the update folder in the root with all the files intact. It didn't update the first time, but after a restart and a long time waiting it updated with a custom bootsplash and a lower power button holding time.

Are you absolutely certain? When I did that I got a system error and had to open up my Gigabeat to fix it.

[Mad Cow]

Actually, no. But I do remember that it didn't work on the first try, I might have had to open it, but it did update properly eventually.