Database Users

[IDEA] Multidevice kitchen

I've been thinking lately... I've been thinking of creating a new multidevice kitchen. The kitchen would support every current device, be based on the newest version of Bepe's kitchen or maybe the visual kitchen. It would add certain things like:
Automatically insert the cecompr.dll needed for both LZX and XPR compressions
Automatically hex edit the imgfs.bin during the cooking process to allow to LZX compression
It would come with an empty payload file for every device
It would support multiple languages and come with language packs
It would use the standard layout of bepe's kitchen/the visual kitchen so it would be easy to also keep build packages that would apply to every kitchen.
If I could get enough cooks involved from other devices, we could even have base STRIPED OEMs from every device that people can easily download.
We can make it automatically be able to dump any ROM and easily extract its XIP or SYS and import them into the kitchen or make the files into a package compatible with the kitchen that people could upload for everyone else to use. (Easier to spread new builds leaked by other people.)
I need more ideas as to what we could make this kitchen do.
I also need to know if any cooks would be willing to help out as it would be a MASSIVE project.
I would start it as soon as I'm done with two ROMs that I'm currently working for and a few kitchen that I'm modding for some people for LZX/XPR multicompression.

No comments, yet.
I'm working with ervius to add the LZX compression to the kitchen itself.
If no one helps, then it's going to be a little hard to do since I will have to download the default ROM for each and every device and then strip down the OEM. Then create bigROM packages to release as well. And then I can't test it since I don't have every device, so it's going to be a little bit of a slow process.
What I will end up doing will be more like just taking ervius kitchen, add a few things here and there and make all the packages and builds and whatnot available. Or at the least create a thread where people can post packages left and right. A repository of sorts. (A lot like the PPCgeeks's BuildOS but compatible with every device and using ervius awesome kitchen.)

Sounds like what Anchilus had one time! I think it was named as hypercore. But great idea though. I am not an expert cook or programmer, but I do cook ROM for myself sometime. My biggest thing is porting the ROM, doesnt matter what tutorial I read, I just dont get it LOL

Take a look in the raphael forums. Already done.

Will Help You
Ivan,
You know that I am willing to do anything I can to help you. Problem is that we have the same devices and you are my mentor so I am not sure how much help I would be, but whatever you need, you name it and I will do my best to help you out however I can.

GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I looked. I couldn't find a multidevice kitchen...

GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I think you mean this? http://forum.xda-developers.com/showthread.php?t=505800
Would be a great idea one kitchen for all devices, although I think the extra devices should be added in the form of plug-in, because nobody likes to dl a 20 GB kitchen . I would help but I'm not that great at dumping but especially not with the still changing structure of ervius visual bepe's kitchen. Is there a wiki or tutorial somewhere that properly explains where to put which folders? 12

Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.

ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
To get the attention of the cooks I think you should start sending email to the chefs and maybe a couple of mods too. I don't think it should be much of a problem on the raph forum, we are blessed with kind and sharing chefs, 12

i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore

mbarvian said:
i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore
Click to expand...
Click to collapse
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry

ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
qsqa said:
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry
Click to expand...
Click to collapse
You mean like an kitchen appstore or a bat to move everything into the right folders? 12

That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.

ivanmmj said:
That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.
Click to expand...
Click to collapse
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
ivanmmj said:
Replace the FIRST one and FIRST ONE ONLY with "LZX". Save the file, close the hex editor. Let your kitchen do it's thing.
That's it.
http://www.4shared.com/file/101370353/b7650aff/Compression.html
Click to expand...
Click to collapse
do we need to do this step on the "mythical" cecompr.dll?
thanks

mbarvian said:
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
do we need to do this step on the "mythical" cecompr.dll?
thanks
Click to expand...
Click to collapse
Already answered there.
But,
Yes.
The cecompr.dll is what tells the XIP how to read the LZX compressed imgfs.bin. The hex editing is what tells the kitchen tools to write the imgfs.bin in LZX compression.
I worked with evirus and now his kitchen has an option for LZX compression. It will do everything automatically. ^_^

That's a great idea. Not sure it could work on my device (ks20) as bepe's kitchen crashes on my nk.exe so I have to build xip part the old way (using xipport). Anyways, if you need french 96dpi resources, I can give you mine.
And for this project, instead of a special software to download packages, why not using a svn repository ?

Although a SVN repository would be awesome, I wonder if there would be a legal problem just like there was with the XDA FTP server used to host ROMs and stuff for building ROMs?

Yes, that's possible... perhaps we should ask a moderator, what was the exact reason it was removed (because after all, everything is still present on this forum, it's just not grouped in 1 place, but I think legal issues remain).
I also know that somewhere on the web, there is a svn server for winmo builds (I had once a wm build that had .svn folders).

Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.

