Download Cyanogenmod Cm13 Marshmallow Roms For Samsung S4 Sph-L720 Jfltespr UPDATED

Download Cyanogenmod Cm13 Marshmallow Roms For Samsung S4 Sph-L720 Jfltespr

Cyanogenmod ROM Samsung Galaxy S4 Sprint (SPH-L720) (jfltespr)

Quick Info

Notes

Note: No longer deprecated

Starting with CM 12 nightlies, this carrier specific device no longer uses the unified device build. Withal, it can still exist found at jflte. Unfortunately, this is not reflected in the congenital-in Cyanogenmod updater in unified builds.

Special kick modes

• Recovery: Vol Up & Home & Ability
• Download: Vol Down & Home & Power

Source code

Galaxy S4 (Sprint) Specifications

Codename:	jfltespr
Likewise known as:	SPH-L720
Vendor:	Samsung
Release appointment:	2013 Apr
Carrier:	Sprint
Type:	telephone
CDMA freq:	850, 900, 1800, 1900 MHz CDMA 800, 1900 MHz EVDO Rev. A 850, 900, 1900, 2100 MHz UMTS / HSPA
LTE freq:	750 MHz (Band 13), AWS
Platform:	Qualcomm Snapdragon 600
CPU:	ane.9 GHz quad-core Krait 300
GPU:	Adreno 320
RAM:	2GB
Weight:	130g
Dimensions:	136.half dozen mm (5.38 in) H 69.8 mm (2.75 in) Westward vii.9 mm (0.31 in) D
Screen size:	127 mm (five.0 in)
Resolution:	1920×1080
Screen density:	440 ppi
Screen blazon:	Pentile RGBG Full HD Super AMOLED
Internal storage:	16GB
SD Card:	up to 64GB
Bluetooth:	4.0
Wi-Fi:	802.11a/b/yard/northward/ac
Principal camera:	xiii MP, 1080p Full HD Video Recording @ 30fps
Secondary camera:	2 MP 1080p Hard disk drive Video Recording @ 30fps
Ability:	2600 mAh Li-ion, removable
Peripherals:	DLNA, Miracast, GPS/GLONASS, NFC, Infrared Port, USB 2.0 (Micro-B port, USB charging), USB On-The-Go one.three, MHL 2.0, HDMI (Television-out, via MHL A\V link), Accelerometer, Barometer, Gesture sensor, Gyroscope, Hall event sensor, Hygrometer, Magnetometer, Proximity sensor, RGB low-cal sensor, Thermometer
CM supported:	10.1, 10.2, xi, 12.1, 13

How to Install CyanogenMod on the Samsung Galaxy S4 (Dart) (jfltespr)

Note: DISCLAIMER

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

Important Notes

Note: No longer deprecated

Starting with CM 12 nightlies, this carrier specific device no longer uses the unified device build. However, it tin still exist found at jflte. Unfortunately, this is not reflected in the congenital-in Cyanogenmod updater in unified builds.

Installing a custom recovery

Samsung devices come with a unique boot style called Download Way which is very similar to Fastboot Way 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 boot mode. Rooting the stock firmware is neither recommended nor necessary.

1. Download and install the Heimdall Suite
   • Windows: Extract the Heimdall suite and take notation of the directory holding heimdall.exe. Yous 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 accept the Microsoft Visual C++ 2012 Redistributable Package (x86/32bit) installed on your computer.
   • Linux: Option the advisable installation packet based on your distribution. The -frontend packages are not required for this guide. After installation, heimdall should be bachelor from the terminal; type heimdall version to verify installation succeeded.
   • Mac: Install the dmg package. After installation, heimdall should be available from the last; type heimdall version to verify installation succeeded.
   • Building from source: The source lawmaking for the Heimdall Suite is available on Github. For more than details nearly how to compile the Heimdall Suite, delight refer to the README file on Github nether the relevant operating system directory. You tin can also refer to the Install and compile Heimdall instructions on this wiki.
2. Download recovery — you can directly download a recovery image using the link beneath, or visit TWRP site to check for the latest version of recovery for your device (if your device tin can be found at that place). For general info well-nigh recoveries click hither.

   Recovery: Download

   md5: 5fbd28742161a1841621727c3c9816e3

