Dowload Firmware 4.4.4 of Samsung Galaxy S Blaze 4g

CyanogenMod ROM Samsung Milky way S Blaze 4G (SGH-T769) T-Mobile (t769)

How to Install CyanogenMod on the Samsung Galaxy Due south Blaze 4G (t769)

Installing a custom recovery

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

1. Download and install the
   Heimdall Suite
   • Windows:
     Extract the Heimdall suite and accept notation of the directory property
     heimdall.exe. You tin 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 take the
     Microsoft Visual C++ 2012 Redistributable Bundle (x86/32bit)
     installed on your computer.
   • Linux:
     Pick the appropriate installation package based on your distribution. The
     -frontend
     packages are non required for this guide. After installation, heimdall should be bachelor from the final; type
     heimdall version
     to verify installation succeeded.
   • Mac:
     Install the dmg package. Later installation, heimdall should be available from the final; type
     heimdall version
     to verify installation succeeded.
   • Building from source:
     The source code for the Heimdall Suite is available on
     Github. For more details almost how to compile the Heimdall Suite, please refer to the
     
     README
     
     file on Github nether the relevant operating system directory. Y’all tin can likewise refer to the
     Install and compile Heimdall
     instructions on this wiki.
2. Download recovery — you can straight 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 can exist found at that place). For general info about recoveries click
   here.

   Recovery:
   Download

   md5:
   780adf6720237cad36296bffdd2c3f28

3. Power off the Milky way Southward Bonfire 4G and connect the USB adapter to the figurer but not to the Galaxy S Blaze 4G, withal.
4. Boot the Galaxy S Blaze 4G into download way.
   Volume Down
   &
   Volume Up, and
   Connect the USB cable
   Accept the disclaimer on the device. And then, insert the USB cable into the device.
