yashsingh1/xdaforums huggingface dataset:
[G2 General] DurbanPoison24:
Oh man no T-Mobile G2 recovery yet but AT&T has one!?? Lol. Well I guess waiting however much long won't hurt too bad knowing there's already a recovery for one variant.
[G2 General] garyd9:
Oddly, it's not a big deal. Just need a dev type person who actually owns a D801 to grab the kernel Savoca has linked several times (in this thread!) and some partitions from the D801 kitkat firmware, mix well, and post it.

I'm pretty sure there are some people around with D801's that are fluent enough with edify scripts that they'd be able to do this... The problem is that it's kind of time consuming to do, and requires a bit of knowledge in how to recover the device if something goes wrong. (The "knowledge" is just being comfortable with the LG flash tool and/or fastboot.)
[G2 General] DurbanPoison24:
Oh man you just made me a bit more nervous. Seems like a lot to do and very tedious with little to no people attempting to do so.
[G2 General] garyd9:
I know I'm going to regret this...

I've pulled down the previous d800 firmware I posted, and reposted something that's packaged a bit better and with some "kinda" user-friendly directions:

(This is only for AT&T D800 devices)

http://xdaforums.com/showthread.php?p=50882393

THIS IS ONLY FOR PEOPLE WITH AT&T LG G2 D800 DEVICES AND WILL NOT WORK FOR ANYONE ELSE. I DON'T HAVE ANY OTHER G2 DEVICE, SO CAN'T TEST ANYTHING WITH THEM - SO WILL NEVER POST ANYTHING FOR THEM.

Again, because there are people on this forum who need something to be repeated more than 3 times... This is only for the AT&T LG G2 model D800.

Oh, and one more thing before I forget:

This will only work for D800 devices.

Take care

Gary

PS: only d800!
[G2 General] barondebxl:
Lol! If after this ^ post ppl still ask questions whether it works for other G2 models I might hire a hitman to hunt those idiots down.
[G2 General] garyd9:
umm... I like you... but there's no way I'm going to "click" you to see your content. :eek:
[G2 General] dr87:
D801 4.4.2 stock rom up and running with TWRP / Savoca's edited kernel

I will post the flashing process as soon as I figure out which partitions are 100% vital

modem seems required, LG logo continuously looped without it
[G2 General] garyd9:
I'd try with rpm/tz/modem. On the D800, none of the three were required, but seemed like a good idea as long as they caused no harm.
[G2 General] Koopa777:
So I can flash this on LS980 right? :p

But seriously, if you still flash that without seeing all those warning, you deserve to have your device bricked. I couldn't even see the hyperlink at first, through all those warnings.
[G2 General] dr87:
yea, seems on d801 rpm and tz isn't needed either.

I can't boot without the modem, my guess is because tmo is on the 34 baseband while every other variant is on 36 (pre kitkat modems)
[G2 General] NolenUmar:
That moment when your device is being developed on :D :pride:

sent from my potato
[G2 General] joshuadjohnson22:
Will this work with D802?

jk haha this was funny
[G2 General] nismology:
So I dd nuked the recovery partition to get into fastboot and it worked. However, the phone is supposed to say "processing commands" or some such to indicate that I can issue commands but I don't see it. "fastboot devices" results in "waiting for device". Have you encountered this?
[G2 General] somboons:
Waiting kernel for D802..
[G2 General] reemar:
so.., we need to flash a kernel that will allow us to use custom recovery.., but for flashing that kernel we need custom recovery, this a bit of a paradox. else we flash that one stright from 4.2.2 recovery as shown here: http://xdaforums.com/showthread.php?t=2666967
[G2 General] albsat:
Too many useless posts and probably mine will be such a one. Mixing custom kernel with 4.2.2 boot and adapting scripts and different partitions of kitkat, could this be a hindrance that devs will not be ready to make custom kernels in the future?
[G2 General] 00001101:
Yes, but before that, devs are waiting for LG to release the Kernel Sources for 4.4.2 for the 802 model.

Sent with LG D802
[G2 General] jrgilbert79:
Technically we need the boot stack from 4.2.2 to allow custom recovery. We only need a modded kernel to boot kk else if you flashed the wrong kernel on accident you would be bricked since recovery wouldn't work. Its a good thing it isn't that way.
[G2 General] ledvedder:
This is great news! Can't wait!
[G2 General] savoca:
Not at all.

