Use fastboot to build Android and fastbootandroid

Use fastboot to build Android and fastbootandroid
When you modify an Android. mk file and find that you cannot find a module that should be compiled separately, you will have to choose a long full editor.

Preparation before full compilation: it is best to delete the out directory of the project, although the compilation will be slow. But the advantage is that the modification takes effect.

After updating the Code and modifying Android. mk, you can use make-j32 to complete the compilation. (We can also use the req 41699 new button to compile the Rock3 project)

After several hours of compilation, you can see the newly generated. imgfile in the out/target/product/msm8916_32 directory, including the boot. img system. img userdata. img recovery. imgfile.

Fastboot enters the following status at startup:

Sudo adb reboot bootloader

View the fastboot device:

Sudo fastboot devices

Erase boot system userdata recovery

Sudo fastboot erase boot/system/userdata/recovery

Run the boot system userdata recovery command 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 be separately burned.

Introduction to boot. img system. img userdata. img recovery. img:

Boot. img contains kernel and memory data. The kernel is a bit like a car engine, and the memory data is similar to boot. After the boot, tell the software what to do, for example, the screen driver displays the second screen animation, welcome interface, desktop, etc. The sound Driver prepares the boot sound and so on.

System. img is an image file that stores system files in Android. The file format is yaff2.

Recovery. img is the image backed up by the system, and the *. GHO file used by the GHOST is the same.

Userdata. img user data