TUTORIAL: The long awaited solution on how to use the SD Image Loader for flashing

domme · 01-05-06, 03:20 PM

OK, this is finally the solution to how the mysterious SD Image Loader is used.

This tutorial has been tested with the X50v, but I suppose it will work with any X50 or X51.

You can find another tutorial of me on how to make your own flash images at http://www.aximsite.com/boards/showthread.php?t=112267

DISCLAIMER: I do not take any responsibility for any damage caused to your devices.
This tutorial is only intended for advanced users.

In this tutorial I am going to mention how to use the Loader to reflash your device, a tutorial on how to build your own flash images from a ROM-Image will be posted later.

First I'd like to mention some Basics. The most important thing is to understand, how the Axim's ROM content is built up.
It consists of the bootloader, which is similar to the BIOS in a desktop computer, of the Operating System and of the Built-In Storage in exactly that order.
Currently there are 2 different bootloaders, one for Windows Mobile 2003 and one for Windows Mobile 5. A Windows Mobile 2003 bootloader cannot boot Windows Mobile 5 and vice versa. The bootloader is language independent. As for the OSes there are quite a lot of different images, differing in OS Version, language and revision.

So what do you have to do to flash your Axim with the OS version you like?

First of all you will have to ensure that you have the correct bootloader on your device. After that you can install the OS you like.

If you do not want to change the type of OS (Windows Mobile 2003 or Windows Mobile 5) you do not have to change anything regarding the bootloader.

For this you will need a bootloader image and the corresponding CRC File, which contains a checksum, to make sure the file has been copied to your device correctly.

The filename of the images have to be of the following format: [Prefix] _ [Imagetype] _ [Revision] _ [Description].nb0

I'd like to explain the different elements of the filename the Image Loader expects:

Prefix: Depends on which Bootloader is CURRENTLY installed on your device. For the WM2003 bootloader it has to be DiMa, for the WM5 bootloader it has to be WM50.

Imagetype: Tells the Image Loader which area of the Rom you would like to refresh, for the bootloader it has to be B, for the OS it has to be K.

Revision: The Revision of the image, has to be either A00 (Official Release), or X00 (Developer Release) whereas 00 stands for any numeric digits. The revision can be anything, it is not important for the flashing process.

Description: Anything you like, e.g. X50v_WM2K5_ENG

Some examples for valid filenames:

DiMa_B_A01_X50v_WM5_ENG.nb0 --> Bootloader image, to be installed on a device currently running the Windows Mobile 2003 bootloader, if the device is currently running the Windows Mobile 5 bootloader the filename had to be WM50_B_A01_X50v_WM5_ENG.nb0

WM50_K_A01_X50v_WM5_ENG.nb0 --> Windows Mobile 2005 OS image, Revision A01

As for the corresponding CRC file the filenames would be DiMa_B_A01_X50v_WM5_ENG_nb0.crc and WM50_K_A01_X50v_WM5_ENG_nb0.crc

It is important that you always install the correct bootloader before installing the OS Image.

Now lets assume you'd like to update your device from Windows Mobile 2003 to Windows Mobile 5:

1. Copy the Windows Mobile 5 OS Image and the corresponding CRC File to a FAT32 formatted SD-Card (Valid Filename for example WM50_K_A01_X50v_WM5_ENG.nb0)
2. Copy the Windows Mobile 5 Bootloader and the corresponding CRC File to a FAT32 formatted SD-Card (Valid Filename for example DiMa_B_A01_X50v_WM5_ENG.nb0)
3. Insert the SD-Card into your Axim and start the SD Image Loader by Pressing Wireless + Power + Reset
4. The Image Loader will search for flash images on your SD-Card, as there is still the Windows Mobile 2003 Bootloader on your device it will only look for files beginning with "DiMa" and therefore will only display the bootloader image.
5. Press the action key twice, this starts the update process. DANGER: If this process fails your device will be a 300$ paperweight...
6. After the process is finished (takes only a few seconds) you will be asked to hard reset your system. Ignore this message and press Wireless + Power + Reset again.
7. The Image Loader will search for flash images on your SD-Card, as there is now the Windows Mobile 5 Bootloader on your device it will only look for files beginning with "WM50" and therefore will only display the OS image.
8. Press the action key twice, this starts the update process.
9. After the process is finished you will be asked to hard reset your device. Follow this instruction and wait for the OS to load. That's all.

