Flame Kitchen Tools v0.4 Alpha - General Topics

From Flame Kitchen Pre-Alpha Version 0.3
http://xdaflameusers.com/viewtopic.php?id=385
Here comes Flame Kitchen Tools v0.4 Alpha. Cooking your own WM5 Rom is now possible.
WARNING
- USE AT YOUR OWN RISK OF BRICKING YOUR DEVICE.
- Flash is only strictly for those who can and able to flash back their own original Rom.
- At the time of publishing this kitchen, authors only managed to cooked WM5 Roms. You may try WM6 at your own risk.
Consolidated by
XdaFlameUsers.com XFU Team
- cwkj
- k.satirli
- thierryb
Many many thanks to all the people (long list of name) from XDA-DEV who have make the so many tools (Bepe, mamaich & many) used here available.
The extraction part is an attempt by copying and adapt from SCOTER Kitchen by JKR I found in XDA-Dev.
The Add File, Delete File and Build is an attempt by copying and adapt from Laurentius Kitchen
Special Thanks to chaimd (for template.bin), comnex, misar, scorpio16v, tjlabais & many
Hope it is useful.
0. Read this Post and all the *.txt files that can be found in the kitchen before you start
- Readme.txt
- PutOriginalDiskimageNb0Here.txt
1. Extraction Steps
i. Drag & Drop the diskimage.nb0 to dump.lnk in "ExtractionRoom" to get Dump files in Tools.
or
Place original diskimage.nb0 in Tools. Type "dump.cmd diskimage.nb0" in Tools to get Dump files in Tools.
(if you do not have a diskimage.nb0 in your extended rom, look for Russian Flame nk.nba to try, http://4pda.ru/forum/attach/839243/flame_nk.rar , rename downloaded nk.nba to diskimage.nb0)
ii. The Dump can be view in Tools before 4. As it is not yet migrated to new Package tools by Bepe, so to view the Dump later after 4, make a copy from Tools to "ExtractionRoom" first.
2. Add Files
i. Using normal copy command, just add the PpcPimBackup.exe file in Dump of Tools. (Example, freeware by DotFred, can be found in XDA-Dev)
ii. If your additional apps needed registry, you need to know how to add registry a new *.rgu file for your new apps.
3. Delete Files
i. Using normal delete command, just delete the PMSN.cpl file in Dump of Tools. (Example)
4. Dump to Package
i. Remove or move "ExtractionRoom\Package\" if any.
ii. After Step 2 & 3,
Run package.lnk in "ExtractionRoom" to get Package files in "ExtractionRoom".
or
Run package.cmd in Tools to get Package files in "ExtractionRoom".
5. XIP Extraction (Skip this step for WM5 Cooking)
i. Place original diskimage.nb0 in Tools.
ii. Run "xip.cmd diskimage.nb0" to get XIP.BIN in Tools.
or
Type "RomMaster.exe diskimage.nb0 -w 5 -b 0x1C0000 -x -o xip.bin" to get XIP.BIN in Tools.
iii. Run xipport.cmd which gets into XIPPort.exe.
or
Run XIPPort.exe.
iv. Click "dump xip.bin" to get dumped XIP.BIN in Out of Tools
v. You can edit the XIP in Out. (if you know how to and needed for WM6)
vi. Click "make pkgs" to get packages in Out of Tools (still not sure how to use the packages), click "Undo" to reverse it back to iv.
vii. Click "realloc P" (errors found is known problem, but it is ok)
viii. Click "write map" to get Map.txt in Out.
ix. Click "build xip_out.bin" to get XIP_OUT.BIN in Out of Tools
x. Do not exit yet as you need to run 7i after 6
6. Build
i. Copy the original diskimage.nb0 to Rom.
ii. Run builtOs.cmd in FlameKitchen to,
- move Oem and Sys in Package to the Oem and the Sys in FlameKitchen,
- move Xip files from Out\Files in Tools to Rom\Xip in Flamekitchen, (Skip this step for WM5 Cooking, a copy of simplified XIP is already there but hidden)
- get into BuildOs.exe.
or
Copy
- Oem and Sys in Package to the Oem and the Sys in FlameKitchen.
- Out\Files\*.* in Tools to Rom\Xip in FlameKitchen. (Skip this step for WM5 Cooking, a copy of simplified XIP is already there)
Run BuildOs.exe.
iii. In BuildOs.exe, click the play button.
iv. After 6iii is completed with no errors, run CreateRom.cmd.
v. After 6iv is completed with no errors, you should see the new diskimage.nb0 in \FlameKitchen\Flash or \FlameKitchen\temp.
7. Put XIP back in diskimage.nb0 (Skip this step for WM5 Cooking)
i. Backup if any, your original diskimage.nb0 in Tools used in 1.
ii. Copy the new diskimage.nb0 from \FlameKitchen\Flash or \FlameKitchen\temp to Tools
iii. In XIPPort.exe from 5ix, change to 001C0000 and diskimage.nb0.
iv. Click "write xip_out.bin to:" to combine xip_out.bin with diskimage.nb0 copied in 7ii from 6v.
8. Check
i. To check if the files are added and deleted correctly into the new diskimage.nb0 by using the new diskimage.nb0 and go to Step 1ii.
9. Flash
i. http://www.xdaflameusers.com/viewtopic.php?pid=2045#p2045
Edit 1 : Kitchen 0.4 undocumented
If you use DumpRom.Cmd, it needs some changes, if you do not understand below, than just follow above instruction,
- "Dump.cmd" to "Dump.cmd %1", copy original diskimage.nb0 in Rom directory and run "DumpROM.cmd ..\ROM\diskimage.nb0"
or
- "Dump.cmd" to "Dump.cmd ..\ROM\diskimage.nb0", copy original diskimage.nb0 in Rom directory and run "DumpROM.cmd"
Edit 2 : Chinese Version Translated by laoniu.
Edit 3 : Others and improvement
1. devictoria has release another ROM Kitchen in this forum.
2. afeng has added the tools created by chaimd to the current v0.4 over at iio2 forum.
Edit 4 : laoniu has improved the kitchen at mobile-wolf forum for WM6.1.
Download:

Flame Kitchen Tools Pre-Alpha v0.3
From Flame Kitchen Tools Pre-Alpha v0.2,
http://xdaflameusers.com/viewtopic.php?pid=538#p538
http://forum.xda-developers.com/showthread.php?t=326943
Here comes Flame Kitchen Tools Pre-Alpha v0.3.
WARNING
- USE AT YOUR OWN RISK OF BRICKING YOUR DEVICE.
- Flash is only strictly for those who can and able to flash back their own Rom.
Consolidated by
XdaFlameUsers.com XFU Team
- cwkj
- leek
- k.satirli
- thierryb
Many many thanks to all the people (long list of name) from XDA-DEV who have make the so many tools (Bepe, mamaich & many) used here available.
The extraction part is an attempt by copying and adapt from SCOTER Kitchen by JKR I found in XDA-Dev.
The Add File, Delete File and Build is an attempt by copying and adapt from Laurentius Kitchen
Special Thanks to comnex, misar, scorpio16v, tjlabais & many
Hope it is useful.
0. Read this Post and all the *.txt files that can be found in the kitchen
- Readme.txt
- PutDiskimageNb0Here.txt
- PutNkNbaHere.txt
1. Extraction Steps
i. Drag & Drop the diskimage.nb0 or nk.nba to dump.lnk in "Extraction Room" to get Dump files in Tools.
or
Place original diskimage.nb0/nk.nba in Tools. Type "dump.cmd diskimage.nb0" or "dump.cmd nk.nba" in Tools to get Dump files in Tools.
(if you do not have a diskimage.nb0 in your extended rom, look for Russian Flame nk.nba to try http://4pda.ru/forum/attach/839243/flame_nk.rar , diskimage.nb0 is same as nk.nba)
ii. The Dump can be view in Tools before 4. As it is not yet migrated to new Package tools by Bepe, so to view the Dump later after 4, make a copy from Tools to "Extraction Room" first.
2. Add Files
i. Using normal copy command, just add the Hibernate.exe file in Dump of Tools. (Example)
3. Delete Files
i. Using normal delete command, just delete the PMSN.cpl file in Dump of Tools. (Example)
4. Dump to Package
i. After Step 2 & 3,
Run package.lnk in "Extraction Room" to get Package files in "Extraction Room".
or
Run package.cmd in Tools to get Package files in "Extraction Room".
5. XIP Extraction
i. Place original diskimage.nb0 in Tools.
ii. Run xip.cmd to get XIP.BIN in Tools.
or
Type "RomMaster.exe diskimage.nb0 -w 5 -b 0x1C0000 -x -o xip.bin" to get XIP.BIN in Tools.
iii. Run xipport.cmd which gets into XIPPort.exe.
or
Run XIPPort.exe.
iv. Click "dump xip.bin" to get dumped XIP.BIN in Out of Tools
v. You can edit the XIP in Out. (if you know how to)
vi. Click "make pkgs" to get packages in Out of Tools (still not sure how to use the packages), click "Undo" to reverse it back to iv.
vii. Click "realloc P" (still not successful with errors)
viii. Click "write map" to get Map.txt in Out.
ix. Click "build xip_out.bin" to get XIP_OUT.BIN in Out of Tools
x. Do not exit yet as you need to run 7i after 6
6. Build
i. Copy/Rename the original diskimage.nb0 to nk.nba.
ii. Copy the nk.nba to Rom.
iii. Run builtOs.cmd in FlameKitchen to,
- move Oem and Sys in Package to the Oem and the Sys in FlameKitchen,
- move Xip files from Out\Files in Tools to Rom\Xip in Flamekitchen,
- get into BuildOs.exe.
or
Copy
- Oem and Sys in Package to the Oem and the Sys in FlameKitchen.
- Out\Files\*.* in Tools to Rom\Xip in FlameKitchen.
iv. In BuildOs.exe, click the play button.
v. After 6iv is completed with no errors, run CreateRom.cmd.
vi. After 6v is completed with no errors, you should see the new nk.nba in \FlameKitchen\temp.
7. Put XIP back in nk.nba
i. Backup if any, your original nk.nba in Tools used in 1.
ii. Copy the new nk.nba from \FlameKitchen\temp to Tools
iii. In XIPPort.exe from 5ix, change to 001C0000 and nk.nba.
iv. Click "write xip_out.bin to:" to combine xip_out.bin with nk.nba copied in 7ii from 6vi.
8. Check
i. To check if the files are added and deleted correctly into the new diskimage.nb0/nk.nba by using the new diskimage.nb0/nk.nba and go to Step 1ii.
9. Flash
i. http://www.xdaflameusers.com/viewtopic.php?pid=2045#p2045
Download: FlameKitchenPreAlphaVersion0.3.zip (1.68MB 19 views)

Reserved ...

Reserved...

Reserved...

Thank you !!!

Here is another version by deVictoria
http://xdaflameusers.com/viewtopic.php?pid=4778#p4778

Reserved...

sometime said:
Reserved...
Click to expand...
Click to collapse
I reserve for future version, you reserve for what?

How to add registry? for instance, the prince kiss registry by EFN at xdaflameuser.... any directional link?

Related

[Full Guide Thread] TNT.Kitchen for Wizard, Auto XIP Porting and Modules Relocating

hi,
As promissed, this is my special Kitchen for Wizard users and chefs. This kitchen is based on Bepe kitchens with some edits on nb file and batches to work well with our Wizard devices.
With this kitchen and guide, all beginners can going very fast to be an expert, so this is suitable for all (experts and beginners).
===============================================
Change Log:
5-Aug Update: 5.2.20273 build 5.2.20273.1.3.3 SYS and XIP (check 2nd post).
13-May Update: 5.2.19213 build 5.2.19213.1.0.4 SYS and XIP (check 2nd post).
29-Apr Update2: 19202 buid added in downloads post as SYS and xip.bin.
29-Apr Update1: another CreateROM.bat to cancel combining all packages to one.
28-Apr Update: date of creating this thread.
===============================================
Kitchen Advantages:
- Real porting for xip in auto mode (no need for write addresses or whatever)
- Auto Relocating for modules (no need to edit .VM folder in SYS)
- All dsm will be combined in one dsm (so, windows folder has only one dsm, no overloading, and this will save more than 1 MB from the Kitchen)
- All RGU will be auto encrypted.
- The kitchen will give you a notice that your packages are overload (no need to flash to test).
===============================================
Requirements:
- you have to download: Microsoft Visual C++ 2008 Redistributable Package.
- Wizard Device.
- SYS folder from the build you want to use.
- OEM folder which contains Drivers and your packages.
- XIP modules from the build you want to port.
- Give some credits if you plan to share your releases.
===============================================
How to start cooking:
1- Extract TNT_Kitchen_for_Wizard to C: dirctory on your PC.
2- Copy SYS folder you want to use to the Kitchen.
3- Add your OEM packages to OEM folder.
4- Run BuildNB.bat.
5- wait until BuildNB.bat shows "press any key to continue".
6- go to nbf folder.
7- run nb2nbf.exe.
8- in Language, choose WWE.
9- tick File #1 and then choose your 80040000-OS.nb file.
10- go to Image Name and choose OS.
11- on the right top corner, choose Translate.
{
"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"
}
12- open nbf folder and run Vista_ROMUpdateUtility.exe if you have vista operating system, or XP_ROMUpdateUtility.exe if you have XP operating system.
===============================================
Some Hints:
- How to know that your packages is larger than what you have to load??
- if you see this msg, so you have to remove some packages:
- How to minmize SYS folder Size??
- there are many of useless packages located on SYS folder, try to see what you don't need and remove.
===============================================
How to port XIP from any new build:
- extract xip.bin from the build you want to port from.
- Download Bepe xip port
- extract xipport to any folder
- the folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to prot. (i will put xip.bin from different new builds)
- run XIPProt.exe
- press Dump xip.bin
- you will have OUT Folder
- press Make Pkgs
- now, open OUT folder, you will have Files and Modules.
- for each folder (Files and Modules) copy MSXIPKernel and MSXIPKernelLTK contents (Note: without .txt files) and paste them to /ROM/XIP folder and replace.
- now, if you cook, you will have the new build with real port.
===============================================
How to port SYS from any new build:
Just extract SYS folder from the new rom you want to use its SYS folder, and paste the new SYS to the kitchen (you have to see the suitable extracting kitchen from the device you want to get SYS folder from it, and also i will upload SYS folder from any new build to direct use)
===============================================
Which OEM Drivers and Apps can you use:
you can search for this yourself, and there are many of them, you can use boy_de_ghet from Here, or use double_ofour OEM which can be found here, also Faria thread contains good OEM (but maybe old). on these packages, you can use Drivers and apps with no problems for Wizard ( OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE...)
from other devices, you can use OEM packages from mattk_r packages (without using the drivers located on that OEM Folder, because they are for Hermes only) the thread can be found here, also maybe they are a little bit old, but you should find something intersted. (you cannot use
OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE.. which are for Hermes Device, just get the other packages)
===============================================
Some Packages should be located in OEM to make your rom bootable:
your OEM should contains: OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS, WinCENLS_WWE (maybe this will be in SYS) and SecurityOff. also, maybe LangDB and Default packages.
All mentioned above are suggestions (maybe experts know about that more than beginners)
===============================================
How to make new packages for your own:
you can learn that yourself by searching and learning, it is very simple but needs nice relax from you, i suggest to read Faria thread to learn how to create your own packages. another very useful thread by double_ofour can be found here
Downloads:
========================
TNT_Kitchen_for_Wizard: contains the base kitchen without SYS and OEM. the orioginal XIP in this kitchen is 5.2.19209
Rapidshare
========================
5.2.19209 SYS Folder: contains SYS folder extracted from Kaiser, just copy SYS to the kitchen
Rapidshare
=======================
29/Apr update1
CreateRom without combining all packages to one: all you need to do is to download this file and put CreateROM.bat in TOOLS folder and replace.
=======================
29/Apr update2
XIP.bin from 19202 build: as mentioned before, use xipport.exe to extract this xip and read guide to know where to extract and what to extract
Download
SYS from 19202 build: just copy SYS to the kitchen
Rapidshare
=======================
13/May update
XIP.bin from 19213 build: as mentioned before, use xipport.exe to extract this xip and read guide to know where to extract and what to extract
Download
XIP Folder from 19213 build: this is the whole folder of XIP which should be located in Rom folder, so just remove the older one and paste this one.
Download
SYS from 19213 build: just copy SYS to the kitchen
Rapidshare
=======================
5/Aug update
XIP Folder from 20273 build: this is the whole folder of XIP which should be located in Rom folder, so just remove the older one and paste this one.
RapidShare
SYS from 20273 build: just copy SYS to the kitchen
RapidShare
Notes:
- you have to unlock your device before flashing, for more details in flashing notes visit this thread.
- i'm not responsible for any damage on your device.
========================================
Important Links:
- How to determine if your Wizard is a G3 or a G4
- CID Unlock your G3 Wizard (Only for Wizards with less than AKU2)
- Easy guide to CID unlock G3 Wizard
- Solution for CID Unlocking G3 Wizard with AKU2 or higher
- CID Unlock your G4 Wizard Hard-SPL
- CID Unlock your G4 Wizard Soft-SPL
- Unlocking and Upgrading G3 Wizards
- Howto flash a Wizard... a little tutorial!
- How to SIM unlock the Wizard
- HOW To Change the Pagepool (WM5)
- HOW To Change the Pagepool (WM6)
- XDA-Wiki for Wizard which contains huge informations needed.
Credits:
- ofcourse first one is Bepe for his great tools
- tom_condon for helping me on so many things in cooking
- misar for his tools in relocating modules
- all the nick names i used in this thread (faria, double_ofour, boy_de_ghet, mattk_r, and vippie)
- for jwzg for the good arrangement in our forums.
================================
i hope you get some useful tools and informations to learn and improve your cooking.
Good Luck and have a nice cooking .
================================
if you don't have the time for cooking, you can download any rom, feel free to see my sign. and click on the latest wizard rom mentioned there.
Perhaps I should build my own. This should be interesting.
Thanks man, you always do a great job.
Please creat kitchen buit 19701 new !!!!
OS 5.2.19701
Vesion clean !
Done.
i will update the thread with the suitable informations and links to keep our working better.
if you think that there are some of useful threads just let me know to edit my posts .
good luck guys .
amsatnetg said:
Perhaps I should build my own. This should be interesting.
Thanks man, you always do a great job.
Click to expand...
Click to collapse
ofcourse you have to build your own (if you have the time)
c28langthang2010 said:
Please creat kitchen buit 19701 new !!!!
OS 5.2.19701
Vesion clean !
Click to expand...
Click to collapse
where is this??
point me and let me do it for you .
well done it's right, i am going to see if i can cook using your kitchen. I was completely clueless when it came to porting a "real" rom from one device from another so i can now see the light. This definately deserves to be a sticky!! thanks again
newbie1221 said:
well done it's right, i am going to see if i can cook using your kitchen. I was completely clueless when it came to porting a "real" rom from one device from another so i can now see the light. This definately deserves to be a sticky!! thanks again
Click to expand...
Click to collapse
you will use it with no problem at all, and i'm sure you will increase your packages size (in case of dealing with 19209 SYS by removing the useless packages from it).
Good luck bro .
Nice Kitchen! I ported 19701 and it works greats! But now the SYS folder... The 19701 from PDAVIET is protected. Can someone provide it or knows how to extract it?
j.vd.spank said:
Nice Kitchen! I ported 19701 and it works greats! But now the SYS folder... The 19701 from PDAVIET is protected. Can someone provide it or knows how to extract it?
Click to expand...
Click to collapse
is it difficult?
about the protuction, no one can open it.
any rom will be cooked using the kitchen here can't be extracted, PDAVIET used the same tools included on this kitchen
its right said:
is it difficult?
about the protuction, no one can open it.
any rom will be cooked using the kitchen here can't be extracted, PDAVIET used the same tools included on this kitchen
Click to expand...
Click to collapse
Not difficult... I can share if someone is interested, but without SYS folder its 'useless'. So we have to wait when someone releases a kitchen
j.vd.spank said:
Not difficult... I can share if someone is interested, but without SYS folder its 'useless'. So we have to wait when someone releases a kitchen
Click to expand...
Click to collapse
i don't prefer the builds that not provided by microsoft, many of builds are hacked like 19400 and yours, so i don't think you will find SYS folder simply.
Very well done wise man!
I'm going to start on my own and report the results later
Thanks a lot for sharing
epimazzo said:
Very well done wise man!
I'm going to start on my own and report the results later
Thanks a lot for sharing
Click to expand...
Click to collapse
you are welcome, have a nice cook man .
its right said:
Downloads:
========================
TNT_Kitchen_for_Wizard: contains the base kitchen without SYS and OEM. the orioginal XIP in this kitchen is 5.2.19209
Rapidshare
========================
5.2.19209 SYS Folder: contains SYS folder extracted from Kaiser, just copy SYS to the kitchen
Rapidshare
=======================
Click to expand...
Click to collapse
The two links are to the same file.....
Andy
nice job =D
i'll try it myself
ADB100 said:
The two links are to the same file.....
Andy
Click to expand...
Click to collapse
no they are different
but after editing , thanks for that.
Itsright,
Got little confused...
During cooking process, only DUMP is created together with log.txt. That's all found inside temp folder. Shouldn't expect boot.rgu and nb file? I added my own stuff like OEM and SYS parts. no issues here.
XIP is also already in but didn't got your point related to OS.NB.PAyload.
What actually does it mean?
Maybe I should review something left behind...
I appreciate other comments too...
Rgs

[KITCHEN][04/Jan/11]ELF(in) Kitchen(s)[ONLINE]

INTRO
I started trying to make a kitchen for our Elves based on bepe's Extended Kitchen and Elf(in) Hybrid Kitchen was "born".
Since then, bepe released his famous PlatformReBuilder(PRB) and I followed him, creating B2 Kitchen (page41 and on).
The Hybrid Kitchen is discontinued but I will keep it posted here for anyone who wants to play with it.
B2_Kitchen has started as an Elf(in) kitchen, but became a multidevice kitchen.
B2_Kitchen has started as a simple batch-file kitchen, but became a multifunctional kitchen.
At the end it is a GUI based on command-line tools just like some other visual kitchens.
The main applications are PlatformReBuilder and ImgfsTools.
So I don't actually feel that I made something new...
I take no credit!
CREDITS TO
bepe for the kitchens and other tools,
pof for the USPL, cmonex for the HSPL,
itsme , mamaich & tadzio for the brilliant but simple tools,
ervius for the great tools,
Noonski for the cooking class [This is how newbies gain the knowledge to cook] and for the inspiration,
Ababrekar for guideness in porting OS from another device,
Aman for sharing his knowledge&helping me make any fixes&upgrades
and many more members/developers of this forum which I consider as a free on line school whose tools and guides made this possible!
These kitchens are free to use or edit but at your own risk, I take no responsibility for any damage caused to your phone!​
B2 Kitchen
B2 Kitchen GUI (LATEST VERSION 2.0.0.0)
Supported Devices:
Elfin
Leo
Diamond
? (Testers Needed for other devices)
INSTALLATION:
Prerequisites:
Microsoft .NET Framework 3.5 (Windows Vista / Windows 7 have it pre-installed)
If you're using Windows Vista / Windows 7, make sure USER ACCESS CONTROL is turned OFF!
DO NOT change the structure of the kitchen!
If you don't want to use ImDisk Driver, you should get another 3rd party software able to create a RamDisk in order to use the relevant feature.
Installation:
Once you download the kitchen, install it following on screen instructions.
When you launch the kitchen for first time you'll get the chance to install ImDisk Driver if it isn't already installed.
(RECOMMENDED if you don't have another 3rd party software for Virtual Drive Management)
To get started, you should import a device by using an official_shipped_ruu.exe as a source.
Otherwise you could place your files manually.
(Be careful to put them in the correct way, respecting the kitchen's structure)
Download links:
Mediafire(For ALL users)
XDA(For XDA members)
********************************************************************************************************************
DESCRIPTION:(Video)
{
"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"
}
Dump any source you want in almost any known format:
RUU_Device_HTC_Version_Signed_Ship.exe
RUU_Signed.nbh
Flash.dio
OS.nbf
OS.nb.payload
OS.nb
nk.fat
Imgfs.bin
xip.bin
Part01.raw and Part02.raw
Import a new device by dumping the device's OFFICIAL Rom RUU_Device_HTC_Version_Signed_Ship.exe.
The kitchen will even create a CustomRUU.exe AND a Task29.exe for the imported device.
Import any new leaked build just with one click.
When you dump a rom / import a new device the kitchen is able to:
Remove any empty packages if you select -EmptyPkgs.
Sort each registry file from your dump to make it more readable if you select SortRegistry.
Sort all Packages into the required style.
Sort all manila localization files by lcid.
Build your rom according to your taste:
Set which packages will be included from the "Packages Selection" area.
Set Rom version, language, ModelID and CountryID that are required for generating the final flashable *.nbh. The Rom date will always be automatically set to current date.
Select among various builds and lcids which one to use for building your Rom.
Select whether to use a real 6.5 nk (if your device has a 6.5 nk) or not in your generated Rom by selecting 6.5nk.
Select whether to use ShaDrac's driver - Extendir - or not by selecting Extendir, without messing up (adding/removing Extendir.dll - editing boot.rgu) your XIP each time.
Select whether to reduce/remove ULDR or not at your generated Rom by selecting -uldr.
Select whether to increase the Storage Memory of your Rom or not by selecting -imgstart.
Choose your Rom's PagePool Size (0-20).
Select compression (XPR-LZX-None) method for building your Rom.
Add Radio and Splashscreen to your final flashable *.nbh.
Set the kitchen to take care the "SLOT 0 overfloating" issue when building a 6.5 Rom while your nk.exe is not a real 6.5 nk.exe by selecting Rec.Mod SYS
If you have used the above option and have recmodded some modules inside SYS/Shared in order to fix the "SLOT 0 overfloating" issue when no real 6.5 nk.exe is available, but now you want to use the same Build (= the same SYS/Shared) for building a new Rom for a device that has a real 6.5 nk.exe you can reversmode the same files by selecting Rev.Mod SYS.
Set the kitchen to search and find any duplicate items in your compilation that would cause crashing issues to PRB before starting the real building process by selecting DuplicateCheck.
Each time you build a rom a log file is created which you can easily see by clicking the "Process" Label.
Search for files or file's content (i.e. Search for a certain registry entry among *.reg files) using the search engine of the kitchen.
Access fast and easy certain files that are commonly used inside a Rom.
You can see lists of *.txt, *.mscr , *.xml , *.provxml , *.cpr & *_manila inside your kitchen by simply clicking the relevant button.
If you click on any file you see in those lists you open it for editing.
Flash any ROM you selected from a list of your created Roms to your device.
You'll get the chance to perform task29 on your PDA - THEN manualy enter Bootloader and FINALLY update the ROM if you have that special CustomRUU inside the kitchen.
Use a RamDisk (ImDisk Driver comes with this kitchen) for the building and dumping processes in order to gain speed and decrease hard disk fragmentation.
Cfc manila files and convert any normal Manila_package to a compressed one just with one click.
Exploit the possibilities of MortScript even during building your Rom:
Forget about app.dat - app.mscr is introduced in this kitchen.
Don't cook in hundreds of files that get copied to various locations but at the same time stay in your "Windows" directory slowing down your device - Create just one archive (app.xdaz) which extracts the files to the correct locations during boot leaving in "Windows" directory only one file with an unknown extension.
Convert cabs--->EXT Packages just with one drag n' drop on a button.
Convert files<-->modules just with one drag n' drop on a button.
Convert rgu files<-->hives just with one drag n' drop on a button.
Convert provxml files<-->reg files just with one drag n' drop on a button.
Convert bmp<-->nb just with one drag n' drop on a button.
Install any cab file to your pda just with one drag n' drop on a button.
Manipulate each package from the "Packages Selection" area just with one click:
Double click on the package to open its folder
Right click on the package to:
Edit directly the package's app.reg.
Edit directly the package's app.dat.
Edit directly the package's app.mscr.
UPX one/all package's executable(s).
Optimize package's png(s).
Optimize package's bmp(s).
Repack package's *.mui files.
Recmod one/all package's module(s).
NosplitMod one/all package's module(s).
Revmod one/all package's file(s).
Install the package to your pda.
Edit directly the initflashfiles.dat of the selected language just by right clicking inside the "Locale" box in the "Configuration" area.
Edit directly the boot.rgu of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
If you want to edit directly the boot.rgu for the Extendir driver just right click the Extendir checkbox.
Read/Write directly the packages.cif and packages.sof of the selected build just by right clicking inside the "Build" box in the "Configuration" area.
Optimize XIP & SYS of the selected build just by right clicking inside the "build" box.
Build 3 different editions of your rom just by selecting an "Edition" (Premium, Basic, Lite) in the "Configuration" area.
This is optional, so if you leave "Edition" blank, then the "P" , "B" , "L" selection in the "Packages Selection" area doesn't matter!
Keep the kitchen accessible at all time. When you close the kitchen, it minimizes to tray from where you can access many functions and browse the kitchen's folders. By double clicking the tray icon you restore the kitchen's window.
If you want to really exit the kitchen while it is visible press F1!
Easily uninstall the kitchen from your system.
Easily save/load your project:
If you double click the "Save" icon then you'll save your current project (its name will be the Edition.build.locale.date&time of saving).
If you click the "Save" icon then you can select from a list of your projects which one to load.
Easily access all the tools that come with the kitchen. Even assign your own favorites to ALL the bottom buttons.
Check existing registry files for errors before building your Rom by right clicking the "Packages Selection" Label.
The time of this operation depends from the number of registry files, so you either give it enough time to finish if you have a lot of packages in your compilation or you click the Stop button to abort it.
Control your pda from inside the kitchen:
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
View/edit/dump your device's registry.
********************************************************************************************************************
BASIC USAGE:
***Valid for any device - Just consider your device's name instead of the Elfin***
Packages Selection:
You can see all the SYS Packages from the BUILD & LOCALE you've chosen.
You can see all the EXT Packages you have in the kitchen's directories.
You can make sub-directories(limitation:up to 16!) to organize them better(i.e. EXT\Elfin\Tweaks , EXT\Elfin\TodayItems , EXT\Elfin\Apps , EXT\Elfin\Utilities , etc) and place your packages inside each sub-directory.
You can select which packages to include in your ROM by ticking the checkbox in front of the package's name. If you have it unticked then the package will be skipped.
If you double click inside the selection cell but not on the checkbox then you can select/deselect ALL packages.
You can see in the "Packages Selection" area that there are 3 columns "P" , "B" , "L" following the Package's name.
These will have an effect ONLY IF you select an Edition under "Configuration" area!
Code:
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]P[/B]remium edition then you must have the checkbox under "[B]P[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]B[/B]asic edition then you must have the checkbox under "[B]B[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
If you want "Package1" to be [COLOR="YellowGreen"]included[/COLOR]/[COLOR="Red"]excluded[/COLOR] in your [B]L[/B]ite edition then you must have the checkbox under "[B]L[/B]" [COLOR="YellowGreen"]ticked[/COLOR]/[COLOR="Red"]unticked[/COLOR].
There is also a ZIP Column. That Column is used to "mark" which EXT Packages you wish to convert to "Mscr_Packages" when you click "ExtToMscr" option.
Code:
If checkbox = unticked then nothing will change.
If checkbox = ticked then Selected Package will be converted to a Mscr Package (this is useful ONLY for applications that get installed to Program Files)
If checkbox = greyed then Selected Package will be converted to an Extendir Package (this is useful ONLY for applications that get installed to Windows and you're cooking Extendir in your Rom)
When you click the "ExtToMscr" the kitchen creates an archive (with the extension *.xdaz) from the Package's files and writes the necessary "app.mscr" (something like the equivalent of "app.dat").
For this it needs the "app.dat" inside the EXT Package so that it translates it to "app.mscr".
(This operation doesn't take place each time you hit the build button)
Your (original) EXT Packages will be copied to TOOLS\pkg\EXT.bak as a backup and only the (converted) Mscr Packages will be kept inside EXT[folder].
These new packages will be used ONLY IF you select "mscr" for ARType( = AutoRun Type) in the "Configuration" area.
Of course MortScript MUST be included in your Rom AND you must have the ARMS.mscr (script with #INSERTLINE switch) inside Autorun.mscr\Elfin folder.
Click to expand...
Click to collapse
Main Functions:
Obligatory routine:
Select device.
Select build.
Select locale.
Clicking the "Dump" button presupposes that you have placed a Rom file inside BaseROM folder.
When the process finishes you'll get a full dump of that Rom.
Drag n' drop a Rom file on this button works the same way!
Right Click on "Dump" button will show you two options:
Import New Device
meaning use another device's official rom to dump&prepare everything that is required by the kitchen to operate.
When everything is completed you'll be asked whether to auto move files or not!
Import New Build
meaning use any archive with the new leaked build to import the included SYS and XIP packages to the kitchen.
Next to the "Dump" button is 1 icon :
The folder-icon is a menu that includes shortcuts to various kitchen's folders.
Clicking the "Build" button starts the building process.
Next to the "Build" button are 3 icons :
The first one is a menu that includes :
ImDiskGui
ExtToMscr
RomTools
RePackOEM
CFCManila
The second one opens the below window. From there you can turn on/off the RamDisk feature, uninstall the kitchen, set your custom (build) commands, etc.!
The third one opens the Search utility of the kitchen.
Clicking the "Stop" button you stop the process you've started.
Clicking the "Phone-icon" button you have the options to:
Select from a list with your created Roms which rom to flash.
Restart your connected pda without even touching it.
Enter BootLoader.
Watch a list of processes currently running on your device.
Launch CeRegEdit
Double clicking the "Phone-icon" button you access the RELEASE\Elfin folder.
Clicking the "Flash" button you minimize the kitchen and start the CustomRUU (ElfinCustomRUU) in order to flash the ROM you selected to your device.
Right Click on "Flash" button will show you the option to Format&Flash, meaning that you'll get the chance to FIRST perform task29 on your PDA (ElfinTask29) - THEN manualy enter Bootloader and FINALLY update the ROM.
Right Click on "Configuration" label will show you the Advanced PRB Settings panel.
Clicking on "Radio" label opens the radio sub-folder.
Clicking on "Splash" label opens the splash sub-folder.
Addons:
You can easily access all the extra tools that come with the kitchen. - Drag n' Drop works for every dark-GRAY button.
You can assign your favorite links to ALL the buttons you see at the bottom!
Those links can be applications, folders, batch files or urls.
In order to set your own you should edit the file myaddons.ini under TOOLS\addons\ keeping the format addon#|Name|Path :
(Just right click on the button you want to change)
Code:
addon1|CFF Explorer|C:\Program Files (x86)\Explorer Suite\CFF Explorer.exe
addon2|Tiny Hexer|C:\Program Files (x86)\mirkes.de\Tiny Hexer\mpth.exe
addon3|Icon Editor|C:\Program Files (x86)\Icon Editor\IcoFX.exe
addon4|Manila Kitchen|C:\Program Files (x86)\Manila_Kitchen
.
.
.
********************************************************************************************************************
TO DO:
Any suggestions are welcomed!
Any bug reports are appreciated!
B2 Kitchen's Structure
This is the structure of the kitchen after importing a device and you shouldn't try to change it because you will have errors!
The build 23545 you'll see in the below pictures is an example in order to help you understand the kitchen's structure.​
Autorun.mscr is the folder where you can put your mortscript file that runs at first boot(named ARMS.mscr).
This mscr must include a line "#INSERTPOINT" !!! This line is required so that all "app.mscr" will be added at that exact point of your script!
The ARMS.mscr must be placed inside the subfolder named after your device.
BaseRom is the folder where you can put any rom you want to dump.
EXT is the folder where you store all your EXT Packages that you want to try in your ROM.
Here you can put any application,utility,todayitem,etc. and choose whether to include it or not, having in mind if it is or not essential for the windows to work!
Those Packages must be placed inside the subfolder named after your device.
OEM is the folder where you have OEMApps, OEMDrivers and other OEMFolders (Device Specific). Check out trueg's posts for more information about these folders.
Those OEMFolders must be placed inside the subfolder named after your device.
If you are cooking a rom in a different language than WWE, then create that subfolder.
For example if I want to cook a greek rom I'll create a subfolder 0408 along with 0409 and place my local.files in 0408.
If you are using the kitchen in OEM mode you can put inside the "Pkgs" subfolder your old-style packages (with *.dsm , *.rgu , etc.). You'll be able to choose whether to include or not each of those from the kitchen's packages selection!
RELEASE is the folder where your custom ROM (i.e.Yourdevice_ROM_Lang_0409_Build_21056.nbh) will be placed after cooking in order to flash it to your device using your CustomRUU.
You must have a subfolder named after your device under RELEASE and be careful with the names of the included *.exes (YourdeviceCustomRUU.exe & Task29\YourdeviceTask29.exe).
ROM is the folder where the XIP is placed.
If you enter this folder you'll see :
Like it is shown above, you must have all the XIP elements, except MSXIPKernel, inside the subfolder named after your device.
If your device has WinCENLS_Lang_0*** as part of XIP leave it there, otherwise an adviced location to store it is OEM\Yourdevice\0***\.
SYS is the folder where all the OS Packages (Not device Specific , but I'd say Screen Resolution Specific) are stored categorized by build number. Check out trueg's and Da_G's posts for more information about these Packages.
You must place those OS Packages inside the subfolders SHARED, dpi_96 , dpi_96_resh_240_resv_320 , etc. like it is shown below.
TOOLS is obviously the kitchen's "engine".
(Each time you build a rom you should find in there a log file from the building process which you can access by clicking on the Process label of the main application)
Inside CORE\Saved folder you must have a subfolder named after your device.
Inside CORE\Devices.list(file) you must have the settings for your device.
$DEV=YourDevice'sName
<1 for device that has only wm6.1kernel , 2 for device that has wm6.1kernel AND wm6.5kernel , 3 for device that has only wm6.5kernel>
KERNEL=3
dpi=192
resh=480
resv=800
ModelID=PB8110000
CID=11111111
chunksize=64
GSMHeaderType=0x301
<" -s" Switch if device's Splash.nb requires smartphone signature , leave blank if device's Splash.nb DOESN'T require smartphone signature>
SplashSwitch=
SplashHeaderType=0x600
<Size of device's Splash.nb>
SplashSize=786432
<" -t 0" for 0x00 or " -t 255" for 0xFF>
SplashPaddingType= -t 255
OSHeaderType=0x400
<hermes for Sectorsize=0x208 , kaiser for Sectorsize=0x808 , titan for Sectorsize=0x800 , leave blank for Sectorsize=0x200>
NBMerge=kaiser
<reduce for device that ULDR can ONLY be reduced , remove for device that ULDR can be totaly removed>
ULDR=reduce
Click to expand...
Click to collapse
Inside Radios folder (see below) you can store any %radio%_0x30$.nb in order to use in your Rom:
You must place those Radios inside the subfolder named after your device.
You can find all Elf(in) Radios here.
Inside splash folder (see below) you can store any
%##splash%_0x60$.nb in order to use in your Rom.
%##splash%_0x60$.bmp is required for previewing!
You must place those Splashscreens inside the subfolder named after your device.
You can find more SplashScreens here or you could make your own with the kitchen tools.
B2_Kitchen_GUI is the GUI that combines all the command line tools. Screenshots here.
Elfin Hybrid Kitchen
ELF(in) Hybrid Kitchen (DISCONTINUED - NEWER KITCHEN @ 2nd POST)
INSTALLATION:
1. Install on your pc Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5!
2. Remove any previous version(if any)of the kitchen(shortcuts too) before "installing" the newer!
3. The archive should be extracted directly to the Drive where Windows are installed (most cases C:\) , otherwise nothing will work!
4. Once you do that, go into C:\ELF(in)_Hybrid_Kitchen and double-click "First_Run_For_ELF(in)_Hybrid_Kitchen.bat"!
5. IF you're using Windows Vista, make sure USER ACCESS CONTROL is turned OFF!
Download through: Mediafire
********************************************************************************************************************
DESCRIPTION:
(Be patient and keep your eyes on the DOS window for additional help&instructions while using this kitchen)
Main Functions:
[a] Dump any ROM from Kaiser, Polaris, Diamond, Xperia, Raphael, Elf(in)...
You may use these formats:
****.nbh (eg: RUU_Signed.nbh, Blue_Elves.nbh, etc) ,
****OS.nb (eg: New-OS.nb, 19588-OS.nb, etc) or ***windows.nb (eg:Mobile_windows.nb, New_windows.nb, etc) ,
****imgfs.bin (eg: imgfs.bin, new_imgfs.bin, etc) .
****.payload (eg: OS.nb.payload, 20270_OS.nb.payload, etc) . <- NOT FOR ELF(in) !
****.raw(only Part01.raw & Part02.raw) .
You get new OEM, SYS and xip.bin(unless you used *imgfs.bin) into C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp .
If you used an ELF(in) ROM then you'll get a full dump, OEM, SYS and XIP, that you could move to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19XXX\ and use it as a cooking base .
[b] Port any XIP from Kaiser, Polaris, Diamond, Xperia... You need xip.bin .
It requires:
NOT to change Ref_XIP folder inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP and
If you have any problems in XIP Porting you have all the needed tools inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP to try manually port the xip .
[c] Build your OS.nb (using the Ervius PkgToolsBuildos which can autofix & autorelocate SYS) .
You'll get the option to make a dumpable ROM using PkgToolsBuildos (by keeping unticked the box next to "All packages in one:") .
NOTE1: Inside ..\Build_ROM the OEM , SYS and ROM\XIP folders are empty . You may "fill" them with the required files .
NOTE2: Because Ervius PkgToolsBuildos is included in the kitchen, you could always use the functions that it provides apart from those described here .
NOTE3: If your xip_out.bin or out.bin is smaller than 2,49MB you could use the attached os.nb.payload (where imgfs start @ 0x280000)
[d] Flash any ROM to your device .
If you have a CID Locked device you have the option to flash a ROM using SoftSPL & your device remains CID Locked with the same SPL !
Additional Functions:
[1] Convert any cab to an OEM Package using Ervius Package Creator .
[2] Create a cab using IABovine's QuickCab 2.0 .
[3] Convert a bitmap to a Splash.nb (& reverse) using pof's nbimg .
[4] Convert files to modules & reverse using RecMod and reversmode . Not all files can be converted to modules.
[5] Convert 24 bit .bmp to .brn and reverse (for editing Cube gfx) .
[6] Compress executable files using UPX 3.03 .
Panel:
Easy access for many tools .
BASIC USAGE:
(Check out ayyu3m's great [PICTORIAL] COOKING YOUR 6.1 ROMS USING ELF(in) HYBRID KITCHEN)
1. Lets say you want to use a SHIPPED or DUMPED (NOT a COOKED!) ELF(IN) ROM as a Base.
--1.1.Double click the desktop-shortcut "Main Menu"
--1.2.Press [a]
--1.3.A window pops up beside the DOS screen. Place in there the RUU_Signed.nbh and close the window!
--1.4.Press [1]
--1.5.When the process is completed (& pressing any key returns you to main menu), you get another window opened with the files you want:
Packages(OEM&SYS)
XIP(folder)
xip.bin
--1.6.Keep that window open and double click the desktop-shortcut "Kitchen"
--1.7.Copy OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\
--1.8.Copy the XIP(folder) to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM\
2. The Base for cooking your ROM is set! Either clean up the OEM folder from things you wish to be removed or just (re)build the ROM.
--2.1.Double click the desktop-shortcut "Main Menu" (if you closed the main menu window)
--2.2.Press [c]
--2.3.PkgToolsBuildos starts
--2.4.Go to BuildOS Tab and click Load Rom.Select which Packages to include and press the green play button[Go]
--2.5.When this process is completed you'll have your OS.nb inside the "temp" folder and the (final product) RUU_Signed.nbh is generated in two places,
(i)..\CustomRUU\ <= For flashing CID Unlocked phones
&
(ii)..\RUU\ <= For flashing CID Locked phones using SoftSPL
NOTES:
A) Ref_XIP folder inside Prepare_XIP is the latest 3.10ROM's XIP, but modified as follows:
-removed modules:
cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files:
boot_ms.rgu, bmui.nb0
-edited files:
boot.hv, boot.rgu,
Code:
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2
[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
-edited modules:
nk.exe
Code:
RTC is enabled
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting
**If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), ADD the removed (from boot.rgu) entries
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
in the PACKAGE's *.rgu.
B) Building your ROM
When you are building your ROM you need:
ROM\XIP(ALL FILES and MODULES) ,
ROM\romhdr.bin and
ROM\OS.nb.payload
This option builds the out.bin(buildxip.exe is used)from the XIP(folder).
C) PP Patching is included in the kitchen operation!
You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!
If you make the following hex change in nk.exe's S000
Aman said:
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler
PS: this method works regardless of the device
Click to expand...
Click to collapse
then the kitchen's PP Patching doesn't work!
You should use the suggested by Aman Multi-platform PP changer v2.21 which is included in the kitchen's panel!
NOTE: I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).
Nice job Kokotas.
great job bro
i would like to test ur kitchen.
Repository:
ElfinCustomRUU.exe
ElfinTask29.exe
Task29&CustomRUU
B2_Kitchen_GUI_Setup
B2_Kitchen_GUI.exe
kokotas said:
Thanks man, but it will be great only if it works for everybody!
I'll pm you the password for the download link.
Regards!
Click to expand...
Click to collapse
TOGETHER we all can MAKE SURE that it works for everybody
how can I obtain pass? I will translate ebglish rom to Turkish and I need that tool..
Nice work.
Not going to switch right away at the moment.
But this looks very good.
I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....
gullum said:
I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....
Click to expand...
Click to collapse
gullum I have touch and I can't wait to cook a new room for touch
ill have a go i got a rom on my phone that that is needed in the upgrade rom list but i have been able to remove it
Project for work
i need to lock down some features of my works PDAs and would love to try your kitchen to attempt this.
can i have a password?
Got a Touch tonight for under 200$ used of cause so now I want a kitchen to make roms
kokotas said:
Sit taken
Click to expand...
Click to collapse
Well deserved!
Gr8 job, Ill keep an eye.
This is fantastic and I'd like to try it. I'd like to cook my rom using this kitchen. Would you pls. give me a password.
Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!
This is on it's way to my pc now thanks in advance
I've already changed Bepe's kitchen to fit my cooking but this one seams more advanced so thanks again
kokotas said:
Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson)
Best Regards!
Click to expand...
Click to collapse
u need to modify the Create_ROM_for_ELF.bat file used for Ervius' buildOS tool. its not working right now, pls check it

Tutorial: How to Dump, Extract and Build a Rom for Windows Mobile

CREDIT GOES TO anichillus for his Tutorial and kitchen. I just modified the tutorial with some pics and steps. Thanks to its right, S.V.I, CRACING and kitchen tools developers. Hope it helps…
Note: I wrote this tutorial on my Blog too. So consider this post as a copy of that post. Plz let me know if i have mistake in the tutorial. Thanks....
1. Some ROMS are password protected. So those ROMS will not dump.
At First you need to download a good Kitchen and a good ROM for windows mobile. All the kitchens are good. For me HyperCore Kitchen is the best choice so download the kitchen from here :
Kitchen source: HyperCore Kitchen
Latest Kitchen Download: Download
You can Use this kitchen for Wizard, Hermes, Artemis, Herald, Universal, Trinity and Prophet. Then Download a Rom for your device. You can find a lots of coustomized ROM for windowsmoble devices on Xda Developers. Before Downloading a windows Mobile Rom you need to know what kind of Windows Mobile Device you Have . And You need a CID Unlocked Device. I know that my MDA is a Wizard and it’s a G3 Device. To know about your device please read Smartphone / PDA Nick Names And Unlocking. I added some Unlocking tools source for different Device. After downloading and Unlocking Your Device You can update your Rom. To coustomize your downloaded ROM follow this steps:
1. Extract The kitchen to your C: Drive otherwise it will not work properly. It should be C:\Core\ on you PC. First of all you need to edit the file named “Device.txt” located on the “C:\Core\ACK\” folder located on systemdrive. You will see set device= . If you have a Wizard then edit the test like this set device=Wizard. Then Go to your downloaded rom directory ans copy the nk.nbf or the .nbf file to Desktop\HyperCore\Panel\Extract\source Folder. Make sure that .nbf file is named as nk.nbf.
Take a look at the bottom picture :
{
"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"
}
2. The Navigate to Desktop\HyperCore\Panel\Extract folder and Start DumpRom and hit Enter to Dump / Extract the ROM from nk.nbf file. You will see its working.. After few seconds..minutes, depending on your PC and the ROM you are extracting you will be prompted with a Status and with some questions. Here you can start PKG Tool and you can move the OS.nb to ROM folder. Type In 2 and hit Enter to copy Os.nb. Now Type in 1 and hit [ENTER] to start Package Tool. Read the window and Hit [ENTER] to countinue…
Bulding Packages
3. You will see some options On the status window. Choose Number 3 manual Option. So type in 3 and hit [ENTER].. Package tool will start. Click on Package tool and go to file > Open then select the folder Desktop\HyperCore\Extract\dump. It will show you Rom Information. After that click on Tools > Build Packages on the package Tool program. It will take some time to bulid the package. It will show you some status afet building packages.Look for [Missing Files] to find info about their Directory. To copy the missing file go to Desktop\HyperCore\Extract\dump directory and Copy the missing files / folders from there to where it shows. After you placed all files where they should be, you must then rename the “dump” folder into “Packages” and only then you can exit the PackageTool. . When you will do that, the batch program will get you to another Status window. Here you can see “Move SYS and OEM to Kitchen. So, select “4” and press [ENTER] but be sure that you renamed the “Dump” folder first into “Packages”. Then type Y and press [ENTER] again. It will move the SYS and OEM folders into HyperCore \Build for later building. Then Exit or Press [ENTER] to Exit the status window.
Dumping XIP from ROM
4. The Only thing you miss now is the XIP section and you’ll have your first OEM and SYS Kitchen after dumping the XIP from the ROM. Go to Desktop \HyperCore\Panel\Extract and start DUMP XIP it will open a folder asking you to place OS.nb on that folder. We already moved the OS.nb to this folder. So Close that folder and hit [ENTER]. This will work to generate the XIP. Read the status window and continue. Type in 1 and press [ENTER] to move the XIP. Press any key to continue and Exit the Status window.
BuilDing ROM from Kitchen
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 56.9 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
6. This will prompt you with couple of choices. It’s pretty easy. Select “1” and this will start the actual BuildOS program. Select the Packages from there and click on little green arrow and wait until finish. Note that, If you have duplicate file on the packages you will get error message saying file exist.. delete duplicate files from SYS and OEM then click on green button again. When done close the build os on the status window to make OS.nb file by choosing option 2. Type in 2 and press [ENTER] to create OS.nb file.
7. After finishing you will see the status window again. Now type in 3 and it will start nb2nbf tool. Now follow this instruction carefully.
Select Wizard on model ID field.
Then select File#1 and browse Os.nb file from Desktop \ HyperCore \Tools\Convert\ .
Then select OS from drop down list.
Click on Start Address field to get the Start address.
Click on Translate to buld nk.nbf file. Here is a picture of nb2nbf tool with this steps .
how to remove programs from sys folder
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
confident said:
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
Click to expand...
Click to collapse
Deleting the folders worked fine for me.
Which dose the samsung onima go under?
Wizard, Hermes, Artemis, Herald, Universal, Trinity or Prophet?
thanks
Hello,
MoonBlazer said:
Wizard, Hermes, Artemis, Herald, Universal, Trinity or Prophet?
thanks
Click to expand...
Click to collapse
No, hypercore or any kitchen found in this website will not work for samsung onima and also the device is not developed by HTC so you might not get any info in this website for cooking ROM's for samsung onima.
SO DO NOT TAKE ANY RISK.
confident said:
i want to remove some applications from the sys folder (like bluetooth ftp,ps shutxp) which i never use.can i simply delete the folder from sys or i have to edit rgu or initflash or dsm file .or anyone knows how to edit xml file so that i can select or deslect program from the buildos tool.thanks in advance
Click to expand...
Click to collapse
* If you are deleting any OEM folders which contains lnk. Simply delete the OEM and also clear the command line in the initflashfiles.dat file which relates to the lnk file inside the deleted OEM. You can ignore this one but I think it will slow down the speed of booting at the first time.
* If you are deleting any OEM folder which does not contain any lnk file then simply delete it.
* When ever you deleted the OEM, Rgu file might be the important to boot the device so confirm the keys inside the rgu and then delete the OEM.
* After build the nk.nbf, The file should be less then 56.9 MB if not its overcooked and it will defiantly crash while flashing.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
I think these tips will help a little, Thanks
Best regards
thanks
CRACING said:
Hello,
No, hypercore or any kitchen found in this website will not work for samsung onima and also the device is not developed by HTC so I might not get any info in this website for cooking ROM's for samsung onima.
SO DO NOT TAKE ANY RISK.
* If you are deleting any OEM folders which contains lnk. Simply delete the OEM and also clear the command line in the initflashfiles.dat file which relates to the lnk file inside the deleted OEM. You can ignore this one but I think it will slow down the speed of booting at the first time.
* If you are deleting any OEM folder which does not contain any lnk file then simply delete it.
* When ever you deleted the OEM, Rgu file might be the important to boot the device so confirm the keys inside the rgu and then delete the OEM.
* After build the nk.nbf, The file should be less then 56.9 MB if not its overcooked and it will defiantly crash while flashing.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
I think these tips will help a little, Thanks
Best regards
Click to expand...
Click to collapse
ok, thanks
Thanks Cracing.Your Touch HD is the best rom i ever used.
* Make sure you device is flashed to hardspl before testing your cooked ROM.
Click to expand...
Click to collapse
I think Hspl is only needed if you have a G4 Device!
ather90 said:
I think Hspl is only needed if you have a G4 Device!
Click to expand...
Click to collapse
O" thats right man. I was not knowing about it.
Why did the htc developerd two edition of htc wizard, I mean G3 and G4.
Regards
nada1
CRACING
ı am not spaek english soryy ı am eng. speak very little
Rom edit Video description pls
Correct English :
Can any one please make a screencast/video of the steps explained above ?
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 57 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
Can any one please make a screencast/video of the steps explained above ?
ferfecir said:
5. If you are on this step, you made your own first kitchen for your windows mobile device. Before building any windows mobile rom you must remember that your ROM size should be 57 MB. Now go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder. If you want to know about how to make OEM package for Windows Mobile please read details about Making Windows Mobile OEM Here. Add remove packages from OEM and SYS folder to adjust the nk.nbf size. After adding an deleting packages go to Desktop\HyperCore\Panel\Build and start BuildOS. Look at the picture below to see this status window.
Can any one please make a screencast/video of the steps explained above ?
Click to expand...
Click to collapse
in this step go to Desktop \HyperCore\Build and add / delete your OEM Pcakages from OEM Folder in that directory. Create or download your OEM packages from here. Then follow the tutorial
Tried this a couple times from the beginning and I can't get past the BuildOS. Seen people have this before with other ROM's but they never post how it was fixed. It's the old "External component has thrown and exception." when it's creating initflashfiles.dat....
Any help with past experience would be much appreciated.
DurKNesS said:
Tried this a couple times from the beginning and I can't get past the BuildOS. Seen people have this before with other ROM's but they never post how it was fixed. It's the old "External component has thrown and exception." when it's creating initflashfiles.dat....
Any help with past experience would be much appreciated.
Click to expand...
Click to collapse
Please explain more. I will try my best to fix your problem.
Thanks CRACING,
I think it has everything to do with I don't know what i'm doing...lol
I have a lot of respect for all of the peeps cooking roms for us. Don't even know where to start when I'm looking at the sys folder. Thanks for offering to help but I'm staying far away from trying to cook a rom to my liking.
DurKNesS said:
Thanks CRACING,
I think it has everything to do with I don't know what i'm doing...lol
I have a lot of respect for all of the peeps cooking roms for us. Don't even know where to start when I'm looking at the sys folder. Thanks for offering to help but I'm staying far away from trying to cook a rom to my liking.
Click to expand...
Click to collapse
Only few weeks ago I was also not in knowing how to cook. I readed may posts and threads on this website but did not went in head. So after many studies and hard works day/night, Now I am able to cooking the ROM's for the wizard. Everyone think that cooking is not so easy but after learning, we can cook ROM's easily.
Now I am insearch in cooking ROM's for HTC Touch HD but the only problem for me is that, I have do not have device to test.
Anyway, Do some research in this good website. You will get many guides for cooking ROM's and threads/post for fixing problems.
Best regards
the path
Desktop\HyperCore\Panel\Extract\source
is on new version not correctly the path are
\Desktop\HyperCore\Extract\Source
gabberjool said:
the path
Desktop\HyperCore\Panel\Extract\source
is on new version not correctly the path are
\Desktop\HyperCore\Extract\Source
Click to expand...
Click to collapse
But mine shows.. Desktop\HyperCore\Panel\Extract\source i am confused
delete your OEM Pcakages
Can any one please make a screencast/video of the steps explained above !
Touch 3G - Jade
Hi,
Can I use this tutorial to create a Rom for my Jade ,or Touch 3 G.Please note that I am not a computer geek.
Regards,
Thomas

[ CRBuilder™ 2 ] [ FOR A COMPLETE AND SMARTER COOK ]

{
"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"
}
Version 2​
Hello Brothers and Sisters,
I'm pleasure to provide you my first kitchen for HTC Wizard, based on Bepe's Platform Rebuilder and other tools. This kitchen is so powerfull and professional, that gives you all the needs to build a prefect ROM's. ROM Builder, XIP Dumper, Splash S Builder, File Editor Suite, and more. Also supports for building multiple languages and editions of a ROM with a single kitchen ( Version 1 Only ). As usual the description is below, Please read it before downloading and using.
Features :
Easy XIP porting.
Super faster ROM building.
EXT packages (Extended packages)
Change Page Pool Size while cooking.
Support for building multiple languages and editions of a ROM with a single Kitchen
.ROM and .VM are not needed in SYS anymore, PRB will create it's own .ROM now
No need to reloc the modules using G'Reloc or WMReloc.
Easy to build 1st and/or 2nd splash screens using Splash S Builder.
And lot more.
Versions :
CRBuilder 2
Platform Rebuilder v2.1
XIP Dumper v2.0
Splash S Builder v2.0
DSM Patcher v1.6
DSMAnalyzer v1.4
Package Creator v2.7
RGU to XML v1.0
SYSVersion 1.2
NB2NBF v2.02
PagePool Changer v2.21
Log Report : Version 2
Deeply modified to look smarter and user friendly.
Replace bat files to exe's.
Placed error msgs
Added page pool changing feature while building ROM.
Modified Splash S Builder.
Modified XIP Dumper.
Installation Notes : CRBuilder
Run CRBuilder 2.exe
Enter the password and install/extract.
The kitchen is ready to use.
Installation Notes : XIP Builder
Drag and drop xip.bin or os.nb.payload or cooked ROM ( OS.nb ) or file which contains XIP, into DUMP XIP.exe.
Wait for processing.
You will get XIP dir and romhdr.bin in root
Go inside XIP; Drag and drop all the dsm files ( One-By-One ) into Package Builder.exe ( Xtra Tools ) using another window.
Now inside the XIP dir you will get : MSXIPKernel, MSXIPKernelLTK and OEMXIPKERNEL.
If your are porting XIP from other device, then you should remove OEMXIPKERNEL and place your devices OEMXIPKERNEL.
Move XIP dir and romhdr.bin to root of the ROM dir of your kitchen.
XIP porting is done.
Paths and Patterns : Single or Multi Language/Edition
OEM - Place all your packages including OEM_Lang_0409, OEMAPPS, OEMDrivers, OEMMISC, OEMOPERATORS.
SYS - I think you all might know this.
ROM - Use your base ROM. i.e OS.NB but rename the file to OS.NB.payload; romhdr.bin.
ROM\XIP - MSXIPKernel, MSXIPKernelLTK, and OEMXIPKERNEL.
EXT - Use this, if you have EXT packages. Use OEM to EXT.exe if you want to convert OEM to EXT packages. Exampe : EXT\LEO\AdobePDF 2_5_1_0_395886_06H
Installation Notes : Single Language/Edition
Build your kitchen, as said in Paths and Patterns above.​
Installation Notes : Multi Language/Edition
Build your kitchen, as said in Paths and Patterns above and also do the following :​
'Skip' and 'Only' Files:
Use 'skip' and/or only files to make multi language or edition ROM's. You can place these 'skip' and/or 'only' files inside SYS and/or OEM packages.
In Config.txt, you will find this line :
set LOCALE=XXXX
LOCALE should be set to the language you want to build the ROM for. i.e 0409, 0804, 0804 or etc
set BUILD=XXXX
BUILD is some custom value like Premium/Basic/Lite.​
File Name/s :
_skip
This package will be skipped always.
_skip_0409
This package will not be included to the ROM if you set LOCALE to 0409 in Config.txt.
_skip_Premium or _skip_Basic or _skip_Lite
This package will not be included to the ROM if you set BUILD to Premium/Basic/Lite in Config.txt.
_only_0409
This package will only be included to the ROM if you set LOCALE to 0409 in Config.txt.
_only_Premium or _only_Basic or _only_Lite
This package will only be included to the ROM if you set BUILD to Premium/Basic/Lite in Config.txt.​
Example:
OEM\Package 1\_skip_0409
OEM\Package 1\_skip_0407
OEM\Package 2\_skip_Lite
OEM\Package 2\_skip_Premium
OEM\Package 3\_only_Premium
OEM\Package 4\_only_0409​
Package 1: Will only be included if you are building a 0409 rom.
Package 2: Will only be included if you are building a Basic rom.
Package 3: Will only be included to a Premium build.
Package 4: Will only be included if you are building a 0409 rom.​
As you can see there can be more than one skip or only files in one package.
A skip or only file is just a file (like an empty text file) that is renamed to "_skip_xxx" or "_Only_xxx", important is that this file MUST not have an extension, only filename!
Video Guide :
Link
Warning Notes :
CRBuilder is only for building ROM(s) so you need all the source to do so. Like OEM's, XIP, SYS, OS Payload and Device base files/modules/packages. To get those, You need to extract any stock or custom ROM/s ( i.e Using hypercore ) but the ROM should not be protected.
Microsoft Visual C++ 2008 Redistributable is must
Supports all type of Windows platforms.
Download :
Link
Password : 02111989
Thank you for using our developments..........
Source​
Wizard's OS Payload : Link
Wizard's Metadata : Link
( Use this when porting non Wizard's SYS )
Wizard's WinCENLS WWE : Link
( Use this when porting non Wizard's SYS )
Wizard's XIP base kernel : Link
( Use this when porting non Wizard's XIP )
Recommend to use Metadata and WinCENLS WWE which comes with SYS source. These are just for reference.
Kitchen Builder Open Source​
Its not the builder, it contains bat files. The source of exe's.
Click here to download.
Empty Post 1
Empty Post 2
My Special Thanks To :​
- AMD, ASUS and NVidia
- XDA-Developers
- Bepe - DONATE
- Ervius - DONATE
- Laurentius26 - DONATE
- Ameet - DONATE
- Cornelha
- Also thanks to the ROM testers, feedbacks, and donations........
hey was about to test this out but says the password is incorrect
mysticgoku said:
hey was about to test this out but says the password is incorrect
Click to expand...
Click to collapse
Sorry, Pass is 02111989
CRACING said:
Sorry, Pass is 02111989
Click to expand...
Click to collapse
lol thanks will test it out now and give feedback
Very Interesting indeed!
Stickied
great work!
excellent thanks!
how do I use your kitchen from a file nk.nbf
Italiano
ottimo grazie!
come posso utilizzare la tua cucina partendo da un file nk.nbf
ippoglosso said:
excellent thanks!
how do I use your kitchen from a file nk.nbf
Italiano
ottimo grazie!
come posso utilizzare la tua cucina partendo da un file nk.nbf
Click to expand...
Click to collapse
This is only the ROM builder. First you need to extract the ( unprotected )ROM using hypercore, then only you can use this ROM builder.
Thanks and regards
Installation Notes : XIP Builder
* Drag and drop xip.bin or os.nb.payload or file which contains XIP, into DUMP XIP.bat.
* Press any key to start; Wait to dump and again press any key to exit.
* You will get XIP dir and romhdr.bin in root
* Go inside XIP; Drag and drop all the dsm files into Package Builder.exe ( Xtra Tools ) using another window.
* Now inside the XIP dir you will get : MSXIPKernel, MSXIPKernelLTK and OEMXIPKERNEL.
* If your are porting XIP from other device, then you should remove OEMXIPKERNEL and place your devices OEMXIPKERNEL.
* Move XIP dir and romhdr.bin to root of the ROM dir of your kitchen.
* XIP porting is done.
Click to expand...
Click to collapse
gives error in this step
usage : dumpxip (os.nb payload)
Click to expand...
Click to collapse
ather90 said:
gives error in this step
Click to expand...
Click to collapse
Have you drag and droped xip.bin or os.nb?
i have put xip.bin
ather90 said:
i have put xip.bin
Click to expand...
Click to collapse
It must work because I have tried xip.bin and os.nb and works fine.
Can you attach here or pm me that xip.bin?
well i went in to folder :
C:\Documents and Settings\Ather Akber\Desktop\CRBuilder\Xtra Tools\XIP Dumper 1.0
Click to expand...
Click to collapse
there i pasted my xip.bin, there was a folder called bin and a batch file called "DUMP XIP"
but now i tried manually from CMD "dumpxip xip.bin" and it worked
ather90 said:
well i went in to folder :
there i pasted my xip.bin, there was a folder called bin and a batch file called "DUMP XIP"
but now i tried manually from CMD "dumpxip xip.bin" and it worked
Click to expand...
Click to collapse
You should drag and drop the xip.bin on DUMP XIP.bat and it will extract the XIP.
Anyway, glad to know that you have extracted xip.
ok, that done, now when i drag the dsms on Package Builder.exe, should i be looking for some files or just the dsms?
cracing this builder works with wm 6.5? or is only for the others windows?

[Q] FSP loox 720 custom ROM. Is it real?

hello.
revived, I still own a pda FS Loox 720
is it possible to make custom rom for this PDA? made of nbf nb0, but he did not see any one program to extract/edit/remove files from the directory works correctly only Dumpromx, but it only allows you to extract the firmware and replace the files, not more.
a short walk to dump the firmware ...
shows that the
start_rom ecec and not one in the firmware of wm2003se.
obtained 13 pieces:
Code:
0. start 80040000
0. ecec 8009edb8
1. start 80180000
1. ecec 802e5c00
2. start 80404000
2. ecec 8097fc98
3. start 809b0000
3. ecec 80a494cc
4. start 80b20000
4. ecec 80c2132c
5. start 80cf0000
5. ecec 80e68394
6. start 80ff0000
6. ecec 81446630
7. start 81470000
7. ecec 814a2ae0
8. start 818b0000
8. ecec 818d5360
9. start 81a20000
9. ecec 81ce8350
10. start 81df0000
10. ecec 81e636d0
11. start 81e80000
11. ecec 81f2ffac
12. start 81f50000
12. ecec 81fa5c3c
13. start 82000000
13. ecec 821cc02c
an example of the firmware:
Code:
80040000 - 80040000 L00000000 rom_00 start
80040000 - 80040004 L00000004 JUMP to kernel start
80040004 - 80040040 L0000003c NUL
80040040 - 80040048 L00000008 'ECEC' -> 8009edb8
80040048 - 80041000 L00000fb8 NUL
80041000 - 8009e7f0 L0005d7f0 o32 region_0 rva=00001000 vsize=0005d7f0 real=80041000 psize=0005d800 f=60000020 for nk.exe
...
80176390 - 80176390 L00000000 rom_00 end
...
81f30808 - 81f30824 L0000001c filent 62 00000805 01c420356cf64524 7498 2039 81f2f7b4 VehicleML.pxt
81f30824 - 81f30824 L00000000 rom_11 end
81f30824 - 81f50000 L0001f7dc NUL
81f50000 - 81f50000 L00000000 rom_12 start
81f50000 - 81f50022 L00000022 filedata h_termservclient.lnk
81f50024 - 81f50034 L00000010 filedata mstsc.lnk
81f50034 - 81f5003d L00000009 modname l2tp.dll
81f50040 - 81f50048 L00000008 'ECEC' -> 81fa5c3c
81f50048 - 81f50fa5 L00000f5d o32 region_2 rva=0004b000 vsize=00001e20 real=0390b000 psize=00000f5d f=40002040 for ipsecsvc.dll
...
81fdaf38 - 81fdaf38 L00000000 rom_12 end
81fdaf38 - 82000000 L000250c8 NUL
82000000 - 82000000 L00000000 rom_13 start
82000000 - 82000018 L00000018 filedata Camera.lnk
82000018 - 8200003b L00000023 filedata CameraWizard.lnk
8200003b - 82000040 L00000005 NUL
82000040 - 82000048 L00000008 'ECEC' -> 821cc02c
....
821cc5c0 - 821cc5dc L0000001c filent 48 00000807 01c4c54239f7e7b7 25600 12138 821c8d8c OV9640.dll
821cc5dc - 821cc5dc L00000000 rom_13 end
821cc5dc - 82200000 unknown
on this and can give an error all the programs?
as they say in the instructions that only one should be romhdr Pointer, and then as many as 14.
and can therefore be extracted only that it was between the first and start rom_00 romhdr pointer. and the rest of the start rom_01 - start rom_13 prog and are not intended as unaware of their existence.
3. Insert this value (4 bytes!) in little endian at offset 0x48 in the NB0 (overwriting original info there). If the original info was part of some file or module in the image, hence corrupting it, you will be able to get that file from unmodified NB0 using dumprom or dumpromx (see below), then use xipport to reinsert the file before rebuilding the image so no worries.
Example for the nec 900c: start adress: 0x84080000, romhdr pointer: 0x85e9c945, 4 bytes to insert: 45 C9 E1 01 (0x84080000 subtracted from 0x85e9c945 and converted to little endian).
That’s all for preparing the NB0 image!
Click to expand...
Click to collapse
say, individually unpack it all, changing the value 0x48 + 4 bytes by calculations for each rom start_ **
and how to combine into one and then the whole firmware? because there will be 14 directories OUT ...
or if / delete / add anything in just one, for example, rom start_05 other rom start_0 * will not be affected?
obtained as follows:
ECEC [4 bytes romhdr pointer] [4 byte subtraction rom start of romhdr pointer] (it's all in the recursively)
but the prog is only the first and all. then not a word ....
first attempt to remove the ECEC and the following bytes to anything nor has led ...
helped to partition a file into 14 parts.
I'm 14 and got modulyaimi directories and files.
but back pack does not work, because it requires coredll. *, and it only be in rom start_00
may suggest how to pack back the modified modules without module coredll
so.
thanks to several people who appeared program that allows you to now edit the firmware for Win CE 4.2.
ask for help in editing, but rather create a custom firmware for a PDA.
list of files attached.
well defined with neskokolkimi programs that do not really need and / or rarely used.
list of files
Code:
oeminfo.xml
defaultconfig.xml
wm_start.wma
Voicbeep.wav
type.wav
Splat.wav
RecEnd.wav
Quietest.wav
online.wav
notify.wav
msgbox.wav
MenuPop.wav
Lowbatt.wav
Loudest.wav
Infend.wav
Infbeg.wav
hwandsw.wav
Default.wav
Alarm4.wav
Alarm3.wav
Alarm2.wav
Alarm1.wav
mxip_XIPKERNEL.ver
mxip_SHELL.ver
mxip_PICTURES192.ver
mxip_OS.ver
mxip_MISC.ver
mxip_LANGSHELL.ver
mxip_LANGCOREAPPS.ver
mxip_KERNEL.ver
mxip_EXAPPS.ver
mxip_CPUOPT.ver
mxip_COREAPPS.ver
mxip_BROWSING.ver
tscscan.txt
sym.txt
hwhelp.txt
autocorrect.txt
AKU_OU1.txt
tahomabd.ttf
tahoma.ttf
cour.ttf
Bliss.tsk
square192.skn
square96.skn
portrait192.skn
portrait96.skn
landscape192.skn
landscape96.skn
nk-exe.sig
coredll-dll.sig
mxip_xipkernel_100.rgu
mxip_shell_100.rgu
mxip_PICTURES192_100.rgu
mxip_OS_100.rgu
mxip_misc_100.rgu
mxip_LANGSHELL_100.rgu
mxip_LANGCOREAPPS_100.rgu
mxip_KERNEL_100.rgu
mxip_EXAPPS_100.rgu
mxip_CPUOPT_100.rgu
mxip_COREAPPS_100.rgu
mxip_BROWSING_100.rgu
CW-registry.reg
VehicleML.pxt
todo.pwi
phone.pwi
memo.pwi
meeting.pwi
blank.pwi
todo.psw
phone.psw
memo.psw
meeting.psw
blank.psw
sysroots.p7b
wince.nls
Region_1_0.nlp
Culture3_1_0.nlp
Culture2_1_0.nlp
Culture1_1_0.nlp
CharInfo_1_0.nlp
Calendar_1_0.nlp
wsp.dll.0409.mui
wininet.dll.0409.mui
waveapi.dll.0409.mui
urlmon.dll.0409.mui
unimodem.dll.0409.mui
shlwapi.dll.0409.mui
netmui.dll.0409.mui
mlang.dll.0409.mui
malcommon.dll.0409.mui
jawres.dll.0409.mui
IECEExt.dll.0409.mui
fatutil.dll.0409.mui
coredll.dll.0409.mui
commdlg.dll.0409.mui
wm_start.lnk
WLNPWRCTL.lnk
WindowsMedia.lnk
welcome.lnk
voice.lnk
Transcriber.lnk
Tone.lnk
tmail.lnk
tasks.lnk
sync.lnk
square.lnk
solitare.lnk
RunningPrograms.lnk
romupdnote.lnk
repllog.lnk
pxl.lnk
pword.lnk
Processor.lnk
poutlook.lnk
portrait.lnk
pmail.lnk
pimg.lnk
pie.lnk
notetake.lnk
mstsc.lnk
MSNMsgr.lnk
MSNMobile.lnk
LEAP.lnk
landscape.lnk
KeyLock1.lnk
Jawbreaker.lnk
hotvoice.lnk
help.lnk
h_wmppc.lnk
h_wince.lnk
h_termservclient.lnk
h_tasks.lnk
h_sync.lnk
h_soltr.lnk
h_simrdr.lnk
h_pxl.lnk
h_pword.lnk
h_pimg.lnk
h_pie.lnk
h_Jawbreaker.lnk
h_inkwrit.lnk
h_inbox.lnk
h_im.lnk
h_ctpnl.lnk
h_connct.lnk
h_cntcs.lnk
h_clndr.lnk
h_calc.lnk
h_bluetooth.lnk
gamesico.lnk
FSCSpeedMenu3.lnk
FSCSpeedMenu2.lnk
FSCPanning.lnk
FSCEasy2Connect_hlp.lnk
FSCEasy2Connect_exe.lnk
FSCBackup_hlp.lnk
FSCBackup_exe.lnk
FSCautorun_hlp.lnk
FSC_Panning.lnk
find.lnk
fexplore.lnk
eventrst.lnk
Enroll.lnk
DispLighting1.lnk
Connections.lnk
CameraWizard.lnk
Camera.lnk
calendar.lnk
calc.lnk
BTTrayCE.lnk
Bluetooth.lnk
Battery1.lnk
async.lnk
AlignScreen.lnk
Album.lnk
addrbook.lnk
mssp2_en.lex
OEM.jpg
DOL.jpg
AudioBK.jpg
initdb.ini
FSCSMdef.ini
wmppc.htm
wince.htm
TranscriberEnu.htm
termservclient.htm
tasks.htm
sync.htm
soltr.htm
SIMReader.htm
rnetw.htm
pword.htm
pocketmsn.htm
piehelp.htm
pic.htm
pexcel.htm
notes.htm
KeyLock.htm
Jawbreaker.htm
inbox.htm
im.htm
FSCSpeedMenu.htm
FSCEasy2Connect20.htm
FSCautorun.htm
FSC_Panning.htm
FSC_Backup.htm
evbruntime.htm
Enroll.htm
default.htm
ctpnl.htm
connect.htm
cntcs.htm
clndr.htm
CameraWizard_(ht)b.htm
CameraWizard_(ht).htm
calc.htm
btwcehlp.htm
bluetooth.htm
agdefault.htm
16_oem.htm
TIPostInit.hcs
TICoexEnable.hcs
TICoexDisable.hcs
BTVoiceEnable.hcs
BTVoiceDisable.hcs
welcomehead.192.gif
volumethumbSQ192.gif
volumethumbSQ96.gif
volumethumb192.gif
volumethumb96.gif
VideoBK.gif
Totem-Heart.gif
Totem.gif
t_msgr.gif
SyncAnimation.gif
stylushead.192.gif
stylus2.192.gif
stylus1.192.gif
stylus1.96.gif
square192.gif
square96.gif
seekthumbSQ192.gif
seekthumbSQ96.gif
seekthumb192.gif
seekthumb96.gif
pushedSQ192.gif
pushedSQ96.gif
pushed192.gif
pushed96.gif
ppc.gif
portrait192.gif
portrait96.gif
piecarrier.gif
oem.gif
myinfo.gif
msn.gif
Magazine.gif
landscape192.gif
landscape96.gif
IMWater.gif
IMAddSuccess.gif
IMAddFailure.gif
FSCSpeedMenu.gif
fly.gif
disabledSQ192.gif
disabledSQ96.gif
disabled192.gif
disabled96.gif
Default_stwater_480_480.gif
Default_stwater.gif
dayview.192.gif
dayview.96.gif
complete.192.gif
Clothes-Line.gif
beam.gif
bannerstrip.gif
banner.gif
avantgo.gif
arrow2.192.gif
11select.192.gif
11select.96.gif
Gprs.gdb
default.fdf
www-Hotspot.fbk
www-GPRS.fbk
wmplayer.exe
WLNPWRCTL.exe
welcome.exe
wceloadsp.exe
wceload.exe
updatexip.exe
unload.exe
umarshaller.exe
udp2tcp.exe
TraShapeSelector.Exe
Transcriber.Exe
Tone.exe
tmarshaller.exe
tmail.exe
testReg.exe
tasks.exe
srvtrust.exe
solitare.exe
sndplay.exe
shfind.exe
shell32.exe
services.exe
rundll32.exe
romupdnote.exe
rnaapp.exe
repllog.exe
remnet.exe
rapisrv.exe
pxl.exe
pword.exe
Processor.exe
PowerWLAN.exe
PowerExe.exe
poutlook.exe
pimg.exe
peghelp.exe
notes.exe
nk.exe
mstsc40.exe
mstli.exe
LEAP.exe
KeyLockRes.exe
jawbreaker.exe
instmsgr.exe
iexplore.exe
idledetect.exe
hwhelp.exe
hotvoice.exe
HFPUI.exe
gwes.exe
FSCSpeedMenu.exe
FSCEasy2Connect20.exe
FSC_PwdStart.exe
FSC_PwdCheck.exe
FSC_Panning.exe
FSC_Backup.exe
filesys.exe
fexplore.exe
eventrst.exe
Enroll.exe
device.exe
ctlpnl.exe
cow.exe
connmgr.exe
coldinit.exe
clocknot.exe
clock.exe
cgacutil.exe
cfdetect.exe
certinst.exe
Camera.exe
calnot.exe
calendar.exe
calc.exe
BTWizardCE.exe
BTTrayCE.exe
BTPanManagerCE.exe
BTFileExplorer.exe
BTCplCE.exe
BTConnManagerCE.exe
BTCePimCmdApp.exe
BTBusinessCard.exe
beam.exe
Backlight.exe
Album.exe
adjustmem.exe
addrbook.exe
XSCSDCard.dll
xls2pxl.dll
wzcsvc.dll
wzcsapi.dll
wsppush.dll
wspm.dll
wsp.dll
ws2instl.dll
ws2.dll
wmvdecoder.dll
wmres.dll
wmlview.dll
wmcore.dll
wmavdecoder.dll
wmadecoder.dll
wldap32.dll
winsock.dll
wininet.dll
wendyser.dll
webview.dll
wdppush.dll
wcestreambt.dll
WBtDll.dll
wbtapiCE.dll
wavedev.dll
waveapi.dll
wapdrv.dll
wap.dll
voicedll.dll
VoiceCtl.dll
VoiceBar.dll
VCOMCtl.dll
VBarCall.dll
usbmsc.dll
usbhid.dll
usbdisk6.dll
usbd.dll
urlmon.dll
unimodem.dll
uicom.dll
tshres.192.dll
tshres.dll
tsctrc.dll
trustmarshaller.dll
TraRes0409.192.dll
TraRes0409.dll
TraRecoEnu.dll
TranscriberSip.Dll
touch.dll
toolhelp.dll
tmailutl.dll
TIRadioInit.dll
tiacxwln.dll
termctrl.dll
tcpstk.dll
tcpip6.dll
taskdll.dll
tapres.192.dll
tapi.dll
syscsps.dll
syncres.192.dll
syncres.dll
syncmgr.dll
stcusb.dll
ssllsp.dll
spnego.dll
softkb.dll
shutil.dll
shlwapi.dll
shellresapps.192.dll
shellresapps.96.dll
shellresapps.dll
shellres.192.dll
shellres.dll
servhost.dll
serial32.dll
serial.dll
secur32.dll
SecIDLib.dll
SDMemory.dll
SdkCE.dll
SDBusDriver.dll
schannel.dll
rsaenh.dll
rra_stm.dll
riresdll.192.dll
riresdll.96.dll
riresdll.dll
richink.dll
relfsd.dll
regenum.dll
redir.dll
rdpdr.dll
rdpapi.dll
pxlfile.dll
pxl2xls.dll
pwwiff.dll
pwddll.dll
pushrouter.dll
pushprxy.dll
psmfsd.dll
pptp.dll
ppp.dll
pm.dll
pimutil.dll
pimstore.dll
pimdlg.dll
pimapi.dll
pegobj.dll
pegcards.192.dll
pegcards.dll
pcmcia.dll
OV9640.dll
outres.192.dll
outres.dll
ossvcs.dll
olece300.dll
oleaut32.dll
ole32.dll
ohci.dll
officeres.192.dll
officeres.dll
office.dll
OEMUtil.dll
oemregistry.dll
oectrl.dll
obexsrvr.dll
obexinbx.dll
obexapi.dll
ntlmssp.dll
nspm.dll
note_prj.dll
note.dll
netui.dll
netmui.dll
netcfagl1_0.dll
netbios.dll
ne2000.dll
ndisuio.dll
ndis.dll
msxml.dll
msscript.dll
mspart.dll
msnsspc.dll
msnewmnu.dll
msmsgsc.dll
msimnetc.dll
msimmsgr.dll
msim.192.dll
msim.dll
MsgStore.dll
msgslang.dll
msdmo.dll
mscoree1_0.dll
mscoree.dll
msasn1.dll
MPEG4SPVIDEOENC.dll
MP4Writer.DLL
mp4spvd.dll
MP4_READER.dll
mmtimer.dll
mlang.dll
miscres.192.dll
miscres.dll
MidiLib2.dll
mfcce300.dll
malcommon.dll
malclmgr.dll
mailtrns.dll
l2tp.dll
KeyLock.dll
keybddr.dll
kbdhid.dll
jscript.dll
JPEGENC.dll
jpeg.dll
jawres.dll
Jacket.dll
irsqrt.dll
irsir.dll
irdastk.dll
ircomm.dll
ipv6hlp.dll
ipsecsvc.dll
ipsec.dll
iphlpapi.dll
inreplce.dll
inkx.dll
inkobj.dll
infantry.dll
imgdecmp.dll
IMEngine.dll
imaging.dll
imagelib.dll
IECEExt.dll
htmlview.dll
HTCcamera1.dll
hidparse.dll
HFPControlPanel.dll
H263VIDEOENC.DLL
gxdma.dll
gx.dll
GSMAMRENC.dll
GSMAMRDLL.dll
GAC_System_v1_0_5000_0_cneutral_1.dll
GAC_System.Xml_v1_0_5000_0_cneutral_1.dll
GAC_System.Windows.Forms_v1_0_5000_0_cneutral_1.dll
GAC_System.Windows.Forms.DataGrid_v1_0_5000_0_cneutral_1.dll
GAC_System.Web.Services_v1_0_5000_0_cneutral_1.dll
GAC_System.Net.IrDA_v1_0_5000_0_cneutral_1.dll
GAC_System.Drawing_v1_0_5000_0_cneutral_1.dll
GAC_System.Data_v1_0_5000_0_cneutral_1.dll
GAC_mscorlib_v1_0_5000_0_cneutral_1.dll
GAC_Microsoft.WindowsCE.Forms_v1_0_5000_0_cneutral_1.dll
GAC_Microsoft.VisualBasic_v7_0_5000_0_cneutral_1.dll
fsdmgr.dll
FSCSMrsc.dll
FSCE2CRes.dll
FSC_LXInfo.dll
Frontlight.dll
find.dll
fatutil.dll
fatfsd.dll
exappres.192.dll
exappres.dll
ethman.dll
eaptls.dll
eapol.dll
eapchap.dll
eap.dll
dssdh.dll
doclist.dll
dhcp.dll
ddi.dll
cxport.dll
cspras.dll
cspproxy.dll
cspnet.dll
crypt32.dll
coreres.192.dll
coreres.dll
coredll.dll
connplan.dll
conncfg.dll
configmanager.dll
compime.dll
commdlg.dll
commctrl.dll
colorConvScaling.dll
clockdll.dll
citydb.dll
chngtrk.dll
cespell.dll
ceshell.dll
cemapi.dll
cemailsync.dll
cellcore.dll
cefobj.dll
cedrmutil.dll
ceddk.dll
ccoreprv.dll
calstore.dll
caldll.dll
cabinstl.dll
bvd_udc_ser.dll
BTWizardProfiles.dll
BTWizardHfp.dll
BtSdkCE30.dll
btrez.dll
bthutil.dll
bthusb.dll
bthuniv.dll
bthuart.dll
bthsc.dll
bthlink.dll
bthcsr.dll
bthamb.dll
btdrt.dll
BTDialer.dll
btd.dll
BtCoreIf.dll
BTChooserLib.dll
BtCeStack.dll
BtCeSendTo_Poom.dll
BtCeProfiles.dll
btcepan.dll
BTCeOsif4.dll
BtCeIf.dll
BtCeBCSPTrans.dll
BTAudioGW.dll
browsres.192.dll
browsres.dll
browser.dll
battdrvr.dll
aygshell.dll
audevman.dll
atlce300.dll
atadisk.dll
asyncmac.dll
asfplayer.dll
appinstaller.dll
Album_Res.dll
airsync.dll
agiehandler.dll
afd.dll
adosync.dll
adoceoledb30.dll
adocedb30.dll
adoce30.dll
addrstor.dll
addrdll.dll
abstraction.dll
AACDLL.dll
statdict.dat
splash.dat
pwipat.dat
initobj.dat
dictprob.dat
SystemInfo.cpl
PowerWLAN.cpl
Powerg.cpl
cplmain.cpl
BTConfigCE.cpl
Backlight.cpl
malconfig.cfg
Zoom-Indicator.bmp
zoom.bmp
winmedia.bmp
webguide.bmp
volume.bmp
voicetag.bmp
Thumbnail-view.bmp
sysvol.bmp
slideshow.bmp
sending.192.bmp
sending.96.bmp
senddsbl.192.bmp
senddsbl.96.bmp
send.192.bmp
send.96.bmp
rotate.bmp
Remaining-video-time.bmp
Remaining-images.bmp
question.bmp
ppccom.bmp
Picture-Theme-Next-Previous-arrows.bmp
Msrg_undo.bmp
Msrg_tab.bmp
Msrg_space.bmp
Msrg_paste.bmp
Msrg_entr.bmp
Msrg_cut.bmp
Msrg_copy.bmp
Msrg_case.bmp
Msrg_back.bmp
Msrg_all.bmp
msn_mail.bmp
msn.bmp
Full-Screen-exit-icon.bmp
Full-Screen-entrance-icon.bmp
device.bmp
crop.bmp
Confirm-Send.bmp
Confirm-Detailed-View.bmp
Confirm-Delete.bmp
Confirm-Back.bmp
Capture-Size.bmp
Capture-Indicator.bmp
Camera-Settings.bmp
bt_tran.bmp
bt_spc.bmp
bt_rtn.bmp
bt_rmode.bmp
bt_rarr.bmp
bt_optns.bmp
bt_lss.bmp
bt_larr.bmp
bt_kbrd.bmp
bt_help.bmp
bt_bspc.bmp
appointment.bmp
Ambience-Incandescent.bmp
Ambience-Fluorescent.bmp
Ambience-Daylight.bmp
alerts.bmp
aglogo.bmp
maxim_radio_dl.bin
ACX100_dl.bin
async.asy
gsm610.acm
wmlb.2bp
wm_wmcom.2bp
wm_volume.2bp
wm_unmute.2bp
wm_stop.2bp
wm_progress.2bp
wm_previous.2bp
wm_play.2bp
wm_pause.2bp
wm_next.2bp
wm_info.2bp
wm_fullscreen.2bp
Win_Start.2bp
web_content.2bp
vcard.2bp
up_play.2bp
undo.2bp
toolbar.2bp
Tip_Icon.2bp
Stop_icon.2bp
stop.2bp
space.2bp
Signal_Strength_Yellow.2bp
Signal_Strength_RED.2bp
Signal_Strength_Green.2bp
send.2bp
scard.2bp
reply.2bp
Refresh_icon.2bp
Red_Bul.2bp
record.2bp
play_play.2bp
pen.2bp
NewCard.2bp
mic.2bp
line.2bp
light.2bp
input.2bp
info_play.2bp
Icon_Work.2bp
Icon_Ntwk_Card.2bp
Icon_Init.2bp
Icon_Connect_Internet.2bp
Icon_Connect.2bp
format.2bp
Folder_icon.2bp
flag.2bp
favorite.2bp
Edit_profile_icon.2bp
Edit_Num.2bp
drform.2bp
down_play.2bp
direct16.2bp
dialup16.2bp
Dial_Num.2bp
deletefolder.2bp
delete_play.2bp
dataconnection.2bp
chooser_prev.2bp
chooser_next.2bp
cf.2bp
BT_PhoneDialer.2bp
BT_icon_Gray.2bp
BT_icon_Blue.2bp
BT_Globe_icon.2bp
BT_BizCard_icon.2bp
brcm_ppc.2bp
Blu_Bul.2bp
autosum.2bp
attach.2bp
align.2bp
address.2bp
add_play.2bp
avantgocfg.1
avantgocfg.0
list of files found by the programs
Easy2Connect
Code:
FSCE2CRes.dll
FSCEasy2Connect_hlp.lnk
FSCEasy2Connect_exe.lnk
www-Hotspot.fbk
www-GPRS.fbk
solitare
Code:
solitare.lnk
h_soltr.lnk
gamesico.lnk
solitare.exe
soltr.htm
FSCSpeedMenu
Code:
FSCSpeedMenu.exe
FSCSpeedMenu3.lnk
FSCSpeedMenu2.lnk
FSCSMdef.ini
FSCSMrsc.dll
office
Code:
h_pxl.lnk
pxl.exe
pxl.lnk
pxl2xls.dll
pxlfile.dll
office.dll
pword.exe
h_pword.lnk
pword.lnk
xls2pxl.dll
pword.htm
pwwiff.dll
calculator
Code:
h_calc.lnk
calc.lnk
calc.htm
calc.exe
Transcriber
Code:
TraRes0409.192.dll
TraRes0409.dll
TraRecoEnu.dll
TranscriberSip.Dll
Transcriber.lnk
TranscriberENU.htm
Transcriber.exe
Msrg_undo.bmp
Msrg_tab.bmp
Msrg_space.bmp
Msrg_paste.bmp
Msrg_entr.bmp
Msrg_cut.bmp
Msrg_copy.bmp
Msrg_case.bmp
Msrg_back.bmp
Msrg_all.bmp
bt_tran.bmp
bt_spc.bmp
bt_rtn.bmp
bt_rmode.bmp
bt_rarr.bmp
bt_optns.bmp
bt_lss.bmp
bt_larr.bmp
bt_kbrd.bmp
bt_help.bmp
bt_bspc.bmp
other files:
Code:
*.psw and *.pxt
wm_start.wma
wm_start.lnk
it's all that I have found so far.
tell me what other programs, libraries, files can be deleted.
for example, wmp, outlook, tmail, etc ...

Categories

Resources