(2018-05-25, 16:56)Matt Devo Wrote:

(2018-05-25, 01:16)sabelstrom Wrote: BTW the hdmi-cable from the Chromebox goes the the HT and a hdmi-cable goes from the HT to the TV, and i hade no sync problem in 16.1 so i think all hardware and cables works fine.

 
your screenshot is calling you a liar, as the audio EDID reflects being connected to the TV, not the AVR/HT

I would try downloading fresh install media and booting in live mode, to ensure all defaults are used, and see if that works once you've verified the HDMI connections. If you still have the problem there, then I'd move your question to the general Linux forum (or LE forums) as A/V sync is a more general Kodi issue specific to your setup, not one specific to the Chromebox (and not one I have any experience with given mine works without sync issues)  

(2018-06-06, 13:38)gaze57 Wrote: Hi!

Reaching out for some help...

Some year ago I successfully turned my Acer CXI Chromebox into standalone Ubuntu/Kodi server using E-Z Setup Script and worked like a charm. Recently, in an effort to fix a suspend issue I thought I should try to update the legacy SeaBios.

Using firmware-util.sh I somehow (don't ask...) managed to flash Asus CN60 Chromebox firmware (Panther) onto my Acer CXI Chromebox (McCloud).

I can boot to recovery mode (saying Panther firmware) but if I try to apply McCloud version of Google recovery image it is not accepted ("Not a ChromeOS image"). Possibly there is a check that prevents you to apply recovery media not matching your firmware ?!

On the other hand if I try to apply Panther recovery media (matching the firmware) it is actually applied but upon reboot it still says that ChromeOS is damaged.

Any ideas on how to unbrick my Acer CXI Chromebox ?


P.S.
Is something like this my only hope,
http://sicarul.com/how-to-un-brick-your-toshiba-chromebook-2-gandof-without-invoking-any-demons/
?

(2018-06-06, 22:27)gaze57 Wrote: Hi Matt!

Thanks for quick reply.

Not sure I follow completely, but you mean something along the lines of a custom recovery image that is identified as a Panther image
(to be able to bypass validation of Panther firmware?) but under the hood it is actually an image containing McCloud recovery media ?

Nevertheless, anything you think can be helpful I'm willing to try. Getting hold of an external programmer is a bit out of my league.

Thanks in advance.

(2018-06-07, 02:49)Matt Devo Wrote:

(2018-06-06, 22:27)gaze57 Wrote: Hi Matt!

Thanks for quick reply.

Not sure I follow completely, but you mean something along the lines of a custom recovery image that is identified as a Panther image
(to be able to bypass validation of Panther firmware?) but under the hood it is actually an image containing McCloud recovery media ?

Nevertheless, anything you think can be helpful I'm willing to try. Getting hold of an external programmer is a bit out of my league.

Thanks in advance.

 yes, a custom panther image that would flash the mccloud firmware while preserving the VPD region.  Shoot me an email at mrchromebox at gmail and I'll give it a go 

(2018-06-16, 05:59)bbsc Wrote: Hi, everybody here. Glad to see the thread allive.
I have a Zako, standalone, UEFI, Libreelec, wired.
Is there a way to control WOL feature (from s3) or to disable it cmpletely?
Thank you in advance.

(2018-06-16, 06:05)Matt Devo Wrote:  unfortunately not, no - that kind of change would require recompiling the firmware 

(2018-06-16, 06:16)bbsc Wrote: Well, then it's interesting if it should wake from any packet or "magic" packet only?
Or it depends on LE settings (default in my case)?

(2018-07-12, 00:16)philberttheduck Wrote: Hi all,

I dusted off my Chromebox to plug into my new TV to upgrade the seaBIOS to 2017 after having it dual boot chromeOS and OpenELEC. Recently decided to reinstall and upgrade to librelec using the script Matt graciously keeps up to date after all these years but I've been getting problems.

Been running into the "your system is repairing itself. Please wait" every time I switch from librelec to chromeOS after using the script to update my old seaBios. It works fine on reboot/shutdown from ChromeOS but any time I go from librelec to chromeOS it forces the repair. Did I do something wrong? Should I just power wash-USB reinstall everything?

(2018-07-13, 18:07)fishypops Wrote: Hi,

I want to take my Asus Chromebox back to the virgin factory settings.  How do I acheive this from the current Libreelec / kodi install situation ?
Thanks.