yashsingh1/xdaforums huggingface dataset:
[Touch Viva, MDA Basic ROM Development] theglen35:
Ok, After i have made the rom and flashed it and i go and select the comm manager nothing happens and if i try to select Today in settings nothing happens and if i select file explorer when it comes up i have to long press or hold down the stylus long to select something.If i restart the phone everything might work and then if i restart again it will not work.

I am sorry about the pics but i am using WM 6.1 at the moment.

What if the kitchen is not fully compatible with WM 6.5, because when i make a rom with 6.1 there are no problems.
[Touch Viva, MDA Basic ROM Development] BesFen:
The Kitchen is fully compatible, and only Visual kitchen can build WM 6.5 without problem. I ever use more than 3 kinds of kitchen, Old style Kitchen for 6828, Elf, Gene, PPCGeek's kitchen, VK, and the best kitchen is base on platform rebuilder by ervius, and VK is base on that.

Does the auto setup run at the first boot? if yes, you should to disable it.

The default Auto setup only compatible with WM 6.1.
[Touch Viva, MDA Basic ROM Development] theglen35:
When you say auto setup do you mean when it says windows will customize in 3 seconds? If it is that then yes it always runs, and how do i disable it?
[Touch Viva, MDA Basic ROM Development] ivanmmj:
The same exact kitchen is running WM6.5 perfectly on the Herald. It's got to be some settings in the Opal OEM interfering with the WM6.5.

The OEM in my kitchen should not autolaunch the customization, either. Is the one from MY kitchen doing so?
[Touch Viva, MDA Basic ROM Development] BesFen:
Yes That is, you can use Ivanmmj OEM, he already disable it.

@: Ivanmmj

