[T-Mobile Samsung Galaxy S II SGH-T989] Cl3Kener:
Hey Everyone,

I'm by no means a pro at kernel building but I've put lots of effort into these kernels so I thought I'd share them with you. The Uber kernel will always be updated to the latest Kernel version and will be overclocked to 1890 MHz or 1998 GHz (2 GHz) you decide which option you are willing to do. Unlike some of the other T-mobile Galaxy S II Hercules developers out there, I actually have a Galaxy S II and plan on having it until Summer 2014. This means that EVERY KERNEL I POST HAS BEEN TESTED AND IS WORKING although it might not be perfect (few things in life ever are).

Even though I don't post anything unless it works I still don't want to be liable for user errors. In other words, if you flash one of these Kernels your warranty is void and I AM NOT RESPONSIBLE for any data loss or bricked devices etc.
​

A Clean install is ALWAYS recommended. That does not necessarily mean you can't install these kernels on you current build it just means that you might have problems if you do. Recently apps have been getting corrupted for whatever reason whether on Stock or AOSP and in most cases they cause RRs and SODs. If you find yourself in one of those situations a clean install is the easiest fix. If you want to try and save you apps then connect to you phone while in recovery using adb. Then type adb shell. Now once you are in that shell you can run this command to fix your apps "e2fsck -yfDC0 /dev/block/mmcblk0p25" it could take anywhere from a few minutes to an hour depending on the state of your apps.

​

[AOSP 4.4.x UBER KERNEL LINK]

UBER 4.1 - 1.89 GHz RELEASE for AOSP 4.4 KitKat

UBER 4.1 - 2 GHz RELEASE for AOSP 4.4 KitKat​

​

All old Kernels can be found on Dev Host via this link (be careful you read file names and descriptions carefully if you choose to take a peek around) http://d-h.st/users/Cl3Kener/
​

Installation Instructions

**** IMPORTANT!!! USE TWRP 2.6.1.0+ for 4.4 kernels!!! Failure to do so may result in bootloops due to changes made to TWRP to accommodate SELinux in 4.4 ROMs (Links include flashable TWRP installation zips credits to meekrawb. Just flash them in your current recovery! :D) ****

1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)

2. Reboot into recovery (MAKE SURE YOU USE THE RIGHT ONE!!! (See red print above))

3. Flash Kernel Zip

4. Reboot and let Settle for ~10 minutes

5. Install Trickster MOD from the App Store for access to all of the options.

6. Change the settings to something other than INTERACTIVE (Especially if you run it with BFQ it will give you the worst screen lag ever). Then enable "Set at Boot" and push the check mark button at the top right hand portion of the screen or else you will lose your configurations.

7. Enjoy!!! :)

​

Error Reporting

I am always open to hearing about your errors although just telling me something went wrong without giving me details does me absolutely no good. So here are my expectations if you do want to complain about something not working:

1. Please list the ROM you are using,

2. The IO scheduler you were using

3. The CPU governor you were using

4. The CPU frequency range (192/1080 etc)

5. What you have done to attempt to fix it.

6. If you were able to simulate it again using the same settings.

7. Anything else you think is applicable to the issue

I would also hope that you would consider trying some of the following things to fix your issue before you ever report it because most of these things will fix the problem without me even having to change a thing.

1) Fix file permissions using a program that does a thorough job. I recommend using the fix file permissions in ROM manager because it is the best I’ve seen. For the record, I don’t actually use ROM manager for anything other than fixing permissions. Please consider trying this first because it tends to fix most of the FC/RR/SOD errors you might have.

2) Make a backup and install a clean version of the ROM you are running and see if you are still experiencing those same errors. You may have corrupted files if you’ve been dirty flashing.

3) If that doesn’t solve it, redownload and reflash, maybe something got corrupted but it still managed to flash. This happens sometimes and I can cause you grief.

4) For advanced users pull a logcat. I know not everyone knows how to do this but you can learn if you check out this OP or other ones like it

SPECIAL THANKS TO:

Android88 - because he is awesome and encouraged me to create this thread!

Samsung - for the source code to build these Kernel (and for making the phone)

Ayysir - for his wonderful tutorial on making a bash script to build kernels and for helping me out all of the time with everything!

Elbermu - For Bringing Thermal and Sweep2Wake to Hercules and for the help!

Bmg002 - For his extensive work fixing/rewriting my init.d scripts

Gruntparty - For completely redoing/fixing the build.prop injector I use for my AOSP Kernels

I Am The Frost - For being my first and best tester on xda. He's debugged several issues in these kernels for me

UBER Kernel Repositories can be found at https://github.com/Cl3Kener/HERC-KERNELS and are properly labeled for your convenience (see the branches)

Informational Links

Here is a fantastic guide on "Innards" of Kernels

Optimizing Linaro Keychains

Building a Bash Script to make Kernels​

JOIN MY GOOGLE COMMUNITY IF YOU WANT INSTANT UPDATES ON ANY OF ANDROID STUFF I DO. ​

​

Reserved!

XDA:DevDB Information

[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4, a Kernel for the T-Mobile Samsung Galaxy S II

Contributors

Cl3Kener

Kernel Special Features:

Version Information

Status: Beta

Created 2013-12-02

Last Updated 2014-01-30