Galaxy Tab 2 7.0 Cyanogenmod

Cyanogenmod ROM Samsung Milky way Tab 2 seven.0 (Wi-Fi) (p3110)

Quick Info

Notes

Alarm: Device specific builds are discontinued!

Delight use "espressowifi" builds in futurity.

Note:

IR blaster is supported for the P3113, delight utilise the P3110 CM builds for flashing.

Special boot modes

• Recovery: Hold Vol Up & Ability.
• Download: Hold Volume Down.

Source code

Milky way Tab two 7.0 (Wi-Fi) Specifications

Codename:	p3110
Too known as:	p3110 (WiFi version)
Vendor:	Samsung
Manufacturer:	samsung
Blazon:	tablet
Platform:	TI OMAP4430
CPU:	ane GHz dual-core OMAP4
GPU:	PowerVR SGX540
RAM:	1GB
Weight:	344 grand (12.1 oz)
Dimensions:	194 mm (7.6 in) (h) 122 mm (4.8 in) (due west) 10.5 mm (0.41 in) (d)
Screen size:	178 mm (seven.0 in)
Resolution:	1024×600
Screen density:	169 PPI
Internal storage:	eight/16/32GB
SD Card:	up to 32GB
Bluetooth:	3.0
Wi-Fi:	802.11 b/g/northward
Main camera:	3.1MP
Secondary camera:	ane.3MP
Power:	4000 mAh (Non-removable)
Peripherals:	capacitive touchscreen, proximity & light sensors, 3-axis accelerometer, additional 3-centrality gyroscope, digital compass
CM supported:	ix, 10, 10.one, eleven

How to Install CyanogenMod on the Samsung Milky way Tab ii 7.0 (Wi-Fi) (p3110)

Note: DISCLAIMER

Modifying or replacing your device's software may void your device's warranty, lead to data loss, pilus loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your ain risk. No ane affiliated with the CyanogenMod project is responsible for your actions. Good luck.

Important Notes

Warning: Device specific builds are discontinued!

Please use "espressowifi" builds in future.

Notation:

IR blaster is supported for the P3113, please use the P3110 CM builds for flashing.

Installing a custom recovery

Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this kicking style. Rooting the stock firmware is neither recommended nor necessary.

1. Download and install the Heimdall Suite
   • Windows: Extract the Heimdall suite and take note of the directory holding heimdall.exe. You can verify Heimdall is working by opening a command prompt in this directory and typing heimdall version. If you receive an error, be sure that you lot take the Microsoft Visual C++ 2012 Redistributable Package (x86/32bit) installed on your figurer.
   • Linux: Pick the appropriate installation bundle based on your distribution. The -frontend packages are not required for this guide. Later on installation, heimdall should be available from the concluding; type heimdall version to verify installation succeeded.
   • Mac: Install the dmg bundle. After installation, heimdall should exist available from the terminal; blazon heimdall version to verify installation succeeded.
   • Edifice from source: The source code for the Heimdall Suite is bachelor on Github. For more than details nigh how to compile the Heimdall Suite, delight refer to the README file on Github under the relevant operating organisation directory. Yous can too refer to the Install and compile Heimdall instructions on this wiki.
2. Download recovery — you can directly download a recovery image using the link below, or visit TWRP site to check for the latest version of recovery for your device (if your device tin exist plant at that place). For general info near recoveries click hither.

   Recovery: Download

   md5: 94b2fc231bee140733a8c11e80330330

3. Power off the Galaxy Tab 2 seven.0 (Wi-Fi) and connect the USB adapter to the reckoner merely not to the Milky way Tab 2 vii.0 (Wi-Fi), nonetheless.
4. Kicking the Galaxy Tab ii 7.0 (Wi-Fi) into download mode. Hold Volume Down. Take the disclaimer on the device. Then, insert the USB cablevision into the device.
5. Windows (but) commuter installation – Skip this pace if you are using Linux or Mac

   A more than complete set of the following instructions can be establish in the Zadig User Guide.

   1. Run zadig.exe from the Drivers folder of the Heimdall Suite.
   2. Choose Options » List All Devices from the menu.
   3. Select Samsung USB Composite Device or MSM8x60 or Gadget Series or Device Name from the driblet down carte. (If nothing relevant appears, try uninstalling whatever Samsung related Windows software, similar Samsung Windows drivers and/or Kies).
   4. Click Replace Commuter (having selecting "Install Driver" from the drop down list built into the button).
   5. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this commuter anyway. You lot may receive 2 more prompts about security. Select the options that allow yous to carry on.
