[TWRP][3.3.1-0][BUMP][All Models] TWRP w/ Thermal F2FS [2019.12.23]

blastagator · Oct 8, 2014

Welcome to TWRP with F2FS & Thermal Control!
---- Supports Models d800/1/2/3/4/5, LS/VS-980, L01F, lgl22, and F320* ----
(for d804/5 use the d802 version)

Do NOT post a question if you don't read the first FIVE posts of this thread!!!

Features:
Added: Thermal control, thanks to using AICP kernel. [originally dr87's idea]
Added: As of 3.0.2-1: Using modified cm-13 kernel with my additions of thermal and other changes.
Added: As of 3.1.0-0: Using modified cm-14.1 kernel with my additions of thermal and other changes.
Added: Full F2FS support, including updated driver and f2fs-tools.
NOTE: You must NOT have "Use rm -rf instead of formatting." in the Settings page. If you have this option enabled, you will not be able to change partition type.
Added: Proper support for f320 & lgl22 External SD Card.
Added: Tap to wake.
Added: NTFS support.
Added: Working decryption support.
DO NO ENCRYPT f2fs - Bootloop of ROM and Recovery will occur!
Added: AROMA hack to fix graphics.
Uses: dr87's auto-select correct panel type.
Uses: Bump (So loki isn't needed)
& All of the goodies that already come packed in to the latest version of TWRP!

Please enjoy this recovery and I encourage feedback!!!

F2FS Information:
Clicky Clicky (or scroll down to post #5)

Bugs/Issues:
TWRP Issues, Generally:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues
https://github.com/omnirom/android_bootable_recovery/issues

Major Thanks to:
TWRP Team
Dees_Troy
OmniRom Team
Cyanogenmod Team
Drgravy
Team Codefire
Dorimanx
jakew02
dr87
Khaon
bart452
xiaolu
Yoinx
And everyone else involved with these projects!

Installation:
1) First, you need any version of TWRP installed and working:
I'd recommend using Autorec to get initial TWRP running.
This is the link for KK: http://forum.xda-developers.com/showthread.php?t=2715496
There is also an apk for lollipop, this is much preferred! (Google is your friend.)
You can use any number of other methods to get some version of TWRP installed and running.
2) Once you have a working TWRP, simply flash my zip to upgrade to latest version.
If you flash the image directly, the panel detection script will not run!
(This is only important if you have a jdi LCD panel.)

Troubleshooting:
If you have any issues, please try the Official Build and compare to check that bug is only present in my version. If it is present in both versions, report it to TeamWin or Dees_Troy. If it only bugs in my version, please let me know ASAP.

Also, please check FAQ before asking questions. Thanks!

Download:
https://www.gregtwallace.com/lg-g2/g2-twrp/
Downloads are installable zip files, the images inside of which are already BUMPed.

Sources:
https://github.com/blastagator
Source Readme:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-13.0-twrp/README.md

Shameless plug for donations:
Venmo Preferred (No Fee)

Zelle, send to [email protected]

Backup (Charges Fee)
Paypal

XDA:DevDB Information
TWRP Touch Recovery w/ Thermal Control and F2FS, Tool/Utility for the LG G2

Contributors
blastagator, TeamWin, and everyone else listed above!

Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-12-23

Created 2014-11-02
Last Updated 2019-12-31

blastagator · Oct 8, 2014

Announcements

May 7, 2016
New CM-13 based build is released! Enjoy all.

May 4, 2016
New release coming this weekend. Make any complaints ASAP about version -g!
VOTE on if you want me to TRY to fix AROMA. (No guarantees!!!)
http://forum.xda-developers.com/lg-g2/general/twrp-poll-aroma-t3372512

April 30, 2016
Release candidate! Give it a test!
http://forum.xda-developers.com/showpost.php?p=66626361&postcount=2543

April 17, 2016
New beta using cm-13 sources. Click HERE. Please test!

April 7, 2016
TWRP 3.0.0-2 is here! Versions older than 2.8.7.3 have been removed from my download site.

February 17, 2016
(Working!) TWRP 3 is here!
More info: https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html

.

blastagator · Oct 8, 2014

Change Logs

December 23, 2019 (3.3.1-0)
-TWRP Change Log:

* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff

April 29, 2019 (3.3.0-0)
-TWRP Change Log:

* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)

