[Galaxy Note 3 Original Android Development] alexyuh:
Assembling system.img for the models on the processor Samsung Snapdragon &Exynos Octa

Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)

What's needed to build their own ROM images: Preferably installed natively (live, not to Wirth., Machine) operating system based on Linux (UBUNTU, Linux Mint) and always 64 bit version.​

Configure the system to use in building firmware:

sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.8-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind libreadline6-dev gcc-multilib g++-multilib libc6-dev x11proto-core-dev libx11-dev libz-dev gawk texinfo automake libtool cvs libsdl-dev

sudo add-apt-repository "deb http://archive.canonical.com/ raring partner"
sudo apt-get update

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-jdk7-installer

sudo apt-get update
sudo apt-get install ia32-libs

Collect firmware:

1. - We will need to complete the assembly binaries Downloading this file

View attachment 2357217

On versions of UBUNTU 13.04 and above may experience problems when you use these binaries, the way to solve:

http://xdaforums.com/showpost.php?p=13834882&postcount=1

2. - Unpack the archive in your home directory, which is desirable in any folder you created previously, for example util

View attachment 2357220

3. - Extract to the same folder from the downloaded firmware zip or in other formats, depending on where you get it. Prior to the status of individual images as below:

View attachment 2357223

4. - Go to the folder in the terminal:

cd utils

We carry out the same in the terminal

ext4_utils/simg2img ./system.img ./system.raw.img

mkdir system

sudo mount -t ext4 -o loop system.raw.img system

Here, the terminal will be prompted to enter your administrator password, enter.

View attachment 2357235

Here's what happened in the folder utils

View attachment 2357236

5. - All our image system.img safely disassembled and placed in a folder for editing system (DO NOT close the terminal after these teams, if something else is needed to perform open another copy of the terminal) Next, go to the folder under administrator privileges (as root) and make the necessary changes. I've been using for these purposes Krusader, it is possible and usual file manager (as root)

For example:

sudo nautilus

But it more difficult to edit the permissions on files of modified, shorter than an amateur))

6. - After making the changes need to raise the image back to this continuing in the same place at the terminal where they made the disassembly:

ext4_utils/ext2simg -v system.raw.img system_new.img

Wait for the end of the process, and then:

ext4_utils/sgs4ext4fs --bloat system_new.img notesystem.img

Wait for the end of the process, and then:

chmod 0644 notesystem.img

View attachment 2357254

7. - All our way safely assembled and ready after a subsequent packaging tar.md5 for flashing. Before packing firmware tar.md5 change the name of the new image notesystem.img on system.img simple renaming. Everything! Can clean the folder for the following assemblies, and unmount the mounted folder system

sudo umount system

View attachment 2357256

Automated build process and edit images​

----------------------------------​

--------------------​

------------​

V

View attachment 2431367​

Special Thanks

Chainfire

A.S._id