Develop Bugs

problem during cooking lvsw 0320

i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.

i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps

zohaer21 said:
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
Click to expand...
Click to collapse
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.

dont know if this would help you but take a lot here :
www.asukal.jp/hv_rom/hive2.txt
or simply use Make_HV, found it in the development & hacking thread.
First covert the hv file to rgu (which is simply REGEDIT4 Format) then make changes and convert it back.

qooqoo said:
i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
Click to expand...
Click to collapse
This is my little surprise

qooqoo said:
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
Click to expand...
Click to collapse
You don't need a .cab for this. The program that goes through Config.txt can handle XML files with registry settings directly. So, grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want. If I'm not mistaken, it's even available bundled with a Chinese ROM already. There you can edit the .rgu files from which the Registry will be created. This eliminates the need to read any of the .hv files. Worked very well for me! Also, since bepe's kitchen recreates the packet structure of the ROM, it's so much easier to understand which files and registry entries have a dependency or belong together. Highly recommended!
Cheers
Daniel

lvsw said:
This is my little surprise
Click to expand...
Click to collapse
weird suprise

lvsw said:
This is my little surprise
Click to expand...
Click to collapse
Why would that be a surprise? Is there more to this than meets the eye?

dutty said:
weird suprise
Click to expand...
Click to collapse
Indeed, I've been hitting my head against it for some days now...

lvsw said:
This is my little surprise
Click to expand...
Click to collapse
himan，give us a solution plz, it is a so good rom, but i can't add anything i want.
tadzio said:
grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
Click to expand...
Click to collapse
thk u but i don't know how to edit a xml file, any suggestion?
tadzio said:
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want.
Click to expand...
Click to collapse
it is for CHT but not for CHS, there is a lot of CHT roms yet, cooked or offcial, but there isn't a official rom in CHS, a just want to convert 0320 vesion to CHS vesion.

I will be watching this thread.
Waiting for good news.

qooqoo said:
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
Click to expand...
Click to collapse
I have the same problem...the LVSW 0313 version was fine...then the new LVSW 0320 won't boot..stopped at the subsplash screen...it is strange that the default.hv is there but doesn't seem to booting the file.

qooqoo said:
thk u but i don't know how to edit a xml file, any suggestion?
Click to expand...
Click to collapse
Any Unicode-capable editor will do. Personally, I use UltraEdit.
Cheers
Daniel

Please don't take offense, but I'm starting to think you got the ROM as it is..."protected" that's why all the customizations are done via AutoRun.exe and xml files.

i found that lvsw 0325 edition can be edit.

qooqoo said:
i found that lvsw 0325 edition can be edit.
Click to expand...
Click to collapse
Yes, 0320 can't be edited. But 0325 could. But you can't use the regular tools..you have to use the "more Storage" tool, then just manually copy the "default.hv" and "user.hv" from the "dump" folder, use the regular tool and covert it to .reg. Then you make modifications to the registry file, convert it back to .hv and copy them back to the "dump" folder..you can add files by just copying files into the "dump" folder..after you are all done with it, just continue with the "more storage" tool to make your new-os.nb

[Help Needed] How to change the ROM date ?

How can i change the rom date ?
the patchers from the kaiser kitchen ain't working for the Hermes,
thanks all for the help.
Jimmy

Jimmy,
My searches haven't turned up anything definitive, but I HAVE seen some mention of the date being held in file S000 in the NK.EXE module. I cannot examine this possibility right now, but maybe I'll have time when I get home tonight.
In the meantime, I would love it if somebody could post a definitive method that works for WM6 devices. It sure would be nice if, when I flash a new ROM, I didn't need to bounce forward 8 months to set the time in initial setup
-pvs

pvs said:
Jimmy,
My searches haven't turned up anything definitive, but I HAVE seen some mention of the date being held in file S000 in the NK.EXE module. I cannot examine this possibility right now, but maybe I'll have time when I get home tonight.
-pvs
Click to expand...
Click to collapse
Correct!

