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

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:
Code:
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
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ raring partner"
sudo apt-get update
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-jdk7-installer
Code:
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 ext4_utils.zip
On versions of UBUNTU 13.04 and above may experience problems when you use these binaries, the way to solve:
http://forum.xda-developers.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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
4. - Go to the folder in the terminal:
Code:
cd utils
We carry out the same in the terminal
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
Here, the terminal will be prompted to enter your administrator password, enter.
Here's what happened in the folder utils
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:
Code:
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:
Code:
ext4_utils/ext2simg -v system.raw.img system_new.img
Wait for the end of the process, and then:
Code:
ext4_utils/sgs4ext4fs --bloat system_new.img notesystem.img
Wait for the end of the process, and then:
Code:
chmod 0644 notesystem.img
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
Code:
sudo umount system
Automated build process and edit images​ ----------------------------------​ --------------------​ ------------​ V
View attachment 2431367​
Special Thanks
Chainfire
A.S._id

---

Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app

---

danieljamie said:
Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Many of the other image format.

---

alexyuh said:
Many of the other image format.
Click to expand...
Click to collapse
help image I9505 Android 4.3
Help me the format image system.img.ext4, the working as above way and the result ODIN flash failed

---

thinh182009 said:
help image I9505 Android 4.3
But flash odin fail
Click to expand...
Click to collapse
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)

---

alexyuh said:
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
Click to expand...
Click to collapse
Thank you for this tutorial. I did successfully I9500 version 4.3. You are asked to do all Note3 are successfully using this method. Thank you very much

---

Please SP all Qualcomm Snapdragon & Exynos 5 Octa
Thank you very much

---

Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l

---

alexyuh said:
Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l
Click to expand...
Click to collapse
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 512000 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p
su-mksh: cd: /dev/block/platform/msm_sdcc.1/by-name/dev/block/platform/msm_sdcc.1/by-name: No such file or directory
2|[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 1970-04-05 13:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-05 13:01 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-05 13:01 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-05 13:01 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-05 13:01 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-05 13:01 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-05 13:01 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-05 13:01 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-05 13:01 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-05 13:01 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-05 13:01 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-05 13:01 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-05 13:01 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-05 13:01 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-05 13:01 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-05 13:01 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-05 13:01 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-05 13:01 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-05 13:01 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-05 13:01 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-05 13:01 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-05 13:01 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-05 13:01 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-05 13:01 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-05 13:01 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-05 13:01 userdata -> /dev/block/mmcblk0p29
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Please Slution. Thanks you very much:good:
---------- Post added at 11:29 AM ---------- Previous post was at 11:01 AM ----------
I was dumb to succeed, but I want you to open and close a tutorial of the original file system

---

You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app

---

alexyuh said:
You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hi alexyuh! Requirements of thinh182009 want your phone to run guide build Qualcomm Snapdragon chip by means of
which you have given above.
Please guide thinh182009. I trust you to do this Thank you very much.

---

FAQ
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:

---

To build on Snap:
http://forum.xda-developers.com/showpost.php?p=46906278&postcount=1
In one of the points have been a topic change:
4 -> After unpacking the firmware from zip -> Change the name on system.img.ext system.img, simply renaming the image.
Code:
mv system.img.ext system.img
And mount as indicated:
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
6-> Assembly:
Code:
sudo ./make_ext4fs -s -l 2894069760B -a system system_new.img system
Code:
sudo chown 1000.1000 system_new.img
Code:
rm -f system.img
Code:
mv system_new.img system.img.ext
Code:
sudo umount system
Code:
rm -r system
Code:
rm *.raw.img
Pack into the firmware tar.md5
To assemble the need to add this folder ext4_utils binary.
View attachment make_ext4fs.zip <-- Unpack the zip of a folder and add ext4_utils

---

alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thanks you very much
very professional:good:

---

alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.

---

[/COLOR]
linhbs said:
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.
Click to expand...
Click to collapse
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...

---

A.S._id said:
[/COLOR]
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...
Click to expand...
Click to collapse
Thank you. You can create makefile from https://android.googlesource.com/platform/system/extras/+/refs/heads/master/ext4_utils/ help me.
I want to get Make_ext4fs. If you create make_ext4fs help me. I believe you do this. Thank you very much.

---

Automated build process and edit images​ ----------------------------------​ --------------------​ ------------​ V
View attachment 2431377​

---

ext4_utils_4.3
1- Download folder on your computer and unzip
2- Open the folder ext4_utils in the terminal
3- Execute the command
Code:
make
4-Enjoy :laugh:
https://mega.co.nz/#!DwIjyRTY!a9Ega2UnJwDg_E__QV0GVSXqWVUl9IudzdsvNUkTGDU

---

dell