Hi All,
I have finally signed up today, after reading numerous threads over the last few days. My problem is that a few days ago I changed ROMs from Omega to CW10.1. After the change the camera is black, clicks repeatedly and crashes after a short while. I therefore reinstalled the Omega ROM, however the problem remained. I next used Odin to flash to a stock Samsung JB ROM. The problem remains. I am now on the standard JB Rom with a Siyah Kernel. I have wiped cache, dalvik cache and perfomed factory reset several times, all to no avail.
Checking the phone/camera firmware reveals TBEC28 for both.
I have downloaded the camera update apk from a thread on here, however upon entering airplane mode this too crashes.
What I would like to know is how, if at all possible to manually change the firmware? I have found the individual rs_m5ls_** .bin files from the camera apk but do not know how to install these, in order to try different versions?
Thanks in advance
In addition to this I found another thread saying to place the .bin camera firmware files in sys/etc/firmware, however no such file exists in the etc folder?
I have tried placing the .bin files on the sd card and also in the /data file, however when using the *#34971539# to update the phone always shows the same TBEC28 for both phone and cam.
Clicking the update always shows the same, 'this is the latest firmware'.
Any experts out there with knowledge of what I am doing wrong or a way around this problem?
Ok
Well im progressing slowly and am now able to flash the camera firmware to various versions using the bin file.
However although varoius versions have stopped the camera clicking the display remains black and crashes
I see many people have had similar troubles. Did anybody fix this?
Related
Now before you all say " great another thread about this problem " hear me out.
Ever since jumping onto Legend's Simpistic ICS ROM I've gotten these problems it started with RC5 and has continued through to RC6 Update 1.
When trying to download an app over 10mb via 3G i get this error how ever when downloading it via WiFi I don't receive it.
I've googled the problem and have found every single solution possible.
Wipe Cache
Wipe dalvik cache
Go to to Apps and clear market cache and data
Factory reset (I do this with every major updated ROM)
I've tried link2sd
I've downloaded Root Explorer and cleared any .dex files and cache I could find..
How ever this problem still persists. The only other thing I can see it being is possibly the modem included with the ROM?
I used to have Simple & Clean ROM which had the ability to download different modems depending on country and never had a problem but like I said ever since Legend's ICS I've encountered it.
Any one else having or had a similar problem and found a solution?
Would be greatly appreciated thanks!
Also I'm using a Galaxy SII w/ Legend's Simplistic ICS RC6 Update 1 ROM
Just another quick update. I've downloaded the KI3 Modem and Australia zip that I grabbed from the Simple & Clean thread back when I was on Gingerbread and have installed them via CWM how ever my problem still persists.
And for some odd reason WiFi doesn't work either it connects perfect but nothing loads which is strange because just last night it was working fine when I downloaded Drag Racing and a few others games.
ICS = buggy leaked beta test rom with multiple users posting multiple and varied errors .
jje
And yet there are hundreds of other android users who are still on Gingerbread reporting this same issues with various solutions on how to fix it.
I've read a few of the ICS threads in the other forum to see if anyone has had this problem but have not come across anyone yet, hence why I'm posting it here.
And to note with Legend's RC5 i had no problem but when i went to update 1/2 it started I also tried WanamLite and didn't have the problem so obviously it's either Legend's RC6 ICS ROM or who knows just wanting some light shed if anyone else has the same problem with an ICS rom or has done something that I haven't
Hello,
Hopefully someone can help
S3 was locked to three UK network.
Odin flashed generic newer UK firmware.
Decided to hard reset via buttons.
(noticed a message about multi cnc being applied)
Once it had gone in to the set up in ICS it keeps saying
" Messaging stopped and had to close " or something along those lines.
Tried to reset again and it wont clear.
Anyone know how to fix?
Should I odin flash the firmware again or do I have to go back to original three firmware file, then reflash the new one?
Also note my handset is now network unlocked using code supplied by provider.
Look forward to any assistance and advice, thanks
I had this problem when flashing a custom rom. The trick is to flash without wiping data, albeit this issues has been cleared up in newer versions.
Not sure what to advise if you're just after the firmware... download a custom rom and make a backup of the sms feature.
Hangon I may have the sms fix still on my phone from when I had this issue I'll upload if I can find it. Make a nandroid first though as I can't be sure it'll be transferable as I used it on the XXALE8 firmware (the only one at the time)
Edit: I no longer have it, can't find it anyway. You'll have to ask indie from omega and see if he still has the file. The one you're looking for is called "sec_csc.zip" I'm sure he'd remember if you tell him its for the sms fix.
Sorry I couldn't be of more help
Sent from my GT-I9300 using Tapatalk 2
similiar problem
Hi guys, I have a problem which is similar but not after a custom rom install. My messaging app just closes when I go to add a contact button to the right. Any ideas. thanks.
Jonny
Hi,
I do not have enough posts to post in the cyanogenmod nightlies thread to get a definitive answer, hence why this subforum. I guess my question may be rom independent anyway.
I 'upgraded' from an M release of cyanogenmod to a nightly and buggered my phone. I was forced to flash the stock firmware and then reflash the nightly to fix everything. Except my camera shows a black screen (behind the onscreen focus and options) and force closes nearly all the time. I thought it was just the nightly, but 2 months and 20+ new nightlies later, I still have the issue. In the nightles dev thread, people say the camera is fine. I know the hardware is fine, because 1 in 40 tries the camera randomly works.
I tried a factory wipe, which I now know just wipes user data. So In CWM, under 'mounts and storage' I formatted everything I could and did another factory reset, cache etc. No fix.
I guess this issue is with the rom itself, if the camera is force closing? So I'll have to use Odin or such to flash a stock rom again and flash another cyanogenmod version? But I want to check this is correct before continuing, and how I can completely wipe any trace of the current rom before flashing the stock and another nightly - so I don't get this issue again.
Thanks
So I finally found the issue, after battling with heimdall on ubuntu 14.04 for hours. Its a hardware problem.
I'm just going to leave my experience here in case someone else has the same issue, since anything to do with all the issue I am about to describe don't seem to be documented anywhere on the web clearly.
Firstly, I battled with heimdall 1.3.2 to recognise my phone on ubuntu. I kept getting;
Code:
ERROR: Failed to receive response!
After a number of threads talking about installing usblibx drivers I found one about which libs to install from terminal;
Code:
sudo apt-get install libXXXX
Code:
libusb-ocaml
libdevice-usb-perl
libhpmud0 (not sure if it's essential)
libusb-0.1-4
libusb-1.0-0
libusb-1.0-0-dev
libusb-dev
libusbprog-dev
libusb++-0.1-4c2
libusb++-dev
libusbtc08-1
libusbmuxd-dev
libusbprog0
libusbmuxd1
I installed all but couldn't find libusbmuxd1, restarted anyway, to the same error. I purged heimdall 1.3.2 and instead installed it from the Ubuntu software centre, which using
Code:
sudo apt-cache policy heimdall
showed that I had version 1.4 installed. Then I managed to find
Code:
libusbx-1.0.14_1.0.14-1_amd64.deb
floating somewhere on the internet, which finally installed the proper libusb stuff and allowed heimdall to continue without the error message.
I made a .pit file from my phone. I recommend this first. After hours searching for a stock rom (samsung has removed most of its firmware downloads? and asked links to be removed on other sites!?) came across this site
(I can't post links as a new user) - google [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall
Which explains how to flash using heimdall. After a successful flash, my phone didn't get farther than the boot animation. I booted into stock recovery with vol up-home-power to factory reset, but noticed a dead droid and red writting. Rather than continue, I wanted to fix this, so I followed the tutorial again, but this time checked repartition under the pit path, and hoped for the best. The phone stalled at the boot anim again, but this time in recovery, all was good.
I did a data wipe / factory reset, cache wipe etc, but nothing. So I stuck the stock rom zip onto the micro sd and installed it from recovery, factory reset, and rebooted. (which is odd, having to install the rom from recovery - because doesn't that kinda defeat the point of using the same image on heimdall in the first place?!?)
The phone booted! So after all that, (Having data/factory reset, wiped the cache, (wiped the dalvik cache when i had CWM before and formatted all I could in mounts and storage) flashed the stock ROM AND repartitioned the phone) i thought that would eliminate any software issues. I thought the camera would work.
Nope.
As usual, the front camera worked, but the back, now, after a pause would give the samsung error:
Code:
unknown error by errorcallback
Now, after googling this (Cyanogenmod gave a different error with no related answers on google) and being annoyed at my time lost, I took the tongue and cheek advice from some random forum commenter, to tap the camera hard.
It worked.
Apparently, the entire time the camera was suffering from a hardware issue. Something about a 'sticky shutter'. Anyways, i'm going to leave the stock ROM and take it into a shop to get it fixed. Just leaving this trail of breadcrumbs in the hope it helps someone else.
Perhaps this could be marked as 'solved'.
Same problem
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
JCNouel said:
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
Click to expand...
Click to collapse
Try flashing stock rom and see if this fixes your problem.
gsstudios said:
Try flashing stock rom and see if this fixes your problem.
Click to expand...
Click to collapse
It fixed it, but then I flashed back the AICP ROM, which is KK, and it malfunctioned again. I'm going to try with a JB Custom ROM.
Update: I flashed a JB Custom Rom (Fusion Rom) and it's working good so far.
Hello,
I have been googling and reading all threads about this issue for over a month now, so it's problably something quite special. Every time I try to use an app using a camera or flashlight, it reports with "Can't connect to camera" message. This first happened while trying to flash a Kitkat rom (Artas's CM11) with wrong recovery. So it was not working, I got back to system, flashed the correct recovery via flashify, got back to it and finally flashed the rom. Ever since that the camera has not been working, with one exception - now this is the interesting thing that makes me think it's not a hw problem - while trying to do all kinds of unbricks and resets I know of (flashing all kinds of different roms, CM based, AOSP, of course all kinds of original roms) I decided to go for KDZ - so I got the original bin I found on this forum and got back to v10i and the camera worked! So I was happy that it's solved and decided to stick with stock rom. It updated to JB (the official way) and ever since, it has not been working. I have tried to flash persist images, to mess with permisions and I can't really think of any other way. (Of course I have tried to flash KDZ again the same way, but it did not work, not even on ICS).
Thanks for every idea!
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'