Develop Bugs

[How] to dump KS20 RAW Rom (step by step)

The method is based on the Rom Dump for Hermes with a little bit of modifications to suit KS20
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Firstly, download the "itsutils tools" at:
http://wiki.xda-developers.com/index.php?pagename=XdaUtils
Now let's start the process:
1. Unzip the contents of itsutils.zip on c:\itsutils
2. Connect your KS20 to PC using USB cable, and make sure ActiveSync is running
3. Start -> run -> cmd.exe
4. cd c:\itsutils
5. First we are going to find the device handles for all the flash partitions, using pdocread -l
c:\itsutils>pdocread.exe -l
221.88M (0xdde0000) DSK1:
| 1.25M (0x13f000) Part00
| 5.00M (0x500000) Part01
| 69.25M (0x4540000) Part02
| 146.38M (0x9260000) Part03
1.90G (0x79b00000) DSK2:
| 1.90G (0x79ae1200) Part00
STRG handles:
handle 05bba79a 1.90G (0x79ae1200)
handle 65dadd7e146.38M (0x9260000)
handle e5dc0512 69.25M (0x4540000)
handle c5d67fb6 5.00M (0x500000)
handle a5dc04ca 1.25M (0x13f000)
disk 05bba79a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 65dadd7e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e5dc0512
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c5d67fb6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a5dc04ca
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
6. If you get the following errror, probably your device is application locked:
C:\itsutils>pdocread.exe -l
Copying C:\itsutils\itsutils.dll to WCE:\windows\itsutils.dll
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart ActiveSync.
Basically you have to modify this registry key, and then softreset using power button:
HKLM\Security\Policies\Policies
valuename '00001001' was set to dword:2, change it to dword:1
dword: any thing other than 1 disallows unsigned
dword: 1 allows unsigned
7. Note: There are two ways to read each partition: pdocread -h 0xHANDLVALUE 0 0xSIZEVALUE diskimage.nb or pdocread -d storename -p partitionname StartValue LengthValue file.raw
We will use the second method for the next step.
Overview of flash partitions (just for your information, not a step)
FLASHDR STOREINFO 114.88M (0x72e0000) dev='FLASHDR' store='Microsoft Flash Disk'
nsect=39700 bpsect=200 free=0 maxpartsize=0
3.12M ( 0x31fc00) Part00 'BOOT' end= 18fe type=20 image update kernel partition (XIP), used while image updates
2.88M ( 0x2e0000) Part01 'RAWFS' end= 1700 type=23 regular kernel partition (XIP), used for normal OS boot
50.88M (0x32e0000) Part02 'imgfs.dll' end=19700 type=25 imgfs
58.00M (0x3a00000) Part03 'fatfsd.dll' end=1d000 type=04 user filesystem
EXT_FLA STOREINFO 10.00M (0xa00000) dev='EXT_FLA' store=''
nsect=5000 bpsect=200 free=0 maxpartsize=0
10.00M ( 0xa00000) PART00 'fatfsd.dll' end= 5000 type=04 extended rom
This does not include the IPL, splash and SPL.
8. Check that all the partition sizes reported by pdocread are correct:
c:\itsutils>pdocread -w -d DSK1: -p Part00 -b 0x800 -t
real nr of sectors: 638 - 1.25Mbyte, (0x13f000)
c:\itsutils>pdocread -w -d DSK1: -p Part01 -b 0x800 -t
real nr of sectors: 2560 - 5.00Mbyte, (0x500000)
c:\itsutils>pdocread -w -d DSK1: -p Part02 -b 0x800 -t
real nr of sectors: 35456 - 69.25Mbyte, (0x4540000)
Note the partition sizes (in brackets) for the next step. They may differ from device to device.
9. Now let's dump the first 3 partitions (coldboot kernel, base kernel and imgfs), use the sizes you found in the previous step.
c:\itsutils>pdocread -w -d DSK1: -p Part00 -b 0x800 0 0x13f000 Part00.raw
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
c:\itsutils>pdocread -w -d DSK1: -p Part01 -b 0x800 0 0x500000 Part01.raw
CopyTFFSToFile(0x0, 0x500000, Part01.raw)
c:\itsutils>pdocread -w -d DSK1: -p Part02 -b 0x800 0 0x4540000 Part02.raw
CopyTFFSToFile(0x0, 0x4540000, Part02.raw)
As the Part02.raw file is large, it will take a few mins, dw just wait and it will be done!!!
Note: Step 7 is not important, can be igorned!

