Q8 (or vsmart Q8) RK3288 – Everything that we know

[yang]

After days of trying, finally I got nice working SPMC with SPDIF DTS passthrough on a Q8 (Q8L 2G/8G 2015-03-10 WW236 ST).

Here is the solution:

1. Flash Modified Ricomagic firmware http://freaktab.com/forum/tv-player-...magic-firmware

2. Replace /system/lib/libmedia.so with the one downloaded from this page: http://forum.openhourlab.com/showthread.php?tid=276

3. Install SPMC 15.0.

[Pihkal]

Some info that's not mentioned and might be useful:

RAM: DDR2LP @ 400 Mhz (x 2) -> Doesn't like overclocking at all! -> need to do more testing.
GPU: 500 Mhz -> tried OC to 625 Mhz, seems to work but needs higher RAM bandwidth for efficiency, need to do more testing.
ARM: 1800 Mhz -> No OC tried yet, overclock-o-matic fails to find the second kernel lock for some reason, don't feel like flashing new ROM/kernel just yet.
Wifi: AP6330

[ConteZero]

Referring to my box (ENY-Q8P-V10)... had some problem with the default update process (with W10 and XP).
Here's the problem and how I "fixed" it:

First of all I fetched Android Tool 2.3 from this forum, complete with the Rockchip driver (the unsigned one: had to disable driver signature check as adverted in W10).
Problem is: there was a "Code 10" error with device detection, meaning that every time I put the Q8 in "update mode" a yellow "?" appears in the device tree and the device isn't detected in AndroidTool.
There's no way to fix it (at least, I wasn't able to fix it) but you can go to device tree and "update driver" with THE SAME driver on the fly, then the device is detected as working and you can "use" it until the next device reboot.

A problem arise when you try to flash a new firmware (in my case Wasser4) because just before writing the device must be rebooted and the infamous "Code 10" happens.
For this reason (since you have a limited time span) keep your device tree open nearby, wait for the reset and "update" the driver as fast as you can, if you're fast enough you'll be able to do this before AndroidTool goes to timeout.

Hope it helps.

[ConteZero]

Add: This is my board, a "standard" ENY-Q8P-V10 but with a different sticker and a white code on the lower left angle.
The CPU "head" (heat spreader) is also different from the one in OP.

Recovery mode is as follows:

Additional rant: memory is "16Gbit LPDDR2 1066MHz 220-FBGA - K3PE0E000A-XGC2"

[mo123]

Add: This is my board, a "standard" ENY-Q8P-V10 but with a different sticker and a white code on the lower left angle.
The CPU "head" (heat spreader) is also different from the one in OP.

Recovery mode is as follows:

Additional rant: memory is "16Gbit LPDDR2 1066MHz 220-FBGA - K3PE0E000A-XGC2"

RAM needs to run at 533Mhz to play 4K videos smoothly, possible on all other RK3288 tv boxes with decent heatsinks.

[ConteZero]

RAM needs to run at 533Mhz to play 4K videos smoothly, possible on all other RK3288 tv boxes with decent heatsinks.

That might be a problem.
From dmesg:

<4>[ 0.648948] DDR DEBUG: version 1.00 20150126
<4>[ 0.648975] DDR DEBUG: Channel a:
<4>[ 0.648983] DDR DEBUG: LPDDR2 Device
<4>[ 0.648997] DDR DEBUG: Bus Width=32 Col=10 Bank=8 Row=14 CS=2 Total Capability=1024MB
<4>[ 0.649006] DDR DEBUG: Channel b:
<4>[ 0.649014] DDR DEBUG: LPDDR2 Device
<4>[ 0.649026] DDR DEBUG: Bus Width=32 Col=10 Bank=8 Row=14 CS=2 Total Capability=1024MB
<4>[ 0.649035] DDR DEBUG: addr=0xbff000
<4>[ 0.649044] DDR DEBUG: stride=9, size=256, halfcap=40000000
<4>[ 0.649053] DDR DEBUG: socAddr[0]=0xbff000, socAddr[1]=0xbff100
<4>[ 0.649062] DDR DEBUG: chAddr[0]=0xbff000, chAddr[1]=0xbff000
<4>[ 0.649073] DDR DEBUG: dtar[0]=0x7017f000, dtar[1]=0x7017f000
<4>[ 0.649127] DDR DEBUG: init success!!! freq=200MHz
<4>[ 0.649134] DDR DEBUG: Channel a:
<4>[ 0.649146] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649159] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649171] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649183] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649195] DDR DEBUG: ZERR=0, ZDONE=0, ZPD=0x0, ZPU=0x0, OPD=0x0, OPU=0x0
<4>[ 0.649204] DDR DEBUG: DRV Pull-Up=0x19, DRV Pull-Dwn=0x19
<4>[ 0.649213] DDR DEBUG: ODT Pull-Up=0x2, ODT Pull-Dwn=0x2
<4>[ 0.649220] DDR DEBUG: Channel b:
<4>[ 0.649231] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649243] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649255] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649267] DDR DEBUG: DTONE=0x3, DTERR=0x0, DTIERR=0x0, DTPASS=4,4, DGSL=1,1 extra clock, DGPS=270,270
<4>[ 0.649278] DDR DEBUG: ZERR=0, ZDONE=0, ZPD=0x0, ZPU=0x0, OPD=0x0, OPU=0x0
<4>[ 0.649287] DDR DEBUG: DRV Pull-Up=0x19, DRV Pull-Dwn=0x19
<4>[ 0.649295] DDR DEBUG: ODT Pull-Up=0x2, ODT Pull-Dwn=0x2

