Database Info

Zip signature verification failure when flashing in TWRP

I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.

I had updated from my oneplus 2 to the oneplus 6. and with great ease was able to unlock,flash android P.
Bad to hear that you are facing such problems, as my switching was error free.
One of the solutions which you could try for the Zip signature verfication:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse

inderjeet.c7 said:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
Click to expand...
Click to collapse
I have tried TWRP with both the current 3.2.3.0 and the previous 3.2.3.2, both downloaded from twrp.me. Sideloading failed, too. Same zip signature error.
I may have to wipe the device and start over yet again. I'd blame myself for doing something wrong, which may very well the the case. But the zip signature issue was there before I installed anything with the stock system.

maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
Try this https://www.bouncegeek.com/fix-signature-verification-failed-oneplus-devices/. I don't know if it'll work for your device as this is for one plus 5t but they are similar in this regard. I would also download all files fresh to make sure there is no corruption. Also disable any lock screen security (finger print, Pin, face lock, etc.)

Among the things I've tried were that I had happened to find that article earlier. Some of it, I can't do. Like clearing the cache of System Update. I'm not seeing that listed in the Apps on Oxygen like it may have been on Hydrogen. One thing I did do, though, almost the only thing, before unlocking and rooting, was to let the system update with an OTA from 5.18 to 5.19. So that could have played a role based on the article's premise.
In any case, I can't sideload, I still get the zip signature failure in spite of what the article says. I tried the other approach. I'll try again later.
This is frustrating. I bought this phone in no small part because it can be rooted and there is a dev community for it. But if I can't do with it what others are and what I want, it may not be worth keeping. I wish I knew exactly this failure is occurring. That it's not rare, I get. But maybe there's nothing wrong with the files. Can all these repeated downloads be bad ones? I've tried both transferring from my Mac via ftp and downloading directly from the web to the phone.

Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.

helioXverse said:
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
Click to expand...
Click to collapse
Yes, I'm booting into TWRP via that command line. It's not permanent. I tried to flash the TWRP zip, but signature verification failed. That was the first of my various failures. If I can't find a way to get this straight, I may return the phone, or at least try and get them to trade it to me for another.

Is your oem lock checked?

netgar said:
Is your oem lock checked?
Click to expand...
Click to collapse
Do you mean is "OEM unlocking" toggled on in Developer Options? If so, yes, it is and has been.

I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0

NickStrupat said:
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
Click to expand...
Click to collapse
Interesting. I didn't try going back that far. I ended up abandoning zip signature verification and am just flashing without it. So far, no problems.

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Help, I can flash and boot LineageOS but not OxygenOS

Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.

I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?

mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.

The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases

mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.

How are you flashing the OS?

mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.

And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.

mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.

TWRP 3.5.0 Installation Silently Fails

Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU

Same question here. It seems that you can only boot from TWRP, not install it.

Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.

TWRP boot timeout, ROM LineageOS

Hello, I'm not usually a poster to any forum as my questions can be found with enough digging but I can't find my answer, so here goes.
BACKGROUND:
Stock: Motorola 5G Ace (kiev). Android 10. I think it was Snapdragon 690.
Unlocked bootloader
Installed to TWRP 3.5.2 for the 5g ace to both partions _a, _b
Used TWRP to flash lineage-18.1-20210701-UNOFFICIAL-kiev
All commands sent through BASH
DISCUSSION:
Tried to install Gapps after LineageOS, recieved errors that said something like no room or storage and went through each line with a fail. Verified cache was wiped, tried again. Failed again then moved to reboot with just OS.
Lineage OS installed with success.
Boot back to recovery, TWRP is gone and now it's LineageOS recovery. Could not figure out how to flash Gapps to with LineageOS, but learned that if reducing Gapps size it should work in TWRP, so re flashed TWRP, no problems.
PROBLEM:
TWRP will not load. At load screen it shows the TEAMWIN logo and lasts for a min or so then times out, reboots and loads OS.
Will adb to bootloader.
Will adb to fastboot, BUT enters TWRP, no screen touch will accept commands then lock screen initates at about 30-60s and hard reset to get out.
Can fastboot to recovery. but enters orginal TWRP boot time out.
-----------------------------------
REQUEST:
Please assist in troubleshooting why recovery will not boot so I can get Gapps flashed.
-----------------------------------
ADDITIONAL NOTES:
If plugged into charger/power it wont stay turned off and boots. Will only turn off from LineageOS.
Can not boot into fastbootd but I'm guessing that was something related to the original recovery that I wiped.
Comments:
Would this have something to do with LineageOS at Android 11 and my original TWRP was set for android 10?
All I was trying to do was get Gapps to load, super bummed that I was so close. At least my phone is still a phone.

Your TWRP is old. You can flash gapps from the linage recovery. If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps. Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.

Your TWRP is old.
That's what I figured, what version would be better? Reading the TWRP pages make me believe I can't just pick anything that has a newer release date.
You can flash gapps from the linage recovery.
Lineage recovery appears gone. Do you know how to get it back, or if i'm wrong and then how do I get back into it?
If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps.
Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.
I agree this would be a good path, but I have no access to any recovery SW. From what I understand I can't do this from inside the LineageOS either. Silver lining; Lineage is working fine.

Are you rooted with Magisk?

I am using TWRP 3.6.0_11.0 RC1.4. There is an installer that you can use Magisk to flash. It downloaded it from the Telegram channel. There is also a .img file in the Telegram channel.

https://t.me/MotoG5GOfficial is the correct channel.

That was it. Old TWRP. Thank you very much.

You are welcome.