Galaxy NOTE 10.1 N8000 CM14.1 (CyanogenMod 14.1, Nougat ROM)

GCam Port | Google Camera APK v9.2 (March 2024) Forums Samsung Device Forums Galaxy NOTE 10.1 – N8000/801X Galaxy NOTE 10.1 N8000 CM14.1 (CyanogenMod 14.1, Nougat ROM)

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #10030
    Linux User
    Participant

    Android Nougat 7.1 ROM for Galaxy NOTE 10.1 N8000/801X CM14.1 (CyanogenMod 14.1) has now arrived through an UNOFFICIAL build. For latest updates, stay tuned to the Lineage OS device list page. This Nougat 7.1 has come for Galaxy NOTE 10.1 N8000/801X via CyanogenMod 14.1 ROM. Since Google released Android Nougat Source code, we have update many Android NOUGAT AOSP ROMs and also many CyanogenMod 14.1 ROMs updated and many are yet to come. This Galaxy NOTE 10.1 N8000/801X for CyanogenMod 14.1 is brought to you by developer lirokoa.

    DISCLAIMER:
    THIS IS STILL AN EARLY BUILD AND CONTAINS BUGS. Installing custom ROM requires a custom recovery to be installed on your device, which may VOID your warranty and may delete all your data. Before proceeding further you may consider backup your all data. You are the only person doing changes to your phone and neither the developer(s) nor we can be held responsible for the mistakes done by you.

    Status of Galaxy NOTE 10.1 N8000/801X CM14.1 (CyanogenMod 14.1) Nougat 7.1 ROM:

    WHAT’S WORKING:
    – Almost everything except the below
    KNOWN ISSUES:
    – Keyboard does not work: enable hardware keyboard in settings
    – Camera is not working: use google camera

     

    GALAXY NOTE 10.1 N8000/801X CM14.1 (CYANOGENMOD 14.1) NOUGAT CUSTOM ROM

    REQUIRED LINKS AND FILES FOR GALAXY NOTE 10.1 N8000/801X CM14.1 (CYANOGENMOD 14.1, NOUGAT) CUSTOM ROM:

    HOW TO INSTALL/DOWNLOAD/FLASH/UPDATE GALAXY NOTE 10.1 N8000/801X CM14.1 (CYANOGENMOD 14.1) NOUGAT CUSTOM ROM:

    1. Follow this if you are flashing CyanogenMod 14.1 ROM for the first time to Galaxy NOTE 10.1 N8000/801X, or coming from another ROM:

      This will delete all your data on your phone. You may consider backing up your phone data or take a nandroid backup. Here is how to take NANDROID backup using TWRP recovery.

      Points to NOTE:
      – Try to avoid restoring apps backup using Titanium Backup. It may break things up.
      – Don’t restore system data using Titanium Backup! It will definitely break the current installation.
      – It is also discouraged to Restoring Apps + Data using Titanium Backup.

    2. Upgrading from earlier version of CyanogenMod 14.1 for Galaxy NOTE 10.1 N8000/801X:

      • Copy the latest Galaxy NOTE 10.1 N8000/801X CyanogenMod 14.1 ROM ZIP file to your phone.
      • Boot into Recovery.
      • Flash the latest CM ROM ZIP from your phone.
        – Here is a post explaining how to flash a custom ROM using TWRP recovery.
        – Use the same guide to flash the GApps too.
      • Reboot and Enjoy

    Complete the initial setup and enjoy Android Nougat 7.1 with CyanogenMod 14.1 for NOTE 10.1 N8000/801X. After this CM14.1 installation you may want to enable ROOT access on your phone and here is how you can do that:
    How to Enable ROOT on CM14.1/CyanogenMod 14.1.

    Stay tuned or Subscribe to the Galaxy NOTE 10.1 N8000/801X forum For other Android Nougat ROMs, CyanogenMod 14 ROMs, other ROMs and all other device specific topics.

     

    The development thread is here for this ROM.

    #11727
    Linux User
    Participant

    Today I tried to update, but a message appears informing “signature error” for the compressed file.

    #11815
    Linux User
    Participant

    Unfortunately it does not really work. This file signature error prevents ROM installation.

    After making all the wipe, the installation begins, but terminates when the signature failure appears, and the N8000 reboots with the current ROM that is already installed on it.

    #63149
    Linux User
    Participant

    I installed CM14 on my Glaxy Note 10.1, N8000. Everything worked perfectly. But the Note stopped. The battery has stopped charging. Has anyone else had this problem? Was it coincidence or some incompatibility between software and hardware?

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.