Showing posts with label possibly. Show all posts
Showing posts with label possibly. Show all posts

Friday, 16 October 2015

Camera does not focus correctly - possibly software?



I have an SM-N910T flashed with Rapture 8.2 running 5.1.1 on baseband COG2.

I've been having trouble with the camera ever since I flashed any custom rom. Sometimes the stock camera fails to open and remains black and spits out "camera failed."
Sometimes it opens with a big delay and is unable to focus to anything. The only temporary fix is clearing the camera cache, and trying again. Even so It's impossible to take a photo without exiting several times.

I have noticed that whenever I boot my phone, I have a "Kernel is not seandroid enforcing" message that pops on the top left corner.

Could it possibly be that I have the wrong kernel interfering with the camera? I've booted in safemode and the issue persists.


Anyone experiencing something similar? I hope it's not hardware related.



Thursday, 15 October 2015

S6 edge + possibly bricked



Friend was messing with her S6 edge + and i was attempting to fix it for her. its getting keanel is not seandroid enforcing and custom binary blocked by fap lock. I can get into download mode but that is about it. Anything to get the phone working so its not a complete waste will work.



Sunday, 4 October 2015

Help with possibly hard-bricked LG G4.



So I have an AT&T G4 and I was attempting to root it, something went wrong, when I completed the rooting process I unplugged my phone and got an Authentication fail #11. So I decided I would flash the H810PR ZDK on to the phone hoping I could fix it using this guide (http://forum.xda-developers.com/g4/g...k-kdz-t3107848) after I completed that I got nothing..... black screen. Now it wont turn on and when I plug it in hear a failed driver sound and this shows up http://imgur.com/EGgdiYL . I've read like two success stoires of people with my problem actually getting AT&T to replace their phone with my problem under warranty, what can I do? :confused:



Saturday, 3 October 2015

Samsung S4 i9500 stuck on (possibly?) a bootloop.



I recently installed a root onto my S4 as well as Cyanogen Mod 12 (or 12.1). My battery has been draining quickly and I read that I just had to wait a few days. Still the battery just melted away like butter. So people (I believe on this very forum) advise to factory reset. I backed up and factory reset. When I did so, the Samsung logo appears, then the screen becomes grey, then black, then grey perpetually. I tried holding power, volume, and home, but they just make the Samsung logo appear again and it goes back to the loop of black and grey. This is the first time I seek help from this forum, so I'm sorry if this is the wrong place to post.



Tuesday, 29 September 2015

Help needed to possibly fix wifi issue



I have an LG G2 D801 which was rooted and running custom rom CloudyG2 2.2(KitKat), I tried to ugrade to CloudyG2 3.3(Lollipop) but may have messed up somewhere and ever since my Wifi and Bluetooth's MAC address has been unavailable. I've been reading around and people are saying it's a hardware issue so it won't be fixed unless a new motherboard has been replaced but i've come across a thread saying the 'bcmdhb.ko' file may need replacing. It's located in System>lib>modules but i realized it's not there. I'm hoping someone could upload or mail me the file so i can try my luck or hell even give a possible fix. Thanks in advance. Currently back on CloudyG2 2.2