Related
***********How to get Manila Sense working on 6.5.x ROMS***********
I have got a copy of sense 2.5.2014 wwe working with 6.5.5 OS. This version clears up issues with Sense not loading and the screen not loading correctly.
I can see a lot of people have been having some difficulty with this so I have provided a Downlaod link:
http://www.megaupload.com/?d=XSAZB44F - This is manila 2014. I have tested on my HD2 and the only issue I can see is Interent Explorer buttons are not quite right, if anybody can resolve this that would be great. I am working on 2016 now to see if I can sort as well. If I can I will upload it as well.!!
This has been tested on an HD2 with 1.66 WWE stock from and sense 23569.
Delete all existing manila and start icon folders in your EXT folder and simply replace with the ones in the zip file.
GhostXSeries said:
***********How to get Manila Sense working on 6.5.x ROMS***********
I have got a copy of sense 2.5.2016 wwe working with 6.5.5 OS. I can see a lot of people have been having some difficulty with this so I have provided a Downlaod link:
http://www.megaupload.com/?d=4NVBEING
Delete all existing manila and start icon folders in your EXT folder and simply replace with the ones in the zip file.
Click to expand...
Click to collapse
Not work for me... my ROM is spanish not WWE
Please, ¿what is your method for this problem?
...Sorry for my no-english ;-)
not working for me, although it boots up fine. if i scroll to settings only the data and wireless settings bit works and on home screen menu doesn't work, using 2.13 rom and 23569
Demon_man said:
not working for me, although it boots up fine. if i scroll to settings only the data and wireless settings bit works and on home screen menu doesn't work, using 2.13 rom and 23569
Click to expand...
Click to collapse
Did you remove the start Icon loader folder? I had similar problems untill I removed this. I can confirm that all settings is working on the rom!
tonofu said:
Not work for me... my ROM is spanish not WWE
Please, ¿what is your method for this problem?
...Sorry for my no-english ;-)
Click to expand...
Click to collapse
I'm affraid that I only was able to build for an english ROM WWE. I will try and make up an instruction set for building other languages.
Has anybody else got it working, I have it fully working on my HD2 I would be keen to hear responses.
Can anyone upload it to hotfile? I wanna test it but cant download the file!!!
I cant download it through megaupload, it stops at the middle everytime.
GhostXSeries said:
Did you remove the start Icon loader folder? I had similar problems untill I removed this. I can confirm that all settings is working on the rom!
Click to expand...
Click to collapse
i extracted the download and deleted out my manila files and start icon and then copied over the new ones. i dont know something not right
When I get a chance I will upload my copy of kitchen for people as well. I just have not had a lot of time this week. I will try and get it sorted this evening for you.
Demon_man said:
i extracted the download and deleted out my manila files and start icon and then copied over the new ones. i dont know something not right
Click to expand...
Click to collapse
What issue are you having? What is your base rom you are using?
GhostXSeries said:
What issue are you having? What is your base rom you are using?
Click to expand...
Click to collapse
Tmous 2.13 dumped rom, 23569 os, my menu buttons and the tabs when i scroll to settings just do nothing i i cant get into settings via the shortcut either
Demon_man said:
Tmous 2.13 dumped rom, 23569 os, my menu buttons and the tabs when i scroll to settings just do nothing i i cant get into settings via the shortcut either
Click to expand...
Click to collapse
I have tested it using a HTC HD2 stock rom version 1.66, that might be were your issue is. Try that and see how you get on. I am still playing around with the build. If I can get one I am completly happy with, I will upload my kitchen folder with both OS and sense for people to use.
hi!
Excuse me, and what about screen? Is it only for WVGA?
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.
Problem with Phone Canvas Enhancement 2G v4.0.52619223128.0 in com2 build.
Hi all, just have an issue and I can't point the finger on the right place to get this one solved
So I'm asking for some help, I'm using the Phone Canvas Enhancement mentioned above, and it works perfect on a com3 build but
for some reason when I cooked this one in a com2 build the options for the dialer are not working.
I'm using the same kitchen, for com3 and com2 with the same pkg's and everything is working the way it should work.
Only in the com2 build I'm not able to setup the call-specific options.
Already changed the mui files, used another dummy_sqm but still no difference.
The com2 build I'm using is 21916, also tried 21914 but no difference.
Someone else have any idea ?
Thanks,
Ok, just want to give it one more try so BUMP
Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.
Laurentius26 said:
Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.
Click to expand...
Click to collapse
I dumped the rom myself, import the 23569 build and import the 21916 build, made a small change on the 21916 build (changed office mobile to office mobile 2010) and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
For now really thanks for the info, I'm gonna work on it and keep you informed if this will solve it.
Btw nice site you have
Greetz,
Try to use the phonecanvas as it's (if possible) and use the correspondending phcan in operatorpkg.
Another thing you need to check is the reg in operatorpkg, if it directs to the phcan you are using.
In my case:
[HKEY_LOCAL_MACHINE\Security\ResOver\Bitmaps]
"Basedll"="leo_phcanOverbmp.dll"
"BaseId"=dword:00000000
"BatteryIconIdStart"=dword:000003E9
"BatteryIconLevels"=dword:00000015
Click to expand...
Click to collapse
Thanks for the compliment about the site.
Rataplan said:
and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
Greetz,
Click to expand...
Click to collapse
What do you mean with "call specific options"?
pkoper said:
What do you mean with "call specific options"?
Click to expand...
Click to collapse
I mean the advanced options, sounds, network, gsm/umts, headset it's a submenu from the dialer, I think that Laurentius26 is right because I miss the registry key for phcan, I'm gonna check it this evening.
Still wondering why I don't have a problem with a com3 build.
Keep you all informed
Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.
pkoper said:
Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.
Click to expand...
Click to collapse
Okay thanks gonna try that, because changing the reg. made my kitchen crash.
Greetz,
Ok, I give up, I build 12 roms with 21916 (all different languages) until I noticed the issue, went back to 21914, same issue.
Tried what you both suggested, kitchen start crashing, went back to the original 21854 with the same pkg everything working normal also the options menu in the dialer.
So the problem must be in the changing the office pkg or a kitchen-update because thats are the only things I've changed.
And I'm not even sure about the kitchen-update.
For now I'm not sure what I've changed to give an honest answer if I get this solved.
Just want to say thanks the both of you, together is power
Regards,
I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post
pkoper said:
I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post
Click to expand...
Click to collapse
Yes, I know, I already found that reg key, but for some reason my kitchen keeps on crashing when I use the 21916 build, so I can not tell you if the trick you told me is working.
In short what I tried:
1. Edit the reg key for the phcan.
2. Deleting the reg key in the Phone pkg.
3. Changing the Phone pkg and use the one from 21854.
4. Building without ext-pkg
5. Make a switch to 21914 and repeated the 4 steps mentioned above.
But for now the kitchen keeps on crashing when I'm using the 21914 or 21916 build, which is very strange because I cooked several roms with it also cooked without the office pkg but still no change.
For now I'm gonna download another com2 build and see if that will do the trick.
In Dutch: Schiet mij maar lek.
In English: Shoot me.
And again really thanks for trying to help me.
Greetz,
Sorry forget my post.
Ok downloading and importing the 21916 again did the trick, download the build from mobileunderground, normally I used the builds from ppckitchen not sure if they are different.
The only thing I can think about for now is that when I'm upgrading my kitchen, went from 1.25 to 133.3 (oskitchen) always in small steps but the only thing I changed was the exe file and the resource folder, and maybe there it went wrong.
I know it is not a real solution but for me this one is solved.
Thanks,
Hey all,
I've now flashed WM Build 23146 on a Touch Pro, but now I'm getting very very very small fonts almost everywhere... (And yeah, I wear my glasses )
Someone knows how to fix this?
Thanks!
MadMatt
Some screenshoots?
Never had such a problem but you are the 2nd person today that have this problem and the other guy does use 23103 language pack too........strange.
_Madmatt said:
Hey all,
I've now flashed WM Build 23146 on a Touch Pro, but now I'm getting very very very small fonts almost everywhere... (And yeah, I wear my glasses )
Someone knows how to fix this?
Thanks!
MadMatt
Click to expand...
Click to collapse
If you mess with the rgu processing order, then you will get tiny fonts. There are two packages that set the font sizes: OS and Base_Lang_0409 (or whatever). You need the Base_lang one to run last.
Hello.
Please check you have Metadata folder in your kitchen..
Some dump's have that sys package in 0409 language folder.
Thank's.
Thanks! After doing all things said above, it works! Thread can be closed.
You should always compare a new Sys to the one you were just using, and then make sure that you havel all of the same packages present, otherwise you run into issues like this. The easiest thing to do first is to just right-click on the sys_xxxxx folder and check the properties. Write down the number of files and folder present, then do the same with the build you were just using that was working. You should have the same number of files and folders, or very close to it. If there are discrepancies, then you need to figure out what you left out. It will save a lot of time. Just using some dump-sorter and then cooking without checking is bound to get you into trouble.
This is a full and only german WM6.5 COM2 21901 ROM.
I made this ROM for my personal needs and my old Polaris. To give him a new live.
Thanks to all Cookers/Developers! Without their knowledge I would not succeed finding the present solution.
This ROM was build with Barin's wonderful OSBuilder kitchen and unlike other ROM's, you can dump and recook it. All RGU/DSM files are inside (it's a real signed ROM). Feel free to modify it, to fit your needs! Please share the knowledge with the community. Sharing the knowledge rather than keeping it secret is the biggest improvement.
ROM-Base:
WindowsMobile Build 6.5.x COM2-21901
Polaris Native Kernel 6.5 (101MB)
Polaris OEM 3.19 with (massiv) modifications
Packages from Mega (most), Iolite and Topaz
Some custom packages and tweaks
Q: Why to hell a COM2-Build?
A: I dont like the big buttom bar in COM5. That's all.
Q: What packages are inside?
A: Most of Mega, No Manila2D, EzInput 1.5...download and take a look
Downloads:
Please read Post #11! New ROM: 21901_007 (06.05.2011).
I will give it a try because I was searching a german 6.5 Rom for a long time.
Whats about the 3D-Drivers for the polaris, are they included ?
Happy Holidays
MrGame said:
Whats about the 3D-Drivers for the polaris, are they included ?
Click to expand...
Click to collapse
Sorry,
3D-Drivers are NOT included. Because the used Kernel is incompatible. If I can find a NK 6.5 for the Polaris with 85MB-RAM (current 101MB) enabled, then I can try to build with the drivers included.
c.u.
MrGame said:
I will give it a try because I was searching a german 6.5 Rom for a long time.
Whats about the 3D-Drivers for the polaris, are they included ?
Happy Holidays
Click to expand...
Click to collapse
if you really need a 3D-drivers for Polaris !!! This use
s_marth said:
Sorry,
3D-Drivers are NOT included. Because the used Kernel is incompatible. If I can find a NK 6.5 for the Polaris with 85MB-RAM (current 101MB) enabled, then I can try to build with the drivers included.
c.u.
Click to expand...
Click to collapse
you should first edit the ROM using HTCRIE, after in edit you can add files 3D-ROM Driver files
Hakim Rahman said:
you should first edit the ROM using HTCIRT, after in edit you can add files 3D-ROM Driver files
Click to expand...
Click to collapse
Wich part of ROM should I edit with HTCIRT?
You cannot use 3D-Drivers with the current Native 6.5 Kernel in my ROM. The kernel is hacked to use the area between 85MB -> 101MB as RAM. The 3D-Drivers like to use this area for DDI.
That's the problem. If I'm wrong, feel free to show me the right way.
s_marth said:
Wich part of ROM should I edit with HTCIRT?
You cannot use 3D-Drivers with the current Native 6.5 Kernel in my ROM. The kernel is hacked to use the area between 85MB -> 101MB as RAM. The 3D-Drivers like to use this area for DDI.
That's the problem. If I'm wrong, feel free to show me the right way.
Click to expand...
Click to collapse
sorry I have to straighten, not htcirt but HTC ROM Image Editor , yes it is definitely ruu signed.nbh in ROM which you make with HTCRIE you can add it or subtract the necessary application files survivors trying & good luck
Hello s_marth,
great ROM, I like it!!
But I use Radio-ROM 1.59.44.02, and I had also wakeup problems. Do you have another solution?
The keylock doesn't work. I don't want to use s2u2. Could you fix it?
Matthias
siggilein said:
Hello s_marth,
great ROM, I like it!!
But I use Radio-ROM 1.59.44.02, and I had also wakeup problems. Do you have another solution?
The keylock doesn't work. I don't want to use s2u2. Could you fix it?
Matthias
Click to expand...
Click to collapse
Hi Matthias,
I also had wakeup hangs with 1.59.44.02 (not so often as with 1.59.46.12). I'm using 1.59.42.15 at the moment. Over the last 4 days I had no problems.
What you mean? Keylock or lockscreen? For keylock please have a look at: Einstellungen -> Persönlich -> Tastensperre. It works for me.
For automatic lockscreen I use LockDevice 1.6.
cu
Sven
Hi All,
I found a big bug in my ROM!
Please edit the registry to the values in the code window and take a soft-reset:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\TFLOSettings]
"EnableScroll"=dword:0
"EnableSound"=dword:0
"EnableCube"=dword:0
Setting "EnableScroll" to "0" is the most important!
If it is set to "1", the HTC touch.dll/biotouch.dll conflicts with the WM 6.5 builtin touch driver. Typical symptoms are random short hangs while scrolling and lame phone canvas. After edit and soft-reset you get a real fast device.
cu
Sven
Hi All,
here you find a new version of my german ROM for the Polaris.
Changes:
Titanium only! No more Manila2D inside. For me, it is useless bulk.
Fixed scrolling (post #10).
EzInput 1.5 fixed, Landscape added, US and DE keyboards only
LockScreen fixed, HTC-LockScreen-Enh. removed.
Transcriber, Windows Live, Footprints, Manila2D are only present in the kitchen (you can get by request)
EDIT-07.05.2011:
Switching from package "MEGA_Power" (powerexe.exe 2.28) to "POLARIS_Power" (powerexe.exe 2.14). I hope this was the end of search for the reason of random freezes or "sleep of death".
If you like to cook your own ROM, PM me for the kitchen.
Downloads:
EDIT-07.05.2011: New ROM with essential fix, you should upgrade
ROM: https://rapidshare.com/files/461069339/ROM_21901_007.7z
THX,
for this german rom in the Year 2011.
Rom Flash is done. Now i Test you Rom in the next weeks. I hope ist work for me.
Gruss Lothar
many Thanx to u for this great work. I installed it two weeks ago, and it works great. The only thing what is boring is the time to what until xda has manage contact or sms service. I dont know whats going on, and i installed htcs qwertz tab because all other tabs hasn´t work well. Hope i can help with your great work.
cheers
sorry 1 exception xda freezing if the display is fading away, until i push powerbutton. then booting finalized its work... any Idea how to handle it.
Just downloaded and its wirks fine.But it is possible, to make the icons and text in the menue bigger. 3 icon per line ?
zm
dl1bjy said:
Just downloaded and its wirks fine.But it is possible, to make the icons and text in the menue bigger. 3 icon per line ?
zm
Click to expand...
Click to collapse
You can allways build your own ROM with my kitchen by request. 3 icons per line is the WM default.
cu
skysegel said:
sorry 1 exception xda freezing if the display is fading away, until i push powerbutton. then booting finalized its work... any Idea how to handle it.
Click to expand...
Click to collapse
Hi skysegel,
sorry I forgot to put some modules to slot0. This is fixed in my last ROM (21901_006 from 10.03.2011). I had tested the new ROM over 1 month and got no freeze or SOD anymore.
cu
Little better, or streamline some better!
sleep of death within 5 minutes 3 times.
23.05.11:
Today, only one time
lazomi said:
23.05.11:
Today, only one time
Click to expand...
Click to collapse
Hi lazomi,
please perform a Hard-Reset after flashing the ROM. This action formats the flash and loads factory defaults.
cu
Sven
hi,
i flash mein xda orbit 2 with your ROM_21901_007 few days ago, yesterday i have several times sleep of death only unplug the battery helps...
and yes i made a hardreset after flashing
at the moment i change the settings "Tastensperre" to "Tasten nicht sperren" and no sleep of death so far
what can i do?
p.s. sorry for my bad english