6. At this signal, familiarize yourself with the Flashing with heimdall notes beneath so that you are prepared for any foreign behaviour if it occurs.
7. On the calculator, open a concluding (or Control Prompt on Windows) in the directory where the recovery image is located and type:

   heimdall flash --RECOVERY recovery.img --no-reboot

   Tip: The file may not be named identically to what'due south in this command. If the file is wrapped in a zip or tar file, extract the file first, because heimdall isn't going to practice information technology for you.

8. A blue transfer bar volition announced on the device showing the recovery being transferred.
9. Unplug the USB cablevision from your device.
   • Notation: Be certain to reboot into recovery immediately later on having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing every bit though your custom recovery failed to install).
10. Manually reboot the telephone into recovery mode by performing the post-obit. Hold Vol Up & Power.
11. The Galaxy Tab ii 7.0 (Wi-Fi) now has a custom recovery installed. Go on to the next section.

Note: Flashing with heimdall

• In Windows 7 UAC (User Account Control) may need switching off. Once Heimdall is finished it can be re-enabled.
• Protocol initialization tin can fail if the device is continued via a USB hub – connect the USB cable directly to the PC
• It may be necessary to run the heimdall flash control as root in Linux or Mac OS X: sudo heimdall flash [...]. Typical symptoms of this are:
  • a blueish bar doesn't evidence upwards later the process has finished
  • Failed to confirm end of file transfer sequence!
• It may be necessary to capitalize the name of the partition on some devices. Try --KERNEL instead of --kernel and/or --recovery instead of --RECOVERY.
• If on Linux 64bit you get "unable to execute ./heimdall: No such file or directory", try the 32bit version and make sure to run it with sudo: reference.
• On Mac Os 10 yous may see this bulletin: "Error: Claiming interface failed!". If so, you demand to disable the default USB drivers with the following commands:
  sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple tree.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.commuter.AppleUSBCDCACMData;
  If you have installed Samsung Kies, you may further need to unload those USB drivers with the following commands:
  sudo kextunload -b com.devguru.driver.SamsungComposite;
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
• Using Heimdall version one.four.0 (the latest version available for download on the Glass Echidna website) you may run across this message or ane similar to it:
  Mistake: Failed to confirm cease of PIT file transfer!
  If you experience this mistake, follow the instructions for compiling Heimdall from source to get the latest version on GitHub with the outcome patched.

Helpful Tip

• The stock ROM may overwrite your custom recovery on boot. To forbid this, kicking immediately into recovery after leaving Download Fashion instead of letting the ROM boot upwardly normally. If your recovery is overwritten, simply redo the steps you followed above and catch it before it boots next time.
• Note for upgrades from gingerbread to jellybean think the recovery is inverse. This means once you install practise NOT restore to sometime-gingerbread-stock ROM from cwm-recovery.
• To upgrade from stock/CM7/CM9/CM10.i.2/CM10.1.3 to CM10.2, yous must first boot into recovery and wipe data, enshroud, and dalvik cache (factory reset). Due to the new partition layout in CM10.2, failing to perform these steps will event in a bootloop. See here for details; more about repartitioning here. If you missed this step before installing, boot to recovery and factory reset, then reinstall CM10.2.
• Some users have reported connection errors if the device is connected to a USB hub. If you experience such errors it is recommended that you try connecting your device to a USB port on the motherboard.
• Antivirus software may prevent Heimdall from connecting properly. Disable your antivirus before proceeding.
• When Heimdall fails to connect, the Download mode may get stuck, making all farther attempts fail too. To retry, you may need to restart the Download fashion: turn off the phone past holding Ability for 5-10 seconds (or by pulling out the bombardment), and so kicking into Download fashion and run Heimdall again.
• If Heimdall fails to connect (errors related to initializing the protocol, or transferring data):

  if you lot merely installed the driver, try rebooting your computer and trying again.

  if you nonetheless have troubles after reboot, in Zadig endeavor installing the libusbK driver rather than the WinUSB driver.

Installing CyanogenMod from recovery

1. Make certain your figurer has working adb.
2. Download the CyanogenMod build parcel for your device that you'd similar to install to your figurer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Place the CyanogenMod .zip package, every bit well as any optional .aught packages, on the root of /sdcard:
   • Using adb: adb push filename.aught /sdcard/

   Annotation: You can re-create the .zip packages to your device using whatever method yous are familiar with. The adb method is used here because information technology is universal across all devices and works in both Android and recovery mode. If you are in recovery manner, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its condition in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you lot are non already in recovery, kick to recovery style at present.
   • Hold Vol Upwardly & Power.
