Database Users

extract from raw rom image?

I was attempting to use dumprom on a PDA phone other than XDA... I extracted the memory address from 0x80000000 to 0x81FFFFFF using pmemdump, and ran it through dumprom. As it turns out only the bootloader and a small part of the kernel got extracted. Nothing of the OS or the application files came out. As it turns out, looking at the dumped file, the 'good part' is missing and seems to be located elsewhere in the memory.
But then I have a rom image that can be used to flash the device, so I tried to use the image with dumprom, but that gave me an error, obviously, as the image is not laid out like how it's mapped out in the memory.
So how should I go about in extracting the files? For example, what do I have to do to modify the rom image to work with dumprom? I'll upload the rom image in question or the memory dump if need be.

To dump ROM of any PocketPC, you should extract first 32 Mb of physical memory starting from 0 address. They contain bootloader and ROM image at least on PXA25x, 26x and 27x CPUs. For example you may use my program: http://mamaich.kasone.com/imate/ROMDump.rar
it comes with source code and dumps 64Mb of ROM to any directory on SD card. Later you can extract files from this dump with "dumprom.exe dump.bin -4 -d C:\dump"
I've tested this method on several devices and it worked. If device contains 32mb ROM, the second half of a dump would be identical to the first 32 mb.
The BIN/NBF files used to flash are sometimes stored in a format with unnecessary parts removed. Such files normally start with "B000FF" signature and their format is explained in PlatformBuilder documentation. You may try to write a program that would convert them to a "normal" dump that dumprom understands.

Unfortunately, that didn't go well. The CPU is PXA255 and the OS is WM2003, but whatever ROMDump pulled out, it wasn't of any relevance. The attached file is what it put out. It's 64MB, but as you can see from the size of the compressed result, there's not much useful information in it. It's just a repetitive garbage data that goes on for the whole 64MB. Maybe the program was accessing the wrong area? To be sure, I ran the file through dumprom, and the program hanged. This isn't even as good as pmemdump, sadly. What seems to be the problem?

Probably the problem is in wrong addresses to dump. You should modify my RomDump code so that it would check all 4Gb of adress space in 32-mb blocks to find a block that looks like a ROM start. Rom starts with someting like:
Code:
0000000000: FE 03 00 EA 00 00 00 00 │ 00 00 00 00 00 00 00 00  ъ
0000000010: FE 03 00 EA 00 00 00 00 │ 00 00 00 00 00 00 00 00  ъ
0000000020: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
0000000030: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
0000000040: 45 43 45 43 4C 4B 12 84 │ 00 00 00 00 00 00 00 00 ECECLKД
0000000050: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
I.e. XX XX XX EA bytes (it is a BL command opcode) followed with garbage (may be 00, may be FFs, may be other XX XX XX EA bytes), and "ECEC" string from offset 0x40 from the ROM start. "ECEC" is present at this offset in my device and several other. But this may be not in yours.

mamaich said:
Probably the problem is in wrong addresses to dump. You should modify my RomDump code so that it would check all 4Gb of adress space in 32-mb blocks to find a block that looks like a ROM start. Rom starts with someting like:
Code:
0000000000: FE 03 00 EA 00 00 00 00 │ 00 00 00 00 00 00 00 00  ъ
0000000010: FE 03 00 EA 00 00 00 00 │ 00 00 00 00 00 00 00 00  ъ
0000000020: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
0000000030: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
0000000040: 45 43 45 43 4C 4B 12 84 │ 00 00 00 00 00 00 00 00 ECECLKД
0000000050: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
I.e. XX XX XX EA bytes (it is a BL command opcode) followed with garbage (may be 00, may be FFs, may be other XX XX XX EA bytes), and "ECEC" string from offset 0x40 from the ROM start. "ECEC" is present at this offset in my device and several other. But this may be not in yours.
Click to expand...
Click to collapse
I met this problem also. In my case, the BIN code of the ROM file that I ROMDumped from my device is looked like this
and the result of "dumprom.exe dump.bin -4 -d d:\111" is shown as following.
How can I solve this problem?
Thanks a lot.