Thanks....I got it

it seems that we have method for install english raw file
and we have this unbranded english version
http://rs75.rapidshare.com/files/126667462/DZ-KS20E-00-V10a-454-XX-APR-29-2008_0.zip
did any body try it???

Can i flash my cel with these extracted files?
I'm from brazil, and here we have the MS25 (KS20, almost the same hardware..)
and i have extracted this 3 files, and then extracted imgfs from part02.raw.. I compared the imgfs from my MS25 with a imgfs extracted from a germany's rom flash.bin.. and it maches in almost everything.. except about the sizes (germany dump folder is almost 2x of my rom's dump folder).
my question is.. for exemple: Can i edit the extracted files and re-flash on my phone with no problems? I really need to know this, because i don't wanna brick my phone.. We don't have oficial roms for emergency, LG Brasil is a kind of lazy and still not provide us the oficial ones..
thank's in advance..

brunoargenton said:
my question is.. for exemple: Can i edit the extracted files and re-flash on my phone with no problems? I really need to know this, because i don't wanna brick my phone.. We don't have oficial roms for emergency, LG Brasil is a kind of lazy and still not provide us the oficial ones..
thank's in advance..
Click to expand...
Click to collapse
Nobody can't answer?

I want to know this as well, I'll probably provide a dutch unbranded rom if this method works.

Recooking dumped ROM

Hello,
before I flash my Diamond with a ROM by the chefs or maybe a ROM made by myself I want to backup the original ROM (T-Mobile GER) for warranty reasons. T-Mobile Germany isn't providing any ROM updates yet, so I have to build my own T-Mobile stock ROM.
I already dumped the ROM after making a hard-reset to bring everything back to factory defaults:
Code:
D:\ROMdump>pdocread -l
210.13M (0xd220000) DSK1:
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 111.50M (0x6f80000) Part02
| 91.13M (0x5b20000) Part03
3.75G (0xf0000000) DSK7:
| 3.75G (0xf0000000) PART00
STRG handles:
handle#0 27a1a642 3.75G (0xf0000000)
handle#1 27c948ea 91.13M (0x5b20000)
handle#2 07db27be 111.50M (0x6f80000)
handle#3 87db279a 4.38M (0x460000)
handle#4 27db2752 3.12M (0x31f000)
disk 27a1a642
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 27c948ea
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 07db27be
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 87db279a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 27db2752
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D:\ROMdump>pdocread.exe -w -h 0x27db2752 -b 0x800 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
D:\ROMdump>pdocread.exe -w -h 0x87db279a -b 0x800 0 0x460000 Part01.raw
CopyTFFSToFile(0x0, 0x460000, Part01.raw)
D:\ROMdump>pdocread.exe -w -h 0x07db27be -b 0x800 0 0x6f80000 Part02.raw
CopyTFFSToFile(0x0, 0x6f80000, Part02.raw)
D:\ROMdump>pdocread.exe -w -h 0x27c948ea -b 0x800 0 0x5b20000 Part03.raw
CopyTFFSToFile(0x0, 0x5b20000, Part03.raw)
D:\ROMdump>pmemdump.exe 0xa8000000 524288 SPLdumped.nb
CopyProcessMemoryToFile(00000042, a8000000, 00080000, SPLdumped.nb)
D:\ROMdump>
Now cooking a dumped ROM requires following files:
RUU_signed.nbh
Part01.raw
Part02.raw
My question is: What is the RUU_signed.nbh file I need in this case?
I guess it has to be the Provider Stock-SPL. If so, can I use the dumped SPLdumped.nb (after converting it to nbh)?
And will the ROM be all original then? Original in a way that I even don't have to Hard-SPL my device to flash it with that dumped and recooked ROM?
I found this little piece of information nowhere, so thank you for your help

Im replying to this so the thread thread stays up top, more chances of someone seeing it!
in the same situation with the O2 UK rom!
come on lads
thanks for creating the thread vogonj

Hello again,
as there is no stock ROM, stock SPL, stock whatsoever for my MDA Compact IV from T-Online Germany, I have to build my own stock ROM.
T-Mobile Germany has absolutely nothing in stock. And I don't expect anything within the next year I don't know why they don't care for their customers
That's why I need your help.
I already dumped the ROM and SPL and got these files:
Part01.raw
Part02.raw
Part03.raw
Part04.raw
SPLdumped.nb
Building a ROM from dump requires the following files:
RUU_signed.nbh
Part01.raw
Part02.raw
Question:
What has to be the content of the RUU_signed.nbh file? Is it the SPL?
If so, can I use the SPLdumped.nb from my dump (after converting to .nbh, of course)? Will the result be a stock ROM then?
Assume that the device is all original out of the box, nothing flashed so far.
Thanks for your help

Calling all LG Incite/CT810 Users/Chefs!

Hi there,
My brother just purchased the LG Incite. I, coming from the Kaiser ROM Development, would love to cook for it, as it is rather sluggish out of the box. However, I am not very familiar with non-HTC devices. So, if anyone out there has an LG Incite and knows how to cook for it, I would like to make a kitchen for evveryone to cook for this phone
Can anyone help out?
Thanks

anyone?

I'm using the LG incite, but the official rom suck.
I really want to have customize rom for it.
And I know notthing about the kitchen

Hey guys!
I have an LG Incite. If you can show me /tell me how to do it, I can probably be of help to unlock the firmware. I really want a more user friendly phone
Oh yeah I forgot. I found out how to get windows 6.5. I just need to find a way to slipstream it into the incite.
any ideas?I don't mind bricking my phone. I hav a backup software.

rkrishnan2012 said:
Hey guys!
I have an LG Incite. If you can show me /tell me how to do it, I can probably be of help to unlock the firmware. I really want a more user friendly phone
Oh yeah I forgot. I found out how to get windows 6.5. I just need to find a way to slipstream it into the incite.
any ideas?I don't mind bricking my phone. I hav a backup software.
Click to expand...
Click to collapse
do you have a micro SD card?

yup
yes I do (2gb). Any ideas?

even i would like to help

YAY!
SO...... now what?
can one of you manage to connect the incite to the computer and by using activesync, try to copy the windows folder and post it somehow on this forum?
PLEEEZE?
P.S., HEY! it's a fellow indian!

rkrishnan2012 said:
YAY!
SO...... now what?
can one of you manage to connect the incite to the computer and by using activesync, try to copy the windows folder and post it somehow on this forum?
PLEEEZE?
P.S., HEY! it's a fellow indian!
Click to expand...
Click to collapse
thank you for being so eager to help!
look here for what to do:
http://forum.xda-developers.com/showthread.php?t=238945
and post the dump.bin here
thanks again

yes waiting for the dump file

karim_31 said:
yes waiting for the dump file
Click to expand...
Click to collapse
i have 2 incites and still under 30 day warranty.
will using the grab_it - invisible ROM dumper cause or doing anything to the phone that will void the 30 day warranty?
Let me know and I will dump.
Sorry if this is a newb post.

redtaz said:
i have 2 incites and still under 30 day warranty.
will using the grab_it - invisible ROM dumper cause or doing anything to the phone that will void the 30 day warranty?
Let me know and I will dump.
Sorry if this is a newb post.
Click to expand...
Click to collapse
not at all!

mbarvian said:
not at all!
Click to expand...
Click to collapse
sweet. when i dump the rom where or who should i send the rom to?

redtaz said:
sweet. when i dump the rom where or who should i send the rom to?
Click to expand...
Click to collapse
put it in a zip file, upload it to mediafire.com and post the link here!

mbarvian said:
put it in a zip file, upload it to mediafire.com and post the link here!
Click to expand...
Click to collapse
one more thing...
which grab it should i download?

redtaz said:
one more thing...
which grab it should i download?
Click to expand...
Click to collapse
i would try this one:
http://forum.xda-developers.com/attachment.php?attachmentid=23564&d=1119937614
or if that doesn't work:
http://forum.xda-developers.com/attachment.php?attachmentid=23565&d=1119937589
make sure to follow the instructions, good luck!
thanks again

ahhhhhhhhhhh! we will have to wait till later today. I thought i had my micro sd card reader with me...
Question: If i save a copy of this rom dump, would i be able to use it to revert back to stock if another rom is flashed to it?

hey mbarvian,
can you assist in getting a grabber for 256? the rom size of the incite is 256K...
thanks!

