Develop Bugs

[Q] Camera Failed

why my camera sometimes can't be used and there is a notification "Camera Failed".?
please help me...

I had this issue too..just reboot your phone and everything will works normaly again..

i hv this issue alsi when i'm using lower class memory card. now using class 10 16gb card with bionic rom without this camera failed problem.
Sent from my GT-I8150 using XDA

rinopermana said:
I had this issue too..just reboot your phone and everything will works normaly again..
Click to expand...
Click to collapse
i have reboot my phone, but that problem happen again for a next time.
please help me...

shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.

yewsiong said:
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.
Click to expand...
Click to collapse
how to flash a new Camera.apk ?
I really don't know.

I had the same problem and I solved it by uninstalling oovoo....it's only a case???

shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
do u have cwm on ur phone? reboot ur phone into recovery then choose advance and choose fix permission, wait until finish, then reboot ur phone after it finish

Unfortunately I have the same problem. My camera does not work anymore. I just receive the message "Camera failed". I still have the stock rom installed and I did not modify too much (I just installed some apps). I have already reset the phone to factory settings which did not solve my problem. Does anybody have an idea what I could try to fix the problem?

Please help...
I just have formatted my device and flashed it with a stock rom. Unfortunately it did not solve my problem with the camera. I still got the error message "camera failed" when I click on the camera app. Any ideas? Is it a hardware problem? Should I flash a custom rom?

I got that message once, and I panicked. Fortunately, rebooting did it just fine.
Perhaps there is something wrong with the firmware...I searched the net and found this article, maybe useful, IDK.

Thanks for the reply and for the link. Unfortunately I do not understand step 3. When I scroll to "Camera" I do not see a 2nd option which should be named as "user". I just see "camera" and "camcorder". What should I do? Do I have to root the phone?

ok, I have rooted my phone and I have tried the fix described in the link above again. However, I was not successfull. I do not get these options described in the link ("user"). Maybe I am using a wrong version of Pro Launcher. I just downloaded the new version from market...Anyone with a suggestion/idea?

Camera failed
I used to face this problem quite a lot when i was using the stock rom, but after flashing to cow's rom, the problem went away, no more camera failed anymore

Yesterday after upgrade to baseband v. i8150dxlc1 Kernel [email protected]#3 (KIES UPGRADE) i dont have that problem anymore

Wiping to start fresh. camera issue.

I need some help figuring out how to get my camera working. I bought a droid incredible that was reconditioned and planned to root and customize it for my sister, so I followed the tutorial that seemed best to accomplish this. since getting root and s-off and trying several roms all the way from GB roms to tinys cm10 I've had no luck getting the camera to work. most camera apps I've tried just leave a black screen until for closing, the JB+ camera is the only one that will appear to be working but the screen is still black, it does not actually take a picture and when I try to back out then I get the force close. I'm wondering if along the way to getting root and s-off something got messed up. I've tried installing older roms with the same result, tried installing tinys rom with no gapps and different gapps even.
I'm wondering if anyone has a sure way to test what's wrong or if anyone could just point me in the direction of a good tutorial to wipe everything and start over. I've only had a week with this phone so not a lot of time to learn about it but any help would be appreciated.
Sent from my XT875 using xda premium

Your camera is probably hosed. Did the camera ever work prior to rooting? There's nothing in the rooting process that would break the camera.
You've already stated that GB and JB have the same issue.
What you can do to help point out the cause though it may do no good is grab a logcat.
Download a logcat app like catlog and open it after getting the force close and wait for it to start displaying code and stuff on the screen. Then go to menu and save the log. This will create a log in the sdcard under a folder called catlog inside a folder called saved_logs. Can you post it up here when done? I fear it will only confirm my suspicions of a bad camera.

I will do that later today and post the log. unfortunately my inexperience and eagerness got the best of me here, I got the phone charged up after taking it out of the box and tested everything I could think of besides the camera before hacking into it. this is a last resort before trying to exchange it.
Sent from my XT875 using xda premium

