This has been fixed using the following methods in my original post, however I still cannot update the modem/firmware in any way, it seems. I fully give up on it, as nobody seems to have a conclusive 100% fix for AOSP ROMs. There are so many fixes on the internet, different ones work for different phones, at my wits end with it and not bothering with the increased signal. Not worth a broken camera.
(Original post)
Hi, I'm unrooting and rerooting due to the camera issue many people are having "failed to connect to the camera" when opening any camera app. I still never found a way to fix it on my phone and am rerooting in order to attempt to fix it now that CM10.1 is out. Can someone please check over this steps to make sure this is the correct way of doing this so I don't brick my phone or end up stuck with this camera issue again? Again, I have tried absolutely everything under the sun other than rerooting, methods on other forums, this forum, etc. Nothing works. Anyway, these are the two methods I will be following:
1
Following the steps from this site:
http://theunlockr.com/2013/04/10/how-to-unroot-the-samsung-galaxy-s-iii/
2
Following the steps from this page, including the optional:
http://forum.xda-developers.com/showthread.php?t=2332825
3
Download CM10.1 (CM official update on main site) and gapps 20130301 (http://goo.im/gapps, uppermost version).
4
Flash
5
Pray I have a working camera.
Are you running either MD3 or MF1 firmware?
Sent from my SCH-I535 using Tapatalk 4 Beta
thesoldier said:
Are you running either MD3 or MF1 firmware?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Flashed MD3 which caused the inital re-break (Forgot to post that I actually had this problem before, and fixed initially by going through the camera files and bringing the .bin files back from a TW ROM, onto my CM backup. Anyway, after breaking, I'm back on MB1 and still broken, the TW .bin file "trick" doesn't work anymore for me now.
What kernel are you running?
Sent from my SCH-I535 using Tapatalk 4 Beta
Did you even try the current firmware? MF1?
Get it here: http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
Flash in recovery and you should be good to go. If that doesn't fix it you may have to ODIN back to stock.
sbenson1226 said:
Did you even try the current firmware? MF1?
Get it here: http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
Flash in recovery and you should be good to go. If that doesn't fix it you may have to ODIN back to stock.
Click to expand...
Click to collapse
Isn't that what's causing the issue, MF1?
Or was MD3 the cause? I had MB1, it was fine, flashed MF1 and the latest CM10.1, and one of those caused the camera issue for me :/
Sent from my SCH-I535 using xda app-developers app
MF1 is the one you want. Download from the link I posted
Sent from my Nexus 7 using Tapatalk 4 Beta
XdrummerXboy said:
Isn't that what's causing the issue, MF1?
Or was MD3 the cause? I had MB1, it was fine, flashed MF1 and the latest CM10.1, and one of those caused the camera issue for me :/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
MF1 and MD3 are essentially the same and both would break the camera unless your kernel is updated to fix the problem.
Isn't the new Tz file the problem? I have MF1 firmware which broke my camera, so I flashed the MB1 Tz and now I'm all good.
Sent from my SCH-I535 using Tapatalk 4 Beta
sbenson1226 said:
MF1 is the one you want. Download from the link I posted
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried all of this already. All of his firmware downloads break it for me.
Sent from my SCH-I535 using Tapatalk 4 Beta
Yeah but what kernel are you running like I said before? You are in aosp they have a cm fix for camera, you can try lean kennel
Sent from my SCH-I535 using Tapatalk 4 Beta
Fixed it by flashing the MB1 AIO from the original updated post. Thank goodness! Haha
Sent from my SCH-I535 using xda app-developers app
It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Also. I currently have PA's latest build. How do I change the trigger area for PIE? I see in screenshots they are on the side. How can I do this? I hate swiping from the bottom since I'm used to doing that to launch Google.
Thanks in advance.
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
ImHereToSaveTheDay said:
It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Also. I currently have PA's latest build. How do I change the trigger area for PIE? I see in screenshots they are on the side. How can I do this? I hate swiping from the bottom since I'm used to doing that to launch Google.
Thanks in advance.
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
Click to expand...
Click to collapse
I got an error the first time I tried to flash the MIUI port in TWRP. Try rebooting the recovery after the error and flashing again. That worked for me.
As for PIE in PA, I don't know as I haven't used it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ImHereToSaveTheDay said:
It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Click to expand...
Click to collapse
Why about adding the error message? You may need to upgrade your bootloader.
Hi. I've updated my Nexus 5 via OTA yesterday. Everything was ok until I've made a video... Sound is awful and completely unaccteptable.. I've done a factory reset, but sound is still very bad.. Anyone noticed it in your N5 after update? Any ideas how to fix it?
Maybe try other kernel? I flashed kernel from Franco and i dont have this isue. I never tried on 4.4.2 or 4.4.3 with stock kernel.
Didn't noticed any change. Try reflashing.
Sent from my Nexus 5 using Tapatalk
Nope!not any issue!try reflash bro
Sent from my Nexus 5 using XDA Free mobile app
Hello to all this might be a dumb question but cut me some slack.*
I know it's not recommended to dirty flash cm12 I wanted to upgrade my phone to cm12 nightly from stock I am tired of waiting will it work or I got no chance?*
I have no patience reinstalling all my apps and backing up my photos and whatsapp
Sent from my A0001 using XDA Free mobile app
tzvblsm said:
Hello to all this might be a dumb question but cut me some slack.*
I know it's not recommended to dirty flash cm12 I wanted to upgrade my phone to cm12 nightly from stock I am tired of waiting will it work or I got no chance?*
I have no patience reinstalling all my apps and backing up my photos and whatsapp
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Are you talking about dirty flashing CM12 over CM11S? Nope, can't do that. You can only dirty flash when upgrading the same ROM (to a newer build).
Transmitted via Bacon
I have been a proud owner of my refurbished one plus one but until today I now want to throw my one in the trash. My problem i am having with my phone is actually a major issue that i just can't figure out and I was hoping someone could help me. The issue is that i can't open the side bar menu in any apps that use it such as google+ or the xda app. There is also an issue where in settings if i select wifi or any other section i can't go back using the back arrow at the top. The issue does get fixed by rebooting but issue happens again after an hour of phone being on. This is really strange and i have always had a good case on my phone and i haven't dropped it once btw if that matters. I hope someone can help me PS i am running Latest snapshot of CM12.1 Lollipop that is out right now.
Sent from my SM-T210R using Tapatalk
i don't know what happened or what u did so if u know things about android n roms just follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and restore your opo to stock will solve all these issues
Do this only if you know what u r doing and also have some knowledge about flashing and it's risks so just carefully follow the guide u will be fine and hopefully the problems will be solved
could be bad flash, clean(wipe everything) and fastbootflash back to pure stock
avoid twrp 2.8.7.0 and 2.8.7.05
Sent from my A0001 using Tapatalk
Startlinger said:
could be bad flash, clean(wipe everything) and fastbootflash back to pure stock
avoid twrp 2.8.7.0 and 2.8.7.05
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Flashed CM12.1 latest snapshot with a full wipe using twrp v2.8.6.0 now the problem is gone
Sent from my A0001 using Tapatalk