Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
maximumbs said:
Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
Click to expand...
Click to collapse
if you're using kaiserchef, just drop the diamond .nbh in BaseROM, then run RunMe.bat, then choose E, then B. I just did it and it worked fine, but if you only want to extract the SYS, I suggest making a temporary KaiserChef2 folder in order to keep the rest of your folders
maximumbs said:
Quick question to all cooks, how do you properly extract the SYS folder from diamond ROM? I used the 20296 XIP from the Diamond thread and used SYS 20273 from NIKI kitchen and ported both for Kaiser and flashed well except the SYS from NIKI Kitchen seems to be missing some files. When I used the 19212 SYS it works fine. I was able to download the OS.NB for 20273 and I tried to use KaiserChef to extract the SYS by adding an additional option in More options to where it will bypass the NBH extract provided that I pre-create a Temp folder and drop the OS.NB, OS.NB.PAYLOAD which I used NBSplit. It created the SYS fine but when I copied my original SYS over to it and cooked, it didn't turn out right. I also tried dumping the ROM using the commands below:
nbsplit -kaiser os.nb
imgfsfromnb os.nb.payload imgfs.bin
imgfstodump imgfs.bin
It successfully dumped everything, but the problem is that I cannot find the SYS folder. I searched for tutorial on this but only thing I find is XIP dumping. Thanks.
One more question, can the OS.NB and OS.NB.PAYLOAD from diamond be used for Kaiser (maybe some sort of porting?) or not at all?
Click to expand...
Click to collapse
The key to making it work??? Use the relocation tools on all & any modules!
Sorry if I have a lot of question, I'm still learning, please bear with me . How do you use the relocation tools in KaiserChef? I noticed when buildos starts compiling the image it does a g'reloc. Is that the same? Does it mean that when you use the relocation tools, you can use the OS.NB and OS.NB.PAYLOAD from the actual diamond ROM?
Also, I can't seem to find any NBH for 20273 or higher roms. The only one I found is the OS.NB from 20273. Anything else is either just the XIP or SYS. Can anyone point me to a good ROM repository? I noticed 20721 is out but cannot find any source. Was it from the OMNIA? I pooked around but found that the OMNIA doesn't seem to use NBH unless the site I was reading was wrong.
Thanks for everyones patience on this. I really would love to cook and contribute back. Just taking a while as I am trying to get the hang of it.
Edit: Found the OMNIA ROM from the thread on this forum. D/L it now... and from what I am getting, I should be able to dump it using Kitchen from Diamond. Hopefully it is similar when it comes to porting the XIP and SYS.
Can anyone tell how to find the version of the XIP from say an NBH or extracted NB?
Thanks
Related
I'd like to prepare a new kitchen but I have some problem to extract XIP from actual Kaiser Rom. I'm using Xipport (the bepe's tools) to dump Xip.bin, but when I press "dump xip.bin" button, i have a crash of the Xipport and i have any dump.
Someone has suggestion to me?!
Thanks
Are you using an original rom or are you dumping from a phone????
The reason I ask is that if you are using an original rom or a customized rom and you use the KaiserKitchen, it already dumps the file for you if you follow the steps. Under folder XIP.
ryncppr said:
Are you using an original rom or are you dumping from a phone????
The reason I ask is that if you are using an original rom or a customized rom and you use the KaiserKitchen, it already dumps the file for you if you follow the steps. Under folder XIP.
Click to expand...
Click to collapse
I'm using a customized rom. I Think that Xip.bin has some relocation in your internal byte like a repack...it's possibile? There is some program that it can analize the file to see if the xip is packed?
furb3t said:
I'm using a customized rom. I Think that Xip.bin has some relocation in your internal byte like a repack...it's possibile? There is some program that it can analize the file to see if the xip is packed?
Click to expand...
Click to collapse
i noticed using any os other than vista could help you.
redbandana said:
i noticed using any os other than vista could help you.
Click to expand...
Click to collapse
I use win xp I think that the chef has crypted or packed some file so, it's impossibile to extract XIP from rom. But, what are the tools to do this? And how to reverse?
just to give you an attention, make sure that you have extracted the exact xip.bin.
i extracted before but after 10 days of problems in porting, i found it was because of xip.bin wasn't 100% correct.
good luck.
Maybe someone can make a complete tutorial for XIP porting ?
its right said:
just to give you an attention, make sure that you have extracted the exact xip.bin.
i extracted before but after 10 days of problems in porting, i found it was because of xip.bin wasn't 100% correct.
good luck.
Click to expand...
Click to collapse
i agree with you, but the answer is: how do you have found the xip.bin correct?!? what are tools that you have used?
Thanks
furb3t said:
i agree with you, but the answer is: how do you have found the xip.bin correct?!? what are tools that you have used?
Thanks
Click to expand...
Click to collapse
for kaiser, sometimes the current tools for extracting xip don't work well, i have no exact idea in kaiser.
but in general, i'm using the famous tools used in many public kitchens.
ItsRight this is a development forum not a crypted forum, so could i know the name of tool and how to use it?! thanks
furb3t said:
ItsRight this is a development forum not a crypted forum, so could i know the name of tool and how to use it?! thanks
Click to expand...
Click to collapse
lol... who told you i'm crypting something !!!
anyway, have a look in kaiser_kitchen which contains good tools for extracting xip.bin
use a hex editor
extract whatever.nbh
then
nbsplit -kaiser os.nb
this gives you os.nb.payload and os.nb.extra.
your xip is in os.nb.payload- open it in a hexeditor
run imgfsfromnb os.nb.payload imgfs.bin
note the start of imgfs address
jump to that address in your hexeditor and delete from there to the end of the file
now move back to the beginning of your remaining data in hexeditor
search for the start of xip part: FE0300EA
(if not a custom rom the address is probably 0x00320000)
when you find that start of xip, delete from there to beginning of file
the data you are now left with is your xip. save it as xip.bin
hope this helps...
My problem is not to find xip.bin, but dump the xip.bin. When I use Xipport, i have a crash of the program.
Tanks for sharing dcd1182, and for rebuilding ?
furb3t said:
My problem is not to find xip.bin, but dump the xip.bin. When I use Xipport, i have a crash of the program.
Click to expand...
Click to collapse
what we are trying to tell you is that your problem dumping xip.bin is probably a result of a problem extracting xip.bin
if you have a proper xip.bin you should be able to dump it in xipport as normal.
edit: or you're missing a dependency of xipport, probably .net 2.0 but im guessing.
ok i did XIPPORT on hermes with buildxip and insert
now on kaiser how do i insert the xip back to OS.nb
is it write xip_out.bin to os.nb.payload at adress 00320000 or ? is it different
1 - i got os.nb 19212 official running in my kitchen --- OK
2 - from payload extracted xip ---- OK
3 - XIPPORT dump OK
- realloc P ERROR " Unknown o32 region flags: d0000040 "
change 72.......dsm - OK
NEED HELP please
- packages and undo OK
- write maps OK
skip to step 5
5 - buid xip_out OK
6 - insert xip_out into os.nb.payload at 00320000 OK
7 - nbmerge to OS.NB OK
8 - OS.nb to kitchen ????????? lets seee OK ......... IT IS BOOTING OK
9 - move new xip MSmodules into XIP BUT HOW WITHOUT REALOC WORKING HMMM
anryl said:
ok i did XIPPORT on hermes with buildxip and insert
now on kaiser how do i insert the xip back to OS.nb
is it write xip_out.bin to os.nb.payload at adress 00320000 or ? is it different
1 - i got os.nb 19212 official running in my kitchen --- OK
2 - from payload extracted xip ---- OK
3 - XIPPORT dump OK
- realloc P ERROR " Unknown o32 region flags: d0000040 "
NEED HELP please
- packages and undo OK
- write maps OK
skip to step 5
5 - buid xip_out OK
6 - insert xip_out into os.nb.payload at 00320000 OK
7 - nbmerge to OS.NB OK
8 - OS.nb to kitchen ????????? lets seee OK ......... IT IS BOOTING OK
9 - move new xip MSmodules into XIP BUT HOW WITHOUT REALOC WORKING HMMM
Click to expand...
Click to collapse
don't care about this error. go to make xip_out.bin and write it into os.nb.payload
sure can change just the DSM file to get new number but i wanted to fuly xipport all the new ms-modules
anryl said:
ok i did XIPPORT on hermes with buildxip and insert
now on kaiser how do i insert the xip back to OS.nb
is it write xip_out.bin to os.nb.payload at adress 00320000 or ? is it different
1 - i got os.nb 19212 official running in my kitchen --- OK
2 - from payload extracted xip ---- OK
3 - XIPPORT dump OK
- realloc P ERROR " Unknown o32 region flags: d0000040 "
change 72.......dsm - OK
NEED HELP please
- packages and undo OK
- write maps OK
skip to step 5
5 - buid xip_out OK
6 - insert xip_out into os.nb.payload at 00320000 OK
7 - nbmerge to OS.NB OK
8 - OS.nb to kitchen ????????? lets seee OK ......... IT IS BOOTING OK
9 - move new xip MSmodules into XIP BUT HOW WITHOUT REALOC WORKING HMMM
Click to expand...
Click to collapse
Did this method of buildxip and then inserting the out.bin into payload via xipport tool work brother? i'm trying desperately to full port xip for diamond myself... nobody suddenly seems to know how to do full xip porting manually
Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks
As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,
Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"
Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.
Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.
I'm stuck
I'm trying to understand process of creating ROM, I've done thise steps:
1. Decompile *.NBH to *.NB files
a. Dutty's NBHTool http://forum.xda-developers.com/showthread.php?t=296311
b. NBHextract http://forum.xda-developers.com/showthread.php?t=289830
2. Deprotect ROM (Ervius ROM Deprotector http://forum.xda-developers.com/showpost.php?p=3102543&postcount=1)
3. OS.NB to OS.nb.payload (NBSplit.exe -kaiser Windows.nb) nb-> nb.payload+nb.extra
4. Extract imgfs (ImgfsFromNb.exe Windows.nb.payload imgfs.bin)
5. Create dump (imgfstodump imgfs.bin) imgfs.bin ->\dump\*.*
in the Dump folder many folders-files of DLLs, imageinfo.bin and imageinfo.txt for each of them.
Now how to decide where is OS and where is App's ?
what to \EXT of kitchen, what to \OEM, \ROM, \SYS ?
or I'm going wrong way ?
Pls "GooRoo of ROMs" help me
You only need ervius visual kitchen to do it all (has dutty's tool included). Open the erviuskitchen.exe and click on dump rom, navigate to the nbh file and the rest will be automatic (unless you are trying to decompile a protected (user-made) ROM)
Side note: this is not development related so I moved this to Q&A
Thanks 12aon
sorry for post not-in-thread
I would like to get SYS, XIP and OEM fram an original Wizard WM5 ROM. Can anyone help?
I tried HyperCore Kitchen but that didn't work.
What I have done so far:
- unzipped nk.nbf file from original installer
- used typho5.exe to extract nb files from nk.nbf (typho5.exe nk.nbf -x)
Now I ave the os.nb file and don't know what to do.
For ImgfsFromNb.exe I need an os.nb.payload file.
May I use NBSplit.exe with a Wizard ROM? Which parameter do I have to use?
What else do I have to do?
Thank you for your help!
mate.. use this:
typho5 -x nk.nbf
ren *OS.nb OS.nb
imgfsfromnb OS.nb imgfs.bin
imgfstodump imgfs.bin
pkgtool
Click to expand...
Click to collapse
Thank you very much!
I got the OEM and SYS folders but there is still one last problem: The names of the subfolders are strange. Seems to be the GUID. Is there a way to get the original names?
I ripped the official german Vodafone WM5 AKKU2 ROM.
Cyberdyne said:
Thank you very much!
I got the OEM and SYS folders but there is still one last problem: The names of the subfolders are strange. Seems to be the GUID. Is there a way to get the original names?
I ripped the official german Vodafone WM5 AKKU2 ROM.
Click to expand...
Click to collapse
No, it's bug in T-Mobile releases.
A bug in T-Mobile releases make my Vodafone realease look strange?
Here they are from the
Code:
RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe
Some packages also have GUID instead of a name, but I do not think that should affect the cooking. You could rename the folder based on what is inside it.
http://rapidshare.com/files/345802803/Dumped_Original_Cingular_ROM.7z
How do I add a file to xip? I want to use extendir. It involves adding the extendir.dll file to xip. When I use xipport and mreloc, there are too many entries in the maps, I am confused which to modify. BTW I am using P525, ROM, SYS, OEM from alex's 20273 kitchen and Osbuilder to cook my rom.