Develop Bugs

ASUS P525 ROM Tool - Cooking your own ROMs

The attached utility will allow to extract .NB0 OS image from ASUS P525 "galaxy.cap" complete rom update packages, and also to update CRC on modified NB0 ROM image, to pass the flasher validity check and flash the modified ROM. Also it will allow to unpack compressed kernel partition.
The application dynamically linked to Visual C runtime libraries. They used by myriads of applications, and most likely you already have them on your system installed. If you are not (on a clean PC for example) and P525ROMTool complains about lack of needed libraries,- download and install this - http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE
For you technical people, the utility source is included too. You can see the basic layout, and that ASUS used Adler32 algorithm to calculate the checksum on ROMs (with slight modification that base sum was initialized to zero instead of one).
The basic procedure for cooking your own custom P525 rom is:
1) P525ROMTool -d galaxy.cap
This will extract the ROMGalaxy.NB0 OS-only image. For custom ROMs I recommend working with NB0 OS images only - no danger of corrupting bootloader & IPL this way.
2) prepare_imgfs ROMGalaxy.NB0 -nosplit
3) DelFile / AddFile
Iam not sure if you can truly fully rebuild the ROM and not to break anything (ROM tools were made for HTC platform, not for ASUS). So I recommend using DelFile/AddFile method at least for the start.
There are a lot of different ROM editing tools around, but I can not give you exact directions what is better and in which conditions - ASUS ROM cooking is less charted area then for HTCs.
I assume you know what you actually need to change on file basis for your ROM customization. If you dont know what I am talking about, this is not for you (read disclaimer at the end of the post, and think over it).
4) make_imgfs ROMGalaxy.NB0 -nosplit
5) P525ROMTool -s ROMGalaxy.NB0
it will ask about changed checksum. Enter "y" to update it. You can run P525"ROMTool -s ROMGalaxy.NB0" again to be sure that checksum was updated properly - it should'nt ask to change it second time.
6) Flash ROMGalaxy.NB0 via bootloader (copy it to SD card root, press "camera" fully, press reset).
Techincally, you can make the .cap file to flash via "autorun" loader, hovewer, I must warn you that .cap file will flash not only OS image, but also the IPL+bootloader. If something goes wrong, bootloader can be corrupted and device will be bricked.
If you flash ROMGalaxy.NB0, it will not flash over bootloader+IPL, so its a lot safer - if something goes wrong, you still must be able to flash emergency rom via bootloader.
Take note that any activity that involves the ROM updating is dangerous. Even if you understand everything, there is some risk. If you have only basic understanding of ROM mechanics, risk increases tenfold - you better consider before screwing up perfectly working and expensive device.
You have been warned.

Ingvarr, thanks a million time. I love yr WM5 Storage and I think I will love this tool also. I will start building my rom based on Sorg's build 6 since it does provide some very useful tools for us.

Ingvarr thank you for your cool tools.
But when I DIY my ROM, I can't make make_imgfs.exe work correctly. It returns some symbols I can't understand.
Even I run make_imgfs.exe just after finish running prepare_imgfs.exe, it returns the err.
Could you help me with this?

make_imgfs ROMGalaxy.NB0 -nosplit
NOT "nk.nba"
It writes the modified filesystem back in the original image, so it should remain the same. You dont want to mix the ASUS and HTC ROMs and then flash it to your device, trust me
I recommend you to read HTC ROM Tools instructions and forum threads and be sure you've got right how it works, before you screw something up

sir,
Bad news，it can't work with CHS ROM （ROMgalaxy.nb0） checksum error！～～～

Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).

Ingvarr said:
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Click to expand...
Click to collapse
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM

harlemyin said:
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
Click to expand...
Click to collapse
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit

Ingvarr said:
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Click to expand...
Click to collapse
yes
and it happens by official P525_V3320_WWE2nd too
checksum in official P525_V3320_WWE2nd is 79AB7436
ur SW changed it to EF722461----not modified NB0
u can download official P525_V3320_WWE2nd with www.asus.com or
ftp://dlsvr02.asus.com/pub/ASUS/IA/P525/P525_V3320_WWE2nd.zip

Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.

sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.

o
thanks a lot.

Thanks. The tool works perfectly on my P525.

Ingvarr said:
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
Click to expand...
Click to collapse
I make a mistake, thanks!

harlemyin said:
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
Click to expand...
Click to collapse
Oh, I know !
I make a mistake !
thanks

Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?

