Hi,
I tried upgrading the camera firmware.
The upgrade worked, but after that I could not use the camera any more as it said "Camera Failed".
Here is the fix:
There are 3 steps for the camera to get onto the camera chip itself.
A: /system/firmware
B: Somewhere else on the phone
C: The camera chip.
Backup first:
Use the "CAM FW to Phone dump" to backup your current firmware.
I have not yet found out where on the phone this ends up, so I do not know how to copy it a PC for backup purposes.
FIX Proceedure:
Copy the new camera firmware to A.
Reboot the phone. After the reboot, the camera firmware will be copied from A to B.
Use the "Phone to CAM FW" option to flash the firmware from B to C.
Reboot the phone as requested, and you should then have a working camera again.
I used the camera-wave.7z to fix mine. (Found in another thread)
The "Show Camera FW version" gives totally bogus information. It shows only the FW version of the files at A, and not the contents of the camera chip itself.
Was this meant to be a useful post?
Yes. It has the FIX proceedure.
It contains an extra "reboot" step that if not followed, results in the same old firmware being flashed to the camera, and not the new firmware, thus failing to fix the problem.
after flashing wave fw no sgs fw worked for me so don't think it's really a fix - i could do that as much as i want - replacing fw and none would work then go back to waves. but the wave FW is pretty crapy against updated sgs fw in quality. in the end i went to service and they replaced my camera module.
are u sure it works?? my camera flash process arrives to 98% then it hold on for 5 seconds and then it tells flash success but nothing change!
I cant find any donwloadfile for the neuw firmeware...
can someone help me????
Related
I made the mistake of using samsung aps to update the camera firmware when it prompted me to.
Unfortunately this was not successful and the update FC so no my camera does not work properly.
Auto flash does not work, and the video only works at night (low light conditions). There is just a white screen in the day (normal light conditions)
There is the service menu to manually flash the firmware, just 2 (*#34971539#) issues with this:
1) I no longer have a fw that works.
2) My camera thinks it has the latest firmware so will not allow a reflash.
So can someone upload the files they have in : /etc/firmware
there should be 3/4 files:
RS_M5LS_OB.bin
RS_M5LS_OC.bin
RS_M5LS_TB.bin
qt602240.fw
The M5LS files look to be the firmware files for the camera.
Also does anyone know how I can update the version in these bin files from oced11 to a higher version oced12 maybe. So the camera firmware flash will allow the update? Or is there anyway that I can force the flash?
========================================================================================
Ok fixed it, for anyone else that has the issue with the Samsung App updater failing on the camera update here is how to fix it:
Copy /etc/firmware/RS_M5LS_OC.bin to the pc
open RS_M5LS_OC.bin in notepad++ and search for the version number (in this case oced11)
change the 11 to 12 (WARNING: only change the number do not add other characters adding even a space may corrupt the bin).
save RS_M5LS_OC.bin and copy it back to the phone in /etc/firmware
enter *#34971539# in the stock dialer.
select "Phone/CAM FW Ver Check" if you have done the previous steps correctly the versions will be different (phone version will be +1 on the camera version)
select "Phone to CAM FW Write"
Once this completes (takes 3min ish) the camera is now working correctly.
The files I used can be found: http://www.mirrorcreator.com/files/0PEES0BI/CamFW.zip_links
Thank you for sharing, might be helpful if something fails while updating.
Hi!
The cam update corrupted my camera, too. I tried to follow your tutorial but there's a little problem: I can't find the "/etc..." folder on my phone. I do have root access and dumped the cam firmware to the phone via the service interface. But still I cannot find it when I connect my phone to the pc. Can someone pleas help me? Thanks in advance!
Talpa85 said:
Hi!
The cam update corrupted my camera, too. I tried to follow your tutorial but there's a little problem: I can't find the "/etc..." folder on my phone. I do have root access and dumped the cam firmware to the phone via the service interface. But still I cannot find it when I connect my phone to the pc. Can someone pleas help me? Thanks in advance!
Click to expand...
Click to collapse
Don't look for it on PC , disconnect phone and download "Root explorer" from market ,then on phone itself with root explorer go to system/etc .
OK I found the folder with android mate. But there is no RS_M5LS_OC.bin only RS_M5LS_OB.bin, qt602240.fw and RS_M5LS_TB. I don't know what to do now.
edit: I'm not sure what happens if I took thelestat's file and put it on my phone. Maybe it's too risky...
Talpa85 said:
OK I found the folder with android mate. But there is no RS_M5LS_OC.bin only RS_M5LS_OB.bin, qt602240.fw and RS_M5LS_TB. I don't know what to do now.
edit: I'm not sure what happens if I took thelestat's file and put it on my phone. Maybe it's too risky...
Click to expand...
Click to collapse
Hi, looks like you are on the OB firmware, where I had an OC camera. you can check using the secret code in the OP.
Copy the RS_M5LS_OB.bin to your PC, Open itin notepad++ and search for the version the secret code shows you. Increment the number by 1, save it. Then replace it on the phone. Flash using the secret code.
If you want, post here the versions from the swcret code, and upload the file. I can do the editing for you.
Mine was dead too.I also can't find RS_M5LS_OC.bin,but i find RS_M5LS_OE.bin,OB,TB...but I open this 3 files,and I can't find the secret code(OCEE09).
Cam FW Ver: SCEF02
Phone FW Ver: TBEC28
Here are my files: w*w.mirrorcreator.com/files/1ONIHVSU/Camfirmware.rar_links
Hi,
It was in the RS_M5LS_TB.bin file. I updated the version to TBEC29.
The file is: http://www.mirrorcreator.com/files/QNQXTGZ8/RS_M5LS_TB.zip_links
Just replace the one on your phone and use the secret code to flash it.
I have OCEF02 as Cam fw and in firmware folder I have:
qt602240.fw
RS_M5LS_OB.bin
RS_M5LS_TB.bin
RS_M5LS_OE.bin
That's meaning I have installed RS_M5LS_OC.bin?
There is any chance to revert to TBEC28?
Thank you.
hi
i really can't believe it
i was flashing firmware update when THE ALARM RINGED!!!!!!!!
the flash app has crashed now i have a non working camera
do i need root to do this procedure?
I just updated my camera firmware through Samsung Apps. It all went fine, took a few minutes then I manually rebooted. Video, photos, flash all work fine.
Strange why it fails for some people. Maybe battery was too low ? Or different version of the camera hardware ?
btw now I have:
Cam FW Ver: SCEF02
Phone FW Ver: TBEC28
hi Thelestat
i rooted the phone now i'm stuck to the "version" part
would you mind to help me too please?
my files are these: htt p://w ww.mirrorcreator.com/files/0UIIP10D/
thelestat said:
Hi,
It was in the RS_M5LS_TB.bin file. I updated the version to TBEC29.
The file is: http://www.mirrorcreator.com/files/QNQXTGZ8/RS_M5LS_TB.zip_links
Just replace the one on your phone and use the secret code to flash it.
Click to expand...
Click to collapse
Is it based in TBEC28?
Cheers.
i REALLY don't know what happened
i managed to find that the firmware on camera was SCEF02
so i managed to put SCEF03 on the file
i tried to flash it started but crashed after 3 seconds
the i gave a punch to the table (i think it helped )
then i go to samsung apps redownloaded camera flash firmware and it said it was the latest version
uninstalled it
gone into the secret menu, and it said camera version SCEF02 and PHONE VERSIOn SCEF02
i gave ok and it started flashing
that were the longest three minutes of my life :O
i rebooted the phone and :O it is working now
it seems to me that downloading the camera firmware update left in /etc/firmware the "right one".... and even if it was the SAME version of the actual camera firmware, it worked
i'm really happy i was worried to have to send the phone to samsung.....
thank you thelestat... really, thank you!
akirax said:
Is it based in TBEC28?
Cheers.
Click to expand...
Click to collapse
yep, same file as the TBEC28 i just upped the version to
Hi everyone,
I recently bought a Galaxy S2 and I'm getting a "camera failed" error whenever I try to start the camera. I even tried to instal some other camera apps from the market but same error.
Can someone please guide me what is wrong with my phone?
Sent from my GT-I9100 using Tapatalk
faremoney said:
i REALLY don't know what happened
i managed to find that the firmware on camera was SCEF02
so i managed to put SCEF03 on the file
i tried to flash it started but crashed after 3 seconds
the i gave a punch to the table (i think it helped )
then i go to samsung apps redownloaded camera flash firmware and it said it was the latest version
uninstalled it
gone into the secret menu, and it said camera version SCEF02 and PHONE VERSIOn SCEF02
i gave ok and it started flashing
that were the longest three minutes of my life :O
i rebooted the phone and :O it is working now
Click to expand...
Click to collapse
I'm confused now, thelestat. This is the exact version of my cam firmware. Is the file you updated for me still the right one? Sorrry, but I'm a little bit frightened of flashing the file. Can this cause serious harm to my phone if something goes wrong? Thank you so much for your help.
Talpa85 said:
I'm confused now, thelestat. This is the exact version of my cam firmware. Is the file you updated for me still the right one? Sorrry, but I'm a little bit frightened of flashing the file. Can this cause serious harm to my phone if something goes wrong? Thank you so much for your help.
Click to expand...
Click to collapse
Yeah it is still the right version. It's the file you uploaded with the version number changed.
It is the exact same firmware as the samsung application tried to update, the change I made, just allows for the secret code flash option to work. It checks for a newer version before it allows the update.
It is unlikely to effect the rest of the phone, as it is only writing the camera firmware. I have used the secret codes to read an write a number of times, and have never had an issue.
I am not able to flash it: Invalid version TBEC29
Phone/CAM FW Ver Check:
Cam FW: SCEF02
Phone FW: TBEC29
By the way is it possible that there is no firmware version called TBEC29 out there? This would explain why it doesn't work.
This sucks...
i got a glaxy s4 and everything works, except the camera. i constantly get the message: camery failed
i tryed everything:
- wipe cache of camera and galery app and reboot
- i also replaced the camer module
- was on 4.4.2 stock and flashed optimized cm 12.1 and imperium v10
if i enter the code *#34971539# on 5.01 stock i can only press phone/cam fw check and cam and phone fw versions are different. i also can press isp core voltage check and vendor id and it returns null value.
under 4.4.2 i could also use other option in that menu but nothing helped. i flashed 5.0,1 and after the camera wasnt working i replaced it with a cam from someone that broke his screen and didnt need it.
can someone please help me?
no one?
bumping threads under 24hrs old is against xda rules.
ok here are my findings:
- even after camera module replacement the camera isnt working
- if i dial *#0*# i can turn on the front cam and it works
when i dial*#34971539# and press PHONE TO CAN FW WRITE than i get:
- CAM FW WER: S13F0SAGB39
- PHONE FW VER: S13F0SAGHO1
and when i press update it updates and tells me to reboot. after reboot the camera still isnt working and the strangest part is when i check cam fw version it is the same as before the update and if i press PHONE TO CAM FW WRITE i get the same option to update again. so actually the PHONE TO CAM FW WRITE is not working.
also i flashed stock android 4.2.2, 4.4.2, 5.01 with odin and the cam fw is always the same. is there any way to manually overide CAM FW? or does anyone have a solution?
i was also thinking if maybe some part of the system is corrupt and if there is any way to completely reflash the phone (because now with odin some settings remain even after flash)
I´m facing a similar problem with my S4, but both front and rear cameras don´t work.
About your situation. What is your s4 model? Did you installed the right module? Between all the s4 models, the rear camera modules are not the same? Between i9500 and i9506, for instance, each have a different rear camera module.
Hope it helps
Seraph| said:
I´m facing a similar problem with my S4, but both front and rear cameras don´t work.
About your situation. What is your s4 model? Did you installed the right module? Between all the s4 models, the rear camera modules are not the same? Between i9500 and i9506, for instance, each have a different rear camera module.
Hope it helps
Click to expand...
Click to collapse
my model is i9505 and i did install the correct module and its not working.
it seem like the camera fw doesnt want to update or its a faulty motherboard.
does someone have an idea what i can try to fix it?
I got the Same problem. It sucks as hell and i hope someone can help us!
same problem, someone knows how to fix now?
Same issue
I have the exact same issue with my T-Mobile variant of the S4. I've tried wiping the camera memory, factory resetting and even applying a new rom. I'll keep searching for solutions and if I find anything, I'll let you guys knows. I'm leaning towards this being a motherboard issue.
II have flashed a new firmware for my Samsung's Camera, and I noticed that the Firmware Install Count was changed from (0:0) to (0:1) on both Rear and Front Camera. How can I revert it back to (0:0)? Should I change the whole Camera Module? I am just hoping to fixed the "Warning: Recording failed". But then, flashing firmware doesn't resolve anything. Thank you!
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Using an unlocked Galaxy Note 3, (not yet rooted), the menu and the back key don't work. Checking the settings, with *#2663#, everything matches except the Touchkey with the following messages: Phone touch key FW version 0x10, Part's touch key FW version 0x12. When trying to update, the message is: IC's F/W is higher that BIN's F/W. It's Android 5.0 stock ROM, Fresh install of yesterday. Can someone please tell me how to update it?
As far as I am aware no update except in newer firmware.
With both. The keys don't work, and when I select update I get the message in this post's title.
Thanks <<<Nomintan>>>. I started the download from updato. Will post the results tomorrow.
<<<Nomintan>>> again many thanks for the download link. Downloaded and installed the firmware in about 40 minutes but it still didn't correct the problem. So, dialed *#2663# for the menu and clicked [Touch key fw update (internal storage)]. A message at the bottom of the screen was hlte_cypress_tkey.bin or hlte_coreriver_tkey.bin is missing.
So, I searched the issue and found two posts on this site here with the same problem and the solution:
https://forum.xda-developers.com/galaxy-note-3/help/to-fix-softkey-note-3-t3446134 and
https://forum.xda-developers.com/galaxy-note-3/help/button-menu-soft-keys-note-t3369533/page2
from which I assembled the information below, as a reference for those who have the same problem.
File download link:
https://github.com/friedrich420/Note-3-AEL-Kernel/blob/master/firmware/tkey/hlte_cypress_tkey.fw
Rename the downloaded file to hlte_cypress_tkey.bin (as mentioned in the first post).
Move the file to the internal Phone partition root folder, (as mentioned in the second post).
Dial *#2663# on the phone pad.
Click on [Touch key fw update (internal storage)]
and voilá.
Keep this file in case of rooting and uninstalling Samsung software. Some removed software may cause the same problem. In that case you can recover immediately.