[Q] Problems rooting Mk809IV (KitKat 4.4.2)

[leech4]

Greetings

I searched the forums but nothing related to my issue was found
I recently got an android PC stick MK809IV (Unbranded) with Kitkat 4.4.2 Rom which has Rockchip RK3188T / 1.4-1.6GHz Quad core as CPU
I managed to try at least two rooting methods (plus some hacking through adb) but failed to have proper root.

The drivers for the stick are properly installed and I get "[email protected]:/ #" while using "adb shell" and root with id command

[email protected]:/ #
id
uid=0(root) gid=0(root) context=u:r:shell:s0
[email protected]:/ #


The method TPSparkyRoot with the batch file from here (Modified to work properly) has showed confirmation that root is ok, as there was no errors during process
I checked file system in read only mode (with xPlore) : su and busybox binaries are in /system/bin, SuperSU also installed in /system/app with 644 permission and root.shell ownership but no ROOT.

The SuperOneClick method tells me that device is rooted but in fact nothing
I think it is permissions and ownership issue or an incompatible su binary (I have tried many ones, sometimes SuperSU says there is no binary, other times says it have to be updated but fails) but have not any clue on how to solve it.

This stick is driving me crazy !
Any idea is welcome

 

[jonathankonrad]

Any further direction for rooting an mk809iv device?

Greetings

I searched the forums but nothing related to my issue was found
I recently got an android PC stick MK809IV (Unbranded) with Kitkat 4.4.2 Rom which has Rockchip RK3188T / 1.4-1.6GHz Quad core as CPU
I managed to try at least two rooting methods (plus some hacking through adb) but failed to have proper root.

The drivers for the stick are properly installed and I get "[email protected]:/ #" while using "adb shell" and root with id command

[email protected]:/ #
id
uid=0(root) gid=0(root) context=u:r:shell:s0
[email protected]:/ #


The method TPSparkyRoot with the batch file from here (Modified to work properly) has showed confirmation that root is ok, as there was no errors during process
I checked file system in read only mode (with xPlore) : su and busybox binaries are in /system/bin, SuperSU also installed in /system/app with 644 permission and root.shell ownership but no ROOT.

The SuperOneClick method tells me that device is rooted but in fact nothing
I think it is permissions and ownership issue or an incompatible su binary (I have tried many ones, sometimes SuperSU says there is no binary, other times says it have to be updated but fails) but have not any clue on how to solve it.

This stick is driving me crazy !
Any idea is welcome

I might have a similar device. It is a generic mk809iv Android TV stick running 4.4.2. I actually managed to root it, but I'm not sure how. I simply downloaded tool after tool that did not work, then suddenly it was rooted. However, it was using KingUser or KingRoot and my antivirus flagged it as a problem. So tried to install SuperSu, but that did not work. Does anyone know how to root these devices safely? Here is an image of my device:

 

[slow66]

I used kingoroot, was easy and quick. Now searching for a rooted rom.

 

[leech4]

I used kingoroot, was easy and quick. Now searching for a rooted rom.

Thank you for the reply, I already found the kingoroot and it is just working fine, I forgot to update the thread by the way.
For those people who are interested, just google it.
It is a free app, so if it works, don't forget to donate to the author
Before rooting, you need to get proper windows drivers installe, enable USB debugging
It is important to disable automatic updates for SuperSU in google play, because when updating, it will ask to update binary and fail, so will lose root.
Keep SuperSU at installed version.

 

[palia]

I need firmware for this device

I might have a similar device. It is a generic mk809iv Android TV stick running 4.4.2. I actually managed to root it, but I'm not sure how. I simply downloaded tool after tool that did not work, then suddenly it was rooted. However, it was using KingUser or KingRoot and my antivirus flagged it as a problem. So tried to install SuperSu, but that did not work. Does anyone know how to root these devices safely? Here is an image of my device:

Jonathan,
I need the firmware for this device, can you provide me please. I have tried 20 different firmware I could download, but none worked.
:fingers-crossed:

 

[jonathankonrad]

Jonathan,
I need the firmware for this device, can you provide me please. I have tried 20 different firmware I could download, but none worked.
:fingers-crossed:

Sure, except I do not know how to obtain the firmware from the device. Is there a link to a "how to". I would need the tools.

 

[s3samngsung]

Is this still alive I have purchased this device did u get it root I have tried kingo it says root but play store verify root says it's not its got kit Kat 4.2.2 very quick its mk809iv what's safe to try going to to get a custom recovery and back up what its got first from what I hear are these unbrickable

 

[mvez73]

Hi everybody. I just bought a mk809iv and i need to root it. I tried Kingoroot but when i connect my stick to my pc kingoroot doesn't recognize the stick. USB debugging is enabled. And my chip is not a 3188 but a 312x (probable 3128) in the about section. Can you help me please? Thank you.

 

[mvez73]

Hi everybody. I just bought a mk809iv and i need to root it. I tried Kingoroot but when i connect my stick to my pc kingoroot doesn't recognize the stick. USB debugging is enabled. And my chip is not a 3188 but a 312x (probable 3128) in the about section. Can you help me please? Thank you.

I finally found a working method. Kingroot and not Kingo Root.

 

[gunther82]

I just bought a MK809IV with chip RK3229, do you know how to root this version? Thanks!

 

[william_ferguson_au]

Getting the proper windows drivers for MK809IV

... you need to get proper windows drivers installed, enable USB debugging

leech4, I'm running Windows 10, have the MK809IV and have installed the Rockchip DriverAssistant_v4.4 on my laptop.
I have enabled USB debugging on the device, but the device is not recognised when I plug it into my laptop.
Windows Device Manager doesn't even show it as a connected device.

When you say "get the proper Windows drivers installed".
Which drivers? From where?