P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all

Night Runner said:
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
Click to expand...
Click to collapse
Everything about complete process is in the first post. What is you dont understand from here?

jmfa59 said:
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Click to expand...
Click to collapse
WWE means "world wide english".
First is 3.32, therefore, its newer.

Ingvarr
Thanks Buddy,
can you explain WW2 and WWE3 it seems that the latter is newer but the version V3.29 is older or is ment for different country

STAR100 (StrTrk) cooked ROM

Hi guys!
I converted latest Cingular rom (4.1.502.5) from nbh to nb format by Der Hermes Rom Koch 0.99.6.1. Then modified some files and reg-keys in windows.nb, and compiled NB-file with only OS (without ipl, spl, first, second splash, ext rom, finally without radio) and generated a NBH file without any errors.
Filesize of new RUU_signed.nbh is 39*930*145 bytes
But i afraid to flash this new nbh. Can anybody tell me, what can happen if new rom is broken or something else. Is there any risk of bootloader broke? Will i be able to rollback to any official rom?

So, tried to flash, but i got a error on 2%:
"Corrupted Image"

the rom is the rom
pda's dont have a backup of the org rom it came with
and transfering a rom from 1 device to another is not something people just do
less so if it's from windows smartphone to windows pda

No Cooking Tool can create a NBH File for Startrek!!!

Ok, but what if to flash it with my rom with Modified RUU Updater?

