Method to attempt to fix the looping reboot issue. - HTC Excalibur

After the removal of duplicate notifications w/ SKTools Lite, removal of the Windows Live service and the FizzWeather fix, I decided to try something else out.
I was reading a thread about dumping ROMS and got to a part that showed me how to access the files on the dumped ROM. I couldn't find any dumped Excalibur WM6 or WM5 ROMS so I used a ROM for the Hermes. I searched the list of dll files within the ROM and found a dll named sdhc_sc2410.dll. I figured I'd copy the SDHC dll from this ROM, add it to my Windows directory and change the appropriate registry entry to point to this file to see if it would fix my looping reboot issue. It didn't. I'd like to get my hands on a WM5 shdc dll but I cannot find any Dumped WM5 Excalibur ROMS here. I never had the issue when running WM5 so I'm thinking the dll file shouldn't be all jacked up like the one on WM6.
If anyone is still running WM5, would you please dump the ROM and extract the file? The file name is located at HKLM\Drivers\Builtin\SDHC (in WM6). Open the dll key to reveal the name of the dll the SDHC uses. I'd like to test w/ the file provided from WM5.

Related

XDA2i Keyboard update Keybddr.dll issue - buttons dont work

Hi
I updated my XDA2i with the above keyboard dll posted on this site and now the buttons do not work. It seems that this dll does not work on the XDA2i.
The original dll was overwritten because for some reason, the dll did not appear in explorer (even when hidden systems files are visible) so I was unable to rename it.
Does anyone have an original copy of the above dll so I can restore the XDA2i to its former glory?
Jonno
i looked in the windows dir on my XDA2i to get the keyboard.dll file for you but i dont have one, where can i find it
John
Hi
For some reason, you cannot see the keybddr.dll file in native windows explorer or on the XDA2i itself, even though other dll's are visible. If you install the Resco file explorer product, you can select the option to view all dll's so this allows you to see the file.
In any case the updated dll does not seem to work on the XDA2i so does anyone know if the current version will be updated?
Cheers
Jonathon
This dll does not work on PPC W2k2 SE so you need to use AE Button Plus. You can get this from searching this site.
J

Problems with 1.40 ROM & 1.13 Radio and O2 XDA 2s UK

Hi,
I upgraded my XDA 2s last week to the 1.40 Type I ROM along with the Type I Radio 1.13 and customised my Extended ROM in the 1.40 kitchen. I have been experiencing some weird problems though and wondered if anyone else had had the same things and if there is a workaround.
1) I had trouble with GPRS reconnecting but then foudn the post about changing Caller ID version so that one is sorted.
2) My bluetooth headest has gone weird on me a couple of times during calls, it suddenly adds a question mark to the headset icon in the top bar and switches the call to the phone which is quite annoying (and dangerous when driving!)
3) It seems that my settings for sounds and notifications keep going back to default, particularly my SMS tone, which is just a WAV file in the Windows directory.
4) Sometimes when i switch it on a white light comes on the screen for a second then it switches off again and has to be pressed again. A soft reset cures this normally.
I really like 1.40 apart from these irritations as I really want to keep WMP10. If anyone has any insight, I have posted the contents of my config.txt file to see if anything could be causing issues.
Thanks for any help,
Fin
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\BA_Version_140.CAB
CAB: \Extended_ROM\Album_BlueAngelAKU26_Generic_WWE_RC20.CAB
CAB: \Extended_ROM\IA_CallerID_1.20_WWE.CAB
CAB: \Extended_ROM\MIDI561.sa.CAB
CAB: \Extended_ROM\ClearVue2.4.381WWE_withoutBP_OzUp.sa.CAB
CAB: \Extended_ROM\Java_V10.1.2.49_BA_WWE_0901_unremovable.CAB
CAB: \Extended_ROM\CAB-MMS-2.0.0.21-BlueAngel-Generic-ENU-27Dec04.sa.CAB
CAB: \Extended_ROM\BA_OEM_PA_Remove_WiFi_Logo.sa.CAB
CAB: \Extended_ROM\BA_Camera_Driver_Patch.sa.CAB
EXEC:\Extended_ROM\TPEnable.exe
CAB: \Extended_ROM\BA_cm_rm_map_o2_v3.CAB
CAB: \Extended_ROM\O2UK_AP_09212004_BA_1.sa.CAB
CAB: \Extended_ROM\O2UK_Button9_WWE.sa.CAB
CAB: \Extended_ROM\O2UK_Connection_Setting.sa.CAB
CAB: \Extended_ROM\O2UK_Hide_WLan_message.sa.CAB
CAB: \Extended_ROM\O2UK_PIE_homepage.sa.CAB
CAB: \Extended_ROM\O2UK_Regional_TimeZone.sa.CAB
CAB: \Extended_ROM\VideoMMSB12_BA.sa.CAB
CAB: \Extended_ROM\TrayLaunch.CAB
CAB: \Extended_ROM\FINIIW.CAB
CAB: \Extended_ROM\RESCOEXPLORER.CAB
CAB: \Extended_ROM\rescoreg.CAB
CAB: \Extended_ROM\FTP.CAB
CAB: \Extended_ROM\SoftReset.arm.CAB
CAB: \Extended_ROM\RAR.CAB
CAB: \Extended_ROM\PocketMSN2K3SE.CAB
CAB: \Extended_ROM\BA ExtROM Unlock WORKING.CAB
CAB: \Extended_ROM\battery_OU_081304.sa.CAB
CAB: \Extended_ROM\install.ARM.CAB
RST: Reset
I am being tortured by the fail in re-connect gprs, could you tell me how to solve me by the 'Caller ID version' that you suggest on your post.
Best regards
Patrick Choy
xda 2s GPRS Connection Issues
mfchoy wrote:I am being tortured by the fail in re-connect gprs, could you tell me how to solve me by the 'Caller ID version' that you suggest on your post.
Hi Patrick
You have to unhide and unlock your extended ROM and replace the Caller ID cab file with older version of the same file that is available on the wiki site in the Blue Angel ROM kitchen. From memory, I believe the older version of the file you need is the one with the 14 suffix. are you familiar with unhiding ans unlocking the extended ROM?
Best Regards
Chris
Thanks Chris but I am not familiar with playing around with the ext rom, do you think there is patches out there that I can apply, otherwise, you walk me through step by step how to do it.. if it's not too troublesome.
Best regards
Patrick Choy
Instead of unlocking the ROM, can't you just copy the photo contact cab file to the phone, rename the IA*.DLL's and then execute the cab file to load the program? Obivously this will be removed after a hard reset.
1.40 Extended ROM GPRS Problems
HennyB wrote:
Instead of unlocking the ROM, can't you just copy the photo contact cab file to the phone, rename the IA*.DLL's and then execute the cab file to load the program? Obivously this will be removed after a hard reset.
Click to expand...
Click to collapse
Mmmm... that might work, although since the existing version of the program is also running, there may be some conflicts, unless you could stop it before starting the replacement... Not sure on that... "The Last One" or "Happy Goat" could probably advise if you if you PM one of them.
mfchoy wrote:
Thanks Chris but I am not familiar with playing around with the ext rom, do you think there is patches out there that I can apply, otherwise, you walk me through step by step how to do it.. if it's not too troublesome.
Click to expand...
Click to collapse
As far as I know there are no patches available at this time. We are still waiting for O2 to release their version of the 1.40 software, which will also include the Blackberry client software. Its only a 50:50 chance that their update will also contain some GPRS, Bluetooth and WiFi improvements, but I would not hold my breath....
The wiki site (wiki.xda-developers.com) is really the place where all the knowledge resides, plus the various ROMs and CABs. It explains explains all in great detail and I would encourage you to read the sections on Blue Angel. In the meatime, here are some specific links to help you step by step through the ROM unhide and unlock process.
http://wiki.xda-developers.com/index.php?pagename=BA_ERK_X_Zip
Once you have unhidden and unlocked the Ext ROM, you will be able to replace the Caller ID file with the older version (1.17), which can be fould here:
http://wiki.xda-developers.com/index.php?pagename=BA_ERK_Applications
The 1.40.147 extended ROM seems to differ from other extended ROMS in that you do not have to update a Config.txt file. You just copy in the new CAB files using the same file naming scheme as the other files in the Ext ROM. I cheated a bit here, by just renaming the older version of the file after I downloaded it (not really good CM practice but it worked for me ). So after unhiding and unlocking the ROM:
1. Download the 1.17 version of the file from the link above to a folder on your device
2. Look at the file name of the Caller ID CAB currently in the extended ROM and rename the file you downloaded to the exact same name.
3. Delete the current Caller ID CAB from your extended ROM.
4. Copy the Caller ID file you just renamed into the extended ROM.
5. Re-Lock and Re-Hide the extended ROM per the instructions at the link above.
6. Then perform a Hard Reset and the modified extended ROM file will reload. WARNING! Remember that a hard reset will ERASE all the date and 3rd party apps you currently have on your device. You will have to resynch with outlook and reload any apps you want again after the hard reset, so make sure all is backed up before you do any of this.
So that's what I did. You could try the trick that HennyB suggested first of course and see if that works. The other option is to wait for the new ROM from O2. And if you do not want to mess with the Extended ROM, but can't wait for the new O2 update, try going back to the current 1.31 ROM from O2 and installing in 'corporate mode' when prompted. The 1.31 ROM always had a very stable GPRS connection for me.
Hope that helps
Regards
Chris
Caller ID
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Caller ID
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
HennyB wrote
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Click to expand...
Click to collapse
Sounds like this is the workaround then. Certainly seems easier than the ROM "surgery' and if you ever have to do a hard reset, you could modify the ROM then..
Regards
Chris
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Click to expand...
Click to collapse
Hi Henny, the rename that you say mean just change the name to something else, correct me if I am wrong about what you say. And crbrow51, you mean if I perform a hard reset, everything that I do according to Henny will be gone, isn't it.
Best regards,
Patrick Choy
I just renamed the IA* files to IA*.dlb from .dll and then executed the cab.
I am definitely running version 1.17 of the Photo Contact program but still have GPRS program. Photo contacts seems to work more reliably though.
Now I dont believe that changing the version of photo contacts will solve the radio problem.
Hennyb wroteI just renamed the IA* files to IA*.dlb from .dll and then executed the cab.
I am definitely running version 1.17 of the Photo Contact program but still have GPRS program. Photo contacts seems to work more reliably though.
Well that fix worked for me, although I did it via the extended Rom update and hard reset. Is it conceivable that a hard reset is needed to completely flush the effects of the existing Caller ID version...? Anyhow, here is a link to a thread that has some more pointers to possible GPRS connection fixes
http://forum.xda-developers.com/viewtopic.php?t=21972&highlight=
mfchoy wrote: Hi Henny, the rename that you say mean just change the name to something else, correct me if I am wrong about what you say. And crbrow51, you mean if I perform a hard reset, everything that I do according to Henny will be gone, isn't it.
Yes, if you do the workaround to bring this file in without updatinf the extended ROM, then the change is lost on a hard reset.
Regards
Chris
Removed phonealarm program (which I thought was great) and now GPRS is working flawlessly.
Not sure if changing to photo contacts helped the situation or not.
What is phonealarm?
What Is Phone Alarm?
Its a great profile and repeating audible alerts program for PPC PE devices.
You can download the trial at
www.pocketmax.net
try AlarmToday by the same developer. Great products, first class support.
Also, as an aside, i have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me ;-)
Regards
chris
Also, as an aside, I have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me
Click to expand...
Click to collapse
GPRS on my phone even with the caller ID downgrade did not work properly until Phonealarm was uninstalled.
I believe the compatibility problem is with the new O2 Asia 1.40 ROM. Users have reported the same problem on the Pocketmax.net forum for phonealarm.
http://www.pocketmax.net/phpbb2/viewtopic.php?t=565
Mmm.. interesting... Which version of PhoneAlarm are/were you using? I had trouble with 1.20 and went back to 1.13... I was thinking of moving to the O2 Asia ROM, to see if there were any improvements to bluetooth connectivity. Guess I could do that and use O2 Plus instead of PhoneAlarm... Thoughts..?
Regards
Chris
Re: What Is Phone Alarm?
cbrow51 said:
Its a great profile and repeating audible alerts program for PPC PE devices.
You can download the trial at
www.pocketmax.net
try AlarmToday by the same developer. Great products, first class support.
Also, as an aside, i have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me ;-)
Regards
chris
Click to expand...
Click to collapse
Thanks
Mmm.. interesting... Which version of PhoneAlarm are/were you using? I had trouble with 1.20 and went back to 1.13... I was thinking of moving to the O2 Asia ROM, to see if there were any improvements to bluetooth connectivity. Guess I could do that and use O2 Plus instead of PhoneAlarm... Thoughts..?
Click to expand...
Click to collapse
I was using 1.22 and the new Asia ROM.
I do not use bluetooth but one of my friends does and said that the older ROM with the bluetooth patch is better than the new 1.40 Asia ROM.
I had a same issue with GpRS not being able to reconnect. Drove me nuts as we use mobile mail to our devices.
Installed the older called id cab (1.17) (just renamed one file) and now its all good.
Also my XDA2s now does not freeze when gprs is reconnecting.
Thanks!

