Hi,
Following this thread: http://forum.xda-developers.com/showthread.php?t=310287 I created a dump directory for a WM6 image. Inside the SYS directories are a number of subdirectories. Some of these subdirectories have familiar names (e.g. calendar.exe). Using calendar.exe as an example, there are 5 files: imageinfo.bin, imageinfo.txt, S000, S001, and S002. Here are my questions:
1. What are these 5 files?
2. What tool would I use to put the folder together to create a single executable?
Sorry for the noob questions but I can't find the answer on the forums!!
OK, after trying out all of the tools in one of the bundles, I found the answer to the second question:
2. Within someone's kitchen tools (I don't remember which one I downloaded) was a file called recmod.exe. Run it with the folder as a parameter and it will put the exe together.
I still don't have the answer as to what those 5 files are though.
My terms may be off base but I'll try to explain what these files are as I understand it (and hopefully not look stupid in the meantime as I'm also trying to explain it in layman's terms).
Many core files are constructed like this so that they are optimized in the Rom to make them run more efficiently on our devices.
Related
I can't copy or move files stored in device ROM.
I've tried with Resco Explorer and Total Commander, but without success.
I didn't understand if there's a registry hack that allows these operations.
I've notice (or so it seemed to me) that I was able to substitute/copy/move some files having the ROM attribute, but many others not (eg: I've tried to copy the nleddrvr_sec.dll, obviously without success, otherwise I'd post this here!).
Surfing in many forums, I read many others asking for the same thing, unfortunately I haven't seen answers to their question about this.
Hope someone explains to me how to do or why is impossible to do.
Mersì bo q.
Gubbài.
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
levenum said:
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
Click to expand...
Click to collapse
As you said here and here (Changing Files in Windows Dir )
it's impossible to move/copy ROM files, just overwrite 'em.
Doing so the system looking for these overwritten copies.
So now the question are:
- there's a registry entry that points to this substitute ROM files?
- to modify an existent file resident in ROM I MUST dump my ROM or another one same or similar?
Mersì bo q, anyway.
Gubbài.
Hi everyone,
My PDA support center distributes updated roms in "nb0" file format, I was wondering if anyone could help me throught openning this file and doing some modification. Since there are many unusefull applications inside it and I want to delete or subsitite them. I read some topics about cooking roms in forum but I cann't find any information about customizing "nb0" files.
Thanks!
Pedram
Fortunetly, I could dump content of ".nb0" file with tools provided here: http://forum.xda-developers.com/showthread.php?t=249836 (Beta: WM5 ROM editing tool). I got pleanty of files in dump folder. It's har for me to diffrentiate which file is which!
Could any one help me to find my voice command application inside this dumped rom and repalce it with another voice commmand application such as MS voice command?
There are some files and directories with this name in my dumped rom:
VoiceBar.dll, VoiceCtl.dll, voicedll.dll, VBarCall.dll, VCOMCtl.dll
I am really confused! I do not know what files should I delete or where copy new files.
Thanks in advanced.
i want to change my windows mobile 6.1 os 64mb rom to 128mb but i cant find any editing tool. im using asus p535 and rom file GalaxyII_new.nb0 like that.
moved to Q&A
I read the guides in this website, but need some extra guidance of how to achieve the following (if it is possible):
Let's say that one of the chefs cooked a ROM that I really like (let's call it "ROM X"), but there is one change that I would like to do to the ROM, for example, let's say I would like to delete the OEM package for the dialer that he used, and use an OEM package for a different dialer.
I understand that I need to do the following:
1. First I need to flash "ROM X" to my kaiser.
2. Now I need to dump "ROM X" from my kaiser, to my hard drive. At the end I get the 4 raw files.
Now comes the stage I'm not sure how to accomplish: I want to load the cooking applet of the kitchen software, and have all the database from the 4 raw files (of "ROM X") appear, so I can make the needed change in the OEM package, and continue to create the ROM. I understand that I need to somehow extract the information from the raw files, to something that the cooking applet of the kitchen software could use, but I'm not sure how...
Can anyone provide a bit of guidance ?
Thank you very much.
Btw, I've seen the following thread which deals with how to reconstruct a dumped ROM, but it doesn't deal with how to make changes to the ROM during the reconstruction process, rather the ROM you create, is simply a 100% duplicate of the ROM you dumped, and this is not what I'm trying to achieve...
http://forum.xda-developers.com/showthread.php?t=337066
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily
When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!
Sorry if i am asking something that is already answered for numerous times, but believe me i have tried to gather the information on my own but none of those worked.
I would like to extract files from Windows Mobile 6.1 Rom to see what are exported dll apis, not only those documented, I am basically waiting for blackstone and having blueangel right here but i actually dont really care which rom image to use, just to get the binaries out.
I am not familiar with terminology you use for describing this (and idea: put together some dictionary ) but for sure none of the described around keywords NbfUtils (activestate ppm just doesnt work), rdmsflsh.pl (After nbfutils installed "by hand" it doesnt find NbfUtils.lib)... After all the misery with bunch of not working tools and switches with curious names (and both probably perfectly understandable by someone playing with roms for years - not my case) I have done some code to dump dlls from rom images by searching for PE and looking for export directory but they are not really highly descriptive without file names.
Can someone PLEASE point me to some relevant data, how to get files and directory structures either from rom images here or .bin images for visual studio emulator?
Thank you for reading this...
http://forum.xda-developers.com/showthread.php?t=289830
Been there, done that...
http://www.xs4all.nl/~itsme/projects/perl/ppm repository does not work (activestate perl) and if i try to do it "by hand" (perl makefile.pl, nmake, nmake install), it is ok for nbfutils, but for compress utils nmake fails with LINK : fatal error LNK1181: cannot open input file 'nkcompr.lib'.
And this is fatal error not warning as someone mentioned somewhere else on the forum...
Concerning Imgfs Utils...
>ImgfsToDump.exe PPC_USA.BIN.payload
ImgfsToDump 2.0 RC 2
Unable to load compression DLL!
The first reason for this was dynamically loading cecompr_nt.dll wich have dependancy to missing c runtime for vc2003 (as i only have vc2008), i have added it but it fails with the same
message, will trace it further, those are at least things i do understand