September 22, 2018 (3.2.3-0)
-TWRP Change Log:

* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files

July 21, 2018 (3.2.2-0)
-TWRP Change Log:

adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations

December 17, 2017 (3.2.1-0)
(Bug fixes for 3.2.0)
-TWRP Change Log:

minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

-TWRP 3.2.0-0 Change Log:

Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks

December 3, 2017 (3.2.0-0)
Removed and replaced with 3.2.1-0

May 20, 2017 (3.1.1-0)

March 13, 2017 (3.1.0-1)

Rebuild of 3.1.0-0 (from 2017.03.10) - Add ability to boot with JB bootloader.
-TWRP Change Log:

-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention

-Tree
++Bootloader offset is now 128!
If you are having OTA problems, make sure your ROM maintainer adds this to their device tree: https://github.com/blastagator/cm_d...mmit/946434d0881b50437422e7855d5d7a096d9608e1
Also, /misc needs to be mounted: https://review.lineageos.org/#/c/19334/)
++Completely rebased onto cm-14.1
++Remove custom USB - Use G2+TWRP usbs instead
++Tweaks to enable compatibility with old bootloader
-Kernel
++Completely rebased onto cm-14.1
++Tweaks to enable compatibility with old bootloader
++Disable lots of unneeded things and changed kernel compression

------------- All builds above this line are cm-14.1 based. -----------------
------------- All builds below this line are cm-13 based. -------------

May 7, 2016 (3.0.2-1)

------------- All builds above this line are cm-13 based. -----------------
------------- All builds below this line are omni-4.4 based. -------------

April 7, 2016 (3.0.2-0)

February 17, 2016 (3.0.0-4)

November 9, 2015 (2.8.7.3)

October 31, 2015 (2.8.7.2)

June 24, 2015 (2.8.7.1)

May 25, 2015 (2.8.6.3)

Much Older Versions:

blastagator · Oct 8, 2014

FAQ

My OTA isn't working or I am now in a bootloop to TWRP.
To get out of the bootloop, connect to adb shell, and issue:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This should resolve the problem. If not, search the thread, some people have other suggestions for various places to nuke the bad commands residing in /misc. To avoid the future problem, contact your ROM maintainer with the following info.
Starting in Android N, the ROM uses /misc partition to communicate with recovery. (Therefore if your ROM is M or lower, OR uses the old communication method, this is not relevant to you). To address OTA problems, it is important to note the newly introduced bootloader offset.
https://review.lineageos.org/#/c/165001
Also, /misc needs to be mounted:
https://review.lineageos.org/#/c/19334/
Your ROM maintainer should add these to their device tree. This will insure that ROM will write to the exact place the recovery is reading from.

I see error: "E: mount -0 bind '/data/media' '/sdcard' process ended with error=255" when I switch partition type on /data.
Update to new version, 2.8.7.1. This problem is fixed.

I see error: "assert failed: run_program(" /tmp/loki.sh") == 0" when I flash X. Why?
Loki is only supported by JB BL. Loki is smart enough to check your BL version before flashing. If you are on KK BL and the thing you are flashing uses loki, you're going to get this error. New BL requires you to use bump.

Now that I have bump, how do I update to the KK bootloader?
If you have a d800 (or d801), see my thread here. If you have a d802, see @dorimanx's thread, here. Credit's to dori for inspiring me to make the package for d800.

USB-OTG isn't working, why not?
To use USB-OTG your device needs to be formatted fat32, not NTFS.

