Posts by Sniperassault

  • [S905X] Help to unbrick the TV box X96

    Quote from ckgambs

    Is there any way I can send one of you guys my android tv box(HK1 p281) and have you upgrade it to the latest firmware possible? I tried very hard to boot it into recovery mode using "Android TV Tools" and then none of the files I tried to update it with seem to be working. Thank you in advance.

    Hi! What you should do is use the "usb_burning_tool" for Amlogic devices and try flashing a ROM that's compatible with your board. (Ideally, you should open the TV box to see which board it uses.) Here's a video from a Brazilian user that explains how to do it. He also provides links to several ROMs to try.In your case, the ideal solution would be to install a ROM that has Android 9 or higher for greater compatibility with streaming apps. If you don't speak English, you'll probably find another tutorial in English, as there are many videos on this topic:

    Tutorial - Atualizando o sistema TV BOX S905W/P281 Links Atualizados para Android TV Tx3,Tx6,MXQ
    Fala galera do Youtube ! Se você tem uma TV Box antiga e quer dar aquele UP esse é o momento, chega de incompatibilidade de app e dores de cabeça pra navegar...
    www.youtube.com

    chewitt Sorry to bother you and for reopening this old thread. I have a doubt and maybe you can help me... I need to install Emuelec on this box. In one of your posts in this thread, you mentioned that I could use the u-boot I currently have, but I would need to change some filenames or scripts in order to match them with LE conventions. I assume you were mainly referring to the Kernel and System files. Besides those, should I modify anything in any of the autoscripts or something from the u-boot through the TTL console? If so, how should I do it? Thanks in advance!

  • [S905X] Help to unbrick the TV box X96

    Hi again Bumerc and thank you for your help!

    Since I don't know exactly how to interrupt u-boot, I decided to do that by the direct way: I measured the vcc pin of the usb port with my multimeter and there is always 5v, whether the box is on or off. The only difference, as I mentioned in the previous post, is that the flash drive's LED turns off when I turn off the box.

  • [S905X] Help to unbrick the TV box X96

    Hi again!

    I've been using the latest "box" stable image this week without issues so far. I would like to know if there is a way to completely turn off the USB ports, because when I turn off the tv box, the USB ports still active. Mainly to save energy and prevent the flash drives from running unnecessarily (since some tend to get warm).

  • [S905X] Help to unbrick the TV box X96

    Thanks Bumerc! I'm going to try the stable build to see if it fixes it. Likewise, if I turn it off, it can be turned on without any problems. As long as that works, I'm happy:)

    Post update: I tried the 12.90.1 and 12.2.0 build and i still have the same bug. I'm reporting this in case this bug is also present on other boxes. I personally can live with that so no problem for me XD.

    Also i noticed that with this u-boot (or maybe because now i use the p281.dtb instead the tx3 mini?) I have more RAM available. Before, it appeared I had 1GB. Now, it shows 2GB.

    What build do you recommend for daily use? I was thinking of giving the box to my dad, since he has an old non-smart LED TV, and it will be useful for him to watch movies and series on it.

  • [S905X] Help to unbrick the TV box X96

    Yeah its works for power on and wake up the box! But there is a bug... When I put the box into suspend mode and go to wake up the box, it gets stuck on a green screen. Kodi continues to work because I can still hear audio from the TV.

    Could it be because I'm using the Nightly build?


    PD: Could you tell me what the Factory_Code was? So I can keep it just in case.

  • [S905X] Help to unbrick the TV box X96

    I had already found the power key code, but I don't know (or didn't understand) how to find the Factory_code. This is how i got the power key code which i assume that is 0x140:

    1046.823517: lirc protocol(nec): scancode = 0x140

    1046.823692: event type EV_MSC(0x04): scancode = 0x140

    1046.823692: event type EV_KEY(0x01) key_down: KEY_POWER(0x0074)

    1046.823692: event type EV_SYN(0x00).

    1046.956640: event type EV_KEY(0x01) key_up: KEY_POWER(0x0074)

    1046.956640: event type EV_SYN(0x00).

  • [S905X] Help to unbrick the TV box X96

    Understood! I'll test them and report back if there are any improvements.

    Last question: I was able to get the remote control to work(If it's usefull for someone the x96max toml file works perfectly) but I'd like to know if it's possible to turn the box on with the power button. I can easily turn it off or suspend with the remote, but I haven't found a way to turn it on or wake up. Not even with the keyboard i can wake up the box. If there is any fix for this let me know, since the only way so far is to unplug the DC cable and plug it again.

  • [S905X] Help to unbrick the TV box X96

    As always, thanks bumerc for your great help!

    I'm using (I think) the original charger. It's 5V 2.2A . I've never thought it would be convenient to power it directly through USB.
    Also, as I mentioned before, this doesn't usually happen all the time. At first, I thought it was because I had to press the Enter key as soon as the Kodi logo appeared, since the times I didn't, it would get stuck on that logo. But after several tests, it turned out to be a coincidence.
    If this happens to me again and i can access the debug logs, i will upload it, in case you know what is causing this issue.

    edit: This happened to me a couple of times, so I was able to get the log file and the crash file. I'm attaching them below in case anyone has any clue as to what the problem might be.

    Log file

    crash file

  • [S905X] Help to unbrick the TV box X96

    Thanks Chewiit for your always clear and concise answers. I'm going to continue experimenting with this OS to see if I can get the remote control to work.

    Quote from chewitt

    It's impossible to guess what might cause Kodi to get stuck on the logo without seeing log files. If there is an issue in the OS it might be visible from the UART output. If there's something in Kodi .. you can enable persistent logging via the LE settings add-on and then check the logs (or look for crash logs) on the next clean boot.

    Yeah, reading in other thread, that was the first thing I did. If the problem occurs again, I'll check the log file to see if there's any indication of the cause. Anyway this doesn't always happen, and it seems random when it does. At first, I thought the cause was a missing input method, but after further testing, I realized it was just a coincidence.

  • [S905X] Help to unbrick the TV box X96

    you guys are f**king amazing!!

    Thank you for not giving up and helping revive this dead box! I am very grateful for your help.

    I'm new in this LE world, so this OS is new to me. I have a few questions I'd like clarification on:

    The system configuration and the app data... Is it saved on the SD or is everything restore every time I restart?

    In the System info menu, It's say that i have 1gb of RAM. This is because is a Fake Box?

    Is the remote control that comes with the box compatible with this OS?

    In the future, if i want to experiment with other Linux-based systems, like Coreelec or Armbian, can I use this u-boot and this .dtb to get them working, or are they completely different worlds?


    PD: If you need me to run any tests or anything so I can contribute to the LE repo or any other member, let me know. It's the least I can do for you.;)


    PD2: Sometimes when i turn on or restart the box it gets stuck on the Kodi Logo. Is there a fix for that or is it normal since it is not a 100% image made for this box?

  • [S905X] Help to unbrick the TV box X96

    Quote from chewitt

    It's harmless to experiment with the p271 dtb file though.

    I will do that! But I have a question about how to do it...


    Should I just use the LibreELEC-AMLGX.aarch64-12.2.0-khadas-vim.img image for this experiment?

    Or should I use the "box" image and install the u-boot 2015.0? If so, as I mentioned earlier, I'm not sure how to edit the .dtb file, as it's different from the "board" images.

    Sorry if this is a silly question, but I'm a bit lost right now.:shy:

  • [S905X] Help to unbrick the TV box X96

    Hi Burmec! Thank you for that explain.

    I don't know if I'm doing something wrong, but I'll try explain you how I did it, and you can tell me if I'm wrong. First, I burned the image you suggested with the tool I always use (LibreElec USB-SD Creator). Then I used AML Boot Card Maker 1.0.1 (I know there are newer versions, but they don't let me burn .bin files) to install the u-boot 2015.0.
    Here comes my trouble: unlike the "board" images, there's no extlinux folder, so I don't know exactly how to add the correct .dtb. I tried creating the extlinux folder with its corresponding file with the .dtb you suggested. I also created the famous “dtb.img” in the root of the SD card, but in both cases, the result is the same in the UART output. From what I can deduce by reading the code the .dtb file has not been found. I've attached the uart output so it's more easier to understand:

    Uart log

    this repeats in a loop.

    PD: I'm also attaching images of the RAM. It has four modules. What caught my attention is that the two on the back of the board have different codes than the one on the other side. I don't know if this is common.


  • [S905X] Help to unbrick the TV box X96

    Hello Everyone! Well i tried the last image that your build, with different .dtb files and the result appers to be pretty much the same: It ends on a Kernel Panic. The new think is there is no more DDR3 chl: Rank0+1 @ 768MHz - FAIL DDR3 chl: Rank0 @ 768MHz - FAIL. I leave attached two uart outputs in case it helps.


    This second is with p212 .dtb