Installing a custom Boot logo on the X30

[OddbOd]

WARNING: Do not even think about attempting the procedure outlined below unless you are prepared to take full responsibility for killing your PDA if you mess up. This technique has been thoroughly tested on the X30Mid (A02 and A05 ROMs) and so far has not caused any problems whatsoever. This does not mean it is 100% safe, it's a hack and should be regarded as such.

Requirements:

• Axim X30
• Hex Editor (any will do)
• An official Dell ROM updater (I have used both R80725.EXE (A02) and R87096.EXE (A05) updates)
• A 240x320 256 colour BMP (size must be 76kb)
  
  Here's one I prepared earlier
  
  

Method:

1. Extract the ROM updater to a convenient location on your HDD, connect your sync cable, check ActiveSync is running and start "Setup.exe".
2. Click on "Backup/Restore ROM" then on "Save ROM" then "SAVE", you will now be asked for a location to save the RIS (ROM Image Saved) file, choose somewhere convenient and let the flasher save out the image.
   
   It should take about 5 minutes and produce a file named XXX_Y_ZZZZZZZZLL.RIS
   
   XXX = Your current ROM version
   Y = Whether your Axim is a Combo(C) or Non-Combo(N) unit
   ZZZZZZZZ = Your exact ROM revision as shown under Settings->System->System Information
   LL = Your ROM language
3. Make a backup copy of the RIS file and keep it just in case you want to revert to the stock ROM. Alternatively, if you have an SD card, you can skip making this second backup as this method allows you to revert to a stock ROM of your choice. I have tested it on my X30 and had no trouble, just remember not to plug the USB cable in before you push the buttons down otherwise it will stall.
4. Open up the RIS file in your Hex editor and take a look through it, the first 0x200 bytes are the file header and tell the flasher what device it is intended for, whether it's a backup or update (there are at least three different types of update), the ROM version and the ROM language. The thing that it does not contain is a checksum of the image contents which as the more astute readers will no doubt have guessed is the secret to why this works. The IMG files that are supplied with the update utility DO contain checksums this is why they are not suitable for hacking custom content into.
5. How you replace the bootlogo is completely up to you and will depend on the capabilities of your hex editor. I saved the file in 3 separate pieces then concatenated the first part, my new boot picture and the third part together. You may wish to simply paste your picture straight over the top of the current one if this is easier. The following addresses will come in handy, though you should be particularly cautious if there is no bitmap header at the address I have indicated (MS bitmaps always start with "BM") as it means your ROM is slightly different:
   
   A02 (Combo) A02_C_06100400EN.RIS @ 0x0014DDB0
   A02 (Non-Combo) A02_N_06100400EN.RIS @ 0x0014D5D8
   A05 (Combo) A05_C_10070400EN.RIS @ 0x0014E268
   A05 (Non-Combo) A05_N_10070400EN.RIS @ 0x0014D994
   
6. At this point you may have found that your BMP file is 2 bytes larger than the original Dell one (0x13036 bytes as opposed to
   0x13034 bytes), I'm not really sure why this is but it is not important. All you have to do is remove two null bytes at the end of where the BMP is located within your image file (i.e. at 0x00160DE5 in the A02 combo ROM).
7. You should now have a modified RIS file 0x02000200 bytes long containing your picture, if your file size is different and you can't figure out why then do not attempt to flash with it (bad things could happen!). If all is well use the Dell updater to flash your modified ROM by using the restore feature.
8. That's it

If anybody is game to try this on a different model let me know how you get on. Any other comments, complaints or general banter will always receive a polite reply.

[eugenchivu]

man..i can't get anything

i have no clue how to do it )

[transcout]

which hex editor exactly did you use? i got the first one i could find, but it doesnt work very wel...

[star882]

I think you can simply replace a file (boot.bmp?) to do this.

[psydstudent]

Originally Posted by star882

I think you can simply replace a file (boot.bmp?) to do this.

Tried it...doesnt work.

The actual image file that is used by the Axim is located in the ROM...that is why the boot.bmp file that you can modify in the Windows directory doesnt do anything. This is also why, as OddbOd's original post discusses, you have to flash the Axim with a new image file that has been modified to include your new boot image.

[OddbOd]

Originally Posted by transcout

which hex editor exactly did you use? i got the first one i could find, but it doesnt work very wel...

I used NitroHex as it has file compare which made it easier to figure out why my first attempt came out 2 bytes too long, it's also abandoned shareware so I don't think the author will care if you register it. I have used Hiew in the past but found it was a bit unwieldy for this particular task having forgotten most of the key commands

Originally Posted by star882

I think you can simply replace a file (boot.bmp?) to do this.

A quick forum search would have shown several people already tried this without success, they were my inspiration to cook up this hack.

[Crypty]

I am generally a lazy person but I am actually going to give this a try with my x30 high. Will let you know how it turns out. Now... To find a good picture.

[hd2002]

Will try this on my x5 tomorrow, any hint on how to locate the hex address of the boot image on diff rom versions?

[OddbOd]

Just copy the boot.bmp file from the Windows directory of your Axim and open it in your hex editor, then, search in the RIS file for the sequence of bytes at the beginning.

For example on an X30 A02 ROM you would do a search for "42 4D 36 30 01 00". The first two bytes are always 42 4D and the next four are the file size according to the MS DIB specification.

[psydstudent]

Originally Posted by OddbOd

Just copy the boot.bmp file from the Windows directory of your Axim and open it in your hex editor, then, search in the RIS file for the sequence of bytes at the beginning.

For example on an X30 A02 ROM you would do a search for "42 4D 36 30 01 00". The first two bytes are always 42 4D and the next four are the file size according to the MS DIB specification.

Okay, I opened the boot.bmp on my x30 A05 C unit and got the following string:

42 4D 34 30 01 00

I found that string in the RIS file at:

0014e268-0014e26e

Now what?

BTW I'm using Hex Editor as my program.

[Shirow]

Is the dell screen that bad? You only see it for maybe 2 seconds. What happens when A06+ comes out. Will this effect it?

[psydstudent]

Originally Posted by Shirow

What happens when A06+ comes out. Will this effect it?

Yea, but we'll just end up hacking that ROM revision too

[mgpirola]

Hi, I am attempting to move from A00 DE to A05 EN on my X30 combo. After modifying the A05 Rom Image to have the Header from A0 I encounter an "Integrity Check" error when try to Rom Update. I am swapping 00-70 using HDD hex editor. Is there some Checksum value in this area I should be taking care off?
Thanks
Mark

[OddbOd]

I am currently testing the ability to change ROM languages as I type this. I have already changed my ROM Version to GE A01 which worked perfectly, using a stock German ROM with the header from my normal English A05 Backup (RIS) file. I am flashing back to a Stock A05 English ROM using the SD Card method to ensure both techniques work.

All finished, all is well. The method I would recommend is to use the flash from SD Card technique as it is language agnostic, the details are here . It works the same way on the X30 though you don't need to remove the battery, also make sure you use a stock Dell ROM of the correct type.

hd2002: I already contacted Chris before posting this thread, he didn't have any problem with it. With regard to possible licensing issues I honestly don't know, you would have to ask the copyright holders.

[hd2002]

for some reason i have a feeling this thread might get locked soon.

To any who actually finished the EULA: do we have the licence to use a different localized version of the pocket mobile 2003 (SE)?