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

[GeForce66]

Are you using the "secure startup" option where you have to enter your pin or pattern during boot? During my trial runs FDE was also working when secure startup was disabled, but after enabling it I got bootloop again

Noob question: is secure startup something different or is it the same as setting a normal lock screen pin?

 

[simpz]

Noob question: is secure startup something different or is it the same as setting a normal lock screen pin?

My boot looping phone is set to take a password to decrypt the disk.

 

[GeForce66]

My boot looping phone is set to take a password to decrypt the disk.

Hmm I also had the bootloop after upgrading without having a password (only lockscreen pin+fingerprint), but then again at that time LOS didn't have the tbe FDE support commits.

 

[Alias X]

Noob question: is secure startup something different or is it the same as setting a normal lock screen pin?

No, when enabled you have to apply your pin or pattern before the system loads any apps, on a dark background. Only a thing on FDE as far as I'm aware.

 

[Largamelion]

I just solved two issues I had been struggling with for a while on LOS 18.1:

- No internet on AA even though 4G icon is present (could be fixed by toggling airplane mode after connecting the phone to the car)
- Not able to text (SMS) people from one certain provider (Proximus)

I disabled VOLTE (which also disabled VOWIFI) and now everything is back to normal. I never had the impression it worked anyway but it never seemed to give me any other issues, other than the two mentioned above. My provider is Orange if anyone wonders and I live in Belgium.

 

[first_damned]

LOS recovery works. Though maybe not like TWRP. With every OTA update root is lost so far. TWRP patched the image automatically when performing OTA update. Apparently LOS recovery does not. Can anyone confirm?



Here it says Android 12 is not supported yet: https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html

Use Lygisk beta with lineage recovery to keep root on ota updates

 

[nachovb]

Hi,

I've upgraded my poco to LI

Installed 05 14, works fine.
Computer (USB) only recognizes Poco F1 while Twrp is active. (Works normally for Moto G7+) ??
Also Twrp will not retain 'Settings'.
Any thoughts?

Hi,

I've upgraded to LOS 19 with a clean install and I'm using LOS Recovery. My computer now does not show Poco F1 in file explorer, nor does it work with adb. However the Safely Remove Hardware icon does show remove Poco F1.

Booting in recovery works fine and I can sideload images and magisk.

Is this a known bug or only happens to me?

Thanks

 

[GeForce66]

Hi,

I've upgraded my poco to LI

Hi,

I've upgraded to LOS 19 with a clean install and I'm using LOS Recovery. My computer now does not show Poco F1 in file explorer, nor does it work with adb. However the Safely Remove Hardware icon does show remove Poco F1.

Booting in recovery works fine and I can sideload images and magisk.

Is this a known bug or only happens to me?

Thanks

Same here! I have no solution ...

 

[fluorecente]

Hi,

I've upgraded my poco to LI

Hi,

I've upgraded to LOS 19 with a clean install and I'm using LOS Recovery. My computer now does not show Poco F1 in file explorer, nor does it work with adb. However the Safely Remove Hardware icon does show remove Poco F1.

Booting in recovery works fine and I can sideload images and magisk.

Is this a known bug or only happens to me?

Thanks

The same here.
I just checked and it doesn't detect the device.
My computer now does not show Poco F1 in file explorer, nor does it work with adb.
In lineageos recovery the device is detected and I can update the firmware..

 

[bigsatan]

The same here.
I just checked and it doesn't detect the device.
My computer now does not show Poco F1 in file explorer, nor does it work with adb.
In lineageos recovery the device is detected and I can update the firmware..

Working here, using linux mint

 

[simpz]

No, when enabled you have to apply your pin or pattern before the system loads any apps, on a dark background. Only a thing on FDE as far as I'm aware.

Yup that's right. Though I have mine set with option 3, a complete password. It will not boot until the code is entered decrypting the drive.

I wonder how you can get a boot log to see what it's outputing and maybe what's tripping it up.

 

[AtomicStryker]

Hi,

I've upgraded my poco to LI

Hi,

I've upgraded to LOS 19 with a clean install and I'm using LOS Recovery. My computer now does not show Poco F1 in file explorer, nor does it work with adb. However the Safely Remove Hardware icon does show remove Poco F1.

Booting in recovery works fine and I can sideload images and magisk.

Is this a known bug or only happens to me?

Thanks

Same here! I have no solution ...

The same here.
I just checked and it doesn't detect the device.
My computer now does not show Poco F1 in file explorer, nor does it work with adb.
In lineageos recovery the device is detected and I can update the firmware..

Works fine for me, on current 14.05. build. Did you unlock and change the USB mode to "file transfer"? If you just plug it in, it charges and nothing else. But it always worked like that, back in LOS 18.1 aswell

 

[nachovb]

Works fine for me, on current 14.05. build. Did you unlock and change the USB mode to "file transfer"? If you just plug it in, it charges and nothing else. But it always worked like that, back in LOS 18.1 aswell

View attachment 5618741

Yes, unlocked and changed usb mode to File Transfer

 

[fluorecente]

The same here.
I just checked and it doesn't detect the device.
My computer now does not show Poco F1 in file explorer, nor does it work with adb.
In lineageos recovery the device is detected and I can update the firmware..

Found solution.
Reinstall ADB driver on windows

 

[GeForce66]

Found solution.
Reinstall ADB driver on windows

Can confirm it is related to drivers.
For me Windows used an ADB driver even though phone was in MTP mode with ADB disabled in developer options.
Simply went into device manager, selected to update driver and manually selected "MTP device" from the list - voila, it was showing again in win explorer

 

[fluorecente]

Can confirm it is related to drivers.
For me Windows used an ADB driver even though phone was in MTP mode with ADB disabled in developer options.
Simply went into device manager, selected to update driver and manually selected "MTP device" from the list - voila, it was showing again in win explorer

For windows 10:
1. With the mobile connected, uninstall the driver from the device manager
2. Disconnect the mobile.
3. Connect the mobile and let Windows install its own driver.

 

[penticton8]

2022 05 21 installed, got bootloop, anyone else ??
(Twrp came up ok but would not install from sd card or
restore, had to factory reset).

 

[P373]

Did a successful clean install with 19.1 2022-05-21 (before 17.1). Mindthegaps arm64 was installes successfully too.
Expected problems with FDE didn't appear.

Installed with LOS Recovery.

 

[simpz]

Did a successful clean install with 19.1 2022-05-21 (before 17.1). Mindthegaps arm64 was installes successfully too.
Expected problems with FDE didn't appear.

Installed with LOS Recovery.

I'm confused by your post.
You did a clean install, so blanked the old data?
In which case it won't do FDE for a new install so it should just work.

Or you did a dirty install without cleaning out data and it did prompt for a password/PIN/pattern before booting so used FDE successfully.

 

[jojy thomas]

2022 05 21 installed, got bootloop, anyone else ??
(Twrp came up ok but would not install from sd card or
restore, had to factory reset).

No issues. Use los recovery;why the headache?