Help me dump the OS of my PPC - Upgrading, Modifying and Unlocking

Hi!
I need your help!
I have an Airis T620 PPC, the official patch from the manufacturer's site for WM5 bricked my PPC.
The AirisT620 is a MIO P550 clone, and I've downloaded the WM5 ROM for Mio P550 (MioP550 - Osc260A R05_P09.nb0) and I've intalled it succesfully on my AIRIS.
BUT, I'd like to dump the WM5 of my friend's AIRIS to a *.nb0 file to upload to my PPC. I've downloaded itsutilsbin-20070705.zip and created a RAW image.
Here's the list of the Parts:
C:\itsutils>pdocread -l
127.00M (0x7f00000) SMFLASH
| 1.12M (0x11fc00) Part00
| 1.88M (0x1e0000) Part01
| 26.63M (0x1aa0000) Part02
| 97.38M (0x6160000) Part03
976.50M (0x3d080000) DSK1:
| 976.38M (0x3d061600) Part00
STRG handles:
handle 63d1c926976.38M (0x3d061600)
handle a3f5081e 97.38M (0x6160000)
handle a3f5012a 26.63M (0x1aa0000)
handle 23f50106 1.88M (0x1e0000)
handle c3f74f2a 1.12M (0x11fc00)
disk 63d1c926
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 a3f5081e
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 a3f5012a
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 23f50106
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 c3f74f2a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I used this to create the RAW image:
Pdocread -w -d SMFLASH -p Part02 0x0 0x1aa0000 Part02.raw
If I try to make an *.nb0 directly I get the following error message:
C:\itsutils>pdocread 0 0x1aa0000 asd.nb0
CopyTFFSToFile(0x0, 0x1aa0000, asd.nb0)
ERROR: ITReadDisk : read 00000000 bytes - A device attached to the system is not
functioning.
How can I convert the raw to nb0, or how can I dump the ROM directly to nb0?
Thank you for your help!

Hi again!
I tried several methods during the weekend. All failed somewhere.
First I tried to dump the OS to hex.
C:\itsutils>pdocread -h 0xc3f0518e 0x0 0x1aa0000 OS.nb
The error message was:
CopyTFFSToFile(0x0, 0x1aa0000, OS.nb)
ERROR: ITReadDisk : read 00000000 bytes - A device attached to the system is not functioning.
the itsutils.log said:
ERROR: DeviceIoControl(FL_IOCTL_READ_SECTORS) - A device attached to the system is not functioning.
than I tried:
C:\itsutils>pdocread.exe -n 2 0x0 0x1aa0000 OS.nba
error:
ERROR: ITTFFSGetInfo - A device attached to the system is not functioning.
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x0, 0x1aa0000, OS.nba)
ERROR: ITReadDisk: outbuf==NULL
- A device attached to the system is not functioning.
after that I tried using bkondisk, and bksamsungflash:
C:\itsutils>prun bkondisk -i
in the bkondisk.log:
ERROR: kioctl(FLASH, init1) - The network request is not supported.
error initializing flash
bksamsungflash gives the same error in its log
And my last try was:
C:\itsutils>Pdocwrite -w -d SMFLASH -p Part02 Part02.raw 0x0 0x1aa0000
CopyFileToTFFS(Part02.raw:0, 0, 01aa0000)
and the last error message was:
ERROR: ITWriteDisk - The media is write protected.
How can I acquire the D-O-C password for my PDA?
Anyone has any ideas how to step further?
P.S.
The policies in HKLM\Security\Policies\Policies\00001001 is set to dword '1'
And I think my PPC is missing the IOCTL Api, how can I install it on my PPC?

Is it more simple using SPB backup.. say backup a good version of the system (without PIM) and flash over?

Hi myc!
Yes, I am using SPB backup to backup my personal files, but in this case I need to acquire the operating system of my PDA, witch can't be done with SPB backup.

