Related
How Can I extract XIP from universal ROM?
I would like to improve the Bepe's Kitchen for Universal.
Thank's in advance.
I use RomMaster and dumprom after prepare_imgfs and viewimgfs to extract XIP in Universal.
If you want I can give you the the script that I modified from Anichillus kitchen.
Cheers,
Yes I want.
Thank's very mutch.
If you want you can send me all the Anichilus Kitchen modified for Universal.
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Why not ?
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, because for me use m'reloc is useless.
Click to expand...
Click to collapse
ervius, you doesn't use m'reloc when you port xip ?
can you tell me which XIPPort is the last one because Bepe doesn't make release number...
The procedure you're using is :
- Dump the xip.bin
- Make Pkgs
- Replace the new modules
- Undo
- Realloc P
- Build xip_out.bin
Thanks for your help
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Click to expand...
Click to collapse
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
peter petrelli said:
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
Click to expand...
Click to collapse
you need m'reloc for nothing.
all xipport process is based on imageinfo.txt files, while m'reloc changes module values on imageinfo.bin (and xipport ignore thatr file in module, in realloc P and in write Map.txt), bwt, I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt.
and to confirm all I hex edited xipport.exe, and it only writes imageinfo.bin, while dump xip.bin, never read imageinfo.bin to check values inside., try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin, realloc P, write map, write new xip.bin, insert into payload and flash rom, it starts normally...., xipport not need imageinfo.bin, and doesn't use them.
ervius said:
.. xipport not need imageinfo.bin, and doesn't use them.
Click to expand...
Click to collapse
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
mun_rus said:
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
Click to expand...
Click to collapse
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
ervius said:
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
Click to expand...
Click to collapse
Can you share your XIPPort release please ervius ?
MickyMax said:
Can you share your XIPPort release please ervius ?
Click to expand...
Click to collapse
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
ervius said:
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
Click to expand...
Click to collapse
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
MickyMax said:
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
Click to expand...
Click to collapse
bo problem, I use this release and xiptools to realloc better all modules into xip...
bye!
Big thanks ervius !
ervius said:
try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin
Click to expand...
Click to collapse
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
tjkhattak61 said:
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
Click to expand...
Click to collapse
you have to use xiptools with imageinfo.bin...
after, when finish, before realloc P and build Map, and build xip_out.bin, delete all imageinfo.bin, xip_out.bin will be created successfull, like all imageinfo.bin were inside all modules...
P.S.: is bit difficult use the xip_tools, but when you understood how it works, is easiest port xip... thanks to the author...
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?
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
You may want to have a look at ababrekars SYS and XIP porting guide in Elf section....
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
2. Just replace the wince.nls version in the SYS\WINCENLS_WWE with the CHS one you have.
3. Modify all the MUI files and registry as to point to your Language of choice.
4. The OS.NB is needed as the shell/container for your new cooked ROM because it's the requirement for using the Tadzio's tools. So, leave it as is.
5. Cook the ROM.
At least that what I did when doing my Hermes version long before.
Cyphol.
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
please correct me if i was wrong..
afaik, XIP part is the same for every language,
also in the end part of the building, you need os.nb only as a "template" to rebuild the new one... it wasn't really use the content inside...
normally, you need to copy all content in the dump_xip to the ROM\XIP directory...
to learn about the process of diamond kitchen (which is based on kaiser kitchen so i assume the tools are the same), i think you better use the kaiser ROM, and try to dump it.. and see what directories and files are generated...
in kaiser kitchen, to rebuild the rom you need 3 dirs, OEM, SYS, and ROM\XIP
cyphol said:
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
Click to expand...
Click to collapse
He would need to if he wants a different OS build. Or am I wrong?
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
of course....
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
Yes, that's right for the reason. If that's the only reason, why don't you replace the core.dll
thank you everyone for your advise.
looks like i just need more reading.
thank you cyphol, pkoper and teamee for your kind advice.
I have replace the SYS\wincenls_WWE folder with SYS\WINCENLS_0804. i believe this might be one of the problems. i will try replacing just the wince.nls within the folder instead of replacing the entire folder.
files which i have modified includes the boot.hv, user.hv, default.hv, boot.rgu, a bunch of other rgu as well. i might have missed out a few others. so i will check again.
thanks everyone for your kind advice. if there is any other suggestions or points to take note of, please kindly let me know.
your guys rocks! XDA rocks!
Hi
i have cooked my own rom im July and then I delete the hole Kitchen Folder. Is it possible to restore the Kitchen and included packages from my nbh file?
10x
Yes you can do that.
Here you can find a great guide on how to dump a rom.
Good luck!