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

Search This thread

Sebba513

Senior Member
Feb 28, 2013
79
6
So is there any ROM which doesn't format system while installing? To create a "full" f2fs device?
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
Edit: NVM. I forgot on this device you have to use loki to flash. Re-reverse-engineered a 2.7 zip I had to get it installed. All good. Running properly on vs980. Thanks!
 
Last edited:

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
So is there any ROM which doesn't format system while installing? To create a "full" f2fs device?

They've done some benchmarking on the nexus 10 and the general consensus is that since /system is read-only, reads are faster on ext4, and most ROM installers format /system specifically as ext4, it is just easier to run only /data and cache as F2FS. Otherwise (until F2FS is more widely adopted) you're stuck hand-editing system-updater scripts if you really want /system to be F2FS.
 
  • Like
Reactions: Sebba513

luv2increase

Senior Member
May 22, 2010
710
144
They've done some benchmarking on the nexus 10 and the general consensus is that since /system is read-only, reads are faster on ext4, and most ROM installers format /system specifically as ext4, it is just easier to run only /data and cache as F2FS. Otherwise (until F2FS is more widely adopted) you're stuck hand-editing system-updater scripts if you really want /system to be F2FS.
So does that mean we should be able to install any ROM and just format data and cache as F2FS? Doesn't the Rom still have to be F2FS compatible? Also, won't the ROM when installi g automatically format the cache and data as ext4? How to stop this? You said edit updater script. Could you PLESSE give us an example?
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
So does that mean we should be able to install any ROM and just format data and cache as F2FS? Doesn't the Rom still have to be F2FS compatible? Also, won't the ROM when installi g automatically format the cache and data as ext4? How to stop this? You said edit updater script. Could you PLESSE give us an example?

I don't think any ROM's format cache and /data. You have to do those yourself. As for editing the updater script, that involves unzipping the ROM and editing the META-INF/com/google/android/updater-script file to not mkfs.ext4 /system and also mount /system as F2FS then re-zipping. That's real easy to mess up so good luck. Make a backup of the ROM file before you update it just in case.
 
Last edited:

luv2increase

Senior Member
May 22, 2010
710
144
I don't think any ROM's format cache and /data. You have to do those yourself. As for editing the updater script, that involves unzipping the ROM and editing the META-INF/com/google/android/updater-script file to not mkfs.ext4 /system and also mount /system as F2FS then re-zipping. That's real easy to mess up so good luck. Make a backup of the ROM file before you update it just in case.
I just wiped cache and dalvic cache and changed the /cache partition to f2fs and rebooted. Everything is working fine and cache held up as f2fs.

Now, if in twrp I formatted the /data partition as f2fs, would all my contents on my internal sdcard such as pictures etc be deleted as well? I want to set it up where my /cache and /data partitions are f2fs and /system is ext4
 

je2854

Senior Member
Oct 3, 2010
1,013
324
Houston, TX
So is there any ROM which doesn't format system while installing? To create a "full" f2fs device?

What ROM is it and i can convert it for you

---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------

I just wiped cache and dalvic cache and changed the /cache partition to f2fs and rebooted. Everything is working fine and cache held up as f2fs.

Now, if in twrp I formatted the /data partition as f2fs, would all my contents on my internal sdcard such as pictures etc be deleted as well? I want to set it up where my /cache and /data partitions are f2fs and /system is ext4

DANGER WILL ROBINSON! DANGER!
I formatted my /data partition to F2FS and lost ALL my internal data as well!
DO. A. BACKUP!
 
  • Like
Reactions: dredq

luv2increase

Senior Member
May 22, 2010
710
144
What ROM is it and i can convert it for you

---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------



DANGER WILL ROBINSON! DANGER!
I formatted my /data partition to F2FS and lost ALL my internal data as well!
DO. A. BACKUP!
So I will have to adb sideload all my data back then?
 

dorimanx

Senior Member
Feb 20, 2010
12,716
93,528
TERA Prime.
www.dorimanx.com
What ROM is it and i can convert it for you

---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------



DANGER WILL ROBINSON! DANGER!
I formatted my /data partition to F2FS and lost ALL my internal data as well!
DO. A. BACKUP!

Data destruction should be acknowledged before doing format and rewrite to other partition.

Process is not converting, its formatting.

So for people that dont know this, we should put a huge warning in OP and if possible in recovery before wipe trigger.



Sent from my LG-D802
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
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!
 

b1g.p0ppa

Senior Member
Feb 26, 2011
974
308
Roam
@luv2increase "So I will have to adb sideload all my data back then?"

I wonder if you backup everything via USB OTG prior to flashing the new recovery img- if restoring afterwards would end up working out alright???

I don't have a computer to recover from potential brickage issues so it's a bit of a gamble for me haha

Any input would be appreciated

Depends on what you mean by "everything". If you're just trying to save pics and media that should work. If you're trying to retain your whole ROM, apps and settings then I wouldn't think it would work.
 

je2854

Senior Member
Oct 3, 2010
1,013
324
Houston, TX
So I will have to adb sideload all my data back then?

Sideloading your personal data is an option.
Back it up BEFORE you convert.





So for people that dont know this, we should put a huge warning in OP and if possible in recovery before wipe trigger.

Do we HAVE TO? I mean it would stupid proof things for the most part. Do you think that it's spoon feeding?


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.

A couple of post back @dorimanx and i have noted that /data partition is not a viable partition to convert [yet].
Please only use /system and /cache as F2FS and keep /data either EXT3 or EXT4 to avoid complications.



@luv2increaseI wonder if you backup everything via USB OTG prior to flashing the new recovery img- if restoring afterwards would end up working out alright???

BEFORE any conversions are done please backup or remove ANY SDCard data you do not want to lose on an OTG and then convert then 'copy' back. But /data will not work on F2FS as of yet.

P.S. i put copy in ' ' because on the past I've learned to copy instead of move... It saves the hassle of recopying after testing.
 
  • Like
Reactions: b1g.p0ppa

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.