[ROM] Mod: HK1 X3 / H96 max X3 / VONTAR X3 / Transpeed X3 Air / Bqeel Y8 Max (Amlogic S905X3)

[webipsum]

ath156

I did not succeed.
I'm using a SAMSUNG 2160p 4K (HDMI) TV.
I can enter Armbian (Linux), but only two colors are displayed (magenta and cyan).
As soon as I test on a 1080p TV or Monitor I comment here.
Thankful.

Note: To use a pendrive on the USB 2.0, I had to skip step 5 and delete u-boot.sd. I currently have no sdcard available.

[ath156]

ath156

6. Create a directory “/lib/firmware/brcm” and copy the file “bcm4335c0.hcd” in it

Please, create on SDCARD or HK1BOX?

Tks.

No. Everything you are doing, you are doing it on the sd card/USB stick. NOT to HK1 Box.

[webipsum]

Armbian (Linux) for HK1 Box and Vontar X3

ath156

6. Create a directory “/lib/firmware/brcm” and copy the file “bcm4335c0.hcd” in it

Please, create on SDCARD or HK1BOX?

Tks.

[ath156]

Armbian (Linux) for HK1 Box and Vontar X3

And here is the easy way to install Armbian (Linux) to an sd card for HK1 Box & Vontar X3. Colors of the screen will be fine/correct.

https://mega.nz/file/Rs0D1SyJ#sqAkbg...nODaPK3dzrlImc

https://mega.nz/folder/A5kmDZAC#6t5FO2NUlIr-070EsGtfPA

https://mega.nz/folder/U8lSWZCC#Nn62fFjIK_T_Cn_60IcpIw

Tip1: For HK1 Box & Vontar X3 the only difference is that you use the 2 files of the 2nd folder (instead of those of the 1st)!!!
Tip2: To boot from USB stick (black port):
- Do not delete "u-boot.sd". (you may need it later for an sd card)
- Do not copy "u-boot.ext" that I gave you.
- Copy "u-boot.usb" to your PC and rename it to "u-boot.ext". Now copy this file (u-boot.ext) back to your USB stick.

[webipsum]

... 3. How to install Armbian(Linux) to an sd card. Post#173 https://forum.freaktab.com/forum/tv-...022#post818022 This guide is perfect for H96 max X3. For other clones you may have to omit step 5 and even have some distorted colors in your monitor/TV. ...

ath156

In the case of my HK1 BOX S905X3 with its firmware, is step 5 to be omitted the one in the Armbian installation instructions PDF?

4. ...
5. Copy “u-boot.ext” to your root of your sd card.
6. ...

Tks.

[ath156]

Some links to certain usefull posts in this thread:

1. Install the firmware with an sd card. Post #149 https://forum.freaktab.com/forum/tv-...085#post817085
2. How to Install Coreelec to an sd card. Post #185 https://forum.freaktab.com/forum/tv-...778#post818778
3. How to install Armbian(Linux) to an sd card. Post#173 https://forum.freaktab.com/forum/tv-...022#post818022 This guide is perfect for H96 max X3. For HK1 Box and Vontar X3 please see Post #200.
4. Playstore not updating. Post #95, #96 https://forum.freaktab.com/forum/tv-...041#post815041
5. Backing up a KODI build. Post #78 https://forum.freaktab.com/forum/tv-...523#post814523 When you restore your partitions from a TWRP backup you restore everything (and KODI) but not its KODI data. So having this additional backup you can perfectly restore your KODI build to its previous state.
6. Lowering the temperature. Post #37 https://forum.freaktab.com/forum/tv-...822#post813822
7. Changing the Bootanimation. Post #68 https://forum.freaktab.com/forum/tv-...292#post814292 You can virtually put any bootanimation you like, for example ugoos by the following: https://mega.nz/file/U8NX0SwR#CHqR_y...zt5iOOV5VYUHhw
8. From AOSP to ATV. Post #https://forum.freaktab.com/forum/tv-...933#post818933
9. TASKBAR-Another Navigation Bar. One way that you can set this application is described in Post #54 https://forum.freaktab.com/forum/tv-...194#post814194 Of course you may prefer other options.
10.POWER SHADE-Notification Panel. You have to enable this application and give all the required/asked rights. Post #212 https://forum.freaktab.com/forum/tv-...668#post819668

[ath156]

ath156 56
Thanks for the news!
And to return to the AOSP option, just uninstall the ugoos-atv-20201215 module on Magisk?
This is. Did I understand you correctly?
Hugs.

Yes, according to the following instructions just "uncheck the module in Magisk and reboot":

