Compile the Android-4.3.1_r source code and swipe to your own Galaxy Nexus I9250 on the real machine

Compile the Android-4.3.1_r source code and swipe to your own Galaxy Nexus I9250 on the real machineRain Date: 2014-04-30
The purpose of compiling the source code is to change the source code, and then can be executed on the corresponding cell phone, only this makes sense. I have a Samsung Galaxy Nexus I9250 on hand, codenamed Maguro. But at the moment Google's official does not provide the corresponding hardware driver for the android4.4.2 version number, the latest is only available to Android4.3, details can be https://developers.google.com/android/nexus/ Drivers see here. I see on the internet based on the 4.4 source code +4.3 driver compilation success and can execute, but I tried, very many errors have not been resolved until now (already in 2014-5-4), so first tried the 4.3 source code +4.3 driver. Here's the whole process:
Note: For details on compiling environment settings, etc. my previous article < based on Ubuntu 14.04 Lts compiled Android4.4.2 source; First step: Get the source code for ANDROID-4.3.1_R1

$mkdir ANDROID-4.3.1_R1$CD Android-4.3.1_r1$repo init-u https://android.googlesource.com/platform/manifest-b Android-4.3.1_r1$repo Sync

Step Two: Compile the ANDROID-4.3.1_R1 source code

[email protected]:~/devenv/android-4.3.1_r1$. Build/envsetup.shincluding device/asus/deb/vendorsetup.shincluding device/asus/flo/vendorsetup.shincluding Device /asus/tilapia/vendorsetup.shincluding device/generic/armv7-a-neon/vendorsetup.shincluding device/generic/mips/ Vendorsetup.shincluding device/generic/x86/vendorsetup.shincluding device/lge/mako/vendorsetup.shincluding Device /samsung/maguro/vendorsetup.shincluding device/samsung/manta/vendorsetup.shincluding Device/samsung_slsi/arndale /vendorsetup.shincluding device/samsung/toroplus/vendorsetup.shincluding device/samsung/toro/ Vendorsetup.shincluding device/ti/panda/vendorsetup.shincluding sdk/bash_completion/adb.bash[email  protected]:~/devenv/android-4.3.1_r1$ Lunchyou ' re Building on linuxlunch menu ... pick a combo:1 2. Aosp_x86-eng 3. Aosp_mips-eng 4. Vbox_x86-eng 5. Aosp_deb-userdebug 6. Aosp_flo-userdebug 7. Full_tilapia-userdebug 8. Mini_armv7a_neon-userdebug 9. Mini_mips-userdebug 10. Mini_x86-userdebug 11. Full_mako-userdebug 12. Full_maguro-userdebug 13. Full_manta-userdebug 14. Full_arndale-userdebug 15. Full_toroplus-userdebug 16. Full_toro-userdebug 17. Full_panda-userdebugwhich would? [Aosp_arm-eng] 12============================================platform_version_codename=relplatform_version= 4.3.1target_product=full_magurotarget_build_variant=userdebugtarget_build_type=releasetarget_build_apps=target _arch=armtarget_arch_variant=armv7-a-neontarget_cpu_variant=cortex-a9host_arch=x86host_os=linuxhost_os_extra= linux-3.13.0-24-generic-x86_64-with-ubuntu-14.04-trustyhost_build_type=releasebuild_id=jls36iout_dir=out====== ======================================[email protected]:~/devenv/android-4.3.1_r1$ Make-j4

Note 1: If this step directly to the brush machine, will appear prompt flash success, but after the restart of Google's logo after the black screen, unable to start. The reason is because the driver does not add in, must complete the third step after the start of the brush machine. Note 2: Errors such as the following may occur during the compilation process:

Can ' t locate switch.pm in @INC (if you are need to install the Switch module) (@INC contains:/ETC/PERL/USR/LOCAL/LIB/PERL/5 .18.2/usr/local/share/perl/5.18.2/usr/lib/perl5/usr/share/perl5/usr/lib/perl/5.18/usr/share/perl/5.18/usr/ Local/lib/site_perl.) At external/webkit/source/webcore/make-hash-tools.pl Line 23.BEGIN failed--compilation aborted at external/webkit/ source/webcore/make-hash-tools.pl Line 23.

The workaround:

$sudo Apt-get Install Libswitch-perl

Step Three: Download the official driver for i9250 (Maguro) and compile it again(1) Download driver: Enter the Https://developers.google.com/android/nexus/drivers#magurojwr66y, the Wi-Fi and other 6 drivers once downloaded, and then extracted, will generate 6. sh files. Put these files in the root folder of the source code can be. (2) Run the. sh file extraction driver: By running "chmod +x *.sh" To add the operational permissions for them, then run the 6 sh files sequentially, each file will let you enter "I accept" to accept the agreement. After acceptance, the extracted driver is placed in a folder named vendor. At this point, the vendor folder should be located under the root folder of the source code, under ANDROID-4.3.1_R1. Then run it again, for example, the following command compiles again, and the compilation time is shorter.

$. Build/envsetup.sh$lunch 12$make-j4

The fourth step is to brush the compiled img onto the i9250 phone.(1) Change the environment variable in ~/.BASHRC android_product_out to:

Export Android_product_out=/home/dennis/devenv/android-4.3.1_r1/out/target/product/maguro

(2) Go to the command line again and start the brush machine

$ adb reboot bootloader$ FastBoot flashall-w

After brushing, the system will voluntarily restart itself, assuming that there are no other problems, you can see the results of your labor!
Rainwater Reprint Please specify source: http://blog.csdn.net/gobitan/article/details/24792589 References :1. http://blog.csdn.net/gobitan/article/details/24367439 based on Ubuntu 14.04 LTS compiled Android4.4.2 source code 2. http://blog.csdn.net/zjmdp/article/details/7737802 Android 4.1 (Jelly Bean) source code compilation Process Summary

Compile the Android-4.3.1_r source code and swipe to your own Galaxy Nexus I9250 on the real machine