Rockbox Technical Forums
Support and General Use => Hardware => Topic started by: shoora on April 11, 2007, 08:12:32 PM
-
I have done some homework on Gigabeat F firmware.
So far:
1. Created program to decode/encode firmware images.
2. Created program to change bitmaps in flash image and modified my Splash screen.
3. Successfully flushed my Gigabeat with modified images.
4. Made patch power button for shorter wait before system starts bootup.
5. Made patch to start up Gigabeat immediately after external power plugged. Great for "Car adapter mode"! With this patch you can not shutdown player while external power connected - it will startup again :-)
I believe it's not impossible to write custom bootloader to load Rockbox image directly. I just don't care that much. Resume (see below) is lot more important!
Firmware utilities, flash listing (IDA 5.10), LCD init code. Will be continued...
http://rapidshare.com/users/VUBQPF
Updated Apr. 19 2007
- GigabeatBmpView: better recognition of bitmap files
- GigabeatBmpView: work only with RGB 24 bit files.
- You may want to change splash screen in "hd-graphic+crc.bin". Then use GigabeatBmpView.exe to vies and change bitmaps (F1 - help).
- You may be interested in changing f-hd-loader+crc.bin (loader and startup code). You can find couple of patches in directory /patches. If you want
BE EXTREMELY CAREFUL making you own patch! You can use provided IDA listing to find place to patch in firmware.
The GigabeatBmpView tool now can process encrypted files.
ote:
Please, use TAB key to switch between bitmaps in graphics file. In this way window sizes will be changed automatically with pixel precision.
WE DO NOT HAVE ANY PROCEDURE TO UNBRICK THE PLAYER.
I can confirm that couple patches from patches directory work and graphics safely be edited.
1. Use fwupDecrypt.exe to decrypt firmware files (hd-zboot-flprog-2440+CRC.bin, f-hd-loader+crc.bin,
hd-secure+crc.bin, hd-panic+crc.bin, hd-graphic+crc.bin) from directory \update (in archive \firmware_upgrade\update).
2. Do something manipulations with this binaries.
3. Reencode them using fwupDecrypt.exe with parameter -e.
4. Use package from /firmware_upgrade to update flash.
-
Wow, good work! What's the possibility of bricking the gigabeat with bootloader hacking? Is there any lower form of bootloader that handles USB? Maybe you can release some of this, because I would find the shorter power button holding very, very useful.
-
nice work shoora!
We still want to flash our own bootloader some day, but I was waiting for more info about the LCD driver IC so we can write our own LCD init code and actually know what we are doing (instead of just taking it from the OF)
Could you visit us in #rockbox to talk about it some more?
-
shoora,
I am really interested in this information. How are you doing your patches? Are you dumping the flash and running objdump or something similar? Currently I am really interested in getting a dump/disassembly of the flash - I just started looking at it tonight and Llorean pointed me to your post. I am interested in working toward a fully replaced bootloader, or at the least patching some of the checks in startup (I think the OF bootloader is interfering with the alarm wakeup, but I am not sure without a dump/disassembly).
-
Wow, good work! What's the possibility of bricking the gigabeat with bootloader hacking? Is there any lower form of bootloader that handles USB? Maybe you can release some of this, because I would find the shorter power button holding very, very useful.
I am pretty sure we can brick the device flashing buggy firmware.
I am not familiar with common practice of recovery from bad flash. But considering number of protection you have to pass before binary will be flashed, we are in danger zone.
I need some time to reorder my stuff for your convenience, and put at least some notes behalf my findings.
-
If a day, we can flash the bootloader, it will have a chance to unflash to put the original bootloader or firmware? I don't see the utily but when you return your player to Toshiba to change a piece or the battery...
-
If a day, we can flash the bootloader, it will have a chance to unflash to put the original bootloader or firmware? I don't see the utily but when you return your player to Toshiba to change a piece or the battery...
I can't see why you wouldn't be able to. But I think that your warranty will be over by the time you have to buy a new battery.
-
If a day, we can flash the bootloader, it will have a chance to unflash to put the original bootloader or firmware? I don't see the utily but when you return your player to Toshiba to change a piece or the battery...
Actually firmware is time stamped. So, you can revert original firmware only with new date. In order to do so you need to decode and then encode original firmware file.
This will only be necessary if you have changed changed your splash screen.
-
Actually firmware is time stamped. So, you can revert original firmware only with new date. In order to do so you need to decode and then encode original firmware file.
This will only be necessary if you have changed changed your splash screen.
If we have our own tool (like the iriver_flash plugin) this doesn't apply of course.
-
Actually firmware is time stamped. So, you can revert original firmware only with new date. In order to do so you need to decode and then encode original firmware file.
This will only be necessary if you have changed changed your splash screen.
If we have our own tool (like the iriver_flash plugin) this doesn't apply of course.
At this point we can...if we really need.
they use _open("/dev/from",_O_SHORT_LIVED|_O_RDWR/*0x1002*/);
Please look for fwup listing in forder
http://rapidshare.com/users/VUBQPF
-
Please look for fwup listing in forder
http://rapidshare.com/users/VUBQPF
Thank you for sharing this, I now have "Powerup on AC plugin" and "Shorted delay on POWER" on my gigabeat.
One thing I noticed was that encrypt.bat and decrypt.bat didn't handle f-hd-loader+crc.bin, so i added:
..\fwupDecrypt\fwupDecrypt.exe f-hd-loader+crc.bin f-hd-loader+crc.bin.decand
..\fwupDecrypt\fwupDecrypt.exe -e f-hd-loader+crc.bin.dec f-hd-loader+crc.bin respectively. Also is it required to de-/encrypt the other 4 files since only f-hd-loader+crc.bin.dec is being patched? I noticed the cycle didn't result in identical files.
Anyway. Everything worked fine. So thanks again.
-
One thing I noticed was that encrypt.bat and decrypt.bat didn't handle f-hd-loader+crc.bin, so i added:
It's just because of time stamp in image. Look at last 16 bytes in decrypted file. fwup utility just compares time stamp of image file with same area in flash and reject flashing of older or same image.
I just decided not to put adiition effort on detection that image was actually modified.
By the way, with some mumba-jumba I've managed to successfuly resume Gigabeat from suspend bypassing bootstrap. The only problem I have is LED controller initialization is unreliable. And, possibly, there some small issues with IDE controller. I am can try to implement something like suspend function to put Rockbox into sleep and return from this function after resume. Same as original Linux on gigabeat.
Do we any Rockbox targets that implement suspend? We can save few seconds on shutdown and on resume (bypassing rebuffering).
I have some project with higher priority, and have plan to return to rockbox in a few days.
-
Nice! I just figured out how to decrypt hd-graphic+crc.bin and work the BMP viewer. I'm guessing you have to run "fwupdecrypt.exe -e -a5 input.bin hd-graphic+crc.bin" after, to encrypt it. Also, how do you work the patches?
EDIT: decrypt.bat doesn't seem to work, it says that it's "unable to open source file", but fwupdecrypt.exe works fine if I do it manually. ??? The paths are all correct, if they aren't it gives another error.
-
I'm guessing you have to run "fwupdecrypt.exe -e -a5 input.bin hd-graphic+crc.bin" after, to encrypt it.
Where did you get the -a5 ? encrypt.bat doesn't have it.
fwupDecrypt.exe -e hd-graphic+crc.bin.dec hd-graphic+crc.bin
Also, how do you work the patches?
decrypt.bat
<patch>.bat
encrypt.bat
note my comment about missing line in *crypt.bat. I am still not 100% sure you need to *crypt all 5 files (or just the one you want to modify), but Shora's date comment seems to support it.
EDIT: decrypt.bat doesn't seem to work, it says that it's "unable to open source file", but fwupdecrypt.exe works fine if I do it manually. ??? The paths are all correct, if they aren't it gives another error.
Double-check your path. It worked for me. Alternatively - did you have the input file open in an editor perhaps?
-
I'm guessing you have to run "fwupdecrypt.exe -e -a5 input.bin hd-graphic+crc.bin" after, to encrypt it.
Where did you get the -a5 ? encrypt.bat doesn't have it.
fwupDecrypt.exe -e hd-graphic+crc.bin.dec hd-graphic+crc.bin
Also, how do you work the patches?
decrypt.bat
.bat
encrypt.bat
note my comment about missing line in *crypt.bat. I am still not 100% sure you need to *crypt all 5 files (or just the one you want to modify), but Shora's date comment seems to support it.
EDIT: decrypt.bat doesn't seem to work, it says that it's "unable to open source file", but fwupdecrypt.exe works fine if I do it manually. ??? The paths are all correct, if they aren't it gives another error.
Double-check your path. It worked for me. Alternatively - did you have the input file open in an editor perhaps?
Then what do the -a* switches do? And yes, I had it open in an editor, could that have caused the problem?
EDIT: the .bat files still don't work, this is what they look like:..\fwupDecrypt\fwupDecrypt.exe hd-graphic+crc.bin hd-graphic+crc.bin.dec
..\fwupDecrypt\fwupDecrypt.exe hd-panic+crc.bin hd-panic+crc.bin.dec
..\fwupDecrypt\fwupDecrypt.exe hd-secure+crc.bin hd-secure+crc.bin.dec
..\fwupDecrypt\fwupDecrypt.exe hd-zboot-flprog-2440+CRC.bin hd-zboot-flprog-2440+CRC.bin.dec The directory structure is the same as in the zip and anll of the needed files are in fwupDecrypt.
-
Then what do the -a* switches do?
I have no idea, first read about it in your post. :)
And yes, I had it open in an editor, could that have caused the problem?
Yes, depending on the file open parameters (exclusive access) it is quite likely that there has been a sharing conflict.
-
Read my edit, I tried without it open in an editor, it seems like it can find the files, but they're the wrong format or something.
-
Read my edit, I tried without it open in an editor, it seems like it can find the files, but they're the wrong format or something.
You call the bat file from inside the update directory, yes?
-
Now it works, I had to put decrypt.bat into the update folder and add an extra "../" in the paths. For some reason I thought that you had to have the .bin files in the same dir as fwupdecrypt.exe.
Is it OK to have non-update files in the update folder?
EDIT: The BMP viewer utility keeps giving me a wrong format error when I try to replace an image, I tried both RGB555 and 24 bit through photoshop CS2. All I did was add a loading bar to the bootsplash.bmp found in the patches dir. I tried just adding one different coloured pixel to bootsplash.bmp and saving it, and it still doesn't work.
-
Same here with Photoshop CS2. I'll try with the GIMP now.
Not working with the GIMP either.
-
Same here with Photoshop CS2. I'll try with the GIMP now.
Not working with the GIMP either.
Try to load and save with M$ Paint from Windows. I've used Paint and Jasc PainShop Pro.
I was too lazy to implement bmp header parser. Just saved couple of headers to compare.
On weekends will, probably, do better parsing later together with internal decryption/encryption.
-
Nope, Paint doesn't work, gives me the same error when I save as 24 bit bitmap.
-
Got GIMP to work, not sure how.
GIMP only worked for one image. It spurts out incompatible images afterwards.
-
Got GIMP to work, not sure how.
GIMP only worked for one image. It spurts out incompatible images afterwards.
Please check the latest version. Replay if you have any problems.
-
Seems okay 'til now. Thanks a bunch!
-
Now it's giving me an "Image dimensions must be the same" error, even with the included bootsplash.bmp. It works on the original image extracted from the firmware, but once again gives me an error after I modify just one pixel. I tried in paint and it does the same.
-
Same here, with Photoshop CS2. GIMP images seem to work fine.
-
Now it's giving me an "Image dimensions must be the same" error, even with the included bootsplash.bmp. It works on the original image extracted from the firmware, but once again gives me an error after I modify just one pixel. I tried in paint and it does the same.
Did you use, so called, V3?
If yes, then can you send this file to me? So I can look what's wrong.
-
This here doesn't work. Rename the extension to .bmp.
-
I've removed your attachment. Please, DO NOT attach things by renaming them. If you feel a filetype should be allowed, contact me and make your case as to why it's necessary to Rockbox that this filetype be supported, and I can make the necessary changes.
-
Now it's giving me an "Image dimensions must be the same" error, even with the included bootsplash.bmp. It works on the original image extracted from the firmware, but once again gives me an error after I modify just one pixel. I tried in paint and it does the same.
Did you use, so called, V3?
If yes, then can you send this file to me? So I can look what's wrong.
It's the bootsplash.bmp in the patches dir of your GigabeatF_Firmware_Hacks.zip file.
-
Now it's giving me an "Image dimensions must be the same" error, even with the included bootsplash.bmp. It works on the original image extracted from the firmware, but once again gives me an error after I modify just one pixel. I tried in paint and it does the same.
Did you use, so called, V3?
If yes, then can you send this file to me? So I can look what's wrong.
It's the bootsplash.bmp in the patches dir of your GigabeatF_Firmware_Hacks.zip file.
With this one http://rapidshare.com/files/26878889/GigabeatBmpView.exe (the latest from rapidshare folder) works like charm for me.
-
This here doesn't work. Â Rename the extension to .bmp.
you can me email. if you want. (it's on about box)
-
Now, the included bootsplash.bmp works, but not my photoshop CS2 modified one.
EDIT: paint also doesn't work.
-
Now, the included bootsplash.bmp works, but not my photoshop CS2 modified one.
EDIT: paint also doesn't work.
Just did another change - removed check for biSizeImage in bitmap header
http://rapidshare.com/files/27068500/GigabeatBmpView_V4.exe
Rapidshare folder updated also.
Hope this is last change ::)
-
Now, the included bootsplash.bmp works, but not my photoshop CS2 modified one.
EDIT: paint also doesn't work.
Just did another change - removed check for biSizeImage in bitmap header
http://rapidshare.com/files/27068500/GigabeatBmpView_V4.exe
Rapidshare folder updated also.
Hope this is last change ::)
Well it accepts my files now, everything seems good. :D
Spoke too soon, I tried updating it and it gives me a 00010003 system error. I'm so unlucky with bootloader modifications, first I brick my H10, and now this.
-
Now, the included bootsplash.bmp works, but not my photoshop CS2 modified one.
EDIT: paint also doesn't work.
Just did another change - removed check for biSizeImage in bitmap header
http://rapidshare.com/files/27068500/GigabeatBmpView_V4.exe
Rapidshare folder updated also.
Hope this is last change ::)
Well it accepts my files now, everything seems good. :D
Spoke too soon, I tried updating it and it gives me a 00010003 system error. I'm so unlucky with bootloader modifications, first I brick my H10, and now I screw this up.
EDIT2: After exiting recovery USB mode it updated, and everything works fine. :D
Here's a quick digi. cam video my my gigabeat loading rockbox. http://www.youtube.com/watch?v=80MVE9szBrc
I don't know why the focus is so off, but you get the idea.
-
Thank you for sharing this, I now have "Powerup on AC plugin" and "Shorted delay on POWER" on my gigabeat.
Is there any chance that these features could become available for non-developers?
Shorter delay on the startup button press, the better I say.
-
Thank you for sharing this, I now have "Powerup on AC plugin" and "Shorted delay on POWER" on my gigabeat.
Is there any chance that these features could become available for non-developers?
Shorter delay on the startup button press, the better I say.
You don't need to be a developer, all the tools you need are in the package, all you have to do is figure out how to use them.
-
When I loaded the fwimg files, (execpt FWIMG01.DAT, becuase the other one loads up the original firmware.) Everything is good exept some of the graphics; the loading bar and the animation when you are charging the Gigabeat is all messed. Could somone please give me a quick guide to decrypt the firmware graphic data, edit them and encrypt 'em?
I suck at this type of thing!
Yours, Sam.
-
shoora, perhaps you can be bribed to join the dark (PortaPlayer) side with an ipod in your hands?
-
shoora, perhaps you can be bribed to join the dark (PortaPlayer) side with an ipod in your hands?
I thought everything is clear with iPod firmware. What exactly you have in mind?
-
shoora, perhaps you can be bribed to join the dark (PortaPlayer) side with an ipod in your hands?
I thought everything is clear with iPod firmware. What exactly you have in mind?
In your first post in this thread you mentioned Resume (thus I assumed sleep and resume) - if my assumption is correct on your intent - this would be the killer PortaPlayer feature.
-
shoora, perhaps you can be bribed to join the dark (PortaPlayer) side with an ipod in your hands?
I thought everything is clear with iPod firmware. What exactly you have in mind?
In your first post in this thread you mentioned Resume (thus I assumed sleep and resume) - if my assumption is correct on your intent - this would be the killer PortaPlayer feature.
This must be something very simple. Samsung ARM9 have persistent registers and Gigabeat firmware/linux they use one of them (GSTATUS3) to store return address. Everything in RAM is preserved. Problem is, when firmware passes control to this address most of hardware is not initialized. It is your responsibility to complete initialization. From other hand, Rockbox does not have yet suspend/resume functionality. Only shutdown.
In iPod's firmware they must use similar feature of PP. We have changes, what Toshiba done to Linux kernel. They have implemented function s3c2440_cpu_suspend in file /linux-2.4.18-rmk6-keg/linux-2.4.18-rmk6-keg/linux/arch/arm/mach-s3c2440\sleep.S. This function is, actually, called by player application on Gigabeat.
-
This must be something very simple. Samsung ARM9 have persistent registers and Gigabeat firmware/linux they use one of them (GSTATUS3) to store return address...
In iPod's firmware they must use similar feature of PP. We have changes, what Toshiba done to Linux kernel.
We don't have a lovely Linux system as the original firmware for any of the PortaPlayer targets, though...
-
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
-
It is a command line tool. You have to run it from a command window, not the GUI.
-
God, I feel like an idiot now!
Thanks!
-
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)
-
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?
-
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.
-
Ok, recovered it!
Yours, Sam.
-
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?
-
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.
-
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.
-
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.
-
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 (http://rapidshare.com/users/VUBQPF)), 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.
-
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.
-
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.
-
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.
-
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.
Okay, thanks for the reply. I'll have to wait until someone else who has a x30 and who has the ability/time to do something similar then.
Peace.
-
Sorry for the bump but I have a question.
Do I just copy the update folder to the root of my gigabeat? Will that update folder have the 2 patches installed and the custom bootsplash?
-
No, you have to do the patching yourself.
-
So the update folder is actually the raw update files that are provided with the 3.0US update? Has anyone fully bricked their gigabeat doing this yet or will I be ok if I just stick with changing the bootsplash and power on times?
-
So the update folder is actually the raw update files that are provided with the 3.0US update? Has anyone fully bricked their gigabeat doing this yet or will I be ok if I just stick with changing the bootsplash and power on times?
I wouldn't recommend it. I got really scared when I tried changing the bootsplash and power button timer and it rejected the update. After a few restarts and some time waiting it finally updated, but the screen was all screwy during the update, which also scared me. You should update to that version before patching.
-
Well I changed my bootsplash and power on time. I already had updated to 3.0US before I found out about rockbox so nothing went to bad. I had a problem because I had to do the recovery procedure because it just did the update every time it booted up so I had to delete the update folder manually. No big deal though and it was worth it I think for my awesome bootsplash,
-
Yea it's sop worth it, but it's annoying how the power button time doesn't change on the charging screen.
-
Man we gotta find out how to properly update our GB's with these tools. I fear that recovery procedure like the plague. I went through the same thing you did Phalangees.
I tried PMing the creator and another guy in this thread who used the tools and still haven't heard back from them.
I still want to apply that Power button patch, change my bootsplash images and the recharging images again as well.
So you guys think the update folder shouldn't be going in the root? I mean it does eventually update the thing just not properly to the point you have to do the dreaded recovery procedure.
Also my update folder contained... ah jeez I don't remember if I put all the files or just the files I updated. Phalangees do you remember if you put all the update files in the update folder or just the ones you updated/changed?
I also used the FWIMG's and other Gigabeat system files that were located in the zip file I downloaded from the creator's Rapidshare page.
-
I think the update doesn't go perfectly because the creator's encrypting code isn't perfect, so it confuses the BL a bit.
-
I actually don't mind doing the recovery procedures anymore. I've done it so many times. I actually do it for fun some times. :P
I got lucky. I don't know exactly how I got the update to work. I had update folders in all the main folders and I had replaced all of the OF. So I really don't know what I did that worked but I got it to. I just read through this entire thread to get an idea of how to do it.
-
Phalangees... recovery procedure "for fun"?... You're a unique guy to say the least.
Update folders everywhere is an awesome idea.
Did you use the original firmware files (FWIMG, etc... ) provided by the zip file you downloaded or did you use your current, original firmware files instead?
-
Firstly Sorry for bringing up such an old thread but this is the only place this has ever been mentioned as far as I can tell.
Does anyone still have a copy of the tools referenced in this thread to allow me to change the splash screens on a gigabeat F?
I've just picked up another one and cant stand the default splashes.
I must have deleted the zip accidentally as I cant find it anywhere.
If you do let me know and i'll supply an email address if you wanna mail it or sort out some other method to get it off you.
Thanks,
Sam