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

[lehnin]

I noticed my Tan apps started working again after the January 16th Update, any clue why?

cts profile still fails.
Before they stopped after an Lineage Update. (around april 30th 2020)
I tried all kind of Magisk settings, had no luck

Also sometimes Magisk is not persistent after OTA.

Also if you have issues decrypting the filesystem in twrp after an OTA try updating twrp.

 

[- Chaorrupted X -]

I noticed my Tan apps started working again after the January 16th Update, any clue why?

cts profile still fails.
Before they stopped after an Lineage Update. (around april 30th 2020)
I tried all kind of Magisk settings, had no luck

Also sometimes Magisk is not persistent after OTA.

Also if you have issues decrypting the filesystem in twrp after an OTA try updating twrp.

I got ctsProfile pass.

Did you tried flashing SafetyNet Fix through Magisk? And install MagiskHide Props Config from Magisk Module, then change your device fingerprint.

 

[lehnin]

I got ctsProfile pass.

Did you tried flashing SafetyNet Fix through Magisk? And install MagiskHide Props Config from Magisk Module, then change your device fingerprint.

Yes, as said this fails now, but tan apps work again.

 

[cyanogensid]

going into fastboot while updating to the 23rd build from 16th
using the same dfe i used before
the only difference was that i updated my twrp to 3.5.0 from 3.3.0
can anybody tell me what should i do, i have tried downgrading to 3.3.0 ,getting the same loop to fastboot
Edit- also updated my firmware day before yesterday to 12.0.3.0
can it be cuz of that?

its saying reason=set_policy_failed:/data/misc
2nd edit- made a nandroid backup from twrp , cleared wipe everything except internal storage flash all the requirements again, got booted into the rom , got into the welcome screen , then rebooted into recovery and restore only data , now everything is working fine TWRP BACKUP RULES !!!!!

 

[Jack Nuddels]

Hi,

one short question. Where can I get an actual vendor/firmware? The forum search brings me to the formwareupdater but on that page is nothing for the Poco F1 ¯\_(ツ)_/¯.
Or isn't it necessary for 17.1?
Thanks for advice

 

[CHGICEMAN]

Here https://xiaomifirmwareupdater.com/archive/firmware/beryllium/

 

[Jack Nuddels]

Here https://xiaomifirmwareupdater.com/archive/firmware/beryllium/

sorry I was dump, had the scriptblocker still on, so there were no content shown -.-

 

[bladehunter]

I got ctsProfile pass.

Did you tried flashing SafetyNet Fix through Magisk? And install MagiskHide Props Config from Magisk Module, then change your device fingerprint.

Hey Can you please tell how to change device fingerprint?
I installed SafetyNet Fix , MagiskHide Props Config and enabled magisk hide for play services and play store but ctsProfile still fails

 

[CHGICEMAN]

Here https://xdaforums.com/t/rom-officia...-xiaomi-poco-f1.4048205/page-23#post-82168217

 

[Smultie]

Hi, I'm noticing ghost touches since a couple of builds. Could of course also be related to the firmware.
Anyone with a helpful hint?

 

[bladehunter]

Here https://xdaforums.com/t/rom-officia...-xiaomi-poco-f1.4048205/page-23#post-82168217

SafteyNet passes, but banking apps still don't work. (Have switched on magiskHide for them). Kindly help.

 

[- Chaorrupted X -]

SafteyNet passes, but banking apps still don't work. (Have switched on magiskHide for them). Kindly help.

Repackage Magisk Manager with random package name. It's in the Magisk settings.

I tried several banking apps, it works.

 

[senpaidev]

Getting bootloops on 30th Jan build. I am updating from 16th Jan build. Anyone else facing this issue? Any solutions. While flashing, I noticed that Magisk was not persisting.

 

[kingnick]

Getting bootloops on 30th Jan build. I am updating from 16th Jan build. Anyone else facing this issue? Any solutions. While flashing, I noticed that Magisk was not persisting.

I updated from the 16th to 30th Jan build also and my Poco is booting normally, I don't use Magisk.

 

[Gustl6500]

Here is the trick:
Settings->System->Advanced->Gestures->System navigation->Gesture navigation (gear icon)->Navigation hint (switch-off trigger)

Thanks for the hint, but the black bar under the keyboard or the free space still remains. The one you mentioned was deactivated anyway.

 

[cjchristopher]

Hi All,

just OTA updated using the in-built updater to 20210206 from 20210123 and have been stuck on the lineage boot animation for ages now.
Have interrupted it and flashed cache/dalvik and repatched the image, but this didn't make a difference.

Help!

EDIT/Update: I managed to fix it by following roughly the process here: https://www.reddit.com/r/LineageOS/comments/l3mqe9 This seems to be a problem with Gapps?
I... did a naughty and did NOT wipe the system partition, so it's a dirty flash of the latest nightly and then Gapps on top again... I note that the OP in this thread says that Gapps can only be flashed on a clean install. I have obviously not done that here, but my system seems stable.
Should I expect any weirdness having done it this way?

 

[cyanogensid]

Can anybody tell me how can I fix the google backup error
It's saying transport error everytime
:/ $ su
:/ # bmgr list transports
com.android.localtransport/.LocalTransport
com.stevesoltys.seedvault.transport.ConfigurableBackupTransport com.google.android.gms/.backup.migrate.service.D2dTransport
* com.google.android.gms/.backup.BackupTransportService
:/ # bmgr backupnow --all
Running incremental backup for all packages.
Package @pm@ with result: Transport error
Backup finished with result: Transport error
:/ # bmgr backupnow --all
Running incremental backup for all packages.
Package @pm@ with result: Transport error
Backup finished with result: Transport error
:/ # bmgr backupnow --all
Running incremental backup for all packages.
Package @pm@ with result: Transport error
Backup finished with result: Transport error
:/ # bmgr backupnow -all
Running incremental backup for 1 requested packages.
Package -all with result: Package not found
Backup finished with result: Success
:/ # bmgr backupnow --all
Running incremental backup for all packages.
Package @pm@ with result: Transport error
Backup finished with result: Transport error
:/ #

 

[puscasumarin]

Can anybody tell me how can I fix the google backup error

This is an old problem, unrelated to LineageOS. It doesn't happen to me (POCO F1 with the latest version of this ROM), but I've seen it happening on other phones. You can find some explanations and a temporary workaround here:
Android backups to Google Drive have been disabled on many phones for months — no proper fix in sight

 

[cyanogensid]

This is an old problem, unrelated to LineageOS. It doesn't happen to me (POCO F1 with the latest version of this ROM), but I've seen it happening on other phones. You can find some explanations and a temporary workaround here:
Android backups to Google Drive have been disabled on many phones for months — no proper fix in sight

I have tried removing the pin too, but that doesn't help.

 

[puscasumarin]

I have tried removing the pin too, but that doesn't help.

Sorry to hear that. What I was trying to say, is that you'll have a better chance finding answers for your problem in other places than this thread.