Untill now yes, but read on xda portal the news, oneplus stopped their developer seeding program which should affect development on new devices.I moved with the latest nightly from official MIUI to LOS 14.1 and now this ...
Do OnePlus smartphones have the best support for Custom Roms of all Android devices?
Someone with High end computer or has access to cloud computing can build this rom with this guide.
But it is better to either hope or tell someone who has contributed patches to the other redmi note 3 roms to talk to lineage group and take charge of it.
Guys this is like the most stable rom out there, it's akin to stock rom and should not let it die as MIUI is withdrawing the support for this phone.
Great so kate firmware is fine too with current blobs (shipped in NON-HLOS/modem)
Thanks for confirming.
If you are coming from MIUI MM build directly, all should be fine.
So the ones having issues, fingerprint or loops, firstly clean flash the build.
Make sure you guys are using the latest compatible firmware (simply flash latest MIUI Dev ROM and do NO modifications with firmware then)
Some guys won't know if their fw is good to go or not, here's some info everyone should know about our device related firmwares. Explained with as simple words as possible.
PS: Before reading further, aboot=bootloader=emmc_appsboot.mbn
Initially our device was released with Android LP. And there was an unofficial way to unlock bootloader. What that actually was a modified aboot you flashed first which was based on LP firmware came with initial device launch.
Now things have been updated, RN3 got MM and yet some guys flashed old LP aboot knowingly or unknowingly.
For e.g. 1. For unlocking bootloader unofficial hassle free way
2. Later on, there were issues with some people having re-locked bootloader automatically when flashing the latest firmware I shared (obv it was pure miui fw zip from a miui release and not mixing of firmware).
Why did that happen with some users at not with everyone? Simple, our RN3 bootloader, when we upgrade it from LP release to MM it re-locked BL for us automatically.
Again, at that time, there were zips made by some users (not me) which said "this won't lock bootloader" and people flashed and thought they're good to go now. How did that zip differ from mine? It simply removed the updating of aboot from it and the zip didn't upgrade the aboot and left it as it was, means for LP aboot users it wasn't updated. And they thought MAGIC! Nope.
So today, I added a check for modem version which checks modem version prior to flashing of ROM in recovery. All it does is it checks the string in /firmware/verinfo/ver_info.txt with the latest one available I define here.
However there's no way it seems to check the "version" for aboot, as Xiaomi doesn't keep any such track of version in their releases for their bootloader. (Even "fastboot getvar all" for us, version-bootloader value is null)
So with aboot, just make sure you guys flashed the MM one ever and never modified it later. If not sure re-flash the MM aboot, if it re-locks, you had been using LP one, if it don't, you're already using MM one.
For locking case, it's hard to unlock while not on MIUI, so directly flashing miui is the better option instead of checking it that way.
To sum it up,
I am not going to revert the change of shipping fp firmware locally, as MIUI does the same AND YOU GUYS SHOULD BE USING COMPATIBLE FIRMWARE.
Guys who have tried clean flashing the May 3rd build and their modem version (Check /firmware/verinfo/ver_info.txt manually) matches with
"MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1" should go through the aboot check as it's only thing fp is dependent on, you can't verify that easily.
Also for those whose modem version is older than that, it is possible you might be using old aboot too, I suggest such people to flash MIUI MM for once and unlock it bootloader official way, so that you're on latest aboot.
Why? Won't be any issues with the ROM related firmware, also further updating fw via the fw zips I share won't re-lock the bootloader.
I am adding the non-modified firmware-update zip in OP for kenzo and kate from MIUI 7.5.4. Though you don't need to update it again on new Global dev release, firmwares aren't changed that often. We just need to be on FW shipped with MIUI marshmallow update.
Every RN3 custom ROMs user should know about this post for their own benefit. Help it spread. I'll add it in OP Post #2 as well.
hello, can anyone tell me where download from this rom? I messed with twrp and now I don't have the ROM in my internal memory. I need it to return it to live.. thanks in advance
There is an unofficial build with dec security patch https://mega.nz/#F!DPJ3AYqZ!w2_J2r4DyW4gJ-Vt4N-zVAhello, can anyone tell me where download from this rom? I messed with twrp and now I don't have the ROM in my internal memory. I need it to return it to live.. thanks in advance
Hey friends!! I am new to building ROMs.. But after hours and hours of hard work was able to build lineage OS from source.. I have successfully build latest PURE LINEAGE OS with NOVEMBER SECURITY PATCH.. I will be building this ROM for my personal use for as long as possible every month with latest security patch.. I will not modify anything in this ROM... If you are interested than I will form new thread of unofficial support of lineage OS with latest security patch..
why nobody maintaining this project? lg g2 re maintained. i think kenzo is better than lg g2 https://www.xda-developers.com/lineageos-16-lg-g2/
Install pixel experience 9.0No maintainer = no official rom
There's a dev who is still updating a lineage version just not officially : https://forum.xda-developers.com/redmi-note-3/development/rom-lineage-os-t3877377
it is lineage 14.1 (nougat)
after that 2 android version updated.
There's also : https://forum.xda-developers.com/redmi-note-3/development/rom-lineageos-16-0-t3844655 Again unofficial though. Not sure if it's even being developed anymore
I have Kate and FCP. Now working perfectly. No modifications.
1. Before dirty flashing I removed old fingerprints
2. dirty flashed May 3.rd release - > booted OK, but fingerprint scanner didn't work.
3. Flashed ResetScreenLockV2.zip - > booted OK, fingerprint scanner working also OK.
Firmware is quite old from January.
Official Lineage post said:Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.
- Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
- This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
- This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
- This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
- The process for this installation will be as follows:
- Install EXPERIMENTAL migration build on top of last CM/LineageOS build by me
- Install LineageOS weekly build
- Re-setup your application permissions