[Recovery][Unofficial]TWRP 3.3.1-1 : 2019-10-25

Search This thread

Phoenix591

Senior Member
Oct 15, 2017
677
754
That link doesn't work, the one on the first post does.

I tried the beta build, /system read only button can be depressed now (a problem I posted before here).

It still does not mount /data on stock Oreo, I do not have a password set, do I need to set one?

It also takes much longer to load, I am guessing trying to mount something.

if it can't mount encrypted data without a password it won't be able to mount it with one. The extra time it takes is it trying to do so.
 

FNetV1

Senior Member
Jun 15, 2015
113
23
you cant root nor rollback to a rootable version. Odin is only for samsung. Download mode can only flash stock firmware (see lg up). There is work being done to root newer sprint updates and they might be close, in the meantime stop taking updates until you're sure theyre on the same antirollback version. The work for a new root is focused on arb 1, to check the arb of your current firmware dial (translate lgmenu to digits) *#LGMENU#*997# svc menu-version info

It looks like I did the right thing in avoiding the Sprint variant and ended up purchasing the H918 (T-Mobile Variant).

Having my whole family currently under Sprint and I am the only one that is a T-Mobile customer, I wanted to have an unlocked phone that can actually perfectly work on all 4 major US carriers and the phone needed to have a removable battery as I won't purchase anything with non-removable battery (I am boycotting phones with non-removable batteries and the more difficult they make to remove the battery (eg: Samsung Galaxy 9S+ requiring a heat-gun, new glass back cover because you WILL break yours, and more) then the more I would boycott it.

Well, I was excited to know that the LS997 Unlocked Sprint variant was compatible with all the LTE and 3G bands from Sprint (Obviously being a Sprint device) and T-Mobile, the only T-Mobile band that LS996 doesn't support is 66, which wouldn't have bothered me anyway, all the other supported bands for my device works in my area and all the other areas I go to. Also its fully compatible with AT&T's and Verizon's bands. In other words, its the perfect LG V20 version to have if you would like a device that can work in all 4 networks with both its GSM and CDMA modem active.

Everything was fine until I started doing research before performing the actual purchase: How to root the LS997 phone. Once I read that it was essentially unrootable, which is a big surprise that Sprint would take a stance similar to that of AT&T in severely locking down their devices. This was a huge disappointment, but I still wanted a phone that can work with Sprint if I decide to switch to Sprint in the future. I spend a long time research every single variant of the LG V20 phone in search of another variant that had both its CDMA and GSM modem active. I research the Verizon's variant and learned that Verizon's variant barely works on other networks, its missing lots of Bands, and for T-Mobile Band 12 is non-existent so that one was also a no go.

I gave up and just purchased the unlocked H918 after days of frustrative research and coming up with virtually zero hope and no future hope for getting an LS995 unlocked with the understanding that my H918 will only work perfectly on T-Mobile and AT&T and all of its MVNO's. Sprint is basically completely out of the loop for the foreseable future. They have basically lost me as a prospective customers and my parents are saying that they are considering switching over to my MVNO based T-Mobile provider which is Ultra Mobile because I pay $25 for a 5 GB data with unlimited talk ($31 when you add the taxes and fees, that's my final bill) and that is significantly cheaper than what they pay for their 3 lines unlimited family plan with Sprint, the only problem is that they are tied with a contract that expires on the year 2020 so they would have to put up with Sprint until then.

So yeah, Yesterday I just received the H918, right now I just finished downloading all the required file+ Images, and I am currently in the process of rooting it.
 
  • Like
Reactions: bountyman334

aCIDsLAM

Senior Member
Feb 7, 2015
84
19
Encryption

Hello all,

i am drying for several days to get a running LG V20 H918 / Lineageos 15.1 with enabled encryption.
What is the valid way, to enable it?

Enabling it in the rom settings (is it the right way?) always reboots the phone, starting the encryption, leading to a bootloop.
Taking the Battery out and rebooting the phone shows my sometimes my phone is encrypted. But depending on the TWRP Version, i cant unlock the data in recovery.

