yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam ROM Development] neogin:
Tadzio Tadzio Tadzio !!! RULE ...............

Tadzio, by doing that .. (thru NBInfo) .. do i still get extra storage ??

i'm interested in your super storage .....

PS... if this work with benq p51 .. it will work with atom family and asus p525, p526, p535, etc .. i'll help u to make this happen !!!!

*******************************************

MSFLSH50 header found at offset 0x1b88

(0 Reserved Entries, 0 Flash Region Entries)

Searching for IMGFS signature...

Found IMGFS at byte 0x00600000 (sector 0x00600000).

dwFSVersion: 00000001

dwSectorsPerHeaderBlock: 00000001

dwRunsPerFileHeader: 00000001

dwBytesPerHeader: 00000034

dwChunksPerSector: 00000040

dwFirstHeaderBlockOffset: 00001000

dwDataBlockSize: 00001000

szCompressionType: XPR

dwFreeSectorCount: 00000DA2

dwHiddenSectorCount: 00000020

dwUpdateModeFlag: 00000000

---

what next ??
[8525, TyTN, MDA Vario II, JasJam ROM Development] wailoon:
any HTC Softbank X01HT owner try this?

seriously i really don't know how to run, can teach me the steps?
[8525, TyTN, MDA Vario II, JasJam ROM Development] Old Kind MadMike:
And I have the same question about my device. I use one of the Atom Exec clones and your utilities doesn't work correct on it's ROM.

How can I get these sizes?
[8525, TyTN, MDA Vario II, JasJam ROM Development] bla0ck:
Sorry I'm getting into it like this =) Tadzio, thank you for all your work.

I have some comments about previous and this version of your's tool concerning wm6 emulator images. Maybe you'll take these into account and return -emu option, at least for nbsplit.

I was able to dump wm6 USA and JPN images with previous tool as follows

nbsplit -emu image.bin

imgfsfromnb ... 1.bin

imgfstodumb 1.bin

You have removed -emu option from this release, and have said that it didn't work. And tool now unable to dump such images. But it's still possible to create dump from 1.bin file.
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
Hi, i just used tadzios Toolchain to dump a Hermes ROM, remove and replace some files, and then rebuild the ROM with the bigstorage-tools.

Worked fine. No problems, but how can i change registry settings from ROM dump, i only want to change some Regkeys and thats all. Can somebody help me. A year ago i used duttys RomKoch 0.9 for editing a ROM, but this doesn't work anymore with new ROMs.:confused:
[8525, TyTN, MDA Vario II, JasJam ROM Development] jiggs:
If the device uses DOC storage like ours XDA Atom, BenQ P51, Rover, Atom Exec, etc. it can't enjoy the big storage. Same for Wizard, Herald, etc.
[8525, TyTN, MDA Vario II, JasJam ROM Development] jiggs:
it's here: http://buzzdev.net/read.php?26,27196 you can read the section on registry editing tools.

cheers
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
Thanks very much, I read the wiki and the forum about cooking and editing registry, but it was very confusing (REGEDIT4, rgu, initflashfiles, user.hv,...).

Always a big :confused: inside my head, but this Link is rookie-friendly.:)

There I found a imgfsBAT.rar which inserts automaticly REGEDIT4 to the file.

What are you using to make the regediting easier? Is another (better) tool available for this?

EDIT: made a boot.rgu file and edited it and saved as unicode file.

made boot.hv of this boot.rgu, but where shall I copy the the boot.hv to? Into dump-directory?

Isn't it possible to recompile the boot.rgu to a new user.hv directly and copy and overwrite it in dump directory and rebuid the nb-file with tadzios chain (with new edited user.hv)?

why is boot.hv only 32kb and user.hv 72kb size? I only made minor changes and added REGEDIT4 and a free line at the end of boot.rgu. Please help, i'm a little confused. The link posted describes everything till boot.hv, but nowhere to read what to do then with it.
[8525, TyTN, MDA Vario II, JasJam ROM Development] scorpio16v:
Some help for you.

The initflashfiles.dat contains the folder structure of your ROM. You can edit it with a texteditor.

To edit the user.hv, that contains the registry entries for HKCR and HKLM you can try the attached tool.

It's a combination of the tools found at buzzdev.net.

Simply put the default.hv in this folder, run the DEFAULT.bat, edit the produced boot.rgu and press the "space-key".

Now the new boot.hv must be renamed to user.hv and can be replaced in your DUMP folder.

Now you can cook your new ROM with the edited registry entries. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
thank you very much scorpio16v! :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] scorpio16v:
No, not me, it´s jiggs work. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
hi, tried to edit the default.hv or user.hv with the edit_hv tool.

Everytime I run the bat-file with the default.hv (or user.hv), edit the boot.rgu (save as Unicode in Editor and do not add REGEDIT4 because this does the bat), press space to rebuid the new default.HV i everytime get a new default.HV file which is 28kb size. If i run the process with this new hv there is nothing inside the rgu. What am i doing false.

In the directory is the unzipped tool (posted by scorpio16v) and the default.hv (or user.hv renamed to default.hv for the bat file). Editor is normal Windows Editor (Notepad). :confused:

EDIT: Solved! Notepad doesn't save in correct Unicode format. So i edited with Notepad and saved as ANSI file, then ran the boot.rgu with through ansi2unicode.exe. Then it was possible to build a working user.hv or default.hv
[8525, TyTN, MDA Vario II, JasJam ROM Development] vivi:
I found this error,what is it?

vivi
[8525, TyTN, MDA Vario II, JasJam ROM Development] ivanmmj:
DOC Storage

You mentioned that you thought that the Herald had DOC storage so that it was not possible to use this tool to get a BigStorage setup.

I'm wondering about this and about merging the main storage with the extended_ROM. I was hoping it would be possible for the Herald before I attempted to figure out how.

EDIT: OK, I found this on the DiskOnChip system... off I go to read the PDF within it...
[8525, TyTN, MDA Vario II, JasJam ROM Development] futureshock:
Hi, how can we find out the chunk sizes for HTC Breeze / MteoR ?!?!
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
Extended Rom

Hi Tadzio,

I have tried to build an upgrade for the dopod d810 (trinity) using your tools, but I seem to loose the extended ROM each time. I only modified the OS.nb and would like to retain the original extended ROM, as it contains all the other specific customization.

Is it your tools that caused this? If so, how would I not loose the ext_rom?

thanks for wonderful set of tools.

TJ
[8525, TyTN, MDA Vario II, JasJam ROM Development] andrew_green:
I'm not Tadzio (obviously) but it seems the ExtROM is not being recompiled back into your nbh (sorry if it's nbf or something else) file you're flashing. How are you re-incorporating OS.nb?
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
That would surprise me. The ImgFs tools are quite defensive when it comes to changing the partition table.

Try running NBInfo over your new os.nb, and compare the partition table with your original ROM.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] ivanmmj:
Make sure you didn't change the "CheckAutoRun.exe" file.
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
Thanks andrew_green for your reply... I am using ervius version of buildOS (a variation of bepe's buildOS) to build HTC Trinity OS.nb.

When I ask ervius about it, this is his reply:

I don't understand what he meant by it because I have check the tadzio tools readme.txt and command line parameters, but I could not find any option to kill extended_ROM.

btw, I use Dutty's NBH tool to reconstruction NBH, and here is the extracted content from my new NBH file (ext_ROM included):

I have attached the nbinfo result: old.txt (before tadzio) and new.txt (tadzio applied).

I only ported the new \SYS files from htc universal. No changes are made to CheckAutoRun since I want the original extended ROM.
[8525, TyTN, MDA Vario II, JasJam ROM Development] kin0kin:
I'm not sure if this is the right place to ask.....after dumping the extended rom using itsutils with the following parameter:

pdocread -w -d ext_fla -p PART00 0 0xa00000 PART00.raw

I renamed Part00.raw to 01_ExtRom.nb....however when I try to extract extended rom, extended rom extractor gave me an error..and if I flash the extended rom...it says image is corrupted. I must be missing something, does anyone in this thread know what could be it? thanks in advance
[8525, TyTN, MDA Vario II, JasJam ROM Development] thierryb:
XDA Flame

Hi tadzio

I would like to find the data and extra option for the XDA Flame.

I have read one of your answers telling that you need these infos :

MSFLSH50 header found at offset 0x2178

(0 Reserved Entries, 0 Flash Region Entries)

Searching for IMGFS signature...

Found IMGFS at byte 0x00a40000 (sector 0x00a40000).

dwFSVersion: 00000001

dwSectorsPerHeaderBlock: 00000001

dwRunsPerFileHeader: 00000001

dwBytesPerHeader: 00000034

dwChunksPerSector: 00000040

dwFirstHeaderBlockOffset: 00001000

dwDataBlockSize: 00001000

szCompressionType: LZX

dwFreeSectorCount: 000006DF

dwHiddenSectorCount: 00000020

dwUpdateModeFlag: 00000000

Hope you can help me.
[8525, TyTN, MDA Vario II, JasJam ROM Development] chaimd:
Hi, tadzio;

Thank you for your great job. I'm using your tools with Cheetah and Kaiser. :)

I have XDA Flame. I'm using prepare_imgfs.exe and make_image.exe. These work with Flame ROM. I've checked SD update file that was rewrited by RAW ImgFS from pdocread.exe -w -b 0x1000.

But I have a problem to build RAW ImgFS. I can't finish to build ImgFS from dump with neither buildImgFs.exe nor ImgfsFromDump.exe. Flame's DataBlockSize is 0x1000. It's different from Hermes(0x200) or Kaiser(0x800).
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
If it's a problem with the data block size (chunk size), use NBMerge with the -data and -extra parameters, where you can directly specify the size.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] chaimd:
Thank you, tadzio;

I replace a ImgFs template from Flame into Kaiser. Then, ImgfsFromDump work completely! And I can flash Flame with a cooked ROM, now! :)

Official Flame's ImgFS uses LZX compression, but Kaiser's one uses XPR. There may be LZX compression. But I can avoid the problem, using XPR template, now.

Thank you, tadzio. Your tools are great! :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
Hi tadzio,

i often use your tool for hermes and always working well.

Now i have HTC Athena, and i wanted to make a ROM dump, do a little mods in ROM, nd rebuild with your toolchain.

So nbh to nb with nbhtool and then dumped with your tools. Got dump-directory and everything seems fine, but when i rebuild the dump to nb i get an error.

========================================================

.......

Processing "xls2pxl.dll" as file

Processing "xmeevtsnd.dll" as module

Processing "ZipView.exe" as file

Processing "zlib.dll" as module

Processing "zoom.bmp" as file

Total Sectors: 0x1f399

ImgfsToNb 2.1rc2

Using bigstorage mode

Sector size is 0x200 bytes

Writing imgfs to offset byte 0x680000, sector 0x3400

Padding ImgFs from 0x3e73200 bytes (0x1f399 sectors)

to 0x3e80000 bytes (0x1f400 sectors)

Not conservative mode. Changing imgfsEnd from 0x4e00000 to 0x4500000

Partition entry before:

File System: 0x25

Start Sector: 0x00003400

Total Sectors: 0x00023c00

Boot indicator: 0x00

First Head: 0x00

First Sector: 0x01

First Track: 0x34

Last Head: 0xff

Last Sector: 0x01

Last Track: 0x26f

Partition entry after:

File System: 0x25

Start Sector: 0x00003400

Total Sectors: 0x0001f400

Boot indicator: 0x00

First Head: 0x00

First Sector: 0x01

First Track: 0x68

Last Head: 0x7f

Last Sector: 0x01

Last Track: 0x4f

ImgFs Flash Region log blocks was 0x478, now is 0x3e8

No Storage Flash Region found!

Done!

======================================================

In commandline i type (like hermes, but without nbmerge):

D:\ImgfsToolsA\ImgfsFromDump.exe D:\ImgfsToolsA\imgfs.bin imgfs-new.bin

ren imgfs.bin imgfs.binX

D:\ImgfsToolsA\ImgfsToNb.exe D:\ImgfsToolsA\imgfs-new.bin D:\ImgfsToolsA\Windows.nb.payload Windows-new.nb.payload

del D:\ImgfsToolsA\imgfs-new.bin

ren Windows-new.nb.payload Windows-new.nb

ren imgfs.binX imgfs.bin

