What could have went wrong? 'getting error building boot.hv' - JASJAR, XDA Exec, MDA Pro ROM Development

I have just downloaded hypercore kitchen and tried to dump from one of the WM6.1 ROMs
Process followed..as attached
Except 3 missing manifests, no other missing files at Pkg Tool stage. Have not made any change to SYS or OEM or any other folder post and just followed to next stage tob build OS.
Then getting the error 'error building boot.hv' when clicked the 'small triangle of build os phase'
What went wrong? Any help from expert chefs?

Check errors in xip\boot.rgu

Thanks for the quick response.
How to check errors in there? It was just created when I dumped the ROM using earlier options of the kitchen? I have not changed anything after dump of XIP and trying to build OS as is.
What possible errors it can contain?

In last Tomal rom (8.2) last line in boot.rgu was a truncated header: no closing parenthesis.

Thank you
You are right. The last line in there is in complete. Corrected it and now able to build OS.

Related

Announcement: Wizard Rom-Packer Kitchen V2.0

Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar
Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!
More space for later use.
thanks. i'll give it a go later tonight
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy
I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..
the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works
I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.
i'll post the working one in a little bit.
edit... here's the one that works for me
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.
weird. intiflashfiles.dat copied over for me using 004's kitchen
I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.
Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.
Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,

how can I cook a ROM by myself?

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".

Uni ROM Kitchen v2.0 by Tomal: Next generation Kitchen for Universal

Guy's,
This is my 2nd attempt to build a useful kitchen for Uni lovers. It uses a new set of tools and technology and you can customize/cook the rom exactly the way you like it. Porting or building XIP was a real pain but the kitchen builds the XIP and IMGFS together and importantly without manual intervention.
I believe this is the easiest kitchen ever built for Uni and you'll simply enjoy it.
The OS has been included in the kitchen is a fresh new Core - CE OS 5.2.21014.
OK, let's go for working part -
Unrar the kitchen in any of the drive in your PC (but must be in root) and it should look like - D:\TML_UNI_KITCHEN.
You'll find a command script "build_rom.cmd" under the TML_UNI_KITCHEN directory. Now, make a coffee, then just hit on this script and reluxe. Your ROM will be cooked within couple of minutes. Well, a little dialog box will pop-up at the asking what to do, select Encode to encode the rom and then exit.
You can follow the encoding steps like:
>>Encode>>Browse>>open nk.prj>>Encode>OK>>OK>>Exit.
Now, got to RELEASE directory, open ROMUpgradeUt.exe and flash the ROM to your device.
Advance part -
You can modify few parameters under the build_rom.cmd to make your custom rom.
set BUILD_TYPE=Regular
This is the type of your ROM to be cooked. The value "Regular" has an association with the directory \TML_UNI_KITCHEN\EXT\Regular. Put all the packages here, those you want to include in Regular build.
set BUILD_TYPE=Vanila
The value "Vanila" has an association with the directory \TML_UNI_KITCHEN\EXT\Vanila. Put all the packages here, those you want to include only in Vanila build.
PLease note, packages under the Regular directory will not be included in Vanila build and vise versa. There is also a Common directory inside the \TML_UNI_KITCHEN\EXT. You can put the packages here, those you want to include in Regular and Vanila both the builds.
set BUILD_NO=21014
This is the build number of the rom. The value "21014" has an association with the directory \TML_UNI_KITCHEN\21014. Actually you can put any value you want but whatever value you put must be associated with the same directory. Importantly SYS and XIP must be located under this BUILD_NO directory, i.e. \TML_UNI_KITCHEN\21014\SYS, \TML_UNI_KITCHEN\21014\XIP.
ROM template located under the \TML_UNI_KITCHEN\ROM directory.
OEM drivers located under the \TML_UNI_KITCHEN\OEM directory.
ROM will be transfered to \TML_UNI_KITCHEN\RELEASE directory after the successful build.
Directory Structure:
\TML_UNI_KITCHEN\21014
\TML_UNI_KITCHEN\21014\SYS
\TML_UNI_KITCHEN\21014\XIP
\TML_UNI_KITCHEN\21014\romhdr.bin
\TML_UNI_KITCHEN\EXT
\TML_UNI_KITCHEN\EXT\Common
\TML_UNI_KITCHEN\EXT\Regular
\TML_UNI_KITCHEN\EXT\Vanila
\TML_UNI_KITCHEN\OEM
\TML_UNI_KITCHEN\RELEASE
\TML_UNI_KITCHEN\ROM
\TML_UNI_KITCHEN\ROM\nk.nba
\TML_UNI_KITCHEN\TOOLS
\TML_UNI_KITCHEN\build_rom.cmd
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Acknowledgment:
Major credit goes to Bepe as it was not possible to built this kitchen without his great tools.
Uni Kitchen v2.0 (beta):
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_2.0_Beta.rar
http://vidmes.com/xda/Uni/ROMs/Tomal/TML_UNI_Kitchen_OEM.rar
Cheers!!!
Gr8 news Tomal.
Thx 4 you hard work.
Good job!Thanks!
Hm, i tried to start kitchen, but unfortunately getting error:
Code:
PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Jan 4
Build: Regular
Locale: 0409
Preparing release structure...
... done!
Collecting standard packages and initializing hives...
XIP: 3 packages
IMG: 71 packages
Error: 0x8000000a
'initflashfiles.dat' does not exist in the specified paths!
ERROR! (errorlevel: 1)
Press any key to EXIT
I get the same initflashfiles error. It occurs in this command line:
.\tools\platformrebuilder.exe
in .\tools\buildOS.cmd
Same error here.. :/ If there is a fix it looks pretty good! Well done, Tomal
opppppsss...my mistake!
I forgot to include the OEM pack. Don't worry, I'll upload it asap.
Update:
OEM part has been uploaded (in 1st post). Extract it under \TML_UNI_KITCHEN directory.
regards
tomal said:
[...]
There is also some other secret thing which I forgot to mention and love to forget. [...]
Click to expand...
Click to collapse
LOL how nasty
gonna try and study it...
thx a lot for your work! hope my little donation was appreciated more than simple words
Wonderful!!!! Thank You
And with VInit help we can add flashdisk until he gets a way to make combined storage work for G4.
this could be the start of something new for uni lovers, many tnx tomal
Thanks a lot Tomal!
Hopefully on my vacations I can get into it!
Cheers,
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
simeonfilipov said:
Great work, Tomal I have just one question. I started build_rom.cmd and after some time a window pop-uped asking for HTC64 EXT rom... and there were 3 options : Encode, Decode and Exit. Afraid of doing something wrong I clicked Exit. Can you give some instructions how to continue the process and if there are any additional settings to make.
Thanks in advance .
Click to expand...
Click to collapse
Select Encode>>browse (to open the project file)>>open nk.prj>>Encode>OK>>OK>>Exit.
Cheers
Thank you! I just flashed with the Vanila ROM and it seems to be very good - it's fast, after soft reset there is ~28 mb free RAM. Again - thanks for your hard work .
it's possible to do a multilanguage/region kitchen? almost for common applications and configuration applets.
thx.
tomal said:
Please note the kitchen is still in beta so you may notice some unwanted thing which I haven't noticed earlier. Also, the XIP inject part has not been finished yet. But it's not a big deal and not necessary for the current build.
You can easily inject it using Bepe's Xiptool if you want. Just pick the xip.bin from "temp" directory after the build, rename it to xip_out.bin and write to nk.nba.
There is also some other secret thing which I forgot to mention and love to forget.
Click to expand...
Click to collapse
I tested it, and its working fine 100%, 1000 thanks Tomal for the great work!!!! I also used the optimize tool from HyperCore kitchen and the final nb.nbf is only 44M, but what about the XIP is it in my new rom or is it not and if not how do I inject it? I tried the implantxip tool from the TOOLS directory but I seam to not getting it how it works. Please help!!!
With the OEM directory in place, this kitchen produces great ROM's!
Thanks Tomal!
Thanks Tomal !
May i know how to use your kitchen to dump other ROM ?
Very appreciated your reply !!!
Thanks & Regards,
Upload This ROM
Can you guys help in uploading a ROM produced by this kitchen new Core - CE OS 5.2.21014
I would like to try it out.
Appricated ...
Vanilla nk.nbf
Here you are Fast and stable :]

