yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] blastagator:
You're just going to have to do kdz/tot if you lost both.

To All: There will be a new build tomorrow. I have disabled hardware acceleration for encryption. CM13 has serious stability problems with hardware encryption on. TWRP seems fine, but to play it safe, I have disabled it and am rebuilding. Literally nothing is changing if you don't encrypt. If you want to encrypt, wait another day to play :) I have already built and tested on d800, it is still decrypting fine w/out the hw support.

I also bought 8GB more of RAM for the build box to (hopefully) speed things up a little. Currently, I cut into virtual RAM during builds.
[G2 Android Development] Startrek852:
They can't use kdz/tot because they don't have download mode. Plus, they already tried KDZ and it didn't work.
[G2 Android Development] johnb380:
If u have fastboot u more than likely have download mode. That's in the bootloader its very hard to lose download mode.

With no Cord or anything plugged into the phone

Hold the power button for 20 to 30 secs or until it flashes on and off a couple times real fast. Then a red led light will be on then let go now as hold vol + down for 5 secs then keep holding it while u plug in USB Cord to pc and phone and download mode will come up for sure.

Edit http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/

That article covers every brick possible and shows how to fix it.
[G2 Android Development] Bandit8623:
latest recovery. i cannot access recovery on my device, but luckily i still have a working rom. what are the steps for me now so i can get my recovery working again? thanks in advance.
[G2 Android Development] eric93se:
Can't get to the red light with this method. Don't remember how I got to it in the past. I do get to the graphic of the small dead android (laying on its back, belly compartment open, red triangle with black exclamation mark).

When I try to factory reset and I get to the menu that asks "are you sure" and you have to confirm twice, I end up with the dead android.
[G2 Android Development] Pimps:
Got black screen past the lg logo after update. .
[G2 Android Development] johnb380:
Well I guess the bootloader that u r on must be different then my device then. All I can suggest is to read that article I posted or some of the unbrick guides around that's your best bet just try everyone out and see if u can get the right drivers on your PC and follow the steps word for word. I've never seen the screen u speak of so I really don't know how to help u. Sorry.
[G2 Android Development] Bandit8623:
when the device is completely off hold volume up. then attach usb cable. should go to download mode. worked for me.
[G2 Android Development] eric93se:
Takes me to fastboot.

I had used two other tools that took away dl mode (if I remember corectly), and also lost access to the ROM. One was SRKtool 2.1, the other was something like rasherd (can't recall).

I just got a tot for the D801 and really wanted to try LG flash tool, but I can't get to dl mode and also change com ports.

Need to know why in fastboot commands aren't getting executed. Going to try more drivers...
[G2 Android Development] Sunandroid:
What you're telling is crap. You can't access fastboot without nuking download mode. At least that's my experience with the D802. In this case it's implemented that fastboot is the fallback when there is no (working) laf partition.
[G2 Android Development] eric93se:
So SRKtool 2.1 has the option to 'fix fastboot mode'. It asks that files are put in one of the programs folder (fastboot, it was empty). It asks for basically all the files found in our bootstack flashable zips (aboot.bin, tz.bin, laf.bin, recovery.bin, boot.bin, persist.bin, rpm.bin, modem.bin, sbl1.bin, dbi.bin) a couple of them are not in the flashable zip; recovery.bin (is this twrp recovery? I don't have a .bin for that) and boot.bin. Should I try without these two?
[G2 Android Development] Sunandroid:
.bin is equal to .img. so you can (at least in this case) rename/replace the name ending however you want.
[G2 Android Development] ploµf:
Easiest is to use flashify ?
[G2 Android Development] kolouch.petr:
OK so I want to flash KK BL but where to download KK BL ???

thank you
[G2 Android Development] Led Zeppelin:
Works w/o any issue with D80230H and Daniel Stuart's Hybrid bootstacks.

Thanks :)
[G2 Android Development] 60nine:
at the bottom of the page (only for d802 model though)

http://www.dorimanx.com/LG-LP/
[G2 Android Development] Tokyo_Dikey:
New version ERROR TWRP3.0.0-1 [Lg g2 D802]

I installed the new version, but installing the MIUİ V7 ROM error is the TWRP Recovery.

I had phone LG logo and I could not take any action.

The new version of TWRP recovery may have been an error in the installation of this ROM why ?

Help me please ?
[G2 Android Development] Startrek852:
SRKTool says you can use either .img files or .bin files for the partitions.
[G2 Android Development] Computoncio:
If you post the log off the error in recovery maybe blastagator can help or see why it fail.

Phone: LG G2 D805

Kernel: Dorimanx kernel v9.0 LP D802

1st ROM : SRK-D80230h_20160107_droidth

2nd ROM : Waiting for custom recovery ;)

