Related
Hi, I am beginner here, can any one help me to create a nbf file from sd dumped rom? or you can also tell me how to do that. thanks in advance!!!
SD dumped rom is here:
ftp://xda:[email protected]/Magician/Dumped_ROMs/o2mini_1.12.07_CHS.zip
What do you want to do with this .nbf. For backup/restore purposes the .nb1 is sufficient.
You can try it with nbfdec, but I don't know what it does with a dumped rom. I use it to decode & encode the nk.nbf contained in a shipped-rom. For nbfdec get it here: http://forum.xda-developers.com/download.php?id=7603
Cheers, M
oltp, thanks for your respose, i have tried nbfdec and finally I got a nk.bf from the SD dumpped rom. but it seems this nk.bf is different with the one contained in shipped rom. my purpose for doing that is to custom the extended rom with that SD dumped rom. but I don't konw how to separate all nbfs (ms_.nbf, nk.nbf, etc)from the dumpped rom.
Take a look @ the ftp & see if your current rom is available as a shipped-rom. If so start with the shipped-rom & try it with that.
Or use bal666's tool HTC64_Extended_ROM_Tool_v1.1.zip from http://forum.xda-developers.com/download.php?id=8015. He made one to convert the ext-rom part of a rom-dump to a fat-image, which you can mount & change.
Succes, M
unfortunately, there is no shipped-rom for o2mini_1.12.07_CHS.zip...so my problem is to separate ms_.nbf and nk.nbf from dumpped-rom.
how could i do that with HTC64_Extended_ROM_Tool_v1.1.zip?
does any one know how to break dumped-rom into two nbfs(nk.nbf, ms_.nbf)? or is there any other way to create two nbfs?
Hello,
The available original shipped ROMs for the HTC Hermes have .nbh files with the RUU, instead of the usual .nbf files found in other HTC rom updates:
By now, there are two shipped ROMs available, containing:
HERMIMG_Dopod_1.23.707.1_SHIP.nbh
hermimg_QtekNOR_1.18.255.3_Ship.nbh
So, it seems that the usual nk.nbf file is no longer used by the Hermes RUU
I cannot extract the various rom components (ExtROM, OS, IPL/SPL, SplashScreen, GSM radio, etc...) out of these files using the usual TyphoonNbfTool, however maimach's prepare_imgfs finds the imgfs and dumps it apparently ok, but it cannot be read using viewimgfs or itsme's rdmsflsh.pl, so I guess the dumped file is invalid.
Anybody knows about this new format?
is it possible to convert it to nk.nbf so we can cook our own roms?
Would it be possible for example to extract the radio rom from Dopod and replace it on QtekNOR rom?
-----
EDIT: I posted the same on TyTN Upgrading forum and there's some more info... ignore this post and continue the thread here:
http://forum.xda-developers.com/viewtopic.php?t=59522
pof said:
Hello,
The available original shipped ROMs for the HTC Hermes have .nbh files with the RUU, instead of the usual .nbf files found in other HTC rom updates:
By now, there are two shipped ROMs available, containing:
HERMIMG_Dopod_1.23.707.1_SHIP.nbh
hermimg_QtekNOR_1.18.255.3_Ship.nbh
So, it seems that the usual nk.nbf file is no longer used by the Hermes RUU
I cannot extract the various rom components (ExtROM, OS, IPL/SPL, SplashScreen, GSM radio, etc...) out of these files using the usual TyphoonNbfTool, however maimach's prepare_imgfs finds the imgfs and dumps it apparently ok, but it cannot be read using viewimgfs or itsme's rdmsflsh.pl, so I guess the dumped file is invalid.
Anybody knows about this new format?
is it possible to convert it to nk.nbf so we can cook our own roms?
Would it be possible for example to extract the radio rom from Dopod and replace it on QtekNOR rom?
-----
EDIT: I posted the same on TyTN Upgrading forum and there's some more info... ignore this post and continue the thread here:
http://forum.xda-developers.com/viewtopic.php?t=59522
Click to expand...
Click to collapse
Hi,
do you know a way to convert a .nbf file to .nbh? i want to flash the cortulla's ROM on my HTC magician using your flasher tool.
Given that crossbow is now floating around out there I was wondering if its possible to cook your own ROM for the Herald? I would happily start researching cooking ROMS etc. if it is. Or are we faced with a situation similar to that of the hermes where we need to find a bootloader that allows the flashing of unsigned code?
Hi,
i think the Problem is that Herald is not so popular as the Wizard and Prophet by now....
Let´s ait and see when someone is getting this nice one unlocked !
you are in the same situation as the Hermes.
AFAIK all devices using NBH for rom upgrades, need the upgrade file to be signed, otherwise bootloader won't flash it.
pof said:
you are in the same situation as the Hermes.
AFAIK all devices using NBH for rom upgrades, need the upgrade file to be signed, otherwise bootloader won't flash it.
Click to expand...
Click to collapse
thanks for the answer (not the one i was looking for though!), i noticed in your hermes thread that you managed to get your hands on the bootloader from a pre production hermes. has this helped? should i be looking for the equivelent for the herald?
It helped because it has the commands to flash unsigned code... i don't know if preproduction bootloaders in Herald will have the same "feature", but it may be handy if you can get one too
I can try looking but i wouldnt know where to start! any advice would be appreciated.
Bootloader of Herald is similar to that of prophet and wizard.The only differrence now is the nbh format.One needs to check if awizard work or not?Then we canthink of debranding.I am working on the Bootloader of herald.Will post everything in Wiki.Pls wait for some time
hdubli said:
Bootloader of Herald is similar to that of prophet and wizard.The only differrence now is the nbh format.One needs to check if awizard work or not?Then we canthink of debranding.I am working on the Bootloader of herald.Will post everything in Wiki.Pls wait for some time
Click to expand...
Click to collapse
ok thanks. If you need any assistance please ask me.
Here you go..
s4vva said:
ok thanks. If you need any assistance please ask me.
Click to expand...
Click to collapse
Thanks to aWizard v 1.3 beta2 and POF for making NBH extract..
I was able to flash my herald from 1.7 dopod asia to new HTC 1.8 without changing/touching IPL/SPL.Here is how to do :
1)Use POF's NBH extract and extract the ROM parts.
2) Copy the OS.nb to awizard ROM folder and rename it to.nba
3) From the Lib folder of awizard, transfer enable rapi and certsps cabs to yr device and install them.
4)Now run the batch file and select "e" to enable rapi.
5) Then you can directly choose the option "w".This will give you the option to choose the ROM u want.Select and wait till awizard finishes.
One can also back up the Extended ROM, Splash image, bootloader, Radio and OS ROM with awizard.
It is very interesting that the size of the .nb file extracted from NBH file and the size of the wizard ROM(80040000.nb) is exactly same.
I tried to put crossbow image into it..but I clouldn't boot the herald.The boot screen showed "OS 10.1.00.88
So if some one can extract the things from both the .nbs we can think of having crossbow in herald..and I think POF can do it.
I hope, this helps the members to upgrade and play with their toys.
You Rock
Finally !!!! Did it. followed the instructions and wallaa finally dutch rom Bye bye bye and Hello English Rom.
Thanx Guys you rock
Look'n forward to crossbow soon.
Very nice discovery hdubli!!
Unfortunately I don't have Wizard nor Herald, and I have not much experience in ROM cooking... you should ask the real gurus here if you want to port the Wizard's xbow to Herald.... I saw it was ported to Prophet, but I don't know about the internals of Herald and Wizard enough to say if this can be also done here or not.
Anyway, kudos for your finding!
P.S. You should add this info to the wiki!
well done hdubli, this is serious progress!
I have no experience of ROM cooking, however I have both a Wizard and a Herald, so if I can help in any way just let me know.
Can I update the page pool? I want more free ram I now have 24 mb, nut I really want al least 32mb
Can you help out how to extract my rom, is there any tuttorial? I tried XDA tools but it apears an error.
best regards
1. NBHextract
2. mamaich imgfs tools to extract OS.nb, if it does not work try tadzio's make/prepare imgf with "-hermes" switch.
thanks a lot
i'll try to get the portuguese rom for xda
best regards
pof said:
1. NBHextract
2. mamaich imgfs tools to extract OS.nb, if it does not work try tadzio's make/prepare imgf with "-hermes" switch.
Click to expand...
Click to collapse
looking for a bit of guidence here
i have the herald 1.8 ROM as .nba (taken from device using awizard)
and i have the wizard OS I want to use as .nb (extracted using typho5)
now my understanding here is i need to extract the herald drivers from the herald OS and replace the wizard drivers in the wizard OS, rebuild the OS.nba and write it to the herald using awizard. Am i heading along the right lines or am i way off? any help would be appreciated.
i really don;t know but if you have a rom with more ram I would like to have it lol
hdubli said:
Thanks to aWizard v 1.3 beta2 and POF for making NBH extract..
I was able to flash my herald from 1.7 dopod asia to new HTC 1.8 without changing/touching IPL/SPL.Here is how to do :
1)Use POF's NBH extract and extract the ROM parts.
2) Copy the OS.nb to awizard ROM folder and rename it to.nba
3) From the Lib folder of awizard, transfer enable rapi and certsps cabs to yr device and install them.
4)Now run the batch file and select "e" to enable rapi.
5) Then you can directly choose the option "w".This will give you the option to choose the ROM u want.Select and wait till awizard finishes.
One can also back up the Extended ROM, Splash image, bootloader, Radio and OS ROM with awizard.
It is very interesting that the size of the .nb file extracted from NBH file and the size of the wizard ROM(80040000.nb) is exactly same.
I tried to put crossbow image into it..but I clouldn't boot the herald.The boot screen showed "OS 10.1.00.88
I do the same thing as you did, tried to put crossbow image into it, and it boot up and freeze at the start screen, so now I have the problem, how to put the old OS back?
I have back up the OS ROM, but my machine can only boot into the tri-color screen, how did you do on your machine, please tell, it will hellp me out.
Thanks
Click to expand...
Click to collapse
Hi there,
I'm pretty experienced with rom cooking, but need a bit of direction from the pros here in a project I'm working on.
I have a working WM6 rom that I'm looking to make a kitchen for in order to more efficiently customize the rom.
I've decoded the rom to nba/fat format (my device uses nba/nbf format) and dumped the imgfs to a dump folder without any issues and can edit the rom that way, but I'm looking to make a kitchen.
I've used bepe's package tool to convert my dump into OEM & SYS folders without any problems. I now just need to be pointed in the right direction on how to rebuild these packages back into a working nba/fat file.
I've tried putting the OS & SYS directories in an existing kitchen like the bepe/helmi/scoter kitchens and using the imgfs tools there building the packages back into a rom. The rom builds successfully but then won't boot past the initial splash screen after flashing it.
Is there something else I need to do? Is it possible Bepe's package tool isn't properly building the packages?
Any help is appreciated. Thanks for everything each of you does to help the community
anyone?
I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones. Export all the registry keys for the programs you have on your phone now and use them to tweak your packages. It really won't take you much longer than if you were able to use the one you dumped. Before you know it, the kitchen you put together will be so much better than the ROM you dumped that you'll forget all about it!
My kitchen is a work in progress, but right now it's SO close to the way I want it that I can do Hard Resets without a thought as the only thing that needs to be done afterwards is restore my contacts!
All my connection settings are there, all of the buttons are set the way I like, all the colors, graphics, themes...everything! I've even set up an extrended rom with custom cabs I put together with all my commerical software with the Registration keys built-in.
I can't recommend a kitchen since I haven't used them all, but I started with Octaivio's with a 1437 build rom, now I've replaced that base rom with the 1908 build one from his latest kitchen and it's worked fine. The reason I used Octaivio is because he used Pbar as a taskmanager instead of that awful useless HTC x button (remnants of it still pop up when switching from portrait to landscape and vice versa).
joemanb said:
I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
Click to expand...
Click to collapse
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones.
Click to expand...
Click to collapse
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.
So its not the RGUs..
Please, if you figure this out, post the solution. When I ran into this, I searched all over the forum for a solution and found at least 2 or 3 other posts with this problem, but never a response.
Good Luck
have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen
austinsnyc said:
have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen
Click to expand...
Click to collapse
No, at this point I'm not trying to change the initflash so I haven't modified it. I know that when the time comes to change it I'll need to do the hex edit thing for the first 2 bytes, the unicode and the last line empty,. etc.
Also I'm not even getting to the 2nd splash. I'm not getting off the initial splash screen.
I'm thinking at this point the imgfs isn't getting put back together properly.
There have got to be some old pros who can tell me what I'm doing wrong.
I think I found part of the problem. In step 5, CreateOS.exe is doing something wrong with the hives. After running it, default.hv which is 770K+ in sys/metadata goes down to like 42K.
Anyone know why this is happening?
source said:
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
Click to expand...
Click to collapse
At this point I think that you have the XIP extracted already, in order to create valid boot.rgu
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.
Click to expand...
Click to collapse
It's a suggestion, but i think you're missing the .rgu files.
Of course, those are not needed when flashing, but when BuildOS creates the default.hv and user.hv...these 2 being invalid, the OS can't boot.
Probably Bepe can clear you better on that one.
Cheers !
source said:
And, by the way, you were given misinformation about the rgu's.
Click to expand...
Click to collapse
Apparently not, after reading Anichillus' response (which agreed with mine) I converted the HVs to RGUs and it WORKS finally!
It's probably not a good idea to reject info out of hand like that..You almost had me convinced. Thankfully I always try to verify information before I accept it, or tell someone they're wrong, mistaken, or misinformed.
Thanks Anichillus!
Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar
Failure with build ROM
Hi Blackdragon_860,
many thanks for your effort - but unfortunately I must say that I have yet to find a
working dumptool for bepe's kitchen that fits the average user.
Using your toolset (put in the root of my drive) seems to create the structure just
fine but whenever I use build_rom.bat (from your kitchen or from bepes) it just gives
me an errormessage from platformrebuilder.exe:
Collecting standard packages and initializing hives...
ERROR! (errorlevel: -1073740777)
please press any key ...
I tried with the new HTC 1.93 GER ROM btw.
Any thoughts on that ?
/mst
P.S. why does yor tool need another location than platformrebuilder that makes it
even more difficult?
Thx for this, great work! one issue: I have made my Diamond roms with Surface Kitchen so far. I give this a go and I take one of my own roms and dump it and rebuilt it..I made no changes every thing went fine no errors and the new OS.nbh was created. Then I flash it but it dont boot, just the splash screen came up? the txt which allways come up normally where you seen the radio and protocol version didnt shown at all..How come?? What did I miss??
OK now I test a stock .nbh file and now the rom boot, but my finnish xt9 was gone I got just the ordinary keyboard in the rom, and the phone canvas is missing too in the rom, random acsess is gone
I used the 2.03 nbh
i use it for every "OFFICIAL" & "ORIGINAL" Rom
and it works greate..
i am working on a update,but for now it works.
greets
released V2
works awesome! THX
Great job! Perfect THX very much
thx for yours feedbacks..
I met an error like this:
Error: 0x80000009
'boot.rgu' does not exist in th specified paths!
Error! (errorlevel:1)
does this means the rom protected?
yes, when the rom is not protect or original it works 100%
Blackdragon_860 said:
Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar
Click to expand...
Click to collapse
dude i tried to extract wm6.5 rom with this. it did not extract ROM folder so i had to manually copy it. after that when i run the rom builder i get an error that boot.rgu is not placed in right paths. i think its supposed to be in XIP and it is there only. then why this problem?