Develop Bugs

Rom Modification (Cooking)

Hi everybody,
I would like to cook Artermis rom for my own Dopod P800W. How can I do this and what about the tools for rom modification? Please suggest me and put the link for download.
Thank you very much.

Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=310076

The steps that I am using
1. Select the ROM that you want that has nbh extenstion
2. use nbhtool to extract the .nbh rom to nb files. Remane the os.nb to RUU_signed.nb
3. use the above link to get the tool to extract the RUU_signed.nb. This tool will extract all files in the rom and put them in folders--->There is a word doc in there that tells you what to do. It is a bit cumbersome but just follow it you will be fine.
4. in Sys folder, remove or add the folder you want--becareful here because there are folder interdpendent to each other so make sure you know what to add or delete.
5. use the Core tool again to build the new os.nb file. Make sure you follow the procedure in the work doc...
6. To build the nbh rom to load back to your device you will need htcrt tools. Copy the new os.nb and other nb files to the htcrt folder--this is what I do. Then run the htcrt program to build the new nbh romfile.
I hope the above will help you. I am building my own rom currently by using some component from B&Bv3.7 and the official wm6 v3.7 as the touchflow ROM. I have been playing with the above tools for sometimes now but still do not know what exactly what is required in each folder yet. Hard but fun...hihi.
attached...nbhtools and htcrt...just to save you sometimes. The core kitchen is in the above link. All programs run in DOS mode, BTW.

Thank you very much, I will try to use it for my rom cooking.

RGU files in ROM, "ROM file" attribute

Hi all
I'm cooking my own rom using Core Pro Kitchen, so far it's going OK.
I read most of this forum and the WiKi, but still have a couple of questions
first:
Do we really need .rgu files in imgfs? AFAIK they are only used to build .hv files.
I tried to delete theese from \temp\dump before creating OS.nb (after running BuildOS), and the ROM works, at least I don't see any drawbacks.
second:
I'm cooking my own custom package into the rom and need all the files in it to be impossible to modify/delete. All files in the package have +r +s +h attributes set, but I'm sill able to modify them on device.
It seems like the modified file is created "above" the ROM one (sort of copy-on-write), because when I use TotalCommander to delete it, it just reverts to the original file from ROM. Is there anyway to make a file completely unmodifiable? Put it in XIP? do I have to rebuild any of three .dsm files in XIP if add my file there?
The file is about 1-2kb
Any ideas?
Thanks, Serge

Samsung i780 kitchen - release 0.2 BETA (New Version!)

PLEASE NOTICE THAT THIS KITCHEN IS A VERY EARLY BETA AS IT HAS NOT BEEN DEEPLY TESTED
*** USE IT AT YOUR OWN RISK! I ASSUME NO RESPONSIBILITY! ***
Hi guys,
after many days of testing I'm releasing my kitchen for i780.
It is very basic: no gui, only batch Windows scripts.
What you can do with this kitchen:
A) Convert your Part02.raw dumped rom to bin flashable PDA rom
B) Create a dump folder to cook your own rom and recreate a bin flashable PDA file.
Please notice that there's no tool included to edit, add or delete modules and files from rom dump.
You must use one of the tools available here in forum to do this or do this by hand.
Donwload the zip file and extract everything.
READ CAREFULLY THE README FILE IN THE ZIP ARCHIVE
This file explains how the procedures work and what you need.
PLEASE TEST THIS KITCHEN AND REPORT YOUR RESULTS
I thank chaimd for his bintonb0 tool, tadzio for his tools and Juggler for conv3 sourcecode.
I also thank Topogigi for his original procedure.
I modified conv3 tool to make it work with i780 rom files and made split and merge tools.
If you want to try this kitchen, I thank you!
[FONT=&quot]If any guru in the forum wants to make a gui for this kitchen or insert tools for module, file and registry editing (like the ones you can find in other kitchens), it would be appreciated.[/FONT]
Issue 1: it seems there's a problem with Part02.raw conversion. It screws up connection settings. Problem is being investigated.
[Partial solution]: it seems that this problem is due to both size and language: I used an English rom to convert an Italian Part02.raw.
Using an Italian rom seems to solve the problem. But you must check the new rom size: if it's too big it gets cut down and it doesn't work.
Version 0.2: this version contains a new conv3 release. This release it's a little bit more complicated than the previous one but it supports a wider variety of rom images and guarantees correct conversions. Previous release could lead to incorrect roms so you should consider it as deprecated.
For Issue 1, limitations are still the same: you should use a rom of the same language of the dump and mind the result size

this is just great

great job
great effort for the great device.
I will try for sure, thanks a lot

Recreate???
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!

mievalt said:
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!
Click to expand...
Click to collapse
You must read the PDF file in the kitchen directory. Some parameters may change according to the ROME used

Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze

vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
you need flashable pda part file for convert,
like XHD1 pda file (you can find in this forum).

vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM

Hi Eunjea & Webise,
Thanks for the explanation.
My current stock ROM is D1 and how to convert it to .bin format if I want to use mine?
Actually I always use English ROM and replace the wince.nls and add some fonts to support Chinese reading
Btw, how do I know what is the value for first jump, footer start and footer checksum address? In the PDF, the first jump address is on 444400 and in my bintonb0.txt I also have 444400, can I follow the same address?
Cheers,
Vibranze
webise said:
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM
Click to expand...
Click to collapse

I just want to backup my ROM which is built by my operator so that if I have problems with the upgrade I can always go back to my original ROM.
How can I create the bin files for te part 1 and 3?

Can anyone advise, as there is no bin file for the Omnia this kitchen will not be compatible, right? Or is there a way to create one?

I managed to dump an Dutch rom, version E1.. Could you explain how I can make a flashable image for the complete rom and/or how to make a radio rom from the three parts I dumped?
Furthermore, i have had some issues when I dumped the rom with the instructions that were in the readme.pdf.
There are some connection problems, that the originally phone doesnt have..when I flashed my rom, there werent any connection settings visible. e.g. settings > connections > connections > advanced > select networks, here was nothing visible.
It seems a bit like the same problem that people had with the english dumped E1 rom. Is there a chance that certain files from the raw files werent correctly put in the i780_flashable.bin (final product) ?

Is this the latest version of famusc's kitchen?

Reconstructing factory dumped rom

I wanted to build an nbh of my stock rom to have for warranty purposes. Yes I know you can download these, but I wanted to build it myself.
I've dumped the original rom with pdocread and have the 4 parts. From what I've read you need to have a base RUU_signed.nbh to reconstruct the rom with a kitchen.
What does the RUU_signed.nbh have that the 4 dumped parts don't.? It doesn't make sense that I can't just compile the 4 parts back into an nbh file.
Am I going to have a 100% factory rom when I reconstruct with the RUU_signed.nbh?

I used Calkulin's Kitchen to make a rom folder from the RUU_signed.nbh file. The difference in the OS.nb.payload and the part02.raw file is 8MB. Supposedly when cooking the rom it merges the imgfs from part02.raw over that part in the OS.nb.payload file. Does anybody know what is in that 8mb that can't be recreated from the dump?

rsw686 said:
I used Calkulin's Kitchen to make a rom folder from the RUU_signed.nbh file. The difference in the OS.nb.payload and the part02.raw file is 8MB. Supposedly when cooking the rom it merges the imgfs from part02.raw over that part in the OS.nb.payload file. Does anybody know what is in that 8mb that can't be recreated from the dump?
Click to expand...
Click to collapse
I've noticed the ROM Version (under Device Information) and the startup date (during screen calibration) are no longer the same as original. But you can go into the kitchen files and change the ROM Version in the registry and re-cook it. Don't know how to change the bootup date though.

New Asus/Garmin Asus abi ROM tool for full ROM customization!

I made a tool p835abisplit2 previously for ROM rebuilding, however that tool only fully works for P565 and earlier devices, which has many limitations for P835 and newer devices. So now I rewrite it to have full functions!
Applicable Devices:
- Asus P835
- Garmin Asus M20, M10
Usage:
- Decompiling ROM
1. p835abisplit3 <abi/exe file>
2. If input is an exe file, then a decrypted abi file will be extracted, which can be used with the Asus internal flash tool (Not available here)
3. 13 files are extracted, content on each file is explained in their file names
3.1 txt file is the partition definition, you can customize the abi by editing this file
3.2 OS file is in B000FF format. Use osnbtool -sp twice to get a correct nb file
3.3 EXTROM is a standard FAT Image, you can open and modify directly with WinImage
- Rebuilding ROM
1. Modify txt file as you need (Optional)
2. Rename updated file to their original names
2.1 For building OS file, use osnbtool -extra os.nb 0x8 and osnbtool -2bin -CutHeader
3. p835abisplit3 /b <abi/exe file>
4. out.abi is created, which can be used with the Asus internal flash tool (Not available here)
5. If input file is an exe file, out.enc (Encrypted abi) and out.exe (Flash utility with updated ROM and region patch)
- Warning
1. This tool now is too powerful that you can easily brick your device if you modify the txt file incorrectly, so take care! (However it is proved to work by hdubli)
2. This tool is checked to create identical abi file if you rebuild without touching anything. If this is not the case with your base ROM, don't continue cooking and let me know!
** Please note that if you modify the partition layout, the length of text must be < 24 bytes **
If this post is left too long without updates, you can check new versions at http://www.studiokuma.com/tools/?section=misc-e

Great job, man!
If you can update the tool for extracting the Acer ROMs that can be used for extracting NeoTouch S200's ROMs of version 3.xxx, that'll be excellent!!!

aa125690 said:
Great job, man!
If you can update the tool for extracting the Acer ROMs that can be used for extracting NeoTouch S200's ROMs of version 3.xxx, that'll be excellent!!!
Click to expand...
Click to collapse
See here:
http://forum.xda-developers.com/showthread.php?t=631207

EXTROM from P835
Great tool, but there is still one backlog. As tool still cant directly extract extrom resp.ASUS_ROM from P835 (its working pretty well with M10,M20,P565). Even at the end is extrom located in os.nb0. After such impementation it will be perfect tool

No, don't trust the tools reports the FATFS at last partition of os.nb0. It is a dummy partition in all new ROMs from any vendor.
As I can tell from the G5 abi, there is no extrom in it.

EXTROM from P835
You are partially right as HKEY_LOCAL_MACHINE\System\StorageManager\Profiles doesnt contains any usual ext partition.
But how you explain that standard EXTROM files are parts of OS.NB0 ?
Isnt so usual that those EXT files are part of main image. These are typical extrom file, see what I extracted :
P835 is bit specific, as not contains just dummy file for extrom package.
And one more question regarding P835, as you probably know there is problem with relatively small ROM space.
Even I removed lot of crap files, ROM image is still showing same size. Pdocread is showing total 200MB on DSK1.
But available is only 97.18MB.

Anyone cooking for the M10?

Works on M20 Rom Thai version.
Also, where can I find Asus internal flash tool?
efe

asus m20 cook rom
Thanks for your good tool, I am now cooking a rom of asus m20 and I have been successed to work out a file called "flash.bin" final, would you please tell me how to do to make it change to say "m20.exe". Or do you have any suggestion eg. use bootloader. Thank you very much. I really need your help.

Firstly, your ROM needs to be extracted by a exe file instead of abi file first.
When you need to build exe file, use the /b switch.
Extract: p835abisplit3 xyz.exe
Build: p835abisplit3 /b xyz.exe
Then out.exe will be the new flash utility with your changes and region lock patched.

starkwong said:
Firstly, your ROM needs to be extracted by a exe file instead of abi file first.
When you need to build exe file, use the /b switch.
Extract: p835abisplit3 xyz.exe
Build: p835abisplit3 /b xyz.exe
Then out.exe will be the new flash utility with your changes and region lock patched.
Click to expand...
Click to collapse
Thanks for your answer, I still meet problem even I use your method, so let me give more detail as follow:
1. I have split the xyz.exe with your tool and a xyz.abi and 13 more files extracted.
2. And I also use some kitchen to make a new rom file called flash.bin.
3. I rename "flash.bin" to "Os.bin" (one of the 13 files)
4. Lastly, I follow your instruction to build ie. p835abispilt3 /b xyz.exe, a out.abi will come out
So, how should I do to change this "flash.bin" to become the xyz.exe for flashing. Your help should be most appreiate. Thanks

my asus m20 device is bricked, any idea? Please help

Jtag
Does anyone have experience with jtag on P835 ?
Or is there any other way how to recover dead bootloader on MSM Asus devices ?

i can't open p835abisplit3.exe
how can i open

M930
Hi Stark Wong,
please could you modify p835abisplit3.exe in order to correctly work with M930 ?
See error message :

I have updated the tool to support longer string, that should fix your issue.
Download it in first post.
To others: You must have the original EXE to form output exe. Just pass the EXE when building, it will read the new ABI and generate a new EXE file. You can't generate EXE when you only get the ABI file.

Thanks
Thanks a lot for fix.
Note that even you will incorretly use this tool, nearly always is way how to recover.
See : http://forum.xda-developers.com/showthread.php?t=722951