MODS: Viper4Android, Xposed
[G2 Android Development] eric93se:
When I send to the phone "fastboot devices" it responds: "? fastboot". No matter what driver I try.
[G2 Android Development] blastagator:
Please try to keep the discussion in this thread TWRP related. If you are having device problems unrelated to TWRP please make a different thread. An OT post here or there is expected since this IS a recovery post, but long back and forth can quickly overtake thread.

Also, if you need recovery help - "I upgraded TWRP and now it doesn't work" doesn't tell me anything.

Thanks all :)

edit: 3.0.0-2 is out. No big changes. Minor tweak to encryption. Be sure to update if you encrypt!

.
[G2 Android Development] Bandit8623:
thanks!. i had to use autorec. using flashify didnt work. and using twrp manager gave me a secureboot error.
[G2 Android Development] blastagator:
I am working on fixing the bootloader issue. Not sure when/if that will happen though.
[G2 Android Development] Startrek852:
[MENTION=5031300]blastagator[/MENTION] can you please fix the problems with AROMA?
[G2 Android Development] Computoncio:
Did anyone post logs, about that issue?

I didn't see nothing, that way it's hard to fix.

Phone: LG G2 D805

Kernel: Dorimanx kernel v9.0 LP D802

1st ROM : SRK-D80230h_20160107_droidth

2nd ROM : Waiting for custom recovery ;)

MODS: Viper4Android, Xposed
[G2 Android Development] Startrek852:
Yes, someone already posted a recovery.log. http://xdaforums.com/lg-g2/developm...f2fs-tools-t2898705/post65183804#post65183804
[G2 Android Development] dredq:
Did Autorec work?
[G2 Android Development] blastagator:
An empty log doesn't help, which is why I didn't respond to that post. I need a log of the failure, not just a normal boot.
[G2 Android Development] Startrek852:
Sorry, didn't notice that. Will get you a log of the failure.
[G2 Android Development] blastagator:
Pretty sure I found the bootloader problem:

This is needed for JB BL:

https://github.com/blastagator/LGG2_Kernel/commit/771b00440adc58a6705b06a3a8e4ce3099d431ee

Was reverted in MM:

https://github.com/blastagator/LGG2_Kernel/commit/dd206c6b38d7f83b37fc35f66441475ed3e8851f

Building test build with revert of the revert :D
[G2 Android Development] nabril15:
OI flashed 3.001 on my d800, and it reboots to a black screen. I can see that the screen is on, but no display. A long press of the power button reboots normally to a working Slimsaber LP rom; i had bumped 2.8.7.3 previously. Md5 checked fine.

Help please and thank you
[G2 Android Development] blastagator:
Use flashify in ROM to flash 2.8.7.3 image. I am working on a fix for JB bootloader.
[G2 Android Development] :
The point of the revert was to push for a move to the KK bootloader, as it is simpler, more aesthetically pleasing, and safer. There isn't really much reason to stay on the JB bootloader unless you're one of the "if it ain't broke, don't fix it", which is respectable, but if you are one of those people, then likely you wouldn't be considering using the latest TWRP ;).

You also need to revert this in your device tree if you haven't already to boot properly on JB bootloader: https://github.com/CyanogenMod/andr...mmit/a7dc930b2ac45a0061f1942cf7e138897ad2b8f2

One more thing: The latest SuperSU system-less root will not boot on G2 sources due to the modification of the boot image. On repack, it needs to be bumped again. It may be beneficial to either auto-bump boot images flashed or include an option in settings which allows the user to bump the boot image using open_bump. May even be something worthy of pushing to the main TWRP branch and doing a check against ro.product.manufacturor or whatever the prop that has the information is against the device and for blacklisted devices show the button to bump. I haven't snooped around in sources lately so I may be missing some sort of functionality that does this already, but I know G3 users are complaining over on the SuperSU sub-forum.

PS: Why lg-devs vendor over TheMuppets?
[G2 Android Development] blastagator:
Thanks for the information! I had already been playing with the tag and kernel command line, stupid kernel commit is what took me some time to find, heh. I understand the desire to go to KK, but if user flashes wrong thing, they should be able to boot recovery to RECOVER, heh... People should ALWAYS be able to boot recovery, unless they really cooked their phone :)

As to including bump, someone made a "c-bump" with the code in C, so I have definitely been thinking of adding this to TWRP, it is just a matter of finding some time to actually invest. Been trying to do a lot for our little device and still balance my real life (I'm actually a lawyer, I love the double torture.)

To-Do: Definitely c-bump :) Cant remember who it is by, but remember seeing the thread.

