Related
Hi there,
Ok, i read the wiki and forum for a couple of days now and i learned quite a lot of it, but some things are a bit unclear or i'm confused (too much input in that spare time ). If i extract one of the Roms you guys cook here, do i just need to replace all the .mui files in that rom with the ones in my language, or i'm missing something here ? Since this would be pretty easy, i can't believe that's all, someone might give me a hint?
indeed, it would be too easy, you should check the thread in stiky
http://forum.xda-developers.com/showthread.php?t=307968
you will see that no one has been able to develop a localized version till now with only replacing the mui files/folder
Hi gurus,
I have tried several official rom and I would like to know on how to I release the ULDR as Bepe had mentioned in his rom thread on the official roms.
i have just learn cooking and have managed to alter offical roms to my likings. but the storage space is just not enough on the official roms, even after cooking.
thus, can any kind chefs share with me on how to release more storage while cooking. I believe this would be relatively useful for all newbie cookers.
Thanks a million!
ruffruff said:
Hi gurus,
I have tried several official rom and I would like to know on how to I release the ULDR as Bepe had mentioned in his rom thread on the official roms.
i have just learn cooking and have managed to alter offical roms to my likings. but the storage space is just not enough on the official roms, even after cooking.
thus, can any kind chefs share with me on how to release more storage while cooking. I believe this would be relatively useful for all newbie cookers.
Thanks a million!
Click to expand...
Click to collapse
clear out ALL the crap, ringtones, wav files, welcome center, autoupdate, and apps you dont want / use.
walshieau said:
clear out ALL the crap, ringtones, wav files, welcome center, autoupdate, and apps you dont want / use.
Click to expand...
Click to collapse
even if i do that, my total storage is just 80mb.
how do i gain more?
can you teach me?
ruffruff said:
even if i do that, my total storage is just 80mb.
how do i gain more?
can you teach me?
Click to expand...
Click to collapse
what tools are you using to extract the nb files?
walshieau said:
what tools are you using to extract the nb files?
Click to expand...
Click to collapse
i am using the diamond kitchen posted in this forum.
kind of straight forward, like pressing 1 or 2 to cook or rebuild roms
You have to break it into steps, and stop after XIP merge with OS (just before buildOS)
This is where you can add, remove anything. Packages, etc.
i have managed to cook up a good storage space rom with the advice from the seniors here as well as the wikis.
but now i have another problem.
i have managed to turn one of the latest official WWE rom into Sim. Chinese. although, i have replaced all the wince.nls in the WWE rom to the asian WWE, but after cooking and flashing, it does not shows the chinese regions.
i have tried several ways but still couldnt find a way to solve this.
for replacing wince.nls in roms, is there areas which i need to look at, or files i need to replace?
btw, the cook WWE rom is entirely in chinese now on my device, the only left unsolve is the wince.nls.
one side track question, how do i disable error reporting? every now and then i received a pop up screen saying that certain task has caused an error ...
can anyone kindly help?
Ruff, if ever there's anything you don't know how to do with tools, just do it on your handset, dump and rebuild the rom. As simple as that.
So just disable the error rep and happy dumping.
^.^
i almost give up here.
i have replace the default.hv and user.hv with the one found in the CHT officlal rom but still, my Cooked WWE rom is still unable to initialise the asian wince.nls ...
what am i missing here?
can any kind soul shed some light?
2nd issue> connectionsetup keep returning an error in the first boot. how do i stop this?
hi all,
thanks for everything.
i just found out why the wince.nls is not used correctly.
after replacing the os.nb in the ROM\ folder with the os.nb from the offical chs rom, it works.
although, i dun understand why but it works now. chinese region is selectable.
i also found that the temp\dump_XIP is practically useless, as the kitchen build os without using it at all ...
guess i still need to figure out more stuff manually and stop using the CMD script. it may be the CMD scripts that is set to extract xip from os.nb when cooking rom. thus, rendering the dump_xip not being used.
thanks. if there is any advice for me, please kindly let me know.
i love XDA and thank you JugglerLKR so much for the kitchen.
Hi ruffruff,
Could you please give me any advice on how to change the OS language ? I had some translation experience on the htc wizard but it was a nightmare. I see it seem easier on diamond roms. It would be great If I could change some of the "plates" cooked on here in Italian. I really hate having the phone in wwe.
smogdragon said:
Hi ruffruff,
Could you please give me any advice on how to change the OS language ? I had some translation experience on the htc wizard but it was a nightmare. I see it seem easier on diamond roms. It would be great If I could change some of the "plates" cooked on here in Italian. I really hate having the phone in wwe.
Click to expand...
Click to collapse
hi smogdragon,
i believe you already have a kitchen at hand.
if so, you will need to find a italian rom first and dump the rom. after which, save the dump. then find the WWE rom which you like and wish to change it to italian. dump the WWE rom and replace all the 0409 packages and files to your italian packages and files which you have dump earlier.
cook the rom and flash.
finally, i have everything working out nicely.
ram available after first boot is still not as much as the senior cookers here.
i have 2 requests and hope that some kind soul or seniors can help me with:
1) Can anyone release to me the correct backward compatible netcf3.5 for rom cooking?
2) Can anyone release to me the 20270 XIP and teach me how to port it to my cook rom?
thanks and hope that some kind soul can assist me.
I see Nothing is changed. DO you replace all the files by hand ? Or have some kind of automated procedure ? The problem for me is I've not seen any .93 build in italian yet so I don't know where to find the files without messing the build.
smogdragon said:
I see Nothing is changed. DO you replace all the files by hand ? Or have some kind of automated procedure ? The problem for me is I've not seen any .93 build in italian yet so I don't know where to find the files without messing the build.
Click to expand...
Click to collapse
u dun really need the exact build for the italians mui files.
just find an available italian rom and extract all the mui files out.
in english rom, replace those 0409 folders and files with your MUI files by HAND. hehe, no pain no gain ...
do more reading on the forum. i am no expert. like you, i am also a newbie/noob in rom cooking. just trial and error. i too need guidance from the expert but in the meantime, when they are not responding, you have to DIY...
cheers
ruffruff said:
u dun really need the exact build for the italians mui files.
just find an available italian rom and extract all the mui files out.
in english rom, replace those 0409 folders and files with your MUI files by HAND. hehe, no pain no gain ...
do more reading on the forum. i am no expert. like you, i am also a newbie/noob in rom cooking. just trial and error. i too need guidance from the expert but in the meantime, when they are not responding, you have to DIY...
cheers
Click to expand...
Click to collapse
Hi,
I'm trying to cook my own rom to convert the official Russian rom into english.
I've a quick question about the replacing the 0409 folder.
I'm going to be going from 0419 folders (russian) to 0409 (english), do I delete the 0419 directories and just add in the 0409 ones, or do I have to delete the 0419 folders and then rename the 0409 to 0419.
I'm guessing just delete the 0419 ones and stick in the 0409 instead, but want to make sure.
Is there anything else I need to do. I guess I'm looking for all the 0419 folders in the \OEM and \SYS directories?
Does anyone know if this will get around the region lock on a Russian Diamond?
Plus is there anything else I will need to do?
Do I have to do anything with XIP, that's something I'm really not sure about?
Cheer
Andrew
Hi here i release an OLD style kitchen based on Bepes tools
I have taken bepe's kitchen and created some batch files to make it a one click extract and one click build and flash
I was so used to the old style kitchens and when they stoped working (failing at xip extract) i was looking for something that worked that i could use easly.
I found bepes kitchen, and it was nearly the same so i ported the batch files from diamond kitchen 0.4 to make this.
this kitchen uses the new style packages but has the look and feel of the diamond kitchen 0.4
I am still looking for the package creater that makes these NEW style packages but can't seem to find it now so if anyone has it please drop me a link so i can include it in the kitchen tools
download link ---->
http://rapidshare.com/files/217781904/Kitchen.rar
Instructions
1 place you RUU_Signed.nbh in the baserom folder
2 click on !Begin
3 Dont touch anything until extraction is finished (approx 5-10minutes)
4 Modify your packages
5 click on !Cook
6 wait until the htc rom tool loads
7 select diamond in device, os.new.nb as the source OS and save as kitchen/RUU_Signed.nbh
8 close htc rom tool and Custom RUU flash tool will load
9 flash and enjoy
......
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Is the Rom dump protected after cooking?
DefJamz said:
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Click to expand...
Click to collapse
this dumps the rom into the OEM, SYS and ROM Folders if you want the EXT folder download Bepe's tool below OEM2EXT
RideTheTube said:
Is the Rom dump protected after cooking?
Click to expand...
Click to collapse
not had time yet to try and test if i can rebuild a cooked rom, will have a go tonight and post my findings.
This is Bepe's Kitchen automated by batch files so he is the best person to talk to about protection
sorry to be a little blunt but i am a noob when it comes to cooking that why i found something that worked for me and made it a little easyer to use,
Protected Rom? Almost Rom when rebuilding, it will delete all dsm file, so you can't use package tool.
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
garymeg said:
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
Click to expand...
Click to collapse
I had the same problem and it was a XIP "mess-up". however I can't help you more than this.
try asking here: http://forum.xda-developers.com/showpost.php?p=3575850&postcount=131
i simply do NOT understand why build a tool that deletes stuffs that are important for cooking. isnt rom cooking supposed to be an open project for ALL? i mean some chef have the donate button in their sigs. but their rom's locked. it isnt fair to those (like myself) trying to learn how to cook a rom. i mean, i try to compare official roms and custom roms insides. what are the difference. it's by comparing that people learn to differenciate. and i would say BAHHH to missing rgu and dsm files!!
My thoughts exactly... Alas...
it is ironic, that NONE of the chefs who lock roms/doesn't supply kitchen/ask for donation wrote the code themselves. In short - everybody operates on stolen/leaked or any other way obtained code.
Ok, there are authors who created tools. And those guys have full right (and reason) to ask for donations fro that - TOOLS.
Otherwise - it's just funny. it's like stealing a car, and then asking police to protect it....
no panic.
at normaly old style kitchens never delete dsm'S.
and if you delete manualy dsm'S, you get all files in folder.
i think, with protect rom it means, no recookable roms.
it stops at point 1 or in the first step by using BEGIN! with a message like
"rom is smaller/bigger than/at starts" or so. excuise me, i've forgot the exactly words.
for checking of recookable rom i checked it with "htcRIE_0.5.0.12.exe".
it shows you all files with oem/sys - folders. but the oem can be empty. you find the oem-files than in sys-folder.
these points are my thinks that i see/learned by beginning flashing and cooking until now. other people can see/learn other thinks so dont dismiss me, if you are not my oppinien - but you can dismiss my english
Htc rom tool
Is it possible to use this for the Fuze?
EDIT: I found HTC tools with support for more phones on this thread a couple posts down
Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San
I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative
I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers
wooooooow thanks a lot buddy finally we have it also !!!
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!
You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
kitchen tools attached in the first post.
enjoy
dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers
thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!
The next post is up
cheers
dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....
trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?
well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool
good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck
Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P
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