Camera won't work when I flash a rom - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Ok here is the deal. I had a camera focus issue with my original S3. Took it to the warranty center and they replaced it. Works great. I rooted then rom'd and it breaks the camera. Doesn't matter if 4.2 or 4.3 camera can't connect.
Flashed back to stock checked the camera works just fine. So I rooted the phone and didn't flash a rom. Camera works fine. I tried to fix permissions for the camera no difference when I flashed a rom.
This is very annoying. I really like having a rom'd phone but I need my camera.
Any suggestions I can try?

Well it seems that no one had any idea about this issue. I talked with a friend last night and he said flash TWRP to the newest. I did flash the newest TWRP and it fixed this issue. Camera works as advertised when I flashed a ROM

Rooted my husband's phone today and encountered this same problem. I flashed with CWR. Do you recommend going back to stock and flashing with TWR or just flashing to TWR without going back to stock?

bonespanda said:
Rooted my husband's phone today and encountered this same problem. I flashed with CWR. Do you recommend going back to stock and flashing with TWR or just flashing to TWR without going back to stock?
Click to expand...
Click to collapse
Make sure you are on the newest clockwork or the newest TWRP

sparker366 said:
Make sure you are on the newest clockwork or the newest TWRP
Click to expand...
Click to collapse
Thanks I'll try that ASAP.
On another note, I'm wondering if flashing the incorrect or out of date CM had anything to do with this. Hes currently on 4.1.2 so I flashed CM v 10.0.0. Any thoughts?
**This is what happens when you learn something, leave it for a couple of years and come back to it on a device that's not even yours**

Related

Why don't custom kernels work on CM10 for me? Did I root wrong?

I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!

[Q] Cannot flash roms anymore

I can no longer flash a new rom and boot up successfully. It goes through the entire flash process correctly, but then boots straight into CWM when i restart. I have tried to flashing back to stock via odin, then starting fresh, did a factory reset from standard recovery. I have flashed MANY times prior with no problems. The only way I can get it to boot is when I restore with Odin. Am I missing something? Any help would be greatly appreciated.
ed20910 said:
I can no longer flash a new rom and boot up successfully. It goes through the entire flash process correctly, but then boots straight into CWM when i restart. I have tried to flashing back to stock via odin, then starting fresh, did a factory reset from standard recovery. I have flashed MANY times prior with no problems. The only way I can get it to boot is when I restore with Odin. Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you try twrp cwm is a broken recovery and did you flash another carriers rom
Sent from my ADR6300 using Xparent Red Tapatalk 2
I tried TWRP and same issue. Boots straight into whatever recovery I have installed. I have never had a problem with CWM before. I was running Serenity 1.1, noticed my GPS wasn't working and reverted back to stock and did factory reset. Ever since, not able to flash. I had flashed a couple of the Sprint leak roms prior to Serenity with no issues.
ed20910 said:
I tried TWRP and same issue. Boots straight into whatever recovery I have installed. I have never had a problem with CWM before. I was running Serenity 1.1, noticed my GPS wasn't working and reverted back to stock and did factory reset. Ever since, not able to flash. I had flashed a couple of the Sprint leak roms prior to Serenity with no issues.
Click to expand...
Click to collapse
flash a stock rom using odin should unroot your phone giving you stock recovery again
amzi said:
flash a stock rom using odin should unroot your phone giving you stock recovery again
Click to expand...
Click to collapse
I don't want stock recovery. I want to be able to flash again. I tried using TWRP after fresh install but still have same issue. Either I boot straight into recovery after flashing rom, or it just sits on the SGS III logo. The only thing I can flash is back to stock either already rooted or plain stock. I am at a loss. I have been flashing with no problems since august and have no idea what the problem can be. I have even tried redownloading the roms.
ed20910 said:
I don't want stock recovery. I want to be able to flash again. I tried using TWRP after fresh install but still have same issue. Either I boot straight into recovery after flashing rom, or it just sits on the SGS III logo. The only thing I can flash is back to stock either already rooted or plain stock. I am at a loss. I have been flashing with no problems since august and have no idea what the problem can be. I have even tried redownloading the roms.
Click to expand...
Click to collapse
Well fortunately for you rooting the GS3 is very easy, so do as he says, Odin to stock, re-root and flash. If you are seriously at a loss because you don't want to go through the trouble to be able to flash and root again then I suggest searching forums for someone who might have the same problem.
That's the problem, after flashing back to stock, and re rooting, I have the problem. I cannot flash anything using CWM or TWRP anymore. I am currently rooted and stock. No recovery installed. Not sure what happened and why recoveries are not working. I don't mind flashing back to stock.
Grab a stock image from sammobile.com and try that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Evidently fifth time is a charm. Restored back to rooted stock, reinstalled apps, twrp and successfully made a back up and restored. Was able to flash Ariel. Not sure what the difference was but back up and running now. Thanks for all the suggestions.

[Q] No problems on CM, but when I try to flash different ROM says I'm not rooted.