I'm having trouble formatting partitions. Why doesn't it work?
Fixed: As of 2.8.3.1
The option to Format Data or do Factory Reset probably won't work. The fstab is set to auto to support f2fs and those two options don't know how to deal with auto (they don't know if you want them wiped to ext4 or f2fs). Therefore, you need to do Advanced Wipe, which works fine. If you are still having trouble, make sure MTP isn't on and make sure your USB isn't plugged in.

OMG, my TWRP thinks this is the 1970s?! HALP!
This is an issue that arises in Android L (for whatever reason). Member murdoch1 found this and confirmed that installing it fixes the 1970 issue in TWRP.

Does [xyz] work?
As far as I know, everything works except for known issues in the common twrp source.

I want to report [xyz] as not working, how do I do it?
Post in this forum. I'll do what I can to fix it.

When will the next version come out?
I don't plan on building again unless a bug is discovered that I can fix, or if TeamWin releases the next version.

Why don't you do [xyz]?
Why don't you do it?

Why doesn't F2FS work?
It DOES work in the recovery. To get it working on your ROM you need to have proper kernel support. Many AOSP ROMs support f2fs partitions. Additionally, dorimanx has added working f2fs on his stock kernel.

Why doesn't AROMA work?
AROMA is old. As of version 3.0.2-1, I added a hack to fix the graphics. If your zip file still isn't working, try my guide:
http://forum.xda-developers.com/showpost.php?p=66747442&postcount=2591

blastagator · Oct 8, 2014

F2FS Information

WARNING: Changing Partition type of /data WILL wipe ALL data, including INTERNAL SD!
You need to specifically backup Internal SD, TWRP does not automatically do this when you backup /data!
(This only applies if you change from ext4 to f2fs, or vice versa; other operations will not magically wipe your partitions.)

WARNING 2: DO NOT ENCRYPT F2FS - ROM and RECOVERY will BOTH bootloop and you'll be doing back to stock method!!!

If you want to use F2FS:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
4) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
5) Reboot OS. That's it! You're ready to go.

If you want to switch to F2FS without losing your data:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Make a backup of your /data partition and copy it to your PC via MTP. Also, copy the content of your /sdcard to your computer. Both of these things will be destroyed when you switch partition type!
4) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
5) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
6) Copy your backup via MTP to your phone. Restore your /data partition.
7) Copy your sdcard files back to your sdcard. (NOTE: For some reason, when I do this, the files end up getting deleted, you may need to copy the sdcard files over after your reboot into your OS.)
8) Reboot OS. That's it! You're ready to go.

Don't complain if you didn't read everything in all 5 of these posts!

EniGmA1987 · Oct 8, 2014

Very nice! Im glad to see more work being done to bring F2FS to the G2. I dont know enough about getting into the ROM and kernels to get this going myself, but I will be following the development more closely now and hope someone else is gracious enough to port one of the stock based ROMs to work with F2FS. I think I remember seeing Dorimanx kernel has support for the file system already too, just no recovery or ROM that was capable at the time.

Yoinx · Oct 8, 2014

blastagator said:
Problem: We need a kernel/ramdisk that will mount the partitions in a ROM!
On my ROM I am using Dori's kernel with which has the f2fs module. However, even though it has the module, the /cache partition does not mount when the rom boots. Perhaps a ramdisk fstab issue? - Possibly my next adventure...

You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.

https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2

You'd probably need to add it with these, though I'm unsure why it's not already listed. It may be in the built ramdisk, built into the file during the compile... It may also be mounted after boot in one of the .rc scripts... But I'm used to seeing all the partitions laid out in the fstab on previous devices.

Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?

blastagator · Oct 8, 2014

Yoinx said:
You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.

https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2

I was thinking modify the fstab. However, in dori's kernel, the fstab.g2 doesn't even have entries for /system /data or /cache. In the recovery I changed those partitions from ext4 to auto. I planned to do the same on the kernel. Even though the fstab is different, I was going to try adding mounts for those 3 partitions and see what happened. However, I couldn't get the image repacked. I used the non-standard mkbootimg from the compiling of the recovery. I tried several different commands to repack - all of which led to a boot loop. (Except one, which got me fastboot because the offsets were wrong.)

