[Q] HELP me for camera - Touch Diamond2, Pure ROM Development

help me for this message : "unable to initilize camera failed to set up the camera device"
my camera dont work,why?help

1. What ROM are u using, or stock?
2. Did u soft-reset (and if it doesn't help hard-reset) your device?

thanx,i use mozart rom v6.5.5.0.3,and then this error ,i use official rom htc.com for diamond2 but bug dont fix, i do several reset but....;help

this error for several htc mobile:
After I flashing my Tmous HD2 to Hspl3 and Radio Rom 2.14.50.04 and OzRom, my camera not work.
When I start the camera this error will be shown.
"unable to initialize camera. failed to set up the camera device."
I Flash it back to original tmous Rom and Spl but the camera didn't work.
First time I flash the wrong Rom, so the mobile phone was dead, a friend repair it with Jtag.
But what's the problem with the camera?
Hello,
I am now an owner of HTC HD2 device, and so far I kinda like it. Except that I had a message saying "can not initialize camera. fail to set up camera device" when opening the camera application and the camera did not work. I then flashed one of the latest official roms and had the same message appear. Flashed it once again and so far it works ok, but I am not sure if problem is fixed because the issue appears occasionally.
Please, could anyone explain if the hardware (camera) is showing symptomes of an imminent failure, or some software issue.
I will be extremely grateful, because it really bothers me a lot.
When I go to use camera it states failing to initialize camera failed to set the camera device ans closes the app. Recently loaded wm6 with dcd rom. tried installing Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX and now cant uninstall that file. any suggestions

well if that error comes up even on official roms i have no other solution for you.
sometimes it's a problem with a new rom but in your case i have no clue...sorry

Related

Himalaya upgarde failed to win200 se please help to downgrad

Dear friends
I was tring to upgrade my iMate Pocket PC also know as Himalaya with windows2003 SE , while upgrading I faced problems, the upgarde failed and now I am just getting no display and OS too. The only message displayed is
Serial
v1.03
nothing is working please help
bye with regrads,
your unit is still okay; even better that the usb version is showing on the screen. it's simply stuck on bootloader mode. what kind of problems did you encounter resulting in the failed upgrade?
one suggestion i can give before you downgrade is to try and proceed with the upgrade to se. put your unit back on the cradle but don't expect activesync to "recognize" the device. just put it back on the cradle and rerun the upgrade to se.
same thing happened when i upgraded but to wm2005. the screen showed error and the only thing on the screen was the usb version. i simply cradled back the unit and ran the upgrade. worked.
cheers
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
oh, it appears that you have the "wrong country" id issue. i'm not entirely sure as to how to avoid this but i believe it has something to do with the correct rom version (guys, correct me if i'm wrong). where did you get the rom you used for upgrading to se? downgrading might be the only trick if there is no rom for saudi-based users...but if any chaps presently living there and were successful in upgrading their units perhaps you could share the rom version/s you used?
cheers
yasirirfan said:
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
Click to expand...
Click to collapse
To overcome the Country ID Error, first you need to install this tool...
ftp://xda:[email protected]/Tools/ER2003Edit_1_4_26.zip
Open the ROM file you want to upgrade, then change the appropriate 'Operator ID' code, after this click 'Save ROM image'.
Upgrade ur device. You will no longer face the error message.

My GPS isn't working after upgrade to wm6..HELP

