yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] jeebspawnshop:
When you change the FS of the data partition, it wipes the internal memory, since they both reside on the same partition.

This is well documented throughout XDA.

In fact, if you're using TWRP, it WARNS you of that fact.

And no, there's no way to recover it.
[G2 Android Development] blastagator:
Warning is huge and in this thread: http://xdaforums.com/showpost.php?p=55892416&postcount=5

There are possible ways to recover, they are all advanced and beyond the scope of my knowledge. I do know that TWRP does not use a "secure" formatting method, so the data is theoretically still there. How to access it, I have no idea.
[G2 Android Development] blastagator:
If anyone is concerned, the EFS restoration bug does NOT affect any of our builds.

(Reference: http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119)

No need to panic :)

.
[G2 Android Development] :
When performing a system wipe does it wipe everything? I ask because I am having some quick cover related issues after flashing an aosp rom. (Screen goes off at initial setup screen) When flashing a stock rom also the same problem until I can get to settings and turn off quick cover.
[G2 Android Development] mastroalex:
Hi, I have an LG G2 D802 with kitkat 4.4.2 stock and I can't manage TWRP to read my password encrypted phone, it says "wrong password". I tried all these versions:

twrp-3.0.2.1-d802-bump-blastagator-signed

twrp-2.8.5.1-d802-bump-blastagator-signed

twrp-2.8.3.1-d802-bump-blastagator-signed

any solution? To me encryption is mandatory.
[G2 Android Development] blastagator:
If you go to Advanced Wipe and select just System, it will only wipe the System partition. If you want to start completely over, check all the boxes. Once you wipe everything you'll probably need to restart recovery to get sdcard access back, then you can copy over what you want to flash from your PC.

Update to something newer. Why are you still on KK? Encryption wise, a lot has changed since then. I was under the impression TWRP team had fixed all backward compatibility, but maybe only for LP and higher. Also, what kind of unlock are you using (pattern, password, pin)? Have you tried a different type of unlock?
[G2 Android Development] mastroalex:
Password, as it's the safest for me. Never tried other unlocks. I'm still on KK cause I have G2 Tweakbox that don't work on LP. I use a lot ring pad and on lollipop I couldn't manage to customise it with other apps.
[G2 Android Development] blastagator:
If I recall correctly, G3 tweakbox works on G2 LP.
[G2 Android Development] Startrek852:
Yes, G3 Tweaksbox for Lollipop works on G2 Lollipop.
[G2 Android Development] mastroalex:
I finally had time to update to lollipop, latest version for LG G2 and latest TWRP 3.0.2-1, still no way to decrypt the partition.
[G2 Android Development] blastagator:
Log? I have used encryption for quite some time and it decrypts fine in TWRP.

