[ROM][OFFICIAL][7.1.2][kate/kenzo] LineageOS 14.1

Search This thread

r0msk1

Member
Oct 6, 2013
13
0
I am downloading this right now. After searching on internet about this build, I found that some users are reporting automatic shutdown problem below 30% and 10%.

After I installed this ROM few years back, I haven't returned to this thread.
I thought it was just me facing that issue. I thought it was battery calibration error. Have you found solution to this?
 

jonny789

Senior Member
Oct 18, 2012
231
17
After I installed this ROM few years back, I haven't returned to this thread.
I thought it was just me facing that issue. I thought it was battery calibration error. Have you found solution to this?

I tried this rom few months ago & it provided good battery backup. I did not find any shutdown problem. Right now I am running crdroid pie rom.
 

r0msk1

Member
Oct 6, 2013
13
0
I tried this rom few months ago & it provided good battery backup. I did not find any shutdown problem. Right now I am running crdroid pie rom.

It might have been solved in the following updates, but I never updated past 20171206. (Oh I just realized it is almost 2 years of no update, as I just checked it now. haha)

How is it then?
 

awalis

Member
Jun 30, 2019
20
4
It might have been solved in the following updates, but I never updated past 20171206. (Oh I just realized it is almost 2 years of no update, as I just checked it now. haha)

How is it then?

In my experience, this problem stopped as soon as I replaced the battery. No more shutdowns around 30%.
So the issue may be related to old batteries that need to be replaced anyway. This extends the life of your phone, without having to spend a fortune.
 

ullas377

Senior Member
Jan 3, 2017
54
4
Hey..
Developers
Please re continue for devlopment lineage 17.1..
Because it is a most famous custom rom...
 

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
6,115
14,290
31
Ambala
OnePlus 9R
THREAD CLEANED

Requesting everyone to stay on-topic. Whether a device is old or not has nothing to with this development thread, and is off-topic. Also, any sort of abuse, or profanity will not be tolerated and will be dealt with severely.

Just hit the report button and move on if you find someone who is not abiding by the forum rules, instead of engaging with them, which only creates drama, and nothing else.

Regards,
shadowstep
Forum Moderator
 

awalis

Member
Jun 30, 2019
20
4
can someone share me a download link for lineage os 14.1 official build for redmi note 3 pro

here you are:

https://archive.org/details/lineage-14.1-20181109-nightly-kenzo-signed

---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------

Why this CustomROM, unlike other ROMs, is still stuck on Android 7 ?!

there's no official maintainer for this device, in LineageOS.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 484
    QQa2TSa.png

    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! :D

    Instructions :
    • Download the latest build and GApps
    • Reboot to recovery
    • Flash the latest build and GApps
    • Reboot

    Downloads :
    First read this before proceeding!

    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-08
    185
    TeamWin Recovery Project (TWRP):

    Download & support: https://forum.xda-developers.com/redmi-note-3/development/recovery-twrp-xiaomi-redmi-note-3-t3567103

    Compatible firmware:

    Source Code:

    Device Tree(s):

    Kernel Tree:

    Vendor:
    • proprietary_vendor_xiaomi: Github (For WIP: this)
    137
    Reporting 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
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

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

    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.
    72
    Official 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:
    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:
      1. Install EXPERIMENTAL migration build on top of last CM/LineageOS build by me
      2. Reboot
      3. Install LineageOS weekly build
      4. Reboot
      5. Re-setup your application permissions

    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.