redtaz said:
hey mbarvian,
can you assist in getting a grabber for 256? the rom size of the incite is 256K...
thanks!
Click to expand...
Click to collapse
actually, I just tried out grab_it, and I wouldn't recommend it. For a complete dump, please follow these steps:
Download the attachment, and install it on your device
Soft-reset
Download this file
Once it is finished, make a new folder on your C: drive named itsutils
Extract all the files to that folder
Plug in your device to your computer
Then click Start > Run, type in cmd.exe, then click then push Enter
Type in these commands:
Code:
cd C:\itsutils
Code:
pdocread -l
You should get something like this:
Code:
210.38M (0xd260000) FLASHDR
| 3.12M ([COLOR="DarkOrange"]w[/COLOR]) Part00
| 3.50M ([COLOR="Red"]x[/COLOR]) Part01
| 69.38M ([COLOR="Blue"]y[/COLOR]) Part02
| 134.38M ([COLOR="Lime"]z[/COLOR]) Part03
STRG handles:
handle e7489c1a134.38M (0x8660000)
handle 474960e6 69.38M (0x4560000)
handle c74b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474960e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
take note of the colored letters at the top. They will not show up like that, but I have just put them there as variables for when you type in these codes (replace w,x,y,z with what you see up there, basically ):
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 [COLOR="DarkOrange"]w[/COLOR] Part00.raw
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 [COLOR="Red"]x[/COLOR] Part01.raw
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 [COLOR="Blue"]y[/COLOR] Part02.raw
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 [COLOR="Lime"]z[/COLOR] Part03.raw
Please note that the bigger ones (Part02 and Part03) may take quite some time (15 minutes sometimes), but it is important that you do not close the Command Prompt window until they are all done!
After that, put Part00.raw, Part01.raw, Part02.raw, and Part03.raw in your itutils folder into a .zip file, upload them to mediafire.com, post the link here, and I'll take a look at them
thank you very much
if you do not understand all of it, please just ask me!
thanks

Will this cause anything to happen to the phone? (like erase the factory rom) or is it just a rom dump? Will i have to worry about the IMEI being a part of that dump?
I just DL the cab and app so let me know and i will proceed.
Thanks

where can i find an HTC WWE SHIP rom?

i've been looking all over, and i cant find it...only the Dopod rom which doesnt work with the hebrew language support...
can anyone point me to where i can get the original HTC SHIP WWE rom?
thanks!

