Skip to main content

Installing a custom ROM on Android (on the GT-N8013)

It's been a while since my last entry and since it is a new start in 2019, I thought I'd write something about "gone with the old and in with the new".

I've had my Samsung Galaxy Note 10.1 (pnotewifi) since 2014, and it's one of the early Galaxy Note tablet series. It has served me well all this years but now it just sits there collecting dust.
My old Samsung GT-N8013
My old Samsung GT-N8013

I've known a long time about custom Android ROMs like CyanogenMod but has never had the motivation to try them out, until now !

Overview of the process

For beginners like me, I didn't have an understanding of the installation process and so it looked complicated and it was one of the reasons I was put off in trying the custom ROM. I just want to say, it's not complicated at all! 

Basically you will need to
  1. Prepare an SD card and install Android SDK (you need adb).
  2. Install a custom boot loader (TWRP is the de facto tool at the moment).
  3. Use adb to copy custom ROM images onto the device's SD card.
  4. Use TWRP to install the images from SD card.
The process above applies to any Android device, but you will need to download the appropriate custom ROM images specific to your device.
Lineage OS offers the most variety for many devices and its official page is the first page to check out. But if you have a very old device like me, chances are even Lineage does not support it anymore. If so, then head to XDA developers forum where you can find unofficial ROMs.

The images I used successfully on my N8013 can be downloaded here.

Step by step installation

Prepare SD Card and install Android SDK.

Saving the images to SD Card and installing them with TWRP will save you a lot of time. Android SDK installation can be found in many tutorials such as this one.

Installing TWRP on the device

Since I was installing on a Samsung device from a Windows PC, Odin was the easiest method for me to install TWRP on my Galaxy note. Installation with Odin has been covered in many tutorials and this is one of the best I found.

Note : Depending on your device, you can also install TWRP from the TWRP app or using fastboot.

On the device, go to Download Mode. On the Samsung Galaxy Note, press and hold the Power Button and the Volume Down button at the same time.
Download Mode on the N8013

After device is in Download Mode, connect USB cable to PC. Then use Odin per installation instructions above to install TWRP.

After TWRP installation is complete, reboot the device into the TWRP screen. For GT-N8013 this is done by pressing and holding the power button and volume up button at the same time.

TWRP screen

Use adb to copy ROM images to the device

Use the following command to push the ROM files.
adb push {file} {path to folder on device}
If you have an SD card on the device it probably is listed as /sdcard01 or something similar. The TWRP screen has a UI to browse storage folders. Go to Install and confirm the folder name on the menu panel.

Install the images

Once the image files are copied to the device, from the TWRP home screen, choose Install and browse to the folder where the image files are. Then just follow the on-screen instructions to install.
You can also specify the Google Apps package to install together with the custom OS. This package is necessary if you want to have Google Apps on your device.

Installation started

Installation complete

Once installation is complete you will see an option to Reboot System and to Reset Cache/Dalvik. For the N8013, if you come from the latest manufacturer build from Samsung (Android 4.1.2) do not reset cache/dalvik. Simply reboot system and boot into your new OS>

Boot into the new OS

Once the OS and Google Apps (GApps) package are installed and you rebooted your device, it will show the OS logo and boot into the desktop.

Tips and Hints

Hopefully you only needed the above steps to install your new OS but if something goes wrong here are some tips to try out.

  1. You are probably using an image not meant for your device. Search for the exact device and variant number that matches your device.
  2. Prepare the device's original manufacturer image. For the N8013 pnotewifi, this image is also included in the download link I gave earlier.
  3. Flash the original image and then try to flash the custom image again.
  4. Try flashing with and without clearing Dalvik/Cache. If you are coming from an original manufacturer's image, you probably do not clear Dalvik/Cache after flashing the new custom image. Most tutorials ask you to clear Dalvik/Cache but in my case it worked when I did not clear Dalvik/Cache after flashing the custom image.
  5. If Google Apps package fail to install try the other varieties such as pico, nano etc.

Afterword

If this works please spread the word so more people can revive their old devices. I personally think custom roms help the environment by extending the life of devices. Any problems please leave comments below.