5. In Team Win Recovery Projection, select bill of fare choices past borer on the appropriately labelled button.
6. Optional (Recommended): Select the Backup push button to create a backup.
7. Select Wipe and and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you lot wish using the same method (if yous are installing multiple packages, install CyanogenMod offset and then install whatever subsequent packages on top of information technology).
12. Once installation has finished, return to the chief bill of fare and select Reboot, then Arrangement. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Samsung Galaxy Tab 2 7.0 (Wi-Fi) (p3110)

Contents

• i Introduction
  • 1.one What you'll need
• 2 Build CyanogenMod and CyanogenMod Recovery
  • ii.1 Fix the Build Surroundings
    • ii.1.1 Install the SDK
    • ii.one.2 Install the Build Packages
  • ii.2 Create the directories
  • two.3 Install the repo command
  • 2.4 Put the ~/bin directory in your path of execution
  • 2.5 Initialize the CyanogenMod source repository
  • 2.six Download the source lawmaking
  • 2.seven Get prebuilt apps (CM11 and beneath)
  • two.8 Ready the device-specific code
  • ii.9 Excerpt proprietary blobs
  • 2.10 Turn on caching to speed up build
  • 2.eleven Get-go the build
  • 2.12 If the build breaks…
• 3 Install the build
  • 3.1 Install CyanogenMod
  • 3.2 Success! So….what's adjacent?

Introduction

These instructions will hopefully assist you to start with a stock Galaxy Tab ii vii.0 (Wi-Fi), unlock the bootloader (if necessary), and then download the required tools also every bit the very latest source code for CyanogenMod (based on Google's Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery prototype from source lawmaking, and then install them both to your device.

Information technology is difficult to say how much feel is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn't crave a PhD in software evolution either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most bones operation. Considering people's experiences, backgrounds, and intuitions differ, it may be a expert thought to read through just to ascertain whether y'all experience comfy or are getting over your head.

Remember, yous presume all risk of trying this, but you lot will reap the rewards! Information technology's pretty satisfying to boot into a fresh operating system yous baked at home :) And one time you're an Android-building ninja, there will exist no more than demand to wait for "nightly" builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where yous become from there– perhaps you'll add a feature, set up a bug, add a translation, or use what yous've learned to build a new app or port to a new device– or maybe you'll never build over again– it'southward all actually upwardly to y'all.

What you'll need

• A Galaxy Tab ii seven.0 (Wi-Fi)
• A relatively recent estimator (Linux, Os X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you take, the longer the build will take (aim for eight GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cablevision compatible with the Galaxy Tab 2 7.0 (Wi-Fi) (typically micro USB, but older devices may use mini USB or have a proprietary cablevision)
• A decent net connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you've installed custom roms on other devices and are familiar with recovery. Information technology may too be useful to know some basic command line concepts such as cd for "change directory", the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an splendid take chances to learn. Information technology's free– just download and run a virtual machine (VM) such as Virtualbox, and so install a Linux distribution such every bit Ubuntu (AOSP vets Ubuntu too). Any contempo 64-scrap version should work groovy, only the latest is recommended.

Note:

You want to use a 64-bit version of Linux. A 32-bit Linux environment will only work if you are building CyanogenMod 6 and older. For CyanogenMod 10.i, if yous encounter problems with 64bit host binaries, y'all tin set BUILD_HOST_32bit=1 in your environment. This is generally non needed, though, particularly with CyanogenMod 10.two and newer.

Using a VM allows Linux to run as a invitee inside your host computer– a computer in a computer, if you will. If y'all hate Linux for whatever reason, you lot can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, and then I'll leave it to you to do that.)

So let'south begin!

Build CyanogenMod and CyanogenMod Recovery

Fix the Build Environment

Notation:

Yous only need to do these steps the first fourth dimension y'all build. If you previously prepared your build environment and accept downloaded the CyanogenMod source code for some other device, skip to Ready the device-specific code.

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. "SDK" stands for Software Developer Kit, and it includes useful tools that you tin can use to wink software, look at the system logs in real time, grab screenshots, and more– all from your figurer.

Helpful Tip

While the SDK contains lots of different things– the ii tools you are near interested in for building Android are adb and fastboot, located in the /platform-tools directory.

Install the Build Packages

Several "build packages" are needed to build CyanogenMod. You can install these using the package manager of your option.

Helpful Tip

A bundle director in Linux is a system used to install or remove software (usually originating from the Internet) on your figurer. With Ubuntu, you can apply the Ubuntu Software Heart. Even meliorate, you may also use the apt-get install command directly in the Terminal. (Learn more about the apt packaging tool system from Wikipedia.)

For both 32-bit & 64-flake systems, yous'll need:

          bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc goose egg zlib1g-dev        

In addition to the above, for 64-chip systems, get these:

          g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev        

For Ubuntu xv.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally come across java notes beneath):

• libwxgtk2.viii-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Coffee Development Kit):

