Hello I have a problem, I have tried to modify a dll file located in the window folder wich is controlling part of the phone skin on a Artemis. (phcanOverbmp.dll)
The problem is that the phone dosen't recognize the altered Dll file becuase the certificate changes when you alter the file.
How do I solve this?? I have tried to create my own certificate, but Aretemis dosen't except it. and I haven't been able to sign the Dll with anyone of the existing Root certificate already installed in the Artemis. How do you work around this problem??
Both create/install a certificate, and how to sign the Dll
I really need help, Thank you
i have the same problem
if anyone have some advice, just tell for us
You can not edit or change a signed DLL in any way. Once you do the signature is broken and the file becomes unusable, you can not resign it.
You have to remove the certificate first, then make your changes.
I saw a code for this somewhere but I don't remember the link.
Look around, there may be a utility to do this.
In your case resigning may not even be necessary.
levenum said:
You can not edit or change a signed DLL in any way. Once you do the signature is broken and the file becomes unusable, you can not resign it.
You have to remove the certificate first, then make your changes.
I saw a code for this somewhere but I don't remember the link.
Look around, there may be a utility to do this.
In your case resigning may not even be necessary.
Click to expand...
Click to collapse
in my case it is necessary, otherwise the phone will not recognize the dll and display the WM5 original skin. I know you can't resign the DLL with their certificate, but i know that you can add your own root certificat in the phone. And then you must sign the DLL with that certificate, (wich is our own certificate) so the phone recignizes it. Then it shall work. I just don't know how to do it.
Thats relatively easy. All you have to do is create a provisioning XML and put it in a CAB. The WM 5 SDK has a sample.
Here is a link to a sample as well.
By the way if this is considered a system file (I am not sure about that) it needs a trusted, not root certificate.
Related
MDApro:
I am trying to replace a Dll file that is in ROM in the \windows dir with a Dll file from my own with the same name.
Then my Dll loads all functions from a copy of the original Dll file. After a soft reset my Dll file gets active and the ROM file is blended out.
So far so good, this works well..... until WM5. Here after a soft reset the device is dead. Hanging in boot screen. Nothing happens.
A hard reset is necessary and the device is alive again.
I have a test app which simulates the Dll load order and it works ok with a Dll file with another name.
When I started test app a notification appears on the device which says that the file xyz.dll is from unknown publisher, trust it or not...
So could it be that it has something to do with signing the dll file? Or does the boot loader (or some one else)
check that all files have the correct checksum or version?
Has anybody information about that? Thanks!
I've replaced DLL files with no problem after soft resets. Did you disable signature security settings?
http://www.beyondthetech.com/downloads/phone/Cert_SPCS.CAB
Taken from the HTC Apache. Disables the security so you can used unsigned files.
Wow how quick!
I have read today about signature security settings and that it is possible to change the settings.
Have tried to disable the signature security today but I think I have done somthing wrong.
Will try again tomorrow with your app and I hope it will work then. Have spend so much time on this the last weeks...
Which file have you replaced?
Have tried it with your Cert_SPCS.CAB. But with no success. After replacing the file and soft reset the device was dead again.
How can I check what security settings are currently set and active on the MDApro device?
1) exe/dll's have to be all signed correct? I assume other files don't (bmp, xml, htm, etc)
2) are files in rom signed or are they assumed to be valid since they are in rom?
2a) if rom files are signed is this preserved on extract via viewimgfs?
3) Can you determine if a file is signed and which cert it was signed with?
4) I see cab's such as the recent Palm Messaging cab that don't appear to install a cert, yet the program runs fine once installed. How is this possible?
hannip said:
1) exe/dll's have to be all signed correct? I assume other files don't (bmp, xml, htm, etc)
Click to expand...
Click to collapse
.EXE, .DLL, .CPL and .CAB files must be signed.
hannip said:
2) are files in rom signed or are they assumed to be valid since they are in rom?
Click to expand...
Click to collapse
All cabs in Extended rom must be signed.
hannip said:
2a) if rom files are signed is this preserved on extract via viewimgfs?
Click to expand...
Click to collapse
Don't know... :O
hannip said:
3) Can you determine if a file is signed and which cert it was signed with?
Click to expand...
Click to collapse
Yes. If you look in the "Digital signatures" tab in the files properties you will see both who signed it and who it was signed for.
hannip said:
4) I see cab's such as the recent Palm Messaging cab that don't appear to install a cert, yet the program runs fine once installed. How is this possible?
Click to expand...
Click to collapse
On a Pocket PC running WM 5.0 a notification will appear that says that the cab comes from a untrusted source. If the user accepts this, the application will run as if it were signed.
Øystein
t0flus said:
On a Pocket PC running WM 5.0 a notification will appear that says that the cab comes from a untrusted source. If the user accepts this, the application will run as if it were signed.
Øystein
Click to expand...
Click to collapse
Thanks for the quick reply!
I'm real curious on the last point. So you are saying as long as a program is installed via a cab and the user accepted the warning that program will run without warning once installed. Correct? So is there some db that contains each file installed and whether they can be run without warning even though it's unsigned?
I must be missing something. I've created a cab file of the HTC StreamingMedia player and it runs fine as long as I have the policies set not warn. But when I change the policies back to normal I can't install the cab even though I've accepted the warning. The installation seems to be going ok, but then I get the following error.
"Installation was unsuccessful. The program or setting cannot be installed because it is not digitally signed with a trusted certificate."
Nice of it to tell me which file or setting it is bombing on. ugh
Ideas?
So the answer to 2a is yes and no. Files are extracted signed, but module-files are not.
hannip said:
So the answer to 2a is yes and no. Files are extracted signed, but module-files are not.
Click to expand...
Click to collapse
Probably they are signed with a cert you don't have on your phone??
If you have the cert, then try extracting them using TestWM5.exe or grab_it! and see if it makes any difference.
pof said:
Probably they are signed with a cert you don't have on your phone??
If you have the cert, then try extracting them using TestWM5.exe or grab_it! and see if it makes any difference.
Click to expand...
Click to collapse
All of the files in my cab are appropriately signed and the certificate is installed on my device. The cab just wont install. I even signed the cab and it still complains, but at least there is no warning at the start.
The files themselves are good. I have tested them on my device by installing them manually and importing the reg file. It's just a cab install issue of some sort.
Is there a way to turn on cab tracing?
One thing:
What device exactly is it?
I know on Smartphones (like the Tornado) even signed cabs are not allowed to install certificates unless the cab is signed by 'privileged' certificate.
The error you described is often caused by cab no being able to change registry setting or install certificates.
It's a PPC device (treo 700wx). The cab does not install a cert. The cert is already on the device. I've been able to install certs via cab before on this device however. The cab does make several reg changes. I'm thinking it's gotta be one of those settings.
Is there no trace or logging available for cab installs? This one is huge and would take some time to narrow down which setting it is having a problem with.
Unfortunately I don't know of any loggers for cab installation.
You should look for reg settings in HKEY_LOCAL_MACHINE and anything having to do with security, certifications, system settings (I know its a wide range, sorry). Those are usually restricted and can only be changed by privileged cabs.
I suppose the only solution is to comment them all and then return them one by one to see which is problematic.
you might want to check out:
http://msdn.microsoft.com/library/d...gpoliciesoncabfileinstallationprocessozup.asp
even though there is wce51 in the url, it's under softphone2003. Security on a single tier sp2003 is very simular to pocket pc 2005. I suspect most (or all) of it will applies.
I had tried to install a file in the top directory and it failed, but worked for another directory. Perhaps I made a mistake, but it made me wonder if somethings aren't allowed. (putting files in \, changing certain registry settings, etc)
hannip said:
It's a PPC device (treo 700wx). The cab does not install a cert. The cert is already on the device. I've been able to install certs via cab before on this device however. The cab does make several reg changes. I'm thinking it's gotta be one of those settings.
Click to expand...
Click to collapse
What kind of cert have you installed? Are you sure it is a application certificate and not a ROOT cert?
If you upload the cab file I can take a look at it...
Øystein
I'm having trouble modifying a string in tapres.dll.0409.mui. I've tried changing the string, even just one letter, in PE Browser and even hex editing.
I've tried signing the file with various different certs, but nothing helps. The file does not work when I boot up with it.
What am I missing here?
fluxist
Several things:
1) Were did you get the original file? The file may be corrupt to begin with.
2) You need to remove the signature (if any) before editing the file or it will be permanently ruined.
3) It is recommended to use Platform Builder to edit MUI files (you can download evaluation version from MS site for free).
Hope this helps.
levenum said:
Several things:
1) Were did you get the original file? The file may be corrupt to begin with.
2) You need to remove the signature (if any) before editing the file or it will be permanently ruined.
3) It is recommended to use Platform Builder to edit MUI files (you can download evaluation version from MS site for free).
Hope this helps.
Click to expand...
Click to collapse
I extracted the file from an RUU. I've been editing it with Visual Studio 2005.
I've tried removing signatures, when present. I've been using UnSigner for that.
It seems that even without editing it, just copying it into /Windows and overwriting the original causes the same problems. I've tried signing it with different SDk certs, also importing the certs to the device, and that doesnt help.
I read in a thread that you need a dll file with an intact PE header, so I've tried removing the resources from another dll and adding my resources to it, but that didn't work either.
Has anyone done this before who can chime in?
fluxist
You are correct about the PE header.
Strange, moving the resources in to a clean DLL should have worked.
Two more things I can think of:
1) What OS is the original DLL for and what SDK did you compile the clean DLL with?
For example WM 6 DLLs will not load on WM 5, and in some cases WM 6 refuses to use WM 5 DLLs as system MUI.
2) If you can, make a simple app that will call LoadLibrary and see if you get an error loading the DLL.
if there is an error it means the DLL is still corrupt for some reason, if not it is most likely some kind of signature / permissions problem.
MUI files usually have only resources.
You can try re-dump it using my ROM Extractor.
When you can try to edit it again.
Some editors rather often corrupt files.
Try different resource editors.
levenum said:
Several things:
1) Were did you get the original file? The file may be corrupt to begin with.
2) You need to remove the signature (if any) before editing the file or it will be permanently ruined.
3) It is recommended to use Platform Builder to edit MUI files (you can download evaluation version from MS site for free).
Hope this helps.
Click to expand...
Click to collapse
Can you guide me to Platform Builder download, i have tried to search for it, even on MS site, and i found sdk stuff, not a debug software that can edit MUI.
So, please, help me...
Intro
Lately I've seen a lot of posts by people who are trying to replace WM internal or driver DLLs, either for hacking/testing or to release. Aside from the possibility they are just doing something that won't work in the first place, I've seen failure a lot of times because files aren't properly signed, or if they are, the certificate in question not being in the right certificate stores for it to have any effect. On some ROMs it will still work due to patched NK.EXE, on others it won't, its just not very reliable.
So, I present you with the correct way of doing this by means of a small tool that will do this for you: DriverWiz. It will take care of most of the stuff, and leave you room for additions. You will however still need some basic knowledge of the command line, if you don't have that, you have no business doing anything like this anyways.
Background
I use this technique myself all the time. When just hacking away, replacing system DLLs to trace calls, etc. It's also the same method used for the HTC-CA drivers and the ICS installer. This method works on most stock ROMs as well, though not on all of them (in rare cases some security policies are set that will prevent CAB installation)
Usage
It's fairly simple to use. Just extract the attached zip file somewhere, open the command promt, and change directory to where the zip was extracted. That's the installation part.
Now when you actually want to build a CAB file from a DLL, you use the DriverWiz.bat file.
DriverWiz v1.0 by Chainfire
Usage:
DriverWiz.bat "Description" "CAB-name" "DLL-name-1" ["DLL-name-2" ...]
Examples:
DriverWiz.bat "New DDI" "ddi.cab" "ddi.dll"
DriverWiz.bat "Two DDIs" "ddi.cab" "ddi.dll" "ddiaux.dll"
Click to expand...
Click to collapse
DriverWiz will take care of signing the DLLs, inserting the certificate, etc, and you will end up with a proper CAB file for this kind of thing. Just copy it to your device and run it to install.
#1. You need to put the DLL files in the same folder as DriverWiz. Do NOT include paths in your DLL names
#2. Include the quotes in the command like in the examples!
#3. The first time you install a CAB made by DriverWiz, your phone may still give you a certificate warning. This is normal, don't worry about it.
Caveats
While this method has never failed me yet, it is possible that some files cannot be replaced this way. Just a disclaimer
Modifying
DriverWiz bases the inf file it will create to build a CAB from on DriverWiz.tpl. If you need to add registry entries to your CAB file, modify DriverWiz.tpl before you run the batch file. You can make other modifications too, add files, etc. Just take care that you don't break it
You can use your own certificates as well, instead of the supplied "Dummy" certificate that comes with DriverWiz. The files you will want to modify/replace are DriverWiz.pfx (used for signing) and DriverWiz.xml (used for injecting the certificate). I'll see about finding a reference for how to do that online and posting the URL here (someday). Creating a new certificate from scratch can be a frustrating effort - make sure you got openssl handy
Changelog
19.03.2009 - 1.1 - Added some file exists checks and attribute changes
Download
Temporary PlaceHolder for more Info.
Whoo this is hot from the plate, looks very promising!
Driver testing withoud cooking! joohie
Well if you replace the wrong files you're still going to need to hard-reset to boot. I advise KITL before you do
Works flawless. You tha man.
Didn't work for me trying to cab up No2Chems Fast Charge battery divers.
ruskiyab said:
Didn't work for me trying to cab up No2Chems Fast Charge battery divers.
Click to expand...
Click to collapse
What exactly happened? Attach the files and such
It made the cab and all, but when I went to install it, the unsigned error message popped up just like when I tried it with WinCE cab manager.
That is perfectly normal behavior. The first time you install a CAB with this certificate it will not know the certificate. However, once you install it, the certificate will be injected in the right place, and the files signed with the certificate (the driver files in the CAB) will be allowed to be run.
It won't happen the second time you try it
So if I try to install it again, it'll work fine? is there aa soft reset required in between? I can replace these drivers manually by renaming the old ones and copying them over, the whole reason I want a cab in the first place is to facilitate the UC process when I flash a different rom
ruskiyab said:
So if I try to install it again, it'll work fine? is there aa soft reset required in between? I can replace these drivers manually by renaming the old ones and copying them over, the whole reason I want a cab in the first place is to facilitate the UC process when I flash a different rom
Click to expand...
Click to collapse
Actually it should just work the first time. Just click OK when the certificate error appears.
Nice nice nice work!
error message
I got error messages when creating a cab from a rilphone.dll. Does it mean anything, or are these errors okay? I guess I'm specifically wondering about the SignTool error. If its okay, then my cab should be good.
EDIT: I think I found the problem. I didn't have UAC disabled in Windows 7. I tried it again, after disabling it, and it works fine now. Thanks for the easy to use tool!
syntax for registry entries?
I was experimenting with creating a cab for the Rogers folks who need a specific rilphone for their Caller ID to work. There are some registry entries associated with this feature, so I was wondering what the correct syntax is for putting the registry entries into the .tpl file. I've tried a few different ways, and I've either a gotten a 'Registry section is empty' message, or a 'Registry has an unsupported registry root key' error. I'm sure its something really simple I'm missing, so any help you can offer is appreciated.
It just seems that since we now have this easy method to sign these dlls, so that they can be used in any ROM, that the Rogers people shouldn't have to jump through so many hoops to get it to work.
EDIT: Nevermind. I'm an idiot that didn't do a little bit of research. All is well now.
Excellent stuff, Microsoft may rant about this way of distributing signtool and cabwiz though.
Chainfire said:
You can use your own certificates as well, instead of the supplied "Dummy" certificate that comes with DriverWiz. The files you will want to modify/replace are DriverWiz.pfx (used for signing) and DriverWiz.xml (used for injecting the certificate). I'll see about finding a reference for how to do that online and posting the URL here (someday). Creating a new certificate from scratch can be a frustrating effort - make sure you got openssl handy
Click to expand...
Click to collapse
Here's an intro to cert stores for WM:
http://msdn.microsoft.com/en-us/library/aa458010.aspx
pfx generation is a 2-liner with openssl:
# Generate a CA certificate
openssl req -new -nodes -x509 -days 9999 -newkey rsa:1024 -md5 -keyout cert.key -out cert.cer -subj "/CN=DriverWiz"
# Convert to pkcs12/PFX format
openssl pkcs12 -export -in cert.cer -out cert.pfx -inkey cert.key
got error messages under vista sp2, any ideas?
I also get an error saying that the latest version of CAPICOM.dll is missing. The ones I can find for download from the internet are version 2.0.0, and the tool requires 2.1.0.1 or later.
Does anyone have the needed version of the dll?
EDIT: Found it, 2.1.0.2 version of the dll is in the attachment.
Time Saver !
Many thanks; DriverWiz /w the CAPICOM.DLL saved me about an hour of troubleshooting.
Cheers,
Thanks for the capicom.dll Even after disabling UAC in W7Rc1 it wouldn't go, so great to have it posted to.
Chainfire, which format should the Reg's be added?
I tried the default .reg formating just under:
[Registry]
[HKEY_CURRENT_USER\ControlPanel\Profiles]
@=""
"ActiveProfile"="Normal"
?
Scrap that i found the .inf format
[AddRegistry]
HKCU,"New Key","",0x00010001,1
Many thanks for this, i'll try to Point Driver replacing Sinners from now on to here.
Well INF files are a regular female dog.
If you rather use WinCE CAB Manager, the trick is easily done as well. I do not have it handy right here (I'm not at dev box), but it goes like this.
Put the DLL's and EXE's that need to go in the CAB into the same folder as DriverWiz
Execute the following command from the command prompt in the DriverWiz folder: signtool sign /f DriverWiz.pfx *.exe *.dll
Open your WCM/CAB with CM
Somewhere is an option for "Pre XML" (main screen IIRC).. click to add/edit, and load the DriverWiz.xml file
Save
signtool sign /f DriverWiz.pfx *.cab
Et voila. I should really make an update to DriverWiz to include CAPICOM and write a proper guide on how to do all this manually (including making your own certificates and such). It's easy if you know how
If you could insert another empty post for me at the top, that'd be great.
I try to create a program which consists of
.asx files (to show online tv channels),
.lnk files (shorcuts to the .asx files) and
a .dll file which contains only some .ico files (icons of the tv channels).
I added all these files to a cab using WinCE Cab Manager and tried to install it on my ppc. So far so good. The problem occurred when the message “The program can not be installed. Choose another location” appeared during installation, just after the process bar was filled.
Although I have no idea about computer programming, I have created many cab’s with WinCE Cab Manager for skins I have created for several programs. Anyway, I realized that the problem occurred due to the .dll file, since this is the first time I add such a file in a .cab.
I created my .dll file using a .dll from another program which had only icons in it, as well. I deleted them using Restorator 2007 and I had an “empty” .dll sized 4KB. Then I added my icon files using XN Resource Editor.
I searched the Internet to see what might be the problem with the .dll and I found out that I have to “register” my .dll file. I really have no idea what this means but it needs to be done. I also found an option in WinCE Cab Manager for “self-registering” file, but it didn’t work either.
So, the question to you dev guys is how can I register my .dll file, or should I create it from the beginning with another way?
Please help! Thanks in advance!
sorry to repost but it seems that posts keep coming in this forum and this thread is already in the second page and I'm afraid that noone will see it and reply to it. By the way, is there any special sub-forum for such questions?
This may help. I use his instructions to edit existing DLL's
http://www.modaco.com/content/i9x0-...88904/lisbian-taskbars-for-i910/#entry1023568
It will unsign the dll which will probably fail on your custom dll but it should sign it when you are done editing.
NilsP
Many thanks for your suggestion but unfortunately it didn't work for me.
As you said, this is mainly for resigning already signed .dll files.
Any other help will be appreciated. I can attach it here if anypne is willing to help. Or just tell me the way. Thanks!
I deploy a few dll's with my app, without any problem. If the installer complains about the location, what did you specify where it should go?
There are 2 approaches to solve this problem:
1.) If you have a private key to match a certificate in the device's certificate store, sign the .dll and .cab with this private key and it will be installed with elevated privledges, and be successful. To facilitate this you can install the "SDK Certificates" - and sign with the matching private key (you should be able to find these on a search, term "SDKCerts" or similar)
2.) Look for an "Application Unlocker" or other security reduction tool, run it, and you should be able to install the cab. On this note, if you check here, it will give you a more technical overview of the security policies. You want to change 4101 / 0x1005 to "SECROLE_MANAGER" (8) - which tells the system to install it with elevated privledges. Also make sure 4102 / 0x1006 is set to 1 to allow unsigned applications.
6Fg8
I don't believe that is the location I specified that causes the problem because when I deleted the .dll file from the .cab, it was installed properly. How do you create your dll files? With programming or you just edit existing files? If I send you my .ico files, will you be able to create the .dll file for me?
Da_G
Thanks but both approaches seem very complicated for me!
So, will I need Visual Basic in order to do this or is there any easier way? Can anyone sign the dll for me?
angelos_cy said:
6Fg8
How do you create your dll files? With programming or you just edit existing files? If I send you my .ico files, will you be able to create the .dll file for me?
Click to expand...
Click to collapse
Yes with programming, C++ or .net. Never had any issue with signing. I can try to make a dll if you send me the icons (or post them here if they aren't too secret ).
6Fg8 said:
I can try to make a dll if you send me the icons (or post them here if they aren't too secret ).
Click to expand...
Click to collapse
I have sent them to you by pm. They are not secret at all but I will create a "program" (wannabe ) with that dll and I want that program to be a surprise for users of the forum where I'll post it. I may post it on xda too, but it's nothing important.
Many thanks!
angelos_cy said:
The problem occurred when the message “The program can not be installed. Choose another location” appeared during installation, just after the process bar was filled.
Click to expand...
Click to collapse
This happens because you've changed resources in signed file, which changed file checksum and invalidated it's signature, and Windows installer refuses to install file with invalid signature. But it won't refuse to install this file WITHOUT signature at all - so use unsigner (search for it on XDA) to remove signature completely; if you encounter error, try to remove signature from original (unmodified) file, and then change resources in it...
6Fg8
the_ozyrys
Thanks to both of you!
6Fg8 has created and signed the dll for me and it finally worked, but I also tried the_ozyrys' method and it also worked.
So thanks to baniaczek too, since he created the unsigner.exe.
Everything worked fine with the dll. Now the cab is installed properly.
However, I have another problem. Just after the installation of the cab on my ppc, it seems that the device freezes for about a minute. This is propably because my cab contains a lot of shortcuts (.lnk files) that go under Programs folder.
So, I would like to ask for another favour, if it's possible. As I said I intend to give this cab to others too. Since this delay can make them believe that my program has freezed their device, I would like to make the cab restart the device just after installation and after uninstallation as well. I think this is made with the "Setup.dll" which I don't know how to create.
If anyone knows how to do this and has the time for it, could you please create this setup.dll for me. If the cab is needed to do this, just tell me to send it to you.
Thanks in advance!
Anyone? Plzzzzzzz!
If you want to sign .dll or .exe u can use the apps posted in the two posts below
http://forum.xda-developers.com/showthread.php?t=432041
or
http://forum.xda-developers.com/showpost.php?p=3530246&postcount=18
raykisi
Thanks for your answer but 6Fg8 and the_ozyrys already helped me on that.
My question now is how to create a setup.dll in order to make my .cab to prompt the user to restart the device after installation and uninstallation. If anyone can do it for me, I can send you the .cab which I alreday created and you can add the setup.dll with those functions.