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

[obvious]

Thanks for the feedback.
Yes it is the exact same data that I attempted to restore.
I am now trying on my colleagues Axim, the exact same test, I'll report back.

Backup detecting a mismatch is theoretically a possibility, but I'm inclined to dismiss it for now, because
1- the change is not a registry change
2- The restore doesn't complain, it just fails, one would imagine that if there's any check, the restore would not continue, or at least warn instead of silently hanging at 3%.

Let's see how the second X50v behaves.

of course it's not a registry issue. I was having a brain fart.

[TalynOne]

Here is how you do it:
1) download the X50V WM5 A01 image posted earlier in this thread
2) use a hex editor to open the WM50_K_A01_X50v_WM5_ENG.nb0 file and search for the following hex string: 00 00 A0 E3 C9 0A 00 EB
You should find it at file offset 2B60BC.
3) change the first two 00 bytes to FF bytes. When you are done the block of memory will be FF FF A0 E3 C9 0A 00 EB
4) notepad the WM50_K_A01_X50v_WM5_ENG_nb0.crc file and change the contents to c5473116. Make sure you don't hit ENTER at the end. The file should be exactly 8 bytes when you save it.
5) put the two files above on a SD card that has been formatted FAT32.
6) follow the instructions above for booting into the "SD update" mode and flash the modified image

Edit: I recommend you already have WM5 installed before you do this. Switching from WM2003 to WM5 involves changing the boot loader, which is risky. Use your original Dell WM5 upgrade CD to go to "regular" WM5 first, then apply the patch.

Good luck! Please post your results if you try this.

Tried this, it flashed OK. Spent 5-6 hours installing/reconfiguring all my apps, running tweaks. Filesys.exe runs even more often now, taking 95 percent CPU, . After every soft reset and power on for 10-15 minutes, .

ARGH!

This is the straw that broke the camel's back, if no one posts a sure fire solutions to this filesys.exe bull in the next couple of days then I'm reverting to WM2003SE and staying there.

WM5 upgrade was the worst decision I've ever made, WM5 is NOT here to stay.

[bada]

I can confirm that restore has issues with the patched ROM.
Just to answer your previous question, yes I did wait for an hour before giving up.

Here's what I did with the colleague's Axim to confirm teh problem.
1- Axim x50valready setup with unpatched WM5_ROM_A01
2- Backup full data (approx 20MB)
3- Hard reset
4- Restore data, works, this proves that there's no issue with unpatched rom and restore
5- Hard reset (not necessary, but just to be on teh safest side)
6- Install the patched ROM
7- Hard reset
8- Restore the backup from step 2
9- For a long long time it was hung at 2%, I was almost at the point of giving up, then I noticed it switched to 3%, so I let it be, and went for lunch, came back from lunch, still at 3%, I figure I read a little about Fake ActiveSync patch and let teh axim try to restore, few minutes later, I heard the restore beep of the completion. I was excited, but not for long, as the screen Read.
"Failed To Restore Files
please make sure the
device is with sufficient
memory space."

Do we know what this polling is doing?
Maybe bumping the poll interval to 18hrs is bad,
perhaps it's garbage collecting, and that's why it ran out of memory as it never managed to GC.

I think I revert back to the slow Ughhhh unpatched ROM
Thanks for all that helped.

[shsmith]

"Failed To Restore Files please make sure the device is with sufficient memory space."

Do we know what this polling is doing?
Maybe bumping the poll interval to 18hrs is bad, perhaps it's garbage collecting, and that's why it ran out of memory as it never managed to GC.

I think I revert back to the slow Ughhhh unpatched ROM
Thanks for all that helped.

I agree with you that you are best to go back to the original A01 ROM. I am beginning to think this patch isn't doing much, and that what improvements I have seen are just the bit of extra performance you normally feel right after a hard reset.

