Hello everyone!
Today I noticed that my camera stopped working on my new Galaxy SIII. I always get a "warning: camera failure" error when I try to start the camera app. I dialed *#0*# to test the cameras seperately, but both megacam and frontcam give me the "camera failure" error.
I bought the phone with 4.1.2, rooted it with Chainfire's CF-Auto-Root, flashed CWM recovery and everything worked fine. After some weeks I got the Kies update to 4.3.0 and updated via Kies. After this, the camera still worked. My root access got lost due to the firmware update, so I tried to re-root it again with the same CF-Auto-Root via Odin. Odin said nothing succeeded but also nothing failed, so I thought it didn't do anything. Well, it did flash the stock revovery again, but my phone didn't leave the download mode automatically after flashing, so I rebooted into recovery mode (because of a notice on Chainfire's website) and rebooted normally from there.
All this happened yesterday and today I noticed my camera doesn't work, so I thought the reason could be something concerning the semi-failed root procedure. Maybe anyone of you can help me fix my camera.
I searched the internet for a solution, but they say it's a hardware problem, which is probably not the case for my device in my opinion.
Thanks in advance!
- furcatus
Flash a full stock rom with odin after a factory reset, test camera before you install/restore any apps or mods.
If still the same then hardware fault.
Sent from my GT-I9300 using Tapatalk
Related
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
Hi,
I've updated the phone to the newer firmware from KIES, and the phone was connected to the WIFI network but signal connection keeps switching on and off, is there anyway to fix this issue so I can have a stable connection?
Have test with my iPhone and Ipad, both connectect to the same WIFI and only my samsung S3 having this problem.
PS: WIFI power saver mode is already <<off >>, keep Wifi on during Sleep mode is set to <<always>>, Network notification is <<un-tick>>
This is my current ROM (Rooted)
AP: I9300BUBLG3
CP: I9300BULG2
CSC: I9300VFGBLG3
settting > wireless & network > more > mobile network > automatic connections > sprint connection optimizer.. unchecked?
This is the international version is Samsung S3, I can't find such settings.
Sent from my GT-I9300 using xda app-developers app
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
jetbruceli said:
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
Click to expand...
Click to collapse
This was the latest stock rom from KIES update (also rooted). But thanks for the reply, I'll try to flash different ROM and see what will happen.
colint3 said:
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
Click to expand...
Click to collapse
I already set it <<off>>, still having issue with the wifi.
superfilm968 said:
I already set it <<off>>, still having issue with the wifi.
Click to expand...
Click to collapse
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
jonjuk said:
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
Click to expand...
Click to collapse
Sorry I don't have BT Home HUB 3, my connection is very simple, just connecting the S3 to a DrayTek Vigor2710Vn Router via Wifi. Please let me know the result after you flash with a new modem. If is working, please provide the link and file name where you got your file so I can flash it too.
Thanks!!!!
***By the way, what ROM version are you using at the moment? Please provide your AP, CP and CSC details if is different to my S3. ***
Repeat Modem has nothing to do with WiFi.
jje
I had the exact same issue, but ONLY after rooting the device (which I did just a day or two after I got it). I tried every possible fix, flashed new roms 3 or 4 times, wiped data and everything else in recovery, but no luck.
However, my final solution was to simply follow a guide to unroot the device, which I did today - and it did indeed work, I guess this issue is mainly happening to rooted phones, for unknown reason. Until I know this is fixed with an update (maybe in 4.1 JB), I won't be rooting this device again.
Link to guide on how to unroot
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
did you reset the flash counter?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
ph10m said:
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
Click to expand...
Click to collapse
Forgot to mention it but I did this yes.
I also think KIES would not update when this is not a zero.
I believe the Vodafone UK 4.1.2 update has only become available this week, updated mine last night OTA - previous update was OTA and worked fine. I constantly get the 'Unfortunately android.process.media has stopped working error' and it's also not keen to load the keyboard, and the battery life is now hopeless.
I've googled the error message and I can see that it's a common problem, and the poor battery life is linked to the error message I'm constantly getting. I've tried to raise a thread on the Vodafone Eforum, but there seems to be some problem trying to login at the moment (the forum software has always been hopelessly slow and glitchy).
After all my googling, despite it being a common issue, I can't seen any real solution - can anyone help?
Re-flash the 4.1.2 firmware via Odin. But this time go inte Recovery and wipe data/cache and Dalvik cache if necessary before flashing.
You're right it's a common problem, and wiping usually fix it. Try it.
Cheers.
Thanks, I presume Odin requires the phone to be rooted?
This is the first android phone I've had where I've been happy with the standard rom. I've connected to Kies and it seems to think there's a further update available, I'm backing up and I'll try this first.
If that doesn't work I'll be looking to root and try some of the custom roms.
Ok try Kies update.
And NO, Odin does not require your phone too be rooted. You can although root your phone via Odin.
Cheers.
scoobydoo99 said:
Thanks, I presume Odin requires the phone to be rooted?
This is the first android phone I've had where I've been happy with the standard rom. I've connected to Kies and it seems to think there's a further update available, I'm backing up and I'll try this first.
If that doesn't work I'll be looking to root and try some of the custom roms.
Click to expand...
Click to collapse
I installed that very rom using mobile odin had no problems at all. After which you can keep it as stock but you able to remove all the bloatware, bock adds etc as you always have root privileges.
Sent from my GT-I9100 using xda premium
My Galaxy S3 GT-I9305 LTE was running Liquid Smooth 2.37. Recently I lost notification and phone ring sounds and now I have lost baseband and I have no cell signal.
In the phone's 'about' section the baseband field is empty. Android version showing is 4.3.
I'm not quite sure what I did wrong, first to try and get back the sounds and then baseband, I have been playing around with various custom and stock ROMS and kernals to get full functionality back.
I've read tons of help posts but nothing works.
Here's a few of the things I've tried with results in brackets, used CWM recovery to restore working backup (failed 'unsupported file' message),
reflashed kernals (neither Boeffla nor yank555 have worked, wipe/data restore in CWM (it still takes me back to 4.3 with no baseband).
I thought I'd re-flash back to the phone's original stock ROM using Kies, but the weird thing is Kies doesn't restore, it upgrades to the latest 4.3 ROM which fails to restore baseband.
I wanted to send the phone back to the 4.1.2 it came with or was it an earlier ROM? I can't remember as I didn't note it down, I bought the phone second hand, it arrived loaded with a stock ROM for Australia's Optus network. I promptly rooted and flashed the phone to Liquid Smooth and the phone ran fine for months on the 2 Degrees Network in New Zealand.
Anyway, I must have tried reflashing a dozen stock roms I've found online using Odin. Some of them partially work, I get sound back, (it seems only the 4.3 ones work, with the german I9305XXUEMKC reliably loading - it even gives me a NZ english install option) but don't restore the baseband
. All the ones I've found for Optus are rejected, I get the 'unsupported device' or status 7 error in Odin.
So I decided to flash one that works, install cwm, root the phone and try installing different baseband kernals to fix the (probably corrupt) efs.
But I'm going round in circles trying to root the phone. Using CWM, supersu shows as successfully installed, but when I boot into the OS root checker shows my phone is not rooted. Knox seems to obstruct every attempt I make to disable it as well. I keep getting these 'knox stopped etc...from working messages'.
I'm sorry if my description is a bit confusing, I'm happy to clarify anything.
I'm at my wits end. I want to try everything before I have to ship the phone off to a repairer who may charge me hundreds of dollars to fix the phone.
This is I9300 not I9305 Q&A
Use the report button and ask a mod to move to the correct forum .
I can offer no help as i fail to understand the post .
As said before you are in wrong place and are not giving us a clear question to answer. If its a root problem there are fixes for it. Status 7 error is discussed in many threads. Flashing MG4 modem fixes efs problem. Downgrading causes problem. Learn to search before making a thread.
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.