Hi! (For borisbme Szia!)
Here I summarize my experiences with T620.
NOTE: with flashing you can easily have an expensive paperweight. I'm not an experienced rom cooker, with the below things you will risk that you make your device a brick. Try this at your own risk!
First take a look at the MioP550 - Osc260A R05_P09.nb0 file. The header structure seems to be rather straightforward.
0x00: "Pocket_PC_2005" \x00 \x00 \x00
0x10: 4 bytes : offset of the 1st section
4 bytes : length of the 1st section
4 bytes : checksum
4*'\x00'
0x20: "MS_IPL" som '\x00's
0x30: 4 bytes : offset of the 2nd section
4 bytes : length of the 2nd section
4 bytes : checksum
4*'\x00'
0x40: "OS_IMAGE" some '\x00's
0x50: 4 bytes : offset of the 3nd section
4 bytes : length of the 3nd section
4 bytes : checksum
4*'\x00'
0x60: "UBOOT" some '\x00's
I believe the 1st secion is the update loader , the 2nd is the actual update in MSFLSH50 format (-acer type) and the 3rd is UBOOT update.
Let's not touch the IPL and UBOOT section for a while ;-)
Based on the above information you can split the image into 3 parts and change the OS_IMAGE part.
I noticed that the checksum is for verification purpose but it does not prevent the flashing of an image with wrong checksum. I learned that because I changed the checksum to FFFFFFF to see how flashing reacts, but after a few "Bad checksum, press any key" messages I accidentally flashed my T620 with the above P550 ROM :-(
Let's look at the OS_IMAGE part.
If you want quick dump, you can try prepare_imgfs "saved OS_IMAGE file" -n -acer and view_imgfs , but you can further decompose the file.
I wrote it's "-acer" type, because it has 512 bytes sectors padded with 8 extra bytes. If you remove the padding then you have a clean MSFLSH50 file you can manipute with msflshtool.
Here I can see some difference between the P550 and T620. The 1st sector is the MBR and the partition sizes are different for the 2 device. The 2nd sector is still MSFLSH50 header, I don't know the structure, so would not change that. My assumption was, that it the file sizes are the same, it would not hurt to replace parts ;-)
One can go further with the P550 partition sizes and change T620 dumps to fit into it.
With the following little python script you can split the OS_IMAGE into parts. Do not comment the code , I not a skillful coder;-)
Code:
from binascii import hexlify
from struct import unpack
parts = (("part00",0x8FE),("part01",0xF00),("filler",0x200),("part02",0xD500))
infile = open("OS_IMAGE.dat","rb")
## MBR
mbr=open("mbr.dat","wb")
data = infile.read(520)
mbr.write(data)
mbr.close()
## HDR
hdr=open("hdr.dat","wb")
data = infile.read(520)
hdr.write(data)
hdr.close()
for (part,size) in parts:
print "Extract part ",part
ofile = open(part+".dat","wb")
for i in range(0,size):
data = infile.read(512)
marker = infile.read(8)
ofile.write(data)
ofile.close()
print "Extract rest"
ofile = open("rest.dat","wb")
while True:
data = infile.read(512)
if len(data) == 0:
break
marker = infile.read(8)
ofile.write(data)
ofile.close()
part00 corresponds to the "pdocread" dumped part00 ( I guess it's the bootloder)
part01 corresponds to the "pdocread" dumped part01 ( I guess it's the kernel partition)
part02 corresponds to the "pdocread" dumped part02 ( It is the IMGFS OS image )
With the following little python script you can combine back the parts into a "new" OS_IMAGE you can use to replace the corresponding part in the ".nb0"
Code:
from binascii import hexlify
from binascii import unhexlify
from struct import unpack
from struct import pack
parts = (("part00",0x2,0x8FE,"fdfffbff"),("part01",0x900,0xF00,"fdfffbff"),("filler",0x0,0x200,"fffffbff"),("part02",0x1800,0xD500,"fffffbff"))
outfile = open("NEW.dat","wb")
## MBR
mbr=open("mbr.dat","rb")
data = mbr.read(520)
outfile.write(data)
mbr.close()
## HDR
hdr=open("hdr.dat","rb")
data = hdr.read(520)
outfile.write(data)
hdr.close()
for (part,start,size,mark) in parts:
print "Combine part ",part,start,size
ifile = open(part+".dat","rb")
for i in range(0,size):
data = ifile.read(512)
if data == '':
print "Less data"
data = '\xff'*512
if(data == '\xff'*512):
marker = unhexlify('ffffffffffffffff')
else:
marker = pack("<L",start+i)+unhexlify(mark)
outfile.write(data)
outfile.write(marker)
ifile.close()
print "Combine rest"
ifile = open("rest.dat","rb")
while True:
data = ifile.read(512)
if len(data) == 0:
break
marker = unhexlify("ffffffffffffffff")
outfile.write(data)
outfile.write(marker)
ifile.close()
outfile.close()
The part00 and part01 is smaller in case of T620 with 0x100*512 bytes compared to P550. Add some '\FF\s to have the same size.
The part02 is bigger in case of T620, but the end of it is full of zeroes. Remove some zeroes to have the same size.
If you bring T620 dumped files to same size, you can replace those parts, combine back to OS_IMAGE and replace that part in the .nb0
The part02 can be fully edited with imgfs tools.
The part00 and part01 has SRPX signature, so you can use SRPX2XIP and then xipport or dumprom to check the content.
The .nb0 got this way can be flashed using DNW.
The next step would be the cooking ;-)
With imgfs tools you can easily remove/add packages. The unfortunate thing is that if you change AKU level then you might have to modify the 2 XIP parts as well. I have no experience with that (so far).
Also for porting WM6 it would be really good the have the pdocread dump of the P560 partitions ;-)
Hope this helps a little bit for proceeding with T620/P550 cooking/porting.
NOTE: with flashing you can easily have an expensive paperweight. I'm not an experienced rom cooker, with the above things you risk that you make your device a brick. Try this at your own risk!

