Related
Hi,
I would like to share the kitchen that I use to build my personal ROM. It's SYS and XIP were ported from the stock Diamond 1.93.456.2 WWE ROM that Tom made available and the kitchen is Bepe's kitchen.
Here it is (Build 19965.1.2.3):
http://rapidshare.com/files/130210385/Artemis_Diamondish_6.1_Build_19965.1.2.3.zip
UPDATE1: I have made a few changes in the OEM folder, I have added Advanced Config, added a patched htc home for the weather and made some changes to the registry. The changed files are in the attached zip.
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/130466202/Artemis_Diamondish_6.1_Build_19965.1.2.3_NBH_ROM.zip
(Usual rules for cooked roms, i.e. USPL etc.. - http://forum.xda-developers.com/showthread.php?t=331845)
UPDATE2: I have uppdated the XIP and SYS to use build 20273.1.3.3 and use .NET CF 3.5 as suggested, thanks xvx45
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/133908594/Artemis_Diamondish_6.1_Build_20273.1.3.3_NBH_ROM.zip
Kitchen:
http://rapidshare.com/files/133917390/Artemis_Diamondish_6.1_Build_20273.1.3.3.zip
UPDATE3: I have uppdated the XIP and SYS to use build 20721.1.4.0
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/142121757/Artemis_Diamondish_6.1_Build_20721.1.4.0_NBH_ROM.zip
Kitchen:
http://rapidshare.com/files/142132785/Artemis_Diamondish_6.1_Build_20721.1.4.0.zip
Fix for the SMS inbox issue can be found in post #99 http://forum.xda-developers.com/showpost.php?p=2616507&postcount=99
Here are some screen shots (of build 19965, mainly the same as build 20273 and 20721 but version numbers changed):
Nice work bro, nice to see new "faces" on Artemis forum.
Cheers.
Thanks, been here a while, just learning as I go. I thought it was a bit quiet on the new ROM front.
Thank you very much for you sharing!
Maybe this was the push i needed to start also cooking.
Who knows...
Cheers
Thanks for share man!
Do you have some screenshots of this ROM?
INFO
Hi,
Just extracted, saw all the separate files, did i miss the full .nb rom image or is this post to cook yourself with the htc romtool?
I know there are a look of cooking-guides, but can anyone explain simple which files tot select from the extraction when running the htc rom tool you have to fill in :
G3 IPL
G4 IPL
SPL
Splash
Radio Ext.Rom
OS
Can i add also .cab files for example somewhere to add to this rom?
Would like to cook first rom.
Thanks,
Innovator
Hi, just run the batch file "BuildNB.bat" and that will generate the .nb and .nbh files, they were removed to reduce the size of the archive.
You may also need to install the VC8 Runtime first, that can be found in the archive:
"tools\vcredist_x86.exe"
There is a tool from Ervius (I think that it is called "packages creator") that will convert cabs to OEMs suitable for cooking with.
Thank you mate, I'll try to make it compatible with Orange France SPV M650 AGPS
Maybe my starting element to come with Artemis community more often (actually my phone but Icook on my old Prophet at this time).
Good job
Hey guys,
This seems promising. I've just installed Tom's latest but have been troubled by bugs (it happens) since he's no longer responding to queries I decided I needed to learn to cook one myself (should be fairly straightforward).
Perhaps we should pool experience & resources and work together, I mean if you look at the activity in the Kaiser forum, you'd be forgiven for feeling a bit left out.
One person could design gfx the other sounds etc. Otherwise I might swap my Artemis for a Kaiser (yes I've been begged!!)
Forgive me if this seems like a pipe dream...
More screen shots....
Here are some more screen shots:
daniel.bigred said:
Hey guys,
This seems promising. I've just installed Tom's latest but have been troubled by bugs (it happens) since he's no longer responding to queries I decided I needed to learn to cook one myself (should be fairly straightforward).
Perhaps we should pool experience & resources and work together, I mean if you look at the activity in the Kaiser forum, you'd be forgiven for feeling a bit left out.
One person could design gfx the other sounds etc. Otherwise I might swap my Artemis for a Kaiser (yes I've been begged!!)
Forgive me if this seems like a pipe dream...
Click to expand...
Click to collapse
I agree, it would be nice to have an "open" ROM that the community contributes to, I hope that this would keep the Artemis platform alive for future releases of Windows Mobile.
P3350
Hi all... i am very new to cooking and still thinking of getting my feet wet... have a couple of questions...
1. I have a P3350 (Artemis with out GPS) and when i install all these roms they are sluggish when compared to P3300s. My friend has a P3300 and the same ROM is fater ... I tested it immediately after flashing by opening the windows folder and other apps... should i be doing any thing different to get my device up to speed?
2. The ROM on the rapid share (http://rapidshare.com/files/13046620....3_NBH_ROM.zip) is this a directly installable ROM?
3. What should i be doing with the 'changed files'.
Sorry if i am sounding noob...
veereshpm said:
1. I have a P3350 (Artemis with out GPS) and when i install all these roms they are sluggish when compared to P3300s. My friend has a P3300 and the same ROM is fater ... I tested it immediately after flashing by opening the windows folder and other apps... should i be doing any thing different to get my device up to speed?
Click to expand...
Click to collapse
I don't know of any, but I am looking into a similar issue that I see with my orbit, I think that I am going to look at the XIP region of the ROM to see if there is something device specific there, sorry for not being much help.
veereshpm said:
2. The ROM on the rapid share (http://rapidshare.com/files/13046620....3_NBH_ROM.zip) is this a directly installable ROM?
Click to expand...
Click to collapse
Yes, this contains everything but assumes that your device is already running the SPL and only contains the OS portion and not the radio. Look at the link in the first post for help on flashing cooked roms.
veereshpm said:
3. What should i be doing with the 'changed files'.
Click to expand...
Click to collapse
These files in the zip should replace the existing ones in the kitchen on rapidsahre.
veereshpm said:
Sorry if i am sounding noob...
Click to expand...
Click to collapse
No problem, we were all like that, I am still learning as I go.
please inform - this pre-built rom, what is it contains of?
set of programms, etc...
And what about memory leaks?
Thank you
Freshup Roms...
Good try for this new rom, but i find the home-skin not stylish enough (dated too soon).
Why not create a rom with Greatball's today screen, see http://forum.xda-developers.com/showthread.php?t=402021
This is the most stylish skin (with SPBMobile 2.1) i have ever seen (last one with analog clock).
Together with Greatball's Samurai Diamond Weather + Night
http://forum.xda-developers.com/showthread.php?t=402124
Would be the most fresh looking rom ever
In combination with latest msn, SPB-backup,PPCBackupcontacts,...
Who can do this & freshup our Artemis for a long time ?
Thanks,
Cheers!
Innovator
mpattman said:
Hi,
I would like to share the kitchen that I use to build my personal ROM. It's SYS and XIP were ported from the stock Diamond 1.93.456.2 WWE ROM that Tom made available and the kitchen is Bepe's kitchen.
Here it is:
http://rapidshare.com/files/130210385/Artemis_Diamondish_6.1_Build_19965.1.2.3.zip
I hope that it will be useful to some of you.
Matt.
UPDATE: I have made a few changes in the OEM folder, I have added Advanced Config, added a patched htc home for the weather and made some changes to the registry. The changed files are in the attached zip.
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/130466202/Artemis_Diamondish_6.1_Build_19965.1.2.3_NBH_ROM.zip
(Usual rules for cooked roms, i.e. USPL etc.. - http://forum.xda-developers.com/showthread.php?t=331845)
Here are some screen shots:
Click to expand...
Click to collapse
When an Italian version?
I have no plans to produce any other languages, but the source to the kitchen is all there for someone to translate to suit thier needs.
Ok, I've tested and make my first Artemis ROM (for test use for the moment).
I've been implemented Orange AGPS drivers but no luck no automatic connexion at the moment when GPS is activated so, I'll make more try. So I've removed some components (Adobe flash & reader, Diamond Keyboard and some little thing) that I don't want and this ROM is stable and fast...very fast coocked with NETCF3.5 Now I'll translate it to French if I've time to that more than my future release
Just one thing mpattman : why to release this kitchen with NETCF 2.0 and not directly 3.5 ?
And the last Word : Thank you mpattman !!!
I can not down your ROM and MYkitchen,please get it to FTP,thank you.
Thanks a ton...
Thanks MPattMan...
I am downloading the kitchen, and will try understanding stuff... will post if i have any doubts... do u have any guide on how to do stuff like adding the programs that i want ? ... i will be more than willing to help, test and learn.
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
You may want to have a look at ababrekars SYS and XIP porting guide in Elf section....
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
2. Just replace the wince.nls version in the SYS\WINCENLS_WWE with the CHS one you have.
3. Modify all the MUI files and registry as to point to your Language of choice.
4. The OS.NB is needed as the shell/container for your new cooked ROM because it's the requirement for using the Tadzio's tools. So, leave it as is.
5. Cook the ROM.
At least that what I did when doing my Hermes version long before.
Cyphol.
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
please correct me if i was wrong..
afaik, XIP part is the same for every language,
also in the end part of the building, you need os.nb only as a "template" to rebuild the new one... it wasn't really use the content inside...
normally, you need to copy all content in the dump_xip to the ROM\XIP directory...
to learn about the process of diamond kitchen (which is based on kaiser kitchen so i assume the tools are the same), i think you better use the kaiser ROM, and try to dump it.. and see what directories and files are generated...
in kaiser kitchen, to rebuild the rom you need 3 dirs, OEM, SYS, and ROM\XIP
cyphol said:
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
Click to expand...
Click to collapse
He would need to if he wants a different OS build. Or am I wrong?
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
of course....
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
Yes, that's right for the reason. If that's the only reason, why don't you replace the core.dll
thank you everyone for your advise.
looks like i just need more reading.
thank you cyphol, pkoper and teamee for your kind advice.
I have replace the SYS\wincenls_WWE folder with SYS\WINCENLS_0804. i believe this might be one of the problems. i will try replacing just the wince.nls within the folder instead of replacing the entire folder.
files which i have modified includes the boot.hv, user.hv, default.hv, boot.rgu, a bunch of other rgu as well. i might have missed out a few others. so i will check again.
thanks everyone for your kind advice. if there is any other suggestions or points to take note of, please kindly let me know.
your guys rocks! XDA rocks!
Dear All,
After messing around with the tweaks here on the forum, I wanted to build my own ROM.
I want it to be:
-Fast (With the known registry tweaks)
-Stable
-Graphically nice
-With the apps I like
-To have Dutch language, with an extra WWE-XT9
-With the latest OS version (.721)
My plan to do this is:
-Get a good (modded-) BaseROM (I have SkippyCentraal 2.8 in mind)
-Remove all unwanted programs
-Exchange the OS.nb (128Mb, .273) with the extracted OS.nb (.721) from a different (non-Dutch) firmware
-Cook it together and flash it to my Diamond
-Make registry changes
-Dump my own (cooked and tweaker .721-) ROM
-Compile again
-Post it here ;-)
Is this just the way it works? I have just read Lolek47's Tutorial Thread
http://forum.xda-developers.com/showthread.php?t=413782
and it seems that simple?
Please advice...
Thanks in advance!
BR Bart
The Netherlands
When I saw the tutorial I thought it is simple. But when really doing it, it is not that simple: my cooked ROM's (so far all of them) aren't even starting up. Hangups all over the place.
My advice to you is: find a good kitchen and just do it. Eventually you wil cook a decent working ROM. But don't expect to do it in a few days (like I did)
BUMP!
ive got the same plan as burdie!
But just in the WWE language, somebody knows a good tutorial?
would really like it!
yourz,
ruubs
I can offer some advice, coming from cooking on a Kaiser:
I think everyone would like to make a ROM with all those things listed While it may not be impossible, it may take quite some time tweaking it just the way you want it
1. You can't use any ROM as a base ROM unless it is chef-friendly. This means that all the .dsm and .rgu files are included. If they aren't, I'd recommend starting from scratch on the latest or most stable base ROM
2. Removing programs should be easy, because all the Diamond's are organized in .dsm files instead of all being dropped in the OEMAPPS folder like the Kaiser
3. I don't really see the point of having a WWE XT9 dictionary with a dutch ROM, care to explain. Also, what are you trying to do with replacing the OS.nb?
4. I'd not recommend dumping the ROM off your diamond then compiling it. Why would you go through all that trouble when you could just make the registry tweaks you want and then cook it up?
i'd be glad to elaborate on any more of these or answer any other questions you have
ruubs said:
BUMP!
ive got the same plan as burdie!
But just in the WWE language, somebody knows a good tutorial?
would really like it!
yourz,
ruubs
Click to expand...
Click to collapse
hi,
short but very usefull rules from
http://forum.xda-developers.com/showthread.php?t=508293
nothing is better than (electronic) paper ...
Hello everyone. I'm beginning a ROM development, using "WM 6.5.5 Build 23563 - All Langs, All DPI, All Resolutions" sources. My phone is HTC Touch Diamond. I have read many tutorials, but i completly miss the part working on XIP.bin, OEM and ROM folders. My primarty question is, where to find them?
I know i can take the SYS folder from the source, depending on language and DPI/resolution, but i really can't figure out where to get those important files in OEM/ROM and XIP.bin.
Thanks for helping, really!
dude xip udon't need if u use elk and da_g roolups as its already in msxipkernel..
ok .rom is also not needed as ot contain device specific files and drivers..
i dint understand that there are video tut on chef central by queppc...why r u making extra thread..u must read befire posting
u m
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