Develop Bugs

ROM cooking without kitchen

Hi guys,
I'm trying to edit a Universal ROM starting from nk.nbf and I'm experiencing a problem: cooked rom starts but shows taskbar with clock working properly but the remaining part of the screen seems not to draw anything and shows welcomehead image... and does not respond to taps or keypress (only powerbutton and backlight buttons working properly)
I'm used to cook roms with kitchens, so I followed these steps:
1. decode nk.nbf > nk.nba with htc tool
2. prepare_imgfs nk.nba -nosplit
3. viewimgfs imgfs_raw_data.bin
4. deleted and modified files
5. converted default.hv and user.hv in .rgu files with RGU.exe tool
6. edited .rgu registry files:
keeping key sorted as found in extracted files
every value is headed by key (not multiple values for a single key)
HKCU in user.rgu
HKLM and HKCR in default.hv​7. converted .rgu files in .hv
the RGU.exe tool adds in user.hv the value
[KKEY_LOCAL_MACHINE\System\ObjectStore\RegistryUpdate]
"boot.rgu"=hex:79,41,C3,2D,24,BD,72,20,37,79,E7,A0,B2,A9,03,CF
How to create boot.rgu?​8. replaced registry hives in dump folder
9. buildimgfs
10. make_imgfs nk.nba -noplit
I've found in KKEY_LOCAL_MACHINE\System\ObjectStore\RegistryUpdate some references to .rgu files that are not included in the rom... should i delete all .dsm files and registry references?
Thanks all...

missing rgu have been deleted before flashing, as Leo did for his latest rom 05, so your source rom is unusable

Thanks...

OK... now the new AKU 0.7.0 is available with .rgu files builtin... but rom behaviour is the same... how to work with packages.sof?
If I move all files recreating the same directory structure of a "working" kitchen and running BuildOS.exe, shall I sort out the problem?

marco.minetti said:
OK... now the new AKU 0.7.0 is available with .rgu files builtin... but rom behaviour is the same... how to work with packages.sof?
If I move all files recreating the same directory structure of a "working" kitchen and running BuildOS.exe, shall I sort out the problem?
Click to expand...
Click to collapse
you may have look here http://forum.xda-developers.com/showthread.php?t=324682
http://forum.xda-developers.com/showthread.php?t=309562
it is a nice way to cook a ROM

Thanks...

Usual cause of a startup like you descibe is a corrupt initflashfiles.dat - have you edited it directly?
If so the first 2 bytes need to removed by a hex editor to work properly.

About Big Storage

Sorry for this thread first, but i do search a lot and i found nothing.
How to merge Exrom into storage?
I remember Bepe gave this method, and i search all his post and i found nothing.
can anyone help me, plz, thanks in advance~

Bepe big storage
yes, was much work to patch the rom that way
how to use it for othre languages? ... best way would be:
(DEV = your ROM Kitchen)
- replace DEV\ROM\OS.nb by a 0.76 OS.nb
- extract the XIP section from the 0.76 OS.nb to DEV\ROM\XIP
- delete DEV\OEM\OEMDrivers\OEM_FLASHDRV.DLL
How to do it yourself:
- nb file: 0x000001F5: short value + 0x48 (e.g: 0xA7+0x48=0xEF)
- nb file: 0x000001FB: short value + 0x48
- patch FLASHDRV.DLL inside the XIP section to validate all NAND blocks... not even sure I could do it again...
... dont know what happens if you flash a ExtROM on 0.76+... but I suppose nothing
Bye

Is there som cookers here?

In the past I cooked some ROM for my old device Trinity P3600 like this:
http://forum.xda-developers.com/showthread.php?t=367317
Now I want to buy an excalibur and i want to try to cook a ROM for this device.
is there any body with wich I can exchange ideas and experiences?
for examples. How can I extract the XIP in this device?
There is already some cooked rom for this device?

I'm tryng to port the last Vox ROM (ake 0.4.4) in the excalibur.
Some cookers come here?

Ok.
I discovered something
For extract IMGFS:
With NBHTool extract Windows.nb afther with Tadzio tool:
Code:
rename windows.nb os.nb
copy Os.nb Os.nb.payload
ImgfsFromNb os.nb.payload imgfs.bin
ImgfsToDump imgfs.bin
For extract XIP:
Code:
RomMaster os.nb -v 0 -w 5 -b 0x00217800 -x -o xip.bin
mk xip
dumprom xip.bin -5 -d XIP >NUL
Someone interested?

Cook a rom for Vox (pb : initflashfiles.dat)

Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.

fireburned said:
Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
Click to expand...
Click to collapse
have u try msflshtool

Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.