5. Windows (only) driver installation –
   Skip this step if yous are using Linux or Mac

   A more complete prepare of the post-obit instructions can be found 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 Serial
      or
      Device Name
      from the drop downwards menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, similar Samsung Windows drivers and/or
      Kies).
   4. Click
      Replace Commuter
      (having selecting “Install Driver” from the drop downwardly list congenital 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 may receive two more than prompts virtually security. Select the options that let yous to behave on.
6. At this point, familiarize yourself with the
   Flashing with heimdall
   notes below so that you are prepared for whatsoever strange behaviour if it occurs.
7. On the computer, open up a terminal (or Command Prompt on Windows) in the directory where the recovery epitome is located and type:

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

   Tip: The file may non exist named identically to what’s in this control. If the file is wrapped in a zilch or tar file,
   extract the file first, because heimdall isn’t going to do it for you.

8. A blue transfer bar volition appear on the device showing the recovery being transferred.
9. Unplug the USB cable from your device.
   • Notation:
     Exist sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery volition be overwritten and the device will reboot (appearing every bit though your custom recovery failed to install).
10. Manually reboot the phone into recovery style by performing the following.
    Volume Down
    &
    Volume Upwardly
    &
    Power
    then release
    Power
    after the phone vibrates. Continue holding
    Volume Down
    &
    Volume Up
    until Recovery mode boots upwardly
11. The Galaxy South Bonfire 4G now has a custom recovery installed. Go on to the adjacent section.

Installing CyanogenMod from recovery

1. Make certain your estimator has working
   adb.
2. Download the
   CyanogenMod build package for your device
   that yous’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. Boot to recovery mode, and connect the phone to your reckoner through USB.
   • Book Down
     &
     Volume Up
     &
     Power
     and so release
     Power
     afterwards the phone vibrates. Go along holding
     Volume Downward
     &
     Volume Up
     until Recovery mode boots up
4. In ClockworkMod Recovery, employ the concrete book buttons to movement up and down. On most devices, the
   power button
   is used to confirm a menu option, but for some devices a concrete
   home
   central acts as a selector. Some devices have bear on enabled ClockworkMod Recovery, in which instance you may be able to swipe to, or touch, bill of fare selections.
5. Optional (Recommended):
   Select
   backup and restore
   to create a backup.
6. Select
   wipe data/mill reset.
7. You take two options for transferring and installing the installation packages. The
   sideload method
   is more universal across devices, whereas the
   push button and install method
   is more commonly used:
   • 
     Sideload method:
     
     select
     install zip > install zip from sideload. Follow the on-screen notices to install the packet. The installer does not necessarily display an “Install consummate.” message. You can tell the install is complete if there were no fatal fault messages and you have regained control over the carte.
   • 
     Push and install method:
     
     Open a control prompt (or Concluding on Mac and Linux) and navigate to the directory holding the package(s) you would like to install. On the device, navigate to the
     mounts and storage
     menu. If you see
     /storage/sdcard0
     or
     /sdcard
     as a mountable volume, go ahead and mount it. If yous exercise not come across one of these partitions, and then instead mount the
     /data
     segmentation.
     Take note of which volume y’all mounted.
     Now, push the package(s) to your device (also, encounter tip beneath):

   – If you mounted
   /storage/sdcard0, then:
   adb push update.nada /storage/sdcard0/

   – If you lot mounted
   /sdcard
   or
   /data, and then:
   adb push button update.zilch /sdcard/

   where
   update.zip
   should be replaced with the packet filename. Become back to the main menu and select
   install zilch. Cull to install from the same directory where you pushed the package(s). If you are installing multiple packages, install CyanogenMod showtime then install any subsequent packages on top of it.

8. Once installation has finished, return to the main menu and select
   reboot organization now. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Samsung Galaxy S Blaze 4G (t769)

Introduction

These instructions will hopefully assist y’all to start with a stock Galaxy South Blaze 4G, unlock the bootloader (if necessary), and then download the required tools as well equally the very latest source code for CyanogenMod (based on Google’south Android operating arrangement). Using these, you tin build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly non for the very very very uninitiated, these steps shouldn’t crave a PhD in software development either. Some readers volition have no difficulty and breeze through the steps easily. Others may struggle over the most bones operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether y’all feel comfortable or are getting over your head.

Recollect, you presume all gamble of trying this, but you volition reap the rewards! It’south pretty satisfying to boot into a fresh operating organization you baked at dwelling house 🙂 And once you’re an Android-edifice ninja, there volition be no more than need to wait for “nightly” builds from anyone. You lot will take at your fingertips the skills to build a full operating arrangement from code to a running device, whenever you desire. Where yous go from there– maybe yous’ll add a feature, fix a problems, add together a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’due south all really up to you.

What yous’ll need

• A
  Galaxy S Blaze 4G
• A relatively recent calculator (Linux, Os X, or Windows) with a reasonable amount of RAM and about 100 GB of complimentary storage (more than if you enable ccache or build for multiple devices). The less RAM you take, the longer the build volition accept (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 South Bonfire 4G (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent net connectedness & reliable electricity 🙂
• Some familiarity with basic Android operation and terminology. It would help if yous’ve installed custom roms on other devices and are familiar with
  recovery. Information technology may likewise 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 chance to learn. It’s gratis–
only download and run a virtual auto (VM)
such as
Virtualbox, and so install a Linux distribution such every bit
Ubuntu
(AOSP vets Ubuntu
as well). Whatsoever recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a figurer, if you will. If you lot hate Linux for whatever reason, you tin can always but uninstall and delete the whole matter. (There are plenty of places to notice instructions for setting upwardly Virtualbox with Ubuntu, so I’ll leave it to you lot to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Surroundings

Install the SDK

If you have not previously installed
adb
and
fastboot, install the
Android SDK. “SDK” stands for Software Developer Kit, and information technology includes useful tools that you can use to flash software, expect at the arrangement logs in existent time, take hold of screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. Yous can install these using the package manager of your choice.

For both 32-bit & 64-scrap systems, you’ll demand:

        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 add-on to the higher up, for 64-bit systems, get these:

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

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

• lib32readline-gplv2-dev
  →
  lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

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

Java versions:
Different versions of CyanogenMod require unlike versions of the JDK (Java Evolution Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod x.one: Lord’s day/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – xi.0: Dominicus/Oracle Coffee SE 1.half dozen or one.seven (OpenJDK 1.vii works fine, but the build arrangement volition display a alarm)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (encounter note near OpenJDK i.viii below)
• CyanogenMod 14.1: OpenJDK ane.viii

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK:
Since OpenJDK 1.seven was
removed
from the official Ubuntu repositories, you take a couple options:

1. Obtain OpenJDK one.7 from the
   openjdk-r PPA
2. Enable experimental OpenJDK i.viii back up in CyanogenMod 13.0 (not bachelor in earlier version). To enable OpenJDK ane.8 support, add this line to your
   $Habitation/.bashrc
   file:
   consign EXPERIMENTAL_USE_JAVA8=true.

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

Create the directories

You will need to fix up some directories in your build environment.

To create them:

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

Install the
repo
command

Enter the post-obit to download the “repo” binary and make it 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 contempo versions of Ubuntu,
~/bin
should already be in your
PATH. Y’all tin can check this past opening
~/.profile
with a text editor and verifying the following code exists (add it if it is missing):

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

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

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

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

Download the source code

To commencement the download of all the source code to your computer:

        $ repo sync
      

The CM manifests include a sensible default configuration for
repo, which we strongly suggest y’all apply (i.eastward. don’t add any options to
sync). For reference, our default values are
-j iv
and
-c. The
-j 4
part ways that there will be 4 simultaneous threads/connections. If you feel problems syncing, you can lower this to
-j 3
or
-j two.
-c
volition ask repo to pull in
only
the electric current branch, instead of the entire CM history.

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

Become prebuilt apps (CM11 and below)

Next,

        $ cd ~/android/organisation/vendor/cm
      

and then enter:

        $ ./become-prebuilts
      

You won’t see any confirmation- just another prompt. Just this should crusade some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), so type:

        $ source build/envsetup.sh $ breakfast t769
      

This volition 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 listing all of the repositories divers in
cm.dependencies
in your local manifest.

At present ensure that your Galaxy South Blaze 4G is connected to your figurer via the USB cable and that you are in the
~/android/system/device/Samsung/t769
directory (you can
cd ~/android/system/device/Samsung/t769
if necessary). And so run the
excerpt-files.sh
script:

        $ ./extract-files.sh
      

You should see the proprietary files (aka “blobs”) become pulled from the device and moved to the
~/android/system/vendor/Samsung
directory. If you see errors about
adb
being unable to pull the files,
adb
may not be in the path of execution. If this is the example, meet the
adb
page for suggestions for dealing with “command not establish” errors.

Turn on caching to speed upward build

You tin speed upward subsequent builds by adding

        export USE_CCACHE=1
      

to your
~/.bashrc
file (what’southward a .bashrc file?). Then, specify the corporeality of disk space to dedicate to
ccache
by typing this from the pinnacle 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 tin be reduced to 20min). If you lot’re only building for one device, 25GB-50GB is fine. If you program to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space volition be permanently occupied on your bulldoze, then take this into consideration. See more than information nearly ccache on Google’s
android build surroundings initialization page.

Start the build

Time to start building! So now type:

        $ croot $ brunch t769
      

The build should begin.

If the build breaks…

• If you feel this non-enough-memory-related fault…

        Fault: signapk.jar failed: render code 1make: *** [out/target/product/t769/cm_t769-ota-eng.root.zip] Mistake 1
      

…you may desire to brand the post-obit change to
~/android/arrangement/build/tools/releasetools/common.py:

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

And then start the build again (with brunch).

• If you lot run into a bulletin about things suddenly beingness “killed” for no reason, your (virtual) machine may have run out of retentivity or storage space. Assign information technology more resource and try again.

Install the build

Assuming the build completed without error (information technology volition exist obvious when it finishes), blazon:

        $ cd $OUT
      

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in
/arrangement
is in a folder called
system. The stuff that will become your ramdisk is in a folder called
root. And your kernel is called…
kernel.

But that’s all only background info. The 2 files we are interested in are (1)
recovery.img, which contains CyanogenMod Recovery, and (2)
cm-13.0-20161224-UNOFFICIAL-t769.nix, which is the CyanogenMod installation package.

Install CyanogenMod

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

        cm-13.0-20161224-UNOFFICIAL-t769.zip
      

At present y’all can flash the
cm...zip
file above as usual via recovery mode. Earlier doing and then, now is a good time to brand a fill-in of whatever installation is currently running on the device in case something goes wrong with the flash effort. While CyanogenMod Recovery doesn’t accept a backup feature, at that place are other custom recoveries bachelor that do. You can also utilize something like Titanium Backup (root required) as an culling.

Success! So….what’s next?

Yous’ve done it!
Welcome to the elite lodge of self-builders. You’ve built your operating organization from scratch, from the footing up. You are the master/mistress of your domain… and hopefully y’all’ve learned a bit on the manner and had some fun likewise.

Now that y’all’ve succeeded in building CyanogenMod for your device, here are
some suggestions on what to do next.

Also, be sure to have a glance at the
Dev Centre
on this wiki for all kinds of more detailed information about 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 Past-SA 3.0
licence.