Have many thanks for your continous work!new unofficial build is up
Android 13 decryption and some fixes
Though I still miss password protected backup, would it be possible to add that?
Have many thanks for your continous work!new unofficial build is up
Android 13 decryption and some fixes
Get logs, must be different from the last timeIgnored and flashed
Still an error when trying to do a full save, btw.
Thanks for your work one more time![]()
Encrypted backups cause many more issues that aren't easily solvableHave many thanks for your continous work!
Though I still miss password protected backup, would it be possible to add that?
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 viafastboot boot twrp.img
but not when flashed into device.
Also ignore the fact that version number inside TWRP doesn't get updated ^^
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.Sorry if this question sounds silly and also if I'm in the wrong thread.
But will a device still boot into system If I flash an imcompatible custom recovery ?
Use unofficial build:Can't make backup of data partition (createTarFork() error 255). MIUI 13.0.5 by xiaomi.eu, lockscreen type: pattern, phone is encrypted. TWRP 3.7.0_12.0 official.
Edit: can't attach logs.
Edit 2: put them into an archive, they are visible now.
No clue what that is, donation links are in my signature/main post
No change. Then again official build is newer than the unofficial one.
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 V13.0.4.0.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 darkBackup 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.
Official twrp-3.7.0_12-0-vayu.img is more recent |
No, use latest TWRP.Guys, for pixelexperience 13 plus i should use latest twrp:
or this unofficial one from nebrassy: TWRP-3.6.2-vayu-10-09-22.img ?
Thanks.