Related
hi
before installing Tom rom I have decided to dump my original rom in case I needed to put it back.
anyway I have been able to dump the 4 Raw files. now I see that in the Kaiser section there is a guide on how to reconstruct a rom to make it flashable and I wonder if I can do the same with my Niki.
any expert could pls confirm this?
thanks in advance for your help.
cheers
edit: I ve just noticed that there are some other threads about this subject...anyway if someone can confirm the right procedure would be great. thanks
Yeah, also wondered about that Kaiser rebuilding tutorial.
Talked to a few people over PM who have the same problem.
But even in the Threads nobody who knows more about flashing/ROMs seem to be willed to help out with a fre informations. :-/
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?
Thyraz said:
Yeah, also wondered about that Kaiser rebuilding tutorial.
Talked to a few people over PM who have the same problem.
But even in the Threads nobody who knows more about flashing/ROMs seem to be willed to help out with a fre informations. :-/
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?
Click to expand...
Click to collapse
well..nice qustions..to which obviously I cant reply..hope someone will be so kind to help us out.
Thyraz said:
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?
Click to expand...
Click to collapse
a baserom is nothing more then a normal rom, just put a rom you like, together with the dumped filen in the kitchen folder. maybe ruu needs some information from the rom file itself, which are not present on the device.
what you find on your device is just that what you dumped. (but after hardreset)
.. i know that this not matters for you anymore. but eroG needs to know.
therealholg said:
a baserom is nothing more then a normal rom, just put a rom you like, together with the dumped filen in the kitchen folder. maybe ruu needs some information from the rom file itself, which are not present on the device.
what you find on your device is just that what you dumped. (but after hardreset)
.. i know that this not matters for you anymore. but eroG needs to know.
Click to expand...
Click to collapse
well yes I defenitely needed to know these things...
now, if it is not of too much trouble for you, where do I find a baserom and is there a guide on how to do it...just to avoid stupid mistakes while doing it?
thanks a lot
So, from baserom there are not much information used. (Perhaps Header information for Rom file, or something like that)
My new ROM is (more or less) the same result as on my device?
And Baserom isn't a own file format, i can use the wwe-rom postet here in the forum?
thx for help
Thyraz said:
And Baserom isn't a own file format, i can use the wwe-rom postet here in the forum?
Click to expand...
Click to collapse
Yes that should work fine.
request guide on how to get dumped rom back to device
i've read alot about how to dump rom from device and how to get dumped rom back to device.
the more i read i got confident how to dump rom .... did it .. and now have my 4 raw files.
on the other hand the more i read about how to get dumped rom back to device ... more and more i got unsure how to do it.
so please all senior posters and specialists - can you please post a cookbook on how to get it back to the device ?
thanks ! alot and keep up the good work here !
Sackbauer, I totally agree with him.
I have 4 Raw files for a Norwegian ROM, but how do can i "transform" them into a acctually "flash" file?
Please someone with the knowledge, write a "easy to understand/ step by step" guide to the ones that don't have a clue about this..
Ole
im getting kinda confused with this also, dumping the rom is no big deal, but putting it back together and flasing my phone with it, thats the big how to...
I has contact with Tom.
And he busy with vietnamese new year now.
He said will back after 1,2 day and answer all questions..
Don't worry
... good to hear that tom will take care after his new year ;-)
also keep my fingers crossed that someone is able to check radio rom and possibly enable gps and wifi ...
let me try first:
- download this kitchen
- Copy your part01.raw and part02.raw into the BaseRom Folder of this kitchen
- Copy a Nike RUU_signed.nbh into the BaseRom Folder (e.g. tom_codons rom just open the. exe with winrar and extract the file)
- Open !Begin.cmd, press 2 and do everything, what is prompted
- Open !Cook.cmd and do what is prompted
- when HTC Rom Tool is opened press Rom_Builder and ... right from System. Then Choose os_new.nb and press built
i wrote this without testing again. so if i missed something tell me, please and i'll try to help.
sounds good !
will try it later this evening and will let you know ...
thanks so far
omg .... it appears that i just "cooked" my first rom out of my dumped files from my niki .
thanks therealholg for your guide !! thats what i was looking for.
the only thing which makes me a bit nervous about reflashing my just cooked rom onto my device is that during cooking it sometimes says "file not found".
but after ignoring these messages i have a nbh file which obvioulsy was not in the folder before !!! ;-) yeah
so, now i know how to revert the process but i am to anxious to try it as this is my only niki.
lets see and wait what others say about the step by step guide of therealholg ...
in anyway - you made my day therealholg
cheers
wow... thanks for this...
tryed it out and works...
the only thing is that it still says Niki Project on the boot screen...
everything else works just fine
marazi said:
wow... thanks for this...
tryed it out and works...
the only thing is that it still says Niki Project on the boot screen...
everything else works just fine
Click to expand...
Click to collapse
You can add the splash screen in HTC Rom Tool.
therealholg said:
let me try first:
- download this kitchen
- Copy your part01.raw and part02.raw into the BaseRom Folder of this kitchen
- Copy a Nike RUU_signed.nbh into the BaseRom Folder (e.g. tom_codons rom just open the. exe with winrar and extract the file)
- Open !Begin.cmd, press 2 and do everything, what is prompted
- Open !Cook.cmd and do what is prompted
- when HTC Rom Tool is opened press Rom_Builder and ... right from System. Then Choose os_new.nb and press built
i wrote this without testing again. so if i missed something tell me, please and i'll try to help.
Click to expand...
Click to collapse
What to do with part00.raw and part03.raw?
Part00.raw is the are with IPL, SPL and Splashscreen. We don't want to override our new SuperCID Bootloaders
Part03.raw is content of your local storage ... i think you can't flash this area with ruu.
hi all friends...!
I'm just back from some days busy with vietnamese new year.
And have made code kitchen for reconstruct a dumped rom niki device.
What we need to do now ?
1. Copy part02.raw u dumped from original rom to Tools folder and run step1.bat
2. Extract RUU_signed.nbh from Ship rom and put in ShipRom folder.
Link download :
http://www.asia.htc.com/download/RU....707.09_Radio_Nike_1.58.16.27_signed_Ship.zip
Or here :
http://www.asia.htc.com/download/RU....871.14_Radio_Nike_1.58.16.27_signed_Ship.zip
3. Run Reconstruct a dumped rom.cmd in my Tools and wait some times.When page DOS done it will exit .U go to Update_Rom folder already have new RUU_signed.nbh.This files reconstructed your original Rom with your languages.
Have funs..!
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?
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
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.
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