edit: loki was built into the flashable zips, with c-bump it should be able to be compiled like loki was and added to flashable zips. There are a few different ways to handle the bumping. A challenge to tackle on a different day.

lg-devs because when I started project that just happened to be the first one I found, lol. It is basically the same and not really that important for recovery.
[G2 Android Development] :
That's true, definitely a good fallback, was just explaining the reason for the commit.

http://xdaforums.com/lg-g2/development/cbump-posix-c-implementation-openbump-t3174339

Unfortunately it looks as if he has left the community and taken things with him, as his GitHub page is gone, as well as his XDA profile, so that option may be out unless a mirror is found. If I can find a mirror, I'll work on something and throw it up on omni Gerrit and let you know.

Edit: True. Wasn't aware if you were flashing the ROM as a whole when built from it, so if you were, then that would not be a good idea with lg-devs.

Edit2: Dori has a mirror on GH! https://github.com/dorimanx/cbump
[G2 Android Development] Startrek852:
[MENTION=5031300]blastagator[/MENTION] can't get logs, because ADB won't work in TWRP3, it says error: device unauthorized. ADB works fine when booted into ROM.
[G2 Android Development] Bandit8623:
it did then as an idiot i installed the latest twrp and now i cant get into my rom . or get into recovery. i can get into download mode but i cant seem to flash back to stock...
[G2 Android Development] blastagator:
I almost feel like I should take it down until I fix the JB BL problem. :X

edit: Compromised and moved it to "beta" category.

.
[G2 Android Development] natenkiki2004:
So the JB bootloader is what causes the black screen when loading TWRP 3?

Maybe I'm an idiot and still don't understand the intricacies of how all this stuff works for the G2, but, I'm on BlissPop 4.0.3 (Android 5.1.1) which requires the LP 30d Bumped bootstack. That would be what I'm using. Does bootstack =/= bootloader? I flashed your TWRP 3.0.0-0 and got the black screen. Does this new TWRP only work on KK and not LP or JB?
[G2 Android Development] blastagator:
I will take a look at this asap.
[G2 Android Development] Bandit8623:
i got my system fixed using the tot method. im now back to stock :) at least im working. thought i was gone there for a bit :)
[G2 Android Development] blastagator:
Great! Thankfully the g2 is pretty difficult to completely kill.
[G2 Android Development] dorimanx:
I want to make short explain / warning.

When using all kind of apps like autorec or flashify to install recovery, they actually may flash JB bootloader when you do it. "As bonus to help you!"

So here is the problem, you have advanced LP rom with KK bootloader for sure that came with rom or been asked to install as part of what you need to boot, as with my kernel.

Then some app stick junk jb boot loader and you get stuck! Cant boot new recovery, and kernel not booting as its need KK bootloader.

Conclusion do not use apps to install recovery ever... till someone will invent app that do only recovery install without "bonus"

You have 2 ways to install recovery.

1.use recovery to flash the new one :)

If you have JB rom, stay away for now! Till dev will restore JB support.

2. Search how to flash recovery image using dd command. Using adb or some terminal/ssh app. When rom is booted.

P.S dori always has the good stuff in git :)

Blastagator :) you are on correct path to fix mdss for jb bootloader.

And you need the panel type script to fix white lines for some devices.

Edit: just checked and i dont have jb support in my lp kernel. I had long time ago, then removed the cmdline changes.
[G2 Android Development] fLipz:
is this the one [Cbump] POSIX C implementation of Open_Bump by ferreirawax, maybe his account is deactivated here on XDA.
[G2 Android Development] blastagator:
I ran a build after:

https://github.com/blastagator/cm_d...mmit/b4448959fec7edfef7f719342cfb144752d6c557

https://github.com/blastagator/LGG2_TWRP_Kernel/commit/a21f8bea9937ee33c4994924cd9f3175b7880788

Screen didn't immediately crash to black, where screen still on and device hung. Device did reboot to ROM after hanging on LG logo for a little bit longer chunk of time (similar to problem I had before adding proper cmdline). In this case, the command line is back, so I'm not sure what else is missing. I will continue the hunt soon, and am open to suggestions.

Out of curiosity: What is the tags address and why was it changed?
[G2 Android Development] Startrek852:
Thanks!
[G2 Android Development] kolouch.petr:
I flashed the latest Kernel-Dorimanx-V9.0-LP-[16-54]-[08-02]-LG-D802-PWR-CORE.zip fo my D802

