[TWRP][JOAN][V30/V30+/V30S][UNOFFICIAL] 3.2.3-7 Oreo final

Search This thread

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
that sounds strange. it's t-mo version as it looks, that's a little problem for me. i can't imagine it, but are there really these kind of specialties with it? may be that logs are helping with this, can you do some pls? beginning from the moment when you try to use the fingerprint scanner, maybe it's visible in logcat / dmesg what's wrong.
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
This is why I really like the "default" (basic) TWRP you made for WTF thread. "Advanced" TWRP often confuses people. The basic TWRP has the categories they need and nothing more. ;)

at this point of time this 3.3.1 twrp can't really be called an advanced version :D only additions are "leave out lockscreen settings when restoring data" and "exclude twrp app". i removed vendor partition too, because developing in this point has stopped imo. weren't these two additions available in default wtf version too...? don't know atm, sry ;)
 
  • Like
Reactions: tech_infinity

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
hoi ?

new twrp image with little fixes, but data formatting still not able to remove encryption -.- you can use "fastboot format userdata" to do this. crypto stuff is included, decrypting of stock rom starts but fails :( am on it. maybe someone knows what is "encryption type 3" and "error number -14" for lg...? this is from libqseecomapi.

https://drive.google.com/file/d/1bowXidNlwxsoPVPXYD13Lam1wEFApxBf/view?usp=drivesdk
 

tech_infinity

Senior Member
Jun 16, 2014
2,511
1,546
aakashverma.com
LG V30
hoi

new twrp image with little fixes, but data formatting still not able to remove encryption -.- you can use "fastboot format userdata" to do this. crypto stuff is included, decrypting of stock rom starts but fails :( am on it. maybe someone knows what is "encryption type 3" and "error number -14" for lg...? this is from libqseecomapi.

https://drive.google.com/file/d/1bowXidNlwxsoPVPXYD13Lam1wEFApxBf/view?usp=drivesdk

Thanks for the update. :)
@SGCMarkus do you know anything about this error?
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
Thanks for the update. :)
@SGCMarkus do you know anything about this error?

could be that it's written in libcryptfs_hw, i'll be back on it this evening :D now it's type 1, just by switching to another libcryptfs_hw repo lol

