Yes, you can install it by twrp itself, no problem
Time maybe - but check the year when making a backup for example. Some roms have the wrong year in TWRP, like ShapeshiftOS or crDroid up to version 7.17 while now on 7.18 I have the correct year again (at least on TWRP 3.6.2_11, I haven't tried the newer ones yet).
TWRP settings not being saved in A12 version, this has been fixed recently
I didn't forget what you asked, my next step is to check if it's safe to create and restore a nandroid backup on A12.Time maybe - but check the year when making a backup for example. Some roms have the wrong year in TWRP, like ShapeshiftOS or crDroid up to version 7.17 while now on 7.18 I have the correct year again (at least on TWRP 3.6.2_11, I haven't tried the newer ones yet).
This sounds promising! Thank you for your contributions.OK. Settings will be saved in the new A12 version.
Now they'll only be deleted if you run format data.
I ended up discovering, and solving, a problem in versions A11 and A12 when a backup with encrypted data was performed.
New versions are now available.
I would like to thank again those who are testing and reporting success and bugs that appear
Dude I'm sorry but I don't want to add mods but you can check with fichl who is expert on this, i don't think there were big changes from A11 to A12. '[THEME][TWRP] TWRP 3.x dark stock theme pack w different colors v4
Erm ... huh? So basically we have to be in Airplane mode when making a backup so we're still offline when restoring it?
Well, it's an old problem that I honestly don't know if it still happens lol, but after a restore or flashing a new rom, some sim cards may no longer be detected and need to be replaced. I don't use my OP5 as a daily driver so I don't have a SIM in it, when in doubt I think it's better to keep this recommendation.
* If you want to test these recoveries fastboot boot twrp_cheeseburger_dumpling_3.6.2-11-v2.img * If you want to use then fastboot flash recovery twrp_cheeseburger_dumpling_3.6.2-11-v2.img
Problem solved, if you want, you can now use version A12.1 v.5
Using LineageOS 19.1
In the end I got the sense that I can cancel decrypt attempt and flash from /data/lineage_updates
But anyway I tried sideload again.
I'm using a macbook pro (m1) and found that if I connect to port on the right side it won't do `adb devices` in recovery or `fastboot devices` in fastboot.
but if I connect to the left it did manage to do it. (using A11 3.6.2-v1).
when using A12 3.6.2-12-v4
This is what I tried, and what it produced.
❯ adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached 10499fc7 device ❯ adb reboot recovery ❯ adb devices List of devices attached ❯ adb kill-server ❯ adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached ❯ adb sideload lineage-19.1-20220606-nightly-cheeseburger-signed.zip adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found