DestructDez1 said:
Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.
Click to expand...
Click to collapse
PM sent. Thank you!!

"Port" a device rom to another device

Sorry for my ignorance but I wonder how one would procede to recompile a dumped rom of a particular device for another device *without* making to much changes.
In my case I want to "port" the OBOE debug rom to the HD2. And I want to do it by leaving all the EXT, OEM and SYS files *unchanged* (resolution of the oboe is the same as the leo). How should I go on?
(fyi, I would say that my cooking skills are just below intermediate)
EDIT: the rationale behind this is that I want to create a base wm 6.5.x rom from a HTC factory rom and work from there, instead of working from a customized 6.5.x HD2 rom and gradually replace packages from new leaked roms of other devices.

keep the OEM main folders of your LEO and switch all the ext and addons OEM folder from OBOE.... it should work.. and remember to use your OEMXIPKERNEL payload and bla bla bal of your LEO too.

Please give as more detail about main OEM folder and addons OEM folders

Please note that Oboe Debug ROm, it's a Chinese ROM, requires a lot of tweaking to make it work with another language, not a straight copy of Ext packs and cook, have a look at HD2 Rom dev about that, also it's a ROm made for CDMA devices which creats another problem to port

Porting is not an easy thing...you cant learn it from a guide...it comes with experience. Just my 2 cents...

Pisca said:
Please note that Oboe Debug ROm, it's a Chinese ROM, requires a lot of tweaking to make it work with another language, not a straight copy of Ext packs and cook, have a look at HD2 Rom dev about that, also it's a ROm made for CDMA devices which creats another problem to port
Click to expand...
Click to collapse
Alright thanks. Better wait for a 6.5.x WWE factory rom with the 800x480 resolution then. Didn't know btw that the Oboe was a CDMA device. Thanks for noticing that.
Well, the good thing is that I now know how to procede when a new rom comes out for another device. Thanks +Que PPC

Also nother tip, I forgot to mention, Oboe Rom it's for Dual Sim device

How can I modify a cooked rom?

Please excuse my ignorance...
I want to modify an existing blackstone rom (I want to remove some apps).
I downloaded osKitchen Zero but it seems that I can import only an official rom.
Is there another application where I can import a cooked rom? I did some search but couldn't find something in all the load of information existing in xda...

blister969 said:
Please excuse my ignorance...
I want to modify an existing blackstone rom (I want to remove some apps).
I downloaded osKitchen Zero but it seems that I can import only an official rom.
Is there another application where I can import a cooked rom? I did some search but couldn't find something in all the load of information existing in xda...
Click to expand...
Click to collapse
You should be able to delete stuff with htc rom image editor.
http://forum.xda-developers.com/showthread.php?t=377514

As far as I know you Can't, only an official rom can be dumped and changed, cooked roms you are not abble to do it

you should'nt! cooked roms are a piece of art (hard) work. You could ask the chef to cook you a personal rom, buy him a beer or three... or step into the world of cooking, i did. and it's great!

@ blister969
No way!
WBR
Siemens Lover

You can modify cooked roms; look up micro kitchen-it dumps roms, and you can modify the dump (remove a few files; tweak the .hv's) and re-build it. You may need to modify it for your device. You can probably do the same thing with EVK, it just may take a little more work.

@Farmer Ted
If you try dumping ROMs built with platformrebuilder, you don't get the dsm's. That doesn't mind, you can still cook it. But no, you actually can't. All modules loose one S00x containing relocation info.
(Btw, this S00x plus imageinfo.bin is weird anyway, original MS way is more sexy.)

OndraSter is right about reloc info, but I think that you can remove those apps without messing with modules .

Here's another thread on the subject. I'm pretty sure you can re-cook ok, with the missing reloc data. Da_G kicked in on the subject:
Da_G said:
Just a small note to add to this:
The last S00X section in a module is the .CRELOC section. This is used to relocate the module on-device (not used to relocate the module on the PC, in the kitchen, where we do it prior to flashing)
Not having the last s00x means that you wouldn't be able to imageupdate that ROM (because the on-device read/write IMGFS driver would not be able to re-base the module since .CRELOC is missing)
But you can certainly still re-base that module on the PC side prior to rebuilding a ROM. So that function in itself won't preclude you from porting modules from one device to another
Click to expand...
Click to collapse

[Q] Problem: No changes take effect in cooked ROM in EVK!

Hi pals
I Cooked a WM6.1 19971 Official ROM for OPAL in Ervius Visual Kitchen. The cooked ROM seems quite alright except that:
1.The original ROM was about 100MB while despite the fact that I added a lot of packages, the cooked ROM is about 80MB.
2.None of my packages exist in the cooked ROM when I flash it.
Can you tell me what the problem is?

The smaller size is fine.
What do you mean packages not there?
Are the files not in the windows folder or are you just missing shortcuts?

mnvoh said:
2.None of my packages exist in the cooked ROM when I flash it.
Can you tell me what the problem is?
Click to expand...
Click to collapse
What?!...EVK generates a build_log...look at this, and u'll see, what's in your rom.
Cannot belive that u've applied packages in EVK they wouldn't cook in....strange.

It is happened to me too in the beginning when i was cooking for kaiser and tried to cook inside HTC Mega packages with Manila 2d...i solved it using OsKitchen,lol.

af974 said:
.i solved it using OsKitchen,lol.
Click to expand...
Click to collapse
Sorry...but usin' OSKitchen is still hard work in my opinion. Maybe others think similar to me, and please forgive me @airxtreme!
But still the best kitchen in my opinion is EVK....

Its not true,
OsKitchen compared to any other Kitchen is much more easy to use expecially for newbie users.
EVK it is much complete.
Which is the best between one and another its only a personal taste.
icke said:
Sorry...but usin' OSKitchen is still hard work in my opinion. Maybe others think similar to me, and please forgive me @airxtreme!
But still the best kitchen in my opinion is EVK....
Click to expand...
Click to collapse

Kitchen
I can`t understand that someone say the os kitchen is to difficult
I work with these kitchen hours and days and no problems whatsoever and easys`t do use, if someone got problem to use this kitchen,live the finger from cooking

af974 said:
Which is the best between one and another its only a personal taste.
Click to expand...
Click to collapse
And that's what i said!
For new's, maybe OSKitchen is easier to use...but still beta.

Speak is free and give opinions too...but please people dont start flaming about kitchens.
I mean about what in red....its not nice.
lumisab said:
I can`t understand that someone say the os kitchen is to difficult
I work with these kitchen hours and days and no problems whatsoever and easys`t do use, if someone got problem to use this kitchen,live the finger from cooking
Click to expand...
Click to collapse

While EVK was building the ROM I checked the log it was generating. I saw all my packages. But when I used osKitchen it had problems with the *.dsm file in the packages and said that it's corrupt. I think it's the problem but I used package-creator-v2.7 to convert *.cab files to a package. So obviously the problem is with the package creator.
But on thing that's for sure is that newbies (like me) should stick to osKitchen.

FYI, Barin's OSBuilder has a .dsm autocorrection option.

Well, OsKitchen has its own package creator so all you need is to import your original rom and convert all your cabs again plus it has an auto mui converter,thats mean if that you have some 0410 mui's and you are cooking for 0409 oskitchen wiil rename all the mui for you.It worth a try.
mnvoh said:
While EVK was building the ROM I checked the log it was generating. I saw all my packages. But when I used osKitchen it had problems with the *.dsm file in the packages and said that it's corrupt. I think it's the problem but I used package-creator-v2.7 to convert *.cab files to a package. So obviously the problem is with the package creator.
But on thing that's for sure is that newbies (like me) should stick to osKitchen.
Click to expand...
Click to collapse

Let's state this once for all: Ervius kitchen is basically a GUI to create _skip files that launches a giant batch file that does all the cooking and that needs to be customized for every device: if you created your own _skip files by hand and used a batch file to cook there would be virtually no difference. OsKitchen has a simple GUI by design but that doesn't mean that it isn't orders of magnitude more complete and advanced than ervius kitchen: it does everything from detecting all device/ROM informations without asking anything (the list of supported devices actually has nothing associated to them but the alternative names: no customized fixed, no customized settings, nothing) to cooking with all sorts of checks to prevent bricking or unbootable ROMs and even parsing all the files in the package: if I had proper relocation code (that I was waiting Da_G to write since he knows that stuff better than everybody else) the kitchen could already natively cook its own ROMs. I'm already using all the code I wrote to replace platformrebuilder to implement all sorts of cool stuff like complete validation of all package files and installing packages directly on the phone trough activesync (to avoid having to reflash any time you want to test something) as you can see on the alphas thread, things that on ervius kitchen, where cooking just means running a giant batch file, you could only dream of.
I hope that finally clears the minds of the people saying that ervius is more advanced or complete: it's not, it's just a simple batch file-based kitchen with an unnecessarily complex GUI. It may have some bundled tools that oskitchen doesn't include (like xipporterex, that while works on some NK.EXE wreaks havoc on unofficial native kernel and latest kernels) but having a dedicated button to launch a tool doesn't make a kitchen "more advanced" or "more complete".

No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?

pkoper said:
No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?
Click to expand...
Click to collapse
Not really, I process all the files before feeding them to platformrebuilder hence the recmod/upx/tweaks/ordering/manila compression/etc without touching any of the original files. I also only use the newest tools available like libnb and osnbtool that the kitchen calls directly and checks the output to warn of any error and to get informations about the ROM format indeed it can import any proper BIN/NB/NBH file and cook it without even knowing what device they come from. The only original imgfstools I keep are nbmerge and nbsplit because I was waiting Da_G to finish his BuildNB function but osnbtool can probably replace both (nbsplit for sure with the -sp parameter).

@OP, it sounds like your package structure is wrong. Are the packages in EXT format (not OEM)? If they're in oem format, none of the files will be included. Just make the packages manually, it's a lot easier.

Can you please post the build log file?

pkoper said:
No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?
Click to expand...
Click to collapse
My kitchen (OSbuilder) uses it's own engine to process packages, build dsms, rebase modules, merge dsm and build ROM file. The only external tool i use is "TurboImgfs" by airxtreme.

Yes , when i wrote that EVK ,maybe, its more complete then OsKitchen i was referring to this, only some tools.
airxtreme said:
It may have some bundled tools that oskitchen doesn't include
Click to expand...
Click to collapse

airxtreme said:
Let's state this once for all: Ervius kitchen is basically a GUI to create _skip files that launches a giant batch file that does all the cooking and that needs to be customized for every device: if you created your own _skip files by hand and used a batch file to cook there would be virtually no difference. OsKitchen has a simple GUI by design but that doesn't mean that it isn't orders of magnitude more complete and advanced than ervius kitchen: it does everything from detecting all device/ROM informations without asking anything (the list of supported devices actually has nothing associated to them but the alternative names: no customized fixed, no customized settings, nothing) to cooking with all sorts of checks to prevent bricking or unbootable ROMs and even parsing all the files in the package: if I had proper relocation code (that I was waiting Da_G to write since he knows that stuff better than everybody else) the kitchen could already natively cook its own ROMs. I'm already using all the code I wrote to replace platformrebuilder to implement all sorts of cool stuff like complete validation of all package files and installing packages directly on the phone trough activesync (to avoid having to reflash any time you want to test something) as you can see on the alphas thread, things that on ervius kitchen, where cooking just means running a giant batch file, you could only dream of.
I hope that finally clears the minds of the people saying that ervius is more advanced or complete: it's not, it's just a simple batch file-based kitchen with an unnecessarily complex GUI. It may have some bundled tools that oskitchen doesn't include (like xipporterex, that while works on some NK.EXE wreaks havoc on unofficial native kernel and latest kernels) but having a dedicated button to launch a tool doesn't make a kitchen "more advanced" or "more complete".
Click to expand...
Click to collapse
Don't let them get you down man. Ervius's kitchen is a piece of **** in my opinion. The GUI blows and it crashes on the smallest thing that's not exactly right with a package. Did I mention the GUI is horrible ?
I will say it as well, erv's kitchen is NOTHING but a glorified GUI for platformrebuilder which is the real workhorse.
p.s. I made my own kitchen GUI, based on platformrebuilder as well. Mine's designed to cook for 12 devices at a time though... so I can't exactly share it. PM me if you'd like the details necesssary to make Samsung Omnia 2 ROMs with prb though, it seems nobody else seems to know what the "secret" is... I just think they didn't try hard enough. lol If anything, you can add 4 more devices to your already impressive collection of supported devices

[SOLVED] Non-booting ROM - I'm doing it wrong

Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks

Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,

Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?

nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,

Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?

nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,

Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.

Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.

nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.

Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?

nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.