Get logs, must be different from the last time
Encrypted backups cause many more issues that aren't easily solvable
I solved the problem using Android Image Kitchen. At first same behaviour. But then after un-/repackimg I added an AVBv2 signature using avbtool. Now also the flashed recovery image boots fine. It looks like the Poco X3 Pro bootloader only accepts signed images.Hi samsungics1200,
thanks for sharing your modified TWRP derived from Nebrassy's TWRP. Did you also modify Nebrassy's updated version 03-07-22? How did you accomplish to modify twrp.flags? I tried it myself using abootimg. But it failed, my builds didn't boot.
Edit: I noticed that samsungics1200's recovery img also only starts when bootet via
fastboot boot twrp.imgbut not when flashed into device.
From my experience: yes. As long as the bootloader (fastboot mode) is intact, and this was always the case with my three devices I had so far. In one case it was necessary to boot a valid recovery through fastboot boot once and start the system from there.
Use unofficial build:
I would try entering some PIN or unlock pattern you used previously for unlocking your phone.System boot prob after restore
Lineage19 A12, Magisk 25.2 rooted, no pin, Twrp off. 3.7.0_12.0. Firmware V188.8.131.52.SJUMIXM
Backup of data, boot & supersystem ran without errors, so did restore. But system boot ends in dark screen after a while of lineage boot logo, then restarts into twrp recovery.
Found data encrypted and not mounted. Mounting asks for password, but, as i said, backup was without any pin or pw, so i couldn't decrypt & mount.
Switched to latest unoff TWRP-3.6.2-vayu-10-09-22.img, same result.
Someone with an idea? Thanx in advance.
The solution in many cases is..... patience. Although with black screen i see no activity, there is one. Guess it has to do with decrypting. So just wait, until phone restarts system itself. No pressure on any button meanwhile, it's not standby mode that causes dark