(...)

<6>[ 1.332937] rockchip_uboot_mem_late_init: Freeing uboot logo memory: 0x02000000@0x7dc00000
<6>[ 1.339249] ddrfreq: verion 1.2 20140526
<6>[ 1.339271] ddrfreq: normal 456MHz video_1080p 0MHz video_4k 456MHz dualview 0MHz idle 0MHz suspend 200MHz reboot 456MHz
<6>[ 1.339283] ddrfreq: auto-freq=0
<6>[ 1.339295] ddrfreq: auto-freq-table[0] 240MHz
<6>[ 1.339305] ddrfreq: auto-freq-table[1] 324MHz
<6>[ 1.339316] ddrfreq: auto-freq-table[2] 456MHz
<6>[ 1.339326] ddrfreq: auto-freq-table[3] 528MHz

So no 1066MHz for me, just 900MHz

[csori23]

4) Brick
If your device don’t have any signal of life, and can’t even enter on upgrade mode, well, the device is bricked. It’s time for desperate measures.

Disassemble your device, and look for the FORSEE chip



locate the 7 & 8 connectors. But the problem is: which corner start counting? Well, most of the cases is in the black arrow, but there was a time that I had to pin the yellow arrow! So, just start the procedure bellow with the black, if doesn’t work, restart and go to the others corners…

1. Open the RKbatchTool
2. Unplug the power supply
3. Plug the OTG USB cable in the micro usb port and in the pc.
4. With a screwdriver, PIN the 7 & 8 connectors
5. Connect the power cable.

The BatchTool should now show an blue device flag instead of the green. If is blue you can simply flash your stock rom again

Sources: http://freaktab.com/forum/tv-player-...x-or-eny-clone

http://freaktab.com/articles/489991-...ck-your-device

Hi.
My TV box, I: XT-V10 2014-09-02 Q8L C Q8L label with 8G / 2G ST XT201410154
Brick was. I did it on the basis of section 4 but does not boot into the system.
A year ago, the same way I did the first time and managed to revive.
The LED lights up blue.
After the flash recovery writes:
E: clone_data_if_exist-> partition scanning error
Formatting / data ...
Formatting / cache ..
REBOOTING ...

but nothing happens.
I tried a hard reset. Nothing.
Firmware is Stock

Can someone help me, what is the problem?

[mrf75]

I installed RKM v5 android 5 firmware on Q8L and everything is ok except wifi , any help would be appreciated to fix this issue.

[zzmakii]

Hi, I'm trying to revive my old Q8L, looking for firmware rk3288-eng 4.4.2 KOT49H eng.yangfeihu.20150625.111516 , MEGA ling does not work anymore, and I can't download it from Baidu.
Can anyone point me to this firmware (or even better send it to me via forum or email) please ?

[csori23]

Hi, I'm trying to revive my old Q8L, looking for firmware rk3288-eng 4.4.2 KOT49H eng.yangfeihu.20150625.111516 , MEGA ling does not work anymore, and I can't download it from Baidu.
Can anyone point me to this firmware (or even better send it to me via forum or email) please ?

Hello. Here you find everything.

https://mega.nz/#F!SYg1yAyT!4InwtlsQJl0cQseaUJKeHw