Related
SYS PORTING GUIDE
Special thanks goes to Monsterfly for helpful guidance on porting SYS to a new build
Inventory:
Tools you will need for porting the SYS
BuildOS+Package Tool by Ervius
G’Reloc Tool by Misar
Procedure:
Use BuildOS+Package tool to dump ORIGINAL ROM and build packages
Copy G'Reloc to the folder where you have original SYS folder
Run it and write down numbers under slot 0, slot 1 and size of rom
Use BuildOS+Package tool again to dump DONOR ROM and build packages
Replace your original SYS folder with Donor's SYS
Run G'Reloc again
Notice that this time numbers under slot 0, slot 1 and size of rom may be different
Just replace them with numbers you got in the firt step
Click »Doit!« and wait till it shows "Done" in the status bar
Use the OEM folder in which you have added ingredients and the XIP fodler that you ported
Info: In some cases you will need to copy WinCENLS_WWE folder to SYS folder (if not present in Donor's SYS) from your original ElfIn SYS otherwise your device will not boot
Build OS in the kitchen of your choice and flash the new build ROM to your device and HAPPY COOKING
Timebomb solution and the boxed closed / ok button solution found here by HTCTouchp
[POLL][REF]*XIP & SYS Porting Guide*[ONLINE]
XIP Porting Guide (Based on Bepe's Buildxip.exe tool)
More detailed Porting guide on manual XIP Porting can be found here
I have added pictorials in .pdf format at the end of this post. Too many pictures so the .pdf file
Special thanks goes to Ervius for a lot of helpful guidance on porting XIP to a new build
Inventory:
Tools you will need for porting the XIP
BuildOS+Package Tool by Ervius
XIPPort Tool by Bepe
M’Reloc Tool by Misar
Procedure:
To make life more simple, I am attaching the XIP.bin extracted from Kaiser 19209 build ROM by Ervius. Dump the XIP.bin file with XIPPort tool and choose to make packages. Download from here (Rapidshare Folder)
In the OUT folder, ignore or delete all the text files (.txt) These files are created by XIPPort tool only to know the physical addresses and are not required for porting
In files and modules folders, delete all folders except “MSXIPKernel” and “MSXIPKernelTLK” The modules and files from these folders are the only items which are to be ported to make a new build. DO NOT copy or replace any files and modules from OEMXIPKernel, as these are device specific
Now open the BuildOS+Package tool and on packaging page click open with option to choose dump folder. Select your original ElfIn XIP folder (OS 19199) and on right you will see the XIP in its directory structure. Don’t click on build packages (you can’t do it anyways, as package.sof file is not present in the XIP folder) Instead click on “OEMXIPKernel” and then right click to select export package. Choose to save on different location, like your desktop. This is only temporary requirement, just to be on safe side that you still don’t replace any files or modules seen in that folder
Now you copy and replace the files and modules seen in the “MSXIPKernel” and “MSXIPKernelTLK” from the new XIP in your original XIP folder, you need to copy and replace only those items found in your original folders, do not add anything new. Now compare each and every .rgu file from your new XIP with your original XIP and check if they are similar (NOT the .rgu files in “OEMXIPKernel”)
After all the files and modules are replaced and .rgu files checked, run the M’Reloc tool and check the modules addresses from your original XIP with your new XIP (Don’t do anything to the modules located in “OEMXIPKernel”) The addresses have to be similar to your original modules from your original “MSXIPKernel” and “MSXIPKernelTLK” folders
Changing of addresses through M’Reloc is not required if you are using the BuildOS+Package tool for cooking ROMs as Ervius has already included the address relocation system into his tool with BuildXIP
In a nutshell you need to follow the following copying & replacement structure and everything will work:
Original XIP (19199): OEMXIPKernel
Donor XIP (19209): MSXIPKernel and MSXIPKernelTLK
Replace this new XIP folder in ROM in Bepe's WM6.1 Elfin kitchen and cook to get 19209 Build XIP, HAPPY COOKING
I have managed to put together a clean Base WM6.1 ROM for Elfin (Touch XL - 128/256) with almost everything removed except the most essential system packages
Please take note, this is a base rom for cooking and not to be directly flashed on the device as it may be unusable. You need to populate the ROM with your choice of packages and the essentials to bring it up to the 50MB limit for making it usable
Link to download the dumped Removed packages: Here
Special thanks to
Bepe for his wonderful kitchen
Noonski for his valuable comments and suggestion all the way
Kokotas for his help in getting rid of the cube
Download Bepe's WM6.1 Kitchen for ElfIn and replace the OEM and SYS folders with yours and cook the OS.nb file
The archived OEM package (dumped and packaged) can be downloaded here
DOWNLOAD HERE (V1)
UPDATE
DOWNLOAD HERE (V2) (Further stripped down OEMApps & OEM_Lang_0409)
20296 MSXIPKERNEL. Mix this with OEMXIPKERNEL and you are ready to cook. Do M'relocing if necessary
Download here: View attachment 108115
SYS archieve
A. The archived SYS package 19199 buid. DOWNLOAD HERE
Stripped to down basic required
B. SYS ported from 19209 Build. DOWNLOAD HERE (Rapidshare Folder) This archieve is from my new ROM (XIP and SYS Ported to new build) Removed packages as per above ist
C. 19588 Build ROM Dump (OEM, SYS & XIP) DOWNLOAD HERE. Thanks to Koko for sharing this archieve (SYS, OEM & XIP)
Hi Abrabekar,
You really came in the right time! I'm about to remove all the unnecessary apps inside Elfin original ROM and now you came with WM6.1
You really save my time, many thanks to you!
Cheers,
Vibranze
Deleted! Double post.
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
JohnQ said:
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
Click to expand...
Click to collapse
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
ababrekar said:
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Click to expand...
Click to collapse
vibranze said:
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
Click to expand...
Click to collapse
you need to populate the rom by adding your choice of packages. the essentials out the removed list would be phone dialer, commanager, bluetooth, netcf, audio manager. also you need to add files so the final cooked os.nb file is above 50mb limit
Don't Mind Vibranze he allready is running his own Rom...
Noonski said:
Don't Mind Vibranze he allready is running his own Rom...
Click to expand...
Click to collapse
i was answering his questions coz no question should go unanswered in my thread
I think it would be a good idea to post which kitchen you advice to cook the nb in.
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
canadian student said:
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
Click to expand...
Click to collapse
as i said, this is a bare naked base rom with all the packages removed for maximum user customisation. the packages removed are listed in my first post here
Noonski said:
I think it would be a good idea to post which kitchen you advice to cook the nb in.
Click to expand...
Click to collapse
good suggestion, like always brother i have updated the first post at the last line guiding to bepe's kitchen for cooking the nb file
(although i need bepe's or your guidance on how to get the exact same contents of his ROM folder from my ROM which can help everyone in achieving more customisation)
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Noonski said:
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Click to expand...
Click to collapse
even i'm looking for a way to get the exact contents of ROM folder what Bepe has in his kitchen for ElfIn. It contains XIP with a lot of other files. I wonder if having the os.nb.payload from my own rom would help rather than using bepe's file still waiting for a guidance
i am attaching the default.hv & user.hv files with the reg entries deleted as per the removed packages list. see if you can check and comment on it, it will be great
eagerly waiting for SuProCore
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Noonski said:
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Click to expand...
Click to collapse
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
ababrekar said:
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
Click to expand...
Click to collapse
Naah you really don't need to.
Those left behind registry settings ussually don't do any harm without the files present.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
well done ,thanks.
ivan i love you...lol just kidding silly goose but thanks a million
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
le_hades said:
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
Click to expand...
Click to collapse
You'd have to go through every file in the OEM folder and find every misdirected link (because of the different language) as well as replace every MUI. So in short, no it's not possible unless you have a LOT of time and want to work really hard. What I would do is just use any of the readily available Spanish Herald ROMs to obtain your OEM files.
mm this is a "fast" and dirty way:
If you use in.ex a 19199 build (0409 wwe)
you need to extract all mui files from 04xx (your langauge from another build, if you use wm6.1 you need to use mui from another wm6.1 build)
rename them from 04xx to 0409, replace all in you 19199 build with the new renamed ones
this can be done both in OEM and SYS
The thing is that i'd like to make a herald spanish 6.1 ROM but I can't find none to port on kaiser forums etc, so i was thinkong about alternatives
ivanmmj said:
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
Click to expand...
Click to collapse
Great job bro,
ivan you rock!!
I learn so much from reading your threads.
I think im almost ready to cook a rom.
I was wondering if you could be my mentor??
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 5.2.1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
homer285 said:
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
Click to expand...
Click to collapse
You ported the XIP AND the SYS folder?
Thanks for your reply, yes I did.
homer285 said:
Thanks for your reply, yes I did.
Click to expand...
Click to collapse
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
ivanmmj said:
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
Click to expand...
Click to collapse
yes Im using the Diskimage_Ver.nb0 from Atom in Rom folder, tried by hand and EasyPortOven same result, only build is porting not CE OS info. Perhaps I need a new XIP to try, anyway thanks for this great tool it really makes porting easy, seriously.
Edit: So the trick for me was the Atom needed porting directly, all modules must have address changed and then ported to diskimage_Ver via XIPPORT, drop into Kitchen/ROM folder along with everything mentioned here .
can anyone confirm if this works for the kaiser, and if it doesn't, what to use for the kaiser?
thanks in advance
I've heard that Keeping your original Device MetaData hive files isn't that important as the Hive Files get created.
But just to be on the Sure side.
When you put the Hive files from MetaData folder into the New Build from the Ported Sys.
Won't that make hive files with unneeded Reg entries?
instead of sticking with your original device Hive Files?
€dit: Wrong thread, sorry!
Drivers?
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
rajathvsm said:
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
Click to expand...
Click to collapse
Things have changed a lot since I wrote this... but:
The drivers are in the OEM folder (as well as most of the device specific stuff.)
You need the OEM, SYS and XIP in order to make ANY ROM.
You can move your OEM into your SYS but it makes it harder to port newer builds to your ROM later on.
You only need the .VM folder, not the .ROM folder. The kitchen will autoadjust itself.
Yep its been a long time... but is useful on old kitchens
I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP
Something about a platform rebuilder + oldschool buildOS hahaha
Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....
I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but
But now everything i install says certificates untrested... i instal sdkcerts and nothing happends
do you think i port the sys or xip wrong?
thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...
wm6.5 build 21812
I see alot of new roms using 19209 and even a 19588 rom on the forum. Could anyone please point me to the Sys Oem and Rom files if possible.
I have been using Octavoi 19199 to build a personal rom and I am now at the point where i am pretty happy with the stability of the rom but would like to update the XIP and Sys
Any help would be much appreciated
588 on the hermes forum. there is a whole kitchen just search their forums.
Thanks S.V.I. i found some kitchens. I also managed to extract the 19588 found here using Hypercore but i produce a rom which wont boot.
I have followed each extraction step. Any ideas why it wont boot ?
If you extracted the 588 that was already ported for the wizard, then I believe the os.nb is quite small.
Also, remeber that most cooks delete the rgu's to save space.
You may have added too many ingredients as well.
i Added exactly the same stuff that i use in my custom octaivoi rom except for what was already included. If I built the rom i get a 49mb OS.nb and the normal is about 57. I dropped all my OEM's except for registry tweaks and now i have a bootable rom.
Gonna try my luck at cleaning out the sys folder.
Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
maximumbs said:
Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
Click to expand...
Click to collapse
if you're using kaiserchef, just drop the diamond .nbh in BaseROM, then run RunMe.bat, then choose E, then B. I just did it and it worked fine, but if you only want to extract the SYS, I suggest making a temporary KaiserChef2 folder in order to keep the rest of your folders
maximumbs said:
Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
Click to expand...
Click to collapse
The key to making it work??? Use the relocation tools on all & any modules!
Sorry if I have a lot of question, I'm still learning, please bear with me . How do you use the relocation tools in KaiserChef? I noticed when buildos starts compiling the image it does a g'reloc. Is that the same? Does it mean that when you use the relocation tools, you can use the OS.NB and OS.NB.PAYLOAD from the actual diamond ROM?
Also, I can't seem to find any NBH for 20273 or higher roms. The only one I found is the OS.NB from 20273. Anything else is either just the XIP or SYS. Can anyone point me to a good ROM repository? I noticed 20721 is out but cannot find any source. Was it from the OMNIA? I pooked around but found that the OMNIA doesn't seem to use NBH unless the site I was reading was wrong.
Thanks for everyones patience on this. I really would love to cook and contribute back. Just taking a while as I am trying to get the hang of it.
Edit: Found the OMNIA ROM from the thread on this forum. D/L it now... and from what I am getting, I should be able to dump it using Kitchen from Diamond. Hopefully it is similar when it comes to porting the XIP and SYS.
Can anyone tell how to find the version of the XIP from say an NBH or extracted NB?
Thanks
Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks
As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,
Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"
Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.
Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.