I've dumped XIP of I780, and rebuild XIP by using 20940 xip.
Now, I found that the the XIP_Out.bin was larger than original xip.bin.
I just imported the xip_out.bin into 780.nb0.os.nb, and finally convernt it into flashable file. Then I found that the flashable file was 0.01Mb larger than the original flashable file. Well, I still flashed it, and found that the mobile stopped at the first screen.
Is there a way to make the xip_out.bin smaller? Or a someone can give me some instructions about rebuild xip for I780? Many Thanks.
Related
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!
Can Sombody Please Post a clean fast rom in OEM and SYS folder format, so that it is ready for cooking with as i cannot seem to find one that will extract with core's kitchen, all i can get to extract is the t-mobile ofical rom and this is far from clean
YuE v10 or v11 would be a good choice.
i second this, urgently - a plea to all cooks!!!
greetz
well i dumped the extraclean 10 but still i'm figuring out how to modify it
any advise?
y_bother said:
well i dumped the extraclean 10 but still i'm figuring out how to modify it
any advise?
Click to expand...
Click to collapse
I now trying to collect it all ;-)
Here is the tools, RRU and BuildRom.bat with Empty SYS OEM and ROM folders foryou chefs to fill with food needed to build a clean rom if this is of any help for testing purposes
http://rapidshare.com/files/149197230/Sys_Oem_Empty.rar.html
sleurhut said:
I now trying to collect it all ;-)
Click to expand...
Click to collapse
Please let us know how to do it when you have worked it out.
I have tried and when i came to build I just got errors with XIP and i also had missing files, os.nb.payload romhdr.bin
solved the os.nb.payload by renaming os.nb to os.nb.payload
copied the romhd.bin from artemis_diamondish
XIP errors with
Code:
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
ERROR: "XIP" dose not exist or it dose not contain any Modules!
I used extract xip in the core's kitchen and xip is in the ROM folder
Any ideas?
OK So now I just Copied XIP from Artemis_Diamondish and the rom builds
so how do i get the correct XIP For this Rom?
EDIT:
This plan didn't work
Anyone managed this yet
thanks
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.
I'm trying to port my Asus P565 (XDA Zest) to WM6.5. This is my first attempt at cooking a ROM and I'm a little stuck - I just can't get the device to boot after flashing.
These are the steps I have done so far:
1. Used p835abisplit2 to extract Original WM6.1 P565 ABI into os.nb0
2. Extracted XIP from os.nb0
3. Extracted imgfs dump from hdubli's 21231 ROM
4. Ported XIP using XIP Kitchen, original XIP as Device XIP, 23022 as Donor XIP & hdubli's 21231 .VM & .ROM folders
5. Padded XIP to original size using bPatch.exe
6. Copied SYS from 23022 into Vivi's P252 kitchen & rebuilt using BuildOS
7. Created imgfs.bin from dump folder
8. Merged XIP.bin back into os.nb0
9. Merged imgfs.bin back into os.nb0
10. Converted to .abi & flashed to device
And I can't get it to boot no matter what. As I said, I'm a n00b to cooking ROMs, so if someone could point out where I'm going wrong I would be eternally grateful!
Blade0rz said:
I'm trying to port my Asus P565 (XDA Zest) to WM6.5. This is my first attempt at cooking a ROM and I'm a little stuck - I just can't get the device to boot after flashing.
These are the steps I have done so far:
1. Used p835abisplit2 to extract Original WM6.1 P565 ABI into os.nb0
2. Extracted XIP from os.nb0
3. Extracted imgfs dump from hdubli's 21231 ROM
4. Ported XIP using XIP Kitchen, original XIP as Device XIP, 23022 as Donor XIP & hdubli's 21231 .VM & .ROM folders
5. Padded XIP to original size using bPatch.exe
6. Copied SYS from 23022 into Vivi's P252 kitchen & rebuilt using BuildOS
7. Created imgfs.bin from dump folder
8. Merged XIP.bin back into os.nb0
9. Merged imgfs.bin back into os.nb0
10. Converted to .abi & flashed to device
And I can't get it to boot no matter what. As I said, I'm a n00b to cooking ROMs, so if someone could point out where I'm going wrong I would be eternally grateful!
Click to expand...
Click to collapse
Use the original 6.1 abi to get OEM and SYS
USe the OEM and use 6.5 SYS from the builds here
Use the scripts which I have mentioned
u can get ROm to boot
hdubli said:
Use the original 6.1 abi to get OEM and SYS
USe the OEM and use 6.5 SYS from the builds here
Use the scripts which I have mentioned
u can get ROm to boot
Click to expand...
Click to collapse
What about P552w? Are the step same as P565?
And How to add the language packages into the list?
Because, It's not suitable to use ervius Kitchen to process Asus ROM
Oh, where could I get the hdubli's scripts?
Moreover... May I know the minimum file list in OEMMISC for making cleaner ROM?
i.e. without Youtube&Flickr, ClearVue PDF Viewer, Asus Today, Asus Launch!, EziMusic, EziPhoto and StreamingPlayer
I have copied OEM packages from 6.1 ROM & SYS from 6.5 ROM into Kitchen & built OS. Still nothing. Do I need to copy anything from new/old XIP into kitchen? Does anything else need to be done to XIP after I port it via XIP Kitchen? I took out hd.dll, osaxst0.dll, mencfilt.dll and cachefilt.dll as there wasn't enough space in the XIP - does this matter?
Also, I am using the .VM file from your ROM for G'Reloc.
I think I'm missing one crucial step somewhere
Nagato - I think P552w should be the same process, only using different SYS DPI. For languages you need the appropriate SYS files for your language from Da_G's thread here:
http://forum.xda-developers.com/showthread.php?t=544445
(See also Post #4 for how to integrate these)
The tools used are:
p835abisplit2.exe - To extract os.nb0 from .abi
osnbtool.exe - To extract IMGFS, XIP & ExtROM from os.nb0
XIP Kitchen - To port 6.1 XIP to 6.5
Does someone explain me how to make the porting of XIP of a new build for the trinity?
excuse me for my English
matlegro said:
Does someone explain me how to make the porting of XIP of a new build for the trinity?
excuse me for my English
Click to expand...
Click to collapse
It's extraordinary simple.
XIP is half OEMXIP and MSXIP. You always keep OEMXIP from your device.
OEMXIP is in ROM/TRINITY. Just copy the existing and rename copy with new build number. you have then for ex : 23017 (existing) and 23088 (new) but contents are identical
You only port MSXIP. For this, get the xip.bin. Then get Xipport, and extract all from xip.bin. then have a look in your existing XIP in kitchen in ROM\SHARED\21864\MSXIPKernel to keep only the files as shown in model. Then, you can add the new XIP, by adding a folder with n° of XIP (ex 23088) in ROM/SHARED and copying the extracted from xip.bin
So, it's just extract and copy files bascially.
brds,
nAr
Or even easier if you use ervius visual bepe kitchen: Copy the new xip to tools\xip.bin_new. Then start visualkitchen, open xipporterex and press "extract form payload" and "port it". If you are lucky, have a proper old payload and a proper new xip, this will import the new xip and build all folders for you.
ickebins said:
Or even easier if you use ervius visual bepe kitchen: Copy the new xip to tools\xip.bin_new. Then start visualkitchen, open xipporterex and press "extract form payload" and "port it". If you are lucky, have a proper old payload and a proper new xip, this will import the new xip and build all folders for you.
Click to expand...
Click to collapse
Very nice move, you smart, , lol, I use the kitchen only to dump roms and click da "Create rom" button ...
offtopic-BTW you tested my new 0407 release ? in da right thread -offtopic
brds,
nAr