Full 1080p Modded Kit Kat 4.4.2 RK3066 ROM

[bgm]

Nice ROM, using a MK819 perfectly~! only bootlooping logo with 2A5v supply that really delivers 1.7A 5.2v Also cannot enable ART, the system will stay in black screen after initial logo, without bootanimation.

[Reliang]

I have install the rom and everything is working perfect except the ethernet is not connected. I am using the Asix AX88178 usb to ethernet. When try to turn on the ethernet I found the Mac address is zero. Can anyone please help. I am using the original imito mx1.

[markust]

I installed the ROM on an original MK808 (non-B version). I am aware that wifi will not work, but that´s OK.

The problem is, that after booting I am getting a flashing Android screen instead of the homescreen, see attachment. It´s been flashing like every 1-2 seconds for 40 minutes now, so now visible progress. The only thing I can do from there is go into "recent apps", which is of course empty. Before the booting seemed fine.

I tried a differend power supply ("tizi Tankstelle, 4.2A), no difference.

What´s wrong here?

[markust]

Hi Avion, thank you for your work, this rom is really the best and fastest ever tried for my mk808 (not b). I am using it with the overclocked shomari kernel [COLOR=#333333]1608 / 400 / 600 and i can reach 16.300 points with antutu. ....

I also tried now the shomari kernel, as gurzo82 seems to have success with it - not with my original MK808. Same flashing screen as before.

[markust]

Next attempt: I flashed the latest RikoMagic RKM MK802IIIS8G(B) FW_141230 (http://www.rikomagic.com/en/download/download_42_1.html). This ROM works on my MK808 (non-B), but it is only 720p. So I then flashed your 1080p OC kernel ([1080p][1608][400][600]). The AndroidTool reports success, but the resolution stays at 720p (checked with "screen tester" app).

I found one hint and tried to change "ro.sf.lcd_density=160" to "ro.sf.lcd_density=240" in build.prop. This was obviously not successful, as the ROM is not rooted and Kingo Root failed to root it.
BTW, one bug that has been reported already for many of the KitKat ROMs is also still in the RikoMagic ROM: The screen scaling is not saved, i.e. after each power cycle the screen scale setting goes back to default. Does anybody know where the default setting is stored? Is this also a setting that could be patched in build.prop?

How do I make the RikoMagic ROM 1080P OC?

Lots of questions...

So seems I am stuck with my old MK808 (non-B), any ideas?

[Shomari]

Help overclock kernel [1608][400][600]

http://rghost.net/7MCsv4ycn

... I'm going to try and fulfill some of the requests in this thread, as well as release an updated ROM/kernels for this RK3066 chipset in the next week or so.

[markust]

... I'm going to try and fulfill some of the requests in this thread, as well as release an updated ROM/kernels for this RK3066 chipset in the next week or so.

Any idea why this ROM got stuck in endless install screen on my MK808 - see photos above? Would be great to get it run, and the screen scaling not being saved is very annoying - would be great to fix this or put the default screen scaling to maximum. For every newer TV it should be maximum to fit exactly into the screen, I don´t know why Android default is still smaller...

[pauldemon]

Valid link for SMSC 8720a kernel. Please!

[Shomari]

Any idea why this ROM got stuck in endless install screen on my MK808 - see photos above? Would be great to get it run, and the screen scaling not being saved is very annoying - would be great to fix this or put the default screen scaling to maximum. For every newer TV it should be maximum to fit exactly into the screen, I don´t know why Android default is still smaller...

... the ROM I'm testing is much newer and doesn't have the scaling problem, at least on the four TV sets I connected to my specific device. It may work for you but I can't guarantee anything at this point as far as compatibility goes.

[quintar]

I've installed this rom and everything seems to be working great. But I did notice that the stick would lock up after being idle for a couple of hours and it'd get really warm. I checked the CPU stats and kworker/u:1 is constantly using ~50% of the cpu. I tried tracking down what is running through that kworker but I can't figure it out. I did a wipe and re-install to make sure it wasn't from an app and it still does it. I turned off WiFi and everything else I could think of and it won't go away. I don't understand why kworker would be running anyway, android doesn't use ACPI?? Any thoughts?

[No_WaY]

hello,
I have a problem with this rom on reboot device not reboot and system not coming up

[markust]

... the ROM I'm testing is much newer and doesn't have the scaling problem, at least on the four TV sets I connected to my specific device. It may work for you but I can't guarantee anything at this point as far as compatibility goes.

Sounds great - anything available yet to try?

I am using now Dumondes ROM for CX803 for the time being (http://freaktab.com/forum/tv-player-...ed-kernel1080p) - works really well on my MK808, but unfortunately no overclocking.

[Wriggerz]

Avion,

I think you're going to be my saviour.

I've been looking for a way to add driver support to a kernel and the ROM im currently running, which i like, i cant seem to find the kernel source for.

I'm going to flash your ROM tonight and then use the source files you kindly linked to to add USB wifi support for the Ralink 5372. Not something i've done before so i wanted to ask, which compiler do i need to use?

Does it matter? I expect it does otherwise there wouldnt be as many versions.

Also, is there a CWM flashable versions of your rom? I broke my OTG port.....

Thanks

[Wriggerz]

Well, personally I'm using arm-linux-gnueabi-4.7. I think you are missing the rkutils package, after compiling the kernel you must crc it with rkcrc.
f you don't have those utils here is the git :

git clone --depth 1 https://github.com/naobsd/rkutils

Compile them and you are set to go, after compiling the kernel you can do something like this:

../rkutils/rkcrc -k arch/arm/boot/Image ../kernel-`date +"%m_%d_%Y"`.img

(change the path to rkcrc, thisi will append date string to kernel filename)

PS. first try to build / run kernel without any modification, after you confirm it's working you should continue to add drivers etc. Be careful that the kernel doesn't grow over the kernel partition size

Nevermind, found the answer on the previous page. Woohoo! Now to get stuck in!

[Wriggerz]

Sorry, still would like to know if there is a recovery flashable version of your ROM bud?

Thanks