Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
You can boot TWRP and mess with the system image from there. If you
fastboot boot your-recovery-image.imginstead offastboot flash...you should be able to load TWRP once without ever writing something to disk. From there, you may be able to prevent the re-flashing of the original recovery, and then perhaps flash TWRP permanently. You'll have to look around and figure out what's possible, but there's still some hope for you.If your native OS is maintained longer than Lineage, it may be wise to stick with that. You can also look got alternatives to LineageOS. For example, my device only has partial Lineage support, with community builds on XDA as the only source for ROMs, but crDroid has maintained images available and PixelOS even has an Android 14 ROM I can try.
For your phone, crDroid seems to be released last, almost exactly a year ago, but Asus updated it a month ago. I would stick with Asus' ROM in this case, and focus on sabotaging the recovery re-flashing.
You could also try to just... build LineageOS and see what happens. Once initial porting is done for an Android version, there's a good chance very little device specific features will break until the next major version comes out. If you have access to get a Linux server with at least 16GB of RAM and about 50-100GB of free space (Windows may work through WSL but no promises), you can build the entire ROM yourself.