disable rear camera? samsung galaxy S III

[alphaomega]

I got my hands on a second hand Samsung Galaxy S III.

It has an unprovisioned SIM card and I got the carrier unlock code from AT&T.

 

I'm trying to figure out if it's possible to disable the rear facing camera (broken protective

lens) because I cannot get the camera app to work (or the other ones I've tested).

 

When I try to launch the app I get an error: camera failed.

 

Read online to try and force stop the app and clear data and cache.

That did not work. Still get the camera failed error.

 

I found the code online to get into the hidden diagnostic menu:

 

 

Tested the front camera and it works.

Tested the mega cam (I assume is the rear facing camera) and it fails.

 

I also found the code to get into the camera firmware menu:

 

 

 

I'm just checking to see if by chance anyone might know

if there is a code I could use to disable the rear camera or if

anyone knows of a camera app that would only use the front cam.

 

It's not really important as I rarely ever take selfies and I can

get to the front camera from the diagnostic menu.

 

Just curious.

Edited February 1, 2015 by alphaomega

[securitybreach]

The default android camera can use the front camera to record as video or take a picture.

 

Personally I would install a custom rom (after backing up the current one) to test if it is a hardware issue or just the software(I am betting on it being a software issue).

[securitybreach]

Oh wait, so it is actually broken?

 

Samsung Galaxy S3: How to Switch Camera

[alphaomega]

Oh wait, so it is actually broken?

 

Samsung Galaxy S3: How to Switch Camera

Yes, I do think the camera is actually broken/damaged more than just the protective lens.

I did try to get into the app settings to set it to the front camera but the app closes out before I can make the change.

 

The default android camera can use the front camera to record as video or take a picture.

 

Personally I would install a custom rom (after backing up the current one) to test if it is a hardware issue or just the software(I am betting on it being a software issue).

 

I initially thought it might be a software issue but now I think it is a hardware issue because I get the same camera failed message when I test the mega cam from the hidden diagnostic menu.

 

I am planning on testing Cyanogenmod on it as soon as I get it properly unlocked from AT&T.

 

I would attempt to replace the camera but I do not trust myself to not mess the phone up more with all those very small parts and delicate ribbon cables.

Edited February 1, 2015 by alphaomega

[securitybreach]

That could still be related to software only.

 

I am planning on testing Cyanogenmod on it as soon as I get it properly unlocked from AT&T.

 

That is so that you can use a simcard from tmobile or similar and has nothing to do with changing the software on the phone.

[lewmur]

I got my hands on a second hand Samsung Galaxy S III.

It has an unprovisioned SIM card and I got the carrier unlock code from AT&T.

 

I'm trying to figure out if it's possible to disable the rear facing camera (broken protective

lens) because I cannot get the camera app to work (or the other ones I've tested).

 

When I try to launch the app I get an error: camera failed.

 

Read online to try and force stop the app and clear data and cache.

That did not work. Still get the camera failed error.

 

I found the code online to get into the hidden diagnostic menu:

 

 

Tested the front camera and it works.

Tested the mega cam (I assume is the rear facing camera) and it fails.

 

I also found the code to get into the camera firmware menu:

 

 

 

I'm just checking to see if by chance anyone might know

if there is a code I could use to disable the rear camera or if

anyone knows of a camera app that would only use the front cam.

 

It's not really important as I rarely ever take selfies and I can

get to the front camera from the diagnostic menu.

 

Just curious.

You might want to check this xda forum devoted to the S III. And, as someone mentioned, there is a difference between "unlocking" a device, to use it with a different carrier, and "rooting" the device, to install custom ROM software. You don't need AT&T to "root" the S III.

Edited February 1, 2015 by lewmur

[alphaomega]

That could still be related to software only.

 

I am planning on testing Cyanogenmod on it as soon as I get it properly unlocked from AT&T.

 

That is so that you can use a simcard from tmobile or similar and has nothing to do with changing the software on the phone.

Software or Hardware related, I still don't know how to verify it either way.

I just assumed it was a hardware failure since the test failed from the hidden diagnostic menu.

As to getting it carrier unlocked from AT&T and changing the software on the phone,

I just wanted to get it carrier unlocked while it still had the original software on it

before I go messing it up.

Edited February 1, 2015 by alphaomega

[alphaomega]

You might want to check this xda forum devoted to the S III. And, as someone mentioned, there is a difference between "unlocking" a device, to use it with a different carrier, and "rooting" the device, to install custom ROM software. You don't need AT&T to "root" the S III.

Thanks, I'll check out that link.

 

True, carrier unlocking a device and rooting a device are two different things.

I just don't want to take and chance at messing things up rooting the device

before I get it carrier unlocked from AT&T.

 

One thing at a time. I've only done this stuff a couple of times so I'm

not that comfortable doing it. I'm too afraid of possibly bricking the device.

Edited February 1, 2015 by alphaomega

[securitybreach]

Well the software has nothing to do with unlocking the sim slot so if you used the default rom or a custom rom, you would do the same process. That is simply adding a 14 character code based on your IME using your using the dialer.

[alphaomega]

Well the software has nothing to do with unlocking the sim slot so if you used the default rom or a custom rom, you would do the same process. That is simply adding a 14 character code based on your IME using your using the dialer.

I don't know.

I just recall reading somewhere that I should be on the original rom to carrier unlock.

And I hope the 14 character code is/could be different depending on manufacturer

because they gave me an 8 digit carrier unlock code.

[securitybreach]

It depends on the model number (IME) and the original provider.

[alphaomega]

After much reading I've updated the system to 4.4.2 (not rooted).

Somehow I must have got lucky that I did not lose any settings or data.

 

After each step I checked:

A. that the warranty flag was not tripped.

B. that the usb adb drivers were still working.

C. that I could get into odin and recovery mode.

D. and if the rear camera test still failed.

 

Warranty flag was never tripped.

Had to re-install the usb adb driver.

Had no problems getting into odin or recovery mode.

Rear camera test always failed.

 

The system started from a factory reset to 4.1.1.

Got the carrier unlock code from AT&T.

Found a carrier who agreed to help me carrier unlock.

Agreed over the phone that I would not have to setup service.

At the store they changed their mind and said I would need to setup service.

 

Note 1: I used the information found here to carrier unlock.

Not positive if the carrier unlock took. Later in the thread someone asked:

Anyway, how to verify it's indeed unlock? I don't have a micro sim to test, if "SHA256_INFO" says "SHA256_ENABLE_FLAG[0]", does this confirm unlock status?

 

Found another store (same carrier) who agreed to help me carrier unlock.

When they put their sim in it did not ask for an unlock code.

 

It gave a message about an unprovisioned sim.

I asked if the sim was working and she said yes they use it to make

calls all the time on the demo phones. She said I should contact AT&T.

Called AT&T and their system was indicating "NA" for carrier unlock.

 

I thought an unprovisioned sim meant that the sim was not configured/provisioned for the carrier?

 

The phone functions worked with another provisioned AT&T sim to make calls when on 4.1.1.

 

Anyway, it does not really matter as I'm not using the phone functions.

I'm using talkatone to make the rare call over wifi.

 

edit 1:

Talkatone: Outgoing call (called person cannot hear me) / Incoming calls work.

Hangouts: Incoming/Outgoing calls work.

 

edit 2:

Talkatone: Outgoing call worked after I unpaired the bluetooth headphones.

They were turned off. Ringer sounds awful.

 

Note 2: I used the information here to upgrade from 4.1.1 -> 4.1.2 -> 4.3.

I used adb and sideloaded the zip files from recovery.

 

Note 3: I used the information here to upgrade from 4.3 -> 4.4.2.

I used adb and sideloaded the cfg file from recovery (after renaming it with zip extension).

 

Screenshots:

http://forums.scotsnewsletter.com/index.php?showtopic=47682&st=125#entry417107

 

edit 3:

Note 4: I used adb to sideload the ota zip file from this page.

 

bootloader/baseband/pda/csc all at FNJ1 warranty void not tripped (no root).

 

Notes:

 

FREE UNLOCK* For Samsung Galaxy S3 and Note 2 - ALL GSM carriers & GALAXY Rugby Bell - Page 13 - RedFlagDeals.com Forums

1. http://forums.redflagdeals.com/free-unlock-samsung-galaxy-s3-note-2-all-gsm-carriers-galaxy-rugby-bell-1266487/13/#post15907770

 

[Download][install] 4.3 OTA Update

2. http://forum.xda-developers.com/showthread.php?t=2387423

 

[Download]AT&T Kitkat OTA file

3. http://forum.xda-developers.com/showthread.php?t=2788012

 

UCUFNE4 to UCUFNJ1 update

4. http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792

Edited February 18, 2015 by alphaomega

[alphaomega]

[alphaomega]

I assumed the greyed out option "Phone to CAM FW Write (Rear)"

might mean there was a problem with the rear camera.

 

While researching something else I came across this post

which helped to better explain the menu:

 

JB 4.1.2 and Camera Driver

My starting point was the same...

Rear Camera ZDFE02

Phone FW ZDFI02

 

With FW ZDFE02 rear camera failed and front camera worked when testing

from lcdtest "*#0*#" and self test mode "*#7353#".

 

Upgraded the camera firmware to ZDFI02.

 

With FW ZDFI02 both rear camera and front camera failed when testing

from lcdtest "*#0*#" and self test mode "*#7353#".

 

 

Downgraded the camera firmware back to ZDFE02.

 

With FW ZDFE02 rear camera failed and front camera worked when testing

from lcdtest "*#0*#" and self test mode "*#7353#".

 

Upgraded the camera firmware to ZDFF03.

 

 

With FW ZDFF03 rear camera failed and front camera worked when testing

from lcdtest "*#0*#" and self test mode "*#7353#".

 

FW ZDFE02 rear camera failed / front camera worked

FW ZDFF03 rear camera failed / front camera worked

FW ZDFI02 rear camera failed / front camera failed

[securitybreach]

Sorry man but I do not have an experience with camera firmware on Android. Usually it just works.

 

As far as Odin, I have not played with that since 2010. Do they have a linux tool yet to access it?

[alphaomega]

Apologies for reviving an old thread. I found a work around.

 

More than a year later and I'm still using this old phone as an mp3 player, to play games,

as an internet search tool, and a phone using Wi-Fi.

 

Never found a way to disable the rear camera but searching the Google play store today I found this:

 

https://play.google....tartFrontCamera

 

So now I can more easily take a photo with the front camera and am able to now record video as well.

 

Not bad for an old phone with no service.