Hi,
I have been using a few kitchens but none of them can dump its own generated ROM back, what I did is:
1. use this kitchen to create RUU_SIGNED.NBH.
2. use this kitchen to dump from NBH file just created.
3. No OEM and SYS directory are created or the directory are created but no files inside.
Can anyone recommend a kitchen which can have files sorted to OEM and SYS in step 3?
Why
HTC_FUZE said:
Hi,
I have been using a few kitchens but none of them can dump its own generated ROM back, what I did is:
1. use this kitchen to create RUU_SIGNED.NBH.
2. use this kitchen to dump from NBH file just created.
3. No OEM and SYS directory are created or the directory are created but no files inside.
Can anyone recommend a kitchen which can have files sorted to OEM and SYS in step 3?
Click to expand...
Click to collapse
Hey HTC_FUZE, Why do you want/need to dump your own ROM? Surely if you have the kitchen - the OEM and SYS are already there! Why don't you just recook with the changes that you want to make to it?
If your trying to dump somebody else's ROM then it may be protected. Some chefs protect their ROMs from being dumped.
Secc
just in case my hdd is dead or files corrupted, so I still have chance to extract rom from my phone and get the same dump as before
Ahhhh...
HTC_FUZE said:
just in case my hdd is dead or files corrupted, so I still have chance to extract rom from my phone and get the same dump as before
Click to expand...
Click to collapse
My best advice to you is to do what i do BACK UP!!! When i first started i never backed my kitchen up, then i lost my whole kitchen, had to start from scratch!! Now, every couple of builds i backup the whole kitchen to a rar and save on a external drive.
A few weeks ago my working kitchen got corrupted somehow, i just restored the rar, imported the new build and was cooking again in no time - without the backup, i'd be knackered!!!
Secc
The OEM folders unfortunately end up in the SYS folder when you dump them. Simply pull them out and put them into the OEM folder and you're set. Something to do with the kitchens recreating the DSM's incorrectly.
@jwzg:
Correct; unfortunately, most kitchens strip the .DSM/.RGU during ROM compilation. Ervius tried to implement a method to preserve the .DSM/.RGU for decompilation but it didn't work as he'd hoped.
@HTC_FUZE:
You need to backup your working kitchen; unfortunately there's no other way. I usually do the following:
File copy the kitchen to a backup HDD
File copy the compiled .NBH I used on the device to a backup HDD
.RAR the kitchen
You could go one extra step and burn the lot to a CD/DVD.
HTH,
This is what I am doing now. However, I would like to have such a kitchen I mentioned. I found one of the ROMs I downloaded can be dumped and sorted like official ROM. I may ask him which kitchen he uses.
I have a Wizard ROM which can be dumped like this. It was made with with an old kitchen that is incompatible with newer devices.
jwzg said:
I have a Wizard ROM which can be dumped like this. It was made with with an old kitchen that is incompatible with newer devices.
Click to expand...
Click to collapse
Hi, Jwzg:
If it is working with Fuze, I would like to have it. Could you give me it? Thanks
Related
I have begged my friend to dump the HK local ROM (from 838pro) for me. I have a Taiwanese CHT9000. After reading the previous articles, it seems that the files in my hand (3 raw files) cannot flash the ROM into my CHT9000. Is that correct? So, what's the purpose of dumping the ROM?
Sorry...I am the beginner here.
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeFAQ
Is it possible extract a ROM from a device and convert it to a flashable ROM? (to have a Backup or to flash it on another device)
Short answer: No, it is not possible.
Long answer: A ROM consists of 7 parts:
1. Extended ROM
2. OS Image
3. IPL (part of bootloader)
4. SPL (part of bootloader)
5. Splash screen
6. HTC Logo (normally uses the same image as the splash screen)
7. GSM radio code
You can dump the original rom, but only the things contained in the FLASH will be dumped, this does not include the IPL, SPL, splash and radio parts, so its unuseful for flashing it back.
Theoretically: if you would have the private keys for one of the 3 certificates stored in the bootloader, used to verify .nbh files, you would be able to create your own .nbh file, and flash it.
Click to expand...
Click to collapse
Hi pof,
Yes. I have read that. So, what's the answer? What does those raw files do? What's the purpose of getting the FLASH dumped? For development?
I used them mainly to see diffs betwen roms / vendors OS bundle and extract files from ROM. You can make a modified OS image out of a dumped OS rom, so when we will be able to flash our own code (see SD-image flashing on the wiki) you can delete unuseful files (help, images...) and add programs directly to the rom... but there's a lot of work to do until we reach that, and very few people can help in the research
Hi
I have another problem. I have dumped my MDA Vario II German ROM and extracted the Part02.raw.
If I try to use the extracted .cab files, the installation fails. Even I can't open the .cabs with Winrar.The files are damaged.
I've tested it with an other Part02.raw from the Developers FTP with the same result.
What's wrong ?
It semms, that the ROM dump ist useless.
Even, you can't use the midi and wave files.Also bmp and jpg files have the same problem.
Couriosity is, that some files work and most not.
I think it's the same problem with other parts of the romdump.
Hey guys
I dumped the black2.5 rom, hoping to make some modifications to the unlock app. Now I have a .raw image, but I am a little unsure as to reading it. I downloaded duttys koch, but I dont think that was the right approach. Im not seeing anything on the wiki, and my searching has brought me here. Can anyone point me in the right direction? Thanks.
@peezy:
Here's how to reconstruct a dumped rom:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoReconstruct
http://wiki.xda-developers.com/index.php?pagename=Trinity_HowtoReconstruct
But in your case, you have the NBH, so no need to dump & reconstruct, you can work with it with tadzio imgfs tools + bepe's packagetool.
pof said:
@peezy:
Here's how to reconstruct a dumped rom:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoReconstruct
http://wiki.xda-developers.com/index.php?pagename=Trinity_HowtoReconstruct
But in your case, you have the NBH, so no need to dump & reconstruct, you can work with it with tadzio imgfs tools + bepe's packagetool.
Click to expand...
Click to collapse
Hopefully a little humor won't get me in trouble, but with dutty's koch, tadzio's tool and bepe's package - you should have everything you need
@pof thanks a bunch!
@todd ahhhh yeeaaahh... <70's pr0n music.wav>
Hello everybody!
Even if this is my first post on this forum, I use to visit this useful place since years, I tried many of those great WM6 ROMs made by our ROM cookers (thanks to all), then I tried to cook my own ROMs using tools recommanded in the Wiki.
But those kitchen tools weren't conveignent for my use, it was a lot of work and patience for making ROMs, we need to use many different programs and scripts, and I thought that the cooking process could be really simplified using an unified graphical interface like dutty's tool. I was patiently waiting for his Hermes Rom Koch V2, but finally I started to develop my own kitchen tool!
Here are some features of this program:
- ROM file manager (to add/delete/extract files or to create shortcuts)
- ROM layout editor (to edit init flash files)
- Registry editor (to modify/import/export default & user registry)
- CAB install files integration
- ROM creation from original OS image or dump directory
I posted some screenshots for better explanations.
This program simply use aWaiter and ImgFS tools for ROM creation/extraction.
For now I still have a lot of work on it, but I would like some advises from experienced developers on this forum, because even if my program works, I would like to know if the cooking process is porper and safe, and how I could improve it (for example using internal functions for ROM creation/extraction instead of external programs, implementing NBH tools,...).
If some of our XDA-developers are interested, I would really like to make this project an Open Source "all-in-one" ROM cooking program, gathering all the others kitchen tools in an unified graphical interface offering the easiest way to cook nice ROMs for our Hermes and certainly for other devices.
I know that I didn't give many details about my program but don't hesitate to ask me about it. I would also have few questions for developers.
Developers and ROM cookers, I'm waiting for your feedback!
Thanks.
This looks very user friendly, I will be watching closely. Good work.
What language is it in? (programming language that is)
Midget_1990 said:
What language is it in? (programming language that is)
Click to expand...
Click to collapse
I developed this program in C# (using .NET framework 2.0).
Thx for your work! It would be better if the tool support packages.
http://forum.xda-developers.com/showthread.php?t=296861
Where to download??
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
I'm still working in this project, so I didn't plan any release yet.
Good idea and nice project.
Go on dude !
Good work.
Great work so far - I fullly support this project.
Lookign forward to the release.
schaps said:
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Click to expand...
Click to collapse
Great project - and I agree, it definitely should support packages. If you've had a look at bepe's kitchen, you already know how much easier it is to understand the purpose of all the files in a ROM if they are organized in packages.
.rgu files are Registry "source code". They are not part of the package mechanism. And yes, when cooking a ROM you can leave them out, as they are not needed at run time. Saves a bit of space.
The .dsm files, otoh, are needed at run time.
When I cooked my ROM, I did find some information (written by bepe) here in the forum about how to make your own packages. Can't remember where that was, but I found it on my hard disk, so I simply quote it here again:
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://www.famkruithof.net/uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files, shortcut on the ROM.
For Example/ Ilustration: Open or read Dev/LOC/initflashfiles.dat using a text editor or any premake initflashfiles.txt at one of the OEM folder.
and there MUST be a empty line at the end of iniflashfiles.txt also!!
Copy all files you need to Dev/OEM/[Your package name]/
Click to expand...
Click to collapse
Hope that helps. If I remember correctly, bepe told me that the OEM folder is treated a bit differently from the SYS folder, so it might be you can't create packages there. But then, you probably also shouldn't.
Oh, and about the initflashfiles.dat: you are aware that the initflashfiles.dat just copies files and does not move them? Using this feature extensively uses up ROM space very quickly, so it should be done for small files (like the start menu shortcut files) only.
Cheers
tadzio
Thanks a lot for your help tadzio!
I also read the different steps about how to add a new OEM package, I found information on this Wiki if someone is interested : http://wiki.ppcgeeks.com/index.php?title=Kitchen.
I think I know enough about it but what I would know is how to extract packages then to merge them for creating a ROM image, like do bepe's tools?
I confirm I also heard that OEM folder processing is different from SYS folder.
Concerning the initflashfiles.dat I guessed that files were copied from ROM to storage memory, good to have a confirmation. So it means that if we want to include a new program in ROM, we should better to let it in Windows folder than to put it in a Program Files folder, right? I have another question about initflashfiles.dat, I saw that it sometimes uses variables for directories instead of strings (for example Directory(LOC_XXX), Directory(0409_XXX),...), where could I find those variable declarations?
schaps for president
schaps said:
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
Click to expand...
Click to collapse
Hi Schaps,
you can have a look in this link:
http://forum.xda-developers.com/showthread.php?t=312985
it's a tool to re-build DSM file, which is better than just creat an empty .dsm file when making new package.
hope this help. It will be cool if your new tool support package.
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?
Looking for some info on how rom files are structured and how manipulte them
I have .nb0 file that I want to flash but I'm not sure what else is in it other than the OS. How do I get this file into a format I can flash ?
spicer said:
Looking for some info on how rom files are structured and how manipulte them
I have .nb0 file that I want to flash but I'm not sure what else is in it other than the OS. How do I get this file into a format I can flash ?
Click to expand...
Click to collapse
Some ktichens will allow you to convert OS.nb into a bootable ROM. There are also some programs that will let you do it. You can try my kitchen, it is pretty straight forward and read through it carefully and you shouldn't have a problem. Kink to kitchen is in my sig.
At0mAng said:
Some ktichens will allow you to convert OS.nb into a bootable ROM. There are also some programs that will let you do it. You can try my kitchen, it is pretty straight forward and read through it carefully and you shouldn't have a problem. Kink to kitchen is in my sig.
Click to expand...
Click to collapse
Thanks! I'll give it a shot. Will this help me figure out whats in cluded in the nb0 file?
Have a look at this thread ...
http://forum.xda-developers.com/showthread.php?t=490787
it provides some info on what's in the ROM and should easily compliment At0mAng's kitchen.
Cheers,
Good info thnx.
Question
When I run option 7->3
( Make a Bootable ROM from OS.nb files -> HTC ROM Tool for Touch Pro ROM)
the program just bails on me. Any idea why? os.nb is there. i can do 7->2 and it works fine but but I have a touch pro (option 3).
also how do I find out what is in a .nb0 file?
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.