I just purchased a second hand as new G3 online. This thing is in mint condition, no scratches or anything. Upon getting it kitkat was installed, i tested everything and the camera worked (front and rear), i took a couple of pics.
I promptly rooted and bumped twrp, made a backup of current install and then proceeded to install chuppachups rom, installed a couple other small tweaks (throttling, and conservative governor). Everything went well until later that day when i went to use the camera, and got just a black screen. Tried facebook messenger and could use front camera not rear. Reset phone, no help. Wiped cache, davlik, internal data - no help. Relfashed chuppachups after wiping everything - no help. At this point i realized i hadn't tested the camera at all after installing chuppachups so restored from the twrp kitkat backup and no camera still... ummmm. Ive tried the xcam apk and that doesn't work either.
Can anyone help resurrect the camera?
Anyone? im at a loss because this was going when i got it. and now i have restored from that backup after a wipe and its not going im confused as to what it could be?
Just performed a lg flashtool reset (cse) using kdz file. this also hasn't helped. . dont know what to do at this stage
Have decided it must be a hardware issue. Opened phone and checked camera connection to motherboard - ok. So have ordered a new camera, they are ridiculously cheap! ($8usd)
Related
Hey,
I know there are a few threads on this but I haven't found one that followed through to a reported solution.
G2 rooted with CyanogenMod 6.1.1 since January of this year. Tried google goggles and the app locked up. I finally realized that was because the camera has stopped responding. When I pressed on the camera help, nothing changes for a few seconds, then it goes to a black screen. Eventually, (pressing on the back key helps) I'll get a force close/wait screen. Camera had been working fine the previous day.
I've tried clearing caches, using a different SD card with no changes. Used the opportunity to finally upgrade to CyanogenMod 7.0.3 and cleared all the caches as part of the flash. Tried the camera the first chance I could get the phone to that point. Same response from the camera (hesitate, black screen, force close).
So, is there anything else to try or is this a hardware camera failure?
Thanks for any help.
Try flashing some other rom. If that fails, then try flashing another radio.
I'd suggest taking a rooted stock rom and a stock radio just to be sure.
Thanks, but I'm trying to understand what any of that would do to fix the camera over what I've already tried.
I guess I'm looking for anyone that actually had a similar problem and either fixed it or failed to fix it.
Thanks.
Well for once the stock rom uses HTCcamera.apk to open the cam. Since you are using CM7 its a completely different apk.
Radio is somethign that is responsible for almost every device on your phone. Then the drivers that are in the Kernel, and then the ROM which has the apk, that uses the driver from the kernel to start the camera that is defined in the radio.
Well, nothing worked. Unrooted and back to stock (camera still doesn't work). Replacement phone is on it's way.
This one has been giving me a headache all day.
Just got a GS3 from Sprint, obviously the first thing I did was throw on a custom recovery and flash Cyanogen. For some reason, no matter what version of Cyanogen I flash, no application can use my back camera. I have wiped all caches, fixed permissions, cleared the gallery cache (as some suggested) with no avail.
Here are the weird things: The front camera works. I can use it in any application, but the back camera always hangs or ends with a "Can't connect to the camera" error. In addition, if I factory default the phone, the camera works fine - so it isn't a hardware issue.
Would love some suggestions on how to proceed!
I really appreciate it!
As a follow up, I tried flashing my cam firmware with the ones found in this post http://forum.xda-developers.com/showthread.php?t=2006128 out of desperation. It resulted in my camera no longer working - even on the default rom unrooted.
:crying:
Hi, the rear camera and flash seem to not be working a few days after installing Viper on my M9. Camera worked for about 1-2 days after flashing latest Viper ROM, but then stopped altogether. Anything trying to utilize the flash also doesn't work (HTC and Google flashlight). I've tried wiping the camera's data & cache, and I flashed the upgraded camera software that is available on Venom Hub, still no luck. Launching the camera app shows a black screen for a few seconds, then crashes back to home screen with no error message. Front camera works fine. Service provider is Sprint. Recovery is TWRP. I know that I could likely get a functioning camera back by re-flashing the Viper ROM or another ROM, but that's time consuming, and I'd prefer to only do that as a last resort. Any help greatly appreciated!
There is no fast way. Reflash the rom over the top, it shouldn't erase anything as you are recovering, not upgrading. Otherwise you're looking at going back to stock to test.
Sent from my HTC One M9 using Tapatalk
IncredibleHulk6 said:
Hi, the rear camera and flash seem to not be working a few days after installing Viper on my M9. Camera worked for about 1-2 days after flashing latest Viper ROM, but then stopped altogether. Anything trying to utilize the flash also doesn't work (HTC and Google flashlight). I've tried wiping the camera's data & cache, and I flashed the upgraded camera software that is available on Venom Hub, still no luck. Launching the camera app shows a black screen for a few seconds, then crashes back to home screen with no error message. Front camera works fine. Service provider is Sprint. Recovery is TWRP. I know that I could likely get a functioning camera back by re-flashing the Viper ROM or another ROM, but that's time consuming, and I'd prefer to only do that as a last resort. Any help greatly appreciated!
Click to expand...
Click to collapse
this happened to me without any software change (that I know of) just a hardware change. I even bought and installed a new rear camera which now allows the use of the front camera but the rear is not detected in the app and the flashlight just loops forever with a "loading" message. I am also SPRINT
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Hello dear XDA Members,
on my OP 5T I was using the latest official Firmware 10.0.1 when suddenly the main camera froze and since then would not open again. I have tried all recommended things like restart, clearing the camera cache or the whole cache partition and so on. I performed a factory reset, downgrade to last OOS 9 version and installed latest LineageOS. Nothing worked. I also ordered a replacement camera module, but this did not work either. So it appears as if this is a hardware issue with the main board. However, I wanted to hear if anybody experienced something similar or even has a way to possibly fix this without the need for a replacement mainboard. for example through some magic commands
The other camera modules (aux back and front) work fine by the way.
Thanks in advance, have a nice day!