Related
I am going to give chef'in a try and as I have never done it before I would ask you to be patient with me.
I have the HTC Leo with Radio 2.10.50 and HSPL installed.
Im using oskitchen and so far I have updated a Stock rom to 6.5.5. Nothing difficult there I hear you say ! But hey, its my first working ROM.
Now I have 2 questions that I hope you can help me with.
Q1. When I flashed the ROM to my phone all worked as you would expect apart from the main screen looked like it had dropped down about 10 pixels. Top and bottom bars looked OK but the middle looked wrong (Screen coming if needed)
Q2. Can someone instruct me on how to set the default wallpaper from oskitchen ?
I have an image called HTC_BG.png and I would like to cook it into the ROM as the default wallpaper.
Ive looked on the forums for help with these questions but I am unable to find them.
Any help / links would be helpfull
Once I have this info, I will proceed to cook my ROM and eventually post the results on the forums along with a complete tutorial as I go along, for those who are looking for similar info.
I have any problems with the buttons and the prefrence folders.
I have create a clip how can you see this problem.
h**p://youtube.com/watch?v=qmDQOzCIWu8
I hope i exist a fix, or what are the right kitchen for the Leo??
BoTTeR1337 said:
I have any problems with the buttons and the prefrence folders.
I have create a clip how can you see this problem.
h**p://youtube.com/watch?v=qmDQOzCIWu8
I hope i exist a fix, or what are the right kitchen for the Leo??
Click to expand...
Click to collapse
From what I know dumping and rebuilding a Leo ROM works correctly on both oskitchen 1.30v3 and 1.31beta3 so you probably changed something that broke that stuff. Always try if a clean dumped ROM rebuilds fine before doing changes that may break it.
Okay... I think im not so Stupid to do this.
I go this way:
1. I Install (extract) OS Kitchen on a folder into my Harddrive (C:/OS)
2. Then i Load the original Rom, extract this to get the RUU_Signed_0407.nbh
3.I Start OSKitchen and klick on Import-> Import a new ROM file.
4. I Select my Model, HTC Leo (HD2) and type the pfad of the RUU_Signed_0407.nbh and go to next (Waiting a minute)
5. I klick on start bulding, and os kitchen go throte without errors..
I Flash the Rom...
And the Taps didn't work. I Have a Windows XP OS and the OS Kitchen Version is 1.31.alpha4
BoTTeR1337 said:
Okay... I think im not so Stupid to do this.
I go this way:
1. I Install (extract) OS Kitchen on a folder into my Harddrive (C:/OS)
2. Then i Load the original Rom, extract this to get the RUU_Signed_0407.nbh
3.I Start OSKitchen and klick on Import-> Import a new ROM file.
4. I Select my Model, HTC Leo (HD2) and type the pfad of the RUU_Signed_0407.nbh and go to next (Waiting a minute)
5. I klick on start bulding, and os kitchen go throte without errors..
I Flash the Rom...
And the Taps didn't work. I Have a Windows XP OS and the OS Kitchen Version is 1.31.alpha4
Click to expand...
Click to collapse
Update to 1.31beta3 because anything before the beta1 had issues with HD2
like Shaddex I am looking into creating ROM's from scratch (for HD2 Leo also!), first for personally use and maybe for general if I can get a ROM to look nice.
My question is, is there a kitchen which work's best for the HD2? Or are all basically generic and just "cook" in different ways?
Sorry to hijack your post Shaddex I hope you get an answer soon, wish I could help
And back on topic
Ok. I extracted Oskitch again, added "RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship"
as the base ROM.
Next installed the "24619_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409" so I can use the latest build.
Thats all I did.
No extra EXT packages, Just cooked the ROM and below is what I get.
Anyone shed any light ?
5haddex said:
And back on topic
Ok. I extracted Oskitch again, added "RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship"
as the base ROM.
Next installed the "24619_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409" so I can use the latest build.
Thats all I did.
No extra EXT packages, Just cooked the ROM and below is what I get.
Anyone shed any light ?
Click to expand...
Click to collapse
The 6.5.3 windows mobile builds have the top and bottom bar of different sizes while Manila is probably calibrated for the WM6.5 bars (indeed there's empty space at the top and overlap at the bottom). There is probably something else you have to do to fix manila after changing the windows mobile build but I'm pretty sure it's not a kitchen problem I've had several people reporting the Leo ROMs dump and build fine with the 1.31 betas.
Is anyone willing to assist me on getting a Stock HD2 rom and upgrading it to 6.5.x without the problems I am seeing ?
5haddex said:
Is anyone willing to assist me on getting a Stock HD2 rom and upgrading it to 6.5.x without the problems I am seeing ?
Click to expand...
Click to collapse
Could you post a screenshot of your problem, and if you upload your background, i will use it to replace the one in HTC Black.TSK (You need OCP CE CAB Manager)
I have posted a screenie of the problem and someone says its because manila is not the correct version for the 6.5.5 im using.
Dont suppose you have a 6.5.5 stock rom ???
So...
Can anyone let me have a oskitchen with 6.5.x + latest manila so I can add to it.
I have recently started to build my own rom for the HD2. I have spent a lot of time getting a stable osKitchen build working with windows 6.5.5. I had some problems getting sense to work properly with the newer versions of windows.
I now believe that I have a stable build and am in the process of buildiing my first rom which I will post shortly.
I have seen that a lot of people have been having problems doing this as well. Now that I have got kitchen working I thought I would share it with people. You can download it from here:
http://www.megaupload.com/?d=UR5N4M4R
It contains the following
Base ROM: HTC HD2 default HTC stock rom version 1.66
OS: 24619
Sense: 2.5.2014 - I have tried using 2016 but can not get this working yet
osKitchen: 1.30v3
This rom compiles and builds correctly. I have flashed my HD2 and it seems to run properly. In a previous thread I stated that I could not get Internet Explorer to work correctly, I have now corrected this error.
This is a completly un-modified kitchen build, which I am happy for you to download and use. If you do upload your ROMS to XDA please just mention that you used my kitchen build.
The one limitation is that it is built for English, WWE only. I hae not been able to build any other languages into the rom.
If you want to use another phone other than the HD2 with this build, simply download your stock rom and extract using the wizzard, Go into your ext folder and delete all manila folders and the start icon folder and then copy the manila and start icon folders in from the leo ext folder.
I can see people have started to download and use this. I would be keen to know how you get on!
Giving it a go with a different device - will let you know how I get on
Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks
Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.
I have searched and asked whether there are any updated OEMDrivers for the native Blackstone 6.5 Kernel? It appears some of the Topaz 6.5 OEMDrivers are compatible with the Blackstone 6.5 native kernel and there are ROMs out there that have these drivers integrated? In the dump of the latest official Topaz 6.5 ROM lots of the .dll files from OEMDrivers are modules that get dumped as single files in the final Blackstone 6.1 ROM. I think due to the memory differences between 6.1 and 6.5 this is beneficial for Blackstone WM 6.5x ROMs with the native 6.5 Kernel?
I don't have the luxury of going through each of the files/modules and cooking ROMs as I only have a single Blackstone and its my only phone. But it does appear this has already been done by some of the Blackstone chefs? If someone could let me know what modules/files I can transport from the Topaz to the Blackstone I'd be grateful - maybe an upload of a converted/updated Blackstone OEMDrivers kitchen folder?
Many thanks
Andy
The Mikenificent ROM contains some updated Topaz Drivers apparently? The chef isn't responding to PM's and any other requests I have made have gone unanswered so does anyone have a dump of this ROM or the OEMDrivers folder?
The link to the Mikenificent ROM has also gone...
Andy
Hi Andy,
I've tried my self, but it's not an easy task.
I'd suggest to identify the target drivers you want to improve from the original Blackstone 1.59 ROM, and then create cabs with the Topaz drivers and install them on top for a quick try. You may need to recmod some of them.
I have tried a few of them, but some are not compatible (E.G.: smarttouch)
An alternative is to ask someone of the users on the mikenificent thread for a copy of the 13.3 Rom, flash it and get a copy of the drivers he is using and compare with the original blackstone drivers.
ypsmav said:
I'd suggest to identify the target drivers you want to improve from the original Blackstone 1.59 ROM, and then create cabs with the Topaz drivers and install them on top for a quick try. You may need to recmod some of them.
I have tried a few of them, but some are not compatible (E.G.: smarttouch)
Click to expand...
Click to collapse
That's probably the best approach. With 6.5 kernels, you can convert all of the oem drivers to modules (in my experience), and there will definitely be more modules among the drivers in 6.5 roms compared to 6.1 roms. If you want to test out some from a topaz rom, dump the rom and then recmod the ones you're interested in. I would just copy them into \windows with total commander or resco explorer, and over-write the rom module. Soft reset, and see how it works. You can do several at a time. For the hell of it once, I converted all of my oem driver dll's to files and then over-wrote the rom modules with the files to see how the device behaved. It worked ok (more virtual memory is used, though), and all of the files did load into ram properly.
I think this is what you are looking for.
> Blackstone-WM6.5-OEMXIPKernel.zip
Laurentius26 said:
I think this is what you are looking for.
> Blackstone-WM6.5-OEMXIPKernel.zip
Click to expand...
Click to collapse
Hi, thanks for the link but I already have that and thats what I am using in my Blackstone 6.5 ROMs. Its the OEMDrivers folder I want to update/replace with Topaz drivers that:
1. Work perfectly on the Blackstone
2. Are newer and written for WM 6.5
3. Offer better performance than the latest Blackstone 6.1 drivers
I have already re-moduled most of the 6.1 drivers however I can't see any performance increase with doing this - I think it is more memory efficient to have modules but since the drivers are essentially the same they perform the same
I have already asked in the Mikenificent thread as well as PM'ing Mikenf(?) and haven't heard anything so far...
Thanks, Andy
Half the fun of cooking is experimenting with the ingredients and settings. I suggest you just get the drivers and find out for yourself.
Topaz Drivers for testing on Blackstone
Hi,
I did a comparison of all drivers Blackstone 1.59 vs Topaz 2.53.
Attached you will find them, split by function (some of them unknown).
I'll be start doing some test myself using some in my next roms and advise
If you test and work, pls also advise.
Any new news here?
WBR
Siemens Lover
I'm making a rom for my HTC Touch2/mega. My currently installed rom is stock rom. Which is comes with my phone and it has no official version of it here. It's in Turkish language and 6,5 but I want to make it 6.5.5 So I'm trying to use this:
http://forum.xda-developers.com/showthread.php?t=544445
(And I don't wan't to lose the original room. Without HardSPL Can't I backup it right?)
And my rom is customized for an operator. So I want to build it in Turkish language. I have the mui's but I'm not sure they will work on 6.5.5 and I wan't to make it multilanguge. Because as default it's asking to me which language I wan't to use. I wan't to add this option too.
But if I try to build a new rom based on my current rom the operator customizations is continues? Like I can't use hdspa/3g with another operator (phone keeps crashing).
And
216xx = HTC htc
217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40
218xx = COM2, continuing dev of 6.5.0.50
219xx = MD, feature test branch, pretty much dead now. (unstable features are added here, this tree is based on COM1, so older base OS code, but the UI/UX code is newer)
22xxx = SEMC sony ericsson
*230xx = COM3, continuing development
*234xx = COM4, appears to be abandoned.
*235xx = COM5, more GUI changes here. New Outlook Interface.
*236xx = LG Electronics Branch
*24xxx = Possible HTC branch
*25xxx = SEMC - Sony Ericsson
*280xx, 282xx = WMD. This is a continuation of com3 from 23090. Most of the changes appear to be with IE
29xxx - Unknown
235xx has threaded email
Click to expand...
Click to collapse
Is there something matter If I choose not the Htc one's like 29xxx?
And Since Microsoft close the my phone Is there any point of keeping it in rom?
And Can I add video calling feature to my Mega with that:
http://forum.xda-developers.com/showthread.php?t=425937&highlight=video
WinCENLS_WWE and what is exactly doing? Is that neccessary for me? WWE means World Wide Edition?
Thanks
No answers? Guys please, I'm waiting for your anwers to cook my rom.
You touched several different problems.
Unfortunately each 6.5.x build will demand reviewing of most of the mui files. I know by myself. I used to build PLK versions of Jackos' ROMs and he has 2 series of ROMs (with 6.5 and 6.5.3 builds).
So you have to choose a build basing on information about it's stability/reliability, not ability to work with Turkish .muis. Either way you will need to mod some of them.
Second problem is to dump an existing ROM which I honestly know nothing about. But if it's a stock ROM, you should be able to find it somewhere anyway. By the information that you have to choose a language at first startup I think that it was not an official Turkish ROM, but the base for the device was WWE (World Wide English) and then there was a mod added by sunnysoft (http://firma.sunnysoft.cz/htc/). That's the same way it is done with Rhodium. We have no official Polish ROM, but only a sunnysoft plugin that enables the language choosing after a HR.
You can find there the newest WWE ROM and the language localization pack that you need.
Sooo I think what you should look for is an official WWE ROM (the version number you should have in Start -> Settings -> System -> Device information -> Software information) and a Sunnysoft mod with a set of different language.
Another problem is that you want to be able to choose a language after a HR. I don't recommend this method because:
- the way it is done by Sunnysoft is that they add a cab file with necessary modifications to a rom and run it after a HR by means of a .lua file or config.txt. The cab file script first asks the user for the language and then installs another cab according to the choosen language.
That means the resource files (and any other that must be added to the ROM) are just injected into the system as files. They do not delete the original english files from the ROM, but just add their own. Besides many of the .mui files (at least the ones from Base_Lang_0xxx package) should be placed as modules not files because otherwise they compromise the memory management.
So what I learned is that you should make as much changes to the ROM via the kitchen and not by a .cab file.
Furthermore the cab file is not able to make all the system changes. I know because I used to produce special PLK .cab files for Polish users of Rhodium. Mainly because we do not have a good Polish ROM and the Sunnysoft version had many bugs.
And there are a lot more changes that it's better to do during cooking than on the "real ROM".
As for myphone of course you can throw it out. It's not necessary anymore.
When I copy changelanguage.exe from my device to computer I was saw Sunnysoft. So like you said there is no official rom in Turkish. And yes it really has so much bug/mistranslates.
Actually I don't want big changes in my rom. I just want update it to 6.5.x
And yes really thanks.
My rom is 1.30.xxx.x but There was several updates on HTC support page so I installed them. Maybe they are updated the version. Should I install them to rom when I building it? Or they will just gone when I install 6.5.x 29xxx
And It seems It will be really hard to translate it to Turkish. Could you teach me? Or maybe not. f it comes too hard to me Maybe we won't be able to 6.5.x Turkish language. Whatever. I wan't to update my phone to 6.5.x without change much.
http://forum.xda-developers.com/showthread.php?t=578915
And there is an wwe edition it says but when i download it there is nothing called with wwe. so I download the sunnysofts version.
Well, I'm afraid you asking too advanced questions for me.
I never changed the build of the ROM. I only developed and adjusted language files to the ROM cooked by someone else (in my case Jackos and Seem_ZA).
That's why I know that even the .mui files are different among different builds.
The "Latest Official ROM" in the thread you provided is 1.28.401.4, and you write that your ROM is 1.30, so I guess you should take the one from Sunnysoft, dump it and then before you try to translate it, try to change the build. You will se if it is stable, if everything works, and then you will decide if you should include all the fixes HTC provided or not.
Remember - the 6.5.x builds are not "official" (except for some phones offered on Chinese market). Furthermore they are not made by HTC as well, so it's rather not likely that they have their fixes. On the other hand you should look into the fixes and try to judge by what they contain. I'm definitely not advanced ehough to help on it.
But I feel that for you the most important matter is read about cooking so that you know what to do and you know what you should change.
Dump the official ROM (from sunnysoft page) using any kitchen system, look into it, try to understand what parts it is made of. There are some tutorials floating over xda like "basics of ROM cooking" or "Kitchen and utensils for cooks" etc. Changing build is a bit complicated task. You will probably not cook a good&stable ROM without knowing the basics.
On the other hand perhaps you will find a good 6.5.x cooked ROM for Mega for which the chef published his kitchen. Then most of the hard work is done, because you don't need to mess up with build changing, testing performance, optimising XIP and many other tasks.
Then you can start thinking of changing the kitchen to compile a Turkish ROM.
Yes. I get it. So I'm starting build a new rom then if it's works good and stable I will try the translate it. And I will come to you for ask your help. And I know they are not official. If they were I don't even think about the upgrade it Thank you very much
If about language modification I can say that I'm quite "trained", but if about ROM cooking... I have very basic problems (look at my 2 questions on the top of Chef central). So I'm sure you need someone much more experienced to start your cooking adventure. Unfortunately WinMo is slowly dying, so almost nobody looks over here anymore...