How to Root MK809III RK3188

[threehappypenguins]

I figured I would be safe if I just simply rooted it for now (not flashing a different rom). Then I can install nandroid and use that to back it up.

I'm trying to follow these instructions: http://www.cnx-software.com/2013/03/...3188-mini-pcs/

However, they're not really clear. So I guessed that I needed to have it plugged into my TV so that I can boot it up and see the screen. I brought my laptop to beside the TV. So I have one plug in the DC outlet so it can turn on. I have another mini usb coming out of the one on the side, and ready to plug into my computer. I turned on USB Debugging, and then, while the TV stick is still in the operating system, I plug in the USB into my computer (from the one coming out of the side of the TV stick).

But nothing happens. So I figure I need to push the paperclip into the little hole on the side, hold it in, and then plug in the USB into my computer. Still, nothing happens. I already have all the drivers installed from the previous instructions and RKAndroidTool.exe connected with it (but I didn't do anything after that point for fear of doing it without the stock rom as a backup). I was previously about the install a custom ROM through these instructions: http://blog.geekbuying.com/index.php...ore-tv-sticks/

But I stopped short because I was afraid of doing it without backing up my ROM.

So it seems like it will only connect when the TV stick is shut down and not in the operating system?

What am I doing wrong?

When I'm looking for a rooting method, should I be searching for MK809III SK3188? Or should I be searching for rk31sdk 4.2.2 (kernel is 3.0.36+)?

I don't understand if I'm supposed to have the TV stick on or off (it's confusing when they're talking about a "reboot"). All the instructions I find are vague and assume people already know what they're doing.

*Edit* Sorry about the title. I forgot to put a question mark so that it's not mistaken as a tutorial, when it's only a question. Moderators, if you are able to change my subject title and add a question mark or "help" or something, feel free to do so.

[threehappypenguins]

Okay, so I figured out why the device wasn't being detected by my PC while it was on. I needed to go to Settings > USB > Connect to PC (check off). Then my PC detected it. However, though it installed "rk31sdk" into the driver's list with a little yellow question mark in Device Manager. So I right clicked on it to update the driver, and I chose the folder with the Windows 8 x64 bit .inf, but it wouldn't install. It just said, "Windows could not find driver software for your device." I tried going into choosing it from a list, and chose "Rockusb Devices," and then the driver that I originally installed (while the device was off and I went into recovery or whatever while pressing the paper clip in there). It said it installed it, but when I tried to run the TPSparkyRoot.bat, as per the instructions, it just said "Device not found."

So I gave up on that method.

Now I'm about to install using this method: http://www.arctablet.com/blog/forum/...ware-20130718/

But this is where I am confused. It says it's for the Measy U4B Android, but it has the same information as mine: rk31sdk 4.2.2 (kernel is 3.0.36+ although mine says "root@lhh12-desktop #59 Sat Jan 18 10:12:18 CST 2014")

Would this still root it? Or will I brick it?

[bluesmanuk]

Windows 8 can be problematic when installing drivers and getting it to flash.

You may have to disable driver signature enforcement to get them installed too.

https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8

When and if you do get into the right mode, instead of rooting, have a look at the custom roms on here that will be rooted and modified to perform better than just stock with root.

[threehappypenguins]

When and if you do get into the right mode, instead of rooting, have a look at the custom roms on here that will be rooted and modified to perform better than just stock with root.

Yes, that was what I was going to initially do. But I'm really afraid of doing it without a backup of my ROM. But all the instructions I find to backup the ROM are confusing. I need SIMPLE step-by-step. So I figured if I could just do a basic root, then I could backup the ROM using Nandroid (which requires root), and THEN install a custom ROM.

[bluesmanuk]

Unfortunately things are not always that straightforward but there are a couple of generic guides here on installing drivers and flashing.

http://www.freaktab.com/showthread.p...s-for-flashing!

http://www.freaktab.com/showthread.php?632-Flashing-Firmware-Image-Files-Using-The-Rockchip-Batch-Tool

Trying different methods is often the case but you may well find somebody post that has the same stick.

Following the instructions for backing up the existing ROM do work if you follow each step exactly as written and you could start with Finless Bobs method that would also give you more knowledge of the structure of images.

The AutomateAndroidToolBackup tool is a simple .exe file that you run with little input needed once you get the stick into flash mode and drivers installed.

[threehappypenguins]

I did it! At least I hope so...

First, download this file: http://www.freak-tab.de/finless/rk_tool21_how_to.zip

Then, unzip it and follow these instructions for backing up your BASIC stock ROM (no user files, no saving apps, etc:

Instructions for dumping....


Before we begin let’s get familiar with the tool.
In the download run the ROM_Dumper_Tool.exe.
When it opens you will notice 3 tabs at the top.
Download image - this is for flashing ROMs
Upgrade Firmware - this is for lashing single .img ROMs. I won’t be going into this area for as we don’t use it for dumping.
Advanced Function - This is for dumping and doing some cool stuff! We will be in here all the time for this procedure.


Note: Anytime we dump a partition the tool always makes a file called ExportImage.img in a folder called Ouptut.
So every time we dump a different partition it will overwrite that file unless we rename them first!
Don't forget that please.


OK first lets dump the basic flashable ROM:

To do ANY dumping we need to dump the parameter file of the ROM from NAND.
Why? because we need the start (offset) and count (size) of the partition or we can’t dump anything.
1) Click the advance functions tab.
2) At the bottom is the "export image" button and to empty boxes, Start and Count.
3) To get the parameter file put a 0 in the start box and a 2 in the count.
4) Now press the export image button.
5) Now we need to make this a real parameter file! Rename the file to parameter.txt
6) We need to clean it up a bit. Open in Windows note pad ONLY!!! Do not open in MS word or anything else or it won’t work!
Also you may need to turn on word wrap to see everything (format menu, select word wrap checked).
7) The first line you will see something like this:
PARMi FIRMWARE_VER:4.1.1
Delete all the junk in front of the word FIRMWARE so it looks like this now:
FIRMWARE_VER:4.1.1
8) clean up ending junk. At the end you will see this word:
(user)
After it will be some junk. Delete everything after (user) including any blank space.
When done make sure to hit enter once so there is a new line after (user)
9) Save the cleaned up parameter file but leave it open as we need it to continue.