Did you make any change of OEM in your kitchen? Because i didn't do it in mine.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
I only disabled the autostarting contumization. It was giving my tester and error when booting due to not finding the files it was looking for on a stripped ROM.
[Touch Viva, MDA Basic ROM Development] theglen35:
Yep ,it still launches in your kitchen. I am sorry guys i have really tried, i give up man. I am going back to WM 6.1, i'll wait till someone figures it out.
[Touch Viva, MDA Basic ROM Development] BesFen:
:D:D:D Cooking a ROM is not easy, need more and more time and effort, If you do more experience, you can make a perfect ROM.;)
[Touch Viva, MDA Basic ROM Development] ivanmmj:
As BesFen said, cooking is NOT an easy process. If you don't port it, you'll have to wait until someone else figures out how to port it, if anyone ever tries. But while you try to figure out how to port it, you will end up learning a LOT about cooking. As far as the autoconfig in my kitchen, it should NOT be popping up. (I made some test ROMs and had someone test it on an Opal a few times until I was sure it wouldn't come up.)
[Touch Viva, MDA Basic ROM Development] theglen35:
I realize it is not an easy thing to cook a rom but both of you guys made it easy through your kitchen and your guidence.

A BIG THANKS TO

BESFEN

FOR BRINGING US THE FIRST KITCHEN AND ALL YOUR HELP. :D

A BIG THANKS TO

IVANMMJ

FOR HIS KITCHEN AND ALL HIS HELP.

I am a little frustrated now guys so i am taking a rest on cooking roms but your guidence and kitchen has helped me to remake WM 6.1 to how i want it to look and feel and that is what i am using right now and i am very contented. :D

THANKS GUYS, when i get back to cooking roms i will let you know my progress.
[Touch Viva, MDA Basic ROM Development] theglen35:
Figured it out

:D:D:D OK Guys i figured it out at long last.Here is what to do:

1-Delete these files in Opal External Packages: OutlookEnhancement, PhoneCanvas, TouchFlo, VolumeControl.

The rom will run smooth without these files.

2-Take these files from Opal External Packages and put it in OEM/Opal/0409 : BuildInfoPkg, ConfigAP, CONNECTIONSETUPDB, ExtendedPkg, ExtraFilesPkg, OperatorPkg, OperatorPkg_PT. If you don't want the (windows will now customize) on first boot just delete these files.

3-Take the .VM file from OEM/Opal and the .ROM file from the original Opal rom and put it in SYS/23xxx/SHARED/COMMON .

And that's it ,ROM works perfect. OH i also replaced the MetaData folder in SYS/23xxx/SHARED/COMMON with the one from the original opal rom but i don't think it made any difference but you could try it.:D:D:D

Also make sure the PP is set to 12
[Touch Viva, MDA Basic ROM Development] ivanmmj:
1. Those files aren't in there on my kitchen. :p

2. Some of those folders are still there. I gotta get rid of them.

3. You shouldn't have to.

4. You shouldn't have to.

I'm going to go ahead and clean up step#2 for v0.6. I wonder if all these problems are because people are using all the EXT packages that were enabled by "default". They were only enabled because I left them enabled when I added them. They're NOT supposed to all be enabled. :p
[Touch Viva, MDA Basic ROM Development] BesFen:
That is Good news.

You can set PP to 20MB to make IE run Smooth, try it.
[Touch Viva, MDA Basic ROM Development] theglen35:
ERROR

Hey guys ,when i get this error what to do?

ERROR!!!!!!!!

562 Modules present;Too many modules....with 6.1 NK.exe and 6.5 XIP you'll have non-bootable ROM...Exiting...

Process cancelled....
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Well, it says you have too many modules. So take off some modules (disable some stuff.) You added WAY too much stuff. Or convert some of the extra modules to files.
[Touch Viva, MDA Basic ROM Development] theglen35:
I replaced my packages with the ones from the Mega Rom and i got the error. I think the packages are too big in size.
[Touch Viva, MDA Basic ROM Development] BesFen:
Not in size, but too much modules, convert some module to file.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
The Mega packages have a few problems (which is why I haven't included all of them, yet.)

1. They have a lot of requirements of other packages.

2. They use modules heavily.

3. They use modules that require two memory allocations (which our kernels can't handle until we see HTC make a native 6.5 kernel for our devices.)
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Question: Does the phonecanvas 3.0 work on the Opal properly.
[Touch Viva, MDA Basic ROM Development] theglen35:
aahhhhh

Man this is really crappy, the rom is still giving the same trouble!!!!!!! Like it was a fluke that it worked good last time. I made another rom and problems, i tried to install the last one that worked good but nothing.

What i have noticed is that when i install the rom on first boot everything works perfectly but as soon as i restart the phone PROBLEMS. AAHHHH I GIVE UP.:mad:
[Touch Viva, MDA Basic ROM Development] ivanmmj:
What EXT packages are you adding? I wonder if it's your choice of EXT packages? Post EVERY EXT package you have enabled. (Remember, there aren't any enabled by default because they have to be, but just because when I add packages, they enable themselves automatically.)
[Touch Viva, MDA Basic ROM Development] BesFen:
Hi Ivan, i want to ask you some question, but it's off topic, sorry.

I plan to buy a one PDA again, Actually i prefer HTC'S device, but no store sell it again in my country.

How about Sony X1 if it compare to Diamond? (I already have diamond) The price is USD 440

Do you have any suggestion about good device for price not more than USD 500?

Thank you.
[Touch Viva, MDA Basic ROM Development] theglen35:
Man believe me i have tried everything,I have added, removed, only left the needed packages and even removed all the packages!! I even removed all the files in the OEM folder except the driver folder, i even replaced all the folders in the OEM folder and nothing seemed to help. It has to be the kitchen man, there is no other explanation. It is perfect with wm 6.1 not 6.5 . If it is not the kitchen then the Opal is complecated to make a wm 6.5 rom. But somehow PhamQuang and his friends make them without problems.

Can you dump one of PhamQuang roms and upload the OEM,SYS,ROM and EXT folders for me man, i have tried but i get an XIP error everytime. I want to compare his files and see what he did to make it run without problems.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
It's got similar hardware but has a higher resolution screen. Getting tired of the Diamond?

I don't know much more about it. I do enjoy my Android phones, though. ^_^

Most ROMs are undumpable. It's probably some things that are built into the OEM that don't like 6.5. I have to do some more cleaning of the OEM. (But I don't have an Opal to test with.)
[Touch Viva, MDA Basic ROM Development] theglen35:
Hey man this file is missing from the MSXIPKernel, do you think this could be the reason the rom is not working properly?
[Touch Viva, MDA Basic ROM Development] ivanmmj:
No. I believe that DSM is part of the MSXIPKERNELLTK which is not required. I don't see how a DSM would cause those issues.

(Most build releases don't even come with it.)

I wish I had an opal to try it with.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
v0.6 Released. Please check my website for a changelog.
[Touch Viva, MDA Basic ROM Development] theglen35:
I downloaded all the folders and when i try to unzip them it says cannot open as archives. :confused:
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Did you download them yesterday or today? (I forgot to update the Opal thread) but the downloads were broken until this morning.

Sorry.
[Touch Viva, MDA Basic ROM Development] licat:
When I cooked with core of wm65, it always show error: integer overflow.:mad:
[Touch Viva, MDA Basic ROM Development] licat:
Sorry, this problem in OpalChef, not in this kitchen:D
[Touch Viva, MDA Basic ROM Development] theglen35:
If i leave out the OEM Driver folder and cook a rom and flash my phone what will happen??
[Touch Viva, MDA Basic ROM Development] ivanmmj:
It won't load any drivers... No USB driver, no graphic driver, no keyboard driver, etc.

I doubt if anything will boot.
[Touch Viva, MDA Basic ROM Development] theglen35:
Weird

Ok ,i have found the problem. When i leave out the BlueTooth folder in SYS/230xx/SHARED/COMMON the ROM works perfect. But if i leave the folder in the ROM when i restart the phone the HOME settings and the COMM Manager does not work.:confused: Any ideas?
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Run that by me again? (This seems to be the bug that everyone was having. Maybe you've figured out what causes it.)

So it happens only if you install the bluetooth modules?
[Touch Viva, MDA Basic ROM Development] theglen35:
Yep, that's definately what happens. I tried replacing it with the one from the original wm 6.1 but it don't work. The ROM works but with no bluetooth. I have to check and see if it will work with the EXT bluetooth packages.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Does the problem happen if you cook a 21054 or a 218xx build?
[Touch Viva, MDA Basic ROM Development] theglen35:
no ,only when you cook 218xx and up. Only 6.5 not 6.1
[Touch Viva, MDA Basic ROM Development] licat:
I have same problem:mad::mad::mad:

if I removed rows follow in file:74f4dd24-b1d3-4e1c-8cb8-16e1bea02a3c.rgu

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial\Unimodem]

"Tsp"="Unimodem.dll"

"DeviceType"=dword:0

"FriendlyName"="Serial Port"

"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial]

"Prefix"="COM"

"Dll"="serial32.Dll"

"Order"=dword:1

"Index"=dword:1

"DeviceArrayIndex"=dword:0

"FriendlyName"="Serial Port"

"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00

"Priority256"=dword:5D

"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}" ; GUID for feneric power-manageable devices.

Rom work perfect, but no bluetooth.

If not remove this text in 74f4dd24-b1d3-4e1c-8cb8-16e1bea02a3c.rgu the room work perfect only at first time (after hardreset), and after softreset the bluetooth automatic disappear and cannot access Home setting, Comm manager. :(:(:(

Anay idea?
[Touch Viva, MDA Basic ROM Development] theglen35:
Your worries are over for i have figured it out. Turns out the comm manager that comes with the kitchen from the original rom is not compatible with WM 6.5. Just make the ROM with the new Comm Manager and everything will work perfect :D:D:D:D:D

Use HTC CommManager 2_9_5_0
[Touch Viva, MDA Basic ROM Development] licat:
Not work --> Problem remain

- I remove CommManager from original rom--> Bluetooth not work after softreset

- I replace CommManager with some version (include 2_9_5_0) --> Bluetooth not work after softreset

:( :( :(
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Out of curiosity, try this:

http://justkitchen.info/JustROMs/OpalBTtest.7z
[Touch Viva, MDA Basic ROM Development] licat:
I tested this your ROM (23081)

-------------------------------------------

*) After upgrade ROM and Hardreset: Everything OK, bluetooth, wifi... Perfect

*) ....and Error occur if you try it by follow steps.

1) Turn On bluetooth, wifi then Turn them off

2) Press volume key up/down

3) Soft reset device ----> Bluetooth not work again, can not access Home setting, cannot open Comma, and cannot volume key up/down :eek::eek::eek:

wifi cannot turn on
[Touch Viva, MDA Basic ROM Development] theglen35:
Put the new comm manager package 2_9_5_0 in the EXT folder and when you cook the rom it will overwrite the old one. Before you cook make sure the package is selected True.
[Touch Viva, MDA Basic ROM Development] licat:
Yes, I did like that. Put comm(2_9_5_0) to EXT, and selected it when cook (Green color in list modules) but Bluetooth still error after softreset (only work first time after hardreset) :mad::eek::mad:

--> I think not problem with Comm, Bluetooth module...It's a bug in Kitchen, am waiting Ivanmmj for fix it
[Touch Viva, MDA Basic ROM Development] ivanmmj:
The problem is not there on any of the other devices that the kitchen supports (Herald, Hermes and Artemis) so it's not the kitchen's Bluetooth module. It's definitively one of the files or programs that came as part of the Opal OEM.

I'm going to start stripping the Opal OEM some more today (if I get time to) and see if I can find the cause.
[Touch Viva, MDA Basic ROM Development] licat:
Thank, waiting...

But note: with these programs and files of Opal OEM, building with XIP/SYS of WM6.1 all done perfect.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
There were a LOT of changes done in 6.5 by microsoft. For example, if you try to add the outlook enhancement to 6.5, it breaks many things for ANY device. It's just not compatible. It's not the kitchen. The kitchen doesn't do anything more than just put together the files you give it into the exact same format and it works fine with wm6.1. It's not the SYS files because the SYS files work fine with the Hermes, the Herald and the Artemis. It HAS to be something in the OEM that's not compatible with the bluetooth modules in 6.5.
[Touch Viva, MDA Basic ROM Development] licat:
I'd cooked Clean ROM with some cases, and all get same BUGs after softreset, you see and hope you solve it:

1) Remove all Opal Packages (Remain only OME Driver, App) --> Comm, Bluetooth, Volume keys Erorr

2) Remove all Opal Packages + Replace bthuart.dll, serial32.dll from other device [Elf, Hermes] --> Comm, Bluetooth, Volume key Error

3) Remove all Opal Packages + Replace btdrt.dll, bthlink.dll,bthutil.dll sometime Bluetooth module from WM6.1 --> Comm show, but cannot turn on Bluetooth.

4) Remove all Opal Packages + App in OEM folder (Remain Only Driver) --> Bluetooth, Volume key Error, and Comm of WM6.5 display only PHONE, WIFI
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Ok, try this one:

http://justkitchen.info/JustROMs/OpalStrip.7z

It's stripped a little more.
[Touch Viva, MDA Basic ROM Development] licat:
Tested

---------

1) After flash, boot OK: It automatic display Comm Manager

