I recently flashed cm10.2.1 with twrp 2.6.3.4 and gapps-jb-20130813. When launching my camera I get this error(Camera Error, Can't connect to camera. Can anyone shed some light on how I can fix this issue?
Are you on jb firmware? Have you ever updated to kk firmware in the past? The firmware should match the rom. So if its a kk rom you need kk firmware, if its a jb rom you need jb firmware. Only thing i can think of, unless its just a known issue with the rom.
?
cmlusco said:
Are you on jb firmware? Have you ever updated to kk firmware in the past? The firmware should match the rom. So if its a kk rom you need kk firmware, if its a jb rom you need jb firmware. Only thing i can think of, unless its just a known issue with the rom.
Click to expand...
Click to collapse
Which kk gapps should I install and do i need to start over with a factor reset or will the previous version that i installed be obsolete after I install the correct version?
Related
Hello I would like to know how to update from 4.2.2 ( Liquid Smooth 2.9) to 4.4. Do I have to update to 4.3 with knox removed and then flash a 4.4 rom? Can I use Odin to flash a 4.3 rooted official rom directly from 4.2.2?
Sorry for my bad English
xXFl4sh said:
Hello I would like to know how to update from 4.2.2 ( Liquid Smooth 2.9) to 4.4. Do I have to update to 4.3 with knox removed and then flash a 4.4 rom? Can I use Odin to flash a 4.3 rooted official rom directly from 4.2.2?
Sorry for my bad English
Click to expand...
Click to collapse
You can just find a ROM you want to flash, read the installation instructions and flash away. If it requires you to update your bootloader, it'll tell you to do so. It might behoove you to read a few pages in the ROM thread, at least read the first and last two pages. Also pay attention to which version of cwm or twrp is recommended. Don't forget to do a nandroid in case something gets screwed up.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I have a really strange issue, I'm on KK with TWRP 2.7.0.0 installed. All KK based ROMs are working perfectly without any problems. But when I try to install TWRP for JB (Issue was also there when I was on B125 with this unlock code) or a JB based Custom ROM my phone vibrates all the time and I'm unable to do anything with it. My thoughts of this is that my phone is still kinda locked on JB but unlocked on KK, so for a completly working JB ROM I would have to downgrade to B118 or B120 right? But now I found a Custom ROM based on JB that works on my device its MIUI V5 by @greatslon ! And I'm wondering why this is working but all others don't, maybe anyone can help me a little bit :laugh:
I've been having this problems before and that is that no kitkat ROM's camera works in my t999 phone, I was in 4.1.1 bootloader before but upgraded to 4.3 bootloader using Mr Robinson's prerooted firmware but still when I installed any kitkat custom ROM, I still get the cannot connect to camera error. the camera works fine in the stock prerooted firmware. plz I really want to use these kitkat ROMs and also want to camera to be functional. any permanent solution will be appreciated.
i guese I can't go on with kitkat roms
dikachik1 said:
I've been having this problems before and that is that no kitkat ROM's camera works in my t999 phone, I was in 4.1.1 bootloader before but upgraded to 4.3 bootloader using Mr Robinson's prerooted firmware but still when I installed any kitkat custom ROM, I still get the cannot connect to camera error. the camera works fine in the stock prerooted firmware. plz I really want to use these kitkat ROMs and also want to camera to be functional. any permanent solution will be appreciated.
Click to expand...
Click to collapse
I guess am only left with the options of using only stock based t999 ROMs. I'll have to say bye bye to aoksp and cm ROMs.
Check the cm threads and ask there when you get up to 10 posts. A lot of people who might be familiar with it probably dont bother looking at anything but their roms thread.
Hello! I'm a bit of a noob when it comes to updating firmware and I've heard that it's really easy to brick your device if you screw it up so I want to ask some questions before I dive in.
From what i've gathered, this is the right place to get the latest firmware and flashing instructions. Do I need to flash the full firmware if I'm not planning on using a stock/Sense ROM? Would it matter either way?
I'm on CM 10.2 now and was thinking about checking out the latest CM 12 nightly or maybe one of the Lollipop GPE ROMs. I don't think I'll be going to a Sense ROM.
P.S. I've had this phone since August 2013 and have never updates the firmware.
JGress said:
Hello! I'm a bit of a noob when it comes to updating firmware and I've heard that it's really easy to brick your device if you screw it up so I want to ask some questions before I dive in.
From what i've gathered, this is the right place to get the latest firmware and flashing instructions. Do I need to flash the full firmware if I'm not planning on using a stock/Sense ROM? Would it matter either way?
I'm on CM 10.2 now and was thinking about checking out the latest CM 12 nightly or maybe one of the Lollipop GPE ROMs. I don't think I'll be going to a Sense ROM.
P.S. I've had this phone since August 2013 and have never updates the firmware.
Click to expand...
Click to collapse
HTC has not released a lollipop version of the stock ROM yet, so there is technically no "lollipop firmware" yet. With the most recent firmware which accompanied the 4.4.3 OTA version, you can still run a lollipop ROM but it seems like a lot of people experience errors with them. Maybe it has more to do with bugs in 5.0.x since lollipop has not been out that long yet rather than outdated firmware, i really don't know. But I am on the most recent firmware and had the now infamous "can't send more than 1 SMS per boot" problem, so I rolled back to stock after a week or two. Either way, you are very, very out of date with your firmware. The level of risk associated with updating it probably isn't as high as you have been lead to think. Just follow the commands in the thread you posted exactly. I have done it many times and my phone has never been bricked.
As for your question as to whether or not it matter if you are not using stock or Sense, yes it still does. AOSP ROMs like CM or GPE still are designed to work with the phone's firmware. CM11 or 12 is intended to work with whatever firmware is out by the time the ROM is being compiled.
Hey! I've been spending hours reverting my rom to stock and doing my OTAs to get to lollipop.
My phone is a Bell M8 with S-ON. I am currently up to 4.4.4 and about to do the Lollipop update. I am aware I should do sunshine on 4.4.3 but am broke right now so was just thinking of waiting until it works on Lollipop.
That being said, the current Bell OTA for Lollipop is version 4.20.666.1 (awesome numbers btw) and most roms say I need firmware 4.16.x.x.
My question is, will those roms work properly on this firmware? Or should I go back to 4.4.3 and use sunshine (I am impatient and want lollipop now, but stock roms suck.)
Thanks for the help!
edit: I found this advice in a rom thread
In future Rom releases, you may stick with your region’s firmware as long as that firmware is from the current released base, such as 5.0.1, 5.0.2, etc.
Firmware flashing is not required for every Rom update. Most of the time it is best to remain on your phone’s native firmware for best signal reception, battery life, and overall performance.
Click to expand...
Click to collapse
So does that mean as long as the rom is the same version 5.0.x that I should be fine?
Ya you should be fine tuning that firmware with the Rom... Can I ask you to also please upload the ota for us ...I've been looking for it all around
danial.aw said:
Ya you should be fine tuning that firmware with the Rom... Can I ask you to also please upload the ota for us ...I've been looking for it all around
Click to expand...
Click to collapse
Where do I find it I haven't update yet.. I'd you can tell me where it is located I can extract and upload it.
I have a TWRP backup of it. Would that work or probably not since the firmware isn't there.