How to Root MK809III RK3188

[threehappypenguins]

I backed up my old ROM, so I can start over. However, that's a BIG pain because I have to go find a computer again (I have Windows 8.1, remember?). When I was at my friend's house, I had no way to test it since they don't (*gasp*) have an LCD TV. Only an old CRT TV. But they're about 30 minutes away, and there are 8 kids running around there, so I'm done there for the day.

[threehappypenguins]

Alright, so I read this: http://forum.xda-developers.com/show...1#post47415109

I have no idea what they're talking about:

But I fix it with
copy WCNSS_qcom_wlan_nv.bin to \persist (on wi-fi fix atrix hd)
and fix permissions chmod -rw-rw--- and chown wifi:wifi
my wi-fi is back to work

Does anybody know what this means? Maybe a step-by-step? It is never explained in the thread. Do I open terminal emulator? What do I type? Do I open a file explorer? If I open WCNSS_qcom_wlan_nv.bin (wherever that may be), what do I do to it?

[threehappypenguins]

I *may* have gotten a little closet to a fix. I opened the Ultra Explorer app on the TV stick and navigated to system/etc/firmware/


In this thread here http://forum.xda-developers.com/moto...tooth-t2813308 the person had WCNSS_qcom_wlan_nv.bin in system/etc/firmware/wlan/prima


The problem is I don't have any other folders in the "firmware" folder. I can't find a WCNSS_qcom_wlan_nv.bin file anywhere. I tried a search, but nothing. I've never had luck with any of these file explorer's search options, though. It won't find files that I *know* are there.


Anyone got any ideas? It seems like if someone has the original .bin file from my original ROM, that if I replaced the current one, it would work. I think.

[bluesmanuk]

You mentioned in another thread that your stick had an AP6210.

This ROM specifies that support, so worth a look.

http://www.freaktab.com/showthread.php?14714-MK809III-KitKat-4-4-SMIC717394-1080p-ROM&highlight=AP6210

[bluesmanuk]

I *may* have gotten a little closet to a fix. I opened the Ultra Explorer app on the TV stick and navigated to system/etc/firmware/


In this thread here http://forum.xda-developers.com/moto...tooth-t2813308 the person had WCNSS_qcom_wlan_nv.bin in system/etc/firmware/wlan/prima


The problem is I don't have any other folders in the "firmware" folder. I can't find a WCNSS_qcom_wlan_nv.bin file anywhere. I tried a search, but nothing. I've never had luck with any of these file explorer's search options, though. It won't find files that I *know* are there.


Anyone got any ideas? It seems like if someone has the original .bin file from my original ROM, that if I replaced the current one, it would work. I think.

Try this.

It has a link to download the file too.

http://www.modaco.com/topic/360156-wi-fi-issues/

It's not guaranteed to work though.

[threehappypenguins]

Try this.

It has a link to download the file too.

http://www.modaco.com/topic/360156-wi-fi-issues/

It's not guaranteed to work though.

There's a link in there to download WCNSS_qcom_wlan_nv.zip, but when I click on it, I need to log in to download. I went to register, and it costs money to do so.

[bluesmanuk]

There's a link in there to download WCNSS_qcom_wlan_nv.zip, but when I click on it, I need to log in to download. I went to register, and it costs money to do so.

Try this

http://forum.xda-developers.com/showthread.php?t=2438733&page=31

Post 302.

[threehappypenguins]

Try this

http://forum.xda-developers.com/showthread.php?t=2438733&page=31

Post 302.

Since I only had the folders /system/etc/firmware/ I created wlan/prima after that. I then copied WCNSS_qcom_wlan_nv.bin to /system/etc/firmware/wlan/prima and it made no difference. I rebooted the TV stick and still no difference.

Perhaps I need something specific for my chipset? That would make sense...

[bluesmanuk]

I think you may be better off reading through the ROM thread for the AP6210 I posted earlier and make another visit to your friends.

Here is a shot in the dark though that may work.

http://www.freaktab.com/showthread.php?16004-ROCKCHIP-RK3288-USB-DRIVERS-FOR-WINDOWS-XP-WIN7_32-WIN7_64-WIN8_32-WIN8_64

I ran the install on my Windows 8.1 machine that has working drivers anyway and it didn't affect anything, so worth running to see if you can do everything from home.

[threehappypenguins]

I think you may be better off reading through the ROM thread for the AP6210 I posted earlier and make another visit to your friends.

Here is a shot in the dark though that may work.

http://www.freaktab.com/showthread.php?16004-ROCKCHIP-RK3288-USB-DRIVERS-FOR-WINDOWS-XP-WIN7_32-WIN7_64-WIN8_32-WIN8_64

I ran the install on my Windows 8.1 machine that has working drivers anyway and it didn't affect anything, so worth running to see if you can do everything from home.

Nope. Didn't work.

[bluesmanuk]

Oh well.

No pain, no gain lol

[threehappypenguins]

I have another idea. Why not just flash this custom ROM by using recovery? So here is how I got started:

I opened up terminal emulator (which is already installed) and typed in

su
reboot recovery

And then it rebooted me into the stock recovery. However, it said to use the volume up/down buttons to navigate and power to select. Obviously that won't work (geared toward phones/tablets, I guess?), and the wireless mouse and keyboard (dongle plugged in USB) weren't working.

SOOOOO. I decided to look up how to install Clockworkmod recovery (one that would allow me to use my keyboard and mouse)!

I found all necessary instructions here: http://androidtvnews.com/cwm-recovery-rk3188-quad-core/

I first downloaded these exact files onto my laptop:

http://files.androtab.info/rockchip/rk3066/20130427/RK30GENERIC_CWM.zip

http://www.freak-tab.de/leolas/cwm/term-install.zip

And also the Busybox .apk. Now on my phone I have Airdroid, so I simply downloaded the .apk from my phone onto my laptop. But if someone reading this needs that .apk (and you can't download from the Playstore on your TV stick if you don't have wifi), this may work: http://file.appsapk.com/wp-content/u...ds/BusyBox.apk

I then transferred everything onto the microsd card I have and placed it in the TV stick. From there, I opened Busybox and updated it (apparently it was installed, but I didn't see it in the list of apps). I then placed term-install.zip and RK30GENERIC_CWM.zip into /sdcard/Download

I opened Terminal Emulator and typed all this in:

su cd /sdcard/Download 
unzip term-install.zip 
unzip RK30GENERIC_CWM.zip
mv recovery.img cwm-recovery.img
sh cwm.sh
reboot recovery

And it booted into CWM no problem with the keyboard working! Yay!

Now... let's see if I can install the ROM this way. To be continued...

[bluesmanuk]

You are going to have to convert a ROM to be CWM flashable first though.

There was a thread a while back about it.

I think this was is.

http://www.freaktab.com/archive/index.php/t-4023.html

[threehappypenguins]

Ok, I *almost* have this figured out!!! I decided to follow these instructions, and use the "blank" zip file given in this link: http://www.freaktab.com/showthread.p...stallable-zips

I used winrar and copied over all the .img files. Moved it on the sd and then put the sd in the tv stick. Reboot into CWM, installed the .zip file, then wipe data/factory reset. Rebooted and saw the new custom ROM logo! I waited... and waited... and waited... it's stuck.

So I took a wild guess and decided to unplug the power from the TV stick, put a paperclip in the little hole in the side, then plugged the power back in it. Lo and behold, it booted into CWM!!! Yay!!!

So I decided to add all the parameter files to my .zip file, put it back in the stick, and repeated the process again. Still no go. Stuck on the logo. I'm wondering if it has to do with this?

We cant resize partitions using cwm (at least I didn't discover how do it, and I tried it a lot of times). So the img files must be equal or smaller that the destination partition, we cant flash a 10,6Mb kernel.img in a 9Mb partition. Usually it will not happens, partitions usually are bigger enough, but I want to advice you.
We can flash only boot.img, system.img kernel.img, we cant flash the loader, format the nand, resize partitions, so if you want to use a 2Gb for the app partion and you have actually only 1Gb. You need to use the pc for resize it.
If we need to hard format nand, we need to use the pc too.

I don't completely understand that and how I would know whether my .img files would "fit" and how to get them to "fit." In the non cwm flashable zip (the original), there is a folder called "ROM." That is where I'm getting the files. In there, there is also a file called RK3188Loader(L)_V2.13.bin. I didn't add this. Then there's also another folder called "Kernels" with a bunch more .img files (for example kernel_1.6_600_400.img). I didn't add those either.

What do I do? Should I edit the updater-script in META-INF\com\google\android ? If so, what should I change? I don't know how to make this zip work!!!

[bluesmanuk]

What I believe it means is that if say when you had the stock ROM, the original parameter file was for 1Gb, which is often the case, if you then use CWM to flash a ROM and you use a 2Gb parameter file then it will cannot automatically resize the original 1Gb partition to make it larger.

If you have a number of parameter files, I would start with the one that is most likely to match the original, which would likely be for 1Gb and go from there.

Make sure that the one that you use just has the name parameter.