- Turn on/off wifi - OK

- Volume key - OK

- Turn on BT, it long respond.... and BT not turn on.

- Goto: Settings -> Bluetooth: Choose Turn on Bluetooth --> A dialog show:"There is no Bluetooth hardware installed on this device"

2) After softreset

- Volume key, wifi, Home Setting: OK

- Comm Manager show, but still BT not turn on

- And Bluetooth still display: "There is no Bluetooth hardware installed on this device"
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Oops, I forgot to reenable the bluetooth modules. Let me create it again and upload it.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
OK, try this now:

http://justkitchen.info/JustROMs/OpalBTtest2.7z
[Touch Viva, MDA Basic ROM Development] licat:
Tested :D

---------

1) After Flash

- Boot Ok, show Comm (Origin) but Customization auto run and Device Reset

2) After Boot again

- Comm not work

- Home setting not work

- Bluetooth not work (Even interface of Bluetooth not show):(:(:(:(:(

3) Reboot device again

- Settings-> Bluetooth show (interface) but cannot turn on BT (cannot go to tab: Mode)

- If try open Comm nothing done, but after that cannot open Settings-> Bluetooth

Time to sleep, will test your work late...
[Touch Viva, MDA Basic ROM Development] ivanmmj:
I have a question: When you're using a 6.5 ROM that doesn't have this problem: Does it have the same comm manager or another comm manager?
[Touch Viva, MDA Basic ROM Development] licat:
V25 ROM of PhamQuang on PDAViet with Comm port from Mega--> Not have this problem.

All ROM 6.5 I cooked by Tools that YOU or BesFen provide for having this problem (try with many XIP/SYS - ... 23053, 23075, 23081...)

This Problems occur with all comm manager:

- Origin of Microsoft

- All HTC Comm version
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Then the question is what they changed on the OEM to make it compatible or what they changed on the SYS. The problem is that getting info from PDAViet can be hard sometimes.
[Touch Viva, MDA Basic ROM Development] licat:
Can not contact to PhamQuang! So that, hope YOUs with your experiences can be solved this problem.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
http://justkitchen.info/JustROMs/OpalBTtest3.7z

Try this one. Just curious.
[Touch Viva, MDA Basic ROM Development] licat:
Tested :(:(:(

--------------

1) First boot

- Wifi auto ON

- Comm not work

- Home Setting not work

2) After Softreset

- Comm - OK

- On/Off Wifi - OK

- Home Setting - OK

- Volume key - Ok

- On/Off BT - Not work (Display "Can't turn on Bluetooth" :D)

3) Reset again

- Volume key - Not work

- Comm display but still not turn on BT
[Touch Viva, MDA Basic ROM Development] ivanmmj:
What I wonder is.... WHY is it that after every reset you get something different? What is being launched at startup that changes things?
[Touch Viva, MDA Basic ROM Development] ichte:
Hey Ivanmmj, if I replace OEMXipKernel folder of Opal with other OEMXipKernel (from other Device, as Jade) what will happen when I fash.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
You should get a non-booting ROM. The OEMXipKernel is device specific. (Some modules aren't device specific by themselves for the whole is device specific.)
[Touch Viva, MDA Basic ROM Development] theglen35:
Delete the .dsm and .rgu files from the Bluetooth folder and everything should work fine. But for some reason the bluetooth icon does not show up in the task bar but the blue light flashes, thats how you know it is on.
[Touch Viva, MDA Basic ROM Development] licat:
OK, I've created a ROM (delete .dsm and .rgu files) and it RUN and Bluetooth perfect. Thank
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Ok, then. I will implement it by adding a seperate bluetooth_Opal section.
[Touch Viva, MDA Basic ROM Development] licat:
New problem: Volume key long respond when press down and hold (up/down).
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Sorry, I've been really busy with work and school and haven't had a chance to respond. Have you tried a larger pagepool than just 6mb? With the RAM the Opal has, you can afford a good sized pagepool.
[Touch Viva, MDA Basic ROM Development] licat:
I've set PP to 12 Mb, 16 Mb and sometime 20 Mb but volume keys not work good (if bluetooth is on it work perfect :D)
[Touch Viva, MDA Basic ROM Development] ivanmmj:
When the bluetooth is on the volume keys work perfectly? o_O
[Touch Viva, MDA Basic ROM Development] licat:
Yes, When the bluetooth is on the volume keys work perfectly

If BT is off the dialog volume slow (delay 1s) display when press and hold volume keys.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Now THAT is weird...
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Bump for 0.7 release.
[Touch Viva, MDA Basic ROM Development] jagan2:
Thank you

Thank you, Downloadin.......:)
[Touch Viva, MDA Basic ROM Development] jagan2:
Sir, one problem is always there that is no availability of parallel downloads could u provide mediafire mirror from next time? because for slow internet many times it breaks and no resume :(
[Touch Viva, MDA Basic ROM Development] ivanmmj:
The files are hosted in the site itself. Unfortunately, my work and school keep me so busy that even uploading them to the site was hard. If you can help me find a Joomla plugin that will automatically mirror files, I can use that to help everyone. For now, you'll have to wait until someone mirrors it for me. (Since I'm at work.)
[Touch Viva, MDA Basic ROM Development] theglen35:
Hey pal can you get a WM 6.5 Native Kernel for the Opal? The 6.1 Native Kernel that the kitchen has works fine when you make a WM 6.1 rom but not a WM 6.5 rom. You get all kinds of problems.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
I can only get it if HTC has created one. Has HTC released any official 6.5 ROMs for the Opal?
[Touch Viva, MDA Basic ROM Development] jagan2:
SJK V0.7 Mirrors

I tried to find joomla plug in but didnt got actually i think i didnt hit the right keyword or not properly searched anyways i tried to upload ur files using web upload. But webupload needs direct link ur is direct but initially the name is diff later ur server gives another name i uploaded but the name remained the initial one long one.

If u download any of the file from the following mirror, after download rename the file to anything.rar or .7z remember to rename the file to rar or 7z format or else it will not work.

Here iam giving mirrors for Opal related files only, as its a opal forum. ivanmmj if u wish i can make a seperate thread where i will post mirrors for all files.:)

Hope this makes ur work simple.

SuperJustKitchen - SYS/XIP System Files v0.7 mirrors

Deposit files

Rapidshare

Mega upload

Mediafire :)

SuperJustKitchen - Main Kitchen Files v0.7 mirrors

Hotfile

Rapidshare

Mediafire :)

SuperJustKitchen - EXT Packages v0.7 mirrors

Rapidshare

Easy share

Mediafire :)

SuperJustKitchen - Opal Required Files v0.7 mirrors

Rapidshare

Ziddu

Mediafire :)

I think these mirror sites are good and enough still anyone needs diff one say i will do if possible.
[Touch Viva, MDA Basic ROM Development] jagan2:
No, htc has not released any official 6.5 rom for opal.

Suggestion

: On your next version of kitchen if u use files from mega rom that would be better and i think that would minimize the probs in kitchen while cooking for wm 6.5. As htc touch 2 is qvga so its rom would be very useful for opal.
[Touch Viva, MDA Basic ROM Development] ivanmmj:
There already are some files from the Mega in the kitchen. The Mega files do not work as well with the Herald, Artemis or the Hermes. That is why I add all the files; to make sure that the kitchen remains compatible with every device.
[Touch Viva, MDA Basic ROM Development] jagan2:
Success

Hey ivanmmj i downloaded the file with the mirror i made actually it will not work but if u rename the downloaded file with anything.rar or .7z And it will work.

yeappy
[Touch Viva, MDA Basic ROM Development] ivanmmj:
Yea, you didn't name the files the same way I did and you forgot to add the .7z after every file. As long as everyone knows to do that, they'll be fine.
[Touch Viva, MDA Basic ROM Development] jagan2:
ivanmmj i liked the options in extra button in evk there was test1 something.. here oem to ext extra great but can u make one thing clear after converting oem package to ext it says press any key to show the files that is converted one when i click it takes me to user/download there nothing.