http://rapidshare.com/files/261031029/hp212ROM_CHS.rar
Forget Chinese, where's the English version?
I already made an HP iPAQ 21x English 6.1 and 6.5 IMGFS a while ago, go to this thread:
http://forum.xda-developers.com/showthread.php?t=535559
I. Disassembling
1
Code:
NBSplit -data 2048 -extra 64 HPImage.bin
2
Code:
prepare_imgfs HPImage.bin.payload -nosplit
3
Code:
viewimgfs imgfs_raw_data.bin
Can anyone help with packing new rom ? unpacking works fine, but there is problem with packing it back, please look in hpimage.bin
If you used my files, it might just be that. I couldn't reconstruct them into anything more than BIN files. Also, you should know that these were my first, and so far only attempt to create ROMs.
Related
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.hv7. 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.
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?
Came from official htc kaiser, based from pdacorner.v9 and tools from bepe (thanks for him)
OS 5.2.19209 Build 19209.1.0.2
Not included:
- OEMApps
- OEMOperators
You need Microsoft Visual C++ 2008 Redistributable Package to using this kitchen
Updated:
- Added os.nb.payload
- Added initflashfiles.dat
Download PART1
Download PART2
Donations are welcome
Finally, A Kitchen on 19209.
Really thanks abusalza for your enormous Gift
Pouvez-vous poster un autre lien de telechargement svp, je n'arrive pas a telechargder depuis megaupload.
merci!
An other link please, i can't download from megaupload.
Thanks!
Good show sir, id highly recommend everybody making thier own ROMs based on thier own needs. Freedom of choice is always best.
Awesome brother!!!
This 19209 is the best wm6.1 build...thanks!
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
mrvanx said:
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
Click to expand...
Click to collapse
yup.......
mrvanx said:
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
Click to expand...
Click to collapse
yap, i get errors too
same here..
Ive narrowed it down to the OEM folder, however im not sure what the exact issue is. Ive just replaced the OEM stuff with my own from "V10 Roller". Remember to add os.nb.payload into theROM folder or you will get an error when the insert program is run.
Also getting exceptions, tried replacing the OEM folder with a known good one but it's still happening. Any suggestions?
caeci11ius said:
Also getting exceptions, tried replacing the OEM folder with a known good one but it's still happening. Any suggestions?
Click to expand...
Click to collapse
Well, I think I solved this problem.
mrvanx said:
Ive narrowed it down to the OEM folder, however im not sure what the exact issue is. Ive just replaced the OEM stuff with my own from "V10 Roller". Remember to add os.nb.payload into theROM folder or you will get an error when the insert program is run.
Click to expand...
Click to collapse
Thanks to mrvanx's hint, I compared each OEM directories with my old kitchen tools. Then I found some stuff is missing in 'OEM\OEM_Lang_0409' directory.
So I copied my old stuff into it, then Error was gone.
Edit:
Well, I found what the problem is. the 'initflashfiles.dat' is missing in 'OEM\OEM_Lang_0409' directory. If there is 'initflashfiles.dat' even if it is 0 bytes, then this problem is solved.
I dont want to sound dumb here, but where can i get the os.nb.payload file?
curveconcepts said:
I dont want to sound dumb here, but where can i get the os.nb.payload file?
Click to expand...
Click to collapse
Not a stupid question at all....
..download a known working rom based on 19209 (theres a few around)....to get os.nb.payload from it do these following things:
(using the programs in the TOOLS folder in this kitchen)
get the os.nb from the RUU_Signed.nbh file using nbhtool (in TOOLS/HTOOLS)
split the os.nb file into os.nb.payload and os.nb.extra using:
"nbsplit -hermes os.nb" on the command line. (the nbsplit.exe must be in the same dir as os.nb before you do it).
DONE.....slap os.nb.payload into the ROM folder when uve done it.
i've tried to updated my kitchen. fiuh... very hard work. my connection was bad. God help me
Help!
Hello!
Give me please - very confused: (
Downloading kitchen, treasure initflashfiles.dat in OEM_Lang_0409, taking the OS.NP.PAYLOAD from PDACorner V9, run BuildNB.bat
BuildOS compiles all successfully, but further writes:
ImgfsFromNb 2.1RC1
Sector size is 0x200 bytes
ImgFs partition starts at 0x00620000 and ends at 0x04080000
No IMGFS signature found. Exiting.
ImgfsFromDump 2.1rc2
Input file imgfs.bin cannot be opened. Exiting.
ImgfsToNb 2.1RC1
Using bigstoragemove mode
Input file imgfs-new.bin cannot be opened. Exiting.
NBMerge 2.1RC1
Could not open input file OS-new.nb.payload
What am I doing wrong? Give please!
Yet more problems. There seems to be issues with some of the programs in the kitchen. By replacing BuildOS with another version I had around I managed to get it to run and not throw exceptions (tried the other posted solutions but had no luck with them) but it seems another program is giving me issues now. Logs:
Creating 'dump' folder...
Done!
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
Slot 0 Boundary: 0x01fa0000
Slot 1 Boundary: 0x03e33000
RAMStart: 0x802ac000
RAMFree: 0x802e6000 - 0x83a00000 L0371a000
KernelFlags: 0x00000000
FSRamPercent: 0x00000020
Done!
Copying OS.nb.payload...
1 file(s) copied.
The system cannot execute the specified program.
Could Not Find J:\kitchen\buildpkg.wrn
The system cannot execute the specified program.
ERROR! (errorlevel: 9020)
Press any key to continue . . .
Looking at the batch files, this would indicate me that "all_packages_to_one" and "insert" are having problems (these are the lines where "cannot execute" appears). I thought it might have been a problem with 7zip, which I used to extract the archive but WinRAR has the same issue. No idea what's going on here, it's a very odd problem...
baxxik said:
Hello!
Give me please - very confused: (
Downloading kitchen, treasure initflashfiles.dat in OEM_Lang_0409, taking the OS.NP.PAYLOAD from PDACorner V9, run BuildNB.bat
BuildOS compiles all successfully, but further writes:
ImgfsFromNb 2.1RC1
Sector size is 0x200 bytes
ImgFs partition starts at 0x00620000 and ends at 0x04080000
No IMGFS signature found. Exiting.
ImgfsFromDump 2.1rc2
Input file imgfs.bin cannot be opened. Exiting.
ImgfsToNb 2.1RC1
Using bigstoragemove mode
Input file imgfs-new.bin cannot be opened. Exiting.
NBMerge 2.1RC1
Could not open input file OS-new.nb.payload
What am I doing wrong? Give please!
Click to expand...
Click to collapse
Try a different os.nb.payload fromanother ROM. The one bundled with pandora beta 9 works fine.
caeci11ius said:
Yet more problems. There seems to be issues with some of the programs in the kitchen. By replacing BuildOS with another version I had around I managed to get it to run and not throw exceptions (tried the other posted solutions but had no luck with them) but it seems another program is giving me issues now. Logs:
Creating 'dump' folder...
Done!
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
Slot 0 Boundary: 0x01fa0000
Slot 1 Boundary: 0x03e33000
RAMStart: 0x802ac000
RAMFree: 0x802e6000 - 0x83a00000 L0371a000
KernelFlags: 0x00000000
FSRamPercent: 0x00000020
Done!
Copying OS.nb.payload...
1 file(s) copied.
The system cannot execute the specified program.
Could Not Find J:\kitchen\buildpkg.wrn
The system cannot execute the specified program.
ERROR! (errorlevel: 9020)
Press any key to continue . . .
Looking at the batch files, this would indicate me that "all_packages_to_one" and "insert" are having problems (these are the lines where "cannot execute" appears). I thought it might have been a problem with 7zip, which I used to extract the archive but WinRAR has the same issue. No idea what's going on here, it's a very odd problem...
Click to expand...
Click to collapse
You can use Microsoft Visual C++ 2008 Redistributable Package.I had the same error end it solved it.
I tried NBSplit and I don't know what values give to -data and to -extra. Tried hermes or kaiser but then I couldn't dump the rom.
I've successful dump it with the same method than the Kaiser...
-data 2048 -extra 8
use kaiser kitchen...easiest way!!
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