Notes:
- XIP porting doesn't work but you can fix that by using a premade XIP as written in the instructions (thanks for ffboy2009 for testing this fix!)
Steps to set up the kitchen:
1. Unpack the osKitchen archive
2. Launch osKitchen and import the TSW file for your device (use the "Toshiba TG01" name and tell it you want to continue when it says it's unrecognized)
3. Go into the Sources\Devices\Toshiba TG01\Profiles\OEMXIPKernel, delete the NK.exe folder and put the NK.EXE from LEO I've attached to this post
4. Go in the kitchen "advanced tweaks" page and in the "OS Sections" select the XIP.bin you have ported or taken from another ROM (remember to match the modules in the XIP you're using with the ones platformrebuilder generates, if the modules aren't the same stuff may break)
5. Happy cooking!
The XIP.bin files have to be generated only when you change something in the xip (which usually never happens unless if you integrate to use extenddir) or when you change windows mobile build. If somebody wants to share their XIPs for different wm builds I will link them there so anybody will be able to cook without having to use xipport by hand.
Update: osKitchen RC18 is available in the oskitchen thread
thx!
great
i will test this!
Hi bro.
This method Unbrick TG01??
Nokser said:
Hi bro.
This method Unbrick TG01??
Click to expand...
Click to collapse
No, it's a version of osKitchen that (if it works) supports cooking ROMs for the TG01.
airxtreme said:
No, it's a version of osKitchen that (if it works) supports cooking ROMs for the TG01.
Click to expand...
Click to collapse
You did it.
Congratulations
airxtreme said:
- Oh yes, there will be bricks! - (Jigsaw, talking about the new osKitchen for TG01!)
Notes:
- Nobody has tested this yet, I don't know if it will work because platformrebuilder could have trouble with some OEM modules (but you're free to try to find out which one is causing issues) and I don't have a TG01 to try. Always make sure everything is fine before flashing.
- XIP porting doesn't work, you have to port your own XIP or take a XIP.bin from another ROM (use TGTool -sn to get the OS.nb, use nbimagetool on the OS.nb to get the xip.bin).
Steps to set up the kitchen:
- Unpack the osKitchen archive
- Launch osKitchen and import the TSW file for your device (use the "Toshiba TG01" name and tell it you want to continue when it says it's unrecognized)
- Go into the Sources\Devices\Toshiba TG01\Profiles\OEMXIPKernel, delete the NK.exe folder and put the NK.EXE from LEO I've attached to this post
- Go in the kitchen "advanced tweaks" page and in the "OS Sections" select the XIP.bin you have ported or taken from another ROM
- Happy cooking!
Click to expand...
Click to collapse
confused
to brick or unbrick?
mfkiwl said:
confused
to brick or unbrick?
Click to expand...
Click to collapse
It was a joke, because there's a considerable chance (I'd say 50%) adding TG01 support to osKitchen has been useless and would only result in unbootable ROMs but there's always hope: platformrebuilder works on many non-HTC devices except for the XIP part (that the kitchen adds separately).
Also even if it doesn't work Da_G is adding relocation and XIP rebuilding to libnb and with that I'll be able almost for sure to get working ROMs for the TG01 probably in a months or so.
ffboy2009 said:
thx!
great
i will test this!
Click to expand...
Click to collapse
Let me know if it works. I have added BIN rebuilding too so you can try working on S200 ROMs too.
BTW remember to check the file with TGTool etc to make sure it's 100% valid. I don't really want to feel responsible for real bricks
airxtreme said:
Let me know if it works. I have added BIN rebuilding too so you can try working on S200 ROMs too.
BTW remember to check the file with TGTool etc to make sure it's 100% valid. I don't really want to feel responsible for real bricks
Click to expand...
Click to collapse
i have tried this 1.27RC7
crashed while building TG01 and S200 rom..even i didn't do any changes with orgi import rom file.
but import rom works well!
i think there may problems really with prb and non htc device
Also,i think ur work is really great!
I wonder if u can add universal support with buildos+extreloc in ur OSK?
i can share my batch files of s200 and tg01
thx for ur great job!
airxtreme said:
- Oh yes, there will be bricks! - (Jigsaw, talking about the new osKitchen for TG01!)
Notes:
- Nobody has tested this yet, I don't know if it will work because platformrebuilder could have trouble with some OEM modules (but you're free to try to find out which one is causing issues) and I don't have a TG01 to try. Always make sure everything is fine before flashing.
- XIP porting doesn't work, you have to port your own XIP or take a XIP.bin from another ROM (use TGTool -sn to get the OS.nb, use nbimagetool on the OS.nb to get the xip.bin).
Steps to set up the kitchen:
- Unpack the osKitchen archive
- Launch osKitchen and import the TSW file for your device (use the "Toshiba TG01" name and tell it you want to continue when it says it's unrecognized)
- Go into the Sources\Devices\Toshiba TG01\Profiles\OEMXIPKernel, delete the NK.exe folder and put the NK.EXE from LEO I've attached to this post
- Go in the kitchen "advanced tweaks" page and in the "OS Sections" select the XIP.bin you have ported or taken from another ROM (remember to match the modules in the XIP you're using with the ones in the OEMXIPKernel folder of the kitchen, if the modules aren't the same stuff may break)
- Happy cooking!
Update: added osKitchen v1.26RC7
Click to expand...
Click to collapse
nice job!!!!
ffboy2009 said:
i have tried this 1.27RC7
crashed while building TG01 and S200 rom..even i didn't do any changes with orgi import rom file.
but import rom works well!
i think there may problems really with prb and non htc device
Also,i think ur work is really great!
I wonder if u can add universal support with buildos+extreloc in ur OSK?
i can share my batch files of s200 and tg01
thx for ur great job!
Click to expand...
Click to collapse
If you put the NK.EXE I attached as I wrote in the istructions platformrebuilder won't crash but as I said in the other thread the problem is making sure the XIP is built properly with the same structure of the one inside oskitchen
airxtreme said:
If you put the NK.EXE I attached as I wrote in the istructions platformrebuilder won't crash but as I said in the other thread the problem is making sure the XIP is built properly with the same structure of the one inside oskitchen
Click to expand...
Click to collapse
OK,i will try and report!
anyway,do i have to edit NK.EXE with s200 too?
thx
ffboy2009 said:
OK,i will try and report!
anyway,do i have to edit NK.EXE with s200 too?
thx
Click to expand...
Click to collapse
If the phone runs wm6.5 you can use the same NK but if you don't know how to do xip porting or matching the XIP modules I suggest you to give up because even a single misplaced module can make the rom unbootable, you need to know how platformrebuilder and xip porting works to get a XIP that is good to use.
airxtreme said:
I can:
- add proper osKitchen support for the device even in the remote worst case scenario where platformrebuilder won't work at all
- release a clean wm6.5.5 kitchen to allow building ROMs for all the available languages (I have released ROMs in 19 different languages for the Toshiba G900 http://www.portegeclub.com/forum/viewtopic.php?p=24434 and still have the tools to help me localizating and to sorting OEMMisc Apps in EXT) so anybody can easily start developing ROMs for the TG01 and put anything inside since oskitchen perfectly handles multilanguage ROMs and is almost idiotproof
But, if the TG01 dies so easily as I read, (with the battery disconnecting enough to permanently brick the device) I don't really want to take any responsibility.
Click to expand...
Click to collapse
It doesn’t dies so easily. I am asking you on behalf of everyone here, including maintenance of TG01 in osKitchen.
i finally make this work for TG01 and S200
pacth the nk.exe u posted
import the official roms,porting xip my self by extreloc
and now,i can run WM 21904 on TG01
thx,if u want to change to extreloc,maybe i can help
ffboy2009 said:
i finally make this work for TG01 and S200
pacth the nk.exe u posted
import the official roms,porting xip my self by extreloc
and now,i can run WM 21904 on TG01
thx,if u want to change to extreloc,maybe i can help
Click to expand...
Click to collapse
There is something I don't understand: isn't extreloc only for IMGFS? How did you use that to port the XIP?
airxtreme said:
There is something I don't understand: isn't extreloc only for IMGFS? How did you use that to port the XIP?
Click to expand...
Click to collapse
extreloc can port xip too!
see this:
Code:
:MENU
cls
ECHO. =-=-=-=-=XIP Porting=-=-=-=-=
ECHO.
ECHO. 1 Use MSXIPKernel porting xip!
ECHO. 2 Use new xip.BIN to porting xip
ECHO. 3 Countinue
ECHO.
ECHO. =-=-=-=-=XIP Porting=-=-=-=-=
echo. Select say to XIP PORTING:
set /p ID=
if "%id%"=="1" goto cmd1
if "%id%"=="2" goto cmd2
if "%id%"=="3" goto cmd3
PAUSE
:cmd1
del xip_out.bin
cls
echo Use MSXIPKernel porting xip!
echo Press“OK” when showing erro windows
@echo off
title XIP AUTO REPLANTING KITCHEN PROVIDED BY EXTReloc
IF NOT EXIST XIPNEW\MSXIPKernel ECHO NO MSXIPKernel IN CURRENT DIRECTORY!&PAUSE&EXIT
IF EXIST TOOLS\PACKAGE\MSXIPKernel RD /S /Q TOOLS\PACKAGE\MSXIPKernel>nul
XCOPY /y /h /r /k /e /Q /i XIPNEW\MSXIPKernel TOOLS\PACKAGE\MSXIPKernel>nul
START "" /B /WAIT "TOOLS\buildxip.bat"
::===============================================================================
CD TOOLS
IF EXIST OUT RD /S /Q OUT
IF EXIST OUT-NEW RD /S /Q OUT-NEW
IF EXIST xip_out.bin del xip_out.bin>nul
title 1.DUMPING AND PACKAGEING NEW xip.bin ...
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
DEL xip.bin>NUL
ren OUT OUT-NEW
::===============================================================================
title 2.DUMPING AND PACKAGEING LOCOLE xip.bin ...
ren my.xip.bin xip.bin
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
ren xip.bin my.xip.bin
::===============================================================================
title 3.COPYING FILES AND MODULES ...
rd /s /q OUT\FILES\MSXIPKernel>nul
rd /s /q OUT\MODULES\MSXIPKernel>nul
XCOPY /y /h /r /k /e /Q /i OUT-NEW\FILES\MSXIPKernel OUT\FILES\MSXIPKernel 1>nul 0>nul
XCOPY /y /h /r /k /e /Q /i OUT-NEW\MODULES\MSXIPKernel OUT\MODULES\MSXIPKernel 1>nul 0>nul
RD /S /Q OUT-NEW
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "undo" /kill
FOR /F "eol=; delims==" %%i in (Remove.ini) do (
IF EXIST %%i\* RD /S /Q %%i
IF EXIST %%i DEL /f %%i>nul 0>nul
)
::===============================================================================
title 4.RELOCING MODULES WITH EXTReloc ...
cd..
[COLOR="red"]TOOLS\EXTReloc.exe -dX.\TOOLS -d.\SYS -l -DllLo -relDLL -WM65[/COLOR]
cd TOOLS
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "realloc P" /clickbutton "write maps" /kill
cd..
[COLOR="red"]TOOLS\EXTReloc.exe -dX.\TOOLS -d.\SYS -relNK -WM65[/COLOR]
cd TOOLS
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "realloc P" /clickbutton "write maps" /clickbutton "build xip_out.bin" /kill
MOVE /y xip_out.bin ..\xip_out.bin
cd..
GOTO MENU
:cmd2
del xip_out.bin
cls
echo Use new xip.BIN to porting xip
echo Press“OK” when showing erro windows
@echo off
title XIP AUTO REPLANTING KITCHEN PROVIDED BY EXTReloc
IF NOT EXIST XIPNEW\xip.bin ECHO NO xip.bin IN CURRENT DIRECTORY!&PAUSE&EXIT
COPY /Y XIPNEW\xip.bin TOOLS\xip.bin>NUL
CD TOOLS
IF EXIST OUT RD /S /Q OUT
IF EXIST OUT-NEW RD /S /Q OUT-NEW
IF EXIST xip_out.bin del xip_out.bin>nul
title 1.DUMPING AND PACKAGEING NEW xip.bin ...
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
DEL xip.bin>NUL
ren OUT OUT-NEW
title 2.DUMPING AND PACKAGEING LOCOLE xip.bin ...
ren my.xip.bin xip.bin
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
ren xip.bin my.xip.bin
title 3.COPYING FILES AND MODULES ...
rd /s /q OUT\FILES\MSXIPKernel>nul
rd /s /q OUT\MODULES\MSXIPKernel>nul
XCOPY /y /h /r /k /e /Q /i OUT-NEW\FILES\MSXIPKernel OUT\FILES\MSXIPKernel 1>nul 0>nul
XCOPY /y /h /r /k /e /Q /i OUT-NEW\MODULES\MSXIPKernel OUT\MODULES\MSXIPKernel 1>nul 0>nul
RD /S /Q OUT-NEW
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "undo" /kill
FOR /F "eol=; delims==" %%i in (Remove.ini) do (
IF EXIST %%i\* RD /S /Q %%i
IF EXIST %%i DEL /f %%i>nul 0>nul
)
title 4.RELOCING MODULES WITH EXTReloc ...
cd..
[COLOR="red"]TOOLS\EXTReloc.exe -dX.\TOOLS -d.\SYS -l -DllLo -relDLL -WM65[/COLOR]
cd TOOLS
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "realloc P" /clickbutton "write maps" /kill
cd..
[COLOR="Red"]TOOLS\EXTReloc.exe -dX.\TOOLS -d.\SYS -relNK -WM65[/COLOR]
cd TOOLS
xipport\AutoExecAndClick.exe /launch "xipport\XIPPort.exe" /clickbutton "realloc P" /clickbutton "write maps" /clickbutton "build xip_out.bin" /kill
MOVE /y xip_out.bin ..\xip_out.bin
cd..
GOTO MENU
ffboy2009 said:
extreloc can port xip too!
see this:
Click to expand...
Click to collapse
Oh well, as long as you can reuse the same xip.bin without ever having to relocate it again (unless you change windows mobile build) it should be fine then.
airxtreme said:
There is something I don't understand: isn't extreloc only for IMGFS? How did you use that to port the XIP?
Click to expand...
Click to collapse
If you want I have a good working WMRelock for TG01 ROM structure, IMGFS etc...
Nokser said:
If you want I have a good working WMRelock for TG01 ROM structure, IMGFS etc...
Click to expand...
Click to collapse
I don't want to add other tools for xip relocation because they all require XIPPort that is a very annoying program. I'm waiting to find a xipport replacement or for Da_G to finish xip relocation of NB
Related
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.
hi
i have a problem when io build OS, the boot rgu file has this lines wrong:
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome]
"SK1TEXT"="Contatti"
"ExtensibilityXML"="<PluginsOrder=\"CMyPhotos;CMusic;CWelcomeCenter;CPhone;CVoicemail;CClock;CText;CEmail;CAppointments;CHomeFavs;CWindowsLive\"
CPRFileName=\"Titanium\" DisplayStyle=\"Titanium\" />"
"SK1URL"=":MSCONTACTS"
"HomePluginGuid"="{892B90CB-9806-427e-8BED-F45C6A9E576B}"
"DockOperatorBar"=dword:0 "Enabled"=dword:0
Click to expand...
Click to collapse
do some one know how the good sintax?
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome]
"SK1TEXT"="Contatti"
"ExtensibilityXML"="<PluginsOrder=\"CMyPhotos;CMus ic;CWelcomeCenter;CPhone;CVoicemail;CClock;CText;C Email;CAppointments;CHomeFavs;CWindowsLive\"
CPRFileName=\"Titanium\" DisplayStyle=\"Titanium\" />"
"SK1URL"=":MSCONTACTS"
"HomePluginGuid"="{892B90CB-9806-427e-8BED-F45C6A9E576B}"
[B]"DockOperatorBar"=dword:0
"Enabled"=dword:0[/B]
imho, just enter. and enter at end.
Why do you have CHome registry keys in your boot.rgu? They don't need to be in there-they should be built into the system.hv, not the boot.hv.
nvmd...
,
Farmer Ted said:
Why do you have CHome registry keys in your boot.rgu? They don't need to be in there-they should be built into the system.hv, not the boot.hv.
Click to expand...
Click to collapse
i'm newbe, i exctracted the boot.rgu file with this command:
mkdir ROM
cd ROM
mkdir XIP
cd ./../..
set _FLATRELEASEDIR=.
echo REGEDIT4 > dump/ROM/XIP/boot.ascii
rgucomp.exe -o dump/default.hv -nologo >> dump/ROM/XIP/boot.ascii
stringconverter.exe dump/ROM/XIP/boot.ascii dump/ROM/XIP/boot.rgu /unicode
del dump\ROM\XIP\boot.ascii
isn't good?
I can't answer that, but I can tell you that in any build, the CHome reg keys are in the sys#/shared/common/CHome rgu (8c58193c-f8ab-447a-af67-a5167df96529.rgu). You may have messed up and dumped the whole registry or something, but you probably shouldn't have that reg key in your boot.rgu.
OK thanku for your interesting....
another question, why do my phone tell me chekscum error when i try to fash the rom craeted by me?
I used wmreloc on a dump build with OSbuild.exe and a xip made with xipkitchen
i have an Acere e101 and around i can not find anything about him, i trying to use the evirusVK but i have only flash.bin file... evirusVK want a nbh file....
up up
please someone who can explane me why after i flash the final rom i got always chekskum error?
i used build OS, wmreloc and osnbtool to build the rom...... I saw that the xip file ported with xipkitchen, is smaller than the the original and boot.rgu file i axtracted with the commands wrote up, is bigger then 1000 kb. why?
Dunno, but 1 MB is way too big for the boot.rgu. That sounds like an .rgu dumped from the system.hv. If you get a stock boot.rgu, it's about 32 KB, but if you dump it from a boot.hv, it may only be 10-12 kb (there's some redundant stuff in the original boot.rgu as well as all of the developer comments). I can't tell you what you're doing wrong, but you're definitely doing something wrong. Sorry I can't be more helpful.
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 .
Hello everyone I have a small issue here hope someone knows how to fix it or if someone had this error before what did you do to fix it??
Well Im Using Ervius kitchen and it was working fine, I'm able to cook with SYS 21901 but if I want to do an upgrade and use something else like 23563, 24611 or others it gives me this error: -1073741819
This error usually comes up when I hit the create rom button, but at first everything looks fine but in the middle of the process it tells me that RomKitchenExecutable and Imgfsfromdump.exe are not responding and it just shut down.
Thanks to everyone in advance
hi,
check this reply from twopumpchump: from this thread
twopumpchump said:
michal_banszel said:
Actually I always got error:
ERROR! (errorlevel: -1073741819)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
What is more... some files in my kitchen f.g. erviuskitchen.exe is now... hidden It has changed itself. And I'm not able to change it all exe files in my main folder (PagePool Changer 2.21.exe and nueSpinLockPatcher.exe) and S00x files in my ROM folder changed into hidden. With no reason. It happend first time to me and don't know why??
Click to expand...
Click to collapse
have you edited your kitchen_build_rom.bat? the files didnt change attribute by themselves i dont think, im guessing you may have edited your bat file to give hidden attribute to your dump and possibly didnt do it right. having the attributes changed to hidden in some files will cause platformrebuilder to crash. maybe try using ervius's bat unedited and unhiding all the files you said you werent able to change the hidden attribute, but you can with the unhide.bat i posted a few pages back. again im just guessing, maybe it will help.
Click to expand...
Click to collapse
lion75y said:
Hello everyone I have a small issue here hope someone knows how to fix it or if someone had this error before what did you do to fix it??
Well Im Using Ervius kitchen and it was working fine, I'm able to cook with SYS 21901 but if I want to do an upgrade and use something else like 23563, 24611 or others it gives me this error: -1073741819
This error usually comes up when I hit the create rom button, but at first everything looks fine but in the middle of the process it tells me that RomKitchenExecutable and Imgfsfromdump.exe are not responding and it just shut down.
Thanks to everyone in advance
Click to expand...
Click to collapse
regards,
mike
This solution didn't help, I did edit the .bat file but only to change the device name, and add REM to the line specified and still it gives me that those programs from the kitchen have stop working or not responding and it stops the process.
where did you get your new SYS???
is from PPCkitchen format?
download another pkg diferente source...
post your build log
+ Que PPC said:
where did you get your new SYS???
is from PPCkitchen format?
download another pkg diferente source...
post your build log
Click to expand...
Click to collapse
the new SYS I have been obtaining them from these page
http://forum.ppcgeeks.com/showpost.php?p=1710334&postcount=55
also the SYS from our friend NRGZ28 doesnt work for me it gives me the same error and keeps telling me that those applications from the kitchen are not responding ( or Crash) but its weird because I can cook with 21901 but I cannt add or if I select another SYS it gives me the error.
http://forum.xda-developers.com/showthread.php?t=650783
P.S. On the build lod it shows that is missing alot of modules and files and thats because at that moment is when it gives me the warning that the romkitchenexecutable.exe and imgfsfromdump.exe are not respnding
mmmm
weird did you check that modules are fine?
i suggest you to use the PPC kitchen file attribs.. i will post them at night to edit the bat.. so the kitchen will be ready to accept PPCkitchen attribs SYS
Ok Thanks I will be waiting bud. I will keep messing with it, and reading to see if I can find the answer to this issue now.
Insert the following as third line into the kitchen_build_rom.bat:
Code:
attrib -a -r -h -s /s
so the kitchen_build_rom.bat reads like this:
Code:
@echo off
cd..
attrib -a -r -h -s /s
REM........................
set IMGSTART=0
set ULDR=ULDR
.
.
.
Do not fiddle around with attributes anywhere else ...
cheers
Cool thanks i forgot this totally
vogonj said:
Insert the following as third line into the kitchen_build_rom.bat:
Code:
attrib -a -r -h -s /s
so the kitchen_build_rom.bat reads like this:
Code:
@echo off
cd..
attrib -a -r -h -s /s
REM........................
set IMGSTART=0
set ULDR=ULDR
.
.
.
Do not fiddle around with attributes anywhere else ...
cheers
Click to expand...
Click to collapse
Thanks, Am testing right now to see if this solves the issue.
Found the answer to my problem, I just needed to add the EXT packages for 6.5 and 6.5x . I was using the same ones that the kitchen created when I dump the rom. I found this out by doing alot of tests between a good kitchen already set up and mine ...
Can someone provide me the link to obtain a clean set of EXT packages for Rhodium and that are 6.5 and 6.5x plz
That my friend is hard... so hard... and the PKGS hunt is a task that we must to do by ourselves you know.... if you search as "Tachi phone canvas EXT PKG" you will find something interesting like a thread with the cab.. so you need to convert it... then maybe in the same or another post or thread there is the OEM and you need to transform it to EXT there arent all full of EXT PKGS repository you know... thats the Cooking world bud search for ressolution too
Thanks
Just to let everyone know I also found out that on my dumped EXT files from my stock rom the GlobalSmartDialing makes the Ervius Kitchen to crash if you erase them or make them NOT to be inlcuded in the rom will solve the issue.
only new ext-pkg's to a other kitchen (language import support is coming...).
a friend of mine wrote a little bat-file for me and i want to share it with you.
the creator insisted to call it bloody rudimentary but i think it's quite useful.
he wants to stay anonymous...
around two hours of brainwork (i remember the command for this... what was it again?) and notepad.exe to create this from scratch.
you only need to adjust the two paths at the beginning.
the batch searches for same packets (exact name matches) and ignores them.
a txt will pop up showing only the new packages.
you can edit this list (only delete pks but don't change entries).
save and close after you removed the lines you don't want to import.
batch will create a temp workfolder in c: (it will pop up once copying is finished).
at this point you can rename the folders (add *_photon_1.36 at the end for example)
and add missing language sub-folders.
if you are done, press any key at the cmd window and all the edited/renamed package folders will be moved to the ext-folder in the destination kitchen (_NewPackages folder).
example (if you want to update only new ext from 1.36 into 1.11 kitchen):
-kitchen1 (source kitchen) photon 1.36 htc
-kitchen2 (destination kitchen) photon 1.11 vodafone
tested and working with oskitchen1.31beta10 file-/folder-structure.
take this code and save it into a txt file. rename it to *.bat and adjust the paths.
Code:
@echo off
REM ------- EDITABLE SECTION
SET L_SOURCEPATH="[COLOR="Red"]X:\osKitchen Zero v1.31beta10_1.36SOURCE\Sources\Devices\HTC HD Mini\EXT Packages\HTC HD Mini Packages\[/COLOR]"
SET L_TARGETPATH="[COLOR="Red"]X:\osKitchen Zero v1.31beta10_1.11DESTINATION\Sources\Devices\HTC HD Mini\EXT Packages\HTC HD Mini Packages\[/COLOR]"
REM ------ END
SET L_WORKPATH=C:\SCRWORK
MKDIR %L_WORKPATH%
SET SCRFILE=%L_WORKPATH%\packets_source.txt
SET TGTFILE=%L_WORKPATH%\packets_target.txt
SET ACTFILE=%L_WORKPATH%\PKG2COPY.TXT
del %ACTFILE%>nul
CD %L_SOURCEPATH%
DIR /B>%SCRFILE%
CD \
CD %L_TARGETPATH%
DIR /B>%TGTFILE%
CD \
FOR /F "delims=" %%I IN (%SCRFILE%) DO (
REM <--------------------------------------------------------------
REM insert logic here to select packages i.e. package numbers
FINDSTR /C:"%%I" %TGTFILE%>nul&& ECHO Exact name match. || ECHO "%%I">>%ACTFILE%
REM insert some better logic here duh!
REM <--------------------------------------------------------------
)
CLS
ECHO !!!! Remove packages you dont want to copy from list but RETAIN LINE FORMAT !!!!
ECHO !!!! Save and close List to continue!!!!
start /w notepad %L_WORKPATH%\PKG2COPY.TXT
REM hier: Collect packages based on pkg2copy.txt
CD %L_SOURCEPATH%
FOR /F "delims=" %%I IN (%ACTFILE%) DO (
xcopy /E /Y /H /I %%I %L_WORKPATH%\PRECOPY\%%I
)
CLS
ECHO !!!!Edit Folders now!!! Add langs etc.. press any key to continue and copy edited folders to destination (_NewPackages)
REM <--------------------------------------------------------------
REM i.E. delete... rename....
explorer %L_WORKPATH%\PRECOPY\
REM automate it duh!
pause
REM <--------------------------------------------------------------
REM !!! ACTION - Copy from Precopy to Target Folder (Targetpath\_NewPackages)
xcopy /E /H /Y /I %L_WORKPATH%\PRECOPY\*.* %L_TARGETPATH%\_NewPackages\
rmdir /s /q %L_WORKPATH%
explorer %L_TARGETPATH%
CD \
tested now with ervius visual kichen.
works. hope y'all enjoy this batch file...
please leave a "thanks" if you like and use it.
thanks
wow this tool is awesome, its amazing how a simple batch file created by notepad can do so much functionality..
gonna use this right now
thanks..
my opinion:
many xda-chef's would use it if they would know about it's existence..
please help me to keep this thread alive so all chefs can see it better...
tell your favorite chefs to take a look at this thread. thanks.
Wow, the time this is going to save me! (^^,) I haven't used it yet but I'm pretty sure I will. Thanks bro!
enjoy......
I didnt try it yet but sounds like a very life saver tool, got one week sticky for let other chefs to check it.
Thanks for sharing.
@ mods: i will take care of unsticky it @ 04 August.
I'm sorry but I've read the intro 3 times and still don't know what it does.
As i said ,i didnt try it yet but for what i understood it updates packages in your EXT folder,example:
You have a 2.14 Leo Kitchen and you want update only NEW EXT packages from 3.04.
Laurentius26 said:
I'm sorry but I've read the intro 3 times and still don't know what it does.
Click to expand...
Click to collapse
feel free to test it. no harm done.
source and destination folders stay untouched.
only the (not exact name match - packets that aren't already in the destination kitchen) packets you don't delete from the pop-up list will be copied to the destination kitchen ext folder (_NewPackages subfolder).
I will give it a shot when I'm back from holiday mate.
Thanks for sharing with us.
HD2Owner said:
feel free to test it. no harm done.
source and destination folders stay untouched.
only the (not exact name match - packets that aren't already in the destination kitchen) packets you don't delete from the pop-up list will be copied to the destination kitchen ext folder (_NewPackages subfolder).
Click to expand...
Click to collapse
wauw!!! works great man!!! perfect! now the only thing is we need to automate copying lang files from an other folder... hihi
kurniawan77 said:
wauw!!! works great man!!! perfect! now the only thing is we need to automate copying lang files from an other folder... hihi
Click to expand...
Click to collapse
You mean for SYS?
seeM_ZA said:
You mean for SYS?
Click to expand...
Click to collapse
i guess he means lang folders for ext-packages since this tool has nothing to do with sys.
it's possible but it would require a more advanced detection logic.
seeM_ZA said:
You mean for SYS?
Click to expand...
Click to collapse
Nah... not that much work...
Unfortunately, my kitchen is setup in a way that would prevent this from working, but this seems like a great idea.
Thanks for sharing!
HD2Owner said:
my opinion:
many xda-chef's would use it if they would know about it's existence..
please help me to keep this thread alive so all chefs can see it better...
tell your favorite chefs to take a look at this thread. thanks.
Click to expand...
Click to collapse
This is all nice and cool.. but what happened to porting your packages MANUALLY and actually looking at them before you put them in your kitchen ? You can't tell me this is how you cook a ROM... you run this batch file and blindly move over "newer" packages to your kitchen ? Wow... I believe packages need to be looked over and brought it one by one to insure compatibility first.
NRGZ28 said:
This is all nice and cool.. but what happened to porting your packages MANUALLY and actually looking at them before you put them in your kitchen ? You can't tell me this is how you cook a ROM... you run this batch file and blindly move over "newer" packages to your kitchen ? Wow... I believe packages need to be looked over and brought it one by one to insure compatibility first.
Click to expand...
Click to collapse
you are right... that's why the tool moves the new ext folders into a sub-folder (_NewPackages).
cooks still need to add compatible lang sub-folders and maybe adjust some keys in the rgu's.
this batch-file is only around a week old. so it's basically new.
the main reason for it's existence is to remove the manual package comparison wich is very time-consuming (detection of already present packages).
of course cooks need to check the new ext like they would need to do when updating them manually.
in my personal kitchen i adjust the ext folder names as following:
Album_3_2_19203733_0_leo_1.66
Album_3_2_20132625_0_leo_2.13
Album_3_2_20161229_00_leo_3.04
Album_3_2_20171628_00_huashan_0.90
this way i always know where the ext's in my kitchen are coming from.
the batch file detection still works when adjusting the end of the folder names.
for example:
source kitchen-Album_3_2_19203733_0
destination kitchen-Album_3_2_19203733_0_leo_1.66
the album folder will still be ignored even after you changed the folder name of the already imported package to Album_3_2_19203733_0_leo_1.66.
just don't change/rename the blue part (original package name)
HD2Owner said:
you are right... that's why the tool moves the new ext folders into a sub-folder (_NewPackages).
cooks still need to add compatible lang sub-folders and maybe adjust some keys in the rgu's.
this batch-file is only around a week old. so it's basically new.
the main reason for it's existence is to remove the manual package comparison wich is very time-consuming (detection of already present packages).
of course cooks need to check the new ext like they would need to do when updating them manually.
in my personal kitchen i adjust the ext folder names as following:
Album_3_2_19203733_0_leo_1.66
Album_3_2_20132625_0_leo_2.13
Album_3_2_20161229_00_leo_3.04
Album_3_2_20171628_00_huashan_0.90
this way i always know where the ext's in my kitchen are coming from.
the batch file detection still works when adjusting the end of the folder names.
for example:
source kitchen-Album_3_2_19203733_0
destination kitchen-Album_3_2_19203733_0_leo_1.66
the album folder will still be ignored even after you changed the folder name of the already imported package to Album_3_2_19203733_0_leo_1.66.
just don't change/rename the blue part (original package name)
Click to expand...
Click to collapse
That's cool I guess... but it still seems like a lot to do, for such a simple operation as replacing a package with a newer one. I personally use beyond compare. It's a MUST have tool for chefs. It's great once you get to know how to use it.
NRGZ28 said:
That's cool I guess... but it still seems like a lot to do, for such a simple operation as replacing a package with a newer one. I personally use beyond compare. It's a MUST have tool for chefs. It's great once you get to know how to use it.
Click to expand...
Click to collapse
i bought beyondcompare too. it's a must have for chef's if you ask me too..
lot to do?? did you actually try the batch-file???
-adjust the 2 paths in the batch
-remove the lines you dont want to import (from the pop-up txt file - save and close to continue)
-adjust packages (insert lang subfolders and rename packages in the pop up temp folder)
-press any key (dos window) to move adjusted packages from temp folder to sub-folder "_NewPackages" in destination kitchen
for me, this batch is a real time-saver........
and i dont even have to use beyondcompare for this specific task anymore..
btw:
i will try to adjust the batch to show a pop-up of the destination-kitchen too when the temp folder is showing (so you dont have to open it manually to pick lang folders).