Now let’s start dumping!
We will do system.img to start with as an example.
1) Look at the parameter file and find (system) and the numbers before it. Example:
0x00180000@0x00484000(system)
REMEMBER the number before @ is the COUNT and the number after the @ is the START!
2) Copy the number after the @ example: 0x00484000 into the start box of the advanced tab in the tool.
3) Copy the number before the @ example: 0x00180000 into the count box of the advanced tab in the tool.
4) Press the export image button and wait for it to complete.
5) Go into the Output folder and rename the file ExportImage.ing to system.img


Now we just repeat the steps 1-5 above for
misc.img
kernel.img
boot.img
recovery.img
backup.img (This can be optional but do it anyway especially if this is a first REAL stock ROM dump as we may need it).


Remember to always use the numbers in front of each name! Don't forget to change those or you won’t have a good dump.
Also remember after each dump, to rename ExportImage.img to the proper name of the image you dumped!
Each time you press Export Image, it will overwrite the existing ExportImage file unless you rename it!


When you’re done you should have the basic ROM dump.
misc.img, kernel.img, boot.img, recovery.img, system.img, and backup.img.


You can now use the flash tool 2.1 or the flash tool 1.37 to flash these.

[bluesmanuk]

It sounds as if you are well on your way to obtaining your goal.

[threehappypenguins]

This is so frustrating! I had everything all set up to install a custom ROM as explained here: http://blog.geekbuying.com/index.php...ore-tv-sticks/

RKAndroidTool.exe recognized the device just fine (it said it was found), so I clicked "Run" and suddenly it disconnects and I get this Windows error, "USB Device not Recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it."

Now it *never* connects. I cannot for the life of me get it to connect. I tried to manually install the .inf (I am running Windows 8.1). When I go to manually install it and click on the "Have Disk," I get the error: "The folder you specified doesn't contain a compatible software driver for your device."

The closest explanation I could find was from foxnix232 here: http://www.freaktab.com/showthread.p...or-Windows-8-1

