Related
After watching for months the issues that many have suffered over this problem, I finally found a solution that will fix all the woes.
A few months ago I was one of the many here that upgraded to 1.11 ROM, had the problem. It drove me crazy to the point that I went back to the 1.06 ROM that was rock solid. Well the other day I did a hard reset to have a clean slate. While looking at the Extended ROM I saw the file DefaultV_1.12 in the EXT Rom (Compared 1.11 ROM on FTP to my device). This was the same file that a XDA developer member had modified to somewhat solve the GPRS problem a few months ago.
At this point I had a hypothesis, so I pulled the same file from the older 1.06 ROM which was rock solid and did not have the “Cannot Connect” problem. In this EXT ROM it is named Default_Version_WWE_106150.sa.CAB.
Installed it first on my Blue Angel as a guinea pig, then for the next three hours I would sit there and disconnect and reconnect. I did it manually by holding the red button to disconnect, then I would reconnect to another webpage, then would have a call come in while in the middle of the GPRS session which would suspend it. After done with the phone call I would reconnect manually by clicking connect as well as by just hitting a link on the webpage.
The Results: No “Cannot Connect” problem.
So off I went to my Magician:
Upgraded to 1.11(I have 850 JAM)
Installed Default_Version_WWE_106150.sa.CAB
Put the phone through its paces, I have been disconnecting and reconnecting without a single problem. I receive phone calls that suspend the GPRS session and I am able to reconnect without a problem. Activesync is able to make OTA connections without a hitch.
During my trials I used the same programs:
Which included:
Photo Contacts(newest version)
Activesync
WEBIS Mail 2
xVbar
PocketZenPhone
Regking 2003
As the only variable throughout the trials was Default_Version_WWE_106150.sa.CAB
This is the solution folks.
At least until someone says it does not work.
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
1st of all let me say this is a great site for the HTC devices, I found it years ago when i had the first XDA (Wallaby i think) and now i own a O2 Mini.
I have just installed your patch and i'll let you know how it goes.
I wonder if this patch does the same as the "downgrading" of the caller id as detailed in this thread: http://forum.xda-developers.com/viewtopic.php?t=20428
The downgrade has been succesful for blue angel users too.
randomshots said:
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
Click to expand...
Click to collapse
Many thanks for posting this information.
For a relative newbie like me who has never manually fiddled with ROM files, can you please explain what I actually have to do to "install" the CAB file, i.e. in which directory on the device do I put it, and how do I run it?
- Peter
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
don't work for me
don't work for me. same problem as before, can't connect due unknown reason.
thanks anyway.
Orcas what is your ROM?
randomshots said:
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
Click to expand...
Click to collapse
The downgrade of caller-id to an earlier version has also solved the problem totally for me and several other people, both blue-angel and magician users. Thats why I was curious just what your patch did. Seems that it is something similar, you are maybe downgrading more of the rom?
Did you try downgrading of the caller-id first? Not just photo contacts but downgrade to the specified earlier build of caller-id?
randomshots said:
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Click to expand...
Click to collapse
Hi there,
Just thought I'd report that I've just installed it. My ExtROM now reports as 1.06.150 WWE.
And... so far, so good!!! I've connected/disconnected to GPRS multiple times, interrupted GPRS with a phone call and then reconnected, have sent files to my device via BT while GPRS is on, and still no problem. It's looking very good!!!
And I'd swear it connects faster than it did previously.
Anyway, I'll keep hammering at it over the weekend and report back on Monday.
Thanks again randomshots!
Well, I'm back already, because I still have the problem. DARN IT!!!!!! :x
The thing that made it happen was that I made a phone call while GPRS was on. When I ended the call and tried to reconnect to GPRS, I got the blasted error. So it seems that receiving a phone call does not cause the error to happen, but making a call does. At least for me.
Oh well, it was worth a try. Back to the drawing board.
Same problem in Hong Kong
I upgraded to ROM v1.11 a few days ago and since then I have the GPRS connection error after 1 or 2 connections. Soft reset will solve the problem. This problem was not encountered at all before the ROM upgrade. It must be the new ROM that mess things up!
As this "default cab" from an old rom seems to solve the problem and also an older version of caller-id solves it there is probably something wrong in the communication between caller-id and some of the customisations from this cab on newer roms. Btw the problem is also in 1.12 roms.
Nice too see that we have two possible solutions here, I will stick to the downgrade of caller-id as it has solved the problem totally for me but it would be interesting to know what the real cause is...
Hi again. Just to answer the previous question to my post: my rom version is 1.12.00 WWE, radio 1.12.00, extrom now says 1.06.150. i think the only thing this cab changes is this rom number, nothing else
orcas
orcas,
I believe you are absolutely right. When the extended rom has finished installing the programs, it runs this .cab file to 'brand' the Magician with the build number. Nothing more or nothing less. But faith can move mountains, as we all know...
I guess some of you know that there is another (older) thread about GPRS problems. If you do not, there is a link below.
Anyway, I finally tried the most recent suggested fix in that thread (downgrading the device's CallerID program to an earlier version) and like a number of others I can happily report that so far, it has fixed my GPRS cannot connect problem. Looking good.
Here is the thread:
http://forum.xda-developers.com/viewtopic.php?t=20428
- Peter
Just thought I'd share that the second fix I tried (downgrading CallerID) has continued to work for me. I have no more problems with GPRS. All is well with my Magician. At last.
Hiya All,
I'm trying to install Hebrew language extender on my Imate Jam rom 1.12
I'de a previous version installed which was fine, tried to uninstall and install a new version because of some minor problems which I though that will be solved in the newer version.
The problem is that during the installation, the install wizard tries to install tahoma and tahomabd fonts to the ppc device and fails in that operation.
The exact error message is "Can't copy C:\Windows\Fonts\\tahoma.ttf", yep with double "\\".
I've also tried to copy the original version which I'd but stayed with the same results.
Any opinion on how to solve this mistery ?
Thanks in advanced,
Bright Star
Sorry, I can't help you with that, but I can confirm that this software is very bad for your Magician.
I purchased the Danish version and ran it for some time. During that period I had a LOT of problems with the BT icon dissapearing.
I started noticing that after a hard reset, the icon was always there until I installed the Language Extender, and then it was gone! Sure enough, since I stopped using this program, my BT icon problems has nearly dissapeared.
So unless someone comes up with a better idea, all I can say is hard reset your Magician and don't use this crappy software again
hi everyone!
as there are many various cabs flying around here (eg. cab & cab2 from xplode, Addon cabs on Helmi_C's WM06 rom, various HTC plugins, etc.), i wonder if there is a correct or some kind of "best" order to install them!
how does everyone's install sequenz look like?
are there any known problems, which result from installing in a wrong order?
or is it totally nonrelevant...?
regards,
krz
AFAIK the only cabs to be installed in a order are:
1. ArcsoftMMS4.2.8.1.cab
2. MMS_enable.cab
from Xplode cabs2
DANDANA said:
AFAIK the only cabs to be installed in a order are:
1. ArcsoftMMS4.2.8.1.cab
2. MMS_enable.cab
from Xplode cabs2
Click to expand...
Click to collapse
QFE
You are right about that
thanks for your answers!!
i knew about the MMS cabs...
i just wondered, because the first time I upgraded to WM2006, everything worked totally fine. I hab no problems no matter what, wifi worked like it should, bluetooth as well, no turning on here and turning on there again (HTC Home Prob), ...
now, after i have downgraded to WM2003, merged the ExtROM and upgraded to WM2006 again, i am experiencing loads of problems!!
the "turn wifi on"-bug occured, i could not turn wlan adapter on with one simple click on the icon in CommManager...
then, after a softreset, the device froze while booting (there is some other thread about that problem). so i had to perform a hardreset again...
i configured my device again and installed the various cabs again, but in the end my device turned out to be totally screwed... turning on wlan was a pain, message-windows in which u can normally choose one of the available wifi spots were text-less (just empty window, only headlines visible...)...
so, i had to hard reset my blueangel the second time today and am now sitting in front of a fresh install of WM2006, thinking about what to do.....
what cabs should i install?
which HTC Home cab is actually the "best"?
any known problems regarding PPCContacts Manager?
do you thinkl, that those problems are somehow connected to merging ExtROM?
disappointed,
krz
ps: can anyone recommend a good backup problem, which saves me from setting up all settings all over again after eacah hard reset(timezone, regional settings, device id, reg tweaks, ...) ??
I keep it clean as i can
Rom version: 6.10.00
Rom Date: 27.02.2008
Page Pool: 16 MB
Core: 5.2.19199
Build: 19199.1.0.0
AKU: 1.0
OEM Software updated:
Sim Manager 6.38
InvokeSIMMgr.dll 1.12
PhoneSetting.dll 5.38
POWER_SERVICE.dll 2.16
STK_Service.dll 4.58
STK_UIPPC.exe 4.56
USSD_Dll.dll 3.16
Comm Manager 2.06
DataDisconnect 1.12
Changes from the original 19199 rom:
Replaced the calculator with SPBCalc and added Touch skin to it
Replaced today images with black ones
Groupped the start menu items in subfolders like in all of my roms
Replaced Welcomehead.96.png with one matching the today images
Removed most of the ringtones
Removed the default themes (left only windows default it can not be removed)
Removed Windows Update
Removed Windows Marketplace
Removed Remote Desktop Mobile
Removed VoIP
Removed Transcriber
Removed Office
Most of this software is available as cabs see the following
Example EXTROM:
Extrom_version.CAB - sets the extended rom version to xplode_7.00
AdobeReader_2.00.288531.CAB - Latest Adobe Reader from the original 19199 rom
htcflashlite.CAB - Latest HTC Flash Player from the original 19199 rom
HTC.Album.1.0.822.716.CAB - Old but working
HTCHome.2.1_1005.722.CAB - Old but working
JbedJava_MIDP_0_0_20070822_1_1_WWE.CAB - Latest Esmertek Jbed Midlet Manager from the original 19199 rom
RDM.CAB - Remote Desktop Mobile from the original 19199 rom
VoIP.CAB - VoIP Support from the original 19199 rom with configuration addons
WU.CAB - Windows Update from the original 19199 rom
WU_enable.CAB - Enable Windows Update (windows update will not work without installing this cab)
Office_6.1.19199.CAB - Office 6.1 with OneNote from the original 19199 rom
Arcsoft_MMS_5.0.31.7.CAB - Arcsoft MMS Client from the original 19199 rom (for some reason the mms settings not show, this is a common bug with this version)
NetworkPlugin_1_0_30468_1.CAB - Latest HTC Network Plugin from the original 19199 rom
AudioManager.CAB - 1.02 409.721 Old but usefull
BT_BPP_1_6_1_0.CAB - Latest HTC Bluetooth Print Plugin from the original 19199 rom
Windows_Live_10.6.0034.0800.cab - Latest Windows Live Mobile
MMS_enable.CAB - This cab enables MMS folder in the mesaging application
BlackBars.exe - This program automatically makes your up and down bars black
Upgrade HOWTO:
1.Download the archive below
2.Extract it to folder in your computer
3.The password for the archive is blueangel
4.Copy EXTROM folder to your SD card (customize it if you want to)
5.Put your device in bootloader mode - For help with this step read here
6.Run Upgrade.exe to start the upgrade procedure
7.After finishing the upgrade wizard soft reset your device to exit bootloader- For help with this step read here
9.Hard reset your device - For help with this step read here
10.Allign screen
11.Wait for the instalation of the cabs from the EXTROM after that the device will soft reset
Congratulations, you are ready to use your device
Notes:
If you have problems or errors with the upgrade utility kill activesync, remove the SD and sim card and retry. After upgrade is completed before pressing the soft reset to exit bootloader insert your sd card in order for EXTROM to kick in. Anyway you can use the rom without any extrom
The HTC Home theme is not included because i have no permission to use it
Download:
RUU_BA_xplode_WWE_6.10.00.rar
Mirrors
http://rapidshare.com/files/95699386/xplode_WM6.1_Pro_CE_OS_5.2.19199__Build_19199.1.0.0_.rar
http://www.sendspace.com/file/qpjpwm
http://www.megaupload.com/?d=72PSPOXQ - by LGSilva
Known Bugs:
The comm manager icon in system tray does nothing on tap - solved see the attached cabs
WMP is skipping when playing MP3 - solved see the attached cabs
Wlan has problem with authentification and does connect very hardly to a protected network - solved see the attached cabs
Camera app crashes after recording MP4 video - working on it (actually it records the video but can not preview it in camera app, but you can view it from any multimedia player which is mp4 capable like WMP, TCPMP, CorePlayer ...)
MMS Settings does not show at all - working on it - temporary solution use the previous version - from here or from cabs2.rar from helmis rom thread (here and here)
OBEX problem (can not recieve files trough BT) - install attached EnableOBEX.cab, go to Start=>Settings=>Connections=>Beam and check "Recieve all incoming beams"
Attached fixes:
WlanMgr.cab - this is a registry setting that maps the comm manager icon in system tray to Wlan Manager
CommManager.cab - this is a registry setting that maps the comm manager icon in system tray to Comm Manager
WMPFix.cab - this is a fix to WMP skipping during playback
!WLAN_Fix.cab - this is a fix to WLAN authentification issues (wifi just does not connect or connect very hard)
HideSimContacts.cab - as the name show this cab hides sim contacts from the contact list
EnableOBEX.cab - adds IsEnabled=0x1 in [HKCU\Software\Microsoft\Obex] - enables obex service on startup
If someone needs .NET CF 3.5 Press Here
FlightMode.cab - for all of you with FlightMode problems this is a lil app from WinMobileApps.com which switches flightmode on/off - the shortcut is created in Communication folder
Cool ! Thank you very much, Xplode.
So, how did you managed to do it without a working BA ?
Also, 2 questions:
1) I though WM6.1 was not officially released yet, is this a alpha, beta, RC or the final version ?
2) Would be nice to see what improvements could we expect from WM6.
Cheers,
JP
Great !!! Waiting for your ROM long time man.Thanks
i got new screen from ebay but it stopped working properly i am disassemble my BA again to see what happened ... (i have no luck with it)
well there was only one official WM6.1 rom by Vodafone for Kaiser this is a port from it
Improvements over WM6 are posted all over the board, don't be lazy do a search
How about WIFI and .NET CF?
xplode said:
i got new screen from ebay but it stopped working properly i am disassemble my BA again to see what happened ... (i have no luck with it)
well there was only one official WM6.1 rom by Vodafone for Kaiser this is a port from it
Improvements over WM6 are posted all over the board, don't be lazy do a search
Click to expand...
Click to collapse
Xplode,
Yes i have seen other WM6.1 threads in the forum (in fact there is a lot of them, specially from pdaviet), but you don't mention for instance if you are using "wifi driver v2" or not, nor if any other speed or stability improvements will this ROM bring versus your WM6 ROM, i meant.
Also any know issues from BA's WM6 solved, etc.
Just a thought.
JP
AAAA, can´t wait longer !!!
i have checked 3 times a day for an update ! (the last 2 weeks !)
(have donate already......)
We must wait... I have PDAviet 6.1 rom but i think that Explode's rom will be better. Respect man you have made grate work!
a couple of minutes to go... must... wait... a little... longer...
thanks for keeping it "clean", which bolsters my hope that it doesn't have the zoomsms application
it's very considerate of you to include the steps on how to upgrade, and to give a description of the ROM.
congratulations on your work, xplode, and good luck on your screen.
Good work explode
thanx a lot man ur the best . I will try it soon ...Im sure it will be great
thnx 1 milliard times
i'm install now
Thanks alot for this great rom!
I found the same wifi-issues like in pdaviet-roms 191999. Wifi isn't really happy to connect to wpa-protected networks. As workaround you can turn on wifi, configure your network settings, turn wifi off without connection. Than turn on wifi several times and wait. On my BA ist will connect after 2x turn on/off most of the time...
Will test other nice features of wm6.1 now...
Hi Xplode! Thanks again for your great releases.
Does this Rom includes Wifi v2? if not, have You tested if it works in this rom?
Thanks for your great rom
Thank you very much.
The rom has the default .NET CF 2.0 SP2, It has not WIFI Driver 2 (i am not sure why you calling it that). Wifi behaves the same way as in my and helmi wm6 roms.
Waiting for a long time till today!
Thanks in advance!
But cannt download...
Nice ROM!
One of the MOST anticipated release...
Thank you so much for the effort Xplode...
Most excellent work!
xplode said:
I keep it clean as i can
Click to expand...
Click to collapse
And clean it definitely is ... running very smoothly and stable. I've not run into any issues with using the applications/setup I use, including the entire EXTROM as you've provided.
WM 6.1 ... Mmmmm ... yummy.
I found out only a few days after I installed the 1.64.08.21 radio rom that my camera was not working anymore :
black screen, hyper slow, "Unable to capture photo. Unable to get frame data from camera device.", cannot switch from rear to front camera, forced to kill the process to exit.
I saw a few threads related to Kayser saying that camera problems were linked to radio rom.
I tried many combinations to revert :
1.64.08.21
1.58.25.14
1.58.21.23
1.70 OliNex
nothing changed : camera still not working (although it worked well with Olinex and 1.58 before I switched to 1.64)
I even tried different main rom sets and SPLs to come back to the original config : HardSPL 2.20, SPL Original, WM6.1 bepe 67, WM6.1 Aserg, SFR 1.25.406.1, SFR original... camera still not working.
The only positive thing is the Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab released on Kayser that makes the camera application usable again (not slow anymore, but screen is completely scrambled, multicolor and showing front camera image when using the rear camera, and switching between rear and front cameras shows that the front camera only works, keeps saying "unable to capture photo" when using the main rear camera (and sometimes with a strange sound like some diaphragm trying to autofocus).
The phone did not receive any shock, so I am a bit skeptical about a hardware issue suddenly rising, but I am concerned by the fact that reverting to any rom does not make the camera working anymore after 1.64.08.21.
My latest working config was
WM6.1 Bepe 0.67 Standard
1.70 OliNex
Please share and if someone found a way to make the camera work again (if this issue is software only and can be fixed...) that would be great !
boldbull said:
I found out only a few days after I installed the 1.64.08.21 radio rom that my camera was not working anymore :
black screen, hyper slow, "Unable to capture photo. Unable to get frame data from camera device.", cannot switch from rear to front camera, forced to kill the process to exit.
I saw a few threads related to Kayser saying that camera problems were linked to radio rom.
I tried many combinations to revert :
1.64.08.21
1.58.25.14
1.58.21.23
1.70 OliNex
nothing changed : camera still not working (although it worked well with Olinex and 1.58 before I switched to 1.64)
I even tried different main rom sets and SPLs to come back to the original config : HardSPL 2.20, SPL Original, WM6.1 bepe 67, WM6.1 Aserg, SFR 1.25.406.1, SFR original... camera still not working.
The only positive thing is the Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab released on Kayser that makes the camera application usable again (not slow anymore, but screen is completely scrambled, multicolor and showing front camera image when using the rear camera, and switching between rear and front cameras shows that the front camera only works, keeps saying "unable to capture photo" when using the main rear camera (and sometimes with a strange sound like some diaphragm trying to autofocus).
The phone did not receive any shock, so I am a bit skeptical about a hardware issue suddenly rising, but I am concerned by the fact that reverting to any rom does not make the camera working anymore after 1.64.08.21.
My latest working config was
WM6.1 Bepe 0.67 Standard
1.70 OliNex
Please share and if someone found a way to make the camera work again (if this issue is software only and can be fixed...) that would be great !
Click to expand...
Click to collapse
Flash Original ROM and you're back in business.
reyjabs said:
Flash Original ROM and you're back in business.
Click to expand...
Click to collapse
Not true
I flashed all roms including the original one (raramomo_ROM_SFR_Original) and still not working.
(one strange thing, I thought the splash boot screen was part of the original rom, but it stays even after flashing the original rom)
would it be possible that software broke the hardware ?
Personally I think your hardware had issues before you flashed this Radio. I am running the same radio and have been for awhile now without issues.
Camera and Viddeo works fine....
I had the same problem - I flashed my Polaris and after it "Unable to initialize camera" I tried use other ROM without good result. I had to flashed to original WWE ROM and sent to servis - of course by warranty ;o) Next week I will have my Polaris after service
bkeaver said:
Personally I think your hardware had issues before you flashed this Radio. I am running the same radio and have been for awhile now without issues.
Camera and Viddeo works fine....
Click to expand...
Click to collapse
mmh... camera has worked flawlessly since the beginning and after many flashes, until I flashed that specific radio rom (once again no physical shock so no reason that it does not work suddenly)
It also seems that I am not the only one having that issue:
http://forum.xda-developers.com/showthread.php?t=351044
http://forum.xda-developers.com/showthread.php?t=349375
but downgrading radio rom did not fix anything like said in threads...
k9nelly said:
I had the same problem - I flashed my Polaris and after it "Unable to initialize camera" I tried use other ROM without good result. I had to flashed to original WWE ROM and sent to servis - of course by warranty ;o) Next week I will have my Polaris after service
Click to expand...
Click to collapse
that is my concern : how possible a soft can break the hardware ? (and apparently not for everybody)
I hope a soft solution exists (I want to avoid sending the phone to service and waiting for a new one, but that seems to be the only issue)
unable to initialize camera - solution
Solution is unbelievably simple. Take out the microSD card. Take out the battery and leave it outside the phone for at least 15 minutes (found this hint in other forum). Then put the battery back into the phone and start the phone without microSD card. Et voila camera is working. Don't ask me how it is possible.
//some comments says that it didn't help them either (don't know if they took out even the microSD card)
UPDATED: After few days the same problem "unable to initialize..." nothing helps (battery, hard reset, anything)
HTC Polaris (Touch Cruise)
ROM Bepe Premium 0.67 WM6.1
Radio Rom: 1.64.08.21
Very odd issue! I can confirm my polaris is working fine (camera ok).
Hobbit_CZ said:
Solution is unbelievably simple. Take out the microSD card. Take out the battery and leave it outside the phone for at least 15 minutes (found this hint in other forum). Then put the battery back into the phone and start the phone without microSD card. Et voila camera is working. Don't ask me how it is possible.
//some comments says that it didn't help them either (don't know if they took out even the microSD card)
HTC Polaris (Touch Cruise)
ROM Bepe Premium 0.67 WM6.1
Radio Rom: 1.64.08.21
Click to expand...
Click to collapse
no luck : did not work for me, even with SD out, even with a hard reset after 15 minutes off with battery and SD out... camera still sluggish and black.
still need to intall the Nadavi fix for Kaiser to make the camera tool reactive and be able to switch to front camera but the rear one is still not available...
Try to find the file "Camera.exe" in windows directory, and run it from there.
If the camera is working, than just create a new link to camera in programs folder.
shayd said:
Try to find the file "Camera.exe" in windows directory, and run it from there.
If the camera is working, than just create a new link to camera in programs folder.
Click to expand...
Click to collapse
yes, the camera application is working, but not possible to capture photo/get frame data from camera device.
Camera working again !
shayd said:
Try to find the file "Camera.exe" in windows directory, and run it from there.
If the camera is working, than just create a new link to camera in programs folder.
Click to expand...
Click to collapse
you know what ? thanks to your idea, I completely deleted all camera.xxx files in /windows, and decided to install the Nadavi_OLD_HTC_Camera_5_0_4_2915_00.cab camera tool (found in the Kaiser section) :
I received a message telling me that it could not properly remove the old camera version, proposed to install whatever, which I did, and then restart.
And tada !! After weeks of flashing differents Roms or radios (which proved to be useless) it is working back again !
This is a completely crazy software bug not at all related to the hardware !
Thanks to all and especially you Shayd for sharing your ideas, that finally helped me !
boldbull said:
you know what ? thanks to your idea, I completely deleted all camera.xxx files in /windows, and decided to install the Nadavi_OLD_HTC_Camera_5_0_4_2915_00.cab camera tool (found in the Kaiser section) :
I received a message telling me that it could not properly remove the old camera version, proposed to install whatever, which I did, and then restart.
And tada !! After weeks of flashing differents Roms or radios (which proved to be useless) it is working back again !
This is a completely crazy software bug not at all related to the hardware !
Thanks to all and especially you Shayd for sharing your ideas, that finally helped me !
Click to expand...
Click to collapse
Glad to see it helped you
Hello All
I have the same issue of camera init.
I have installed the Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab and now I cannot launch the camera.exe.
Any idea to solve it without hard reseting my Polaris?
Thanks in advance!
Gadgio said:
Hello All
I have the same issue of camera init.
I have installed the Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab and now I cannot launch the camera.exe.
Any idea to solve it without hard reseting my Polaris?
Thanks in advance!
Click to expand...
Click to collapse
try that : http://forum.xda-developers.com/showthread.php?t=391455
boldbull said:
try that : http://forum.xda-developers.com/showthread.php?t=391455
Click to expand...
Click to collapse
Thanks a lot for the tips!
(For info my Cruise was in Repair center last week : I could't hear my caller (maybe a solder issue) so they change the motherboard, reflash the phone and now the camera is working again).
boldbull said:
that is my concern : how possible a soft can break the hardware ? (and apparently not for everybody)
I hope a soft solution exists (I want to avoid sending the phone to service and waiting for a new one, but that seems to be the only issue)
Click to expand...
Click to collapse
I had exactly the same problem with HTC Tytn. Unfortunately I never solved the problem (camera never worked well again: at times yes at times no).
Now I am with a new Polaris and I am scared of flashing anything into it.