Hi,
I've an AMEO, i tried recently to upgrade to WM6 here is what i've done so far
1. Unlock / SuperCID by the tool provided in the forum (Successfull)
2. Tried to use the SuperCID only Rom in the forum (here the trouble started)
With everytime i try to upgrade the update process stops at random points, i extracted the rom to check where does it stops and i found that it stops when i tried to flash the GPS.. i did succesfully flashed the whole rom twice but neither the Wifi or the GPS worked, and now i'm running it with the official release wm6 (27/7) but without the GPS.
3. Extracted the GPS and tried to Flash it through SD .. same thing.
any ideas guys?
i've been trying this for 2 weeks now .. what is the hell is wrong with this phone ..
NOTE: it works perfectly with the WM5 ROM
Try a different ROM Image...
run a tool called GPSviewer to check whether it can communicate properly with the GPS module.
Doesn't work
It defenitly not the rom as i used it on the other AMEO i've and it works perfectly, i usually use the SD update, and it shows where is the error and it is at the GPS update .. i get the error 00018003 in red color on the top of the screen and the GPS- ( FAIL ) during the update. i've tried all the rom in the forums and it does the same. I've tried to downgrade again to WM5 and it is the same issue the GPS isn't working anymore.. is there a solution .. it seems it can't write at that address i think 00018003 or something like bad blocks in the NAND! is there any fix for that?!
Experts .. i needd youuuuu
Try the SuperCID2 unlocker, then try reflashing.
Never heared about SuperCID2 !!! What is that, if there is something like that where i can find it?! i did search the forum didn't find anything
Thanks for helping

Prophet G3 without camera

