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

[Phoenix591]

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.

 

[Parasol_Monsters]

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.

OK, thanks.

I got the recovery and dmesg logs if you want them.

They confirm that decryption does not work.

 

[FNetV1]

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.

 

[aCIDsLAM]

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]

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.

 

[aCIDsLAM]

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]

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)

 

[zinou213]

Can we know what is this kernel specs ..."MK2000-CLANG" found in your AFH ???

 

[cnjax]

Can we know what is this kernel specs ..."MK2000-CLANG" found in your AFH ???

Read back a few pages there's been discussion about it

Sent from my LG-H910 using XDA Labs

 

[angilinmago]

bug: can't recognise the otg usb straightaway, had to do the data wipe every time and otg usb shows up as otg (USB) 1, which is strange

 

[anotherdj]

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

 

[Phoenix591]

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]

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]

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]

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.

 

[Redline]

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

Check the latest build in the 16.0 thread now.

 

[jtl999]

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]

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

 

[[email protected]]

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]

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!