Related
I finally got my ftp up and running. As promised, I have uploaded a slightly modified Vista backup for Acronis. It contains a preinstalled version of Office 2007. So, if you dont own Office 2007, please uninstall it
(Right-Click here and choose Save as...)
MyBackup.tib Slighty modified post-recovery Vista. Reg tweaks and Office 2007 (thanks to TokyoRob for providing the original)
Acronis will be back soon
RealVGA_11.CAB gives you real VGA under SnapVue
ResPack128dpi.ARM.CAB resolution pack for RealVGA
Recovery Partition Content.rar I guess the file name is meaning enough (thanks to devictoria for the upload, i know it was painful)**FIXED**
TabletPC_PatchXPproSP2.exe TabletPC patch for a non WINXP SP2 installation, can be applied at any time. Tested with English version only.
change_vista_language.iso Vista PE to change the language of any Vista installation, tested with HTC Shift.
Vista_x64_language_packs_links.html language pack needed for "change_vista_language.iso" (64bit)
Vista_x86_language_packs_links.html language pack needed for "change_vista_language.iso" (32bit)
WINMOUNT (tool to mount XVISTA.WIM) will be replaced with Microsofts WAIK (use ImageX.exe and command line)
http://www.microsoft.com/downloads/...6D-15F3-4284-9123-679830D629F2&displaylang=en
hdat2iso_4_6b1.zip boot image to use Hdat2, tool for SETMAX address and unhide HPA
hsect-2.1win32.zip POF's very loved HTC SHIFT EMBEDDED CONTROLLER TOOL
testdisk-6.9.dos.zip tool to unhide the recovery partition
Update 07/05/2008:
HTC Shift XP Drivers.rar added the Windows XP drivers and Vitakey package by febelus (http://forum.xda-developers.com/showthread.php?t=386492)
Update 07/23/2008
A-Patch140rc2b31_WLM.zip added to modify WindowsLive Messenger 8.5 (this enables you to save some desktop space when chatting)
Update 08/08/08 (nice date..should get married today)
Removed illegal content, such as Keygens, Crack and Serial. Trial versions should suffice. Added Windows Automated Installation Kit (WAIK) to alter the recovery partition content (license free).
The server is planned to be permanent, but only temporarily public. In one or 2 months, I will change the access to
ease my traffic. But until then, grab it while you can.
If anyone wants to add something (tools, different languages), please contact me for upload instructions. This ftp is planned to stay permanent.
https://phatpipez.homeftp.org/HTCShift/Shift/A-Patch140rc2b31_WLM.zip
Fingerprint_and_Omnipass.rar
HTC Shift DRIVER - Vista.zip
https://phatpipez.homeftp.org/HTCShift/Shift/MyBackup.tib
OrigamiExperiencePackv2.msi
Original WWE.rar --- original Windows Mobile rom for Shift.
https://phatpipez.homeftp.org/HTCShift/Shift/RealVGA_11.CAB
https://phatpipez.homeftp.org/HTCShift/Shift/Recovery Partition Content.rar
https://phatpipez.homeftp.org/HTCShift/Shift/testdisk-6.9.dos.zip
Aquasesh
I have tested the connection to my FTP... Its HTTPS, you have to install or allow the certificate in order to access my files.
Also, use Firefox or Opera to download. IE7 suffers from a HTTP Header error when accessing large files. ( i tried to fix it, but no luck)
Dont tell me its a nuisance to use FF or Opera instead of IE7.
If you really need / want those files, you should be willing to install one of those browsers...
I will UPDATE the files next Friday, any request, let me know.
Aquasesh
UPDATE 08/08/08
Windows Automated Installation Kit (WAIK)
This is used to create your own recovery partitions. You can slipstream updates, software and drivers.
It is license free and can be optained from the link in post #1.
To mount the XVista.wim from the Shift's recovery partition, locate the ImageX.exe in your programs folder.
(default =C:\Program Files\Windows AIK\Tools\x86\imagex.exe)
Copy the XVista.WIM to a location of your choice (preferably c and run the Imagex.exe in the Command Prompt.
First you have to find out which installation you want to mount. Usually Vista contains more than one installation
(Home, Home Premium, etc...) Each has a number.
In our case its easy, its only Vista Business, so we mount Number 1.
Type imagex.exe /mountrw c:\Xvista.wim 1 c:\Xvista
mountrw means read and write access
c:\Xvista.wim is the location you copied it....
1 is the image number within the archive
c:\Xvista is the mount path (can be anything you want)
The installation should now appear in Windows Explorer like a normal folder and you can modify its contents.
Recovery Image
With regards to the recovery partition restoration process;
The previously referenced instructions involve using a binary file to dd the image back to the disk.
When your RAR file is unarchived, it shows a directory structure with multiple files and one large WIM file.
What mechanism should one use to replicate the RAR contents to the recovery partition?
Thanks..
jposluns said:
With regards to the recovery partition restoration process;
The previously referenced instructions involve using a binary file to dd the image back to the disk.
When your RAR file is unarchived, it shows a directory structure with multiple files and one large WIM file.
What mechanism should one use to replicate the RAR contents to the recovery partition?
Thanks..
Click to expand...
Click to collapse
The binary file you are referring to is a result of a different recovery approach. You copy the hidden partition into a binary file and copy it back to its exact location on the hdd, later.
If you want to use my RAR file, you have to follow these instructions, to create an external boot media.
http://forum.xda-developers.com/showthread.php?t=393070
Thanks for the files. MyBackup.tib is not working(not able to download).
TRoN_1 said:
Thanks for the files. MyBackup.tib is not working(not able to download).
Click to expand...
Click to collapse
im not sure what the problem is in IE7. But with Opera and Firefox, the download works normal.(rightclick "save as")
I will try to see how I can fix it.
aquasesh said:
The binary file you are referring to is a result of a different recovery approach.
Click to expand...
Click to collapse
Not having access to a USB floppy, would anyone happen to have the binary file that is used with the dd method?
Thanks..
MyBackup.tib Slighty modified post-recovery Vista. Reg tweaks and Office 2007 (thanks to TokyoRob for providing the original)
Recovery_Partition_Content.rar I guess the file name is meaning enough (thanks to devictoria for the upload, i know it was painful)**FIXED**
Great files, thanks.
I can't download files above. The first one is about 278 MB long, corrupted after download. The second one is 0-length file. Would you please check it? Thank you for your time.
When I right-click and save as...
Internet Explorer cannot dowload MyBackup.tib.
The supplied HTTP header is invalid.
TRoN_1 said:
When I right-click and save as...
Internet Explorer cannot dowload MyBackup.tib.
The supplied HTTP header is invalid.
Click to expand...
Click to collapse
Please use Firefox or Opera to download it. I have some trouble with my
Server...but those browsers work
They also support resume, which is recommended with such large files.
@jposluns
you need a USB Stick, not a floppy. The image as well as the BIN file are about 3GB.
You can also burn the contents to a DVD if you make it bootable. I havent tried it yet, but should work.
aquasesh said:
you need a USB Stick, not a floppy. The image as well as the BIN file are about 3GB. You can also burn the contents to a DVD if you make it bootable. I havent tried it yet, but should work.
Click to expand...
Click to collapse
There is something critical that I'm missing here..
The instructions in the link you provided imply that the USB drive will be bootable, and that it is from there that the recovery will occur.
Your RAR file does not have an MBR, nor does it apparently have a tool to install one, so *something* would have to be used in order to install an MBR to the USB drive.
What is that *something* ?
Thanks..
jposluns said:
There is something critical that I'm missing here..
The instructions in the link you provided imply that the USB drive will be bootable, and that it is from there that the recovery will occur.
Your RAR file does not have an MBR, nor does it apparently have a tool to install one, so *something* would have to be used in order to install an MBR to the USB drive.
What is that *something* ?
Thanks..
Click to expand...
Click to collapse
To make it short, you have 3 choices.
Firstly, you wait until i create a bootable recovery ISO, which you can burn to a USB stick. (maybe on Friday, if I can make the time)
Secondly, you try to make one yourself.
Or, you simply download Acronis TI Home, install it on a PC, create a recovery bootdisk, which you can put on a USB stick and use Mybackup.tib from my ftp to restore the Shift.( I usually use this method, since I dont have to setup anything, and I have office 2007 integrated)
I will try to polish up the problems on my FTP coming weekend and add some more stuff, USB iso and so on.
If you can tell me what mechanism is used to make the MBR in the recovery partition, I can make an ISO myself.. I've tried a few different boot loaders, though none seem to work with the RAR contents.
Or.. If an Acronis image of JUST the MBR/Track0 for the recovery partition is available, that would be relatively simple too.
Worst case, I'll wait for your ISO.
Thanks for all your help!
jposluns said:
If you can tell me what mechanism is used to make the MBR in the recovery partition, I can make an ISO myself.. I've tried a few different boot loaders, though none seem to work with the RAR contents.
Or.. If an Acronis image of JUST the MBR/Track0 for the recovery partition is available, that would be relatively simple too.
Worst case, I'll wait for your ISO.
Thanks for all your help!
Click to expand...
Click to collapse
To make it a media bootable for a recovery, you need to use etfsboot.com
found in the folder /BOOT
Now, i have to find out which commandline parameter i have to use, which will take some trying out.
Worst case scenario, I can only make DVD bootable, but even that would be ok for most.
Working ISO.. Wish me luck..
I've just followed the instructions at http://www.mydigitallife.info/2007/05/10/how-to-make-vista-bootable-dvd-with-wim-downloaded-files/ to create an ISO file using the WIM files from your RAR.
UltraISO can then be used to image the ISO onto a USB stick (4Gb or greater).
I'm in the process of doing so right now and will test it tomorrow morning.
jposluns said:
I've just followed the instructions at http://www.mydigitallife.info/2007/05/10/how-to-make-vista-bootable-dvd-with-wim-downloaded-files/ to create an ISO file using the WIM files from your RAR.
UltraISO can then be used to image the ISO onto a USB stick (4Gb or greater).
I'm in the process of doing so right now and will test it tomorrow morning.
Click to expand...
Click to collapse
Looks like a good guide. Those seem like the right etfsboot parameters.
Im sure you can do it.
its basically the same way HTC does it, I guess the boot.wim contains the WindowsPE for the recovery.
Good Luck
Recovery Image was too big, please share it in eMule!
aquasesh said:
I finally got my ftp up and running. As promised, I have uploaded a slightly modified Vista backup for Acronis. It contains a preinstalled version of Office 2007. So, if you dont own Office 2007, please uninstall it
URL is https://phatpipez.homeftp.org/HTCShift
you will also find all the stuff i use on my shift, such as:
MyBackup.tib Slighty modified post-recovery Vista. Reg tweaks and Office 2007 (thanks to TokyoRob for providing the original)
Acronis True Image 11 Build 8053 Home.rar we all know this
MMSLite.bld265.CAB MMS addon, WM 5 and 6 for SOFTBANK ONLY
RealVGA_11.CAB gives you real VGA under SnapVue
ResPack128dpi.ARM.CAB resolution pack for RealVGA
Recovery_Partition_Content.rar I guess the file name is meaning enough (thanks to devictoria for the upload, i know it was painful)**FIXED**
TabletPC_PatchXPproSP2.exe TabletPC patch for a non WINXP SP2 installation, can be applied at any time. Tested with English version only.
UltraISO_Premium_Edition_v9.1.2.2465 can burn bootable image files to USB media
change_vista_language.iso Vista PE to change the language of any Vista installation, tested with HTC Shift.
Vista_x64_language_packs_links.html language pack needed for "change_vista_language.iso" (64bit)
Vista_x86_language_packs_links.html language pack needed for "change_vista_language.iso" (32bit)
WinMount.v2.2.2.rar tool to mount .WIM files. Such as XVISTA.WIM
hdat2iso_4_6b1.zip boot image to use Hdat2, tool for SETMAX address and unhide HPA
hsect-2.1win32.zip POF's very loved HTC SHIFT EMBEDDED CONTROLLER TOOL
ppxsetup2.rar PPXplorer for Windows Mobile. Good file commander.
testdisk-6.9.dos.zip tool to unhide the recovery partition
Update 07/05/2008:
HTC Shift XP Drivers.rar added the Windows XP drivers and Vitakey package by febelus (http://forum.xda-developers.com/showthread.php?t=386492)
The server is planned to be permanent, but only temporarily public. In one or 2 months, I will change the access to
ease my traffic. But until then, grab it while you can.
If anyone wants to add something (tools, different languages), please contact me for upload instructions. This ftp is planned to stay permanent.
Aquasesh
Click to expand...
Click to collapse
Hi aquasesh,
It is very difficult to download the recovery image with Firefox or IE, can you please share it in eMule, so that more Shift owners can download it share it.
Thanks in advance.
szjohnwong said:
Hi aquasesh,
It is very difficult to download the recovery image with Firefox or IE, can you please share it in eMule, so that more Shift owners can download it share it.
Thanks in advance.
Click to expand...
Click to collapse
I dont think sharing it in Emule is better than using Firefox.
I dont understand how it can be difficult to download it via a different
browser...Its just the same as IE
you just install opera or FF and rightclick the file you want...then choose "save as"....
Besides, sharing it in Emule is too slow, it will take ages to download it.
jposluns said:
I've just followed the instructions at http://www.mydigitallife.info/2007/05/10/how-to-make-vista-bootable-dvd-with-wim-downloaded-files/ to create an ISO file using the WIM files from your RAR. UltraISO can then be used to image the ISO onto a USB stick (4Gb or greater).
Click to expand...
Click to collapse
Update: An ISO was built, though when I imaged it to USB and booted off of it, an error of "can't find HP WIM files" resulted. I believe that the version of the <surrounding files exe> that I used was specific to HP, and there are a few more WIM files it's expecting. I've downloaded another variant and have it building an ISO now.
I installed Opera and when I right-click and save as, it downloads and says it saved the file. I did this 3 times in 3 different folders (I aborted once), but the files is nowhere to be found. In Opera under Transfers tab it says:
From https//phatpipez.homeftp.org
To D:\MyBackup.tib
Size 4.3 GB(4,576,253,952)
Transfered 4.3 GB(4,576,253,952)
The file is NOT there. I don't get it
HTC finally came out with a wm6.1 update for the Telus touch phone.
I cant install the .exe file directly from my phone, and I tried to extract the .cab file, but it's just not installing...
I'm not running the new mac, with the intel processor. So I cant run windows on it.
Any other suggestion for me ?
Put it on a flash drive and install it from Kinkos or the library.
Thanks Balana,
Yep I tried to put it on my flash drive, but i get the message that it is an invalid ppc application.
And what is Kinkos ?
The update exe's don't contain a cab file. They contain an .nbh ROM image. If you extract that file from the exe you can flash it directly from your SD card. I'd suggest looking for specifics in the Upgrades/ROM Development forum of your particular device.
Thank's Bedoig.
Tried everything, finally I had to resort to the ultimate sacrifice... working on a PC ! Flashed my device to wm 6.1 Cant be happier, now I have the GPS on my HTC touch.
Hello everyone, put my old kitchen, a little 'restored.
IMPORTANT: To build a good rom, you 1st have to dump an original rom for your preferred device, to have all files needed to build it after (header.xml, splash.xml ecc...)
List of Features:
Check rom version for exchange for new payloads (tested on hd2 rom 3.14 and it worked!), some minor adjustments, the editor, RGU, app.ref etc ..., now always starts as an administrator.
to test it, dump an original rom and then have fun customizing!
New style, new tricks at runtime, new tools for dumping and building !!!!! (Libnb.dll!)
Fixed bugs on inclusion radio.nb and splash.nb !!!!!
Import into .\ext, old-style packages, OEMpack, EXTPack (and also from Cab files
in the context menu is also remodule package (from files to module!) and re-file package (from modules to files!); other bugs solved!
Rapi connection problem solved with device in activesync and remove ring tones, images by default!:
Feature on delete files (ringtones, images (wallpapers) and other images (avatars) from a folder in oem \ langdevice \ .....)
Features to all feedback packages, from kitchen and easily editable text file (packages_usefull_infos.txt) in the root of the kitchen.
Can also import "rebuild dumped roms", from DFT dumped, OSkitchen kitchens and RAW Dumped roms!
Support to run the cabs charged by hands at 1st boot after flash!
Save & restore all tweaks in all the tabs when save/load a rom!
Added info exchange Rom language and Rom on the first use of header.xml libnb.dll nbh file to create!
Added new feature to force the run provxmls in Rom
Now when a dump .NBH, the new build is imported, in your EVK in use!
.\TOOLS folder
Inside the folder .\tools, you will find a new folder: registry_tweaks. The .\registry_tweaks folder includes some sample files. Replace and/or add .REG and .PROVXML files, name the files properly and the .REG files will be added as registry entries, the .PROVXML will be renamed as ****. ZZZZ_ provxml, as files are added. provxml, precisely in the rom and run when you first start to customize the rom as you like
The kitche includes two context menus for adding new .REG or .PROVXML files, edit them or delete if unused one!
Also includes new versions of DSM_editor and implantxip (no fake virus info about, someone in previous version, not me, inserted automatic "admin execution" with a kind of utility, into my implantxip.exe!, and maybe that "trick", was detect as fake virus, now, with my original updated version of implantxip.exe, my kaspersky doesn't find anything!!!!!)
Note
DSM_editor and implantxip (no fake virus info about, someone in previous version, not me, inserted automatic "admin execution" with a kind of utility, into my implnatxip.exe!, and maybe that "trick", was detect as fake virus, now, with my original updated version of implantxip.exe, my kaspersky doesn't find anything!!!!!)
System Requirements.
.NET FRAMEWORK 4.0 to execute new version of visualkitchen and new tools inside (dsm_editor and implantxip!)
Version History
12.2.9: compatible with x64 system machines, was libnb.dll,not was dll, was my exe, only I had to force x86 execution, also on x64 machines, that version was only for x86 machine, now at runtime, it is recreated, if is x64, compatible version is putted into .\tools folder, else a x86 compatible version will be copyed into .\tools folder!!!
12.3.7: package creator added as optiona choice when wanna import a cab into packages!
12.3.7: Added option to turn tricks "reg" to be placed in rom that will be in a good provxml 'forced to be the last to be executed, overriding any settings from other taxes proxml !!!!!
12.3.7: when forced execution provxml, reg cab, the sequence is .PROVXML in Rom, .PROVXML uploaded by you, proxml derived from the reg trick and finally the cabs
12.3.7: added possibility to add and execute a .tsk file into ROM!!!
12.3.9: bug solved on provxml creation when found "delete regkey" or "delete regvalues"
12.4.3: bug solved on save and load roms, new icon for exe!
12.4.3: "reloaded" update pagepool options on new implantxip.exe
12.4.4: solved problems with implantxip value as default
12.4.5: inserted possibility to load, edit and delete mortscript scripts into rom to run (config.txt will be populated with selected scripts) at 1st boot!
12.4.8: when you choice a bmp to became a splash screen, the kitchen automatically check if the format and size is good, if not, automatically modifyes the image, makeing before a backup of it, and adjusts it according to the file "splash.xml"
(I suggest to redump an original rom for your device, becouse there are a lot of libnb.dll, and I've changed in times, so maybe splash.xml, could be different in format!)
12.5.0: updated package_creator, see and edit into \tools folder user_folders.txt to add your own modded folders into start menu for lnk files extracted by cab files; now, all manila-language files will be stored automatically into relative 04XX subfolders, so only real lang-manila files needed will be stored into rom, and before build, cfc_gui.exe will be executed to compress and patch manila, if you want, only have to click on "tools<>patch manila", on cfc_gui.....
see U!
12.5.2: new built of implantxip, and some little little improvements on erviuskitchen.exe!
12.5.3: Added Visual advices for packages that have to be recmode or reversemode!
12.5.6: re-file or re-module packages that you insert into comments like "remodule, or re-file! (only id relative poackage is enabled while build rom!)
solved little bug on packages colouring (same color on "false/true" packages (enabled/disabled!))
12.5.8: solved some trubbles with LZX Compression!
12.6.0: more compatibility with new xipporterex to change rom version on nk.exe into 3.14 TMOUS ROMS! and now recontruct better alla lang files/folders for manila!!!!
12.6.2: Full compatibility with all Language codecs to recontruct well all lang files/folders for manila, and also all MUIS files will be stored in relative language SubFolders!!!
12.6.3: only exe, now remove also all *.cpr files with resolution different thankn used by your device, and store all of them into :\moved\cpr_moved\namepackage\resolution\...
Download Link
http://www.4shared.com/file/0Nv3ETFr/VisualKitchen_12_5_8.html
Updated only exe! (12.6.3_rev2)
http://www.4shared.com/file/9yFFf6YA/erviuskitchen_12_6_3_only_exe_.html
Quick Thread Link
Discussion on Latest kitchen start here: http://forum.xda-developers.com/showpost.php?p=9500214&postcount=2484
Reserved for future expansion
OLD visual multilang/multidevice/multibuild kitchen for last bepe rom-tools!! V1.8.2
Hi, this is a visual multilang kitchen based on last bepe's tools to build a rom.
Last Version: 1.8.1 aka 10.8.1 (1.8.1)
Date: 28.07.2009
Download Links: 1.8.1, 1.8.2
new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder.rar 7MB
erviuskitchen_1_8_2_fixed.rar 523 KB
Latest version of Ervius Visual Kitchen tools. New visualkitchen with all dsm/rgu recreations/updater to have complete old_style roms ready to use .pkg updater!!!!! The KITCHEN has been updated to include logging; (see build_log.txt into root of kitchen after built a rom!!!)
Note: Also attached to this post as <filename>.RAR.ZIP. After download, remove (.ZIP) before UnRAR'ing.
Changes In This Release:
XIPPORTEREX:
Added compatibility with new 2.09 kn.exe to r/w correctly date/version on ROM!
Added capability to find version/release_date on new wm 6.5 nk.exe!!!
DUMP Process:
Now if dump a stocked rom, in EXT packages it leave relative dsm/rgu, create a global packages.ini (with all dsms infos inside!) and for each EXT Package, create "package.ini" file, with all infos about relative dsm,
All shadows, depepndencies, certificate needed in .\tools folder, it populate "dependencies" and "certificates" folder with all dsms and certs files found during dump process, used to insert/edit all dsms into rom with dsm_editor
OTHER button:
Provides for selection of ULDR reduction, PagePool sizing, disable Certificate
Verification, etc. Settings are stored in: ERVIUSKITCHEN.INI.
Editor:
Addresses issues when using "editor".
Compilation:
Solved bug on 6.5 reak aku roms
Addresses issues when searching structures and duplicate files during compilation.
Added possibility to change max number of modules in an hybrid ROM (nk.exe from 6.1 kernel and XIP From 6.5 kernel) the value is saved on that rom configuration, so every rom loaded has his max-modules value setted
Extraction:
Addresses issues when extracting contents of some device .NBH/.NB files.
Compatibility:
Addresses unsupported Language code (ex: 040C).
Added compatibility with old style rom (IMGFS & XIP).
All modules can be reallocked.
DSM processing; all dsm and rgu are updated/created -only with old_style roms creation! (required for cab.pkg updater support.)
In old style ROM mode; all is executed automatically, XIP porting is automated:***
- Correct realtive device's .VM must be copied to .\OEM\<devicename>\.VM
- Correct XIP.BIN must be copied to .\ROM\SHARED\<buildnum>\
Post-Download Instructions:
Extract the contents of kitchen archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Backup existing kitchen files. Files/Folders to backup are:
- Files in root of kitchen (ex: C:\XDA\My_Visual_Kitchen)
- .\TOOLS folder
Remove (delete) ERVIUSPACKAGES from TOOLS folder (ex: C:\XDA\My_Visual_Kitchen\TOOLS\ERVIUSPACKAGES).
Copy the contents of the extracted archive to the kitchen (ex: C:\XDA\My_Visual_Kitchen\) folder.
----------------------------------------------------------------------------------------------------------------------------------
Implantxip.exe (Pagepool Patcher/changer!)
Download Link: implantxip.rar 166 KB
implanxip can works with:
all kind of payload file, and more:
if a payload has ULDR removed (ULDR part not present!), it can work on it and reallign well some bytes into MBR
you can also remove completelly the uldr section (you could save some more space into payload in this way! (be attenction: in some payloads this operation causes non-booting roms!!! make a backkup of original
payload before use: "-uldr tryremove parameter!!!)
for help about: in prompt command write: implantxip /h )
Note: Also attached to this post as <filename>.ZIP.
----------------------------------------------------------------------------------------------------------------------------------
EXT Packages Rebuilder
To build EXT_Packages from old style ones; use the tool at your own risk!!! Fixed lost modules into new package created, now all modules are into .\files subfolder after ext package is built.
Download Links:
EXT_PAckages_rebuilder+Structurer_all_lang_enabled_v3.zip 8 KB
EXT_PAckages_rebuilder_modules_fixed.rar 9KB
Note: Also attached to this post as <filename>.ZIP.
Excellent work as always ervius.
Grazie mille.
^.^
That might come in handy for some ppl.
For my part, I'm used to command line as my primary WS is linux based. As a matter of fact, i prefer it.
@Ervius: Do you have any experience in coding for unix/linux?
At some point, pof coded a htc-flasher kitchen, but it was mostly wrappers for the windows programs.
Most of the tools we use for ROM building have their source code available, so...
Anyways, I'm off.
A.
GREAT!!
I'm testing it in my kitchen just today. I'm looks fantastic. Thanks!!.
If now you can integrate your XIP porting tool then.....
Regards,
elparra72 said:
I'm testing it in my kitchen just today. I'm looks fantastic. Thanks!!.
If now you can integrate your XIP porting tool then.....
Regards,
Click to expand...
Click to collapse
this is a alpha version, and stucks on platformrebuilder.exe execution, , but when I have some time more maybe insert all inside, xipporterex and other tools of mine!
can you post it on rapidshare please, megaupload is a menace. thanks.
In any case this is a great work!!.
I've been checking folders structure and adapte it to Spanish (or another language) is really easy. I'm preparing a new ROM, but as soon as I post it in a Spanish site, I'm going to 'play' with this application and l'll inform you about troubles. Thanks !!
On the other hand (I know this is not the best post to speak about), Your active sync killer is not working fine in 2.xx ROMs. Are you preparing a new one? Do you have a solution?. Thank a lot in advance.
Kind regards!!!
El Parra72
elparra72 said:
In any case this is a great work!!.
I've been checking folders structure and adapte it to Spanish (or another language) is really easy. I'm preparing a new ROM, but as soon as I post it in a Spanish site, I'm going to 'play' with this application and l'll inform you about troubles. Thanks !!
On the other hand (I know this is not the best post to speak about), Your active sync killer is not working fine in 2.xx ROMs. Are you preparing a new one? Do you have a solution?. Thank a lot in advance.
Kind regards!!!
El Parra72
Click to expand...
Click to collapse
you can adapt, but add other languages, near 0409\ and 0410 folders you can add 04xx\ or o8xx\ all you want, the kitchen at start recognizes how many into, and show all into combobox, you only have to choice in witch language want build the rom
for activesync killer, what you refer to, mine or the original by eliasweb???
bye!
I've detected this trouble in both. I've test them in several ROMS based on 'oficial' v.2.xx. I'm going to look for your post and follow this trouble there. Thanks.
..................
this looks better and better. I dearly hope that it will come with some kind of manual.. anything... just to know what to press and which button does what...
Thanks!
mjaxa said:
this looks better and better. I dearly hope that it will come with some kind of manual.. anything... just to know what to press and which button does what...
Thanks!
Click to expand...
Click to collapse
visual kitchen version beta1 released at 1st post, and see all ROM\ structures.....
Hi ervius, thanks for your tool.
I was trying beta1.
I have a couple of questions:
i've tried to import a package (generated with package creator) , I browse to the folder containing it, but after the right-click-> import package, it doesn't appear in the list of the applications.
I see it has been copied to the EXT folder but nothing more.
Also importing a package resets all the choices I made on what packages to include/exclude
If you need more details just ask
Thanks
A.
very nice, I will test this this week, and see if i notice anything. once again thank you
andreapappy said:
Hi ervius, thanks for your tool.
I was trying beta1.
I have a couple of questions:
i've tried to import a package (generated with package creator) , I browse to the folder containing it, but after the right-click-> import package, it doesn't appear in the list of the applications.
I see it has been copied to the EXT folder but nothing more.
Also importing a package resets all the choices I made on what packages to include/exclude
If you need more details just ask
Thanks
A.
Click to expand...
Click to collapse
well, well, so, some bugs are detected...
continue ti test it
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
ruipgouveia said:
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
Click to expand...
Click to collapse
Check the screenshots. You'll see the directory structure there.
ruipgouveia said:
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
Click to expand...
Click to collapse
use bepe's packagebuilder.exe on a dumped rom, after use my EXT_PAckages_rebuilder+Structures_rebuilder (attached here!) on dumped rom, finally you'll have all rom structures ready to be koocked by my visual kitchen!!!
bye!!!
P.S.: at first post "beta 2" is ready (some bugs solved!)
[WM Kitchen] OsKitchen Zero v1.33.5: The Easiest & Most Complete Kitchen (20/10/2010)
Index of this thread
(This Page) General Informations, Download links, Screenshots
Using OsKitchen Zero (Tutorial)
Moving from Ervius Visual Kitchen to osKitchen
Frequently Asked Questions
Useful Resources (Links where to find the latest Windows Mobile Builds and EXT packages)
Description
What does this kitchen do that others don't? You should ask yourself what the other kitchens do that this one doesn't because it literally does everything: importing the ROM directly from the EXE updater, detecting all the informations to rebuild the ROMs from the ROM file itself (no more messy BAT/CMD to edit to get things working), sorting the packages with the best EXT packages conversion engine available (no more EXT packages with weird names or out of place), building ROMs for different languages in the same pass picking all the correct windows mobile packages (EA/NonEA/AH/CS/Transcriber/Uniscribe/Fonts) to use, directly installing packages on the devices without having to flash each time (package installer), automatically recmodding of packages (without touching any of the original files) to allow cooking windows mobile 6.5 ROMs using older kernels, automatic manila CFC compression to save space and improve speed (and supporting latest manila builds where CFCGui has issues) and much, much more while keeping all the user interface well organized and being extremely easy to use. Start the kitchen, import a stock ROM and go! Give it a try and find out yourself how it lives up the hype or if still unconvinced scroll down to see how much simple yet complete the kitchen is by looking at the screenshots.
Features
The kitchen has the most streamlined and self-explanatory UI you can find, it can natively import and rebuild ROMs for all the devices in the supported list without having to mess with any batch/cmd files, it shows detailed informations about every Windows Mobile package and warn about conflicts and unmet dependencies, it can build multilanguage ROMs in the same pass by automatically choosing all the right localization packages required for each language, it can import windows mobile builds of any kind, convert OEM packages/CABS/HTC Hotfixes directly to EXT packages, can automatically recmod/UPX and natively compress/patch manila manila files with CFC, it automatically detects older kernels and suggests all the right packages to recmod to get the ROM working, it checks the ROM integrity while building to avoid many common user mistakes, has a lot of tweaks directly selectable with just a click from the kitchen interface, it has the most advanced search system available and much more.
Supported devices
HTC: Artemis, Athena, Blackstone, Diamond, Elf, Gene, HD Mini, Herald, Hermes, Iolite, Jade, Kaiser, Leo, Mega, Nike, Opal, Polaris, Pharos, Quartz, Raphael, Rhodium, Sedna, Titan, Topaz, Trinity, Vogue, Whitestone (CDMA variants of all phones are supported as well)
Palm: Treo Pro
Sony-Ericsson: Xperia X1 (HTC Kovsky)
Samsung: i900/i910 (Omnia) (delete the giisr.dll in the OEMXIPKernel folder or the ROM won't boot)
Asus: P565 (XDA Zest) (even thought not officially on the list the kitchen can import the NB0 ROM extracted from the ABI file with p835abisplit2)
Other devices, with caveats: as long as you have tools to convert between NB and your phone format the kitchen should work fine unless platformrebuilder doesn't support your device (I.E. it crashes). If platformrebuilder DOES NOT support your device you can still put a dummy NK.exe from another device to stop platformrebuilder from crashing (be sure the NK version (6.1/6.5) is the same) and insert your own crafted XIP.bin (there's a setting in Advanced Tweaks to use a custom xip file).
Download link
(First time using osKitchen? Read the brief tutorial in the 2nd post)
v1.33.5 All in one package:
http://forum.xda-developers.com/attachment.php?attachmentid=423263&stc=1&d=1287585346
DISCLAIMER: This software is provided "as is" and I don't take any responsibility for any damage caused to phones or anything else. I added all sorts of integrity checks I could think of to prevent the generation of invalid ROM files and so far none of the thousands of users who downloaded the kitchen reported invalid ROM files but just like when flashing any cooked ROM don't forget that there is always the risk that the phone may end up bricked (due to defective usb controllers, defective cables, defective phone memory, wrong radio file, software interfering with the flashing tools, power outages, etc).
System requirements
Microsoft .NET 2.0 (.NET 3.0 and 3.5 are 2.0 based so those work as well), already preinstalled on most computers, the kitchen won't start without it so it's easy to find out if it's missing
The following three system requirements also are preinstalled on most computers; the kitchen will warn you if they are needed so don't worry installing them unless required:
Microsoft Visual Studio 2008 runtime, required by xidump during the importing process
Visual Studio 2003 (7.1) Runtime Libraries, required by platformrebuilder to solve the "cereg400.dll cannot be loaded" error message, required by XIDump to solve the "Failed to init decompression!" error message and required by IMGFSFromDump to solve the "Unable to load compression DLL!" error message. Copy those libraries in the Resources\Tools folder and if that still doesn't work in the system32 subfolder of your windows folder (the right subfolder for 64bit systems is syswow64)
XmlLite Update Package required to solve the "Unable to load LibNB.dll" errors (only for Windows XP SP2)
Changelog from v1.33.4 to v1.33.5
Fixed os.nb file deletion issue for devices with no sectorinfo
Changelog from v1.33.3 to v1.33.4
Fixed delete shadow order entries not being saved
Implemented internal manifest management to reduce disk overhead during package scanning
Implemented detection of registry values that are found without a preceding registry key specifier
Improved file copy and file deleting speed
Changelog from v1.33 to v1.33.3
Fixed issue with packages with duplicate files causing errors in the package installer
Fixed issues on CAB files with "\." InstallPath attribute
Un-tied Calibration Data and Skip Welcome screen settings
Fixed IMGFS cache not being applied correctly
Fixed issues when installing packages registry files containing multi_sz strings with the package installer
Fixed new packages sorting issue
Changelog from v1.32 to v1.33
Fixed issue when using a drive root directory as temp folder
Fixed a localization manager issue that was causing longer startup times
Fixed some issues in CAB file folder mapping
Fixed the kitchen truncating i780/i900 BIN files
Added error messages when the DPI or MUI settings are missing on the phone
The kitchen now allows importing ROMs even when the language folder is missing (multilanguage Samsung ROMs)
Added a warning when the initflashfiles/app.dat files are not Unicode
The kitchen now reads app.dat as ASCII when Unicode characters are not detected
Fixed issue in which the initflashfiles.dat file was left locked for a few seconds during the import process prompting a retry/cancel file operation
Added detection and parsing of DPI_ EXT subpackages
Changelog from v1.31 to v1.32
Implemented total integrity check that checks all the structure of packages, modules and every single line of initflashfiles/registry files for issues. All the issues within the package will be shown next to the package name in the packages list.
Added support for variables in initflashfiles.dat, app.dat to make localization easier (because the variables will be replaced with the correct localized folder when the ROM is built). The list of supported variables can be found in the FAQ of the official osKitchen thread.
Added “RAM Drive Mode” setting to have additional cleanups performed during the build process to reduce the space usage of the temporary folder
Fixed crash when trying to open a search result file that has a defective associated application
Implemented total integrity system: every package, DSM, module and initflashfiles file will be validated for integrity and all the problems detected will be shown with an error/warning icon on the left of the package
When importing a ROM the initflashfile values are saved with the converted hexadecimal values like the generated app.dat files
When importing a ROM the progress bar will now warn of temporary folder cleanup even when the import has failed
Removed the unnecessary PackagePath attribute from the project files
Fixed the kitchen crashing when the resources folder was missing or the command line parameters were wrong
Renamed universal package converter to universal package importer
Fixed LCID validation not checking the LCID length correctly
Fixed the pagepool size patching message reporting unlimited instead of the real size
In-line comments are now maintained when the initflashfiles is split during the ROM import
When importing a ROM the initflashfiles lines that are not valid will now be commented out
Removed the %LCID% variable as alternative to %ROM_LCID% in the ROM filename
The ROM filename variables replacement is now case-insensitive and the value of the variables has any non-filename friendly characters removed
Remove Uniscribe/Transcriber mutual exclusion warning
Improved error handling during the NBH generation process
Fixed error message during build when packages contain more than one RGU file
Fixed some registry entries being unrecognized when tabs were used for spacing
Fixed the recmod messagebox appearing twice when the device is selected and no is chosen as answer
Fixed the windows mobile build importer not deleting the imageinfo.txt files in modules
Implemented a rudimentary “Install Package on device” function that allows installing a package on the device to avoid having to flash the phone for every changed file. Currently only sends the main package (no LCID/res subpackages), doesn’t apply registry entries and applies initflashfiles entries with no variables replacement.
Fixed the kitchen crashing when the packages contained corrupted DSM files
Fixed WinCENLS_Lang_RTL_0401 detected as having the wrong syntax
Fixed error messages saying that the packages had a wrong syntax on _CS packages
Fixed Danish appearing as “da-dk” and “Portuguese” listed as “Portugese”
Fixed the locale listview showing the LCID in the country code column
Now the locale combobox shows the locale name and country instead of just the LCID
Implemented automatic Unicode detection in initflashfiles.dat files
Fixed the file copy operations continuing even after the non-resumable error message
Fixed package validation not working in the universal package importer/windows mobile build importer
Added an “Expand all” context menu entry for search results
Added warning when wince.nls ends up in both XIP and IMGFS partitions
The packages issues are now listed by subpackage
The “Install Package on Device” function now also includes the subpackages, the settings to compile the packages are extracted from the phone itself and all registry values except multistring/binary are added
Removed missing DSM warnings
Implemented binary entries support in the “Install Package on Device” function and fixed temporary folder issues
Fixed duplicate DSM creation in package properties and reduced the wait before the packageproperties form is shown
Fixed error message when loading old kitchen project files
Added support for REG_NONE registry keys
The kitchen GUI is now shown before the project files or imported ROM informations are automatically loaded
Fixed the new DSMs file for SYS/OEM packages being saved with a Guid different from the registry key one
Added support for REG_MULTI_SZ on “Install package on device”
Fixed the kitchen leaving old combo box values when loading projects referencing non-existing devices, profiles or windows mobile builds
Search now removes unnecessary wildcard characters from the search string when wildcard mode is enabled to improve search speed
Renamed “Empty project” to “New project”
Fixed crashes in “Install package to device” with some SYS/OEM packages
Implemented integrity check support for boot_ms.rgu and boot.rgu files
Removed TGTool from the kitchen archive
Disabled F5 refresh during ROM generation
Implemented path variables support in the “Install package on device” function (note: the WM build on the phone must be present in the kitchen and have the build number as folder name for the localization to work)
Fixed issue with "Install package on device" function and short filenames and multiple initflashfiles files
Halved the time required for project loading and packages list refreshing
Implemented IMGFS support for unicode characters
Implemented CE variables support in “Install package to device” function
Added HTC Oboe to the devices list
The sort column order is now reapplied after loading a project instead of defaulting to sorting by name
Fixes some issues with empty DSM files
Fixed crash when using unicode package names
Added check to prevent boot.rgu and boot_ms.rgu from being present in non-XIPKernel packages
Fixed the locales combo box not being refreshed after a new ROM has been imported
Fixed issue in which the kitchen would save a DSM file with random name instead of overwriting the correct DSM file if the source DSM file was corrupted
Implemented case insensitive manila.exe/mode9 CFC patch
Completed translation entries list for ROM importer
Added tools error handling in UPX/Recmod/PNG Compression/xidump/nbimagetool/TGTool/o2Util/ImgfsFromDump/OsNbTool/Platformrebuilder
Fixed erroneous error handling in imgfsfromdump that was causing file copy error messages if the tool failed
Fixed reduced OS file generation ignoring imgfsfromdump error messages
Fixed TSW/MST management not checking that the output file was correctly created
Fixed the kitchen ignoring missing custom user tools error messages and continuing the build process
Initflashfiles parsing now parses files as UTF8 when the UTF16 BOM header is not detected
The registry file validation now checks if the REGEDIT4 header is present
Fixed the locales selection combobox not detecting new language changes during refresh
Fixed “Install to device” function copying square resolution packages for some resolutions
Fixed LCID EXT packages lacking the RGU file not being moved into the correct main package folder
Fixed registry validation generating errors about dwords where values have initial spacing/tabulation
Added translation entries for the module validation messages
The kitchen now reads partitions informations from the OS.NB file and calls osnbtool with the proper partition numbers (to support older ROMs without ULDR)
The kitchen can now extract BIN files from more updaters (Samsung i780 and others)
Added translation entries for OS.NB generation error management
Added translation entries for the registry validation error messages
Improved error messages (added categories) on the error tooltips
Added translation entries for the package validation error messages
Added translation entries for the initflashfiles validation error messages
Added translation entries for the manifest validation error messages
Added initflashfiles variables for Application Data (%CE19%) and Program Files\Games (%CE8%)
The initflashfiles entries of imported CAB files are now mapped to the correct initflashfiles variables
How to use
Once unpacked the kitchen is ready for use, as soon as you start it you will be asked to import data from a stock ROM.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tree Structure
The new kitchen structure is very simple however it requires a ROM to be imported for device configuration files to be generated. Always import a ROM for your device and start working on it.
Output - Where generated roms are saved
Projects - Where the project files are saved
Resources - Tools and other internal kitchen files, shouldn't be touched!
Sources - Contains all the files of your Windows Mobile builds and Devices
Devices
#DEVICE NAME# (You can use the name "Common" to share packages between multiple devices)
EXT Packages - All the EXT packages must go here
OEM Packages - All the OEM packages must go here
Profiles
#Device Profile Name# - Contains the "Device Informations.XML" file and all the various packages required for building the ROM
NBH Structure - Contains files required by the kitchen to rebuild the NBH correctly
OEMXIPKernel - The OEMXIPKernel with all the device drivers and native kernel must go here
NB Structure - Contains files required by the kitchen to rebuild the Os.NB correctly
ROM Parts - .ROM, .VM, imgfs-template.bin, romhdr.bin and other files needed for relocation and XIP/IMGS generation must go here
Windows Mobile Builds
#Windows Mobile Build Number#
All - The language-neutral DPI and Resolution files must go here
Common - All the language-neutral Main Packages must go here
#LCID FOLDER# - All the localized packages must go in the appropriate LCID folder
Additional files
Visual Studio 2003 (7.1) Runtime Libraries, needed to solve the cereg400.dll cannot be loaded issue: http://www.mediafire.com/?mjmmgtwmion
ImplantXIP and ImgfsToNB tools, needed for the alternative building method: http://forum.xda-developers.com/attachment.php?attachmentid=374999&stc=1&d=1281153923
Using OsKitchen Zero
What you need to know first
The first thing you need to know is that Windows Mobile is not like a desktop operating system: you can't take a ROM from another phone and flash it on a different phone model because Windows Mobile relies on an extremely specific kernel and drivers that are compiled by the manufacturer for each device model. The Windows Mobile ROM contains only the Windows folder - yes, that's right, the ROM is just the plain Windows folder with NO subfolders - while every other folder (Windows\Start Menu, Program Files, My Documents and also Start Menu links etc.) is generated when the ROM boots the first time.
Every official Windows Mobile ROM is composed of packages. Microsoft and device makers create those packages to split windows mobile and the additional software into separated components. The real "Windows Mobile" code, interchangeable between phones, is stored in packages commonly called SYS packages, while everything the manufacturer added (the drivers and the additional applications for customization) are called the OEM packages. The EXT packages are "fake" packages that the kitchen uses to overcome the limitations of standard packages (for example EXT packages are often used to build multilanguage packages without having to create a single additional package for each language).
The Windows Mobile package structure is very simple. SYS and OEM packages are identical in structure and can only contain:
A DSM file (a file that contains some package informations, for example what other packages it require or what files it contains, most kitchens usually ignore this)
A RGU file (a registry file containing the registry entries associated with the packages)
Other files or modules that compose the package: the modules are folders that usually have file-like names (meaning they have an extension) and are a different way to store executable and DLL files on the ROM.
Note: A SYS/OEM package cannot have any subdirectory with the exception of modules directories.
EXT packages - that as already said are "fake" packages that are converted to the Windows Mobile package format by the kitchen - have a different layout: everything goes into a "files" folder except the registry files (app.reg), dsm files, initflashfiles entry files (.dat) and there can be subfolders with a LCID (language-ID) code as name (a LCID is a string composed of four HEXadecimal numbers identifying a language, e.g. 0409 for US English, 040C for Spanish, etc.) to store language-specific files in the same structure (.dsm and .reg in another "files" subfolder, like for the main folder).
EXT packages are the main way custom packages or packages from other devices are distributed on websites and forums. Recent HTC ROMs contains additional informations that allow kitchens to automatically convert OEM packages to the more user-friendly EXT packages: this allows to quickly remove applications just by disabling the package; other ROMs instead have everything stored in a single package (usually OEMMisc) and require more work to remove original applications.
The only important thing you still need to know is how the rest of the filesystem structure (Program Files, My Documents, Start Menu, etc.) is created during the first boot. All the system folders are generated and populated during the first boot because, as wrote before, the ROM contains only the Windows folder. Windows Mobile has two facilities for the first-boot (hard-reset) initialization: INITFLASHFILES.DAT, a text file that is usually in the OEM_Lang folder and that only allows creating folders and copying files (Documents folders, default pictures, and most start menu entries are usually added this way) and .PROVXML files that are some XML files that can do other advanced operations (like setting registry keys, certificates, phone settings).
Usually anything you can perform with PROVXML files, that unfortunately are difficult to edit and require a large knowledge of the format, can also be easily performed using initflashfiles and registry files. You can use the app.dat and app.reg files inside EXT packages (or initflashfiles.txt and RGU files in OEM packages) to add entries to both the initflashfiles file and to the registry: the kitchen will use them properly during the building process adding the app.dat entries to initflashfiles.txt and the reg entries to the final registry (the ROM boots with a precompiled registry HV file but you'll usually never have to mess with that when using a kitchen).
Manufacturers also use some advanced proprietary post-install tools to install custom cabs, apply themes and operator configurations (e.g. AutoRun, RunCC). Those rely on TXT configuration (*config.txt) files and can cause trouble (error messages about missing files during the first boot) when removing packages or files from packages that those config file point to if you don't update them.
When you want to upgrade a Windows Mobile Build the changes in the start menu are usually so many that it's REALLY recommended to start over with a new fresh initflashfiles.txt for that windows mobile build (you can find one for each language in the Da_G's rollup threads). Since in the official ROMs the start menu entries are all crammed into the initflashfiles.txt file (the app.dat exists only in the "fake" EXT packages) you will have to either take the time to create app.dat files for each package or to copy back all the initflashfiles entries for OEM/EXT applications back after you put the new initflashfiles for the windows mobile build you changed. The kitchen will try to move the config.txt and initflashfiles entries inside the correct packages while the ROM is imported to make SYS upgrades easier.
Now that you know the basics you can proceed to the first step...
Preparing the kitchen (Importing the Device ROM file)
1. Download osKitchen Zero and unpack the ZIP archive
2. Find a ROM update file for your device: the kitchen can import the EXE from all HTC and some Samsung updaters or alternatively the raw ROM file (the main used extensions: .NBH,.BIN and .NB are supported)
3. Open osKitchen Zero and the Import ROM Wizard will open
4. Select the device you want to work on from the drop-down list, you can actually write any device name because the list is just for reference to make sure people understand that the kitchen has been tested only with those devices
5. Select the ROM update file
6. Click NEXT
Building your first ROM to make sure everything works
At this point the main kitchen window will open. Since you imported a ROM all the "Project Settings" options will only have one choice, go on and select the only available choice for all the fields (device model, device profile, windows mobile build, language) and clicking Yes in case the kitchen asks you to automatically apply recommended changes should be enough to build a bootable and working ROM. The only setting that has more than one choice is the Compression setting that if you want to have the most available space to add your programs should be set to "LZX", if you want to use another compression first make sure that your phone will be able to flash a bigger ROM file.
Now you can go ahead and build your first ROM by clicking the "Start building button": the kitchen will work for a while, then tell you that the building process has been completed and ask you if you want to open the Output ROM folder; you can then answer yes, take the ROM file that has been generated and flash it, making sure it's the right format for your phone.
NOTE: don't try importing a ROM made for other phones different than the one you want to flash because the kitchen will rebuild the ROM for the device you imported and not any other. If you flash a ROM made for another device you risk bricking your device.
Once the ROM works (if it's a supported device it should work fine on the first try, if it doesn't please report the issue here so we can help fixing it) you can start working on the ROM. So that's it, you're ready to go. If you read the "What you need to know first" you will probably already have an idea of where to start for whatever change you want to do.
Moving from Ervius Visual Kitchen to osKitchen
Open osKitchen and import the latest ROM for your device
Replace the OEM packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "OEM Packages" folder
Open the OEM folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the OEM packages that are inside the Common and the LCID folder (0409 for english, etc.) into a folder with any name you want inside the osKitchen "OEM Packages" folder (where you deleted them). The .VM folder can be ignored.
Replace the EXT packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "EXT Packages" folder
Open the EXT folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the folders that are inside the Common (usually empty) and the Windows Mobile Build subfolder (it's a 5-digit number) in the osKitchen "EXT Packages" folder (where you deleted them).
Replace the OEMXIPKernel
Locate the folder oskitchen created in your device (it's in the Sources folder), go in the Profiles subfolder and then in its "default" subfolder, you'll find a folder named OEMXIPKernel, delete it.
Open the ROM folder in the Ervius Kitchen folder, locate the folder of your device, open the Windows Mobile Build subfolder (it's a 5-digit number) and then copy the OEMXIPKernel folder in the osKitchen "Profile\default" subfolder (where you deleted it).
Import the Windows Mobile Build
Locate the oskitchen Sources folder, open the "Windows Mobile Builds" subfolde and delete any folder in there.
Create a new folder with the number of the windows mobile build present in ervius kitchen (5-digit number) and create three subfolders inside: Common, All and a LCID one for each language (0409 for english, etc)
Open the ROM folder in the Ervius Kitchen folder, locate the folder named "Shared", open its Windows Mobile Build subfolder (it's a 5-digit number) and copy the MSXIPKernel folder in the osKitchen Windows Mobile Build "Common" folder you created earlier.
Open the SYS folder in the Ervius Kitchen folder, locate the Windows Mobile Build subfolder (it's a 5-digit number) and proceed as following:
Everything in the "Common" subfolders of the folders that start with DPI_ goes in the "All" folder you created in the osKitchen Windows Mobile Build folder.
Everything in the LCID (0409 for english, etc) subfolders of the folders that start with DPI_ and of the SHARED folder goes in the LCID (0409 for english, etc) folder you created in the osKitchen Windows Mobile Build folder.
Everything in the "Common" subfolder of the "SHARED" folder goes in the "Common" folder you created in the osKitchen Windows Mobile Build folder.
Frequently Asked Questions
How do I share packages between devices?
Create a folder named "Common" inside the "Sources" folder and put your packages (grouped in folders like standard device packages) in the "EXT Packages" and "OEM Packages" folders
Why is the final ROM file bigger or the total and available storage space lower than when using another kitchen?
It shouldn't. The other kitchens probably come with LZX compression selected as default while instead you told osKitchen to use XPR or None compression. You can also save additional space by using the ImplantXIP building method that removes the ULDR and some other wasted space.
How do I speed up the ROM generation process?
The kitchen needs to copy a lot of data and this may be a problem on computers where the hard-drive performance is low (i.e. laptops); antiviruses, firewalls and other applications may also interfere with the process speed therefore it's suggested to keep them off while the building process to save time. The kitchen allows setting another drive as a temporary folder to speed up the ROM generation and you can use a RAM drive (if you have enough RAM) or another hard-drive to improve the process speed.
How do I translate the kitchen?
When you start the kitchen for the first time if a translation file isn't found it will be created in "Resources\Localization" with the name matching your locale code (en-US.lng for american english, fr-FR.lng for french, it-IT.lng for italian, etc.): open that file with a text editor and translate all the text that comes after the "|||" separator (the text on the left of the separator shouldn't be touched, it's used both for reference and to identify the lines by the kitchen). Remember to post on this thread the translated files if you want them included in the official releases.
How do I reduce the space used by "Temporary OS.nb"?
It's suggested not to because the file will be needed in the next kitchen versions with the internal libnb NB dumping engine that will analyze the file, generate a new OS Structure.xml and delete it for good. The kitchen creates its own reduced files and keeps them in the Cache folder: if you really want to reduce the space used by the kitchen you can take the reduced file and replace the Temporary OS.nb with it.
How do I upgrade from an older kitchen version?
Simply delete oskitchen.exe and the Resources folder from your previous kitchen folder and put the new ones included in the archive or just unpack the archive overwriting the files. If you were using a version previous to 1.26 you will have to reimport a ROM and replace the imported packages with old ones (SYS/OEM/EXT/OEMXIPKernel (with nk.exe added inside) and remember to look at how the packages are structured). If you upgrade from 1.30 or below to 1.31 you may have to move your OEM Packages in a group subfolder because now the OEM packages are grouped like the EXT packages.
What are the variables that are supported in app.dat/initflashfiles.dat? (works only with 1.32 and higher)
%SystemDrive% (/)
%MyDocuments% (/My Documents)
%MyDocuments-MyMusic% (/My Documents/My Music)
%MyDocuments-MyPictures% (/My Documents/My Pictures)
%MyDocuments-MyVideos% (/My Documents/My Videos)
%MyDocuments-Templates% (/My Documents/Templates)
%ProgramFiles% (/Program Files)
%Windows% (/Windows)
%Windows-Fonts% (/Windows/Fonts)
%Windows-StartUp% (/Windows/StartUp)
%Windows-StartMenu% (/Windows/Start Menu)
%Windows-StartMenu-Programs% (/Windows/Start Menu/Programs)
%Windows-StartMenu-Programs-Games% (/Windows/Start Menu/Programs/Games)
Useful Resources
Windows Mobile Builds
Da_G All-In-One Windows Mobile 6.5.x Builds (Strongly recommended, contains all languages and all resolutions needed for almost any device)
Latest SYSs and OEMs XDA thread (where all the latest SYS builds are posted)
Common EXT Packages
(if you have suggestions or know where to find newer versions please post them)
Latest Touch Pro 2 EXT Packages (English-only, WVGA only)
Coming soon...
Help wanted!
1. Kitchen translation
Translators for the kitchens are needed! The kitchen is now completely localizable and will generate a translation template in the Resources\Localization folder when it's started up the first time: that file can be easily edited to translate all the text of the kitchen (also include an about entry for credits) and the kitchen will validate it and keep it updated every time it's launched organizing the entries that are missing or not found. If somebody has some spare time to help me translate the kitchen in other languages please attach a translated lng file to a post so I can include it in the kitchen archive.
2. Informations about the WM6.5.X packages required for each language
In order to improve the automatic localized packages selection I need to know which of the following packages:
Code:
BronzeEA BronzeNonEA BronzeAH | CommonEA CommonNonEA | SYSTEM_DEFAULT_FONTS COMPLEXSCRIPT_FONTS | gb18030 | Riched20 Riched20_CS | SipAR | Transcriber UNISCRIBE | Webview Webview_CS
are needed for each of the following languages:
Code:
0402 BRG Bulgarian (Bulgary)
0404 CHT Chinese Traditional
0405 CSY Czech (Ceská republika)
0408 ELL Greek (Ellas)
0411 JPN Japanese
0412 KOR Korean
0415 PLK Polish (Polska)
0419 RUS Russian
041B SVK Slovak" (Slovensko)
041D SVD Swedish (Sverige)
041F TUR Turkish (Türkiye)
0424 SVN Slovenian (Slovenija)
0804 CHS Chinese Simplified
081A SPB Serbian (Latin)
If anybody knows the right packages needed for one (or hopefully more) of those languages please let me know.
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
jagan2 said:
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
Click to expand...
Click to collapse
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
For the rest, great kitchen!
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Upload 23529 and I'll give this kitchen a whirl
Cheers.
KilZone said:
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Click to expand...
Click to collapse
It's because my sources are from 2.7 and didn't update the titlebar.
KilZone said:
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
Click to expand...
Click to collapse
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
dickenz said:
Upload 23529 and I'll give this kitchen a whirl
Cheers.
Click to expand...
Click to collapse
It was already up but with the wrong name (28223), now names are fixed.
Awesome, thank you that clears it I guess. Just forgive my stupidity... Downloading the ... latest ... version now (and updating my current version).
airxtreme said:
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
Click to expand...
Click to collapse
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
dancer_69 said:
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
Click to expand...
Click to collapse
Yes, I think I added its device file.
I'll download now and test, thanks.
EDIT
I just checked and I allready have this version(Os kitchen 1.4 RC2.7)
and I have successfully build an nbh with this version, I just not flash it yet.
So, it's supported.
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
rgb-rgb said:
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
Click to expand...
Click to collapse
Give me the link to download the rom so I can try to see why no OS.nb is detected.
airxtreme said:
Give me the link to download the rom so I can try to see why no OS.nb is detected.
Click to expand...
Click to collapse
http://www.htc.com/us/support/tilt-2-att/downloads/
Third download on the list. Complete ROM
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
jagan2 said:
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
Click to expand...
Click to collapse
http://www.mediafire.com/?zy0ejwmiwmy
PLEASE SEND THIS AS A FEEDBACK TO MS TOGETHER!
Well, it seems I don't have permission to post it to the development thread so I've got to post it here~
I found that on Windows 10 Technical Preview for phones, you could easily access C:\ in File Explorer.
All you have to do is to create a shortcut on your PC which links to C:\ then copy it to your phone.
Just click it in File Explorer on your Phone then you could see the files & folders in C:\, AND IT IS READ-ONLY.
However I failed to access D:\WPSystem using the same way, so I suppose it's just a bug. Don't know whether Microsoft will fix it in the next version.
See the attachments for screenshots.
And something interesting:
Found a folder named "Program Files(x86)", does that mean there will be x64 support for Windows 10?
Hey, Nice Findings, Nice Research !
I Like It
Interesting.
probably no x86 64bit support, as windows Phone runs on arm (until x86 based processors become standard in phones)