Originally, i thought that i have 220.127.116.11 but it turns out i have 18.104.22.168 (SKHMIXM). I have no issues with LOS functions and everything works fine on 22.214.171.124.SKHMIXM (bluetooth, sound, calls, messages, 4G). The only thing i cannot test is VoLTE because i have no subscription with support for it.If theres anyone here using any of these models with lineageos, then please let me know which firmware version is working fine for you.
- POCO F3 Global : V126.96.36.199.SKHMIXM
- Mi 11X India : V188.8.131.52.SKHINXM
- POCO F3 Turkey : V184.108.40.206.SKHTRXM
- POCO F3 Taiwan : V220.127.116.11.SKHTWXM
- POCO F3 Indonesia : V18.104.22.168.SKHIDXM
- POCO F3 Russia : V22.214.171.124.SKHRUXM
- POCO F3 EEA : V126.96.36.199.SKHEUXM
- Redmi K40 China : V188.8.131.52.SKHCNXM
Note : Broken firmware usually have audio/touch issues
@althafvly could you maybe look at this? Thanks a lot@althafvly
I dived some deeper into the 4G Calling issue.
What we found out is that vendor.prop (https://github.com/LineageOS/android_device_xiaomi_sm8250-common/blob/lineage-19.1/vendor.prop#L241) refers to oem_sw_j11.txt
However, oem_sw_j11.txt has no reference to KPN (my provider).
Other files in the /data/vendor/modem_config do have reference to KPN:
alioth:/data/vendor/modem_config/mcfg_sw # grep -i kpn *.txt
Could that be the issue?
That prop is same as your stock miui. mcfg_sw is in modem.img in firmware (lineage just mounts that image in vendor partition). If you use any other region firmware you might have this issue, use firmware of EU region for poco f3 EEA. Follow linked guide to flash firmware.
I dived some deeper into the 4G Calling issue. What we found out is that vendor.prop ([URL]https://github.com/LineageOS/android_device_xiaomi_sm8250-common/blob/lineage-19.1/vendor.prop#L241[/URL]) refers to oem_sw_j11.txt However, oem_sw_j11.txt has no reference to KPN (my provider). Other files in the /data/vendor/modem_config do have reference to KPN: alioth:/data/vendor/modem_config/mcfg_sw # grep -i kpn *.txt mbn_eea.txt:mcfg_sw/generic/EU/KPN/Commercial/NL/mcfg_sw.mbn mbn_sw.txt:mcfg_sw/generic/EU/KPN/Commercial/NL/mcfg_sw.mbn oem_sw_l3a_eea.txt:mcfg_sw/generic/EU/KPN/Commercial/NL/mcfg_sw.mbn Could that be the issue?
That also interrests me. So far I was using ADB sideload for all firmware updates.
It's to avoid third party files, yes.@althafvly
The instructions for upgrading the firmware now describe extracting it with payload-dumper-go from the original ROM and then flashing the individual files through fastboot.
However, there are also flashable zips of the firmware available from xiaomifirmwareupdater.com which, as far as I can tell, are flashing exactly the same files in the same order.
Did you write the instructions for the firmware updates this way so users don't have to rely on third party websites to provide flashable zips or do those zips not work anymore for some reason?
He was the dev. If we couldnt trust any single file he decided, what's worth a rom flashing for.
This rom which proceed to 'a slim-hardened' version + n0kernel balanced
OTA update or did you sideload it?Hello all,
For your information, the latest ROM build is working fine for me (and no loss of Magisk or modules in the update process).
The kernel has not been updated to 4.19.255 yet (you can follow mainstream releases at www.kernel.org).
The security string has been updated to 2022-08-05.
- What does this do?
- Spoof build as a user build (lineage builds are userdebug).
- Spoof bootloader unlock status.
Spoof build fingerprint as an old device (mi 8 in our case). Why ? Else its pain to pass without root.(No longer spoofs as mi 8, POCO F3 by default)
- Latest platform-tools from https://developer.android.com/studio/releases/platform-tools or android studio.
- With adbroot
1. Extract the ih8sn-aarch64.zip in a folder with 'adb' access or in platform-tools folder.
2. Turn on USB debugging and Rooted debugging in Settings> System> Developer options.
3. Connect phone to PC
4. Open powershell/terminal in your location and run push script. (.sh/.ps1)
- With recovery
1. Boot into recovery (Volume UP + Power)
2. Apply update > Apply from ADB
3. In terminal : adb sideload ih8sn-aarch64.zip
4. Click yes for verification failed
- Adding 60-ih8sn.sh file will keep the spoofing stay in ota updates.
- Re-flash same ih8sn.zip/push-script to uninstall.
Use Magisk Delta, turn off Zygisk and it will work fine. Although I don't understand why not use the modules, since you got Magisk anyway.I decided to give ih8sn a try today. So far I passed safetynet with MagiskHide props config and Universal safetynet fix. I disabled both modules and rebooted into recovery -> sideload ih8sn. After reboot I checked status with YASNAC but it won't pass! Both basic integrity and CTS failed. I decided to try it again, uninstall/install ih8sn via recovery, but it didn't work! Can anyone give my tips on that?
So far my setup is working to pass safetynet, however with ih8sn I can get rid of two magisk modules.