3. Power off the Galaxy S4 (Sprint) and connect the USB adapter to the figurer but not to the Milky way S4 (Sprint), yet.
4. Kick the Galaxy S4 (Sprint) into download style. Vol Downward & Dwelling & Power Accept the disclaimer on the device. Then, insert the USB cable into the device.
5. Windows (but) commuter installation – Skip this step if you are using Linux or Mac

   A more consummate ready of the following instructions can be establish in the Zadig User Guide.

   1. Run zadig.exe from the Drivers binder of the Heimdall Suite.
   2. Choose Options » List All Devices from the menu.
   3. Select Samsung USB Blended Device or MSM8x60 or Gadget Serial or Device Name from the drop downwardly card. (If zero relevant appears, effort uninstalling whatever Samsung related Windows software, like Samsung Windows drivers and/or Kies).
   4. Click Replace Driver (having selecting "Install Driver" from the drib downwardly listing built into the push button).
   5. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow yous to carry on.
6. At this betoken, familiarize yourself with the Flashing with heimdall notes below so that you are prepared for any foreign behaviour if information technology occurs.
7. On the computer, open a terminal (or Command Prompt on Windows) in the directory where the recovery image is located and type:

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

   Tip: The file may not be named identically to what's 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 it for you.

8. A bluish transfer bar will appear on the device showing the recovery being transferred.
9. Unplug the USB cable from your device.
   • Note: Be sure to reboot into recovery immediately later on having installed the custom recovery. Otherwise the custom recovery volition be overwritten and the device will reboot (appearing equally though your custom recovery failed to install).
10. Manually reboot the telephone into recovery mode by performing the following. Vol Up & Home & Ability
11. The Galaxy S4 (Sprint) now has a custom recovery installed. Continue to the side by side department.

Annotation: Flashing with heimdall

• In Windows 7 UAC (User Account Control) may demand switching off. One time Heimdall is finished it can be re-enabled.
• Protocol initialization tin fail if the device is continued via a USB hub – connect the USB cable direct to the PC
• It may exist necessary to run the heimdall flash command equally root in Linux or Mac Os X: sudo heimdall flash [...]. Typical symptoms of this are:
  • a blue bar doesn't prove upwardly after the procedure has finished
  • Failed to confirm end of file transfer sequence!
• It may be necessary to capitalize the name of the partitioning on some devices. Endeavour --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 information technology with sudo: reference.
• On Mac Bone X you may run across this message: "Error: Claiming interface failed!". If then, you need to disable the default USB drivers with the following commands:
  sudo kextunload -b com.apple tree.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;
  If you have installed Samsung Kies, yous may farther need to unload those USB drivers with the post-obit 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 1.4.0 (the latest version available for download on the Glass Echidna website) you may run across this message or one similar to it:
  Error: Failed to confirm end of PIT file transfer!
  If you feel this mistake, follow the instructions for compiling Heimdall from source to become the latest version on GitHub with the issue patched.

Helpful Tip

• The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into recovery later on leaving Download Manner instead of letting the ROM boot up normally. If your recovery is overwritten, simply redo the steps you followed above and catch information technology before information technology boots next fourth dimension.
• Notation for upgrades from gingerbread to jellybean remember the recovery is changed. This means once you install do NOT restore to old-gingerbread-stock ROM from cwm-recovery.
• To upgrade from stock/CM7/CM9/CM10.1.2/CM10.1.3 to CM10.2, you must outset boot into recovery and wipe data, cache, and dalvik cache (mill reset). Due to the new partition layout in CM10.ii, failing to perform these steps will outcome in a bootloop. See here for details; more near repartitioning here. If you lot missed this pace earlier installing, kicking to recovery and factory reset, then reinstall CM10.ii.
• Some users have reported connexion errors if the device is connected to a USB hub. If y'all feel such errors it is recommended that you effort connecting your device to a USB port on the motherboard.
• Antivirus software may prevent Heimdall from connecting properly. Disable your antivirus earlier proceeding.
• When Heimdall fails to connect, the Download style may get stuck, making all farther attempts fail too. To retry, you may need to restart the Download mode: plow off the phone by holding Power for v-10 seconds (or past pulling out the battery), then boot into Download way and run Heimdall once again.
• If Heimdall fails to connect (errors related to initializing the protocol, or transferring data):

  if you just installed the driver, attempt rebooting your computer and trying again.

  if you still have troubles afterwards reboot, in Zadig try installing the libusbK driver rather than the WinUSB driver.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you'd like to install to your computer.

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

