Overclocked RK3288 kernels

[Catadarius]

Overclocked RK3288 kernels

Hi all
Overclocked kernel from ugoos team is available now

HERE

Regards

Hy Sam,

Good news. Can you tell me if this kernels works with wasser 2.0.3?

And how we can install them

[no_spam_for_me]

Hy Sam,

Good news. Can you tell me if this kernels works with wasser 2.0.3?

And how we can install them

hmmm, I think if someone would like to OC his device, he/she should know what to do (also how to configure AndroidTool using the parameter)
And I also think it's up to you to find out, if the Ugoos kernel/resource will work with wasser 2.0.3 or not

[sam_ugoos]

Hy Sam,

Good news. Can you tell me if this kernels works with wasser 2.0.3?

And how we can install them

Unfortunately i can't guarantee that it will work, need to try. Which device do you use?
If parameter file is available in your firmware and kernel not packed in boot you can try to flash kernel like this:


Just load parameter file from your firmware and choose kernel and resource from our archive. If device will not start just return resource and kernel from your firmware.

[no_spam_for_me]

BUT I don't know if wasser use the same addresses (that's why I wrote "also how to configure AndroidTool using the parameter") maybe he use the same addresses, maybe not ????

[sam_ugoos]

BUT I don't know if wasser use the same addresses (that's why I wrote "also how to configure AndroidTool using the parameter") maybe he use the same addresses, maybe not ????

Of course, thats why need to load parameter from wasser firmware.

[no_spam_for_me]

Most ROM's use the same address for boot.img and kernel.img, since it's the first partitions flashed on RK3288 devices.

Most, but maybe not all, and "the first partitions" is wrong
e.g.

0x00000000    parameter
0x00002000    uboot
0x00004000    misc
0x00006000    resource
0x0000e000    kernel
0x00016000    boot
:

:
But you must always load your ROM's parameter file to get the correct address for the partitions before you flash an overclocked kernel.

Of course, thats why need to load parameter from wasser firmware.

But if you both write "load" I'm not sure most people know what that means...

Last but not least, I don't know if wasser changed something at the "partition-table" but I know sometimes he like to cook his own soup

---

At parameter you will find a line:

CMDLINE:console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00180000@0x00092000(system),0x00002000@0x00212000(metadata),0x00400000@0x00214000(userdata),0x00020000@0x00614000(radical_update),-@0x00634000(user)

The important part is the part after mtdparts=rk29xxnand: and the structure is
length @ address (partition name)
e.g.

0x00002000@0x00002000(uboot),
0x00002000@0x00004000(misc),
0x00008000@[B]0x00006000[/B](resource),
0x00008000@[B]0x0000e000[/B](kernel),
0x00010000@[B]0x00016000[/B](boot),
0x00010000@0x00026000(recovery),
0x0001a000@0x00036000(backup),
0x00040000@0x00050000(cache),
0x00002000@0x00090000(kpanic),
0x00180000@0x00092000(system),
0x00002000@0x00212000(metadata),
0x00400000@0x00214000(userdata),
0x00020000@0x00614000(radical_update),
-@0x00634000(user)

So you can find out, if the adress-values at the RKAndroidTool are the right ones or not (if not, you have to use the address-values which you determine at the parameter)....

[scooter2014]

I get the kernel to work on the mk902ii but i cant get it to go past the 1800, ill try d33 kernel now but seems to run good on the mk902ii and makes it run alot smoother as well.

cool as a cuqumber as well

[Guest]

Can someone please tell me if this kernel can be flashed to HPH 4gb/32gb?
If it's not compatible, can I take some HPH files from my rom, and flash them altogether?
Please advice what to watch for, and if it's doable at all?
Thanks.

[tabnk]

Deleted

[tabnk]

I'm have a bluetimes TV BOX. Can I'm flash this kernel.img and resource.img to my TV BOX using dd command in a Terninal emulator ?

[tabnk]

I'm trying to extract kernel.img from my stock firmware with dd command before Flash the new kernel.

My extracted kernel.img is 16MB, is this correct size ?

You can.
Lots of things like IR Remote, LED Lights and wifi might not work.
Will also loose passthrough & fast ethernet support.

[tabnk]

Currently, my TV BOX does not load any setting from resource.img. Does this indicate my boot.img has kernel.img inside ?

Depends what size the kernel in your parameter file is.
Your kernel is probably 6MB and the other 10MB empty space, it's also backup up.
Just make sure you have no kernel inside your boot.img, otherwise the standalone kernel is not used.
Boot.img shouldn't be more than 4MB in stock ROM otherwise there is also a kernel inside.
If you backup boot.img, it's also going to show the full 16MB with empty space, so you won't know by doing that.

[tabnk]

Uploaded boot.img here http://www.filedropper.com/boot_2 (32MBytes). Thank.


Btw, I'm modified (Overclock RAM and GPU) in my resource.img but my TV box never load any setting from. Been trying for the past few days.

It has to load settings from resource.img.
Only way to tell is if you upload your boot.img, then I can check if it has a kernel inside.

[tabnk]

Another question. Can I'm just flash the kernel.img while keeping my existing resource.img ?

[Gormar]

Uploaded boot.img here http://www.filedropper.com/boot_2 (32MBytes).

With that boot.img mistery of your case is probably resolved .
It didn't occure to me that if kernel.img is inside boot partition then resource.img may have meet similar fate.

Open your boot.img file in Hex editor and search for "pd_ddr" ASCII string and you should know what do to next

As to using different resource.img and kernel.img it is rather not adviced. Success strongly depends what drivers are compiled in both kernels and in many cases it would not work.