At the moment there are no official builds so if you flash an unofficial build over an official, clean flash is really advised!Does anyone know if upgrading 19.1 > 20 will need a clean flash/data wipe?
BTW, did you ever execute this step in the magisk installation documentation:
It says it is optional. It looks like you only need to set some flags or parameters to this partition, nothing is said about what vbmeta.img file. I never did it and never had a problem with Magisk itself. Problem is I have no idea what it does, why it is optional and how you can diagnose if you need it. And if you need to flash this manually after every OTA or if it is a one time only.
- (Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Any idea on this?
This device uses Android Verified Boot (AVB)
This means that installing TWRP or swiping to allow system modifications will prevent you from being able to boot. To bypass AVB's boot prevention, you will have to disable it or install a custom ROM that ships with disabled AVB.
To disable AVB via fastboot, grab the vbmeta image from the ROM you are on, and flash it with the following command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
AVB should be now disabled on your device.
This is LOS thread not MIUI. Ask in the proper section.hello
should I unlock first and then install payload miui 13.0.3 global
Or first payload miui13.0.3 and then unlock ?
and also when we unlock poco f3 can we lock it again if we install miui official?
thank you please help
Install miui 13.0.3.0 global with payload is the first instruction in LOS official website .
I once flashed a lineage update in twrp and wasn't able to boot afterwards. Reflashing the old version in lineage recovery fixed it.I accidentally found the answer on the TWRP page. If you google twrp alioth you will get a different landing page for F3 than if you navigate the devices page. On the old page there is nothing about vbmeta but the new page has:
For me this was probably done by LOS at first install.
So, if it's the first instruction, why did you feel the need to ask if you should do it first?Install miui 13.0.3.0 global with payload is the first instruction in LOS official website .
that was a simple question senior
https://wiki.lineageos.org/devices/alioth/upgradeThank you very much for the project. I had been using 18.1 but decided to finally update. However I need to mention, the information here;
-is correct for M2012K11AG. That is whats in this thread, but I didn't know to come here specifically. I tried to follow this website;Install LineageOS on alioth | LineageOS Wiki
wiki.lineageos.org
-where the information must be outdated, because following it leads to a FASTBOOT loop. There is no mention of vendor_boot.img or MIUI firmware, and there is no link to the lineageos.wiki page with more up to date information. Thankfully being stuck in FASTBOOT allowed me to follow the wiki page here but until then it was a scare. I have no idea how I came to that website before the official wiki guide, it was just in my bookmarks so I goofed up.![]()
Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) - LineageOS ROMs
Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) Official roms Download last nightly build (2023-01-07) (mirror EU).LineageOS 19.1 – [ Android 12.1 (Snow Cone) ] [Recovery file (2023-01-07) (mirror EU)] Previous version (nightly) (2022-04-16) LineageOS 18.1 – [ Android 11.0 (Red Velvet Cake) ]...lineageosroms.com
Also, could Magisk be added to the instructions? It wasn't hard to figure out by following the GitHub instructions, but I was under the impression I had to flash it through LineageOS recovery, when it only actually works if you boot back into fastboot and flash it through there
No. This is LOS thread, magisk or any other 3rd party is NOT supported.
To flash anything you need to unlock first. Even stock rom needs unlock if you are trying fastboot flashing. Locked bootloader = OTA only (via official updater app)hello
should I unlock first and then install payload miui 13.0.3 global
Or first payload miui13.0.3 and then unlock ?
and also when we unlock poco f3 can we lock it again if we install miui official?
thank you please help
Just to be sure, i need to sideload this at point 6 from this guide right?#ih8sn
- What does this do?
- Spoof build as a user build (lineage builds are userdebug).
- Spoof bootloader unlock status.
- Spoof security patch date to match build. (Due to this you will see out of date android security patch warning in lineage privacy trust section, ignore it)
Download:![]()
Installation: Follow this guide.
Note:
- Spoofing stays in ota updates.
- Might not work with magisk installed.
- Use ih8sn-uninstaller.zip to uninstall.
@althafvly I can confirm that. CTS profile match fails but ih8sn works.Actually, I'm experiencing the same problem with ih8sn. All the relevant properties (ro.build.fingerprint, ro.build.version.security_patch, etc.) have the correct values that match ih8sn.conf when queried with adb shell getprop command. However, YASNAC and other older SafetyNet checkers report CTS profile failure. YASNAC displays values that match ROM security patch date and true model.
ih8sn seems to working (at least partially) since advice to relock bootloader no longer appears when ih8sn is installed.
It's broken after recent changes in safetynet. So far haven't found a workaround (unrooted). Use magisk safetynet fix for now.@althafvly I can confirm that. CTS profile match fails but ih8sn works.
You post about donating for the wrong reason (I don't believe you btw) hoping that your complaint somehow speeds up the release and you think the maintainer is the "schmuck"? smhI donated $100 to this schmuck of a maintainer and there is still no Android 13 in sight.
Yes! You are absolutely correct. One bug and all threads will be full of complaints.You incorrectly claimed that @[email protected] posted false info then pivoted into question that they already answered. Not needing to update the firmware as frequently (if at all) and smoother OTA updates is a good enough reason for me. It also explains why devices that are no longer receiving manufacturer updates have 20 already.
I would prefer the maintainer(s) to actually work on development or even take a well-earned break than having to explain their methods to us here. No matter what info was provided, somebody would question and challenge it anyway, just like you did.
It's a catch 22 situation. They have policies and systems in place which create a solid, desirable ROM with great support and updates yet people want them to bypass these policies and systems to speed up the release. I bet those same people are the first to complain if something goes wrong.
Let them cook!
Does LOS not use the compass app the way MIUI does? Calibrating my compass and enable it to autostart in MIUI helps dramatically for me.I really hope that the new firmware paired with the LOS 20 relase fixes the proximity sensor issue, I'm so tired of that that I consider to sell the phone and buy one with a physical proximity sensor.