
Firstly I tried to install the driver, with no luck - the box was detected for short periods of time (seconds, during red light), then after initial boot, it was already undetectable (blue light). So as I read here and elsewhere, thought what could be the problem generally. Dismantled it (I'm attaching some pics of the PCB) to look for the answer there (pins for shorting etc.). Meanwhile, decided to check the VID of the device (to search for it on the internet), for witch to happen I had to use Aida64 to look for more detailed info and to be quick and as soon as the device is detected (red light - as unknown device), refreshed the aida64's windows devices tab. For example, my VID value is "USB\VID_2207&PID_320C&REV_0100" and found that there is no driver (library) for that number in the *.ini file of the driver in the version of "RK_DriverAssitant" I downloaded (unknown/unspecified version), then tried with 4.1.1 same - my VID, missing. So I started searching for other versions and came across ver.4.4 which contained the aforementioned VID. And then driver flawlessly installed. So, now it holds on red light and is detected in both "AndroidTool v2.3" and "RKBatchTool v1.8". And now I'm waiting to receive the firmware for it (frmver: 7.1.2 NHG47K/foxluo07121011 - rooted version), from the seller in Gearbest (btw, If you came across that or compatible firmware, share it

P.S. One more thing, until the unit was dismantled (I already knew, about the general problem with the cooling), I removed the aluminium radiator from the CPU (carefully, with butane soldering iron with heat blow tip), cleaned the chip (wasn't easy - the shit is like rock and probably with the same thermal dissipation characteristics

So, I hope someone will find that post useful. I would back then.
Comment