I am in the midst of decompiling the filesys and msflash modules in IDA in order to come up with a better understanding of what is happening and what we might be able to do about it. In the process, I realized that my patch didn't change what I thought it did. The sleep function is passed not the number of seconds, but the number of milliseconds. That means with the patch to sleep(0xFFFF) amounts to only about 65 seconds of sleeping, a thousand times less than I wanted.

On the other hand, bluevolume's registry change seems to be helping. I don't understand the mechanism behind it, which is why I am going back to IDA and trying to understand what the code is doing.

Bluevolume's patch thread is here:
http://www.aximsite.com/boards/showthread.php?t=112194

[bada]

Thanks for the feedback.
Yes I applied that, along with few others from this thread and I already see an improvment.
http://www.aximsite.com/boards/showt...light=wm5+tips

IT seems that lots of people are able to tell which process is consuming CPU?
How are they telling this?
What tool shows the cpu utilization per process?
MemMaid only shows the processes and their memory usage.

Thanks for your continued effort on this shsmith

[neonkoala]

Obvious, I have noticed this but it is the host site which is actually a reseller of ziggyhost which has been suspended so I am not able to do anything.

[shsmith]

IT seems that lots of people are able to tell which process is consuming CPU? How are they telling this?
What tool shows the cpu utilization per process?
MemMaid only shows the processes and their memory usage.
Thanks for your continued effort on this shsmith

I use SuperTasks from http://www.softwareandson.com/SuperTasks/.
I also hear that Vidya task manager shows this information.

If you decide to try supertasks, and you don't end up registering it, make sure you uninstall it before it expires as I have heard it will need a hard reset to get rid of it after the expiry.

[bada]

Thanks, much appreciated
I tried vidya and it is working just fine.
Won't bother with software that is written so sloppy that you can't uninstall without HR when it is expired.

[UnLoGiC]

Now that we have the roms i the uncompressed .nb0 format does anybody have a clue how can we extract the files from the image or mount the image itself?

[Provito]

Either the procedure does not work for the x51v or I'm doing something wrong.

I've run through all the steps to create the os rom and ensure that the names of all the files are correct but the SD updater (A04) does not give me the option to select the images.

On the root of the SD card is the following:

WM50_K_A01_X51v_WM5_ENG.nb0 (34560k)
WM50_K_A01_X50v_WM5_ENG_nb0.crc (blank file with 12345678 in)

As the x51v has the Windows mobile 5 installed I thought that the above should be selected, instead the device reports "No suitable image found" -> "Update failed"

Could the naming of the files be different for the x51v?

I've tried a number of variations such as

WM51_K_A01_X51v_WM5_ENG.nb0 (34560k) etc but to no avail.

If I name the file diag.nb0 this is recognised correctly.

Anyone managed to get it to work on an axim x51v if so is the naming different?

[Provito]

Before anyone points out that the crc file should match the nb0 It was a typo in the previous post. It should have been:

WM50_K_A01_X51v_WM5_ENG.nb0 (34560k)
WM50_K_A01_X51v_WM5_ENG_nb0.crc (blank file with 12345678 in)

[lrizio]

In your explanation, you say:
"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."


Is there some way to check what bootloader I currently have installed in my 50v?

[obvious]

Now that we have the roms i the uncompressed .nb0 format does anybody have a clue how can we extract the files from the image or mount the image itself?

http://www.aximsite.com/boards/showthread.php?t=112267

[UnLoGiC]

http://www.aximsite.com/boards/showthread.php?t=112267

That thread describes how to extract the rom but now how to mount or alter the filesystem inside it.

I've been doing som research and it seems the the only availible tools for this right now are some pretty crude commandline tools found at xda-developers...

[obvious]

That thread describes how to extract the rom but now how to mount or alter the filesystem inside it.

I've been doing som research and it seems the the only availible tools for this right now are some pretty crude commandline tools found at xda-developers...

ah ok, I misunderstood. I think most people are using IDA to reverse/disassemble the code. Altered images should be (I'm new at this so I could be wrong) mountable somehow using the relevant MS emulator.