Related
For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol
I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks
Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.
no, there is nothing what tell me what to do. so what should i do with that error.
i will make stick this thread.Hope next times will see some roms with this kitchen
Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.
kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.
I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?
ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.
Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.
all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio
ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp
i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file
Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?
@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
thank you.
thaihugo said:
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi
Thank you very much.
Ram
Thank you for your hard work and dedication we put it. Best regards
thaihugo said:
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
davidgreen said:
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
Click to expand...
Click to collapse
Make sure you keep your langugage specific folders intact.
Thanks
Ram
G'Reloc Situation
thaihugo said:
Hi,
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi thaihugo
My G'Reloc posts the same numbers always before and after, and strangely they are same for kaiser and SnapVUE. Am I doing anything wrong there?
Slot 0: 01F90000
Slot 1: 03DD0000
Size of ROM: 83400000
Unknown: 00000000
These are the numbers I have seen in ImageInfo.txt under .VM folder in SYS
Thanks
Ram
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
thaihugo said:
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
Click to expand...
Click to collapse
oh. Thank you
Ram
Help needed...
After all...i decided to cook my own rom...
Read alot , did everything i have read...
"cab oem" ing
"initflashfiles.dat" modification
but when it came to the end , buildos gives an error such as
The target file "temp\dump\mstscax.dll is a directory not a file"
Mind do wake me up for what i am missing ?
Safak
Help #2 for the noob
I have found out the problem about the previous tab... It was about wrong configuration of Remote Desktop...
I have overcome it but came a new one which is
Buildos gives this error
"Error building default.hv and user.hv"
and now , what ?
Help this poor lamer :-(
eh...
I ignored the latest error and have my own rom...and i m now flashing it to my Shift...
Will let yo know whn done...to be honest i m a little nervous about the result...
Urgent Help
I m in deep trouble...
I messed everything and now i m dead...Winmo side does not even boot...tell me what to do...tell me if there is a way to go back ?!?
how about flashing working rom to it?
omg
Recovered....thanks alot for your patience...
Average Joe
Hi guys,
I recently bought a HTC shift which SnapVue came out to be in Chinese, i really need to change the language and liberate it ASAP. I 've read so many replies on many different threads that i'm just completely confused right now. I barely understand all the technical words used out here. I need help please. Thank you.
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
gullum said:
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
Click to expand...
Click to collapse
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
thaihugo said:
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
Click to expand...
Click to collapse
ok first problem now ... I made my first atempt to flash a rom and now snap vue only gives a black screen what to do now?
edit maybe it should be added to first post that to recover from bad cooked flash then just flast the included rom
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
gullum said:
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
Click to expand...
Click to collapse
Hi
Can't wait. Could you check whether you are able to attach to audio to notes etc.
Thanks
Ram
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?
Who can help me create a oem package？
Microsoft Chinese Input Method Editor
download：
http://www.megaupload.com/?d=VZS7FWKG
thanks a lot
sorry
i did it by myself
dunkleosteus said:
sorry
i did it by myself
Click to expand...
Click to collapse
mmh...
so I am late ??
Nice to see you solvedd it, but since we are all learning here, may I suggest you to share your solution, and not only the problem!!
Anyway I use ervius package creator 2.5
TIP: check for identic filenames between your newly created package and the other SYS/OEM packages
If any file name inside your new CAB->package is exact to other file name in the OEM or SYS folder then you will not be able to build your OS file, at least not with bepe's "BuildOS" tool (I assume you use jerpelea's kitchen)
If you have a name conflict, rename the repeated-name file from your new CAB->package to something else and create a provxml file to rename it to it's original name at final customization (add a line to OEM/OperatorPkg/config.txt: "XML= /windows/yourprovxmlwhatever")
Hope this helps
gtrab said:
mmh...
so I am late ??
Nice to see you solvedd it, but since we are all learning here, may I suggest you to share your solution, and not only the problem!!
Anyway I use ervius package creator 2.5
TIP: check for identic filenames between your newly created package and the other SYS/OEM packages
If any file name inside your new CAB->package is exact to other file name in the OEM or SYS folder then you will not be able to build your OS file, at least not with bepe's "BuildOS" tool (I assume you use jerpelea's kitchen)
If you have a name conflict, rename the repeated-name file from your new CAB->package to something else and create a provxml file to rename it to it's original name at final customization (add a line to OEM/OperatorPkg/config.txt: "XML= /windows/yourprovxmlwhatever")
Hope this helps
Click to expand...
Click to collapse
i use package-creator-v2.7
i did get MSPY oem,just little wrong with rgu,but i dont know,so i think wrong with my oem.
Hi all... (sorry for my english)
I'm a noooooooooooooooooooob chef and i have some questions for you...
I cooked my first Rhodium ROM , but i have this problem:
When i tap on some program, i have an error message!!!
This error message tells me that you can not start the application because you can not find some components of the program, or you do not have a valid certificate...
PS: I think this is the same problem for which does not start the Sense 2.5!!!
I use "Rhodium Native WM6.5" (OEMXipKernel + os.nb.payload + romhdr.bin) with "buid 21864" (xip.bin + MSXIPKernel + SYS), and i have replaced in SYS folder NetCF2.0 with NetCF3.5 (i have moduled a cab file)...
I have tryed to use Leo EXT and Rhodium EXT, but i have the same problem!!! And i have the same problem also with NetCF2.0...
Where i wrong?
possible that no one can answer?
but I'm on XDA or not?
That error means that you are missing some dependencies. Use PE Explorer or Dependency Walker againt all exe and dll's in the package that you are having the errors on. You'll get a list of dll dependencies. Find out what packages have those dlls and include them in your rom.
Good luck.
either this or try opening the exe's from you're windows folder, this will tell you if you're shortcuts are bad.
if I understand correctly I have to check all .exe .dll and .dsm files? right?
dependencies defined in this files? and with the previous tools I can decipher the dipendencies?
Now I procure the tools ... thanks for the help ...
Well .. it seems that things are clearer now thanks to you ..
I used "Dependency Walker", and I looked the exe file of the EXT that does not work on my ROM... I realized that there are some missing .dll files that should be in the EXT folder called "files", but there does exist...
If I dumop the Shipped ROM where I took the EXT, I find them?
joshkoss said:
either this or try opening the exe's from you're windows folder, this will tell you if you're shortcuts are bad.
Click to expand...
Click to collapse
sorry but i don't have understand this method...
Can you explain the procedure in other words?
I'M REALLY SORRY FOR MY ENGLISH...
ciko84xp said:
sorry but i don't have understand this method...
Can you explain the procedure in other words?
I'M REALLY SORRY FOR MY ENGLISH...
Click to expand...
Click to collapse
it's ok man!! head over to my kitchen thread: here. Download my kitchen and read the tutorial's on the first page...
Good work my friend.. your kitchen and your tutorial's are really useful for a noob chef like me...
Now I have one question... if I use "Depenadancy Walker" for open the .dll files inside the EXT package that I want to cook with my ROM, I understand that I need some .dll files to put in "files" folder of the EXT in question... at this point, I search the missing .dll files in "dump" folder and I find them in OEM folder...
the problem is this: if I follow the way to arrive at folder where are the .dll that I need, I can't find it... it's impossible to see the file.. I see only 4/5 white files called "S000", "S001", "S002", "S003", etc etc... but I don't find the .dll file that i need...
WHY????????????
ciko84xp said:
Good work my friend.. your kitchen and your tutorial's are really useful for a noob chef like me...
Now I have one question... if I use "Depenadancy Walker" for open the .dll files inside the EXT package that I want to cook with my ROM, I understand that I need some .dll files to put in "files" folder of the EXT in question... at this point, I search the missing .dll files in "dump" folder and I find them in OEM folder...
the problem is this: if I follow the way to arrive at folder where are the .dll that I need, I can't find it... it's impossible to see the file.. I see only 4/5 white files called "S000", "S001", "S002", "S003", etc etc... but I don't find the .dll file that i need...
WHY????????????
Click to expand...
Click to collapse
First off... usually you need the entire EXT package that contains those dlls.
Second, the dlls that are directoried are actually modules. Leave them as is and include that EXT package in your ROM. You only need to recmod modules and convert to files "if" that package is giving you problems with platformrebuilder.
Third, Any package that you include from a dump, you need to look inside the initflashfiles.dat and see if there are any entries for the package you are including. You can either add those to your initflashfiles.dat or as I do, copy them and create the app.dat file for your EXT package.
Is there a guide to help noob cooks? I want to try getting into it, rather than just testing everyone else's, but I have no clue where to start.
ianderson_76 said:
Is there a guide to help noob cooks? I want to try getting into it, rather than just testing everyone else's, but I have no clue where to start.
Click to expand...
Click to collapse
There are a lot of thread. First thing you need to learn being a chef is know how to search. Use the link in my sign to search. Search for kitchen in this forum, and you will find tons of info. Read, keep reading, flash, keep flashing...thats the only way to cook a good ROM.
I think all the help given to the OP is what makes this forum...