Can't Copy cmhome.dll and other dll files!!

I am having trouble copying the dll files from my Windows directory on my Dash. I have used Total Commander and Windows Explorer. It says access denied. I can copy some dll files such as the bronzeres.dll. But I cannot seem to get the others. I have tried to make them unhidden (Visible). I have rebooted my phone and pc, just in case there was something weird going on with either. I am stuck. The whole reason I am wanting these is to see how they operate. I have been able to alter my homescreen xml code to insert Fizz Weather into the iconbar, but would like to attempt at adding plugins such as Fizz Weather to the actual panels instead of just a panel with a link to start Fizz Weather. I would really appreciate any help with this. I am really at a stand still at this point.
Those files are XIP (execute in place) they arent real files, they are in a weird format optimised for running fast, although they display in explorer you cant copy them. However you can overwrite them with replacements and the original XIP versions are hidden from applications.
To retrieve these XIP dlls to your PC you need to dump the ROM and reconstruct the files. Its pretty easy there are loads of guides on the Wiki.
Follow this first:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Then second to extract the files:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoExtractImgfs
here you go heres cmhome.dll
indiekiduk said:
Those files are XIP (execute in place) they arent real files, they are in a weird format optimised for running fast, although they display in explorer you cant copy them. However you can overwrite them with replacements and the original XIP versions are hidden from applications.
To retrieve these XIP dlls to your PC you need to dump the ROM and reconstruct the files. Its pretty easy there are loads of guides on the Wiki.
Follow this first:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Then second to extract the files:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoExtractImgfs
Click to expand...
Click to collapse
I tried to dump this ROM but I'm not getting very far. The 1st link you gave is for the Hermes and does not appear to be the same as the excalibur. I cannot seem to dump the raw files needed to dump the rom. Any help??

