Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
R-TV BOX S10 KODI 17.4 ANDROID 7.1.2 S912 TV BOX FIRMWARE UPDATE 20170920
Collapse
X
-
abdullah.. See the link on my post #25. I am running GT1 on my S10. Apply SC1 with USB burning tool and SC2 via OTA. Remote does not work, but you get the navigation tool bar and notification line. It is can be rooted and makes the S10 very workable. Give it a try.Nvidia Shield (2017 & 2019), A95x Max, WD EX2 NAS
-
Originally posted by cjeman View Postabdullah.. See the link on my post #25. I am running GT1 on my S10. Apply SC1 with USB burning tool and SC2 via OTA. Remote does not work, but you get the navigation tool bar and notification line. It is can be rooted and makes the S10 very workable. Give it a try.
So I´m wondering if somehting can have changed in the latest S10 boxes from a HW perspective or something else ?
As it seems that the latest boxes can only be "patched/unbricked" with the stock rom 171213, the other roms does not work to like the 170722 or 170912.
Comment
-
Originally posted by almirus View Posthere is all compatible firmwares for s10 (3G DDR4) https://yadi.sk/d/2QbDv1vl3NDW45
Comment
-
Originally posted by abdullah View Post
Hi MrPappi,
Please let me know if you manage to get the GT1 firmware working on your R-TV S10. I find the UI of the S10 extremely dull & boring.
Thanks.
I have recently bought the S10 but I really cant upgrade the S10 to either the alfawise build or GT1. Using the burning tool always gives "[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed" it's the same to me,where is wrong?
Comment
-
Originally posted by tht View PostAs for the 20171213 Firmware it loads fine on a 3gb/16gb S10 but never boots.
The only way to make it load is to only use the system.PARTITION and recovery.PARTITION added to the 20170912 Firmware.
Use the Customization Tool and just replace the two file above it will boot fine and seems to run okay, This firmware the 20171213 is not Rooted but that was take care of using SuperSU 2.82 zip file via TWRP.
Other than the way above I have found noway to get the 20171213 to boot it has some other files embedded in the .img file " aml_sdc_burn.UBOOT.ENC , DDR_ENC.USB , meson1_ENC.dtb , UBOOT_ENC.USB " But regardless it seems the bootloader.PARTITION and boot.PARTITION seem to be Hosed.
Comment
-
Originally posted by tht View PostAs for the 20171213 Firmware it loads fine on a 3gb/16gb S10 but never boots.
The only way to make it load is to only use the system.PARTITION and recovery.PARTITION added to the 20170912 Firmware.
Use the Customization Tool and just replace the two file above it will boot fine and seems to run okay, This firmware the 20171213 is not Rooted but that was take care of using SuperSU 2.82 zip file via TWRP.
Other than the way above I have found noway to get the 20171213 to boot it has some other files embedded in the .img file " aml_sdc_burn.UBOOT.ENC , DDR_ENC.USB , meson1_ENC.dtb , UBOOT_ENC.USB " But regardless it seems the bootloader.PARTITION and boot.PARTITION seem to be Hosed.
Comment
-
Suggest you later don't buy the TV box of the company, the shenzhen company in China in order to reduce the quality of your to their complaints, they change on hardware encryption PCB that they cannot use the ota upgrade. You can't root and enter recovery mode. Only one firmware is used to hang the box. Advice from a Chinese player who is deeply hurt.The company changed the PCB of the TV box after National Day last year. It can't be upgraded.
Comment
-
After trying all rom listed in this link: https://yadi.sk/d/2QbDv1vl3NDW45. Here is my conclusion:
1. No other ROM except R_TV_BOX_S10_20171213.img that can be installed to this rom. Even for the earlier-version stock rom, it won't work.
Versions of the burning tool have nothing to do with the successful/ unsuccessful rom flashing.
2. Bootloop caused by installing incompatible rom, is easily fixed by reinstalling this R_TV_BOX_S10_20171213.img rom (as long as your device is detected by the burning tool).
3. I think I agree with yetian that the company might be locking the firmware modification for this box. However not all partition being locked. Logo & system partitions are not locked anyway.
4. So I have tried making some mixing of those partitions (logo & system) taken from another rom. Some of them are working but the rom not really stable except for aml_7.1_s912_q9377-S912_XGO_mac-20171206.
5. Here's the rom that I've modified. http://www.mediafire.com/file/soect5...c-20171206.zip.
6. After using this rom for almost 2 months. I'm quite satisfied with this:
a. It's quite stable
b. it's rooted
c. it has top status bar.
7. Don't do root-related activities that causing modification of the boot.img and recovery.img like installing magisk or twrp. it's causing bootloop. Remember, these partitions, i think, are locked/encrypted.
So for you, who's desperate of replacing stock rom for this locked tv box, please feel free to try this rom.
DO IT AT YOUR OWN RISK!!!
Comment
-
It seems you have the locked/encrypted box. Unfortunately not much options you have in this case. Try this rom instead.
http://freaktab.com/forum/tv-player-...71213-stockrom
Comment
What's Going On
Collapse
There are currently 1880 users online. 2 members and 1878 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment