[SOLVED] What is required for changing a ROM base? - Windows Mobile

For HD2 ... for example, changing from 2.10 to 3.
I have replaced the OEMXIPKernel, now the ROM is not working anymore. (freezing on the second splash where the red info is displayed) The info showes the newer rom version, but it wont go any further. Is there something else that i need to replace?

No ideas on this? I thought it should be an easy question ....

i'm almost sure about it that u don't need to change MSXIPKERNEL... only OEMXIPKERNEL wil do.... another very very very quick way is ...exchange only nk.exe!

kurniawan77 said:
i'm almost sure about it that u don't need to change MSXIPKERNEL... only OEMXIPKERNEL wil do.... another very very very quick way is ...exchange only nk.exe!
Click to expand...
Click to collapse
I tried changing nk.exe, as well as OEMXIPKERNEL ... it just doesnt work. This time it goes a bit further, but it freezes on the welcomehead image.
any more ideas?

Shu. said:
I tried changing nk.exe, as well as OEMXIPKERNEL ... it just doesnt work. This time it goes a bit further, but it freezes on the welcomehead image.
any more ideas?
Click to expand...
Click to collapse
You need to change OEMXIPKernel and sometimes OEMDrivers/OEMDriversHigh. If you changed EXT packages you also have to recmod some files to avoid the ROM hanging during boot.

Second splash screen with red info?? What do you mean by that?

airxtreme said:
You need to change OEMXIPKernel and sometimes OEMDrivers/OEMDriversHigh. If you changed EXT packages you also have to recmod some files to avoid the ROM hanging during boot.
Click to expand...
Click to collapse
Thanks for the reply, I will try it now and report back
ai6908 said:
Second splash screen with red info?? What do you mean by that?
Click to expand...
Click to collapse
I mean the screen where it displays information about radio, protocol and ROM version in red

airxtreme said:
You need to change OEMXIPKernel and sometimes OEMDrivers/OEMDriversHigh. If you changed EXT packages you also have to recmod some files to avoid the ROM hanging during boot.
Click to expand...
Click to collapse
It did work! thanks a lot. problem solved

Shu. said:
It did work! thanks a lot. problem solved
Click to expand...
Click to collapse
what exactly have you done to fix it?
You need to change OEMXIPKernel and sometimes OEMDrivers/OEMDriversHigh. If you changed EXT packages you also have to recmod some files to avoid the ROM hanging during boot.
Click to expand...
Click to collapse
witch files have to be recmoded? i only know about ntfconfig

Related

Improve FM Radio Library Build 103.816

I think this FM Radio is improved as far as reception concerned. Less interference noticed overall. Back up the current library (just in case you don't like this one) from the Windows directory and replace it with the files in the zip.
Where does it come from ?
plopplop said:
Where does it come from ?
Click to expand...
Click to collapse
From udk's latest ROM
Is there a possibilitie to change the fm radio with a working wm6.1 rom already flashed because when i try to copy the files over the files on my device i get a error that i cant override them.
Ajacied410 said:
Is there a possibilitie to change the fm radio with a working wm6.1 rom already flashed because when i try to copy the files over the files on my device i get a error that i cant override them.
Click to expand...
Click to collapse
use total commander or resco explorer. Either will over-write the libraries.
It would be great to make a cab file out of it. Could anybody help with it?
mffu said:
use total commander or resco explorer. Either will over-write the libraries.
It would be great to make a cab file out of it. Could anybody help with it?
Click to expand...
Click to collapse
That depends - what are all the needed Registry entries ? It's simple enough to have all the files in the zip CAB'd to install in \Windows, but are there Registry entries needed beyond these ?
i tried it yesterday.Copy all files in Windows folder with resco,check version and see version number is ok.I listened to radio all night and havent a problem
ianl8888 said:
That depends - what are all the needed Registry entries ? It's simple enough to have all the files in the zip CAB'd to install in \Windows, but are there Registry entries needed beyond these ?
Click to expand...
Click to collapse
This library is complete. You can unzip it to the storage card, tap on the FM Radio.exe and it will work. I believe we need a cab maker. That type of program writes everything into the registry during the installation.
Thanks. I will try this one tonight ... ;-)
mffu said:
I believe we need a cab maker.
Click to expand...
Click to collapse
Here you go.
Tested. Works.
Sascha
The PDAViet rom also has version 1211.721 which also has better reception than the one on the stock rom. Now I can use my favourite headset which had poor reception, maybe due to shorter length than some crappy one I had
SaBo said:
Here you go.
Tested. Works.
Sascha
Click to expand...
Click to collapse
Doesn't work on my Cruise. Stock ROM. The App doesn't want to start.
Neither the cab not the zip works. I thought that my sprite backup would have the original Files from the rom,it does not. Does anyone have the stock radio files to get my radio working again?
TIA!
EDIT: It looks like I have lost the ability to launch the radio app. At this point, I really don't want to do a hard reset. Don't apply this update unless you are willing to lose this function.
victoradjei said:
The PDAViet rom also has version 1211.721 which also has better reception than the one on the stock rom. Now I can use my favourite headset which had poor reception, maybe due to shorter length than some crappy one I had
Click to expand...
Click to collapse
this is the default version that i have on my HTC Polaris/Cruise.
I'd like to backup my files before copying the new one but can't copy fms_api.dll, even using Resco explorer...
Doesn't work on my Cruise. Raramomo ROM. The App doesn't want to start.
Has somebody a cab of the original radio ?
LIPA said:
Doesn't work on my Cruise. Raramomo ROM. The App doesn't want to start.
Click to expand...
Click to collapse
What application doesn't start?
The CAB can only be installed if you turn certification off.
I don't know if this is possible with all stock ROMs.
Sascha
SaBo said:
What application doesn't start?
The CAB can only be installed if you turn certification off.
I don't know if this is possible with all stock ROMs.
Sascha
Click to expand...
Click to collapse
The FMRadio.exe does not start. The cab was installed properly without issue.
mffu said:
That type of program writes everything into the registry during the installation.
Click to expand...
Click to collapse
Yes, I know that - it was the point of my post.
But what I asked is: "Are there any other Registry entries that need updating ?"
The answer seems to be - apparently not, since another post reported it as working by just copying the unzipped files into \Windows ... but other posts reported this as not working.
Generating a CAB is easy of course, making sure it actually works may be harder.
E.Bonobox said:
this is the default version that i have on my HTC Polaris/Cruise.
Click to expand...
Click to collapse
The FM Radio I posted is better than the PDAViet's one. I have less interference or static after I upgraded to it. I am on PDAViets's 06 build and I get a clear and crisp signal off the stations I had the crappy static with the original build.
And YES, you got to have the security policies changed in order to overwrite some files in the Windows directory. Search for the SDA Application unlocker. That should fix the problem with upgrading.
In my first post I mentioned about backing up the original files. If you happened to fail doing so, try to find Dutty's FM Radio cab.
Thank you!

Restore Original Pop Out Scroll Bar

