https://mega.nz/#!BKQS2a4K!G5YrKHWUy2HvL2TOqOlLzwn7Sulp7q8i7-h8uVi0uk8
UNIVERSAL V2 - IF TOP DONT WORK
https://mega.nz/#!bphxHJBB!jRhp0AeNa8orSwscFJHJdE7M14_GxQgbHpnbq-21vy8
Step 1 Download & Extract the bundle for your device
You will be getting either a zip or 7z file, personally I would use 7zip to extract these files, you should get a recovery.img and also a folder called TWRP. If you have these two things move on to step 2
Step 2 - Locations
Both SD Card and USB being formatted Fat32 - Some boxes except most s905 you can use the SD card for both TWRP folder and recovery.img, Regardless I use SD only for recovery.img, so drag and drop the recovery.img onto the Fat32 SD Card and Drag and drop the TWRP folder onto the Fat32 USB drive. Done
Step 3 - Formatting before installing.
Connect everything but the power - Connect a real USB mouse/Airmouse to the box due to the regular remote will not work, connect the USB drive and connect the SD Card, Everything but power. Some boxes have a reset button on the side and some the reset button is inside the AV jack, you will feel it, If in the AV jack simply use a toothpick or use a Q Tip with the cotton end removed and slide it in the AV jack and you will feel the button.
HOLD THIS BUTTON AND DO NOT LET GO - At the same time plug it in and keep holding, boxes with physical power button press this now. You will be presented with a blue screen, you will get a read only scren most likely, slide to proceed.
First thing first I always recommend backing up partitions incase something is to go wrong. There are tons of cloned boxes its hard to cover them all. I personally would go to backup. Locate where it says storage, and change from internal to usb otg for USB drive or external sd for your SD Card. Backup all your partitions.
When done, go back. Press the little house button on the screen or the back button until back at the TWRP menu, go to restore, Make sure usb otg or external sd is chosen, wherever you put the TWRP folder, If you are using a box not from me PM me the model and I will confirm what to restore, for example, M8, M8S BCM and AP models, MX3, M10, You can restore all, S912 boxes some are different so PM me to be safe. After I tell you what to restore do so. Let it do its thing. Once done, reboot and enjoy. If it fails by any means. Do not reboot, just go back and choose wipe, format data, type yes press enter. Once done just go back and restore data JUST BY ITSELF so untick everything but data, once finished restore all the other partitions. All done
Enjoy the build - When you first boot my firmware let it sit after it boots for a good minute or two. It will auto load my custom firmware patches and more.
If you are using M8, M8S, M10, MXq you need to follow below -
When you start the TV box. Let it sit a few minutes and first things first. In Android applications click on No Frills CPU - the accelerometer and when it opens click apply and than exit. It is super important with my custom rom to unlock the other 2 CPU Cores and the other 4 GPU Threads. If this does not make sense just go into my apps and look for no frills, same app as on the desktop you will just see the name instead.
NOT EVERY FIRMWARE HAS NO FRILLS - IF NOT DO NOT WORRY ABOUT IT.
i do not own the firmware
credits go to ghostware.
Congrats!
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
MyM8SFinallyWorks said:
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
Click to expand...
Click to collapse
i used a m8s+ rom and the 5.1.1 rom from acemax the only problem is with the m8s+ rom is ethernet dont work so by doing this i got ethernet to work.
Thanks for this link
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
lutty321 said:
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
Click to expand...
Click to collapse
you have to open it and look inside
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Tazosman said:
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Click to expand...
Click to collapse
if you have the recovery.img file on the root of the sd card, toothpick method should take you to TWRP where you can then flash the zip. did you give it some time (with the reset button pressed in)? it can take approx 10 seconds sometimes.
Failed signiture
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Hi
i just tryed this metod but my M8S does not respound anymore(no on light) it seems dat it is deed???Has any body iedea what can i do now?
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Devmau53 said:
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Click to expand...
Click to collapse
Either your download is corrupt, or you are not using TWRP to perform the update.
Has anyone been having random freezing and reboots?
wolfpack64 said:
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Click to expand...
Click to collapse
I also had that problem even though I flashed the square remote zip after the lollipop update. I might have flashed the M8N remote though to be honest and I don't have the box anymore to test more remote patches.
You can try the M8S remote zip from the link below and report back if it worked for you.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s802/eny-acemax-ott/firmware-roms-tools-af/18312-s802-multi-remote-patcher-zips
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
highpoiss said:
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
Click to expand...
Click to collapse
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
MyM8SFinallyWorks said:
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
Click to expand...
Click to collapse
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
highpoiss said:
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
Click to expand...
Click to collapse
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
MyM8SFinallyWorks said:
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
Click to expand...
Click to collapse
Same problem installing acemax firmware over original 4.4 rom wil brick my device brick at first boot.
Help needed M8S ap6360 v1.3 20150921
Can someone make a TRWP backup from this rom ? specially the boot file
Also want to know where to download the M8s+ rom what daniel uses in this treat
Thanks
Hi d4nielr,
Wanted to thank you for the excellent work in compiling this ROM to support m8s app6330.
After trying out various ROMs and in the process bricking my device several times and un-bricking it using the burning tool, I finally came across your forum.
Thanks for the wonderful rom and the installation was a breeze and smooth sailing throughout.
Btw, for the installation I can only use the other most USB port. If I insert the sd card into the inner most usb port, it will take me to the bootloader.
So, for the TEAMWIN logo to appears, I need to put the sd card into the outer most usb port which is located at the back of my m8s unit.
cheers.......
Update.....
Unfortunately, after a cold boot, it doesn't work any longer. Back to kitkat using usb burning tool.
Related
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.
Hello, i have an MX10 Android TV box that is stuck in bootloader. I Initially tired udating the binaries in SU and it was since stuck on the logo screen so i tried to reset through the AV port and found no Rom/ Firmware or what not so I did a complete wipe/ factory reset.. Now I cant seem to find the right software to download to an SD card to get it back up and running. Im stuck:crying:
Liftkit said:
Hello, i have an MX10 Android TV box that is stuck in bootloader...
Click to expand...
Click to collapse
I don't have this device but, the following is only thread that I can locate that just might have a solution for you that's specific to your device. Read through it and you'll even locate the stock Firmware and others. Don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3747746
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
RK Factory Tool
Liftkit said:
Hello, i have an MX10 Android TV box that is stuck in bootloader. I Initially tired udating the binaries in SU and it was since stuck on the logo screen so i tried to reset through the AV port and found no Rom/ Firmware or what not so I did a complete wipe/ factory reset.. Now I cant seem to find the right software to download to an SD card to get it back up and running. Im stuck:crying:
Click to expand...
Click to collapse
Hi,
Flash firmware directly with your PC, it's easy to do that..
Firmware, see on website geekbuying.com/item/MX10-Android-7-1-2-RK3328-4GB-32GB-TV-Box-386668.html?utm_source=freaktab.com&utm_medium=referral&utm_campaign=lily&utm_term=MX10
Good Luck..
Liftkit said:
Hello, i have an MX10 Android TV box that is stuck in bootloader. I Initially tired udating the binaries in SU and it was since stuck on the logo screen so i tried to reset through the AV port and found no Rom/ Firmware or what not so I did a complete wipe/ factory reset.. Now I cant seem to find the right software to download to an SD card to get it back up and running. Im stuck:crying:
Click to expand...
Click to collapse
MX10 TV BOX
Download nougat firmware - https://naijarom.com/mx10-tv-box
download driver - http://ul.to/0bqfz2v9
- Using pc to extract the 2 zip file
- look for SD_Firmware_Tool.exe in the driver extracted folder
- right click run as administrator
- First Choose removable disc select sdcard
- Second select upgrade firmware
- Third select img file from the extracted firmware folder
- click create and wait till success.
- remove sdcard and input to tv box
- use a plastic Lego stick and input to AV (keep it pressed)
- power on tv box and it will enter to recovery page
- flash from sdcard and wait till success
By the way, this firmware is rooted.
Also tested on Android games support wireless game controller and it works.
Conclusion Android 8 firmware not suitable for mx10 tv box.
Hope this helps.
/
severing77 said:
Hi! I am new here and I hope that I choose right spot for posting a thread.
Would someone be kind to help me please?
I have Android Box A95X F3, never had any issue. This morning I made some stupid mistake and I installed Magisk on it which flashed and booted some image. After it finished and I restarted device, system disappeared (dead Android logo is on screen). I tried to wipe data and do factory reset, but every time I press reboot system now it goes back to boot screen with dead Android logo.
Same screen as here appear: https://i.ytimg.com/vi/7E81YRF9ieY/maxresdefault.jpg
Can someone help me and say what should I do?
I have some experience with booting custom ROMs on Android phones, but I am not sure how to fix this on Android Box.
P.S. For booting system external to the device, how can I connect it with my PC? Do I need macho to macho USB cable?
Thanks in advance
Click to expand...
Click to collapse
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
SlamD said:
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
Click to expand...
Click to collapse
Can you give me guide to flash my a95x f3 air!!
SlamD said:
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
Click to expand...
Click to collapse
Hey friends,
Have you got any solution for this.
Because same thing happened with my A95x f3 box. I tried flashing rom by using burning tools but. Some error comes after 1 % process. May be I am flashing wrong image.
Can some please guide me where I can get correct from
Thanks
Good night I hope your team will help me update my box TV Knowing that the device has an
Android version 6.0
Amlogic S905x
P212
I would like to update it to the latest version of android to take advantage of installing applications can you help me
Attached are photos from inside the device
edisondweikat said:
Good night I hope your team will help me update my box TV Knowing that the device has an
Android version 6.0
Amlogic S905x
P212
I would like to update it to the latest version of android to take advantage of installing applications can you help me
Attached are photos from inside the device
Click to expand...
Click to collapse
you can try my custom rom for s905x
aidanmacgregor said:
you can try my custom rom for s905x
Click to expand...
Click to collapse
How to download a ROM and install it on your Xbox TV ??
aidanmacgregor said:
you can try my custom rom for s905x
Click to expand...
Click to collapse
How to download a ROM and install it on your Xbox TV
And knowing the appropriate system for the device, knowing there are many versions upon download
If you don't know your WiFi chipset open you box to find it and download the corresponding rom from Aidan's download repo , if your not sure post pictures of it and it will be identified
jimenis said:
If you don't know your WiFi chipset open you box to find it and download the corresponding rom from Aidan's download repo , if your not sure post pictures of it and it will be identified
Click to expand...
Click to collapse
According to what I saw on the AIDA64 app
It appeared to me that the Wifi Recieves is the type and model of the telink company
Quick Google of the board I see an ap6212 but really you need to open your box and see what's printed on the WiFi chipset . attached is what I found so check against yours and remember you will loose any widevine certification install a new firmware
AP6212
Download the ampak ap6212 version listed and install with usb burn tool https://androidmtk.com/download-amlogic-usb-burning-tool
Remember to uncheck erase bootloader and have a mouse and keyboard just incase your remote won't work
Do I only deselect the erase bootloader .. or is there something else
I hope to explain how to connect the device to the computer and install the ROM
You will load the IMG file first , deselect erase bootloader to connect use a double male usb lead to connect box to pc , try first by simply inserting see if it shows as connected if not locate the recovery button and depress while inserting the usb once connected press start and wait till it completed to 100%. I would try usb port nearest power supply or marked otg ...good luck
jimenis said:
You will load the IMG file first , deselect erase bootloader to connect use a double male usb lead to connect box to pc , try first by simply inserting see if it shows as connected if not locate the recovery button and depress while inserting the usb once connected press start and wait till it completed to 100%. I would try usb port nearest power supply or marked otg ...good luck
Click to expand...
Click to collapse
What is the redeem button and where do I find it ??
As for the program, this is as good as the picture ??
Currently, I will be looking for a dual male usb cable in the store
Use version 2.2.4 of usb burn tool , it will show normal erase use that setting , uncheck erase bootloader have the rom you want loaded by going to file select IMG .never heard redeem button ...
jimenis said:
Use version 2.2.4 of usb burn tool , it will show normal erase use that setting , uncheck erase bootloader have the rom you want loaded by going to file select IMG .never heard redeem button ...
Click to expand...
Click to collapse
When connecting the cable, does it connect automatically, or does it need to press a specific button?
All boxes are different, some just connect others need reset button held down with toothpick and you have to find the correct usb port like advised or you can short the band using a pin .Another way to upgrade is by using burn card maker to create bootable SD from the image once made insert SD card and if your system is booted use a program like terminal emulator to reboot and start the update the command is reboot update
I installed the system on the box TV and it worked perfectly, but the problem was that it did not recognize the remote. What is the solution to control it? I hope you will benefit
Good for the remote maybe somebody else will point you in right direction it involves taking files from old IMG and modifications to kernel , a good solution is to buy a cheap Bluetooth remote or usb remote , some game controllers work or just use a usb keyboard and mouse
Who is the person who will define the old remote control on the system and where to find it
You could try asking the owner of the rom under his thread https://forum.xda-developers.com/t/...date-tv-netflix.4191157/page-37#post-85043449
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Reserved for future shenanigans.
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
effgee said:
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Click to expand...
Click to collapse
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
reza0511 said:
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
Click to expand...
Click to collapse
Regular Air firmware's do not work.
P1-P3 don't work for sure, P4 I don't know but I think not.
I haven't found a photo yet of the P4 hardware.
Try USB Flashtool 4/64 image for X96Max_Plus_Q2 to get your recovery back if such a firmware exists, otherwise try the 4/32. X96 Max Plus Q2 firmware (X96Max_Plus_Q2_20201209-1446.img)
You should be able to get recovery back via flashing one of those images.
X96 Max Plus Q2 firmware is compatible, but if you use the 4/32 image you will only see the half of your storage.
Restoring your TWRP full backup again once you get the max firmware (for twrp) installed will not work unfortunately. Already went through this.
reza0511 said:
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
Click to expand...
Click to collapse
You have a Conceptum box or just the same motherboard?
If you have a Conceptum, you are pretty much ****ed. They wont release the original firmware. You will have to buy a second box and get the image via dd.
I had to buy a second box and get the disk image via dd, and then restore the dd image using dd from within TWRP, overwriting the entire storage with the image. This was using the terminal built into TWRP.
In general, restoring from TWRP doesn't work well on these boxes, especially going from rom to rom as the partition layouts are different and TWRP doesn't handle it correct.
Conversion of the dd image to usb flashable is tricky and I haven't done it.
The person that MAY be able to do such a thing is Ricky ( https://forum.xda-developers.com/t/...w-milestone-donate-version-available.3786991/ ) but I dont know and I don't think there is any point as my dd image has partition layout for 32 gb version, you will lose half your storage unless he can also expand the partition.
Even if you manage to get TWRP back, there will probably be a partition layout difference from the firmware you use to get TWRP on the box, and the TWRP image backup you did. It probably will not work.
You need to get your original firmware, or a dd image of the same box.
You can also use the Slimbox for x96max_plus_q2. I did NOT like Slimbox 12 because it was missing google play and a lot of other things. But it will restore recovery.
solved !!
i save my box by below two steps
1- burning veitnami atv version of x96air img file (google for link )
2- restoring my full twrp via recovery
reza0511 said:
решено !!
Я сохраняю свою коробку, выполнив следующие два шага
1- сжигание veitnami atv версии файла img x96air (гугл для ссылки)
2- восстановление моего полного twrp через рекавери
Click to expand...
Click to collapse
is there a link?
Я уже решил свой вопрос. Спасибо за ваш сайт. Меня интересовало восстановление кирпича x96air_100. Я из Украины.
I have already solved my question. Thank you for your site. I was interested in the restoration of the brick x96air_100. I am from Ukraine.
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Soldiaz said:
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Click to expand...
Click to collapse
Hi.
To get Magisk working, its a bit of a difficult process.
Essentially, Amlogic released / built their kernels with a kernel boot option "skip_initramfs" which magisk needs "want_initramfs" for this to work.
The process is complicated as you must hex edit your boot.img after you have patched it with the Magisk Manager patching method called "Recovery Mode"
4pda where this was discovered - https://4pda.to/forum/index.php?showtopic=774072&st=25020#entry91068157
Video from 4PDA that shows the hex editing process - https://mega.nz/file/pJ1RTChR#b5rLNs-4GF2qlZXKzbL0P5lmAeLLYObJ_w3_Yf8h16U
You can also get the video from the above thread but if I recall you must register to download and unless you know russian its difficult to register there.
A guide I wrote that you can follow along with the video to understand the process - https://rentry.co/wgu9u
Every detail matters, I studied the video for many hours to understand the process, good luck.
My thread about this process here: https://forum.xda-developers.com/t/...ide-to-accompany-video.4320923/#post-85493037
Thanks!!!! Dam looking not that easy .
The Boot img from x96 Air you edited, is it Stock?
Sorry i dont check my mesages here very often.
I don't know which boot image you are talking about, it would be very helpful for you to link me which one specifically I need to answer the question for..
If you are talking about the image for my Air Extreme, it is stock and patched by magisk, and then hex edited for magisk. But I dont know its compatibility for any of the other Air versions.
effgee, just wanted to let you know there is a lot of information and multiple versions of the X96 Air TV Box Firmware available at...
Original Google link... (Vietnamese)
https://www.google.com/url? sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiDtPO9yZj0AhUOXM0KHYnzCIUQFnoECA8QAQ&url=https %3A%2F%2Ftinhte.vn%2Fthread%2Ftong-hop-cac-ban-firmware-cua-android-tv-box-x96- air.3050996%2F&usg=AOvVaw1it1QO7hR_e5XsrdSZH-Rj
Google Translated (English) link...
https://tinhte-vn.translate.goog/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/? _x_tr_sl=vi&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=nui,sc
Direct link... (Vietnamese)
https://tinhte.vn/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/
"X96 Air" search via direct link... (Vietnamese)
https://tinhte.vn/search/333184298/?q=x96+air&o=relevance
Hope they help!
Mr350
Ps... If you have trouble with the Google translation links not working try a Google search for... x96 air tinhte.vn ... that might work then click Translate this page.