AssassinsLament said:
Correct!
Click to expand...
Click to collapse
Thanks Assassin ... but, checking my ROM dump, it seems my base ROM does not contain a module named NK.EXE. Instead, I have an actual file by the name of NK.EXE in my XIP folder. Thus, there aren't any "S00?" files to work with.
Does anybody know of any other place I might be able to change this ROM's date?
TIA,
-pvs
[EDIT]Weird, I used a binary editor, found the date string inside of NK.EXE, and successfully changed it. I cooked the newer version of NK.EXE into the ROM, and ... the ROMDate was still the same. Sheesh! It would seem there should be SOME way to change this thing.
Can anyone please give some other suggestions?
Thanks again,
-pvs
[/EDIT]

[SOLVED]How to change OEM version in SplashScreen on BootUp

hi guys.
am building my own roms these days. not totally noob but not an expert as yet.
actually i have seen many roms which have the initials of the person who cooked the rom in the splash screen on the bootup.
like you get RGD
where R is radio
G is something and
D is the OEM or ROM version.
like swtos roms have swtos written on there, aztor and IOR Morna as well.
how to do the same?
i've attached a picture though its not clear but just gives an idea.

help me someone please..

sunnyin86 said:
help me someone please..
Click to expand...
Click to collapse
you can use a hex editor , or u can use xipportex.

deeren said:
you can use a hex editor , or u can use xipportex.
Click to expand...
Click to collapse
but what do i need to edit using hex editor or xipportex??

Just open the file and look for the string you want to change

verrazzanoprince said:
Just open the file and look for the string you want to change
Click to expand...
Click to collapse
well am not sure if what am gonna ask is really dumb or not but have no choice.
1st of all am not able to find hex editor and xipportex.
and even if i do then what file do i need to open to change that version?
how to use hex editor and all??

actually am using bepe's kitchen and for that there needs to be a proper XIP folder which i could only find in MORNA's XIP.
now i've added the 21038 build files to this xip but do not know what to edit to change that oem version.
my complete rom build 21038 is done and am just left with this.
Am attaching the xip folder so if anyone could change the version to " 2AHEN MAKK", i'll be really thankful to you.
Eagerly waiting for your response as i need to release the rom asap.

sunnyin86 said:
actually am using bepe's kitchen and for that there needs to be a proper XIP folder which i could only find in MORNA's XIP.
now i've added the 21038 build files to this xip but do not know what to edit to change that oem version.
my complete rom build 21038 is done and am just left with this.
Am attaching the xip folder so if anyone could change the version to " 2AHEN MAKK", i'll be really thankful to you.
Eagerly waiting for your response as i need to release the rom asap.
Click to expand...
Click to collapse
you need to edit the s000 file from nk.exe folder whic is located in the oemxipkernel with a HEX EDITOR.
The version number can be found at values around 3500.

here it is . i've noticed it's from xor morna. be sure to give credit to carburano when u release you rom.
good luck.
http://www.4shared.com/file/96538355/f0e7d17b/XIP.html

deeren said:
here it is . i've noticed it's from xor morna. be sure to give credit to carburano when u release you rom.
good luck.
http://www.4shared.com/file/96538355/f0e7d17b/XIP.html
Click to expand...
Click to collapse
sure broda. thanx. will check the xip and let you know.

deeren said:
here it is . i've noticed it's from xor morna. be sure to give credit to carburano when u release you rom.
good luck.
http://www.4shared.com/file/96538355/f0e7d17b/XIP.html
Click to expand...
Click to collapse
hey. i just checked it. there is a mistake. what you have edited is "22AHEN MAK"
but i want "AHEN MAKK".
thank you very much.

yes it works. thans deeren

XIP Extract

Hi!
I'm a rom developer and i've managed to cook a rom for my Benq E72 using the build 23017, but now i want to use the build 23090.
I'm trying to extract the "XIP" of an Standard Emulator Image from MS SDK 6.5.3 using this command:
nbsplit -emu os.nb
os.nb.payload
RomMaster -w 5 os.nb.payload -x -o xip.bin >NUL
But i always get an error....
[Info] It is a common ROM.
[Error] Load nb00 failed.
Also i have a rom for this device that use the build 23090, but i cannot extract the xip either
Hope someone could help me! Or tell me where i can get the XIP and SYS 23090 for Smartphone!
Thanks!!!

Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish

AndrewSh said:
Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish
Click to expand...
Click to collapse
Thanks!
I want to use that build because is the only one i know that works well on my device....
Thanks for the file, i'll try it!
I can mix that XIP 23092 and SYS 23090 right? i have the spanish resources from the emulator rom

samWMEmuKitchen v0.2b - ROM Kitchen for Windows Mobile Emulator

nickleby said:
I can mix that XIP 23092 and SYS 23090 right?
Click to expand...
Click to collapse
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Alexx~, dude , I think nick has problems with extracting the stuff from emulator.

AndrewSh said:
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Click to expand...
Click to collapse
Ok! Thanks for all your help!!

Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones

nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
You have to check it by yourself. Normally everything should work, why not. All the issues described in the topic are for 20% device-dependent and for 80% user-dependent
For me and of course for Alexx~ (he knows much more than me about the things) - every build works

AndrewSh, i realized what the problem is. In samWMEmuKitchen have the opportunity to extract dump, after the dump will be created os.nb, from which they can then extract xip.bin the usual way.

It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin

nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
NO! Those builds does not work on Smartphone devices.
BenQ E72 does have WM Standard.
Those resources are for touchscreen devices (WM Professional).

Alexx~ said:
It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin
Click to expand...
Click to collapse
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks

nickleby said:
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks
Click to expand...
Click to collapse
run the program as an administrator

I am writing in this way directly, since I have not received help in the forum, and that maybe I have not been very specific in my request to place it in the forum.
I own a Smartphone, brand MWG Zinc 2 Rom and all I own are in English.
Just explained on the website of the creators of the ROM for my device, the entire procedure for Cook ROM.The page es PDAGismo.com
My question is very different from the way this process is done for different devices because they do not know much about it.
The page is in Thailand but you can translate, I do not understand is the whole process of the preparation of the ROM.
Someone could explain all this ?
It is so hard to accomplish this task by a person with basic computer knowledge and without any programming domain?
Help me, please.
Thanks

Help For updating wm6 XIP to wm6.1

First thx for helping me
I was trying to port a XIP from Touch Cruise
Yet it cant even boot in the system [only suck at the screen with the red words at the bottom]
Any clear tutorial for me. Thank you

You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?

the.decoy said:
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
Click to expand...
Click to collapse
Yes i am using Ervius Visual Kitchen
What i do is using the xipporterex to port the xip.
I even tried to follow the bepe tutorial from darkforceteam with bepe kitchen.
Yet same error occured.
Would u mind giving me a clear step for making it workable?
thx

Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?

the.decoy said:
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
Click to expand...
Click to collapse
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]

Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?

OPzero said:
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Click to expand...
Click to collapse
Oh thats easy. The "Rom Version" (that shows on boot) just needs to be patched (it is reading it from the copied OEMXIP).
Just go back into the Porting window then click the button "Find Date/Version on \ROM\Xip\"
That will populate the Rom Date and Rom Version fields.
You can then edit those fields and click each of the "Change" buttons to patch the newer Date/Version into the OEMXIP
You can also set the PagePool value using the "Change PP to Mb" function (it is not possible to query the current PP value however it does tell you what it previously was when you change it). You could always set it to something sensible like 4 or 6 and see what it was before that.
EDIT: If you were actually talking about the CE OS build number that shows in "About Device" then that is much harder to change. It is embedded somewhere within the MSXIP (requires hex editing I am not familiar with - and that is effectively make a "fake" build anyway).

OPzero said:
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
Click to expand...
Click to collapse
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.

the.decoy said:
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
Click to expand...
Click to collapse
It's ok, would u mind pm or post some link which release those stuff?
Thank you very much!
I will still upload my rom and pm to u~
Check it when u hav time
really really thx

You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow

the.decoy said:
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
Click to expand...
Click to collapse
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx

OPzero said:
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
Click to expand...
Click to collapse
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414

the.decoy said:
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
Click to expand...
Click to collapse
1 more question
I downloaded a XIP SYS Pack from
http://forum.xda-developers.com/showthread.php?t=650783
However there are 5 Folders
How can i port them into the kitchen?
Thx for that