Wowww!!
This post is really Interresant !
I have a mio p550, and i have an mio p560 dump !
Anyone can help me how to port the mio p560 rom to my p550 rom ??
great thanks !!!

Airis T620 Raw files
Hi,
I've dumped my ROM, and now I have the raw files. Can anyone tell me how to convert them back into a usable ROM? Thanks in advance.

Related

new rom for Samsung SGH-I780 - i780DXHC1

Can someone please asist this guy to dump it?
or explain there (PPCSG) How to?
http://www.ppcsg.com/index.php?showtopic=98612&st=240#
Thanks,
Nadav.
Nadavi said:
Can someone please asist this guy to dump it?
or explain there (PPCSG) How to?
http://www.ppcsg.com/index.php?showtopic=98612&st=240#
Thanks,
Nadav.
Click to expand...
Click to collapse
Hi Nadav, can you also share with us the steps on how you create an upgradeable ROM from the dump ROM? Thanks.
Go here:
http://forum.xda-developers.com/showthread.php?t=370529&highlight=topogigi&page=28
hello oddball1
but what is the operation to have the 3 files r*.aw ?
when i use this link i have o lot of error : http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
do you have th good parameter for the samsung ? or the parameter do you have uded to dump your rom
sacha06 said:
hello oddball1
but what is the operation to have the 3 files r*.aw ?
when i use this link i have o lot of error : http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
do you have th good parameter for the samsung ? or the parameter do you have uded to dump your rom
Click to expand...
Click to collapse
Use this tutorial, it's really complete. You only need to change the length of the raw parts according to pdocread -l results.
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
Topogigi said:
Use this tutorial, it's really complete. You only need to change the length of the raw parts according to pdocread -l results.
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
Click to expand...
Click to collapse
Hi Guys,
I've the i780DXHC1 ROM device with me. However, I'm stuck in Step 8, here's the output
D:\itsutils>pdocread -l
254.25M (0xfe40000) DSK1:
| 1.25M (0x13f000) Part00
| 2.88M (0x2e0000) Part01
| 76.25M (0x4c40000) Part02
| 172.50M (0xac80000) Part03
971.50M (0x3cb80000) DSK2:
| 971.38M (0x3cb60e00) Part00
STRG handles:
handle e765de1a971.38M (0x3cb60e00)
handle c77f842e172.50M (0xac80000)
handle 678567be 76.25M (0x4c40000)
handle c785679a 2.88M (0x2e0000)
handle a7856752 1.25M (0x13f000)
disk e765de1a
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 c77f842e
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 678567be
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 c785679a
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 a7856752
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:\itsutils>pdocread -w -d DSK1: -p Part00 -t
real nr of sectors: 1 - 512.00byte, 0x200
Did I do anything wrong? Please advise... so that I can upload this ROM to you all
Thanks!
hello paullim29
i have the same error when i try to dump the 3 files *.raw
but no answer in this forum....
sacha06 said:
hello paullim29
i have the same error when i try to dump the 3 files *.raw
but no answer in this forum....
Click to expand...
Click to collapse
i'm trying to locate someone who can help you
Nadavi
See post #3 here:-
http://www.ppcsg.com/index.php?showtopic=98149&pid=701195 :-
hello Ineedtoys
what we found in this link ? thanks
See post #3 here:-
http://www.ppcsg.com/index.php?showt...149&pid=701195 :-
hello,
here the good syntaxe to have the 3 files
pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x11f000 Part00.raw
pdocread -w -d DSK1: -b 0x800 -p Part01 0 0x240000 Part01.raw
pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x5380000 Part02.raw
ps: i have now the rom orange Fr ,
ONLY if those memory addresses match those from the pdocread -l command. Please follow all the instructions and not just quote part!
so is there a new ROM for us to try?
sacha06 said:
hello,
here the good syntaxe to have the 3 files
pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x11f000 Part00.raw
pdocread -w -d DSK1: -b 0x800 -p Part01 0 0x240000 Part01.raw
pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x5380000 Part02.raw
ps: i have now the rom orange Fr ,
Click to expand...
Click to collapse
What version of the rom you've got?
Well,
Upload the rom to rapidshare.com
so we can create a usable rom from it.
like you see in my msg, rom orange FR
sacha06 said:
like you see in my msg, rom orange FR
Click to expand...
Click to collapse
I think he meant the version. Go to Start > Settings > System > Version. You can then obtain the PDA & PHONE version.
If everything goes well, I'll be uploading the DXHC1 ROM today! This comes with the hard-reset + new mouse driver and it's in English (Singapore)
paullim29:Thank you! I really need the "Hard reset".
paullim29 said:
I think he meant the version. Go to Start > Settings > System > Version. You can then obtain the PDA & PHONE version.
If everything goes well, I'll be uploading the DXHC1 ROM today! This comes with the hard-reset + new mouse driver and it's in English (Singapore)
Click to expand...
Click to collapse
Thank you paullim. I am waiting this ROM too.
paullim29 said:
I think he meant the version. Go to Start > Settings > System > Version. You can then obtain the PDA & PHONE version.
If everything goes well, I'll be uploading the DXHC1 ROM today! This comes with the hard-reset + new mouse driver and it's in English (Singapore)
Click to expand...
Click to collapse
great !!! excellent work and hope to see the rom today!!!
gotta love xda-dev!!!
Hi Guys,
Here's the DXHC1 ROM!!! Please get it to flashable format so that we all can upgrade to this latest firmware Thanks to all the great guys' help. Without them, this wouldn't be possible at all...
http://rapidshare.com/files/111926777/DXHC1.zip

