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.
Related
Guys, Have been searching the site for a couple of weeks now and cant find a solution to my problem.
I work for a company that deals with alot of XDA2 units, so far I have managed to develop a custom extended rom that works fine, but have not been able to find a way to remove links from the start menu and the program menu. seen several threat on the site but no solution. The links have to be removed if a hard reset occurs. At present It has to be done by cloning an image onto the unit (1600 in total)
Any help would be appreciated.
popeye
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
M4io said:
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
Click to expand...
Click to collapse
I'm using Restorator utility (search through the forum) to do the aforementioned things and much more. Works flawlessly with new Second Edition rom
thx, I completely forgot about that utility. I will defenitely give it a try
http://forum.xda-developers.com/viewtopic.php?t=9333&highlight=restorator
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
Hi All
Im looking for Xperia logo animation on the startup, I dont really know the name of the file, but it is the screen that comes after the sony ericsson logo If i recall.
Thanks in advance
theres a cab with it i posted here, the cab just sticks the file in windows and makes sure the reg is pointing to the right place
http://forum.xda-developers.com/attachment.php?attachmentid=140838&d=1230499556
fards said:
theres a cab with it i posted here, the cab just sticks the file in windows and makes sure the reg is pointing to the right place
http://forum.xda-developers.com/attachment.php?attachmentid=140838&d=1230499556
Click to expand...
Click to collapse
Thank you very much, ill test it when I get back home
just thought, the gif is on my x1, :doh
zipped to overcome the gif file limit
unzip and stick in the windows folder
fards said:
just thought, the gif is on my x1, :doh
zipped to overcome the gif file limit
unzip and stick in the windows folder
Click to expand...
Click to collapse
oh cool thanks man, how does this differ from the cab file?
its just the gif file, you can change the setting with advanced config or manually editing the registry
to point to the file
hklm/software/htc/htc animation startupgif /windows/semc1904.gif
Apologies for hijacking the thread slightly (it looks nicely resolved to me though), does anyone know where the initial Sony Ericsson image is stored - i.e. the one that greets you when you first fire up the Xperia?
I found SEMC2904.bmp in the Wndows folder which is exactly what the startup screen looks like, but even if I change that file the startup image stays the same.
Any ideas? Or failing that, is there a registry setting to change the path for the initial startup image?
Mr Anderson said:
Apologies for hijacking the thread slightly (it looks nicely resolved to me though), does anyone know where the initial Sony Ericsson image is stored - i.e. the one that greets you when you first fire up the Xperia?
I found SEMC2904.bmp in the Wndows folder which is exactly what the startup screen looks like, but even if I change that file the startup image stays the same.
Any ideas? Or failing that, is there a registry setting to change the path for the initial startup image?
Click to expand...
Click to collapse
That's a bootsplash, not so easy to change, best done with a rom kitchen.
fards said:
That's a bootsplash, not so easy to change, best done with a rom kitchen.
Click to expand...
Click to collapse
Okey dokey - thanks for a helpful answer. I'll leave it be.
As a former Palm and Symbian user I still have much to learn about Windows Mobile, so I'm grateful for your assistance.
Can't restore xperia animated logo
Hi there,
been trying to get back xperia animated logo but no luck, seems that registry keys are not enough.
I've messed witk Mainsplash and Subsplash and successfully changed both by modifying htc rom tool settings and playing with nbimg, but xperia animated logo doesn't have anything to do with bootsplash, it's managed bt registry and no need to mess with reflashing inital splashes.
Here's what occurs at wm boot:
1. Display Mainsplash
2. Display Subsplash
3. Display Animated logo
4. Display Welcomehead*.png
I 've also tried playing with registry keys which were used successflly by HTC prophet users to display boot animation (see : http://forum.xda-developers.com/showpost.php?p=1719336&postcount=19)
but still no luck...
Has anyone succesfully restored Xperia boot logo ?
EDIT: Solved!
Hi there,
been trying to get back xperia animated logo but no luck, seems that registry keys are not enough.
I've messed witk Mainsplash and Subsplash and successfully changed both by modifying htc rom tool settings and playing with nbimg, but xperia animated logo doesn't have anything to do with bootsplash, it's managed bt registry and no need to mess with reflashing inital splashes.
Here's what occurs at wm boot:
1. Display Mainsplash
2. Display Subsplash
3. Display Animated logo
4. Display Welcomehead*.png
I 've also tried playing with registry keys which were used successflly by HTC prophet users to display boot animation (see : http://forum.xda-developers.com/showpost.php?p=1719336&postcount=19)
but still no luck...
Has anyone succesfully restored Xperia boot logo ?
EDIT (14/01/2009):
Finally managed to get this stuff back, registry keys were not correct.
Here is a link for all those who want to get back their Xperia Boot Logo.
Unzip this file in your kitchen's OEM folder, it is ready to be cooked:
http://www.4shared.com/file/80625819/778c01d2/Xperia_stock_startup.html
(if you want to get it back without cooking anything, just put the file in \windows
on your device and edit your registry according to included keys in .rgu file)
Hope someone will find this usefull.
Cheers.
the reg key works prefectly in mine and on several other wwe roms are you on a french rom? that may be the problem..
you dont need to start playing with cooking roms just to get the htc animated startup working.
of course the easy way is to use advanced config to choose the gif you want to use.. and thats where i got the reg key from
Thank you for the answer fards, the problem was that at the beginning i was trying to put the wrong reg key which was included in archive posted some posts above.
First reg key i've tried was:
HKLM/software/htc/htcanimation
Tried also with a space between "htc" and "animation" but none worked.
By searching a little i found some htc prophet related posts with registry settings that put me on the right path.
After some unsuccessful tries i found that the following keys did the trick - at least for me -:
"Volumn"=dword:00000000
"WAVFile"="dummy"
"Enabled"=dword:00000001
"GIFFile"="\\Windows\\SEMC1904.gif"
"Priority"=dword:000000C8
As you can see, the keys for playing a wave file when dislaying animation are here too.
Since i'm beginning in cooking stuff - and also in the whole ppc world - and wanted to make an ultralight ROM from my stock french one, i wanted to do everything at hand, in order to improve my understanding of the whole stuff, including little "cosmetic" details as well as critical system tweaks to fit my needs without using a single piece of additional software.
I've edited my previous post according to how i resolved this and included a zip archive to replace the one posted previously, which was including wrong registry settings.
Nice to see what we can achieve by working on various things and exchanging ideas, techniques and advises.
I've learned many thing since i began last week, but still a lot to learn...
Now i can go to the next level...
Cheers and thanks again.
ragnascroutch said:
Thank you for the answer fards, the problem was that at the beginning i was trying to put the wrong reg key which was included in archive posted some posts above.
First reg key i've tried was:
HKLM/software/htc/htcanimation
Tried also with a space between "htc" and "animation" but none worked.
By searching a little i found some htc prophet related posts with registry settings that put me on the right path.
After some unsuccessful tries i found that the following keys did the trick - at least for me -:
"Volumn"=dword:00000000
"WAVFile"="dummy"
"Enabled"=dword:00000001
"GIFFile"="\\Windows\\SEMC1904.gif"
"Priority"=dword:000000C8
As you can see, the keys for playing a wave file when dislaying animation are here too.
Since i'm beginning in cooking stuff - and also in the whole ppc world - and wanted to make an ultralight ROM from my stock french one, i wanted to do everything at hand, in order to improve my understanding of the whole stuff, including little "cosmetic" details as well as critical system tweaks to fit my needs without using a single piece of additional software.
I've edited my previous post according to how i resolved this and included a zip archive to replace the one posted previously, which was including wrong registry settings.
Nice to see what we can achieve by working on various things and exchanging ideas, techniques and advises.
I've learned many thing since i began last week, but still a lot to learn...
Now i can go to the next level...
Cheers and thanks again.
Click to expand...
Click to collapse
i tried all the methods posted on this thread...and is til cant get the animation back up. are there any other ideas?
bknewtype said:
i tried all the methods posted on this thread...and is til cant get the animation back up. are there any other ideas?
Click to expand...
Click to collapse
What is your rom version ? is it a stock one or a cooked one ?
ragnascroutch said:
What is your rom version ? is it a stock one or a cooked one ?
Click to expand...
Click to collapse
stock rom, 1.02.931.3. im not ready to try cooked yet lol
how about edit the startup sound file?
boot logo
ragnascroutch said:
Hi there,
been trying to get back xperia animated logo but no luck, seems that registry keys are not enough.
I've messed witk Mainsplash and Subsplash and successfully changed both by modifying htc rom tool settings and playing with nbimg, but xperia animated logo doesn't have anything to do with bootsplash, it's managed bt registry and no need to mess with reflashing inital splashes.
Here's what occurs at wm boot:
1. Display Mainsplash
2. Display Subsplash
3. Display Animated logo
4. Display Welcomehead*.png
I 've also tried playing with registry keys which were used successflly by HTC prophet users to display boot animation (see : http://forum.xda-developers.com/showpost.php?p=1719336&postcount=19)
but still no luck...
Has anyone succesfully restored Xperia boot logo ?
EDIT: Solved!
Hi there,
been trying to get back xperia animated logo but no luck, seems that registry keys are not enough.
I've messed witk Mainsplash and Subsplash and successfully changed both by modifying htc rom tool settings and playing with nbimg, but xperia animated logo doesn't have anything to do with bootsplash, it's managed bt registry and no need to mess with reflashing inital splashes.
Here's what occurs at wm boot:
1. Display Mainsplash
2. Display Subsplash
3. Display Animated logo
4. Display Welcomehead*.png
I 've also tried playing with registry keys which were used successflly by HTC prophet users to display boot animation (see : http://forum.xda-developers.com/showpost.php?p=1719336&postcount=19)
but still no luck...
Has anyone succesfully restored Xperia boot logo ?
EDIT (14/01/2009):
Finally managed to get this stuff back, registry keys were not correct.
Here is a link for all those who want to get back their Xperia Boot Logo.
Unzip this file in your kitchen's OEM folder, it is ready to be cooked:
http://www.4shared.com/file/80625819/778c01d2/Xperia_stock_startup.html
(if you want to get it back without cooking anything, just put the file in \windows
on your device and edit your registry according to included keys in .rgu file)
Hope someone will find this usefull.
Cheers.
Click to expand...
Click to collapse
how did u change the boot logo using htc tools? can you show me the steps?
I had the same isue
ragnascroutch said:
Thank you for the answer fards, the problem was that at the beginning i was trying to put the wrong reg key which was included in archive posted some posts above.
First reg key i've tried was:
HKLM/software/htc/htcanimation
Tried also with a space between "htc" and "animation" but none worked.
By searching a little i found some htc prophet related posts with registry settings that put me on the right path.
After some unsuccessful tries i found that the following keys did the trick - at least for me -:
"Volumn"=dword:00000000
"WAVFile"="dummy"
"Enabled"=dword:00000001
"GIFFile"="\\Windows\\SEMC1904.gif"
"Priority"=dword:000000C8
As you can see, the keys for playing a wave file when dislaying animation are here too.
Since i'm beginning in cooking stuff - and also in the whole ppc world - and wanted to make an ultralight ROM from my stock french one, i wanted to do everything at hand, in order to improve my understanding of the whole stuff, including little "cosmetic" details as well as critical system tweaks to fit my needs without using a single piece of additional software.
I've edited my previous post according to how i resolved this and included a zip archive to replace the one posted previously, which was including wrong registry settings.
Nice to see what we can achieve by working on various things and exchanging ideas, techniques and advises.
I've learned many thing since i began last week, but still a lot to learn...
Now i can go to the next level...
Cheers and thanks again.
Click to expand...
Click to collapse
Hi all....
ragnascroutch:
I had the same isue
I followed your instructions (modifying de Reg Key only) With all the Keys exactly like you except in the Key
"GIFFile"="\\Windows\\SEMC1904.gif"
Just worked with
"GIFFile"="\Windows\SEMC1904.gif" (only one back slah)
thanks Budie......
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!
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...