I managed once getting it running with an older build from 2018, but i had the feeling, the data partion was corrupted?
After installing more programms, it lead to a boot loop again, letting me format data and starting again, having the same problem after a while.

Am i doing something wrong, alltogether? Do i need to flash and encrypt with encryption3.zip?
Encryption3 doesnt reboot for me in recovery.

I would be happy for a small lead or hint. Thanks
 

Phoenix591

Senior Member
Oct 15, 2017
677
754
Hello all,

i am drying for several days to get a running LG V20 H918 / Lineageos 15.1 with enabled encryption.
What is the valid way, to enable it?

Enabling it in the rom settings (is it the right way?) always reboots the phone, starting the encryption, leading to a bootloop.
Taking the Battery out and rebooting the phone shows my sometimes my phone is encrypted. But depending on the TWRP Version, i cant unlock the data in recovery.

I managed once getting it running with an older build from 2018, but i had the feeling, the data partion was corrupted?
After installing more programms, it lead to a boot loop again, letting me format data and starting again, having the same problem after a while.

Am i doing something wrong, alltogether? Do i need to flash and encrypt with encryption3.zip?
Encryption3 doesnt reboot for me in recovery.

I would be happy for a small lead or hint. Thanks

Don't bother with he encryption zip, did I not write in it's description stock only don't bother on lineage go through settings? Doing through settings in Lineage worked most of the time last time I set that up. If having issues in twrp once it shows encrypted try the beta version linked near the top of the op.
 
  • Like
Reactions: cityneversleepz

aCIDsLAM

Senior Member
Feb 7, 2015
84
19
Don't bother with he encryption zip, did I not write in it's description stock only don't bother on lineage go through settings? Doing through settings in Lineage worked most of the time last time I set that up. If having issues in twrp once it shows encrypted try the beta version linked near the top of the op.

Using encryption ZIP was only another try, to get somewhere. Using the latest TWRP beta, it doesnt accept the decryption password. Downgrading to 3.2.3-1 lets my decrypt the data partiton again but still not booting into system. I may try enabling it with older LineageOS Builds. Maybe that is a working way.
 

Phoenix591

Senior Member
Oct 15, 2017
677
754
Using encryption ZIP was only another try, to get somewhere. Using the latest TWRP beta, it doesnt accept the decryption password. Downgrading to 3.2.3-1 lets my decrypt the data partiton again but still not booting into system. I may try enabling it with older LineageOS Builds. Maybe that is a working way.

Hmm, it was way back in July 2018 x86cpu and I got it working in both (on 15.1), but I havn't touched encryption with lineage 16 yet (because he said hes working on possibly setting it to use FBE, so want to wait on testing/tinkering there until its mostly ready on lineage's side)
 

anotherdj

Member
Mar 2, 2018
25
2
Silicon Valley
Uploading some new builds that redo how encryption is handled (back to more like the much older builds), that may help.

Now with this build (2019-04-22-ENC Beta) it refuses to mount my encrypted /data, although I give it correct password :) System stays mounted, though.

I'm running stock-based ROM (last Nougat-based AlphaROM) on LS997.

Btw, I've retried twrp-3.2.3-0-ls997.2018-08-17.img, and now it also unmounts /system soon after mounting, although it used to keep it mounted earlier. Qseecom exits with exit code 0 soon after mounting /system, so maybe that's the cause or related. Snippet from dmesg on 2018-08-17 build:

<6>[ 568.837953 / 05-02 20:05:15.689][3] EXT4-fs (sda18): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 568.837987 / 05-02 20:05:15.689][3] SELinux: initialized (dev sda18, type ext4), uses xattr
<13>[ 568.950360 / 05-02 20:05:15.809][1] init: Starting service 'qseecom'...
<13>[ 569.010588 / 05-02 20:05:15.869][0] init: Service 'qseecom' (pid 2548) exited with status 0
<13>[ 569.010708 / 05-02 20:05:15.869][0] init: Service 'qseecom' (pid 2548) killing any children in process group
 
