Android system re-brushed rom précis-writers

when it comes to a drastic makeover of Android, it should be clear to understand the composition of each image of Android to be discovering.

First of all, the files that need to be burned during the android burning process include uboot.bin\boot.img\system.img\userdata.img\recovery.img and other files.

Xiaomi's brush machine files mainly include data\meta-inf\recovery\system\blob\boot.img\file_contexts files.

There is only one folder under the Data folder Miui from the name can be found inside the file is mainly Xiaomi user interface files.

System/app The main store in this is the regular download of the application, you can see the APK format is the end of the file. Under this folder the program for the system default components, the software installed by itself will not appear here, but in the \data\ folder .

System/bin files in this directory are local programs of the system, from the Bin folder name can be seen binary binary program, which is mainly the Linux system comes with components (commands)

system/etc from the folder name, the system configuration files, such as the APN access point settings and other core configurations are saved.

system/fonts font folder, in addition to the standard font and bold, italic can see the largest file volume may be the Chinese font, or some Unicode font where the Droidsansfallback.ttf file size

system/framework The framework is primarily a core file, which can be seen as a system platform framework from the suffix name jar.

System/lib The Lib directory is primarily the system's underlying library, and some so files, such as the Platform Runtime Library
System/media/audio Ringtone Music folder, in addition to the regular ringtone, there are some system alert event tones.
system/usr user folders, including shares, keyboard layouts, time zone files, etc.

System/priv-app you can store some of the app files you've written

System/vendor Store Product related documents

bootimg files are generated by image and ramdisk.img files. There are related descriptions in the/build/core/makefile file. # The boot image, which is a collection of other images.

Internal_bootimage_args: = \

$ (Addprefix--second, $ (installed_2ndbootloader_target)) \

--kernel $ (installed_kernel_target) \

--ramdisk $ (installed_ramdisk_target)

There are specific packaging descriptions in the system/core/mkbootimg/bootimg.h.

** +-----------------+

** | Boot Header | 1 page

** +-----------------+

** | Kernel | N Pages

** +-----------------+

** | RAMDisk | M pages

** +-----------------+

** | Second Stage | o Pages

** +-----------------+

It is clear from the above that the composition of the boot.img file is mainly to package the kernel and ramdisk.img files and add the file header to complete.

If you need to modify the official Xiaomi file, you can use the

#./split_bootimg.pl boot.img

Page size:2048 (0x00000800)

Kernel size:6695672 (0X00662AF8)

Ramdisk size:1276106 (0X001378CA)

Second size:0 (0x00000000)

Board Name:

Command Line:

Writing Boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... C Omplete.

Unpack the RAMDisk file, first to create a folder for the extracted files, after entering the folder, execute the following command:

#gzip-DC. /boot.img-ramdisk.gz | Cpio-i

After making changes to the file, the boot.img file needs to be re-made.

Using the Mkbootfs tool (the Mkbootfs tool is automatically generated at ~/android-src/out/host/linux-x86/bin after compiling the Android source code) to re-create the RAMDisk, you can use the following command to operate:

#mkbootfs./ramdisk | gzip > ramdisk-new.gz

Re-creating the boot.img,mkbootimg using Mkbootimg can also be found in the ~/android-src/out/host/linux-x86/bin directory:

#mkbootimg--cmdline ' no_console_suspend=1 console=null '--kernel boot.img-kernel--ramdisk ramdisk-new.gz-o Boot-new.img

Android system re-brushed rom précis-writers