Related
FOREWORD:
I would like to keep this thread EXPLICITLY for people who want to learn how to MANUALLY cook and the questions surrounding the topic.
If you are a "GOD MODE" and you are more interested in insulting people for trying to learn DONT read this thread
n00bs DO YOUR RESEARCH!! - See links in my Signature and at the bottom of my second post
If you are answering a question PLEASE answer it fully and as simply as possible.
WELCOME TO ROMDonalds!!!!!!!!!
This kitchen is designed for those users, like me, who have been using their devices for a while and want to learn the methodologies behind hand cooking a ROM. By hand cooking I mean manually adding OEM software, adding CAB’s so they don’t have to be installed after flashing, hand editing registry hives and such like.
Don’t get me wrong GUI kitchens are excellent but, to fully understand the processes that go on behind cooking your own ROM,I feel that it should be done manually so you can see and hopefully understand what happens at each stage, so you could say that this is more of an educational kitchen.
.
.
How It Works
There are various stages to cooking a ROM, so when you run “ROMDonalds.exe” you will find a group of files, ordered by number, logically, you start at number 1, and follow the process through to completion.
After running “ROMDonalds.exe” you will find a new folder on your desktop called “ROM Donalds” this is your kitchen.
Inside each of these files are all the various pieces of software you will need to complete that particular stage of the process in addition to this there is an instruction manual that walks you through each step, with background information on what is happening not just the required steps.
.
.
The Kitchen Software
All of the software in this kitchen is available in other kitchens in various forms, some of the software has been slightly edited from original form but not by much, so I do not profess to having produced some revolutionary cooking software as it all currently exists.
The difference is that instead of having a folder full of tools with strange looking names, which would be intimidating and confusing to a new user, everything is sectioned out with instructions.
.
.
Thanks:
Special Thanks to Midget_1990 for helping with the software
Thanks to all those who originally designed the softwares used in this kitchen, namely:
Tadzio - for his tools
bepe - for his tools
the-equinoxe - Splash Screen Tools
dutty - NBH Tool
also thanks to anyone I forgot (sorry about that!)
.
.
Disclaimer
I accept no responsibility for devices getting screwed!!
.
.
Download Links :
In the second post of this thread you will find all the required download links, patches and Instruction Manuals, detailed as follows:
ROMDonalds Kitchen : This is your base kitchen
Animated Startup Screens : A pack of various animated startup screens
Selection Of OEM Apps: A large selection of pre-created OEM packages ready for cooking
.
.
Download Links
Release Notes :
1) If you find any errors with the instructions please detail them in the thread, but also PM me with the error and necessary changes so I can update the "How To Cook.pdf"
2) This has been tested as much as possible on Vista and XP and fully works on both (for me!!)
3) Section in "How To Cook.pdf" on converting CAB to OEM needs refining, if you are new to this ignore the section and just use the OEM apps i have included until i make this section better
4) There is a folder in ROMDonalds called "09-AdvancedTools" . . some may asy why... the answer is that these "Advanced Tools" are the most useful ones i have found in my travels while creating this kitchen, I have not written about each one in the "How To Cook.pdf" but i may in the future. If you need help with these ask in the thread and i will update my first 2 posts accordingly.
.
.
Instructions
1) Download at least the following: Instructions, ROMDonalds Kitchen, Selection Of OEM Apps (Animated Startup Screens are just an extra if you want them!!)
2) Extract "ROMDonalds.rar" then RUN "ROMDonalds.exe"
3) Extract "Selection Of OEM Apps"
4) READ INSTRUCTIONS SLOWLY AND CAREFULLY
5) Enjoy
.
.
Download Links
Instruction Manual:
Sendspace - Last Updated : 29/07/07
Megaupload - Last Updated : 29/07/07
Rapidshare - Last Updated : 29/07/07
ROMDonalds Kitchen :
Whats Been Updated? - Advanced Tools Section Updated, initFlashFile Generator FIXED
Sendspace - Last Updated : 01/08/07
Megaupload - Last Updated : 01/08/07
Rapidshare - Last Updated : 01/08/07
Animated Startup Screens :
Sendspace - Last Updated : 28/07/07
Megaupload - Last Updated : 28/07/07
Rapidshare - Last Updated : 28/07/07
Selection Of OEM Apps :
Sendspace - Last Updated : 28/07/07
Megaupload - Last Updated : 28/07/07
Rapidshare - Last Updated : 28/07/07
Other Useful Links :
Available Radio ROMs : Click Here
2.10.Olipro (HardSPL v7) : Click Here
Hermes Upgrade Guide (mrvanx) : Click Here
Hermes Wiki : Click Here
Google Search Forums : Click Here
.
.
Attached Files
Notepad 2.zip This is a better text editor then notepad!
FOR BATTERY ICONS CHECK THIS THREAD
NEW THEMES PACK
NEW PACKAGE CREATOR:
Instructions
1: run the package creator
2: select open CAB and direct it at your CAB
3: When Cab Analyzer comes up, select extract (the icon 3 to the left of the folder icon with "MSCE" undernearth it) THis will open up the "extract" windows, you will notice that it is already pointing at a folder in your C:\XXXXX (XXXX will be the name of the CAB) you MUST extract it to this directory (it is only a temp and it will be moved to desktop in abit)
4: once extracted close the CAB manager, then the initflashfiles tab will open in the package creator. Select "enable options" then select your CUSTOM shortcuts (the initflashfiles.txt will already have the intended shortcuts in it, these are extra ones if you want any) when you have finished here press apply and done
5: set name for the option.xml and the section you want it to show in, then press complete package. On your desktop now you will find your package!
hope you like it, it is really fast once you get used to it!!
.
.
First to say you thank you. I was waiting for this. Great work Man.
hi - I like the name , i too believe in alot of manual cooking because i feel its the best way to learn. I use most of your tools and also htc rom tool by dark simpson. I'll have a look at your animated startup screens - been looking for those.
well done mate you deserved it. although i busy with my new toy in my sig I will give your kitchen a try to see what i can dish up for myself.
duttythroy said:
well done mate you deserved it. although i busy with my new toy in my sig I will give your kitchen a try to see what i can dish up for myself.
Click to expand...
Click to collapse
You will find the kitchen very familiar, it has nothing you wont have used already!! (although you may want to look at the advanced tools folder!!)
i would really appreciate it if you could cook and follow my instructions just to see in there are any obvious mistakes (Other than spelling & grammar!!)
Thanks alot
Great work man... will give it a spin later. Thanks
Nice work mate
Cooking for the masses eh, do you have a "drive through"
benec,
The combined clean battery and 3G icon cab does not work. I get a message saying that i dont have permissions to install that cab.
Trying to overrite the dll file into window also has the same effect
etreby71 said:
benec,
The combined clean battery and 3G icon cab does not work. I get a message saying that i dont have permissions to install that cab.
Trying to overrite the dll file into window also has the same effect
Click to expand...
Click to collapse
ok, i hadnt tested that, sorry about that, ill see if it can be fixed!!
The pdf says to run the powertoys program that is in the ROM tools folder, where is the rom tools folder?
sprice82 said:
The pdf says to run the powertoys program that is in the ROM tools folder, where is the rom tools folder?
Click to expand...
Click to collapse
appologies: it should read:
XP [FONT="]users run “CmdHerePowertoySetup - XP.exe” this is found in the “ROMDonalds” folder.
Instructions Download Links Updated 29/07/07 [/FONT]
This is great, easy to digest information, great work piecing all this together and writing the pdf.
One thing I must say is I very much do enjoy the use of the visual package selection method, manualley cooking in the cabs is great but being able to check a box next to what I want is always a plus.
twist said:
This is great, easy to digest information, great work piecing all this together and writing the pdf.
One thing I must say is I very much do enjoy the use of the visual package selection method, manualley cooking in the cabs is great but being able to check a box next to what I want is always a plus.
Click to expand...
Click to collapse
I like GUI cooking too, please dnt think i am belitteling other Kitchen designers!
MY problem's with the GUI cooking method are:
1) YOU DONT LEARN ANYTHING - THE MOST IMPORTANT PART - THE IDEA OF THIS KITCHEN IS TO TEACH PEOPLE WHAT GOES ON WHEN COOKING
2) its lazy, as the install screen of ROMDonalds says "Getting Something Is Good, Doing It Yourself Is Better!!!" (im not saying its not a great idea that people can customise their own ROMs that fast, and have whatever they want included)
3) its hard to modify an already cooked rom (i.e. Black Satin on Pandora)
4) its not guaranteed to work, stupid errors thrown up with no option to fix
5) if you cant change the base ROM you are stuck with it, also what you think is a good base, someone else may say sucks and visa versa
6) there is way more OEM software about than CAB's so if you manually cook, you are not restricted by what is included int he kitchen
I created a kitchen like this so i could learn in the way I WANTED to learn, not with some of the hap-hazard instructions there are available.
I found that through using the instructions i have published i have learned alot about the stages of cooking, so now, when i look at other kitchens, and it tells me to "Dump Rom" or "extract XIP" etc, i know wats going on!!
(also when errors in the GUI kitchens come up, i have a MUCH better understanding of where and why the error has occured!!)
I hope people find it as usefull as i have!
I love this kitchen I have allready learned TONS from it, I am just saying it would be nice to be able to use this kitchen AND be able to use a GUI for adding more packages as well.
But I completly understand your thinking and I definently have allready learned alot!!!
And again I appreciate your taking the time to put this together with a great PDF walkthru.
I am also wondering if there is anyway to delete something from the windows dir after it has been copied elsewhere ? or if you can move files instead of copying them. I am looking to cooking in Opera and it requires a few files in a few diffrent dirs and I would hate to have copies of these files in the windows dir and the dirs they are suppost to be in.
twist said:
I love this kitchen I have allready learned TONS from it, I am just saying it would be nice to be able to use this kitchen AND be able to use a GUI for adding more packages as well.
But I completly understand your thinking and I definently have allready learned alot!!!
And again I appreciate your taking the time to put this together with a great PDF walkthru.
I am also wondering if there is anyway to delete something from the windows dir after it has been copied elsewhere ? or if you can move files instead of copying them. I am looking to cooking in Opera and it requires a few files in a few diffrent dirs and I would hate to have copies of these files in the windows dir and the dirs they are suppost to be in.
Click to expand...
Click to collapse
you mean to create 1 folder called "Opera" and have all of the dir's and files for Opera inside that folder so you can drop it into the windows dir on a dumped ROM?
this can be done altho im not sure how, i want to include this into my instructions but as i said im not sure on how to go about it, JJ did it with some of the black ROMs, Satin definately.
only thing i can suggest is to dump SATIN and see how JJ did it!!
If you find anything please post it here so i can include it, and ill do the same.
Unable to find default.hv & user.hv in dump folder and a couple other questions
Hello Bennec83,
Thanks for the informative kitchen tools!! I am hoping to create a custom made ROM from these tools.
Question:
I have dumped the recently released Dopod ROM without difficulty and am now at the stage (stage C before C.1) of finding the two files in the dump folder: default.hv and user.hv ...I performed a search and then manually looked for the files without success. I have followed the format for dumping and I may be missing something but these files are not appearing...Any suggestions??
Also, if I wanted to delete say windows auto update or other folders in this ROM without creating a conflict, this dumping section would be the appropriate area, correct?? I guess this is the part where trial and error occurs...correct? I am trying to maximize storage space without conflicts.
Thanks so much for your time,
vjgrace
bennec83
GREAT work m8! Just read your cooking instructions and they are superb. I haven't tried the kitchen yet, but from what I read it is pretty straight forward and very well explained !
Thanks for creating this, I will test in the following days and let you know of my experience
Again, great work and keep us posted of any changes...
Twist in regards to cooking in opera - there is no way to delete the files after they are copied out of the rom. I know it seems wasteful but that is the way it is. Most cooks hence keep the inclusion of this type of app down to a minimum because of storage space. Would recommend compression of opera.exe to use less storage memory - and find the oem package so you can use the rgu and initflashfiles.txt from there to make life easier.
vjgrace said:
Hello Bennec83,
Thanks for the informative kitchen tools!! I am hoping to create a custom made ROM from these tools.
Question:
I have dumped the recently released Dopod ROM without difficulty and am now at the stage (stage C before C.1) of finding the two files in the dump folder: default.hv and user.hv ...I performed a search and then manually looked for the files without success. I have followed the format for dumping and I may be missing something but these files are not appearing...Any suggestions??
Also, if I wanted to delete say windows auto update or other folders in this ROM without creating a conflict, this dumping section would be the appropriate area, correct?? I guess this is the part where trial and error occurs...correct? I am trying to maximize storage space without conflicts.
Thanks so much for your time,
vjgrace
Click to expand...
Click to collapse
HI,
default.hv and user.hv are a pain in the arse to find, you need to change the folder options so you can "show hidden files and folders" AND uncheck "hide protected operating system files" (see screenshot)
then the next thing i do is order everything by type, then scroll down to "HV File" and you will find them both
with regards to your second question, this is about dumping and cooking a ROM.
a ROM is originally compiled from an operating system, to change features inside the OS you need to dump the ROM differently as this kitchen (at the moment) is only for adding and removing APPs and tweaks.
To do what you want you need to get the "SYS" "OEM" and "XIP" folders from your ROM, swap them into a different kitchen (one that allows you to run something called "BuildOS.exe" )
I will be releasing one here, but the first thing to do before you start messing with the OS of your phone, is to get used to doing the methods in this kitchen.
It is my Birthday today, so i cannot put together a "BuildOS" package and instructions today but I will, soon!!
hope this helps
First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!
GriFolle said:
First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!
Click to expand...
Click to collapse
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5
tnyynt said:
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5
Click to expand...
Click to collapse
Thanks a lot!
So, to replace OEM, just put out (from a rom) and put in (in mine)...so simple?!
Ahahah...
Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!
GriFolle said:
Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!
Click to expand...
Click to collapse
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.
tnyynt said:
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.
Click to expand...
Click to collapse
confused...
I think I have to create just the packages of apps I would to add...not even all the apps contained in the stock rom!
Looking and reading tutorials in this forum I understood that If I would (i.e.) add/rmv apps to my rom I've just to put its files in base rom and then (after extract all) add/remove what I want. Then rebuild.
But for all others teorically I don't do anything...Is this wrong?
PS: thank you for the previous reply
[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online)
I've seen a few requests for kitchen's & rom's based on 21042 XIP/SYS so I decided to knock one up using the 2.03MRII 2.03.401.3 base and XIP/SYS from 21042 build.
This kitchen & rom is currently completely stock. Nothing removed from the OEM & SYS folders, no tweaks no addon programs just standard diamond build with newer core.
The only extra included which isn't in the original stock rom is remote desktop mobile (came with the sys not an extra) which of course you can remove from the kitchen if you wish. As it's the new sys it obviously contains the newer builds of MS apps including Windows live. Also this does not have the newer version of IE, just standard version.
Keyboard currently supports English, French, German, Greek, Italian & Spanish t9 however this should be updatable with the 14 language patch available elsewhere.
The kitchen is bepe platformrebuilder in almost stock form. No extra tools except for it runs htc rom tool to build the nbh file at the end.
XIP is not changed in anyway except updated msxipkernel & msxipkernelltk from 21042. No pagepool patching, cert patching or time/date/name changes. os.nb.payload size is reduced in the kitchen however this has no bearing on the final rom.
As this uses bepe's platformrebuilder, if you wish to change the date, build, pagepool, cert patching in the kitchen directly, these need to be done on nk.exe in the oemxipkernel. Any changes made to os.nb.payload (except uldr) will not be carried forward to the final rom as the nk.exe will overwrite changes to the payload. The payload itself is not ported so if you extract this and replace the msxipkernel folders then you will be back to a 20764 xip. There is no need to port the payload as replacing the msxipkernel & ltk folder in the xip folder properly ports the xip anyway if you are using bepe's kitchen (surface kitchen does not work properly in this way)
Also any rom's built with this tool are automatically locked as the kitchen deletes rgu's & dsm's from the cooked rom for space saving and performance. The files are extractable but then all you get is a dump of the files, without being able to seperate to packages.
Hope this helps some of you out there.
Also on the link there will be a stock diamond rom built from this kitchen - entirely stock but with latest xip/sys - even .netcf is still v2.0 that's how stock it is. It does however have more storage memory as it is cooked - original has 82Mb total and 57 available - this has 102Mb in total and 75+Mb free. Using the kitchen you could make a rom with alot more free space however.
I would recommend atleast upgrading .netcf to 3.5 in this rom if you are lightly cooking. Package for this is available on the forum
If you release a rom using this kitchen, please do not forget to credit the source.
Shaks.P Roms are free and always will be. If you like my Roms optionally send me a drink here:
Download Links:
http://diamond.geg0r.de/index.php?dir=Shaks%2FStock%2F
Please donate to bl0w for providing this mirror.
Important: Hard spl is required to use either the rom on this link or any rom created with this kitchen.
Basic Tutorial
As the rom is already ported & extracted, all you need to do is make your modifications then build the rom.
Step 1. Modify the sys & oem folders with the packages that you need. Make a backup of any folders you delete in case they cause issues with anything else.
Step 2. Once you are happy with the modifications, run build_rom.bat. This will create the os_new.nb file in the root of the kitchen folder. Once this is done, it will load the htc rom tool that builds & signs the final nbh file.
Step 3. Once the htc rom tool loads, select Build!, Change the version to anyversion you would like (this version only shows up when flashing). Under system, click on ... and select the os_new.nb file that has just been created. Then click on Build! ROM and this will ask where to save the nbh file and the name. Save as diamimg.nbh if you want to flash thru internal storage or any other name you like if using customruu.
Step 4. Ensure your device has hardspl, then flash the rom you just built either using custom ruu or using the internal storage method. If it doesn't work, you can allways flash another rom after getting the device in bootloader mode.
Can't wait
Thanks!
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
alxalx said:
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
Click to expand...
Click to collapse
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Thanks shaks!
Not only do you provide the best ROM around, but now also a kitchen, you rock!
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
shaks1979 said:
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Click to expand...
Click to collapse
Thanks man! I appreciate it!
Dynomite232 said:
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
Click to expand...
Click to collapse
This is just something I felt like doing for today. The kitchen won't get updated much (probably not at all as it's not modified). The roms will continue but will be going for the long release cycles again just like 3.20. I envisage I will probably have one more release and if that doesn't have issues then no more flashing till something big happens again (maybe stable tachi rom comes)
This kitchen is so stock that it can't replace my rom without alot of work - no tweaks, extra packages or anything for that matter except what comes in the stock as that's what some people wanted and I thought it won't take long so I did it.
P.S sorry for the delay with the upload. Having some issues
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Dynomite232 said:
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Click to expand...
Click to collapse
Well 3.20 was a damn good, stable, time tested rom. I know a few people who won't change from it at all. Tested the latest but went back to it because they preferred it. 4.x series are a little bit more experimental but still go for the same stability. Next release should take of that small percentage who have corrupt memory/hard reset issues hopefully but I don't expect a big changelog as 4.10 is otherwise fine.
Should the bluetooth work well with this rom?
Thanks!
alxalx said:
Should the bluetooth work well with this rom?
Thanks!
Click to expand...
Click to collapse
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
shaks1979 said:
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
Click to expand...
Click to collapse
Thanks man, downloading now!
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Dynomite232 said:
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Click to expand...
Click to collapse
That's right - delete what you don't want, modify rgu's for packages, add your own packages e.g. using ervius package creator to turn a cab into a package or use a package already provided. You'll get lets of cooking help from here (talks about surface kitchen but basic concept the same):
http://forum.xda-developers.com/showthread.php?t=413782
Add your own packages into the OEM folder.
Downloading... In the meantime thank you!
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Dynomite232 said:
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Click to expand...
Click to collapse
Add this package to your oem folder for 14 languages & edit the line in the rgu to specify languages you want
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