edit: If you did a dirty flash (i.e. didn't wipe /data and create new encryption using lollipop ROM) the KK encryption scheme might still be in use, and perhaps that is not supported.
[G2 Android Development] mastroalex:
Thanks for your attention. In recovery I executed an hard reset, format partition, wiped system-data-cache-davlik then installed this: SRK-D80230F-EUR_20160528_droidth.zip which is 5.0.2 V30F EUR kernel 3.4.0.

Preinstalled recovery was TWRP Blastagator 2.8.6.1 and I updated to latest version bump blastagator signed 3.0.2-1. Then I encrypted my phone, no way to use TWRP. I tried again older versions, no way.

It says "unable to mount" then "password failed, try again".

Maybe later I'll try to unencrypt - decrypt with another password.
[G2 Android Development] mastroalex:
Here's my log.
[G2 Android Development] blastagator:
Your log:

crypt_ftr->fs_size = 22675456
Using pbkdf2 for cryptfs KDF
Invalid hex string
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 22675456
Using pbkdf2 for cryptfs KDF
Enabling support for allow_discards in dmcrypt.
load_crypto_mapping_table: target_type = crypt
load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p35, extra_params = 1 allow_discards
Error temp mounting decrypted block device '/dev/block/dm-0'
Failed to decrypt data.

My successful log:

crypt_ftr->fs_size = 51478528
Using scrypt for cryptfs KDF
Invalid hex string
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 51478528
Using scrypt for cryptfs KDF
Enabling support for allow_discards in dmcrypt.
load_crypto_mapping_table: target_type = crypt
load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p38, extra_params = 1 allow_discards
Password matches
Data successfully decrypted, new block device: '/dev/block/dm-0'

Try setting the password to the default password and see if it still doesn't work. Perhaps you are using some kind of symbol or non-standard character that it doesn't like. If the default password doesn't know, let me know and we can go from there. If default password works, then some symbol/character is causing an issue and maybe we can figure out the specific character and a solution.

Your block doesn't match to what my d800 has. Not sure if this is related.

cache -> /dev/block/mmcblk0p35
[G2 Android Development] mastroalex:
What's the default password? The one I was using was very simple, no special characters.
[G2 Android Development] blastagator:
When you choose your unlock password it asks if you want to require the password at boot time. If you choose no, the phone stays encrypted but uses the default password for the encryption. No need to decrypt, you can just change the password option back after testing.
[G2 Android Development] mastroalex:
My phone says a password or pin is mandatory and forces me to input one. Anyway I tried another wipe, then with the "clean" phone I set password "123a" and it didn't work. Then tried again with pin code 1234, it didn't work either.
[G2 Android Development] blastagator:
If you didn't do a factory reset and then re-encrypt, it could be related to KK encryption scheme. I am pretty stumped as to what else the issue could be. If you do "Advanced Wipe" in TWRP, that won't clear the encryption. You have to do the factory reset, the one that requires you to type "yes" to confirm. This will delete everything on /data, including the internal SD.
[G2 Android Development] mastroalex:
Nope, I did that, also format. I'll try to ask an Italian forum where people should have my same ROM. Of course I'll update you if I have any news.
[G2 Android Development] blastagator:
Thanks. I'd be very interested to find out why it isn't working. I don't think I've had any other reports of problems with encryption since working the encryption issue out. Maybe the kernel in the ROM you're using has some setting the others don't, but that seems pretty unlikely since this is the second ROM you've tried. I'm pretty stumped. Link me to the current and previous ROM?
[G2 Android Development] SdtBarbarossa:
reformating /data should fix it ( and delete everything !!! )

twrp->wipe->advanced wipe-> change fs

there change the fs of /data to something else e.g. f2fs and then back to original ext4
[G2 Android Development] mastroalex:
I tried twice with both f2fs and FAT, it didn't work.

Current SRK-D80230F-EUR_20160528_droidth: http://xdaforums.com/lg-g2/development-d802/rom-stock-30d-flashable-zip-t3070383

Previous (the prerooted version D80220H_prerooted_recovery_friendly_by_6riloo): http://xdaforums.com/lg-g2/development-d802/rom-original-eur-80220h-kdz-to-recovery-t2941528
[G2 Android Development] whoadood:
This recovery is great, but Autorec simply does not work well with recent versions of SuperSU, and having to de-root and root using an old version is a *****... What I did was:

1. Installed Autorec from the Play Store

2. Used adb pull to copy it to my computer

3. Opened it with 7-zip and, in the assets folder, there's aboot.img, boot.img and laf.img, I copied them to my mobile

4. Downloaded this build of TWRP, opened the zip and copied recovery.img to my mobile

5. Flashed them all with dd

I know this is sorta off-topic, but that's what worked for me. Anyway, great job with this build of TWRP.
[G2 Android Development] Neoguto:
How can I flash this TWRP over cyanogen recovery??

I tried to install by zip directly, and sideload zip, but always fails!!

Someone can help??
[G2 Android Development] hteles:
I guess you will need a signed twrp, beware of incompatible Loki vs bump bootloader methods.

Long time ago I flashed a older twrp and after that I've updated to the newest blastagator's twrp. If you can find a bumped signed twrp zip you should be safe. Other possibility is to use DD method bit it's riskier.

Not @ the PC, can't help further right now.

PS. CM Roms have a option to install CyanogenMod recovery. You should disable that in the future.

Regards.
[G2 Android Development] Neoguto:
So, i did it on the first flash of cm13 i made, but on the 08/11 update, the dirty flash failed, so, I needed to flash via adb, and there's no option to do choose via adb!!

I'm gonna search a bumped signed twrp, Thanks!!! :good::good::good:

Found the twrp-2.8.7.3-d802-bump-blastagator-signed but with no succes in the flash, the damm cyanogen recovery still there!!! :(

EDIT: Solved, Thanks again man!!! :)
[G2 Android Development] obito1994:
Please give me link twrp for lg g2 l01f file .img

I can't find file .img

I only find file .zip not .img to flash in Flashify
[G2 Android Development] Startrek852:
There is no img, you have to flash the zip.
[G2 Android Development] Sunandroid:
You can extract it from the zip.
[G2 Android Development] blastagator:
The flashable image is inside of the zip file, as [MENTION=5744495]Sunandroid[/MENTION] said.

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

Has anyone successfully encrypted f2fs? I know there is a big angry warning message I made because it didn't work, way back when, and led to a brick. Curious if anyone has tried it and it is working now. If so, what ROM(s)/kernel(s)?

I might try it again to see if anything has changed, when I have some free time.
[G2 Android Development] miecio92:
Please help me.

Cyanogenmode Recovery repleced my TWRP Recovery, how to flash TWRP now? AutoRec works only on stock roms, and I'm now on CM13 base rom...

I've tried to install recovery via Rashr app, but there was no TWRP, so I wanna dlash CWM Recovery and the TWRP, but now when I try go into recovery I've got certification error... :P System ups normally.
[G2 Android Development] Sunandroid:
Extract the *.img from the zip and flash twrp via flashify.
[G2 Android Development] miecio92:
Thanks! I've flashed recovery.img via Raptr and worked too :)
[G2 Android Development] captainhase:
I have a similar problem. I'm not able to flash twrp via the cyanogen recovery, flashify or twrp manager. I got a secure boot error on the lg screen with these methods. I don't want to brick my phone only because of a recovery. And, I googled raptr and found nothing helpful.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] Startrek852:
You are using TWRP from this thread, right?
[G2 Android Development] captainhase:
OK, tried again and this time it worked. Must have done something different last time.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] m890:
How to fix error createTarFork back up ended with error 255.

