Development [ROM][OFFICIAL][alioth/aliothin][12.1] LineageOS 19.1

Search This thread

festor

Senior Member
Jun 4, 2013
149
98
It's just impatience on my part. I'll have some time this weekend so I was going to try 19.1 (from stock) but I should just hold out for 20.0 stable.

DT2W and haptics don't work on the 20.0 beta (not a dealbreaker for me) but it comes with V13.0.6.0.SKHMIXM firmware so I might have more issues with my EEA phone/firmware. I see that beta > stable also might require a clean flash anyway.
 
  • Like
Reactions: duttyend

barturblits

Senior Member
Jul 4, 2014
336
80
BTW, did you ever execute this step in the magisk installation documentation:

  • (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
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.

Any idea on this?

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:

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.

For me this was probably done by LOS at first install.
 
  • Like
Reactions: duttyend

pedramtt

Senior Member
May 3, 2010
68
32
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
 

McFlypants

Senior Member
Mar 22, 2013
388
150
Xiaomi 12
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.
I once flashed a lineage update in twrp and wasn't able to boot afterwards. Reflashing the old version in lineage recovery fixed it.

Did this bootloop come from flashing in twrp?
 

booci

Senior Member
Jan 28, 2009
135
92
Buzau
Install miui 13.0.3.0 global with payload is the first instruction in LOS official website .
that was a simple question senior
So, if it's the first instruction, why did you feel the need to ask if you should do it first?
This also is on the official website: "Warning: Before following these instructions please ensure that the device is currently using the firmware version mentioned below". First word in the warning is literaly "Before".
 

goshgrr

New member
Feb 2, 2023
1
0
Thank 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;
-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.
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
 

oirtemed

Member
May 22, 2022
9
15
Thank 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;
-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.
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
https://wiki.lineageos.org/devices/alioth/upgrade
^ I'd suggest reading the upgrade instructions from the official wiki
 

TitaniumGom

New member
Jan 14, 2023
2
4
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
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)
There still is a way to flash things with locked bootloader which is called EDL mode, but for Xiaomi devices it is not really open for public.

If you are going back to stock rom then yes you can lock it again. Just make sure you are on global device (Poco F3) not China thing (K40) since China device + Global stock rom + Locked bootloader means soft brick.
 
Last edited:

neves2k

Member
#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.
Just to be sure, i need to sideload this at point 6 from this guide right?

I flashed Gapps, rebooted to system, rebooted back to recovery & flashed #ih8sn.
It flashed successfully but CTS Profile match is failing.

If anyone could just tell me if #ih8sn it's still working or not I would appreciate so I don't clean flash again for nothing.

EDIT 1: I clean flashed anyways. CTS Profile match keeps failing but Netflix (Known app that doesn't work without safetynet) now shows up and installs from PlayStore... Guess it's working?
Also something i noticed is that after using ih8sn the device certified option in PlayStore just vanished xD

EDIT 2: I did a clean install and didn't applied ih8sn, after installing my bank app it triggered the safetynet issue. So i just went to lineage recovery and sideloaded ih8sn, rebooted into system, and now the app works.
So yeah, even that CTS Profile match fails, this fix safetynet.

Also something that I miss on this lineage build it's the lack of change the system color :/ By default it just picks up the wallpaper color... Hope this feature gets in next versions. I like to have it selected to a solid color only.

Thank a lot anyways for this amazing ROM! :)
 
Last edited:

guest2free

Member
Feb 18, 2018
13
7
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.
 

booci

Senior Member
Jan 28, 2009
135
92
Buzau
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.
@althafvly I can confirm that. CTS profile match fails but ih8sn works.
 
  • Like
