Dear Ray, i’m sorry that, for reasons unknown to me, my discussion has aroused you a certain indignation and disappointed your expectations whatever they may ever be. I cannot feel guilty simply for asking for something, and furthermore as far as i know i haven’t placed any compulsion on anyone. I can only leave the interpretation of your words to common sense, and kindly invite you to a civil and respectful conversation for the sake of the discussion that is being faced. Thank you
Reading through the thread it seems that @kostaman suggested that the vendor supply the CE team with a box to help with providing CE compatibility.
@n34s then made a request to the vendor and the vendor’s response showed that they were not interested in doing so, to which @n34s asked for comment from the team.
Somehow I think that this last element may have potentially given rise to a possible though that @n34s may have expected the team to go and purchase a unit (which was not how I saw it myself) and so came the response @Ray along these possible lines.
Probably just a case of misinterpretation that sometimes just happens, especially when the tone of a voice that is easy to read and understand doesn’t always come across in the same way with text on a screen, which increases the chances of misinterpretation.
1 Like
I don’t know what to think about this but this sentence tripped me off:
If CoreELEC developers need box debugging, the fastest way is that he can get it on AliExpress.
Not sure who made that comment, but it is disrespectful.
Sorry if i go a little OT, but i’d like to congratulate with @Compent cos he’s the right man at the right time. I suppose the nickname is an abbreviation of the word “competent” because i must say that it fits you perfectly 
with respect for others of course.
@Ray i fully understand your disappointment and indeed, if it can make you smile, my reaction was even worse than yours.
I actually replied to their answer, and i must say that i haven’t been very light with’em: i’ve been through a lot for the fact that they put on the market a product that hasn’t been properly tested and that, due to requirements required for obtaining the Google certification (Widevine L1), it’s impossible to fix bugs in a short time because any modification made to the system would entail the need to regain this certification, and i believe that the process lasts approximately 3 months (at least that’s the time i had to wait, from the news of the bug resolution to obtaining the fw with the correction).
Not surprisingly, in the new release they solved the problem in typing the “Q” letter, but they forgot to implement the Storage Access Framework (SAF) and, because of this, it’s not possible to grant write permission on external storage devices, and with a 64Gb ROM this thing in my opinion makes no sense.
Anyway @Ray if you’d paid a little more attention you’d have also mentioned the line before that sentence:
I also want to clarify that i’ve not invented absolutely anything. Those were their words and not mine, kindly a bit of attention 
.
Now, if you don’t mind, i’d like to keep the thread tidy so that i can easily get a feedback regarding the Android kernel version. Thanks for your understanding
1 Like
Ok I misunderstood. I thought it was your sentence. I apologise.
2 Likes
Hi!
How can i restore previous fw? /20190320/ this is important for me. thank you!!
The older version (Android 9) cannot be restored. I tried it via PC and via OTA upgrade. I confirm that after upgrading to Android 10 (KM9PRO) it is not possible to run CoreELEC
1 Like
I have a tried and tested solution. You need to change the Android TV 10 OS to an older version of Android TV 9. Then you will be able to boot CoreELEC. I’m sending a link to IMG and tools. http://kodi.pilsfree.tv/img/androidtv/km9pro2gbddr3v13/
Attention, this IMG is for version km9pro classic v.1.2 - 1.3 (2GB DDR3)
It may throw an error at the end of the conversion. That’s right, it turns off the tool and the AndroidTV 9 OS starts up.
I know the post is almost a year old.
I also have MECOOL KM9 Pro classic (2GB RAM), unfortunately also with AndroidTV 10 and I do not get CoreELEC installed.
Unfortunately the link for AndroidTV 9 in this post no longer works (Not Found). Maybe it is possible to update that or somehow help to downgrade to AndroidTV 9?
Thanks a lot.
Thank you.
The files in the links are from 2019. And also the question is whether this allows downgrade from a higher Android version?
The files in the link here in the thread from Mar '21 were perhaps more recent? Most importantly, a downgrade worked with it.
But I will take a closer look at your links. In one of the links is a description of how such a USB burning tool works. This is important for me, because I don’t know anything about it.
FYI, it’s much easier for fiddling with Android versions to use “Burn_Card_Maker v2.0.2” with which you make a bootable uSD card with android.img on it. It boots and flashes automatically.
(P.S. this program may not work properly on all Win10 versions/machines; in that case use Windows 7 
1 Like
Thanks for the info.
I am using Windows 8.1.
Put the bootable SD card in the powerless box. Then hold down the reset switch of the box with a toothpick and then connect the box to power. Then Android boots and flashes automatically.
Is that correct?
Yes, this is correct, if “bootable uSD card” was made/prepared with Burn Card Maker v2.0.2. Otherwise the box will not boot and start flashing. It must be made with mentioned program. What this program does differently is to first partition uSD card with 2 partitions. On the beginning of the card it makes a 16MB hidden (unallocated) partition, and the rest is then formatted in Fat32. On this second partition then go the files needed for flashing process.
(Btw, what is put on the first, hidden, partition I have no idea
1 Like
I have tried Burn Card Maker v2.0.2 and v2.0.3 and I get the following error message:
L(1041 or 1037)check uboot file after read failed
I have tried two different images (AndroidTV 9).
SD card: Intenso 16GB - freshly formatted.
I am using Window 8.1.
Any idea?
EDIT:
I made a mistake:
“Erase Flash” must have “Force Erasing” selected.
And with “reboot” hook out.
Then no more error message came.
With my MECOOL KM9 Pro Classic I tried a downgrade from AndroidTV 10 to AndroidTV 9 and it didn’t work.
I tried this file: https://androidfilehost.com/?fid=1395089523397954434
And on the Internet I found (I do not remember where): KM9PRO.ATV9.V1.20191211.zip
With Burn Card Maker I wrote the file to a SD card and it was successful.
Under Windows there were two partitions: At the beginning of the card a 16MB hidden (unallocated) partition and the rest then formatted in Fat32.
I then put the SD card into the powerless box. A toothpick was used to press the reset button while connecting the box to power. At the front of the box, the blue LED lit up and blinked from time to time. After about two minutes, I stopped holding down the reset button with the toothpick. The LED remained blue and blinked from time to time.
After about 45 minutes nothing else happened, the screen stayed black. I disconnected the box from power again, removed the SD card and reconnected the box to power. It then started the AndroidTV 10 which was previously on the box with my settings.
I suspect this AndroidTV 10 is blocking a downgrade. On the two files was only the normal AndroidTV 9, but nothing to make the blocking ineffective.
The users here in the forum where such a downgrade was successful, certainly had files that made the blocking ineffective. Unfortunately, the links to these files no longer work (Not Found), for example here in the thread from Mar '21.
Which files do you have on the uSD card after it’s made with Burn Card Maker?
You should have these 3 files:
aml_sdc_burn.ini
aml_sdc_burn.UBOOT
KM9-ATV9.img
If you don’t have them all, then the flashing process cannot start…
1 Like
Yes, these three files are on the SD card.
Then, either your boot-loader got locked with new Android 10 firmware, or files on uSD card are not correct or corrupted.
IIRC, then the only method to revert the box to previous firmware is to shorten relevant pins on the circuit board and use “Amlogic_USB_Burning_Tool”. I’m not aware of any other possibility…