yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] jeffreii:
Well you can at least be a little more hopeful for a root exploit than a bootloader exploit...despite the seemingly impossible bootloader situation on the AT&T MF3 S4, they were able to find a root method to replace motochopper fairly quickly.

However, I am not sure about the SELinux Enforcing status of the Note 3...haven't read about that yet.

Thanks for the info though. I'm definitely considering the T-Mo route...kind of waiting to see what kind of dev support it gets though. I'm also curious about the new Nexus and even this 6" flexible LG being announced this month...not really a rush to switch to the Note 3 for me considering waiting a few weeks might also drop the price significantly.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] mohan_kr:
Yup you are right..Believe me I want an ATT Note 3, but I am not very hopeful unfortunately..

Fortunately for MF3 (4.2.2 code base) they had permissive (SELinux), with Android 4.3 kernel with full blown SEAndroid support, samsung is releasing with SELinux enforcing, hence even if an exploit is found, it is going to be extremely difficult to get it executed.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] ozzman39:
http://www.engadget.com/2013/10/04/galaxy-note-3-kernel/
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Agent:
Grr..that's it..I'm moving to canadia <- pun intended
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] sinichi21:
Aw this is sad i just got note 3 today sigh at&t really sucks.. wish i can buy a tmo but its too expensive to get the phone only sigh so dissapointed
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] JVogler:
Yes, At&t is locked tight! I just paid over $700 to them and am having a hell of a time transferring over from my Note 2 without a proper root. I'm using Helium, but with only about 80% success.

-- Note II, TapaTalk II--
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] pterry30:
The Canadian note 3 is not bootloader locked. I have it rooted and recovery installed. I bought the Telus model. Also it is not region locked.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] DeathOfAllThings:
Guh, looks like my brand new att note 3 is going to the ebay... maybe I can get some money from that and buy a tmo version.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] SkipKelley:
I have a Note 8 LTE on AT&T with a locked book loader. We were able to get root, but it involved Odining (is that a word) back to the original software, then applying the PDA, then re-applying the other parts without the PDA.

http://xdaforums.com/showthread.php?t=2430540

Maybe ZeroxCorbin can shed some light on what he did. No rom flashing yet, but full root so TB works and SU.

I'm not at that level, but I'm sure someone can figure you what he did and maybe us it here.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Raiderman:
I have signed all of the petitions, and facebook stuff. It will not do any good, but I have also sent an email to at&t requesting an unlock for my boot loader. If you pay full price for the device, then you should be allowed to do with it as you wish. I told them if I did not receive an unlock, then I would opt out and go to T-mobile to purchase it. We shall see!
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] cpgeek:
While I wish you the absolute best of luck, I honestly don't think an unlocked bootloader has been written for this particular model of the hardware and I doubt they are going to spend hundreds of thousands of dollars for a handful of people who are like "give it now or i'll jump ship to tmo"... in this case, the best we can hope for is either an exploit or that the note4 be unlocked next year.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] tomthedancingbug:
listen

you will never get the bootloader unlocked for the att note 3

its just not going to happen, either third party or via att/samsung

if you want an unlocked bootloader note 3 go to any other carrier
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] aalupatti:
Never say never
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Jammol:
Okay Bieber!!!

Lol, designgears is working on the bootloader now.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] 1sagain:
Telus Canada

I also have a Canadian SM-N900W8 NOTE 3 and it is bootloader unlocked and NOT region locked. (Paid out right)
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] DirtyDroidX:
The only thing I can assure everyone is , ppl are looking into this, Safestrap is a possibility with some more time, finally no one can tell you 100% what the future holds.

Sent from my SAMSUNG-SM-N900A
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] benji667:
how are you ordering the canadian version? i was thinking of doing that but didnt know how..
[General Accessories] dude52:
I'm really looking desperately for a really good pair of earbuds for my phone. Because I listen to music everyday. I only have one pair of earbuds and its the ones that come with the HTC ONE X so does anyone know any good earbuds with REALLY good bass and clear highs mids lows for under $40 please please help
[General Accessories] vectron:
Under $40 you can definitely get headphones, but don't expect audiophile clarity. Those labeled as "super bass" will have muddy bass with high volume distortion across the whole dynamic range and probably filter with rolled off high frequency to make bass sound better (like beats $100+ stuff). Call me crazy, but I reviewed a few budget headphones and there was one I really liked for $9, my review is here: http://xdaforums.com/showthread.php?t=2435376 (ES900i model sounded actually pretty decent). Klipsch S4A II were not bad either, stronger bass and relatively clear across the whole frequency range, and those you can get on amazon for a little over $50.
[General Accessories] jRi0T68:
Sony MH1C or Brainwavz R1, both always reviewed as superb for their price.

Also, see the guide in my sig.