Last edited:

Phoenix591

Senior Member
Oct 15, 2017
677
754
Can we know what is this kernel specs ..."MK2000-CLANG" found in your AFH ???
its what it says on the tin, its literally the oreo version of mk2000 (as of the date it they were built), but with minor programming changes that allow it to be built with clang, a totally different compiler than gcc (the traditional compiler used). Clang claims to offer optimization specific for the kryo cores of our SOC. Benchmarks are still pretty comparable though.
 

aCIDsLAM

Senior Member
Feb 7, 2015
84
19
Hmm, it was way back in July 2018 x86cpu and I got it working in both (on 15.1), but I havn't touched encryption with lineage 16 yet (because he said hes working on possibly setting it to use FBE, so want to wait on testing/tinkering there until its mostly ready on lineage's side)

Well it seems to be an OS issue.

With the mentioned TWRP, i can encrypt with LOS 16 where it failed with 15.1. To bad i have camera issues there, so still not all i need but thats no twrp issues.

Thanks for keeping the last modern phone with replaceable battery alive with your work!
 

Phoenix591

Senior Member
Oct 15, 2017
677
754
Well it seems to be an OS issue.

With the mentioned TWRP, i can encrypt with LOS 16 where it failed with 15.1. To bad i have camera issues there, so still not all i need but thats no twrp issues.

Thanks for keeping the last modern phone with replaceable battery alive with your work!

Dirty flash 16 over 15 (only need to do setup and maybe gapps in 15) to fix the camera
 

aCIDsLAM

Senior Member
Feb 7, 2015
84
19
Hmm, it was way back in July 2018 x86cpu and I got it working in both (on 15.1), but I havn't touched encryption with lineage 16 yet (because he said hes working on possibly setting it to use FBE, so want to wait on testing/tinkering there until its mostly ready on lineage's side)

Dirty flash 16 over 15 (only need to do setup and maybe gapps in 15) to fix the camera

Thats what i did. Some boots the camera works, but mostly not. Well i posted that too in the rom thread.
 

jtl999

Senior Member
Sep 7, 2012
143
22
Tried 2019-04-22-ENC Beta on my H990 with x86cpu's LineageOS 15.1 build from December (yes I know I should update, will do soon(tm)). Decryption fails regardless of password being valid or not.
 

mikekote666

Senior Member
Jan 30, 2018
212
109
its what it says on the tin, its literally the oreo version of mk2000 (as of the date it they were built), but with minor programming changes that allow it to be built with clang, a totally different compiler than gcc (the traditional compiler used). Clang claims to offer optimization specific for the kryo cores of our SOC. Benchmarks are still pretty comparable though.
Well personally i think the v9.1 GCC is better than v.8 clang
Can i ask if you'll keep up the work with the kernel or not as we have a new beta release v2.2
Thanks for the awesome work with the 2.1 really amazing and the added optimizations made phone faster in overall use
 
  • Like
Reactions: Vortell
Apr 24, 2019
19
13
Atlanta
Heya, Im having a problem with the latest TWRP build (3.3.0-0), whenever I go and upgrade my TWRP to 3.3.0-0 it completely bricks my TWRP partiton (no longer able to boot to TWRP). Does anyone know a fix? I have no need to upgrade my TWRP version, but its always nice to have the latest. Thanks! :)
 

SrdjanPsy

