When I open the 3.2.5 kitchen or any dcd kitchen in BuildOS from PPCKitchen I don’t get any options on what to build into the rom and not build, like if I wanted to uncheck certain things in the kitchen that I don’t not want, like I can with no2chem rom's.
Why is this?
That's because this is xda-developers and not ppcgeeks. DCD uses different kitchen software. After you unrar the kitchen, you'll see a file called BuildNB.bat. Run it.
To add OEMs, simply add your folders to the OEM directory and they'll appear in the kitchen.
Ivan
btonetbone said:
That's because this is xda-developers and not ppcgeeks. DCD uses different kitchen software. After you unrar the kitchen, you'll see a file called BuildNB.bat. Run it.
To add OEMs, simply add your folders to the OEM directory and they'll appear in the kitchen.
Ivan
Click to expand...
Click to collapse
And if i would wanna uncheck certain options. Like the upgrade to the camera cause i dont wanna lose the flash option
Dude, just extract the kitchen folder to your desktop from the rar...and run buildnb.bat
Everything else is pretty straightforward.
I wonder if the problem is that you're not actually running DCD's BuildOS??
Unpack the .rar, and run BuildNB.bat - you'll be able to make changes there.
Ok.....I'll try that. Thanks for the info guys
I see your running Radio ROM 3.37.71....You have good service with it?
Just wondering if anyone has told you to unrar the file then run BuildNB.dat yet?
lllboredlll said:
Just wondering if anyone has told you to unrar the file then run BuildNB.dat yet?
Click to expand...
Click to collapse
POST #4 and #5 ...Now to go home and flash to 3.2.5
Related
Does anyone have just the OS ROM portion of the new VZW MR1 update? If so could you link it or explain how you disassemble the NBH file? What tools did you use and do you know of a good thread to learn to make your own kitchen?
Yes, I have searched for these. Kitchen one just returns too many results. The Stock OS querry returns too many unrelated posts. I have seen it floating around before.
Any help is appreciated with any portion of this post.
Thanks!
scrosler said:
Does anyone have just the OS ROM portion of the new VZW MR1 update? If so could you link it or explain how you disassemble the NBH file? What tools did you use and do you know of a good thread to learn to make your own kitchen?
Yes, I have searched for these. Kitchen one just returns too many results. The Stock OS querry returns too many unrelated posts. I have seen it floating around before.
Any help is appreciated with any portion of this post.
Thanks!
Click to expand...
Click to collapse
First, you need to extract the self-extracting EXE that Verizon/HTC made.
Download the utility called NBHUtil. This will extract the NBH file and create NB files. In order to compile the individual files into an NBH again, use NBHGen, found in the kitchen under tools, with the following schema...
***Sample
TITA1000
00000000
VZW2.09
USA
200,0_SPL.nb
600,1_Splash.nb
601,2_SubSplash.nb
900,New_ExtROM.nb
300,3_Radio.nb
400,4_os-new.nb
*** End Sample
1 - is the phone model. Must be written as TITA1000
2 - CID
3 - Version
4 - Region Code
5 - 10 - these are the individual files.
first 3 digits is the area of memory to write the file. These MUST be as the sample. Then a comma and the "File Name". In order to create an NBH file that only has one, just delete the other lines. For OS only make it like this...
** OS Only
TITA1000
00000000
DCD_3.2.6
USA
400,4_os-new.nb
*** End OS Only
Edit: Forgot to explain NBHGen. It is a command line utility. Create the "Sample" text above and name it ****.txt (whatever you want to call it). Then run in CMD prompt..... nbhgen ****.txt. All the files must be in the same directory. If it finds the txt file, and the nb files, it will successfully create the NBH file as Ruu_signed.nbh
** OS Only
TITA1000
00000000
DCD_3.2.6
USA
400,4_os-new.nb
*** End OS Only
Click to expand...
Click to collapse
This isn't a dcd rom so why would you call it DCD_3.2.6? Should be whatever the output from nbhextract gives.
gc14 said:
This isn't a dcd rom so why would you call it DCD_3.2.6? Should be whatever the output from nbhextract gives.
Click to expand...
Click to collapse
Yes. I am aware... it's just a sample. You can call it whatever you want. Obviously don't use somebody's "Copyrighted" name. LOL.
gc14 said:
This isn't a dcd rom so why would you call it DCD_3.2.6? Should be whatever the output from nbhextract gives.
Click to expand...
Click to collapse
Thank you both very much. This is the info I needed. I want to delve into making my own kitchens. This is what I needed.
Thank you both!
nitro66215 said:
First, you need to extract the self-extracting EXE that Verizon/HTC made.
Download the utility called NBHUtil. This will extract the NBH file and create NB files. In order to compile the individual files into an NBH again, use NBHGen, found in the kitchen under tools, with the following schema...
Edit: Forgot to explain NBHGen. It is a command line utility. Create the "Sample" text above and name it ****.txt (whatever you want to call it). Then run in CMD prompt..... nbhgen ****.txt. All the files must be in the same directory. If it finds the txt file, and the nb files, it will successfully create the NBH file as Ruu_signed.nbh
Click to expand...
Click to collapse
Quick Question. I noticed the NBH tool you posted as the ability to make and NBH files as well as tear them down. Would you use the NBH Gen program to generate NBH files over this NBHUtil that you posted?
EDIT: Nevermind! I built my first OS only ROM from these two tools. My next question is how do I break the OS.NBH or NB down into the actual kitchen files. I would assume that is the next step to creating your own kitchen, correct? Long ago on my Apache I used the DogGuy Kitchen maker with success. I tried that the other day and it made a mess of my Titan, hehe. Any suggestions? Alos, I would prefer to learn command line if at all possible. I hate GUI's. Yes I really did say that. I hate GUI's.
These tools are in the kitchen as well. There is a readme attached.
scrosler said:
Quick Question. I noticed the NBH tool you posted as the ability to make and NBH files as well as tear them down. Would you use the NBH Gen program to generate NBH files over this NBHUtil that you posted?
EDIT: Nevermind! I built my first OS only ROM from these two tools. My next question is how do I break the OS.NBH or NB down into the actual kitchen files. I would assume that is the next step to creating your own kitchen, correct? Long ago on my Apache I used the DogGuy Kitchen maker with success. I tried that the other day and it made a mess of my Titan, hehe. Any suggestions? Alos, I would prefer to learn command line if at all possible. I hate GUI's. Yes I really did say that. I hate GUI's.
Click to expand...
Click to collapse
I've used the NBH tool to build it... but it came out funky. So I just use the NBHGen utility
nitro66215 said:
I've used the NBH tool to build it... but it came out funky. So I just use the NBHGen utility
Click to expand...
Click to collapse
Ok, same thing here. Otherwise everything is working exactly as you described. Thanks.
Will try the the IMAGEFS tool now.
This is too easy... So far...
Another question but sort of off topic. Is there a way to grab a ROM NB or NBH file from my phone? If so would it bring back all the custom apps and settings?
So I've spent the better part of the evening getting familiar with cooking ROMs--very cool! I cooked a few using PPCGeeks kitchen and played around with different things/options. I've kind of hit a road block--did some searches but really couldn't find anything solid that would guide me. Hopefully someone can point me in the right direction.
1) In the wiki, there are stock ROMs downloadable for Sprint. Is there any way to get the OEM packages that were used to build the ROM? Reason is that there are a few apps that I would like to have that I have not been able to locate that are in the stock ROM.
2) If I have the CAB for an app, is there an easy way to create an OEM package for it? I picked apart a CAB and it looks like it can be done manually but a couple of the CABs I have are pretty big with a ton of files.
Thanks!
Joe
Hey!
I'd recommend going on to ppckitchen.org and downloading their ppckitchen Kitchen. Once you download the application, run the update (if you're running Vista, you'll want to run that as an admin) which will download several rar files containing OEMs and ROM files. Be patient, they're big.
Once updated, navigate to the Kitchen install directory (mine is in C:\Program Files\PPCkitchen.org\BuildOS) and copy the OEM RAR files from the Kitchens directory to new location. I'd recommend the core, PPCKitchen_OEM, Carrier and Generic files as they contain most of what you'll be looking for.
Now, unrar the files and take the OEMs you want to your usual kitchen file (I use DCD 3.2.6). Be aware that some OEMs will not work with some ROMs and wil crash the BuildOS, so experiment and see what works for you. Also, take a look inside the PPCKitchen app (pay respect to the Master Chef) and see if the OEMs you want don't require prerequisite OEMs to be installed.
Voilá... dinner's served.
Hope this helps.
As for the CAB OEMizing, never done that, I pretty much scavenged everything I need. Maybe someone else can help us both.
drnoir said:
Hey!
I'd recommend going on to ppckitchen.org and downloading their ppckitchen Kitchen. Once you download the application, run the update (if you're running Vista, you'll want to run that as an admin) which will download several rar files containing OEMs and ROM files. Be patient, they're big.
Once updated, navigate to the Kitchen install directory (mine is in C:\Program Files\PPCkitchen.org\BuildOS) and copy the OEM RAR files from the Kitchens directory to new location. I'd recommend the core, PPCKitchen_OEM, Carrier and Generic files as they contain most of what you'll be looking for.
Now, unrar the files and take the OEMs you want to your usual kitchen file (I use DCD 3.2.6). Be aware that some OEMs will not work with some ROMs and wil crash the BuildOS, so experiment and see what works for you. Also, take a look inside the PPCKitchen app (pay respect to the Master Chef) and see if the OEMs you want don't require prerequisite OEMs to be installed.
Voilá... dinner's served.
Hope this helps.
As for the CAB OEMizing, never done that, I pretty much scavenged everything I need. Maybe someone else can help us both.
Click to expand...
Click to collapse
Thanks! I did all that already but I'm in "learning" mode right now so I wanted to try a bunch of different things out... one of which was creating OEM files from cabs.
joestop said:
Thanks! I did all that already but I'm in "learning" mode right now so I wanted to try a bunch of different things out... one of which was creating OEM files from cabs.
Click to expand...
Click to collapse
This is what you need. Its great! Turns CAB's into OEM's. Its what I use in my kitchens and ROMs.
http://forum.ppcgeeks.com/showthread.php?t=9830
Good Luck!
-Scott
scrosler said:
This is what you need. Its great! Turns CAB's into OEM's. Its what I use in my kitchens and ROMs.
http://forum.ppcgeeks.com/showthread.php?t=9830
Good Luck!
-Scott
Click to expand...
Click to collapse
THANK YOU!!!
Hi all, I'm trying to make Fido Call Display to work on my Device, and I found the solution here. However the solution requires me to cook the rilphone.dll file into the ROM that I'm using (NAFT's v2.3). I've never cooked a ROM before and I'm far from understanding the procedure, but I don't think it's that hard to add a file in a cooked ROM. Can you guys help me out with this?
Please show me how to add/replace rilphone.dll in NAFT's v2.3 ROM. Thank you.
Replied on other thread
Da_G said:
Replied on other thread
Click to expand...
Click to collapse
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Pretty much leaves the only option as cooking it in, unless you are already using a ROM with a modified nk.exe in XIP to disable certificate checking.. then you can just drag and drop rilphone.dll and reboot.. but since stock ROMs are not modified in such a way, you cook it in, as all files cooked into ROM are trusted..
Unfortunatly there is no way to modify XIP without cooking either.
If a ROM is unprotected (still has it's rgu's) - download a ROM kitchen for your device.. extract the rom of your choice.. replace rilphone.dll in \OEM\OEMDrivers.. then re-assemble the ROM.. no registry manipulation needed.
For the raphael ROM kitchen, name your ROM "RUU_Signed.nbh", put it in \BaseROM
Run RaphaelKitchen.bat
select "e" for extract, then "a" for "From RUU_Signed.nbh"
let it go through its motions, when it's done replace rilphone.dll in \OEM\OEMDrivers
again in RaphaelKitchen.bat select "cf" then "b"
click "BuildOS" tab
click "Load ROM" button
navigate to RaphaelKitcken folder (has subfolders OEM, ROM, SYS, etc), press ok
click green "Go" button
when done, close the window
again the kitchen will go through some motions, when it pops up XVI32 and says "Page Pool Changer" in the command prompt window simply close xvi32
now it should prompt to flash to your device.. and you're done
Click to expand...
Click to collapse
Ya, I tried it with NAFT's v2.3, but it seems that the file is protected... the file can't be read.
I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.
Da_G said:
I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.
Click to expand...
Click to collapse
i tried what you told me to do on the other post; Rename the file, and extract it... I have no problem renaming the file, but when I tried to extract it with Raphael Kitchen, I got error like "Cannot read the file" or something like that... here is the dump log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
Click to expand...
Click to collapse
Nothing was extract.
hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..
Da_G said:
hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..
Click to expand...
Click to collapse
I redownload the Rom and it seems to work now. I can finally extract it.
As for the rilphone.dll... do you have the right one for Rogers Display? and the one that will work for Fido as well?
edit: I successfully reflashed my ROM, but the display thing doesn't work. Beside replacing rilphone.dll is there any reg I need to change? (can you give me the right rilphone.dll file?
I got the rilphone.dll file here
Sucessfully cooked in NaFT's v3.1, however it still doesn't work. It always show unknown Caller.
any help here would be much appreciated
how can i use a kitchen, i have several from dcd, scrosler, and no2chem that ive wanted to try out but cant, to my understanding i have the latest kitchen from ppckitchen.org and have tried putting the .rar kitchen files to my buildos/kitchen folders but cant get them to show up for my selections, how can i do this? do they have to be in a folder??? do i have to extract them??
1 download kitchen RAR file
2 extract to desktop
3 run build os
4 enjoy
ok, do you mean run the .bat file or what? also, what i mean is how do i use it with the ppckitchen???
yes run the .bat file. kitchens are premade in order to "cook" your ownish version of the rom. you can add applications in OEM form to customize the kitchen further. if you have a kitchen for all those roms that you talked about, you need only that specific kitchen that you want to try. cook your rom say in dcd's kitchen, then flash the rom and try it out. honestly, you'd probably be better off using the .exe and flashing a standard version of the kitchen.
I myself am having the same problem. I downloaded DCD beta kitchen but how do I get BuildOS to see the kitchen. I am looking for exact locations to extract the files and where exactly I need to run BuildOS from. Like the normal program files directory or in the unzipped kitchen directory.
drewcam888 said:
I myself am having the same problem. I downloaded DCD beta kitchen but how do I get BuildOS to see the kitchen. I am looking for exact locations to extract the files and where exactly I need to run BuildOS from. Like the normal program files directory or in the unzipped kitchen directory.
Click to expand...
Click to collapse
DCD's kitchen works by itself. You do not put it in the PPC kitchen.
Just download DCD's kitchen, extract to its own folder, run the batch file.
unL33T said:
DCD's kitchen works by itself. You do not put it in the PPC kitchen.
Just download DCD's kitchen, extract to its own folder, run the batch file.
Click to expand...
Click to collapse
When I do this a DOS window opens and says relocating modules. The a BuildOS window opens and a bar on the bottom moves across while it is loading or doing something. The DOS window then asks me to put the phone in bootloader and the RUU opens. Shouldn't I be selecting OEM and packages to include first? Am I running the kitchen wrong?
kflipproductions said:
yes run the .bat file. kitchens are premade in order to "cook" your ownish version of the rom. you can add applications in OEM form to customize the kitchen further. if you have a kitchen for all those roms that you talked about, you need only that specific kitchen that you want to try. cook your rom say in dcd's kitchen, then flash the rom and try it out. honestly, you'd probably be better off using the .exe and flashing a standard version of the kitchen.
Click to expand...
Click to collapse
thats another thing, ive seen tutorials where it shows to click the .exe but the thing is that there is no .exe file in it, just the .bat file. believe me, ive tried searching but could not come up with anything.
unL33T said:
DCD's kitchen works by itself. You do not put it in the PPC kitchen.
Just download DCD's kitchen, extract to its own folder, run the batch file.
Click to expand...
Click to collapse
so then there is a way to do it from the .bat file??? also, when ever i click the bat file, i get an error saying that i need .net framework 2.0 and i already have it, i know this because when i downloaded it and tried to install it, it tells me i already have it. the picture attatched is what screen comes out as an error.
m_reyna_16 said:
thats another thing, ive seen tutorials where it shows to click the .exe but the thing is that there is no .exe file in it, just the .bat file. believe me, ive tried searching but could not come up with anything.
so then there is a way to do it from the .bat file??? also, when ever i click the bat file, i get an error saying that i need .net framework 2.0 and i already have it, i know this because when i downloaded it and tried to install it, it tells me i already have it. the picture attatched is what screen comes out as an error.
Click to expand...
Click to collapse
Both of those are odd problems I haven't seen before. Maybe posting what OS you're working in (XP/Vista, 32 or 64 bit) might help some other people help you. My experience with the kitchen is limited to 32 bit XP and I haven't had any problems.
unL33T said:
Both of those are odd problems I haven't seen before. Maybe posting what OS you're working in (XP/Vista, 32 or 64 bit) might help some other people help you. My experience with the kitchen is limited to 32 bit XP and I haven't had any problems.
Click to expand...
Click to collapse
well i have a vista 32 bit laptop, just so anyone knows
go to THIS thread for the solution
This is the kitchen I am currently using to build my rom series, my main reasons for releasing this are to try and progress development of 6.5 builds on the athena.
I am going to assume that if you have in depth knowlege to rom building that you would have probably put your own kitchen together, so please dont post questions etc if you have tried to do something out of your comfort zone i.e porting new builds(this is a bit more involved)
The kitchen contains saved builds of my latest releases, 23060 and 23053, load whichever you wish and add and remove packages etc, I will try and assist as much as I can.
There are many guides on ervius kitchen I would suggest reading them if you are new to it.
My hope is that we can resolve the few remaining issues I have in a more efficient way than me spending 5/6 hours every night building and testing roms, the main existing problems are:
DRM
Manila
Autorotation
All the saved config files have been recmodded to attain max slot 0 memory allocation, I would not advise recmodding any more modules as this will probably cause a non booting rom.
I will try and update with latest versions with a config file as they become available.
Please do not release roms into the forums, my intention is that you use it to learn and build your own spec roms
Download Link!!!!!
http://www.megaupload.com/?d=YI469SR4
***PLEASE NOTE***
THIS IS NOT FOR PEOPLE WHO DO NOT UNDERSTAND WHAT THEY ARE DOING, YOU RUN A HIGHER RISK OF BRICKING YOUR DEVICE IF YOU GO IN BLIND, AS WITH ROMS THIS IS FOR SPL3.5 DEVICES, I AM MORE THAN HAPPY TO ASSIST ANYONE WHO NEEDS IT PROVIDING YOU ACCEPT I CANNOT GIVE ALL MY TIME TO THIS AS I HAVE A FAMILY AND A JOB TO LOOK AFTER, IF YOU NEED HELP I CAN WALK YOU THROUGH IT VIA MSN ETC
******Reserved************
********Reserved*********
Lol, first hurdle, the kitchen is 802mb and sendspace wont allow me to upload more than 300mb
anyone got any ideas
can you upload a torrent?
ZIP > split > upload parts?
Split to 100MB parts and PLEASE upload it to Rapidshare
Thanks
you can rar/zip and split it into 250MB parts (less parts to download than to have each part at 100MB) or you can upload to torrent (but we would need seeders....the dedicated file servers are a better option though)
I managed to reduced the size somewhat and its now on megaupload, the link is now in the first post.
For those wishing a beginers course, I am going to try and do one tomorrow, but will start a seperate post for it.
I have not tested this kitchen but it should work fine.
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
lennie said:
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
Click to expand...
Click to collapse
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
avengerpenguin said:
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
Click to expand...
Click to collapse
As I asked in private messages. can u make a tut for this specially how to work with your kitchen xip/sys porting section?
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
lennie said:
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
Click to expand...
Click to collapse
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
avengerpenguin said:
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
Click to expand...
Click to collapse
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
lennie said:
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
Click to expand...
Click to collapse
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
avengerpenguin said:
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
Click to expand...
Click to collapse
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
lennie said:
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
Click to expand...
Click to collapse
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
avengerpenguin said:
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
Click to expand...
Click to collapse
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
lennie said:
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
Click to expand...
Click to collapse
I have been struggling with this as well, I have not managed to find a portable xip.bin for 28014 as of yet. If you find one let me know please.