[Problem] [ERROR]Please check HTCLOG - Windows Mobile

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...

Related

[Problem] Notifications & Sounds Menu Bug

Hi,
The problem:
When entering the notifications & sounds menu in wm 6.5.5 the right ringtone shows up, when choosing another one and playing it, no problem occurs. But when I want to exit the dialog via OK, all ringtones in the menus are skipped through until the default windows-ring01 ringtone is on top of the list. The dialog is not closing that way, cause every time I want to, the whole skipping happens again and the default ringtone is set.
I used the search quite excessively, but didn't find a solution. I know I came across this error before and I'm pretty sure I was able to fix it, but I have no idea how.
Anybody able to point me in the right direction?
thanks
Do you have a native kernel (WM6.5) or non native kernel (WM6.1)? If it is non native, then recmod browsingie files, and the error should go away...
Did you cook in DRMMiddleware? Maybe other DRM packages are also needed.
That usually happens when you have DRM packages cooked in. Remove them...
This happened to me and my Kaiser when i tried to build a rom with different SYS and MXIPKernel.....hope this aint your situation.
Thanks for the hints! I switched to other SYS & XIP - its working fine now.
Just for clarification:
- Native 6.5
- DRM is build in right now
So it seems it was the different XIP and SYS I was using.
Narrowed it down to the boot.rgu and boot.hv files in the XIP. Didn't take a closer look, but I can say for sure that some setting in there is causing the bug.
chalid said:
Narrowed it down to the boot.rgu and boot.hv files in the XIP. Didn't take a closer look, but I can say for sure that some setting in there is causing the bug.
Click to expand...
Click to collapse
That's where some of the DRM codecs get referenced. Most likely the one you had before, had those references removed
this can be fixed by adding "MediaOSModules" package to sys from another sys from the same com build,and deleting "MediaOSFiles" package from sys.
In some cases if I add mediaos files as modules, then utube will not play. But it plays fine with them as files!

[SOLVED] Damned ringtones!!!

I hope someone of you could help me! I'm cooking roms for xperia X1 with last EVK on windows XP!
I'm now using build 23568 or 23569 and a strange thing is occurring:
I've cooked successfully a pair of rom and then I needed to change something.... after that all my roms with that builds suffer by strange trouble:
when selecting a ringtone for the incoming call (I can preview its sound) and then hit OK to confirm it all the ringtones roll up and down for a second on the screen and then the default ring (windows-phone) is autoselected and no chance to close that window....... so I can't select different ringtones.
I've tried to revert back the change I made but the same happens. If I try to cook an older build I have in EVK it's working fine!!! I've tried to completely remove 23569 build and put it on from beginning but the same thing happens.....
Please help me! This is driving me crazy!!! I've searched up and down on this and other forum but nobody seems had this issue before.....
Does windows media player work? If it doesn't then it's a XIP issue: make sure you used the latest msxipkernel package.
I had that issue twice long ago. One time is was xip issue, the other time a bad lockstreamdrm package
Thanks a lot for the help! It was a xip issue..... I don't know why the msxipkernel had been modified.... restored the original one and it works!!
Thanks again.
Another XIP-file case solved!
I am having this exact same problem.....
i replaced the XIP and lockstreamdrm on first boot i was able to go into phone options and hear the ring tone without the corrupt error... but after just a bit i get a phone call and its silent....
i go back to phone options and try to play the ringtone and get the corrupt error...
After that i was doing some bmp replacements within the phcanimages and phcanimages2 and after replacing those to dll's on my device (they were the same as the ones cooked in, just updated bmps) i can choose ringtone without error and it rings on incoming calls...
any ideas?
did a clear storage and when phone came up i was able to select ringtone without error... was not able to try a call then because i had to activate phone..
after soft reset i am able to choose and hear when call is coming in..
so maybe the clear storage did it? i will report back after cooking again
This is most likely due to using the Lockstream DRM packages in EXT without the corresponding registry entries at the bottom of boot.rgu. Don't ask me why they put reg. entries from one program in two different places.
jwzg said:
This is most likely due to using the Lockstream DRM packages in EXT without the corresponding registry entries at the bottom of boot.rgu. Don't ask me why they put reg. entries from one program in two different places.
Click to expand...
Click to collapse
How can i fix?
after a few hours of ringtones working fine, i tried to go back into ringers and get the same corrupt error.......
Delete the Lockstream DRM packages (NOT Lockscreen) out of your ROM and see if it works normal.
jwzg said:
Delete the Lockstream DRM packages (NOT Lockscreen) out of your ROM and see if it works normal.
Click to expand...
Click to collapse
gotcha
trying now
I removed the Lockstream DRM packages from my kitchen recooked and still same error...
i also put fresh SYS & XIP's into kitchen...
im using the same kitchen i always have and didnt change anything that i havent changed before.... been cooking my BigMaxsense ROM for months now without this problem..
Thanks for any help
Okay just wanted to post what was causing my problem
i stripped my ROM clean and only put the essentials into it and started adding things a few at a time..(guess i should have done this to start with)
found out that Microsoft.Voice.Command.v1.6.21725 was the root of the problem.. removed it and everything works fine..
thanks to all that helped!

[Q] The files inside modules are required for cooking 6.1?

Hello ppl, after so much cooking in 6.5 i decide to play a lil into 6.1... well i never cook for 6.1
Ok here is teh question as the title says... i jump into 21057 build 6.1 and I have a weird thing that is annoying... A mouse pointer (a lil arrow) does any body knows how to get rid of that arrow in my screen?
thanks a lot
Im usin HTC Hermes 6.1 build 21057 QVGA 0409 EVK 1.8.2
So 71 views and none idea? OMG i need to start over with an old build... maybe is a feature in the gwes shell or other core file
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
to my experience - NO
i did always delete all of them..
did you track your crash down to OEM/SYS?
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).
Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
Farmer Ted said:
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).
Click to expand...
Click to collapse
Thats true, my 6.1 rom is a mess i will try that thanks
Laurentius26 said:
Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
Click to expand...
Click to collapse
mmm interesting where can I learn more about that Changes you talk about?
to be homest i have the same thing
when i look at modules i have a dll in it called the same as folder
i have this since the beginning i started cooking and thought it whas meant this way but here im reading its not:-o
will the rom become faster if i delete all the dll's from the modules?
definetly gonna give it a go tomorrow:-o
yes... we are wrong, as the kitchen warns us when in SYS and EXT is a module with a file inside... but it dont happends when we got them in OEM.
The idea to have modules instead of files is cause the file is already recmoded when the cooking process starts at IMGFS merging (maybe im wrong) doing the recmod into slots by the reloc tool... so... in 6.1 the Greloc did it in the oem and goes wrong, and the same happends for WMreloc for 6.5 cooking.
and yes having modules allows us to have correctly recmoded files at the end to have faster roms so... the files inside modules is a wrong way to cook
i will try to dump again the stock... in OSkitchen zero... then i will add it into my 6.1 kitchen... but something is weird in my case... cause my device dont has stock rom for 6.1 ( we have wm6 shipped roms) but i will try it anyways
It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate
seeM_ZA said:
It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate
Click to expand...
Click to collapse
muchias gracias for this s my entire ext folder is full of files inside modules:S
:verry nice program and verry quick
edit2: gonna flash my new rom without the files inside modules and see what happens
i deleted them from the oemdrivers folder and all the ext packages(im hoping for some nice extra speed)
edit3: just looked at the kitchens i made for tp2 and leo and they have the exact same thing files in modules in ext packages and oemdrivers:s
and the strange thing none of the kitchens told me this and all gave nice working roms where evrything works like it should:S
edit4: hmmm looks like weather animation is slower after deleting all the files in modules:s
Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.
seeM_ZA said:
Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.
Click to expand...
Click to collapse
for the weather animation im quite sure as yesterday i let it run the weather animation for rain ten times after eachother and it whas ten times smooth
now i did it 5 times and 5 times with stuttering in it:s
Strange :? You sure you didnt change anything else?
seeM_ZA said:
Strange :? You sure you didnt change anything else?
Click to expand...
Click to collapse
100% sure
i downloaded the program you mentioned and let it run over the entire ktichen so all files in flders with the same name got deleted then i cooked the rom and flashed it
gonna reflash the rom i used before i deleted all those files to doucble check if im right about the weather animation but im 99% sure about the outcome
Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe
seeM_ZA said:
Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe
Click to expand...
Click to collapse
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower
miniterror said:
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower
Click to expand...
Click to collapse
Haha, I hope it works out for you bro
I tested out my weather animations and they're perfectly fine, without the dlls in modules. Im running 21909 and sense 2016 CFC'ed (from Leo 3.04) on TP2.
So... laurentius, how can I use Greloc instead of WMreloc in EVK to cook 6.1 ROMs???
i have this using WMReloc in a vanilla ROM 6.1
Memory Map...
SLOT 0: 0x02000000 - 0x01660000 (END: 0x00060000, 64 MODULES)
0x02000000 - 0x01fe0000 - ROM 0
0x01fa0000 - 0x01e20000 - ROM 1
SLOT 1: 0x04000000 - 0x02020000 (END: 0x02020000, 253 MODULES)
RAM IMAGE: 0x80000000 - 0x8029cc34
RAM: 0x8029d000 - 0x802cc000 - Used for kernel modules
0x802cc000 - 0x83a00000 - 55 MB free
... done!
I guess this 64 Modules in slot 0 are causing troubles
I'm not too familiar with 6.1 but what I do know is you want as little modules as possible in slot 0, so ideally you want no modules there.
EDIT: Wrong info here, my bad.
All the best

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.