edit: he knows this error on another lg device, but afaik didn't find a solution, too
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
yay, "first step" done: twrp 3.3.1-0 is up and needs heavy reliability testing and some tweaks of quirks are left, too. pls report absolutely everything you find not working as you expect it :good: like non-working formatting of userdata (a part of this is that twrp doesn't want to secure erase userdata, i even don't know if that's the full reason, but i think this somehow is connected to new mke2fs (make_ext4fs is dropped by google and twrp since 9)).

let the testings begin :good:
 

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,583
14,412
Atlanta, Georgia
like non-working formatting of userdata (a part of this is that twrp doesn't want to secure erase userdata,

I still haven't seen anyone who reported this problem follow the WTF Instructions for formatting data.

Wipe data (factory reset),
Flash Magisk,
flash the Pie compatible Encryption Disabler,
Flash Root Checker disabler
Format Data (where you type yes),
Reboot to Recovery from within TWRP
Flash Magisk AGAIN
Reboot phone


See this post:
https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
I still haven't seen anyone who reported this problem follow the WTF Instructions for formatting data.

Wipe data (factory reset),
Flash Magisk,
flash the Pie compatible Encryption Disabler,
Flash Root Checker disabler
Format Data (where you type yes),
Reboot to Recovery from within TWRP
Flash Magisk AGAIN
Reboot phone


See this post:
https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
it's only present in 3.3 :D formatting with mkfs_ext4 in 8.1 default recovery works, no matter if pie or oreo. but google have chosen with pie to switch to its successor, mke2fs from e2fsdroid / e2fsprogs. and this one isn't able to remove encryption on some phones, not only our v30. so fastboot erase userdata needed instead, everything else is the same.
 
  • Like
Reactions: ChazzMatt

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,430
45
Germany
LG V30
OnePlus 7T Pro McLaren
turned out an essential part for removal of crypto wasn't called in 3.3, when formatting the userdata partition to remove encryption and start fresh: fixed. let's say twrp 3.3 is for pie, 3.2 for oreo, when it comes to encryption only. you can use both versions, if crypto isn't a musthave for you, otherwise you may not be able to access your internal sdcard or data in twrp; everything else is the same now.
 

callihn

Senior Member
Oct 14, 2012
159
31
I have never been able to get the correct date and time in TWRP regardless of TWRP version, Android version or device and there is no persist/time. Any ideas?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 58
    Hi!

    !!! First things first: big phat huge !!!THANKS!!! to the full TeamWin Team, SGCMarkus (initial twrp tree), Phoenix591 (for inspiration), Dees Troy (for his trees), z31s1g for his brilliant theme and Captain Throwback (inspiration, too) !!!

    For Pie ROMs you should use 3.3.1 recovery, either OrangeFox (based on TWRP with many very useful additions, with Magisk module manager being only one of it :good: ), or good old TWRP itself. 3.3.1 needed for decryption of pie ROMs!

    Feature list:
    - capable of installing treble and/or vendorized ROMs
    - Possibility to leave out lockscreen settings when restoring a backup (sometimes you have to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings are independent from your encryption settings)
    - Time and date is showed correctly, independent of /data
    - some extra partitions (see below)
    - Oreo 3.2.3-7: compiled with (modified) 8.1 TWRP branch
    - Oreo recovery: Decryption of AOSP up to 8.1 and stock ROMs userdata is working (cherrypicked stuff for bringing that up), so, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't there anymore :)
    Pie is not decryptable for the moment, neither with old Oreo recovery nor with newer PIe recovery: this is being worked on. Encryption changed in Pie, this needs some extra "love"
    - everything working: backup, restore, decryption, time, mtp, adb, installing of treble or vendorized builds, themeable, .........
    - modem image support: backup, restore, flashing of modem images either taken directly from kdz or via diskdump (this already was available but then broken at some point of time, sry for that! ;)).
    - Same for OP image

    Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
    Also, if you want to restore an older backup, don't restore 'firmware' from it!!! This will break your WLAN, at least, and you have to flash a modem.img to get it back working.

    For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already (described above).

    For decryption: it works as it should. Therefore it is a little bit tricky to restore a ROM which has encrypted userdata, when you'd installed any other ROM in between. or formatted data There are some points to remember when restoring, a little guide is available in 3rd post, and some tipps too.

    Some instructions:
    How to flash?
    If starting fresh with an unmodified phone, this thread should help you installing it
    When you already have TWRP installed, you can flash this recovery from within TWRP:
    - Tap "Install"
    - Tap "Install image" button, located down right
    - Locate your downloaded image and select it
    - Select "recovery" from the list which shows up then
    - Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
    And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
    fastboot flash recovery <twrp-image-name.img>

    When you experience errors or sth isn't working as it should in your opinion:
    When an error occurs, pls supply me a log from TWRP, taken immediately after the error showed up. You can use the "Copy to SDCard" option (advanced options) in TWRP for this. Grab this file then and upload its content to pastebin.org.
    I can't help without as much detailed info as you can supply. This should include at least following information: phone model, used TWRP image (exact name of image), task you wanted to do (which ROM e.g.).

    There's now an optional version of TWRP available, which contains the inclusion of internal storage in data backups (IntSD version). Exclusions (folders which won't be backed up): TWRP, Movies, Music and Download folders. These won't be included in backups, as they can be really big.
    With the recovery including internal storage you can backup to internal and external storage, no matter. The data_image recovery can backup its data image to external sd only, of course.

    If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).


    DOWNLOADS:

    Oreo and Pie capable 3.2.3-7 TWRP:
    Download links (always the latest and newest only; one version for all):
    File name: TWRP-3.2.3-7-DataIMG.img (default)
    MD5sum: aac1525f9bd85d6efbc0fb65bda4a904
    MAIN Download: AndroidFileHost - TWRP-3.2.3-7-DataIMG latest
    File name: TWRP-3.2.3-7-IntSD.img (non-default, includes main part of internal storage in data backup)
    MD5sum: 23113ad33772a5f783dcabd09fa97ebb
    MAIN Download: AndroidFileHost - TWRP-3.2.3-7-IntSD latest

    Some additional words to different versions;
    I personally use internal w/ sdcard backup, all my pics and almost everything possible app related on my phone is on external SDcard. Some data always remains on intSD (e.g. whatsapp, the Android folder which contains settings and app data too, k-9 mail folder and others), this needs to be in a backup for me. This is, what the intSD version does: but it leaves out the big folders (download, music, movie and TWRP).

    As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.

    All you need to compile this yourself:
    [url]https://github.com/seader/android_device_lge_joan-twrp[/url]
    [url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
    [url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
    [url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with encryption cherrypicks and the stuff added. encrypt-8.1 branch = intSD version, master branch = DataIMG version)
    19
    grmpf... no progress til now, regarding crypto (but at least some other stuff found and fixed). but: there are plenty of possibilities left, so hope isn't dead :D next continuing day: sunday, eventually maybe an evening in between. could be that new twrp already works (partially) for unencrypted pie ota phones, if it is i can release a test version (with crypto disabled) on sunday :good: press a thumb pls :)
    15
    i had some additional hours yesterday and the result was absolutely better than expected :) after some finetuning and flag playing most of the services needed for pie decryption are coming up and are listening. it even recognizes correctly if a pattern, pw or pin was used for secure startup; but unfortunately doesn't decrypt it... looks like vold changes are needed. i hope it's easily solveable and doesn't eat up much more valuable time :D when this is done, then there are some additional tasks to do for a flawless twrp experience, but this should be more easy to solve.

    i'll keep you updated :good: :) i would like to say that coming wednesday is the day, but i can't promise it, sry. maybe a first beta / pre-final can be released then: btw, it would be nice if someone with oreo stock encrypted fw installed could do one or two tests with the new recovery, because we want and need a single recovery which is fully working for both oreo and pie, stock and aosp. hard goal i believe...
    14
    good morning :)
    ok, after yesterdays edits with 3.3 recovery i think: we will stay with 8.1 recovery... for me it looks like pie branch (3.3.1) is really supposed to be used for a/b native oreo / pie devices, which our v30 simply isn't. 8.1 branch should be able to decrypt pie too, it's used for a big pallette of older legacy devices which got updates for pie, and some of them have twrp decrypt enabled. beside that there's not much changed in 3.3.1, which makes it no "absolutely must have" update: all it offers is available in 3.2 too, there's no critical new stuff for us. for a/b devices there is ;) but...

    so, for now, 3.2.3 / 8.1 oreo branch is the one to use for our v30, even with pie. it's capable of flashing everything (3.3 isn't, our dmverity and rct disabler zips e.g. won't flash and will abort with an error). it works just fine with a non-encrypted v30 updated to beta pie ota. it's too much work to change everything to make it working nicely with our older device. so if you're on pie ota already, install 3.2.3 and flash rct / dmverity / encryption disabler and you're good to go for backups, flashing etc pp :good:

    i've got a 3weeks vacation in 1½weeks, and have ~ 1week of free time available then to work on this: the other two weeks we drive away. i think we will get an update then ;) hopefully then there's already official pie available for us. for now i'll concentrate on work, it's a hard time because we are missing manpower (due to vacation time ;)) and it really fuggs me hard... let's wait for time in which my brain and body is more fit and can concentrate better on this :)

    see ya! :good:
    14
    update available: with some OP partitions available now, an OP image flashing function is added, beside a sources update.

    have fun and a nice weekend! :good: