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

Search This thread

lgfans

Member
Feb 11, 2018
13
0
thanks for any help! my us998 can't boot up after flashing this 30b.

my problem as blow:
My device(us998) is running on us99820g, Android 8.0.0. TWRP's version is 3.3.0 .
I flashed this zip package and Magisk (verion 20.0).
It stop at logo when i reboot on system.

any suggestion? thx first.
 

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,618
14,438
Atlanta, Georgia
my problem as blow:
My device(us998) is running on us99820g, Android 8.0.0. TWRP's version is 3.3.0 .
I flashed this zip package and Magisk (verion 20.0).
It stop at logo when i reboot on system.

any suggestion? thx first.

Do NOT NOT NOT use EXPERIMENTAL, BETA 3.3 TWRP. Even the Dev says not to use it.

Only use stable 3.2.3.7. The only TWRP you need is in the WTF thread and also linked in all the Pie KDZ threads.

Also if you ever intend to update to US998 20h TWRP flashable zip, you need to temporarily go back to Magisk 18 to install that.

_____

SHORT ANSWER:
3.2.3-7 is the one which is capable of everything and should be preferred by everyone, 3.3 is in early beta stage only and needs additional love.

LONG ANSWER:
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:
 
Last edited:
  • Like
Reactions: tech_infinity

lgfans

Member
Feb 11, 2018
13
0
Do NOT NOT NOT use EXPERIMENTAL, BETA 3.3 TWRP. Even the Dev says not to use it.

Only use stable 3.2.3.7. The only TWRP you need is in the WTF thread and also linked in all the Pie KDZ threads.

Also if you ever intend to update to US998 20h TWRP flashable zip, you need to temporarily go back to Magisk 18 to install that.

_____

SHORT ANSWER:


LONG ANSWER:
thx a lot. IT works well now. I updated from v20G to V30 sucessfully under your help. :good::good::good:
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
every 3.2.3.7 recovery is working very well :) i remove the pie beta now.

updates on pc crashes: i'm in the middle of testing and setup session atm, and progress is visible. no more shutdowns and crashes with current new bios and (ram and cpu) settings anymore, this is very promising now. i hope it's stable now, so new compilings can be done :)

it would be nice if everyone, who has most recent android 10 and twrp 3.2.3.7 installed, could give logs and descriptions of eventually arised problems and mis-flashes with twrp, so i can start working on a new 3.3 recovery then :good:
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
good morning,
there's currently a 3.3.1 twrp.image tested. as it looks, the only problem with it is using anykernel 3 zips, because they freeze. we found nothing in the logs and this doesn't happen with 3.2.3 recovery. twrp reacts when connected to twrp but screen loses navbar and one can't exit from flash process. when this is fixed, there's nothing holding it back then: beside crypto stuff :( it's completely w/o crypto til now, this needs further investigations. plan for crypto is to support it only for aosp and not stock anymore, because stock crypto is... kind of tricky too :D everything else is working now (adb, mtb, microsd, time and date, wiping, mounting, removal of lockscreensettings when restoring, twrp app install prompt removal, basics like flashing or (compressed) backups and restorings, ...) as it should, so not that bad :good: stay tuned, i'll keep you updated :)

Hi team, anyone tried orange recovery for lg v30? Someone knows if there is any version compatible with lg v30 (h930)?
i didn't even know this existst :D hmm, i look at this, interested now :)
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
spoken too early! i'm making this public now, consider it a first testing version w/o encryption, but with everything else working, including anykernel3 zips. compatibility of this twrp with some older zips should be increased too, but: forget about aroma zips... aroma just is outdated, no more being worked on, therefore no more interesting as it would require changes in twrp sources.

TWRP 3.3.1-beta5 download, have a look at above post for features and add anykernel3 zip compatibility ;) needs extensive testing of every little feature in it, as soon as an error arises pls contact me either here or via pm pls. :good: this build has logcat enabled, final build won't have it enabled.

btw, i tested almost everything of it and found it stable. only one thing isn't working: encrypted compressed backups. maybe this gets fixed this evening. and sometime later crypto trials :D
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
Last edited:

LeTerrible

Senior Member
Dec 19, 2012
82
23
@seadersn yes, used beta 6. Normal backup works fine. But encrypting backup with password was slow but working till 95%. Then it hust froze. Had to hard reboot.

---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------

Yes used beta6. Could it be because i am backing up in my external sd card and not internal sd?
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
jip, encrypted backups are slow, and even slower when.stored on microsd and not internal. but: this new beta 6 is a little bit buggy too :( i had an error restoring an compr. encr. data backup, it stalled too, some little percent before ending -.- so more work to do :good: this could only be a problem with fstab and reservedsize=40m.

so be prepared and handle this recovery 3.3.1 as a beta, means, make backups beforehand with working twrp 3.2.3.7 before doing critical testings. on the other hand: it's working when not using pw protected backups ;)
 

tech_infinity

Senior Member
Jun 16, 2014
2,515
1,549
aakashverma.com
LG V30
a new image :) twrp.3.3.1 with the ability added to encrypt / pw protect your backups. grab it here:

https://www.androidfilehost.com/?fid=4349826312261670996

to do: add decrypt of userdata. when? next months :) some words about that, from TWRP team:

https://twrp.me/faq/encryptionsupport.html