Hi Guys,
I'm using the Dusk theme and bars etc.. Once I'd installed I noticed that the Pop Out scroll bar had vanished. This I thought was an extremeeeeeely useful setting....
So I hard reset and dumped the today reg from HKCU, after a little messing about figured that I'd just import the reg keys from the original settings. Here are the keys
[HKEY_CURRENT_USER\Software\Microsoft\Today\ScrollBar]
"ScrollBarThumbThemeImage"="\\Windows\\HTCblack_scrollbarThumb.png"
"ScrollBarThumbThemeImageBottomMargin"=dword:00000022
"ScrollBarThumbThemeImageLeftMargin"=dword:00000008
"ScrollBarThumbThemeImageRightMargin"=dword:00000008
"ScrollBarThumbThemeImageTiled"=dword:00000000
"ScrollBarThumbThemeImageTopMargin"=dword:00000022
"ScrollBarTrackThemeImage"="\\Windows\\HTCblack_scrollbarTrack.png"
"ScrollBarTrackThemeImageBottomMargin"=dword:00000000
"ScrollBarTrackThemeImageLeftMargin"=dword:00000000
"ScrollBarTrackThemeImageRightMargin"=dword:00000000
"ScrollBarTrackThemeImageTiled"=dword:00000000
"ScrollBarTrackThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImage"=""
"ScrollBarUpArrowButtonDisabledThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImage"=""
"ScrollBarUpArrowButtonSelectedThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImage"=""
"ScrollBarUpArrowButtonThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonThemeImageTopMargin"=dword:00000000
I'm sure there is a genius in here that could turn this into a cab. Otherwise, copy the text save in a text file add "Windows Registry Editor Version 5.00" as the first line of the text file.
Rename as a .reg file. Import with your preferred reg tool.
In recent posts I've been berated for my efforts to help. I'm no genius, but I have tried this and it's working on my o2 device.
BACKUP BEFORE TRYING. EITHER THE REG ENTRIES OR THE ENTIRE DEVICE
Hope this helps someone
remove .txt from the attached file.
BIG Thanks to johncmolyneux for the cab.
It doesn't work for me. I changed the theme to one of the other pre-installed ones and set the registry values as described above, but there was no change (after a soft reset).
I have made a cab file, but I'm not gonna upload it till we know why it didn't work and I've fixed it.
Did you import all of the values or change a few?
I tried the change a few initially and all I got was the original original (i.e.wm5) scrollbar.
When I imported the file in the first post it worked. These were the only changes that I'd made.
Do you have the original ROM?
The Pop out images are in the windows directory named "01THUMBxxx"
Neville.Holland said:
Did you import all of the values or change a few?
I tried the change a few initially and all I got was the original original (i.e.wm5) scrollbar.
When I imported the file in the first post it worked. These were the only changes that I'd made.
Click to expand...
Click to collapse
The Dusk theme isn't one of the pre-installed themes is it? Did you try it with one of them?
I didn't..... I only used the HTCBlack theme (Which I think it set by default).
I therefore also don't know if the Pop Out Bar is present in the other themes.
I'm going to do a backup and try another theme.
Confirmed working on the DVF Green Theme
Confirmed working on the Classic Blue Theme
Works perfectly, thanks!
There's a lot of misplaced spaces in what you posted, after removing them, it works.
Nvm: comment removed.
That's how it pasted. they shouldn't be present in the txt file.
Neville.Holland said:
Confirmed working on the DVF Green Theme
Confirmed working on the Classic Blue Theme
Click to expand...
Click to collapse
Okay - I'll recheck the cab file then. It must be doing something wrong.
johncmolyneux said:
Okay - I'll recheck the cab file then. It must be doing something wrong.
Click to expand...
Click to collapse
Did you do it from the text file or copied from the screen... reference freyberry's comment...
Neville.Holland said:
Did you do it from the text file or copied from the screen... reference freyberry's comment...
Click to expand...
Click to collapse
I just read it from the screen - it's the simplest way to then recreate the structure in Visual Studio. I've already had spaces in my posts before now, so I was aware of that issue.
Anyway, I've fixed the cab file and it works a treat now, so I'll send you a link to it so you can download it and attach it to the 1st post, rather than have it here on the second page.
The Cab?
Could you you create a cab or still having error?
johncmolyneux said:
I just read it from the screen - it's the simplest way to then recreate the structure in Visual Studio. I've already had spaces in my posts before now, so I was aware of that issue.
Anyway, I've fixed the cab file and it works a treat now, so I'll send you a link to it so you can download it and attach it to the 1st post, rather than have it here on the second page.
Click to expand...
Click to collapse
gsidhom said:
Could you you create a cab or still having error?
Click to expand...
Click to collapse
I've created the cab, uploaded it and sent a link to Neville.Holland so he can post it in the first post, rather than have it in the middle of the thread.
But I guess since people may want it straight away (and he's not currently online), I can post it here and just remove it when he does his thing later.
Thank You For Effort
Thank you very Much,
By the way I'm Still An HD User But I will Try it on mine
johncmolyneux said:
I've created the cab, uploaded it and sent a link to Neville.Holland so he can post it in the first post, rather than have it in the middle of the thread.
But I guess since people may want it straight away (and he's not currently online), I can post it here and just remove it when he does his thing later.
Click to expand...
Click to collapse
gsidhom said:
Thank you very Much,
By the way I'm Still An HD User But I will Try it on mine
Click to expand...
Click to collapse
I think this is a windows 6.5 thing, so if you're still on 6.1 it probably won't do anything, but I'd be interested to know what happens
Prted HD2 Rom
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
johncmolyneux said:
I think this is a windows 6.5 thing, so if you're still on 6.1 it probably won't do anything, but I'd be interested to know what happens
Click to expand...
Click to collapse
gsidhom said:
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
Click to expand...
Click to collapse
Check the windows folder for a series of images starting 01Thumbxxx. I suspect that it's a little more in-depth than a few images.
gsidhom said:
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
Click to expand...
Click to collapse
That can soon be fixed
Edit:
The second one is there - it's just a bit hard to see
Thanks for the .cab, johncmolyneux!
Hope you don't mind if I add it to the add ons for my ROM?

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

[Problem] Rom stop at end of RUNCC

Hello my friends,
I have a problem on my LEO.
I have updated my cooked rom with some EXT from the last OOBE Rom, and my rom stop when the progress bar of runCC is complete.
I just have changing some EXT :-(
Have you one idea about the package that cause this problem ?
Thanks a lot my friends,
regards,
Nixeus
I'm faced with the same problem and could not find a solution for it. check your operatorpkg. maybe there is something wrong.
Nixeus said:
Hello my friends,
I have a problem on my LEO.
I have updated my cooked rom with some EXT from the last OOBE Rom, and my rom stop when the progress bar of runCC is complete.
I just have changing some EXT :-(
Have you one idea about the package that cause this problem ?
Thanks a lot my friends,
regards,
Nixeus
Click to expand...
Click to collapse
If sometimes RunCC balks at installing certain cabs. If it can't install a cab, it will not allow the device to reboot. It will simply act as if a hard reset was ordered on the next start-up.
i have no cab installation setup during runcc process
jwzg said:
If sometimes RunCC balks at installing certain cabs. If it can't install a cab, it will not allow the device to reboot. It will simply act as if a hard reset was ordered on the next start-up.
Click to expand...
Click to collapse
Yeah, this is most likely the case. Search for all config*.txt and check its entries and ensure the referenced files do exists. After it hangs at the progress bar and if you wait long enough, it may prompt you on which cab is missing. I just had this issue yesterday. My fileop txt was missing, and removing that entry fixed it for me.
Did you recmod:
..\EXT\LEO\2.13_TmoUS\LEO_External_Packages\Notification Enhancement v3.5.20161429.00\files\NTFConfig.dll
check this again and all referenced files are present. any other idea?
EDIT: Problem solved. I removed the SQM AUTOUPDATE and FWUPDATE and included DUMMY SQM and DUMMY FWUPDATE.
After i included SQM FWUPDATE and AUTOUPDATE the ROM bootes as normal.
There must be something wrong with my DUMMY Packages
EDIT2: DUMMY Packeges were not the cause. I started over with a clean kitchen and started from scratch. cant say wich packages caused the problem
tidus18 said:
Yeah, this is most likely the case. Search for all config*.txt and check its entries and ensure the referenced files do exists. After it hangs at the progress bar and if you wait long enough, it may prompt you on which cab is missing. I just had this issue yesterday. My fileop txt was missing, and removing that entry fixed it for me.
Click to expand...
Click to collapse
Thanks a lot for your answer, i just have added some EXT and i have this problem.
Maybe it's with the number of modules ?
I will try to remove some packages...
If you have another idea about the packages which make this problem, please tell me
Thanks a lot,
regards,
Nixeus

[Q] quick links are missing

hi on my home screen the quick links icons i cant add,theres supposed to be 9 but 2 are missing,i can remove them but cannot add or change any of them,any ideas?
i dont mean the quick launch icons at the bottom i mean the 9 icons/photos on the homescreen..thanks for looking
restart your htc... and remove each of them and add again from contacts or other.. may be u can add contacts pic.. fav.. etc
Hi, I have the same trouble. This solution doesnt work:-/
thanks but doesnt work for me either,im left with 2 blank spaces now out of 9 quick links,cannot add to either of the blank ones
BATFINK74 said:
thanks but doesnt work for me either,im left with 2 blank spaces now out of 9 quick links,cannot add to either of the blank ones
Click to expand...
Click to collapse
Anyone has some advice exept reinstall?? Still doesnt work:-/
Try this should solve the problem with the icons .... and why so many people avoid the Hard-Reset? Hard-Reset is cool
15MA1L said:
Try this should solve the problem with the icons .... and why so many people avoid the Hard-Reset? Hard-Reset is cool
Click to expand...
Click to collapse
Thanks for help, but it didnt work:-/
r.cervenka said:
Thanks for help, but it didnt work:-/
Click to expand...
Click to collapse
Hola, the remove qtc cab is so you can change the icons for some of the programs..., but for your QuickLinks issue, please check your registry:
HKLM\Software\HTC\Manila\Home
There you have 0 - 8 meaning the values and keys for all 9 quicklinks ;-)
Check them and see if two (2) of these are corrupt.... If so, then check the entries of the good ones and adjust the "bad" ones
Probably some flunked or failed instal that screwd up, or what else did you instal?
What ROM are you running? Stock? If it is a custom ROM, inform your chef
BHS Interceptor said:
Hola, the remove qtc cab is so you can change the icons for some of the programs..., but for your QuickLinks issue, please check your registry:
HKLM\Software\HTC\Manila\Home
There you have 0 - 8 meaning the values and keys for all 9 quicklinks ;-)
Check them and see if two (2) of these are corrupt.... If so, then check the entries of the good ones and adjust the "bad" ones
Probably some flunked or failed instal that screwd up, or what else did you instal?
Click to expand...
Click to collapse
Yes, in registry should be 9 files from 0-8, but the file number 2 is missing at all. That is probably the problem. I just don't know how to add a "file 2" manually, because I don't know ContactFavorType. The rest of values should be ok..
It was caused by some error during uninstalling of a official Facebook application distributed via Marketplace. So on the position 2 (file 2 in the regitry) was Facebook, but right now there is nothing:-D
r.cervenka said:
Yes, in registry should be 9 files from 0-8, but the file number 2 is missing at all. That is probably the problem. I just don't know how to add a "file 2" manually, because I don't know ContactFavorType. The rest of values should be ok..
It was caused by some error during uninstalling of a official Facebook application distributed via Marketplace. So on the position 2 (file 2 in the regitry) was Facebook, but right now there is nothing:-D
Click to expand...
Click to collapse
Hola, simply check for the value on the other ones... my values differ since I have CHT and a cooked ROM, but if you want, take a look at my original set up without CHT, right after flashing the ROM - The ROM Cook only set the first three links as you will see at the bottom of the file ;-)
BHS Interceptor said:
Hola, simply check for the value on the other ones... my values differ since I have CHT and a cooked ROM, but if you want, take a look at my original set up without CHT, right after flashing the ROM - The ROM Cook only set the first three links as you will see at the bottom of the file ;-)
Click to expand...
Click to collapse
Yes, you are the guy Now it works, thank a lot
r.cervenka said:
Yes, you are the guy Now it works, thank a lot
Click to expand...
Click to collapse
You´re welcome. Glad it helped you

Categories

Resources