Need help extracting files from ETEN M600 ROM

Okay, so I've tried everything. PDOCREAD, DUMPROM, pget, grab_it, testdump.exe, FiziFetch. I need help with getting at all of the files and doing a complete ROM dump of the device. The only ROM Dump I have is the one that ETEN provides for upgrading the phone, I have attached that here. EUU.exe is the exe you run on the pc, and normally the rom file is called temp.dat, and it uses the other .exe which is compiled for windows ce to the phone to do the updating process.
Any help here would be greatly appreciated. In particular I want btagext.dll in the /Windows directory and full instructions on how to do it myself for other protected files.
The ROM can be obtained by going to updates.eten.ch and downloading the latest English ROM file for the M600. The direct link is here:
ftp://support.com:[email protected]/Download/Updates/M600/ENG/EUU_M600_WWE_R01_100_0171.EXE
To get the ROM file and the update file, goto your documents and settings/profile name/local settings/temp folder and clear out all the files.
Run the .exe you downloaded from above, and then look in the temp folder you just cleared. You should see a temp.dat which is the ROM file, EUU.exe which is the file that facilitates the transfer of the file to the ETEN M600 and another file USBDLUpdate_Console.exe which is a windows CE compiled file that facilitates the flashing process in some way.
Pdocread part of the itsutils is able to read see some of the information on my device:
pdocread –l lists the following:
122.19M FLASHDR
| 1.03M Part00
| 1.52M Part01
| 33.98M Part02
| 85.47M Part03
1.89G DSK1:
| 1.89G SD
STRG handles: a34cc21e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
( 1.89G) e3b41b8a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
( 85.47M) e3b4153e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
( 33.98M) 83b41436
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
( 1.52M) a3b412be
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
( 1.03M)
However it is not able to do anything other then that. All attempts at trying to access those partitions or device (flashdr) fail with errors such as these (this is just a small list of commands command options i've tried):
C:\itsutils\build>pdocread -d DSK1
ERROR: ITTFFSGetInfo - The handle is invalid.
C:\itsutils\build>pdocread -d DSK1:
ERROR: ITLogDiskInfo - An exception occurred in the service when handling the co
ntrol request.
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\build>pdocread 0x0 0x200 foo.bin
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CopyTFFSToFile(0x0, 0x200, foo.bin)
ERROR: ITReadDisk - An internal error occurred.
C:\itsutils\build>pdocread -o -p part03
ERROR: ITTFFSGetInfo: outbuf==NULL
WARNING: using default 512 bytes for sectorsize
C:\itsutils\build>pdocread -d FLASHDR -w
ERROR: ITTFFSGetInfo - The handle is invalid.

Re: Need help extracting files from ETEN M600 ROM will pay $
I don't think that you'll be able to get a working dump of btagext.dll or any other system DLL. It does not have relocation information.
temp.dat in eten upgrade is in some strange format, it seems that data blocks are mixed.
What is the result of testdump.exe? I've attached the WM5 build of this program.

Re: Need help extracting files from ETEN M600 ROM will pay $
I've tried that before. That just dumps some information that is in memory. You can see calendar information, contact information, etc. If you put in 128mb which is the ROM size, it says DUMP OK this time (it had filesys errors the time I tried it a couple weeks ago) See here:
http://www.eten-users.net/topic1085
Anyways, in the end it dumps a 64 meg file instead of the 128 you specified, which is just the stuff in memory the 64 megs of RAM that this thing is suppose to have. If you use romdump on that file it doesn't get to many files, just about 30 or so and none of them are very important (most you can get via windows explorer and activesync)
FB

Re: Need help extracting files from ETEN M600 ROM will pay $
why do you think that eten has 128Mb OS ROM? It has only 48Mb ROM, other is left to persistent storage. So these tools would never dump full 128Mb, only 64Mb max.
You should upload somewhere the output of testdump tool, so I can look at it. It should produce _correct_ ROM dump. You just cannot extract files from it correctly. "dumprom" is for older oses, and with "-5" switch it would extract only files from XIP section (about 20 files). Use my "viewimgfs" tool to get everything from IMGFS.

I looked in the control panel, you are right it appears that the system part takes up about 48 mb, with the rest of the 128mb as user storage. It's kind of wierd though that testdump would stop at 64mb, wouldn't it stop at 48mb instead? If not why is it not doing the full 128 mb.
I tried what you had suggested and unfortunately that doesn't work either. I dumped a 64mb image, and a 48mb image. viewimgfs.exe didn't work on those images. I tried prepimgfs on the 48mb one and it couldn't find imgfs start location. I tried it on the 64mb one and it found it but the resulting file was about 256kb with a 4kb "removed_data" file which is definately not right.
I tried it without first running prepareimgfs and it just says "unable to load compress .dll".
I can't send a rom dump of what I have yet as it contains all of my contacts and calender information in looking at the memory dump in a hex editor, I'll have to whip the device clean again and I can send one but that may take awhile, i've got a lot of stuff setup right now.
Any other suggestions?

I found another bit of information. I played around with MTTY, which I know is for HTC devices, just to see what it would do though I thought I would try. It connects to the bootloader, however you never get to a command prompt. It appears that i can send a command, but then it trys to just download a file (the updated ROM). So I'm not sure if anything else can be done with this, I was hoping I could do something like "d2s" but it appears that with MTTY that doesn't seem possible.
I'm wondering if there is some way to map a USB port to a COM port so I can use regular hyperterminal. Does anyone know how to do this as Hyperterminal only supports COM ports...

MTTY is identical to hyperterminal

Ahh okay, it must be that they haven't implemented a nice interface like HTC devices where you can issue all of those commands

Hi!
Until now can you dump it? I can help you dump....
PM me,OK?

Okay, so i've finally been able to get these files from Vijay, however I'm still running into issues as describe here:
http://www.eten-users.net/topic1500
Anyone have any information on how to reconstruct PE files?

Request: Please post HOWTO for dumping Orginal ROM

Hi folks,
i've been reading quite a bit here, but found nothing real specific for dumping a original rom of the polaris. could someone please state a little howto, like for the other devices? or can other howtows (eg: dumping elf rom) be used for the polaris ?
thanks a lot....

seminiox said:
Hi folks,
i've been reading quite a bit here, but found nothing real specific for dumping a original rom of the polaris. could someone please state a little howto, like for the other devices? or can other howtows (eg: dumping elf rom) be used for the polaris ?
thanks a lot....
Click to expand...
Click to collapse
found with search...
http://forum.xda-developers.com/showpost.php?p=1847607&postcount=13
cheers!

thanx for your answer, will try to make a backup now.....
cu

ok, i extracted the 4 files, part00-04.raw. how can i create a file to flash for my device ?

seminiox said:
ok, i extracted the 4 files, part00-04.raw. how can i create a file to flash for my device ?
Click to expand...
Click to collapse
And do you want a coffee?
do you know how to search in this board ?
Just found with search function..........
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
bye

ouioui01 said:
And do you want a coffee?
do you know how to search in this board ?
Just found with search function..........
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
bye
Click to expand...
Click to collapse
well sorry for that, i have just been not shure if the description for an elf will work on my polaris. but still got some new question:
i first did a hardspl. to create an archive the guide says is have to:
take the extracted 05_OS.nb as shell/template for your ROMdump, will be overwritten!
D:\_ROM>make_imgfs.exe 05_OS.nb -nosplit
Searching for IMGFS start... Found at 00620000
Fixing... Done!
which can be extracted from
the ruu_signed.nbh from valid RUU_update.exe
so, if i don't have a valid ruu_update.exe (with original german xda orbit2 rom) i have no possibility to follow the instructions...... ???

I'm in the same boat. I want a "clean" orbit 2 but, as we all know, any O2 shop will a) give me **** and b) ask me for a lot of money if I arrive with a custom-flashed orbit 2 I want repaired.
The guide looks good, but isnt really tailored for the current Polaris situation, is it?
From what I know, I guess that I can just take the generic HTC Polaris WWE on the FTP as a signed template and compile my backup ROM that way, right?
And last question: will that revert olis HardSPL too?

schaggo said:
And last question: will that revert olis HardSPL too?
Click to expand...
Click to collapse
not with my device

I also would like to know, if the files provided here
http://wiki.xda-developers.com/index...f_HowtoDumpRom
are lgood to dump my original polaris rom?
Did someone ldo that already?
A step by step guide how to ldump my original polaris rom lwould be great...

Dumping a ROM isnt the problem. Getting the slightly branded/altered O2 ROM (in perspective to the original HTC factory Polaris ROM) back onto the device without an original O2 Updater is going to be the problem, right?
Since the HTC 1.25.405.1 Updater doesnt equal an (whenever it arrives) O2 Updater, right?
So compiling a backup ROM consisting of the currently available HTC WWE Updater and my Orbit 2 ROM backup is going to result in a device which could be identified as a Touch Cruise with O2 ROM extentions and not an original Orbit 2 with an O2 ROM, right?

I tried to dump according the wiki, but it looks different. (see below)
There seem to be some errors. Can anyone help?
D:\rom>pdocread.exe -l
210.88M (0xd2e0000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.75M (0x3c0000) Part01
| 86.00M (0x5600000) Part02
| 118.00M (0x7600000) Part03
7.61G (0x1e6e80000) DSK1:
| 7.60G (0x1e6a80000) Part00
STRG handles:
handle 85ba9956 7.60G (0x1e6a80000)
handle 873ff0f6118.00M (0x7600000)
handle 874995a6 86.00M (0x5600000)
handle 47499582 3.75M (0x3c0000)
handle a74993b2 3.12M (0x31f000)
disk 85ba9956
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 873ff0f6
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 874995a6
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 47499582
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 a74993b2
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:\rom>pdocread -w -d TrueFFS -p Part02 -t
ERROR: ITTFFSGetInfo - Das Gerõt kann nicht verwendet werden.
WARNING: using default 512 bytes for sectorsize
real nr of sectors: 1 - 512.00byte (0x200)
D:\rom>

http://forum.xda-developers.com/showpost.php?p=1923718&postcount=121

Dump rom from Mio C520 PNA

Mio C520 is working with WindowsCE core 5.0.
For dump I folow this: http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom but I have some problems.
1.First I use:
pdocread -l
Click to expand...
Click to collapse
and I got this :
C:\itsutils>pdocread -l
22.00M (0x1600000) SMFlash
| 20.00M (0x1400000) Part00
952.50M (0x3b880000) DSK1:
| 952.50M (0x3b87f000) Mio
1.90G (0x79e80000) DSK2:
| 1.90G (0x79e61200) Part00
STRG handles:
handle 6fb7499e 1.90G (0x79e61200)
handle 2fc1f746952.50M (0x3b87f000)
handle 6fe1db82 20.00M (0x1400000)
disk 6fb7499e
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 2fc1f746
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 6fe1db82
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Click to expand...
Click to collapse
2. I use:
C:\itsutils>pdocread -w -d SMFlash -p Part00 -t
Click to expand...
Click to collapse
The underline of prompter blink....
I wait and I wait, approximately 5 minutes .... and nothing.
7-8 minutes reset Mio and appears a new message:
real nr of sectors: 1 - 512.00byte, 0x200
Click to expand...
Click to collapse
3. I use this command:
C:\itsutils>pdocread -w -d SMFlash -p Part00 0 0x1400000 Part00.raw
Click to expand...
Click to collapse
Appears:
CopyTFFSToFile(0x0, 0x1400000, Part00.raw)
Click to expand...
Click to collapse
And I wait.........
Please advice, what is wrong ?
Thanks,

I have exactly the same problem with my Medion E4430.
If I use romdumptoCF.exe from http://hpcmonex.net/romstuff.htm I get only a couple of data and then only 0x00 in the rom.dump file.
How can I dump the whole 22 Mb of ROM in a file to use it on another similar device?
The ROM is a 25 Mb SMFlash Samsung Flash disk (Storage Manager says) with only 22 Mb of data (pdocread.exe says)

Try DiskRW (http://www.gpspassion.com/upload2/DiskRW.rar)
1.Start DiskRW
2.Select from combo-box (right side of to 'Store:' label) -> SMFlash
3.Press '...' button and select 'Storage Card' (where to save your SMFlash.img). Make sure you have 64Megs free on the SDCard.
4.Press 'Read' button
5.After the SMFlash is downloaded you'll receive a Message Box as confirmation (that download was finish).

Thank you. That was the answer.
But I have now another problem: I try to rewrite the flash from one device to another and when I use DiskRW I get "Error Writing Disk at offset 00000000h". In the log file I see something like that:
DeviceFlag=READONLY
DeviceProfile=SMFLASH
...
Number of Mounted Partitions=1
Is ther something that I can do to enable write on the SMFLASH?
The ReadOnly tag has something to do with the fact that one partition of SMFLASH is mounted?
P.S. The devices are exactly the same type, so the Flash image should work just fine.

Already have CHS ROMS ?who can share here?

i have got a T2222 it's CHS ! OS version is 1.26.00 who got the rom ? can u share it ?

or someone have the kitchen tools? i have try Diamond's & Kaiser's kitchen , but it not work! somebody can help?

superwing121 said:
我有VIVA的简体ROM 可是没有Hardspl 你能搞定吗？
Click to expand...
Click to collapse
有VIVA的简体ROM先发出来试验下哪些Hardspl是适合的?

superwing121 said:
是武汉多普达行货原厂ROM 你加我QQ吧 16963068
Click to expand...
Click to collapse
你的QQ拒绝添加好友，我加不了你

qingyuan-chen said:
你的QQ拒绝添加好友，我加不了你
Click to expand...
Click to collapse
兄弟给我一份加我的Q108738798

viva 的rom
qingyuan-chen said:
有VIVA的简体ROM先发出来试验下哪些Hardspl是适合的?
Click to expand...
Click to collapse
不要跑到qq.. 别人也有viva的问题.. 来给我们老外讲怎么按装英文rom
看了繁体字就疯了
btw, 我有繁体的rom, 有用吗？
[sorry for the broken chinese, it's a known fact that white skin stops one from speaking chinese correctly.. help me! i'm stuck with traditional chinese on my hongkong-bought viva!]

itaychi said:
不要跑到qq.. 别人也有viva的问题.. 来给我们老外讲怎么按装英文rom
看了繁体字就疯了
btw, 我有繁体的rom, 有用吗？
[sorry for the broken chinese, it's a known fact that white skin stops one from speaking chinese correctly.. help me! i'm stuck with traditional chinese on my hongkong-bought viva!]
Click to expand...
Click to collapse
Could you please extract the official chinese EZInput keyboard files from the HK version of Viva?

superwing121 said:
我有VIVA的简体ROM 可是没有Hardspl 你能搞定吗？
Click to expand...
Click to collapse
i was waiting for hardspl ,but i also want i CHS rom to test ! can u upload somewhere and give me a link!

terry888_1978 said:
i was waiting for hardspl ,but i also want i CHS rom to test ! can u upload somewhere and give me a link!
Click to expand...
Click to collapse
Could u please kindly share this file to us!~
Currently, I'm using a French OS on my Viva >_<~~

@itaychi
Can you upload ur traditional chinese opal rom to rapidshare or megaupload or sendspace....and share the link with us?

dpauser said:
Could u please kindly share this file to us!~
Currently, I'm using a French OS on my Viva >_<~~
Click to expand...
Click to collapse
sorry man , i just have a CHS viva and 4 raw files, about the hardSPL , i havn't ! i hope Cmonex Olipro can help us to get i hspl , that we will flash any rom we want !

能分享一下吗？谢谢！

in english please

raykisi said:
@itaychi
Can you upload ur traditional chinese opal rom to rapidshare or megaupload or sendspace....and share the link with us?
Click to expand...
Click to collapse
sure, if anyone can direct me to straight-forward instructions to how to dump the rom? i did try to look a bit on the forum and ran a search but it seemed like it's different for every device and this is the first smartphone i have (and only a week for all that's worth..)

How about this one, the Hong Kong Version CHT, can?
http://210.64.124.194/download/RUU_....708.2_infineongsm4.1.13.66_03.29.90_Ship.exe

alx75 said:
How about this one, the Hong Kong Version CHT, can?
http://210.64.124.194/download/RUU_....708.2_infineongsm4.1.13.66_03.29.90_Ship.exe
Click to expand...
Click to collapse
Thanks a lot , for the CHT rom ! but still haven't the hard spl so , can't flash in to the Viva yet ! still waiting!

terry888_1978 said:
sorry man , i just have a CHS viva and 4 raw files, about the hardSPL , i havn't ! i hope Cmonex Olipro can help us to get i hspl , that we will flash any rom we want !
Click to expand...
Click to collapse
Could you plz pack up & upload the 4 raw files to rapidshare....and share the link with us? Thx!

Safe to recycle.

it's happy to see HSPL is comes out , but still not CHS rom share out. if someone have , please share here!! hspl is work for me! waiting CHS rom!!

911sniper said:
Could you plz pack up & upload the 4 raw files to rapidshare....and share the link with us? Thx!
Click to expand...
Click to collapse
i've try the itsutilsbin tools to dump the rom out ,but not work for me!
here is the log ! someone can help me out?
C:\itsutilsbin>pdocread -l
Copying C:\itsutilsbin\itsutils.dll to WCE:\windows\itsutils.dll
99.18M (0x632d000) DSK1:
| 3.08M (0x313400) Part00
| 4.18M (0x42f000) Part01
| 88.25M (0x5840000) Part02
142.12M (0x8e1e800) DSK2:
| 142.12M (0x8e1e400) Part00
STRG handles:
handle d3a61ea2142.12M (0x8e1e400)
handle d3bbced2 88.25M (0x5840000)
handle b3bbce66 4.18M (0x42f000)
handle 53bbceae 3.08M (0x313400)
disk d3a61ea2
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 d3bbced2
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 b3bbce66
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 53bbceae
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:\itsutilsbin>pdocread -w -d FLASHDR -p Part01 0 0x42f000 Part01.raw
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x0, 0x42f000, Part01.raw)
ERROR: ITReadDisk: outbuf==NULL
- 设备未就绪。
C:\itsutilsbin>pdocread -w -d DSK1 -p Part01 0 0x42f000 Part01.raw
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x0, 0x42f000, Part01.raw)
ERROR: ITReadDisk: outbuf==NULL
- 设备未就绪。
C:\itsutilsbin>pdocread -l
99.18M (0x632d000) DSK1:
| 3.08M (0x313400) Part00
| 4.18M (0x42f000) Part01
| 88.25M (0x5840000) Part02
142.12M (0x8e1e800) DSK2:
| 142.12M (0x8e1e400) Part00
STRG handles:
handle d3a61ea2142.12M (0x8e1e400)
handle d3bbced2 88.25M (0x5840000)
handle b3bbce66 4.18M (0x42f000)
handle 53bbceae 3.08M (0x313400)
disk d3a61ea2
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 d3bbced2
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 b3bbce66
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 53bbceae
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:\itsutilsbin>pdocread -w -d DSK1 -p Part01 0x42f000 0x800 Part01.raw
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x42f000, 0x800, Part01.raw)
ERROR: ITReadDisk: outbuf==NULL
- 设备未就绪。
C:\itsutilsbin>pdocread -w -d DSK1 -p Part00 0x313400 0x800 Part00.raw
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x313400, 0x800, Part00.raw)
ERROR: ITReadDisk: outbuf==NULL
- 设备未就绪。
C:\itsutilsbin>pdocread -w -d DSK1 -p Part00 -t
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
real nr of sectors: 1 - 512.00byte, 0x200
C:\itsutilsbin>pdocread -w -d DSK1 -p Part01 -t
ERROR: ITTFFSGetInfo - 设备未就绪。
WARNING: using default 512 bytes for sectorsize
real nr of sectors: 1 - 512.00byte, 0x200
C:\itsutilsbin>