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.
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.
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Code:
00_GSM.nb
01_IPL.nb
02_SPL.nb
03_MainSplash.bmp
03_MainSplash.nb
04_OS.nb
Copy 02_SPL.nb and 03_MainSplash.nb to C:\HTCRomTool and 04_OS.nb to C:\XIPPORT
ok, now we have official SPL and MainSplash ready to use but we need the OS too
To obtain exactly the original OS we need to modify some registry keys inside "boot.hv" according to our language.
This file is located in the XIP section, so we should extract the xip files from 04_OS.nb, modify boot.hv and re-inject the xip in the os.
Don't worry, we have another solution because we already have the original xip obtained from dump process ([email protected]'s wiki)
The XIP section is Part01.raw
Copy Part01.raw to C:\XIPPORT and rename it to "xip_out.bin"
Run xipport.exe, change the offset to "00313800", the filename to "04_OS.nb" (see pic01 at the end of post for detail) and press "write xip_out.bin to:"
This tool write the xip section (xip_out.bin) in the OS (04_OS.nb) at the specified address (00313800).
Now we have 04_OS.nb with our original XIP
Rename 04_OS.nb to OS.nb and copy it to C:\tadzio
Copy imgfs_raw_data.bin obtained from dump process to C:\tadzio
Open a command prompt, go in C:\tadzio and type this command:
Code:
C:\tadzio>imgfstonb imgfs_raw_data.bin os.nb os-new.nb -bigstoragemove
This tool recostructs the OS (os-new.nb) from our dumped image (imgfs_raw_data.bin)
Now we need to patch the size of OS-new.nb, to do this type this command:
Code:
C:\tadzio>bPatch.exe -1 0xFF 0x632D000 OS-new.nb
The size of patched file must be 99.1 MB (103,993,344 bytes)
Ok, our OS is ready to use!
Copy OS-new.nb to C:\HTCRomTool and run "htcrt.exe"
This tool creates and signes a .nbh file from a .nb file. I suggest you to create 2 .nbh, one for OS and Spalsh (eg. OS.nbh)
and one for SPL (eg. SPL.nbh).
Select "ROM builder" tab and fill the fields like screenshots at the end of post:
OS.nbh (see pic02 for detail)
SPL.nbh (see pic03 for detail)
Press "Build!", type the filename without extension and press "Save"
Flash OS.nbh first so if something wrong in the image and the device don't boot you'll be able to flash any other ROM; while, if it boots ok, then flash the SPL.nbh.
Copy OS.nbh to C:\RomUpdate, rename it to ruu_signed.nbh, run "ROMUpdateUtility.exe" and follow the instructions
At this point we have flashed OS and Splash, if its all ok and the device boot right, then you can flash SPL
Delete ruu_signed.nbh, copy SPL.nbh to C:\RomUpdate, rename it to ruu_signed.nbh and run "ROMUpdateUtility.exe"
That's all!! Now you have completely restored your device to its original condition.
I've tested this procedure, worked fine for me and i hope for you too
.
.
.
bye all
.
.
.
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
avathar behemoth said:
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
Click to expand...
Click to collapse
i've tried to play around this few time ago with no succes
I've configured wifi interface card throw registry hack, it appears in the network adapter list, but when i turn on wifi nothing happens...
did you use the files i posted in the wifi thread? (posted the tnetw 1251 driver and a file from the extended rom of the artemis... wifinit.exe) but kudos to you for getting a device listed in the pharos (though i looked with task manager i think in a previous rom i flashed and i saw wifi.dll or something loaded at the list of pharos devices)
poldo964 said:
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Click to expand...
Click to collapse
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
wittanny said:
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
Click to expand...
Click to collapse
oops! sorry
hi
i have not imgfs_raw_data.bin ????
when i run the romupdateutility i get error "invalid vendor id"
please help
lindows said:
when i run the romupdateutility i get error "invalid vendor id"
please help
Click to expand...
Click to collapse
you need HardSPL to flash a NON official ROM
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
fmulinacci said:
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
Click to expand...
Click to collapse
are you italian?
poldo964 said:
are you italian?
Click to expand...
Click to collapse
yes, why? do I write english so bad ?
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
fmulinacci said:
yes, why? do I write english so bad ?
Click to expand...
Click to collapse
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
Click to expand...
Click to collapse
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
poldo964 said:
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
Click to expand...
Click to collapse
ok, I got it....however my Pharos was French (a great deal, about 150€ at FNAC in Geneva...I could not let it on the shelf), and I did not back it up before upgrading....let us hope in 1 year nothing bad will happen ;-)
Hi all,
I'm looking for the official french version. Could anyone share it or tell me where i could DL it?
Thanks all.
OK, so I was asked by kevinpwhite to write up a guide on how I made a ROM with with Orange logo, so here it is.
Also, i'm sure some of this isn't needed, but I tried to be thorough. I'm not much of a guide writer so if you find this hard to follow or think its missing something, please let me know and i'll try my best to fix it.
Now before I begin, I should warn everybody that flashing unofficial software is unsafe, I followed this guide myself before posting but I can hardly guarantee safety by just using it myself.
Files Needed:
TGTool 1.3.19 - http://forum.xda-developers.com/showthread.php?t=650075
tg01_sddl+ - http://www.4shared.com/dir/18687254/7d532a3f/Windows_Phone_65.htmla
TG01WP_6.5_Orange_UK_Update - TG01WP_5005000176.tsw
TG01WP_6.5_IT_Update - TG01WP_5005030076.tsw
For ease of use, I renamed my ROM's ITA and UK respectivly, and I will be refering to them as ITA.tsw and UK.tsw in this guide.
So for starters, put your UK.tsw and ITA.tsw in the same folder with TGTool. Run 'Command Prompt', navigate to your chosen folder and then we can begin.
Step 1 - Take the English software out of the UK ROM.
Code:
tgtool -sp UK.tsw UK.nb0
Step 2- Insert that into the Italian ROM.
Code:
tgtool -mp UK.nb0 ITA.tsw TG01WP_00.tsw
Step 3 - Copy TG01_SDDL+ to your 'Storage Card' if you haven't already done so, and copy TG01WP_00.tsw into a folder named 'prg'.
Step 4 - Run TG01_SDDL+ and let it flash.
Now as far a I can tell, this only removes the Orange logo from bootup, it still has an Orange logo on shutdown and still contains all Orange apps and settings. So you will still also need to follow kevinpwhite's "Soft De-Brand Procedure" to remove the majority.
Da Mafia - thank you very much - practically an instant response !
I can follow the logic now and think I understand this process better. The next will be to try doing it....carefully
Do you think any more steps can be taken beyond wrapping elements of one ROM within the shell of another or does that then immediately get into the realms of 'proper' cooking such as the experts are currently grappling with ?
I don't know of any easy way to make further modifications, so anything more than this will need a 'proper' cook. I've tried to look into this myself but the TG01 is my first Windows Mobile phone so I have no experience and don't know how much of the guides for other phones transfer to the TG01.
Hmm.. I've just tried the process and am getting an error message
" Upgrade image not found, copy an image to 'prg' folder of the storage card."
The TG01WP.tsw file generated OK (apparently) and I have copied to the prg folder (file size is identical to original).
View attachment 300061
To be repeated tomorrow
TG01WP_00.tsw
Thats what was wrong. Will update the first post.
thank you da mafia that's brilliant
i got this far
but i'm going to wait till tomorrow, as it's a bit late to start a new adventure
TGTool v1.3.19 copyright(c) 2010 cedesmith
Checking ITA.tsw complete
Creating TG01WP.tsw complete
Checking TG01WP.tsw has completed without warnings
Da Mafia said:
TG01WP_00.tsw
Thats what was wrong. Will update the first post.
Click to expand...
Click to collapse
Many thanks for the amendment. I am pleased to report that I have now succeeded with the re-flash.
One additional point to mention - changing the filename of the output .tsw file did NOT work. It was necessary to re-generate with the correct filename structure - evidently cedesmith's TGTool does something internally with that information.
View attachment 300191
Initial Toshiba splash screen, then few seconds dark period and then the normal Windows orange-coloured screen cal screen. Following the full 'soft-debrand procedure', apart from the residual .cab and other files dormant in the ROM \windows, etc. the device is now as 'clean' as I suspect is possible.
Brilliant stuff Da Mafia - thank you for taking the first 'great leap' !
Brilliant stuff cedesmith - thank you for providing the TGTool. I am sure that it will lead to much greater things, but even this apparently modest step needs to be seen as really significant
Next question is how can the UK OS Payload .nb0 file be filleted to remove the unwanted .cabs, etc.....
On a second tack, I have made a Registry archive post-debrand using CeRegEditor, but at present cannot figure how to be able to write that back to the device on top of the original Registry. Does anyone reading this have any expertise with that side of things they can share please ?
morning guys,
YES
this method worked great
to confirm what Da Mafia & Kevin have said...
this mod will basically re-create your standard oragnge phone - but with no orange boot up screen
sensational - can't thank you both enough
cheers
Adam
I guess I have a method to avoid orange cab's to install at all. But here is nothing sure at all... I'm flashing a working ROM now because i have to leave. I failed so many times flashing a 6.5.5 non bootable (im starting to get used to the pin method lol). By the way, I would work faster if you can tell me if that procedure works properly once I come back to house:
Code:
tgtool -sp tg01uk.tsw tg01.os.nb.payload
osnbtool -d tg01.os.nb.payload 2 imgfs.bin
imgfstodump imgfs.bin
imgfsfromdump imgfs.bin imgfs-new.bin
osnbtool -c tg01.os.nb.payload 2 imgfs-new.bin
tgtool -mp tg01.os.nb.payload.new tg01uk.tsw tg01uk-new.tsw
If it works I'm 90% sure I can build a debranded 6.5.0 ROM.
adzman808 said:
morning guys,
YES
this method worked great
to confirm what Da Mafia & Kevin have said...
this mod will basically re-create your standard oragnge phone - but with no orange boot up screen
sensational - can't thank you both enough
cheers
Adam
Click to expand...
Click to collapse
Hi Adam,
Glad you have been successful too ! I've now pasted in the Welcomehead and Shutdown screens and just soft reset a few times in the course of installing various basic software ... whole effect is just what was needed !
arag0n85 said:
I guess I have a method to avoid orange cab's to install at all.
Click to expand...
Click to collapse
I've not had time to absorb the detail of each step you've suggested....but could you please clarify which action will prevent the .cabs installing ? And is it simply to stop the auto-installer (same as editing the Registry pre-boot) or is it actually removing the .cabs from the payload completely ?
Sorry if a dim question, but feeling my way here !
kevinpwhite said:
I've not had time to absorb the detail of each step you've suggested....but could you please clarify which action will prevent the .cabs installing ? And is it simply to stop the auto-installer (same as editing the Registry pre-boot) or is it actually removing the .cabs from the payload completely ?
Sorry if a dim question, but feeling my way here !
Click to expand...
Click to collapse
Well, none of the steps I posted avoids the installation of cab's. It just unpacks and repacks the payload. If this simple steps works, I have located the cab files and registry pre-boot places that I need to edit.
So, I just need someone to test if the simple unpack-repack procedure builds a bootable rom. I will be out of house until tomorrow morning I guess and it's going to be faster to have someone testing it before I come back.
Also, If someone wants to try, just use the attached initflashfiles.dat and see what happens. It won't remove the cabs but I think it will avoid most of the Orange installations.
Originally Posted by arag0n85
... just use the attached initflashfiles.dat and see what happens.
Click to expand...
Click to collapse
Again sorry to be dim... how does one run the .dat you posted ? Does this need to be inserted pre-boot or is it run post-boot ?
nail varnish remover, some cotton buds, a small flat blade screwdriver & patience...
...and you can kiss goodbye to the orange logo on the back too !!
Cheers
kevinpwhite said:
Again sorry to be dim... how does one run the .dat you posted ? Does this need to be inserted pre-boot or is it run post-boot ?
Click to expand...
Click to collapse
you need to replace the .dat file on the dump directory after the instruction:
imgfstodump imgfs.bin
arag0n85 said:
I guess I have a method to avoid orange cab's to install at all. But here is nothing sure at all... I'm flashing a working ROM now because i have to leave. I failed so many times flashing a 6.5.5 non bootable (im starting to get used to the pin method lol). By the way, I would work faster if you can tell me if that procedure works properly once I come back to house:
Code:
tgtool -sp tg01uk.tsw tg01.os.nb.payload
osnbtool -d tg01.os.nb.payload 2 imgfs.bin
imgfstodump imgfs.bin
imgfsfromdump imgfs.bin imgfs-new.bin
osnbtool -c tg01.os.nb.payload 2 imgfs-new.bin
tgtool -mp tg01.os.nb.payload.new tg01uk.tsw tg01uk-new.tsw
If it works I'm 90% sure I can build a debranded 6.5.0 ROM.
Click to expand...
Click to collapse
I've just done this and flashed fine.
It looks like imgfstodump doesn't dump everything, my rebuilt imgfs is nearly 20MB smaller, also I cannot see initflashfiles.dat to replace, but still the phone flashed OK and is working.
Da Mafia said:
I've just done this and flashed fine.
It looks like imgfstodump doesn't dump everything, my rebuilt imgfs is nearly 20MB smaller, also I cannot see initflashfiles.dat to replace, but still the phone flashed OK and is working.
Click to expand...
Click to collapse
It may be also because the compresion of the payload it's diferent,I don't think it's because rubish in the payload, but well, if that's the case it's also welcome.
The initflashfiles.dat that i posted should be placed into the dump directory after the imgfstodump process. It should avoid the installation of orange maps, video player and other orange stuff. If it works then I just need to delete the files from the dump directory before rebuilding and voila, a debranded 6.5 payload.
Right, it turns out initflashfiles.dat was actually there, i'd just overlooked it. So i've flashed again using yours and again, working fine.
Da Mafia said:
Right, it turns out initflashfiles.dat was actually there, i'd just overlooked it. So i've flashed again using yours and again, working fine.
Click to expand...
Click to collapse
did you find any diferences?
I can't say for sure, but it looks like there is a tab missing from the Orange Homescreen, I don't normally use it so could be wrong, and I think the Orange Maps shortcut from the menu has gone too.
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 .