When I tried to compile my own Android ROM, I got the following error:
target Executable: skia_gm (/media/ssd/buildout//target/product/i9100/obj/EXECUTABLES/skia_gm_intermediates/LINKED/skia_gm)
target Executable: skia_test (/media/ssd/buildout//target/product/i9100/obj/EXECUTABLES/skia_test_intermediates/LINKED/skia_test)
target Executable: test-opengl-configdump (/media/ssd/buildout//target/product/i9100/obj/EXECUTABLES/test-opengl-configdump_intermediates/LINKED/test-opengl-configdump)
/bin/sh: 1: /home/ted/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: not found
make: *** [scripts/mod/empty.o] Error 127
make: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
The problem was that the arm toolchain wasn’t installed. After installing the toolchain compiling succeeded.
Installing the toolchain can be done with the following command:
git clone https://android.googlesource.com/platform/prebuilt
After that, run the following command to add the toolchain to the PATH variable:
Compiling should now succeed without the previous error.
I’ve found this information on http://source.android.com/source/building-kernels.html, a very helpful information source for Android development.
I wanted to flash a custom firmware on an HTC Desire S because I didn’t like the Sense interface HTC installed on the device. It felt sluggish and I think it was ugly.
I have unlocked the bootloader on htcdev.com, rooted the device, and installed ClockworkMod (cwm). I chose a rom that seemed usefull (in this case CyanogenMod), and copied the cwm image (.zip file) to my sd-card, and booted into recovery. Here I made a backup of the current rom, did a full wipe, and flashed the image. After this I rebooted the device, expecting to see my new rom boot.
Instead of booting, all I saw was a white screen with the letters HTC in green on an white background. This state is named bootloop.
After flashing back the original rom, the device booted without problems.
I have tried several roms, all with exacly the same problem. After a lot of online research i have finally a booting custom rom. The solution was to flash the correct boot.img file for your rom to the device with the fastboot utility. The file boot.img is in the .zip file of the rom you chose. Flashing the boot.img can be done this way:
- Boot the HTC in fastboot mode by powering on the device while holding the Volume – button, and choosing fastboot
- Connect the phone to your computer with an micro-USB cable
- Flash the boot.img you extracted from the custom firmware:
fastboot flash boot <path to boot.img>
- Reboot the phone
After these steps your HTC Desire S should boot the custom rom as expected!