Last week I did a hard reset, but since then did not test the camera soft.
The camera is still working as I can use it with QCode. But camera.exe for the camera seems dead. I don't know if it is due to an other software installation since then.
Does someone have an idea to help me that would avoid me loose time redo a hard reset and install applications?
Given the titel you give this "Camera is not a valid Pocket PC Application..." I assume this is the message you are getting?
Can you check if the Camera.exe in /windows is in ROM or not? You can check with programs like Total Commander. If Camera.exe is not in ROM, delete (or rename) it. Also, Camera.lnk should be in ROM. If you delete the non-rom versions, the rom version should appear again (if you have Total Commander set to show ROM files)
If they are in ROM, do you get the message when starting Camera.lnk? Do you get the error when starting Camera.exe directly? Either way, you may need to not only hard-reset, but reflash your ROM as well. Are you using a custom ROM?
thank for your reply, indeed i have only one camera.exe file in the rom. I'll reflash the rom...
I did not flash my HD until now, that's the good time to do it ;-) I suppose that the problem appeared after I installed the Microsoft VB Runtimes for PocketPC.
Odd. If you did not flash yet and are still on factory ROM there is no reason why the build in camera.exe should be corrupted. It may indicate that above hypotheses is false, though I would not see how.
Do try a hard-reset before you reflash. If it is some other problem, like installing VB runtime, it should be gone after a reflash
machina2 said:
thank for your reply, indeed i have only one camera.exe file in the rom. I'll reflash the rom...
Click to expand...
Click to collapse
Just so we do not miscommunicate: You will only ever see one Camera.exe. The question is: Does it have the ROM attribute. If you (or any installer) install another, it will be in flash, and the ROM one gets 'hidden'.
So, do you see it with the ROM attribute, or did you assume because you saw only one that it was in ROM?
Looking at their properties, they are marked as ROM.
I deleted and got : "impossible to delete" . (seems logical if this is rom)
Before I hardreset / flahs phone, just for testing, would someone be able to send me the camera.exe file?
I'd like to help, but that is not so easy, with these devices, not only can you not copy to rom, you also cannot copy from rom. So it would have to be someone who dumped the entire rom on a PC using one of the ROM kitchens.
Ok, I hard reset and the camera works now. i will consciously reinstall my apps checking which one may have cause the problem. I wish it is not one of the games I said were working on the HD.
So I finally found that I was copying a file HTCSensorSDK.dll which caused this problem. mistake from me, I thought it was necessary for the graphic api.
Related
Hi. Are there actually any ported ROMs for the Uni that allows a super-clean (i.e. purely Microsoft) WM5? Thanks.
This is exactly what i am here at the Forum for please someone step up?
Cause i foudn one in general by name one time but im not sure if they are shapped for the Universal
I guess to clarify ...
A Clean version of WM5 shapped for the Uni if possible
I want to amke sure i do not lose any features
Please help thanks
rightnow im on the newest qtek but is actign weird so im going back to my orignal imate
don't install the extended ROM...
Can you explain SIMPLY which file is the extended ROM?
philby said:
Can you explain SIMPLY which file is the extended ROM?
Click to expand...
Click to collapse
What "ady" meant was:
1st: Install Buzz's Ext ROM Unlocker and unlock your Ext ROM.
2nd: Cut and paste them to your SD Card and save a copy on your computer for backup.
3rd: Perform a hard reset. Since you already took off the Ext ROM, you now have a pure Microsoft OS running on your device.
To answer your question, the Ext ROM is what you see being installed when you perform a hard reset. It is indicated by a progress bar during installation after a hard reset. The Ext ROM contains the customizations provided by the "Brand" name of your device.
The simpliest way to avoid the installation of the Ext ROM, if you don't want to unlock it is:
1st: Perform a hard reset.
2nd: "IMMEDIATELY" perform a soft reset by pressing the reset pin as soon as you see the "Microsoft Today Screen". By doing this, the installation of the Ext ROM is by-passed.
If you are going to ask me where to find the Unlocker. Just do a search. Hope this cleared it up.
Thanks for the excellent reply. Can you tell me what exactly would be excluded by not installing the Extended ROM contents? I am guessing this would be like selecting a corporate install on the O2 XDA EXEC?? Thanks again for any reply.
philby said:
Can you tell me what exactly would be excluded by not installing the Extended ROM contents?
Click to expand...
Click to collapse
Any customisations your operator has made. It's hard to say what exactly as that changes per ExtROM (and each new version of Windows Mobile by each operator has a new ExtROM so...)
If you don't install the ExtRom you have plain Windows Mobile, if you install the Extended ROM (which it will be default) it adds patches, customisations (backgrounds, sounds, GPRS settings etc), button configurations, home page settings, add icons, remove icons, custom programs etc.
My advise is to read the wiki (link in top left) open up your ExtendedROM as the poster above advised and then customise it how you want, or just by pass it completely each time and add in what you want manually.
philby said:
Thanks for the excellent reply. Can you tell me what exactly would be excluded by not installing the Extended ROM contents? I am guessing this would be like selecting a corporate install on the O2 XDA EXEC?? Thanks again for any reply.
Click to expand...
Click to collapse
xanth is absolutely right. The Ext ROM changes with each "Brand". I am attacching a link for the O2 Ext ROM explanation: http://forum.xda-developers.com/viewtopic.php?t=32527
Some applications in the Ext ROM, you can deduce what it is made for like "default_Backgamon etc...(which installs the game backgamon in Imate Ext ROM) and some are similar to O2's, so let it be your guide.
why
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Re: why
sandrobber said:
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Click to expand...
Click to collapse
Actually ALL WORKS FINE with a clean install, as mentioned above, the only thing you might have to add is the settings for MMS, and video call capabilities. But ALL SOFTWARES INSTALLED WORKS. From BT to WiFi, camera app, voice dial, etc... I know because I already tried it.
Re: why
sandrobber said:
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Click to expand...
Click to collapse
Well that depends on the base Windows Mobile ROM. Some will have some features, while some won't (won't fit possibly?) and would require the ExtROM to install them.
I appreciate this is a Universal thread, but one example is the BlueAngel. The SX66 doesn't come with a camera so it's ROM doesn't contain camera software and if you used that on a regular BlueAngel (XDA IIs for example) you'd need to install the camera software seperately.
Hope this actually makes sense.
what about a real clean ROM...
i mean a ROM that does not contain any of those "dog barking" junks media files and themes (there is around 8MB of these), as well as unnecessary EXTROM files. YET sparing drivers for camera, bluetooth , and other crucial drivers.
thanx
go it
then you are correct to hard reset then soft reset before your device wants to load the ext-rom
unnecessary media files are not in the ext rom
they come with the winows folder and the my doc. they r more than 8mb , and they serving for NOTHING... so stopping the erom wont save you from them
So, some of you have this error, some dont. So lets try and figure it out. Heres what we know.
The problem affects ALL Artemis WM6 ROMS.
Remember, the issue doesnt appear when just using it normally. Its only under certain circumstances. Heres how you re-create the problem.
Run Tomtom, this causes the error90% of the time.
Create a new word document and try to save anywhere.
Heres my setup and what ive tried to fix it.
Device: MDA Compact III
SD Card: 1gb
Ive tried font cache size, system cache, removing the memory card.
Please dont post "I dont get the error" if you havnt tried running tomtom or saving a word document.
Thanks
To add to the problem re-creation, I was trying to copy a directory with around 15 files in it from the internal memory to the storage card, the message just kept popping up for all the duration of the copy process, I stoppped clicking ok eventually. I looked at the free program mempry available then and it was pretty good at around 22mb.
Device: Orbit XDA
SD Card: 1gb
I too have noticed that looking at the free storage space seems to fix it for tomtom (but not word). There is something else wrong with Excel in that the "Save As" is in the wrong place, infact where it is isnt actually save as.
You're right, I haven't noticed this before with excel. I can't remember if it was like this before, was it? It won't be easy figuring this little memory issue out. I hope someone has a trick up their sleeves.
I have the WM6 emulator running on my pc and the excel thing isnt there. Comparing the registry settings on the emulator with my device. I would love to hear if anyone does actually have Word working without issue.
BREAKTHROUGH!
OK. I installed the original Orbit rom and... IT WORKS!!!! So the question is what did bepe and the guys do when they de-branded it? The orbit rom has an Ext-Rom with a load of branded stuff PLUS! some patches. I bet one of these patches fixes the issue!
These custom roms have NO Ext-Rom at all, hence the increased storage space. however in the process of removing the ext rom they have managed to cause these memory errors.
So guys, any chance of a rom close to the Orbit rom but with the English language and Ext rom left in tack?
Great work mate, it is the removal/merging of the extended rom that's causing the problem then. Maybe it's not even a patch in the extended rom, maybe it's the way the extended rom was merged that's causing it. This surely deserves more looking into.
Great breakthrough
Word FIX!
Thanks to pvdhelm for the tip on this one. Attached is a patch to fix the memory issue with word (and only word). To fix it for other apps you need to view the memory in the control panel and click on "Storage Card". The word fix is pernament but the other memory issue it only until you reset your phone.
Absolutely brilliant, so it looks like missing registry entries!! We need to find out what was in the original extended rom then to find out if we're missing anything else. Looks like only me and you here, you should post this fix in the main threads mate.
Cheers and well done.
I have a copy of the rom, tried isntalling it all but to no avail. It looks like on boot up the system thinks it has a different ammount of ram due to the ext rom being merged. By displaying the ammount of storage it realises it has a different ammount and fixes it. Until the next reboot. So if anyone knows what changes when you view the storage that may be fixing it I would love to know.
Or if somone can make a rom with the ext rom still in place.
EDIT: Heres one just for the MDA Compact III without WiFi users. It applys the Word memory errror fix but also fixes the Comm Manager issue and does so just for the MDA as it removes WiFi from the list.
Maybe this is a clue for you all. I have never had these errors, ands I use Tomtom daily and have tested word for you again with no fault.
The difference? Well I upgraded to WM6.0 the original way before USPL patch and flashed the OS only. I'm assuming you with problems used the ROM installer method. Am I right with my assumption? If so that should narrow down the culprit.
I used Bepes original WM6 WWE OS only upgrade, therefore the Ext ROM on my device is still the old T-Mobile WM5 one and was simply not allowed to run. So it can't be right to assume there is something missing from an EXT ROM patch.
It's most certainly the extended rom being merged then, there's nothing else to it.
gajet, can you give me the exact steps you took. I went from the T-Mobile rom to Black and blue then to the others. I uses USPL first though.
Can you give me a quick set of steps you took i.e Original T-Mobile rom, then ran USPL, then updated to Bepes.
Also, if you used bepe's can you also tell me which rom update util you used? as the one ive tried has errors at the end.
Thanks
dannyoneill said:
I have a copy of the rom, tried isntalling it all but to no avail. It looks like on boot up the system thinks it has a different ammount of ram due to the ext rom being merged. By displaying the ammount of storage it realises it has a different ammount and fixes it. Until the next reboot. So if anyone knows what changes when you view the storage that may be fixing it I would love to know.
Or if somone can make a rom with the ext rom still in place.
EDIT: Heres one just for the MDA Compact III without WiFi users. It applys the Word memory errror fix but also fixes the Comm Manager issue and does so just for the MDA as it removes WiFi from the list.
Click to expand...
Click to collapse
VERY interesting reading!
If you move this thread, please drop a link on here for us, thanks. The first one to crack this problem will be worshipped from afar I am sure!!
I think it could be an order of upgrade issue, heres the latest.
1. Downgraded to T-Mobile WM5 rom
2. Ran USPL
3. Upgraded to Bepe WM6 using the EXE version
The word issue is no longer there but the out of memory in Tomtom is. Also no ext rom.
It would be good to know from others and gajet what steps they took and which files they uses to do it. Especially as gajet still has his extended rom.
I've tried:
official t-mobile wm5 to german wm6 to bepe uspl &
official t-mobile wm5 to bepe uspl
Both times I have had the error with tomtom but no problems with word.
Both times temp fix (looking at storage) worked (sorry about font cache red herring - thought I was onto something there).
Just tied chi-tai extended battery plugin with the storage showing on the homepage (as a way to force system to get correct memory) but no joy.
I have htc touch com manager and phone skin but not the home plugin.
Cheers
Matt
I think Ive cracked it. Just doing some final testing but watch out for a new "How to" thread.
go Danny go.
Look forward to seeing it.
Will test and report back once you've posted.
Cheers
Matt
Sadly the original thread was edited to reflect the OS update was repackaged but eddie2k still goes on the reexplain the process in this thread.
eddie2k said:
then use winrar to unpack the (bepe) wm6 wwe rom in this page (written in red). flashed using bootloader method.
after u get german rom installed , run ARTE os flash utility from xda ftp (log in properly) link don't work if not logon properly..
ftp://ftp.xda-developers.com/Uploads/Artemis/arte.zip unpack
copy os.nb from first folder (bepe) wwe rom to arte folder and rename os.nb to windows.nb then run UpgradeRom.bat
hard reset, soft reset done.
Click to expand...
Click to collapse
Now I didn't bother installing the german O2 release as my MDACIII was CID locked, so I just used ARTE package with Bepes WM6 .nb renamed and flashed the OS only, then after hard resetting, at the point of about to load EXT ROM soft reset.
This thread was also the guide although you could skip the process of extracting the .os from a ROM package as Bepe originally provided us with the raw windows.nb file.
Thanks gajet, Ive just posted the steps. Your post was deffinatly the key. Once I saw you still had your ext rom I knew we could do it.
Answer is here
http://forum.xda-developers.com/showthread.php?t=313486
Hello all, best wishes for all of you.
I am new on this forum and read many stuff here allready. However i didn't find a real solution yet for my problem to get cab-files installed, f.e.:
I'd like to install Gyrator 2 on my HTC Touch HD (UK) (And other software)
When i try this i get this error:
"The file "gyrator" cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring the file".
The same message occures when i try to do this with other cab-files. GSen was going fine and even CabInstaller did. Net Compact Framework 3.5. installed and ROM version: 1.14.401.3
I copied the cab-files from PC to PPC by dragging it into the Storage Card.
I would really appreciate your help, because im goin' nuts!!!
Tia ....
Hello.
try this:
- make a soft reset and try again to install from the SD card
- make a soft reset, copy the .cab file with activesync to the phone memory (not on the SD card) and try again to install
when this also won´t work I´m afraid you will have to hard reset your phone..
i had same problem
why dont you just use Gsen, same thing, works great! its definately here
BlackMonkey said:
Hello.
try this:
- make a soft reset and try again to install from the SD card
- make a soft reset, copy the .cab file with activesync to the phone memory (not on the SD card) and try again to install
when this also won´t work I´m afraid you will have to hard reset your phone..
Click to expand...
Click to collapse
Didn't work either ... A hard reset? Uhm .... Don't like that, i hope and will wait first for a solution ...
patterns said:
i had same problem
why dont you just use Gsen, same thing, works great! its definately here
Click to expand...
Click to collapse
As said it is not only Gyrator but it occures with more cab-files. The rotate is not my only goal, therefor i surely could use Gsen, but Gyrator 2 cn do much more. The same with other 3rd Party's ...
Use Advanced Configuration to make sure that your security warning is disabled.
What .cabs are you trying to install?
Problem SOLVED!!
AllTheWay said:
Use Advanced Configuration to make sure that your security warning is disabled.
What .cabs are you trying to install?
Click to expand...
Click to collapse
Problem solved! The way i used CabInstaller was wrong. Instead of open the CaBinstaller first and then adding the cab-file and destination path, i double clicked on the cab-files first and then it won't work, because i gave CabInstaller permission to take over the control of installing cab-files
Thank you anyway for thinking with me ..
Great to hear you solved your problem!
<off-topic>Could you please change your subject in the initial post? subject is supposed to describe what the thread is about like "unable to install CAB files" or something like that...thanks<off-topic>
Hi, my bluetooth does not seem to work on the device. If I reset it i get the error message on start up saying 'BTTRAYCE' is not a vlaid Pocket PC application. Is my unit faulty. I have thought about doing a hard reset on the device but wanted to check with you guys if there is a simple fix, the unit needs replacing? or if the hard reset would work. If I was to do the hard reset what can I use to backup all my contacts with there facebook links etc and will the facebook links still exist?
Bladesharp said:
Hi, my bluetooth does not seem to work on the device. If I reset it i get the error message on start up saying 'BTTRAYCE' is not a vlaid Pocket PC application. Is my unit faulty. I have thought about doing a hard reset on the device but wanted to check with you guys if there is a simple fix, the unit needs replacing? or if the hard reset would work. If I was to do the hard reset what can I use to backup all my contacts with there facebook links etc and will the facebook links still exist?
Click to expand...
Click to collapse
You can use a program called Sprite Backup, although its not free. That will backup a lot of things, but to be honest, its probably best to start from scratch as it backs up all registry changes too, which could be the problem for you.
My bluetooth works fine, what part are you having trouble with?
Bluetooth Issues
I am having the same problem.
I have narrowed it down to tomtom installation (no bluetooth issues until tomtom is installed)
I have tried with TT7 910 9185 as well as TT7 445 and after the reboot the same error occurs.
I have also tried installing it on the memory card, and hard resetting it, however, the TomTom doesn't appear to talk to any Satellites.
I installed Tomtom 7.910.9185 and it says "Unable to start. Not enough memory" or similar. I installed it from cab on my 8GB Storage Card in the same way that worked perfectly on my Raphael.
The point of telling you that is my bluetooth is still working perfectly.
As for you Bladesharp, surely if you Activesync all the relevant links and details will remain with your contacts? I'd say a hard reset will determine if it's a hardware issue.
rb14 said:
I installed Tomtom 7.910.9185 and it says "Unable to start. Not enough memory" or similar. I installed it from cab on my 8GB Storage Card in the same way that worked perfectly on my Raphael.
The point of telling you that is my bluetooth is still working perfectly.
As for you Bladesharp, surely if you Activesync all the relevant links and details will remain with your contacts? I'd say a hard reset will determine if it's a hardware issue.
Click to expand...
Click to collapse
I'm on 7.915 for TomTom and don't have the issue.
Links to Facebook won't transfer with Active Sync, they are stored somewhere seperately on the phone and are not part of the Contacts program in pOutlook.exe, they are part of Manila which is not transferable. Not sure where it is stored, have been looking now for about 2 months
I came across something similar to this last week after installing TomTom from a CAB, and found this post on a related issue...
http://www.noeman.org/gsm/trash-section/65951-tomtom-7-bluetooth-problems-sorted.html
I deleted the two bluetooth files (BtSdKCE30.dll & BtCoreIF.dll) from the TomTom CAB as described, did a hard reset and reinstalled, and haven't had the problem since. Could be the same issue?
Could someone who has not installed TomTom please post the dates of their BtCoreIf.dll & BtSdkCE30.dll? Mine are both 04/24/08 20:10.
Does anyone know if it is possible to revert to the ROM version of these files WITHOUT doing a hard reset?
If some kind person was able to provide me with the ROM version, can I just overwrite the ones in RAM?
R
These came from my device's \Windows directory, and are dated 14th May. I think they are unaffected by this problem, certainly I don't get the boot delay or BTTray boot crash that seem to be the possible symptoms of this. (Use caution, of course; backup what you can before tinkering in case of disaster.)
Sounds the same as my thread
http://forum.xda-developers.com/showthread.php?t=522373
someone already tried the above files? will it correct the problem?
Thanks for the files.
I am happy to confirm that installing the two DLLs gets BTTrayCE.exe working again.
I just renamed the 04/24/08 versions to .was and use Total Commander to copy the files from my storage card to \Windows and rebooted the phone... ActiveSync wouldn't let me copy them directly from my PC as it said there was already a 05/14/09 version there and it was read-only!
As it rebooted, it complained that BtCoreIf.dll was from an unknown supplier but I just OK'd that and everything is fine. Bluetooth & TTN working.
R.
PS Didn't need to copy BTTrayCE.exe as this had not been overwritted.
Ah, thanks for letting me know. I wasn't sure if the exe was also needed, I only included it since one of the symptoms I was getting was that this wasn't a valid executable; but I guess that was just caused by the corruption of the dll's.
I don't think the DLLs are corrupted, just an earlier version.
Just like the bad old days of Windows 3.1 where installing one package would break others due the installing of different versions common DLLs. Gosh, I feel old!
R.
dicko99 said:
I don't think the DLLs are corrupted, just an earlier version.
Click to expand...
Click to collapse
Ah yes; that makes more sense! I still had a boot delay even with the files from the most recent TomTom version I could find.
Hi there,
i had the same Problem with TT. In my case I also copyed the BTTrayCE.exe. Now I dont get any error anymore but the Bluetooth can still not be started. Can somebody please upload the Original BTTrayCE.exe. Thank you
I did a reset of my Swisscom German Device. Copyed the 3 BT Files and installed the TT7 v7.910.9185 again. After restart of my Device the same BT Error. I replayced the 3 Files with my Original ones and restarted again. New Error comes up "Bluetooth Stack can not be started"
zizzo
Thanks guys a lot. Rewriting those two files solve the problem. Bluetooth works now.
ianjd said:
These came from my device's \Windows directory, and are dated 14th May. I think they are unaffected by this problem, certainly I don't get the boot delay or BTTray boot crash that seem to be the possible symptoms of this. (Use caution, of course; backup what you can before tinkering in case of disaster.)
Click to expand...
Click to collapse
Thanking you very much kind sir. I unzipped these files directly to my storage card in USB mode and just double clicked the exe file and it fixed my bluetooth up for me. (good job as I am a technical biff when things get registry level)
EDIT sorry I thought it did but it didn't just fix it by double clicking the exe. I've hard reset now as I don't really know what I am doing
As said in the thread here:
http://forum.xda-developers.com/showthread.php?t=522373&page=4
There is no need to replace the two files.
Just delete them and soft reset. They will be replaced with the two right ones.
Bluetooth problem with TomTom resolved!
matrixis2day said:
I replayced the 3 Files with my Original ones and restarted again. New Error comes up "Bluetooth Stack can not be started"
Click to expand...
Click to collapse
I had the same and here's what I just discovered and what worked:
I removed the files and expected them to be replaced upon restart. When I checked I noticed a file in the \Windows directory named BtSdKCE50.dll - I had not noticed this before. I (re)moved this, rebooted again and now Bluetooth and FM Radio (!) are working, yay!
hth,
TA2
This fixed my problem. Couldnt delete the old files but copied the replacements over the top and that sorted it. My version of Tom Tom wont work stil but it is 7.5 I think.
I've had exactly the same problem I've tried overwriting the dll's with the files provided in this thread,
Now whilst I don't get the error message, when I try and enable bluetooth, I get "cannot start bluetooth stack" error
Any ideas peeps?
I put 6.1(same with the 6.5) on and i am geting errors from old files(pics,vids,everithing).i get there is no application associated with *filename* run the application first....
I get the same error if i install a app from a cab file and try to run it.
Didnt find anything with the search.any ideas.
Either the roms you tried don't have the proper software/codecs installed, or the files have gotten corrupted.
I'm guessing you flashed the at&t stripped rom between flashing cooked roms?
That's all I can think of.
yes i flashed at&t between roms.
You could try crc's full rom or my rom, I know the video and pictures work in them.
all the old files seem to be .denc endings now(*.doc.menc etc)
it seems i hade the encryption option enabled on my old rom, so all the files on my sd are encrypted.
Not too sure you will be able to recover from that, I never tried encryption.
well you can go back to wm 6.1 or 6 im not sure, those builds has the encrypted app for SD and decrypt them again and please dont use it again, or your apps will eat more ram than normal... and gives you some low ram or other issues.