I've read as many posts on this problem from the S3 through the S5 and have still not come up with a solution to the problem that's plaguing my S3. There are a lot of different hypothesis across the internet about the cause of this problem. I'll give the details with my personal experience.
As a side note, there is a possibility I could have flashed something wrong or rooted something wrong, but, given every other application works with no force closes on anything, I'll assume that everything was rooted and flashed correctly.
I've tried a couple of different ROMs after rooting the SGS3, but have stuck with Wicked. Unfortunately, I did not try out the camera until I came across Wicked, which is where the problem presented itself. This does not mean that it's Wicked itself, but possibly a problem further along than that.
Here's the specs on the phone.
I went from a fully updated software version on the T-Mobile USA Samsung Galaxy S3 non-LTE to
Android 4.1.1
Baseband T999 UVUEMJC
Kernel 3.0.65 Deviant
Build Wicked V10
I've tried the normal Force Stop Camera then clear Cache, cleared Davlik, tried other cameras, Factory Reset twice, reloaded ROM, and will flash new baseband (4.1's) My guess is that's the problem, possibly.
I've checked hardware as well from tightening screws, covering the camera, and removing the rear camera and plugging it back in; no change. As well as testing the hardware via *#0*#. The front camera works, rear/Mega does not. Which leads me to believing it's a software issue and not a hardware issue.
Flashing CM 11 - M9 on I9300, stock camera is missing
I have flashed CM11 - M9 on my Samsung Galaxy S3 (I9300) freshly, doing factory reset and wiping all the data, then flashed PA Gapps Full Modular version. After booting the phone, was getting a prompt "Google Keyboard has stopped", there after was unable to get the keyboard option at all, during setting up the phone and CM account. Again, wiped, factory reset, clear cache and freshly flashed the CM11 - M9 without flashing PA Gapps this time. Booted the phone, got the setting done, noticed that Gapps are already installed in the phone. And CM stock Camera is missing
I have been using CM 11 since a long time, but issue arrived when I flashed Gapps 4.4.3 (Google Stock), my CM camera has been replaced with Google Camera which sucks, thereby I have decided to reflashed my phone with CM11 - M9. Now the Stock CM Camera is missing.
Someone, please suggest, how to fix this issue??
Gaurav Kumar said:
Someone, please suggest, how to fix this issue??
Click to expand...
Click to collapse
I would suggest trying to start a new thread instead of posting a problem that is no where related to the problem at hand. Might give you some better feedback.
I've brought back the Galaxy S3 back to stock:
Android Version: 4.3
Baseband: T999UVUENC2
Kernel: 3.0.31-1962493
Build: JSS15J.T999UVUENC2
Lo-And-Behold the camera and everything else works now. Definitely a software issue or a flash issue with Wicked ROM 10
I may flash it again in the future, but for now the stock ROM is much more stable all around and will continue using it, rooted of course.
do you have a link where to find the stock rom?
thnx for so far
caffeinetripp said:
I've brought back the Galaxy S3 back to stock:
Android Version: 4.3
Baseband: T999UVUENC2
Kernel: 3.0.31-1962493
Build: JSS15J.T999UVUENC2
Lo-And-Behold the camera and everything else works now. Definitely a software issue or a flash issue with Wicked ROM 10
I may flash it again in the future, but for now the stock ROM is much more stable all around and will continue using it, rooted of course.
Click to expand...
Click to collapse
Rick_v1989 said:
do you have a link where to find the stock rom?
thnx for so far
Click to expand...
Click to collapse
I believe that I downloaded mine here at SamMobile. It's pretty self explanatory and has given the best information on reverting back to stock firmware, let alone the choices for the models and firmware are second to none as I've searched and searched across many websites. It offers, as far as I can tell, the most recent firmwares for all Samsung phones across many/all carriers.
Related
Hello, I have the "4g" flavor white back T-Mobile version of this tab and with there being different flavors of the 10.1 I am not sure which rom to use. After rooting the phone and getting revovery installed CM downloaded and installed the wifi version of the rom. I thought I found the nightly thread of the tmo version but revovery wouldn't install it saying that the build version was wrong. So I have gone back to stock until I can get this issue cleared up. I think my build prop may be wrong in the device because com.phone.android force closes on boot on the stock rom (I think I need to reinstall stock). But I am still not sure which flavor of the rom to install. I want the CM ICS.
I am not new to installing and using custom roms. I have been doing this since the MT3GS and have been using CM on that since Froyo. I am currently using MT4GS and currently have the CM ICS alpha 4 on it. I am just a bit confused at this point since it is not cut and dry.
c0c0c0 said:
Hello, I have the "4g" flavor white back T-Mobile version of this tab and with there being different flavors of the 10.1 I am not sure which rom to use. After rooting the phone and getting revovery installed CM downloaded and installed the wifi version of the rom. I thought I found the nightly thread of the tmo version but revovery wouldn't install it saying that the build version was wrong. So I have gone back to stock until I can get this issue cleared up. I think my build prop may be wrong in the device because com.phone.android force closes on boot on the stock rom (I think I need to reinstall stock). But I am still not sure which flavor of the rom to install. I want the CM ICS.
I am not new to installing and using custom roms. I have been doing this since the MT3GS and have been using CM on that since Froyo. I am currently using MT4GS and currently have the CM ICS alpha 4 on it. I am just a bit confused at this point since it is not cut and dry.
Click to expand...
Click to collapse
I have this one on now There are also CM9 nightlies on the CM site I believe but no issues with this other than camera. There is a camera patch also that makes the back camera work.
http://droidbasement.com/db-blog/
Here is the thread with the camera patch.
http://forum.xda-developers.com/showthread.php?t=1787399&page=65
Not sure why not many people help on this device it's a very nice device and works great on the T-Mobile network but anytime I ask anything no one ever really answers.
This thread will help you get started
http://forum.xda-developers.com/showthread.php?t=1446500
Thank you very much!! I think I have the wrong recovery installed which is causing all my issues. It is seeing my device as a wi-fi only device and not a tmo device.
I just got home a few minutes ago, and I had the wrong recovery installed. I got the right one in and everything is going swimmingly so far. Thank you again!
I wish there were subforums for every flavor instead of everything all mixed up. It makes it confusing when you are dealing with 80 different versions of the same device.
SOLVED: Thanks to ares05 I already got the rom I wanted! I didn't find that specific rom in the first place... Anyway, anyone googles for this same matter can use my thread as an Q&A. The only thing I did to get Neatrom Lite working was putting it on Internal SD (Without wiping data). And flashing it (choose zip from internal SD) from the custom CWM recovery, then reboot. (Yes for beginners, CWM is an requirement!). For Nexus layout lovers try regular Cyanogenmod, Trebuchet or MIUI. They are all great.
----------------------------------------------------------------------------------------------------------------------------------------------
Hello,
Question to myself: did I researched, googled and watch the video upon registration?
Yes, but that doesn't solve my specific problem or provide enough information to try the risky situation.
Problems:
I have trouble upgrading from Android 2.3.5 to 4.0 through Odin3 v1.85. It's very unclear what Rom I need to get to flash.
I flashed through Odin3 Android 4.0 before, through reading a lot and accepted the try and ended up getting boot loops. So I flashed back my android 2.3.5 XWKJ5. that gave me CWM but also voided the possibility to upgrade through Samsung Kies what I regretted later.
Then I thought, Okay... I'll get the basic Custom Rom: Cyanogenmod 9.1 then, through wiping cache/factory and dalvik cache and flashing through zip file on SD card everything went great. But I was unhappy with CM9 because the playstore app didn't work anymore and I didn't liked the overall layout of the camera, apps and some other minor bug I found - I forgot... So I went back to Android 2.3.5 with nandroid backup.
Also I have ROM manager but that doesn't let me update the specific CWM 6.0.1.0 rom as it says "An error occurred while downloading your recovery." Probably more people have this?!
What I need to know to solve this matter:
I want the default (stock) android 4.0+ ICS firmware on my phone with root. Can someone provide me the exact link of the .tar/.tar.md5 file needed to upgrade my phone to that android version or higher if the rom is available for it (4.1.3?). Since I find it hard to search the correct rom needed to get this result. The rom you might provide me can be slightly modded but that's okay, as long as I have all the ICS features and the layout it naturally comes with.
All the current Phone specific data you might found useful in helping me:
Samsung Galaxy S2 (I-9100)*
Android 2.3.5
Gingerbread.XWKJ5
CF-Root 5 Kernel (Root, CWM, Superuser).
+Has made an Nandroid backup through recovery.
+Backed up my apps through Titanium Backup.
*It's no AT&T or T-Mobile version, luckily.
TL;DR: I WANT TO UPGRADE ANDROID 2.3.5 TO 4.0+, WHAT SPECIFIC ROM I NEED TO FLASH?
I hope someone good willing enough is there to help me and I will check this thread often for any replies,
Scy.
There are a bunch of ROMS here which will give you the stock ICS look and feel. I haven't tried all of them but if that's the kinda ROM you want then you could check out the ROM that I'm currently using, Neatrom Lite. Follow the link on my signature to the ROM thread. The latest version for Neatrom is 4.0.4 and you could download it from the link given on the first Page of the thread.
If you wanna try something else you check out the following links :
http://forum.xda-developers.com/showthread.php?p=23562820
This is a thread with an index of all the stock ICS ROMs
http://forum.xda-developers.com/showthread.php?p=23275441
This is an index of all the custom ROMs.
Take your pick.
Sent from a GT-I9100 having a mind of its own
Yeah, that's sort of what I want. The biggest reason of wanting to update is that my brother has stock ics 4.0 and his battery consumes like 50% less energy in locked mode(s), factor in the fact that his update cleaned a lot of the processes and unused apps. Also I am fond of the original stock look - especially the camera controls.
I will try neatrom (lite) later tonight I checked out the official forum Page, looks very very to my liking. I am so excited, thanks for showing will report later if it worked out.
- EDIT -
Yaaaay! Everything went flawlessly, it's cool that there is no Wipe needed as the forum thread indicates. I don't know if it works fluidly yet, but it seems everything is up and running like if it was original ICS. I think the Siyah kernel helps alot in battery usage which means alot to me because I travel alot. I will keep this rom for a long while if no bugs/freezes pop up! Seems so promising, thank you thank you thank you~~!!
Okay...I have had this problem for a while now and cant find a solution to the current problem. Here goes. I have the Samsung Galaxy Note I717M. This is the Canadian version to the AT&T Note I717 I have been rooting my phones for several years now and pretty familiar with the ongoings of the whole process. I rooted my phone via ODIN and put a custom rom onto my Note with no problems. Everything works great! Where I run into a problem is when I decided to go with the Jellybean update 4.2.2. The Jellybean rom I am using is called Jellybam version 7.8.0. ParanoidAndroid Ver. 3.15 quincyatt_jb-mr1_build-6. When I installed it everything seemed to work fine for the first couple of days. All of a sudden my phone started to freeze where everything was non functioning. This frozen state would last for about 15 seconds then my screen would go completely light blue for another 5 to 10 seconds then turn off and reboot. It doesnt do this with any 4.2.1 custom roms. Only with the 4.2.2 version. Does anyone have this similiar problem? Is there a fix for this? I love my custom 4.2.2 rom and dont want to go back to any other earlier Android OS and rom. Can someone shed some light as to what is happening and is there a proceedure that needs to be followed or done differently so that this doesn't continues to happen. Or yet again is the a know issue? Any insight to fixing this problem would be greatly appreciated! I await your helpfull tools and hints. Any help I will be happy with.
thanks Guys
Paul
This is a known issue on Kelly bean roms. Oddly, most people are having less reboots with the new 4.2.2 over the 4.1.2 .... The issue is the kernel. There is no source to build from yet. So ... There are issues.
I have had a lot of freezing and reboots on many of the jelly roms. I'll tell you that you rom, jellybam, is not supported on xda.
I'm am currently on the unofficial AOKP and having great luck. You may want to give it a go.
So after this 4.2.2 10.2 update on the Verizon Galaxy S4 which now changed the baseband version to I545VRUAME7 I can no longer access boot recovery to install the latest 4.2.2 10.2 CM Nightlies. That I have deduced from google search.
What I do not understand is why is CM NIghtlies still releasing newer and newer 10.2 nightlies for the Verizon Galaxy S4 if you can not boot into recovery yet.
I really hate the factory operating system. Facebook never works right and I can not even use my Smoothie King APP!!! It keeps force closing. Not to mention, the keyboard is extremely slow and buggy too.
Is there something I do not know?
Thanks
Because anybody who bypassed the bootloader under the old software version (MDK) still has a bypassed bootloader, and some of them want CM10.2. It's only the stock update that breaks the bootloader exploit, not Android 4.2.2 and above in general. You can still install new ROMs to the phone forever as long as you hacked it under MDK, and never put completely stock, unrooted ME7 on it for some reason.
Your question have been answered, but I don't know how you or anyone else is having issues with the stock ROM. Any apps force closing or going slow such as facebook are not the ROM's fault, its the app itself. So you are stuck with the factory ROM for now, and who knows how long. I have been on the stock ROM and it still runs fast enough for me and i've rooted every phone I've owned since the G1.
AsaSpades said:
Your question have been answered, but I don't know how you or anyone else is having issues with the stock ROM. Any apps force closing or going slow such as facebook are not the ROM's fault, its the app itself. So you are stuck with the factory ROM for now, and who knows how long. I have been on the stock ROM and it still runs fast enough for me and i've rooted every phone I've owned since the G1.
Click to expand...
Click to collapse
Had the same issue on the previous 10.1 stock rom. The CM Nightlies ROM fixed my problems and made the Galaxy S4 much faster.
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
xN1ghtShadoWx said:
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
Click to expand...
Click to collapse
First thing I would do is upgrade to jellybean stock. The kernel you have(4.0.3) is vulnerable to the superbrick bug, and rooting the phone from 4.1.2 is easier/safer. Once you do this, you almost never need to worry about this bug again, as the newer kernels are safe. From there use philz kernel to root the phone. Just follow the steps in that thread and match the kernel to the rom. Have a good read, but particularly the 2nd and 3rd posts. Then you need a "kitkat compatible" recovery to flash cm12. You can use the newer philz recovery from HERE. Just flash it then reboot straight back to recovery. Then flash cm12 and gapps etc as normal
Bootloader
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
xN1ghtShadoWx said:
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
Click to expand...
Click to collapse
Don't worry about that. That is just the kernel(not bootloader if thats what you thought). Yes it is fine to flash stock firmware if you need.