I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
HEdwards2008 said:
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
Click to expand...
Click to collapse
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
yardie.spike said:
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
Click to expand...
Click to collapse
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
HEdwards2008 said:
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
Click to expand...
Click to collapse
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder.
Click to expand...
Click to collapse
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
mbarvian said:
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
Click to expand...
Click to collapse
Theres a new ROM tool????Anyone tried??
NEW IS GOOD!!!
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build. I have to agree that a new version of the HTC Rom Tool would be cool.
HEdwards2008 said:
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build.
Click to expand...
Click to collapse
I just put up a Kaiser 20270 kitchen from PPCKitchen.org and AstainHellbring. Try it, let me know what you think. Feedback thread is here.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
Click to expand...
Click to collapse
So if I'm understanding this correctly....in order to achieve a completely clean ROM without all the extra fixings I would simply need to use the os.nb file and not the os-new.nb file when cooking correct?
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
I do know that in order to get the base OEM packages out of the main build you have to go through and remove and edit certain files to get it done right, which there is information in the Wiki about but haven't really had time to focus on it much. As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
No dont put os.nb in the base rom put the RUU_unsigned and extract using KAISERKITCHEN.cmd.....read my previous posts.
gguruusa said:
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
Click to expand...
Click to collapse
This looks very promising, downloading it now. Thanks for this! Hope they update it 20273 soon
HEdwards2008 said:
As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
Click to expand...
Click to collapse
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
gguruusa said:
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
Click to expand...
Click to collapse
I shouldn't have any problems then seeing as to how I know that you need to have HardSPL installed and also to be sure to flash the radio AFTER the ROM in order to prevent bricking.
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
Click to expand...
Click to collapse
I totally agree my favourite build was one that went wrong and nearly bricked my phone....sounds sick, but it was going back over what i had done and fixing that was the fun part. That ROM turned out to be possibly my most stable (Yardie 2.1.240) Ha ha i love cooking!!!
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
Click to expand...
Click to collapse
Bah. The fun of cooking is getting a ROM to look and feel like you want. Making a kitchen is entertaining when you haven't done it before, but it's really 99% repetition and 1% art.
Related
Okay after reading through a few threads on XDA I thought I might take a stab at writing a Simple tutorial of the knowledge I know of cooking a rom
Step 1: Download a kitchen of your choice I think the Kitchens from Matt are the best to use only my recommendion
Step 2: Download the OEM packages you'll need..Leave them in a different folder then the Kitchen right now..
Step 3: Make a OEM folder in the kitchen folder if theres not one already and place it in the kitchen folder
Step 4: Take the OEM packages from the desktop and drag the ones needed for your rom
Step 5: Click Build OS check the files your going to have in your ROM to be built..if it errors look at where it errored and check the OEM package to see if it meets the standered below
Step 6: Now add any thing you need to edit in the dump or replace files (EX: Welcome Screen, themes, initflashfiles.dat file ect)
Step 7: Now run the CreateROM.bat once finished you'll have a new file in the temp folder
Step 8: In the kitchen there will be a nb2nbf_wizard.exe if not search the forums..open that model ID will say Wizard.. change the language to WWE then on the bottom you'll see empty fields..those are self explanatory pick OS for the ROM then locate the file in the TEMP folder of the Kitchen
Step 9: Now once its finished translating where ever the output direction was it will be your file to flash, now move that to the RUU and flash and say Hello to your own Cooked rom
PS Steps will varies from Kitchen to kitchen but this covers the jist of basic ones
nows for the complex parts how to make an OEM package...Information from double_ofour
Step 1: Vist http://www.famkruithof.net/uuid/uuidgen the Create UUIDs of another type should be set to Version 4: random then a code like this "6bfb7458-6a83-450a-9da5-b5feabba8335" will be made
Step 2: make the code the name of the 2 text files you have in the OEM package folder, Change one Text file extension to RGU and the other DSM
Step 3: now the RGU is where the Reg hacks are the first line MUST be REGEDIT4 then you list your Reg hacks.. in the formate like this
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"TaskManager"="1_5_29968_1"
Step 4: Leave a space after the last reg hack and save as UNICODE
Step 5: add any files to the OEM package Folder they will be put in the /Windows directory
to make an extension into the programs folder you should edit the initflashfiles.dat
How to edit the initflashfiles- Should be done between useing the Build OS and Create Rom
Step 1: open the file with note pad
Step 2: remove any lines that aren't needed..sometimes you'll see likes to create a folder for a shortcut when your not using the program
Step 3: add a line to create a shortcut for a program from your own OEM package...Most packages here already do it for you
sigh I'm tired of typing but theres a basic out line of what cooking a rom consists of..feel free to add anything I might of missed
Just thought I'd help out anyone looking to cook a rom and needs a little guide
Please don't ask for help here..I'm not text support..I think there shoul dbe one thread for all cooking questions..you guys could even use the thread when i asked for help
PS again thanks to all the people here at XDA that made cooking simple easy even ifs making a OEM pack or a fix or even a kitchen thank you all
thanks ANTC!!!
thanks dude! can we have pictures too? (what the heck - had to ask )
thanks this is EXACTLY what I was looking for
mattk_r said:
thanks dude! can we have pictures too? (what the heck - had to ask )
Click to expand...
Click to collapse
sigh..sure once i can release my full touch rom using your kitchen
so no deal matt...lol not like you need a tut how to make a rom...maybe you could help with the cam issue to for my rom
everytime I click buildos.exe I get an error. No matter what folder I try it in, it just wont work.
How do I dump an official rom?
maybe some one can help you with the dump question its hard for me to put into words since core does it by it self
and th build os problem is something to take up with the maker of ur kitchen try doing a windows update you may need sp2 or net framework
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
dferreira said:
How do I dump an official rom?
Click to expand...
Click to collapse
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
It won't dump using your kitchen... Try the last oficial RUU Prodigy of WM5 and you'll see that it seems to be protected, since it can't extract the 8004000 :s
anichillus said:
I suggest making this thread sticky, removing all unnecessary posts, including this one and transform it into an How To thread. Where everybody can post tutorials on different aspects of rom cooking.
Same you do with an unofficial one lol The difference is that you won't find any missing files and that means less work for you.
Click to expand...
Click to collapse
Coming from you thats a huge compliment..
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
nycelitemaster said:
what can i do if i want to add programs like TNT, i have few apps compared to mfrazz's build or TNT and now if i add 1 more program in my kitchen it crashes the buildimgfs.exe, anything i can do to add more? i am using faria's kitchen tool
Click to expand...
Click to collapse
Try using Core kitchen that should do the trick
hopefully as a newbie I can make my own rom with this
and please do help me if i encounter any problems
thanks in advance
Personally, I would suggest doing a topic like this in the Wiki. Then have a topic here that is stickied to point to the Wiki entry.
Here's a page I started for the Faria Kitchen last May. http://wiki.xda-developers.com/index.php?pagename=FPRK_Cooking_Instructions
You could take what ANTC posted and merge with the info I provided and come up with a nice generic page for cooking )most of the kitchens work the same since they all use basically the same set of tools).
Here's a page on making OEM packages that da_jojo added on:
http://wiki.xda-developers.com/index.php?pagename=FPRK_Creating_ROM_Packages
BTW: If you do the instructions in the Wiki then any / all of us can help maintain it (where posts here can only be maintained by the original poster).
i think this is good for those who already know how to cook, but too brief for beginners who know little about cooking a rom.
My problem when building the rom is when it is finished this error comes up
"c:\DocumentsandSetting\M541378\ApplicationData\hIqInc\PPC-BuildOS\9.05.3.0Temp\ROM\XIP"
so in my ROM folder there is no XIP, I create the folder, and I re-create, it and then the XIP folder erases. I have no idea why this happens? Can anyone please help....
Updating rom image USING FARSTONE DRIVE CLONE
Hi all i'm new at the forum, i would like to know if i can create an image with farstone drive clone of all the programs i have and configurations and then upload it to the phone?? I would like that even if i have to perform a hard-reset on the device it would still have all the progs and configurations created on the image uploaded.
Any suggestions are welcomed!!!!!
hi, I am a newbbiess... i am totally not understand what do u mean by kitchen... but i am intrested in generate a ROM myself.. please advice..
I have a rom (*.nbf) that someone made there are more likes than dislikes, but I wanted to take his rom rip it back down prior to the rom so that I can remove and add my own stuff. Can you point me in the right direction. I seem to find stuff about ripping a rom but they referance a *.nbh file. all I got is the *.nbf.
also when I break the file back down does it keep all the tweeks just the way they were prior or do I have to re add them?
- Albert
I recommend HyperCore to do this. Its a kitchen up in the stickies at the top of the rom. It has a nice setup for pulling a rom apart (basically drop the nbf into the extract area and then use the panel to do the extract), and then moving it into the kitchen and then building it back into a custom rom by manipulating the OEM packages, etc.
Good luck
I have that aready but it asks for a nbh file and i have a nbf. Do you know where there may be a better cookbook?
almulder said:
I have that aready but it asks for a nbh file and i have a nbf. Do you know where there may be a better cookbook?
Click to expand...
Click to collapse
i thought that it asks for an nbf, but i think you can just rename it.... im sure someone will correct me because that doesn't sound right
anyways i always use the core pro kitchen
http://forum.xda-developers.com/showthread.php?t=313859&highlight=core+pro
very user friendly, i've had issues with hypercore...
Ok I need a few opinions.
I am wanting to find out who has the easy and the best Kitchen.
I want to take a "nk.nbf" and edit it.
I want to remove packages that are in there and add others.
I have "TNT.1933_Professional___HTC_Home_Wizard" Rom I have tryed to use "HyperCore Kitchen" but could not get the rom to work.
I took the original ron, extracted it and then re made it (With out changing anything) to see if I was doing it the correct way, but after I loaded the rom it locks up after it posts the ver screen.
Is this the rom I am using or the way I am using it. Or is it the kitchen.
I really want to learn to make my own. So if some one has time to walk me though it I would be ever so greatfull.
I have searched and search the site and most walkthroughs apply to old vers of kitchens. I still tryed to follow them but cant get a rom to work. I know I must be missing something somewhere.
- Albert
I don't think you have the .rgu's
If the chef deletes the .rgu files you can't rebuild his rom the easy way. You should either seek a rom that has all the files or ask the maker to share them.
Ok thank you
Yep, a lot of the roms have the .rgu files removed. You can use my cooking pack or I recall that there was a Lite version of TNT that was meant for cooking that would still ahve the .rgu files (but then you'll have to get the packages to put in it what you want). Then of course there is theloon's kitchen stuff which has tons of packages and all.
As promised, here are Just2Clean's kitchen files. You will need to use either JustClean's EasyBakeOven or Bepe's kitchen in order to use them. Just download either of the kitchens, delete the OEM and SYS folders and replace them with these.
This does NOT include my micro Extended ROM, but if you've flashed my ROM, you already have it installed.
Linky It's the Working_Folder
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Thanks. I will try to cast some magic with this
(for personal use, of course )
macaraballojr said:
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Click to expand...
Click to collapse
This is not my newest build, this is the Just2Clean that I had already released. If you want to get a newer build, search for EasyPortOven 2.2 and use that to port over the ROM. It will change the ROM, though, as the SYS folder has been optimized. You'll learn more about this in one of my upcoming cooking lessons.
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
macaraballojr said:
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
Click to expand...
Click to collapse
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
ivanmmj said:
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
Click to expand...
Click to collapse
What would we do without u bro but many thanks for the info
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
slimag said:
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
Click to expand...
Click to collapse
One of the packages you chose is probably not compatible with Just2Clean. To make it compatible, read the error and it will tell you. If a duplicate file is found, delete the extra file from the OEM folder or the SYS folder.
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Ghostrider said:
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
Click to expand...
Click to collapse
What do you mean by not start up. There are MANY files and batch files and programs that work together as a kitchen. You'll have to be more specific. Perhaps a screenshot of what happens.
slimag said:
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Click to expand...
Click to collapse
You can't choose packages because the packages are all stored in the OEM folder. I forgot to mention that. Don't delete the OEM folder, just the folders in the OEM folder have the same name as the files in the other new OEM folder...
when I put the new files in the OEM and SYS Folder it say's BuildOS.exe don't work anymore, The Program has an Problem, and must be Closed.
Then the same with Buildxip.exe don't work anymore.
Ghostrider
That means that there's a conflicting name on an RGU, DSM, or inside an option.xml. If you do not go through BuildOS, Buildxip will crash because it will not have something to build in the first place, as it's BuildOS's job to get the files where they need to be.
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
slimag said:
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
Click to expand...
Click to collapse
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
ivanmmj said:
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
Click to expand...
Click to collapse
I don't felt me insulted
I'm testing this now.
Ghostrider
Edit:
I have Just2Clean and MMS 3.5.1.24.R2 as UPX and non UPX deleting the UPX version did't do it. I deleted both the UPX and non UPX version in the Kitchen files for Just2Clean, and now it is working.
I don't have the Just2Clean Customization
Ghostrider
Great to hear!
There should be a Just2Clean customization there also. It's labeled "Customization - Just2Clean."
I think what he meant is that Just2Clean customization packages don't work.
I did as you suggested by deleting the .rgu and .dsm starting with Z, but that still didn't work.
The option XML file needed to be edited because it pointed to those Z files not the A files.
Not sure if just deleting the .dsm and .rgu starting with A would've worked because I didn't try that.
After deleting the UPXed packages everything works for me now.
Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks
go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.
Yep, looks like you didn't set it to Herald when you built it.
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?
Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.
After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks
Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.
I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help
Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.
The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.
The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.
working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.