Alternatively I was going to recompile the dori kernel but I haven't really delved into adding the custom ramdisk into that compile, got too tired last night.

Yoinx said:
Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?

Using: mount -t f2fs /dev/block/platform/msm_sdcc.1/by-name/cache /cache
The partition mounted properly using the dori's build of dori's kernel 8.0.1

Yoinx · Oct 9, 2014

You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.

Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily

blastagator · Oct 9, 2014

Yoinx said:
You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.

Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily

Dori was nice enough to point it out for me:

https://raw.githubusercontent.com/dorimanx/LG-G2-D802-Ramdisk/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/init.target.rc#L45

I plan to fiddle with it

Yoinx · Oct 9, 2014

Simple enough. They're just running it in the scripts then. I modified my old phone's kernel to have simulated run levels by running a script from each of the points in the init.rc events, so you could run commands at various points throughout the boot sequence via init.d essentially. I liked the feature, but I don't think many others really had a use for it.

Same concept, the only downside by it being hard-coded is that you need to repack each time instead of just modifying an init.d script on the fly.

Glad you found it though

blastagator · Oct 9, 2014

Yoinx said:
You can get something like kernel workshop

Try googling "kernel workshop" --- grumble

Yoinx · Oct 9, 2014

Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...

http://forum.xda-developers.com/showthread.php?t=2073775

It's android image kitchen. I had the wrong name.

blastagator · Oct 9, 2014

Yoinx said:
Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...

http://forum.xda-developers.com/showthread.php?t=2073775

It's android image kitchen. I had the wrong name.

Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!

Yoinx · Oct 9, 2014

blastagator said:
Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!

Interesting. I haven't started really building anything for the G2 yet.... not enough time IRL at the moment. When I flash kernels though, it's just boot.img.

What's this dt.img that you're talking about? The non-standard mkbootimg is typically just just for offsets.

You may be better off just downloading the kernel sources and building from scratch if the imgtools dont work.

Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)

blastagator · Oct 9, 2014

Yoinx said:
Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)

You sir are a god send! Unpacked the Dori kernel, repacked, and the repacked image booted right up!!! I'll be sure to update if I make any headway with automount

blastagator · Oct 9, 2014

Oct 8, 2014 Build
-Fully sync'd everything to the above listed gits
-Moved the tap to wake code out of bootable/recovery and into a custom recovery init.rc
-Moved a couple files into g2-common/twrp folder to improve organization
-Sync'd with main repo to get any code changes and confirm the init.rc wasn't causing issues anymore
-Posting this build in .img and .zip format

Signed Zip: https://www.dropbox.com/s/sd1lo0mijouu6kg/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs-signed.zip?dl=0
Zip MD5: https://www.dropbox.com/s/xmw5e4pzw...gator-twrp-2.8.0.0-w.f2fs-signed.zip.md5?dl=0
Img: https://www.dropbox.com/s/gmzfyg7rs8guw1m/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs.img?dl=0

blastagator · Oct 11, 2014

Oct 10, 2014 Build
-Full repo sync.
-Changed vendor tree from a CM11 build that I had been using to dr87's git.
-Built for (almost) all LG G2 models.

blastagator · Oct 11, 2014

-deleted- (double post)

je2854 · Oct 11, 2014

Your title for the OP says it is for the vs980 as well...
I don't not see a link for it though

[TWRP][3.3.1-0][BUMP][All Models] TWRP w/ Thermal F2FS [2019.12.23]

Inactive Recognized Contributor

Inactive Recognized Contributor

Inactive Recognized Contributor

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Yoinx

Guest

Inactive Recognized Contributor

Yoinx

Guest

Inactive Recognized Contributor

Yoinx

Guest

Inactive Recognized Contributor

Yoinx

Guest

Inactive Recognized Contributor

Yoinx

Guest

Inactive Recognized Contributor

Inactive Recognized Contributor

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Similar threads

Top Liked Posts