ROM doesnt boot and I can only get to TWRP :( have no idea hot to fix it, please help someone, thank you
[G2 Android Development] Startrek852:
Ask in the Dorimanx thread, not here.
[G2 Android Development] kolouch.petr:
SOLVED (flashed CM12.1 again) sorry for OT

I would really like to have TWRP 3.x but I cant find KK BL for my D802 Cyanogenmod based. Any link to download the right KK BL for D802 ?
[G2 Android Development] A Sornchai:
L22 : when I flash version 3.0.0-2 complete and then reboot system. It's OK, but when I reboot to recovery again, can't boot.

My rom : cloudyG2 2.2
[G2 Android Development] Aisfkhan:
I had previously installed Your last version of twrp with hybrid bootstack and everything was working fine but today I flash your 3.0 recovery and now my phone bootloops and I can't even get into the download mode....also not in recovery.

"Currently in Love with Htc one M8"
[G2 Android Development] dredq:
Flashed 3.0.0-2 last night on VS980. Reboot to Recovery. There is weird lag. First the LG screen appears for a few seconds and then black screen for 1-2 seconds and then finally the TWRP screen. I noticed this with 3.0.0-1 as well but the lag on 3.0.0-2 seems to be more.... I don't know if this is something to worry about.
[G2 Android Development] zizuka:
So if im on KK rom that normally boots with JB bootloader, I can flash KK bootloader then KK ROM and latest TWRP will work?

I think ill just wait for fix but im still on JB bootloader, dont know if phone with KK ROM will work with KK bootloader if must have JB bootloader.... Sooo confused
[G2 Android Development] runekock:
Most kitkat roms won't work with the kitkat bootloader.

To work, the kernel must be bumped, and bumping was only invented around the time that LP appeared.
[G2 Android Development] nabril15:
I'm sorry for the ignorance.

After installing flashify and downloading 2.8.7.3.zip, do i choose the flash zip option in Flashify, and reboot?

If i hold power qnd volume down key, I get the white factory reset screen. Does that mean I have the jb bootloader? Or kk? I ask to learn.
[G2 Android Development] dredq:
If you need to use the volume keys to choose selection and power to make a selection then you have KK.
[G2 Android Development] Trixanity:
If in doubt, don't flash a new recovery. While it's nice to have the latest version, it's not vital. 2.8.7.3 works just fine for flashing.
[G2 Android Development] romitkin:
You should extract the recovery.img out of the zip, then flash as recovery image through flashify.
[G2 Android Development] 60nine:
you were flashing dorimanx kernel on CM rom? that's a no go... dorimanx kernel is only for stock based roms (stock LP, cloudy, somboons, google edition1.3...)
[G2 Android Development] raptorddd:
theres something wrong with recovery, i have no log but i had to go KDZ 3 times. it works ok, not sure if xposed was the issue, tried different xposed worked fine . but after flashing regular stuff i get boot loop. and no recovery, from now 2.8.7.3 works fine.
[G2 Android Development] Startrek852:
http://xdaforums.com/lg-g2/development/lg-g2-bootstacks-t3173715
[G2 Android Development] zizuka:
So if kernel is bumped KK bootloader will work? I can bump.

Whats progress to flash bootloader? Flash BL, reboot recovery, re-flash ROM and done? Or flashing ROM again not necessary? U know?
[G2 Android Development] Sunandroid:
Flash BL, reboot. Done. No need to reflash the ROM.
[G2 Android Development] Aisfkhan:
Where I can find the kitkat bootloader?

"Currently in Love with Htc one M8"
[G2 Android Development] Aisfkhan:
Kindly please help this will be my 4th time to try 3.0.0 Recovery.

I'm currently now on D80120E 4.4.2 fully stock..which steps should I take to install bootloader and 3.0 recovery.

Before I was on 2.8.7.3 Recovery with hybrid bootstack and I flashed the 3.0.0 recovery after then my phone wasn't reboot to recovery it was continuously bootloops...then I go back to stock and recovered my phone.
[G2 Android Development] Startrek852:
Read the posts that are on this page that explain how to do it.
[G2 Android Development] blastagator:
Update

Obviously recovery needs (ideally) to work no matter what, that is why it is recovery, derp. I am spending as much time as I can on this issue. At this point, I might just have to scrap the change to cm-13 tree and go back to the old tree.

This:

https://github.com/blastagator/LGG2_TWRP_Kernel/commit/a21f8bea9937ee33c4994924cd9f3175b7880788

fixed the immediately black screen but device screen is still on problem.

The command line needed to be changed back (JB BL does not properly append the screen to the command line), so I did:

https://github.com/blastagator/cm_d...mmit/b4448959fec7edfef7f719342cfb144752d6c557

LG logo shows no for semi-normal amount of time, then device reboots. Somewhat scratching my head at this point. I have kdz/tot'd my phone several times now for you fine people :p

If any dev is interested, my build manifests are at:

https://github.com/blastagator/cm_device_lge_g2-common/tree/cm-13.0-twrp/twrp/manifests

Any ideas are welcome. I hope to spend some more time on it tomorrow night, but then I'm going out of town for a work conference for a few days, so who knows.
[G2 Android Development] kolouch.petr:
sucessfully flashed the KK BL but not able to make TWRP 3.0.0.2 work. Only blank screen appear. Anyway I will stay on TWRP 2.8.7.3. thanks for help
[G2 Android Development] raptorddd:
stay with 2.8.7.2 thats how i got mine with no recovery, remeber you pionted me to a thread to fix. i tried it 4 times and it just get black screen and had ato KDZ. lets wait for stable version.
[G2 Android Development] :
Just gonna drop some small important things that are popping up frequently.

-If 3.0.0-2 is giving the black screen, list the bootstack you used as well as your device. This is important because between Dorimanx's, Rashed's and Daniel's, there are different components in each and the issue may be related to one of the components. I am able to not 3.0.0-1/2 fine on a d800 with Daniel's bootstack.

-If you have issues flashing the image, use flashify to flash the recovery.img, however you can flash the TWRP zip in your current recovery as well.
[G2 Android Development] Computoncio:
The kernel you use only affects the rom, and not the recovery.

Recovery is a separate system, independent of the rom you use.

If you got no recovery that's because of the bootstack. Some roms flash bootstack, maybe thats the problem.

I'm using kk bootstack from blastagator and only have the aroma flash issue. Didn't found anything else broken.

Phone: LG G2 D805

Kernel: Dorimanx kernel v9.0 LP D802

1st ROM : SRK-D80230h_20160107_droidth

2nd ROM : Waiting for custom recovery ;)

