Let's make HD2 the best Windows Phone 7 device
My tutorial on porting WP7 sys (and update to NoDo) for HD2 is in my 2nd post, you'll find too my tricks and ideas
Thanks to Ruzzichella, DFT, bepe, cotulla, ervius, AnDim, Nokser, ansar, OndraSter, airxtreme, misar etc. etc.
{
"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"
}
16/05 First release:Porting HD2 WP7 rom to NoDo (see 2nd post)
New theme with transparency I've called Aero
HTC Hidden Wi-Fi works since I've updated some OEM packages. To have a wifi mac adress which don't change at reboot try to set it in the nvram.txt file (see my second post)
Rom is unlocked and prevented to relock.
A video demonstration: Youtube_WP7_NoDo_ROM_HD2 (thanks Jaxbot)
05/06 Update:Green key is now hard remaped, I've chosen the function of bluetooth Headset: Play/Pause multimedia, Skip by pressing twice, Answer a call (when receiving), End call, (when in call), long press to rapidly call someone by speech input.
Replaced camera button by a software button with autofocus like on Androïd so no more blur.
Radio is working without the need of headphones.
Added keyboards layout for some other countries and added some cool features. More layouts to come soon.
Improve performances, localisation (assisted gps - agps), Bluetooth, battery consumption. (mine is between 3 and 6 mA)
Solving of certains difficulties to establish a link with some Wi-Fi routers.
Smooth gradients (no more 16bit banding bug) without lost of performances.
Backlight adjusted and set to never by default (work have to be done)
Changed volume settings and added a sound template to make it more clear.
Replaced all Microsoft and OEM wallpapers by transparent png, so a total of 41.
08/06 Update:Replaced all overlaped modules of the 7392 base rom, so improve about everythingSpeech recognition (long press Win key and Call contact Green key) works for every languages
13/06 Update + 16/06 minor Update:Added direct access to Wi-Fi and Bluetooth in start menu and home tiles.
Added direct acces to Airplane mode and Brightness (16/06)
Update of the HTC RIL manager module and added the last HTC Connection Setup for autodata config at boot.
Added keyboard layouts but there is a limitation of 20 keyboards so I split the rom in 2.
Added some other long press on keyboards layout ie w->www. f->ftp://ftp. (16/06)
23/06 + 26/06 Update:Rom is rooted now (first WP7 rooted rom)
Optimisation of the policy database for root access (+live games fix) (26/06)
Added direct acces to Cellular and Location
Added direct acces to Sound and Lock and changed all icons added to real metro theme (26/06)Added 2 extra themes (Aero variations with transparency): Aero Black and Aero RichThe Rom Files: v5_lang1 and v5_lang2 - These are the roms, no language pack!!! see below
Rom is split in two versions with differents keyboards layouts
In both: Spanish, French/Canada/Swiss, German, English US/UK, Italia
Lang1: Finish, Hungarian, Swedish, Czech, Danish, Dutch/Belgian, Norwegian, Polish, Poruguese/Brazilian, Filipino
Lang2: Turkish, Malay, Arabic(as Ecuador), Hebrew(as Uruguay), Farsi(as Bolivia), Chinese, Greek, Korean, Russian, Indonesian, Ukrainian, Thai(as El Salvador)
A xap to give back the 3rd option speaker/headset in FM radio (but you'll need Headphones): ProvXml-FMradio.xap (thanks to xboxmod, for use see his thread)
A pack with all HD7 radios (files part00.bin to replace in Data.zip before flash): HD2 WP7 radios pack
If you want another hard keys remaping template see here
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)
Tutorial to port sys (update to NoDo)
Ok guys, I don’t know why DFT haven’t release an update for HD2 earlier since it take only few days to a noob to achieve a working NoDo rom. Their first version was built on a test rom with developer’s certificates from Microsoft and HTC, debug tools, recompiled drivers for HD2 and a method to build SLDR and NK sections. They had before everybody a test version of Mango too. So I suppose they, or only one, is working for HTC or has good contacts and perhaps had a commercial interest or was more interested by the exploit than giving users a great experience of WP7 on HD2, updates as soon as it’s possible and tools/knowledge to members like ervius, AnDim, Nokser etc. to achieve that by themselves. Someone in another post suggest an agreement not to release their mango before the 24th, it’s quite possible. But I don’t know and I don’t blame, it’s life lol
Perhaps we’ll see a version of Mango for HD2 soon (and new exiting videos^^’) but since a lot of people are waiting for NoDo (some desperate posts made me cry XD) I’ll give you a first version, and better, the method to achieve that by yourself for the next coming.
!The trip isn’t how to flash an HD7 rom on HD2 like certain people seems to believe and we don’t need a new malgr for the moment!
What you need:
DSM editor by Ervius http://forum.xda-developers.com/showthread.php?t=523139
WP7 Rom Tools by AnDim http://forum.xda-developers.com/showthread.php?t=884239
IMGFSFromDump-TURBO by airxtreme http://forum.xda-developers.com/showthread.php?t=610713
Imageinfo.bin, packages.cif/sof Tool by kokotas http://forum.xda-developers.com/showthread.php?t=674477
DFT rom and DWI by by bepe and Cotulla
A rom with 7392 SYS like RUU_Mozart_TMO_DE_1.32.111.01_5.65.09.25_22.45.50_ RELEASE http://forum.xda-developers.com/showthread.php?t=1065281 (MOZART is not important for SYS parts)
Some extra roms for updated other SYS languages
A rom with latests HTC packages to have the possibility of stuff like Hidden Wi-Fi like RUU_Schubert_O2_DE_3.04.207.01_Radio_5.66.09.21a_2 2.48.50.21 http://forum.xda-developers.com/showthread.php?t=1037967
Optional:
A rom for a new radio, this one seems to be the latest too
A rom for developpers tools and kitl like RUU_Schubert_hTC_Asia_SEA_WWE_1.57.728.02_Radio_5.52.09.16_22.33a.50.10_TEST
Roms for OEM APPS stuff that you want
A good HEX editor and a file/directories comparator may help a lot
Just a little time and patience lol
PS: open roms with an archive tool like 7-Zip and take the RUU_signed.nbh file, we only need this.
1. A new radio: (optional)
The radio is the part00.bin in the Data.zip
With HTCrie open the nbh which contains the radio you want, select GSM and extract the GSM.nb
Open it with an hex editor and search for 7F 45 4C 46 01 01 01 61, it’s the beginning of the part we need. The end is the series of 00 just after the last AMSS string you can find (refer to DFT part00.bin if you need help).
Keep only this section (delete the rest) and add some 00, for example if the files ends at the byte e004d0h go to e004ff.
Save the file, rename it part00.bin, you’ll have your new radio (in this case 5.66.09.21a).
Replace it in the Data.zip, you can flash now with DWI to test it.
You’ll show the new version in the Settings/About of WP7.
2. Change The SYS by 7392 Step 1: Common packages
With HTCrie open the nbh which contains the 7392 SYS build (or another you want), extend OS/IMGFS and select SYS. Extract it to a folder.
Do the same for other rom(s) containing extra languages in another folder.
Add the extra *_LANG_0XXX packages from the second directory to the first, after that you can delete it (the second folder lol, if only English was my native language^^).
You can use NabSync and NabSync_Lang_0XXX packages or not, if not delete them, just remember you’ll not need to add MOS entries in default.hv in this case.
Put the metadata package in another place, we’ll use it in step 2.
Put the content of all other packages in a new folder (for ex called IMGFS), with HTCRIE open the same 7392 rom, extend OS and in IMGFS content select .ROM and .VM modules, extract them in your IMGFS folder.
It’s your new SYS.
You could past/overwrite it in DFT IMGFS and build the rom now it will function (the DFT video of March) and YES it’s as simple as that, you’ll have new stuff from NoDo like copy/paste but not the possibility of Hidden Wi-Fi since it depend of OEM packages.
PS: It’s possible since there isn’t many changes in NK and SLDR sections made by NoDo, so we can use like that. dsm files are not very important (just to have good references of packages) and rgu content is added in default.hv
Modules that need to be updated are:
NK: cachefilt.dll, hd.dll and osaxst0.dll
SLDR: exfat.dll, filesys.dll, k.coredll.dll, k.fatutil.dll, kernel.dll, mtpuldrsvc.dll, pm.dll, sdbus.dll, sdmemory.dll and unifiedblock.dll
3. Change The SYS by 7392 Step 2: metadata package
With HTCrie extract the metadata package of the SHUBERT rom which contains OEM that you need, so we have to play with 3 metadata packages: DFT, SHUBERT OEM, MOZART SYS.
It could be a little simpler if we have a 7392 rom for SHUBERT but not for the moment.
Some files need to be updated, first is BasePolicy.xml, compare the new content of MOZART with DFT one, same for SCHUBERT (replace C:\WM700\release\LEO and C:\WM700_7392\release\MOZART by C:\WM700_7392\release\SCHUBERT). If you find new entries and you judge them useful (refer to dsm and find the package) then add them in MOZART one (it’s the most important for SYS).
Second is DefaultCerts.dat, these files contain certificates. In hex each one begin with 30 82 ?? ?? 30 82 so you can cut this file in x parts, one for each certificate.
The common build is Microsoft root, oem roots, Microsoft Windows Mobile PCA0, oem, Microsoft Mobile Device Unprivileged PCA0.
We’ll keep DFT one as bas as it’s include Qualcomm infrastructure development, Microsoft Corporation CE Image Update Test and HTC_Develop_Test, useful for later (we never know^^). DFT has included HTC_Develop_Test twice (like in dsm beside Microsoft Corporation CE Image Update Test) so you can remove the second.
What you need is to take DefaultCerts.dat from other metadata packages, extract OEM 168 or/and OEM 169 (personally I’ve included both from other roms so I’ll never have to touch this file again) and insert oem/oem root certificates in DFT one.
packages.cif and packages.sof are certainly updated but you can edit them with Imageinfo.bin, packages.cif/sof Tool.
Compare the imginf.txt you obtain for each roms you use (you can sort this file to make it more simple).
Like with BasePolicy.xml, if there is an entry that you judge useful, just add it in packages.cif and .sof (refer to this tool’s post in forum to know how use it well, but it’s quite simple).
The last two files but more important are default.hv and user.hv
To edit them just drag them onto HVEdit.exe by AnDim, you’ll obtain default.hvm and user.hvm which can be edited like rgu files.
To rebuild hv just drag hvm onto HVEdit.exe
I suggest keep the 7392 ones as base, compare them with DFT originals and modify entries you want.
For some you need a little knowledge (refer to forum) but for most it’s language entries and some tweaks.
You can refer to rgu files which differ and take a look at NoDo and 7392 pku to know which files/rgu are concerned (see forum to know how obtain pku for each zune update and extract them but don’t use files as they are in your build since most of them are not suitable (except dsm), they only contain information to update files/modules)
You can add for exemple your LiveID useful for HD2 users:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\GwpCPC]
"ActivationCode"="77777-77777-77777-77777-77777"
Copy the content of the new metadata package in your IMGFS folder. Now you have a fully functional SYS that you can use instead DFT one Let see OEM packages.
4. Change OEM packages Step 1: common packages
With HTCrie extract in two folders (like for SYS before) the OEM packages, one for DFT (for most you’ll find them at the wrong place: in SYS - like for most of TEST roms you can find) the other for the rom with most updated HTC packages.
You don’t need HTC_8x50_OS_UI_LEO as we replace it by HTC_8x50_OS_UI_SCHUBERT
You don’t need StartKitl and kitl.dll from DFT as it’s debug tool (we’ll see later) and HTC_CSPOSDrivers is new stuff so don’t search it in DFT rom.
Other packages which can be used without modification beside HTC_CSPOSDrivers are CSConn_DB, HTC_Global_Customization, OEM_8x50_BLDR, OEM_8x50_BSP, OEM_8x50_LOGO, OEM_8x50_MODEM, QC_8x50_OS_MM_CFG_2 so just delete them like for HTC_8x50_OS_UI_LEO in DFT folder to see more clearly.
5. Change OEM packages Step 2: updated packages
Like I’ve said we could use DFT OEM packages as they are but we won’t have new stuff from HTC like Hidden Wi-Fi. So we have to update some modules.
We could update the most of them (certain drivers are HD2 specific) but since we can’t update NK/SLDR sections for now you’ll got some troubles (I’ll speak of that later).
So for each package we change all files,rgu and dsm but we have to keep some modules from DFT.
For HTC_AppDrivers and HTC_OSDrivers don’t keep anything (so delete them from DFT folder) but remove HTCConnectionSetUp.dll since it is in SLDR and have some dependencies so you’ve got some troubles to connect secure wifi networks.
For HTC_8x50_OS_UI_COMMON, OEM_8x50_OS, QC_8x50_OS_GPS, QC_8x50_OS_MMRIL overwrite all modules with DFT ones
For HTC_8x50_OS_WIRELESS overwrite all modules. wl_server_serial.dll and wlan_oem.dll were files, we need updated ones in modules from new oem package for HTC Hidden Wi-Fi, the other thing to do is to verify in default.hv that BtOem, RSS and WLANOEM entries are in HKEY_LOCAL_MACHINE\Drivers\BuiltIn\ sections like in new roms and not in HKEY_LOCAL_MACHINE\Services\ like DFT’s one (and never both) otherwise it won’t work.
For OEM_8x50_OS_CAMERA replace modules and add camerasettingsmanifest.0XXX.xml from DFT in new one (since these files are normally in SLDR in new roms we have to add them). Use DSM editor to edit c6158f86-ef71-4a8b-8c04-0cf57c158b2f.dsm and add entries for these files (refer to this tool’s post to know how use it but it’s easy too).
For OEM_8x50_OS_SURF replace all modules. But you don’t have to add Backlightmdd_htc_6541.dll, just be sure you have backlightmdd.dll instead in default.hv like in new roms.
For QC_8x50_OS replace modules. You have to delete windiag.dll or verify in default.hv that “dll”=”windiag.dll” is replaced by “dll”=”” like in new roms.
6. Change OEM packages Step 3: extra packages (optional)
HTC_OEMAPPS contain OEM software.
You can add from different roms and operators. Just add the *.xap and * _License.xml you want, edit mpap_HTC_MASD_01.provxml to add/have only entries for these files and use DSM editor to edit 47c557c0-08b2-493c-a380-08c72d78e3ba.dsm and update the list of files in this package.
operatorpkg contain the HTC or Operator personalization files. Like for OEMAPPS, keep/add what you want from different roms, Email accounts/providers, Browser favorites are useful, MNS_Cust_xxx too, I’ve personally built a new theme with transparency called Aero, added the entries in the default.hv and add the 02XX*.xaml in this package.
A picture with transparency in png format for the lockscreen too.
After use DSM editor to edit 438abf0c-b691-4259-a742-1f224fa3b5ba.dsm like before.
You can add developer stuff/kitl and HTC tools packages too: AutoDeviceConfig, CommsDogfood, CoreOSDogfood, dogfoodDM, EtwChannelDefaultInternal, KitlShell, LoaderVerifierTestCerts, NetDrvVMINI, QC_8x50_OS_TEST, SensorView, SirepForPlatDev, StartKitl, TouchTools. GPSxxx from HTC_8x50_OS_WIRELESS.
Extract them from a test rom and add the content and entries in default.hv you find in rgu files.
HTC_TEST tools are xap files: DebugFlagEdit, GCFSettings, HTC BATTERY TOOL, HTCGPSTool, RegisterEdit, StopWatch, StressTool, USBModeSwitch. Refer you at the HTC_OEMAPPS explanations.
You have finished the job with OEM part, just extract the content of each of these packages in your IMGFS folder.
7. Wi-Fi problems: (optional)
Some people had some troubles with the old roms and wifi. In forum most were speaking about the SD-card but it didn’t solved the problem (and gone back to android^^).
It’s not the only problem. If you examine the file nvram.txt which is used to enable the built-in wifi chip there are some differences between files from DFT, HD2 3.14, SCHUBERT operators.
EDIT: macaddr=00:11:22:33:44:55 in its file seems the place to put a mac adress for routers with some mac filters.
I list it below, so i use a mix from HD2. When I was using the original, I didn't reached secured networks, I had to remove battery for hours.
Code:
DFT: SCH:TMOUS/WWE/TIM/O2UK HD2 3.14: SCH:Orange + MOZ:O2UK
boardrev=0x32 boardrev=0x36 boardrev=0x32 boardrev=0x36
pa0b0=5747 pa0b0=6003,6003,5576 pa0b0=6003 pa0b0=5552
pa0b1=64128 pa0b1=64086,64086,64172 pa0b1=64086 pa0b1=64245
pa0b2=65195 pa0b2=65195,65195,65155 pa0b2=65195 pa0b2=65200
pa0maxpwr=72 pa0maxpwr=82 pa0maxpwr=72 pa0maxpwr=78
opo=20 opo=16
ofdmpo=0xAAAAAAAA ofdmpo=0xAAAAAAAA
mcs2gpo0=0x6666 mcs2gpo0=0xAAAA mcs2gpo0=0x6666 mcs2gpo0=0xCCCC
mcs2gpo1=0x6666 mcs2gpo1=0xAAAA mcs2gpo1=0x6666 mcs2gpo1=0xCCCC
rssismf2g=0xa rssismf2g=0xa,0xa,0xa rssismf2g=0xa rssismf2g=0xa,0xa,0xa
rssismc2g=0xb rssismc2g=0xb,0xb,0xa rssismc2g=0xb rssismc2g=0xb,0xb,0xa
rssisav2g=0x3 rssisav2g=0x3,0x3,0x3 rssisav2g=0x3 rssisav2g=0x3,0x3,0x3
rcal_flag=0x61 rcal_flag=0x61
rxpo2g=2 rxpo2g=1 rxpo2g=2 rxpo2g=0
rxpo2gchnflg=0x1c00
btc_params6=20 btc_params6=20
I suggest to modify this entries in default.hv too
Code:
HKEY_LOCAL_MACHINE\Comm\BCMSDDHD1\Parms
"11nModeDisable"=dword:0 ; Wifi n
"PowerSaveMode"=dword:0 ; 0: Best Performance 1: Best Batterry 2: Between
"IBSSMode"="0" ; set the connection type in an ad hoc network (b/g)
"LegacyPowerCycle"=dword:0 ; new rom entry
"FrameBursting"="1" ; communication protocol (higher data transfer throughput)
8. Build your rom:
All this process can be found in the forum for more explanations:
Rename the your IMGFS folder to dump (yes you could have done it at the beginning^^) with HTCrie open the part04.bin from DFT you find in Data.zip, select IMGFS and extract IMGFS.bin
With ImgfsFromDump recompile the new IMGFS, the command line is: ImgfsFromDump imgfs.bin imgfs-out.bin
With HTCrie replace the IMGFS in part4.bin: select IMGFS, click on add files, choose imgfs-out.bin, it take only few seconds.
Replace part04.bin in Data.zip by the new one and flash it with DWI, you’ve got it!
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)
26/06 working great for me!
No issues other than the usual bugs!
To increase the speed, download Advanced Config Tool here: http://forum.touchxperience.com/viewtopic.php?f=11&t=890 and then in the "tweaks' section, check 'Don't dehydrate apps on pause' and UNckeck 'Enable Wi-Fi 802.11n Mode' or wifi won't work. (may or may not work, try not to fiddle with the settings too much )
Mango next !!
** also reserved for future comments *** =D
oh man. what have u done!! ;-)
waiting for the link.
GOD!!!
U are the ONE!!!!
Waiting for your link...
waiting on link too.
btw what do you mean send "Miss U" to the number?
Hope this brings out others to provide custom WP7 roms.
Hi YukiXDA,
I don't think you are a "noob" by any stretch of imagination.
I must admit most of it is too intimidating for me to even think of attempting. so I will, like I'm sure a lot of other users, will be waiting patiently for you to upload the ROM.
If I understand the last part right - All I would need to do to update my phone to NoDo is flash your updated ROM using DWI, isn't it?
Not noob but I begun from scratch lol
Imagination and thinking it's possible without DFT tools and new malgr. I regret the fact that there isn't a groupware at xda to achieve such of things (and a way to update SLDR/NK) since some guys have a lot of knowledge here. I hadn't but I didn't understand and not like that we are all waiting DFT tools and release as they have it from several months. So I tried ^^
Yes I've put my Data.zip beside DWI, same way as before for now
Remeber it's a first test version, we need reports...
It's uploaded
@thebranded:
I hope It 'll encourage other people to develop more WP7 stuff on HD2 too.
The problem of updating XIP is for any phones not just ours. But new drivers for future updates yes.
"btw what do you mean send "Miss U" to the number? " -> Just send a sms with "MISS U" as text (for my private life^^)
you are a fake foreigner，bie lai zhe tao le，tao bu chu shen me dongxi chu lai de。
hi XD(XD应该是国语?)
shen ma de fu yun a
神马都是浮云，鉴定完毕！
B!ueice said:
假洋鬼子，就别来这套了，到处乱喷，没人会理你的。
Click to expand...
Click to collapse
支持B!ueice，有本事的也建個論壇搞個直刷讓全世界人看看，別只是說這不好那不好的，這顯得你很沒本事。
這到底是神馬？？跟神馬？？？
downloading now.
hey YukiXDA. what about u'r device? everything working good?
i'll test and report back.
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
JonnieLasVegas said:
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Just installed now - only just got started and i don't have a code for sign in, so cant test live etc but so far looking good.
Says version is 7.0.7392.0.
Copy and paste is available and working..
wifi working...
....
It DOES appear to be unlocked - tried installing apps with toms XAP installer..
Says it fails after a while-but checked phone and app is on phone and working
this ROM
Hi,
I got an questions ?
1. How fast is this ROM ?
2. Is this ROM unlocked + prevented to lock again ?
3. Did you fix the green/yellow color after shot with flash ?
Thanks a for info and good work !
Related
So, you wanna cook a rom but don't know where to start??? Is the Raphael Kitchen & PPCKitchen to complicated? Are you only interested in changing a few graphics, or removing programs from a rom that you don't use?
Well, then this thread is for you. This info is also good for chefs with existing builds that want to make quick changes to OEM packages & keep their rom up to date with the latest apps & packages.
Firstly, I need everyone to say a big thank you to Bepe, Tolstoy at PPCGeeks, Bot, Kyphur, Oli, Pof, Cmonex, & a big thank you to qsqa!!!
This lite kitchen will allow you to make changes easily to all stock roms & even to cooked roms, if your chef is kind & confident enough to create a version that includes all of the rgu & dsm files. Have a paticular rom you like & only wish to change a few items? Ask your favorite chef to get with the spirit of XDA-Developers & to create an easybake compliant rom! Just like qsqa did!!!
I will also be releasing a rom, light & very empty for all of you wishing to have a rom that is suited best for the person that has to use it, YOU!
I will be including guides, tools, suggestions, roms & all the things necesarry to create your very own customized rom, both easily & based on a good solid stable build.
This is an easy five step process that allows you to make any unprotected rom your own & the tools & methods have been only slightly adapted by me from a nice guide prepared by Tolstoy aimed at CDMA devices.
First Things First - Preparing for your easybake experience!
Download the attached Raph_Blank_Kitchen at the bottom of post #1 or from here: http://rapidshare.com/files/174704051/RAPH_blank_kitchen.rar Uncompress/extract the Raph_Blank_Kitchen to your C: drive.
Find & download any OEM shipped/extracted or easybake compliant unprotected rom such as that I will release shortly, or from qsqa, i.e. PROven 1.08
After Extracting your new Raph Easybake Kitchen you will find a folder in C: named Raph_Blank_Kitchen. Within this directory you will find several more folders:
1: OEMizer - a tool to help you create oem packages, registry tweaks or provisioning xml's.
2: RUU - This folder is the output folder where you will find your rom completed & ready for flashing after an easy 5-step baking process.
3: Tools - This folder contains everything you need to cook a rom, change the page pool, etc...
Within the root directory, you will also find the following files/programs:
1: PrepIt.bat - This script deconstructs any Rom, seperating it into OEM, SYS, & ROM folders, placing the modules & files in their appropriate place for cooking. After running Prepit.bat you will see 3 new folders inside your kitchen, OEM, ROM & SYS.
A. OEM - This is the directory in the kitchen that you will copy your OEM packages into to add programs to your rom. You can also delete packages included by other easybake friendly roms.
B.SYS - This is the similar to the OEM in that you can delete packages from the donor rom, changing packages here will require the use of G'Reloc & possibly RebuildDSM or BuildDSM. Deletion of packages however is easy.
C: ROM - You won't do anything with this folder at this point in your chefdom, but this is where the OS & XIP meet.
2: G'Reloc.exe - This will relocate modules that you have altered.
3: BuildOS.exe - This builds the operating system portion. It combines the OEM's and System files.
4: BuildIt.bat - This script builds your rom. It will Package everything together and copies your new rom to the RUU directory.
Now you got it all set up!!! So, How easy is it???
Try 5 easy steps!!!
Yep!!! Five steps to your own cleaner customized rom:
1- PrepIt.bat
2- Add/Remove OEM Packages/Tweaks/Files
3- BuildOS
4- BuildIt.bat
5- Flash your newly customized Rom
Other important info:
So, now you have extracted the Kitchen to the C: drive, copied the base rom (.NBH file)
Step Details:
Step #1: Deconstructing your base rom
Run PrepIt.bat - Just double click on the file named PrepIt.bat, or run it from the CMD Prompt. This will again seperate the nb content from the nbh, split the nb content into the IMGFS & XIP Content, & Dump the Imgfs into the appropriate SYS or OEM Folder. This step also renames your donor rom to Input.nbh.
Step #2: Adding or Removing OEM & SYS Packages
Addng programs, registry tweaks, or provisioning xml's is as easy as copying the oem package into the OEM folder. Nothing to it! Oem packages can be made or downloaded from numerous sources.
ADD PROGRAMS- simply drag your OEM from the right PPCGEEKS_OEM directory and drop it into the c:\kitchen\OEM folder
Removing Items can be a little bit tricky. Use common sense here. Look for packages named after whatever you want removed & delete them. Most anything in an OEM folder can be removed with little consequence, some thing in the SYS folder you don't want to mess with though. Take a look, look for the name of what you want gone & if its a simple program like Total Commander for instance, just delete the appropriate folder & it will be gone.
Step #3: BuildOS.exe
Just click the BuildOS.exe BuildOS will then build a new OS while adding/removing the OEM packages that you either added or deleted in step two. Clicking BuildOS.exe will bring up a new window, That is the BuildOS program. In the window you should see most of the OEMS that you added. Make sure you check mark the OEM Packages that you have added. Once you are sure you have selected all the programs you want added to the rom, click that green arrow in the upper left of the window. This will create the OS. You will see the green progress bar to the bottom right.
BuildOS will say DONE in the bottom status area when complete.
There are a few things that can go wrong, but the most common is duplicate packages. Make sure your not adding a duplicate package to the rom & you should be okay.
Step #4: BuildIt.bat
This step will go thru the process of reconstructing the newly moddified rom back into the .nb & then the .nbh flashable format. If all went well, you'll have a new RUU_Signed.nbh in the RUU folder directory.
Step #5: Flash your new ROM
In the RUU folder you will find your new rom & the tools needed to flash it. Just click the ROMUpdateUtility.exe & it will flash your new rom.
Changing the Pagepool...
Now that your rom is complete, you may want to change the pagepool. Again, I have included everything you need to accomplish this in the Tools folder.
Step 1: Open the XVI32 folder & launch xvi32. Open the newly created rom in the RUU folder named RUU_Signed.nbh or drag & drop it to the XVI32 folder. In XVI32, use the search function. Select the bubble that says "Hex" & search for this hex string: 03 15 A0 03 02 15 A0 13 00 10 82 E5
Change the last four numbers to 00 00 A0 E1
Then press F3 on your keyboard or search for the Hex string: 03 15 A0 03 02 15 A0 13 00 10 82 E5 once again & again change the last four digits to 00 00 A0 E1.
The page pool is now NOP & can be opened & set to whatever number you like using the pagepool changer I've included in the Tools folder.
Moddifying Graphics & Customizing Packages
Coming Soon!
Other Useful & Important Tools
There are several tools that make customizing roms fun, fast & best of all...FREE. Of course there are other tools that cost money that are recommended, but let's see what we can come up with as for suggestions of free or low cost software for customizing roms. Where available & as time permits I will upload all of the tools &/or give links to the developers website along with basic instructions for making their use easy & frustration free!
A few of the must haves are as follows:
1. CERegistryEditor - This is an amazing tool that allows you to make registry changes on your device via activesync, export registry setting, unlock your registry, etc... This tool will also work with all registry formats including .reg, .rgu & most importantly .hv registry hives can be edited directly. This tool is amazing & very powerful as it allows you to export values as .rgu files that can then bee made into registry tweak OEM packages with the already included OEMizer or made into provisioning xml's using the famed rgu2xml tool in conjucntion with the OEMizer.
Coming soon: Tips & examples on using this tool to create registry & provxml packages.
2. EditPad Lite - EditPad Lite is a free version of EditPad Pro & is simply the BEST free text editor around period. EditPad will allow you to directly read & modify many important file such as initflash.dat. This allows you to remove or add things to your rom such as Folders, Start Menu items, etc... You can also use it to modify .rgu files, .reg files, .lnk shorcuts & many more.
Coming soon: Tips & examples on using this tool to modify many things in your rom.
3. Gimp - This is an amazing & most importantly free, graphic editing tool that handles numerous image file types. This can be used to edit, modify or change images to suit your own tastes. Items such as Dialer & Dial Pad Graphics & colors can easily be modified with gimp. Icons & folder icons, such as .ico files can also be edited allowing you to customize your folder icons when used in cojunction with PEexplorer, Gconvert, or Resource Tuner. Simply put, Gimp is a necesarry tool of great value when it comes to modifying or even creating new or existing graphics & images.
Coming soon: Tips & examples on using this tool to modify many things in your rom. Including an overview of some of the greatest & most overlooked features included in this tool.
Okay last one
EasyBake Compliant ROM's & Chefs!!!
1: PROven 1.0x by qsqa
2: M-ROM 1.1 by merten3000
3: Semilite or v2final by Aruppenthal
4: G3 Lite & Ultralight - Coming Soon!
Come on Elite Team!!! Other Chef's! Get with the spirit of XDA & let's see what happens when we are all free to expand on others breakthroughs!!!
Wow, I just start using it, want to modify qsqa rom LOL Thank You!
By the way I'm using win vista, hope everything of the kitchen work with it.
Again Thank You!
I think this deserves to be sticky. At least for the time being
ahh this program basically ensures me spending more time messing with my phone =]
thanks for your hard work!
Is this working with Vista 64-bit?
im running vista 64 and it works perfectly fine
just be sure to run as admin
beautiful tutorial,. congratulations and thank you GSLEON,.
hchavarria said:
Is this working with Vista 64-bit?
Click to expand...
Click to collapse
sure,.
When you have all needed files installed, it should work,.
any idea if this will work for tilt roms as well?
sdale said:
any idea if this will work for tilt roms as well?
Click to expand...
Click to collapse
The kitchen would need some modification to work on the tilt I believe. GSleon3 could say for sure. I will take a look at it if i get a chance.
BTW great work on this GSleon3
what a useless thread...... unsticky this please!!!!!!
LMAO JK gsleon..... Great job on this bud!!!
This Cooking device [kitchen] will not work with the new [ROM][DUTCH][28-12-2008] M-Rom v1.3 (XIP/SYS build 20931) 'unprotected' from merten3000.
Thanks for this thread and info. I want to begin cooking ROMs and was not sure where to start but now I do.
I would like to use the latest AT&T ROM for my build. How can one make it unprotected so it can be used in your kitchen?
I have the Sprint version of the HTC Touch and I would like to start cooking my own ROMs but I am having a hard time finding the Base ROM to Start cooking, (the ???.nbh file). If someone could guide me as to where I can get one of these file I would appreciate it. Is this something I can pull from my phone and if so what is the name of the file. Thanks
Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is.
There are many chefs that provide quality ROM's for you to use. However, if you've gotten excited about the idea of cooking your own ROM's, you've probably felt overwhelmed by the volume of Forum Threads and Wiki pages at your disposal to learn how to do this. The goal of this thread is to provide a starter kitchen so as to help new and intermediate chefs; the kitchen will produce a fully functional ROM for a Raphael device.
The kitchen includes a Read Me and Change Log file. The Read Me file contains answers to frequently asked questions as well as "known" issues. The Change Log file includes a list of changes that were made to files such as the .RGU, .PROVXML, etc.
Kitchen
Post #2 provides a kitchen that is built with Ervius Visual Kitchen; the post additionally provides updates to the content of the kitchen when necessary.
Discussions on the current version of the kitchen posted in this thread begins here: http://forum.xda-developers.com/showpost.php?p=5398310&postcount=1176
Application Packs
Post #3 provides additional applications that have been tested in the Ervius Visual Kitchen. It is recommended to download the packs before altering the kitchen.
OEM Packs
Post #4 provides OEM folders that are specific to the Ervius Visual Kitchen. These are intented for chefs who are looking to add the latest OEM to an existing kitchen.
ROM/SYS Packs
Post #5 provides ROM (XIP) and SYS folders that are specific to the Ervius Visual Kitchen. These are intented for chefs who are looking to add the latest ROM/SYS to an existing kitchen.
Workstation/System Requirements:
WinRAR 3.30
http://www.rarlab.com
IZArc 3.81
http://www.izarc.org
Microsoft Visual C++
http://msdn.microsoft.com/en-ca/visualc/default.aspx
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft .NET Framework
http://msdn.microsoft.com/en-us/netframework/default.aspx
Microsoft .NET Framework 3.5 Service Pack 1
Microsoft .NET Framework 2.0 Service Pack 1
Microsoft .NET Framework 1.1 Service Pack 1
Tutorials:
The following tutorials are available for newcomers who wish to learn about how to use the kitchen in this thread:
Kitchen
Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=521632
Porting
Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen
http://forum.xda-developers.com/showthread.php?t=526610
Wiki:
Previous versions of the tutorials, kitchens, tools updates, fix packs, OEM packs, and ROM/SYS packs can be found at the Raphael Wiki in the WM6.1 ROM Kitchen (Simple and Visual) section.
http://forum.xda-developers.com/wiki/index.php?title=Da_G's_Simple_ROM_Kitchen
Languages, DPI, Resolutions:
Language localization packages, DPI files, and Resolutions can be found in the Development & Hacking forum.
http://forum.xda-developers.com/showthread.php?t=547314
Package Repositories:
Raphael OEM Package Repository
http://forum.xda-developers.com/showthread.php?t=482173
Raphael OEM Packages
http://www.4shared.com/dir/12314954/9a1ec6bc/sharing.html
Credits:
Special thanks to the following folks for sharing their knowledge and expertise. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
da_g
cmonex
olipro
bepe
ervius
ameet
Contributions:
A thanks goes out to the following folks for their contributions to the kitchen. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
da_g
aruppenthal
b4pjs
captain_throwback
eras2r
jmckeejr
noonski
notatreofan
nrgz28
r.camies
xboomer55
Visual Kitchen
Created using Ervius Visual Kitchen 1.8.2; includes sleuth255 User Customization (UC) version 2.0. This post includes a list of packages that are included in the kitchen, a change log, and a read me file - which can also be found in the documentation folder of the kitchen. Also, take a moment to look at the Visual Kitchen Pack post, there's a list of what is included in the pack attached to the post.
WWE Visual Kitchen 6.1, OEM: 5.12.206.1 (20779), SYS: 21055, ROM: 21056/20779, 158 MB, 17.01.2010
Post-Download Instructions:
Extract the contents of kitchen archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Move the kitchen to the desired location.
Cooking Instructions:
Launch Erviuskitchen.exe.
Click the Load ROM button.
Select the FUZE/PRO .ERV ROM file.
Click the Create ROM button; allow the process to complete.
Wait for the Done message to appear in the Bottom Status window.
Exit the Ervius VisualKitchen application.
Tip
If the compilation is successful, the last three (3) lines in the Report window of the Ervius VisualKitchen application will display: ROM Builded successfull! Reenabling all skipped packages. All packages Reenabled. All Done.
RUU_SIGNED.NBH will be in the RELEASE_Raphael kitchen folder.
Verify the BUILD_LOG file after compiling a ROM; module entries in SLOT0 typically indicate that the stability of the device will be unpredictable; recode some modules.
The Sensor SDK 4 package provides enhanced screen rotation support; it includes a .PROVXML file that can be customized to include additional applications - Whitelist & Blacklist.
Known Issues:
Bottom of text cut-off in Connection Setup with large menu package installed.
Very Rare: Tapping Cancel on Connection Setup panel may be required if panel appears during post-ROM flash and/or Hard Reset.
Very Rare: Airplane Mode may be enabled (instead of Phone Mode) post-Hard Reset configuration phase. Pro: make setup finish faster, Con: extra tapping steps to switch Phone mode back on from Comm Manager.
Kitchen Tools Update:
Latest version of Ervius Visual Kitchen tools that have been tested with the kitchen in this post. The KITCHEN_BUILD_ROM.BAT has been updated to include logging; otherwise, the remainder of the files are those found on the Ervius Visual Kitchen thread.
None Available
Kitchen Fix Packs:
A kitchen Fix Pack addresses issues and oversights that were discovered after the release of the Visual Kitchen. The Fix Pack only contains changes to files and packages that were released as part of the kitchen. The Fix Pack does not contain changes to packages that appear in a Visual Kitchen Pack; changes/fixes for packages in a Visual Kitchen Pack will be addressed as part of a new pack.
None Available
Visual Kitchen: Application Packs
The Kitchen Application Packs includes additional applications that have been tested in the Ervius Visual Kitchen. The packages have been organized (sequenced) so as to ensure that the ROM produced by this kitchen is the same as the Package Builder (legacy) kitchen.
The pack applications have all been set to Unselected (False) - a package must be double-clicked to include the package during ROM compilation. The PACKAGES.TXT files in each PACK will overwrite the base kitchen version - providing a description for each package.
The .TXT files attached to this post contain the list of packages that are in the corresponding kitchen pack.
Visual Kitchen PACK 1, 29 MB, 13.06.2009
Visual Kitchen PACK 2, 28 MB, 13.06.2009
Visual Kitchen PACK 3, 30 MB, 26.06.2009
Visual Kitchen PACK 4, 50 MB, 16.08.2009
Visual Kitchen PACK 5, 05 MB, 16.02.2010
Post-Download Instructions:
Extract the contents of kitchen pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Copy the contents of the extracted kitchen pack to the kitchen .\EXT folder.
Tip
The archive folder structure matches the kitchen folder structure that corresponds to the build on which the package has been tested.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
The applications in these packs were tested using the Customized Device profile (DEVICE_CUSTOMIZED).
Recoded Modules Application Packs (Optional)
Although Windows Mobile 6.1 improved Virtual Memory (VM) by providing SLOT 60 and 61, modules can not be allocated in SLOT 60/61 - only files. Current kitchen relocation tools did not require any changes as SLOT 1 and 0 are the only slots where modules can reside. Device stability is compromised however, when there are too many modules as "spilloff" occurs into SLOT 0 resulting in reduced available memory which causes the device to report memory errors (even if it's not truly out of memory) or erratic application functionality.
RECMOD Application Packs contain versions of packages that appear in the kitchen and existing kitchen packs. These packages have had their modules recoded; the package names have _RM appended at the end of the name. When using RECMOD packages, it is important to remove the non-recoded version from the kitchen to avoid ROM compilation errors.
Visual Kitchen Recoded Modules PACK 1, 15 MB, 16.08.2009
Visual Kitchen Recoded Modules PACK 2, 05 MB, 16.02.2010
Visual Kitchen: OEM Packs
Chefs looking to simply update their existing kitchen OEM folder without having to download an entire kitchen can now do so with an OEM pack. The OEM Packs include the OEM folder for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The OEM pack also includes a corresponding optional DEVICE_* and OVERRIDE_KEYPAD_* package.
The DEVICE_* package contains all of the files that were removed from the original OEM folder. Closely examine the contents of the package before use as it contains untouched stock files that were found in the released ROM.
The OVERRIDE_KEYPAD_* package contains a copy of the the KEYPAD.DLL file from the .\OEM\OEMDrivers folder and can be used to ensure that the desired KEYPAD.DLL is installed during ROM compilation.
A text (.TXT) file appears in the .\DOCS folder of each OEM pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of the OEM pack change logs have been added.
OEM: 5.12.206.1 (20779), 06 MB, 30.07.2009
OEM: 5.11.502.2 (20771), 22 MB, 30.07.2009
OEM: 5.05.405.1 (20764), 08 MB, 30.07.2009
Post-Download Instructions:
Extract the contents of OEM pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Copy the contents of the .\OEM\Raphael\.VM\ folder in the kitchen to the extracted OEM pack .\.VM\ folder (ex: C:\XDA\VISUALKITCHEN-OEM-PACK-20771\OEM\Raphael\.VM\).
Rename the existing .\OEM folder in the kitchen (ex: OEM.20771 or OEM.precopy).
Kitchen Conversion Instructions:
Copy the contents of the extracted OEM pack, which now includes the contents of the .\OEM\Raphael\.VM\ folder, to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).
Rename the .\OEM.<buildnum> folder copied to the kitchen to .\OEM (ex: OEM.20771 to OEM).
Tip
The archive folder structure matches the kitchen folder structure of the legacy kitchen found in this thread.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
Note
The DEVICE_* and OVERRIDE_KEYPAD_* packages will be set to Selected (True) - a package must be double-clicked to exclude the package during ROM compilation.
Visual Kitchen: ROM/SYS Packs
The ROM/SYS Packs include the ROM and SYS folders for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The ROM/SYS also includes corresponding base ROM compilation profiles, pre-configuration (ERV) files, that have been tested in the kitchen.
Chefs will find untouched versions of the base XIP.BIN and OS.NB.PAYLOAD (no imgfs) as well as the donor XIP.BIN and OS.NB.PAYLOAD (no imgfs) - when available.
A text (.TXT) file appears in the .\DOCS folder of each ROM/SYS pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of ROM/SYS pack change logs have been added.
SYS 21056, ROM: 21056/20779, 37 MB, 17.01.2010
SYS 21056, ROM: 21056/20771, 37 MB, 17.01.2010
SYS 21056, ROM: 21056/20764, 37 MB, 17.01.2010
Post-Download Instructions:
Extract the contents of ROM/SYS archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Rename the existing .\OEM\Rapheal\.VM folder in the kitchen (ex: .VM.20771 or .VM.precopy).
Backup the existing .\ROM\Raphael\ files (.TXT, .BIN. PAYLOAD) in the kitchen. The files to backup are:
INFO.TXT
OS.NB.PAYLOAD
ROMHDR.BIN
XIP.BIN
Kitchen Conversion Instructions:
Copy the contents of the extracted ROM/SYS pack to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).
Tip
The archive folder structure matches the kitchen folder structure of the visual kitchen found in this thread.
Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.
Note
.NET Compact Framework (NetCF) is a merged version of 2.0 & 3.5.
The following applications have been removed from the SYS folder and placed in the kitchen EXT folder; they are also available in an Application Pack and the Package Repository noted in the first post of this thread.
- Auto Data Config (ADC)
- Adobe Flash
- Infrared Data port (IrDA)
- Live Search
- Modem Link
- Remote Desktop Mobile
- Voice Command (MSVC)
- Voice Over IP (VoIP)
- Windows Live (MSN)
- Windows Media Player (WMP)
Emulator
Da_G,
Thanks for the kitchen.
Just wonder if there's any good ROM emulator to test any mod before flashing into a real life device?
This will hopefully prevent bad ROM and bricking phone.
With HardSPL, you stand little chance of bricking the phone, you can always return to bootloader and flash a working ROM. But as to an emulator, yes there is one, but it does not emulate the hardware the Raphael has, so for that purpose it would not work, none of the drivers would load up and the emulator would not boot. You would have to create a special version without drivers - but then, you aren't really testing the important part As long as you have HardSPL, you can flash without worry.
As for a guide to mashing things up before cooking, i'm putting together a large collection of packages.. choosing what you want in the ROM will be as simple as checking boxes.. as far as editing the registry goes, you need a program that can open/save in unicode.. i personally use EmEditor..
Thanks Da_G. This one is working great. I checked with base OEM/ROM/SYS folders. If I want to include any cab files how can I include them? I tried to copy a cab file in packages folder and it didn't pick up. Is there any thing I need to do? Actually my idea was to include some cab files in the rom instead of using UC while flashing.
Thanks
You have to convert the cabs to packages first.
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Da_G said:
With HardSPL, you stand little chance of bricking the phone, you can always return to bootloader and flash a working ROM. But as to an emulator, yes there is one, but it does not emulate the hardware the Raphael has, so for that purpose it would not work, none of the drivers would load up and the emulator would not boot. You would have to create a special version without drivers - but then, you aren't really testing the important part As long as you have HardSPL, you can flash without worry.
As for a guide to mashing things up before cooking, i'm putting together a large collection of packages.. choosing what you want in the ROM will be as simple as checking boxes.. as far as editing the registry goes, you need a program that can open/save in unicode.. i personally use EmEditor..
Click to expand...
Click to collapse
You're the man I wait with great patience going to also try the idiots guide as well as building in PPCKitchen as we speak I've had some issue getting the ROM to build... do I need Visual Studio as my backend dev box? I have 2003 Visual Studio but I'm thinking I need a newer version as for EmEditor; I'll grab that too. Thanks for the coaching, I hope to churning the buttah lik you my friend lol.
You need the .NET 3.5 runtime for windows (not .NET CF 3.5 for windows mobile), you can find it at microsoft's site. I believe that's the only requirement for the apps in the kitchen to run..
I'm about half-way done on the packages, archive is only 55mb so far.. gonna post a pre on my ROM thread since it's based on my ROM.
Thanks a bunch Da_G! I feel tempted to cook something. Do you also have a package that can give a man more time? Now THAT would be useful!
No packages for more time, sorry
{
"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"
}
Here's the first version of all the packages i've made thus far: http://forum.xda-developers.com/showpost.php?p=3176535&postcount=1498
You don't need the kitchen from the first post, i included it in the package there.. same steps to follow, but i've included a good amount of packages.. of course there will be more coming soon, rome wasn't built in a day
Don't forget to scroll down on the list of packages, it goes off screen in buildos
Da_G said:
No packages for more time, sorry
Here's the first version of all the packages i've made thus far: http://forum.xda-developers.com/showpost.php?p=3176535&postcount=1498
You don't need the kitchen from the first post, i included it in the package there.. same steps to follow, but i've included a good amount of packages.. of course there will be more coming soon, rome wasn't built in a day
Don't forget to scroll down on the list of packages, it goes off screen in buildos
Click to expand...
Click to collapse
Da_G YOU RULE BRO!
Posted a Diamond Phone canvas + Slide 2 Answer package, you can get it here - thanks to player911 for fixing it all up
It will of course be included in the next revision, but here it is now
Da_G said:
Posted a Diamond Phone canvas + Slide 2 Answer package, you can get it here - thanks to player911 for fixing it all up
It will of course be included in the next revision, but here it is now
Click to expand...
Click to collapse
Quick question - why don't you use original Diamond package (called "PACKAGE_Diamond_PhoneCanvas_Slider") for S2A taken from 2.03 Diamond rom? - it's working perfectly in my PROven
Dunno, figured there was some issue with it? I don't use it.. when i tested it shortly it seemed to work fine, is there a difference from the package I posted?
I've updated several of the packages in the kitchen with new builds from the just-released diamond gsm rom, and added a couple more new packages. still no scripting to select the os version you want, but it'll come
On my way out the door, so no time to upload now.. hopefully tonight Gonna test them while i'm out.
Da_g kitchen works great still don't know what I'm doing or what's going but how do I change manila's and stuff? I want to use the confuzed backgrounds and colorings.
Thanks!
The easiest way to do that is to ask monx if he can share his customized packages, you can then just drop them in the \Packages folder and select them (providing he has made an option.xml to go with it)
Hello Guys n Gals!
Its not a very long time since we have been on this forum but despite of this fact, the experience has been terrific for all of us i think. Over the past few months, We have shared a lot of information and content in this gene forum which was otherwise almost going dead. Its great to see so many chefs coming up these days, almost everybody seems to be customizing his/her own roms. These new changes in the forum users made me think about sharing content on the forum in a different, more optimal way.
So here i am, with my Visual Kitchen. Visual kitchen, as most of us know, is a combined effort of 2 great forum members Ervius and Bepe. It is the most easy, well organized and the only multi device, visual kitchen available as of now. Sometime before, our good friend Besfen and Ankit360 worked on it and made it work for Gene. Besfen also posted a great tutorial to use it full of pictures and all. As for me, i took all the packages that i have customized, debugged and maintained over time and organized them properly into the kitchen. I used all the information posted by dear Besfen and made the kitchen such that you guys dont have to do much of this work again.
So from now on, you will download this kitchen and all the packages only once, and i will post updates fully customized for this kitchen. YOu will just have to download the updated stuff only and not the whole heavy duty kitchen. This way, it will be easier for you to download and at the same time, easier for me to upload. Also, this one kitchen will work for both Old and New Gene, for both WM 6.1 and WM 6.5
Necessary details about using the kitchen are in the following posts, read these carefully. If you want to go more indepth, read Besfen's thread, here:
Besfen's Excellent Visual Kitchen 1.8.1 Tutorial for Gene
Here are the download links for the Core Kitchen Components :
Visual Kitchen Core : http://www.mediafire.com/?jwwd1jomdli
NEW! EXT Packages for Old and New Gene (updated 5-10-09) :http://www.mediafire.com/?mjoncymzgzm
Old EXT Packages (from 18-9-09) : http://www.mediafire.com/?xnmnzdznt2m
Requirements for Running the Kitchen :
The kitchen requires at least .NET framework 2.0 and Visual C++ 2008 redistributable installed on your computer. The latest versions of .NET framework and VC++ redistributable are 3.5 SP1 and 2008 SP1 respectively, and i highly recommend to install these to avoid any future problems and maintain good performance of system. The links to these components are given below :
.NET Framework 3.5 SP1 Main Setup
.NET 3.5 SP1 Setup that runs from Web (2.8 MB, rest is downloaded as needed for your computer): http://www.microsoft.com/downloads/...2F-5D1A-413D-8319-81DA479AB0D7&displaylang=en
.NET 3.5 SP1 full Offline Installer (231 MB) : http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe
.NET 3.5 SP1 Updates to be applied after its installation :
Update 1 (About 16 MB, includes 3 files) : http://support.microsoft.com/kb/959209
Note : This update has different versions for XP, Vista and Server 2003 computers and again different versions for X86 (32 bit) and x64 (64 bit) editions of Windows given on the same page. Download the one appropriate for you.
Update 2 (429 KB) : http://support.microsoft.com/kb/959209
Visual C++ 2008 SP1 Redistributable:
For 32 bit Windows Computers (4 MB) : http://www.microsoft.com/downloads/...75-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en
For 64 bit Windows Computers (4.7 MB) : http://www.microsoft.com/downloads/...ca-337f-4b40-8c14-157cfdffee4e&DisplayLang=en
I hope you guys will have a great time with the kitchen and you will be able to customize your roms to your heart's content.
Setting up and using the Kitchen
First Time Setup:
===============================
1. The first file containing the Visual Kitchen Core should be extracted to the root of a drive, ie. on C:\ or D:\ or whatever. You should get a folder such as C:\VisualKitchen or D:\Visual kitchen. Dont put the kitchen on a path that contains spaces.
2. The second file having th EXT packages should give you a folder called EXT which should be placed as it is in the Visual Kitchen Folder. It should go like C:\VisualKitchen\EXT.
Thats it! Your basic kitchen is set up. Please note that i could have been given EXT folder with the kitchen itself, but i have kept it seperate coz kitchen wont be updated most of the times but EXT folder could be from time to time.
How to insert a new OS build:
==============================
When i will post an OS build, it will come as a file called KATsVK_SYS_XIP_<buildno>.7z. On extracting this will give you two files : SYS_<buildNo>.7z and XIP_<buildNo.7z>. The SYS zip file will have a folder with the name of the build such as 21857, it should be exracted as it is inside the SYS folder of the kitchen.
XIP zip file will have a ROM folder inside it. First extarct this folder somewhere else. Then move it to visual kitchen directory. It already has a ROM folder so Windows will ask to merge these two folders. Say yes to this prompt and everything will be placed where it should.
Thats it!
Your kitchen is ready with new build.
Using the Kitchen
===============================
After you have updated your Kitchen with a new build SYS and XIP, launch the ErviusKitchen.exe (Vista/7 users should either set the compatibility settings to "Run as Administrator" or right click the file and choose the same command everytime.).
Now do this in order : In the upper 3 boxes, Choose DEVICE as New or Old Gene, Language as 0409, EXT Build as 6.1 or 6.5 depending upon which OS you are cooking, XIP build to the build you want to create rom with and same with SYS build.
Pagepool can be set at time of cooking by clicking the "Other" button on the top left corner. Also leave the -uldr and -nocert textboxes blank.
You can disable and enable the pacakges to be included into your rom on the fly by double clicking them in teh area where their names are shown.
Thats it!, hit the Create ROM button and wait for the process to finish. YOur ROM will be there in RELEASE_NewGene or RELEASE_OldGene folder.
Customizing the packages inside the EXT Folder
=====================================
The EXT folder is logically divided into 3 sections :
NewGene, OldGene and Shared.
The first two are further divided into 6.5 and 6.1 and contain packages specific to these OSs. The packages are different for both OSs, mostly due to the fact that WM 6.5 needs the new PNG icon system.
Shared folder contains packages that can be used across both devices and across both operating systems.
Note that The NewGene and Old Gene folders have exact duplicates, and one might worder that why didn't i put them all inside the Shared folder. The answer is that, shared folder cannot be subdivided further to arrange packages for 6.1 and 6.5. So thats why this redundency was needed.
While updating these folders just keep in mind that you put packages according to their type in different folders. If the package contains WM 6.5 png icons and registry settings, then that package should be seperately placed inside WM 6.5 folder in both NewGene and OldGene folders. If its a generic package with no icons and anything like certain frameworks, dlls etc, then it should go into Shared folder outside the NewGene and OldGene folders.
The NewGene and OldGene folders also contain Common folder, which was not useful in the present scheme that i used. So these are left empty, however, you cannot delete these, the kitchen will stop working.
Cutomizing the SYS folder
=====================================
The SYS folder is also divided into many subfolders at various levels. At first level, its divided according to the Build number, each build number has its own folder inside SYS.
Then inside each build, there are three folders, a Shared folder containing Language only files and Common SYS, a DPI_96 folder containing 96 dpi files that are applicable for all 96 dpi resolutions like 240x320, 320x320 etc. and a DPI_96_resh_240_resv_320 that contains files specific to the devices with horizontal resolution of 240 and vertical resolution of 320 like our Gene.
This arrangement allows files for multiple resolution based devices to be kept in one place. Files not specific to resolution of devices are in Shared folder and resolution specific are in other two folders.
Now again, all these three folders are divided into 2 more folders each, 0409, and Common. 0409 is the language code of WWE, United States English, so files that are language specific goes into this one and other go into Common.
You dont have to remember all this, just remember one thing, if you add a package (which can be a group of one or more folders like xyz, xzy_dpi_96, xyz_lang_0409 etc ), its components should go into the right folders and when removed, all the folder should be looked for its lang and dpi folders too.
Other Folders
=====================================
1. Utility : The utility folder contains two utilities:
a. SuperRecMod: This utility can be used to recmod modules(convert modules to flat files). Create a shortcut to the SuperRecMod.exe to your send to folder. In Windows XP, this can be found by just going to start>Run, writing sendto and pressing enter. IN Windows Vista and Windows 7, it is located at <systemdrive>:\USers\<username>\Appdata\Roaming\Microsoft\Windows\Sendto, where <systemdrive> is the driver letter of the drive on which Windows is installed (uaually C drive) and <username> is the user account name you are currently looged in to windows with.
After doing this, you can just select the modules to be recmodded, right clicking on them and choosing SendTo><your shortcut name>.
b. PruneNonQVGAResources.bat : In a raw sys, like that posted by our friends da_g on xda and joojoobee666 on ppcgeeks, the folders contain some non qvga files in the common sys. This happens in WM 6.5 SYS, in LockscreenEA, LockscreenNonEA, BronzeEA and BronzeNonEA folders. Now you can create a shortcut to this batch file in the sendto menu just using the method specified above and send these folders to this batch file to get rid of Non QVGA cpr files.
2. RUU: This contains the ROM Update Utility, just put the generated ROM inside this, connect your phone to pc with cable and run ROMUpdateUtility.exe to update your ROM.
3. RELEASE_NewGene and RELEASE_OldGene : These folder are used by the kitchen to store the final .nbh file after cooking.
4. Removed: In this folder i put those components which i dont use generally in my roms, these are mostly taken from SYS and are stored according to build numbers.
A Big thanks to :
Bepe, Ervius, Besfen, Ankit360, Ramerson, Zelalat, Pasha, Lomlom, Olipro, Orefkov and all those great friends, names of whom i have forgot to mention,
for all the knowledge and tools that these people have created and shared with their immensely brilliant minds and days of hard work Wothout you guys, i would not be able to even flash my device once.
Thank you all!
Reserved for Future use
Thank you
will not be enough
But really we should change the GENE name to SUMIT
Thank you Boss
i will try asap
Hey KRAZY,While extracting kitchen My Norton 2010 says-
{
"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"
}
@Krazy: Excellent Work As Always..thanks so much for sharing..
i disabled my antivirus while cooking.
while making ROM i read this line...why it is saying 6.1 NK.exe.is he talking about WM6.1 ROM,but i cooked WM6.5!!
382 Modules present; with 6.1 NK.exe Max Modules is around 535 for this ROM! btw, bootable ROM will be created!!!
Click to expand...
Click to collapse
BTW,i cooked successfully but not flashed YET..BUT THANX A LOT..now i can manage multiple bui;t in one KITCHEN!!!hurray!!
@deathgame:
The virus warning is false and is a usual case with system tools which disassemble code. Sometimes partner companies (like Microsoft and others) also ask Antivirus makers to mark these executable as virus as it helps in "illegal" activities. But mostly its a false warning by a lousy antivirus engine.
I have tested this kitchen with atleast 5 antiviruses and my system is an upto date Windows 7 RTM one with UAC turned to full setting (just like it was in Vista) not to a level below it which comes by default with Windows 7. Apart from that, my mind is also an antivirus and it has worked really well since last 10 years, Never had a virus in my system, except for the time when there was a sudden increase in Pen Drive based viruses on XP. But before it could bother me, Vista came and i switched
As for the 6.1 nk.exe message, understand that although we are cooking Wm 6.5 roms, we dont have a 6.5 native kernel or nk.exe which resides in OEMXIPKernel package in XIP. 6.5 native kernel means the operating system kernel which is compiled against the 6.5 code and HTC device drivers. This kind of kernel will provide the two extra slots of virtual memory allowing more modules to be used inside roms.
If, suppose, we had a native kernel for 6.5, we would check the Real WM 6.5 AKU checkbox and then we wont have to recmod modules at all
@Others: Thanks guys! Enjoy yourself
hello sumit i followed ur steps bt when i click create rom it says specify device id what to do please help me
You have not followed my steps properly actually. On tht top of the kitchen window, First of all, select the Device, from the Dropdown list. This will fill up the Device ID.Then choose EXT Build, then XIP Build and then SYS build. After that click Create ROM.
wooooooooooooooooooooooooooooooooooooooooow what ......nooooooooooooooooooooo this is happening...u r great..i build rom using visual kitchen...only one thing how can i add new packages...in which folder?should i have to build new packages or older one r sufficien?plz
saurabh88 said:
wooooooooooooooooooooooooooooooooooooooooow what ......nooooooooooooooooooooo this is happening...u r great..i build rom using visual kitchen...only one thing how can i add new packages...in which folder?should i have to build new packages or older one r sufficien?plz
Click to expand...
Click to collapse
u can put packages in
D:\VisualKitchen\EXT\SHARED\Common_Packages
if software is compatible to both
kraaaaaaaazy for u........done in done...using 21857....rocking....bi=uild using ur visual kitchen..rom cooking is never easy then before but thanx to ugreat man...salute......
yes build new 23052 and it rocks..but little bit slower and sluggish then 21857..will defiately switch to it tommorow....
@Saurabh: Thanks buddy. If you want to customize the kitchen, read the first 3 posts, i have explained everything. Specially look in the section, customizing the EXT folder, that will solve your queries
Hi Sumit, as always, great work.
ramersonw said:
Hi Sumit, as always, great work.
Click to expand...
Click to collapse
+1 for tht
The material provided in the unofficial theme. In the case of a failed flash unit, and the topic of the site is not liable! All actions are at your own risk.
I present you the firmware WM 6.5.Standard Build 23 017
Just a flashing 3 languages (0407 (German), 0409 (English), 0419 (Russian)), the default English. And 3 input language.
Screen theme (Sliding Panel & Sliding Panel Media) converted from Rose Sliding Panel's, which made it possible to use HTC Weather.
After the firmware necessary to reboot the device!
Programs: Celetask, CHome configurator, Clock on Top, WM5torage, Registry edit.
Links:
http://www.mediafire.com/?hnd324uanwwz0id
https://rapidshare.com/files/3185754262/6.5.BIN
Calls, SMS sending, SMS takes, SMS as chat, Bluetooth works, in general, everything seems to be working pretty well!
Thanks to all who helped in creating this firmware!
downloading - will give you feedback asap
I have checked on the package and here are the comments:
The backlight/display driver is not acting according to the settings in the control panel. The display does not get off. The light gets off - but not the LCD. You can see that when you put the display in bright light. When making my kitchen for WM6 I have tried out several different drivers all having one or the other problem and finally decided for the one present there. Please re-check your choice in the light of above problem which creates a big battery drain unfortunately.
The German language is only fractional available. I think that the packages are missing some .provxml files or that these are not read correctly. You can cross-check needed actions for multi-language in my beginners guide for cooking. Especially tracking down the correct execution of .provxml is tricky. There are some threads at XDA dealing with this. I found finally that using the rapiconfig tool on the connected PC sending the files for execution is giving a fast and reliable method for debugging. Search for "provxml" and "rapiconfig".
For my kitchen I had added at the end of each .provxml a registry entry to write to HKLM\Platform with the name of the .provxml as an entry. This way you can check if the file was executed in the first place and then further investigate which was not.
Finally I have seen that the WM65 allows to have skinned menus which complement the sliding panels appearance. Would be good to see that in the WM6.5 ROM as well.
Good luck with your further cooking!
Oh one last thing: You should change your topic title to include "WM 6.5". Not all know that WINCE 5.2.23017 is one internal version of the WM6.5. I think that WM6.x translates to WINCE 5.2.y before that was WM5 with WINCE 5.1.z.
tobbbie thanks for the posts!In other rom, i want to do all languages good!
Upd.04.09.11
Hmmm... I don't know what with backlight driver!!!I i don't change him!
Nex update will be only with 2 languages (en-ger and eng-rus) because, i don't know how edit mxip_lang.vol!!!
Have you done anything lately to the ROMs? I finished my Typhoon and Tornado porting to OS Builder, so Hurricane is on the list now to have these old candy-bar phones complete on OSB.
When dumping the ROM with OSB, I noticed that you had used the "merge packages" option when assembling it. This makes it harder to get started, though not impossible as I have the XIP to build my own 6.5 (which I used from the Captain for the Tornado).
Where did you get the base from?
Which kitchen tools have you used?
Hi tobbbie!
Ok, i send you archive later.
but there is a problem, display driver(backlight) don't work correctly(i trying 5 or 6 backlight.dll) and if driver saving power correctly, when you receive incoming call, display don't turn on =(
I think best choose for hurricane is 6.1 =)
It is strange with the backlight. Usually the OEM parts are those that do NOT change in the porting process and so their behavior should also not when the SYS changes.
Problem with the Hurricane is that many OEM modules do not have a relocation section and so can not be properly relocated by some tools. In the batch kitchen I used, the wmreloc.exe could magically do the job nevertheless, probably by making clever general assumptions on the structure of the modules.
When porting Aleut's WM65 for Typhoon to OS Builder I have identified the modules without relocation section (wmreloc writes a special file to the modules folder for those) and "nailed" them to their current location by adding them to the OSB list of "do not relocate" modules.
To be sure that you start with a working set of modules, it is mandatory to start with a dump of such a working device and not a fresh directory setup - where you would rely on the relocation to properly work for ALL modules.
For Typhoon there were just 5 modules without relocation section because there existed a leaked WM5 "dogfood build" for that device. This had all modules including their relocation section. So just the non-Typhoon (Feeler and Amadeus) specific things (keyboard I remember) needed that special treatment.
For the Hurricane I had counted many more such modules and I am not sure if I will ever get a running OSB setup for this. Last time I tried I could not even get my working WM6 setup rebuilt, so this project may find an early ending.
Good news: I got my WM6 build running and re-built with OS Builder. Took some time to discover that the empty boot.rgu from OEMXipKernel package has left out the Launch20=service.exe from the resulting registry, which made the boot stop at that point.
So nailing the OEMDrivers does work here as well - there is hope for more to come here as well
Tobbbie, it's fantastic!!!
I use your kitchen to create imgfs.bin, then i use imgfs.bin with program nbwork to create os.nb(with uldr.bin xip.bin imgfs.bin) and then use you program xipbin =)
To port wm standard roms, i also tryed 28004, and once it's work, but there is no different =)
P.S. links add some minutes later, now uploading to mediafire.
Thanks for your work!
link: http://www.mediafire.com/?qu1x574f8u437g0,lb4ha9rm53n9gpu
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Why do you need extra tools outside my Hurricane kitchen set? If you put the WM6.5 XIP and Partition framework in the Source folder with the right names then the batch should deliver a ready-made .bin at the and as well.
The easiest way to get back to the one-step batch would be to pick one of your two-step created .nb files, rename it to 82040000-OS.nb and put it to the SOURCE folder.
Batch processing will cut out the pieces and supply the compression for imgfs later - no more two-step.
Last step of the kitchen is basically to joint the new created imgfs with the already ported XIP and ULDR (if present) to a new .nb and then put it to transfer format of the BIN file - transparent blocks with some kB size (not sure if it is64k) and a checksum so that transfer errors can be detected.
Anyway the important part is the creation of the imgfs and especially the correct relocation of modules, something special with the Hurricane and its many modules without reloc section.
You up'ed 2 files, one named "part1.." is there a part 2 also or is this the create_wm6_5?
I guess I will just use the SYS I have for WM61 (from Rose) and WM65 (from Captain) in my Tornado OS Builder kitchen for porting inside OS Builder. This is easier than porting from Batch to OS Builder.
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
sniper304 said:
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Click to expand...
Click to collapse
Why professional - you have touchscreen on Hurricane? Just the 96DPI is nice for more screen estate (smaller top/bottom bars) - but I don't care, really.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
BTW: WM6 Kitchen runs full gear and all options - time to port to WM61 and WM65
in part 1 your kitchen with sys 6.5
in create 6.5 nbwork and rom files(uldr.bin xip bin)
I don't like imgfstonb tool =)
Some times i get bad roms, with bugs, but when i used nbwork, all roms work good.
tobbbie said:
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
Click to expand...
Click to collapse
I found one advantage WM65 over WM61 that maybe useful for some: WMPlayer shows embedded Album Art in WM65 while it does not in WM61. This includes the art display in the sliding panels Media Panel. I use Conduits PocketPlayer for years so never cared about this.
All OS Builder kitchen run well now (6.0, 6.1-Rose and 6.5-Captain). XIP porting was a little inconsistent across these versions but all startup and reboot without flaws.
Still have to cleanup the package sort order - at least in WM6.5 - and see if A2DP would work well (though it is a CPU hog and I would never recommend it).
Release may happen next weekend -> watch out for a dedicated thread then.
Best with the Hurricane cooking is that you will not have to care about ROM size and balancing with storage space on the device in 1 MB steps like on the Tornado - or be limited to fix size like on the Typhoon. The "l" (load) commend will trigger in the SPL a ROM-size matched formatting of the BINFS (in 64k steps, I guess).
Also "good" is that the device still has a RIL v1, so the Radio ROM is smaller (and less capable) then the Tornado Radio. You will hardly note the difference, however will NITZ (Time setting via GSM Network) not work with this RIL.
Even with 8MB Paging Pool (my default) you have free RAM of ~32MB (Sliding Panels Homescreen) or ~34MB with standard Homescreen. You could make the PP even 10-12 MB here and have the device even more "snappy" with several applications in parallel.
tobbbie Thanks for the good work!
I want also clean rom from FWUpdate, because in our phone it's not used, i some time make experiments with some files and when deleted one(i don't remember what file =((( )and it will free about 3 Mb Ram(on startup 35-36MB with sliding panels with weather =)), but i sometimes think, it's unbeliveble, because when i deleted that file, some system pictures don't work(etc. system notification) =(
I think the need to rewrite some system files in order to achieve this = (
No wild deletions, please. FWupdate is removed in the OSB kitchen and only one stub is left in WM6.1+ because otherwise the ROM does not work. Also some other packages are made optional (e.g. SQL mobile) - it so easy making something selectable with OSB (drag + drop), really fun to play with.
The OSB framework has sophisticated tools to analyse the dependencies, so a lot of insight to gain there. If you are curious, download my Tornado OSB Kitchen and do some dry-cooking, the Hurricane will be 98% the same. Also visit the main OSB kitchen thread to get the basic documentation.
The principe:
With [XBmod-Yuki] rom you can send cutom packages like officials to device.
The packages modify the rom itself so they stay in place even after a reset
If you have installed a package and don't want it anymore use the _REMOVE package for it if present or update it by another one.
you can found REMOVE cab here
If you have any error with the WP7 Update Cab Sender
You can use L to retrieve the logs from device
Decompress the Devicelog.cab file you'll find in your logs folder
The important file to check is UpdateValidator.log
At the end of this file you'll find details of the error and which package is in cause.
______________________________________________________________
WP7 Update Cab Sender:
Copy cab/s in "WP7 Update Cab Sender" folder then run the bat.
Use B option to backup the device this can save a lots of time no reflash7004+update process if problem.......
WP7-Update-Cab-Sender
XP User fix for cab sender
I recommend to send cab packages with Backup /b option. specialy for os update.
Backup can be restored with /r option (in 3mn (for empty device) & restore device with all your settings,cabs, sounds ect.
If you have memory error try to remove the bigger cab you have installed(OEM apps,wallpaper)
Update 27/02
-Connection DataBase Update cab (Fix MMS for some provider (free fr))
__________________________________________________________
OS Update packages
Download Link
Be sure to apply update for all languages you have in rom.
if you have problem when press phone icon, change languages you use or verify if an update for your language is out.
__________________________________________________________
Official 22 Languages Cab
http://forum.xda-developers.com/showthread.php?t=1306415
__________________________________________________________
Recommended Cab
XBmod-Yuki-SP1 Rom UPDATE
Apply after 7740 or 8107 Update.
ChangeLog:
-Updated Bldr
-Updated Bsp
-Added new mango oem driver
-New camera Settings
-HTC hub live tile fixed
-Updated HTC Wireless (Wifi,Bluetooth & Ics Fix)
-New tweak:
-Brightness settings
-New Accent colors
-New Audio settings(improved in call volume & global volume)
-Added VS 2010 Fix
-& more...
Download link:
SP1-XBmod-Yuki.cab
SP1 install new HTC Drivers needed by last htc apps like HTC hub but
some apps using old the htc lib doesn't work.(touchxplorer,touchxperience native keyboard.)
You can install those old htc drivers to have those apps working again after SP1 but you will lose htc hub livetile.__________________________________________________________
Operator Cab:
Download link
(MMS settings & operator settings)important package to apply
operatorpkg_*****_**.cab
__________________________________________________________
Customisation Cab
Nokia_notification_sound
(new sound for sms,mail,calendar)
Nokia_wallpapers2
(nokia wallpaper set)
__________________________________________________________
Tweak:
Download link
DEV_XAP_IE_DEPLOYER
(Deploy xap from web with internet explorer(do not hard reset after this one)
DEV_ROOT_REMOVE.cab
(remove root ability)
DEV_UNLOCK.cab
(developer unlock (chevron))
DEV_VOLUME_LOW.cab
(fix HD2 volume to high)
DEV_VOLUME_LOW_REMOVE.cab
DEV_AUDIO_GAIN.cab
(Another audio fix with AC3 & drift correction activated,DO NOT USE WITH DEV_VOLUME_LOW.cab)
DEV_AUDIO_GAIN_REMOVE.cab
DEV_FM_ANTENNA_INTERNAL.cab
(Ability to run fm radio without headset)
DEV_FM_ANTENNA_INTERNAL_REMOVE.cab
DEV_CALLERID_FIX.cab
( fix for Caller ID when receive call)
DEV_CALLERID_FIX_REMOVE.cab
__________________________________________________________
Hardware Key mapping Cab:
Play/Pause multimedia, Skip by pressing twice, Answer a call (when receiving),
End call, (when in call), long press to rapidly call someone by speech input.
Download link
OEM_DEV_KEYBOARD_1.cab
| Play | Search | Start | Back | Power
OEM_DEV_KEYBOARD_2.cab
| Camera | Search | Start | Back | Power
OEM_DEV_KEYBOARD_3.cab
| Camera | Start | Search | Back | Power
OEM_DEV_KEYBOARD_4.cab
| Search | Play | Start | Back | Power
OEM_DEV_KEYBOARD_5.cab
| Start | Play | Search | Back | Power
OEM_DEV_KEYBOARD_REMOVE.cab
| Play | Start | Search | Back | Power (in rom)
__________________________________________________________
Shortcut Cab:
Download link
DEV_SHORTCUT_BLUETOOTH.cab
DEV_SHORTCUT_BLUETOOTH_REMOVE.cab
DEV_SHORTCUT_BRIGHTNESS.cab
DEV_SHORTCUT_BRIGHTNESS_REMOVE.cab
DEV_SHORTCUT_CELLULAR.cab
DEV_SHORTCUT_CELLULAR_REMOVE.cab
DEV_SHORTCUT_FLIGHTMODE.cab
DEV_SHORTCUT_FLIGHTMODE_REMOVE.cab
DEV_SHORTCUT_LOCATION.cab
DEV_SHORTCUT_LOCATION_REMOVE.cab
DEV_SHORTCUT_LOCK.cab
DEV_SHORTCUT_LOCK_REMOVE.cab
DEV_SHORTCUT_SOUND.cab
DEV_SHORTCUT_SOUND_REMOVE.cab
DEV_SHORTCUT_WIFI.cab
DEV_SHORTCUT_WIFI_REMOVE.cab
__________________________________________________________
BootLOGO
-Download link
A logo package can't be removed
So you can only apply a superior version
In rom there is OEM_8x50_LOGO_BACK2THEFUTURE_v444
So Look at the bmp exemples
And apply the logo you want from versions v445, v446 etc
Or if you are not sure you can test logos from versions v445, v446 etc
And after apply logos from versions v454, v455 etc
.
(Rooster 1st splash in tools folder.)
OEM_8x50_LOGO_Rooster100.bmp
OEM_8x50_LOGO_Rooster100_v452.cab
OEM_8x50_LOGO_Rooster100_v462.cab
OEM_8x50_LOGO_*.bmp
OEM_8x50_LOGO_*_v***.cab
__________________________________________________________
Taskbar icon:
DEV_TASKBAR_XBMOD.cab
DEV_TASKBAR_REMOVE.cab
__________________________________________________________
XBmod icon pack + taskbar:
This cab install glass icon & taskbar not the grey color.
Apply DEV_SKIN_XBMOD_v4.cab
DEV_SKIN_REMOVE.cab
SMS icon (press on it to enable new icon 1st time you use this cab)
__________________________________________________________
test rom packages:
Download link
DEV_FILEBROWSER.cab
(HTC test rom file explorer with fat partition support....)
DEV_FILEBROWSER_REMOVE.cab
LoaderVerifierTestCerts.cab
(certificate for test rom apps)
LoaderVerifierTestCerts_REMOVE.cab
SirepForPlatDev.cab
(usefull for platformbuilder debug.....)
SirepForPlatDev_REMOVE.cab
__________________________________________________________
SDCARD & ANDROID RELATED CABS:
Download link
These files change the size and format of the SDcard extrapartition
This partition is used as working part for updates and to save logs
It is usually formated as FAT16 and sized of 200MB
So choose the file which the number of GB you want, send the cab to device and Reset
The first partition will have the new size now and already formated in FAT32
So you can use it as USB key or for Androïd without having to do it manually
Take care if you reset again datas on it will be lost
If you want to revert back to FAT16, 200MB just use DEV_EXTRAPART_REMOVE and reset
This feature is to be used beside DEV_STORAGELOCK.cab
With this tool you can unlock your SDcard
The card will be relocked after each reboot to WP7 what is a security in case of stolen device
So use the tool each time you want to boot to Androïd or use SDcard as USB key.
DEV_STORAGELOCK.cab
this will install unlock tool for your sd card (possibility of dualboot)
DEV_STORAGELOCK_REMOVE.CAB
(remove unlock tool take care sdcard will be relocked at reboot.)
(those need a reset from about screen)
DEV_EXTRAPART_.....
DEV_EXTRAPART_5G.cab
DEV_EXTRAPART_6G.cab
DEV_EXTRAPART_7G.cab
DEV_EXTRAPART_8G.cab
DEV_EXTRAPART_REMOVE.cab
__________________________________________________________
Special thanks to YukiXDA for all work he as done, Da_G,HD2O,Ultrashot,Barin & W.I.N.C.O & Ruzzichella for apps dev.
Original [XBmod-Yuki] Thread here
Create your own WP7 update packages.
The principe:
The goal is to have roms for all WP7 community which can share custom packages without breaking the system updates
A cooker put his certificate in rom so only the cooker sign cabs to have them sendable to the device
This to avoid problems of bad utilisation packages ie to retrieve users informations
But a rom could share multiple developpers certificates, the choice comes to the cooker
And a cooker just have to resign an existing package with his certificate to let it be sendable to his rom
Any developper can make packages he want, when he releases it any cooker can choice to make a package with it
Developers and designers make their customisations they want to device
But they have to never change a system file or it will break the system update process
So sometimes some tricks have to be found to modify some things like the use of .mui filesUpdate Cab Building Process
An update cab is a container for 3 different types of packages.
with ability to replace any files in all part of the rom.(sldr,nk,imgfs)
never need to create a new rom, you can create a cab for what you want (logo,radio & more)
take care update cab modification are not removed by a hardreset.
Canonical
contains the entire contents of the package. It is used for a first-time package install, and if there are any major updates to be issued that would require the complete package.
The file extension is .cab.pkg
Update
contains a binary delta between a package already on the device, and the updated version of that package. if a package change was a simple registry entry - no need to replace all .dll and .exe in that package, just alter the .rgu with a Diff/Patch.
The file extension is .cab.pku
Delete
contain a .dsm file already on the device , and remove all files inside the corresponding package.
The file extension is .cab.pkr
At the root of a package, the .dsm defines the Package structure (all files, registry entries, etc.)
There is a "shadow order" defined in the .dsm as well
- this controls what "priority" .rgu's are compiled together into the device HV.
- a package that shadows another package will override any .rgu entries that shadowed package may contain.
This is important to consider when utilizing .cab.pkgs to obtain your desired end registry.
This shadow order also applies to provxmls inside the package
- a package that shadows another package will override its provxml settings as well.
You can found more technical information in Da_G thread
Beside canonical/update and remove there is other flags in WP7
So use a program which can preserve the flag, dsm builder for ex change them to a bad one
You can find flags for regular(NK/IMGFS) ULDR(SLDR) and Reserved too
If you have no program to make a remove here is a methode:
- Use the default dsm of your package
- Change the version to 0.0.0.0 (but let OS version)
- Remove all files / certificates / dependencies and shadows
- Save the file as that and open it in a hex editor:
- Save you've got it
The delete 40 00 flag is for Regular, 60 ULDR, 70 Reserved
21 00/21 04 For update ULDR, 22 00/22 04 Canonical ULDR
01 00/01 04 For Update regular, 02 00/02 04 canonical regular
You can use the tool DSM Flag Editor to do this.(thx Ruzzichella)
{
"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"
}
Updates packages need diff files and we need tools for that.
but we can send dll to replace.....
when you make a dsm keep the oem certificate AND add your own.
You can Build your own cab package with WP7 Update Cab Builder
Developers, if you want try this process send me your cab and i will sign it for you to try on the rom.
Cab building process need your personal certificate (.pfx) in tools folder.
you can create your certificate with signcode & convert it to pfx with pvk2pfx.
download link:certificate-tools
and you need to build a rom with this certificate cooked in.(DefaultCerts.dat & MsDefaultCerts.dat )
IMPORTANT:
Never send a cab without your certficate or you won't be able to remove or modify the package
And you won't be able to provide a removal to users
How to Unlock WP7 SDCARD Using Leo.
After use XBmod-Yuki Rom 2.0 or 2.1 SDcard is Encrypted/Locked like a real WP7 device.
Lots of users seem to have problem with this!
so here the process.
Insert your locked sdcard in the device.
flash Xbmod-yuki rom 2.1 & directly install DEV_STORAGELOCK.cab at 1st boot.
after reboot run the Unlock tool.
press ok then at reboot remove the battery or boot on magldr & flash your new rom.
(Do not let the device reboot WP7 or this will relock the card.)
You can also unlock card on a real WP7 device using attached packages.
package_STORAGELOCK
XBmod, for partion the SDcard:
should install DEV_STORAGELOCK.cab, unlock then install partion cab (DEV_EXTRAPART_7G.cab), after that reset the phone!
thank you
edit: confirm, it's working!
This cab install glass icon & taskbar not the grey color.
Xbmod plleeeease give us grey, I love the grey colour scheme.
I live in hope.
Thanks
Strop said:
Xbmod plleeeease give us grey, I love the grey colour scheme.
I live in hope.
Thanks
Click to expand...
Click to collapse
Hi
you can change colors with advanced config 1.3.0.0.
xboxmod said:
Hi
you can change colors with advanced config 1.3.0.0.
Click to expand...
Click to collapse
Thank you for prompt response.
Strop
xboxmod said:
Shortcut Cab:
Download link
DEV_SHORTCUT_SAP.cab (Shortcut Internet share)
DEV_SHORTCUT_SAP_REMOVE.cab
Click to expand...
Click to collapse
Hello Guys,
Is there any improvement about the Wifi Internet Sharing?
I was reallly excited at the beginning but disapointed after installing because it is not working (only a menu). Thus, i've made a little search over holly google and found this article: http://forum.xda-developers.com/showthread.php?t=1233612
But it seems like still not working on HTC because of the lack of drivers also carrier block.
So, will be appricated if you have any news regarding this. (I have spent my summer without internet because of this missing function and do not want to spent another.)
All the bests.
v-numbers meaning?
Hello and thank you for your great work!
What did you mean with the various v-numbers like v449, v459 and so on in the boot logo section..
Regards,
Oliver
oliverweidel said:
Hello and thank you for your great work!
What did you mean with the various v-numbers like v449, v459 and so on in the boot logo section..
Regards,
Oliver
Click to expand...
Click to collapse
The rom as v444 build in,so if you want to change it, you need to use an higher version 449,459.....
Whwen I try to apply 7403-7661.rar I get the following error in the sender window 8018004D.
It seems to be too large 205 meg.
Am I missing something?
When im trying to apply the Swedish language cab, im getting a low memory error.....any help please??
bigx86 said:
When im trying to apply the Swedish language cab, im getting a low memory error.....any help please??
Click to expand...
Click to collapse
Hi
try to install only languages you need like swedish & english 0409 for security.
if always a low memory error try to hard reset before install.
If someone wanna add some useful functions to the flag editor pm me...
oh man, a new world...
Sdcard & android related cabs:
After setting up dual booting using 7gb .cab, I tried to (r)estore from an earlier (b)ackup and send using cab sender and it failed due to different sized sd.
Just a heads up for those expecting to be able to use restore for anything.
I would love to be able to create a CAB with that sets my MS Activation Code so I don't have to manually enter it whenever I need to hard reset. A simple tool to create one after I put my code it would be great. Any takers?
MagpieMDP said:
I would love to be able to create a CAB with that sets my MS Activation Code so I don't have to manually enter it whenever I need to hard reset. A simple tool to create one after I put my code it would be great. Any takers?
Click to expand...
Click to collapse
This +10
3 month Zune Pass to the person that does this.
EDIT: Payed to xboxmod, thanks!
First, thanks for all your work fo us.
I had a problem, when a make a call or pick up a call,
the handset vol is low, it's there some cabs can help with me?
Thanks.
First, thanks for all your work fo us.
I had a problem when send unlock.cab to my fone.
╔════════════════════════════════════════════════════════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠════════════════════════════════════════════════════════════════════╝
■
╠══════» S ·(S)end Cabs to device
■
╠══════» B ·Send Cabs to device with (B)ackup
■
╠══════» R ·(R)estore device backup
■
╠══════» L ·Read last Update (L)ogs from device
■
╚══> Your choice: S
╔══════» Creating list of cabs
■
■
╠══════» Updating device
■
UpdateWP version 4.8.2345.0
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#6&1c647433&0&0000#{ca3d7387-f67
b-11da-bbec-8000600fe800}
SN: bb09d480 - 698b002e - 124b08ab - 48616498
Name: HTC HD2
KITLName: QSD8XXX01196189
Manufacturer: HTC
ModelId: 4
Model: HD2
MobileOperator: 000-00
Version: 07.10.07720.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.03 seconds
Checking system requirements: Completed in 0.03 seconds
Downloading updates: Completed in 2.28 seconds
Checking system requirements: Completed in 0.02 seconds
Transferring updates: Completed in 0.15 seconds
Preparing to install: Completed in 4.08 seconds
Restarting your phone: Completed in 53.41 seconds
Installing updates: Completed in 14.34 seconds
Checking your phone's status: Completed in 0.01 seconds
Restarting your phone: Completed in 55.24 seconds
Completing updates: Completed in 4.26 seconds
Error:
Update device bb09d480 - 698b002e - 124b08ab - 48616498 Complete with error code
: 80180011, error message: IU (Image Update) installation failed on phone: None
of the packages in the update are applicable.
■
╚══════» Done
Press any key to continue . . .