HELP !!! First try to cook my ROM

I want to do a simple job: backup my actual kaiser rom, modify my rom adding/removing some application, then cook the new modified rom.
I was looking for a lot of time inside the forums for a guide/tutorial how to dump my actual KAISER rom , then modify it adding/removing some applications, then cook the new ROM to be flashed.
After a look around I was able to dump correctly part000.raw,part001.raw,part002.raw and part003.raw.
After I downloaded kaiserkitchen_01_20_08 and installed it.
Then I downloaded Alex 5.1 OEM packages and copied into c:\kaiserkitchen\packages.
Then I downloaded Alex 5 HT ROM 3.03 and copied into c:\kaiserkitchen\sys and c:\kaiserkitchen\sys
I moved .raw files in c:\kaiserkitchen\BaseROM
Then I started kaiserkitchen.cmd. I followed instructions to extract a dumped rom and cook it. The black window worked for some minutes and finished with message : Ignore any error while deleting files ! followed by 10 lines with message Impossible to find specified file...
All seems to be ok here. Yes ?
From here I can not go on, because when I launch BuldOS+PackageTools I can see only some applications that I imagine are from Alex oem, but I want to work only with my applications and I can not find them ! Where are applications installed in my actual ROM. How can I use them to rebuild my own ROM ?
Please, help me !!!!!!!!!!!!!!!!!!!!!

[Q] Build OS doesn't create RUU_Signed.NBH

Hi,
I'm trying to recreate my original ROM and have a problem with creating the nbh file with buildOS. Whole process seems doing fine, but at the end there is no RUU_Signed.NBH file in the main directory. Last thing which buildOS do is "creating registry" and then simply show "done". Pagepool Changer doesn't start and i don't get any error message. Any idea where can be problem?
I'm noob in cooking ROMs, so if someone can create nbh file for me, it would be great. Here are my raw files:
rapidshare.com/files/409577803/Part01.raw
rapidshare.com/files/409599604/Part02.raw
Is still here anyone who can help? Thank you very much, have to reclaim my Raph.
Can't you just download the stock rom? There are a lot of them available, if you search around or check the wiki. It's a lot easier than re-building.
Thank you for your response. There was some special Czech ROM by O2 and I can't find it anywhere. Maybe they will not care about type of ROM because It's hardware malfunction but I want to be sure.

Categories

Resources