CyanogenMod 10.2 on Samsung Galaxy S4 (Japanese DoCoMo version - jfltedcm)

Here is how I managed to get CyanogenMod on my Galaxy S4 - the Japanse DoCoMo model.



Starting back to front, the short version is:



Get the repo command, and get ready to compile CyanogenMod as usual



repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2


Prep the extra repositories needed to compile the Samsung phone model.



$ cat .repo/local_manifests/s4.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project path="device/samsung/jf-common"      name="kbc-developers/android_device_samsung_jf-common"   />
  <project path="device/samsung/jfltedcm"       name="kbc-developers/android_device_samsung_jfltedcm"    />
  <project path="device/samsung/msm8960-common" name="CyanogenMod/android_device_samsung_msm8960-common" />
  <project path="device/samsung/qcom-common"    name="CyanogenMod/android_device_samsung_qcom-common"    />
  <project path="hardware/samsung"              name="CyanogenMod/android_hardware_samsung"              />
  <project path="kernel/samsung/jf"             name="CyanogenMod/android_kernel_samsung_jf"             />
  <project path="kernel/samsung/jfdcm"          name="kbc-developers/android_kernel_samsung_jfdcm" revision="kbc-aosp-jb-mr2" />
  <project path="vendor/samsung"                name="kbc-developers/proprietary_vendor_samsung"         />
</manifest>


Note that I am using a few of the kbc-developers' repositories. These have important updates for the DoCoMo phone model.



On that note, it doesn't really matter which kernel is to be used (the jfdcm DoCoMo customized version modded by KBC, or the official jf version), but I thought I'd go go with KBC's one, since it had some updates for the NFC, and I was hoping to get the NFC working.



As I was trying to replicate the binary releases that KBC published, I also had to disable SELINUX by adding the following line to device/samsung/jfltedcm/BoardConfig.mk:



TARGET_KERNEL_SELINUX_CONFIG :=


And to actually allow the boot partition to be flashed, I had to register my phone's bootloader in device/samsung/msm8960-common/loki_bootloaders. Just append this text to the file:



# DoCoMo
bootloader=SC04EOMUAMDI
bootloader=SC04EOMUAMF1


Once all this is done, building CyanogenMod as usual worked just fine. I source the following file to do the trick, where $HOME/android/cm-10.2 is where I ran the repo init command:



export USE_CCACHE=1
export CCACHE_DIR=$HOME/android/ccache
export OUT_DIR_COMMON_BASE=$HOME/android/out
export PATH=$PATH:$HOME/android/bin
export ANDROID_JAVA_HOME=/etc/java-config-2/current-system-vm
export CM_BUILDTYPE="chutz"
cd $HOME/android/cm-10.2
. build/envsetup.sh
breakfast jfltedcm
TOP=$T


Inside $HOME/android/bin I keep a copy of the repo command itself.



External links I found useful



Comments

  1. ChipsSeptember 14, 2014 at 5:20 AM

    Hi there,

    Reading your post admittedly left me scratching my head. When I installed Cyanogenmod on my S2 in the states, I just ran the installer from the website. I'm guessing the reason for the over my head scripting here is because that is not possible with the docomo s4? I'm hoping to put Cyanogen on this phone, but I don't want to achieve alchemy of phone to brick.

    Hope my question isn't a bother.

    Cheers.

    ReplyDelete

Post a Comment

Popular posts from this blog

Installing Gentoo with full disk encryption

The purpose of this exercise - install Gentoo where all disk partitions are encrypted. Boot from a system rescue disk and partition the disk - use GPT partition table where the first partition is reserved, second is the boot, and the third one is for the rest of the data. Device Start End Sectors Size Type /dev/sda1 2048 32767 30720 15M BIOS boot /dev/sda2 32768 442367 409600 200M Linux filesystem /dev/sda3 442368 375093902 374651535 178.7G Linux filesystem Encrypt partitions number 2 and 3, and open them cryptsetup luksFormat /dev/sda2 cryptsetup luksFormat /dev/sda3 cryptsetup luksOpen /dev/sda2 crypt_boot cryptsetup luksOpen /dev/sda3 crypt_data Format the boot partition mkfs.btrfs /dev/mapper/crypt_boot Prepare LVM for the rest, and format the top level vgcreate vg0 /dev/mapper/crypt_data lvcreate -l 100%FREE -n data vg0 mkfs.btrfs /dev/vg0/data Mount and set up any subvolumes mount /dev/vg0/data /mnt/gentoo btrfs subvol create /mnt/gentoo/@ /mnt/gentoo/@home umount /mnt/gentoo Now
Read more

ADSL Router Model CT-5367 user and pass (VIVACOM)

Writing down the username and password for the vivacom ADSL router, in case I need it again. user: root pass: warmWLspot Useful to telnet 192.168.1.1 and then reboot . Originally found at Neo2SHYAlien blog . And here I found passwords for other models, just in case. ZTE ZXDSL 832 username: root password: GSrootaccess ZTE ZXDSL 831 username: root password: GSrootaccess ZTE username: root password: 831access Huawei SmartAX MT882 username: root password: MT882rootaccess ZTE ZXDSL-531b username: root password: rootWLaccess Pirelli – DRG – A124G username: root password: warmWLspot Comtrend CT-5367 username: root password: warmWLspot HG530 Home Gateway username: root password: warmWLspot
Read more

FreeIPA cluster with containers

Notes on how to install a FreeIPA cluster on Ubuntu. Mostly following the instructions on https://github.com/freeipa/freeipa-container Start with what would be the primary host. If you install a third replica you would want to review the replica agreements to ensure you have a two-way replication between all pairs of nodes.
Read more