Reactions: duttyend

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    I donated $100 to this schmuck of a maintainer and there is still no Android 13 in sight.
    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"? smh

    I often wonder if requests for quicker releases are just from trolls trying to get unpaid devs to abandon projects. Nobody could be stupid enough to believe demands from randoms would in any way motivate people who are working for free... surely? Would these requests make you work harder?

    The maintainer(s) are currently working on 20 while still maintaining 19.1 with more updates than other ROMs. If you genuinely want a quicker release and not for them to step down, show some patience and maturity.

    https://download.lineageos.org/devices/alioth/changes
    5
    Look, the reason for delay is somewhat technical.
    The thing is, with lineage, unlike other ROMs, they have to stick with a specific Firmware version.

    If LOS 20 is relased for the device now, it will be stuck with the current MIUI 13 firmware for the entirety of LOS 20 lifespan of our device.

    Even for LOS 19, you can read in wiki. The recommended firmware is way back from May 2022. Not the latest.

    This is to ensure that OTA updates work smoothly and dont break some vital function of the device.

    Other ROMs often require updating the firmware too occasionally, but LOS sticks with one version for life of the version.

    So in short, it is better to wait for Official MIUI 14 fw to drop rather than having to being stuck with Android 12 firmware on a Android 13 ROM.

    Hope this clears up things!
    Cheers.
    4
    New firmware is out for EU region: V13.0.11.0.SKHEUXM. So far everything works great.
    3
    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!
    Yes! You are absolutely correct. One bug and all threads will be full of complaints.

    @alfix8
    The reason is very simple and pro-user.

    If you are on TG, you surely would know that lots of people often complain that their audio is broken or even face issues with choppy video playback after updates.
    The fix for this is to update their firmware to the recommended versions.

    With LineageOS, once you install LOS the first time with the correct recommended firmware, you can rest assured that you wont need to use a computer for future updates on that version.You can simply use the OTA updates and have peace of mind knowing that nothing will break. SInce the ROM is tested with a single firmware, the baseline is set and it is easier for everyone.

    With other ROMs you might need to check whether the recommended firmware has changed and perform necessary actions.

    And yes, that clearly explains why older Devices already have LOS 20. They dont receive FW updates. So the baseline is fixed.

    Another Trivia:
    LOS 19 was released on 26th April 2022, A12 firmware was released Mid April 2022.
    Our device got official LOS on 14th May 2022.

    LOS 20 was released of 31st December 2022. But we still don't have A13 firmware.

    One silver lining is that a lot of LOS 20 source-side bugs will be fixed since lots of other devices are using LOS 20 for the last 3 months. We'll get a rather refined experience.

    Have Patience!
    2
    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.
    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.
  • 44
    lineageos-png.5317459
    LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), 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)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • VoLTE/VoWifi
    Bugs:
    • Nothing (?)

    Downloads:

    Wiki:

    Note:
    • Must follow installation wiki for this device.
    • 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.
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported.
    • Flashing LineageOS through custom recovery is not supported and not advised. Use LineageOS Recovery instead. Right now, Lineage Recovery is really only intended to be used on devices with Seamless Updates (aka A/B partitions) and, in that role, it is only intended to be embedded within the OS's normal Boot image. While flashing TWRP, it replaces boot image's ramdisk (possible security risks), also using TWRP might break ota updates and cause other issues with LineageOS like bootloops.
    Bug reports:
    • DO NOT report bugs if you're running a custom kernel, recovery or Xposed or Magisk mods.
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.).
    • Report bugs here: https://wiki.lineageos.org/how-to/bugreport#reporting-a-bug

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

    Support:
    XDA is preferred for main discussion. But if you need any other support, check unofficial support group. We strongly discourage direct contact with devs through social media.

    Credits :

    @SebaUbuntu

    @Sahil_Sonar


    DONATIONS : Paypal
    16

    SafetyNet


    By default LineageOS doesn't pass SafetyNet, why?, Check here https://lineageos.org/Safetynet

    You can use this unofficial method to pass SafetyNet: ih8sn Broken after recent changes
    15
    LineageOS 19.1 official build is out

    Make sure follow steps before upgrading to lineage-19.1

    - Follow this fresh install https://wiki.lineageos.org/devices/alioth/install
    - Follow this for upgrade https://wiki.lineageos.org/devices/alioth/upgrade

    - Install Android 12 Gapps after installing rom (if you use)
    - Update firmware to required firmware version MIUI 13.x.x builds (Based on Android 12).
    V13.0.5.0.SKHCNXM 12.0 China
    V13.0.4.0.SKHEUXM 12.0 Europe
    V13.0.4.0.SKHINXM 12.0 India
    V13.0.2.0.SKHMIXM 12.0 Global
    15
    Note: This method might not work anymore.

    #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.
    9
    Unofficial LineageOS-20.0 build for alioth/aliothin

    - Download

    Known bugs:
    - None

    Note:
    - Do not try to upgrade from official LineageOS-19.1
    - Installation is same as LineageOS-19.1
    - Required firmware is same as LineageOS-19.1
    - GAPPS build includes ih8sn.
    - No guaranteed updates for these builds.
    - Report bugs with logs