Every time I load up the camera app on my sgs i9000 it says camera failed in a dialog box how do I fix this either some one shows me how to fix or I send to Samsung and get my phone in like 4 long boring week's
Sent from my GT-I9000 using XDA App
This happened to one of our first phones. Had to have it replaced. Fortunately it happened the day after we bought it sonwe got an in store replacement.
Did you flash any custom roms or kernels, edit system files, or install camera mods?
I think it wouldn't hurt to try and flash a stock rom to see if that helps.
i have the same problem camera dont work :/ i can record video but i cant shot any photo any suggestions ? i have rooted the phone via odin and installed fix for download mode + installer rom manager after i have tried to hard reset but still same :/ im thinking to update it to darkys 8.1 ROM but i dont know if it would help and i would loose warranty then pls help
try it darkys 8.1 is great and fast to i did the same as you odin to root it and it put busybox on too then went for darkys 8.1 rom and in that you get sgs tools theres a camera hack which lets you take photos with the power button (much easyer) and the camera works with hardly any battery power left, but when i went to do cam hack it said no busy box installed so went to market to get it but it caused my phone to re-boot all the time so stuck it in recovery mode on cwm and saw su +busybox install done that now hack works great fast at loading cam up too and if it ALL goes pair shape flash it back with odin to stock then off to the shop with for replacement
i flashed my phone via kies patcher again to froyo and now the camera works. no root yet just clean froyo .
Dear all,
Hope this is the right location and if not please move... thanks!
A brief history on my problem: I had a Canadian Bell ( SGS Vibrant ) I9000M and recently rooted and unlocked for an oversea trip. It was on the stock Gingerbread from Bell and everything works fine and after I'm back in the middle of the day the phone starts rebooting to the 'S' animation ( bootloop? ). Then, I tried to reflash it with other stock roms but no luck.
Then, during one flash my USB port failed on me and bricked. I decided to flash with primary and secondary bootloader and the phone no longer to display anything after power on.
After following AdamOutler's thread on the hardware unbrickable mod now can go back to Download Mode. I was so glad to see things back so I immediately flash it with Heimdall one-click ( with XXJVT rom ). However, everything went smooth, except when everything ( incl primary and secondary bootloaders ) are loaded it still doesn't turn on. I tried many times with same result.
Anyone can shed some light on this? Thanks!!!!!
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Do you try a hard reset, you probably can do it from recovery mode, but not sure.
Maybe he solve your issue ?
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
WEissbr0t said:
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
Click to expand...
Click to collapse
Dude, did you get your camera back?? I made he same mistake just a couple of hours ago.. I am feeling so depressed, I dont know what to do.
Did they say anything about the flash counter?
me too
I have had this problem as well. My camera has no touch on the screen after rebooting. I saw it flick and lock and then I tried to re-flash the rom etc, but it didn't help.
Sent to Samsung and they are saying that the motherboard and screen have to be replaced at a cost of $350. They are seeing if they can repair under warranty, but it doesn't sound too hopeful.... Perhaps, I will give up on my Galaxy Camera. I am not going to pay $350 to have the item repaired. I didn't know if it was a software fault or a hardware failure. I think it really should be a warranty issue....
Anyhow, I guess clockwork mod can really wreck things up..... Anyone, found a way to fix this issue? Why didn't the default Samsung ROM flash and factory reset fix the issue if it is supposedly software?
WEissbr0t said:
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Click to expand...
Click to collapse
I had the same problem dude, got the touchscreen replaced at the service center.
New touchscreen works totally fine.
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Flash stock rom
7dervish said:
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Click to expand...
Click to collapse
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
ant75 said:
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
Click to expand...
Click to collapse
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
7dervish said:
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
Click to expand...
Click to collapse
There is no solution for touchscreen problem. You just give service your camera and they change touchsreen. Cause it's a hardware problem
Jeah it definitively was an HW Problem. Got a New Touchscreen and all works fine
Gesendet von meinem GT-I9100 mit Tapatalk 2
A pity, read the solution, because I'm at the same point
Am using cm10 beta7 but am getting bootloop after turning on bluetooth..the problem is
1)i turn on bluetooth
2)phone goes into reboot loop but doesn't boot up
3)i pull out battery and put it back and turn on phone
4)phone boots with bluetooth on and bluetooth works fine
please note that i did a clean odin flash of official gb and then installed it with all cache data dalvik cache wipes... bluetooth works well with stock gb..so hardware no fault..
please anyone help!! i've also seen other ppl complaining about this problem..even in cm9..ANY FIX??
pradeepjoshua said:
Am using cm10 beta7 but am getting bootloop after turning on bluetooth..the problem is
1)i turn on bluetooth
2)phone goes into reboot loop but doesn't boot up
3)i pull out battery and put it back and turn on phone
4)phone boots with bluetooth on and bluetooth works fine
please note that i did a clean odin flash of official gb and then installed it with all cache data dalvik cache wipes... bluetooth works well with stock gb..so hardware no fault..
please anyone help!! i've also seen other ppl complaining about this problem..even in cm9..ANY FIX??
Click to expand...
Click to collapse
Hello, I have the same problem, and now in its variant :
- the sgs reboots when activating bluetooth, with bluetooth off
- it looks like no way to activate bluetooth without provoking smartphone reboot
Does cm update fix this problem ?
Other suggestion ?
Thanks for reading
z2x said:
Hello, I have the same problem, and now in its variant :
- the sgs reboots when activating bluetooth, with bluetooth off
- it looks like no way to activate bluetooth without provoking smartphone reboot
Does cm update fix this problem ?
Other suggestion ?
Thanks for reading
Click to expand...
Click to collapse
You should ask this problem in the development forum of your CM version and/or kernel version. They may be able to help you more e.g. by asking for specific logcat data from the time of your reboot.
Other than that, I'd say there is something fishy with your kernel. Did you try to use stock kernels? Or the latest CM10 of Ivendor? People are having less and less problems with that.
Hi,
I am fairly advanced in this stuff and generally i know what im doing, i used to have a HTC Desire HD and was always changing roms etc.
I have had a Galaxy S I9000 for a month or two now and recently i flashed Vanilla Rootbox ( http://forum.xda-developers.com/showthread.php?t=2122727 ) just like any other rom using CWM recovery as i always have done.
After finding i want to change roms, i am unable to boot into recovery mode, download mode and even bootloader.
I have tried using the key combinations to access all of these modes, ive tried using adb to access all three and whatever i try and do it just boots up normally to vanilla rootbox as if i had just booted up normally.
Just incase it means anything, when i try and boot into these modes, the Samsung Galaxy S I9000 Screen (the boot screen before the Vanilla Rootbox one) shows up for about 4-8 seconds and then disappears for not even a second (the screen just goes black almost like it tries to load the mode but then redirects itself to a normal bootup) and then shows the same screen again for a further few seconds, before going to the Vanilla Rootbox boot screen, from there it just loads up normally.
I have searched all over the internet for a solution and there isnt even any posts with the exact same problem.
I really would appriciate any help with this as i am stuck with this rom which in my opinion is awful and drains the battery on my device.
Thanks, Jake:fingers-crossed:
have a read here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
slow--welder59 said:
have a read here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Click to expand...
Click to collapse
nope, still no luck
i think it has something to do with the rom as i have had no trouble with other roms, do you know if there is a way to flash a rom without using bootloader, download mode or recovery?
thank you very much for the response by the way
Mate you tried a USB jig?
Sorry for late reply, bought a Jig in the end as they were down from £10 to £1.60 on amazon! worked like a charm, straight into download mode, back to stock rooted and now back up and running rooted with cyanogen 10.1 nightly, very nice!
Close Thread, - JIG IS THE ANSWER.