so, nothing...(
when will be way to flash this device...

http://forum.xda-developers.com/forumdisplay.php?f=302
this is prob the place to look and or ask that question

[VOX] How to get proper OS.nb from Part02.raw

I have a rom dump Part02.raw for HTC VOX. I want to get a proper OS.nb from that file. I don`t have original rom which Part02.raw came from.
My phone is cid and sim unlocked.
I was trying many tools with no effect.
I was using tadzio tools (ImgfsTools 2.1rc2.zip), but this gave me a not proper (about 40~mb, when it should be more than 62~mb) OS.nb which can not be flashed to device (system is not booting after flashing).
When using mamaich imgfs tools (imgfs_tools_182.rar) I get a "proper" OS.nb. I`m abble to flash it ok and phone boots ok, system is starting ok, cold boot is restarting phone ok, system starts ok again. But none of customization is done during cold boot and is missing. I get a plain vanilla rom on device. Looks like none of mxip_*******.provxml files are parsed during cold boot.
That`s not what I want, I want to get a identical copy of dumped rom (Part02.raw)
Everywhere I look, I find a tutorials for ppc not for sp. So I used them, with no luck, and I can`t find any help in Vox forum.
Q: What I did wrong? Why I didn`t get a PROPER flash? Is XIP has something to do with it?
(Part02.raw is from Orange Polish rom for Vox, RUU with rom can NOT be found enywhere. A donator OS.nb I took from HTC_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90. A donator OS.nb is much much bigger than Part02.raw)
Help please.
(I was trying to flash Part02.raw back to phone with pdocwrite.exe but this tool says that partition cannot be found, strange, cos pdocread.exe is reading partition fine and makes dump to Part02.raw ok, so I think that IMGFS partition is somehow locked for writing)

Error, Unknown rom version....(happens to every rom I create now)

I really don't understand what is wrong. All the roms that I create now cannot be created properly. The preconfig wont run, themes wont even apply, and when I try to reflash it with other roms, RUU says unknown version...I had to boot into bootloader to flash it. (without forcing sspl in ruu)
What the heck is happening? I'm cooking the same way i've been cooking (build OS + dutty's nbhtool) I'm getting very frustrated

Which kitchen or base ROM are you using? Need more info of exactly what you are doing!! Does this happen when you flash to official ROMs too?

I've used pandora, hypercore (they are both the same thing really). Both used to work fine, now they no longer work and both gave me the same errors "after" I flashed the rom I made. Here's the outline of the problem:
1) assuming current rom is schaps's 4.01
2) Runs RUU, auto detect fine
3) flash with the rom I made, flash completed, reboot
4) rom doesnt work properly, preconfig doesnt launch at all, tsk doesnt apply properly, and etc
5) run RUU, cant auto detect, "error, rom........."
6) boot to oli 2.10 BL, flash with "any" premade rom
7) repeats #1
The Roms I made were based on ATT's official rom, I've also used vp3g's coz most craps have already been removed.
1) run nbhextract to extract RUU
2) run nbsplit, imgfsfromnb, imgfstonb
3) toss os.nb into hypercore XIP extract, extract XIP
4) put everything into pandora's kitchen (root/ OEM folder, SYS folder, ROM [Os.nb, XIP folder]
5) remove/add stuff, rebuild .dsm if needed
6) run buildOS
7) run createbat
8) run NBtools (left "version as it is", chose hermes100, SuperCID, no ext rom/radio/spl)
9) rom created, then flashed.

I just made a basic rom with pandora. No editing done besides using the oem packages included to make it. Can someone try the rom out and tell me if you are facing the same problem? (Just a bare OS rom)
i.e. after flashing the rom, with active sync connected, RUU gives Error 244 and the only way to reflash it is get into bootloader mode. OR can RUU still work in windows after flashing it?
I need to know if there's something wrong with my bootloader (whether i need to reflash it) or somehow somewhere the kitchen tools that I've been using suddenly just screwed up any help is greatly appreciated
*I only have problems with the roms that I recently created, again, they used to work fine, I have no problems flashing other people's roms*
http://www.sendspace.com/file/3ycn37

I'd delete your HyperCore and Pandora folders and re-extract them from the original downloads to be honest. Whilst I can't think of what might cause the Error 244, I've found myself that after mixing this and that between HyperCore, Pandora and any of the zillions of 'working' folders I've got kicking about I do eventualy end up overwriting something somewhere that needs to be consistent between builds and knacker myself.

I have managed to solve the problem after redumping everything via the original tools. However, I'm still using hypercore kitchen to extract XIP. I no longer use dutty's NBHtool to create the image, I'm not sure if it contributes to the problem, but I'm having great results with nbhgen.
When I'm done cooking my rom, I'll document down everything I know and create my own kitchen.

Backing Up and Restoring ROM Image

Hi there.
The HTC Diamond has recently been released in Canada under Rogers and I'd like to backup the stock rogers ROM for safe keeping (and sharing).
I've been trying to find instructions on how to do this and found:
http://forum.xda-developers.com/showpost.php?p=2370527
Which is great, but after creating the RAW rom dumps, how do I flash the ROM backup back to the device?
Thanks!
noob edit: I apologize if this has been covered in the past. I have tried searching but surprisingly, I haven't found anything...

In my continuing research, I found this tool: HTC ROM Tool
http://forum.xda-developers.com/showthread.php?t=311909
I recall seeing this on a diamond wiki page. Is there an updated version that has Diamond rom support?
Thanks,

No one here can help a lonely noob trying to learn? Is what I'm asking even possible? Thanks!

I'm a noob too, but what you do is, you get one of the kitchens, put the extracted files in baserom (or similar folder) extract all sys and OEM packages, then adjust it as you wish (by deleting), and create new rom with HTC rom tool, and then you flash it back.
I'm beginner myself, but this should work.
Make sure you have all Visual C++ and NET. packages installed on your PC, and try to install the kitchen directly on C:/ drive. It helps.

I got the Rogers Diamond last night as well. I extracted the Part0x.raw files (as per Pof's instructions), then used a kitchen to extract the SYS/OEM from Part02.raw and the XIP from Part01.raw.
I haven't cooked them yet to test, but will try tonight hopefully and maybe post it if I'm successful. I got a brick when I tried making the OS ROM out of an existing ROM, as described in the Hermes and Elf DumpRom wikis. So I guess cooking it instead is the safest way to go.
Also remember to flash the unsigned Hard SPL 1.93 by OliNex after you back up the SPL.

hello,
one possible solution is to use a kitchen. for example:
http://forum.xda-developers.com/showthread.php?t=452184
put your raw's to BASEROM-folder.
put your original provider-rom in the same folder.
start !BEGIN
now you can select between two EXTRACT-MODEs.
first mode is extract ruu_signed.nbh only.
the second is for raw's with ruu_signed.nbh.
USE THE SECOND and wait until its finished.
now you can change or tweaks something - if you want.
follow the instructions and than you have your flashable rom.
BUT THE BACKUP/COPY - ROM is not for 100% the same like on your device.
for example: you have installed some programs with serial-key or activating by internet.
after restoring you have to enter/activating again.
some files will be changed back by original rom-files like the registry.
your personilized startmenu goes away - tweakees will lost.
the reult:
you will be angry.
after some experimantells now i used a combination of own cooked rom (with tweeks and buyed programs) and a backup-file which is not so big in MB.
okokur