Someone with a HTC Cavalier has to dump their ROM using the tools in this forum and post the dumped RAW files.
Code:
You will need itsutils (http://www.xs4all.nl/~itsme/projects/xda/tools.html) from itsme:
LIST NAND PARTITIONS
$ ./pdocread.exe -l
85.88M (0x55e0000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 41.38M (0x2960000) Part02
| 37.88M (0x25e0000) Part03
STRG handles:
handle c34713fe 37.88M (0x25e0000)
handle e348c912 41.38M (0x2960000)
handle c348c8ee 3.50M (0x380000)
handle 2348c71e 3.12M (0x31f000)
disk c34713fe
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e348c912
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c348c8ee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 2348c71e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
DUMP THEM!
$ pdocread.exe -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
$ pdocread.exe -w -d FLASHDR -b 0x800 -p Part01 0 0x380000 Part01.raw
$ pdocread.exe -w -d FLASHDR -b 0x800 -p Part02 0 0x2960000 Part02.raw
$ pdocread.exe -w -d FLASHDR -b 0x800 -p Part03 0 0x25e0000 Part03.raw

thanks, but i'm not sure how i progress from here...any help?
thanks.

i think, that you can use very good ookba's ROM with english interface and edit et9 input for your language, there are many how-to's on this forum and internet, even some cabs with many languages preinstalled

Try search here

gutek85 said:
Try search here
Click to expand...
Click to collapse
There's no WWE HTC ROM for Cavalier on that site. As it was mentioned to get that ROM it has to be dumped first.
Cheers

Here I'll upload all Cavalier ROMs I find in web

Mio P360&P560 ROM CEimage [BETA Official] / Boot Menu / [HOW TO] dump a ROM, by ansar

Mio P360&P560 ROM CEimage [BETA Official] / Boot Menu / [HOW TO] dump a ROM, by ansar
Hi,
Update on 3/10/2010 10:35 AM:
The following are the findings for the ROM image upgrade procedure, after an extensive testing:
1. The MS_IPL image has been identified.
2. It is not yet possible to dump the boot loader image due to the MS_IPL image placing on almost the same memory location.
3. Due to the above we cannot yet define the accepted by the boot loader ROM CE image layout.
4. The one way is to assume a layout and test it to see if it is accepted.
5. This way is completely safe.
6. It was identified the internal (final) layout of the ROM CE image by direct read access to the chip.
7. The result of this reading was 100% error free that denotes the possibility of error free writing directly to the chip.
8. This last writing (directly on the chip) it is not yet tested due to the possibility to damage the device.
9. The internal (final) ROM CE image noted at (6.) above is already in our hands but not tested yet.
10. This is the second way to the ROM upgrade procedure, but we do not know if it is safe as that of reading the chip.
Development will be continued on both ways, in order for the ROM upgrade to be finalized.
Thanks to pavlac and mumux for their extensive help and testing.
A. Screens of the official version
Pending ...
B. Download Links
Pending ...
C. Instructions to successfully flash the rom image
1. Make sure that P560 can be connected and synchronized with your PC / Laptop.
2. Use the procedure bellow to enter the boot loader menu.
3. Form the Uboot Menu select 0=WINCE Upgrade and press right key.
4. From WINCE Upgrade menu select 3=WINCE by USB and press right key.
5. From your PC run dnw5.0e.exe program.
6. Select USB port>Status and see if the USB info screen is displayed.
7. Select USB port>Transmit and open the provided file.
8. Wait for the process to finish, disconnect and slide bottom switch to OFF.
9. Wait one minute and slide bottom switch to ON in order to perform a hard reset.
End of Update
IMPORTANT UPDATE on 10/9/2010 16:35 PM:
Before issuing the relevant official ROMs derived from the partxx.raw files
it is very important for each distribution i.e. WWE, FRE, ELL etc to have the checksum of each ROM.
In order to achieve this, the owner of a specific build should perform as follows:
************************************************** **************
A. Evaluating the checksum:
1. Enter to uboot loader main menu as described bellow after this update.
2. On the main menu by pressing down the jostick navigate to [4=Memory Tools] and select it by pressing-in the joystick.
3. On the Memory Tools menu by pressing-in the joystick select [0=ROM CheckSUM], get it and write it on a media.
4. Select [2=Exit] in order to exit the Memory Tools and return to main menu.
************************************************** **************
B. Evaluating CPLD_32 and CPLD_64 user code:
5. On the main menu by pressing down the jostick navigate to [5=Other Tools] and select it by pressing-in the joystick.
6. On the Other Tools menu by pressing down the jostick navigate to [2=read CPLD_32 user code], get it and write it on a media.
7. On the Other Tools menu by pressing down the jostick navigate to [3=read CPLD_64 user code], get it and write it on a media.
************************************************** **************
C. Evaluating Nand Tools
8. On the Other Tools menu by pressing down the jostick navigate to [4=Nand Tools] and select it by pressing-in the joystick.
9. You can write down on a media what this screen is displaying.
a. Exit the uboot menu by sliding the bottom switch to power off.
************************************************** **************
Now if you have a WWE distribution you can post the above results in the form:
My Boot loader header: CHUD_350_UT_Rxx_yyyy_2G or CHUD_350_UT_Rxx_yyyy_512M or whatever.
WWE CheckSUM: 0x........ CPLD_32: 0x........ CPLD_64: 0x........
followed by the description of your Nand Tools menu.
************************************************** **************
Thanks for commenting and supporting.
************************************************** **************
************************************************** **************
Update on 7/9/2010:
The thread is updated due to final info on entry to uboot loader menu.
[HOW TO] dump your original ROM is added,see bellow.
The next step is the development of custom/official ROMs.
****************************************************************
There are at least two ways to enter the Boot Loader menu:
****************************************************************
A. First way.
1. Disconnect usb and power adaptor (all) cables from the device.
2. Turn the device to power off by sliding the bottom switch from ON to OFF position.
3. Press and HOLD the device top power button and then slide the switch from OFF to ON position.
Important note: KEEP holding top power button when sliding bottom power switch and release it when enter to bootloader.
****************************************************************
B. Second way.
1. Disconnect usb and power adaptor (all) cables from the device.
2. Turn the device to power off by sliding the bottom switch from ON to OFF position.
3. Hold JOYSTICK RIGHT + press and hold RIGHT BUTTON.
4. Slide bottom switch to ON
Important note: KEEP holding JOYSTICK RIGHT + RIGHT BUTTON when sliding bottom power switch and release it when enter to bootloader.
****************************************************************
[HOW TO] dump your ROM.
****************************************************************
This is how to dump your original ROM part00.raw, part01.raw and part02.raw files for future use.
These are guidelines and the addresses in blue from your own device must be used in the commands instead of those in the example.
1. Get the itsutils from here: http://forum.xda-developers.com/wiki/index.php?title=XdaUtils
... and unpack in your desire disc (C:\itsutils, D:\itsutils, etc.)
2. Connect your device to a PC/Laptop, sync and on your PC/Laptop run a command line or shortcut and issue the following commands:
2.1 First command:
C:\itsutils>pdocread -l
[Tap on yes, if asked to accept running the dll.]
*********************
On your screen you will see:
*********************
Copying C:\itsutils\itsutils.dll to WCE:\windows\itsutils.dll
80.00M (0x5000000) SMFLASH
| 1.25M (0x13f000) Part00
| 1.75M (0x1c0000) Part01
| 45.50M (0x2d80000) Part02
| 31.50M (0x1f80000) Part03
1.82G (0x74900000) DSK2:
| 1.82G (0x748ff000) Part00
3.69G (0xec400000) DSK1:
| 3.69G (0xec000000) Part00
STRG handles:
handle#0 839a5546 3.69G (0xec000000)
handle#1 23f61dd6 1.82G (0x748ff000)
handle#2 a3f5b99a 31.50M (0x1f80000)
handle#3 c3f5b11a 45.50M (0x2d80000)
handle#4 23f5b0f6 1.75M (0x1c0000)
handle#5 a3f61fda 1.25M (0x13f000)
disk 839a5546
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 23f61dd6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a3f5b99a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c3f5b11a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 23f5b0f6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a3f61fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\itsutils>
*****************
2.2 2nd command:
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part00 0 0x13f000 Part00.raw
*********************
On your screen you will see:
*********************
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
C:\itsutils>
*****************
2.3 3rd command:
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part01 0 0x1c0000 Part01.raw
*****************
On your screen you will see:
*****************
CopyTFFSToFile(0x0, 0x1c0000, Part01.raw)
C:\itsutils>
*****************
2.4 4rth command:
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part02 0 0x2d80000 Part02.raw
*****************
On your screen you will see:
*****************
CopyTFFSToFile(0x0, 0x2d80000, Part02.raw)
C:\itsutils>
*****************
Now you can upload your partxx.raw files and post your link to them
in order for the official rom to be constructed for future use by you and all other users.
Many thanks to pavlac and all ROM uploading members for your testing and reporting.
Regards, ansar.

Hi, I want You to help to cook some rom for P560
Yes, I was able to enter Boot Loader Menu by your suggestion.
pavlac

pavlac said:
Hi, I want You to help to cook some rom for P560
Yes, I was able to enter Boot Loader Menu by your suggestion.
pavlac
Click to expand...
Click to collapse
Hi pavlac,
This is outstanding news for P560 and hope for P360 too!!
I will prepare the WWE WM6 5.2 17945 Build 17945.0.3.2 just for testing/archiving purposes.
This version will be used after flashing a WM6.1 / WM6.5 ROM and one wants to send the device for service.
In order to proceed it is very important to describe the screen (s) of the menu:
1. Describe exactly of what you see (or make a photo in .jpg format) of the main menu and
2. Describe each one of the submenus, if any, regarding ce image upgrade.
You can also send me a private info post by clicking on name above my avatar, if you like to do so.
Regards, ansar.

Mio P560 Boot Loader Main Menu & Submenus:

Hi pavlac,
Your contribution to P360/P560 ROM development is unparallel.
I will prepare the WWE WM6 CE OS 5.2.17945 Build 17945.0.3.2 first.
If your device has a different one, before flashing a new ROM you must dump your own ROM first.
For details see #1 post.
If you have any difficulty just let me know.
The ROM that will be prepared it will be flashed as a CE image, no change to UBOOT and MS_IPL, and so will be absolutely safe.
Stay tuned and Best Regards, ansar.

Hi ansar.
I have tried to get the bootloader mode on the p560, but no succes
Any other ideas ?

Taurus1ax said:
Hi ansar.
I have tried to get the bootloader mode on the p560, but no succes
Any other ideas ?
Click to expand...
Click to collapse
Hi,
Can you describe (exactly, not i did follow the instructions) in detail how did try to enter bootloader?
See also Important Note in #1 post.
Regards, ansar.

The method described in the first post doesn't work (for Mio P360). Holding the top power button and setting the bottom switch to "ON" does nothing other than booting into WM normally. I also tried the P350 method (holding the joystick "DOWN" and switching the PDA on) and it booted into WM safe mode.
Also, pavlac's screenshots in post #4 seem to be from Mio P350, not P360 (see the CHUB350_UT_R09_0911_2G header in the first attachment).
I'm also interested in backing up/upgrading P360's ROM if anyone can help I'd appreciate it!

Hi,
All Mio P350/P550 report OSCAR at main uboot screen.
Try a variation to press and HOLD the top [+] button and slide the bottom switch to OFF.
Keep holding down the top [+] and slide the bottom switch to ON.
Do not release top [+] up to enter uboot.
Regards, ansar.

None of these work
I have tried many variations of button pressing and nothing brings up the boot menu.
Anyway, thanks for your time, if I find anything I'll post it!

Hi.
I found something on polish pda forum. Try this:
Bottom switch OFF, hold JOYSTICK RIGHT + press and hold RIGHT BUTTON, keep holding both and then slide bottom switch to ON.
On my P560 it dosen't work, but I hope Yours will be OK.

pavlac said:
Hi.
I found something on polish pda forum. Try this:
Bottom switch OFF, hold JOYSTICK RIGHT + press and hold RIGHT BUTTON, keep holding both and then slide bottom switch to ON.
On my P560 it dosen't work, but I hope Yours will be OK.
Click to expand...
Click to collapse
OKAY that did it!
Different procedure for such similar devices is strange though...
And the boot screens are similar to those you have posted in the previous page, my header is CHUB350_UT_R12_1105_512M. I have a Greek ROM, if you are interested, I will back it up and post the link here (as long as the admins verify my account and let me post external links).
Regards!!

Working for me too (mio P360),
french ROM, header is CHUB350_UT_R12_1105_512M too

My P560 dumped ROM
That's great that it works!
They say that devices with updated ROM have different combination than others devices, with older ROM.
Boot loader header: CHUB350_UT_R09_0911_2G
UT Checksum =0x419D4CD
OS Chksum=0x20D7507
CPLD_32 usercode=EF777E77
CPLD_64 usercode=***FAIL!***
Nand Tools = need soft reset
Code:
www_sukcesnet_com/~pavlac2/Mio_P560_CHUB350_UT_R09_0911_2G.zip
Sorry, but I don't know witch distribution I have. How to find out? I tried to search what WWE/ELL/FRE means but no success.

pavlac said:
That's great that it works!
They say that devices with updated ROM have different combination than others devices, with older ROM.
Click to expand...
Click to collapse
Hi,
The #1 post is updated, many Thanks for your contribution to this.
New Official/Custom ROMs are on the way.
Regards, ansar.

dump completed
Here is the dump
www_dot_nospaceleft_dot_com/raw.zip
Here is the logfile :
--------------------------------------------------------------------------
Code:
C:\itsutils>pdocread.exe -l
Copying C:\itsutils\itsutils.dll to WCE:\windows\itsutils.dll
80.00M (0x5000000) SMFLASH
| 1.25M (0x13f000) Part00
| 1.75M (0x1c0000) Part01
| 45.25M (0x2d40000) Part02
| 31.75M (0x1fc0000) Part03
396.00M (0x18c00000) DSK2:
| 396.00M (0x18bff000) Part00
14.94G (0x3bc000000) DSK1:
| 14.93G (0x3bbc00000) Part00
STRG handles:
handle#0 835ef906 14.93G (0x3bbc00000)
handle#1 43f61dd6 396.00M (0x18bff000)
handle#2 43f5b99a 31.75M (0x1fc0000)
handle#3 c3f5b11a 45.25M (0x2d40000)
handle#4 e3f5b0f6 1.75M (0x1c0000)
handle#5 e3f61fda 1.25M (0x13f000)
disk 835ef906
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 43f61dd6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 43f5b99a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c3f5b11a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e3f5b0f6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e3f61fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part00 0 0x13f000 Part00.raw
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
C:\itsutils>
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part01 0 0x1c0000 Part01.raw
CopyTFFSToFile(0x0, 0x1c0000, Part01.raw)
C:\itsutils>
C:\itsutils>pdocread -w -d SMFLASH -b 0x800 -p Part02 0 0x2d40000 Part02.raw
CopyTFFSToFile(0x0, 0x2d40000, Part02.raw)
C:\itsutils>

mumux said:
Here is the dump
www_dot_nospaceleft_dot_com/raw.zip
Click to expand...
Click to collapse
Salut,
Merci pour la distribution Française!
Regards, ansar.

Here is the ELL ROM dump from Mio P360 :
Boot Header = CHUB350_UT_R12_1105_512M
UT Checksum = 0x41B9AAD
OS Checksum = 0xFB95D345
CPLD_32 User Code = 0000B5C9
CPLD_64 User Code = *** FAIL! *** (WTF?)
Code:
hxxp://rapidshare.com/files/418212081/Mio_P360_ELL_ROM_dump.zip.html
And the log file :
Code:
E:\= NEW =\= Mio P360 =\= ROM Development =\itsutilsbin-20091117>pdocread -l
Copying E:\= NEW =\= Mio P360 =\= ROM Development =\itsutilsbin-20091117\itsutils.dll to WCE:\windows\itsutils.dll
80.00M (0x5000000) SMFLASH
| 1.25M (0x13f000) Part00
| 1.75M (0x1c0000) Part01
| 44.25M (0x2c40000) Part02
| 32.75M (0x20c0000) Part03
396.00M (0x18c00000) DSK2:
| 396.00M (0x18bff000) Part00
1.86G (0x77580000) DSK1:
| 1.86G (0x7756fe00) Part00
STRG handles:
handle#0 23f68fd6 1.86G (0x7756fe00)
handle#1 23f61dd6 396.00M (0x18bff000)
handle#2 63f5b99a 32.75M (0x20c0000)
handle#3 e3f5b11a 44.25M (0x2c40000)
handle#4 03f5b0f6 1.75M (0x1c0000)
handle#5 c3f61fda 1.25M (0x13f000)
disk 23f68fd6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 23f61dd6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 63f5b99a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e3f5b11a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 03f5b0f6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c3f61fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E:\= NEW =\= Mio P360 =\= ROM Development =\itsutilsbin-20091117>pdocread -w -d SMFLASH -b 0x800 -p Part00 0 0x13f000 Part00.raw
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
E:\= NEW =\= Mio P360 =\= ROM Development =\itsutilsbin-20091117>pdocread -w -d SMFLASH -b 0x800 -p Part01 0 0x1c0000 Part01.raw
CopyTFFSToFile(0x0, 0x1c0000, Part01.raw)
E:\= NEW =\= Mio P360 =\= ROM Development =\itsutilsbin-20091117>pdocread -w -d SMFLASH -b 0x800 -p Part02 0 0x2c40000 Part02.raw
CopyTFFSToFile(0x0, 0x2c40000, Part02.raw)
I would like to propose some additions to the guide on the first post :
1) For Mio P360, the navigation in the boot menu is done with the joystick, but the selection (ENTER) of each item is done with the right button, not by pressing the joystick.
2) The device must be connected to the computer and synchronized to WMDC/ActiveSync in order to dump the ROM.
3) There is a security prompt to accept the run of itsutils.dll by the device, it should be accepted.
4) The HEX addresses that the ROM parts reside on ARE NOT THE SAME in every device (maybe they are the same for same devices), so after the first command pdocread -l the addresses should be noted for use in the next steps.
For my device (Mio P360 ELL ROM), part02 of the ROM was in address 0x2c40000 and not 0x2d80000 as ansar's (this happens in mumux's device as well as I see).
So the commands must be :
pdocread -w -d SMFLASH -b 0x800 -p Partxx 0 <HEX address of Partxx as seen in the first command> Partxx.raw
Also I want to note that reading of CPLD_64 User Code FAILED (!!) and that when tried to enter the NAND Tools menu, my device froze and I had to soft reset it. Any answers why these happen could come handy.
Cheers

Candlemass said:
Here is the ELL ROM dump from Mio P360 :
UT Checksum = 0x41B9AAD
OS Checksum = 0xFB95D345
CPLD_32 User Code = 0000B5C9
CPLD_64 User Code = *** FAIL! *** (WTF?)
Click to expand...
Click to collapse
Hi,
The #1 post is updated, please include your boot loader header i.e. CHUD_350_UT_Rxx_yyyy_512M.
It seems that CPLD_32 and CPLD_64 [Complex Programmable Logic Device] are used to distinguish
the logic capacity of the two-input NAND gates for each implementation [P360 or P560].
So do not worry about it, each device must access its own NAND memory size.
Thanks for the ELL P360 distribution and commenting and supporting.
Regards, ansar.

ansar.ath.gr said:
Hi,
The #1 post is updated, please include your boot loader header i.e. CHUD_350_UT_Rxx_yyyy_512M.
Click to expand...
Click to collapse
Ok done, I edited my post above.