Database Users

T-Mobile US MDA - Java?

Anyone know what files/have the files necessary to put the Java Virtual Machine back on the T-Mobile (US) MDA Load?
Its on the SDA but not the MDA - and this sucks!

Genesis3 said:
Anyone know what files/have the files necessary to put the Java Virtual Machine back on the T-Mobile (US) MDA Load?
Its on the SDA but not the MDA - and this sucks!
Click to expand...
Click to collapse
Just a simple .lnk file to \Windows\Jmm.exe. AFAIK, the intent Midlet manager comes with all HTC Wizards pre-installed; it's only the link file that is missing.
You can also download this link file from http://www.winmobiletech.com/sekalaiset/MIDlet Manager.lnk

Nope - the FILE is missing! And copying it over from a SDA (which has it) doesn't help - it won't run (may be different link options or somesuch)
It appears that T-Mobile whacked it out of their ROMs! Anyone got a copy of that I can try dropping in there?

Genesis3 said:
Nope - the FILE is missing! And copying it over from a SDA (which has it) doesn't help - it won't run (may be different link options or somesuch)
It appears that T-Mobile whacked it out of their ROMs! Anyone got a copy of that I can try dropping in there?
Click to expand...
Click to collapse
http://www.winmobiletech.com/sekalaiset/jmm.zip - give this a try. Unpack it to \Windows. Let me know if it works/doesn't work.

WORKS, kinda.
It comes up but won't load the GLM software. Not quite sure why.... looking at that now.
Update - says it failed to run image \windows\target.img
Looks like there's one file missing in that archive.

