yashsingh1/xdaforums huggingface dataset:
[G2 General] gull_s_777:
Using totally stock room. No root/flash/debloating etc.... I am no advance user. :)

Auto Sync is off and wifi is always on and connected.

Using Lux for Auto Brightness.

Here are my recent stats

http://xdaforums.com/showpost.php?p=50611123&postcount=379

Played Hungry Shark for hours and still got 7h+ screen on. Remove it and it might have gone to 9h+ screen on. :D
[G2 General] dalbig:
So, got the att ota update. Love it! Only downfall is that you can't choose between dalvik or ART.
[G2 General] :
thats pretty nice i got almost 4hrs so far on about 40% used.they did a good job
[G2 General] m0biusace:
I used LG Flash tool to flash 10o. Then live chatted with AT&T and a very helpful rep pushed the q and c updates. The whole process took less than 20 minutes.
[G2 General] heynando:
but you were under at&t's radio-spectrum coverage (connected to their network) and you were also using their SIMcard right? Asking this just so that we are at the same page :D
[G2 General] m0biusace:
correct
[G2 General] mat7bit:
Guys I don't understanding one thing: I've a fully-stock d802 and I'm expecting the kk ota for the next 7 days.. I haven't rooted My device, waiting for this update.. but read this thread make me confused: should I root before update my g2?
[G2 General] Darmstadtium:
Bro

ok, i am guessing here..are you asking whether one should root before taking the OTA, cos there is no rooting method available as of now for 4.4.2 Lg G2 ?
[G2 General] gharris040604:
Do you have the q update yet?
[G2 General] mat7bit:
Mmm yes my question can be interpreted like that.. :D

But can also be read as: if I root I'll get the ota? And root will survive to the update? :D

No I've the 10e update.. But I'm not sure that the d802 version has got an higher update
[G2 General] tonynmisty:
Just to clarify, I'm on a Straight Talk SIM and when I called ATT, they still pushed 10q for me, all they needed was my phone number.
[G2 General] bova80:
battery life seems vastly improved
[G2 General] muppetmaster916:
This is getting really repetitive lol, the method to update is very clear, it's stated about 100000 times in the past 5pages
[G2 General] AndroidUser00110001:
Sorry I did not get you the file yet. I have not updated again yet. When I try to update I get phone is not registered and have been on phone with AT&T too. Yes...SIM card in and have service.
[G2 General] Mangtas_666:
Ohh thankz for the info
[G2 General] maddy1439:
help

brothers someone plz help me ,,i m noob in android,,few days back i buy lg g2 D802 in india,and my region is hyderabad,,i just want to know what's mean AT&T lg g2,VERZION lg g2,T-MOBILE lg g2 ,and D802 ,mine is D802 ,,is it different from AT&T and other,,some one plzz clarify my doubt,help will be appriciated
[G2 General] freebee269:
D802 is international version. At&t Verizon t-mobile are u.s. carriers so they have different model numbers. So yes you have a different one than the one they are talking about in this thread. So this thread will not help you.

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

You have a d802. This thread will not help you since it's only for the at&t version d800.
[G2 General] vween:
You cannot get the Kit Kat update if you are rooted. It will download, reboot, start the flash process and then error out. You will then get the message popup explaining that your device is suspected of rooting and there's not update for a rooted device.
[G2 General] maddy1439:
thanks for reply

thanks for reply
[G2 General] vween:
You can't use the LG Backup service to save everything?
[G2 General] dxwilliams40:
I was able to keep root and update to kit Kat. Checked survival in supersu pro. Root survived both updates.
[G2 General] vween:
Oh that's cool. I tried using temp unroot and survive OTA (or whatever it's called) in SuperSu (non pro) and it didn't let me update.

Glad to hear you were able to keep root and update.
[G2 General] MIOMOOVUSER:
Can you post/message me the number that you called? I'm on Straight Talk but am having issues getting a hold of a customer rep.
[G2 General] tonynmisty:
I actually have a Moto X that has AT&T service, which is what I used to call. I was having trouble getting a hold of them too, so I called 611 from my Moto X and got them with no problem. If you know anyone who has AT&T service, ask to borrow their phone, it takes less than 10 minutes.
[G2 General] yomero911:
The problem is for the people outside USA, we had att g2 .. but not att service ... how can we update? .. still waiting for flashable zip ...