I copied the text to these links, I hope this is alright.
This one is from when I opened the jb camera.
http://pastebin.com/aDEHH4V1
This one is from the stock camera
http://pastebin.com/jxRNiqfw
Sent from my ADR6300 using xda app-developers app

Stock as in stock one with the ROM and then other was JB Camera+ - which has a known graphic glitch on this device but not related to your issue.
Here's the problem:
Code:
01-02 19:01:19.352 I/QualcommCameraHardware(113): Open Device node : /dev/msm_camera/control0
01-02 19:01:19.352 E/QualcommCameraHardware(113): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
01-02 19:01:19.352 E/QualcommCameraHardware(113): createInstance: startCamera failed!
01-02 19:01:19.352 D/QualcommCameraHardware(113): ~QualcommCameraHardware E
This is for both camera apps?
You are using the included kernel and didn't change anything weird did you?
Also, can you get the output of the following in terminal?
ls /dev/msm_camera/*
Can you RUU back to stock and test? The fact that it reports that it cannot open the camera device doesn't bode well.

Yes each link was for one of the cameras the jb camera and the stock camera as titled. I was not aware of the jb camera issue but I included it because it had a different result from the stock camera or any other I've tried. If there is another to try I'll gladly try.
I didn't change anything with the kernel or anything besides installing busybox.
This is the result from the terminal line:
[email protected]:/ $ /dev/msm_camera/*
/system/bin/sh: /dev/msm_camera/*: not found
127|[email protected]:/ $
I can look up a tutorial to RUU back and test if that's the next thing you suggest.
Sent from my ADR6300 using xda app-developers app

You missed ls. It should be
Code:
ls /dev/msm_camera/*
However, it may not be worth wasting your time. If you have a file explorer you can check the same by checking for an msm_camera folder in /dev. If the msm_camera folder exists, check there for a control0 file. However, even then I'm probably wasting your time checking this so just RUU.
Here's a good site with various incredible resources:
http://pvillecomp.com/

Yeah there is no /msm_camera/ under dev.
Sent from my ADR6300 using xda app-developers app

ok, I went back to stock 2.3.4 and the camera works! I'm very relieved it's not the hardware. now to find an updated tutorial to root this thing and try again. I'll post the results here once I'm all done and I'll try to pin point what I may have done the first time that was different so hopefully there can be a lesson learned here, at least by me.
Sent from my XT875 using xda premium

homeskool said:
ok, I went back to stock 2.3.4 and the camera works! I'm very relieved it's not the hardware. now to find an updated tutorial to root this thing and try again. I'll post the results here once I'm all done and I'll try to pin point what I may have done the first time that was different so hopefully there can be a lesson learned here, at least by me.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Yeah. I'm glad it's not hardware. I have doubts on it being your rooting process. I believe it could be how you flashed your ROM like if you flashed ROM and mods or kernels or just the ROM and if you forgot to wipe when updating to CM10. You said you didn't install any kernels so I'm wondering how it wouldn't report that /msm_camera location unless you have the wrong kernel or somehow the wrong ROM for your Incredible.

I got time to work on this last night and I finally got it working.
first thing I did was wipe everything I could with the factory reset, clear storage and PM31IMG the stock Rom. I still had s-off and unlocked so I followed this tutorial: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html
I didn't have to unlock or downgrade to get s-off so I basically used this to get the right drivers and files to upgrade the hboot then root. I double checked the md5 sum on all the files after downloading them again and every time I got the phone on I checked the camera to make sure it worked after each step. once I got CWM recovery installed and got root, I made a backup then installed tinys cm10 and gapps and now all is good.
the only thing I can imagine going wrong from the first time following the tutorial is that I wasn't as careful checking the files after downloading and I didn't double check the version of software after each step to make sure it took. during the process this time while double checking the software version after flashing the rom, I noticed it didn't take so I had to repeat that step.
this made me realize how important it is to check everything as you go. many thanks for all the help!
oh yeah! the other that was different this time is that I had an sd card installed and formatted to fat32. the first time I didn't have one until after everything was done. I noticed before I started last night that the external storage would not mount. once I wiped everything then I was able to mount the sd card. I'm not sure if that would have anything to do with my problem but I have noticed other threads where people had problems mounting sd cards. anyways, thanks!
Sent from my XT875 using xda premium

[Q] HUGE problem after Kies/JB 4.1 Update!

I will try to make this short and sweet...
"backed up" phone prior to letting Kies update my phone.
apparently everything but my photos/videos was backed up. (stupid me for not double checking that AND the version it was updating to)
updated phone. phone is pretty much useless now. (EVERY SINGLE APP freezes and crashes eventually)
wont connect VIA USB... knows it is connected and so does the computer. computer now refuses to install (it tries) anything involving MTP. all other drivers are installed. Kies can see the device.. tell me how many photos... but by the time I try to transfer anything Kies or the USB app on the phone freezes and crashes.
ive tried everything under the sun that is basic. uninstall drivers.. uninstall kies... reinstall things.. reboot. safe mode... USB debugging.. etc. NOTHING will get my computer to pull the files or the phone to stop crashing the programs.
I NEED to get these photographs from the phone.. there are at least 2k of them.
what are some options I have or things I could try?
and DO NOT say factory reset.. thats not an option until I get desperate.. do that and try some recovery software for photos.
thanks for any help. I have about a week or so to figure this out... so I can return this stupid galaxy express I had to buy just to have a functional phone.

Have you tried using a micro SD card and transfer your photos internally via a file manager app.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Domoo said:
Have you tried using a micro SD card and transfer your photos internally via a file manager app.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
do you have a suggested app? and is this possible without going into the gallery cause that I cant even open... just freezes and fails

Why dont u just make a nandroid backup and wipe. Then flash the latest stock rom through odin. If that fixes the issue of freezing apps and your mtp problem you can restore the backup and should be straight.
Sent from my SPH-L900 using xda premium
Edit: also are you familiar with adb? You could boot to recovery and pull the photos with adb from there. And how much space is free on internal storage? The issues your experiencing sounds typical of full internal storage

billard412 said:
Why dont u just make a nandroid backup and wipe. Then flash the latest stock rom through odin. If that fixes the issue of freezing apps and your mtp problem you can restore the backup and should be straight.
Sent from my SPH-L900 using xda premium
Edit: also are you familiar with adb? You could boot to recovery and pull the photos with adb from there. And how much space is free on internal storage? The issues your experiencing sounds typical of full internal storage
Click to expand...
Click to collapse
you have to break that down a bit... only time I have to work on this is coming off of 12 hour shifts and im not too functional lol
there is space on internal I think about a gig or so left. the phone did NOT have issues prior to updating to 4.1. ALL problems started after 4.1.
also just tried installing a file manager... wont install. play store app freezes

TrinitySRT said:
you have to break that down a bit... only time I have to work on this is coming off of 12 hour shifts and im not too functional lol
there is space on internal I think about a gig or so left. the phone did NOT have issues prior to updating to 4.1. ALL problems started after 4.1.
also just tried installing a file manager... wont install. play store app freezes
Click to expand...
Click to collapse
Well to me it sounds like some issue was caused in the upgrade. Are you currently using a custom recovery? I ask because I have a feeling a factory reset will be your fix and with a custom recovery you could backup then wipe so you can troubleshoot w/o losing everything
And in the future once u fix this I recommend Dropbox which will automatically backup all those pictures so u dont have to worry about losing them again. Regardless of what you want to do to fix it we should be able to pull the pics even with mtp being borked

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

You could try rooting your phone and flashing a recovery. After that, go into the recovery and fix permissions. This won't delete anything and it's worth a shot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

billard412 said:
Well to me it sounds like some issue was caused in the upgrade. Are you currently using a custom recovery? I ask because I have a feeling a factory reset will be your fix and with a custom recovery you could backup then wipe so you can troubleshoot w/o losing everything
And in the future once u fix this I recommend Dropbox which will automatically backup all those pictures so u dont have to worry about losing them again. Regardless of what you want to do to fix it we should be able to pull the pics even with mtp being borked
Click to expand...
Click to collapse
no the phone has nothing special installed. looked into the custom recovery... and its not going to work (at least I dont think) cause I dont have a solid USB connection... as in it does "connect" per se. the phone knows its connected... the computer knows its connected but it doesnt show up as a drive like it used to.

In download mode, you shouldn't have problems like that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

TrinitySRT said:
no the phone has nothing special installed. looked into the custom recovery... and its not going to work (at least I dont think) cause I dont have a solid USB connection... as in it does "connect" per se. the phone knows its connected... the computer knows its connected but it doesnt show up as a drive like it used to.
Click to expand...
Click to collapse
rani9990 said:
In download mode, you shouldn't have problems like that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Can you not get it into download mode ?
If you plus it in will Odin recognize the phone ?

Updated to 4.3 and now I lost hundreds of pictures and videos from gallery

I updated it on 12/09/2013 and I can only see pictures back until that point and not before! I noticed it too late..
Man I tried every thing I could. ****, I downloaded the entire internal memory and converted it to VHD so I could run Recuva but still most of the recovered files are in huge zips and cant open them with any 7zip/winrar type of software. I downloaded other picture apps and they dont see it either. The SD card has it's stuff still there so thats not a problem.
I have been told its because the first roll out of 4.3 was bad and some people had issues. I want to able to downgrade to 4.1.1 but for some reason most of the methods out there are for people who have a non-stock 4.3 OS and not the OTA update.
Can anyone help me? I really want those pictures/videos back!
So, how can I go back to 4.1.1? It might be my last chance to get it right. I have Clockwork recovery and tried to put on the stock tmobile OS but it always fails via Odin and Rom manager. Phone still works. please help!

Check the mnt/shell folder
Sent from my SGH-M919 using Tapatalk

serio22 said:
Check the mnt/shell folder
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I tried everything. I do believe it's gone at this point. I recovered a few pictures that were half cut off with a professional recovery sw. Freaking terrible. Lost so much stuff. Never again I suppose :/

ilikeMangoes said:
I tried everything. I do believe it's gone at this point. I recovered a few pictures that were half cut off with a professional recovery sw. Freaking terrible. Lost so much stuff. Never again I suppose :/
Click to expand...
Click to collapse
Take a quick look in data/media/0 or data/media/legacy

Easy way to tell instead of looking thru all your folders.
Is the space still taken? If yes, then it's there somewhere, if not, then they are most probably done for.
Sent from my SGH-T999 using xda app-developers app

[Q] T999 UVDMD5 - Can't connect to camera (rooted or unrooted)

Hi All,
I'm am absolutely stumped and have tried what feels like everything I can to resolve my issue to no avail. So, I'm hoping to find success from the wisdom of the seasoned XDA community.
I have an SGH-T999 with baseband UVDMD5. In early September, my camera stopped working. When I open the camera app, I'm greeted with the infamous "Can't connect to camera" message. The front camera works fine (via Skype), but the rear camera does not. I've tried all of the following but the camera still won't work:
1) Unrooted and re-flashed the stock root66;
2) Finding the correct "SLIM_ISP.bin" file, placing them in the /data folder, and set the permissions to 777;
3) Re-flashed the stock UVDMD5 bootloader, firmware, and modem;
4) Took the phone to a shop to have a new camera installed and they couldn't get the new hardware to work either (so, it's definitely software related);
5) Cleared the app cache and fixing permissions in recovery;
6) Restored a Nandroid from a previous state of the device when the camera was fully operational;​
I don't know what else to do. PLEASE help me folks. I really want my camera back. Thank you in advance for your time and insight.
I've attached a Catlog I recorded while attempting to open the camera, if that helps at all.

just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness

Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi Doc, I tried that. Sorry. Should have listed it. I took it to a shop to have a new camera installed and they couldn't get the new hardware to work either. So, it's definitely software related.
Thanks for the suggestion though. Please let me know if you have any other ideas.

mrrocketdog said:
just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness
Click to expand...
Click to collapse
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.

At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

halebopper said:
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.
Click to expand...
Click to collapse
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness

mrrocketdog said:
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness
Click to expand...
Click to collapse
Thank you for your response and the suggestions.
That point makes complete sense. However, what I'm saying is that I've restored s Nandroid from a state when the camera was functional. However, the camera still doesn't work despite restoring a Nandroid from a previously operational state. So, please correct me if I'm wrong, but, considering that, what good would extracting the apk from the Nandroid do if restoring the entire Nandroid doesn't make the camera work?
Regarding your second suggestion, I have tried clearing the app cache and fixing permissions, but it didn't work. I'll add this to my list of attempted fixes in my original post.
Thank you very much mrrocketdog. I sincerely appreciate your continued interest and support. I hope we can figure this out.

well dang it ! hopefully someone else will chime in with some ideas. sorry i didnt have anything new. will keep thinking.
err on the side of kindness

DocHoliday77 said:
At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi DocHoliday77,
Thank you very much for the reply and the suggestion. Your advice seems sound.
I'm not sure what you mean by "controlling app." I'm afraid my knowledge is too limited to tell you if I've flashed the 4.3 firmware.
Not sure if this helps, but I have intentionally not upgraded beyond the stock baseband UVDMD5 version. I understand the baseband versions following UVDMD5 are bad due to the addition of KNOX and the inability to flash back to previous baseband versions.
Currently, I have flashed Carbon rom, which states the Android version is 4.4.4. However, I don't know if the Android version number is reflective of the firmware.
Regarding flashing a 4.1.1 rom, is there a rom you suggest that would be better for this than others? Should I just grab an older version of Carbon or would it be best to use Odin to flash back to a stock root66 version of 4.1.1 ?
Btw, not sure if you saw, but I uploaded a Catlog I recorded while trying to launch the camera app. I don't know if that will reveal anything or not. I can't make two cents of Catlogs other than to identify that errors are occurring. I really hope this isn't a faulty motherboard.
Thank you again for your continued interest and support. I really appreciate your advice. It means a lot. I hope we are able to resolve this.

If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok Doc. I flashed root66 T999 UVDLJC (Official JB Firmware - Latest JB 4.1.1 Firmware). After rebooting the phone, I entered the first code you provided - *#34971539# - into the phone dialer. This pulls up an all black screen with a gray colored placeholder/header at the top that reads, "CameraFirmware Standard." Again, other than the gray header and title, the rest of the screen is all black with no text or anything, except for the notification bar at the very top. Then, after sitting on that screen for a few seconds, it closes and the message, "Unfortunately, Factory Test has stopped," displays in a pop-up message.
I can make my assumptions about what that means, but I'd prefer your opinion. What do you think?
Thank you again for your time, insight, and assistance. I respectfully look forward to your response.
p.s. Just to clarify my experience for potential future readers, the second code you provided - *#7412365# - didn't work. It displayed, "Unable to process request" in a pop-up message.

That tells me that the system is most likely having problems communicating with the camera.
I'd open it up and make sure it's properly connected. It's very easy to do. You can find disassembly videos on YouTube if you want to see what to look for first.
If the shop couldn't get a new one to work, I'm honestly not sure what else you can try. It does sound like a hardware issue though. My best guess is its got something to do with the motherboard.
Sent from my SAMSUNG-SGH-I747 using Tapatalk