First of all, the original system can only be brushed into the Nexus series of mobile phones, such as Xiaomi, Huawei and so on do not think, I was to borrow a NEXUS4 classmate,
First connect the phone with a USB computer, you can use the ADB devices to see if the connection is successful, which to open the phone debugging mode, otherwise it will show offline
The first problem is to use the ADB and fastboot, I do not know where, on the online revenue how to install ADB and fastboot, in fact, do not install, in Out/hosts/libux-x86/bin below is a variety of tools, This includes ADB and fastboot, so you can run ADB directly into this folder, or add environment variables
The second problem is running FastBoot flashall-w hint that there is no product_out environment variable, this means that the environment variable is located in the address of the search system.img and so must be set this environment variable, the hint also said can use the-p parameter, This is not a good use, it is recommended not to use, and, run fastboot can not use sudo, so always hint that there is no environment variable
The third problem is that after the brush has been stuck in the Google interface, the reason is not the driver when compiling, this guy's blog is next to the previous write http://blog.csdn.net/gobitan/article/details/24792589 Said how to install the driver. Just do it.
The fourth problem is that the phone can not start after the direct press of the power button and down the volume key into the FastBoot, when connected to the computer, the computer can control the phone.
The fifth problem is that I first brush a few run FastBoot flashall-w after the hint that I can not find boot.img this is because I run the compiler before the lunch selection is 1 compiled only to run on the emulator, to run on the real machine, to select the 9th, This will produce boot.img.
Problems with the IMG image being brushed into the phone after Android compilation is successful