• CyanogenMod 7 – nine: Sunday/Oracle Java SE 1.half-dozen
• CyanogenMod 10.1: Lord's day/Oracle Java SE 1.half-dozen or 1.7
• CyanogenMod x.two – 11.0: Sun/Oracle Java SE 1.half dozen or i.7 (OpenJDK 1.7 works fine, but the build system will display a alert)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (meet note about OpenJDK 1.8 beneath)
• CyanogenMod 14.1: OpenJDK ane.8

Ubuntu xvi.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK ane.vii was removed from the official Ubuntu repositories, yous have a couple options:

1. Obtain OpenJDK 1.vii from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 back up in CyanogenMod thirteen.0 (non available in earlier version). To enable OpenJDK 1.8 back up, add together this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=truthful.

Besides see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to prepare up some directories in your build surround.

To create them:

          $ mkdir -p ~/bin $ mkdir -p ~/android/system        

Install the repo command

Enter the following to download the "repo" binary and make information technology executable (runnable):

          $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+10 ~/bin/repo        

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following lawmaking exists (add it if it is missing):

          # prepare PATH and so it includes user'southward individual bin if information technology exists if [ -d "$Domicile/bin" ] ; then     PATH="$Domicile/bin:$PATH" fi        

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Notation: Make certain the cm branch entered here is the one you wish to build and is supported on your device.

          $ cd ~/android/organization/ $ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0        

Download the source code

To start the download of all the source lawmaking to your reckoner:

          $ repo sync        

