Hostilian Posted November 7, 2018 Share #1 Posted November 7, 2018 This is a popular board for Xpenology installs, so just as an FYI.. Asrock have finally 'officially' released some of the BIOS that have been floating around the internet for a while.. Feeling a lot more comfortable updating them now - considering the previous reports of bricked boards.. 1.70 (bridging BIOS - need to do this first) 1.80 (latest update) Asrock J3455-ITX Quote Link to comment Share on other sites More sharing options...
cdrvbfhq Posted November 7, 2018 Share #2 Posted November 7, 2018 4 hours ago, Hostilian said: This is a popular board for Xpenology installs, so just as an FYI.. Asrock have finally 'officially' released some of the BIOS that have been floating around the internet for a while.. Feeling a lot more comfortable updating them now - considering the previous reports of bricked boards.. 1.70 (bridging BIOS - need to do this first) 1.80 (latest update) Asrock J3455-ITX Hi, thanks for the update! is there a changelog or something like that somewhere? I couldn't find it on Asrock's website or in the forums. What changed in 1.70 and 1.80 compared to 1.60? Quote Link to comment Share on other sites More sharing options...
T-REX-XP Posted November 7, 2018 Share #3 Posted November 7, 2018 hi. I installed this update. but nothing happened with HW transcoding. So it is still now work. Quote Link to comment Share on other sites More sharing options...
Hostilian Posted November 7, 2018 Author Share #4 Posted November 7, 2018 Not sure, couldn't find it on the site either - though 1.7 was meant deal with Spectre. Both worked without issue on my board.. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 10, 2018 Share #5 Posted November 10, 2018 hey @Hostilian - how do you have transcoding working on your board? seems like you might be the only one on this forum who does! Quote Link to comment Share on other sites More sharing options...
Hostilian Posted November 10, 2018 Author Share #6 Posted November 10, 2018 I don't use transcoding... To be honest, I don't see the point; I stream to whatever I'm watching it on in whatever format it's in.. I'm not saying it's not working, just that I've not tried it.. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 11, 2018 Share #7 Posted November 11, 2018 12 hours ago, Hostilian said: I don't use transcoding... To be honest, I don't see the point; I stream to whatever I'm watching it on in whatever format it's in.. I'm not saying it's not working, just that I've not tried it.. ah so ill assume its not easiest way to tell if transcoding would work is to see if /dev/dri exists Quote Link to comment Share on other sites More sharing options...
Hostilian Posted November 11, 2018 Author Share #8 Posted November 11, 2018 I don't have video station, media server or any other media packages installed on this box - I don't even use it to store movies (that's on my other DS3615 box).. It's a low-power, always-on box for Surveillance station, MP3's, Backups and a temporary file store.. Should that folder exist without any of those packages - and without any attempt to stream anything? It doesn't exist, by the way.. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 12, 2018 Share #9 Posted November 12, 2018 13 hours ago, Hostilian said: I don't have video station, media server or any other media packages installed on this box - I don't even use it to store movies (that's on my other DS3615 box).. It's a low-power, always-on box for Surveillance station, MP3's, Backups and a temporary file store.. Should that folder exist without any of those packages - and without any attempt to stream anything? It doesn't exist, by the way.. yeah it should be there regardless of what is installed. means the gpu is crashing on startup, performance will be pretty lousy and will occasionally get stuck on shutdown/restart. basically there's not one advantage to running the 918 loader unless transcoding is required. Quote Link to comment Share on other sites More sharing options...
fenguoerbian Posted November 12, 2018 Share #10 Posted November 12, 2018 These versions of bios is on-line several days ago. But there seems to be some problem with the bios file. My j3455-itx has bios version 1.60. When I use instant flash of the motherboard, the 1.70 doesn't show up while 1.80 shows up. But the website clearly states one should first update the bios to 1.70 if it's original version is older than that before updating to 1.80. So currently i still haven't update my bios. But on the website, it says bios v1.80 updates the TXE FW version to 3.1.50.2222, which is exact my current verion(my bios version is 1.60, which is not listed on the website of asrock). Quote Link to comment Share on other sites More sharing options...
Hostilian Posted November 12, 2018 Author Share #11 Posted November 12, 2018 21 minutes ago, fenguoerbian said: These versions of bios is on-line several days ago. But there seems to be some problem with the bios file. My j3455-itx has bios version 1.60. When I use instant flash of the motherboard, the 1.70 doesn't show up while 1.80 shows up. But the website clearly states one should first update the bios to 1.70 if it's original version is older than that before updating to 1.80. So currently i still haven't update my bios. But on the website, it says bios v1.80 updates the TXE FW version to 3.1.50.2222, which is exact my current verion(my bios version is 1.60, which is not listed on the website of asrock). Dont use the version that connects to the internet to download the BIOS OR any version that updates within Windows. You'll potentially be left with a Brick.. Always update with a previously downloaded BIOS file, extracted, and use the BIOS utility to select this file for upgrade. I've read many reports of these boards being bricked due to the first two methods. I downloaded 1.7 and flashed that (fine) from 1.40. Then 1.8 and flashed that (fine). Quote Link to comment Share on other sites More sharing options...
deklan Posted November 12, 2018 Share #12 Posted November 12, 2018 Update to 1.8 via USB stick was successfull too (just my picky flatscreen doesn't like the DVI signal anymore, VGA is OK) I've downloaded 1.7 and 1.8, unzipped them to USB stick and flashed from 1.4 to 1.7 and then from 1.7 to 1.8 I can check TXE FW version later at home. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 12, 2018 Share #13 Posted November 12, 2018 (edited) It's not worth it - there's nothing new this bios really provides. In fact - the exact same bios was release back in june for the j3455M. they've just finally got around to updating it for the other j3455 model boards. http://www.asrock.com/mb/Intel/J3455M/?cat=Download&os=BIOS from testing each of the versions on 3 different models with a handful of operating systems - v1.30 is the one i recommend Edited November 12, 2018 by ideasman69 Quote Link to comment Share on other sites More sharing options...
deklan Posted November 16, 2018 Share #14 Posted November 16, 2018 On 11/12/2018 at 10:38 AM, ideasman69 said: from testing each of the versions on 3 different models with a handful of operating systems - v1.30 is the one i recommend Do you also recommend to go back from v1.80 to v1.30 (if downgrade is possible)? Why do you recommend v1.30? Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 16, 2018 Share #15 Posted November 16, 2018 14 minutes ago, deklan said: Do you also recommend to go back from v1.80 to v1.30 (if downgrade is possible)? Why do you recommend v1.30? yeah downgrade is possible. just use afudos.exe on a usb boot disk with DOS (but i have one of these as backup) 1.30 was the last release before all the spectre/meltdown stuff. bios' past this gave unpredictable results in Windows 10 and lowered performance. 1 1 Quote Link to comment Share on other sites More sharing options...
deklan Posted November 16, 2018 Share #16 Posted November 16, 2018 (edited) 12 hours ago, ideasman69 said: yeah downgrade is possible. just use afudos.exe on a usb boot disk with DOS (but i have one of these as backup) Thanks, I will try it. Which afudos version will work? There are a lot of versions out there with different compatibilities (AMIBIOS8, APTIO) and different parameters. Google search failed Update: Update worked fine with AFUDOS 5.07.01 (for Aptio V) using command: afudos APLITX1.30 /X /B /P /N Flashing process took longer than expected but finally everything is fine. Thanks ideasman! Edited November 16, 2018 by deklan Update stepts + result added Quote Link to comment Share on other sites More sharing options...
ed_co Posted November 25, 2018 Share #17 Posted November 25, 2018 (edited) On 11/7/2018 at 9:36 AM, Hostilian said: This is a popular board for Xpenology installs, so just as an FYI.. Asrock J3455-ITX FYI, maybe could be useful for someone thinking about what to get to start a xpenology build. It is so trendy I guess just because it is what DS918+ has, and which people I think doesn't know that this motherboard has, despite is saying celeron, but is just an Atom family processor and not a regular desktop one. That's the reason I didn't get the original DS918+, which I was about to buy (I was coming from the DS1512+), until I realized about the Atom processor, which on top of that is old considering new hardware. Edited November 25, 2018 by ed_co Quote Link to comment Share on other sites More sharing options...
nevusZ Posted January 4, 2019 Share #18 Posted January 4, 2019 On 11/16/2018 at 8:08 AM, ideasman69 said: yeah downgrade is possible. just use afudos.exe on a usb boot disk with DOS (but i have one of these as backup) 1.30 was the last release before all the spectre/meltdown stuff. bios' past this gave unpredictable results in Windows 10 and lowered performance. thanks so I am gonna stay on version 1.30 Quote Link to comment Share on other sites More sharing options...
NicoLarve Posted September 15, 2020 Share #19 Posted September 15, 2020 I wonder how could you have flashed this *UEFI motherboard* with MSDOS. I used to flash motherboard using Freedos, but it is not possible on UEFI hardware anymore. :( What is the trick I am missing here? (I left the windows world since so long, ...) I have the same motherboard with firmware v1.60, and like others, it was impossible for me to upgrade to v1.70 (not seen by flash utility), so I gave up with the idea to upgrade to v1.80. However, I am very interested in downgrading to v1.30. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
NicoLarve Posted September 15, 2020 Share #20 Posted September 15, 2020 More importantly, I have front USB2/USB3 (those from the mobo connectors) that have unstable powering making, for example, keyboard's LEDs to blink! I have other issues with this motherboard, including "CMCI Storm" reported in system logs. These issues are the reasons why I wanted to give a try to more recent firmware versions at first. By the way, with v1.60, I have /dev/dri/ (Debian 10.5 - Linux 4.19). Quote Link to comment Share on other sites More sharing options...
Hostilian Posted September 15, 2020 Author Share #21 Posted September 15, 2020 Copy the bios update files (unzipped) to a FAT32 formatted USB flash drive. Boot your PC into the BIOS - you should have a BIOS updater utility somewhere in the menus. Use it, select your USB drive as the source, choose the update file and that should be it. Let it do it's thing and cross your fingers.. You don't need to boot to DOS on a floppy drive (the run a BIOS updater) nor update from within the OS anymore. Quote Link to comment Share on other sites More sharing options...
NicoLarve Posted September 15, 2020 Share #22 Posted September 15, 2020 (edited) Il y a 3 heures, Hostilian a dit : You don't need to boot to DOS on a floppy drive (the run a BIOS updater) nor update from within the OS anymore. When I do that, I can only see v1.80 proposed by the BIOS updater utility. In the end I cannot upgrade to v1.80 since one have first to install v1.70 beforehand, but it never shows up even when it is the only BIOS file present in the USB stick. I thought that using a DOS bootable stick + afudos.exe would allow me to control what can be done (either to install v1.70+v1.80 or to downgrade to v1.30 as some are suggesting in this thread). Edited September 15, 2020 by NicoLarve Quote Link to comment Share on other sites More sharing options...
Hostilian Posted September 16, 2020 Author Share #23 Posted September 16, 2020 Can only suggest you make sure it's the correct BIOS file and it's unzipped correctly. There are a couple of versions of this board; so make sure you grab the right one. Can't remember exactly, was 18 months ago or more.. Quote Link to comment Share on other sites More sharing options...
NicoLarve Posted September 16, 2020 Share #24 Posted September 16, 2020 Thank you. This is what I did: all of the BIOS I have come from the same page: https://asrock.com/mb/Intel/J3455-ITX/#BIOS I do really have a J3455-ITX board (=lshw= confirmed it). Files have been unzipped of course and are all of the same type, according to =file= command: $ file A* APLITX1.30: Intel serial flash for PCH ROM APLITX1.40: Intel serial flash for PCH ROM APLITX1.70: Intel serial flash for PCH ROM APOITX1.80: Intel serial flash for PCH ROM Only v1.80 is detected by the BIOS. That is why I am interested in afudos.exe and bootable MSDOS. Quote Link to comment Share on other sites More sharing options...
Hostilian Posted September 17, 2020 Author Share #25 Posted September 17, 2020 Have you tried downloading, unzipping and copying 1.70 file - to the flash drive - on a Windows PC? Is it definitely Fat32 file type? Might be worth wiping it and reformatting - in Windows. No idea about Afudos. Mine both worked fine when upgrading within the BIOS. 😕 Quote Link to comment Share on other sites More sharing options...
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.