morning guys
any builds for my old F2 A95X with a S905X2 please? seems a shame to waste something with 4gb ram lol
cheers and have fun!
morning guys
any builds for my old F2 A95X with a S905X2 please? seems a shame to waste something with 4gb ram lol
cheers and have fun!
me again
I've dug out a Nexbox A95X with 2gb ram, S905X
i tried it with chewitt test build but nothing, any ideas on that one?
thanks again!
S905X boxes should work quite well, S905X2 less so (unless hardware decode disabled) .. "but nothing" doesn't really describe a problem that would could respond to
S905X boxes should work quite well, S905X2 less so (unless hardware decode disabled) .. "but nothing" doesn't really describe a problem that would could respond to
fair comment lol
ok so this box has been 'dead' for over a year, maybe 2, it's used to have one of 'balbes images' burnt to the internal mmc but I 'hosed it' one day with a 'dodgy upgrade'
I downloaded your latest LibreELEC-AMLGX.arm-10.85.0-box.img.gz image, changed the uenv.ini to meson-gxl-s905x-nexbox-a95x.dtb but absolutely nothing on the TV (using the toothpick method)
at least when I tried an image with the F2 box I could see the A95X splashscreen on the TV
yours confused
I'd guess that u-boot has been corrupted or overwritten with an incompatible version. Assuming the eMMC didn't die the easiest way to get things working again would be to use Amlogic burning tool to restore the correct factory image for the box (from XDA forums or similar) so that the box boots (Android). Once it boots again, it's simple to boot an LE image. Alternatively you need to connect a UART cable to the box so we can see the early boot output - but this involves the box being opened and UART cable attaching, which may (or may not) require the UART pins to be soldered to the board first. From the level of technical detail in your posts, I'd suggest the restore-Android approach.
me again
I've dug out a Nexbox A95X with 2gb ram, S905X
i tried it with chewitt test build but nothing, any ideas on that one?
thanks again!
I am running the one of the latest nighties on my A95X. The DTB with the A95x name doesn't work right. Use meson-gxl-s905x-p212.dtb. Assuming you updated the uEnv.ini file, I would suggest that you also make sure you have a android 7x rom installed on the box's MMC using the flash utility before booting. I have seen older Uboot from pre android 7 cause issues too.
the easiest way to get things working again would be to use Amlogic burning tool to restore the correct factory image for the box
well I use arch linux and I tried to use this https://github.com/khadas/utils but it's made for ubuntu and apt won't install on arch so I've drawn a bit of a blank.....I did actually put the original image back on the F2 box but I can't remember what I used lol.......it was defo a command line utility but I've built a new PC and slept a few times since then.......so more
nice day to you sir
edit: right I tried this https://github.com/Stane1983/aml-linux-usb-burn
but I'm getting
Waiting for Amlogic device to be connected...
even though I can see it with lsusb
Bus 005 Device 006: ID 1b8e:c003 Amlogic, Inc. GX-CHIP
bahh!!!!
Display Morewell I use arch linux and I tried to use this https://github.com/khadas/utils but it's made for ubuntu and apt won't install on arch so I've drawn a bit of a blank.....I did actually put the original image back on the F2 box but I can't remember what I used lol.......it was defo a command line utility but I've built a new PC and slept a few times since then.......so more
nice day to you sir
edit: right I tried this https://github.com/Stane1983/aml-linux-usb-burn
but I'm getting
Waiting for Amlogic device to be connected...
even though I can see it with lsusb
Bus 005 Device 006: ID 1b8e:c003 Amlogic, Inc. GX-CHIP
bahh!!!!
Did you push in the button with a tooth pick? If that is not working you might have to open it up and short a couple of traces to force it into recovery mode.
Did you push in the button with a tooth pick? If that is not working you might have to open it up and short a couple of traces to force it into recovery mode.
I got a bit further (by running as sudo) but it is bombing out
Unpacking image [OK]
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
Initializing ddr ........[OK]
Running u-boot ........[OK]
[KO]
I think I need to bin this one now cos it's taking up too much of my time.....
which is probably better spent trying to find an image and dtb that works on the F2 A95X
cheers
I've dug out a Nexbox A95X with 2gb ram, S905X
You must restock 1st.
We do suggest Slimbox or Aidan's customs, but dunno which flasher under Linux (Amlogic USB Burning Tool under Windows, of course).
I moved things into a separate thread to avoid clogging up the main one with box recovery posts.