fireburned said:
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
Click to expand...
Click to collapse
usually it is in part0 or part1 ... use xipport to see which have the boot.hv & boot.rgu ... u only need those files ... around 20-40Kb files
Then u can put it in ROM folder in ur Kitchen

Thank you cruzzmz for your replies
I used XIPort to extract Windows.nb.part0/Windows.nb.part1.
I obtain this :
Code:
Windows.nb.part0
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
boot.hv
boot.hv.imageinfo.txt
ceconfig.h
ceconfig.h.imageinfo.txt
default.hv
default.hv.imageinfo.txt
initobj.dat
initobj.dat.imageinfo.txt
user.hv
user.hv.imageinfo.txt
\MODULES
busenum.dll
cecompr.dll
ceddk.dll
cereg.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
imgfs.dll
mmtimer.dll
mspart.dll
nk.exe
OMAP850_SDHC.dll
ONDisk.dll
packageinfoapi.dll
pm.dll
ramdisk.dll
rawfs.dll
regenum.dll
romfilter.dll
sdbus.dll
sdmemory.dll
serial.dll
uldrui.dll
updateapp.exe
busenum.dll.txt
cecompr.dll.txt
ceddk.dll.txt
cereg.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
imgfs.dll.txt
mmtimer.dll.txt
mspart.dll.txt
nk.exe.txt
OMAP850_SDHC.dll.txt
ONDisk.dll.txt
packageinfoapi.dll.txt
pm.dll.txt
ramdisk.dll.txt
rawfs.dll.txt
regenum.dll.txt
romfilter.dll.txt
sdbus.dll.txt
sdmemory.dll.txt
serial.dll.txt
uldrui.dll.txt
updateapp.exe.txt
Windows.nb.part1
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm.imageinfo.txt
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm.imageinfo.txt
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu.imageinfo.txt
boot.hv
boot.hv.imageinfo.txt
boot.rgu
boot.rgu.imageinfo.txt
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm.imageinfo.txt
initflashfiles.dat
initflashfiles.dat.imageinfo.txt
mxip_initdb.vol
mxip_initdb.vol.imageinfo.txt
mxip_lang.vol
mxip_lang.vol.imageinfo.txt
wince.nls
wince.nls.imageinfo.txt
\MODULES
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
busenum.dll.txt
cachefilt.dll.txt
cecompr.dll.txt
ceddk.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
fsreplxfilt.dll.txt
hd.dll.txt
HtcFsdspy.dll.txt
imgfs.dll.txt
mspart.dll.txt
nk.exe.txt
ONDisk.dll.txt
osaxst0.dll.txt
pm.dll.txt
ps2fatutil.dll.txt
regenum.dll.txt
The good files are in Windows.nb.part1 ?
Next step : copy boot.hv/boot.rgu in ROM/XIP folder ?
Thank you very much !

And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?

fireburned said:
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
Click to expand...
Click to collapse
dont think it is a problem as long as when u do buildOS u dont get any error (hint: if there is error check the temp folder open log.txt)

I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.

Help me please... I tried... But i'm blocked...

fireburned said:
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Click to expand...
Click to collapse
I dont seem to hv that file on my ROM\XIP folder, maybe u can try deleting all files inside XIP except for boot.hv & boot.rgu
then try buildOS again
BTW what is the size of both files?

I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?

fireburned said:
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
Click to expand...
Click to collapse
dunno if this can help
If you did something like the following sequence:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
Then the initflashfiles.dat should definitely be in the 'dump' folder.
Did you remember the -nosplit option for prepare_imgfs.exe?
Edit: Just a thought. The initflashfiles.dat is hidden plus the .dat extension is normally used by system files, so could it be something so simple as the fact that your explorer is not showing hidden and/or system files?
Click to expand...
Click to collapse
seems like the initflashfiles.dat is in the dump folder after u do a viewimgfs

You can put initflashfile.dat inside imgfs (for example OEM/OEM_LANG_XXX) and delete it from XIP.
Buildos.exe from Bepe search initflashfiles.dat insiede IMGFS:

cruzzmz : I tried your solution
Code:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
But, in dump folder, i haven't initflashfiles.dat
I tested several solutions, and each time, initflashfiles.dat is in my XIP folder.
cicciocant : I tried to put initflashfiles.dat in dump folder, and run PKGTool, but file is not copy to OEM_Lang_XXXX folder (missing dsm ???), and BuildOS fails, with same error.
I tested to put initflashfiles.dat in OEM_Lang_XXXX manualy, and i have an other error when i try to BuildOS : "initflashfiles.dat is a directory not a file! copying the File!!!"
In my XIP folder, i have :
Code:
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
boot.hv
boot.rgu
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
initflashfiles.dat
mxip_initdb.vol
mxip_lang.vol
wince.nls
An idea ?
And thanks for your help.