Senior Member
Mar 3, 2012
66
17
Belgrade
Somehow I downloaded the image for F800 instead of H918 and I even flashed a stock rom in it, but custom ones gave me an error. Took me a min to realize what I did and reflash the proper img. Thanks so much for keeping V20 up to date!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi I have an lg v20 f800 with twrp 3.0.2.1 and los17.1 for vs995.
    Can I upgrade twrp to last versions F800 3.3.1-1 and how to do it without loosing anything?
    or should i install VS995 last TWRP version?

    Thanks
    direct flash over via twrp, install → tap install image → find twrp version.img → choose recovery and swipe to confirm flash. reboot to recovery and check is the twrp version. upgrade twrp not going loosing anything.
  • 89
    Inspired by Backcheck building for the VS995, I've decided to build the latest TWRP for the US996 and now most other V20 variants as well. I'm an amateur, but so far in my own use it seems to be working fine (flashes Open Gapps, Lineage, and Magisk fine, and tested a small backup and restore). That being said, use at your own risk. Any advice and contributions are welcome.


    My device tree


    Made possible by:
    The TWRP team
    Jcadduono for the kernel and initial device tree
    @askermk2000 for continuing work on stock based kernels
    @emdroidle for creating Kdzwriter: a useful tool for flashing all or part of a kdz (stock firmware file) without a pc.


    Known Issues
    • Occasionally the battery will incorrectly display 50% usually after rebooting from recovery into recovery
    • Decryption doesn't work on stock based Oreo roms



    Please post and let me know anything else!
    Changelog
    2019-10-25
    Changed one last thing to try to fix stock Oreo decryption.
    There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
    2019-05-17-NOT Beta
    Made sure the decryption process is setup exactly like it used to be in the past so it should hopefully work if the BETA builds don't (do try the beta build first if you're using encryption, it would be so much easier going forward if the beta way of doing decryption would work), and fresh build for 3.3.1
    2019-05-17-ENC Beta
    Added a few other services to try to fix encryption again, if someone using encryption would give today's builds a try I'd appreciate it.
    2019-04-22-ENC Beta
    Redid how encryption is handled so its much more like the older builds.. still can't handle stock oreo encryption unfortunately, but should have less issues with /system mounting, and might work with something x86cpu is working on for lineage 16.
    Basically if you're having issues with 3.3.0 try this one
    2019-04-07
    Not a whole lot, but TWRP officially decided to tag version 3.3.0 along with some small changes, such as being able to check zip integrity using .sha256 sum files in addition to .md5 and .md5sum files
    2019-04-01
    Updated kernel
    Updated kdzwriter to latest version
    2018-10-18
    Fixed crash on startup (by updating the kernel again)
    2018-10-16
    Properly updated H990 build
    Hopefully fixed F800 build
    Minor kernel update for all variants
    2018-10-06
    Fixed crash/reboot on stock Oreo so that it doesn't take 10 tries to get in (by changing to an oreo kernel), /data decryption still broken.
    2018-09-30
    Enabled quota features in the kernel to fix stock based oreo
    2018-08-17
    /vendor partition support, x86cpu and I got it working and setup so that if a split vendor partition exists we'll be able to back it up or flash to it in TWRP, and of course keep /data decryption working. For those without a /vendor partition it will only show up on the twrp mount page.
    Adjustments to the time so that it will be correct with Lineage 15.1
    Adjustments to scripts to prevent things from getting confused and mounting and unmounting /system repeatedly as has been reported by some.

    Provided nothing crazy happens with these builds, this will likely be the revision we go official with.

    Older Changelogs

    2018-08-05
    F800* build
    Refactored time script: now the date and time is closish to accurate with a lineage 15.1 rom, there is a lineage bug keeping it from being totally accurate.
    Twrp 3.2.3: twrp once again recognizes .md5sum files and not only .md5.
    2018-07-17
    Fixed encryption in Lineage which 3.2.2-0 broke
    2018-07-13
    Added LAF/Download mode as a target for flashing images and creating backups, you may replace laf/download mode with a second twrp install if you so choose.
    Updated to 3.2.2 , not many changes for us since I was the author of most of the time/date fixes mentioned.
    2018-05-05
    Adjusted time fix script
    Added support for multipartition USB OTG devices such as external hard drives
    2018-04-24
    Adjusted encryption support script to be more reliable: a bad password would break decryption until restarting the script manually.
    2018-04-21
    Kdzwriter by @emdroidle is now included: no symlink needed
    Adjusted an encryption support service for Oreo compatibility.
    These are important enough to merit finally going from 3.2.1-0 to 3.2.1-1.
    2018-04-15
    Added experimental /data image backup, itl save everything on/data including internal storage but requires a lot of space.
    Transitioned from kernel level exfat driver to the twrp bundled fuse based driver to hopefully resolve some backup corruption issues.
    Refactored fixdate script to always produce the correct year at the cost of hardcoding the accurate year.
    Suddenly had issues rebuilding previous kernel, transitioned to a mk2000 based kernel.
    2018-04-06
    The date fix script now always checks every six seconds (was running 22 seconds after the last time it had adjusted the date) and fixed an issue where the date may end up as 2017 instead of 2018 (observed in a us996 10o based rom).
    Diagnostic script runs for 90 seconds now.
    2018-03-24
    Stock ROMs date really should be fixed now.
    Made date diagnostic script run for 1 minute instead of 30 seconds because I'm adjusting the date later and 30 seconds cuts it close getting /data decrypted to copy the log to internal storage
    2018-03-23
    Trying harder to fix the date on stock ROMs by having the script run twice
    Added diagnostic script that writes a 1Kb file to (Internal Storage)/TWRP/twrp-date.log Help me get the date right on stock ROMs especially H918 users
    2018-03-21
    Adjusted H918 clock to hopefully be more accurate
    Keep the feedback coming
    2018-03-20
    Fixed date for those on stock ROMs by adding an init script to check and fix the date.
    This makes the us996-noadj version redundant since now its all handled in the same build.
    Feedback requested
    I'd like confirmation the year is correct from those running stock roms
    as well as any H918 users of either stock or aosp based ROMs( please specify which)
    To do so simply hit advanced then terminal and then type date(enter).
    2018-03-16
    Full /data decryption now works! Can now decrypt /data when encrypted by Lineage's encrypt phone option as well as stock! (Stock tested 3-19 by flashing the us99610n flashable zip without immediately rooting and selecting the require pin at boot option .)
    2018-03-14
    Fixed Lineage OTAs (the updater can now properly reboot into twrp apply the update and reboot back into lineage on its own now) by adding misc partition to fstab
    Further Upstream TWRP Changes since 3.2.1-0 in these builds

    Mar 09, 2018
    Dees-Troy
    Don't rename twrp.fstab to recovery.fstab
    committed by Dees-Troy ⋅ 53273ecc
    Mar 08, 2018
    invisiblek
    install: ignore build dates for A/B installs
    committed by invisiblek ⋅ e7b66e10
    Dees-Troy
    FBE: Decrypt spblob v2 (February security patch)
    committed by Dees-Troy ⋅ c5dd5791
    Feb 26, 2018
    FatihFIRINCI
    Languages: Update Turkish translation.
    committed by FatihFIRINCI ⋅ 90765a20

    2018-02-13
    Fixed US996 no offset build to actually have no offset
    2018-02-08
    Initial H990 build
    Added second US996 build with no offset (if the date comes back as 1972 on the other build use this one)
    2018-02-06
    Made clock offset configurable per model (changed TWRP patch)
    Fixed screen offset (at some point I added the kernel second screen fix but left the twrp level fix active too)
    2018-02-04
    Fixed the clock to actually have the correct time most of the time (two patches I created applied to twrp itself, see my device tree for source)
    Upstream TWRP Changes since 3.2.1-0
    Merge "Add Portuguese (Portugal) translation." into android-8.1

    bigbiff authored and Gerrit Code Review committed 10 days ago

    Commits on Jan 23, 2018
    Add Portuguese (Portugal) translation. …

    ElTifo committed 18 days ago

    Commits on Jan 18, 2018
    Merge "Fix typo in Micro SD to have a consistency" into android-8.1

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Added missing translation in Turkish translation" into android… …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "There are a few typos and bugs in the French translation, for … …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Typo / Uppercase-Lowercase in German translation compared to a… …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Typo and bug fixing in Dutch(NL) translation, for example wher… …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Fix minor inconsistency in Czech translation" into android-8.1

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Added missing translation(s) in Portuguese(BR)" into android-8.1

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Added missing translations in Swedish language file" into andr… …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "Added 2 translations in Italian language file" into android-8.1

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Merge "There's a missing translaton in the Greek language file." into… …

    bigbiff authored and Gerrit Code Review committed 16 days ago

    Commits on Jan 17, 2018
    Use /persist as Qualcomm time fix source during early boot …

    nkk71 authored and Dees-Troy committed on Dec 16, 2017

    Commits on Jan 16, 2018
    Merge "Relink adbd needed in android 8.1" into android-8.1

    bigbiff authored and Gerrit Code Review committed 18 days ago

    Commits on Jan 4, 2018
    Use libdrm_platform for minuitwrp in 8.x trees …

    Dees-Troy committed on Jan 4

    Add spblob decrypt for secdis method (Pixel 1 non-weaver) …

    Dees-Troy committed on Dec 15, 2017

    Commits on Dec 21, 2017
    Fix typo in Micro SD to have a consistency …

    pr030880 committed on Dec 21, 2017

    Typo and bug fixing in Dutch(NL) translation, for example where a tra… …

    pr030880 committed on Dec 20, 2017

    Added missing translation in Turkish translation …

    pr030880 committed on Dec 21, 2017

    Fix minor inconsistency in Czech translation …

    pr030880 committed on Dec 21, 2017

    Added 2 translations in Italian language file …

    pr030880 committed on Dec 21, 2017

    Added missing translations in Swedish language file …

    pr030880 committed on Dec 21, 2017

    Added missing translation(s) in Portuguese(BR) …

    pr030880 committed on Dec 21, 2017

    Typo / Uppercase-Lowercase in German translation compared to all othe… …

    pr030880 committed on Dec 21, 2017

    Commits on Dec 20, 2017
    There are a few typos and bugs in the French translation, for example… …

    pr030880 committed on Dec 20, 2017

    Commits on Dec 19, 2017
    Relink adbd needed in android 8.1 …

    nkk71 committed on Dec 19, 2017

    There's a missing translaton in the Greek language file. …

    pr030880 committed on Dec 19, 2017

    Commits on Dec 15, 2017
    Merge up to android-8.1.0_r1 and fix conflicts …

    Dees-Troy committed on Dec 14, 2017

    Commits on Dec 12, 2017
    Fix build error in AOSP 8.1.0 r1 tree …

    Dees-Troy committed on Dec 12, 2017

    Fix [email protected] rule for various 8.0 trees …

    Dees-Troy committed on Dec 12, 2017



    If the clock and/or date (check by going to advanced->terminal then typing date(enter)) is wrong, first try rebooting to normal Android for a while, then if its still wrong after rebooting into recovery let me know your model, and the time/date it claims to be and the correct time (or just the difference)

    Download
    TWRP-3.3.1-1: 2019-10-25
    (Is linking just the folder alright for ya'll? If enough people say something I'll go back to direct links to each device, but copy and pasting individual links for each device gets to be kind of a drag)

    Optional: DO NOT USE THIS OPTIONAL ENCRYPTING ZIP WITH LINEAGEOS
    Since Magisk and supersu disable mandetory encryption by default unless installed with an already encrypted /data and stock and stock based roms have no ui option to encrypt, I've created a flashable zip encrypt-v2.zip (uses the anykernel template by osm0sis ) that makes encrypts /data without data loss. Requires a charged battery (if the power is cut during encryption you could lose all data!) and it checks if you're using one of my twrp builds since afaik none of the others work with encryption.
    Stock users it will stay on the LG boot animation while encrypting! Do not even think about pulling the battery unless you didnt want your data anyway.
    DO NOT USE THIS OPTIONAL ENCRYPTING ZIP WITH LINEAGEOS, it has it's own option to encryption in settings under security.


    Old versions

    TWRP-3.3.1-0: 2019-05-17
    TWRP-3.3.0-0: 2019-04-07

    3.2.3-5: 2019-04-01
    F800
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.3-4: 2018-10-18
    F800
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.3-3 and 3.2.3-2 not listed due to being particularly broken

    3.2.3-1 : 2018-09-30
    F800
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.3-0 : 2018-08-17
    The links for this version will soon point to the latest version with the new changes but these will be labeled 3.2.3-0 and yet have all the new changes.
    F800
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.3-0 : 2018-08-05
    F800
    H910
    H918
    H990
    LS997
    US996
    VS995


    3.2.2-1 : 2018-07-17
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-3 : 2018-05-05
    H910
    H918
    H990
    LS997
    US996
    VS995


    3.2.1-2 2018-04-24
    H910
    H918
    H990
    LS997
    US996
    VS995


    3.2.1-1 2018-04-21
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-0 2018-04-15
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-0 2018-04-06
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-0 2018-03-24
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-0 2018-03-23
    H910
    H918
    H990
    LS997
    US996
    VS995

    3.2.1-0 2018-03-21
    H918
    (Only the H918 changed)

    3.2.1-0 2018-03-20
    US996
    H910
    H990
    LS997
    VS995
    H918

    3.2.1-0 2018-03-16
    US996 (if date shows as 1972 use US996-noadj )
    H910
    H918
    H990
    LS997
    VS995

    3.2.1-0 2018-03-14
    US996 and if the date shows as 1972 use US996-noadj
    H910
    H918
    H990
    LS997
    VS995

    3.2.1-0 02-06-18
    US996 If the date comes back as 1972, use this build instead
    LS997
    H910
    H918 if clock is incorrect on H918, try this build
    VS995
    H990


    3.2.1-0 02-04-18
    LS997
    H910
    H918
    VS995
    US996

    3.2.1-0 for the US996
    14
    I'm still around, just released a minor update, just bringing up kdzwriter and the kernel to the newer versions.
    9
    Someone have tried use kdzwriter with twrp 3.2.1.0-2018-4-15 version? I have this problem.
    https://forum.xda-developers.com/v20/development/tool-kdz-writer-t3649818/post76274425#post76274425

    So what was wrong was that you wern't doing the ln -s part of the directions in the kdzwriter thread. so it couldnt find the linker (the second paragraph under unix-like describes exactly what happened) needed to run the program (it was looking in /system) It was working in the old twrp because it mounts /system by default and new versions don't.

    Anyway today's build flat out includes kdzwriter and is ready to use.
    9
    Last I heard (months ago) it's blocked indefinitely due to issues getting the camera to work at all. It's all basically ready (for a split oreo vendor partition) except for that though.

    Maybe once I can get pie working I can revisit things again. Stuck in a couple places still. No nfc, fingerprint or Bluetooth yet.

    ---------- Post added at 03:05 AM ---------- Previous post was at 03:03 AM ----------

    It's for LineageOS 16.0/Android 9.x coming in the future since this is required.

    The vendor split it is not needed for pie to work. It only it's needed to run gsi images, which is a LineageOS vendor and gsi system. The LineageOS build had the vendor and system, so a split out is not required.
    9
    You are The Man!:good::good:

    • The first and so far the only TWRP that supports encryption!
    • Kdzwriter couldn't be easier to use anymore! Not even symlink creation needed, it's right there ready to go!
    • Working exFAT support!
    • Timestamps are at last fixed!
    • Amazing value for all LG V20 owners, kudos @Phoenix591!
    Well someone needed to be taking care of TWRP, at the time I started only the vs995 had a 3.2.x build. Figured might as well be me since TWRP is simpler than a full ROM like LineageOS. (Re:the system is busy issue its a nonissue, just twrp trying to unmount it before I end one of the services necessary to decrypt. I unmount it immediately after)
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