[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] p0w3r_off:
i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.

so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.

what did i do so far is:

*flash twrp 3.4.0

*boot up to twrp 3.4.0

*use adb shell twrp remountrw

*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it

*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally

*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)

*reboot without wiping system partition and installing lineageos only brings up normal stock rom

*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again

*wiping system partition and reboot only brings up android one loading screen endlessly

so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.

oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.

what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"

edit again.

I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:

*reflashed via fastboot the stock rom

*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)

*booted to fastboot, flashed newest twrp to boot

*booted to recovery

*adb shell twrp remountrw

*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)

*adb shell

*entered in adb shell mount /system

*adb shell twrp wipe data

*adb push lineageos.zip /data/

*adb shell twrp install /data/lineageos.zip

*adb push ddv.zip /data/

*adb shell twrp install /data/ddv.zip

*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)

*adb reboot bootloader

*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)

*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img

*fastboot reboot

*then the phone - now on lineage - asked me to factory reset, i did

*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine

if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme :)

in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.