706 replies to this topic

[wes58]

mediacell, on Jan 24 2010, 03:09, said:

how to edit this file, i just delete offset 18h~1Fh, but extreloc still not recgnize this file.

If you are using my application it does it when you dump the rom.

[mediacell]

wes58, on Jan 24 2010, 05:03, said:

If you are using my application it does it when you dump the rom.

so, we dont need to deleted 18-1Fh?

[wes58]

mediacell, on Jan 24 2010, 05:29, said:

so, we dont need to deleted 18-1Fh?

That's correct, you don't have to do anything. You can check the size of the imageinfo.bin in sys\.rom folder. It should be 36 bytes long - that's the file size that is required for extreloc to recognize the rom as 6.5. Original file was 44 bytes long

[aol1978]

please attach pictures of how you cook a rom to guide more
thank you very grateful

[Tylwith]

i have followed all the step but even if i don't modify the rom after flash my phone stay stuck at the orange windows screen.
the other think the new packed rom have a different size from the original with only dump and buid

[powser]

A lot of times "Stuck on  boot screen" is because no relocation has been done ( my own experience, not using wes58 tools). maybe you could check extreloc since it seems to be part of the package?


I'd like to thank wes58 for creating a nice kitchen although I haven't used it.. It would've made my cooking much easier last time if i had it....

[Gary Crutcher]

@Wes58

I am getting the same error as a few others when building the ROM:

imgfs-new.bin not Found

You mentioned spaces in the folder paths.
I noticed when I unrar the kitchen it creates a folder: Finished ROM
Notice the space after 'Finished'

Could this be a problem?

[wes58]

Gary Crutcher, on Jan 27 2010, 03:54, said:

@Wes58

I am getting the same error as a few others when building the ROM:

imgfs-new.bin not Found

You mentioned spaces in the folder paths.
I noticed when I unrar the kitchen it creates a folder: Finished ROM
Notice the space after 'Finished'

Could this be a problem?

No, it's definitely not this one. It's strange because I tried putting kitchen root folder in different locations and never had a problem. What operating system have you got on you computer?

The other thing that you can check is if buildOS was successful. You should have a buildOs log in temp folder, you should have there also dump folder with all the files created by buildOs. Also you can check if you have imgfs-new.bin in temp folder.
After you finishe BuildOs, there is a Dos window minimized on the toolbar. You could open it and see if imgfsFromdump is running. You should see files being shown in the dos window.

Let me know what you find.

[Gary Crutcher]

wes58, on Jan 27 2010, 14:54, said:

No, it's definitely not this one. It's strange because I tried putting kitchen root folder in different locations and never had a problem. What operating system have you got on you computer?

The other thing that you can check is if buildOS was successful. You should have a buildOs log in temp folder, you should have there also dump folder with all the files created by buildOs. Also you can check if you have imgfs-new.bin in temp folder.
After you finishe BuildOs, there is a Dos window minimized on the toolbar. You could open it and see if imgfsFromdump is running. You should see files being shown in the dos window.

Let me know what you find.

I am using Windows 7.
I am using pda.bin (I8000xxxJA5) dump from sorg's utility.
I am using your RomTool1.2B.

The dump works ok. No errors

I then click on the Build ROM tab.
I leave everything as it is, then click Build.
The BuildOS window opens. I click play...and wait.
SYS and OEM folders are created and have data in them.
After BuildOS is complete there is NO DOS window minimized.

The temp dir has the following:
dump folder with many files
boot.hv
boot.rgu
log.txt

No imgfs-new.bin
No buildos.log

I then click File | Exit the BuildOS window.

ExtReloc opens...I close it.

Process ends with error: imgfs-new.bin not Found

Hope this helps.

[wes58]

Gary Crutcher, on Jan 27 2010, 08:21, said:

I am using Windows 7.
I am using pda.bin (I8000xxxJA5) dump from sorg's utility.
I am using your RomTool1.2B.

The dump works ok. No errors

I then click on the Build ROM tab.
I leave everything as it is, then click Build.
The BuildOS window opens. I click play...and wait.
SYS and OEM folders are created and have data in them.
After BuildOS is complete there is NO DOS window minimized.

The temp dir has the following:
dump folder with many files
boot.hv
boot.rgu
log.txt

No imgfs-new.bin
No buildos.log

I then click File | Exit the BuildOS window.

ExtReloc opens...I close it.

Process ends with error: imgfs-new.bin not Found

Hope this helps.

Sorry, The Dos minimized windows should appear after you close extReloc. I am using windows 7 as well. Buildos log is the log.txt file that you have. when you open it you should see at the end something like rgucomp done. I will send you a link to the file which will have dos window pop up all the time.

[Gary Crutcher]

wes58, on Jan 27 2010, 16:29, said:

Sorry, The Dos minimized windows should appear after you close extReloc. I am using windows 7 as well. Buildos log is the log.txt file that you have. when you open it you should see at the end something like rgucomp done. I will send you a link to the file which will have dos window pop up all the time.

Ok. Thanks

[Gary Crutcher]

@Wes58

Same problem: no imgfs-new.bin
No DOS windows staying open either.

I also tried under Vista with same error.

Maybe I am doing something wrong and do not know it.

Will be going out to dinner now...back later.

Thank you.

[defaultBR]

