• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

bgcngm

Recognized Developer
CTS profile check still fails on 06-04 build. Even with the fingerprint build fix included. Does Google perform additional checks nowadays? LOS16 didn't have the CTS profile check failing.

I wouldn't call is a "fix". The build fingerprint was updated on request. CTS profile was failing before and still fails with that one. I wonder if any build fingerprint for POCO F1 ever passed CTS. I use the old Oreo build fingerprint on my MIX 2S and CTS profile check passes.
 

psherbet

Member
Nov 15, 2015
15
1
I have CTSprofile true with MagiskHide Props Config and setting fingerprint to Poco F1.

I'm on lineage-17.1-20200405-nightly-beryllium-signed.zip
 

psherbet

Member
Nov 15, 2015
15
1
What is the build fingerprint that you're using?

A2NH9v7.png
 

siroga825

Senior Member
Oct 30, 2015
266
65
Yea, you're forcing the latest one. New builds are already using that one.
I did update to todays build, but after disabling props config, it was failing again.

Btw, can you tell me please name of package that is responsible for fingerprint authorisation vibration? There is no option to disable it in menu, but i found terminal method :)

---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------

I know this procedure but my bank application does not work that way.

Is there any other way without using Magisk root an Magisk hide?

Try clean install, lastest build should already have implemented lastest fingerprint (license? Or what is it) so it should pass without magisk

Otherwise idk, im not using any banking apps on phone :/
 

youvedone

Senior Member
Apr 9, 2015
255
76
Man, you guys are so confused regarding encryption.

Flashing a recovery image has nothing to do with encryption.

Encryption only concerns the Data partition/Internal Storage.



If you need help, you need to give us the error output you got.

Also, whether you have an Intel or AMD Ryzen.



Also, how did you flash LOS without TWRP installed?



If you need help, give us the error outputs you got.
Why is intel or ryzen relevant?

Gesendet von meinem POCO F1 mit Tapatalk
 

Yadiesa

Senior Member
Jul 28, 2019
51
11
Hello dev..
WhatsApp still freezing then no response sometime. After watching video on chat
See screenshot
 

Attachments

  • IMG-20200407-WA0003.jpg
    IMG-20200407-WA0003.jpg
    42.6 KB · Views: 552

exodius48

Senior Member
Apr 7, 2013
3,555
674
Yori's Heart
Xiaomi Mi 11 Ultra
I know this procedure but my bank application does not work that way.

Is there any other way without using Magisk root an Magisk hide?

Hide these apps: your bank app, Google play services, gogle service framework, google play store
Then delete bank app from magisk root (if any) or simply uninstall magisk manager app then reinstal it. Use magisk latest from here https://github.com/topjohnwu/Magisk/releases
Mandatory: Hide magisk manager app and delete any files of magisk related from your phone memory like obsolete module.zip , etc etc.

If still does not work and you need bank app, memeUI with locked bootloader is right for u
 

bigwillie1

Senior Member
Apr 27, 2008
52
7

I used the 06-04 LOS 17.1 build with the updated device fingerprint --> CTS profile match failed. Then I used the MagiskHide Props Config (like the instruction above) and now the CTS profile checks. Maybe the MagiskHide Props Config module changes something else other then the Device Fingerprint? And maybe that can be changed to the LOS17.1 code? So that installing an additional module isn't necessary anymore ;)?
 

[email protected]

Senior Member
Mar 6, 2013
317
242
Mumbai
@bgcngm

Thanks for this commit
https://review.lineageos.org/c/LineageOS/android_device_xiaomi_beryllium/+/272196/

I guess we will also need the secutity patch to be dated :"2020-02-01".

ro.build.version.security_patch=2020-02-01

edit: I don't think changing patch date is possible.

What is the build fingerprint that you're using?

I used the 06-04 LOS 17.1 build with the updated device fingerprint --> CTS profile match failed. Then I used the MagiskHide Props Config (like the instruction above) and now the CTS profile checks. Maybe the MagiskHide Props Config module changes something else other then the Device Fingerprint? And maybe that can be changed to the LOS17.1 code? So that installing an additional module isn't necessary anymore ;)?


@bgcngm

I had a look at MagiskHide Props. The Module changes the Build Fingerprint as well as the Security Patch Date.
So basically, if Fingerprint and security patch dates match, it will pass.
If i'm not wrong, then the current Fingerprint on the LOS ROM will work only if the Security Patch Date is 2020-02-01.
However, in our case LOS is on March Security Patch. So the fingerprint and Patch dates do not match. Which leads to the SN fail.
 
Last edited:

siroga825

Senior Member
Oct 30, 2015
266
65
@bgcngm

I had a look at MagiskHide Props. The Module changes the Build Fingerprint as well as the Security Patch Date.
So basically, if Fingerprint and security patch dates match, it will pass.
If i'm not wrong, then the current Fingerprint on the LOS ROM will work only if the Security Patch Date is 2020-02-01.
However, in our case LOS is on March Security Patch. So the fingerprint and Patch dates do not match. Which leads to the SN fail.

So basically older, less secure patch will make cts pass? Kinda stupid from google.
 

fluorecente

Member
Mar 25, 2007
37
8
@bgcngm

I had a look at MagiskHide Props. The Module changes the Build Fingerprint as well as the Security Patch Date.
So basically, if Fingerprint and security patch dates match, it will pass.
If i'm not wrong, then the current Fingerprint on the LOS ROM will work only if the Security Patch Date is 2020-02-01.
However, in our case LOS is on March Security Patch. So the fingerprint and Patch dates do not match. Which leads to the SN fail.

Is it possible to change the Security Patch Date to 2020-02-01?
If possible I try to set this date to see what happens.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 135
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:
    yG18r6g.png

    Working:
    • Camera (and flashlight)
    • WiFi
    • Bluetooth
    • Telephony (Calls and Data)
    • IMS (VoLTE and WiFi Calling)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • Encryption (FBE / FDE)

    Broken:
    • Nothing (?)

    Compatibility:
    Compatible with all Xiaomi Poco F1 variants.​
    Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v11.0.3.0 global stable package.​

    Downloads:

    Notice:
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

    Installation:
    • Reboot to recovery
    • Format /system, /data and /cache
    • Install LineageOS zip package
    • Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
    Important notes:
    • * Required * firmware version must be based on MIUI Q-based builds.
    • GApps can only be flashed on clean installs.
    • Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    Credits & collaborations:
    All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​

    Device wiki:
    51
    Enjoy everyone. :)
    42
    Will you gonna maintain this rom?

    Obviously. Did you ever look at the wiki and the list of maintainers? ;)
    35
    The silence is certainly the best reply for the ignorant people.

    Sent from my Mi MIX 2S using Tapatalk
    22
    Lost magisk again when updating OTA with latest recovery. Now I have to plug my phone into my PC and flash back to TWRP because LOS recovery still doesn't have working decryption.

    Why not delist this recovery until it works? Lol ? Very broken.
    Dude, LineageOS recovery is not broken just because you lost Magisk. Also, not having decryption support doesn't mean it's broken. No one forces you to use LineageOS recovery, so you are free to use TWRP recovery. Finally, you are not even forced to use LineageOS at all, but at least show some respect for the people that brings you stuff for free.