CM11 for A/S8 (in-progress)

[Deadphyre]

I just decided to grab all the nand's into a respective img.

[AManofFewWords]

I've successfully compiled a new zImage (turned out to have a uImage AND a zImage) and repacked it into a boot.img. I've also added all the new modules into the vendor/modules in system. Will flash when I get a chance.

New kernel runs 3.4.75, compared to our old 3.3.0.

[AManofFewWords]

Kernel does not boot. Will stay with 3.3.0. I think it's because of the PhoenixSuit, we most likely need a CWM.

[AManofFewWords]

Well, just had a mind breakthrough. SELinux isn't even enabled in our kernel. I'll see what I can do.

(Note: SELinux is required in Android 4.4.)

[Deadphyre]

Wonder why it's not enable. What would it take, as far code goes, to get it enable?

[AManofFewWords]

Kernel recompile with it enabled.

I've actually compiled a TWRP 2.6.3.0 that can flash KitKat. But it needs a new kernel for it to work, in more detail, one with SELinux enabled. I encounter errors with compiling a kernel with CM, but works fine alone. I think it's the toolchain.

[guessyet]

Kernel recompile with it enabled.

I've actually compiled a TWRP 2.6.3.0 that can flash KitKat. But it needs a new kernel for it to work, in more detail, one with SELinux enabled. I encounter errors with compiling a kernel with CM, but works fine alone. I think it's the toolchain.

you could compile the kernel seperate.. however, make sure your environment is configured properly.. the $PATH and such.. Also, make sure you enable the required options for android in your defconfig.. Always merge the base and recommended configs for android over top of the hardware defconfig for your device..

Good luck..

[guessyet]

Well I installed it using PhoenixSuit, which I'm afraid is likely the reason. I've searched on Google anywhere, this doesn't seem like a very spread-out problem.

TWRP 2.6.3.0 doesn't work for KitKat sadly, we need a CWM 6.0.4.3+.

Addition: I'm also using stock kernel, which could be a reason.

remember that phoenix suite wipes *ALL* partitions and re-creates them when you flash with it.

[AManofFewWords]

TWRP is having update-binary errors flashing the kernel

[Deadphyre]

Are installing through update or through the install portion? When testing out the first zip you sent I did that and after going through install it went ok of course it didn't boot but that's what trial and error are for. I'm also wondering why we can't boot directly to recovery without first booting into the os.

Sent from my SPH-L710 using Tapatalk

[AManofFewWords]

My bad I had school. I thought there was a button combination like POWER+VOL UP+VOL DOWN or something like that.

[elektrik]

My bad I had school. I thought there was a button combination like POWER+VOL UP+VOL DOWN or something like that.

there *is* a key combo like that, but that only puts it into flash mode for phoenixsuit, which isn't what he's talking about. he's talking about inside recovery (at least I think). btw, for those of you who want an app to boot into recovery, check out petrus' app. He modified it for me to work with my elektricity ROM (and therefore, all allwinner based tablets). you can download from here:http://www.freaktab.com/showthread.php?1050-Reboot-App

[guessyet]

there *is* a key combo like that, but that only puts it into flash mode for phoenixsuit, which isn't what he's talking about. he's talking about inside recovery (at least I think). btw, for those of you who want an app to boot into recovery, check out petrus' app. He modified it for me to work with my elektricity ROM (and therefore, all allwinner based tablets). you can download from here:http://www.freaktab.com/showthread.php?1050-Reboot-App

The firmware has a built in configuration for a recovery key, however, our devices do not have a *dedicated* button assigned for this purpose. Under the current configuration, it utilizes keys on a keypad. Since we have no keypad - it is of no use.. Mapping this function to the volume-up button is something that I would love to do.. It is on my todo list.. that is... if it is possible to do so..

[elektrik]

The firmware has a built in configuration for a recovery key, however, our devices do not have a *dedicated* button assigned for this purpose. Under the current configuration, it utilizes keys on a keypad. Since we have no keypad - it is of no use.. Mapping this function to the volume-up button is something that I would love to do.. It is on my todo list.. that is... if it is possible to do so..

it is possible, though I don't remember where I've seen it.

BTW, I'm making progress in building/compiling my kernel Guess, but could still use your help-feel free to hop on tomorrow if you can help... :-)

[Deadphyre]

It should very well be possible to code in a key combination to boot directly to recovery. Having the ability to put it into flash mode is nice and all but I don't want to have to boot into the OS just to get into recovery.