Related
Have any of you guys figured out how to fix a keyboard layout without having to recook a rom with the proper keybddr.dll file?
I have a T-mobile Wing, and we have the problem over in the herald forum where most of the best Rom's are made for the P4350 Herald... and the main problem is the keyboard layout being different.
Since that cook doesn't have an actual TMO Wing, he is building Rom's blind when he tries to port them over to the Wing from the P4350... so I dunno if there may be any other way of fixing this issue perhaps thru the registry or some alternative method.
Thanks.
bump
-------
It depends of what you have to change. if it is an entry in the registry, it is easy to do it manually or with a .reg file.
If you want to update a rom dll you can create a cab that will install them over the rom ones.
Merci mon pote!
So making a Cab will overwrite files that are "inaccessible". To my understanding, the keybddr.dll file is inside the Windows folder. I read some guy who deleted the keybddr.dll file for a herald in his windows folder and replaced it with the one for the Wing, and he said he Wing became completely unresponsive.
Would this problem occur if a cab file was made?
I found the file in \Windows\keybddr.dll, so could it be as simple as making a cab to delete the current one and write the new one followed by a soft reset?
Would you by any chance be able to make such a cab if I gave you the correct keybddr.dll file?
It the file is in the rom, you can not delete it, except by cooking a new rom. But I think that you can overwrite it with a cab, because I have some cab from O2 that overwrite some files of my rom.
The advantage of cab over cooking. if is easier, you can undo it, and if your system hang after installation you can do a hard reset.
I have never created a cab. I think that other people can help you better than me, or you can try by yourself. You will find tools. Probably I could help you in few months because it is something I would like to learn to do.
duprade said:
Have any of you guys figured out how to fix a keyboard layout without having to recook a rom with the proper keybddr.dll file?
I have a T-mobile Wing, and we have the problem over in the herald forum where most of the best Rom's are made for the P4350 Herald... and the main problem is the keyboard layout being different.
Since that cook doesn't have an actual TMO Wing, he is building Rom's blind when he tries to port them over to the Wing from the P4350... so I dunno if there may be any other way of fixing this issue perhaps thru the registry or some alternative method.
Thanks.
Click to expand...
Click to collapse
You dont really say what you want to change, but have you had a look at the symXXXX.txt (xxxx being four digits depending on what language you are using) file in \Windows? It contains the whole character set and configures what button corresponds to what character (each line is a button, the list of characters on each line is what you get when your press that button then symbol). It is a read only file in the rom that has to be exactly 496 bytes (at least on my Hermes) to work so my recommendation is to copy it to your computer, edit the file in notepad, then move it back to your device using Resco Explorer.
Btw, you can only change alphanumeric characters with this. If you have to move the Start Menu button you're out of luck.
The keybddr.dll file in the HERALD is different than that of the WING...
The better Rom's made that are compatible with the Wing, are actually Herald Roms, but there are some differences between the devices, and the most annoying issue is the keyboard problem... so I am trying to find a way to simply change the keybddr.dll file ... without having to actually recook the actual rom.
This is what "misha" posted in the Herald forum
misha said:
I have been reading many threads at this forum about the WING issue with keyboard mapping for the ALT function symbols. It looks like several rows of key mappings are different between herald and wing.
herald
(PIC)
http://content.modaco.net/nedge2k/images/15-Mar-2007_02-terra-main.jpg
ALT function HERALD:
1st row: @ ! ? / # 1 2 3 ( )
2nd row: _ (some char) % - + 4 5 6 = ENT
3rd row: Cap ‘ & : * 7 8 9 PageUp Enter
4th row: ALT ; CommMan Sym Space 0 , PageDown Launch-Button
wing
(PIC)
http://www.tracyandmatt.co.uk/blogs/media/T-Mobile_wing.jpg
ALT function WING:
1st row: ( ) = / # 1 2 3 ! ?
2nd row: _ “ % - + 4 5 6 @ Del
3rd row: Cap ‘ & : * 7 8 9 PageUp Enter
4th row: ALT ; CommMan Sym Space 0 , PageDown IE-launch
I am using the v4.12.07.10 PDAVIET Touch Flo Pro
After digging around I see that there is this file (\Windows\ sym.0409.txt
) that contains the symbols in the following format:
aàáâäåąãăæ
AÀÁÂÄÅĄÃĂÆ
cçćč©
CÇĆČ©
dð
DÐ
eèéêëę
EÈÉÊËĘ
iìíîï
IÌÍÎÏ
lł
LŁ
nñ
NÑ
oòóôõöőøœ
OÒÓÔÕÖŐØŒ
pþ¶
Pþ¶
r®
R®
sşšß
SŞŠß
tţ
TŢ
uùúûüű
UÙÚÛÜŰ
yý
YÝ
zźż
ZŹŻ
$€£¥
/\|
"'«»
([{<«
)]}>»
+±&-_
!¡?¿
.:,;
*#
@~
%^
I wonder if changing around the symbols that are miss mapped would fix the keyboard issue between wing and herald ROM……
One problem, I can not modify this file because under properties in (Total Commander) it stated that the file is Read Only and it is in ROM.
Any ideas how to modify this file?
Click to expand...
Click to collapse
Hi.
can some one upload User OEM for the new WM6 Kitchen for these programs..
1. LG Menu (LG Prada Today Plugin)
2. Pocket CM 0.19
3. Vicsoft UI Tweaker
4. MT Software Today Agenda V1.1
5. Pocket CM Keyboard 0.13
6. FtouchFlo 1.4.1
I wanna include these programs into my kitchen for future flashing...
thanks
if u can send me the download link for all of them i will turn them to OEM packages for u
hi thanks.. here they are
Mod Edit: Pocket CM links removed per Pocket CM website instruction:
"Is it free?
Yes it is free, for your personal use only (in short: you can use for anything you want, you can't just redistribute it... however you can point anybody to this website). Even more if you want it to stay free, please make donation. Anything is appreciated and will encourage me to continue the development of it as a freeware. To make a donation please use:
Can I post this application to my website?
If you want to post information about this application, please reference this website. Do not provide direct download link.
Also because feedback and comments is important to me, please drop me a mail (qpouplard // gmail.com).
If you want to publish this application on your site, please contact me first. "
So, go here to get it:
http://www.pocketcm.com/
here's the lg plugin
http://forum.ppcgeeks.com/showthread.php?t=14326
alright then..will start making them now
okay.. thanks
Lets keep this thread open for any one who needs to get help on OEMs.. rather than waiting for the new OEM package to come out..
thanks for your help
pocketCM 0.19
download here: http://pocketcm.com/phorum/read.php?18,8733
2 xda2jj: read first act then - for next time and dont change posts w/o notifying "poster". At first i posted direct dwn, but then i changed it to Quentin's site.
PCM
today agenda
PCM keyboard
touchflo
these are in the OEM.rar for the 6700 helmi kitchen. Not sure what else you are needing.
I know they are already in the kitchen.. But i want the updated versions.. unless there is already an updated OEM package that i dont know about.. the OEM Package I have was released 12-17-2007..
Well, I can tell you this much. The BuildOS that is in the works now will actually pull updated OEMs from the web. So, I guess you could learn to update OEMs which really isnt that hard once they are setup or hang tight for the new BuildOS.
Holy Crap!
That's great news!
The new builld os is capable of accessing the web to get OEM updates?.. thats Friggin awesome!
Would it be able to look for new OEMs as well as Updating current OEMs?
I can't wait.. can you give us a clue on when this new BuildOS would be available?
can any one attach the new BuildOS here please...the oems will take time as im running Vsita and ill have to setup my lappy as it has vista..sorry
Here are some of my OEM packages
http://forum.xda-developers.com/showthread.php?t=333359
Hi guys, Not so sure Tene wants his cabs posting, maybe check.
Have someone the program "Notes" from WM6 as a cab. file ?
i doubt it - it's in OEMapps(i think) with everything else, and to take only one app and properly check all Reg.Keys for it..... Not worthy even to think about it
Here it is. credit to Dutty Throy.
phsnake said:
i doubt it - it's in OEMapps(i think) with everything else, and to take only one app and properly check all Reg.Keys for it..... Not worthy even to think about it
Click to expand...
Click to collapse
Anyone with cab files can now build their own packages - thanks to Ervius! And Alex!
This attached tool is part of Alex's Kaiser Kitchen but it'll create OEM packages that can be used across all kitchens...
ather90 said:
can any one attach the new BuildOS here please...the oems will take time as im running Vsita and ill have to setup my lappy as it has vista..sorry
Click to expand...
Click to collapse
Moe5508 said:
Anyone with cab files can now build their own packages - thanks to Ervius! And Alex!
This attached tool is part of Alex's Kaiser Kitchen but it'll create OEM packages that can be used across all kitchens...
Click to expand...
Click to collapse
something is wrong with your file it will not extract. its only 26 k is that possible? well let me know as I have several programs I want to turn into OEM and most of the other programs Ive tried dont work.
hey thanx for this..its works on vista ultimate..but i cant make it open CAB files..it only re-makes prev built packages
EDIT :-
Got it to work..it uses a CAB manager to analyse cab files..its available by the name MSCEInf
the package creater looks for MSCEInfen if the settings are in english or it will look for MSCEInfit if the language is in italian
im attaching the required file..its by default named to MSCEInfen
Here are the Orignal Instruction by the developer :
Converting Cabs to Packages with Ervius Package Creator
If you haven't read someone elses guide before and tried their method of making an OEM package, consider yourself lucky. The manual processes described by some, going through the lengthly process of extracting a CAB file, converting SETUP.XML to registry formats, creating an INITFLASHFILES.TXT manually and so forth takes A LOOONG TIME and I applaud all of those OEM Package builders who used the old methods, because those methods for creating an OEM package was truly an error prone exercise in futility and patience!!!
The method I describe below is semi-automated and uses Ervius Package Creator & Benthon's MSCEInf.exe. Everyone should thank Ervius & BenThon, because we now can convert a cab to an OEM package in a matter of minutes instead of hours...
Setting up & running for the first time
You can skip this entire step if you're using the Kaiser ROM Kitchen w/ Alex's latest updates, as I've included all the files for you. Go ahead and select 'p' from the ROM Kitchen menu and then jump down to 'Steps to convert cab to OEM package'.
All of the files below, plus the cab or the OEM package folder must be in a folder on your C: drive! If not, you will have problems running this program. It's a limitation created by Ervius, not me...
Download and uncompress BenThon's MSCEInf.exe and Ervius Package Creator to the same directory
Rename MSCEInf.exe to MSCEInfen.exe
Run packages creator 5 4.exe. When running for the first time, you will see the following two error messages:
"Error reading Settings file. I delete it!!!" - Click on OK.
"Unhandled exception has occurred in your application..." - Click Continue.
Check the following boxes (settings will be saved in settings.ini for future execution)
Select 'ENG' to change to English.
Check 'Prefix files for duplicate in package subfolders'
Check 'Enable options'
Steps to convert cab to OEM package
Click on 'Open CAB file' and select a cab file to convert.
Click on the 7th icon from the left, 'Extract CAB files with original names in a folder'.
When the folder selection menu comes up, click on 'OK' regardless of the location shown. It will create a folder named after the cab in the same directory where the cab is located.
It will seem like nothing happened, but be assured that the files have been extracted. Click on the X to close the window.
If you really forgot to click on 'extract' and nothing was extracted, an error message will appear - "U've cancelled creating package from cab analyzer... exit!"
The next window that appears, known as the 'initflashfiles tab' is for executable and help file links. Select which files you want your links and the folders to place them. Select and apply for each link and when finished, click done to proceed.
You're now back to the main menu. The UUID for DSM and RGU has been pre-generated. You have the option of going back to 'open initflashfiles tab', creating option.xml with a group, or completing the package.
Once you have chosen the appropriate options.xml category, click on 'Complete Package.
Your cab has now been converted to an OEM package in a subdirectory where the original cab resided.
Click to expand...
Click to collapse
This is only OS + ExtROM, does not include radio nor splashes nor SPL.
This is basically the same OS+ExtROM as found on Sprint's latest official ROM 3.56, MINUS all that Sprint bloatware (OnDemand, AudibleAir, Sprint Music, etc.) occupying both OS and ExtROM space. I also removed Sprint Navigation and Sprint TV from the ROM and ExtROM (respectively) because I want more control on how Sprint programs are installed (into the device vs into SD card); I have the separate CAB installers for Sprint Navigation (TeleNav) and Sprint TV so I can install them the way I want. I also removed the ringtones from the ROM because I don't like Windows Mobile's approach to copying ringtones from ROM (\Windows) to internal memory (\Windows\Rings) which effectively results in unnecessary file duplication within device memory, but I have stored the removed ringtones into an SD card so I can later add them either to \Windows\Rings (with no wasted copies in ROM) or to \Storage Card\Windows\Rings.
The amount of memory I gained this way was used to (1) update the core fonts (Courier New, Tahoma) to the latest versions found on Windows Vista (the versions found on the original ROM date way back to 1999, even in WM6.1! plus WM only includes regular-face Courier New, I had to add bold/italic/bold-italic versions), (2) add smartphone fonts Nina and Segoe Condensed, (3) add the Windows Vista version of Japanese font TTC MS Gothic/MS PGothic/MS UI Gothic (the AC3 compressed version is still outdated, version goes back to 1999 ), (4) replace the USA wince.nls with the Japanese wince.nls (which includes all charsets found on USA wince.nls + adds Shift-JIS, JIS, and EUC-JP), (5) add the WM6 Japanese IME files, (6) update the SymbolPad's config file to allow inputting almost all the Pan-Euro characters found in Vista's Tahoma and all math symbols included in MS Gothic, (7) add PQzII with some customized bitmaps so you can map CTRL, ALT, and IME to any buttons you want, (8) add PHM RegEdit, Notepad and a few other PPC PowerToys (I also added MADE because it is more powerful than Notepad), (9) add KT_Capt (print screen!), and (10) add FontOnStorage (yes, a very old program that dates back to WinCE 3.0, but still works on WM6.1 as long as the fonts in your SD card don't conflict with those already in internal memory). I preserved Adobe Reader LE, the Camera app, and IA Zip.
I modified the registry entries to (1) enable ClearType and menu animations (but disabled HTC's EnlargeMenu because it doesn't play nice with menu animation), (2) set internet cache/cookies/history to load onto SD card, (3) display both date and time (and AM/PM) in title bar, (4) enable font linking so Tahoma can work together with MS UI Gothic to display full Latin/Greek/Cyrillic/Japanese, (5) enable and configure the Japanese IMEs, and (6) set the new black Vista-like HTC theme as the default rather than WM6.1's solid-green default theme or Sprint's annoyingly-bright orange theme (although both themes are still included if you want to use them).
I used NBHExtract on the original stock ROM to extract the NB files, then NBSplit/ImgfsFromNB/ImgfsToDump to dump the OS, then PKGTool to convert dump to packages, then the usual ROM-kitchen procedures (remove unwanted files, add wanted files/packages with some help from CAB Extractor and InitFlashFiles Generator, modify RGU entries, regenerate DSM files with BuildDSM, modify packages.sof with XVI32, and dump XIP with RomMaster), then BuildOS to "bring packages to a boil" into new dump, then ImgfsFromDump/ImgfsToNB/NBMerge to "simmer" new OS.nb, then HTC Extended ROM Editor to remove the Sprint bloatware from ExtROM.nb, then finally NBHGen to "bake" both OS.nb and ExtROM.nb into the new ROM.
As I said above, the radio and splash image NBs are not included in this 82.2-MB ROM; adding the radio and splashes, the ROM grows to 94.1 MB, which is still 2.5 MB smaller than the stock ROM (even after adding that big, uncompressed Japanese font MS Gothic which is about 8 MB, but that's because the font itself is smaller than the whole combination of OnDemand/AudibleAir/SprintMusic/TeleNav/ringtones).
I thank pof/TheBlasphemer, mamaich/Tadzio, bepe, AnDim, and bot for all the executables they made that made my ROM cooking possible.
For those Sprint Mogul owners who don't want outdated fonts, annoying bloatware, or duplicated-in-device ringtones, my ROM can be downloaded via RapidShare:
http://rapidshare.com/files/144942116/Sprint_Mogul_3.56_OS_ExtROM_only_by_Unicode787Plus.exe.html
congrats! I just cooked my first couple roms a few nights ago, and one for my girlfriends titan too. its fun and addictive!
Sprint Navigation (TeleNav) and Sprint TV installer CABs
For those who download and flash my Sprint Mogul ROM and still want TeleNav and Sprint TV in their Moguls, they're attached to this message. Just copy them to an SD card and install them, easy! (You can install them either into internal memory or into SD, makes no difference!)
Will later post the ringtones I removed from my ROM.
Sprint Mogul ringtones
Ringtones removed from my ROM are attached to this message. For some reason I had to split them into two different ZIP files because xda-developers constantly refused my single 2.18-MB ZIP (even after using Legacy ZIP 2.0 compression method)
MMS
There is no way to add MMS (PIC/VIDEO)? I'm not using the 8525, i have a new MOGUL (SPRINT)
Sorry, I don't use MMS at all (and VERY VERY RARELY use SMS), so I don't know how to add MMS support to Mogul. For that you'll have to ask either mamaich or bepe in either this forum or ppcgeeks.
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
mrfordwrench said:
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
Click to expand...
Click to collapse
Yes you can flash back the original ROM - by redownloading it from the HTC website. Same procedure if you try any other custom ROM - like mamaich's or NoChem's kitchens...
Battery icon
mrfordwrench said:
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
Click to expand...
Click to collapse
Read my private message - that explains the purpose of PQzII.
As for the battery icon, I don't know. If you disable date/clock display on the title bar (either by doing so from Settings or by messing up with the Registry), then you'll see a useless battery icon instead of the clock. HTC's own custom battery indicator (shows only on Today screen) is a bit more accurate, but not as accurate as Palm Treo's own custom title-bar battery icon. If I could somehow copy Palm's battery-icon code (cannot do so directly from the phone - it seems to be copy-protected, and I don't have access to a Treo WinMo kitchen) and transplant it into my next Mogul ROM, then I would be happy.
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Cooking ROM
tarun_kabra said:
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Click to expand...
Click to collapse
Once you have generated imgfs.bin, you must dump it with a tool named ImgfsToDump.exe. It will create a folder containing the whole dumped image. Then you must use another tool, PKGTool.exe, to unpackage the dump folder into its constituent package subfolders (called packages). Now it's just a matter of removing unneeded files (be careful here, you don't want to remove files that are needed by WinMo itself) and updating outdated fonts (Courier New and Tahoma) with newer versions (you will first need to find on which pacakges they are located, then copy the new versions onto those same package folders) and, optionally, adding new fonts, input methods, or other programs onto the Custom subfolder. You will also need to edit some RGU registry entries (each package may have one) in order to activate some features or input methods. Then you will need to run another tool, BuildDSM.exe, to reprocess the edited packages. Then it's time to build a new dump from the new and edited packages: you will need to download BuildOS for this. BuildOS has a tool called BuildOS.exe, but running such a tool is tricky since you can't just double-click on it (it will crash), you must run it from some batch file located just outside the folder containing the tool; BuildOS.exe will convert the packages back into a new dump. Then it's just the matter of reconverting the dump into a new Imgfs.bin (with ImgfsFromDump.exe), inserting Imgfs.bin into a new NB file (the ROM itself) with ImgfsToNb.exe, then repackaging the NB file into the final NBH ROM with NBMerge.exe.
This is roughly all I can remember. You can optionally seek help from other fellow users, since I learned my technique from one or several of them: mamaich, no2chem, maybe Asukal...
Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar
Failure with build ROM
Hi Blackdragon_860,
many thanks for your effort - but unfortunately I must say that I have yet to find a
working dumptool for bepe's kitchen that fits the average user.
Using your toolset (put in the root of my drive) seems to create the structure just
fine but whenever I use build_rom.bat (from your kitchen or from bepes) it just gives
me an errormessage from platformrebuilder.exe:
Collecting standard packages and initializing hives...
ERROR! (errorlevel: -1073740777)
please press any key ...
I tried with the new HTC 1.93 GER ROM btw.
Any thoughts on that ?
/mst
P.S. why does yor tool need another location than platformrebuilder that makes it
even more difficult?
Thx for this, great work! one issue: I have made my Diamond roms with Surface Kitchen so far. I give this a go and I take one of my own roms and dump it and rebuilt it..I made no changes every thing went fine no errors and the new OS.nbh was created. Then I flash it but it dont boot, just the splash screen came up? the txt which allways come up normally where you seen the radio and protocol version didnt shown at all..How come?? What did I miss??
OK now I test a stock .nbh file and now the rom boot, but my finnish xt9 was gone I got just the ordinary keyboard in the rom, and the phone canvas is missing too in the rom, random acsess is gone
I used the 2.03 nbh
i use it for every "OFFICIAL" & "ORIGINAL" Rom
and it works greate..
i am working on a update,but for now it works.
greets
released V2
works awesome! THX
Great job! Perfect THX very much
thx for yours feedbacks..
I met an error like this:
Error: 0x80000009
'boot.rgu' does not exist in th specified paths!
Error! (errorlevel:1)
does this means the rom protected?
yes, when the rom is not protect or original it works 100%
Blackdragon_860 said:
Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar
Click to expand...
Click to collapse
dude i tried to extract wm6.5 rom with this. it did not extract ROM folder so i had to manually copy it. after that when i run the rom builder i get an error that boot.rgu is not placed in right paths. i think its supposed to be in XIP and it is there only. then why this problem?
Welcome to my tutorial in cooking for the TG01.
I shall no longer be updating this thread, so please feel free to post and make any contribution you see fit.
This is meant to be a very simple, plain English guide to cooking.
With this in mind i will not be showing you how to port a new sys/xip or any of the more advanced features like sense
lets just see if we can dump, modify, build then flash a working, booting ROM for now.
This tutorial is only what i have learnt whilst beginning to cook my own ROM, so if you find a mistake or have something to offer feel free to post
If you have a question that your going to post, please please search the forum first, i learnt a lot of what i know from threads that have nothing to do with the TG01 or even the type of kitchen we're using. So as the rules state - Search before posting, Thank you.
Modifying the ROM of a Windows Mobile is dangerous to your devices health. If you mess it up it can be fatal.
The information contained in this tutorial is only as far as i am aware. Don't blame me if you brick it.
Having said that, i have never had a problem the short pin method couldn't fix.
You will need the attached .zip file, it contains the kitchen and associated applications.
In this tutorial i am using L3V5Ys kitchen, cab converter by Jason8, Package converter by Total Fire and Package Creator by Ervius.
So thanks to them and everyone in the XDA community for making this kind of thing possible.
1. Dump a ROM
1.1. Download the ROM you wish to modify. I suggest Miros miROM4, its clean and fast without any clutter.
1.2. Extract the ROM and place the resulting .tsw file in the BASE folder in the kitchen. Then rename it "TG01WP_5005000176.tsw"
1.3. Run dump.bat and wait for it to finish, this could take a little time depending on you PC, it may be worth making a tea as it seems to take longer if you watch it.
1.4. You should now have some new folders in your kitchen, for now the only one were interested in is SYS.
2. Modify a ROM (Removal of packages)
2.1 Open your kitchen folder then open the SYS folder,
2.2 You should now be faced with a window with lots of folders in it. The folders are called packages.
2.3 Delete the package Entertainment and its associated packages (Entertainment, Entertainment_DPI_192, Entertainment_Lang_0409 and Entertainment_Lang_0409_DPI_192)
2.4 This has effectively deleted the games that ship with your chosen ROM,
2. Modify a ROM (Adding packages)
2.1 Open your kitchen folder then open the SYS folder.
2.2 Copy the package from its source to the SYS folder. Remember that for this kitchen it must be an OEM\old type package (see post #4)
2.3 Thats it, you added software to your custom ROM.
2. Modify a ROM (modify existing package)
2.1 Open your kitchen folder then open the SYS folder.
2.2 Open the folder titled "Redist_dpi_192_resh_480_resv_800"
2.3 Replace welcomehead.192.png with the one in the downloaded zip.
2.4 That's it, when you boot your new ROM it should show the new welcome screen.
3. Building and flashing a ROM
3.1 Run "2. build no XIP port_no auto.bat" (this is the original build.bat, modified by myself to skip the port xip and BuildOS/auto parts)
3.2 When the cmd prompt opens press any key
3.3 When BuildOS opens check the packages you wish to install then click the green arrow in the top left.
3.4 When BuildOS has finished, close it and the cmd window will carry on opening and closing other programs as it goes. You do not need to touch any thing till it has finished and it asks you to hit enter.
3.5 Assuming you pressed enter when it asked, the cmd window will have now closed.
3.6 Go into your kitchen folder and you should have a new file called "TG01WP_00.tsw" This is your ROM.
3.7 Copy "TG01WP_00.tsw" to a folder called PRG on your storage card (if its not there then create it) and then run SDDL+ or use the short pin method to flash it.
3.8 That should be it, you should now have the rom you started with but minus solitaire.
The Kitchen:
In your "Kitchen" you will find some folders and some files. They all relate to either the ROM ityself,
or the tools used to edit/dump/create the ROM.
BASE - This is the folder in which you put the rom you are dumping
OEM - This is the folder where the Toshiba part of the ROM would be if it was an official Rom that was being dumped,
however when dumping a cooked ROM this folder will be empty as a cooked ROM cannot be dumped correctly by the tools available
and all packages are put in the SYS folder. This will not affect the output, and the OEM packages can be left in the sys folder.
If you dump a cooked ROM you will need to create the OEM folder as BuildOS panics without it, even if its empty it needs to be there.
SYS - This folder contains the dumped ROM separated into packages
ROM - This folder contains the xip, boot.rgu and boot.hv. For this tutorial we won't be working with anything here.
TOOLS - This is where the exe's are that make up the kitchen, you don't need to touch these, the .bat files do it all for you.
Temp - This is the kitchens working folder, you don't need to go here unless there are problems building the ROM but that is beyond the scope of this tutorial.
Packages: (there are 2 types, EXT and OEM, our kitchen can only handle OEM so thats what i'll be discusing)
Each package contains an element of the ROM. For example the BROWSING package contains the parts of the ROM required for internet browsing.
For a package to be usable it requires certain things
Required:
.dsm file - This is to complicated for the scope of this tut so for now just accept that this file is necessary and should never be deleted. All dsms must have a unique name.
That is all a package needs to be a package, though without any files in it won't actually do anything.
Optional:
.rgu file - This file contains the reg entries for the package in question and its name will be the same as the .dsm file in your package.
initflashfiles.txt / initflashfiles.dat - This file tells the PPC where to put the files that are within the package, ie. a short cut to a program in the start menu.
NOTE without an initflashfiles.txt all items within the package will go to the Windows folder.
option.xml - Holds information relevant to the package
The files you wish to install, without them its pretty pointless.
Packages often have other packages associated to them, for example the Entertainment package also has Entertainment_DPI192, Entertainment_Lang_0409 and Entertainment_Lang_0409_DPI_192.
Where Entertainment is the package, Entertainment_DPI_192 has the files specifically for our screen size, Entertainment_Lang_0409 has the files for our language (0409 is WWE)
and Entertainment_Lang_0409_DPI_192 has files that are for our lang and our screen size.
Modifying a .rgu file:
.rgu files contain registry information for the package they are in. If you wish to modify this data then you can do so with notepad, though i recommend downloading Notepad2. If you open a .rgu file and don't understand what's in it then you need to go learn about windows registry editing first. I am assuming that if you are looking at building a custom ROM you already know about reg editing.
CAB Converter:
This program is used to convert a .cab file into a package to be cooked into a ROM
1.Open CAB_Converter.exe
2.Click "add a cab" and browse to your cab or drag and drop your cab into the window
3.Click on the text representing your cab at the top of the window so its selected.
4.Click CAB->OEM, and wait till its finished. Should only be a few seconds.
5.Your package will be in the CAB Converter folder in the converted OEM folder
Package Converter:
Our kitchen only supports OEM\Old type packages, so what if we want to use an EXT\Visual type package? Well Total Fire kindly made and distributed a tool that converts from one to another.
The program is fairly self explanatory but i'll quickly cover converting from a visual to an old package.
1.Open the converter, then click "select" where the greyed text say package,
2.Browse to and open your visual package.
3.click "Convert VTO", now wait till you see "Conversion Complete".
4.Your now usable package will be in the same directory as the visual package with the text "PACKAGE TF" added to the title.
Package Builder:
If you wish to create your own packages, this is the tool to do it.
1.Create a folder named whatever you want your package to be named
2.Add to it the files you want
3.Add to it a .reg file if required
4.Open package Creator, in the bottom right you can choose ITA or ENG.
5.Click open package and browse to the folder you created.
6.Now the initflashes.txt options page appears, here you can select the .exes in your package and choose where to create short cuts. You will need to click apply on each one.
7.Now click complete package.
8.The creator will now create a .dsm file, a .rgu file with your .reg file settings in, an initflases.txt file and an option.xml file within the folder turning it into a package.
9.This package can now be used in your kitchen.
Reserved...
Reserved....
leeston2379 said:
CAB Converter:
This program is used to convert a .cab file into a package to be cooked into a ROM
1.Open CAB_Converter.exe
2.Click "add a cab" and browse to your cab or drag and drop your cab into the window
3.Click on the text representing your cab at the top of the window so its selected.
4.Click CAB->OEM, and wait till its finished. Should only be a few seconds.
5.Your package will be in the CAB Converter folder in the converted OEM folder
Click to expand...
Click to collapse
Thanks for a lovely tutorial! Makes sense!
I am continuously facing this attached error! Any ideas how to solve this! :s
Wich cab do you use ?
What is your Operating System ?
EVEALEX62 said:
Wich cab do you use ?
What is your Operating System ?
Click to expand...
Click to collapse
I used Opera.cab (opera 10) and with windows 7
EVEALEX62 said:
Wich cab do you use ?
What is your Operating System ?
Click to expand...
Click to collapse
chek property of your folder in c: or test to reinstall this program with administrator right (clic right).
Can you send me MP with your cab, I'll test tomorow morning
Have a good night
drupad2drupad said:
Thanks for a lovely tutorial! Makes sense!
I am continuously facing this attached error! Any ideas how to solve this! :s
Click to expand...
Click to collapse
Its better to grab hold of one of the existing opera packages on the forum, I never successfully converted it to a working package. Just seemed to be the opera cab as i have no problems with any other. I think ninjaduck does a nice version with flash and the like already in.
I never saw that particular error myself though. Sorry I can't be more help.
So long and thanks for all the fish.
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.
leeston2379 said:
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.
Click to expand...
Click to collapse
i have one samsung galaxy tab and next week i get also one HTC Desire HD of my company. Android is really good- but more fun i have with WinMo.
today i have get my second "new" tg01!
you were ever friendly and helpful. thank you for your activity and cooking for our tg01 community.
i wish you all best, good luck and cheers, miro
leeston2379 said:
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.
Click to expand...
Click to collapse
Hi Lee!
TG01 community will miss your contributions! In case your retired TG01 lures you back to development, I will keep my eyes peeled. I hope you like your new android, but in case, Winmo is missed (I wish!), do come back!
Hi.
Leeston2379 will not be doing any changes here any more so I allow myself to upload my version of his kitchen here without creating new thread.
What has been changed ?
"Virgin" kitchen was only for packages modification without any pagepool changes or xip porting. Leeston2379 was basing on l3v5y kitchen which have certain bug. Interestingly this bug was "not active" as far as old ( original ) xip.bin was taken in .tsw file creation.
There are 4 batch files for new system building:
a) 2. build_without_xip_port.bat - the same as original leeston2379 batch but with fixed bug although here it is not "active"
b) 2. build_without_xip_port_pagepool_set.bat - allows to set pagepool size
c) 2. build_with_xip_port.bat - like original but allows to port new xip
d) 2. build_with_xip_port_pagepool_set.bat - like original but allows to set pagepool size and port new xip
I did not utilize automatic execution via for example
AutoExecAndClick.exe /launch "xipport.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
In my oppinion it is buggy . There are any timing races or something other causing any strange errors from time to time. User has to like in original l3v5y kitchen press different buttons in xipport software.
Thanks Mangasora for his post concerning porting xip
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Hi.
Leeston2379 will not be doing any changes here any more so I allow myself to upload my version of his kitchen here without creating new thread.
What has been changed ?
"Virgin" kitchen was only for packages modification without any pagepool changes or xip porting. Leeston2379 was basing on l3v5y kitchen which have certain bug. Interestingly this bug was "not active" as far as old ( original ) xip.bin was taken in .tsw file creation.
There are 4 batch files for new system building:
a) 2. build_without_xip_port.bat - the same as original leeston2379 batch but with fixed bug although here it is not "active"
b) 2. build_without_xip_port_pagepool_set.bat - allows to set pagepool size
c) 2. build_with_xip_port.bat - like original but allows to port new xip
d) 2. build_with_xip_port_pagepool_set.bat - like original but allows to set pagepool size and port new xip
I did not utilize automatic execution via for example
AutoExecAndClick.exe /launch "xipport.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
In my oppinion it is buggy . There are any timing races or something other causing any strange errors from time to time. User has to like in original l3v5y kitchen press different buttons in xipport software.
Thanks Mangasora for his post concerning porting xip
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
2. build_without_xip_port_pagepool_set.bat is my mod based
on leestone 2. build_without_xip_port.bat. bug?
please explain a little bit better: what you have do, what changed, the method for xip porting and how works? i hope is testet from you