(2017-11-07, 16:09)htpcero Wrote: (2017-11-06, 19:02)P.Kosunen Wrote: (2017-11-06, 09:51)htpcero Wrote: I hope linux users can shed light on how to get either 1.72 or 1.66 firmware installed, without a copy of windows.
I'm planning upgrade with Windows PE USB stick.
https://knowledgebase.macrium.com/displa...scue+media
Macrium Reflect Free Edition has easy wizard for building Windows PE boot stick.
https://docs.microsoft.com/en-us/windows...able-drive
Or you can make one manually if Macrium one does not work.
I tried this.
Win10 PE boots ok from a USB stick on the J4205, and the 1.72 FW update tool can be launched but it fails to detect the LSPCON graphics device; trying to start the upgrade regardless fails with the same error. I tried booting WinPE with the TV receiver connected to either port (DVI+adaptor, and hdmi2.0), same result.
I also tried with the v1.66 installer, same error message: "System Connection Failed"
I tried installing the J4205 graphics drivers to the live PE instance, but that failed. Only thing I can't think of (short of making my HTPC dual boot which would be awful) is trying to get the J4205 drivers into the WinPE ISO
Did you succeed updating your J4205 lspcon firmware to 1.72 via booting from WinPE? Any hint or guidance would be welcome 
FWIW, this may save some ppl some time.
The only way to get the firmware update to work on my J4205 HTPC (BIOS v1.40) was installing Win10 in a spare disk. After the Win10 installation, I added the official drivers from asus. At that point, the firmware update tool could detect the chipset and the upgrade worked (you have to connect your hdmi-2 AVR/TV to the HDMI2 output for detection to work)
Word of advice. I tried both "NUC" versions of 1.72 (AY and BN) - firmware upgrade completes successfully, but video is lost right after each upgrade. Further, restarting Win10 fails continuously (after a while you get a blue screen offering to troubleshoot the system, restart, reinstall, to no avail).
There is a workaround to get a windows login prompt though: restart the system without any video output connected, and connect (hot-plug) to either video port afterwards, most of the time you will be able to get a login prompt and from there all is normal. That way, you can reconfirm the firmware version that got installed and also change it if needed.
I tried the above with newer Intel HD Graphics drivers instead of the ones from ASUS (the one linked in a few posts above), exact same results on windows.
Tried also my main kodi install (Fedora 26/kodi 17.5/kernel 4.13.10) with both versions of fw 1.72. Linux indeed boots and kodi loads (again: so much better than windows), but on the HDMI2 port, xrandr was no longer showing 4K support (max out @ 1080p), and the screen would flicker when playing video about twice a minute.
Then I tried fw1.66, this time windows10 video survived the installation, but I was still getting the same blue screen on Windows restart (could only login after restarting with no monitor connected and then hotplugging). Perhaps that can be fixed (but who cares) - linux worked like a champ as usual on either output.
Bottom line, you might be able to save some time by skipping WinPE and also aiming for FW 1.66. And by staying as far from windows as possible
One reason you may want updated firmware is if you are planning to switch your build to HDMI2.0 once they mainline the intel HDMI patch, hopefully in 4.15. At that point maybe kodi 18 will be out and we will also get hardware-based hevc/10b decoding