I get this Windows-new.nb, but if i run OSchecker it tells me not safe, will make bad blocks, also 10MB smaller than original .nb-file (?)

Am I doing something wrong?

The error seems to be in this step ImgfsToNb.exe.

Can somebody help please, i like this tool very much!
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
No, I don't think so. The line "No Storage Flash Region found!" just tells you that your ROM doesn't seem to have a Storage partition (i.e., Storage is not handled by the MSFLSH driver, but probably by a DOC driver). That means the memory saved in the ImgFs partition cannot be added to your Storage.

Also, the ROM is now intentionally smaller - this allows BigStorage on supported devices.

I am not sure why your OSchecker reports bad blocks, but you may want to try the -conservative command line parameter (see ImgFs tools documentation). This parameter will make sure the resulting ROM has the same size as the original ROM, which should make your OSchecker happy.

Happy New Year

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
Hi tadzio,

now i rebuild with conservative mode, and now these blocks are same size, but still message: No Storage Flash Region found!

OSChecker.exe says still will lead to bad blocks, invalid file.

if i rebuild nb to nbh with nbhtool then i get a nbh file which is 300kb bigger than original.

What can happen if i flash this nbh?
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
Again, this is not an error message. It just tells you that your original ROM does not contain a Storage partition controlled by the MSFLSH driver. This is perfectly normal for all devices that have a DOC Storage area.

I don't know OSchecker. But if I were you, I wouldn't flash the resulting ROM before you understand what exactly makes OSchecker unhappy.

Happy New Year

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] ivanmmj:
I'm able to rebuild the OS and it WILL flash, but unfortunately, I have to pad it to the 51,200kb limit that the RUU flasher requires and I end up with getting the exact space I would get free if I had flashed a nb with a real 51,200kb worth of data. It seems that the Herald reformat its storage only during a RUU flash (we also have aserg's way but that doesn't touch formatting) and that the RUU limit is the one that stops us from gaining from this program. Even though it is DOC storage. How is everyone here flashing the ROMs that you make with these tools?

EDIT: I'm using HTC ROM Tool 1.0 to create my NBH's, not 1.1 and I haven't tried using NBHGen. But that doesn't bypass the 51,200kb limit imposed by the flasher.
[8525, TyTN, MDA Vario II, JasJam ROM Development] neogin:
hey hey long time no see .. Tadzio,

i wonder .. DOC chip still can't use your tool up until now, right ??
[8525, TyTN, MDA Vario II, JasJam ROM Development] neogin:
i wonder .. what

this

work ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
That is true.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] mickey-r:
I get wm6 acer n311 rom by football and i want translate it according

to thid thread : http://xdaforums.com/showthread.php?t=311078.

I get imgfstools 2.1rc2 and i saw that the nbsplit have -acer key but

it don't work with flash.dio.

Anybody can explain to me how to have .nb file from .dio file
[8525, TyTN, MDA Vario II, JasJam ROM Development] hwpeter:
for Trinity?

Can I ask what is the command lines for Trinity?

Thank you in advance
[8525, TyTN, MDA Vario II, JasJam ROM Development] ivanmmj:
Anyone have any clue about this one?
[8525, TyTN, MDA Vario II, JasJam ROM Development] cyron_at:
I am also interested in the command line parameters for the trinity....

Thx!
[8525, TyTN, MDA Vario II, JasJam ROM Development] epimazzo:
Tadzio,

Which page did you write this Herald/Wizard procedure? Didn't find here actually...

Thanks for your help.;)
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
Just two posts above the one you quoted - #238 in this thread.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] ivanmmj:
The herald can also get a large storage from this, but the RUU flasher limits us by giving us a 51.2mb requirement. I'm not sure about the Wizard.
[8525, TyTN, MDA Vario II, JasJam ROM Development] wparkx:
Hi tadzio

Could you tell me how to create bigstorage rom for TITAN offcial Rom? i need your help.
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
Sorry, but I never worked with a Titan.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] flaviopac:
Is there any apps like these for HTC Touch??

:confused:
[8525, TyTN, MDA Vario II, JasJam ROM Development] Neil4711:
Can use for Chinese ROM??.
[8525, TyTN, MDA Vario II, JasJam ROM Development] cnbenson:
I have just bought a IPAQ 614c. I want to translate the ROM to CHS. But I have nothing except part02.raw now.