Plz help me?
[G2 Android Development] Quicksilver1:
Good job blastagator.
[G2 Android Development] riwan15:
Hi !

Your version 3.0.2-1 fixed my charging problem on d802 ( No charging off/recovery/on or with luck) Now i'm charging Off and in Recovery :) Thanks you !!

Have a nice day :)
[G2 Android Development] blastagator:
Try googling. The answer is literally in the first search result:

http://xdaforums.com/showpost.php?p=65173989&postcount=4
[G2 Android Development] Adil Aziz:
Hey everyone! Sorry for a stupid question but.. right now I'm running AICP 12.1. But my twrp recovery version is 2.8.7.3.. should I just install recovery image with flashify?
[G2 Android Development] Davido_96:
Flash newest version in your old twrp man.
[G2 Android Development] Adil Aziz:
Yup.. Got it. Sorry, just had a stupid confusion
[G2 Android Development] rebel377:
so ,for f2fs only need to change data amd cache? in another guide he changed all
[G2 Android Development] Startrek852:
Yes, ONLY data and cache. Do NOT change system.
[G2 Android Development] duongthinh441:
I can flash it on kitkat 4.4 and using flash 7.1 rom ???:)
[G2 Android Development] roberto32:
installed lineage OS with this version, but won't boot (certificate error)

So I tried to install the new lineage android, it went fine. But when I reboot I got the secure boot error - do I also need the flash the boot loader ( possibly bumped) ?
[G2 Android Development] hteles:
You need to bump the kernel.

Look here https://www.androidfilehost.com/?fid=673368273298919002
[G2 Android Development] roberto32:
Flash this file right?
[G2 Android Development] roberto32:
didn't work maybe need to try another bump file, which one from these http://www.gregtwallace.com/lgg2-projects/miscellaneous/ ?
[G2 Android Development] roberto32:
so I create the bump myself (just the boot.img)

here it's https://drive.google.com/open?id=0B-x5n6YYFt2dVmpyem9lZ2ZkM28 Would it be still working, it is 2 years old (the bump python script) ? anyway, when I got the bumped boot img, just replace the original boot img and then flash the that ROM (zip) with that bumped boot.img right?
[G2 Android Development] hteles:
Hi,

If you came from cm13 or later you should flash in this order.

ROM

Gapps

SuoerSu

Bumpboot.

Official G2 LINEAGEOS XDA thread is here. Read the thread, is small right now.

https://xdaforums.com/lg-g2/orig-development/rom-lineageos-14-1-unofficial-t3535119

Regards
[G2 Android Development] cemanie:
anyone can help me..i used twrp blastagator,,after flash this ROM & gapps ,reboot system...but after logo LG it going back again to twrp..

how to solve it?i have try many times,with other rom too,it can't help me..

please help me..thanks
[G2 Android Development] limpbizkit78:
Hi! I had the same problem with my D800. I had to reinstall the official stock rom. I had installed Exodus Rom 6.0.1
[G2 Android Development] ali.akbar01:
Thread states of formating data and cache partition to f2fs. What about other partitions like system?
[G2 Android Development] jeebspawnshop:
/system does not benefit from F2FS file system, so leave it as EXT4.
[G2 Android Development] ylzzirg:
3.0.2-1 zip signature verification failed

