Related
How to:
1. Extract Polaris_Kitchen and put it in C:\ , so we will be C:\Polaris_Kitchen
2. In Polaris_Kitchen\TOOLS\Polaris.htcrtproj set:
VersionId
LanguageId
3. Put your packages inside OEM
4. Execute BuildOS and select/deselect packages that want to include in your ROM then start it and at the end of his work close it.
5. Execute Build ROM.bat
6. Please Wait
7. That's all, inside FLASH directory will be a RUU_signed.nbh ready to flash!
General information:
OEM: HTC Polaris 3.13.405.0
SYS: HTC Polaris WWE 3.13.405.0 - (Build 19965.1.2.3)
Useful Links
Polaris Hard SPL v2
Polaris CustomRUU
Custom Splash Screen
Thanks to:
bepe for his BuildOS
Dark Simpson for his HTC ROM Tool
misar for G'Reloc
Olipro for his Hard-SPL
tadzio for ImgFS Tools
Changelog:
Code:
What's new in v1.4?
[+] Updated the kitchen to Official HTC ROM
[+] Updated OS CE 5.2.19965 (Build 19965.1.2.3)
What's new in v1.3?
[+] Updated OS CE 5.2.19214 (Build 19214.1.0.4)
What's new in v1.2?
[+] Updated OS CE 5.2.19209 (Build 19209.1.0.2)
[+] Updated OEM part - Polaris CHT 1.52.753.3
[!] Fixed Ringtone Settings problem
[!] Fixed USB to PC, now it's in Connections
[!] XIP rebuild
What's new in v1.1?
[+] New SYS part from AT&T Kaiser ROM (Build 19209.1.0.2)
[+] Updated to .NET 3.5 Compact Framework
[+] Voice Command 1.6.19209
[!] Fixed small issue in the Kitchen
Download:
Polaris Kitchen v1.4
Password: Polaris_Kitchen_v1.4
Download Improved "Build Rom.bat":
Build ROM.zip (thanks to worstenbrood)
Note: I improved "Build Rom.bat" a bit so you can use the kitchen from ANY directory, not only C:\Polaris_Kitchen, adjust the 2 environment variables at the beginning (set version_id=... and set language_id=...) to your needs and execute buildos.exe, then "Build Rom.bat".
Download base ROM in other languages:
FRA
GER
NLD
ITA
NOR
PTG
SPA
RUS
How to extract and reconstruct OEM and SYS parts:
P.S.: OEM part must be an Polaris OEM, not from other devices!
1. To extract .nbh files you need NBHextract.
Put your .nbh file and nbhextract.exe into a directory
From prompt commands: nbhextract file_name.nbh
Delete all extracted files except xx_OS.nb
Rename xx_OS.nb in OS.nb
2. To extract OS.nb files you need ImgFS Tools (v2.1rc2)
Extract all files inside the zip into the same OS.nb directory and from prompt commands:
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
We have dumped the ROM and than we need reconstruct OEM and SYS parts, to make this need PKG Tool.
This step it's very simple, open the dump directory with PKG Tool than Tools -> Build Packages
Ok now we have OEM and SYS parts.
!! Remember, use only OEM part from Polaris ROM don't use from other device or your ROM don't boot. !!
How to create a package from a .cab
There is a very very powerful tool to do this, Ervius Package Creator (EPC).
1. Download latest version of EPC from his thread.
2. Select your ROM Language.
3. Select Package's group.
4. Click on Open Cab File than select your cab.
5. Copy the directory created inside your OEM directory.
5. Done!
Thanks to my friend Ervius for this awesome tool
hi friend, I'm happy to see that works go on, and with a fantistik kitchen....
I think so, people will be able to eat somethings good!!!!!
Thanks for all work i'll try it for the next flash
Hi UDK, I always attend to taste your rom on my polaris
Yes thanks man a good explanation to cook a rom i was waiting for this
Hi Udk i'ts to make wwe version?
Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?
HTC Touch Dual Dialer for Touch Cruise
Hello,
the touch cruise dialer satisfy me not. I saw the dialer in Youch dual and it's much better.
Can I replace mine for touch dual dialer? What should I do to replace?
PS: I thought there is a .cab with dialer, I should just luanch it and it will remove the previous one himself, but I cannot find such a .cab. Help.
Another question, if I finally replace my dialer with another one - will the view of "Calls list" be replaced with the new one? I wish it will.
infido said:
Hi Udk i'ts to make wwe version?
Click to expand...
Click to collapse
Yes it's WWE.
lexi1986 said:
Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?
Click to expand...
Click to collapse
Need only to change OEM (Polaris OEM) and SYS (Kaiser SYS) from a Dutch ROM.
Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.
lexi1986 said:
Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.
Click to expand...
Click to collapse
First all you need an Official Polaris Dutch ROM (find it here) to extract OEM part only.
To extract .nbh files you need NBHextract.
To extract OS.nb files you need ImgFS Tools
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
To reconstruct OEM and SYS parts you need PKG Tool
Remember, OEM from Polaris and SYS from Kaiser, don't mix them!
Then put your OEM and SYS in C:\Polaris_Kitchen (delete existing).
Open ROM\XIP\boot.rgu and change:
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:409
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:409
to
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:413
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:413
save and exit.
That's all.
Thanks i will try youre great.
DONE: now i have to wait for the Polaris Kitchen youre great i hope this work. The Download link is availible tonight ?
Edit: Nevermind there are online great work
Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up
lexi1986 said:
Thanks i will try youre great.
Click to expand...
Click to collapse
Try, it's not difficult
omaga said:
Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up
Click to expand...
Click to collapse
part1 and part2 are now online!
Have fun
Thank you UdK!
very fantastic UDK
moderator... Sticky thread???
I get an Error: The File temp\packages\75bcd9fa-30b9-8705-5d86-11acd2e2c1b1.dsm already exists
after that the BuildOS stops.
Edit: After closing BuildOS the file Buildrom.bat is busy with things maybe it's going to be ok.
I have got a .nbh file now i going to flash and look if it is working.
Edit: Flashing has worked but my phone is hanging on boot any idea ???
If BuildOS returns error close it and then close prompt commands, don't flash the .nbh.
I will fix this, If buildos returns error automatically stops all others tools.
XIP 20721 for Polaris.
SHAYDER said:
XIP 20721 for Polaris.
Click to expand...
Click to collapse
Call me stupid.... what's XIP?
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20721 is current XIP.
To build ROM with new XIP you must: put "MSXIPKernel" folder to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
thanks....
20721 seems have Microsoft touch function
and 20721 XIP seems good , too.
now trying ^^
Brilliant cooked in and working fine
I am a total n00b so took a risk flashing but it went in and reports as 5.2.20721
Shayder,
no more need for your imgfs.bin and os.nb.payload like in the
XIP 20296 you posted?
Olioaglio
German ROM to dump available?
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Olioaglio said:
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio
Click to expand...
Click to collapse
I cant help you. ((Glass 0.4, UDK R7 GER, bepe) they Specially so have made) You must find needed files in internet.
Good work my friend. Indeed a good help.
kindly post the os.nb.payload as you have posted in the other XIP.
....regards
...c_shekhar
"imgfs.bin" and "os.nb.payload"
First off let me say thankyou for putting this package together.
I have cooked a rom and it boots up fine so I have started to customize it. Run into a few problems that I am hoping someone will be able to fix.
Here goes
I have used the package creator to insert some cabs into the installation. 3 of my cabs went in fine the rest create errors when building the registry.
So I am looking for a way to auto run the cabs. When the OS loads it seems to run a UC application from 2 places.
config_operator.txt
config_PT.txt
These point to cabs in the \windows directory and are installed upon first running of the rom. Brilliant I though. I copied the cabs i wanted into the OEMAPPS folder. Now when the rom is flashed my cabs are 100% copied OK into the windows folder as I can see them and run them.
So I edited the config_operator.txt
CAB: \WINDOWS\googlemaps.cab
CAB: \WINDOWS\coreplayer.cab
CAB: \WINDOWS\3iepatch.cab
CAB: \WINDOWS\opera1938.cab
CAB: \WINDOWS\advancedconfig.cab
CAB: \WINDOWS\keyboard.CAB
EXEC:\WINDOWS\cusTSK.exe \WINDOWS\Htc.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\PP_AKv33-Defau
Now when I re-flashed and the OS boots and I can see it in the install run my cabs and it looks like they are installing. The last one restorepie.cab then resets the device.
Upone reset my cabs have not been installed even though it looked like they were. Why is this?
Also is there a switch I can put to delete the cab after install? something like
CAB: \WINDOWS\opera1938.cab -d
Thanks in advance.
I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck
SHAYDER said:
I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU!!!!
I went through the rgu for my opera package and did as you said. Now build perfectly no errors.
Time to get some more cooking done!!
Shayder,
Trying to use your kitchen but got stuck on how to change the automatically splash screen already setup in the BAT file? I was looking for NB file so I could just change the path but didn't understand those files named polarishtcrtproj.....
Thanks a lot and also for sharing this stuff!
SHAYDER said:
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Click to expand...
Click to collapse
To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck
Thanks Man!
Cooked already but is showing CE OS 20721 and Build 20275
Things happens
SHAYDER said:
To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck
Click to expand...
Click to collapse
version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721
Yep...agreed
I have used Niki's SYS but got stuck on splash screen all the time
SHAYDER said:
version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721
Click to expand...
Click to collapse
I can help? Just whot do you do?
Hello,
I want to cook my own ROM. After I read many many sites at this forum, I found a 'polaris kitchen 1.3' that seems to be good for me.
I want to use the original WM6.1 O2-ROM as base for my 'new' ROM.
My target is the original ROM without some progs (O2 specific) an also without tomtom, 'Erste Schritte' (First Steps) and opera.
I want to add MyMobiler, and some other cabs. Also, I want to make some registry corrections.
These steps I made:
1. Extract the Updatefile with 7Zip and got the neccassary file 'RUU_signed.nbh' as I understand correctly.
2. Extract the 'RUU_signed.nbh' with this command
Code:
NBHextract.exe RUU_signed.nbh
Now, I have these files
- '00_Unknown.nb', <== Radiofile (Thanx to ianl8888)
- '01_SPL.nb', <== ???
- '02_MainSplash.bmp', <== O2 BootSplashScreen Bitmap
- '02_MainSplash.nb' <== ???
- '03_OS.nb' <== OS file which we need to split
Question1: Do I need only the '03_OS.nb'? What do i need the other files for?
3. I used this command to split the nb-File '03_OS.nb'
Code:
NBSplit.exe -kaiser 03_OS.nb
I got this:
- '03_OS.nb.payload'
- '03_OS.nb.extra'
Question2: Is it OK to use the parameter -kaiser? Remember, I will create a orbit2/polaris ROM
Question3: What are this files for?
4. now I used this command
Code:
imgfsfromnb 03_OS.nb.payload imgfs.bin
to build the 'imgfs.bin' file
5. with the following command I've created a 'dump' folder
Code:
imgfstodump imgfs.bin
This dump folder include many subfolders and files
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Maybe this is the next step ... (Thanx to ianl8888)
8. Now we must dump the 'xip.bin' with this command:
Code:
RomMaster.exe 03_OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Question5: What to do next?
Hi,
that is exactly the same I wanna do. After you have the SYS and OEM folder the next would be to re-create the ROM folder for your kitchen. We need a new XIP. That is the point where I don't know how to continue. I have already tested to replace the original SYS and OEM with those versions I build via dumping the new O2 Germany ROM. But after trying to rebuild and flashing the ROM with the kitchen the ROM won't boot.
Therefore I asked the chefs at http://forum.xda-developers.com/showthread.php?p=2657634 to help me.
Hopefully we can take a step further.
Tom
I have already managed to build a new german rom based on the
O2 GER 3.13 released some days ago and I used the XIP 20743 from
Shayders thread to build. Had no errors in cooking but I did not
flash yet because of maybe wrong location of XIP files in the ROM.
But I have another problem with HTC ROM Tool when trying to cook
the radio 1.59.42.15 (or any other) in the ROM. The tool always states:
"The size of this file is greater than default. Do you want to assign this file?"
I said yes and it builds the rom but now I don't know if it would work
because of the warning. I tried different radio.nb files and all of them
are 17MB and all of them give the error in HTC ROM Tool when assigning
them... Is this normal?
Olioaglio
Orbitter2 said:
Hello,
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Question5: What to do next?
Question6: Should I copy these folder to the kitchen?
Click to expand...
Click to collapse
I don't know how to proceed yet with the "re-building stage", but I think you are still 3 steps short of this, anyway:
we need the XIP.BIN file to use the XIPPORT.exe tool on for XIP Files\Modules. The XIP build no. I have extracted is 19965, but we are already at 20753 for the device-independent MS files
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
ianl8888 said:
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
Click to expand...
Click to collapse
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
But now, when attempting "make pkgs", XIPPort.exe falls over with "could not load file or assembly" errors these tools are so prone to. A path problem (I think) that continually drives me up the wall. We need the "packages" from XIP.BIN to know which files are the OEM drivers etc specific to the Polaris.
So I'm at steps 7, 8 and 8.5 ... it's like pulling teeth
BTW, 00_unknown.nb is the radio file.
ianl8888 said:
I have successfully extracted it from an Eten temp.dat file
Click to expand...
Click to collapse
I already thought I knew your nickname from somewhere .
ianl8888 said:
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Click to expand...
Click to collapse
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
BTW, 00_unknown.nb is the radio file.
Click to expand...
Click to collapse
I already inserted this into #1
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Olioaglio said:
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Click to expand...
Click to collapse
I also did it this way. You're right, there is a ruu_signed.nbh after all that staff has finished. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
tomduke99 said:
. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
Click to expand...
Click to collapse
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Orbitter2 said:
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
Click to expand...
Click to collapse
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
2) rommaster.exe is found (from my memory only) in any one of the Polaris or Kaiser kitchen files. It is a very old file, though - Nov 25, 2005. You can also find it in Shayder's kitchen on the front page of this sub-forum
Perhaps there's a later version of a "rommaster.exe" somewhere ?
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
If you are too unsure to test with flashing (I thought that was what HardSPL was for !!) then try to extract your own RUU_signed.nbh in full and see what you get.
ianl8888 said:
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
Click to expand...
Click to collapse
later edit: I have XIPPort.exe "making pkgs" now. XIPPort needs to be in its own folder ( ?? )with the support dll's etc.
So now I'm at Step 9 (the unknown) with \OEM and \SYS "packages" for editing.
The base ROM I'm trying to edit is the recent release of the official HTC WM6.1 Polaris ROM. This ROM is not protected by "all-commands-to-one" etc and so is fully extractable and editable if I can figure out how.
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
I am trying to do two things with this ROM:
1) replace the XIP device-independent files with an upgraded set (build 1995 to build 2073)
2) remove all the crap that HTC and other ROM cooks put into it - like Cube, Home, Office etc etc
In other words, I'm trying for a WM6.1, recent XIP build, very clean ROM
Maybe ...
ianl8888 said:
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
Click to expand...
Click to collapse
There is a very useful "sticky" thread on some of this, started by udK.
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
My version attached. If someone wants to try...
It's a german light version of O2 3.13.207.0 ROM
without Cube, TTN, Opera, useless stuff.
With XIP 20743 cooked in as os.nb.payload with
Polaris Kitchen V1.3
No radio included. You will most likely have to flash
1.59.42.15 manually after installation of the rom.
Olio v1 GER (Rapidshare link)
Olioaglio
If been testing around with this thread and this one and made a successful rom, some how the xip files needs to be extracted, 3,4 MB is little low, cause the one i got was 3.8 MB.
I used buildos+package_tools-2.7.exe to build my package and htcrt.exe to build the rom. (i change model from KAIS***** to POLA***** to get working and flash able rom)
I will experiment more cause i need to convert raw dump to original rom for warranty
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
Yes, the various Registry addresses change as the XIP build changes so we need to understand RGU's, DSM's etc. The uDk sticky is helpful
Because the kitchens require a "template" to re-build a ROM, I still believe that the most thorough method is to use the just-released WWE WM6.1 HTC ROM as this template. Extract it all, replace the XIP device-independent filesystem with a newer build, remove all the stuff you don't want from \OEM "packages" and re-compile.
This is struggle street maybe, but this jigsaw is a challenge.
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
At this point I have OS version CE OS 5.2.20753 but the Build is still 19965.1.2.3. Therefore the next step should be replacing the SYS parts with its equivalents from a newer Build.
Questions about this:
1. Can I use a SYS folder from another (newer) ROM without modifications?
2. How to build a ROM with German localization? Shall I only copy the language specific folders from the original ROM to the SYS-part of the new ROM?
3. Are there some other stuff? What about Registry settings for different languages?
....
I read so many threads but I'm still not sure what to do next.
Thanks.
Tom
tomduke99 said:
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
Tom
Click to expand...
Click to collapse
Yes, that's real progress.
BUT - list step-by-step exactly how you did it, please
This is the problem - many posts about being successful, very few listing the detail.
I finally found a way to overcome space issue that cause BuildIMGFS throw error when you put too many files in the ROM using captaintrip's kitchen
The repack used imgfsfromdump instead of buildimgfs which avoid the size issue and in additon can reduce the final size of flash.dio
The usage are the same with captaintrip's kitchen, I only rename the bat to "iPAQ61x_91x flex kitchen" since this works for both 61x and 91x
You will need to rename flash.dio to TEMPLATE.ROM and put it under ROM folder, when you run iPAQ61x_91x flex kitchen.bat it will also prompt you,follow instruction
keep in mind if you use flex kitchen to build your rom won't be able to extract it properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
use iPAQ614c Rom Kitchen.bat if you want to build your rom in old way
Updated July 7th: attached new cecompr_nt.dll that fixed memory leak, necessary for LZX compression, replace the one under TOOLS folder
Download (v0.3):
mediafire
Updated: Dec 9th ,09
v4 Beta:
-improve ability to decompose ROM, however the packages in SYS and OEM portion is usually mix up so you have to manually move them to correct folder after extraction
Download:
21501 kitchen
21215 kitchen
Rom folder for w version for 21215 (Rename it to ROM if you want to build w version)
21232 kitchen
21234 kitchen
21725 kitchen - removed due to too many issue, use 21728 kitchen instead
21728 WWE Kitchen
21728 ITA Kitchen
21728 GER Kitchen
21728 FRA Kitchen
21812 WWE Kitchen
21815 WWE Kitchen
23001 WWE Kitchen
23001 CHT Kitchen
23004 WWE Kitchen
21921 WWE Kitchen
23009 Hybrid WWE Kitchen
23016 18.1 WWE Kitchen
21854 WWE Kitchen
23047 WWE Kitchen
23052 WWE Kitchen
21867 WWE Manila 24M2 Kitchen
21869 WWE Kitchen
21869 WWE Manila 25M Kitchen
23088 WWE Kitchen
28002 WWE Kitchen
28011 WWE Kitchen Beta 29
28011 WWE Beta 29_2 Kitchen - kitchen of Beta 29.2
note: you can replace WinCENLS_Lang_0404 with WinNLS_WWE (from other rom kitchen) to save ROM space
-arcsoft streaming player & codec can be removed if you don't need them
23515 xip (use with 23518 SYS)
23518 CHT Kitchen (LZX)
23518 WWE kitchen
21888 WWE Kitchen
23529 WWE Kitchen
28230 WWE Kitchen
23544 WWE Kitchen
23563 WWE Kitchen
91x 28011 WWE Kitchen -not tested since i don't own 91x device so use as your own risk, use dnw in the worst case
91x 23518(23515)/21888 untested xip
Official WM 6.5 Tookit/SDK/Emulator: here
FCC Information for 610c
FCC information for 910c
----------------------------------
Structure Overview
XIP is the kernel, this is also what you see those 2xxxx build mean, the whole term is called "Execute in Place", i.e execute files in rom directly without copying to ram, this is for boot process, anything wrong mean you will stuck in clean boot
OEM is for device/manufacturer specific program/drivers
SYS is for Windows Mobile system files
A package is a folder with at least a dsm file,all other files are extra
-rgu file is just reg file which you can use notepad to edit
-default all files goto Windows directory (obviously exclude rgu file)
-initflashfiles.dat/txt is a text file with instruction to move files to different directory
Files vs Modules
Modules are folder with ".dll" in their names. Inside the folder there is imageinfo.bin, S00X where x is a digit. When they are cooked into ROM they will become dll with proper relocation (done by WMReloc/G'Reloc). Supposedly being modules would make them load faster(because no need to relocate at runtime?) and some dlls must be in modules or else some program will not work properly. However there are also cases that modules must be converted to files.
Technically you can put everything in SYS since at the end buildOS will merge everything together but it is easier to manage if you follow the OEM/SYS structure
Common Issues TroubleShooting
hang on 1st boot screen (HP Logo)
-XIP porting issue, .rom , .vm file not correct .etc
hang on 2nd boot screen (WM splash screen)
-module did not relocate properly (did you run WMReloc or GReloc?)
-XIP (lower possibility, i don't think it affect..just in case you should keep in mind)
hang/crash on today screen
-software conflict/missing .etc , check your SYS/OEM files
Endless HP update/customization engine
-happens because of different model uses different customization engine, using one from other model/region will cause it to rerun every boot time, the only solution seem to prevent it to run from start by removing it from initflashfiles.dat. Convert all the fix into packages and integrate to the rom instead
installed SIP(virtual keyboard) cannot be switched
-use recmod (under tools folder) to convert all modules into files in browsingie folder
cannot compose new sms/email .etc
-replace redist_lang_[lang_code] folder with one that worked before
wifi cannot turn off after boot
-set HKLM/Comm/SDIO86861/Wireless to 1
XIP
To insert ported xip, run this command: osnbtool -c TEMPLATE.ROM 1 xip_out.bin
where xip_out.bin is your new XIP file
xip porting tutorial can be found all over the place in xda/ppcgeek .etc
Also make sure in ROM folder, the boot.rgu is from your device xip (the kitchen I provided only contains 61x xip so to cook for 91x you need to put 91x boot.rgu instead)
Phone Radio
rilgsm.dll is needed but usually it is in OEM folder
PagePool
Overview: xda wiki
edit using pagepool_by_wlodixon under flash folder, copy your flash.dio and run the appropriate cmd
The only exception is if the rom set pagepool to 0 (Dynamic PagePool), it won't able to recognize and you have to hex edit
hex edit the xip.bin at 0x000A75E4, change all 4 bytes to your desired value (all 0 for dynamic pagepool)
Convert cab to OEM
get package creator here
use it to open cab, then wince cab analyzer opened, choose extract folder icon, after close wince cab analyzer, you will be present with shortcut screen, do you things and hit done, finally hit complete package unless you want to change some option
Create simple cab for file/reg changes
get QuickCab
Xt9
corresponding lang files in OEMApp/OEMLang_#### where #### is the 4 digits lang ID
-[2letter langs code]hpd.ldb
-[2letter langs code]lbUN_xt9s/lsUn/.etc].kdb
-et9.SQR.[Language].bmp [Optional, some language like Polish/Portuguese just point to english bmp in registry]
-[a bunch of number/digit known as GUID].rgu (if you open it up you will find there is registry on xt9)
also under OEM\OEM_Lang_[Lang number]
-initflashfiles.dat (actually you can use notepad to open it and seacrh for ldb/kbd/bmp to see which lang files )
cooking different language
-you will need your language OEM folders from original HP rom
-your language wince.nls
-replace all language mui (e.g 0409=English) with your language mui
-some languages may added extra folders, be sure to copy them into SYS too
-sometime the hp customization/update will end up endless run in every start, in this case you will need to prevent it from running and integrate all updates into the ROM
OptionXML Addon
I have written this small .Net 3.5 App to generate option.xml for SYS packages which will allow you to select the common package and different language more easily without moving folders all the time, just unzip the zip to kitchen which will overwrite the existing batch file and put the exe under TOOLS folder.
To select/UnSelect a category in BuildOS, you can click on the Category group (e.g click on 0409 will select all 0409 packages in SYS), then click on one of the packages will select/unselect the whole group
Reserved for extra space in case
-------------Step by Step guide for xip porting-----------------------
Make sure you read this tutorial first
1. copy(either get it from kitchen or dump it using osnbtool) the existing xip_out.bin and rename it to xip.bin, open xipport, click dump xip.bin and you will get a OUT folder
2. choose write map then make packages , now rename this out folder to some other name
3. dump the new xip(from other device) using osnbtool, rename it to xip.bin & do the same as step 2 with xipport
4. now copy MSXIPKernel & MSXIPKernelLTK under Modules and Files folders from OUT folder(from step3) and overwrite to corresponding 61x OUT folder(from step1)
4.5 as said in the xda tutorial, remove hd.dll, osaxst0.dll folders and their corresponding text files under modules to avoid physical address overlap
5. use xipport to undo and then realloc and write maps. Then you check map files to make sure there is no !!!(memory address overlap) I recommend using XIP address tools to check for overlap, sometime you will get error when you realloc (key already exist .etc), use xip address tool and set work folder to OUT then you will see error on first dll addr which you have to fix all highlighted red cell(overlapped address). Note that to fix first dll addr address you have to highlight the cell, enter the new start address on the V address cell in bottom, click modify, then use mouse to highlight the 1A cell above, and change the D address cell to the same as V then click modify button(on the right of V cell). You should see the change in table then. For virtual base overlap you only need to modify V cell only
Note: first dll addr overlap will result error when you click realloc in xipport.
The goal is have no overlap as shown in MAP.txt. When there is no more overlap, use xipport to build xip_out.bin and then insert the xip into the dio file using osnbtool
Commands:
extract xip: osnbtool -d flash.dio 1 xip.bin
insert xip: osnbtool -c flash.dio 1 xip.bin
also make sure your ROM\boot.rgu is from your device xip
-----------------------------------
IPAQ 91x boot keys:
Clean bOOt - Voice Commander + OK + Reset
Download Image - Volume Down + OK + Reset
Calc Checksum - Volume Up + OK + Reset - disconnected, SD card out
RUU - Volume Up + OK + Reset - UsbConnected, SDcard out
SDloader - Volume Up + OK + Reset - USB disconnected,SDcard in SDloader
Modem_CAL - Voice COmmander + Volume Up + Reset
Diagnostics - Voice Commander + Volume Down + Reset
-------------------------------------
LZX Compression:
The default compression algorithm for ROM is XPR, if you must include lots of files that causes your resulting rom >80mb under XPR(81920kb - ROM Size limit for 61x, bigger than this the device won't boot), you need to use LZX compression. It reduces rom size by ~13% but with ~1-3% performance hit(from other post I read, I never verify the performance hit).
To use LZX compression, you need to replace the cecompr.dll folder in XIP Modules with the one attached in this post. Re-port the xip (realloc + write map + build xip_out.bin) and then use osnbtool to inject the xip inot TEMPLATE.ROM.
Then hex edit the imgfs_raw_data.bin in the rom kitchen, replace the first string "XPR" without quote you found with "LZX" without quote.
Make sure you have replace the cecompr_nt.dll under tools folder of the kitchen with the one I attached in 1st post to avoid memory leak
Now just build normally, you will notice the time to inject file will take much longer because of the compression
Is there any ROM kitchen tools for hp iPAQ h6365 WM2003?
Wow great kitchen. Thanks for sharing.
here, here! keyx you da man
One thing though - when you say this:
Phone Radio
if you are using SYS from other device, make sure you replace ril.dll and phone.dll from a working rom in phoneRedist or you will get a phone radio not installed which disable phone function
rilgsm.dll is also needed but usually it is in OEM folder
Click to expand...
Click to collapse
I'm not sure that is actually correct. I've been using ril.dll and phone.dll from all kinds of donor SYS; these are OS files that should be generic. It is only rilgsm.dll that is manufacturer-specific.
you are right, I corrected the post
I think I do anything wrong...
If I extract your ROM(WM 6.5 Beta 3.81) and put it together to a ROM again, it is 10MB smaller.....After extracting this, its 1MB smaller...
Question is, why?
Greets
chucknican
actually for unknown reason if you use my kitchen to build rom, you won't able to extract it properly...i am not sure why. But currently it is the only solution for me to overcome buildimgfs error
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
chucknican said:
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
Click to expand...
Click to collapse
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
benjaminries said:
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
Click to expand...
Click to collapse
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
keyx said:
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
Click to expand...
Click to collapse
So... these files go in the root folder? That's what works for me anyway. Hmm... I think this could be easily added to the script, if you ever have to release an update to the kitchen. Anyway, thanks.
21501 kitchen added on 1st post
EDITED: kitchen updated to detect missing of imgfs_raw_data.bin and extract it automatically, I also updated some tools versions
ADC and Ipaq Data Connect
Are both of these necessary? When both are installed the ADC seems to run first and configures a "Proxy Internet" Profile in the Connection Manager which lists all 3 possible connections for my data carrier, even though I can only use the internet2.voicestream.com with T-Mobile. Maybe I am not using this correctly, but once I removed the ADC, the ipaq data connection worked fine and I was able to connect to the internet without a problem. Is this all this app does, or is there another usage that I should leave it installed for?
Thank-you
you can remove ADC if you don't want it, i think it just help to setup data connections
Customization
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Where do you test the new roms? In the device or in somekind of emulator?
gkleding said:
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Click to expand...
Click to collapse
what do you mean by bsprop not installed correctly? if you convert it to OEM folder correctly it should work but if you leave the customization engine run on startup there is no point to preinstall bsprop since it will reinstall again from ipaq file store(unless you did not install the update before).
Also if you modify initflashfiles.dat i believe you should use hex editor to remove the FF FE header added by notepad.
Sometime when you flash a lot the device will act weird & does not reboot from flashing, you can try to clean boot it or reflash. I think you can remove all highlighted entries without issue. You may need to leave a blank line at the end of file though.
wmwidget is a widget engine that can run apps that use pie as a container/interface, for me it looks kinda like a shortcut to a webpage, msn weather/money .etc are the sample widget come with 6.5 for now. You can remove it if you don't use it.
SwimmerBoy said:
Where do you test the new roms? In the device or in somekind of emulator?
Click to expand...
Click to collapse
device only until i figure out the emulator issue
Hello FHM and the rest of the board members,
Could you please help me to backup my original ROM? It is a Swisscom version of S740. Maybe I need it later again... or others are interested in.
Regards
Semmelknoedel
Hey,
I have the HTC Rose from Swisscom too, please tell me if you manage to backup the rom and flash the 6.5 rom.
Thanks in advance!!!
Sadly I can't help you with your question as I'm interested in doing it too... sorry...
Dumping ROM From phone .
here is a thread on dumping rom's from a phone http://forum.xda-developers.com/showthread.php?t=616995
and some more (Dumping a rom) http://forum.xda-developers.com/showthread.php?t=334680
good read (the tools you nead) http://www.xs4all.nl/~itsme/projects/xda/tools.html
and to reconstructed the dumped rom http://forum.xda-developers.com/showthread.php?t=337066
please read the thread's , it should work on the rose to .
need a little more help
Hi ceesheim,
Posting the necessary links was very helpful for me. I was able to dump the ROM from my SwissCom S740. Now I have got the 4 RAW files.
I'm following the instruction written by dj13241. Now i faced a problem on step: "rebuild a flashable ROM from a dump" at topic 3 (Insert XIP (Part01.raw) into new-os.nb.payload). As I executed the command for the first time cmd was asking for admin-rights. OK. I have opened cmd as admin. Now I have inserted the command: implantxip Part01.raw new-os.nb.payload
An Error was shown in cmd "xip file not specified". What did I wrong? Please see also the attached snapshot.
Thanks in advance.
Semmelknoedel
First rename part01.raw to xip.bin.
Then the correct command is:
insertxip -xip xip.bin -payload new-os.nb.paylod
Thanks FHM for answering. But it doesn't work. I'm using a insertxip.bat copied from "new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder".
Content of this bat-file:
@echo off
rem echo Processing "%1"
implantxip -xip XIP_new_ported\xip.bin -payload ..\ROM\%1\OS.nb.payload
after execution of the command you mentiond in thread before, I get this error message:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
PAYLOAD: ..\ROM\-xip\OS.nb.payload not found!
XIP not Inserted!
Based on the bat-file I have inserted the folder "XIP_new_ported" and "ROM->-xip".
Where is the mistake I made?
Hi Weezphili,
here are the addresses you need:
Swisscom ROM for the Rose:
3.12M (0x31f000) Part00
3.25M (0x340000) Part01
80.38M (0x5060000) Part02
122.50M (0x7a80000) Part03
Semmelknoedel said:
Thanks FHM for answering. But it doesn't work. I'm using a insertxip.bat copied from "new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder".
Content of this bat-file:
@echo off
rem echo Processing "%1"
implantxip -xip XIP_new_ported\xip.bin -payload ..\ROM\%1\OS.nb.payload
after execution of the command you mentiond in thread before, I get this error message:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
PAYLOAD: ..\ROM\-xip\OS.nb.payload not found!
XIP not Inserted!
Based on the bat-file I have inserted the folder "XIP_new_ported" and "ROM->-xip".
Where is the mistake I made?
Click to expand...
Click to collapse
did you do this ?
"Extract XIP (Part00 and Part01 ... You will need bepe's dumpxip.exe from ervius visual kitchen):
1) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part00.raw
2) Rename XIP folder to XIP_00 (ren XIP XIP_00)
3) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part01.raw
4) Rename XIP folder to XIP_01 (ren XIP XIP_01)"
You don't need to dump the part01.raw. It's the XIP, all you need to is to rename it to xip.bin!
Put the xip.bin and the os.nb.payload (or whatever the name is you have) in the same folder as implantxip.exe!
Open an elevated CMD (Windows key + R then type in cmd) switch to the folder with the exe, bin and payload file with:
cd C:\yourfolder
then type in what I wrote above! Done
frauhottelmann said:
You don't need to dump the part01.raw. It's the XIP, all you need to is to rename it to xip.bin!
Put the xip.bin and the os.nb.payload (or whatever the name is you have) in the same folder as implantxip.exe!
Open an elevated CMD (Windows key + R then type in cmd) switch to the folder with the exe, bin and payload file with:
cd C:\yourfolder
then type in what I wrote above! Done
Click to expand...
Click to collapse
This is done, but another question: you command is "insertxip -xip xip.bin -payload new-os.nb.paylod" but there are xip.bin and the os.nb.payload and implantxip.exe and insertxip.bat in that folder. After execution of your command the same error like before:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
XIP: XIP_new_ported\xip.bin not found!
XIP not Inserted!
E:\Test>
mmh... strange!
Don't use the bat any more. Just use my command, it's the same thing, it just works
Otherwise upload the the files (raws) and I'll do it for you!
frauhottelmann said:
Don't use the bat any more. Just use my command, it's the same thing, it just works
Otherwise upload the the files (raws) and I'll do it for you!
Click to expand...
Click to collapse
You are right, the problem is the bat-file. But I couldn't find a insertxip.exe
Do you have one for me?
Uuuuups did I wrote insertxip?? My bad. I meant implantxip
Sorry
frauhottelmann said:
Uuuuups did I wrote insertxip?? My bad. I meant implantxip
Sorry
Click to expand...
Click to collapse
And also at the end of the command insertxip -xip xip.bin -payload new-os.nb.paylod -> the "a" is missing
Now it works with this command:
implantxip -xip xip.bin -payload os.nb.payload
Thanks for your help. I'm going to go the next steps...
Problems with final steps
As described in dj13241's thread the final steps are:
- Merge os-new.nb.payload into os-new.nb (nbmerge -kaiser os-new.nb)
- Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
... I don't want build a ROM for Touch Pro 2 What do I have to select in the dropdown list or shall I use FHM's Vox Rose Kitchen 2.0?
Thanks for you help.
Yes, lol my fault again. That happens when I use my laptop keyboard, I mistype a lot...
Get the TOOLs part of my kitchen then in the tools folder open the HTC ROM Tool (htcrt.exe) choose the Diamond and change DIAM***** to ROSE1000 under OS select your os-new.nb and click on build to make a nbh that you can flash.
EDIT: nbmerge -kaiser os-new.nb is the right step
frauhottelmann said:
Get the TOOLs part of my kitchen then in the tools folder open the HTC ROM Tool (htcrt.exe) choose the Diamond and change DIAM***** to ROSE1000 under OS select your os-new.nb and click on build to make a nbh that you can flash.
EDIT: nbmerge -kaiser os-new.nb is the right step
Click to expand...
Click to collapse
But there is no os-new.nb. If you read the dj13241's thread and you are looking for os-new.nb you only find it at the end of his instruction. So I guess that it is the os.nb i have extracted with command nbhextract RUU_Signed.nbh
By the way: the RUU_Signed.nbh I use is from Blackstone.. is this ok or not?
HTC ROM Tool (htcrt.exe)
FHM, what can you tell me about the SPL, Splash and Radio contents? Will this not be part of my original ROM I try to build? I think a Radio is necessary, do I also have to dump it from Rose?
...a lot of work. Thank god it's holiday...
you made only the rom ( no spl , radio , splash ) .
if you flash your new build rom you keep your old splash and your old radio (they are still on the phone ).
no need to dump them .
only when you flash a new radio or splash you could dump the old first .