[ROM][DISCONTINUED] LineageOS 19.1 for Xiaomi Poco F1

[Retrial]

Flashing the zip doesn't help. It was indeed no clean install. But several system flashes were fine, only this update from TWRP v3 to v4 leads to the data partition not be able to be mounted anymore even though I switched back. Did the new version change anything regarding partitioning? I want to avoid a reset and clean install now as much as possible :-|

Sorry I looked different post and I thought you did dirty upgrade from 18 to 19. So many similar posts.
Twrp by reingz v4 changelog is that support Android 13. I don't know if anything else changed, but I personally upgrade to v4 fine and I am in crDroid which use LineageOS as base.
Are you sure you used v4 System ext version and not NSE?
You can try to ask @REIGNZ3 . I don't know what went wrong in ur case.

 

[blackby]

Sorry I looked different post and I thought you did dirty upgrade from 18 to 19. So many similar posts.
Twrp by reingz v4 changelog is that support Android 13. I don't know if anything else changed, but I personally upgrade to v4 fine and I am in crDroid which use LineageOS as base.
Are you sure you used v4 System ext version and not NSE?
You can try to ask @REIGNZ3 . I don't know what went wrong in ur case.

I did upgrade dirty from 18 to 19 but that was some time ago. I did run 19.1 fine and did no update on the system image. The only thing I did was flash the new recovery version and now I cannot boot anymore.

 

[Retrial]

I did upgrade dirty from 18 to 19 but that was some time ago. I did run 19.1 fine and did no update on the system image. The only thing I did was flash the new recovery version and now I cannot boot anymore.

If you are still on FDE encryption (coming from 18) then this twrp doesn't work correctly. The version of TWRP by REINGZ based on A12 working only with FBE.

 

[blackby]

If you are still on FDE encryption (coming from 18) then this twrp doesn't work correctly. The version of TWRP by REINGZ based on A12 working only with FBE.

Thats what I understand now. Even thoguh the system might not be using anymore. Any way I might access that still FDE-based data for backup purposes?

 

[hakkitarion]

Hello all,
I have a problem with screen mirroring on the Amazon Fire TV. I can select my Fire TV when I connect, but after a few seconds the Fire TV comes up with the message " display duplication is closed".
I remember it had worked earlier.
Any tips would be appreciated.

 

[Retrial]

Thats what I understand now. Even thoguh the system might not be using anymore. Any way I might access that still FDE-based data for backup purposes?

Idk if it's gonna work:
Try to "clean-dirty" downgrade according my dirty installation guide to Los 18 which u were and try with Official TWRP or with TWRP by REIGNZ A9.
If nothing works the only way is to clean install.

 

[LTFOUND]

Updated to the new TWRP version. I cannot decrypt the data in recovery. And now I cannot boot the system anymore, tells me the pin is wrong. Any suggestions?

Did you remove your encryption method before updating TWRP? I've always done that, just in case

 

[Deleted member 8833290]

Did you remove your encryption method before updating TWRP? I've always done that, just in case

I never did this and never had any problems. But it is a good practice, just in case.

 

[keypal]

I am a user in China, when I make a call, it hangs up automatically and the signal is lost, there is no problem with the previous version(lineageos18.1).

 

[jojy thomas]

I am a user in China, when I make a call, it hangs up automatically and the signal is lost, there is no problem with the previous version(lineageos18.1).

View attachment 5729231
View attachment 5729237

Carrier video calling is broken!

 

[jojy thomas]

Just installed today's ota update, all good

 

[keypal]

Carrier video calling is broken!

Please tell me what I should do,installed today's ota update,the problem still exists.

 

[jojy thomas]

Please tell me what I should do,installed today's ota update,the problem still exists.

Nothing,
The dev should fix it,

 

[keypal]

Nothing,
The dev should fix it,

Thank you for your answer. I hope the developer can fix it as soon as possible.

 

[sponk0]

FYI: today's build installed fine via OTA, all looks good so far. Security string updated to October 05

 

[first_damned]

I can't get the latest pixelify magisk module to work, anyone got any ideas? It's the only module I have installed, it just bootloops.

 

[TomBrix]

I think I have the same problem. Is there a way to make my F1 work again, like going back to "lineage-19.1-20221008-nightly-beryllium-signed" and if yes, how? Do I just install it via TWRP?
Thanks.

 

[first_damned]

I think I have the same problem. Is there a way to make my F1 work again, like going back to "lineage-19.1-20221008-nightly-beryllium-signed" and if yes, how? Do I just install it via TWRP?
Thanks.

What's your problem?

 

[TomBrix]

I was coming from "lineage-19.1-20220924-nightly-beryllium-signed" (or perhaps earlier) and installed "lineage-19.1-20221015-nightly-beryllium-signed" via LOS updater. During update in TWRP I saw a message "binaries for magisk" missing (or similar). However, the phone rebooted and is now in a bootloop (circle of LOS logo is going from right to left a few times, then reboots).

 

[Retrial]

I was coming from "lineage-19.1-20220924-nightly-beryllium-signed" (or perhaps earlier) and installed "lineage-19.1-20221015-nightly-beryllium-signed" via LOS updater. During update in TWRP I saw a message "binaries for magisk" missing (or similar). However, the phone rebooted and is now in a bootloop (circle of LOS logo is going from right to left a few times, then reboots).

You can try to manually update the ROM / fix bootloop.

• Download the ROM+GApps in your PC
• Boot to twrp by REIGNZ based on A12 System_Ext
• Transfer the ROM+Gapps while u are connected to pc and in twrp
• Wipe System, System_ext, Vendor, Dalvik Cache, Cache
• Flash the updated build, Gapps
• Boot to system
• If it works boot to twrp again and flash Magisk.