Related
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="]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?
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
tomme45i said:
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
Click to expand...
Click to collapse
You can do that from the kitchen. I know ervius kitchen has two dialog boxes on the left, sort of middle of the screen, where you can set ROM date and version. It will patch the nk.exe accordingly.
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
P.S.: Sorry tomme, don't really read the Trinity threads anymore. But I will take a look every now and then, promise!
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
tomme45i said:
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
Click to expand...
Click to collapse
That's because of the nk.exe that has already been patched. Try another nk.exe or an older buildOS.
tnyynt said:
Try another nk.exe or an older buildOS.
Click to expand...
Click to collapse
I try on PkgToolsBuildos 4.2b3 and on 4.3b1. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
tomme45i said:
I try on PkgToolsBuildos 4.3b1 and on 4.3b3. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
Click to expand...
Click to collapse
Try with this one.
tnyynt said:
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
Click to expand...
Click to collapse
it can be changed, it's just a hardcoded MOV instruction in assembly
tnyynt said:
Try with this one.
Click to expand...
Click to collapse
tnyynt thank you for you answer, but even on older version situation is the same. Program always overwrite 1st digit. Here is screenshot from older version buildos+package_tools-4.1b1:
You can't change the first digit in ROM version, no matter which nk.exe you try to change.
On the old nk.exe (the one used to fix the losing password bug for some users) you'll always have 0. before whatever you want your ROM version to be.
On the newer nk.exe you'll always have 3. before whatever you want your ROM version to be.
That's something you just can't change, because it's an hardcoded value and this was the reason why my ROMs for trinity were 3.something (because when I started cooking I was using the newer nk.exe) and even after changing to the old nk.exe (to solve the losing password bug for some users - a problem I never had in my device), I had to start numbering my ROM as 0.3.something.
My advice:
If you don't have the password bug with your device, and are not planning on releasing the ROM, use the newer nk.exe and number your ROM 3.1.0, and forget about the 3..
The ROM version in Device Info is a completely different thing. That value is not hardcoded anywhere, and since it's a registry value, you can put whatever you wish and it will display properly.
In conclusion, if you're using the PkgToolsBuildos (doesn't really matter which version you're using) to change the ROM version (and this is responsible only for the value that appears on the boot screen), leave the left field as it is, and change only the right field to what you want and save changes.
I hope this will clear your doubts about this. Happy cooking!!
I don't know the difference between this two version of NK.exe so FInixNOver thank you for explanation!
I release my roms on polish forum. First nine was based on old NK.exe, so the last was 0.9. Now when I try new NK.exe I was surprised that my rom version in boot is starting from 3.
BTW. I think only first digit is hardcoded, cause I can change dot symbol by hex editing S000 file.
One more time FInixNOver thank you for your reply!
FInixNOver said:
That's something you just can't change, because it's an hardcoded value
Click to expand...
Click to collapse
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
cmonex said:
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
Click to expand...
Click to collapse
I stand corrected. I just said that because I was never able to change that value. So if you say it's possible, even better!!
Hi all! Is there any way to flash nordic ROM with samsung upgrader that you can download from http://www.samsungmobile.com/support/i780/index.jsp? I'm currently using DXIB1 and when I try to flash XBHK2 it says that I have wrong PDA version. I already played with HEX editor and managed to pass version check but after that XBHK2 get's stuck in the 3rd file. Any help with that? Of course if some of you have flashable PDA bin from nordic ROM then please share it with us!
Thanks in advance
Ok it's flashing now. I made some changes in HEX editor and it seems that all you have to do is to change i780XB to i780DX from the bottom of the file. Sorry for bothering you all.
Hi I have a question and I've been unable to find an answer. If I build / cook a rom, is there any way to turn the .nbh file back into a state where you can modify / edit the files inside the rom so you can re-cook ?
Hi,
can someone explain to me how I can add or replace a file in a nbh file so I can flash it to my device ?
I am not a cook, but only want to customize existing roms to my own needs so I can install my cabs during install and need for instance to add the sdconfig.txt
I did several searches, but did not found what I was looking for.
So I hope someone can guide me here with a little help.
I was looking for the same but peoples told me its not so easy like we think because 1st you need to Dump the ROM extract it then edit it and make it again in nbh pack to be flashed also mostly the coocked rom`s are locked this mean its not posible to edit them.
tsalta said:
I was looking for the same but peoples told me its not so easy like we think because 1st you need to Dump the ROM extract it then edit it and make it again in nbh pack to be flashed also mostly the coocked rom`s are locked this mean its not posible to edit them.
Click to expand...
Click to collapse
There is an app around that lets you do exactly what you're looking to do. I don't remember what it's called but it definitely does exist. Keep looking and if I find it I'll post a link here.
EDIT::: Here it is - http://forum.xda-developers.com/attachment.php?attachmentid=159179&d=1235143207