(2015-05-24, 10:29)Soli Wrote: Thanks Matt.
1. Could the script be made to inject a manual typed MAC address when restoring the original firmware?

Quote:2. Does it autogenerate a new MAC address when using a generic firmware

Quote:3. Anything else embedded in the firmware? (Like some unique Chrome serial, that let me take advantage of that 1TB google drive offer)

Quote:4. Can I simply hexedit the firmware with the correct MAC, or is it hidden?

Quote:It might be a good idea to mention that the MAC is embedded in the wiki, since I am probably not the only one that only took backup of the first device. After all, when I upgrade the Chromeboxes somewhere in the future, I plan on restoring them to ChromeOS and hand them over to someone else in the family.

(2015-05-24, 11:36)Namoi Wrote: Hi,

I just wanted to say a big thanks to Matt.
I finally installed OE on my HP Chromebox without any issue. It works great AFAICS but i didn't tried yet to integrate my media library as I am concern with something you guys could help me to sort out.

My medias are stored on an external self powered enclosure pluged via usb. I read some posts on Openelec forum about unmounting usb hdd at shutdown issues (OE not unmounting the drives but just making a sync, OE shutdoqn to fast for the drives to be able to parc themselves for non self powered enclosure i imagine and so on).
Could someone know if there are some issues about this ?

Also, i was wondering what happend if one use suspend intead of real shutdown ? Does the drives stay mounted ?If not, does the shutdown.sh script could be used unmount the hdd or does the suspend mode prevent the script to be executed ?

Thanks as i am a "little" afraid to screw my hdd knowing that i will also pluged them on a windows machine from time to time.

PS: i know i can safely remove the hdd through the Kodi context menu, but it's a pain to do it each time one wants to suspend or shutdown the machine.

thanks again

(2015-05-24, 16:05)megamawax Wrote: Thanks Matt.

I assume, in regards to the PS3 remote, that we're talking this one: http://www.amazon.com/Media-Blu-ray-Remote-Control-Playstation-3/dp/B0050SX9I2/ref=sr_1_1?ie=UTF8&qid=1432476016&sr=8-1&keywords=PS3+remote made by Sony as opposed to some off-brand version?

If anyone else has advice regarding miracast on the chromebox (using the CB as the receiver or the transmitter) or steam streaming on it, I'd love to hear about it. Or if anyone has familiarity with using a Wii remote, I'd be interested in hearing about that too.

Thanks.

(2015-05-24, 18:47)Soli Wrote: Thanks Matt. Last one (hopefully):

Do I understand it correctly that after flashing the standalone firmware, I still have all my device specific information in the firmware (the 16kb vpd), but I will lose all of that once I go back to Chromeos without a real backup?

Quote:If so, would you be able to add a feature to the script to inject the current firmware information from a standalone/dual boot firmware into another backup file? (For us with more than one identical devices, but only took backup of the firmware of the first device)

Quote:And just to be clear and spoonfeeded: if you have several chromeboxes and you have no backup of the firmware, and go the generic route, all your chromeboxes will then end up with the same A0:00:BA:D0:0B:AD MAC address right?

(2015-05-24, 20:03)Soli Wrote: Thanks Matt. This was essential information. Hope you could implement the injection feature in the future. Knowing myself, I'll probably be all over the Skylake Chromebox as soon as it's released..even though I don't really need hardware HEVC decoding for the forseeable future

(2015-05-24, 17:27)Soli Wrote: Celeron 2955u does not support miracast. You'd need at least the 3050u.

(2015-05-24, 20:09)Matt Devo Wrote:

(2015-05-24, 20:03)Soli Wrote: Thanks Matt. This was essential information. Hope you could implement the injection feature in the future. Knowing myself, I'll probably be all over the Skylake Chromebox as soon as it's released..even though I don't really need hardware HEVC decoding for the forseeable future

we'll likely see Braswell boxes before Skylake ones, and I expect those will be the low-cost HEVC-capable x86 platform of choice

(2015-03-18, 17:32)UdoG Wrote:

(2015-03-18, 16:30)Matt Devo Wrote: this has nothing to do with the script, but I'm in a generous mode today.
It's telling you exactly what the issue is - gbb.flags is nonzero, and one of the flags that is set is preventing you from disabling developer mode. Use the script to reset the boot options to the default (which sets gbb.flags to zero), reboot, and you should be able to return to normal/verified boot mode.

YES - thanks a lot. This was my problem! After reset the boot options I was able to disabling the developer mode.

(2015-05-25, 21:39)capm19 Wrote: Hi I have the same prolebama yours, but not how to restore the flags to zero, can you tell me how do I fix