https://mega.nz/file/Q8twlQBQ#jugSpfuMXR10_SOxHKf9X84v8cJy60ZCK8aLR-2czFY

As I already mentioned before I never tried it myself (I always prefer AOSP versions).
If you try it please report here if everything is OK or not.
Prior to this mod always have a good TWRP backup (just in case ..............)

[webipsum]

ath156 56
Thanks for the news!
And to return to the AOSP option, just uninstall the ugoos-atv-20201215 module on Magisk?
This is. Did I understand you correctly?
Hugs.

[ath156]

For anybody that is using my custom rom (which is AOSP version) and needs the same in ATV version, it seems that this is now possible without the need to make a new installation !!!!

All you have to do is use an ugoos module (as a Magisk module) which will automatically convert your version from AOSP to ATV.

And since you already have Magisk preinstalled all you have to do is use the following module:

https://mega.nz/file/JcchlACK#2r15pP4jJme5_yhXA6ILklW-lrQTO-2j-ubnK-Vz9r0

Important Note: As I never liked ATV versions I have not tested this tranformation by myself, but according to information it has no side effects. If anybody will try it please report about it. You are always advised to have a good TWRP backup before you do any attempt (at least of Boot, System, Vendor and Data partitions).

[ath156]

Your advice for backing up was just the TWRP method, I have these, I followed your advice.
I just wish you had included that people should also backup their images too. Which there was no included advice for properly doing so.
Is there a program/method that you think is best?

OK. Let me try to make very clear some things to you.
1. You do not have to "backup" a firmware image. You either redownload it (from maker's site, from seller's site, from developer's site etc) or just keep a copy of the image file.
2. You do a TWRP backup of a certain firmware especially if you have made some alterations/additions to it (i.e. you installed some applications, you inserted your Google accounts etc or even made some changes to Vendor or System Partitions). So if you try another firmware you can return to your initial/present state by doing a clean install of your original firmware and just restoring Vendor, System and Data partitions with TWRP. If you made no changes to Vendor or System partitions, just restoring the Data partition is enough.
3. Of course you can also use your TWRP backups in other ways. A usual trick is to copy the whole Vendor partition from one firmware to another, but this is not always successfull. If you want to mix+match different partitions from different firmwares you must know very well what you are doing.
4. If your only problem is that you can no longer start Emuelec (from sd card or USB stick I suppose) this is very simple. Just do what you did the 1st time. The easiest way is to install "Terminal Emulator" and write to it "reboot update". After this if you start your TVbox with the sd card inserted it will start with Emuelec by default (or coreelec or linux/armbian etc). But everytime you install another firmware you have to repeat the above procedure.
5. Finally if you want to try my custom firmware properly please do a clean install first. If you want to return back to your original firmware please do also a clean instal to it (and probably restore your TWRP backup there).

[wargex]

Your advice for backing up was just the TWRP method, I have these, I followed your advice.
I just wish you had included that people should also backup their images too. Which there was no included advice for properly doing so.
Is there a program/method that you think is best?

[wargex]

I still have access to another device that hasn't had firmware changes on it. I'm just unsure how to get a backup firmware img thing that I can boot, just for clarification.
Not that I'm still not going to use your firmware in the end. I'd just like to know how to make appropriate changes when necessary.
Do you have any advice on accomplishing this?

[ath156]

I'm sorry, but what is the point of obtaining backups if they're practically useless? I did the SD, it worked. it broke being able to boot from anything but nand, your firmware.
Are you telling me to redo it again and hope its fixed or?

You can not easily jump from one firmware to another one just by a TWRP backup. Otherwise you will end up in a kind of a "merged version" as you call it. You know there is something called as "clean install" of a firmware.
If you want your original firmware just do a clean install of your original image (original/stock firmware) and then use your TWRP backup to restore. Good Luck.

[wargex]

I'm sorry, but what is the point of obtaining backups if they're practically useless? I did the SD, it worked. it broke being able to boot from anything but nand, your firmware.
Are you telling me to redo it again and hope its fixed or?

[ath156]

wargex You cannot properly recover your original firmware by just using TWRP backups to another custom firmware !!! You must install each firmware first and then use TWRP backups to recover a previous state !! Otherwise you may have a mixed system.
So if you don't have a USB-A/USB-A cable to install my firmware (which I think is the best way/option) at least try to do the sd card as I say here (please pay attention to the notes):

https://forum.xda-developers.com/t/rom-mod-hk1-x3-h96-max-x3-vontar-x3-transpeed-x3-air-bqeel-y8-max-amlogic.4157515/page-3#post-84007103