MODS: Viper4Android, Xposed
[G2 Android Development] babe0607:
Hi...

I have D802, Thunder rom v2.2, Dori kernel 9.0 and TWRP v3.00-2. Is TWRP v3.00-2 working with aroma?

because I've tried to install the flashable zip SRK D80230H_20160107_droidth from somboons (i did clean install first. I wiped everything except internal memory) with TWRP v3.00 and when it was in recovery and aroma started, screen stuck to aroma and after a few seconds booted to rom(thunder rom).

I've tried 2-3 times the same procedure and the result was the same.

TIA

Phone: LG G2 D802

Dorimanx kernel v9.0 LP D802 THUNDER ROM V 2.2

MODS: Viper4Android, Xposed, TWRP 3.0.0-2, G3 tweaksbox
[G2 Android Development] djtiesto22:
Just install stable 2.8.7.3 and try to flash that file. We all known that latest twrp is not stable so please wait the [MENTION=5031300]blastagator[/MENTION] working on a fix so no need to panic for everything...
[G2 Android Development] babe0607:
Thanks for the reply [emoji4]

I'm not in a panic... I wait for stable version. Also i use otg with NTFS instead of 2.8.7.3. I was just reporting about aroma...so everything is good calm and fine ?

Phone: LG G2 D802

Dorimanx kernel v9.0 LP D802 THUNDER ROM V 2.2

MODS: Viper4Android, Xposed, TWRP 3.0.0-2, G3 tweaksbox
[G2 Android Development] blastagator:
Due to all of the problems, I updated the omni44 branches I maintain. I ran a build and confirmed 3.0 working (read: booting and basic function testing). If I can't find a solution to the cm-13 woes, I am just going to run a build on the old trees and everyone should be happy again.

I also confirmed decryption is properly working (tested against cm-13.0). Also confirmed booting on JB BL.

This is recovery, it needs to work for everyone.

This is also why the downloads have been taken down. Sorry for the fuss! Please don't post up the existing 3.0 versions, they are just causing too many headaches. (Primarily my head from reading this thread, lol.)

edit: I did a large chunk of commit rollback - Now booting the cm-13.0 tree on JB BL. :D New build will be out the next day or two (hopefully before leaving for my work conference), otherwise I don't get back til Tuesday night.

ADB is fixed as well.
[G2 Android Development] desirexel:
Report : D800 rashed's bootstack AICP mm11 twrp. 3.0.0-0 works fine but update to 3.0.0-2 white lines like autorec related white line with JDI vs LGD panel issues on kk

I revert to 3.0.0-0 through button combination. 3.0.0-0 works great for me..