I figured it out.
The problem is not with Windows 8.1 - well it actually is, but not in the regular way.
8.1 brings some updates to the USB stack - better, more detailed error messages, and most importantly, a new way of determining devices if they're working correct or not. As the MaskROM mode uses a damn old protocol, it does not respond properly, and Windows flags the device as faulty, stops everything else, and bye-bye Download mode. As it gets the faulty device VID and PID (0x0000,0x0002), the drivers are refused no matter what (even if you add these VID and PID to the supported list!).
Solution: Either install an older Windows, or Linux. On Linux, get VMWare with XP running, and pass over the device.
Actual solution: Wait till Rockchip updates the bootloader, with a more up-to-date protocol. Then we can use it on 8.1

So I decided to boot up my Windows XP that I already had for VirtualBox, and I had the USB 2.0 extension installed. I don't understand how to get it to detect the device. I'm supposed to choose a device to pass over, but I don't see the device in the list. Just two unknown devices. So I pass both unknown devices over, and they just show up in the device manager under Other Devices as USB device (with a yellow question mark). I try to manually install the .inf in the Windows XP VirtualBox, but I get an error "The specified location does not contain information about your hardware."

So I am at a loss. I can't flash my device. Ugghhh...

[threehappypenguins]

Yeah soooo...

I just plugged it in the HDMI port in my TV, plugged in the DC, and now it won't even boot in the OS. No logo, no nothing. The TV is not even detecting it. Like nothing is plugged in the port. Ahhhhh!!!!

[bluesmanuk]

Go back a step or two to how you managed to get Windows to recognise the device in order to use the rom dumper tool.

Perhaps you could try uninstalling the driver and going through the same procedure again to get Windows 8 to see it in order to flash a new ROM.

Can't help with the virtual XP as I've not used it for so long now.

[bluesmanuk]

Yeah soooo...

I just plugged it in the HDMI port in my TV, plugged in the DC, and now it won't even boot in the OS. No logo, no nothing. The TV is not even detecting it. Like nothing is plugged in the port. Ahhhhh!!!!

Sounds odd that on the basis that all you have done so far is backed up your original ROM.

I'm guessing that you have done the usual checking of AC adapter etc just to rule out an unhappy coincidence.

You've got the power cable plugged into the back and not the side port?

[threehappypenguins]

You've got the power cable plugged into the back and not the side port?

Yes. In the DC port on the bottom (when plugging into the TV to boot it up). It booted up before, but not now.

As for undoing stuff, I've already tried uninstalling the drivers. I may have to do something in the registry to completely wipe it clean because it keeps showing the error and not doing what it originally did. But even if I got the drivers going on my Windows 8.1 laptop, my guess is I would run into the same problem as soon as I ran the tool to install the custom ROM. Everything was working until I ran the tool. It's probably just as foxnix232 describes it.

Since I can't get it going on the Virtualbox, then I'm going to have to drive down to the local library (and drag my 2 and 4 year old with me) and use the computers there. Ughhh...

[bluesmanuk]

I've run all the backup tools and options dozens of times and all it does is backup data from the stick and doesn't write anything to it, so can't see it being that.

The only tool that I know can can cause issues is using the 2.1 tool to flash, which Bob advised not to use, instead of 1.37.

[threehappypenguins]

I used 1.37. I downloaded the package neotvcr_mk809_3_ug007b_20130615.zip

What I ended up doing was going to the local library, went to install the driver, then did a face palm when I realized "Of COURSE the computer blocks out weirdos like me and requires admin privileges to install drivers! D'oh!" So I ended up driving way out to a friend's place, and successfully flashed the rooted ROM on there.

Now I have another big problem. The wifi won't turn on. I go to turn it on, and it won't. turn. on. Neither will the bluetooth. Since ROM is rooted, is there anything I can change to make it work? A file I can edit? A command I can put in Terminal emulator? I can install any kind of app by just loading an .apk on an SD card and then installing the app on the TV stick.

Any ideas? The wifi and bluetooth worked fine with the original ROM.

[bluesmanuk]

I'm pretty certain that there is no very easy way to do what you want as the particular ROM that you have used will have been built for specific wifi etc chipsets, so there are essentially two options.

One is to look through the threads with the varying ROM's available to see which one matches your specific device (you could open the stick up and look at what is in it to identify components) or try them all until one works.

Not what you will want to hear I know but I don't think that there will likely be an easier route.