3. Place the CyanogenMod .cipher package, as well equally any optional .nothing packages, on the root of /sdcard:
   • Using adb: adb push filename.zippo /sdcard/

   Notation: You tin can copy the .nada packages to your device using any method you 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 mode, you may demand to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.

4. If you are not already in recovery, boot to recovery fashion now.
   • Vol Upwardly & Home & Ability
5. In Team Win Recovery Project, select bill of fare choices by borer on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and and then Factory Reset.
8. Select Install.
9. Navigate to /sdcard and select the CyanogenMod .naught package.
10. Follow the on-screen notices to install the package.
11. Optional: Install whatsoever additional packages you lot wish using the same method (if you are installing multiple packages, install CyanogenMod first and so install any subsequent packages on summit of it).
12. Once installation has finished, render to the principal menu and select Reboot, then Arrangement. The device volition now boot into CyanogenMod.

How To Build CyanogenMod For Samsung Galaxy S4 (Dart) (jfltespr)

Contents

• 1 Introduction
  • 1.1 What you'll demand
• ii Build CyanogenMod and CyanogenMod Recovery
  • 2.1 Ready the Build Environs
    • 2.i.1 Install the SDK
    • 2.1.2 Install the Build Packages
  • two.2 Create the directories
  • two.iii Install the repo control
  • 2.4 Put the ~/bin directory in your path of execution
  • 2.5 Initialize the CyanogenMod source repository
  • two.6 Download the source code
  • 2.7 Get prebuilt apps (CM11 and below)
  • ii.viii Prepare the device-specific code
  • 2.nine Extract proprietary blobs
  • ii.10 Plow on caching to speed upwardly build
  • 2.11 Kickoff the build
  • 2.12 If the build breaks…
• 3 Install the build
  • three.1 Install CyanogenMod
  • 3.2 Success! So….what's adjacent?

Introduction

These instructions will hopefully assistance you lot to start with a stock Galaxy S4 (Sprint), unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google's Android operating system). Using these, yous can build both CyanogenMod and CyanogenMod Recovery image from source code, and and then install them both to your device.

Information technology is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn't require a PhD in software development either. Some readers will have no difficulty and breeze through the steps hands. Others may struggle over the most basic operation. Because people'due south experiences, backgrounds, and intuitions differ, it may be a proficient idea to read through just to ascertain whether you feel comfy or are getting over your head.

Remember, yous assume all risk of trying this, but you lot will reap the rewards! Information technology's pretty satisfying to boot into a fresh operating arrangement yous baked at home :) And once you're an Android-building ninja, there will be no more need to wait for "nightly" builds from anyone. You lot will have at your fingertips the skills to build a total operating system from code to a running device, whenever you lot want. Where you lot get from there– peradventure you'll add a characteristic, fix a bug, add a translation, or use what you lot've learned to build a new app or port to a new device– or maybe you'll never build again– it's all really up to you.

What you'll need

• A Galaxy S4 (Sprint)
• A relatively recent computer (Linux, Os X, or Windows) with a reasonable amount of RAM and near 100 GB of complimentary storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will accept (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cablevision uniform with the Galaxy S4 (Dart) (typically micro USB, merely older devices may use mini USB or have a proprietary cable)
• A decent internet connectedness & reliable electricity :)
• Some familiarity with basic Android performance and terminology. It would help if you've installed custom roms on other devices and are familiar with recovery. It may as well be useful to know some basic command line concepts such every bit cd for "alter directory", the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are non accustomed to using Linux– this is an excellent adventure to learn. Information technology's complimentary– just download and run a virtual machine (VM) such as Virtualbox, and so install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, simply the latest is recommended.

Note:

You want to utilise a 64-bit version of Linux. A 32-bit Linux environment will only work if y'all are building CyanogenMod 6 and older. For CyanogenMod 10.ane, if y'all meet issues with 64bit host binaries, y'all can set BUILD_HOST_32bit=1 in your environment. This is generally not needed, though, peculiarly with CyanogenMod 10.two and newer.

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

So let's begin!

Build CyanogenMod and CyanogenMod Recovery

Gear up the Build Environs

Note:

You lot only need to do these steps the outset time yous build. If you previously prepared your build environment and have downloaded the CyanogenMod source code for another device, skip to Prepare the device-specific lawmaking.

Install the SDK