i'll create a new thread on sunday, if at least five ppl say that it's working for them too. this twrp is capable of operating with all joan devices, beginning with oreo :good:
Been using the beta 6 for a couple of days. Made and restored a few backups. Flashed ROMs, kernels and other stuff. Everything works as it should :fingers-crossed::good::D
Thanks!
 

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
Been using the beta 6 for a couple of days. Made and restored a few backups. Flashed ROMs, kernels and other stuff. Everything works as it should :fingers-crossed::good::D
Thanks!
thx for feedback ;) with 3.3.1 there's one big problem: you can't format fde encrypted userdata. twrp says it formatted data, you reboot to rom and it doesn't boot you to the setup screen, but wants your previously set pin/pattern/pw. it even accepts it, only to say you five to ten seconds later: "decryption unsuccessful & data corrupt. factory reset needed." only "fastboot erase userdata" or "fastboot -w" (i got a message that unlocked phones partitions aren't allowed to be formatted this way. repeating command three times did it then.) works for removal of crypto (typed both three times in a row).

everything other than the workaround needed for getting rid of encryption and the process for decryption of userdata is working, even encrypted pw protected (compressed or not) backups. until someone eventually finds another flaw :D
 
Last edited:

seadersn

Recognized Developer
Nov 3, 2010
3,616
3,432
46
Germany
LG V30
OnePlus 7T Pro McLaren
Fingerprint Sensor Not Working... After Nandroid Restore I tired two, three roms and it seems to be the same problem with them too, Fingerprint Sensor will give all kind of errors after Nandroid Restore. Do you have any idea how to fix it, without flashing the ROM again?

fortunately, not a problem with twrp, imo :) i write that because the three different roms which i tested with / restored didn't have that problem but were lockscreen-unlockable with fingerprintscanner just fine. no aosp roms btw, only pie. pie 31a fw installed.

which rom did you try with twrp? did you restore only boot, data and system or all the other partitions too? if all the other partitions too (which is absolutely not needed, see following link pls), then be careful to not switch between different fw versions. this could explain your non working fp scanner.

https://twrp.me/faq/whattobackup.html

i explained that already. it's written somewhere in this thread, maybe even in 1st post (don't know atm anymore :D): when backing up and restoring, restore only the partitions you really need. modem, persist etc is NOT a partition needed to restore in general, ONLY boot, system and data.

maybe you've gotten a mixed firmware with restoring e.g. modem from 31a to base fw 22j.
 
Last edited:

tech_infinity

Senior Member
Jun 16, 2014
2,515
1,549
aakashverma.com
LG V30
fortunately, not a problem with twrp, imo :) i write that because the three different roms which i tested with / restored didn't have that problem but were lockscreen-unlockable with fingerprintscanner just fine. no aosp roms btw, only pie. pie 31a fw installed.

which rom did you try with twrp? did you restore only boot, data and system or all the other partitions too? if all the other partitions too (which is absolutely not needed, see following link pls), then be careful to not switch between different fw versions. this could explain your non working fp scanner.

https://twrp.me/faq/whattobackup.html

i explained that already. it's written somewhere in this thread, maybe even in 1st post (don't know atm anymore :D): when backing up and restoring, restore only the partitions you really need. modem, persist etc is NOT a partition needed to restore in general, ONLY boot, system and data.

maybe you've gotten a mixed firmware with restoring e.g. modem from 31a to base fw 22j.
That's not a twrp issue. I restored Stock, aosp pie and aosp Q ROMs using twrp(both beta 6 and stable before that), had no issues at all whatsover :fingers-crossed::D
 
  • Like
Reactions: seadersn and zfk110

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,618
14,438
Atlanta, Georgia
fortunately, not a problem with twrp, imo :) i write that because the three different roms which i tested with / restored didn't have that problem but were lockscreen-unlockable with fingerprintscanner just fine. no aosp roms btw, only pie. pie 31a fw installed.

which rom did you try with twrp? did you restore only boot, data and system or all the other partitions too? if all the other partitions too (which is absolutely not needed, see following link pls), then be careful to not switch between different fw versions. this could explain your non working fp scanner.

https://twrp.me/faq/whattobackup.html

i explained that already. it's written somewhere in this thread, maybe even in 1st post (don't know atm anymore :D): when backing up and restoring, restore only the partitions you really need. modem, persist etc is NOT a partition needed to restore in general, ONLY boot, system and data.

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. ;)
 
  • Like
Reactions: seadersn and zfk110

zfk110

Senior Member
Jan 11, 2014
1,112
229
Atlanta
fortunately, not a problem with twrp, imo :) i write that because the three different roms which i tested with / restored didn't have that problem but were lockscreen-unlockable with fingerprintscanner just fine. no aosp roms btw, only pie. pie 31a fw installed.

which rom did you try with twrp? did you restore only boot, data and system or all the other partitions too? if all the other partitions too (which is absolutely not needed, see following link pls), then be careful to not switch between different fw versions. this could explain your non working fp scanner.

https://twrp.me/faq/whattobackup.html

i explained that already. it's written somewhere in this thread, maybe even in 1st post (don't know atm anymore :D): when backing up and restoring, restore only the partitions you really need. modem, persist etc is NOT a partition needed to restore in general, ONLY boot, system and data.

maybe you've gotten a mixed firmware with restoring e.g. modem from 31a to base fw 22j.

I tried with this stock firmware

https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3980701

and this one

https://forum.xda-developers.com/lg-v30/development/rom-havoc-os-t3908402

Same firmware I restored only boot, data and system. everything restore fine, I normally make a backup without finger/password, but after the restore FP doesn't response.
 

Attachments

  • q.jpg
    q.jpg
    87 KB · Views: 77
  • f.jpg
    f.jpg
    37.4 KB · Views: 72
  • Like
Reactions: seadersn

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: