Kit Kat 4.4.2 RK3066 (Fully Working)

[Shomari]

Re: Kit Kat 4.4.2 RK3066 (Fully Working)

From the specs of my device i've figured out that the original is 5V 2A, the guy who sold me this should've been using a spare one (5V 1A).

At my little town the only supply i've found has 5.1V 2.1A (I think is an iPad spare charger) and i was kind of worried about that 0.1 extra Volt, but the i've read this at some other forum:



So, i'll try this one and give you my feedback, still after using the new tool and erase flash before upgrade the stick became a little more stable.

After root, i can't manage to log at play store, that's weird, i think it must be location issue, so i'll try the FusedLocation.apk

Well... Later i'll give my comments.

By the way, i've couldn't manage to get debugging options, to get them you should go to: Settins->About Device and click 7 times on Build number and there you go...

Thanks for the feedback you'll probably be fine with a 2.1a charger at least with the stock kernel. Good luck!

[gatorojo]

Power Supply

Just the kernel: http://ge.tt/6PbspOn1/v/0?c

Good luck and please report back. I still think it's power supply issues in your case but you never know, you're close.

From the specs of my device i've figured out that the original is 5V 2A, the guy who sold me this should've been using a spare one (5V 1A).

At my little town the only supply i've found has 5.1V 2.1A (I think is an iPad spare charger) and i was kind of worried about that 0.1 extra Volt, but the i've read this at some other forum:

USB 1 and 2 spec is 5v +- 5% which is 4.75 to 5.25v, so 5.1v is with USB specification.

So, i'll try this one and give you my feedback, still after using the new tool and erase flash before upgrade the stick became a little more stable.

After root, i can't manage to log at play store, that's weird, i think it must be location issue, so i'll try the FusedLocation.apk

Well... Later i'll give my comments.

By the way, i've couldn't manage to get debugging options, to get them you should go to: Settins->About Device and click 7 times on Build number and there you go...

[Shomari]

Thank you. I'm gonna try the Ugoos 4.4.2 ROM + kernel from this ROM to see if everything will work. Will report back.

This ROM is better overall but the other has transparent bars as the low ram flag is not enforced in the build properties as it is in this one. I think location services might be enabled in the other one without modding as well.

[optimummind]

Just the kernel: http://ge.tt/6PbspOn1/v/0?c

Good luck and please report back. I still think it's power supply issues in your case but you never know, you're close.

Thank you. I'm gonna try the Ugoos 4.4.2 ROM + kernel from this ROM to see if everything will work. Will report back.

[HaLLoWeD]

Be sure to utilize an adequate power supply, especially if the device is hanging during reboot.

After seeing posts about boot loops, I tested a stock 1.5a power supply and the device hung on reboot. My 3.5a power supply has never caused my device to freeze/lock up or reboot, even through testing and regular use of my OC kernel.

I'll buy another one tomorrow, seems like a power issue to me too. Below saved my night for tonight Thanks again

To solve the issue, always resume device from standby before powering on TV. Turn device on, then turn TV on.

[Shomari]

Just solved the prb. Somehow previously working drivers didnt worked and i've used PLT-7035 ADB Drivers after enabling USB Debug. Many thanks for your help

I really appreciate your help, it was hanging after a restart and never resumed. Have to power off / on again and again wasnt aware of such a bug. I faced such an audio issue and enabled passthrough only was working fine. Now just a blank screen, Wish i had read a few mins before Will try to recover now

Be sure to utilize an adequate power supply, especially if the device is hanging during reboot.

After seeing posts about boot loops, I tested a stock 1.5a power supply and the device hung on reboot. My 3.5a power supply has never caused my device to freeze/lock up or reboot, even through testing and regular use of my OC kernel.

[HaLLoWeD]

This ROM carries with it a minor HDMI audio bug persistent in KitKat update.

HDMI doesn't send audio to the TV when device is resumed from standby.

To solve the issue, always resume device from standby before powering on TV. Turn device on, then turn TV on.

The audio issue is caused by Rockchip's KitKat audio kernel configuration. The device expects a specific response from the HDMI sink, if it isn't found it effectively mutes the HDMI audio engine by treating the device as a DVI interface. 'rk30-hdmi: warning: EDID error, assume sink as DVI'

I really appreciate your help, it was hanging after a restart and never resumed. Have to power off / on again and again wasnt aware of such a bug. I faced such an audio issue and enabled passthrough only was working fine. Now just a blank screen, Wish i had read a few mins before Will try to recover now

[Shomari]

Just solved the prb. Somehow previously working drivers didnt worked and i've used PLT-7035 ADB Drivers after enabling USB Debug. Many thanks for your help

Excellent! Enjoy.

[HaLLoWeD]

Just solved the prb. Somehow previously working drivers didnt worked and i've used PLT-7035 ADB Drivers after enabling USB Debug. Many thanks for your help

[Shomari]

Rockchip HDMI audio issue

This ROM carries with it a minor HDMI audio bug persistent in KitKat update.

HDMI doesn't send audio to the TV when device is resumed from standby.

To solve the issue, always resume device from standby before powering on TV. Turn device on, then turn TV on.

The audio issue is caused by Rockchip's KitKat audio kernel configuration. The device expects a specific response from the HDMI sink, if it isn't found it effectively mutes the HDMI audio by treating the device as a DVI interface. 'rk30-hdmi: warning: EDID error, assume sink as DVI'

[HaLLoWeD]

Please ensure you have enabled 'connect to pc' in settings>USB. (settings left hand panel)

I enabled connect to PC, it shows connecting but fails.

When i enable "USB debugging" as advised i get a new unknown driver message.

[Shomari]

I'm trying to root my iMitoMX1, KingoRoot doesn't recognize the device at all. Tried with different laptops even native windows installed both x32&x64 but no luck. Asked me to enable developer options, once i enable system was unable to identify "rk3066" driver. I've tried to install rockusb driver but failed.
Any ideas ?

Please ensure you have enabled 'connect to pc' in settings>USB. (settings left hand panel)

[HaLLoWeD]

Towel root failed. KingoRoot worked; first select unroot, the rom shows rooted by default. Then run again and select ROOT. OP updated with OC kernel and CWM info.

I'm trying to root my iMitoMX1, KingoRoot doesn't recognize the device at all. Tried with different laptops even native windows installed both x32&x64 but no luck. Asked me to enable developer options, once i enable system was unable to identify "rk3066" driver. I've tried to install rockusb driver but failed.
Any ideas ?

[inflock]

Ynt: Kit Kat 4.4.2 RK3066 (Fully Working)

thats why i hardbricked my device in my last attempt. I recovered after I entered mask mode by doing short circuit 8-9 pin's of nand flash chip. Anyway hope to hear good news about KK.

GT-N7000...

[Shomari]

Enable Location Services

download this file http://ge.tt/5CaW6Pn1/v/0?c and either adb push to /system/app or use a file explorer like Root Explorer to put the app in /system/app and reboot. Please report back if that enables location services on your device.

Brilliant, working now! Well done mate, on the quick settings (Upper right hand corner swipe down), I left mouse clicked down on the location icon for 3 seconds and it switched on. I ran fix permissions too and rebooted then was asked on startup to allow google access to location services. All working great, thanks alot. Google earth working perfectly.

For anyone else, to change permissions manually on fusedlocation.apk, enable root explorer under tools in ES explorer, select FusedLocation.apk under /system/app and press more icon (bottom right hand side in ES), then select properties and next to permissions select change and tick Owner-Read and Write, Group-Read, Other-Read only. You should end up with rw- r- r- on previous screen. Switch off root explorer once you've made the changes and reboot.

||