Offeacy61

It sounds like you're in a tough spot with your x88 box, but there are definitely a few things you can try to unbrick it. Check Power Supply: As you mentioned, the power supply might be outputting 13V, which is not ideal. It's crucial to have a stable 5V supply for the device to boot properly. If you can, try using a different power adapter (5V, 2A) and see if that helps stabilize the boot process. Use a Correct Recovery Image: Make sure you're using the correct image for the box. It seems like you were trying to burn the image directly, but if the process was interrupted, it could leave your internal storage in an inconsistent state. Try downloading the official firmware for your box model from the manufacturer's site (if available) or from trusted forums where users with similar devices share their files. Try the USB Burning Tool: Some boxes like this one can be recovered using a tool like the USB Burning Tool (if it's based on Rockchip). You can try flashing the firmware through USB using the tool while the box is in recovery mode. Here’s a general approach: Download and install the USB Burning Tool. Put your box into MaskROM Mode (this usually involves shorting specific pins or pressing a button while plugging the box into your computer via USB). Connect your device to the PC and use the USB Burning Tool to flash the firmware. Serial Console Output: If you're comfortable with it, connecting a serial console to the box can give you a lot of insight into where things are failing. This could help identify whether it's a hardware or software issue. The serial output could give you error messages that could point to a specific issue (e.g., faulty bootloader or file system corruption). SD Card Recovery: If you can't get it to boot from the internal flash, continue using the SD card with a stable Armbian image. If the internal storage is corrupt, you might still be able to boot and recover your box through the SD card by reinstalling the firmware on the internal storage via the system running off the SD card. If you haven't already, you could also try reaching out to the manufacturer or seller for support, as they might be able to help you with the recovery process. But if that’s not an option, digging into the serial console is definitely your best bet. Good luck! Hopefully, you'll be able to get your device back up and running soon.

Thanks for the detailed description! Very useful post, especially for those who are just starting to tinker with Armbian on TV boxes. I had a similar situation with another S905X3 box - neither Wi-Fi nor Bluetooth worked, and there was trouble with HDMI audio. Special thanks for the advice on disabling unattended-upgrades and systemd-networkd-wait-online, I just encountered problems with long loading, now I understand where the legs are growing from. Regarding USB audio - an excellent solution, I didn't even know that it was so easy to bypass the lack of built-in sound. I will try with a similar adapter. If you have a chance, tell me later whether you managed to set up Wi-Fi via a USB adapter or in another way. And I wonder if you tried other window environments besides XFCE? LXQt, for example? In any case - a great guide, thanks for your work!

It sounds like you're having a bit of a tough time getting that LCD screen to work with your Orange Pi. The fact that the manufacturer only provides drivers for Arduino and RP2040 is definitely limiting, but there are a few things you can try to get it up and running. Check the display's controller chip: The key to getting an LCD screen to work with any board is knowing what controller chip the screen uses. Often, drivers are not provided for specific boards, but if you can identify the chip (it could be something like an ILI9341, ST7789, etc.), you can search for libraries or drivers that support it on Linux-based systems like your Orange Pi. Linux Framebuffer or SPI Libraries: If it’s an SPI-based LCD, you might be able to use Linux framebuffer support or libraries like fbcp (framebuffer copy) or fbtft (framebuffer to TFT) which are often used for connecting LCDs to Raspberry Pi-like devices. These libraries could potentially work with your Orange Pi if the wiring is correct. Using Klipper with an LCD: Since you're trying to use this for a Klipper setup, check if there are any custom firmware or configurations in the Klipper community for connecting LCD screens to Orange Pi devices. Sometimes, other users will have created patches or drivers specifically for non-standard setups. Try finding alternative drivers: Even if the GitHub repository you found didn’t work, check if there are forks or alternative branches of that repository. It’s also worth checking out other forums or user groups that focus on 3D printing or Orange Pi setups. You might find someone who has already solved this issue. Wiring Check: Make sure that your wiring matches the expected configuration for your board. Sometimes, the issue can be as simple as a misconnected pin. Hope this helps! Let me know what controller the screen uses or if you need help with any specific steps.