Bought a Nexus 7 about a month ago, updated it to KitKat, rooted it and flashed the latest stable CM. No problems at all. Today I decided to try some other ROM's. Flashed one and the root access was acting funny so I flashed my CM recovery. Tried to flash Paranoid Android and can't even get that one to boot up. It's something to do with my root access, but I don't know what else to do. I've flashed different versions of SU and nothing is working. Everything is great as long as I stay on my CM backup but if I do anything involving updating SU or flashing a ROM it's screwed. Anybody got any ideas?
BeeBiteBoy said:
Bought a Nexus 7 about a month ago, updated it to KitKat, rooted it and flashed the latest stable CM. No problems at all. Today I decided to try some other ROM's. Flashed one and the root access was acting funny so I flashed my CM recovery. Tried to flash Paranoid Android and can't even get that one to boot up. It's something to do with my root access, but I don't know what else to do. I've flashed different versions of SU and nothing is working. Everything is great as long as I stay on my CM backup but if I do anything involving updating SU or flashing a ROM it's screwed. Anybody got any ideas?
Click to expand...
Click to collapse
I haven't flashed CM in a couple years, other than mods I stay on stock roms but I'm thinking your problem has something to do with the kernel you have with CM and maybe changes to the partitions if any. Personally... I would flash the factory image without flashing the userdata.img so you don't lose your data. Then you can try PA or whatever.

[Q] Wifi issue on all roms [sgh-i747m]

Ok so here is the deal: I rooted and flashed cwm touch. I flashed PAC man ROM 4.4.2 nightly and after installing like 15 or so apps from the play store, my WiFi stoops working. It won't pick up any access points (I know my WiFi router is fine). So after being fed up I do a factory reset/wipe and flash PAC man ROM 4.4.2 again, this time it works fine. Now I did a full wipe and flashed carbon ROM 4.4.2 nightly and same problem: WiFi works fine and after downloading many appsit spontaneously stoops working. Not wanting to loose all my settings I just did, I reflashed the ROM and wiped the dalvik cache and cache but WiFi still doesn't work. Please help thanks!
Maybe you need a different modem than the version you've been using?
audit13 said:
Maybe you need a different modem than the version you've been using?
Click to expand...
Click to collapse
Its weird I thought that may be the case but I think the modem should work fine with my hardware... And it was working flawlessly for over a month (after I flashed PAC man ROM the second time before I switched to Carbon)
drewstopher said:
Its weird I thought that may be the case but I think the modem should work fine with my hardware... And it was working flawlessly for over a month (after I flashed PAC man ROM the second time before I switched to Carbon)
Click to expand...
Click to collapse
I have seen posts where updating the bootloader required an updated modem. I suggested updating the modem in case you updated your bootloader. All this being said, it is weird that it just stopped working. Unfortunately, I don't what else to suggest other using a stock ROM for a while to see if the problem reappears.
audit13 said:
I have seen posts where updating the bootloader required an updated modem. I suggested updating the modem in case you updated your bootloader. All this being said, it is weird that it just stopped working. Unfortunately, I don't what else to suggest other using a stock ROM for a while to see if the problem reappears.
Click to expand...
Click to collapse
Thanks I just did a full wipe and flashed seems to be working fine now..... But still weird thanks for input!

Problem flashing custom rom

Backstory - I have been rooting and flashing custom roms for the last 5 years starting with my 1st HTC Evo. So I have a lot of experience.
But this is wearing me out. So I picked up at Note 4 this past Friday. I only got around to rooting it tonight (Hawaii time). (Which is also weird because all of my phones were rooted as soon as I got home. Note 3 rooted only 20 minutes after I left Sprint last year.) Any ways, I have the NK2 build. I rooted using the Chain Fire method and I flashed TWRP 2.8.3. Did a full wipe and tried to flash Bonsai the deodex version. TWRP kept rebooting every time I tried to flash the rom.
Does anybody have any ideas on what to do? I haven't tried flashing TWRP 2.8.1 yet though.
I wasn't even aware TWRP updated to to 2.8.3.0 but do see it now. I'm using openrecovery-twrp-2.8.1.1-trltespr.img downloaded from flashify.
BTW, I don't see a Bonsai NK2 ROM. Try a NK2 ROM. I'm running rooted stock NK2 so don't have a suggestion in regards to custom NK2 ROM.
http://forum.xda-developers.com/not...-nie-stockish-knox-root-sprint-stock-t2919346
Its wasnt labeled Bonsai. It is a NK2 friendly rom. Meh. I guess i still have to look around.
OK that's basically stock NK2 deodexed; didn't mean to steer you away from that. Bad download? Try again.
The weird thing is, i downloaded thru chrome on my laptop and i got a message after it downloaded saying it was a file that is not normally downloaded and asked if i wanted to discard it. Sigh. I hope i can get this on my phone. Thanks for the help
Have Wi-Fi connection available to your phone? Download to phone.
smh. I just noticed that I was trying to flash it off of my sd card. ARGH!!! Thanks for the help samep.

Categories

Resources