The CM manifests include a sensible default configuration for repo, which we strongly suggest yous use (i.eastward. don't add any options to sync). For reference, our default values are -j iv and -c. The -j four office means that in that location will exist iv simultaneous threads/connections. If y'all experience problems syncing, you lot tin lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the unabridged CM history.

Prepare to wait a long time while the source code downloads.

Helpful Tip

The repo sync control is used to update the latest source code from CyanogenMod and Google. Call up it, as you can do it every few days to go on your code base of operations fresh and up-to-date.

Get prebuilt apps (CM11 and below)

Next,

          $ cd ~/android/organisation/vendor/cm        

then enter:

          $ ./go-prebuilts        

You won't see whatsoever confirmation- just another prompt. But this should crusade some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done once more.

Set up the device-specific code

Helpful Tip – Errors during breakfast

Unlike maintainers setup their device inheritance rules differently. Some require a vendor directory to be populated before breakfast will even succeed. If y'all receive an fault here nigh vendor makefiles, and then leap down to the adjacent department Excerpt proprietary blobs. The kickoff portion of breakfast should have succeeded at pulling in the device tree and the extract blobs script should exist bachelor. After completing that section, you tin rerun breakfast p3110

After the source downloads, ensure yous are in the root of the source code (cd ~/android/system), then blazon:

          $ source build/envsetup.sh $ breakfast p3110        

This will download the device specific configuration and kernel source for your device. An culling to using the breakfast command is to build your ain local manifest. To do this, you will need to locate your device on CyanogenMod's GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Helpful Tip

If you want to know more about what source build/envsetup.sh does or but want to know more most the breakfast, brunch and dejeuner commands, you tin can head over to the Envsetup help page.

Helpful Tip

Instead of typing cd ~/android/organization every time you want to return dorsum to the root of the source lawmaking, here's a brusk control that volition practice it for you lot: croot. To use this command, you must first run source build/envsetup.sh from ~/android/organization.

Now ensure that your Galaxy Tab 2 7.0 (Wi-Fi) is connected to your reckoner via the USB cable and that you are in the ~/android/arrangement/device/samsung/p3110 directory (y'all can cd ~/android/arrangement/device/samsung/p3110 if necessary). And then run the excerpt-files.sh script:

          $ ./extract-files.sh        

You lot should come across the proprietary files (aka "blobs") go pulled from the device and moved to the ~/android/system/vendor/samsung directory. If you see errors about adb beingness unable to pull the files, adb may not be in the path of execution. If this is the example, run into the adb folio for suggestions for dealing with "command not found" errors.

Note:

Your device should already be running a build of CyanogenMod for the branch you wish to build for the excerpt-files.sh script to function properly.

Notation:

It's important that these proprietary files are extracted to the ~/android/system/vendor/samsung directory by using the extract-files.sh script. Makefiles are generated at the same time to make sure the blobs are somewhen copied to the device. Without these blobs, CyanogenMod may build without error, but you'll be missing of import functionality, such as graphics libraries that enable y'all to see anything!

Plough on caching to speed up build

You can speed up subsequent builds by adding

          consign USE_CCACHE=1        

to your ~/.bashrc file (what's a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the tiptop of your Android tree:

          prebuilts/misc/linux-x86/ccache/ccache -Chiliad 50G        

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for example, a typical 1hr build time tin can exist reduced to 20min). If you lot're only building for ane device, 25GB-50GB is fine. If yous programme to build for several devices that do non share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so have this into consideration. Meet more information about ccache on Google's android build environs initialization page.

Helpful Tip

If you are a very agile developer, working on many other projects than just Android, y'all might prefer to go along your Android ccache contained (because information technology's huge and can slow down the efficiency of ccache in your other projects). Beginning with CyanogenMod 12.one, you tin can specify environment variables for the location and size of CyanogenMod's ccache. Some syntax examples: export ANDROID_CCACHE_DIR="$HOME/android/.ccache" and export ANDROID_CCACHE_SIZE="50G".

Start the build

Fourth dimension to get-go building! And then now type:

          $ croot $ brunch p3110        

The build should brainstorm.

Helpful Tip

If the build doesn't commencement, try lunch and cull your device from the menu. If that doesn't work, try breakfast and choose from the menu. The command brand p3110 should then work.

Helpful Tip

A 2nd, bonus tip! If you become a command not found error for croot, brunch, or tiffin, be sure you've washed the source build/envsetup.sh control in this Terminal session from the ~/android/system directory.

Helpful Tip

A tertiary tip! If the build to fails while downloading Gello, y'all'll demand to import a missing certificate into Maven'south truststore. Detailed instructions on how to do that tin can exist found here

If the build breaks…

• If you lot feel this not-plenty-retentivity-related error…

          ERROR: signapk.jar failed: return code 1make: *** [out/target/product/p3110/cm_p3110-ota-eng.root.naught] Error ane        

…you may want to make the following change to ~/android/organization/build/tools/releasetools/mutual.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and supplant it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If y'all encounter a bulletin about things suddenly being "killed" for no reason, your (virtual) automobile may have run out of memory or storage space. Assign it more resource and try again.

Install the build

Bold the build completed without error (it will be obvious when it finishes), type:

          $ cd $OUT        

in the aforementioned terminal window that you did the build. Here y'all'll find all the files that were created. The stuff that will get in /system is in a folder called arrangement. The stuff that will go your ramdisk is in a binder chosen root. And your kernel is chosen… kernel.

Only that'due south all merely groundwork info. The ii files we are interested in are (one) recovery.img, which contains CyanogenMod Recovery, and (ii) cm-13.0-20161224-UNOFFICIAL-p3110.nothing, which is the CyanogenMod installation package.

Install CyanogenMod

Dorsum to the $OUT directory on your computer– you should see a file that looks something similar:

          cm-13.0-20161224-UNOFFICIAL-p3110.zip        

Note:

The in a higher place file name may vary depending on the version of CM you are edifice. Your build may not include a version number or may identify itself as a "KANG" rather than UNOFFICIAL version. Regardless, the file proper noun will stop in .zip and should exist titled similarly to official builds.

Now you lot can wink the cm...zip file above as usual via recovery manner. Before doing then, now is a proficient time to make a fill-in of whatsoever installation is currently running on the device in example something goes wrong with the flash attempt. While CyanogenMod Recovery doesn't accept a backup feature, at that place are other custom recoveries available that do. You can also use something similar Titanium Backup (root required) equally an alternative.

Success! And then….what's next?

You've washed information technology! Welcome to the elite gild of self-builders. You've built your operating system from scratch, from the ground upward. Yous are the master/mistress of your domain… and hopefully yous've learned a bit on the manner and had some fun too.

Now that you've succeeded in building CyanogenMod for your device, here are some suggestions on what to exercise adjacent.

Also, exist sure to have a glance at the Dev Middle on this wiki for all kinds of more than detailed data well-nigh programmer topics ranging from collecting logs, agreement what'south in the source lawmaking directories, submitting your ain contributions, porting CyanogenMod to new devices, and a lot more than.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC Past-SA 3.0 licence.

Source: https://cyanogenmodroms.com/p3110/

Posted by: pollardwhictibed.blogspot.com

Share this post