If you lot accept not previously installed adb and fastboot, install the Android SDK. "SDK" stands for Software Programmer Kit, and it includes useful tools that yous tin use to wink software, wait at the arrangement logs in real fourth dimension, grab screenshots, and more– all from your computer.

Helpful Tip

While the SDK contains lots of different things– the 2 tools you lot are virtually 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 pick.

Helpful Tip

A parcel manager in Linux is a system used to install or remove software (usually originating from the Internet) on your computer. With Ubuntu, you can utilise the Ubuntu Software Center. Even ameliorate, you may besides use the apt-get install command straight in the Final. (Learn more than nearly the apt packaging tool organisation from Wikipedia.)

For both 32-chip & 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.eight-dev libxml2 libxml2-utils lzop maven openjdk-seven-jdk pngcrush schedtool squashfs-tools xsltproc naught zlib1g-dev        

In addition to the above, for 64-bit systems, become these:

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

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu xvi.04 (xenial) and newer, substitute (additionally see coffee notes below):

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

Coffee versions: Dissimilar versions of CyanogenMod require unlike versions of the JDK (Java Development Kit):

• CyanogenMod 7 – ix: Lord's day/Oracle Coffee SE 1.6
• CyanogenMod ten.1: Lord's day/Oracle Java SE ane.6 or 1.7
• CyanogenMod 10.2 – xi.0: Lord's day/Oracle Java SE 1.6 or i.7 (OpenJDK 1.seven works fine, merely the build organization will brandish a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.viii beneath)
• CyanogenMod fourteen.one: OpenJDK ane.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK i.seven 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 ane.eight support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK ane.8 support, add this line to your $Home/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also encounter http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up up some directories in your build environs.

To create them:

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

Install the repo command

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

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

Put the ~/bin directory in your path of execution

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

          # set PATH and so it includes user's private bin if it exists if [ -d "$Domicile/bin" ] ; so     PATH="$HOME/bin:$PATH" fi        

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Brand sure the cm co-operative entered hither is the ane yous wish to build and is supported on your device.

          $ cd ~/android/arrangement/ $ repo init -u https://github.com/CyanogenMod/android.git -b cm-xiii.0        

Download the source code

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

          $ repo sync        

The CM manifests include a sensible default configuration for repo, which we strongly propose y'all apply (i.e. don't add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there volition be iv simultaneous threads/connections. If y'all experience problems syncing, y'all can lower this to -j 3 or -j 2. -c will ask repo to pull in merely the current co-operative, instead of the unabridged CM history.

Set up 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 lot tin can do information technology every few days to keep your code base of operations fresh and up-to-date.

Get prebuilt apps (CM11 and below)

Next,

          $ cd ~/android/system/vendor/cm        

and so enter:

          $ ./get-prebuilts        

You won't see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source lawmaking. In one case completed, this does not need to be done again.

Prepare the device-specific code

Helpful Tip – Errors during breakfast

Unlike maintainers setup their device inheritance rules differently. Some crave a vendor directory to be populated before breakfast will even succeed. If you receive an error hither about vendor makefiles, so bound downwardly to the next section Excerpt proprietary blobs. The first portion of breakfast should take succeeded at pulling in the device tree and the extract blobs script should exist bachelor. After completing that section, you can rerun breakfast jfltespr

Later the source downloads, ensure y'all are in the root of the source code (cd ~/android/arrangement), and then blazon:

          $ source build/envsetup.sh $ breakfast jfltespr        

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

Helpful Tip

If y'all want to know more most what source build/envsetup.sh does or simply desire to know more most the breakfast, brunch and dejeuner commands, yous can head over to the Envsetup assist folio.

Helpful Tip

Instead of typing cd ~/android/arrangement every time you want to render dorsum to the root of the source lawmaking, here's a short command that will exercise it for you: croot. To use this command, you must first run source build/envsetup.sh from ~/android/organisation.

At present ensure that your Galaxy S4 (Sprint) is connected to your calculator via the USB cablevision and that y'all are in the ~/android/system/device/samsung/jfltespr directory (y'all can cd ~/android/organisation/device/samsung/jfltespr if necessary). And then run the excerpt-files.sh script:

          $ ./extract-files.sh        

You should see the proprietary files (aka "blobs") get pulled from the device and moved to the ~/android/arrangement/vendor/samsung directory. If yous see errors about adb being unable to pull the files, adb may not exist in the path of execution. If this is the case, see the adb folio for suggestions for dealing with "control non found" errors.

