Sig Posted April 24 Posted April 24 Hi Guys, I was trying to install Armbian in a couple of boxes buit I had no luck. One is a SEI500W from SEI Robotics with AML 905X2 and the other is a Sagecom DIW 585 with AML 905X I followed the process and after trying to boot to recovery they start Andoid tv as normal (just takes more time). In the other hand I was able to run EMUELEC (Gaming emulator) on both devices with an image on SD so I'm assuming the problem is not a block. What do you think? Is there any ideas to try? Thank you in advance! 0 Quote
SteeMan Posted April 24 Posted April 24 What build and instructions are you using? https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus If you are using the above instructions, note the first sentence about having ever run another distro on the box. If so a reinstall of the original android firmware is required to reset the box to a unmodified state (I point this out as you say you have run emuelec on the box - and yes running from sd card counts as running on the box). 1 Quote
Sig Posted April 24 Author Posted April 24 @SteeMan Thank you for your quick answer! I missed that line I'm sorry. I assume Corelec and Emuelec will cause same problem with boot. Not sure how to reinstall firmware , I've only run automatic updates. Any advise to get and install original firmware? 0 Quote
cuker Posted April 25 Posted April 25 Restore from CoreELEC: https://wiki.coreelec.org/coreelec:restore 0 Quote
Sig Posted April 25 Author Posted April 25 @cuker thank you for the tip. I've just tried, but after installing the aml_autoscript suggested on that link the box with Armbian on Sd inserted starts a boot loop. It boot normally to Android TV with no SD card inserted. Any other suggestions will be appreciated. 0 Quote
SteeMan Posted April 25 Posted April 25 @Sig That procedure is a one time this thing. If you pressed the reset button correctly it will have reset the boot loader environment. So remove the SD card and try booting without and SD card (that should be android as normal), then try the Armbian. If it doesn't work, try the reset process again (there is no good way to know if you timed the pressing and holding of the reset button correctly, except through trial and error). ( I generally find holding the reset for about 5 seconds while power is applied is about right, but too long or too short and it won't work as intended) 0 Quote
Sig Posted April 25 Author Posted April 25 @SteeMan Yes i did it that way. Inserted the SD with the fix for boot. It booted, then I powered of and removed SD. After that I Inserted the Armbian SD card but then is when the boot loop appears. So there was no way to boot form any SD card anymore. But still works on Android TV when no SD card is present. Please let me know if I'm doing something wrong. Thank you. 0 Quote
SteeMan Posted May 30 Posted May 30 What image are you using? What uboot are you using? What dtb files have you tried? (per the instructions you should try all compatible dtb files to find the one that works best) 0 Quote
Sig Posted May 30 Author Posted May 30 Thank you @SteeMan. I used a couple of image to try: Armbian_20.10_Arm-64_bullseye_current_5.9.0 , Armbian_community_24.5.0-trunk.474_Aml-s9xx-box_bookworm_current_6.6.28_xfce_desktop.img adn I think I tried Armbian_community_24.5.0-trunk.433_Aml-s9xx-box_jammy_current_6.6.28_cinnamon_desktop.img also. About uboot I have two boxes one is S905 and the other is 905x then I used both u-boot-s905x-s912 and u-boot-s905x2-s922. And for dtb I used the same the box is using when running Emuelec and working . Maybe something different is needed. Let me know if I'm doing something wrong. 0 Quote
SteeMan Posted May 30 Posted May 30 2 minutes ago, Sig said: About uboot I have two boxes one is S905 and the other is 905x then I used both u-boot-s905x-s912 and u-boot-s905x2-s922. That doesn't make sense. Did you type something wrong there? s905 shouldn't use either of those uboots and u-boot-s905x2-s922 doesn't match either of those cpus. 0 Quote
SteeMan Posted May 30 Posted May 30 4 minutes ago, Sig said: And for dtb I used the same the box is using when running Emuelec and working . Maybe something different is needed. As the instructions say, you need to try all compatible dtbs for your cpu. Don't assume something from one os applies to another. 0 Quote
SteeMan Posted May 30 Posted May 30 And finally going back to the original point, the only way to reset the box I would recommend is to reflash a fresh android firmware. I can't speak for the correct working of that coreelec script. 0 Quote
Sig Posted May 30 Author Posted May 30 Thanks again @SteeMan. Which Uboot should I use? My idea is the dtb file is related to hardware so it would work (maybe with some errors) but works no matter the OS is. I will try different dtb per you suggestion. Unfortunately with this android TV there is no way to flash the original firmware because is not available, it is a branded box with andoid TV. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.