Hi, Folks
I tried to use diamond's kitchen to extract Opal rom but when the process up to using "ImgfsFromNb.exe" an error msg come up and said it has to be closed.
But at the same time, i can extract Jade rom with no problem
So, wht is a proper way to extract Opal rom?
try kaiser kitchen
Thx for the reply, but it didn't solve the problem
Even i use kaiser kitchen, same error with ImgfsFromNb is occur, actually the diamond kitchen that i use b4 is also based on a kaiser kitchen
Any other idea?
don't use kaiser kitchen.
directly use the imgfsfromnb.exe command on the os.nb.
O...it works, thank you so much
Related
Hi!
If I cook my own ROM using the core pro kitchen for Artemis, what is the necessary steps I have to do to repack the rom into i nbh file and be able to flash it with the RUU utilities? I guess this is be possible now that we have the USPL, thanks to Pof and all the other geniuses in this forum.
Regards,
PK
All existing tools for making NBH work fine with hermes / trinity, but not with artemis as signature positions differ. To create artemis NBH you have to use this method, until a better tool to automate this is done.
1) Use nbhgen.exe to create NBH (edit sample.txt)
2) nbh2dbh.pl RUU_signed.nbh file_unsigned.dbh
3) imaghash.exe -raw file_unsigned.dbh file_signed.nbh 1024
I'm making a tool for this at the moment, it is almost finished, but I can't test the generated .nbh's because T-mobile still has my Artemis in repair!!!
today Mr.Dark simpson release HTC rom tool Repack *.nb ---> Nbh
work in HTC Artemis and ....
Link here :
http://forum.xda-developers.com/showthread.php?t=311909
Cheers..!
tom_codon said:
today Mr.Dark simpson release HTC rom tool Repack *.nb ---> Nbh
work in HTC Artemis and ....
Link here :
http://forum.xda-developers.com/showthread.php?t=311909
Cheers..!
Click to expand...
Click to collapse
Tom,
I tried Dark Simpson's utility with your OS.nb but failed. Could you please tell how to do? Thanks.
Khuanchai said:
Tom,
I tried Dark Simpson's utility with your OS.nb but failed. Could you please tell how to do? Thanks.
Click to expand...
Click to collapse
Khuanchai my friend..!
Copy it in Disk C
And try agian.
This worked verry good.
tom_codon said:
Khuanchai my friend..!
Copy it in Disk C
And try agian.
This worked verry good.
Click to expand...
Click to collapse
Thanks, Tom. The new version 1.01 now works beautifully.
pof said:
All existing tools for making NBH work fine with hermes / trinity, but not with artemis as signature positions differ. To create artemis NBH you have to use this method, until a better tool to automate this is done.
1) Use nbhgen.exe to create NBH (edit sample.txt)
2) nbh2dbh.pl RUU_signed.nbh file_unsigned.dbh
3) imaghash.exe -raw file_unsigned.dbh file_signed.nbh 1024
Click to expand...
Click to collapse
Where can I get imaghash.exe please?
Hi!
Thanks a lot for these great advice. I relay start thinking of cooking my own ROM, it seems like all the tool is quite mature now, both the core pro kitchen and the Mr. Dark Simpson's authoring tool.
One thing I could need some more advice about though, is how to make an OEM package, or where do download already created packages.
Regards,
PK
paalkr said:
Hi!
Thanks a lot for these great advice. I relay start thinking of cooking my own ROM, it seems like all the tool is quite mature now, both the core pro kitchen and the Mr. Dark Simpson's authoring tool.
One thing I could need some more advice about though, is how to make an OEM package, or where do download already created packages.
Regards,
PK
Click to expand...
Click to collapse
If you want do some OEM package...!
May be OEM Storage 1.75.
Extract All File in Storage 1.75 cab
Copy to Folder Storage 1.75
All reg in Storage 1.75 cab copy to Notepad and see link :
http://www.famkruithof.net/uuid/uuidgen
That it ID.Maybe : 6b44e778-1c4d-11dc-8314-0800200c9a66
Save all reg Storage 1.75 name 6b44e778-1c4d-11dc-8314-0800200c9a66.rgu ( Save to Unicode Format)
And Create file empty 6b44e778-1c4d-11dc-8314-0800200c9a66.dsm in Folder Storage 1.75
Now you have OEM Storage 1.75
Cheers..!
Quick question
Is there a way to replicate 1 xda orbit onto another? The reason I am asking this is because I have killed my xda orbit to the point where it hangs on the "O2 Welcome Screen". It does however boot up into bootloader mode and I can connect to it using mtty.exe. My mate has an xda orbit which was bought at the same time as mine... is there anyway to mirror that device onto mine so that it starts working again?
This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders. It currently supports the following:
Herald
Wizard
Prophet
Kaiser
Elf/Elfin
Hermes
Zinc
Athena
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
(You will need 7-Zip to open the file.)
This is compatible with Bepe's extended kitchen, but I don't believe he ever released one for every device out there. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. The ONLY tested section has been the Herald section as that's the only device that I have.
If your device is compatible with Bepe's kitchen or my kitchen, it will automatically launch the kitchen right after.
Instructions:
Delete your old SYS folder
Place the SYS file you wish to port into Working_Folder
Place your xip.bin that you wish to port into the Prepare folder
*Note: Close the XIPPort program after pressing "Make Packages." The script will take over after that.
You should not have a Working_Folder with an OEM, SYS and XIP folder (and a Tools folder if you have Bepe's kitchen, even more if you have my kitchen.)
Double click on the RunMe file and choose your device.
For those who have a kitchen:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data but will bypass a few "info" scripts. This will not cause any problems.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Changelog
V2.2
Added Athena Compatibility
V2.1
Added Prophet Compatibility
Added Elfin/Elf Compatibility
Added Hermes Compatibility
Added Kaiser Compatibility
Added Zinc Compatibility
Added Atom Compatibility
V2
Added Wizard Compatibility
Rewrote script to add expandability
V1.5
XIP porting complete
V1
SYS porting complete
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Welcome to EasyBakeOven!
Devices supported:
Herald/Atlas
Wizard
Note: Make sure that the XIP in your recieving folder has been extracted already (You should have a ROM folder with a XIP folder inside it.) This is not an issue if you're using Bepe's Extended 6.1 kitchen or my own JustClean EasyBakeOven.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Click to expand...
Click to collapse
l3v5y said:
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Click to expand...
Click to collapse
Noted. Thank you!
Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Click to expand...
Click to collapse
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
l3v5y said:
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
Click to expand...
Click to collapse
Just for being nice to me, here you go!
That's the newest official build. Be careful of anything "newer," they're fakes.
It's the one labeled 19213.7z
You'll need 7Zip to open the file. In it as the xip.bin and the SYS folders.
Yay!!!
Porting time!
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
l3v5y said:
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
Click to expand...
Click to collapse
Already ahead of you. Today I noticed that I tend to leave a mess behind. lol I'll have it remove the files before replacing them, then I'll have it delete the extra files created during the process when it's done. (This part is already ready but I just haven't uploaded it. The removing the files before replacing them, I haven't done so, yet. Although this might not really be needed. Only the cleaning after part.)
...Maybe I don't know what you're talking about. lol
Explain it to me.
AssassinsLament said:
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Click to expand...
Click to collapse
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
xvx45 said:
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Click to expand...
Click to collapse
That would be more than welcomed especially since I'm gonna use my Herald cooking class and modify it to teach Artemis users, also.
ai6908 said:
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
Click to expand...
Click to collapse
My hope is that it will allow just about anyone to port a ROM. ^_^
ivanmmj said:
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
Click to expand...
Click to collapse
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
AssassinsLament said:
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
Click to expand...
Click to collapse
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
ivanmmj said:
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
Click to expand...
Click to collapse
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
AssassinsLament said:
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
Click to expand...
Click to collapse
It might be.... I'll have to do some research...
Ok, I even installed the vs2008 runtimes, same thing.. I found buildxip v.54, same thing... then i moved the whole ROM folder (new XIP) out and put in the old 19209 one and it ran... so maybe there's something wrong with 19213 with hermes? ok, I give up. Thanks for your help!!
19213 porting to elfin
i'm trying to port the 19213 to my elfin, and after porting when i use bepe's kitchen, it gets stuck at this screenshot. anybody help!!!
Hi,
I have a weird crash only on WM 6.1 only and I would need NK.exe from a WM 6.1 device.
So if you are good at manipulating ROM, decompress it, ...
Could you please send me the file.
Actually I was able to uncompress a ROM for kaiser with NBHextract and ImgfsTools but I don't know how to uncompress XIP file to get NK.exe.
So if you could help me or send me the file ...
Thanks
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?
hi everyone
i try to use osKitchen but i had one prob. i can not understand MK folder how to create define.text ? pleas help coz i want to cook rom
i did MK forder but kernel not select
see sum screenshot from attachmens
Don't use oskitchen cooking roms for Opal.
There are some issues that haven't fixed yet.
If you cooking a nbh successfully,there is a flash write error at the end of the flashing.
define.txt.txt-->define.txt
My phone is: OPAL, but the use of OSKITCHEN decomposition, packing the official ROM is normal, but after the computer prompt Brush "226" error code, the phone automatically restart, direct access to three color screen and an error ~! Is this software does not support this type of phone models OPAL?, I use software version is 1.25, my phone model is: OPAL (HTC VIVA), still issue I found our handset, XIP using a OS.NB, not OS.NB.PAYLOAD . there any way let OSKITCHEN use OS.NB to customize ROM?