Waiting for D802 source, so I can make you good and patient people a 100% vanilla kernel that is as perfect as the official one that we can't use for custom recoveries...
[G2 General] Kickoff:
I just checked the new LG G2 User Guide for the KiKat version (D801). It states:

LG assumes that all the great devs will have success (soon?) with the development of custom recovery for KK. :)
[G2 General] garyd9:
"user guide"? What's that?
[G2 General] epapsiou:
no wonder your company doesn't let you near your users :)
[G2 General] Kickoff:
http://g2-lg.com/t-mobile-lg-g2-d801-user-manual-guide-android-4-4-kitkat-version/
[G2 General] garyd9:
Wow. I didn't get one of those. My phone came with a bunch of AT&T junk... It certainly didn't come with any type of manual when the OTA was pushed. (There was a "device help" thing, but I think I disabled that waste of space even before I disabled carrierIQ)
[G2 General] 6ril1:
http://www.lg.com/us/support-mobile/lg-D800

http://www.lg.com/us/support/products/documents/LG-D800-ATT_UG_EN_KK OS_Web_V1.0_140214-1.pdf

http://www.lg.com/us/support/products/documents/eBrochure_LG_G2_ATT_v2_.pdf

http://www.lg.com/us/support/products/documents/LG G2 D800 QSG (KitKat).pdf

http://www.lg.com/us/support/products/documents/LG G2 D800 Spec Sheet_R1.pdf
[G2 General] garyd9:
That is nice, but it doesn't change that the phone didn't come with a proper manual, and a proper manual isn't even linked to in an obvious place on the phone. The warnings might as well not exist if you have to actively search on the internet to find them. This is more especially true for a phone distributed and branded by a US carrier. If I modify the phone's system and LG tries to deny warranty using only a warning that's buried on the internet as a grounds for denying warranty service, they'd lose in a court battle. (For that reason, I'd guess there's a more obvious warning or disclaimer somewhere - even if I never have actually seen it. I doubt the LG legal department is stupid.)
[G2 General] dr87:
You can find the process for D801 here

I tried to make it as simple as possible and include all links, if you cannot understand the directions I would not even mess with this.

Huge thanks to all dev's who worked hard on this
[G2 General] zPacKRat:
How far off topic you guys going to take this. Owners manual discussions do not belong here.
[G2 General] garyd9:
Honestly, the entire thread is moot now. We have mechanisms for kitkat+recovery on every device that has had kernel source released.
[G2 General] AndroidUser00110001:
I am going to lock it up once I get to my computer.
[G2 General] Swamphound:
All I can do is thank you all from a grateful user.

Sent from my VS980 4G using Xparent Green Tapatalk 2
[G2 General] Qverse:
Thank you all for starting with a vision and pointing to path for KK recovery . You Guys are the ones who make that difference in XDA, keeping it alive ! :good:
[G2 General] shriom_manerker:
i apologize for being off topic, please consider this as the last thank you post ! why dont you guys just use the "thanks" button on all major posts ? just do that and thats very much appreciated by the developers.

on another note , i think we should have "developers discussions" section ! the galaxy nexus had it in xda. itll be helpful if we have that too
[G2 General] garyd9:
I doubt that will happen with this device. There simply isn't enough active creative dev on it.

