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

Search This thread
Just formatted a 64gb sd card, am backing up my internal storage(pics, music, TWRP backups, etc.) I never restore rom data, settings, system apps/data or anything like that- Tibu taught me the hard way haha so after the usb backup is finished, flash image and format? Then flash my rom of choice and plug in my usb otg and copy it all back to my phone correct? Or am I missing a step?
 

je2854

Senior Member
Oct 3, 2010
1,013
324
Houston, TX
Just formatted a 64gb sd card, am backing up my internal storage(pics, music, TWRP backups, etc.) I never restore rom data, settings, system apps/data or anything like that- Tibu taught me the hard way haha so after the usb backup is finished, flash image and format? Then flash my rom of choice and plug in my usb otg and copy it all back to my phone correct? Or am I missing a step?

backup /data/userdata on an OTG, edit NETA-INF in install script of ROM, format /system and /cache to F2FS, install ROM AND kernel reboot.
In that order...
You cannot install and then convert as it formats the fresh install.
 

je2854

Senior Member
Oct 3, 2010
1,013
324
Houston, TX

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
VS980 zip failed to flash for me.
Code:
assert failed: run_program("/tmp/loki.sh") == 0

/tmp # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2014-10-20 21:49 loki
-rwxr-xr-x root root 417 2008-08-01 12:00 loki.sh
-rw-rw-rw- root root 16532 2014-10-20 21:50 recovery.log
-rwxr-xr-x root root 283576 2014-10-20 21:49 updater

/tmp # sh -x loki.sh
+ dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/tmp/loki/aboot.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.133037 seconds, 7.5MB/s
+ /tmp/loki/loki_patch recovery /tmp/loki/aboot.img /tmp/loki/recovery.img /tmp/loki/recovery.lok
[+] loki_patch v2.1
[-] Unsupported aboot image.
+ exit 1
 

blastagator

Inactive Recognized Contributor
Dec 27, 2012
1,288
4,707
Fern Park, FL
VS980 zip failed to flash for me.
Code:
assert failed: run_program("/tmp/loki.sh") == 0

/tmp # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2014-10-20 21:49 loki
-rwxr-xr-x root root 417 2008-08-01 12:00 loki.sh
-rw-rw-rw- root root 16532 2014-10-20 21:50 recovery.log
-rwxr-xr-x root root 283576 2014-10-20 21:49 updater

/tmp # sh -x loki.sh
+ dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/tmp/loki/aboot.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.133037 seconds, 7.5MB/s
+ /tmp/loki/loki_patch recovery /tmp/loki/aboot.img /tmp/loki/recovery.img /tmp/loki/recovery.lok
[+] loki_patch v2.1
[-] Unsupported aboot image.
+ exit 1

Is your time set correctly (and your time zone) in your existing recovery?
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
Is your time set correctly (and your time zone) in your existing recovery?

Yes. Time is accurate, not using 24-hour clock, time zone is right and use DST is checked.

Sorry, but I've got to commute home from work now. Won't be able to get back on xda until later tonight, maybe 9:30 Central time. Will be happy to continue troubleshooting then.
 

blastagator

Inactive Recognized Contributor
Dec 27, 2012
1,288
4,707
Fern Park, FL
Yes. Time is accurate, not using 24-hour clock, time zone is right and use DST is checked.

Sorry, but I've got to commute home from work now. Won't be able to get back on xda until later tonight, maybe 9:30 Central time. Will be happy to continue troubleshooting then.

Ok. When you get home let me know what recovery you are using currently.
 

dorimanx

Senior Member
Feb 20, 2010
12,716
93,528
TERA Prime.
www.dorimanx.com
So I formatted my /data partition to F2FS and am getting the encryption unlock prompt as well. I verified that data_system.sh and init.g2.rc existed on my phone beforehand. I think the problem is that since /data is now F2FS it doesn't mount properly since fstab.g2 is still trying to mount it ext4 and so it assumes it must be encrypted.

I know I can go back to ext4 but I really want to get to F2FS. Can someone please tell me how to permanently change /fstab.g2? It gets replaced at each boot via some method that I am not familiar with.

This is on VS980 running CloudyG3 2.0 and Dorimanx kernel 8.5. Thanks in advance!

Open the file and look, there is no more data mount inside when your partition is f2fs before you post an wrong info without even check it.


Sent from my LG-D802
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
Ok. When you get home let me know what recovery you are using currently.

I am using your TWRP 2.8.0.2 I loki_flashed earlier today from your .img you posted this morning. I will be online later.

Open the file and look, there is no more data mount inside when your partition is f2fs before you post an wrong info without even check it.

Sent from my LG-D802
Sorry, dori, I don't know what you mean. After formatting /data to F2FS I made sure it was mounted and I adb pushed my pics, media, tibu files back into it before attempting to reboot. Adb wouldn't connect when it was at the encryption PIN screen so I couldn't tell what was mounted. I know it couldn't have been mounted though because fstab.g2 has ext4 as its type and it was F2FS at that point. That mount attempt would have failed and I just made an assumption that that was why I was getting the encryption PIN screen because it is the only time I've ever seen it.
Sorry if what I said came across as anything other than an honest (albeit clumsy) attempt to contribute to this effort.
 
Last edited:

luv2increase

Senior Member
May 22, 2010
710
144
Yes. Time is accurate, not using 24-hour clock, time zone is right and use DST is checked.

Sorry, but I've got to commute home from work now. Won't be able to get back on xda until later tonight, maybe 9:30 Central time. Will be happy to continue troubleshooting then.

Vs980 working great here with 2.8.0.2!!

You must use flashify app and flash the .img in android
 

blastagator

Inactive Recognized Contributor
Dec 27, 2012
1,288
4,707
Fern Park, FL
I am using your TWRP 2.8.0.2 I loki_flashed earlier today from your .img you posted this morning. I will be online later.

A) If you're already using the most recent version, why are you trying to reinstall it? :p

B) I installed the vs980 zip on my phone successfully, but since I have a d800, I obviously couldn't boot it. However, flashing within TWRP worked fine.

I messaged one of the other vs980 users to see if they have same problem before trying to diagnose further.
 
Last edited:

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
I am using your TWRP 2.8.0.2 I loki_flashed earlier today from your .img you posted this morning. I will be online later.

A) If you're already using the most recent version, why are you trying to reinstall it? :p

B) I installed the vs980 zip on my phone successfully, but since I have a d800, I obviously couldn't boot it. However, flashing within TWRP worked fine.

I messaged one of the other vs980 users to see if they have same problem before trying to diagnose further.

LOL, I know it's really derpy to install the same version over the top. It's half OCD and half best practice. I thought it would be good to keep the zip around in case some future twrp zip failed for some reason I'd have this version on my phone already and could just flash it back. And I thought well I'd better test it first...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 380
    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://xdaforums.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 greg@gregtwallace.com

    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
    71
    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://xdaforums.com/lg-g2/general/twrp-poll-aroma-t3372512


    April 30, 2016
    Release candidate! Give it a test!
    http://xdaforums.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



    .
    62
    November 9, 2015 (2.8.7.3)

    November 9, 2015 (2.8.7.3)
    -Sorry about bad 2.8.7.2 build :(
    -Still built off of omni-4.4 source code. (Android-M isn't ready for a full release yet.)
    -Vendor: Complete overhaul of vendor blobs, now using cm-12.1-caf branch from lg-devs
    -TWRP: Make separate flags for ability to backup or restore partitions
    -Device: Add ability to backup/restore Bootloader partitions
    ++User cannot use TWRP to restore Bootloader, too dangerous!
    -Device: Removed system_image
    ++We don't need this for our phone and it was confusing people who didn't READ the change log
    -TWRP/Device: Remove any warnings about system mount RO, this isn't important for our phone
    -Device: Set max brightness to actual max (255)
    -Device/TWRP: Create default brightness, set it to 175 (~68%)
    -Kernel: Latest f2fs driver
    ++This should fix issue where ROM running kernel with newest f2fs doesn't boot
    ++Note: This breaks compatibility with ROM using old f2fs driver. Read note below.
    -Kernel: Other commits that were needed to make latest f2fs driver work
    -Kernel: Config changes that might allow encrypted f2fs to work now!
    -Kernel: Enable SELinux
    ++Before I accidentally completely disabled, now it should boot Enabled, but in Permissive mode.
    -TWRP: More tweaking to recreation of media folder / setting internal storage path
    -Device: Remove integrated supersu

    IMPORTANT - f2fs /data note: If you restore OLD backups, you will probably cause ROM or recovery (or both) to hang! This is obviously bad because your only option at that point is doing a back to stock kdz. To avoid problems, make NEW backups AFTER upgrading to the new version of TWRP. Backups made with 2.8.7.3 can be restored with 2.8.7.3 without causing issue.


    All should work fine. Should be a safe build again. I did make some changes to the actual TWRP code & submitted patches to their gerrit, but I am fairly confident we're back in business.

    Also of note - I can't believe it has been a year since I started this project!
    56
    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://xdaforums.com/showpost.php?p=66747442&postcount=2591
    56
    2.8.5.0 is out. I will compile today after work.