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
Related
I have ROM files in NBF format. I want to convert it to BIN format in order to edit it. I tried using some tools (prepare_imgfs.bat and NBFtools) method with no success. Can anyone tell me how to do it?
However I'm using Vista. Maybe Vista won't allow to convert it?
i have the same problem, but not with vista, with xp. :-(
helppppppppppppppp
Here, extract nbf with typhoonnbftools.exe (dump as decrypted)
and pack with nb2nbf - read wiki for htc wizard
I've been able to convert the NBF to BIN using prepare_imgfs command after reinstalling Vista. Now no matter how hard I try the viewimgfs command can't dump the BIN file. Maybe the possibility of cooking a ROM in Vista is minimum.
how can i edit BIN files?any softwares?
editing .nbf can be done(contact chinese, they made iphone and vista rom), ive tried the metods mentioned before,but did not work for me. the problem is if u make an unstable rom who can stop in upgrading utility you can get not a custom mobile rom, but a custom brick.
WOW, I thought we've got all those cool tools from you guys.
It's simple, just with a bunch of tools you can do a lot with your nbf. The pack is too big I don't think I can have it upload, but I have file names you can google.
rem If your nbf is only an OS rom, just rename it to have your nbf converted to nb Because nbf is made up of bin(sometimes known as .nb), and a OS only nbf is simply a bin file.
rem to have your os.nb splitted.
tttt\prepare_imgfs.exe os.nb -nosplit
rem extract files to dump\
tttt\viewimgfs imgfs_raw_data.bin
rem extract regisrty to edible rgu files
set _FLATRELEASEDIR=.
tttt\rgucomp.exe -o dump\default.hv -nologo > default.rgu
tttt\rgucomp.exe -o dump\user.hv -nologo > user.rgu
pause
rem below is a batch file I've to have my registy packed to hv files.
rem rgucomp.exe only convert a boot.rgu to default.hv, so you have to rename your rgu first. don't forget -b parameters
set _FLATRELEASEDIR=.
del boot.hv
ren .\default.rgu boot.rgu
tools\rgucomp.exe -b
copy boot.hv default.hv /y
ren .\boot.rgu default.rgu
ren .\user.rgu boot.rgu
tools\rgucomp.exe -b
copy boot.hv user.hv /y
ren .\boot.rgu user.rgu
del boot.hv
Pause
rem pack your dump\ to nb. If your ROM over sized the program buildimgfs.exe will crash.
tttt\buildimgfs.exe
tttt\make_imgfs.exe os.nb -nosplit
OK that's it. I only do these with my Typhoon so I don't have to convert my os.nb to nbf for RUU. But i guess you can get enough help with google. All those .exe tools mentioned above can be found through google, too. I've tried. Just search and download.
My English is not so good, please read with imagination, sorry for any inconvenience.
Ok heres the simple way.
nk.nbf -> OS.nb using typhoonnbftool (right click the OS section and dump decrypted, however under the file type, you must select 'All files' and call the file your about to dump OS.nb)
imgfsfromnb OS.nb imgfs.bin
imgfstodump imgfs.bin
Your OS has now been dumped to the 'dump floder'. Edit as you like, then recontruct using the following:
imgfsfromdump imgfs.bin imgfs.new.bin
imgfstonb imgfs.new.bin OS.nb OS.new.nb
then use nb2nbf to compile OS.new.nb back into an nbf
Easy enough
Phil
Thanks Phil ! I was pulling my hair all weekend trying to figure out how to convert nbf->nb and come monday, you answer the question. Great ! Thanks much !
PS: How much more do we have to wait for Crossbow alpha ?
It's all uploaded and ready to go on my private FTP (no waiting times or download limits ) so as soon as vlodeck unlocks the thread, i'll be posting it
Phil
jm012a9749 said:
It's all uploaded and ready to go on my private FTP (no waiting times or download limits ) so as soon as vlodeck unlocks the thread, i'll be posting it
Phil
Click to expand...
Click to collapse
think you could post it here since the thread is not unlocked yet?
vlodecks last activity was 10 minutes ago
I've PM'd him asking him to unlock the thread, PATIENCE people!
Phil
he's gone offline now
Ok, I'm back now but i dont see any link in the first post?
EDIT: I just wanted Phil to edit the first post in order to provide the link, I get it know. Thread reopened.
Go ! Go ! Go !!
Unfortunately i couldnt edit my post until you unlocked the thread vlodeck
Phil
Ohh, I see. The forum must've changed something
Ok, today is my official "I am dumb" day. I just got home and tried to load up the Imate SP5m AKU2 ROM nbf in typhoonnbftool and tried to decode it to a nb file. I do not see any area where I can 'right click on the OS and select dump selected'. I do recall that I saw it sometime on saturday night....just that I dont remember now. Can you please guide me a bit with this ? Thanks much !
Use typhoonnbftool 0.41 (attached), looks like the version you are using is 0.3, which can't read tornado nbf's properly
Phil
Hi,
I search how to dump XIP from HTC 1.34 rom.
I try to understand how to cook my rom :
- Extract RUU_Signed.nbh ok
- Extract Windows.nb to OEM/SYS folders ok
- Extract XIP, not ok...
I can't build os without XIP.
Could you help me ???
Thanks.
I have tried nbsplit/rommaster/dumprom/buildxip, but nothing... Errors errors and errors...
Could someone help me ?
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
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