-No longer accidental, just Jeremy. F.cfb

[Guide] Headphone/Earphone Buying
[Sony Xperia ZL] jordiang:
Hi everyone,

Im new to rooting so dont shame me here, be nice :)

I followed the steps by DoomLord to root my ZL, downloaded the ADB drivers properly (when tested, it shows my model number),

also flashed .423 kernel as instructed

http://xdaforums.com/showthread.php?t=2458268

Everything went well until i tried the 1 click DoomLord root and i got this error as attached.

When i checked after that using rooter checker, my phone is not rooted.

Can someone help me? Thanks :)
[Sony Xperia ZL] martin132014:
In there the phone detected that your phone is on 2.67....are you sure that you flash. 423 correctly...?
[Sony Xperia ZL] iggut:
YEp. Looks like there was an issue with the step that tells you to flash the .423 kernel ftf.

Try re-downloading that ftf file and flashing it again (then set USB debugging & Unknown sources to ON) and run the DoomLoRD Rooting Kit v18 again.

I had the same error and ends up I flashed the other kernel ftf file by accident.
[Nexus 7 (2013) Q&A] Ektronik:
Hello, my name is Jon. I've got a serious problem with my Nexus 7..

So.... I've had my Nexus 7 for about a month and a half and I decided to root it.

Everything was going good. I got it unlocked, loaded a new recovery mode ( Clockwork 6.0.0.6.), and put super user on it.

I loaded up Clockwork and was looking around in it and I accidentally wiped ALL OF THE DATA OFF... That included the operating system..

Now.... When I try to boot up it stays at the GOOGLE SPLASH SCREEN and won't move past that, unless I go to Fastboot or Recovery Mode..

I can't load data on to it due to there not being an sd card slot and my computer won't recognize it enough to allow me to put data on to it.

It recognizes it as "ANDROID ADB INTERFACE" and says it's working properly.

IT WON'T LET ME FORMAT IT OR FACTORY RESET IT DUE TO IT NOT BEING ABLE TO MOUNT THE SD CARD...

I've tried about everything I can think of...

PLEASE HELP!!!! I've had this tablet for for a month and a half and I am definitely not about to let it die.

It's ANROID 4.3 (JWR66Y) Wifi tablet- Running Clockwork 6.0.0.6 recovery :confused:
[Nexus 7 (2013) Q&A] meekrawb:
It looks like JWR66Y is for the Nexus 7(2012). Is that what you have?

This is the Nexus 7(2013) forum.
[Nexus 7 (2013) Q&A] Crwolv:
Yikes!! :( like meek said, basically tell us which tablet it is and a ton of us can help.
[Nexus 7 (2013) Q&A] bass0324:
Simplest way I know to fix this is download any rom you wish to install with gapps to your computer (not sure if stock requires you to flash them too since I never ran stock on my nexus devices :)). Next download and install the android adk to get adb running. If you are on Windows, located the platform-tools folder in the sdk and press shift and right click on it and select open command window hear. Type .\adb devices to be sure you can recognize your device and then use .\adb push command to transfer your files from the computer to your tablet while in recovery mode
[Nexus 7 (2013) Q&A] goofball2k:
You'll need to download the appropriate rom for your device, and use ADB/Fastboot to push to your nexus.

One thing I

always

do is before I touch anything in TWRP (same idea as CWM) is to make a complete backup of my device before I do any wiping. Granted, if you wiped internal storage as well, this wouldn't help but it would help if you just did a factory reset without wiping internal storage completely.

See if you can do these steps.

http://wiki.cyanogenmod.org/w/Install_CM_for_grouper

You'll want the section Installing CyanogenMod from recovery
[Nexus 7 (2013) Q&A] meekrawb:
Whichever Nexus you have, you should download the factory image from here

https://developers.google.com/android/nexus/images

Only download the one for your device or you may hard brick it.

Let us know definitively which device you have so we can help you better.
[Nexus 7 (2013) Q&A] madder_addict:
hard-brick

I have made that mistake. I have nexus 7 (2012) . When it's stuck at nexus logo or bootloop, i always download the right files and flash them. Then it works great but the last time :rolleyes:

I flashed nexus 7 (2013) files to nexus 7 (2012) by mistake. Now it doesn't open and stuck at Google Logo. Can't get in recovery mod and my computer doesn't recognize it. How can i solve this :confused:
[Nexus 7 (2013) Q&A] jova33:
Does adb recognize it?
[Nexus 7 (2013) Q&A] madder_addict:
Nope. This is the main problem and i couldn't do anything.
[Nexus 7 (2013) Q&A] maully217:
soft bricked

hi, im presuming you can still access the recovery screen on your nexus7 :) even though its stuck looking for the operating system that you have wiped.:crying:

