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.
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
WHy are you using itsutils to dump the ROM. Just extract the .exe rename it to RUU_signed.nbh and dump it using the kitchen....
Much easier and more fool proof this way.
joerf1115 said:
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
Click to expand...
Click to collapse
Sounds like youve done more work than nessessary! Do like ryncppr said above, use the lastest pagepool patcher to change version number on boot. Don't know why you would want to though!
thank you ryncppr and yardie.spike.. That was just a small issue i wanted to change but the main issue is that the rom created from the kaiser kitchen is WM6 and not the new OS. What am I doing wrong?
[Cooking] Need Help Clearing out the bloatware
ok I solved the issue with the rom being WM6 and not 6.1. I just deleted the ROM, OEM and SYS folders and the os-NEW.nb file. Then I extracted the rom I dumped from the phone and I can now cook a 6.1 rom. BUT the issue I have now is all the bloatware is on there still with the software I selected during the cooking process. How can I remove all the software that came with the ATT rom?
[EDIT] Okay I have been messing around in the OEM, SYS and ROM folders...Is this the right place to remove the oem software and if so how do I go about doing it. I found, in the OEM folder, the EXEs for the shop stuff...can i just remove those or are there othere files I need to edit as well...pls help I just want to learn
OK for those wanting to cook their own rom from the ground up, below is a link to help with cleaning up the BaseROM.
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks
go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.
Yep, looks like you didn't set it to Herald when you built it.
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?
Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.
After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks
Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.
I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help
Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.
The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.
The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.
working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.
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.
What is XIP and how i can update it in my custom ROM, my ROM its based on the official ROM for Kaiser but... its a Spanish one , (so i dont know if i can use XIP from ROMs in English).
Regards!
you can use English XIP's, but first, what kitchen are you using?
thanks for the reply, always you are there in any rom post =), i am using kaiserkitchen_01-20-08 software, this its the readme i dont know where on the whole site i get it, but work like a charm...
Code:
Kaiser ROM Kitchen - version 0.3 - now with rebuilding dumped ROM support
by jcespi2005 and jugglerlkr from xda-developers.com
Welcome to ROM Kitchen for HTC Kaiser and compatible devices (to name a few - HTC Tytn II, P4550, Kaiser, AT&T Tilt (8925), MDA Vario III, Orange Tytn II, SFR V1655 etc.)
We take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from xda-developers wiki. To install kitchen you will need password - you will find it later in this guide. Please install kitchen to root folder - C:\, D:\ or whatever you like. It is rquired because of filesystem limitaion on long filepaths and filenames.
Do not forget to backup your original ROM and all important files, infomation, settings etc with your favorite backup software!
Kaiser ROM Kitchen has been created using tools and knowledge of many people (in alphabetical order):
bepe
dark simpson
itsme
jcespi2005
jugglerlkr
mamaich
pof
tadzio
theblasphemer
and many others we forgot to mention...
XP SP2 or Vista with MS .NET Framework required to use it.
To use ROMs you cook with this kitchen first you have to CID unlock your device using HardSPL (kaiser-HardSPLv1 included in package). You can read more about this tool and download latest verion here:
http://forum.xda-developers.com/showthread.php?t=334679
Also you need some base ROM for kitchen to work. After installing Kaier ROM Kitchen put file RUU_signed.nbh to BaseRom folder! You can get some ROMs and info how to flash them here:
http://forum.xda-developers.com/showthread.php?t=332246
To extract RUU_signed.nbh from WWE "shipped" ROM for example, just unpack .exe file with winrar, you'll find some files including the RUU_signed.nbh. Put it to BaseROM folder. Do not delete it from there, it required for the whole process and future modifications of ROM.
Now you have to decide what do you want to do, just cook BaseROM the way you want it, or rebuild dumped ROM.
If you want to rebuild dumped ROM you have to put Part01.raw and Part02.raw into BaseROM folder. For more information how to dump ROM go here:
http://forum.xda-developers.com/showthread.php?t=334680
Tools required to dump ROM (just in case) http://www.xs4all.nl/~itsme/projects/xda/tools.html
When you have prepared your device, installed kitchen and placed necessary files to BaseROM folder you can start using it.
Just click on !Begin.cmd and follow onscreen prompts. This script will prepare all files for future cooking.
When !BEGIN script exits successfully you may want to add/delete some packages, do registry changes, apply fixes etc. This what kitchen is for, cooking ROMs ;-) OEM and SYS folders are result of previuos 1-7 scripts. When you finish cooking continue to make your newly cooked ROM flashed to your device for testing and distribution.
Now OEM and SYS folders are modifed to your needs, ROM is ready to be cooked and flashed.
To cook ROM Clock on !Cook.cmd script and follow it to HTC ROM Tool part. If HTC ROM Tool part just follow onscreen instructions on how to use HTC ROM Tool. You can read more about it and find latest version here:
http://forum.xda-developers.com/showthread.php?t=311909
If everything worked as it should - you have result of your work: RUU_signed.nbh. It can be flashed to device using Kaiser Custom RUU (included in package), latest version can be found here:
http://forum.xda-developers.com/showthread.php?t=334890
Click on !FLASH.cmd to flash new ROM to your device. Follow onscreen instructions.
Warning: resulted RUU_signed.nbh will contain only OS - no radio, spl and splash - this is done by design!
When you need to update your ROM with latest modifications you made in OEM, SYS and ROM folders just click on !COOK.cmd script to insert all changes you made in OEM & SYS folders into resulted RUU_signed.nbh.
Remeber: if you start from !BEGIN.cmd you will ruin all your work!!!
P a s s w o r d to install Kaiser ROM Kitchen is "resiak" (without quotes).
version history:
version 0.3 - some more automation, now you don't have to click on every script; added rebuilding rom option
version 0.2 - minor cosmetic issues and fixes, better handling of RUU_signed.nbh and XIP dumping
version 0.1 - initial public release
also, like i say in the frist post i use a HTC TYTN II Spanish Official ROM, extracted and recooked with that kitchen and OEM packages and files from everywhere....
So i can use superior XIP from other similar device ROM?, do i need replace the SIS folder also? regards!
wolframio74 said:
thanks for the reply, always you are there in any rom post =), i am using kaiserkitchen_01-20-08 software, this its the readme i dont know where on the whole site i get it, but work like a charm...
Code:
Kaiser ROM Kitchen - version 0.3 - now with rebuilding dumped ROM support
by jcespi2005 and jugglerlkr from xda-developers.com
Welcome to ROM Kitchen for HTC Kaiser and compatible devices (to name a few - HTC Tytn II, P4550, Kaiser, AT&T Tilt (8925), MDA Vario III, Orange Tytn II, SFR V1655 etc.)
We take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from xda-developers wiki. To install kitchen you will need password - you will find it later in this guide. Please install kitchen to root folder - C:\, D:\ or whatever you like. It is rquired because of filesystem limitaion on long filepaths and filenames.
Do not forget to backup your original ROM and all important files, infomation, settings etc with your favorite backup software!
Kaiser ROM Kitchen has been created using tools and knowledge of many people (in alphabetical order):
bepe
dark simpson
itsme
jcespi2005
jugglerlkr
mamaich
pof
tadzio
theblasphemer
and many others we forgot to mention...
XP SP2 or Vista with MS .NET Framework required to use it.
To use ROMs you cook with this kitchen first you have to CID unlock your device using HardSPL (kaiser-HardSPLv1 included in package). You can read more about this tool and download latest verion here:
http://forum.xda-developers.com/showthread.php?t=334679
Also you need some base ROM for kitchen to work. After installing Kaier ROM Kitchen put file RUU_signed.nbh to BaseRom folder! You can get some ROMs and info how to flash them here:
http://forum.xda-developers.com/showthread.php?t=332246
To extract RUU_signed.nbh from WWE "shipped" ROM for example, just unpack .exe file with winrar, you'll find some files including the RUU_signed.nbh. Put it to BaseROM folder. Do not delete it from there, it required for the whole process and future modifications of ROM.
Now you have to decide what do you want to do, just cook BaseROM the way you want it, or rebuild dumped ROM.
If you want to rebuild dumped ROM you have to put Part01.raw and Part02.raw into BaseROM folder. For more information how to dump ROM go here:
http://forum.xda-developers.com/showthread.php?t=334680
Tools required to dump ROM (just in case) http://www.xs4all.nl/~itsme/projects/xda/tools.html
When you have prepared your device, installed kitchen and placed necessary files to BaseROM folder you can start using it.
Just click on !Begin.cmd and follow onscreen prompts. This script will prepare all files for future cooking.
When !BEGIN script exits successfully you may want to add/delete some packages, do registry changes, apply fixes etc. This what kitchen is for, cooking ROMs ;-) OEM and SYS folders are result of previuos 1-7 scripts. When you finish cooking continue to make your newly cooked ROM flashed to your device for testing and distribution.
Now OEM and SYS folders are modifed to your needs, ROM is ready to be cooked and flashed.
To cook ROM Clock on !Cook.cmd script and follow it to HTC ROM Tool part. If HTC ROM Tool part just follow onscreen instructions on how to use HTC ROM Tool. You can read more about it and find latest version here:
http://forum.xda-developers.com/showthread.php?t=311909
If everything worked as it should - you have result of your work: RUU_signed.nbh. It can be flashed to device using Kaiser Custom RUU (included in package), latest version can be found here:
http://forum.xda-developers.com/showthread.php?t=334890
Click on !FLASH.cmd to flash new ROM to your device. Follow onscreen instructions.
Warning: resulted RUU_signed.nbh will contain only OS - no radio, spl and splash - this is done by design!
When you need to update your ROM with latest modifications you made in OEM, SYS and ROM folders just click on !COOK.cmd script to insert all changes you made in OEM & SYS folders into resulted RUU_signed.nbh.
Remeber: if you start from !BEGIN.cmd you will ruin all your work!!!
P a s s w o r d to install Kaiser ROM Kitchen is "resiak" (without quotes).
version history:
version 0.3 - some more automation, now you don't have to click on every script; added rebuilding rom option
version 0.2 - minor cosmetic issues and fixes, better handling of RUU_signed.nbh and XIP dumping
version 0.1 - initial public release
also, like i say in the frist post i use a HTC TYTN II Spanish Official ROM, extracted and recooked with that kitchen and OEM packages and files from everywhere....
So i can use superior XIP from other similar device ROM?, do i need replace the SIS folder also? regards!
Click to expand...
Click to collapse
Hi, you will need to use a xip similar or close build number than what your currently using.. some xip's will work with the sys your using and some will not.. u'll need to test individually and find compatible ones that boot.. i suggest using something called easyportoven i think it works for kaiser.. or if u're looking to learn porting xip u'll want to head over to dev and hacking forums and look at the xip porting tutorial.. i'm gonna be putting one together soon but it's for the new type kitchen from bepe, i don't think it would work with yours.. anyway.. peace and good luck.