[SOLVED] Initflashfile.dat problem: device frozen until taskbar is pressed.

Hi,
I've been facing the following problem on my ROM: After a fresh flashing or hard reset, the device is unresponsible, and the start menu does not start and subsequently Manila doesn't start, until the taskbar is pressed.
Any ideas?
could it be something on the kitchen (osKitchen Zero 1.33.5) or OEM packages?
EDIT 4/OCT:
Solved.
I've started from scratch using LEO 3.14 initflashfiles and removing/changing only the necessary, and testing after each change.
Saved as Unicode UTF-16 with CR+LF (first 4 digits removed with HEX editor)
I didn't removed/changed the links that didn't create a shortcut. Only those which were creating links on the wrong place.
EDIT 1/Oct:
After rebuilding my whole kitchen, found the problem is related to Initflashfile.dat.
The dumped initflashfile.dat works without problems, but when I modify it, the problem appear.
I was editing using notepad2.
After found the problem, I searched the forum and found that after modification it needs to be HEXedited removing 4 first digits:
4. Install Hex Workshop Trial if you havent already. Open initflashfiles.dat in the hex editor.
The first 4 digits should say FFFE or something like this. Highlight those first 4 numbers and right click and delete. This is the header written in by notepad. This HAS to be removed for you initflashfiles.dat to work correctly. Then save.
Click to expand...
Click to collapse
But even after removing these digits I still have the problem.
Can someone give me some advise about how to modify the Initflashfile.dat?
I've attached the 2 files for your reference.
Thanks in advance.
Brgds
I use LockScreen from Huasan in COM3 without problems. It also may interact with your lockdevice 1.6 and you must put out Lock Screen App Launcher from Leo. Perhaps is this. I had this issue but I don´t remember why was. Sometimes was custom icons or backgrounds like "StartMenu_Background_Screen_480x800.png" & "StartMenu_Background_Screen_800x480.png". I didn´t be able to change these png´s. Get Lucky
This issue is driving me crazy.
I've just cook a ROM witout any external package only Sys and OEM and the problem is still there.
Also checked with a COM 2 build and the same issue.
I'm using osKitchen Zero v1.33.5, I've tried reimporting the original ROM and recoocking it with the same issue.
Any idea what else I can check?
Could it be a kitchen related problem?
I would suggest cooking with a different kitchen, but same pkgs and see if there is an issue. Sometimes kitchens do cause bugs...
Hi,
Finally managed to find what file was producing the problem.
I modified the first post and attached the files.
Hope someone can help me!
thanks in advance.

Categories

Resources