First of all --thanks blastagator for all your efforts on this! Much appreciated!

So...I was on build 2.8.7.3 but recently downloaded, verified md5, and then flashed builds (zip files) 3.0.0-4, 3.0.1-0, and 3.0.2-0 with no issues. I downloaded these from www[dot]gregtwallace[dot]com/lgg2-projects

However, when I try to flash build 3.0.2-1 I am getting a file signature error:

Zip signature verification failed!

Error installing zip file '/sdcard/twrp-3.0.2-1-d800-bump-blastagator-signed.zip'

I did verify the md5 on the file after downloading it. For good measure I downloaded it and verified it again, but still same error. Any ideas??
[G2 Android Development] Eselter:
Disable signature verification in TWRP.
[G2 Android Development] blastagator:
I thought I had them all signed correctly, but yes, if you verified the md5, turning signature verification off will do the trick.
[G2 Android Development] rebel377:
i fixed contexts and it stuck now i cant reboot recovery and my rom bootloops
[G2 Android Development] blastagator:
That is a feature that is outdated/broken in underlying TWRP and should not be used. If you flash a kernel with selinux PERMISSIVE, you should be able to boot. Reflashing ROM should fix it.
[G2 Android Development] dhiaa17:
Story if I am asking this in the wrong thread but I didn't find any answer anywhere

First I own a lg ls980(sprint version) it was on jelly bean when I got it but last year I rooted it and installed twrp(using freegee since autorec caused sofbrick to my phone) then I flashed cm12.1(android 5.1.1) and everything worked fine

Yesterday I decide to flashed cm13 or any other marshamellow based ROM so I found a post on xda (https://xdaforums.com/sprint-g2/help/sprint-lg-g2-ls980-how-to-install-cm13-t3273187) that said that the bootstack and I have to install bumped twrp(blastegator) and a hybrid bootstack(https://xdaforums.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219) so I installed bumped twrp first and everything was OK but after I installed the bootstack my phone bricked ( I got secure booting error ) I was unable to boot neither in recovery or system so I had to unbrick my phone (forcing qbulk mode and using skr tool) and reflashed a stock ROM and installed twrp and cm12.1 again

Everything work fine but I really want to to upgrade to cm13 so what should I do about the bootstack (I am sure that the problem is because of the bootstack because I tried twice and in both case my phone brick after I install the hybrid bootstack and before I install cm13)

Thanks in advance for your help :)
[G2 Android Development] runekock:
[MENTION=7914650]dhiaa17[/MENTION]

I guess that the old CM isn't bumped, and so is incompatible with the new bootloader. However, you should still have been able to start recovery using the key combination. Only the key combination may be different between the old and the new bootloader.

The other way to do it, is upgrading to the newest stock first, root and install recovery using autorec for lollipop. Then you won't have to upgrade the bootstack.
[G2 Android Development] dhiaa17:
I thought about upgrading to stock but I read somewhere on xda that cm13 require kitkat bootloader that's why I was reluctant to do that but I will try it anyway

Thank you for your help
[G2 Android Development] runekock:
Yes, the Lollipop bootloader hasn't been cracked, so all roms and recoveries require either jelly bean or kitkat bootloader. Therefore, autorec downgrades the bootloader; autorec for kitkat downgrades it to jelly bean, while autorec for lollipop downgrades to kitkat. Most of the rest of the bootstack should be lollipop, however. So if you can find the proper autorec, that is the easiest, because it knows just what to do.

The kitkat bootloader is the one that requires bumping. The earlier hack (Loki) used for the jelly bean bootloader no longer works.
[G2 Android Development] dhiaa17:
Oh I understand now and I will give it a try

Thanks
[G2 Android Development] InsideMuz:
Will TWRP 3.1.0 be supported?
[G2 Android Development] blastagator:
BETA RELEASE 3.0.3-a

NOTE: This is in between "official" releases. A lot of new features have been implemented, but I don't have a list. Also, since it is in-between, there may be some incomplete features or minor kinks.

Device tree updated to CM-14.1

Feedback: Specifically, please let me know if your VARIANT is working. All should be working, but I can only test d800.

Also, if you know you are on the old bootloader, please let me know if that works.

Have fun, all!

http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.0.3-a

------