(I've been very involved in the creation of the dev discussion sections...)
[G2 General] Clark Joseph Kent:
Done...thread closed.

Judgment is near.....
[G2 General] Sean473:
I don't want to flash anything.. I'm not not in the mood to do factory resets..
[G2 General] zPacKRat:
Stay on topic, there is a thread for finding a method to root, maybe your efforts would be better spent there.
[G2 General] AndroidUser00110001:
I have it working without messing anything up to get there. It is my normal recovery now that I can boot into OS and that recovery with no problem.
[G2 General] muhamet:
I flashed Wothewer TWRP non roote need recovery t Kitkat rom.And ther i find new recovery and options like:aply update zip from sd,adb sideload ..,., i think wee need t amply root from ther.Sory bad English
[G2 General] rinxas:
I've been able to boot to that recovery and tried to flash by sideloading the SuperSU file but it gave me and error. :-\

Enviado do meu LG-D802 através de Tapatalk
[G2 General] freakyd9984:
Will this work on T-Mobile d801 when it comes out
[G2 General] daddioj:
yeah I found this recovery when kitkat first dropped. I forgot for what reason , I did adb reboot recovery. and was surprised to see this when phone rebooted. good luck with the recovery :good:
[G2 General] Z51:
I'll try and load Phil's recovery tomorrow. Forgot my laptop at work. Gonna attempt it tomorrow. If I brick it I'll restore to KK haha
[G2 General] spiderio:
how to boot to this recovery from kitkat??
[G2 General] suhiiii:
Just reboot in recovery with adb or titanium backup.
[G2 General] ljp1132719438:
Anyone working on Multirom for G2?
[G2 General] nismology:
While we're on the topic of fastboot.....does anyone know how to purposely enter fastboot mode?? I got this crazy idea that using the command "fastboot boot recovery.img" could (temporarily at least) work instead of the "fastboot flash recovery recovery.img" that the bootloader won't allow. I just need to find a way to get to fastboot first. :good:

I've tried different key combinations and even used dd to overwrite the stock recovery with TWRP to get into it but I just got an error message.

--------------------------------------------------------------------------------------------

The other angle is to try to get Loki updated with the new aboot info.
[G2 General] farhanito:
Have you tried "adb reboot bootloader" ?
[G2 General] gunnyman:
doesn't work
[G2 General] nismology:
Unfortunately all that does is reboot the phone. There's no "bootloader mode" per se like there is with my old GNex.
[G2 General] AndroidUser00110001:
If you flash recovery phone will not boot since it is part of the boot process check. Since we have root with KitKat you can load recovery as you normally would on JB but once again phone will not boot. The bootchain needs to be broken to get into fastboot. Only way I have seen so far.
[G2 General] nismology:
Yea I have have used dd and loki_patch/flash to attempt to get into custom recovery and gave up on those methods. My concern is using "fastboot boot recovery.img" to bypass installing it directly to the recovery partition since that obviously doesn't work. I used this method with my GNex of booting into custom recovery without actually installing it. I'm trying to get into fastboot mode to try it but can't manage to do so. I hoped dd'ing TWRP to get to fastboot mode but it didn't work either. Hope that clarifies.
[G2 General] garyd9:
If you can't exploit a bug in the boot chain (as was done with loki), then the boot chain has to be changed to something exploitable. The trick is using the exploitable boot chain with a newer kernel/system.

... and look at that: LG has posted kernel source for both the d800 and d801 kitkat kernels:

https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=_KK_
[G2 General] GizmoKaca:
This is great news! Thanks for this information! :)
[G2 General] easyguy:
Damn, I guess LG is using a new security system to not let us use custom recoveries. I'm surprised about that.
[G2 General] garyd9:
It's not new. The same "system" is used by the SGS4, and derived from a system used on moto phones for quite a while. Here's a blog post about the sysem (and how the "loki" exploit works): http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html

The newer boot loaders actually are fixing a bug that allowed the exploit documented in that blog. In fact, the bug was fixed in the "lk" sources quite a while ago... around May of 2013.

Oh, and be happy that at least LG allows us (probably because of an oversight) to revert to an older bootloader. My understanding is that on the SGS4, once you've updated to the "fixed" bootloader, you can no longer go back.
[G2 General] nismology:
We still don't know that the Loki exploit won't work. Every firmware update on supported devices requires an update to Loki, testing to make sure it still works and the changes merged into source and that hasn't happened yet.

https://github.com/djrbliss/loki/commits?author=djrbliss

---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------

This is huge and can't be overstated.
[G2 General] garyd9:
Yes, we do know that the exploit won't work with the newer bootloaders. The kitkat bootloaders have been examined and are known to contain the following patch (or something very similar): https://www.codeaurora.org/cgit/qui.../?id=0e163a4eec7b7fcaa4fe066b0207802e5503e10f

To understand that patch, you have to understand how loki works...

Basically, loki exploits a bug in the older bootloader that allows a custom kernel or recovery image to overwrite the bootloader itself. That, in turn, is used to overwrite the portion of the bootloader that checks to see if the kernel/recovery image is unmodified.

The patch linked above validates the kernel/recovery image load addresses to ensure that they don't overwrite any part of the bootloader itself.
[G2 General] nismology:
Wow. My education is just beginning. I was hoping it was simply a matter of waiting on a Loki update. Yikes! Now I'm really glad indeed that we can downgrade to the older bootloaders. Phew....

More reading for me! Thanks!
[G2 General] AL_IRAQI:
Maybe we should ask [MENTION=631273]Chainfire[/MENTION]

