[TWRP][3.3.1-0][BUMP][All Models] TWRP w/ Thermal F2FS [2019.12.23]
- Thread starter blastagator
- Start date
@dorimanx sorry bodering you but i saw all this thread and saw your words about you bump some images for your people and saw some people saying that already using the "bumped" bersion maded by you, where can i find it? (if is that real).
http://dorimanx.shine.sk/LG/
under the page, there are bumped kernels, but not latest, they are 2.8.1.1. im using without any issue.
so thats the point, i though those people were running the latest, i already got the early versions, thanks for this information.
Link Disabled
Your drop box link has been disabled and I'm unable to open the google drive files.
Your drop box link has been disabled and I'm unable to open the google drive files.
Ya you guys are hitting my dropbox hard
DL from the download tab if you can't get either to work.
Finally found my device tree problem. New builds will almost certainly be out tomorrow.
Great, please make it bumped!
Thanks for our time and effort on this!
Enviado do meu LG-D802 através de Tapatalk
To DEV
here is the way to sign the recovery with LG keys for original JB/KK bootloader.
LOKI is no longer needed.
https://github.com/dorimanx/Doriman...mmit/71546ca4c587e5e57412234c8e3b51f09146801e
have fun. you can BUMP all of your images, and forget about loki.
Attached my work folder.
this is not for USERS!!! dont ask how to use if you cant understand.
it's for DEV.
Correct me if I'm wrong but it looks like that script would bump the img and then still use the loki flashing script. So the image would actually be bumped, then loki'd, and then flashed.
I'm thinking I should take out the loki script and just use the part that correctly selects the LCD Panel type.
Edit: I took the loki stuff out and left a tweaked panel script. Bumped 2.8.2.0 is up and running. I promise all builds will be up soon
Last edited:
Thank you for releasing latest TWRP but...
But... I m so sorry. I m L01f(japan) user. So how can I get to port this latest twrp(?) could i take some information(?)
This is my email: [email protected]
Thank you.
But... I m so sorry. I m L01f(japan) user. So how can I get to port this latest twrp(?) could i take some information(?)
This is my email: [email protected]
Thank you.
This is on my to-do list. I recently found a git with the vendor blobs. I hope to work on this after I get the new bump'd build out on all the other models.
The problem is, this has nothing to do with your recovery at all and this is what this thread is about.
Ask in your ROM's thread.
from OP
If you want bump, go bump yourself.
that is FUNNY! you made me laugh :laugh:
If you want bump, go bump yourself.
that is FUNNY! you made me laugh :laugh:
Dec 6, 2014 (2.8.2.0)
-Reworked all device trees to use the CM stock device trees + a couple mods to add TWRP support.
-Still using the Omni4.4 source.
-BUMP'ed and new flashing script that still auto-detects panel type but does NOT use loki.
++Bump works on JB & KK bootloader.
-All the other goodies as listed in 2.8.1.9.
-If you're on d800 and want to upgrade to KK bootloader, go here.
-Reworked all device trees to use the CM stock device trees + a couple mods to add TWRP support.
-Still using the Omni4.4 source.
-BUMP'ed and new flashing script that still auto-detects panel type but does NOT use loki.
++Bump works on JB & KK bootloader.
-All the other goodies as listed in 2.8.1.9.
-If you're on d800 and want to upgrade to KK bootloader, go here.
Last edited:
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
376Welcome 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-3171Announcements
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
.62November 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!56FAQ
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=259156
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone