Warning - camera failed

I suddenly started getting the error "Warning Camera failed" when i attempt to use the back camera on my rooted s6 edge running stock touchwiz. The front camera i working fine.

I tried wiping my phone and installing a custom rom, but the error kept occuring.

Is there anything else software-wise i can do to attempt to fix this, or is this perhaps a physical problem?

- Thank you!

Warning: record failed in all lollipop custom ROMs

Hello

so I've been moving between ROMs a lot ,,, in all lollipop TW ROMs I can't record videos at all even with snapchat
but on MIUI KK or on official KK ROMs and on CM12 and AOSP LL ROMs I've no problem at all...

how can I fix that? I tried Full Wipe and changing between ROMs but still the same issue shows !

Warning: CM11 and 12 don't work with the latest versions of TWRP and Philz touch

The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note...2972922/page32, I got it working.

The long story:

I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.

Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.

Hopefully this post will help someone down the road.

[Guide] Disable Hotspot warning popup (5.0.2)

What does this mod do?
This mod disables the popup that warns about disabling wifi when you enable the Hotspot feature from the Notification panel quicksetting toggle. The popup normally only occurs when wifi is enabled, so this will prevent that popup.
This does not disable the warning if you enable hotspot from the Settings menu.


What app needs modifying?
SecSettings2.apk - must be deodexed app because we will be editing smali code.


The mod:

1. Decompile your deodexed SecSettings2.apk


2. Open smali\com\android\settings\wifi\mobileap\WifiApWar ning.smali with a text editor


3. Search for
   
   
   

   Code:

   
   

   ---

   .local v1, "wifiState":I

   ---

   
   


4. Enter the following code on a new line just below that line
   
   
   

   Code:

   
   

   ---

   goto :cond_5

   ---

   
   


5. Save and recompile.

How does this mod work?
When the hotspot is enabled, a check is performed to see if wifi is enabled, and if it is, a popup message is displayed to warn the user that wifi will be disabled while the hotspot is enabled.
By inserting the "goto :cond_5", the comparision checks of "wifiState" are skipped, so the warning does not get created.


Tips:
If you have trouble recompiling the resources after making the mod:

• The classes.dex normally get compiled before the resources


• Simply find the newly compiled classes.dex in the output folder and copy it back into the old deodexed app (7zip).

Help! Cannot boot past bootloader unlock warning.

I unlocked and rooted my device. Everything was working fine until I rebooted the device. The device would boot up, but after the Motorola start animation I had a blank screen. I tried using the return to stock tool, but the results were the same. So I booted into recovery and wiped everything, then booted into the the bootloader, and tried the restore to stock tool again. Now I cannot get past the unlocked bootloader warning? Can anyone help me with this? Thanks

How to Remove Unlocked Bootloader Warning

Now that we have root there must be an easy way to remove the unlocked bootloader warning. Anybody know?

Warning to all those tethering with root.

So, today I woke up to a lovely text from T-Mobile warning that I have concealed tether usage data. The transcript of the text follows:

Quote:

Originally Posted by T-Mobile The plan for line XXXXXXXXXX on your account includes unlimited 4G LTE data on-smartphone only. It also comes with up to 7GB of 4G LTE data for Smartphone Mobile HotSpot to share your phone's internet with other devices. T-Mobile's systems have detected that this line has actively used methods that conceal Smartphone Mobile Hotspot usage and, as a result, significantly exceeded the 7GB limit on its plan. This activity violates our Terms and Conditions. To enforce our Terms and Conditions and protect the network experience for all our customers, continued violation will result in the line being ineligible for its current plan and moving to our 1GB limited 4G LTE plan. Details at http://t-mo.co/1J4PTjw

Regarding my tethering usage, I've only used a good 2GB extra than the mobile Hotspot allows. So, their idea of significantly exceeded seems pretty strict. So, even if you don't think you fall into the "percentile" of that one person using 2TB, to T-Mobile, you do. I'd still like to see them try to move me down to a lower plan though. I'll just leave and go to something like sprint.

So, I recommend being extremely careful. I have no idea how they detected it, but they are.

Warning: New AT&T Note 4's may ship with Lollipop OC5

Reposting this from another thread:

Quote:

Originally Posted by harrypalmz (Post 62569411) Just received 2 shiney AT&T Note 4's on 8/26 as an upgrade. Unfortunately BOTH are on Lollipop 5.01, build C5...which from what I've been reading means it can't be rolled back to 4.4...so this method of achieving/maintaing root probably won't work.

This is a bad thing for people who like to tweak because (based on my reading) OC5 cannot be rolled back to KitKat, and cannot be rooted at this time.

I also have a new Note 4 on order, so I will post which firmware version it has when I get it.

If anyone else has received a new AT&T Note 4 recently, which firmware version did it come with?

Warning: New AT&T Note 4's may ship with Lollipop OC5

Reposting this from another thread:

Quote:

Originally Posted by harrypalmz (Post 62569411) Just received 2 shiney AT&T Note 4's on 8/26 as an upgrade. Unfortunately BOTH are on Lollipop 5.01, build C5...which from what I've been reading means it can't be rolled back to 4.4...so this method of achieving/maintaing root probably won't work.

This is a bad thing for people who like to tweak because (based on my reading) OC5 cannot be rolled back to KitKat, and cannot be rooted at this time.

I also have a new Note 4 on order, so I will post which firmware version it has when I get it.

If anyone else has received a new AT&T Note 4 recently, which firmware version did it come with?

Warning message?

Hi , I just flash the ROM Arab Emirates h815p 10g via Flashtool 2014 to remove all of the operator clarochile and I get a warning message each time you start cell , yet still apk light but startup logos left , ringtones and wallperpers .
I present my model is h815p Claro Chile .
They know that means and how is eliminated.
Rom Apparently all goes well it works .

Attached Thumbnails