Related
I share my base so that our Cook could have easier life (I hope).
This is not a ready-for-flashing product. You will still have to Cook and BuildOS. Don't download if you have no idea what to do with cooking.
This is Vanille ROM (SYS & OS) based on 2.20.707.1B WWE. Both files and Registry are trimmed.
I use this base to cook my own ROM and everything looks good. I am appreciated if you could trim down the size further.
What are removed (Removed items are included in zips attached):
------------------
SYS
-Windows Update
-Internet Sharing
-Transcriber
-Windows Live
OEM
-Comm Manager
-Audio Manager
-Home Plugin
-Phone Skin <== experimental
-Task Manager (X button)
-MMS
-TouchPad and Touch Keyboard
Enjoy!
Base-ROM (SYS & OEM)
http://www.fs2you.com/files/78a403eb-8c8d-11dc-922a-00142218fc6e/
Ripped SYS files
http://www.fs2you.com/files/a7c5aaa3-8c8d-11dc-b3b1-0014221f4662/
Ripped OEM files
http://www.fs2you.com/files/34c020ba-8c8e-11dc-96c1-0014221b798a/
Attached is the Network Wizard from ExtROM, removed operator's customization package.
PS: The two "CheckAutoRun" files are also removed. You may copy them back from your original ROM.
100+ view but no one loves it? omfg.
chill dude ... thanks for the uploads the the chefs will be happy with it
evermick said:
100+ view but no one loves it? omfg.
Click to expand...
Click to collapse
Don't worry bro, I'm downloading it now and I will do some cooking 2nite.
Cheersss
kick to first page.. I wonder if ppl know what to do with this
Bascially when you put back Comm Manager, Audio Manager, MMS, Phone skin and Task manager, pack it into .NBH and flash it, it is a Vanilla ROM already.
I seperate each part just for the sake of easier replacement of different modules.
I am trying to make a clean, trimmed down rom. I am sure I can learn something by reviewing your base here.
Thank you vm for sharing!
Hey guys... Exploring the keyboard oem package i've noticed that there are alot of language database files for other languages than the ones selectable in the rom.
Mayb we can edit the reg to make these languages also available?
I'm studying on it, but still no progress.
gr. bram
bram_smulders said:
Hey guys... Exploring the keyboard oem package i've noticed that there are alot of language database files for other languages than the ones selectable in the rom.
Mayb we can edit the reg to make these languages also available?
I'm studying on it, but still no progress.
gr. bram
Click to expand...
Click to collapse
Good finding, I did not notice it.
Thou, I noticed there are a lot of lang files when I remove the Touchpad.
Sounds like I can remove even more files for keyboard layout as I don't need them
Yes I Accept Bribes And Donations, Just So I Can Build Up A Small Buffer For A Broken Device So I Can Keep On Cooking, Ripping Apps, And keep Building full SD Card Coded Cabs and Keep The World Save From Bricks
XDA-Developers FireFox & IE Search Bar Plug In
Vanilla 2.2 Cooking Rom
Kitchen
My Full Signature With All Links To Important Stuff:
Touch/ELF
IPL: 1.17.0002
SPL: 1.11.000
RADIO: T-Mobile NL03.08.90
ROM: SPC WM6.09 (SP1) / TMNL2.26 Full / Stripped
Wizard/G4
IPL: ????
SPL: ????
RADIO: ????
ROM: ????
SDA/Typhoon
IPL: ????
SPL: ????
Versatel/24 Skin
Orange SPV100
DEAD
O2 XDA - Wallaby
Next Device - HTC Rapheal
Noonski said:
Sorry Mick, there's to much going on.
If this is from the 2.2 dopod rom my advice would be to leave HTChome exe's and Dll's in the Rom, as not everyone has this new updated Home Plugin yet.
Click to expand...
Click to collapse
This can be found again from my posted "OEM-ripped.zip"
Entertainment can be removed.
I think some of us have an option.xml file for this.
And Office.
I have them both at home.
Click to expand...
Click to collapse
These stuffs could be easier removed from the SYS. They are packed within seperate folders already. So no hard work is needed
Maybe I should seperate those stuffs in next version (if there is any) to make the ROM even easier for noobs.
Also it would be nice to integrate Rapi certificates.
Click to expand...
Click to collapse
Maybe I would just build a seperate package for this
evermick said:
This can be found again from my posted "OEM-ripped.zip"
These stuffs could be easier removed from the SYS. They are packed within seperate folders already. So no hard work is needed
Maybe I should seperate those stuffs in next version (if there is any) to make the ROM even easier for noobs.
Maybe I would just build a seperate package for this
Click to expand...
Click to collapse
Maybe i didn't use the right words.
What i wanted to say sort of is.
That you don't need to remove the actuall packages.
You split the whole rom up by adding option.xml files.
You set the needed folders to True and the unneeded folders to False.
Just check the option.xml i just attached for the entertainment folders.
Also are removed files from Oem folders brought into a new DSM file to prevent Missing files when extracting the rom.
And if WLM is removed do you add the removed Shortcuts to the WLM packages.
You know me i'm saying this to help, because if you want a good true vanilla it has to be perfect.
I've added some new packages to Elf Repository for use in kitchen.
HTCHome 2.1 plug in with Added Tab settings.
Updated Network Wizard SD and MM Package.
WWAN (if only for the option xml file, it's pretty useless to have anyway)
Multiple GlyphChace Settings Oem Packages.
All using Xtriny's new Build which does allow changing of Pagepool settings.
There's a memory fault in the pre 5.2.1933 version of 2.2 Rom.
At the moment i just started a new ROM and it's going to take weeks to finish it.
Luckely no ones waiting for a new ROM anymore because they are popping up left and right.
So i can take my time. I think it's time i take my responsibility and stop being a chef.
A lot is going wrong and i'm not talking about you.
Looks like we are making another "Pandora" style kitchen when we add option.xml to individual packages.
It is a good idea, but will consume lots of time. Let me see if I could do it
That's what i mean. But you don't need to do this alone.
I'm uploading every detail i can find.
So there's allready a lot of packages available.
After every change i make a selectable package.
And even when you re extract the rom you don't get missing files.
For instance when you remove files from OAMAPPS folder and rebuild the DSM contents. All the modules in folders won't be added and you still have missing files.
But if you then take the EXE's and DLL's out of the folder sand put them into OEMAPPS folder and then make Rebuild the DSM you won't have missing files.
Weird thing is that when you then extract that NBH file the OEMAPPS will then be extracted to SYS folder instead.
This shouldn't be a big problem as you have probaply seen in other kitchen's
Here's a Vanilla Based on 2.2 os 5.2.1933
You can extract the Rom and recook it.
4MB PP
It's 50.1 MB 62.63 Storage It's Nice and Neat.Everything not in it can be found in repository.
(The only thing i forgot is to remove the ZIP link)
Hay Noonski
The thing is i've been lookin for a clean rom with big storage and a lot of free ram with TochFlow and WITHOUT htc-home plugin for my Touch
How much Stoarge in the one u linked to? and free ram?
If some one have a good clean stable rom, would u plz pm or post me the link
Cobra2 said:
Hay Noonski
The thing is i've been lookin for a clean rom with big storage and a lot of free ram with TochFlow and WITHOUT htc-home plugin for my Touch
How much Stoarge in the one u linked to? and free ram?
If some one have a good clean stable rom, would u plz pm or post me the link
Click to expand...
Click to collapse
It's amazing.
It's almost 63 MB storage 59.39 free.
Memory free around 26.
no HTCHome wlm X button audio Manager and it's clean and recookable.
But i'm Pulling it so Xtriny can post it. It came from his base.
I just completely stripped it to 50.1 MB as close to the max as possible.
evermick said:
I share my base so that our Cook could have easier life (I hope).
This is not a ready-for-flashing product. You will still have to Cook and BuildOS. Don't download if you have no idea what to do with cooking.
This is Vanille ROM (SYS & OS) based on 2.20.707.1B WWE. Both files and Registry are trimmed.
I use this base to cook my own ROM and everything looks good. I am appreciated if you could trim down the size further.
What are removed (Removed items are included in zips attached):
------------------
SYS
-Windows Update
-Internet Sharing
-Transcriber
-Windows Live
OEM
-Comm Manager
-Audio Manager
-Home Plugin
-Phone Skin <== experimental
-Task Manager (X button)
-MMS
-TouchPad and Touch Keyboard
Enjoy!
Base-ROM (SYS & OEM)
http://www.fs2you.com/files/78a403eb-8c8d-11dc-922a-00142218fc6e/
Ripped SYS files
http://www.fs2you.com/files/a7c5aaa3-8c8d-11dc-b3b1-0014221f4662/
Ripped OEM files
http://www.fs2you.com/files/34c020ba-8c8e-11dc-96c1-0014221b798a/
Attached is the Network Wizard from ExtROM, removed operator's customization package.
PS: The two "CheckAutoRun" files are also removed. You may copy them back from your original ROM.
Click to expand...
Click to collapse
can this b used for cooking roms for elfin (128\256)? which kitchen do we use to cook this rom?
I'm not sure.
But it's an earlier Base then the vanilla version i posted up ahead.
But if you download the .nbh file and extract the os.nb then read the PP chaging tutorial in th cooking class kitchen you can check if it has the correct value.
If the value for pagepool is 20 it is for both elf and elfin.
hello guy´s
i am new here and i want to flash the vanilla2.20.707.1B on my elf
i´ve got ipl 3.10 and spl 3.07 on it . the problem is : every time i try to flash ( Executing HTC_Touch_WWE_ME_2.20.456.1B.exe ) it Goes through the bootloder to status bar , after holding on at 1 % the touch restarts to winmob.
Ahe Flash prog ( RUU ) is showing ERROR 260: Connection.
can someone plz help me i´ve searched all the fourums . after 4 -5 h of trying you are my last hope.
Greetz Foe
I´m not sure, but if your IPL / SPL is the patched version, it has overwrite protection, and the ROM you´re trying to flash is full, it contains all areas: IPL, SPL, ROM, Splash and Radio.
The way around is to extract the individual ROM components and rebuild the NBH file including only the ROM section, leaving IPL, SPL, Splash and Radio out. When you flash this one, IPL/SPL won´t be overwritten, so no error will pop.
Any kitchen around comes with all the tools you need for the procedure. If you don´t know how to do it, take a look at the forums, this subject is very well covered.
Hope this helps.
Eduardo
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.
Say I downloaded "frauhottelmann"'s GUI kitchen and I grabbed the original, unmodified S740 SYS and OEM folders from a thread here.
What would I need to replace in order to build a ROM that will bootup on an Excalibur ? I have the "dump" of the original 6.1 ROM from the Excalibur. Some drivers maybe ? Any help ? Thanks
Oh, so you got it already. You should start with the OEM folder of the Excalibur. Then you might have to add some of the *.cpl.xml from OEMMISC to get all settings to work. The new packages are a bit trickier to use. You need more files from the new OEM. And don't use the new Connection Setup, it doesn't work. You should be able to use the whole SYS folder though.
This is going to be difficult then. The only kitchen that exists for the Excalibur, dumps the contents of the ROM in one folder and doesn't seperate the foldes out to OEM, SYS, etc...
So is the SYS folder where all the drivers are then ?
No. There are two main folder. SYS is for the general Windows Mobile OS part. OEM is what the manufacturer or you add. The folder for drivers is on OEM and is called OEMDrivers. If you have a dump, you can make "packages" with PKGTools. There is no official 6.1 ROM right? So I guess this will be a problem, because then it doesn't sort the packages right. You'll have to try. Maybe send me a screen shot of the files or the result!
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
yes pkgtools included.
give it a try and post if it worked!
good luck mate... i saw your prog for the weather! really nice!!
htc sliding plugin also rocks! anyway keep it up!
Well I managed to make an excalibur ROM that works (partially) with the VOX GUI kitchen, and replacing the OEMDrivers with the drivers from my official WM6 ROM. Problem is, the center button on the keypad doesn't work. Everything else is fine... although WI-FI and BT don't turn on. Any ideas what I'm doing wrong ? Oh and the startup screen is all skewed and in 4 pieces, right after the splash screen, bu before the usual winmo 6.1 splash screen.
Well I'm over that road bump now, and I'm trying to port the S740 XIP and SYS over to take advantage of the new CHOME
So far, so good...
Thanks guys for the support. I was able to make a new ROM based on the 20279 core from the S740 ALL by myself. Reading these forums for a few days is what did the trick... heh. THe ROM runs great and I have to say that BuildOS+package tools is my best ROM cooking friend right now...
NRGZ28 said:
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
Click to expand...
Click to collapse
There is no rgu file in the rom you dumped.
and the one is not official 6.1.
You can dump the
moto q8 WM6.1 rom
s740 official rom
C810 official rom for your resource.
I know.. that was my original problem. No worries though, as I used the SYS folder from the S740 and all is well now
I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?
Anyone willing to spare some time to help please?
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?
OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.
I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.
If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)
I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.