:( :(
[G2 General] MoDat:
Grr. I spoke to 4 different Att reps and each one told me they cant push updates through
[G2 General] garyd9:
Message posted to the LG opensource site:

I expect the response to be something similar to "we'll do it eventually." (When I requested D80010o, it took them about 3 weeks to post the source.)
[G2 General] SuperSport:
Any way of getting on ATT Chat Support? Maybe it's not the SIM/Service, but the fact that ATT needs to send it.

---------- Post added at 08:37 AM ---------- Previous post was at 08:31 AM ----------

No stress, thank you for remembering though. As far as the Phone Not Registered issue. [MENTION=5182870]podagee[/MENTION] has listed a fix for that here: http://xdaforums.com/showpost.php?p=50596752&postcount=2316

Also, this goes out to EVERYONE. If anyone can grab the dlpgkfile for update q and send it to me, I would REALLY appreciate it. I'm waiting for that file so I can create an installer for everyone to update to KitKat without asking ATT to push it.

When you get the q update, the file will be sitting in /cache/fota. It's about 15MB. You will need to be rooted to grab it, and I'm not sure yet how to do that because the phone reboots quickly. Maybe shut down and ADB in to get it??? I don't really know...
[G2 General] MoDat:
Who did you guys speak to get this updated pushed to your phones. I've now live chatted 5 times, spoken to 5 different people, including a supervisor and they keep telling me that they have no way of pushing out updates to the phone
[G2 General] SuperSport:
"They" are lying, or don't know how, but I'm guessing lying.
[G2 General] streetsmart999:
Sorry bro... its just bad luck for you I guess.
[G2 General] redpirate8:
I'm seeing a lot of confusing info regarding root surviving. For some, the root survives OTA's. For others, the system detects root and won't update. This is just a theory, but I'm guessing that it depends how much of the system was modified. Maybe re-enable all frozen apps in Titanium and uninstall all mods including Xsposed and System Tuner that we use to freeze Carrier IQ
[G2 General] bigfau:
I believe if you return to stock then root and call AT&T and have them push the 10q update you will keep root. After they push 10q and you verify root still exists have them push D80020c Kit-Kat to phone.Baaammm! rooted Kit-Kat.
[G2 General] SuperSport:
Exactly. This is a large update, I highly recommend backing up your phone, restoring back to Stock, Root, and go from there. I've done it a few times, and Root holds every time.
[G2 General] tonynmisty:
This is what I did, except the 20c was available OTA after AT&T pushed the 10q update. I tried undoing every modification I had done, but it still detected root. I had no other option but to return to stock and re-root.
[G2 General] SuperSport:
Now, just a thought. Each time I've had ATT push the updates, they pushed BOTH 10Q and 20C. I wonder if them PUSHING 20C is what makes the difference? Maybe that bypasses the Root Check??? Just thinking out loud.

---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------

Did you return back to stock by flashing the TOT using LG Flash Tool? I return back to stock 10o, root that, then ask them to push 10q and 20c.
[G2 General] sniffs:
I have my line on an enterprise business account and I even chatted with their Enterprise Support and they didn't know how either. They had me call 800-331-0500 and when I did, I was put on hold for a "technical support person" who then told me to call LG.
[G2 General] dxwilliams40:
My steps exactly.
[G2 General] bigfau:
That's my thinking also. I have had them push both updates at least 4 times. Each time I still had root. Maybe I should try it again and not have them push the 20c update, to see if I lose root. Or someone who keeps losing root should have them both pushed to their phone to test our theory.
[G2 General] Makman20:
What number did u dial and how did you get through to a att rep? This stupid automated crap is annoying.
[G2 General] Clark Joseph Kent:
I did mine thru the AT&T Chat via online AT&T site.....no need to call...
[G2 General] maorosh:
now its rolling out to israel via 'Ronlight'

they choice some tester's before 2 week ago

and it will be rolling to every one soon
[G2 General] SuperSport:
If you do, can you do a BIG favor and grab the dlpkgfile of 10q? That would alleviate all of these issues...

OR, does anyone know how I can grab it from MY phone on the next update? The phone reboots really fast. Can I shut down before it installs, then go into download mode, or some other mode and adb it out? I don't really know. :confused:
[G2 General] Makman20:
Im not an at@t customer and they require you to logon. Thanks but I guess I'll just have to wait.
[G2 General] JackpotClavin:
Hello, ever since the Korean F320 4.4 kernel source dropped, I've been trying to get it booting on my Verizon G2, which is still on 4.2.2 (officially). It appears that the new boot images have a device tree appended to them, and don't use a separately-generated dtb blob that gets thrown into the boot.img.

I think that the differences between the 4.2 bootloaders and the 4.4 bootloaders is that the 4.4 support the appended zImage-dtb; while the 4.2 ones do not. After disassembling your pulled boot.img from a thread, I saw that the 4.4 zImage is 9.4MB, and the zImages for 4.2 are around 7.7MB which are significantly less. I also examined the 4.4 zImage with a hex-editor and found that the stuff at the end of the 9.4MB zImage is consistent with the appended device tree.

So the easy solution would be to create a dtb.img and throw it into the boot.img like the 4.2 boot images and bootloaders expect from it, right? Well I tried doing that, and it got me nowhere, because I believe that aboot is looking for certain values from the device tree, which aren't consistent with the new 4.4 kernel's device trees (because of changes and whatnot to the source, and the exploitable-aboot that I'm using which is months older than the corresponding kernel source from the new 4.4 kernel). So I tried throwing old 4.2 dtb source into the kernel source and rebuilding, and it got me to a black screen, past the LG logo, but no adb access or anything, and rebooting yielding nothing in /proc/last_kmsg, so I couldn't debug anything... but it was further than anything I had gotten before. So I think there's two things that it could be... 1. The old devtree worked with my aboot, but did not work with the actual kernel once the kernel was looking for devtree values; or 2. The F320's 4.4 kernel source simply isn't compatible with the US devices, and we have to wait for the new source to drop!
[G2 General] tonynmisty:
I guess I wasn't exactly clear on what I did. It kept detecting root, so I used LG Flash tool and flashed back to 10d, then rooted, then took OTA to 10o, then called AT&T and they pushed 10q, then I had to move the date forward, after that, 20c was available OTA, so I took the OTA and kept root. I would have flashed 10o, but 10d was already downloaded on my computer, so I just used it. I think that "it" can somehow detect mods that were made, even if you have undone them.
[G2 General] bigfau:
That could be possible. Every time I went back to stock it was 10o and I have never lost root updating to kit-kat(20c).
[G2 General] vween:
Ok, so I when back to 10o. I have not rooted yet.

So, If I follow what you're saying, I can root, don't disable anything like carrierIQ and don't install xposed modules, etc. Simply leave everything the way it is except for being rooted. I should be able to get the KK update without losing root.

Does that summarize it?

Thanks
[G2 General] SuperSport:
Yes. 100% stock 10o, but WITH Root. Root will hold after 10q & 20c updates.
[G2 General] bigfau:
Yes, but you will have to have them push both D80010q and D80020c updates to you.
[G2 General] streetsmart999:
Through Chat with AT&T. I did not call.
[G2 General] muffinflesh:
Confirmed, I also just followed above steps. Restored to 10d, updated and rooted at 10o, then got ATT to push me 10q and 20c, kept root.
[G2 General] vween:
Ok, thanks. I'll give that a try.
[G2 General] mistermidas:
Just curious, since Im on the Sprint build and it'll be a lil while before we get the KK update. But has anyone who updated to KK and lost root, been able to restore root using the IOroot22 method?
[G2 General] garyd9:
Okay, this is REALLY interesting...

First, it'll save me the time of trying to put an "old" bootloader together with a new kernel/system.

Second, I think you might correct in #2 above (in that there is different hardware.) However, you have the actual F320 kernel source, so it should be feasible to massage it to work with your device. Try getting the kernel source for your verizon device and diff'ing it with the F320 kernel tree. Both kernels are 3.4, so the differences shouldn't be too much to pick through.

I really wish I had the free time to mess with this. I really need about 20 hours of uninterrupted time to work through differences, etc. There's a solution. There's ALWAYS a solution. It just takes time to find it.

It's also extremely helpful when people share what they've tried (failures and successes both) so there's a cooperative effort.

MODS: Would a thread in "lg g2 at&t development" section be allowed for DISCUSSING this issue? It would impose a burden on you, as it would have to be heavily policed to keep out the "my root doesn't work" type posts.

Thank you

Gary
[G2 General] bigfau:
Maybe someone should start a new thread of how to keep root while updating to Kit-Kat. To try and keep the "my root doesn't work" type posts to a minimum.
[G2 General] streetsmart999:
I guess It depends... Seriously. Cos Mine was..

1.What ever the phone came with (never saw the version)

2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.

3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.

4. Kitkat update came..

5. I de-froze all the apps before the update..

6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004

Once booted it said this update is not for rooted device. (or something similar)

7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.

8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...

9. chat with AT&T asked them to push 10q the silent updated.

10. once it was done I asked her if she can push Kitkat too.. she did.

The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)

SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)

Edit:

Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
[G2 General] JackpotClavin:
I've been trying to boot the 4.4 images in fastboot and it throws up some devtree errors and how aboot is looking for values, but they're a bit cryptic and hard to decipher, plus they flash on the screen for fractions of a second then go away as the kernel tries to boot, so I have to record them with an older device and play it back frame-by-frame.
[G2 General] Yamahar6riding:
Anyone in the ATL area able to get the update? I was able to get to the 10o using the LGtool but when I called AT&T to get the q she said there was no q only kitkat and it was region specific, that she couldn't push the Update.
[G2 General] streetsmart999:
Try to chat with them instead of call. (If you already did chat.. then its only waiting game).
[G2 General] garyd9:
....

fine - I created a thread for it:

http://xdaforums.com/showthread.php?p=50629141
[G2 General] garyd9:
It might be useful to take a look at the lk source for aboot... the messages you're seeing might be in there. Also try to find the messages in the kernel you've compiled.

Here's the aboot source: https://www.codeaurora.org/cgit/qui...c?id=0e163a4eec7b7fcaa4fe066b0207802e5503e10f
[G2 General] Yamahar6riding:
That did the trick, didn't even ask me what I was talking about. I gotta pro on the chat. Now its just taking forever for the final update to install, lol
[G2 General] sniffs:
When I called AT&T (I can't use chat, my line is on a business enterprise account and have to use Premier, which I dont have a log-in to), they told me(right before they told me to call LG to push the updates, as LG pushes the software and uses AT&T's network) that I "HAD" to be on WIFI to pull updates. Anyone pull these updates via cellular? I realize WIFI makes more sense, but just questioning the validity since they told me to call LG..
[G2 General] SuperSport:
You do need to be on WiFi.
[G2 General] garyd9:
For questions about Xposed not working, Try this: "search this thread". In that box, type "xposed". That will lead to http://xdaforums.com/showthread.php?p=50576333&highlight=xposed#post50576333
[G2 General] Gulfcoastowl:
viper4android

I really love the viper4android audio effect on my phone. I recently updated my phone to kitkat and maintained the root. My question is does this mod work anymore on the new kitkat update from AT&T as I want to install it and use it. Has any one comes across issues on kitkat?
[G2 General] Hid3rs:
An adventurous person with 4.4.2 and root access should give a try to this:

You can find the modified camera in his thread.
[G2 General] Clark Joseph Kent:
Members, please....Why is there so much of the same questions being asked over and over.....The answers are in the thread, search, read and read, if you do not want to search or do any homework, well then maybe you should just move on; stop asking the same issues/questions. I see questions being asked if you had read the same page it would of been answered.

And the questions regarding root/tweaking/moding your devices, most are still booting up with the update, much less worrying about all this...If you are one who has no clue, IMO you should just wait til the Dev's update their threads, vice coming in here and repeating the same items...

Now just short of closing this thread down, please be nice, play nice. And READ & SEARCH before posting, I see 52 pages of the same thing....
[G2 General] bigfau:
I got my hands on .dll and .tot files for D80020c Kit-Kat

Im going to upload right now.

Also I lost root . I tried OTA Root Keeper but it said I wasnt rooted even though I was.
[G2 General] sniffs:
dooood!! hook it up!! nice!!!!! I don't care about root now, I flashed the stock 10o a few days ago, but I'll be more than happy to flash this also!

I assume this'll flash on the 32GB AT&T LG G2?
[G2 General] SuperSport:
Unfortunately, when flashing using Flash Tool, it wipes whole device.
[G2 General] aaron105:
I guess the only option for saving data will be using LG Backup app
[G2 General] easyguy:
So this has 4K and 120frames videos?
[G2 General] abdel12345:
Sadly no (I don't have it to check myself but according. Others) . I believe that there will be a small update later adding some things like knock code once they are released but just speculation not anything with proud
[G2 General] Xstop:
Anybody able to change the dpi to 380? I haven't received the update. Still waiting
[G2 General] garyd9:
Going back to defeating the bootloader... (and thinking "out loud")

LG G2 D80010o bootloader: exploitable by loki

LG G2 D80020c bootloader: has checks to prevent the loki exploit

The d80020c bootloader has "self-preservation" code... meaning that it has explicit checks for kernel/ramdisk/tag memory blocks overwriting portions of the bootloader (which is how the loki exploit works.)

The d80010o bootloader does NOT have these checks. However, it appears that the D80010o and D80020c kernel images (boot partition) are in different or somehow different formats. This format is probably the same as the korean kernel images.

We have the korean kernel source...

Q: Can we recompile the korean kernel source to result in a file that meets all requirements of the korean bootloader EXCEPT that it doesn't have the proper signature?

Q: If the above is 'yes', then we can determine what's different in the format. Likely, it's just a header difference, or perhaps inclusion of device tables, etc.

Q: Using the D80010o bootloader, can the loki exploit be extended to overwrite more than just the check_sig() function, but to overwrite that, AND more?

Q: Can we create our own 'aboot' image that has code for loading the newer format kernel images, but that completely ignores the signature?

Q: Can a loki-like exploit be used to overwrite nearly the entire aboot image (in non-persistent memory) to include code that not only bypasses the signature, but also handles loading the boot image?

If "yes", then we use the d80010o bootloader, patch a boot image to include a "replacement" aboot image somehow, use the "loki" exploit to overwrite the d80010o bootloader - but overwrite nearly the entire aboot image - and then load our own kernel (or recovery) image happily.
[G2 General] ncfastls1:
By the way, anyone running into the issue of not being able to update due to root, here are the resources I used to get the LG flash tool to get me back to stock.

Rootjunky's video walkthrough: https://www.youtube.com/watch?v=kqw_LFuyHbE

And his download folder containing the necessary files: http://rootjunkysdl.com/?device=LG G2

The megalock file thing is in the unlock directory. Hope this helps as I had a bit of a headache trying to run around figuring out what steps to follow and where to get the files. I chatted with ATT and had the rep push the software update to me, which worked and now I'm on d80010o. Says he didn't have an option to push the kit kat update and for me to just do a software update through settings but it says I'm up to date. It rolls out in batches so I guess I have to just keep trying until I get it.
[G2 General] Yamahar6riding:
I had a similar issue. If you are at your computer just do a chat with them through the att website for technical support. Worked much better and faster than the phone rep.
[G2 General] :
Att does it. Maybe u just came across one of those lazy people. Easier if you make a my att account. Use live chat. They help better than calling em.
[G2 General] garyd9:
FYI - I've confirmed that the next build of xposed framework will work on D80020c. (I recompiled from rovo89's github.) I'm only posting this to let people know that I've confirmed that it'll be working soon.

No, I won't share the results of my recompile for the following VERY simple reason: If rovo89 intended it to be made available, he'd have released it himself. If you are technically able to deal with the various bugs that crop up with unreleased software, then you're also likely able to recompile from git.
[G2 General] Ltilt2:
up and running on 4.4.2.... Going back to stock was a pain though but after 2 days of trying finally was able to go back. Then from there install all available updates and chatted with att and they push the pre kat update. From there I forward the date and time and all is good now. Running KK