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
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
Hi, this is my first post in this forum. I tried to be a good newbie and read quite many threads before posting. And there are already great HOW-TOs available, but I have some more detailed questions for which I could not find my answer in this forum yet.
So here is what I want to do: Backup the full device (To be able to restore it in to the state it was in once it came from the operator)
here is what I so far did:
Step 1:
Application Unlock the Device
Step2:
Back-up personal data with PPCPimBackupV2.8
Writing down device information (such as Rom version, Radio, Device ID…)
Backup most of the registry (using extract function in MobileRegistryEditor)
Rom-Version: 1.37.774.3 SVE
Radioversion: 1.00.25.03
Protokollversion: 52.26a.25.09H
Device SPL: SPL-1.37.0000
Step 3:
Back-up ROM
With itsutils and pdocread.exe.
Now 4 .raw files: part00, part01, part02, part03
Step 3:
BackupSPL:
A. Used itsutils with
Pmemdump.exe 0xa8000000 524288 SPLdumped.nb
B. Also downloaded the official SPL-1.37 (just to make sure / google)
-----------------------------------------------------------
I would like to back-up everything needed to return it to the original state before fooling around with ROMs.
So my question is how to I backup the:
1. Is there a way to just read in the complet memory of the device (e.g in a raw file, that covers all from bootloader, OS, RADIO etc [so a full image of the device] sorry for asking / might be quite stupid question)
2. CID (how to find out at what memory position this is stored)
3. RADIO ROM (is this already included in the raw files from step 2?)
Steps after that to flash the new ROM so far seem rather clear to me as they are in detailed descriped in this forum. Will be my first Rom flashing and decided to stick with a official ROM for now. The main purpose for flashing the device is to change from Swedish to English and to get some bug fixes for the device.
So thank you guys for the help already provided.
Would be great if you can give me a hint on this.
ThoTho,
Perfectliy explained your interest, its' just the same thing that iv'e been trying to do since I started to see all these ROMs availables.
What I've found in another forum (only that this in Spanish, I hope you do not bother ) is that this could be done with SPB, so I will try to do so to check if it is that easy.
Hopefully we'll get some help.
Gus66
Hi,
as I've seen on the SPB homepage, the backup tool backups all the data, but I would like to backup the factory rom because I use czech language on my device and I didnt see original czech rom.
Or should I hard reset the device, make and then make the backup with SPB?
The created exe is than a genuine rom file or just some program file with the contacts/mail/etc backups that can only be run in WM environment?
you can get your manufacturers ROM either from their website or direct from HTC
i know i can get vodafones ROM in a nice application
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
Since this was a question I have moved it to the Q & A forum before I get spanked by a moderator.
http://forum.xda-developers.com/showthread.php?t=1640484
The topic over there is clearly Excalibur related - so I believe it should be here.
anyway - why do you need bkondisk to get dumps of the existing partitions?
Do you have a Spanish ROM to flash on the device already or do you want to make one yourself (I doubt that)?
The usual sequence for flashing is:
1.) application unlock old OS
2.) run jump-SPL (a RAM replacement for the ROM SPL which does not care for CID lock)
3.) flash new OS
I also have backed up my old OS, but I have no idea how to flash that back. bkondisk can only READ - not write!
The dumped data are also still somehow "crypted" as the Samsung OneNAND storage which you dump has an own encoding.
Try to get a shipped ROM of the version that has a matching CID, so can be loaded without all the unlock/jump-SPL stuff.