I have uploaded the following images for you to try this tutorial:

X50v Windows Mobile 2003 Revision A05 Englisch
http://www.rapidsharing.com/b75c6f60...a37ad85f5b3703

X50v Windows Mobile 5 Revision A01 Englisch
http://www.rapidsharing.com/3f9b6619...621aedfe742c0e

X50 Windows Mobile 2003 Revision A05 Englisch
http://www.rapidsharing.com/27641c54...aa750911e67214

Remember, if you want to change from WM2003 to WM5 and vice versa you will have to change the prefixes of the bootloader files after extracting... ;-)

BTW...I still need an X51v A06 Rom-Image for testing purposes...

awdark · 01-05-06, 03:30 PM

This is a very nice writeup. The part that im still a bit unclear about is:
Imagetype: Tells the Image Loader which area of the Rom you would like to refresh, for the bootloader it has to be B, for the OS it has to be K.

Out of curosity, how did you learn about this? An insane amount of trial and error?

Edit, I see.. B is the bootloader K is the file with the ROM. So one have to copy all 4 files into the SD card in order for it to work.
(dont need it now, but I know I will eventually brick mine and I will need it)

domme · 01-05-06, 03:39 PM

I am working for Dell...no, only a joke, it's pretty easy to find out if you have the correct filename of an image file and have a closer look at a ROM Dumo.

coolbre304 · 01-05-06, 03:46 PM

Good Write Up, It will help a whole lot of people.

Shrink · 01-05-06, 03:52 PM

Good job! Now the question on a lot of peoples' minds might be: could I use this method to flash an X51v WM5 rom onto an X50v with WM5 on it already?

domme · 01-05-06, 04:00 PM

If anyone could send me the ROM-Image aof the X51 I would give it a try!

Tblove · 01-05-06, 04:08 PM

Nice job.Thanks for taking the time.

hosps · 01-05-06, 04:31 PM

Thanks for doing a great writeup. Looking forward to trying this when I get home from work tonight.

PS: Does anybody know a good brick replacement for my 50V?

Maniek · 01-05-06, 04:42 PM

It's look like miracle... Big chance to come to life my dead Axim. But it's one problem I have got X50 (not X50v). Could someone prepare files *.nb0 and crc file for this model (now WM 5)? Or tell me how can I do this self. Thanx.

obvious · 01-05-06, 04:48 PM

Good stuff. When you have the time could you describe the image editing process to create a valid .nb0 and .crc file after a ROM dump?

For the record, This post describes how to dump an existing ROM.

Shrink · 01-05-06, 05:34 PM

I've put a sticky on this post considering this has been an issue which has come up frequently.

I think it is important for prospective readers and followers of this guide to recognize that this procedure is not officially supported by Dell and that they probably won't be held responsible (nor does Aximsite or the author of the post) should you brick your pocket pc.

Now that that is out of the way, good work!

trustno1 · 01-05-06, 05:47 PM

Congratulations, that's a really good job !

It will be useful here in France too, where Dell refuse to send a replacement, considering that the warranty is void when upgrading an x50v to WM5... Is it the same everywhere else ?

rlarson_mn · 01-05-06, 06:56 PM

Quote:

Originally Posted by coolbre304

Good Write Up, It will help a whole lot of people.

I agree, great instructions. An example of the type of people that populate this great site.

shsmith · 01-05-06, 07:09 PM

Do you know how the .crc files are made? The "normal" CRC reported by zipping utilities is different than what's in the .crc file. Is there a tool that scans a .nb0 and calculates the expected .crc? Thanks!

domme · 01-05-06, 07:15 PM

Quote:

Originally Posted by shsmith

Do you know how the .crc files are made? The "normal" CRC reported by zipping utilities is different than what's in the .crc file. Is there a tool that scans a .nb0 and calculates the expected .crc? Thanks!

Yes I know how to make them...I will post information on that tomorrow.