For help he roots nexus 5 with cf-auto root

But the problem here we can't boot into fastboot or unlock bootloader :'(

Sent from my LG-D802
[G2 General] felipondrioxcl:
I'm very sad about loki... we need custom recovery :(
[G2 General] garyd9:
I am (er.. was) working on a mechanism to bypass the newer bootloader. If my theories are correct, the method will work with all the models (with just a recompile required.) The idea was to use the older bootloader with the newer (recompiled and loki'd) kitkat kernel (and old recoveries.)

Sadly, I got close to burned out working on it over the weekend, so decided to take a break for a week or so. I was in a "I can't get anything at all to work properly no matter what I do" state... and the only way I've found to get out of that state is to walk away and try again later with a fresh head.

If no one else comes up with a solution before then, I'll probably jump back into the project this weekend or next.

One issue is that while there seems to be multiple people working on this, very few people are willing to share their ideas on possible ways to deal with it. So, it's quite possible that we are all repeating the attempts of others. :(
[G2 General] gunnyman:
So there's no central LG G2 IRC Community? :(
[G2 General] garyd9:
No idea. I don't use IRC.

To be honest (and I hope no one bashes me for typing this) - I'd be scared to log on to it if I did use IRC. My reason is that you don't see much "development" chat on those things, but you do see people screaming for other people to cater to them and solve their problems because they're too lazy to read and search forums. I'm not a really good "people person." (Okay, perhaps that's an understatement.)
[G2 General] gunnyman:
I've participated in several successful hack sessions via IRC. MotoX Root and system write and HTC One Conversion to GPE for example. Sorry you haven't had a more positive experience :(
[G2 General] savoca:
Tried that too last weekend, I actually downgraded the board files to the latest ones compatible with 4.2.2 and still got nothing, tried new and old offsets for the boot.img as well.

Since I've got a sprint variant I'm just going to wait for the KK ota to move any further.
[G2 General] gunnyman:
I guess LG has gotten better at locked bootloaders since the Optimus G. :(

They didn't have to copy Samsung THAT closely :p
[G2 General] GeneralRam:
Deleted

---------- Post added at 12:38 PM ---------- Previous post was at 12:28 PM ----------

Can you access flashboot while in this recovery? If so, wouldn't it allow a flash of a customer recovery that way?
[G2 General] gunnyman:
Phone won't boot with anything but stock recovery.
[G2 General] joshuadjohnson22:
Now if we could only perfect an app like Flash Gordon to flash roms.... That would change the landscape of android.. then you would only need root
[G2 General] farhanito:
..or bootstrap recovery, just like Droids era.
[G2 General] garyd9:
Did you actually try to recompile the newer kernel source (from a korean variant - as that was the only one available at that time) and put that with the older bootloader? There are some dtb changes that might be needed. (Check your PM's for the boring details.)

Take care

Gary
[G2 General] AndroidUser00110001:
I tried all that too and furthest I got was getting this hidden recovery to show up under normal circumstances without breaking the boot chain. My next step is to try to disable the signature check when flashing zip files from this hidden recovery so at least users can flash zip files but still keep the stock boot.img.

I tried to compile Clockwork recovery and TWRP but when I flash to device it will boot to OS but I can not get into any type of recovery. I have to see if I am compiling recovery wrong or see what else could have went wrong but at the very least the phone boots.

It's not a matter of flashing recovery. If you have root you can flash recovery but the recovery has to bypass the security checks for the phone to boot.
[G2 General] garyd9:
Summary of attempts (for custom kernel/recovery) by various people who have posted what they've tried. This ONLY applies to booting the kitkat system firmware.

* "10d" refers to firmware (bootloader/chain, kernel, recovery, etc) that was originally installed on the LG G2. The actual version might differ based on specific hardware models.

* "20c" refers to the firmware (bootloader/chain, kernel, recovery, etc) that is installed with the "kitkat" update from LG. The actual version might differ based on specific hardware models.

* "loki modified" refers to a recovery or kernel that has been loki_patch'd to work with a "10d" bootloader.

* "stock" refers to binary images that haven't been otherwise customized.

(the 10d/20c are the versions on the d800 device, but other devices might have different letter suffixes)

Known

NOT

to work:

* Any combination of the 20c bootloader with anything other than the unmodified 20c stock recovery or 20c kernel.

(any combination involving the 10d bootloader will allow a custom recovery, but then we still need a kernel to normally boot the device)

* The 10d bootloader with an unmodifed 20c stock kernel

* The 10d bootloader with a loki modified 20c stock kernel or loki modified 20c stock recovery

* The 10d bootloader with any stock or loki modified 10d kernel (The 10d kernel doesn't work with kitkat)

* The 10d bootloader with a recompiled and loki modified 10d kernel **(This is the CURRENT state -- it's likely possible to modify the 10d kernel sources to work)

* The 10d bootloader with a recompiled (but not changed) and loki modified 20c kernel. (This doesn't work without modification of the 20c kernel sources to "match" the 10d bootloader requirements.)

Things people are still working on trying (or haven't yet tried as far as I'm aware):

* 10d bootloader with MODIFIED 20c kernel sources -- with kernel source changes that the 10d bootloader expects. Known required changes at this time are device tree and kernel command line changes.

* 10d bootloader with 10c kernel sources modified to be compatible with the kitkat system firmware.

* 10d bootloader with AOSP-based kitkat kernel sources modified to be compatible with the LG system firmware.

* Somehow modifying the 20d stock recovery to bypass signature checks, but without changing the actual stock recovery image (which would cause it to fail bootloader signature checks.)

* some type dual stack or 2nd init hack.

---
[G2 General] AndroidUser00110001:
Did you not read my last post (my sarcasm back at you from another thread in case you thought I was fishing for something)? That is what I have done so far sort of but you got me confused on how do you modify the stock recovery image without actually changing it. If you modify it are you not changing it...
[G2 General] easyguy:
Thanks for the hard work guys.
[G2 General] garyd9:
I'm confused... Your very recent post says:

So, that was why I included the part you quoted. I'm not sure how you'd go about doing that without modifying the image, but I didn't want to say that it's not possible just because I'm not sure how it'd be done. (The "hidden recovery" in your message is the "stock recovery" in mine)

The bottom 5 lines are "Things people are still working on trying (or haven't yet tried as far as I'm aware)"

If I've made an error in my summary, please point it out and I'll be happy to correct it. The whole idea was to consolidate what is known to NOT work AND what is still being attempted.
[G2 General] AndroidUser00110001:
The hidden recovery as I call it is what the picture is in the first post. Yes you can get to it if you break the boot chain but as I said before I got it to the point where it is the recovery that shows up when you go into recovery with phone still being able to boot to OS. The stock recovery to me is all the bull**** text with the only options to cancel or keep pressing power to reset phone.

Since I am able to boot into the hidden recovery by just going into recovery by key combo I am going to try to disable the signature check when flashing files from the hidden recovery so it can be used for now to flash ROMs that use stock boot.img (like safe strap) or other zip files. If it works of course...
[G2 General] garyd9:
Okay, it's just a difference of terms. :) The screenshot that looks like a trimmed down CWM is a standard android recovery and should be contained in the partition named "recovery." (More on this below.)

To be honest, I have no idea where "press power to erase your phone" screen is located. I suspect it's stored in the bootloader (aboot) or someplace earlier in the bootchain, but I really don't know.

There's also a download or fastboot in the phone which is most likely part of the boot loader as well.

...

and just for amusement, I just erased my entire phone (but not on purpose.) (heh.) In typical android, at a root shell prompt, the command "reboot recovery" should reboot you into the recovery partition. What never occurred to me (until it was too late) was that the stock _LG_ recovery will wipe the device if no other parameters are passed to recovery. (This is what happens when you use the "press power to erase your phone" - it boots the recovery partition with no params.) (there are exceptions, but I don't know what they are.)

So, I did a "reboot recovery" to verify that what you called the "hidden recovery" was the same as what I was calling the "stock recovery" (they are.) In the process... well... I have a backup at home. ;)
[G2 General] AndroidUser00110001:
Yes and when CWM first started it was pretty much this recovery with extra options. The hidden recovery( I call it hidden since most users don't see it) is what I boot into now when I boot into recovery and phone is still able to boot into OS. You do not get the normal text recovery front. The CWM and TWRP I made will allow phone to boot to OS but I cannot boot into TWRP or CWM. This part of android hacking is still new to me so I am not sure if I built CWM or TWRP wrong or there is something else I am missing. This is why I am going to try to disable the signature for flashing zip files and then we might be able to have a safe strap for now if it all works out.