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.
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.
OK, so burn me if you'd like but for the past year or so everyone has been porting the Kaiser SYS and XIP to their devices... but with the recent release of the Diamond, Xperia and TouchPro builds it seems like us Kaiser users want to Port too!!!! So here is my problem
I am having issues right now for some reason as I am \porting the SYS from the Touch DIamond ROm. OS,OSFiles, Shell, .VM, changing the .VM with G'Reloc but for some reason the build # is not changing....WHY I HAVE NO IDEA
In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.
I also have used BuildOS+packageTools4.b3 in order to do a XIP port??? I am clueless. I used to do this no problem but for some reason it is not working now???
bayfoco said:
do drop by to www.ebayfoco.com look through the articles there. With information on anything from getting the you like products,
Click to expand...
Click to collapse
enough of this bot already, he was in the development and hacking section as well
mbarvian said:
enough of this bot already, he was in the development and hacking section as well
Click to expand...
Click to collapse
Not anymore. Banned for spam.
P1Tater said:
Not anymore. Banned for spam.
Click to expand...
Click to collapse
thanks, I guess you need a reason to ban
ryncppr said:
In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.
Click to expand...
Click to collapse
why are you only bringing over those parts of SYS? take it all.
oh, and replace *DPI_192* from new source with *DPI_96* from kaiser original.
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....
I'll try once more before I whip my computer across the room
ryncppr said:
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....
I'll try once more before I whip my computer across the room
Click to expand...
Click to collapse
if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.
also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.
oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.
i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!
The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???
Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?
dcd1182 said:
if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.
also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.
oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.
i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously
Click to expand...
Click to collapse
I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.
ryncppr said:
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!
The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???
Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?
Click to expand...
Click to collapse
welcomehead.96 is in sys.
lennysh said:
I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.
Click to expand...
Click to collapse
SO you only ported the .VM? That isn't really a SYS port then is it?
ryncppr said:
SO you only ported the .VM? That isn't really a SYS port then is it?
Click to expand...
Click to collapse
Lol...
I think you took my statement backwards... Ported the entire SYS, all except the .VM. I have four devices all running Build 20270.
Let me rephrase so it's not twisted, they are all four running CE OS 5.2.20270 (Build 20270.1.3.1)
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.
Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?
I am using the KaiserKitchen to dump my rom. THough I had to rebuild my XIP and separate OEM and SYS for some reason...
I am dying for someone to update the Kitchen for the Kaiser. I am not familar with writting .bat files or I would try.
There is alot of newer programs that need to be implemented into the Kitchen
BuildOS+PackageTool is now 4.b3
HTCTool is newer
PackageTools is newer
I sent a PM to several master chefs but have not heard anything back....
The way that I ported the SYS is as follows....
1st, I dumped both ROMS I want to use. I name the folders accordingly on my C:/ Drive.... KaiserKitchen_BUILD and KaiserKitchen_TOUCHPRO (example)
After dumping both ROMS I make a folder on my desktop and name it NEWSYS. I copy all the files to my NEWSYS folder from the Dumped ROM Folders that I want. PRetty much everything except the .92 files (like stated earlier) after making my NEWSYS the way I want it, I cut my SYS from my KaiserKitchen_BUILD rom to my desktop and replace it with NEWSYS (remember to rename to SYS after copying)
Then I put G'Reloc in the Kitchen folder (same folder as the OEM,XIP,SYS,TOOLS,PACKAGE---main folder) and run it. Since I change the .VM I have to place my numbers back into and press "do it".
The SYS should be fine now.
Thanks buddy, Maybe dutty and his new crew did something to lock the rom down as his was the one i was trying to dump. I find what the other guy said about just changing out the .VM folder if thats the case porting roms couldn't be an easier!
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...
austinsnyc said:
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.
Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?
Click to expand...
Click to collapse
That depends on what rom your dumping... If it's a stock rom, you should not have this issue...
ryncppr said:
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...
Click to expand...
Click to collapse
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.
Now the same ROM + OEM and switch back to older SYS: everything OK.
Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?
g77 said:
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.
Now the same ROM + OEM and switch back to older SYS: everything OK.
Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?
Click to expand...
Click to collapse
RUU_Diamond_HTC_Europe_1.35.401.3_Radio_Signed_Diamond_52.26.25.09_0.93.25.26_Ship
+
RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
Copy .VM from WWE to Diamond
Use G'Reloc
Cook it up!
Boots just fine, no problems whit provxml, shortcuts, activesync, execute or.cabs here.
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.