[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.

Samsung i900 Omnia rom backup help

Hi to all the Samsung experts, I currently have a Samsung i900 and am looking for a way to extract my rom and create a flashable format. I have used pdocread to extract 3 .raw files but am not sure how to proceed from here. Can anyone advise? Thanks.
Hoping that the i780 istruction can be used for the omnia, the relevant posts are here..
http://forum.xda-developers.com/showpost.php?p=2237280&postcount=10
http://forum.xda-developers.com/showthread.php?t=393490
Thanks, I have read those threads, problem is you apparently need a flashable .bin to start with which in this case I do not so am looking for a way to use the .raw files only. Do you know if that is possible?
efjay said:
Thanks, I have read those threads, problem is you apparently need a flashable .bin to start with which in this case I do not so am looking for a way to use the .raw files only. Do you know if that is possible?
Click to expand...
Click to collapse
No you don't need the bins, you can start from the raw files.
Just look at the famusc kitchen and read the included instructions.
Ok here is a way to dump the nb file and then dump its contents.I have already done that, including xip
Use itsutils and following command in dos window :
psdread -1 0 0xDISKSIZE os.nb
Then use imgfs tools or tazio tools to dump, and further processing.
We need now how to flash back the custom os.nb to omnia
still searching for sd card flashing combinations
@The Solutor: I have read the famusc kitchen docs and it explicity states you need an existing .bin PDA rom. However there are a few commands in there that may be worth checking out.
@hdubli: I will try the command you suggested later today. What are the tazio tools? And dont Samsung phones use .bin files to flash rather than .nb?
You don't need the bin.
Here step by step:
- Downlad and install the kitchen
- Copy Part02.raw into the kitchen folder
- Open cmd and type: ImgfsToDump Part02.raw (This will create dump folder)
- Execute RecreateBin.exe
You got your bin file!!!!
mievalt said:
You don't need the bin.
Here step by step:
- Downlad and install the kitchen
- Copy Part02.raw into the kitchen folder
- Open cmd and type: ImgfsToDump Part02.raw (This will create dump folder)
- Execute RecreateBin.exe
You got your bin file!!!!
Click to expand...
Click to collapse
Do you mean RecreateBin.bat? There is no RecreateBin.exe and looking at the contents of the .bat file I dont think it will work as it makes reference to i780 files which I dont have and most likely wont work with the Omnia.
imgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
yes it is the .bat file sorry.
I780 should just be name of the files that you get at the end...
I can't say if it works you just have to give it a try...
But that would be the way we do it with our i780 roms...
Try and report. You should get a i780.bin file.... otherwise it should stop with an error.
I have a Samsung Omnia German version and would like to get the english version. Anybody know where to find the WWE ROM and CID unlock or what i need to install it?
any luck
Any luck on cooking a samsung i900 Rom
JesperRas said:
I have a Samsung Omnia German version and would like to get the english version. Anybody know where to find the WWE ROM and CID unlock or what i need to install it?
Click to expand...
Click to collapse
What does ur version read?
My one read i900XXHE4. I am also looking for way to upgrade to i900DXHG4
anyone manage to extract the rom?
or is there anyway i could extract those dll in the roms?
would like to try reverse it see if can extract the data for the accelerometer
Link
Here is the Link
For the update
any body can backup the rom G2 and previous and let us flash it? i sooo want the old rom back.. G4 fully sucked with too many issues on it..
What is the build info on G4?
I can dump the rom but you will have my serial #
silencer22 said:
anyone manage to extract the rom?
or is there anyway i could extract those dll in the roms?
would like to try reverse it see if can extract the data for the accelerometer
Click to expand...
Click to collapse
it looks like a .bin file and oddly enough executing it changed all my Atom .nb0 files to 'open with' USDL4...
Do kitchen tools exist or Perhaps somebody could be commisioned to make tools for us, I'd be up for that!
whats the go on creating a flashable rom? i tried to flash chinese G8 rom and i regretted it.. now i cant flash it back to WWE G4 rom. =( anyone here able to make flashable rom or F8 or G2 WWE roms? pls pls pls..
I tried to back up my i900 Omnia ROM and get this:
C:\12>pdocread -l
128.46M (0x8076000) DSK1:
| 1.47M (0x179000) Part00
| 2.58M (0x295800) Part01
| 124.40M (0x7c66800) Part02
90.44M (0x5a70000) DSK2:
| 90.43M (0x5a6f000) Part00
0.00 (0x0) DSK5:
| 0.00 (0x0) PART00
15.00G (0x3c0000000) DSK3:
| 15.00G (0x3bffffc00) Part00
STRG handles:
handle 6698a06e 15.00G (0x3bffffc00)
handle a698a026
handle c6cc2472 90.43M (0x5a6f000)
handle 06e0479a124.40M (0x7c66800)
handle 26e04776 2.58M (0x295800)
handle 26e0472e 1.47M (0x179000)
disk 6698a06e
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 a698a026
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 c6cc2472
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 06e0479a
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 26e04776
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 26e0472e
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:\12>psdread -1 0 0xDISKSIZE os.nb
remote disk 1 has 65772 sectors of 2048 bytes - 128.46Mbyte
SerialNr: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CopySDCardToFile(remote, 1, 0x0, 0xd, os.nb)
ERROR: ITReadSDCard - The parameter is incorrect.
C:\12>pdocread -w -d FLASHDR -p Part00 0 0x179000 Part00.raw
ERROR: ITTFFSGetInfo - The device is not ready for use.
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x0, 0x179000, Part00.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use.
Any thoughts?
I am improving :
C:\12>psdread -1 0 0x8076000 i900XHHG4.nb
remote disk 1 has 65772 sectors of 2048 bytes - 128.46Mbyt
SerialNr: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CopySDCardToFile(remote, 1, 0x0, 0x8076000, i900XHHG4.nb)
but I am waiting more than 30 min and no activity. How long does it take to copy 128MB?

Vodafone UK

HI,
Does anyone have the Vodafone UK rom ?
I have searched but only found the Dutch version.
I guess you could search better?
It's on the 1st or 2nd page...
Misread
Hi,
I think you have misread my post.
There is a Dutch version but I need the English version.
There are posts about the Vodafone UK rom, but no one has uploaded the shipped rom.
However I have tried to backup it up from my phone but got an error saying "Application Locked".
Not being clued up in the world of flashing I got a little nervous and gave up before I really screwed things up.
I know everyone is going to say there is plenty of information on the forum on how to do this, but nothing is clear cut on exactly what to do and half the instructions are written in cooks language which I don't understand.
Plus the issue I have with the HARD_SPL, I notice that you have use a different version for the version ROm you have on the phone!!! That is also confusing me.
Why can't it be as simple as the touch, had no problems flashing that with the swiftblade ROM, which was awsome.
I am willing to give it ago and learn a few things on the way to get the ROM so other people can have it to, but I will need someone to help me through step by step and also I can write a guide so other noobs can follow it. I think this will also help stop with the posting of the same questions on the forum.
So if there is anyone out there who is willing to spend a little time with me to get this sorted we noobs would greatly appreciate.
Cheeers
G
help
Someone must be able to help out ?
Not seen or heard of any available UK Vodafone ROMS on here yet. (correct me if i'm wrong)
However to get started on flashing - check out the mod my diamond pages for info about flashing this device. a lot easier than searching here.
Appreciate the info.
I am trying to dump the rom first so it can be added to the forum for Vodafone UK users.
But can not find a clear cut set of instructions anywhere. When I run the pdocread.exe command I get following message:
"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\thomas>cd desktop/dump
C:\Documents and Settings\thomas\Desktop\Dump>pdocread.exe
Copying C:\Documents and Settings\thomas\Desktop\Dump\itsutils.dll to WCE:\windo
ws\itsutils.dll
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked."
I don't know what this means!!
Garetht said:
Appreciate the info.
I am trying to dump the rom first so it can be added to the forum for Vodafone UK users.
But can not find a clear cut set of instructions anywhere. When I run the pdocread.exe command I get following message:
"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\thomas>cd desktop/dump
C:\Documents and Settings\thomas\Desktop\Dump>pdocread.exe
Copying C:\Documents and Settings\thomas\Desktop\Dump\itsutils.dll to WCE:\windo
ws\itsutils.dll
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked."
I don't know what this means!!
Click to expand...
Click to collapse
you need to locate EnableRAPI.cab file and run it on your device
Garetht said:
Appreciate the info.
I am trying to dump the rom first so it can be added to the forum for Vodafone UK users.
But can not find a clear cut set of instructions anywhere. When I run the pdocread.exe command I get following message:
"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\thomas>cd desktop/dump
C:\Documents and Settings\thomas\Desktop\Dump>pdocread.exe
Copying C:\Documents and Settings\thomas\Desktop\Dump\itsutils.dll to WCE:\windo
ws\itsutils.dll
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked."
I don't know what this means!!
Click to expand...
Click to collapse
Why do you get mad but appreciate the info this does not make sense.
EnableRapi
Cursor moved
half way there
Right then, I have managed to get this so far:
C:\Documents and Settings\thomas\Desktop\Dump>pdocread.exe -l
210.38M (0xd260000) DSK1:
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 108.88M (0x6ce0000) Part02
| 94.00M (0x5e00000) Part03
3.75G (0xf0000000) DSK7:
| 3.75G (0xf0000000) PART00
STRG handles:
handle 87a2a642 3.75G (0xf0000000)
handle 67ca48da 94.00M (0x5e00000)
handle 47db27be108.88M (0x6ce0000)
handle 87db279a 4.38M (0x460000)
handle a7db2752 3.12M (0x31f000)
disk 87a2a642
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 67ca48da
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 47db27be
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 a7db2752
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I tried to do the second bit but didn't know what to, and this is the result of it:
C:\Documents and Settings\thomas\Desktop\Dump>pdocread -w -d FLASHDR -b 0x800 -p
Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use.
But am stuck on what to do next ?
have you examined other DUMP procedures like this hermes
do you have all the itsutils tools collection
Tools
I have all those tools.
But I don't know what to write in the command line to start the 2nd part. I have read the link you gave me but it doens't make sense
Any pointers ?
anyone
Anyone got any pointers ?
Problem after problem!!!!!
Got this far now:
C:\Documents and Settings\thomas\Desktop\Dump>pdocread -w -d FLASHDR -p Part00 0
0x31f000 Part00.raw CopyTFFSToFile (0x0, 0x31f000, Part00.raw)
ERROR: ITTFFSGetInfo - The device is not ready for use.
WARNING: using default 512 bytes for sectorsize
(C) 2003-2008 Willem jan Hengeveld [email protected]
Usage: pdocread [options] start [ length [ filename ] ]
when no length is specified, 512 bytes are assumed
when no filename is specified, a hexdump is printed
-t : find exact disk size
-l : list all diskdevices
-v : be verbose
-s OFS : seek into source file ( for writing only )
-b SIZE: specify sectorsize used to calculate sector offsets
-B SIZE: specify blocksize to use when reading the disk
-G SIZE: specify blocksize to use when transfering over activesync
-u PASSWD : unlock DOC device
-S BK1x : specify alternate disksignature ( e.g. BIPO, BK1A .. BK1G )
-W OFS : specify optional 'writeenable' flag ptr
Source:
-d NAME : devicename or storename
-p NAME : partitionname
-h HANDLE : directly specify handle
either specify -d and optionally -p, or specify -h
Method:
-n NUM : binarypartition number ( normal p if omitted )
-w : read via windows disk api
-o : read OTP area
if the filename is omitted, the data is hexdumped to stdout
if no length is specified, 512 bytes are printed
numbers can be specified as hex (ex: 0x8000) or decimal (ex: 32768)
C:\Documents and Settings\thomas\Desktop\Dump>
As you can see I get an Error saying " ITTFFSGetInfo - The device is not ready for use".
Now I am really stuck !!!
Help please..........................
instead of FLASHDR use DSK1:
no sure
Well that did something, but not sure what:
C:\Documents and Settings\thomas\Desktop\Dump>pdocread -w -d DSK1: -p Part00 0 0
x31f000 Part00.raw CopyTFFSToFile (0x0, 0x31f000, Part00.raw)
(C) 2003-2008 Willem jan Hengeveld [email protected]
Usage: pdocread [options] start [ length [ filename ] ]
when no length is specified, 512 bytes are assumed
when no filename is specified, a hexdump is printed
-t : find exact disk size
-l : list all diskdevices
-v : be verbose
-s OFS : seek into source file ( for writing only )
-b SIZE: specify sectorsize used to calculate sector offsets
-B SIZE: specify blocksize to use when reading the disk
-G SIZE: specify blocksize to use when transfering over activesync
-u PASSWD : unlock DOC device
-S BK1x : specify alternate disksignature ( e.g. BIPO, BK1A .. BK1G )
-W OFS : specify optional 'writeenable' flag ptr
Source:
-d NAME : devicename or storename
-p NAME : partitionname
-h HANDLE : directly specify handle
either specify -d and optionally -p, or specify -h
Method:
-n NUM : binarypartition number ( normal p if omitted )
-w : read via windows disk api
-o : read OTP area
if the filename is omitted, the data is hexdumped to stdout
if no length is specified, 512 bytes are printed
numbers can be specified as hex (ex: 0x8000) or decimal (ex: 32768)
C:\Documents and Settings\thomas\Desktop\Dump>
I have a file called Part00.raw in my dump folder now but it is 0KB.
Is that correct ?
pointers
Can someone see what I did wrong in the last post ?
anyone help ?
Trying to do the same get to same part but get
C:\itsutils>pdocread -w -d DSK1: -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
ERROR: ITReadDisk : read 00000000 bytes - The parameter is incorrect.
any suggestions anyone.
Chech this post out seems to be working for me
http://forum.xda-developers.com/showthread.php?t=412447
Just need to change the coulered values to match yours. Also make sure the numbers on the right of the coulered ones are the same, were slightly dif for part 2 and 3.

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.

Categories

Resources