[KERNEL][STOCK]10.6.1.14.4 + bootloader » insecure, dpi-unlocked, pre-init scripts

[_that]

Here is the first customized kernel based on firmware 10.6.1.14.4 - Asus' release of Android 4.2.1. Since Asus have not released source code yet, the only thing we can do for now is use their zImage and modify the ramdisk.

This contains my usual ramdisk mods:

* ro.secure=0, ro.debuggable=1 and adb enabled in default.prop
* adb binary with direct root access (thx scrosler)
* dpi unlocked, must/can be set in /system/build.prop instead
* my pre-init binary that allows any ramdisk modification by a script in /system/boot

As a special this time, this package includes the new bootloader. With the old 10.4.4.x bootloader, the kernel boots but hard freezes after a minute. It also includes the new stock kernel modules which are extracted into /system/lib/modules.

In my experiments it was painless to boot older JB 4.1 kernels and recoveries with the new bootloader, and it is possible to downgrade from this bootloader to 10.4.4.25 using fastboot. I still take no responsibility if it does not work on your device, you flash everything at your own risk.

Be patient when flashing - encrypting the bootloader takes almost a full minute.

Do not flash this on any other ROM than Asus stock 10.6.1.14.4 or those derived from it - it won't work due to the new filesystem layout of Android 4.2 (unless you apply a small pre-init script that I will post later).

View attachment kernel-10.6.1.14.4-that1-with-bootloader.zip

Do not flash this if you have an ancient recovery - I used TWRP 2.4.1.

 

[_that]

(reserved)

 

[sbdags]

Stolen, I mean downloaded for CROMI 4... Cheers mate

I already made a kernel but yours is already better :good:

 

[_that]

Stolen, I mean downloaded for CROMI 4... Cheers mate

I already made a kernel but yours is already better :good:

I forgot something important in the ramdisk. Can you guess what it is?

Anyway, we should talk about /system/boot support - ideally including Hundsbuah. I'd like to see my pre-init hook in all CROMi-supporting kernels so that we have an easy place to support ramdisk mods like Data2SD, or dual-booting Android 4.1 and 4.2. What do you guys think?

 

[buhohitr]

I forgot something important in the ramdisk. Can you guess what it is?

Anyway, we should talk about /system/boot support - ideally including Hundsbuah. I'd like to see my pre-init hook in all CROMi-supporting kernels so that we have an easy place to support ramdisk mods like Data2SD, or dual-booting Android 4.1 and 4.2. What do you guys think?

Yes, I love your dual-booting and auto data2sd detection. :good:
To be honest Hunds kernel is become more complex and more like a beta testing kernel, it's not for regular users anymore. I'm back to your V6 version. Smooth and trouble free!

 

[_that]

Yes, I love your dual-booting and auto data2sd detection. :good:
To be honest Hunds kernel is become more complex and more like a beta testing kernel, it's not for regular users anymore. I'm back to your V6 version. Smooth and trouble free!

Overclocking has never been for regular users. But I can learn a lot from Hundsbuah's kernel.

Comparing when I first extracted and merged clemsyn's changes to the then-current stock kernel ("wtf am I doing here?") to what I understand now about the Tegra 3 ("ah, so pll_x provides the CPU clock"), there is some progress already.

 

[Tylorw1]

I forgot something important in the ramdisk. Can you guess what it is?

Anyway, we should talk about /system/boot support - ideally including Hundsbuah. I'd like to see my pre-init hook in all CROMi-supporting kernels so that we have an easy place to support ramdisk mods like Data2SD, or dual-booting Android 4.1 and 4.2. What do you guys think?

Wonderful idea. It would be nice also to try to make it in 1 flashable zip for newbie users. Id not, then a detailed guide on how to do so. Really looking forward to getting 4.2.1, and maybe a dualboot with 4.1.1.

Tylor

Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.7 Odex AND That's UltraCleanRom(7 sec boot )
Kernal: _That's Stock V6 Kernal
Theme: Timberwolf's Blues & Jazz Theme V2.1
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/showthread.php?t=2204100

 

[pinky059]

Seen you mention here and in the OP that 2.4.1.0 worked fine with new bootloader and kernal you posted here.

http://forum.xda-developers.com/showthread.php?t=2204100&page=8

Is it safe to try it out or am i missing something that you have on your setup that I may not have?

 

[Tylorw1]

Seen you mention here and in the OP that 2.4.1.0 worked fine with new bootloader and kernal you posted here.

http://forum.xda-developers.com/showthread.php?t=2204100&page=8

Is it safe to try it out or am i missing something that you have on your setup that I may not have?

You need to have TWRP 2.4.4,because sbdags will be releasing a patch they will know how to handle the new bootloader properly.

Tylor

 

[_that]

Seen you mention here and in the OP that 2.4.1.0 worked fine with new bootloader and kernal you posted here.

http://forum.xda-developers.com/showthread.php?t=2204100&page=8

Is it safe to try it out or am i missing something that you have on your setup that I may not have?

I had no problems with that version, but I only used the adb connection, 'install' and 'reboot'. I think it is safe in the sense that it won't brick your tablet, but I'd still advise you to wait a bit longer for sbdags' version unless you have nvflash, just to be safe.

You need to have TWRP 2.4.4,because sbdags will be releasing a patch they will know how to handle the new bootloader properly.

Let's wait and see what that patch is and if it's really needed. Maybe it's related to functionality I didn't use yet. The bootloader seems to be compatible even without any patch.

Update: The patch seems to be completely unneeded on the TF700 and unmodified TWRP works fine - read more here: http://forum.xda-developers.com/showpost.php?p=39991967&postcount=96

 

[_that]

New findings from the weekend:

While this kernel does work with CROMI 3.4 (Android 4.1) when using the proper ramdisk preinit script, I get some pauses and error messages in the kernel log when repeatedly switching between launcher and app drawer (the zoom/fade effect is not smooth).

The error message is from host1x and says something about syncpoint stuck waiting.

Apparently there is some minor incompatibility between the 4.2 kernel and the 4.1 Android GPU drivers.

 

[pinky059]

I had no problems with that version, but I only used the adb connection, 'install' and 'reboot'. I think it is safe in the sense that it won't brick your tablet, but I'd still advise you to wait a bit longer for sbdags' version unless you have nvflash, just to be safe.




Let's wait and see what that patch is and if it's really needed. Maybe it's related to functionality I didn't use yet. The bootloader seems to be compatible even without any patch.

Update: The patch seems to be completely unneeded on the TF700 and unmodified TWRP works fine - read more here: http://forum.xda-developers.com/showpost.php?p=39991967&postcount=96

Thanks....Kinda what I figured...

 

[Mike3.14159]

Quick question......just noticed in that my build number is showing WW and I know I flashed the US version of the stock rooted 4.2. So I am on WW bootloader and the US rom. Am I going to run into any compatibility problems or anything??

If so, I want to keep this kernel - love having it at 213dpi instead of 240 - so I dont see why I couldn't just flash the bootloader/twrp packege that I flashed before upgrading to 4.2(the one for US sku) without touching the kernel. Correct me if I'm wrong!

 

[_that]

Quick question......just noticed in that my build number is showing WW and I know I flashed the US version of the stock rooted 4.2. So I am on WW bootloader and the US rom.

You mean the build number showing in the bootloader, right? Because the build number in "About tablet" is from your ROM's build.prop and should therefore show "US".

Am I going to run into any compatibility problems or anything??

Extremely unlikely. I compared the bootloader binaries, and the only difference is the text that they display as build number, and of course the digital signature.

If so, I want to keep this kernel - love having it at 213dpi instead of 240 - so I dont see why I couldn't just flash the bootloader/twrp packege that I flashed before upgrading to 4.2(the one for US sku) without touching the kernel.

If you downgrade your bootloader, you can't run the 4.2 ROM. But if you want, you can of course replace the WW with the US version of 10.6.1.14.4.

 

[Mike3.14159]

You mean the build number showing in the bootloader, right? Because the build number in "About tablet" is from your ROM's build.prop and should therefore show "US".

Wowwww........downloaded the bootloader/twrp combo upgrade (which I did get the US) and the rom from sbdags while learning how to figure out the angles of a hyperbolic triangle - something I will never be of any help except for passing the class - didn't read the line stating that the rom was based off of the WW build and even though the bootloader and build number have the same digits I don't know why I associated the two as having anything to do with each other! Guess my ADD just got the best of me haha

If you downgrade your bootloader, you can't run the 4.2 ROM. But if you want, you can of course replace the WW with the US version of 10.6.1.14.4.

Just reflashed the US 10.6.1.14.4 bootloader and changed the display.id to say US so all confusion is now out of the way!!

Thanks!

 

[buhohitr]

_that, if you don't mind, can you make a zip for just the kernel with fsync support? Thanks.

 

[_that]

_that, if you don't mind, can you make a zip for just the kernel with fsync support? Thanks.

No. I will port all existing patches to the new base, not only fsync control. Actually, I already have, and the kernel currently runs on my device.

The feature I currently can't get to work is the framebuffer console - so no support for UltraCleanROM in this kernel so far.

 

[buhohitr]

No. I will port all existing patches to the new base, not only fsync control. Actually, I already have, and the kernel currently runs on my device.

The feature I currently can't get to work is the framebuffer console - so no support for UltraCleanROM in this kernel so far.

I just hit "thanks" but I also would like to say " Thank you".

 

[dasunsrule32]

So what did you patch to get around the Surface Flinger issues?

 

[_that]

So what did you patch to get around the Surface Flinger issues?

Nothing, I simply used the matching kernel source for the ROM. The SurfaceFlinger problem was only with the old (10.4.4.25-based) kernel and the new (10.6.1.14.4-based) GPU drivers.