[ROM][OFFICIAL][7.1.2][kate/kenzo] LineageOS 14.1
- Thread starter TheStrix
- Start date
Same. The latest zip file before they pulled it off their website for our device.
I tried on havoc 2.4 also but its not working . for WhatsApp its not showing install option in playstore.
What I did :
Officially unlocked bootloader
Twrp
Flash Rom and gapps.
Been doing it since 2017 and faced no such problem.
Have flashed Lineage 14.1, (updated Twrp to latest version) Pixel experience oreo, Resurrection remix oreo and now on Havoc.
I think probably have a problem with Firmware.
Anyone have mirror link of ofiicial lineage os ?? Noughat , not its removed from lineage os site
---------- Post added at 02:01 PM ---------- Previous post was at 01:51 PM ----------
This will be very thankful
---------- Post added at 02:01 PM ---------- Previous post was at 01:51 PM ----------
Sir may u upload official 14.1 zip to gdrive,
This will be very thankful
G
GuestD0695
Guest
Why would you use an outdated official Lineage 14.1?
The security updates would be very old.
I'm currently in the process of building LineageOS 14.1 for MicroG, once I automate it there will be weekly/bi-weekly builds.
It's built from official source code, except it has MicroG and F-Droid preinstalled.
Link: http://lineage.erazem.eu/builds/full/
It will soon support OTA updates as well.
Warning: I haven't tested it yet (just built it), so there may be problems, although there shouldn't be since it's built from official sources. I will create a separate thread for it soon.
Last edited:
Does your build include kernel level patches? If not, ASB string is nothing but a date.
G
GuestD0695
Guest
It's built using LineageOS4Microg's doocker image, which should pull the latest source code from official LineageOS sources. If I understand correctly, those should already have the latest patches.
Besides that no, I haven't modified the code in any way.
Besides that no, I haven't modified the code in any way.
Then it's two years or so since kernel was last patched, which doesn't sound so secure
G
GuestD0695
Guest
Doesn't lineage backport patches?Then it's two years or so since kernel was last patched, which doesn't sound so secure
Here's their changelog for 14.1: https://review.lineageos.org/q/branch:cm-14.1+status:merged
They do backport patches on a system level, kernel patches must be ported manually by maintainer. See the official kernel source used by Kenzo, last commit is dated November 24th 2017, which is highly outdated and therefore insecure.
There's a few up to date custom kernels though the support nougat that you can flash if you want. A device with unlocked BL is not secure anyway but better safe than sorry I guess.
G
GuestD0695
Guest
For those who find the rom's been deleted.
https://archive.org/details/lineage-14.1-20181109-nightly-kenzo-signed
Just give me a thanks. ?
https://archive.org/details/lineage-14.1-20181109-nightly-kenzo-signed
Just give me a thanks. ?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
484
The package supports both Xiaomi Redmi Note 3 (kenzo) & Xiaomi Redmi Note 3 SE (kate).
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
- Boots
- RIL (Calls, SMS, Data)
- VoLTE
- Fingerprint
- Wi-Fi
- Bluetooth
- Camera
- Camcorder
- Video Playback
- Audio
- Sensors
- Flash
- LED
- GPS
Known issues:
- You say!
Instructions :
- Download the latest build and GApps
- Reboot to recovery
- Flash the latest build and GApps
- Reboot
Downloads :
First read this before proceeding!
- Official weekly builds: https://download.lineageos.org/kenzo
- LineageOS addons download: https://download.lineageos.org/extras
- Unofficial maintainer builds: https://goo.gl/B7kzfu
- Google Apps: http://opengapps.org/
Credits :
- @banmeifyouwant: For his kernel patches
- @luca020400: "Me: HAALP!" He answered me
- CyanogenMod/LineageOS Team
- Xiaomi: For providing the Kernel Source Code
Donations:
You don't have to but if you want;
Donate via PayPal: http://paypal.me/ParthBhatia/
Donate via PayTM: http://i.imgur.com/54cQl9N.jpg (QR code)
XDA:DevDB Information
LineageOS 14 for kenzo, ROM for the Xiaomi Redmi Note 3
Contributors
TheStrix
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2017-01-21
Last Updated 2017-05-08185TeamWin Recovery Project (TWRP):
Download & support: https://xdaforums.com/redmi-note-3/development/recovery-twrp-xiaomi-redmi-note-3-t3567103
Compatible firmware:
- kenzo: https://www.androidfilehost.com/?fid=817550096634784493 (from MIUI Global DEV v7.7.6)
- kate: https://www.androidfilehost.com/?fid=673368273298953184 (from MIUI Global DEV v7.5.4)
Source Code:
Device Tree(s):
Kernel Tree:
- android_kernel_xiaomi_msm8956: Github | Gerrit
Note: It is a unified kernel for both Mi Max and Redmi Note 3.
Vendor:
137Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- 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.)
- If it is a random reboot, grab /sys/fs/pstore/console-ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Frequently Asked Questions:
Q) ROM zip failed to flash with "assert failed" or "ERROR: 7"?
A) Update your firmware. Read this for more.
Q) Is VoLTE supported?
A) Yes
Q) Support for Vulkan API?
A) Yes
Q) Is Goodix FP supported?
A) Yes
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Yes.
Q) How do I update GApps? (Also useful if you have GApps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + GApps. (Yes, without rebooting). Reboot.
Q) Facing Settings -> Security force close?
A) Update your firmware.
Q) No audio in voice calls?
A) Update your firmware.83
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
& modem=NON-HLOS
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.72Official builds
So, OFFICIAL builds are compiled and are available to download on lineage links!
I suggest everyone to read the following linked post before you proceed with official build installation so that you know what you're doing!
This post is regarding everyone should know the stuffs mentioned here: http://lineageos.org/Update-and-Build-Prep/
Official Lineage post said:
Other stuffs to remember:
- Official builds will NOT be shipping root baked into the ROM. Root will be a downloadable zip based install similar to gapps installation (only need to flash it once). [Addon isn't ready as of now, it'll be available in future, I'll let you guys know about it when that happens]
- VoLTE indicator icon is my addition, it's not present on official ROM source (May be added in future, but it isn't present as of now. VoLTE works, but no VoLTE icon is shown, do not want posts regarding that in future so making it clear)
OP updated with links.