if so then try wugfresh nexus root toolkit as im sure it will flash original android operating system on it even though it is soft bricked.:fingers-crossed:
[Nexus 7 (2013) Q&A] Nbsss:
You should be able to get to fastboot mode and then use factory images
[G2 General] xdabbeb:
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.

If you don't know how to launch an activity, you can do the following:

Via ADB:

adb shell "am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences"

Via Terminal on your phone:

am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences

I haven't done any more checking, but I'm guessing this is just a flag that could be set in sys/devices/blah... by init.d script on boot as well.

If you prefer a gui, there are plenty of launchers out there that can select an activity to start. I actually had it set up as a long-press pie on LMT while I was playing with it.

It seems (on my phone, at least), that the app wasn't as good at turning it back on, but you can just clear the app data/cache on "Content Adaptive Backlight Settings" in application manager, reboot, and you'll be back to stock behavior.

Sorry I didn't post this sooner. I've been too busy playing with the G2!
[G2 General] jayochs:
this doesn't work.

I've tried this weeks ago. simply telling the app to turn it off does nothing, as it's still on no matter what. deleting the app produces the same exact effect.

in the build prop, the line pointing to cabl is set to false. therefore it's really not even reading what the app is saying it seems.

I believe it's a kernel issue that can only be solved once we get a custom one.

again, this isn't a fix and doesn't turn it off at all sadly.

https://www.youtube.com/watch?v=slwkFhpiYbs&feature=youtube_gdata_player this video was made when it was set unchecked and set to off.
[G2 General] xdabbeb:
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
[G2 General] SysAdmNj:
Is this issue on all carrier versions?

I use auto-brightness and the annoyance I have is that it doesn't change brightness right away when entering different lighting environments. It either takes time or doesn't change at all until I uncheck/check the auto-brightness setting.
[G2 General] jayochs:
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
[G2 General] xdabbeb:
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
[G2 General] whittikins:
I believe the original Nexus 7 had this feature in the kernel too. However, in custom kernels you could use Trickster mod to toggle the feature off. I think the kernel devs had to expose the setting though, so maybe we'll get this taken care of if we can get a custom kernel.
[G2 General] Scott:
Here are some build props for Qualcom devices that control the CABL

ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1

By adding / editing these lines in the build.prop you should be able to adjust as noted in the lines.

And yes, it is in the kernel.

Dont know why LG has an app for it?
[G2 General] jayochs:
Scott, I sent you a message on hangouts but in my build prop, i don't show a 1 for the cabl setting.. i show false... as if it's already turned off in the build prop. I changed it to true once and it didn't do anything. those two top settings seem to be what's in the app.. you can check a box to turn it on and off (the first line) and then you can set the degree to which it handles the cabl (second line.) I've messed with both in the app and it did absolutely nothing... does the kernel need to be changed as well?
[G2 General] Noam23:
I'm not sure you really want to "fix" this feature.

LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
[G2 General] jayochs:
we do want to bc it causes horrible screen flicker issues. you can be sitting on a pic and it doesn't know what to do so it flickers badly
[G2 General] Scott:
I did not know about the contrast ratio on these screens. Makes sense what you are saying.

However like Jay said it does not react smoothly or at appropriate times.

Some will need to edit the kernel code to fix this.
[G2 General] xdabbeb:
Yep. What [MENTION=2770600]jayochs[/MENTION] and [MENTION=426561]scrosler[/MENTION] said. What you wrote does make sense, and I had noticed that it behaves the opposite of the CAB implementation on AMOLED screens (where it dims on lighter colored content)...so that gives even more credence to what you're saying, but the implementation is a little buggy. It transitions abruptly and causes the "flickering" that many have reported. I certainly wouldn't mind having it enabled if the transitions were slower/less frequent, but it's kind of annoying as it is. I never was able to find a way to disable it in the stock kernel anyway, so hopefully it can be fixed one way or another now that the source is available. Still the best phone I've owned!
[G2 General] SysAdmNj:
So any success with any method here or elsewhere?
[G2 General] antinorm:
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.

This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
[G2 General] jayochs:
i'm thinking it's CABL, but it's kernel level, NOT software level, which is why disabling it does absolutely nothing.
[G2 General] Rayan:
I've been using Lux Auto Brightness to fix the issue.

Cheers!
[G2 General] jayochs:
it's not an issue with auto brightness, that's a completely different problem.