Original Post:

I have updated everything to cm-14.1 sources. I am going to run a beta build today or tomorrow and post for everyone to BETA TEST.

I think I've covered everything, but we will see.

I had to trim kernel down a lot, so I need to make sure all variants work. I also changed the way support is added for JB bootloader, so I will be specifically interested in confirming JB works, as well as confirming all variants work.

Since this will be a release in between official TWRP versions, things may be incomplete/weird/broken, but nothing major that I'm aware of. Stay tuned.

---------------
[G2 Android Development] krija:
Thanks for your work. Here is everything ok [D802].
[G2 Android Development] Hiyaslalabs:
While I was in Cloudyg2 3.3, I updated twrp to bump. Rebooted to twrp, did a full wipe, flash rom(7.1) gapps and bootstack. Then rebooted to a secure booting error. I did this procedure with a MM rom & it worked on my D802. What could be wrong?
[G2 Android Development] andh1ka:
The rom might need 'bump'
[G2 Android Development] Startrek852:
You need to download blastagator's bumpboot zip from here: http://www.gregtwallace.com/_privat...igned.zip&type=miscellaneous&version=bumpboot then flash it.
[G2 Android Development] Hiyaslalabs:
When will I flash that bump boot on the correct procedure? Thanks
[G2 Android Development] Startrek852:
Flash it last.
[G2 Android Development] kopitaneskita:
[MENTION=5031300]blastagator[/MENTION]

thank you for the latest beta release, really appreciate it :good::good::good:
[G2 Android Development] coolhandfluke:
BETA RELEASE 3.0.3-a

[MENTION=5031300]blastagator[/MENTION]

I have installed BETA RELEASE 3.0.3-a on a d802 without encryption.

A backup initiated in ROM manager worked as expected and the restore was fine. All previous changes to default settings have been retained. Everything seems to be working as expected.

Thank you for all your work.

Edit - I'm on a lollipop bootloader

ROM and gapps flashed OK as well
[G2 Android Development] js290:
Anybody else noticing with 3.0.2-1 for d800, that it takes multiple attempts to sideload before adb recognizes the device is in sideload?
[G2 Android Development] melezz:
Hi everyone,im on stock kitkat and i want to try twrp using Autorec,my question is,Autorec flash witch kernel?and if its affect battery life or it flash the same stock kernel?
[G2 Android Development] jeebspawnshop:
Autorec does not flash a kernel.

It flashes a recovery.

The two are entirely separate entities.

I would STRONGLY suggest that you do some reading on the nature of recoveries (such as TWRP) and the nature of kernels (such as Dorimanx, Lambda, etc), as you clearly have little / no knowledge of fiddling with Android systems.

If you do not educate yourself before proceeding, you will find yourself with a softbricked phone and no skills with which to fix it.
[G2 Android Development] melezz:
Thank you very much for your quick answer,but here in this picture,it say flashing kernel?.And my question is what is lokifying boot and recovery?What is Loki?
[G2 Android Development] rd.nary95:
It flashes a customised kernel so that you can reboot back into the stock recovery.

Loki is the name of the workaround used to bypass the Jellybean bootloader and allow custom kernel and recoveries to be flashed. For Android 4.4, Autorec would downgrade the bootloader so it can utilise the Loki bypass and then flash a kernel to avoid bootloop from the changes made.

EDIT - Correct me if I've missed anything
[G2 Android Development] melezz:
Thank you for your answer.Then if i flash Autorec then i will lost my stock kernel?Witch custom kernel Autorec flash on my phone?It will affect my battery life?
[G2 Android Development] rd.nary95:
It's a similar kernel that's just has the patches to work with the stock ROM and it shouldn't affect your battery life
[G2 Android Development] Startrek852:
It's the exact same kernel, it's just modified so that you can actually boot after downgrading the bootloader.
[G2 Android Development] kolouch.petr:
TWRP bootloop after upgraded LineageOS

I tried to OTA Lineage OS and since I did it I got bootloop to TWRP. I tried to wipe everything and then I installed clean Lineage OS for my LG D802.

No help, I get boot lop even updated TWRP to the latest 3.0.3-a (originally I had 3.0.2-1)

My phone is useless since I "updated"lineage os . any help ? thank you
[G2 Android Development] xNotta:
Has the 2014.10.25 (2.8.1.1) version for the LS980 destroyed anyone's phones?

(I remember a recovery for an HTC EVO that perm bricked a bunch people's phones and I want to be safe and just make sure before I flash.)