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".
Hi all!
Downloading custom ROMs is VERY cool, but a bit of a pain sometimes because the downloads are huge. I have a suggestion about how this could be resolved.
To explain my idea, let's look at how you would flash a ROM using the new method being suggested. You'd need the following things...
- USPL (as usual)
- Custom RUU (as usual)
- 'Control' ROM NBH
Here's the first difference. The control ROM in my proposal is the widely circulated HTC ROM NBH, which can be found here. You'd keep the NBH from this ROM (RUU_Signed.nbh) named as HTC.nbh, and it would be used by all subsequent updates.
So let's imagine that I have a device (USPL'd of course) that I want to flash to the T-Mobile ROM. I'd make sure I had a directory with the Custom RUU and Control ROM NBH in, then i'd download the file from the ROM creator. In this file would be a batch file, a ROM patch and the patcher. The batch file would patch HTC.nbh to T-Mobile spec, then run Custom RUU. The beauty of it? The download would be very small!
Would it work? YES! And to prove a point, please check out this post - where you'll find Orange, T-Mobile and Tilt ROMs in tiny downloads based off the control NBH. ROM chefs - let's start using this system, which i'm calling 'Kaiser TLR ROMs' for obvious reasons.
ROM chefs, to create the patches you just need to use bsdiff, which can be found here. Use the syntax 'bsdiff HTC.nbh YourROM.nbh YourRom.patch'. You can see a sample batch file in my link above.
So... what do u think?
TLR
I don't get it once your HTC is HardSPL'ed then there is no CID lock and you can flash any rom to your device. Most rar files containing the RUU_signed.nbh are only 40-50MB thats pretty small and can be deleted when your finished flashing. To me this seems like a lot of extra work for the cook(sometimes me) and more support issues I find it easy just to upload the ROM i made to rapidshare or some other file hosting site and people can download as they like.
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
theloanranger said:
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
Click to expand...
Click to collapse
Sounds interesting about the legal hosting capability for diff ROM files instead entire ROM. The ROM archive goes down in the past for the M$ pressing . If we can archive only diif ROMs, this can be one solution to take back the ROM archive into the FTP at XDA.
One offtopic question, where did you get the Orange Shipped ROM for Kaiser?
Cheers.
I didn't, it's a dump and repack, as is the T-Mo one.
TLR
I have been toying with the idea recently of brewing a ROM that is entirely my own, something that fits my needs perfectly. However, I am having trouble figuring how to go about doing so.
1. Basically, what I want to do is to start with a stock AT&T ROM, strip everything out of it, then only add back in what I use. It would seem simple enough, however what gets me is that when I extract the AT&T ROM, most of the applications seem to be contained within the OEMAPPS folder, with no simple way to sort through it. Sure I could just delete the folder and re add what I want, but thats not exactly what I had in mind. I would really like to pull out all the apps from that folder into their own individual folders so that I can keep anything if I feel like it while not having to keep everything. Does anyone know how to do this, or if there is any way other than doing it manually?
2. If I want to have registry tweaks installed on the ROM, what is the best way to go about doing so?
3. I have been searching and searching, but I cannot seem to figure out where the image that appears after the device splash screen is stored. Can someone point me in the right direction? I know Alex has his own custom image. EDIT: I am referring to the Welcome Screen.
4. When I previously cooked ROMs using the kitchen, it seems to retain the version number of the ROM that I based mine off of. Does anyone know the reason for this?
Yeah, a lot of questions I know, but once I get my ROM finished, I'll be sure to release it here.
Best thing I can recommend to you is try Alex's ROM Cooking tutorial. His ROM is AT&T ROM stripped. All apps are in OEM format so you can re-add as needed. The process of stripping the OEM apps is complicated and you need to find all files associated with a certain program.
Alex already did this so why do it again? You get a fully stripped ROM.
For the registry tweaks take a look at the OEM Packages included with Alex's ROM Cooking tutorial. There are several registry tweaks he has included so you can take a look at it and create you own from that.
The splash/welcome screen is called welcomehead.96.png. It's in the \Windows folder. You can cook your own by replacing the file in "SYS\Redist_dpi_96_resh_240_resv_320" folder if you use Alex's ROM tutorial. It's probably the same for other ROMS if you extracted your own but I haven't tried this. I replaced it so each time I create a ROM it's already there.
As for the ROM version you can change it (I think). In the OEM folder there's an OEMVERSION that contains a .provxml file. You can edit that and you'll see a version number.
Hope that helps.
Right, I know Alex has already released a completly stripped down version, but I really just want to cook something entirely of my own. Not that I dislike Alex's package, but I really would just like to do the work entirely by myself so that I can know all of the changes that were made, and how they were done. It gives me the kind of flexibility that I would like. Also, Alex has made some of his own changes to his UltraClean, so I don't have the level of control that I want.
I read the guides in this website, but need some extra guidance of how to achieve the following (if it is possible):
Let's say that one of the chefs cooked a ROM that I really like (let's call it "ROM X"), but there is one change that I would like to do to the ROM, for example, let's say I would like to delete the OEM package for the dialer that he used, and use an OEM package for a different dialer.
I understand that I need to do the following:
1. First I need to flash "ROM X" to my kaiser.
2. Now I need to dump "ROM X" from my kaiser, to my hard drive. At the end I get the 4 raw files.
Now comes the stage I'm not sure how to accomplish: I want to load the cooking applet of the kitchen software, and have all the database from the 4 raw files (of "ROM X") appear, so I can make the needed change in the OEM package, and continue to create the ROM. I understand that I need to somehow extract the information from the raw files, to something that the cooking applet of the kitchen software could use, but I'm not sure how...
Can anyone provide a bit of guidance ?
Thank you very much.
Btw, I've seen the following thread which deals with how to reconstruct a dumped ROM, but it doesn't deal with how to make changes to the ROM during the reconstruction process, rather the ROM you create, is simply a 100% duplicate of the ROM you dumped, and this is not what I'm trying to achieve...
http://forum.xda-developers.com/showthread.php?t=337066
Does anyone know what type of a file a .nbh is and how to make it veiwable/modifiable. If there was a way that we can mod the NBH file that I believe would be the successful way of rooting the MyTouch 3G. I will be getting one of the production devices in a week or so anyone want to have anything dumped let me know.
the nbh is a ROM and you can't flash it without a modified SPL. i'm not even sure the SPL used for android even supports the file type but any kitchen from winmo can decompile it
Not really so much an android thing but is a hardware thing of HTC. The Dream and Sappihre support these files. There is a NBH file which will take you all the way back to RC29 and also flashes back the original SPL as well. So it is my belief that if we can make a compatible NBH for the sapphire it will accomplish the end result.
Of course it will... That's what NBH files are made for. I don't think you can make one since it's signed (or something) with a key we don't have.
Ehh, i have an idea:
Some has to decompile .nbh and modify it to work on mytouch 3g.
Than you have to create a goldcard.. not sure about if viperbjk is putting sapphire into qmat..
Yeh I have tried to decode with hex editor and have not had any real luck with it at all. Looks coded. Just wondering if anyone knows how to decode would be greatly appreciated. I have tried to use some of the old Windows mobile kitchen tools.
There are lots of tools to extract NBH files, they should work if HTC hasn't changed anything...look for other devices kitchens and you'll find the tools.
Also there's a project which tries to achieve the same result under linux http://code.google.com/p/htc-flasher/.
where did you guys get an android nbh? this is odd because android is updated by placing and update.zip on the root of the sd card (among other ways) which is handled by the SPL. why wouldn't HTC just stick with nbh then?
sammypwns said:
where did you guys get an android nbh? this is odd because android is updated by placing and update.zip on the root of the sd card (among other ways) which is handled by the SPL. why wouldn't HTC just stick with nbh then?
Click to expand...
Click to collapse
android is updated by .zip but NBH is an all in one image type file that flashes htc phones to factory defaults. its usually used by the support techs to restore phones.
android/google=zip
htc =nbh
tripledes said:
There are lots of tools to extract NBH files, they should work if HTC hasn't changed anything...look for other devices kitchens and you'll find the tools.
Also there's a project which tries to achieve the same result under linux http://code.google.com/p/htc-flasher/.
Click to expand...
Click to collapse
this looks promising...i wonder if we can figure out how to resign it....
Hi,
I have just tested the HTC-Flasher and unfortunately it does not work with the DREAIMG.nbh
So i someone know how to extract and re-flash the dream NBH please help.
Bye
Herc. 8)