this is the content adaptive backlight problem.
[G2 General] mannequin:
so no solution was ever found for this (besides a new kernel)? my phone doesn't flicker but on the brightness below 50% i can notice it's trying to readjust itself slightly once in awhile (with xda app or play store for example).
[G2 General] UnskilledOne:
Encountered this issue as well. So, the cause of this has something to do with the software and not the hardware? Don't want to send my phone back just to receive yet another problematic set.. I set my screen brightness to 38 which it flickers on certain photos and apps. Bumped it up to about 45 and it seems to have stopped.
[G2 General] Infinite Jest:
Are you referring to the behavior when you scroll through a webpage and the brightness adapts and flickers depending on the color content currently being displayed?
[G2 General] jayochs:
yes content adaptive brightness works to make blacks look blacker since it's an LCD. they want to make it as close to amoled blacks as they can, therefore it changes the brightness in a way we can't adjust whatsoever. it has to be kernel as there's no software fix and it's not a hardware thing. nobody has made a single verizon kernel though, and i wonder why.. did LG never release source or something?
[G2 General] AllTheWay:
I use an app called screen filter and it does seem to help. Though it could just be a placebo effect. I will test it out for a few more days and see if the issue comes back.
[G2 General] jayochs:
screen filter does sort of help because it's like placing a semi transparent image over the screen to drop brightness.. but it drops contrast too so it doesn't look too good. it still does it but you don't notice it as much.
[G2 General] coolbeer1990:
Any update guys ?
[G2 General] Cookie&Cream:
Hi guys, I am also a G2 user and I doubt it is an hardware fault because at first I thought it was so I went to service centre and had my LCD change but problem still exist with brightness below 50%, above %50 I dont really see flickering except exiting an app. Hope LG can fix this bug with a new kernel version or android 4.4 update.
[G2 General] ndnesh:
Hmmmm don't see this on mine. I am always at around 30 to 40 brightness. Will monitor more and report.
[G2 General] atacante:
Is there news about the flicker? i have in my G2 too :( if i change the firmware will again?

edit

problem solved with 10G ROM !!! (189 6EE/T-MOBILE(UNITED KINGDOM))﻿
[G2 General] ndnesh:
I think all these will be resolved in KITKAT ROMs
[G2 General] leechseed:
Couldbanybody answer this? Thanks
[G2 General] jayochs:
and you know this, how?
[G2 General] gunnyman:
Because auto brightness works now. I uninstalled lux because LG fixed it in kitkat.
[G2 General] DenisJ:
I also install kitkat on my VS980 (Verizon) ...cause I have this problem:

The light dim until 40-50% ... then from 50% til 100% stil remain unchanged, and the light on my phone is very low

Anybody still have this problem please ?

Thanks in advance

Denis
[G2 General] Jockson:
So has this issue been fixed in latest roms? Thinking of getting this phone but this issue doesn't look like something I could live with.
[G2 General] buenarc:
Download uget. Use it for all downloads over 1gb.
[G2 General] mannequin:
it was fixed in the 1st official JB update.
[G2 General] buenarc:
did not know about the contrast ratio on these screens. Makes sense what you are saying.:)
[G2 General] Jockson:
Are you sure? Because some people are saying content adaptive brightness is still there and cannot be disabled. My TV has the same thing forced in certain picture modes and it looks awful.
[G2 General] mannequin:
yes, at least for T-mo D801 variant, the 1st update completely fixed this issue.
[G2 General] Jockson:
OK thanks. By "fixed", do you mean LG actually disabled content adaptive backlight or they made the changes appear more gradual and smooth? I'd really like to completely disable any kind of contrast "enhancement" features.
[G2 General] edani:
Screen flicker

No solution to the problem of screen flicker. Own a g2 lg d805 chile

1 -. Kitkat install brasil - no problem solved

2 -. Cloudyflex 2.2 install and kernel dorimanx - no problem solved

even follow the screen flicker

help
[G2 General] Maidenx:
Same here =(
[G2 General] edani:
Mi phone in twrp = screen flicker

Enviado desde mi LG-D805 mediante Tapatalk
[G2 General] RobinOtten:
delete doh
[G2 General] edani:
backligth

test... not solve the problem... another idea?
[G2 General] krogoth:
This is dynamic contrast, You cant disable it without kernel modification.
[G2 General] edani:
solution

temporary solution.

with AOSP roms ... no flashing screen instal cyanogenmod or paranoid, etc.

before the end of the warranty, flash the normal rom and back to the technical service, **** lg g2.
[G2 General] edani:
no solve

UPDATE..

AOSP rom no solution the bug... Slds

Fast.. SAP
[G2 General] Okazar:
Just updated to KitKat on the Rogers phone D803

Still flickering. I'm trying to ignore the problem in order to keep the phone but my OCD complex says otherwise. I bought the phone on Sunday... I guess im going to exchange it for the M8 as sad as that sounds.

Cant really hold off till the G3 and personally don't want to.... not with browsing battery stats like that! (due to higher resolution)

Im more than pleased with my Optimus G E97x... but i had to change my plan and thus $0 phone (G2) was it's result.