Genesis3 said:
WORKS, kinda.
It comes up but won't load the GLM software. Not quite sure why.... looking at that now.
Update - says it failed to run image \windows\target.img
Looks like there's one file missing in that archive.
Click to expand...
Click to collapse
Give it a try: http://www.winmobiletech.com/sekalaiset/target.img.zip
Put the ZIP file itself (don't decompress it) into \Windows.

Well it comes up now - GLM fails to load claiming the JAR file is invalid, but the Java Virtual Machine starts without error.

Genesis3 said:
Well it comes up now - GLM fails to load claiming the JAR file is invalid, but the Java Virtual Machine starts without error.
Click to expand...
Click to collapse
What JAR file is that? Midlet manager is only able to run non-device-specific midlets - that is, NOT Nokia/Sony-Ericsson etc. specific ones. With other stuff, it'll report about invalid JAR files.

Menneisyys said:
Genesis3 said:
Well it comes up now - GLM fails to load claiming the JAR file is invalid, but the Java Virtual Machine starts without error.
Click to expand...
Click to collapse
What JAR file is that? Midlet manager is only able to run non-device-specific midlets - that is, NOT Nokia/Sony-Ericsson etc. specific ones. With other stuff, it'll report about invalid JAR files.
Click to expand...
Click to collapse
Its the Google Local Generic MIDP 2.0 version off www.google.com/glm.
Runs on the SDA, but refuses to load on the MDA. The VM IS running now though.... thanks.

Genesis3 said:
Menneisyys said:
Genesis3 said:
Well it comes up now - GLM fails to load claiming the JAR file is invalid, but the Java Virtual Machine starts without error.
Click to expand...
Click to collapse
What JAR file is that? Midlet manager is only able to run non-device-specific midlets - that is, NOT Nokia/Sony-Ericsson etc. specific ones. With other stuff, it'll report about invalid JAR files.
Click to expand...
Click to collapse
Its the Google Local Generic MIDP 2.0 version off www.google.com/glm.
Runs on the SDA, but refuses to load on the MDA. The VM IS running now though.... thanks.
Click to expand...
Click to collapse
OIC... the generic MIDP2 version works great on my Qtek 1.6.7.1 ROM.

Leave it to T-Mobile to cripple the damn thing....

I've also been playing around with getting java on the T-Mob US MDA. I didn't have the benefit of an SDA, but on the ftp site I found various extended roms for the Wizard. Specifically on the 'O2 Mini Asia Exteded Rom...' I found a .cab that installs the jvm/midlet manager.
The program itself runs just fine, and installs and downloads the .jar specified in any jad file I execute. The problem comes when I try to run a program from within the Midlet Manager. What I get is:
Error
Failed to run the MIDlet
This happens with google, Opera and another program I want to run. Is this the same error you are getting?
The O2 Mini is a Wizard - correct? Could there be something else in the ROM that needs to be installed?
Anyone have any ideas?

No, I'm getting an error trying to LOAD the GLM site from www.google.com/glm.
It appears to load, goes through all the motions, and then complains about an invalid JAR file.
I don't have any JARs handy I can load off a local SD card to see if it will work with those. I'll look around for some....

So you are getting an error already when trying to download the app from Google? I don't know how familiar you are with J2ME apps, but they typically consists of 2 components. A .jad file which is a simple text file that describes some properties of the app and a link to the actual app.
The point I am at I can successfully go to the Google/glm site and select the Generic Advanced app, agree to terms and then I click to download. Once I do that PocketIE asks if I want to save or run the .jad file. I then select to run it, and it kicks off the midlet manager. Then the midlet manager will download the .jar file and it is available in the manager with icon and everything. Once I click on the Google or Opera icon to launch the J2ME app I get the error I described.
If I understood correctly it seems you haven't gotten this far yet?

Correct. I cannot load the application - it is transferred but the JMM application refuses to install it.
I suspect a registry difference here - and if we find it, we may have a working solution.

Well, I would have thought that the .cab I got from the other extended rom would create all the appropriate registry keys to run the program. At least jmm works and downloads the jar.
I have no idea why it won't run them though. I also used LokiWiz to unlock the device, and after that I had to reinstall the jmm cab because the device complained that jmm.exe was not signed/authorized.
I see that some keys have been created in HKLM\Software\Tao\. I have attached them here.

It may be a file association for the .JAR type....

After looking around a little in the registry, I can see that there are a lot of keys created. I think it will be difficult for you to manually copy everything from the SDA. There are entries for the right extensions, but there is one more interesting one that I'd like to see what is in the SDA (or any Wizard with Java capabilities) \HKCR\CEJavaVM. On my device it is empty.

ecf said:
After looking around a little in the registry, I can see that there are a lot of keys created. I think it will be difficult for you to manually copy everything from the SDA. There are entries for the right extensions, but there is one more interesting one that I'd like to see what is in the SDA (or any Wizard with Java capabilities) \HKCR\CEJavaVM. On my device it is empty.
Click to expand...
Click to collapse
That key is not there at all on the SDA nor on my MDA.
There are several file associations ("Jarfile" and "Jadfile") all of which look ok......

Works on a Cingular 8125
Do it works on a Cingular 8125, however, how do you get to Midlets after you install them?
EDIT: I just need a .lnk file to the JMM.
Danny

How To? - Package themes/clocks, compiling themes into .cab quick install files

I have access the to the files through WINRAR and can change the pics with Minila Editor. But How does one package them for install through a .cab file?
i hav downloaded packages_creator5.exe and also have the msceint.exe file in the same folder as i installed the ervius program, but how on earth does one put it together to work?
Please teach me?

Well there are a few ways to create .cab files but one quick method would be to use a program called QuickCab... Very easy to use it walks you though the process, makes life a whole lot easier if you are new to it.
go here ---> http://forum.xda-developers.com/showthread.php?t=400221

ProphecyXR said:
Well there are a few ways to create .cab files but one quick method would be to use a program called QuickCab... Very easy to use it walks you though the process, makes life a whole lot easier if you are new to it.
go here ---> http://forum.xda-developers.com/showthread.php?t=400221
Click to expand...
Click to collapse
looks promising, thanks, BUT, only that it says "cannot find Cab file, here it is the output from CabWiz:
Windows CE CAB Wizard
Error: Section [DefultInstall] key "CESetupDLL" - file "setup.xml is not a DLL so cannot be used as the special Setup.DLL"
solution? what did i do wrong?

went through installation it but no difference is made, it did not show the 'restart device' either. what is the 'setup.dll file for, where do i find such a file or what are the settings ?

HTCDiamond22 said:
went through installation it but no difference is made, it did not show the 'restart device' either. what is the 'setup.dll file for, where do i find such a file or what are the settings ?
Click to expand...
Click to collapse
hmm...
So you are trying to package some manila files to a cab file, so that you can install it on the phone.. right?
start QuickCab
Enter Application Name and Author(you)...
Don't check 'use custom setup.dll
Next->
Chose witch files to have in the cab ( Add-> ) to windows dir
Next->
No registry edit!
Create...
This works fine for me...
and about the 'restart device'... I don't know how to set it... on some cabs it says it ond on some it dont..

NisseDILLIGAF said:
hmm...
So you are trying to package some manila files to a cab file, so that you can install it on the phone.. right?
start QuickCab
Enter Application Name and Author(you)...
Don't check 'use custom setup.dll
Next->
Chose witch files to have in the cab ( Add-> ) to windows dir
Next->
No registry edit!
Create...
This works fine for me...
and about the 'restart device'... I don't know how to set it... on some cabs it says it ond on some it dont..
Click to expand...
Click to collapse
I've done that but it still does not work, I think that it may be the files i selected, should one only place in the files as showed in manilla?
no extra files to be added?

HTCDiamond22 said:
I've done that but it still does not work, I think that it may be the files i selected, should one only place in the files as showed in manilla?
no extra files to be added?
Click to expand...
Click to collapse
ok... where does it go wrong? on your computer or on the phone?
because you first say that Cabwiz is giving you an error and then you say that you cant install on the phone?
If it doesn't say that you have to restart our phone... just restart it yourself
...and you have .Net Framework 2.0? (on your computer)

NisseDILLIGAF said:
ok... where does it go wrong? on your computer or on the phone?
because you first say that Cabwiz is giving you an error and then you say that you cant install on the phone?
If it doesn't say that you have to restart our phone... just restart it yourself
...and you have .Net Framework 2.0? (on your computer)
Click to expand...
Click to collapse
.Net 3.5
I've uninstalled all the clocks and have restarted, going to try again

I've uploaded the file, does it work?
restarted device and reinstalled. still not working

aha .. ok.. now I see your problem...
You can't extract the files directly from a cab file with ex. winrar....
They will end up like this ... '4E6705~1.002'
use package-creator-v2.7 if you want to extract the files from a cab...
you can find it here...
http://forum.xda-developers.com/showthread.php?t=388883
Just run that and press 'Open Cab file'

[DEV-UTIL][19.03.2009]DriverWiz - Make signed CABs from driver DLLs that work

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.

[HELP] How to register a dll?

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.

Cooking SDKCERT in ROM

Hallo everybody,
I just want to ask how I can built in SDKCERT directly into ROM.If I want to convert SDKCERT.CAB to EXT then after I have again CAB so newerending story.

You won't need to use the SDKCERT package. If you are using Ervius Visual Kitchen for example, all you need to do is ensure that Disable Cert(ificate) checking is selected. This way, your compiled ROM will already have Certificate checking disabled allowing you to install updated drivers and such.
This tutorial discusses some of the changes you'll likely need to make:
http://forum.xda-developers.com/showthread.php?t=526610
HTH,

if you still need it ,here its is. just add to any package.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Thank you very much!!!

Johan Kraczmar said:
Thank you very much!!!
Click to expand...
Click to collapse
Np.
Here is a little tip for future...
most certificates are in cab form,open the cab with winrar,you will see a file called;_setup.xml, that is the cert info.
just rename _setup.xml to mxip_999_certname.provxml and you done.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks

He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Lewy1 said:
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks
Click to expand...
Click to collapse

af974 said:
He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Click to expand...
Click to collapse
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.

Did you tried the solution in post #3?
For which device are you trying to install?...from Vogue to -> ?
Sometimes from different devices isnt a certificate fault but some missing dll.
Check for this app Dependency walker and search if you have all the modules to make run camera Vogue.
Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.

hilaireg said:
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,
Click to expand...
Click to collapse
Farmer Ted said:
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.
Click to expand...
Click to collapse
First of all, thanks guys for your help!
Yes, your right that the problem is also when I try launching the camera from the windows directory. Now the problem is that I don't understand too much when it comes to digging into the contents of these files, so I think I'll need some help.
I assumed I needed Dependency Walker which you wrote about in your Kitchen Utensils review, so I opened the camera.exe and the results are attached as a Dependency Walker Image. The camera EXT I have come from converting a cab that's been floating around XDA. By the way I had the same problem when using the mega camera.
Thanks so much for the patience and help.

Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.

hilaireg said:
Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.
Click to expand...
Click to collapse
Thanks, that was quick. Looks like I got a lot of work ahead of me.