loudsubz

4 hours ago, Mike Noonan said:

I keep getting "Match device type failed, stop running!"

Any ideas?

 

try pressing the switch button first then upgrade

12 hours ago, Amr said:

HYG: On a Windows PC/Laptop:
1)Install Rockchip_DriverAssitant_v5.1.1

2)Install RKDevTool_Release_v2.79

3)In RKDevTool open config file change language to 2, [Language] Selected=2, save file

4)Grap a Data Micro USB Cable, not power one, make sure of this to have successful flashing

5)Open RKDevTool, connect your T3 screen USB to computer while putting it in Flash Mode, for TT u hit Power with volume up while plugging in the USB, for wall I think u hit reset while plugging in the USB to laptop or PC

6)It should show one device connected!

7)U go to Upgrade firmware tab, Use "Firmware" to load the image, then "Upgrade" to write the image to T3

8]It should show progress, wait till its 100% complete, and in the screen if all good it will say all is good, now the screen will be rebooted and u have ur T3 back!

9)Update to your latest OS3 release!

Google the programs, download and install, use this for T3 image

https://mega.nz/file/gaJl1IrY#pGEN1sIxxyL9v8hXQx9lbNlyZ4rVfHAXBBCcOE1rpMY

You will thank me later, I have a PayPal if you want to donate  as I had just lost a cheap source of bricked screens that I bought over the past year!

 

Appreciate that write up.

It does work well. Mt only question is do you have access to the older firmware's or know how to save them from a working T3? After restoring I had to use C4 image updater tool to roll back to 2.9.1 as thats what this particular system was running on. Not a deal breaker just extra steps.

The only other note I would add is I had to press the "switch" button in the firmware tool as I was getting an error trying to upload every time.

15 hours ago, AK1 said:

I agree with all of the above.  The issue remans is Ari should have disclosed this issue on the Epic web site or via email to his licensees given the known severity of the outcome and the amount of time wasted to get back to an "unhacked" controller state. It makes no sense to expect a Dealer doing what should be a business-as-usual upgrade to visit this forum, dealer forums or the dealer KB . 

I agree it would be nice for sure, and thinking from a business standpoint it should be standard practice, but even with other manufacturers a lot of times you have to go searching for the answers, it's not always readily available. That does't make this right I'm just pointing out. Ive had issues with other devices where some support guys werent even aware within their own company that there was a problem with a firmware on certai devices.

Ari, do you plan to have a new updated driver available on your website anytime soon or is the fix posted above currently all that will be available for the next little while?

Been following this thread but didn't feel compelled to post until now.

I had the same issue happen with mine (hc800) running latest driver, went from 3.1.0 to 3.1.1. but only after I purposefully updated it after talking to Ari, getting feedback and troubleshooting on my own controller. Around the beginning of Jan I heard Jeremy making comments on the facebook group about the issue and since I had not heard anything reached out to Ari to see if he had any info, which he did not until he tried the update himself and found the issue and correct it with a patch right away.

Now I can relate to AK1 being in a jam, running circles etc to get a controller back to optimum running condition and then being upset about the whole process, on the other hand like Ari mentioned it only affected connectivity with composer pro so at that point I would have done some searching on the KB and FB/Online forums for answers.

Theres even a post on the official forums where Ari mentions:

We are aware of the issue, I provided Chris with a simple command which can be run on the controller to fix the issue, which is due to a bug in our driver which we've identified. Thanks for the heads-up Jeremy!

Ive had catastrophic failures when doing updates with C4, so this kind of issue is nothing new nor phases me anymore, as a technician/programmer you get used to it and figure out all the tips and tricks to get a system back up and running asap (image update tool etc)