When a android.mk file is modified and it is found that a module should be compiled separately, we will have to choose a long, full-length series.
Pre-Complete preparation: It is best to remove the project's out directory, although it will be slower to compile. But the advantage is that the changes will take effect.
After updating the code to modify the ANDROID.MK, use MAKE-J32 for the full compilation. (We can also use the Req 41699 New button when our company is fully ROCK3 project)
After a few hours of compiling, you will be able to see the newly generated. img file in the OUT/TARGET/PRODUCT/MSM8916_32 directory, including the boot.img system.img userdata.img recovery.img file.
To enter the FastBoot state when powered on:
sudo adb reboot bootloader
View FastBoot Devices:
sudo fastboot devices
Erase Boot System userdata recovery
sudo fastboot erase Boot/system/userdata/recovery
Burn the boot system userdata recovery in the MSM8916_32 directory
sudo fastboot flash boot/system/userdata/recovery boot.img/system.img/userdata.img/recovery.img
Restart
sudo fastboot reboot
Wait.
Of course boot system userdata Recovery can also be burned separately
Introduction to Boot.img system.img userdata.img recovery.img:
BOOT.IMG contains the kernel and memory data, the kernel is a bit like the engine of the car, the memory data is a bit like booting boot, after the boot to tell the software what to do, such as screen driver to display the second screen animation, welcome interface, desktop, etc. sound drive to prepare the power on the sound and so on.
System.img is an image (image) file that holds system files in the Android system, and the file format is yaff2.
RECOVERY.IMG is the mirror of the system backup, and Ghost uses the *. Gho file is a meaning.
USERDATA.IMG User Data
Use FastBoot to burn Android system version