Note:

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

Note:

It's important that these proprietary files are extracted to the ~/android/organisation/vendor/samsung directory by using the extract-files.sh script. Makefiles are generated at the same time to make certain the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without mistake, simply you'll exist missing important functionality, such as graphics libraries that enable you to see anything!

Plow on caching to speed up build

You can speed up subsequent builds past adding

          consign USE_CCACHE=ane        

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

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

where 50G corresponds to 50GB of cache. This only needs to exist 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 instance, a typical 1hr build fourth dimension can be reduced to 20min). If y'all're merely building for one device, 25GB-50GB is fine. If yous plan to build for several devices that do not share the aforementioned kernel source, aim for 75GB-100GB. This space will exist permanently occupied on your drive, so take this into consideration. See more information about ccache on Google'southward android build surroundings initialization folio.

Helpful Tip

If you are a very active programmer, working on many other projects than just Android, y'all might prefer to continue your Android ccache independent (considering information technology's huge and can slow downward the efficiency of ccache in your other projects). Beginning with CyanogenMod 12.ane, you can specify environment variables for the location and size of CyanogenMod's ccache. Some syntax examples: export ANDROID_CCACHE_DIR="$Domicile/android/.ccache" and export ANDROID_CCACHE_SIZE="50G".

First the build

Time to first building! So now type:

          $ croot $ brunch jfltespr        

The build should begin.

Helpful Tip

If the build doesn't start, attempt tiffin and choose your device from the menu. If that doesn't piece of work, endeavour breakfast and choose from the card. The command brand jfltespr should then work.

Helpful Tip

A 2nd, bonus tip! If y'all get a command not establish error for croot, brunch, or lunch, be certain yous've done the source build/envsetup.sh command in this Terminal session from the ~/android/system directory.

Helpful Tip

A third tip! If the build to fails while downloading Gello, you lot'll need to import a missing document into Maven'south truststore. Detailed instructions on how to do that tin be institute here

If the build breaks…

• If you experience this non-enough-retention-related error…

          ERROR: signapk.jar failed: return lawmaking 1make: *** [out/target/product/jfltespr/cm_jfltespr-ota-eng.root.zip] Error 1        

…you may want to brand the following modify to ~/android/arrangement/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (information technology should announced either nether OPTIONS.java_args or near usage of signapk.jar), and supervene upon it with -Xmx1024m or -Xmx512m.

Then kickoff the build again (with brunch).

• If you lot see a message about things suddenly being "killed" for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without fault (it will be obvious when it finishes), blazon:

          $ cd $OUT        

in the aforementioned final window that you did the build. Hither you'll find all the files that were created. The stuff that volition become in /system is in a folder chosen organization. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that's all just background info. The 2 files we are interested in are (i) recovery.img, which contains CyanogenMod Recovery, and (ii) cm-13.0-20161224-UNOFFICIAL-jfltespr.goose egg, which is the CyanogenMod installation packet.

Install CyanogenMod

Back to the $OUT directory on your reckoner– you should see a file that looks something like:

          cm-13.0-20161224-UNOFFICIAL-jfltespr.cypher        

Note:

The higher up file name may vary depending on the version of CM yous are building. Your build may not include a version number or may identify itself equally a "KANG" rather than UNOFFICIAL version. Regardless, the file proper name volition end in .zip and should be titled similarly to official builds.

At present y'all can wink the cm...null file higher up as usual via recovery mode. Earlier doing so, now is a proficient time to brand a backup of any installation is currently running on the device in case something goes wrong with the wink endeavor. While CyanogenMod Recovery doesn't take a backup feature, at that place are other custom recoveries available that practice. You can too employ something like Titanium Backup (root required) as an alternative.

Success! Then….what's adjacent?

Yous've done it! Welcome to the aristocracy gild of self-builders. You've built your operating arrangement from scratch, from the basis up. You are the chief/mistress of your domain… and hopefully you lot've learned a bit on the way and had some fun as well.

At present that y'all've succeeded in building CyanogenMod for your device, here are some suggestions on what to do side by side.

Also, exist certain to take a glance at the Dev Eye on this wiki for all kinds of more detailed information most developer topics ranging from collecting logs, understanding what's in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

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

DOWNLOAD HERE

Posted by: arnoldsleasedgered69.blogspot.com

Share this post