Compiling SlimRoms 6.0 for the Samsung Galaxy S4, T-Mobile (JFLTETMO SGH-M919)

I’ve noticed a pattern. Other than CM13, all of my 6.0+ roms compile successfully (eventually) but fail to actually run on the device. I am really not sure why this is, so I’ve been doing some research. One of the things that seems ambiguous to me, is which version of Java to use. According to the AOSP “setting up the build environment” page, MM and LP will/should build with OpenJDK7. However, it also states that the current branch, which is still 6.0, or MM, requires OpenJDK8. So, I downloaded and installed OpenJDK8. Then I re-compiled SlimRoms 6.0. As you can see, it was still successful when building:

[CODE]
using prebuilt boot.img from BOOTABLE_IMAGES…
boot size (6846464) is 65.29% of limit (10485760)
running:  openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running:  java -Xmx2048m -jar /home/alaskalinuxuser/Documents/projects/phones/compile/slimroms6/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpOefJAw /home/alaskalinuxuser/Documents/projects/phones/compile/slimroms6/out/target/product/jfltetmo/slim_jfltetmo-ota-3e88c0e4c2.zip
done.
_______________________________________________
/                              http://www.slimroms.org |
/   _____________________________________________|
/   /
/   /  _  _       ______
/   /  | |(_)     (_____ \
/   /   | | _ _____ _____) )___  _____  ___
_____________________/   /    | || |     |  __  // _ \|     |/___)
|                        /     | || | | | | |  \ \ |_| | | | |___ |
|_______________________/       \_)_|_|_|_|_|   |_\___/|_|_|_(___/

Package Complete: /home/alaskalinuxuser/Documents/projects/phones/compile/slimroms6/out/target/product/jfltetmo/Slim-jfltetmo-6.0.1.alpha.0.1-UNOFFICIAL-20160524-1009.zip
make: Leaving directory `/home/alaskalinuxuser/Documents/projects/phones/compile/slimroms6′

#### make completed successfully (58:16 (mm:ss)) ####

[/CODE]

However, it didn’t have any affect on functionality. The build was successful, but the operational test was a fail. I am not quite sure where to go with this just yet, since there are not any build errors, but I’ll keep plugging away at it. Next on my list is changing the tool chain for the kernel from arm-eabi to linaro, but I somehow doubt that is it. Then again, I am in personally uncharted waters right now.

Linux – Keep it simple.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s