• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

DroidSK

Senior Member
May 13, 2014
106
23
Hi, i've flashed lineage-14.1-20180103 ROM and also a file aptX.zip from this thread and it started!
I've tried force apt-x on Nitrogen 8.1 and it didn't work... after that i've found that it's impossible to use aptx on Nitrogen and tried LineageOS 14.1 ... so now I enjoy better music quality.
Also I did not find a way to run an Apt-x on Oreo.
Guessing nitrogen 8.1 is oreo build. If yes there is different zip for oreo. I flashed it and had aptx work when i had the oreo pixel experience rom on my kenzo.

Sent from my Redmi Note 3 using Tapatalk
 

youssef0789

Senior Member
Mar 5, 2016
824
322
⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
 
Last edited:
  • Like
Reactions: Mohangrmc

mhackoy

Senior Member
Mar 12, 2014
208
23
look i know what i'm about to say will upset a lot of people and they will go oh no need for this and no need for that and i'll just keep doing it , so here is how i do it on every single ROM :

1 - download the ROM , G-apps , Custom Kernel [ if u use one ]
2 - put them on your sd card [ i put then on my usb stick and do it via OTG , do it the way you like , even if you want to put them on you internal storage ]
3 - turn off your phone
4 - boot into TWRP
5 - go to the wipe section
6 - select advanced wipe
7 - select [ Dalvik / ART Cache ] , then select [ Cache ] and then select [ System ] nothing else .
8 - then swipe to wipe
9 - go back to the main screen in TWRP
10 - go to the install section
11 - then flash the ROM , then the Kernel [ if u use one ] , then the G-apps
12 - then reboot

so you will ask me do i have to download and flash the G-apps every time i update the ROM ? , the answer is yes you have to cause if you use my way you will be wiping the system , so you have no G-apps on the phone , so you have to flash the G-apps every time , why i use this way ? cause it's the cleanest way to update , if u face any bugs you can report them but if you dirtyflash or use any other method , when u face bugs then you will have to clean flash the whole thing and then reproduce the bug and then report it , that's it .

Thank you so much.
 

youssef0789

Senior Member
Mar 5, 2016
824
322
⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
 
Last edited:

kongeo

Member
Aug 31, 2013
44
12
hi i installed the rom and it runs smooth! great work well done!

i want to know if there is a way to disable check when i enter pin to unlock..

like when i enter correct pin auto unlock and no need to hit check button
 

Zagash27

Member
Dec 6, 2013
36
2
Hi! I am leaving MIUI and searching for a ROM that suits my needs, but haven't made a decision yet. LOS seems to be perfect in terms of smoothness (at least from what I see on this thread), comes without root which is a huge plus for me (I play Mario and Pokemon GO), and is the successor of CM, which has always been my goto ROM across my previous devices.
The only thing that keeps me from installing this ROM is customization. I am very interested in changing at least the color of my interface to black, statusbar and such, but as far as I know this ROM doesn't have any sort of customization, and even substratum in legacy mode seems to cause bootloops and performance losses. What are my options if I want to customize this ROM? I really didn't want to go to the custom LOS builds as they might not be as polished or frequently updated as this one, and they come with root.
 

deptchcharge

Member
Dec 23, 2014
46
11
Hi! I am leaving MIUI and searching for a ROM that suits my needs, but haven't made a decision yet. LOS seems to be perfect in terms of smoothness (at least from what I see on this thread), comes without root which is a huge plus for me (I play Mario and Pokemon GO), and is the successor of CM, which has always been my goto ROM across my previous devices.
The only thing that keeps me from installing this ROM is customization. I am very interested in changing at least the color of my interface to black, statusbar and such, but as far as I know this ROM doesn't have any sort of customization, and even substratum in legacy mode seems to cause bootloops and performance losses. What are my options if I want to customize this ROM? I really didn't want to go to the custom LOS builds as they might not be as polished or frequently updated as this one, and they come with root.
If you're looking for such levels of customization, you can go for ViperOS. Supports substratum as well as the kind of customization you're looking for.

Sent from my Redmi Note 3 using Tapatalk
 

venki164

Senior Member
Apr 1, 2016
53
1
POCO M2 Pro
If it possible, explain it step-by-step to flash in locked bootloader of redmi note 3 Kenzo...

---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------

As far I know it doesn't have root after flash.
In extras section u can download zips to root and also unroot.
If it possible, explain it step-by-step to flash in locked bootloader of redmi note 3 Kenzo...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 483
    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.