Rom Dump/Build Application

[Guest wes58]

ohh something useful would be minimize button :( and option minimize to tray :P

I could hide all the console, xipport and extreloc windows but I leave some minimized so you can open it and see what it is doing. I minimize all except for Extreloc. And I do it on purpose because I am not detecting if there are errors in reallocation (whether extreloc displays in the log windows "Error = 0" or not.), and this way you can see what is happening. If Extreloc displays errors in log windows (I don't think it happens too often), the rom continues to build. So you should monitor this part of the process - it doesn't take that long and it closes automatically.

Edited April 2, 2010 by wes58

[Guest wes58]

my mobile hangs at the start screen (SAMSUNG OMNIA II) when ever i use the rom_tool.

:P :( :( B) ;) :o

in detail, I do the following :

1. flashed secany's rom to my mobile

2. got rom_dump.bin

3. using o2util , got .nb0

4. started rom_tool

5. followed the default steps as in the attached pictures

6. then i use octans mini or octans 2.14 to flash the .nb0 to my mobile

7. i only flash the .nb0 without anyoither file which i can do with the origional .nb0 before using the rom_tool and it works fine.

8. after flashing the resulted .nb0 ,my mobile hangs at the first screen (SAMSUNG OMNIA II)

anyone can tell me what is my wrong step please (MSG log is attached)?

From the message log everything looks ok, except it seems strange that there is no information about "Timebomb" or "Beta Keys". There should be two lines (text different depending on the conditions:

*** TIMEBOMB bitPattern not Found in \shell\shell32.exe

*** BETA keys not Found in 1f1aca24-d942-464a-9281-10567741499c.rgu

It also doesn't show in one of the pictures - I think it's the third one. It shows only text for Page Pool and Security Patch?

It looks like there is no SHELL folder in you SYS_7173 folder!

You should check that you have all the files?

So, from the pictures I can see that you are trying to port different OS version to you new rom (which you call sys_7173). Is this correct?

If you checked that you rom files are correct, you can try:

1. Try to build the rom but select also options "delete osaxst0.dll" and "delete hd.dll".

2. And then try to build the rom doing manual reallocation and see if you get any errors in the Extreloc log window - select "Manual Realoc. of modules". Follow the steps shown on the pictures which are in the file in the first post.

By the way, when you dump the rom from the phone and get rom_dump.bin you don't have to convert it to .nb0. You can just open rom_dump.bin with romTool and dump it.

[Guest samihussein]

From the message log everything looks ok, except it seems strange that there is no information about "Timebomb" or "Beta Keys". There should be two lines (text different depending on the conditions:

*** TIMEBOMB bitPattern not Found in \shell\shell32.exe

*** BETA keys not Found in 1f1aca24-d942-464a-9281-10567741499c.rgu

It also doesn't show in one of the pictures - I think it's the third one. It shows only text for Page Pool and Security Patch?

It looks like there is no SHELL folder in you SYS_7173 folder!

You should check that you have all the files?

So, from the pictures I can see that you are trying to port different OS version to you new rom (which you call sys_7173). Is this correct?

If you checked that you rom files are correct, you can try:

1. Try to build the rom but select also options "delete osaxst0.dll" and "delete hd.dll".

2. And then try to build the rom doing manual reallocation and see if you get any errors in the Extreloc log window - select "Manual Realoc. of modules". Follow the steps shown on the pictures which are in the file in the first post.

By the way, when you dump the rom from the phone and get rom_dump.bin you don't have to convert it to .nb0. You can just open rom_dump.bin with romTool and dump it.

yes , no SHELL folder in SYS_7173 !! where should i get it ?

yes i'm trying to port different OS (sys_7173)

i tried the manual realoc before and i got no erros.

ok to be 100% sure , can u please list what should i do in manual realoc in steps ?

i know that i can use the rom_dump.bin directly with rom_tool but i was trying all the possible reasons.

will try now to build again and see the result.

thank you

Edited April 2, 2010 by samihussein

[Guest wes58]

yes , no SHELL folder in SYS_7173 !! where should i get it ?

yes i'm trying to port different OS (sys_7173)

i tried the manual realoc before and i got no erros.

ok to be 100% sure , can u please list what should i do in manual realoc in steps ?

will try now to build again and see the result.

thank you

I don't know what this version is without SHELL folder? Is it going to work?

There is no point listing the steps for manual reallocation because they are shown/numbered on the picture. You can also check Extreloc screen in automatic reallocation - look in the log windows there should be last message "Errors = 0". But I think that the problem may be missing some folders in your sys_7173.

[Guest Ryrzy]

I could hide all the console, xipport and extreloc windows but I leave some minimized so you can open it and see what it is doing. I minimize all except for Extreloc. And I do it on purpose because I am not detecting if there are errors in reallocation (whether extreloc displays in the log windows "Error = 0" or not.), and this way you can see what is happening. If Extreloc displays errors in log windows (I don't think it happens too often), the rom continues to build. So you should monitor this part of the process - it doesn't take that long and it closes automatically.

hmm ok but sometimes i have opened more apps and in bottom taskbar in win is full :( i want to minimalize only romTool.exe... but you have right... if i make rom and minimize this i would not see if there are some errors :P

[Guest Teflanzy]

hi everyone

does anyone know what files are related to the camera in the oemapp folder?

thanks

[Guest Matulek]

Hey, when i try to use LZX Compression, The rom crashes on boot. I tried to change the cecompr.dll from lzx folder, but nothing changes. Can someone write here, how to use it?

edit:

ok. now its working. I replaced files from LZX to MODULES and its. ok.

Thanks;)

Edited April 3, 2010 by Matulek

[Guest wes58]

Hey, when i try to use LZX Compression, The rom crashes on boot. I tried to change the cecompr.dll from lzx folder, but nothing changes. Can someone write here, how to use it?

edit:

ok. now its working. I replaced files from LZX to MODULES and its. ok.

Thanks;)

I am not sure what you did. When you select "LZX compression", and you start the build the files from LZX folder (cecompr.dll modules) will be copied to dumped xip.bin (in OUT folder) and replace original cecompr.dll modules. You don't have to do anything manually.

The only thing that you had to do when you update your version of romTool was to:

1. copy/replace cecompr_nt.dll which is in TOOLS folder. I am not sure if the version I had before was for LZX compression

2. copy imgfsLZX.src to ROM folder. When you dump your rom this file will be created but if you are using LZX compression with the rom that you dumped with previous version of ROM tool you have to copy this file from the archive.

3. copy LZX folder to you XIPTOOLS folder.

[Guest wes58]

hmm ok but sometimes i have opened more apps and in bottom taskbar in win is full :( i want to minimalize only romTool.exe... but you have right... if i make rom and minimize this i would not see if there are some errors :P

I tried to keep ExtReloc window minimized but because of the Debug tab and log window, if I minimize it, I can't get messages from the Debug tab Log window. So we have to keep it maximised.

I managed to read the text from the Log window so I can find out if there are any errors during reallocation and display it on RomTool.

[Guest Gary Crutcher]

Wes58,

Thank you for the new RomTool. It IS sweet!

Saves me a lot of mouse clicks.

[Guest HK.QooS]

i press [DUMP PDA] and [Run] it until Finish

i press [build PDA] Tab

i got a Error Msg: \XipTools\Xip\xip.bin not Found

and i check XipTools Folder , i just find a file call [Xip] inside and ~4MB

and i dont have a folder call XIP

i know SYS = OS , if i dont change OS version

i just want to try DMUP AND REPARK IT 1st

[Guest wes58]

i press [DUMP PDA] and [Run] it until Finish

i press [build PDA] Tab

i got a Error Msg: \XipTools\Xip\xip.bin not Found

and i check XipTools Folder , i just find a file call [Xip] inside and ~4MB

and i dont have a folder call XIP

i know SYS = OS , if i dont change OS version

i just want to try DMUP AND REPARK IT 1st

Versions prior to version 2, used xipOrg and xipNewOS_xxx folders in xiptools. Those folders were included in the full kitchen archive.

Since version to I decided to change them to XIP (that's where xip.bin is copied when you dump the rom) and XIP_XXXX (is the folder where you copy xip.bin from different version of OS).

It says so in the first post and also in the pdf file include in the archive version 2.

You replace XXXX with whatever number/text you want as long as the sys folder from the new os is called with the same numbers SYS_XXXX. For example WM version 23541 you put sys files in folder SYS_23541 and create a folder in xiptools for xip.bin (from new OS) XIP_23541.

To answer your question, I guess you also answered it yourself, saying that you don't have XIP folder. You have to create XIP folder in xiptools and then dump the rom again.

[Guest abdelrahim]

Thanks alot ...Now I will start cooking...THE FIRE is READY :P :(

[Guest Omnia 2 8000]

Thanks for the tool. Is there a way to change the XXEU CSC file to Canada based. I see that the CSC file contains the ImeiUK and when i look at it it has the settings for UK based Operators and I want to create a North American Based CSC file. How can do that? Please help me out.

[Guest wes58]

Thanks for the tool. Is there a way to change the XXEU CSC file to Canada based. I see that the CSC file contains the ImeiUK and when i look at it it has the settings for UK based Operators and I want to create a North American Based CSC file. How can do that? Please help me out.

The best way for you is to use Samsung Mobile Firmware Downloader from quattro formaggi and find a firmware with the csc for your country and use this csc file (you can change/delete some files if you want) with you current firmware.

You would have to find a csc with the RGS or BMC in the csc file name (for Canada) and you would have to search for a firmware in i8000L phone model.

After you dump files from the csc have a look in CSCConfig.reg and see what value you have for "CSC_Operator". If it is not equal to 0, it is set to some operator in you country, change it to 0 - I am not sure if this value is hardcoded in the csc header or not.

Have a look in CSCConfig.reg and CSCConfig.xml and delete some settings if you want.

[Guest wes58]

Some time ago people were asking how to backup the csc from your phone.

I have modified Samsung application (a quick fix to test it) to get the files from the CSC stored on the phone. Although this application does not backup complete csc file (as one file) at the moment, you can extract the csc files that are on your phone.

I did some more modifications since this morning and currently the whole csc can be extracted as one file with correct header. The files can then be extracted from this CSC using my application.

I will have to modify my application to build the file with the proper 'footer' (end of csc file which has to be added). I am not sure how many people are there who still have original csc file on the phone and want to back it up, but I thought I try to make it work.

If anybody would like to try/test it and let me know if it works it would be good.

How to do it:

1. Extract the archive on you PC and copy the folder csc_bak on your Main Storage (don't put on SD or "My Storage"!)

2. Run cscGetFiles.exe from you file exporer on the phone. It doesn't give you any information that is has completed but you can check the content of the csc_bak folder and BACKUP.CSC file should be there.

The csc file, BACKUP.CSC will be created in the csc_bak folder on your Main Storage.

3. After that you can extract files using my application and you will see if all the files are there.

It shouldn't cause any other problems ... but there is no guarantee!

Added updated archive

csc_bak.rar

Edited April 5, 2010 by wes58

[Guest sonblack]

My small donation for you: 94P417185P4348647 (LE HONG SON)

Keep up your good work!

Edited April 5, 2010 by sonblack

[Guest wes58]

My small donation for you: 94P417185P4348647 (LE HONG SON)

Keep up your good work!

Thanks a lot Sonblack for another donation.

[Guest rlai]

Hi Wes58, I got your tools working finally and was abel to re-generate a ROM. However, it doesn't seems I can make any change, I replaced the wince.nls on "ROM\XIP" folder and generate the ROM, it created a ROM with the old wince.nls (deleted already). (I decompose the newly created ROM and found the wince.nls is still the old one. Thus, it seems it is using wince.nls from somewhere else. Can you please advise which file I should replace? I searched on on the folder and it is the only wince.nls I can find.

[Guest sinancetinkaya]

Hey, when i try to use LZX Compression, The rom crashes on boot. I tried to change the cecompr.dll from lzx folder, but nothing changes. Can someone write here, how to use it?

edit:

ok. now its working. I replaced files from LZX to MODULES and its. ok.

Thanks;)

Wes's tool is working well, I tested it many times. I guess you've skipped a step from Wes's introduction.

cecompr_nt.dll > Tools folder (this one supports LZX compression for IMGFS)

LZX folder > XIPTools (LZX module for XIP)

ROM\imgfsLZX.src and imgfs.src > ROM folder

Are they correct ?

[Guest wes58]

Hi Wes58, I got your tools working finally and was abel to re-generate a ROM. However, it doesn't seems I can make any change, I replaced the wince.nls on "ROM\XIP" folder and generate the ROM, it created a ROM with the old wince.nls (deleted already). (I decompose the newly created ROM and found the wince.nls is still the old one. Thus, it seems it is using wince.nls from somewhere else. Can you please advise which file I should replace? I searched on on the folder and it is the only wince.nls I can find.

So, from what you wrote, I understand that you want to modify xip by replacing some files - wince.nls?

Xip dump that is in \ROM\XIP folder is not used for creating a new xip. It is only required for BuildOS to work.

To build the rom, after modifying/porting xip, xip.bin in \XIPTOOLS\XIP folder is used (and xip for new os, if you are porting it in \XIPTOOLS\XIP_XXXX) - which is only dumped to files/modules during build.

There are two ways that you can access the files/modules of xip (and replace manually the files that you want):

1. select 'MANUAL Realloc. of Modules' and you are porting new OS (you selected something else than [sYS] in Sys. list) . Otherwise I don't dump xip.bin into files.

2. or, select 'MANUAL Realloc. of Modules' and you select an option to delete one or more module from xip, or select LZX compression.

When Extreloc starts you will have \OUT folder in \XIPTOOLS. In this folder you will have dumped xip.bin files. You can change the files that you want, and run reallocation of xip and imgfs in Extreloc manually.

[Guest rlai]

Thanks wes58, playing with it :-)

So, from what you wrote, I understand that you want to modify xip by replacing some files - wince.nls?

Xip dump that is in \ROM\XIP folder is not used for creating a new xip. It is only required for BuildOS to work.

To build the rom, after modifying/porting xip, xip.bin in \XIPTOOLS\XIP folder is used (and xip for new os, if you are porting it in \XIPTOOLS\XIP_XXXX) - which is only dumped to files/modules during build.

......

[Guest rlai]

Hi wes58, need some help as it is first time trying to make my own ROM. I am assuming the program that work on XIP is the XIPPort and your program will use the XIP_Out.bin to generate the new ROM?

I am working on the XIPPort, however, I got LANGDB.txt missing when I trying to create XIP_Out.bin. I am able to create a XIP_Out.bin if I don't create module, however, it doesn't seems to change anything.

[Guest wes58]

Hi wes58, need some help as it is first time trying to make my own ROM. I am assuming the program that work on XIP is the XIPPort and your program will use the XIP_Out.bin to generate the new ROM?

I am working on the XIPPort, however, I got LANGDB.txt missing when I trying to create XIP_Out.bin. I am able to create a XIP_Out.bin if I don't create module, however, it doesn't seems to change anything.

When you dump xip.bin with xipport and then press "make pkgs", xip files/modules are split into packages. To make xip_out.bin you have to press "undo" to convert packages back to normal dump with files and modules. If you don't do that you will get the massage about missing langdb.txt file.

If you make any changes to xip files modules (adding a file with different size you may have to run reallocation.

I don't understand what you mean 'it doesn't seem to change anything'?

I am using xip_out bin (which I create during build) only if I make any changes to xip! Otherwise I don't care and leave existing xip which is part of xip.nb.

I you are trying to change some files in xip, you can only do it the way I wrote you before. I could make an option in my application to use either xip.bin or dump of xip.bin (files and modules) to create a new xip_out.bin, but so far I have never needed to do it (and nobody else needed this option either).

You could also create your xip_out.bin with xipport manually and insert to xip.nb with osnbtool (osnbtool -c xip.nb 1 xip_out.bin). Both files have to be in the same directory. Then you build the rom without making changes to xip, so my application will use xip.nb (with your inserted xip_out.bin). But I still think the better option is what I wrote previously.

[Guest rlai]

Thanks again. I mean it still use the "old" wince.nls when I generate the ROM, I believe it might have changed the file, didn't know ROMtools not using the xip_out.bin.

I tried use the method (2) above, however, it doesn't seems it use my own wince.nls. A few question if you can help

1) Will reloc change the files size of wince.nls? This is how I determine if it is the old one or new one.

2) If I do manual reloc, would romtools use the OUT folders or another files? What I did is to replace the wince.nls, then continue with reloc.

Thanks for the help.

I don't understand what you mean 'it doesn't seem to change anything'?

I am using xip_out bin (which I create during build) only if I make any changes to xip! Otherwise I don't care and leave existing xip which is part of xip.nb.

I you are trying to change some files in xip, you can only do it the way I wrote you before. I could make an option in my application to use either xip.bin or dump of xip.bin (files and modules) to create a new xip_out.bin, but so far I have never needed to do it (and nobody else needed this option either).

You could also create your xip_out.bin with xipport manually and insert to xip.nb with osnbtool (osnbtool -c xip.nb 1 xip_out.bin). Both files have to be in the same directory. Then you build the rom without making changes to xip, so my application will use xip.nb (with your inserted xip_out.bin). But I still think the better option is what I wrote previously.