Related
sorry for this new thread but i have searched all wiki and part of forum and i haven't found any solutions.
Q1 - In LVSW rom, autorun is enabled, but in Black edition, it is disabled. can any one tell me how to modify this, i think it was defined in registry. but where? i found some things here:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Windows\\autorun.exe"
"AutoRunCFG"="\\Windows\\config.txt"
"AutoRunFlag"=dword:1
"AutoRunType"=dword:1
"TurnRadioFlag"=dword:0
Q2 - how to modify OS vesion which is displayed in Device Information.. for example:
LVSW's os vesion is always 3.22.200.2
Black 1.2 is 3.22.200.4 but Black v2.0 is Pro Black 2.0
thanks in advance.
I am not sure on your first question??
On question nr.2 this can not be any simpler. I searched the registry for the phrase "Pro Black" and found the key and changed it to whatever and that showed up under device information.
qooqoo said:
sorry for this new thread but i have searched all wiki and part of forum and i haven't found any solutions.
Q1 - In LVSW rom, autorun is enabled, but in Black edition, it is disabled. can any one tell me how to modify this, i think it was defined in registry. but where? i found some things here:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Windows\\autorun.exe"
"AutoRunCFG"="\\Windows\\config.txt"
"AutoRunFlag"=dword:1
"AutoRunType"=dword:1
"TurnRadioFlag"=dword:0
Click to expand...
Click to collapse
Extended ROM autorun is achieved by the following 4 steps:
1. include checkautorun.exe and checkautorun.lnk under \windows in your ROM
2. make sure that checkautorun.lnk is in \Windows\Startup. This is done with a line like
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
in initflashfiles.dat
3. add the following registry keys (or make sure they are there):
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunType"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
4.Then of course you will need to have an extended rom with autorun.exe and config.txt + other stuff in it to run.
I hope this helps.
--eluth.
HKLM\Software\OEM
The key ROMVersion..change it to whatever you like..
thanks a lot Halldor, eluth and bernardryan, i will try.
Remember to set AutoRunFlag to 0
Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)
can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff
Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well
teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.
You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??
mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive
mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok
I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...
Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?
Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files
Looks pretty complicated with no real guide, will look into other kitchens!
I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?
Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar
Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"
Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA
It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.
I've been reading an gathering information for weeks now to build my own personal ROM. Since I'm unable (at the moment) to build one from scratch
Somehow it doesn't seem to work for me and I could not find an answer to my problems. I really hope some ROM Guru is willingly to help me out here.
I've used the Diamond Kitchen to extract the NBH files. And like it should it creates the OEM and SYS folders when you don't use protected ROM's like Dutty's, Swtos or Bepe's.
I've tried multiple ROM's to rebuild for my personal needs. And here are the most common problems I've encountered:
- Diamond (or Raphael) Volume Control does work. Even when it's included correct in the ROM. Reinstalling Volume Control after flasing using a CAB does work strange enough.
- The sound settings panel won't close after changing sounds.
ROM's I've tried to personalize:
- Panosha
- TOR (SubZero)
- SwiftBL
- VIC Lite
- And probably a few other ROM's I managed to extract (using the kitchen).
I've read some threads about the same problems but they seem to be part of a ROM thread instead of a specific "cooking thread". That's why I started it here.
Do you experience the same problems or do you have some good ideas than please let the rest of us know
I have the same problem
Everything seems OK, except the damned sound configuration.
If someone has an answer, we would appreciate it very much.
Thanks in advance...
Thanks for you reaction. Concerning the Volume Control, there is a way to get this to work. Just add a CAB that you call using the config.txt.
It's not ideal but it should work.
Unfortunately this procedure can't be repeated for the sound setting panel
I played with it a lot and even if I do nothing with the ROM, this sound config problem occurs. I extract the ROM and then rebuild it without modifying anything. This looks like a kitchen problem I thought.
I use Surface Kitchen v1.01. You another one, so this is a little confusing
Edit:
Maybe we can do the same without using those settings but direct in the registry?
Someone knows those keys?
Been using Kitchen 1.0.1 for a couple of days now as well. Updated the programs that were out of date. Did not help.
I also get always this error, could it be the cause?
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
tararura said:
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
Click to expand...
Click to collapse
Well, most of the times this fault is there, its a mistake with your new or edited rgu file like \\ or forgotten empty last row.
regards
Anja31
I recommend you guys try cooking the 1.93 official ROM .., i cooked a personal one for me .. no problems at all
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
- The sound settings panel won't close after changing sounds.
Click to expand...
Click to collapse
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Thanks will try that one as soon as I can.
Had one crazy thought. Since there are some replies from some real cookers here I was wondering about the next thing.
At the moment I always select option "1" in my kitchen. So I don't rebuild it (option "2"). It shouldn't but is it possible to have more success when using option "2"?
I tried all variants....
select 1 (yes) -> Access denied
select 2 (no) -> the message will appear for a lot of files... even when you always select 2 the ringtone panel won´t work
select 3 (all) -> access denied
So IMO it has no impact, which option you take...
I choose "1". I just want to cook the ROM.
Ah.. now I understand what you mean... the question at the beginning...
of course you have to select "1"...
I talked about the overwriting question (screenshots in post before)
First of all: thanks for this thread...I was going crazy with this issue..!
Has anyone tryied the reg.key posted before?
PS: @maccune...did you tryied to recook swiftbl?! How?! Is it not a protected rom??
Might be wrong about SwiftBL. Tried so many that I could be mixing them up
Tried so many because I hoped there would be one that would work just fine.
If it was up to me I'd use TOR v5 since it's basic and still a Diamond build.
Also the cooker told he didn't mind if people would use his ROM as a base ROM for your kitchen
duttythroy said:
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
Click to expand...
Click to collapse
Hi dutty, what do you use to cook and protect your rom ? a made home version ?
Sorry, wrong thread...
Caspertje19 said:
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Click to expand...
Click to collapse
Wohoooooooo!
It works... really great... perfect...
I also was going crazy to this issue....
now its solved.....
thx a lot.....
BUT: Another question: How can I add this as RGU File to ROM?
Here is my first build of a diamond rom,
I Have taken a cooked rom and Modifyed/tweaked a little and am now looking for some help to finalize this
The rom is fully working but i would like some help with 1 or 2 final tweaks
1st problem:- I cannot get the SDautorun to work, i have added the line "EXEC:\wondows\sdautorun" to config.txt and sdautorun is in the windows folder but nothing happening sdconfig.txt is in internal storage and formatted correctly (copy the folder with cabs and sdconfig.txt to artemes sd card and no probs)???
2nd problem :- I cannot get the custom folder icons working? please post any dll and shortcuts for me (The folder icons i would like to change are for folders named "Accessories, Applications, Bluetooth, Communicatons, Games, GPS, Media, And system tools)
3rd Problem :- where do i change the version ID for device info to my name?
4th Problem :- How can i change the default regional settings to location UK from US
5th Problem :- I can't seem to move the bluetooth explorer shortcut to the bluetooth folder
6th Problem :- How did Duttythroy get his internal storage icon to opem file explorer at Internal storage and an icon of the internal storage?
7th Problem :- where is the default WM6-Green theme stored as i would like to change some colours before Customization mainly the green in the next and skip buttons straight after hard reset
8th Problem :- I have also tried to get the .NET/SLQ Server fix cooked into my rom but after cooking Netcf2,slqserver,then netcf3.5 manilla wont load but if i remove cf2 manila loads the beejive IM wont load cos the fix hasnot been done any help Here?
all you chefs out there i would be gretfull for any help on the above issues for me as having this rom on my diamond would be great (For me anyway)
Would love as much help as possible,
I would like to thank all the developers in the forum for creating the tools neaded
also I wish to thank the chefs for there Roms i use as a base and packages used
and a special thanks to you for stopping by reading and making your helpful comments for me to learn more.
rom cooming soon in kitchen format for the chefs to look at to fix my problems
download here (uploading)
1: I think you might want to work on this wise saying you have in your sig yourself "Search, Read, Learn and you will be wise............ "
2: Am I mistaken or are you cooking for the Artemis? This is the Diamond forum.
adwinp said:
1: I think you might want to work on this wise saying you have in your sig yourself "Search, Read, Learn and you will be wise............ "
2: Am I mistaken or are you cooking for the Artemis? This is the Diamond forum.
Click to expand...
Click to collapse
1: searching has got me nowhere thats why i am stook with these points, i am proberly searching in the wrong place or i am searching too hard and missing the point.
2: I am cooking for diamond. only mentioned artemis as i tested the sdconfig.txt file and folder on it
This generally goes against my spoon-feeding, but:
1: Check if you have a typo. Provisioning also means that argument should start from the 6th character, in this case:
EXEC:\Windows\SDautorun.exe bla bla bla
2: Icons are generally links
For example: in folder Z, you've got someicon.lnk
Which is linked to somedll,-45 (icon in position 45)
3: Search & you'll find. The best way to learn cooking, is to actually cook. You won't learn anything if everything is given to you on a silver plate.
4: There are some interesting links on msdn about provisionining. There even is an example how to change regional settings.
5: ?!? Care to be more explicit? Check the BTFTP package.
6: Ask Dutty directly. ^.^
7: hint: SYS folder (or use the damn search). And THIS proves you didn't even CARE to take a look at WHAT you're exactly cooking. I must admit, that the file isn't always present, you must sometimes take a look at the rgu.
8: You'll have to cross-reference. I'm guessing you have left both NetCF 3.5 and 2.0 enabled in the registry...
adwinp said:
This generally goes against my spoon-feeding, but:
1: Check if you have a typo. Provisioning also means that argument should start from the 6th character, in this case:
EXEC:\Windows\SDautorun.exe bla bla bla
2: Icons are generally links
For example: in folder Z, you've got someicon.lnk
Which is linked to somedll,-45 (icon in position 45)
3: Search & you'll find. The best way to learn cooking, is to actually cook. You won't learn anything if everything is given to you on a silver plate.
4: There are some interesting links on msdn about provisionining. There even is an example how to change regional settings.
5: ?!? Care to be more explicit? Check the BTFTP package.
6: Ask Dutty directly. ^.^
7: hint: SYS folder (or use the damn search). And THIS proves you didn't even CARE to take a look at WHAT you're exactly cooking. I must admit, that the file isn't always present, you must sometimes take a look at the rgu.
8: You'll have to cross-reference. I'm guessing you have left both NetCF 3.5 and 2.0 enabled in the registry...
Click to expand...
Click to collapse
sorted No5 My mistake, totaly overlooked this one while moving all the files into folders, going to work on the net cf issue first as this is holding me up next everything else is cosmetic and i can cope with that.
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