Comments

  1. ChionaDecember 30, 2019 at 1:59 PM

    So does this leave the Android version 4.1.2 intact?
    Have you attempted to get Android 5 or later installed (some of the apps I use require 5 or later...)

    ReplyDelete
    Replies
    1. Sonny KurniawanMay 1, 2020 at 9:56 AM

      Hi, sorry for the late reply. No, the Android version 4.1.2 will be overwritten. Actually the Cyanogen build that I installed was based on Android 6.0. So yeah I got it working with the steps mentioned here

      Delete
  2. AdriApril 3, 2020 at 8:27 PM

    What do you mean use adb? Where do I type in the push command?

    ReplyDelete
    Replies
    1. Brian CoeApril 6, 2020 at 10:33 AM

      https://www.androidexplained.com/install-adb-fastboot/

      Delete
    2. Sonny KurniawanMay 1, 2020 at 9:57 AM

      Adri, as per the link Brian shared, please install ADB as part of the Android SDK, then you can run the command mentioned in the article.

      Delete
  3. HymellMay 28, 2020 at 12:11 PM

    Hi! Could you say if the S-Pen still working after the installation?

    ReplyDelete
    Replies
    1. Sonny KurniawanMay 29, 2020 at 8:21 AM

      No, the S-Pen requires Samsung proprietary software so it's not included in the Cyanogen Builds. As far as I know there is no way to get the S-Pen to work without Samsung's help

      Delete
    2. UnknownJune 15, 2020 at 2:43 PM

      FYI - I am running Lineage 14.1 on my GT-N8013 and the pen works.

      Delete
  4. HymellMay 29, 2020 at 1:19 PM

    This comment has been removed by the author.

    ReplyDelete
  5. CalebJune 6, 2020 at 12:48 AM

    This comment has been removed by the author.

    ReplyDelete
    Replies
    1. CalebJune 6, 2020 at 1:04 AM

      This comment has been removed by the author.

      Delete
  6. worm manAugust 29, 2020 at 10:01 AM

    Gt- N8010 compatible on this rom

    ReplyDelete
  7. KeithOctober 16, 2020 at 10:20 AM

    Thanks for posting this. I just picked up a mint Note 10.1 2012 with a case, stylus and charger for $20 usd today! SCORE! How does your tablet perform with the new rom. And what apps have you found that the s pen DOES still work in? Can the stylus still be used at all or no? Thanks again.

    ReplyDelete
  8. UnknownNovember 16, 2020 at 9:18 AM

    Thank you for the explanation and especially for uploading the files. Is everything working properly after the update except the S-Pen especially the GPS and the WiFi? What version of android is the custom rom and can you update the common apps like gmail and maps via the google play store? Thank You!

    ReplyDelete
  9. Unow22September 14, 2021 at 10:19 AM

    You’re likely to find the taste metallic, bitter, and saltyThis detox program works for all kinds of toxins, including THCcom/wp-content/uploads/2021/06/Screen-Shot-2021-06-01-at-1laweekly An occasional user will have a lot less to detect than a heavy user Take a deep breath and try not to think about it Visit: https://www.urineworld.com/

    ReplyDelete

Post a Comment

Popular posts from this blog

Using FCM with the new HTTP v1 API and NodeJS

When trying to send FCM notifications I found out that Google has changed their API specifications. The legacy API still works but if you want to use the latest v1 API you need to make several changes. The list of changes is listed on their site so I won't be repeating them again but I'll just mention some of the things that caused some trial and error on my project. The official guide from Google is here : Official Migration Guide to v1 . The request must have a Body with the JSON containing the message data. Most importantly it needs to have "message" field which must contain the target of the notification. Usually this is a Topic, or Device IDs. Since my previous project was using GAS, my request had a field called "payload" instead of "body". Using the request from my previous project, my request in Node JS was as follows: request ({ url: 'https://fcm.googleapis.com/v1/projects/safe-door-278108/messages:send' , method: ...
Post a Comment
Read more

Building a native plugin for Intel Realsense D415 for Unity

Based on a previous post , I decided to write a plugin for the Intel Realsense SDK methods so we can use these methods from within Unity. FYI Intel also has their own Unity wrapper in their Github repository , but for our projects, I needed to perform image processing with OpenCV and passing the results to Unity instead of just the raw image/depth data. There is a plugin called OpenCVForUnity to use OpenCV functions from Unity but previous experiments indicate the image processing inside Unity can take a long time. I hope this post can help someone else who wants to use Intel's cameras or any other devices natively in Unity. Test Environment Windows 10 64bit Unity 2017.2.0f3 x64 bit Realsense SDK from Intel CMake 3.0 or higher Steps Checkout the native plugin code here . Don't worry about the other projects in the same repository. The relevant code is in the link above. Checkout the Unity sample project here . However, instead of master you need to go to the br...
5 comments
Read more

Microsoft Azure Face API and Unity

During one of my projects, I came across Microsoft's face recognition API (Azure Face API) and it looked good enough to recognize people's faces and detect if a person is a newcomer or a repeating customer to our store. As our installations mainly use the game engine Unity, I wanted to be able to use the Face API from Unity. Face API does not have an SDK for Unity but their requests are just HTTP requests so the Networking classes in Unity can be wrapped into methods to make it easy to call these APIs. First of all, to those who just want to see the code, here it is . My tests focus on the identification of a face in an input image. The full tutorial I followed can be found here . The Main scene goes through the steps in the tutorial such as creating a PersonGroup and adding Persons to the group if it is not created yet. Just make sure you: Change the API key. I used a free trial key which is no longer valid. Use whatever images you want. I don't mind you us...
Post a Comment
Read more