[Q] oskitchen - diamond problem - always the same oemxip? - Windows Mobile

hello, first off, i did search but couldn't find anything like this problem at all
intro:
i did successfully install oskitchen and import the latest official build (wm 6.1)
imported a da_g package with the 6.5 23563 build, no problems at all but... the notification area in the top launched the htc notifications panel from that time (a gray screen with some of the icons in bigger size, if you don't remember what it was like i can put a screenshot, it does not matter really to understand the problem though)
"no problem, i can make a new profile with a different oemxip and oem drivers and that will be gone", and so i did, i searched for some kitchens with a set of drivers fitting my needs as reference and made a new profile with those
problem #1:
oskitchen needs the "temporary os.nb", which i don't know how to build it from the files in the project (and indeed cannot find how to do it because the search says "os" and "nb" are too short and would not use them), nor oskitchen build it for me...
so i did a dump from a rom built with the very same oemxip and package configuration (same sys, same packages, same oem drivers, same oemxip) and copied the os.nb
problem #2:
that worked fine... or so i thought: the notification screen was still there
as of now, there is absolutely no files from the original rom dump, but when i cook it the notification screen is still there! it's driving me crazy, how it can be there still??
i wonder if oskitchen does not work work with profiles as i think it does (meaning it always look for the "default" profile?), i don't really know and i'm completely lost as of now
so, my request for help is triple-fold:
#1: is there any way to build the "temporary os.nb" from the files instead of getting it from a rom dump (and so, i can control which things will be in the .nb)
#2: do you have any idea as of why the notification screen does appear yet none of the original files from the diamond rom is there
#3: in the case i cannot get rid of it in the "good" way, do you know how to make the notification screen to not appear anymore (you know, the wm 6.5.x way is more than enough, and less intrusive)
thank you so much

This one should be posted in OsKitchen thread. http://forum.xda-developers.com/showthread.php?t=628948
Closed.

Related

Typhoon wm5 new build developing

As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Hi, Do you have any working (even bugy) WM5 ready to install? I need it to fix my phone and revert back to W2003.
Thanks
Inquiry
Hey Sp3Dev, just wanted to know whats going on with the new build you have been working on. Did you manage to get the help that you were looking for. I just got this device yesterday to use until my Artemis arrives, but I think I will end up keeping it to replace my d600 just because I love customizing my devices. Hope you are still working on a little somthing for my SP3i.
sp3dev said:
As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Click to expand...
Click to collapse
I can help a little. I only use the files already listed in the packages.sof. I don't know how to read the file though. I use Bepe's kitchen. When you seperate the files into OS and LOC, you may find some folders only contain a .dsm file. These are extra folders and can be either deleted, or used for holding additional files. these files should already be listed in the packages.sof. You may have to test them one at a time by using the createOS.exe. Now to rebuild a .dsm file, put the your folder in the OEM folder, and createOS. This will automatically rebuild the .dsm files in the OEM folder. I'm sure there is a more elegant method, perhaps by using the kitchen tools directly, but i don't know how. I recently had to translate a chinese AKU 3.2 set into english, and thats basically the method i used. This post was written w/ the assumtion that you are familiar w/ Bepe's kitchen.
Regards,
Jason
Hello.
How are you trying to create this build? Have you started off with the original Typhoon WM5 Beta, or do you use a "true" WM5 build and try to incorporate Typhoon drivers? I suppose you are doing the latter, which I really hope you'll accomplish!
If you need any help betatesting and stuff, please say so

[Problem] [ERROR]Please check HTCLOG

I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
millski said:
I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
Click to expand...
Click to collapse
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
TMartin03 said:
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
Click to expand...
Click to collapse
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
millski said:
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
Click to expand...
Click to collapse
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
TMartin03 said:
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
Click to expand...
Click to collapse
Tried that, still wouldn't work. If I cook without RunCC the ROM will boot without error, but then the initial customisation doesn't run i.e. no SIM or operator settings are made.
I don't think I'm going to get to the bottom of this so I've started building a new kitchen. Does anyone know which packs from Leo 2.14 will make my ROM TMOUS HD2 compatible? I can't remember...

New HTC Rose @};- Project

Hello everyone!I had started a project for our devices (and yes this mean a holl new ROM) I started this days to make something and I managed to do something but need a lot of help from other users of this section of the forum who have knowledge of ROM cooking,so for those of you that want to help improving this project I want a PM from you.
Use my kitchen, with it you can extract ROMs and cook ROMs without problems... I don't exactly know why you are being so overly excited in the General Hacking Forum, since all that you need is already there, use it!
no the prb. is that i need more support for ex how to extract a .nb image?or how to extract from a ROM the programs that it haves?Because with yours i didn`t manage to do something to different and now i`m preparing the build a new ROM 6.5.3 with new XIP and new SYS
In my kitchen go to TOOLS -> bats -> extract.bat and open it in an editor, it should tell you everything you need to know about extracting roms (the nbimagetool extracts pretty much every *.nbh and *.nb you throw at it). Once the dump is put into packages by the pkgtool, the programs are sorted into those packages (if the cook didn't prevent this for example by deleting the dsm files during the cooking process, in this case all you get is a veeeeery long list of files )...
EDIT: I forgot to mention, I had a lot of problems with the 6.5.3 emulator image, the home screen wouldn't rotate (CHome that is). And I figured that 6.5.3 isn't worth the hassle on non-touch screen WM phones (I am moving to Android soon anyway )
I also had some problems with the SYS when i was trying to make G`reloc and gived me a Skybox language error and stoped,but after I deleted Skybox it worked like a charm .Did you had this to?
That's normal. G'Reloc doesn't support the new modules of WM 6.5 that are allocated to memory slots that don't exist in previous WM versions. So you either remove or recmod the modules or you use wmreloc instead of G'Reloc...
yes i found out that if I remove it everything is ok i removed it with unlocker but now i want to try wmreloc hope it will go without errors
I always used the recmod mehtod, but removing skybox makes sense anyway, because it's available in the market...
Something for you to read on the topic: http://www.techparaiso.com/windows-...memory-and-native-kernels-in-windows-phone-os
So it`s better to remove it because eats lot of memory anyway I don`t use it but I wanted to be included exactly like in the original ROM but in the last days I was thinking to do it different and I will do probably a light version and one customize by my own needs but I would love also to know what the users would want to include,so waiting for some proposals

phonecanvas fixes?

I expect to get lots of 'search' and 'read' answers but hopefully someone will point me in the right direction
I have been searching (and searching) and building and flashing for days and I can't resolve the phoneCanvas issue where I have a scrollbar down the righthand side of the screen. This is what I have done so far:
Using osKitchen I have imported a recent Blackstone ROM (1.56.405.1 WWE)
Replaced the OEMXipKernel with a 6.5 one found on here
Imported a newer Windows Mobile Build (5.2.23138)
Added some applications and registry settings I need
Rebuilt the ROM and flashed it
At this point it works but the dialer is wrong - there is a scrollbar down the right of the screen and I cannot see the CLI of incoming calls.
OK, so I researched this and found that there is a problem with the HTC Phone Canvas. I found lots of replacement Phone Canvas's and have rebuilt the ROM using various ones I have found. The results are always either the same (i.e. scrollbar) or a messed up screen which is a mix between the default Windows Phone dialer and the replacement one.
I have also extracted the phonecanvas (and video dialing if applicable) from other devices and rebuilt the ROM with these but I always get the same results.
I have also tried editing the original phcanrc.dll file (Phone Canvas v3.50.33398.1) to include the 'EXSTYLE = 0x02000000' and again rebuilt the ROM with this but I am still not getting anywhere
I have tried some of the custom ROMs on here and they don't have this issue so I know it can be fixed but I am really struggling. I need a step-by-step guide as to how I fix this please....
Andy

HD2 Leo 3.14 Custom ROM freezing after standby

I have build a custom hd2 rom with oskitchen and xip/sys 28244.
It's working very well.
Now I have added some ext packages found here that seems to be useful. And now the new rom has the following issue: After leo goes to standby by itsself or by pressing the off key and some time later it will not wake up. Buttons are lightened but screen stays black. I have to put the battery out or to reset. Than rom is working again until next standby.
It happens only, if device is in standby for some time. If you press off and then wake up device immediately, all is working well.
Any idea, if this can be result of some added package or some component of the xip/sys build?
Have now found out something:
If I remove the following ext packages from my built rom, the rom works without freezing after going to standby:
HTC Tweaks
AMEBA
Opera Mini 5.1
Google Maps 4.1.1
But If I install those apps as cabs, the rom is working well after installation.
Can it be that they conflict with some built-in package of leo which causes the freezing issue, which is not there if installing the packages?
thunder141, not sure what you mean by HTC Tweaks but if you increased system cache (as it proposed to do somewhere in Leo related threads) to absolutely huge unacceptable meaning - your phone just tries to cache memory...
Get rid of that tweak, or check your Storage Card (maybe format will help) - possibly the system is trying to cache to it and it's fragmented or just too slow....
i mean the app hd2 tweak with standard configuration converted to an ext from the cab
thunder141, am I supposed to know what does that mean - "app hd2 tweak with standard configuration "?
I tweak my roms by myself and never try to have fun with someone's "tweaks compilations"
Can you be more specific? Give me a link to the cab or attach your package for me to have a look.....
sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me
Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
thunder141 said:
sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me
Click to expand...
Click to collapse
af974 said:
Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
Click to expand...
Click to collapse
No, at his page there are hd tweak for other device and hd2 tweak for hd2 (leo). (http://www.montecristoff.com/hd2tweak.htm)
But, as I said, its not only this ext pkg but the others mentioned make my device freeze, too. And if used by cab install, not. And I do not understand the difference for those apps, if they worked when not cooked in.
I decided to put them in my uc_net folder for now and left them out of my rom, so my device won't freeze
before my hd2 got bricked due to my stupidity, i was trying to find solution to freezing issues.
i found out that if cad.dll and wavedev.dll are excluded, no death occurs after sleep. (of course, these dlls are vital for sound, so we cannot exclude them).
so my suggestion would be to first exclude these 2 dlls and include your packages to see if this clash is causing problem and then find compatible version of your packages with these 2 dlls or find compatible dll.
personally, i think these 2 dll have some odd bug with certain versions of windows system.

Resources