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
SYS PORTING GUIDE
Special thanks goes to Monsterfly for helpful guidance on porting SYS to a new build
Inventory:
Tools you will need for porting the SYS
BuildOS+Package Tool by Ervius
G’Reloc Tool by Misar
Procedure:
Use BuildOS+Package tool to dump ORIGINAL ROM and build packages
Copy G'Reloc to the folder where you have original SYS folder
Run it and write down numbers under slot 0, slot 1 and size of rom
Use BuildOS+Package tool again to dump DONOR ROM and build packages
Replace your original SYS folder with Donor's SYS
Run G'Reloc again
Notice that this time numbers under slot 0, slot 1 and size of rom may be different
Just replace them with numbers you got in the firt step
Click »Doit!« and wait till it shows "Done" in the status bar
Use the OEM folder in which you have added ingredients and the XIP fodler that you ported
Info: In some cases you will need to copy WinCENLS_WWE folder to SYS folder (if not present in Donor's SYS) from your original ElfIn SYS otherwise your device will not boot
Build OS in the kitchen of your choice and flash the new build ROM to your device and HAPPY COOKING
Timebomb solution and the boxed closed / ok button solution found here by HTCTouchp
[POLL][REF]*XIP & SYS Porting Guide*[ONLINE]
XIP Porting Guide (Based on Bepe's Buildxip.exe tool)
More detailed Porting guide on manual XIP Porting can be found here
I have added pictorials in .pdf format at the end of this post. Too many pictures so the .pdf file
Special thanks goes to Ervius for a lot of helpful guidance on porting XIP to a new build
Inventory:
Tools you will need for porting the XIP
BuildOS+Package Tool by Ervius
XIPPort Tool by Bepe
M’Reloc Tool by Misar
Procedure:
To make life more simple, I am attaching the XIP.bin extracted from Kaiser 19209 build ROM by Ervius. Dump the XIP.bin file with XIPPort tool and choose to make packages. Download from here (Rapidshare Folder)
In the OUT folder, ignore or delete all the text files (.txt) These files are created by XIPPort tool only to know the physical addresses and are not required for porting
In files and modules folders, delete all folders except “MSXIPKernel” and “MSXIPKernelTLK” The modules and files from these folders are the only items which are to be ported to make a new build. DO NOT copy or replace any files and modules from OEMXIPKernel, as these are device specific
Now open the BuildOS+Package tool and on packaging page click open with option to choose dump folder. Select your original ElfIn XIP folder (OS 19199) and on right you will see the XIP in its directory structure. Don’t click on build packages (you can’t do it anyways, as package.sof file is not present in the XIP folder) Instead click on “OEMXIPKernel” and then right click to select export package. Choose to save on different location, like your desktop. This is only temporary requirement, just to be on safe side that you still don’t replace any files or modules seen in that folder
Now you copy and replace the files and modules seen in the “MSXIPKernel” and “MSXIPKernelTLK” from the new XIP in your original XIP folder, you need to copy and replace only those items found in your original folders, do not add anything new. Now compare each and every .rgu file from your new XIP with your original XIP and check if they are similar (NOT the .rgu files in “OEMXIPKernel”)
After all the files and modules are replaced and .rgu files checked, run the M’Reloc tool and check the modules addresses from your original XIP with your new XIP (Don’t do anything to the modules located in “OEMXIPKernel”) The addresses have to be similar to your original modules from your original “MSXIPKernel” and “MSXIPKernelTLK” folders
Changing of addresses through M’Reloc is not required if you are using the BuildOS+Package tool for cooking ROMs as Ervius has already included the address relocation system into his tool with BuildXIP
In a nutshell you need to follow the following copying & replacement structure and everything will work:
Original XIP (19199): OEMXIPKernel
Donor XIP (19209): MSXIPKernel and MSXIPKernelTLK
Replace this new XIP folder in ROM in Bepe's WM6.1 Elfin kitchen and cook to get 19209 Build XIP, HAPPY COOKING
I have managed to put together a clean Base WM6.1 ROM for Elfin (Touch XL - 128/256) with almost everything removed except the most essential system packages
Please take note, this is a base rom for cooking and not to be directly flashed on the device as it may be unusable. You need to populate the ROM with your choice of packages and the essentials to bring it up to the 50MB limit for making it usable
Link to download the dumped Removed packages: Here
Special thanks to
Bepe for his wonderful kitchen
Noonski for his valuable comments and suggestion all the way
Kokotas for his help in getting rid of the cube
Download Bepe's WM6.1 Kitchen for ElfIn and replace the OEM and SYS folders with yours and cook the OS.nb file
The archived OEM package (dumped and packaged) can be downloaded here
DOWNLOAD HERE (V1)
UPDATE
DOWNLOAD HERE (V2) (Further stripped down OEMApps & OEM_Lang_0409)
20296 MSXIPKERNEL. Mix this with OEMXIPKERNEL and you are ready to cook. Do M'relocing if necessary
Download here: View attachment 108115
SYS archieve
A. The archived SYS package 19199 buid. DOWNLOAD HERE
Stripped to down basic required
B. SYS ported from 19209 Build. DOWNLOAD HERE (Rapidshare Folder) This archieve is from my new ROM (XIP and SYS Ported to new build) Removed packages as per above ist
C. 19588 Build ROM Dump (OEM, SYS & XIP) DOWNLOAD HERE. Thanks to Koko for sharing this archieve (SYS, OEM & XIP)
Hi Abrabekar,
You really came in the right time! I'm about to remove all the unnecessary apps inside Elfin original ROM and now you came with WM6.1
You really save my time, many thanks to you!
Cheers,
Vibranze
Deleted! Double post.
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
JohnQ said:
well im just waiting for another version wm6.1 ROM for elfin~at least after swiftblade and couldyfa's~ any updated wm6.1 ROM for elfin is welcome! `cheers~
Click to expand...
Click to collapse
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
ababrekar said:
@JohnQ.. this is not an upgrade to swiftblade's or cloudyfa's wonderful roms but just a clean base rom for everyone to cook have more personalised options
Click to expand...
Click to collapse
vibranze said:
Hi Ababrekar,
Yeah, but how I supposed to populate the SYS and OEM folder? Or to be precised, how should I continue from your OS.nb file?
Cheers,
Vibranze
Click to expand...
Click to collapse
you need to populate the rom by adding your choice of packages. the essentials out the removed list would be phone dialer, commanager, bluetooth, netcf, audio manager. also you need to add files so the final cooked os.nb file is above 50mb limit
Don't Mind Vibranze he allready is running his own Rom...
Noonski said:
Don't Mind Vibranze he allready is running his own Rom...
Click to expand...
Click to collapse
i was answering his questions coz no question should go unanswered in my thread
I think it would be a good idea to post which kitchen you advice to cook the nb in.
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
canadian student said:
I was wondering if there is a WM 6.1 Rom with nothing extra added. Just like an original HTC ROM? Like with no accessories folder, or HTC Action screen etc. I really don't like any of that stuff. I really only wanted WM 6.1 for the threaded sms.
Thanks in advance
Click to expand...
Click to collapse
as i said, this is a bare naked base rom with all the packages removed for maximum user customisation. the packages removed are listed in my first post here
Noonski said:
I think it would be a good idea to post which kitchen you advice to cook the nb in.
Click to expand...
Click to collapse
good suggestion, like always brother i have updated the first post at the last line guiding to bepe's kitchen for cooking the nb file
(although i need bepe's or your guidance on how to get the exact same contents of his ROM folder from my ROM which can help everyone in achieving more customisation)
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Noonski said:
Well i've been working a month on SuperCore now but it now contains Packages for almost everything you have removed.
Looked up most of the registry settings for removed items to.
Generated new .dsm files and made option.xml for each.
And i still need to make registry keys to make removed controlpanel items work from SD.
So now i can wait another month before uploading new SuperProCore.
Now if somone could tell me how to make a os.nb.payload for ELF only with 4MB pp poeple would really be happy.
Click to expand...
Click to collapse
even i'm looking for a way to get the exact contents of ROM folder what Bepe has in his kitchen for ElfIn. It contains XIP with a lot of other files. I wonder if having the os.nb.payload from my own rom would help rather than using bepe's file still waiting for a guidance
i am attaching the default.hv & user.hv files with the reg entries deleted as per the removed packages list. see if you can check and comment on it, it will be great
eagerly waiting for SuProCore
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Noonski said:
Most of the keys are double ussually.
So you'll find the same keys also in SYS and OEm .rgu files as in hives files.
Click to expand...
Click to collapse
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
ababrekar said:
oh ok. so to completely remove the removed package list from the rom, i will have to also edit the .rgu files found in oem & sys?
Click to expand...
Click to collapse
Naah you really don't need to.
Those left behind registry settings ussually don't do any harm without the files present.
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
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
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
ciko84xp said:
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
Click to expand...
Click to collapse
I can't help you either ... try to PM one of the Chef you knew from the forum.
ciko84xp said:
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Click to expand...
Click to collapse
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
parleyp said:
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
Click to expand...
Click to collapse
I downloaded this "RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship", which should be the Official HTC ROM for TYTN II (my device), but I have the same errors described in the first post using the BEPE's kitchen!
What do you mean by "You will have to get a base from a chef?
I do not believe that any chef would give me his base, should give me the entire folder containing the kitchen built! Or not?
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
I am having the same issue with Bepes kitchen - I have the official signed rom from Sprint for the Mogul and every time I try to use dump_800.bat on the OS.nb file, it fails and says access is denied...
ciko84xp said:
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
Click to expand...
Click to collapse
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
DaveShaw said:
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
Click to expand...
Click to collapse
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
ciko84xp said:
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
Click to expand...
Click to collapse
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
DaveShaw said:
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
Click to expand...
Click to collapse
ok Dave.. I follow your advice! then you story if I have made progress ...! thanks!