Hi, I’m from a group of peoples whom works in an environment which camera is prohibited. I had tested my Prophet flashing from WM5 to WM6.0, WM6.1 Prophet Shadow 2.0 TE Rom is running smooth and very stable in my Prophet.
Thank-you very much Cloudyfa for your wonderful Rom
As to use my Prophet G3 in my working environment, I had dismantled the camera and test booting up my ppc. During boot up, it hanged at this htc display, done a hard reset and re-boot, it still hanged at this display and it sight like the booting program is searching for something.
Decided to flash back to WM5 NVID and Goodd…. It boot up to WM5 and try clicking on the camera icon, it’s not functioning. Tested it’ functions and connect to GPS every thing works smooth and steady, but not as fast as WM6 Rom and no launcher etc…..
Re-flashed to WM6.0 and WM6.1 Rom, always hanged when boot up in one way or the others . Flashed back to Prophet Shadow 2.0 TE Rom and reboot, it still stuck at the htc isplay page. If look at the booting up window carefully, it show IPL 2.20, SPL 2.20.0000, GSM 02.19.21 & OS 5.2.20.21
To my understanding of the flashing process, the Prophet Shadow 2.0 TE Rom had already flashed in my prophet and rebooted my itself, but hanged at htc display because the process is looking for the camera hardware which I had dismantle out and that why is go round & round until it hanged.
Please correct me, if I’m wrong. Thank-you.
For troubleshooting, can any body provide me a tool (program) and guide me into the nk.nbf file to remove the camera execution file from loading? And with this tool, I can also use it to flash future Rom and enjoy flashing new roms.
Maybe new threads will be form for those who like to have Prophet without camera.
Rewards, I will buy you beer, ha…ha…ha…
Prophet G3 w/o camera
IPL : 2.20
SPL : 2.20.0000
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Prophet G4 c/w camera
IPL : 2.15
SPL : 2.20.0001
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
glim59 said:
Hi, I’m from a group of peoples whom works in an environment which camera is prohibited. I had tested my Prophet flashing from WM5 to WM6.0, WM6.1 Prophet Shadow 2.0 TE Rom is running smooth and very stable in my Prophet.
Thank-you very much Cloudyfa for your wonderful Rom
As to use my Prophet G3 in my working environment, I had dismantled the camera and test booting up my ppc. During boot up, it hanged at this htc display, done a hard reset and re-boot, it still hanged at this display and it sight like the booting program is searching for something.
Decided to flash back to WM5 NVID and Goodd…. It boot up to WM5 and try clicking on the camera icon, it’s not functioning. Tested it’ functions and connect to GPS every thing works smooth and steady, but not as fast as WM6 Rom and no launcher etc…..
Re-flashed to WM6.0 and WM6.1 Rom, always hanged when boot up in one way or the others . Flashed back to Prophet Shadow 2.0 TE Rom and reboot, it still stuck at the htc isplay page. If look at the booting up window carefully, it show IPL 2.20, SPL 2.20.0000, GSM 02.19.21 & OS 5.2.20.21
To my understanding of the flashing process, the Prophet Shadow 2.0 TE Rom had already flashed in my prophet and rebooted my itself, but hanged at htc display because the process is looking for the camera hardware which I had dismantle out and that why is go round & round until it hanged.
Please correct me, if I’m wrong. Thank-you.
For troubleshooting, can any body provide me a tool (program) and guide me into the nk.nbf file to remove the camera execution file from loading? And with this tool, I can also use it to flash future Rom and enjoy flashing new roms.
Maybe new threads will be form for those who like to have Prophet without camera.
Rewards, I will buy you beer, ha…ha…ha…
Prophet G3 w/o camera
IPL : 2.20
SPL : 2.20.0000
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Prophet G4 c/w camera
IPL : 2.15
SPL : 2.20.0001
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Click to expand...
Click to collapse
Hey...... did you ever try the simple step.....
remove the sim card?
just brain storming......
Yes, try every methods that i had learn from this thread, from 31/06/08 until now, out of solutions then ask of help
Regards
glim59 said:
Yes, try every methods that i had learn from this thread, from 31/06/08 until now, out of solutions then ask of help
Regards
Click to expand...
Click to collapse
if your prophet still can flash........
did you try intertek's micro V3 rom?
he had removed the default camera (except the camera.dll)
give it a try....... ^^
I removed the camera recently too (G4). Didn't boot either. This has nothing to do with the software, it seems like its in the mobile's firmware (bios).
Instead of removing the camera module, remove the lens! Dead simple. on the sides of the camera lens module there are 4 small metal leaves to prise up. The lens module comes out together with the spring that is underneath it. All you are left with is a cmos. You could possibly put the lens back in later, with a fiddle.... Its now totally useless to take photos with and the security people at your company can see that the camera has no lens when they look through the camera hole at the back of the mobile, which means you'll be OK if they stop you and look at the mobile. So you can't get sacked or carted of the premises.
I work at most of the major car companies in germany, so I have the same problem
Hi, Jellyme
did you try flashing with new rom? did it boot up?
I will download and flashing intertek's micro V3 rom tonight after work
thkx
No, I didn't try a new rom.
I don't think a new rom will work, as my Prophet hung at the HTC Logo, before the OS even started booting. My guess its a Boot ROM thing: It checks for a reponse from the camera chip.
However, I hope you have luck with a new ROM! However, I wouldn't want to be stuck on a particular ROM.... some of them here are just a little too buggy to live with.
jellyme said:
No, I didn't try a new rom.
I don't think a new rom will work, as my Prophet hung at the HTC Logo, before the OS even started booting. My guess its a Boot ROM thing: It checks for a reponse from the camera chip.
However, I hope you have luck with a new ROM! However, I wouldn't want to be stuck on a particular ROM.... some of them here are just a little too buggy to live with.
Click to expand...
Click to collapse
Go for Korand's 3.2 ( wm6.1) stable fast and bug free, its a clean rom with basic features.. ^^
edit: Should be Korand 3.1 ...
> Go for Korand's 3.2 ( wm6.1) stable fast and bug free,
> its a clean rom with basic features..
There are no bug free 6.1 for me. However, most are pretty damn close! It always depends on which functions you need. For some, the 6.1 are bug free, for my particular usage (business) they are good enough, but not bug free. I'm happy with the 6.1 that I use, with the camera lens removed...
The BIOS needs to be told to ignore the camera at startup. Anyone with an idea how to do this?
jellyme said:
> Go for Korand's 3.2 ( wm6.1) stable fast and bug free,
> its a clean rom with basic features..
There are no bug free 6.1 for me. However, most are pretty damn close! It always depends on which functions you need. For some, the 6.1 are bug free, for my particular usage (business) they are good enough, but not bug free. I'm happy with the 6.1 that I use, with the camera lens removed...
The BIOS needs to be told to ignore the camera at startup. Anyone with an idea how to do this?
Click to expand...
Click to collapse
Umm... Does the ROM not boot up at all without a camera (do different - WM5 - ROMs do the same)?
I had tried a few of WM6.0 &WM6.1 without camera, ever intertek's micro V3 rom which removed the default camera (except the camera.dll) advised by dioxda2, It hanged for half a hour at the Front booting display showing IPL..SPL... and showing the ROM version.
As for WM5.0 NVID rom w/o camera no problem flashing and when activate the camera, display flipped and remain normal without having the camera display page.
Thank-you Jellyme for your method, just flashed with camera w/o len last night, but need to flashed 3 times before it able to boot up to Shadow 2.0 TE and it slight unstable when activation of some programs. I will monitor it for a few days.
As for me, re-moving the len from the camera is still no good enough, cause work involve with Military Security. I'm putting my two arms and limbs high up the air , ha..... ha..... ha.....
At the same time, I had also e-mail to HTC service centre to check whether they have any device or dummy camera connector to plunge back on the main board. No reply yet.
Regards
Would completely removing the camera drivers work? Or maybe put some tape over the lens
completely removing the camera, it will boot up to HTC display and then hanged for shadow 2.0T. For the other, stuck Front booting display showing IPL..SPL... and showing the ROM version.
Not adviseable to put some tape over the lens, Security check do not want to see camera in the camera window, ever len is out and still have to place a piece of thick Black paper on the camera receiver to complete cover the shadow of the camera image, in which the camera is still active.
Military security would not clear this conditions of the Prophet or camera phones.
It may be possible to cook a ROM with no camera drivers at all... That way, it wouldn't work at all...
> It may be possible to cook a ROM with no camera drivers at all...
> That way, it wouldn't work at all...
Thats what we want. Actually I think the Camera drivers have only to be removed from the registry... in case references to them are found there. Then the camera drivers should be removed.. or a dummy camera driver written that just has the required interfaces and returns OK at every call, if removing the camera drivers doesn't work.
Maybe getting the driver from a WM phone without a camera or from WM 5.0?
jellyme said:
> It may be possible to cook a ROM with no camera drivers at all...
> That way, it wouldn't work at all...
Thats what we want. Actually I think the Camera drivers have only to be removed from the registry... in case references to them are found there. Then the camera drivers should be removed.. or a dummy camera driver written that just has the required interfaces and returns OK at every call, if removing the camera drivers doesn't work.
Maybe getting the driver from a WM phone without a camera or from WM 5.0?
Click to expand...
Click to collapse
I think devices without the camera won't have the drivers at all... I can re cook a WM5 ROM now with no camera drivers/no camera exes etc...
Hi, my guys over here are buying new camera phone like iphone, Samsung i780, Nokia E51i........etc to dismantle the camera or cameras.
Their phone still work without camera.
FYI only
regards
glim59 said:
Hi, my guys over here are buying new camera phone like iphone, Samsung i780, Nokia E51i........etc to dismantle the camera or cameras.
Their phone still work without camera.
FYI only
regards
Click to expand...
Click to collapse
It might just be WM, or even just the Prophet...
It might just be WM, or even just the Prophet...
Click to expand...
Click to collapse
Samsung i780 is using WM 6.0 rom............ FYI
glim59 said:
Samsung i780 is using WM 6.0 rom............ FYI
Click to expand...
Click to collapse
Then it's our Prophets

Camera wouldn't work after Rom Update HD2 unable to initialize camera

After I flashing my Tmous HD2 to Hspl3 and Radio Rom 2.14.50.04 and OzRom, my camera not work.
When I start the camera this error will be shown.
"unable to initialize camera. failed to set up the camera device."
I Flash it back to original tmous Rom and Spl but the camera didn't work.
First time I flash the wrong Rom, so the mobile phone was dead, a friend repair it with Jtag.
But what's the problem with the camera?
****sorry for my bad english***

Camera don't start after Rom Update.

After I flashing my Tmous HD2 to Hspl3 and Radio Rom 2.14.50.04 and OzRom, my camera not work.
When I start the camera, this error will be shown:
"unable to initialize camera. Failed to set up the camera device."
I Flash it back to original tmous Rom and Spl but the camera don't work.
First time I flash the wrong Rom, so the mobile phone was dead, a friend repair it with Jtag. Could he or make he a mistake?
****sorry for my bad english***

Categories

Resources