Did you find any solution?Hi, sorry if this has been asked before but I can't find anything that sorts my problem... So, I have previously been running Lineage OS 17 on my XZ1 Compact (G8841) and I then returned it to stock using FlashTool. Now, I want to return to Lineage OS again but I can no longer flash the TWRP recovery; the terminal just hangs on the fastboot flash. I am not the best at all this malarkey but I am guessing it something to do with root (maybe?). Anyway, If anyone has any pointers I'd be massively grateful. Oh, and nice work on the ROM, it's a beast on this phone. Cheers, Spike.
Will there be a TWRP update for 11?
fastboot reboot
)fastboot boot twrp.img
.But after the reboot, I tried to flash something and all folder suddenly showing weird name, probably encrypted?
hello everyone
I want to return to Lineage OS again but I can no longer flash the TWRP recovery; the terminal just hangs on the fastboot flash
Not sure why this is happening, perhaps an insufficient or incompatible power supply issue, but the solution is to try different computers/USB ports. Also, in my case it only worked with Linux, EndeavourOS to be specific, but should work on Ubuntu or any other "complete" Linux OS/distro.
Don't wait on TWRP updates in this thread, get the latest version from the source and reflash it, it works for me on ROMs with Android 11 and 12: https://twrp.me/sony/sonyxperiaxz1compact.htmlAny ideas on why is failing to boot with the flashed recovery? Could this be related with the fact that there's no TWRP for Android 11 for the XZ1 Compact? Is there any alternative to TWRP?
I'm using Pie 9 TWRp 3310. It work fine. But after the reboot, I tried to flash something and all folder suddenly showing weird name, probably encrypted?
It's because of the encryption. Files on LineageOS 19 are encrypted if accessed via TWRP recovery, LineageOS 19 (maybe 18 also) has its own alternative recovery that can be installed during the first boot, perhaps the files are not encrypted if accessed from there. Either way, it's a security measure against unauthorized access to files. I'm pretty sure I've read somewhere that it's a default feature in Android 12.
The error 255 is caused due to insufficient space. One solution is to backup or restore one or several partitions at a time instead of all at once, alternative solution is to back up to external memory card.
Hello 4qxThe error 255 is caused due to insufficient space. One solution is to backup or restore one or several partitions at a time instead of all at once, alternative solution is to back up to external memory card.
Not entirely. Are you getting this error while trying to backup or restore?
I don't think you need to use any TWRP versions apart from the latest one. By "USB OTG is not recognized" you mean that you can't see your phone files from the computer while in recovery mode? If so, you can copy files to or from the phone with adb, for example:I have tried with TWRP3310,3509,35290,36190 and SD card, internal storage etc.
USB OTG is not recognized.
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc