My MK808 won't go past the "Google TV" screen!

[rickonvb]

I also tried to reboot the system and it also got stuck in the MK 808 Filness screen. This time we have an image with colored lighting balls.

[leolas]

Well you advanced a lot, but i fear that your system nand is corrupted i am writing a basic guide to start for the first.

[Finless]

Realize this. I have seen clones that MUST use the security protected kernel or they will not boot. I fear either your NAND memory is hosed or you actually have a clone.

Have you tried the MK808B Sunvel clone ROM?

Bob

[leolas]

Thanks a lot Abducted. Sorry i forget this thread. Lets see if Abducted and me can help you.

I suggest you some steps:
Download this rom:http://www.freak-tab.de/finless/mk808b_finless_17.zip and unzip it.
Disconnect all usb from the device and remove the sdcard if you have 1 inside the stick.
Conect a usb wire to the pc, The stick must have only connected the hdmi out.
Press the reset button and let it pressed while you conect the usb from the pc to the OTG port in the stick.
Windows must sound like a new device detected. You can now release the reset button.
Open rk flash tool from finless rom.
Push ERASE NAND(IDB).
Now push in flash Rom.
Wait until it finished and if everything goes ok wait at least 1 minute before disconect the usb from OTG.

If you have attached a tv or monitor to the stick while you flash it and once it finish you can see how it reboot, then it enter in recovery and format some partitions, and when it is finished the device will reboot and enter in android system.
Sometimes if you disconnect the usb from OTG fast after flash the device and before the unit made the formats you will get like if your nand get corrupted.
Pls try it.

Hi!

I am in a similar situation. I received my MK808B a week ago and was trying to get it working since than.

I started by flashing the Finless 1.7 ROM meant for MK808B and for a day or two I was happy with my new toy and everything was looking fine. However the stick froze while I was playing around with XBMC and started producing strange errors after I rebooted it (pulled the power), all of the user settings got lost (start screen layout, wifi password, etc...), apps were not able to start and random freezes. So I have reflashed my MK808B with the same ROM but it froze within a few hours while I was installing the previous apps. And again the settings were lost after the reboot. Afterwards I have repeatedly tried to reflash with the same ROM but I got the same errors. After one freeze the device couldn't even reboot properly, it got stuck at the boot screen.

I have tried to use the Finless Jelly Bean BETA ROM with the same results. Random freezes, lost settings. Right now my MK808B is again in a state where it is stuck at the non animated Finless boot image, so I would need to flash it again.

Has anyone experienced similar issues ever? I am starting to believe that my unit is faulty, or that it is a heating issue.

Are you using the stock power supply?

[leolas]

Realize this. I have seen clones that MUST use the security protected kernel or they will not boot. I fear either your NAND memory is hosed or you actually have a clone.

Have you tried the MK808B Sunvel clone ROM?

Bob

He post in the first of thread some pics and he have the rk903 device.

[Abducted]

He post in the first of thread some pics and he have the rk903 device.

That's what i was thinking, but since this isn't quite working either he might as wel give it a try. Maybe it's a V3 clone

Also after Gilgames posted that post i did consider a NAND failure, but during a flashing proces the img files are first writen and then checked, so i would expect an error there if the NAND is bad right?

[Finless]

Also after Gilgames posted that post i did consider a NAND failure, but during a flashing proces the img are first writen and then checked, so i would expect an error there is the NAND is bad right?

Correct! I have never seen a good flash and check that then would not work UNLESS the ROM was not made for that device. But I guess there is always a first time but I highly doubt it! Something else is going on here me thinks!

Bob

[Gilgames]

Hi,

since I wrote my previous post I have also tried the CWM method with the same end result.

I collected some logs from my latest trial which I think show odd behavior. There are some write errors in there that I think shouldn't be.

I have also taken my stick apart to verify it is an actual MK808B and not some clone.

Here are some pics I have taken and the dmesg log: https://drive.google.com/folderview?...1E&usp=sharing

[rickonvb]

It is working!! It is working!!!

That's what i was thinking, but since this isn't quite working either he might as wel give it a try. Maybe it's a V3 clone

Also after Gilgames posted that post i did consider a NAND failure, but during a flashing proces the img files are first writen and then checked, so i would expect an error there if the NAND is bad right?

Hello everyone!!
First of all, I would like to thank you all for helping me out!

After all of our discussion I started making all kinds of arrangements. Changed power supplies, cables, devices (yes, I have 2), etc.

For one second I thought it was the power supply. But now I know it is finally the power supply cable!!!
Even though the device was powering up, I suspect that the internal cables were too thin to handle all of the required current.

Now both of the devices are running Finless 1.7 flawlessly (wi-fi is rocking).

By the way, I used the CWM technic (first cleaning the cache and then formatting and restoring the system).

[leolas]

Hello everyone!!
First of all, I would like to thank you all for helping me out!

After all of our discussion I started making all kinds of arrangements. Changed power supplies, cables, devices (yes, I have 2), etc.

For one second I thought it was the power supply. But now I know it is finally the power supply cable!!!
Even though the device was powering up, I suspect that the internal cables were too thin to handle all of the required current.

Now both of the devices are running Finless 1.7 flawlessly (wi-fi is rocking).

By the way, I used the CWM technic (first cleaning the cache and then formatting and restoring the system).

Good, nice to see you resolve your problem.

[BrunoNRG]

My MK808B is doing the same, won't go past the Google TV screen. Already tried two different power
adapters and a couple usb cables, tested on two different tv's, never flashed, running stock 4.2.2 rom...

Any ideas? Thanks in advance

Edit: What happens if I press the reset button, will it boot in recovery?
If it does, I could try to restore the room backup I did a few days ago...

[Finless]

If your flashing one of my ROMs read the README please... I give detailed instructions for what to do.

YES the reset with plug in will put you in flash mode. Again read my instructions. I spend a lot of time writing them!

Bob

[BrunoNRG]

Thanks for the information Bob and (even though I never used one of your roms) for all your work
regarding android tv sticks. I understand that you spend much time writting the Readme, but I'm
not flashing a rom, never did. I'm just trying to get the MK808B to work again, with the stock rom,
I never flashed any rom on it. I want to know what happens if I press the reset button with the
device plugged on the tv, if it goes to the recovery menu, will it be possible to restore a rom backup?

[Finless]

OK long story and this is all posted here if you spend the time reading... sorry but I will summarize.

Android is a Linux OS system. If you unplug the device while it is running, it can corrupt the file system! This will cause it not to boot again.

Unfortunately the only way to recover is to flash a ROM!

So now your what is called soft bricked. Now you must flash a ROM to recover. No other way!

The reset button only puts the device into ROM FLASH MODE. That's what it does.

So now, go read how to flash a ROM using stock (not much documentation there), or download one of my ROM's and read the readme and flash the ROM.

Sorry you got stuck but now you know. never just unplug the TV stick! Or install APPs that you should not have that can cause corruption of the ROM.

Bob

[BrunoNRG]

Excluding the times the divece "froze", I allways used the option on the notification / status bar to shut it off.

I guess there's a first time for everything, because I was really enjoying the 4.2.2 stock rom, I'll try
your 2.1 rom, that I belive to be the same but with all the improvements you add to your roms.

Appart from SetCPU, that was set to Ondemand and 200MHz
min and 1608MHz max, I have no idea what could cause this...

Once again, thank you very much for all your help!