seems like my rom that i cooked doesnt have initflashfiles.dat in the XIP folder.
Maybe you can try ask around in hypercore kitchen thread

Thanks cruzzmz, i posted my question.

RELEASE: ImgfsToDump v3 (and v3.3 beta3)

Here a new version of that very important tool.
First of all, thanks to mamaich and tadzio for creating the versions before!
And also for Da_G for helping and testing with this version.
WARNING: I've added a more WM like handling of files. That might mean that some of the dump protections are not working anymore, did not try myself yet... but if the OS can read the files, why should this tool not be able to do it? :$ ... was not my intention anyway, and I really didn't try it yet.
Intention was to make the tool faster and it is now! Different algorithms and different way for decompression does the trick.
ImgfsToDump v3
Code:
ImgfsToDump.exe imgfs.bin
this does the same job as the old one, but faster
Code:
ImgfsToDump.exe os.nb
... ok, that is new ... can dump from OS.nb, OS.nb.payload with auto detection and without extracting imgfs.bin
Code:
ImgfsToDump.exe -v os.nb
-v[erbose] ... yeah, there is an option now to simulate and so to only show file names on screen
Code:
ImgfsToDump.exe -w *.mui os.nb
-w[wildcard] ... most useful part I think... this will only extract all the mui files from the ROM
Code:
ImgfsToDump.exe -v -w flashlite.dll os.nb
this is useful for quickly check if a rom contains a specific file.. it will only show the result on the screen if the file exists, but not dump the file
Also added some bat files that work with drag and drop... just drag an os.nb and drop it onto one of the bat files
Code:
Wildcard: *.cpl
IMGFSTODUMP 3 Copyright (c) 2009-2010 bepe Oct 16 2009 14:07:12
cplmain.cpl
historyui.cpl
ipsecvpnui.cpl
MyPhoneLauncher.cpl
AGPSSettingsCPL.cpl
ConnectionSetup.cpl
TaskManager.cpl
MyCpl.cpl
Done!
ImgfsToDump v3.1 Beta
ADD: It's working with packages now, check out the bat files
FIX: Wildcards ignore case now
ADD: New option: [-build] extract files into packages
ADD: New option: [-type <OEM|SYS>] extract only SYS or OEM packages
ADD: New option: [-pkgwildcard <wildcard>] Wildcard for filtering packages
Code:
ImgfsToDump.exe -b os.nb
- Extract into packages
Code:
ImgfsToDump.exe -b -t OEM os.nb
- Extract only OEM packages
Code:
ImgfsToDump.exe -b -t OEM -p *adobe* os.nb
- Extract only OEM packages that contain 'adobe' in the package name
ImgfsToDump v3.2 Beta
ADD: HTC NBH support
ADD: New Layer system
REMOVED: -l -n option
ADD: XIP extraction .... don't tell me that the exe name is not fitting anymore :$
ADD: OS version and build output (only if you are building packages and only with .nbh .nb .xip)
ADD: Some Device information (only for .nbh .nb)
ImgfsToDump v3.2 Beta 2
ADD: Emulator ROM Support
ADD: options for XIP and IMGFS... IMPORTANT: allmost all options have been changed!
ImgfsToDump v3.3 Beta 2
FIX: XIP modules are working now
ADD: Extract compressed XIP sections
ImgfsToDump v3.3 Beta 3
ADD: LZX working now
xidump v1.0 Beta
ADD: Fix for invalid OEM certs
best regards
bepe

Great update bepe, thanks!

Thanks bepe.

As always, great work bepe. Testing now...

very nice !!!
Thanks bro
Tom

Sounds good, thanks bepe

Thanks Bepe again. Is it compatible with your platform builder?

Wow cool
Speed is actually what we need when got a new 200+ Official ROMIMAGE

Thanks bepe for the update

nice
very nice !!!thx

Thank you to share

awesome!
thanks bepe

nice update
thanks

I‘m a chinese ,and thank's for your software .

wonderful Bepe. many thanx.

Nice work！ ths

Great update bepe, thanks!

new Beta
A bit early... but here is a new version to try.
It's still a beta, but has some new options for building packages.

thanks again bepe
i will give it a try as well.
EDIT: the tool works fine, but don't you think you need to add "/D" switch in the batch files here
Code:
cd /D %path_arg%

Grest tools, thanks