using this tool it create the FOlder
SYS, OEM and DUMP
but only sys have files
OEM and DUMP DONT HAVE
btw, DUMP isnt OEM/DUMP AND ROM?
what i have to edit so? when it repack, repack from what folder? ROM/SYS/OEM or DUMP Folder???
btw its clean, i dont have files to edit in it ;(
thx



EDIT: THe problem is when you select to dump to imgfs to packages, here it dont work, only in modules

btw, how can i extract the pda.os.nb to edit the hex and calculate the checksum to edit in pda.nb0.pre???

Edited by defaultBR, 28 January 2010 - 04:42 AM.

[aol1978]

hello west build.os appears when the file already exists that I do in
that?

[Gary Crutcher]

For those of you who are experiencing 'imgfs-new.bin NOT found', the
problem seems to be an "out of memory" error with ImgfsFromDump.exe.

I discovered it was my anti-virus program causing this to happen.
I am using bitdefender (will contact them today).

If I disable my anti-virus, then do Build OS, everything works fine and an
imgfs-new.bin is created.

Your problem/solution "may" not be the same as mine, but you might want to try it.

Update: Bitdefender has "Game Mode" and if I enable it, no more "out of memory" errors.

Edited by Gary Crutcher, 28 January 2010 - 12:22 PM.

[wes58]

defaultBR, on Jan 28 2010, 04:37, said:

using this tool it create the FOlder
SYS, OEM and DUMP
but only sys have files
OEM and DUMP DONT HAVE
btw, DUMP isnt OEM/DUMP AND ROM?
what i have to edit so? when it repack, repack from what folder? ROM/SYS/OEM or DUMP Folder???
btw its clean, i dont have files to edit in it ;(
thx

EDIT: THe problem is when you select to dump to imgfs to packages, here it dont work, only in modules

btw, how can i extract the pda.os.nb to edit the hex and calculate the checksum to edit in pda.nb0.pre???

after you dump the rom files are placed in the dump folder.
When pkgtool runs it splits them in oem and sys folders which are still in the dump folder.
My application moves oem and sys folder in the kitchen root folder.

If you have files only in sys folder, this is because you are trying to dump someone elses modified rom. When you run builos it removes microsoft certificates from the dsm files and package tool can't split the files in oem and sys folders. You can still do it manually if you look for for folders that start with oem.

Why do you want to calculate the checksum, it is done when you build the rom.

Edited by wes58, 28 January 2010 - 10:18 AM.

[Gary Crutcher]

Wes58,

After the BuildOS, is the header and xip.nb automatically added in the finished rom?

If so, does this mean I can then flash the *.nb0 file?

[defaultBR]

wes i got now,


like the question up by Gary,


so you only

1) Dump
2) Modify
3) Reppack using your tool? (here i found something strang, you have packages, but to reppack you have to select temp/dump or /dump/ :S where is pack from packages???)


about the header? etc...? it do everything automatic?


thx

Edited by defaultBR, 28 January 2010 - 07:17 PM.

[wes58]

defaultBR, on Jan 28 2010, 17:19, said:

wes i got know,
like the question up by Gary,
so you only

1) Dump
2) Modify
3) Reppack using your tool? (here i found something strang, you have packages, but to reppack you have to select temp/dump or /dump/ :S where is pack from packages???)
about the header? etc...? it do everything automatic?
thx

I guess I could change the description but that wouldn't be correct. Pack from packages is when you select "build imgfs from dump\temp".
When you dump to packages (to sys and oem), to build the rom you have to run Build.OS.
The result of BuildOS is -> packages in SYS and OEM are converted to 'flat dump', the files/folders are put by BuildOS in \temp\dump folder.
Imfgs.bin is built out of this folder when you have it selected.
Leaving the description as is, maybe correct because this part of the process is building imgfs.bin from \temp\dump folder. It's not building from packages because packages are already converted by buildOS to files/modules.
So if I wanted to be correct I would have one box for selecting 'build from packages' but this process would combine running buildOs, ExtReloc and imgfsFromDump.
I want to have those processes separate (so I can choose which part I want to do).
So, yes I will leave it as it is because that is describing part the process that it is doing.

I have the default options selected when you start the application, which means that you don't have to change anything (if you don't have much knowledge about rom building) to dump rom to packages and build from packages nb0 file. If you want to port the new OS you have to select other options, but that's something that you have to learn about before you do it.

The header file is added automatically. If you dump nb0 file and have an option to 'extract header from nb0 file' selected it will extract it and use it to build the new nb0 file.
If you don't select it or you use .nb file (if you dump the rom from your phone with Sorg's application you get a .nb file - to be accurate you get .bin file that you rename to .nb) the header will be created (it is stored in the application).
I will add an option to open .bin file so we don't have to worry about renaming phone dump to .nb
In that case you may want to update the version of your rom by changing it in the Pda Version edit box. It shows the header version that is stored in the application - which was the last version available at the time of compiling an application.
I will add an option to open .bin file so we don't have to worry about renaming phone dump to .nb

So, after nb0 file is create you can flash the phone using it.

Edited by wes58, 28 January 2010 - 07:06 PM.

[wes58]

Gary Crutcher, on Jan 28 2010, 12:18, said:

Wes58,

After the BuildOS, is the header and xip.nb automatically added in the finished rom?

If so, does this mean I can then flash the *.nb0 file?

Yes everything is combined together to build .nb0, which is you PDA.nb0 and can be used to flash the phone with Ocatans downloader.