OK, this technically requires more time than I can spare to explain thoroughly ... but maybe if I just outline the steps you can do some google searching to work out exactly how to do it:
- First you need to clean up the SYS for you needs. For Trinity you need to have QVGA sys structure so that means only 96DPI and 320x240
- That means sorting the SYS package folders into an EVK SYS structure and removing the other DPI and resolution folder structures.
- Go get XIPDumpSoter (or whatever it is called now) by teh penguin so that you can use it to automatically sort the folders. Then delete any that are for other DPI or RES (eg: 192DPI or 640x480, etc). You _only_ want 96DPI and 320x240 (and of course any that are non-res specific)
- That should give you the folder structure to put into \SYS\NEWBUILD#\
- You will need to copy over the WINCENLS sys package from your existing SYS as that will not be in the new SYS (there are other replacement folders like SQM_DUMMY, and also some that we often just delete but you can learn that stuff later)
- We have already discussed what you need to do with the MSXIP
- Lastly, (and this is really very much the "art vs sicence" part), you will need to go through and "recmod" a certain number of "modules" within certain sys packages.
I simply don't have the time right now to get into recmod but if you google you will find plenty of helpful posts explaining it. I think there is even a basic recipe of what to recmod for 64M users done by JooJooBee ... that would get you going.
Put simply, at this stage you need to read read read read read lots of chef threads to pick up the finer details. Sorry I am too busy at work to be any more help than this.
Good luck.

Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!

OPzero said:
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
Click to expand...
Click to collapse
I'm actually going to bed before 3am tonight, so I will not be long here, but I just had a thought. When you cook the ROM, are you checking "Real WM 6.5 AKU" in the Kitchen? Don't do that. You cannot actually use a Native 6.5 Kernel on the Trinity as one does not exist. Also, as mentioned by the.Decoy before, you MUST have 'wince.nls' in your Kitchen somewhere or it will not boot. Thirdly, try cooking a version without ANY Extended packages. Only the original XIP and SYS and see if that boots. When you get that going smoothly, start adding EXT packages. Good Luck!
I'll check back in a couple days to see if you've made any progress. If you'd like to send your kitchen to me also, I'd be happy to look it over and see if I can find anything wrong in there.

Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Update:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx

OPzero said:
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
Click to expand...
Click to collapse
Ummm are you trying to use a freshly extracted OEM from an official ROM?
If so then yes, there is a massive amount of conversion that must be done to it before you an cook it into a rom. Even before you break it up in to components and edit all the reg and dat files ... you first need re-sign everything with an SDK cert because you won't have the official cert that HTC built them with.
Seriously. If you are just starting out then use an existing chef's OEM (use mine or anyone else who has posted a kitchen).
Even I have not yet ever had the time to complete build an OEM from scratch (not that I don't want to one day). I was always just adapting the OEM that Chanvi had provided us in his kitchen, primarily because he had already done all the work to make it mesh with WM6.5
OPzero said:
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Click to expand...
Click to collapse
I am bit confused by what you said there
As Supersport explained, we do not have a Native 6.5 kernel for Trinity.
So that option should not be checked.
OPzero said:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
Click to expand...
Click to collapse
Again, this is why I said to try "Load ROM" and see what happened
Those are just simply EXT packages which contain 1 single provxml. Each one sets the registry value for "ROM Version" (the info that comes up in "About Device" in Settings). There is one for every type of "Saved ROM" you can build from that kitchen.
I created them so that people could build each of the several types of rom from my kitchen but never need to edit the provxml files to change what the version info was.
If you are going to try cooking your own roms, the best advice I can give you is find a text editor you like and just start opening up ALL of the REG DAT RGU and PROVXML files you can find and see what they are doing.
You can even do it from within EVK. Select the type of file on the left panel called "Editors" (or just select "All") then click "Show Editor". You can open the files it finds by double clicking them in the panel on the right.
Anything custom that ever happens in the setup of a rom is controlled by these files.
If you want to see how something works (or what it does), just open up the files and read them

Sorry, wt i mean is that my rom become bootable after unchecking it
~~ That is so amazing ~~
Now i am Reading the horrible, endless.....etc tutorial, [I can finally have my own rom ]
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~

Sorry can't help you there.
I have never ventured beyond WWE lang for my kitchens.
OPzero said:
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Click to expand...
Click to collapse