Can the imgfstool be used in this way?

RAW--DUMP--RAW? or

RAW--DUMP--kitchen-RAW?

Thanks a lot!
[8525, TyTN, MDA Vario II, JasJam ROM Development] k101d:
Thanks Tadzio,

Your job very impressive, I just only use your batch file (NBDumpHermes and NBBuildHermes) it make me very happy to customize the rom for Treo 750 its work.

So can you make another easy way like this for the process off add cab file to the dump rom before re build with NBBuild...

Thanks again.

k101d
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
I stopped working on these tools some time ago, sorry.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] lennysh:
NBSplit.exe

How do I figure out how to exactly use the nbsplit.exe -data -extra commands? Where can I get the information to fill in behind those params? The ROM I'm trying to use it on doesn't already have it's own switch.
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
I was wondering the same thing. Earlier in the thread (see post 255) tadzio writes that the nbinfo results can be useful in determining the needed -data and -extra switch/command settings, particularly the part in the nbinfo results following the line:

"MSFLSH50 header found at offset"

This question doesn't seem to be followed up on anywhere in the thread.

How do we determine the switch settings needed, if any, by the nbinfo results?

I've tried -titan, -hermes, -kaiser switches, as well as not using nbsplit at all and just copying os.nb to os.nb.payload with poor results at the dump. I end up with a 900 kb dump file. I'm a noob for sure, and maybe I'm missing something else here completely. Any help would be greatly appreciated. I've got an ipaq hx4700 and using pdaviet wm6 rom. I'm stripping the an .nbf file using a hexeditor to get an .nb file and then using tadzio's tools.

My nbinfo results after "MSFLSH50 header found at offset" are:

MSFLSH50 header found at offset 0x200
(0 Reserved Entries, 3 Flash Region Entries)

Flash Region Entry 0:
---------------------
Region type: XIP
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000012
Size in log. blocks: 0x00000000 -> Size in sectors: 0x00000000
Sectors per block: 0x00000200
Bytes per block: 0x00040000
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200

Flash Region Entry 1:
---------------------
Region type: READONLY_FILESYS
Start phys. block: 0x00000012
Size in phys. blocks: 0x00000091
Size in log. blocks: 0x00000000 -> Size in sectors: 0x00000000
Sectors per block: 0x000001f8
Bytes per block: 0x00040000
Compact blocks: 0x00000002
-> Bytes per sector: 0x00000208

Flash Region Entry 2:
---------------------
Region type: FILESYS
Start phys. block: 0x000000a3
Size in phys. blocks: 0x00000157
Size in log. blocks: 0x00000000 -> Size in sectors: 0x00000000
Sectors per block: 0x000001f8
Bytes per block: 0x00040000
Compact blocks: 0x00000002
-> Bytes per sector: 0x00000208

Searching for IMGFS signature...
Found IMGFS at byte 0x00500000 (sector 0x00002800).

dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: LZX
dwFreeSectorCount: 0002D9E5
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
---
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
Then "data" is 0x200, "extra" is 0. However, since "extra" is 0, running nbsplit will do nothing.

Cheers

tadzio
[8525, TyTN, MDA Vario II, JasJam ROM Development] :
That was quick. Thanks tadzio.

Any idea why I'm ending up with a 900kb dump file? These are the steps I took and errors:

1. used imgfsfromnb.exe on os.nb.payload resulting in a 35mb imgfs.bin file with the following reported:

Sector size is 0x200 bytes

ImgFs partition starts at 0x00480000 and ends at 0x027b1000

Dumping IMGFS at offset 0x00500000 (size 0x022b1000)

Done!

2. used imgfstodump.exe on imgfs.bin file resulting in a 900kb dump file with many errors including some reading:

Cannot create ahioem.dll\imageinfo.bin

Unhandled exception in DumpImageData!!!

Unhandled exception in DumpXipData!!!

Error! Cannot map dump\ahioem.dll\imageinfo.bin

unknown header type, fs_data_table??

Thanks for any help.
[8525, TyTN, MDA Vario II, JasJam ROM Development] tadzio:
No idea, sorry.

Cheers

tadzio