Help on extracting a Hotfix.

I was wondering if someone could give me some direction, cause I have been trying and havent found a way yet. I am trying to extract a HTC hotfix from their site on my computer. I can extract the hotfix into a folder, but its in 8.3 filename format, I am trying to extract it so that I can cab it up and try installing it in my spare tp2.
And to answer the question, its not for the TP2 thats why I cant run it on the TP2, my problem is I am trying to extract it, and then make it a cab with WinCE Cab so that the registry settings get implimented and files get copied to the right location.
Any help would be appreciated, been looking all day to make this work
Can you provide a URL to the hotfix, so others (such as myself) can have a try at this?
Its the sms hotfix from htc dated 1.28.2010 for the HD2, But that still doesnt answer my question of how to extract this exe file to make a cab and try it. Seppi had done it to an older version which helped a bit with the issue but its not this new version which I am willing to try since the older version did work and did improve the sms somewhat. What I need is to be able to extract the exe with long file name, everytime I extract it it extracts with the short filename.

INCities.cdb

When installing the .CAB file, it works perfectly.
When converting a .CAB file to OEM and cook it, it works but part of the application is not working.
Noticed that INCities.cdb file is the cause, then i did the following:
1- Convert the original .CAB file to OEM and cooked it.
2- Create a new .CAB file including only "INCities.cdb" file in.
3- Run the Created .CAB file after first Cooked-ROM boot.
The application works as expected
What does the created .CAB do which is missing from the converted OEM files? although the same file is included in the OEM.
I spent Hours and Days to analyze it without success.
I'm attaching the created .CAB for reference.
Any body knows the trick?
hello,
This cab does not seem to be a problem ... You can also the OEM file that you created for your kitchen.
By.
rickou26 said:
hello,
This cab does not seem to be a problem ... You can also the OEM file that you created for your kitchen.
By.
Click to expand...
Click to collapse
Yes, the CAB doesn't have any problem.
The application doesn't work properly without running this CAB.
how to solve this? i don't need to install the CAB.

Categories

Resources