Hi guys....
I've been a member of this comunity for 2 years now, but posted very litle, because I would be mostly spamming, re-interating what others have said, with" wow, this is fast...nice job"...and such..so i only post when I realy have to.
I downloaded the hypercore kitchen, and after some reading of the contained links and txt files, decided to have a go at it...
I would like to target Tomal's v8 but although very fast, it seems to have a significant number of com bugs...So maybe I'll go with v7.7...
I copied the nk.nbf file to the correct directory, and ran the decoder, but it errors on the next step saying that there is no OS.nb file...
Should this file be extrated from the nk.nbf?
Is this a problem with the nk.nbf file I'm using?
I would apreciate some help on this, as I'm looking for a full flavored cake, but to my taste...see I'm "diabetic" so I have to be extremly caution with what I cook...
When you decoding nk.nbf, decode it to OS.nb (change second line) instead nk.nba.
Something else to be aware of with Tomal's ROMs is that he ships all his RGUs in a single RGU.cab file.
You'll need to extract the contents of this file into the dump directory AFTER the imgfstodump and BEFORE the pkgtool step.
-PJC
Thanks for the quick answers, guys...
Something pop-up as a doubt...can I cook from an usb stick?(installing the kitchen, and workind directly trought the usb stick)???
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
psapg said:
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
Click to expand...
Click to collapse
With HTC Extender Rom Tool you must extract nk.nbf not ext_rom, and when extracting name it OS.nb (i thing it is 2nd line in tool)
Perhaps the would-be chef should read a cookery book?
There's a very, very good guide in this forum, which is what I started off with and had no problems whatsoever, but I can't for the life of me remember if it was beasty or thingonaspring who wrote it (apologies to the real author if I missed them out!). It also includes some fixes for the batch files.
Remember - the wiki and search are your best friends...
PJC
Hi Again...
The construction workers finaly had done some real work, so now my kitchen is properly furnished with all the CABinets i need...so now to try to cook me a simple meal, and try to learn from it....
Can't rebuild Ranju 7.7
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
jandevries12 said:
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
Click to expand...
Click to collapse
imgfstonb doesn't seem to support the FLASH disk that's in Tomal's ROMs. I don't know what he uses, but when I've based things on his work, I use a different 'donor' OS.nb for the imgfstonb stage. Obviously, I lose the FLASH disk, but as I don't use it anyway, that's not an issue for me.
^^ yup, exactly, it is due flash disk.
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
jandevries12 said:
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
Click to expand...
Click to collapse
As I understand it (and I'm sure someone can correct me if I'm wrong), the donor OS.nb is used as a 'template' for storing the IMGFS into an NB structure. As far as I've been able to tell, pretty much *any* OS.nb from *any* ROM can be used as the template.
Basically, imgfstonb takes 3 arguments - the imgfs file itself, a 'donor' OS.nb, and the 'target' OS.nb final output. This is all hidden by the scripting, but is what I've found by playing with the underlying utilities.
The only restriction I've found is that ROMs that contain Flash disk can't be used as the donor OS.nb.
PJC
Could one of the senior members of this forum please comment on pjc007's statements above?
Is it correct that the donor os.nb is only used to determine the right structure for the ROM?
(I'm asking because I got the impression from other posts on this excellent site that the donor os.nb is used as source for the XIP part, but I don't know for sure)
Well, I have the same matter now, I really want to cook sth to use the way I want a rom to be and share with others as I feel really bad just to download, I hope to upload my own rom and share but I read the instructions again and again , look for sth on the internet, download all the things to my PC that will be used to cook, still not certain what I'm going to do.
My question is if I cook a bad rom, then I up it to my EXEC, Is there any chances for it to die ? Or simply just install another well-known rom to rescue it if my rom jail to boot?
Related
You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
It does not need to be told how to do it, but told how to search ! A lot of people here know how to do it, just GOOGLE it !
sorry, I've already searched... Maybe I'm searching badly!
Could you please help me?
Basically you need to extract the ROM installer, you will find an nbf file in it, then get an NBF file converter, to convert it into some sort of editable format, then you start cooking the ROM, placing whatever you want, and in the end, convert it back into NBF
Hello,
You might find something useful here:
http://www.modaco.com/index.php?showtopic=255064
It would be more helpful if people genuinely try to help others instead of directing them to Google.
A
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
duke_stix said:
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
Click to expand...
Click to collapse
if all were like you ...
I know it isn't but in so much amount of infos it's not easy to find ones that apply to your device or even thing you wanna do!
Need help too
Yea, Please..my probs are the reconverting my data into a .nb->nbf file...after flashing My phone hangs in First Bootscreen...please help!Only Reflashing helps...i really want to cook a rom by myself.
Ive used THIS kitchen...but it is for Wizard-devices only....but i think,it can be used for Tornado,too.
as far as we tried we could not make a proper dump of the wm5 tornado...
but i did manage to build a rom kitchen with wm6 for the tornado...this was a whileago and the base rom is the same as the current available...if ther is enougth request i may be inclined to update the RK and release it.
to get you started here is some pointers.... you can use the same tools from the wizard, imgfs tools.
When I use nb2nbf_wizard.exe, is this created nk.nbf flashable for my Tornado (german XDA Phone aka HTC Douton)?
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Have you removed the first two bytes of the initflashes.dat? When not, it can't be booting correctly! That was my mistake when I started to cook my own ROM's for my HTC Prophet (XDA Neo)!
What?
really?I may think,it is only needed after a Registryedit....thank you.!
edit:did not work...
arpy said:
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Click to expand...
Click to collapse
i have the same problem like you.
I've made a nk.nbf from the *.nb files with nb2nbf_tornado.exe.
I've also extracted *.nb (OS, IPL, SPL, etc) from nk.nbf from windows mobile 6 alpha and then 'translated' those nb files with nb2nbf_tornado.exe. Same result: succesfull flash, stuck in first screen every time..
so not the "initflashes.dat" file is guilty..
...and nobody out there may help us?
arpy, it seems that if I include only OS without IPL & SPL in nb2nbf, all are OK..
But still with my modified OS does not get over the first splash screen.. maybe i've done smth wrong. In dump folder, I've added some files (some overwritten), i've removed some files, modified initflashfiles.dat (last line blank, + removed the two first bytes with winex), modified the hv files (saved in unicode standard, first line REGEDIT4, last line blank.. complied: no errors). replaced carrier_splash and shutdown
that's all what I've modified ...
edit:
arpy, try to translate only the OS module with nb2nbf_tornado. and tell me the result. also, tell me what changes you've made
edit2: found this: http://forum.xda-developers.com/showthread.php?t=298327 . improved tools
edit3: i've dumped my modified OS module with tadzio's ImgfsTools and discovered that initflashfiles.dat had the two bytes that i've removed with win hex.. what the?!
i've removed again, and run the whole build rom process again , but this time with tadzio's ImgfsTools.
Same result.. (stuck in first screen)
Maybe i've modified something wrong.
edit4: i've repeated the whole process and OS module flash and work ok . I haven't tried yet with all modules, only OS. I think I've made some mistakes when trying to replace drivers.
@DSF
Can you post a Step-By-Step Solution?I want to figure out my prob...which tools do you use?And how?May you Post your ROM?
well, i will post summary. i hope to release a "tornado romcook kitchen" and more detailed steps these days.
here is my OS module:
http://rapidshare.com/files/45915194/RUU.rar.html
right now i'm trying to figure out how to make the sd driver from iphone/other roms to work on my custom rom. every time i try other sd driver, i cannot view the card.
i'm using the tadzio's ImgfsTools (see link in my previous post).
steps:
- download typho5.exe, ImgfsTools, nb2nbf_tornado (you can get them by searching via gogole)
- copy all those files in the same folder, eg: ROMDEV
- copy nk.nbf in ROMDEV
Commands:
1) typho5.exe -x nk.nbf
2) imgfsfromnb.exe 82040000-OS.nb imgfs_raw_data.bin
3) imgfstodump.exe imgfs_raw_data.bin
Now the OS files are dumped in dump folder. Do the changes (delete, copy, modify, etc). When editing registry and initflashfiles.dat file, perform the important steps describeb at http://www.molski.biz/romcooking.html (turn off word wrap and use UNICODE in notepad, etc). If you're dune with those things do next:
4) imgfsfromdump imgfs_raw_data.bin imgfs_new.bin
5) imgfstonb imgfs_new.bin 82040000-OS.nb 82040000-OS_final.nb
if no error occured in the whole process, run 6) nb2nb_tornado.
There, chose the nb files, OS will be 82040000-OS_final.nb and not 82040000-OS.nb. Don't forget to use the correct image name. (eg: for 82040000-OS_final.nb chose OS)
The language, oem, operator version, cid can be left blank.
When you're done, press translate.
Copy the generated nk.nbf file in the rom update folder (RUU), execute ROMUpdateUtility.exe and follow the normal flash steps..
That's all.
Thanks to all those ppl that made this possible
PS: if you flash only the OS module (without IPL & SPL), even if the update proces crashes, you will not 'brick' your phone . Mine happen to crash on 2%.. i transpired instantly
kartam said:
You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
Click to expand...
Click to collapse
Actually, I have some files about how to cook a rom, but they all Chinese, and may be useless for you.
DSF: the way you describe works with the tornado. thx. ive testest
an usefull app to edit initflashfiles.dat and the registry files is "notepad2".
I have been using many kitchens over the past year. Cooking horrible roms, decent ones and now a pretty good one. My problem was always the various tools lying all over my hard drive. Luckily I came across this litte gem by Ervius
Package Tools and BuildOS rolled into one. I also noticed that it handles rgu files much better than the previous BuildOS, it choked on an incorrect rgu file. Which in turn allowed me to get Video working in HTC Album 2
I have modified the batch files for our Wizards and have been cooking and im loving it
PackageTools+BuildOS (Latest combined version)
rgu-2-xml : Convert .rgu to provxml files
SYSVersion : Generates a version list of your SYS Folder
All the usual build tools :G'Reloc, M'Reloc, ImgFS Tools
AllPackagesToOne - Protect your rom from being ripped apart and the whole world being able to share in your utter cooking brilliance, via a tickbox ofcourse
Automatic Find and Fix duplicate file errors during BuildOS process
More features which I am either too lazy to list or dont use at all
Just add SYS,ROM and OEM folders. It also have a nice feature which allows you to select OEM Packages and save it as a preconfigured rom. Extra OEM packages can be placed in a Packages folder. BuildOS will load those files also (No more OEM's all over your hard drive).
BuildOS also runs G'Reloc during the dump process, but for good measure I also included it in the batch file.
Also added -conservative to the Imgfs Tools portion of the script to protect against overcook
BuildOS generates pretty log files which shows where stuff went wrong
Extract the zip file. Run Kitchen.exe and watch the magic at work.
Note
For some reason the output window text is black on a black background, but at the top is a nice running status. If not sure just hilight the output window.
If you start up and It complains about folders just create them
Download
Ported 20931 SYS/XIP without PIE 6 download
Microsoft Visual C++ 2008 Redistributable Package (x86) is need to be installed in your PC
[URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en]Get it here[/URL]
Hi,
Nice kitchen.
But its little bit difficult compare to hypecore.
Thanks for great kitchen.
Nice release ..i think im gonna start cooking too
Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?
Noonski said:
Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?
Click to expand...
Click to collapse
It does, in the prettiest little tick box you have ever seen, just below the Output Window. One of the really cool features of this version of BuildOS is the ability to scan for and fix duplicate files
sounds really impressive! downloading...
I'll recook my rom with it and let you know how it went
where should I extract this kitchen?
Error: pkgdll is missing
Never mind. copied it to the same folder as the kitchen.exe
I cant cook... .net problems
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.
+ Que PPC said:
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.
Click to expand...
Click to collapse
What OS are you running on your pc ? .net 2.0 and higher really like XP Sp2. Do a google search for CCleaner and "Uninstall Utility" this might help before you format dude.
Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.
S.V.I said:
Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.
Click to expand...
Click to collapse
I really wish I could decompile and just fix the black on black issue. Coz it is a simple case of just changing the font. Unfortunatly it is not written in .net like the previous BuildOS, so no luck there
This should be your default layout:
Base Folder-
->Compile Tools (OS.nd encoding tools)
->Flash (Created by Batch file, your new OS.nd ends up here)
->OEM (I like to put the BASE OEM Folders in here OEMAPPS etc)
->Packages (This is where I drop my custom OEM folders)
->ROM (OS.nb XIP,romhdr.bin lives here)
->SYS (Yeah well we know this one)
The error you are getting is when you try and extract a rom with Package Tools in the kitchen. Here is the procedure:
Create a base folder, I normally use Base_Buildnumber_Device
Select your Dump Type in the bottom check boxes, either a folder where you have already dumped a rom or an *.nb,*.nbf type file
Start your kitchen and select Open on the Package Tools tab.
Browse to the folder you have just created select the folder of rom file based on the above selection
Package tools will now extract the rom and create OEM and SYS Folders if possible
In case of cooking which I believe you are after:
Create the above folder structure with all files in place
Select BuildOS tab
Click Load Rom
Edit OEM's etc and just press Go
thank god u placed this tut, i thought i was the only one with theis prob oO
I'm almost having to pour cold water over my self
Click to expand...
Click to collapse
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S
ather90 said:
thank god u placed this tut, i thought i was the only one with theis prob oO
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S
Click to expand...
Click to collapse
Dude I battled to get the whole thing running as the tut's where for Kaiser and the tools were abandoned by the looks of it. But once i started using the cool right click and import package features I was sold.
Sorry. double post.
->ROM (OS.nb XIP,romhdr.bin lives here)
That may be what I am missing. how do I extract that?
I Have OS.nb; XIP.bin XIPfolder
@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread
->ROM (OS.nb XIP,romhdr.bin lives here)
Click to expand...
Click to collapse
should the XIP be in the bin extension or in a folder the one which Hyper Core Generates) ?
ather90 said:
@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread
Click to expand...
Click to collapse
OMFG dude I think you are right. Dev by day ... cook by night ... hey wtf is my gf ?!?!?
how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??
fachry said:
how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??
Click to expand...
Click to collapse
Yeah I realised now that when I zipped up the Kitchen I left pkgcommon.dll in the Tools folder, this should be copied to the same folder as Kitchen.exe.
Your error however comes from me not stating the .net Framework 2.0 or highers is required. I take these for granted since I have Visual Studio installed on my machine anyway
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
ciko84xp said:
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
Click to expand...
Click to collapse
I can't help you either ... try to PM one of the Chef you knew from the forum.
ciko84xp said:
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Click to expand...
Click to collapse
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
parleyp said:
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
Click to expand...
Click to collapse
I downloaded this "RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship", which should be the Official HTC ROM for TYTN II (my device), but I have the same errors described in the first post using the BEPE's kitchen!
What do you mean by "You will have to get a base from a chef?
I do not believe that any chef would give me his base, should give me the entire folder containing the kitchen built! Or not?
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
I am having the same issue with Bepes kitchen - I have the official signed rom from Sprint for the Mogul and every time I try to use dump_800.bat on the OS.nb file, it fails and says access is denied...
ciko84xp said:
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
Click to expand...
Click to collapse
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
DaveShaw said:
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
Click to expand...
Click to collapse
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
ciko84xp said:
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
Click to expand...
Click to collapse
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
DaveShaw said:
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
Click to expand...
Click to collapse
ok Dave.. I follow your advice! then you story if I have made progress ...! thanks!
I apologise up front if this has been answered elsewhere, but I have searched high and low without any luck...
A number of ROMs are so-called "chef friendly" ROMs, i.e. they can supposedly be extracted with the .dsm and .rgu files intact, packages neatly in folders, etc.
I would like to customise one of these for myself, but I'm not having any luck.
I am using Alex's kitchen to extract the ROM, and I've tried these methods:
1. ruu_signed.nbh in the BaseROM folder, option 'a' on the Extraction menu.
2. Cooked ruu_signed.nbh in the BaseROM folder, and dumped part01.raw and part02.raw from the cooked ROM, using option 'b' on the Extraction menu.
3. Shipped ruu_signed.nbh in the BaseROM folder, and dumped part01.raw and part02.raw from the cooked ROM, using option 'b' on the Extraction menu.
I manage to get OEM, ROM and SYS folders which look fine. Initially I am just trying to recook these using the kitchen, with no changes. I am including the splash from the cooked ROM as well, but my NBH is about 3MB smaller than the cooked NBH I extracted from. There are no errors in the build process, flash works 100%, but the phone refuses to boot fully, it just gets stuck at the splash screen with the RGD numbers.
I have read the dumping and reconstructing threads, but obviously I am missing something important, I just cannot see what it is.
Can anyone point me in the right direction?
Please identify the ROM you are trying to extract so we can help.
I am trying this using gullum's TF2D II.
I can't find it now, but I definitely saw gullum state in a previous thread that all his ROMs are chef friendly, so I just chose that ROM because of that. Ultimately though, I'm not particularly fussed which ROM I use for this, it's just for my own use.
I know for sure that mine works because I do that a lot since the initflashfiles.dat changes after cooking the ROM, and I could try out gullum's for you. If you want I can put the folders in a RAR file and upload them for you . Oh and whenever I was cooking and my phone didn't boot the culprit was a registry error with opera, just in case you want to know.
kaiserII101 said:
... I could try out gullum's for you. If you want I can put the folders in a RAR file and upload them for you
Click to expand...
Click to collapse
That would be awesome. Or you could just let me know what additional steps I am missing. I don't mind getting my hands dirty, I'm just a bit stumped, being relatively new to all this.
no what you are doing sounds right. I'm not sure what the problem is. I will just re-cook the ROM to make sure it works and then put up the folders. I'm about to go on vacation though so expect it mabye by Mon. or I may do it on vacation since I have an unlimited data plan for my phone and I am bringing my laptop
Not to worry, for some reason it's working now. I have already ripped out a few bits that I don't want and added a few that I do want, and so far my phone has been stable for about 4 hours.
Thanks for the offer anyway.
you do NOT need to rebuild the Part01 and Part02 raw files. All you need to do is set the .nbh as your base
I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?
Anyone willing to spare some time to help please?
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?
OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.
I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.
If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)
I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.