Question DS412+ not booting: serial console shows EFI Internal Shell missing boot devices, but EFI partition on internal storage seems intact

[ragnarok]

Do you have image if BIOS for DS412+ ?

If you are asking me, then no. My inventory only covers 209+, 411, 415+, 116, 220j and 1821+...

 

[DSfuchs]

Do you have image if BIOS for DS412+ ?

to be found here, out of our thread:

WeTransfer | Send Large Files Fast

The simple, quick and secure way to send your files around the world without an account. Share your files, photos, and videos today for free.

we.tl

 

[Vitaliy]

Link is expired. Can I use .ROM from here Download Center - download | Synology Inc. ?
This file is different from provided in that link.

 

[DSfuchs]

Der Link ist abgelaufen. Kann ich die .ROM-Datei von hier verwenden: Download Center – Downloads | Synology Inc. ?
Diese Datei unterscheidet sich von der unter dem angegebenen Link bereitgestellten Datei.

NEIN

 

[Vitaliy]

Could you please explain? English if possible

 

[Vitaliy]

A CH341a programmer works just fine. Just make sure it outputs 3.3v and not 5v - some of them have to be voltage fixed…

You are right. Great device to kill chips. Easy to fix.
I ordered W25Q32JVSSIQ from 10Pcs W25Q32BVSIG 25Q32BVSIG W25Q32FVSIG 25Q32FVSIG W25Q32FVSIQ 25Q32FVSIQ W25Q32JVSSIQ 25Q32JVSSIQ 25Q32 SOP-8 FLASH IC - AliExpress 502
and this TZT CH341A CH341B 24 25 Series EEPROM Flash BIOS USB Programmer Module + SOIC8 SOP8 Test Clip For EEPROM 93CXX / 25CXX / 24CXX - AliExpress 502
What would be right procedure to program Bios for this NAS? I never tried to do it. Where do you get images for your devices?

 

[ragnarok]

You are right. Great device to kill chips. Easy to fix.
I ordered W25Q32JVSSIQ from 10Pcs W25Q32BVSIG 25Q32BVSIG W25Q32FVSIG 25Q32FVSIG W25Q32FVSIQ 25Q32FVSIQ W25Q32JVSSIQ 25Q32JVSSIQ 25Q32 SOP-8 FLASH IC - AliExpress 502
and this TZT CH341A CH341B 24 25 Series EEPROM Flash BIOS USB Programmer Module + SOIC8 SOP8 Test Clip For EEPROM 93CXX / 25CXX / 24CXX - AliExpress 502
What would be right procedure to program Bios for this NAS? I never tried to do it. Where do you get images for your devices?

Well, ideally you would get a DS412+ donor bios image from a friend and flash that to the Winbond chip before soldering the Winbond to the board, since the socket IC adapter is far more reliable, than a cheap SOIC8 clip.

I have only been forced to re-flash once - on my DS415+, due to a faulty bios update taking place during a DSM upgrade. It was able to boot, but had no network and disk were only recognized when doing hot-swaps.

From my notes back then, the procedure was

• Acquired the CH341a programmer
• Performed the voltage fix (lift IC pin 28 (VCC) and connect that to the middle pin of the AMS117 voltage regulator (V out), and connect pin 9 (V3) to ASM117 (V in)
• Grabbed an old Windows 7 laptop
• Installed CH341a drivers
• Installed NeoProgrammer v2.2.0.8
• Took apart the DS415+ and connected the SOIC8 clip (successfully, but only after multiple attempts)
• Detected and read out the current, still readable bios
• Grabbed the bios.ROM file contained in the DSM 7.1.1 .pat archive
• Created a new 8MB 0xffh filled hex file
• Pasted all content of bios.ROM from .pat to 0x200000h
• Copied 0x0h:0xfffh from bios of running system to 0x0h
• Saved and programmed that image to the eeprom, and voila - boot successful

Somewhat later I realized, that I could have done this much simpler, by booting from a WinRescue image and loading the isfl drivers and use a modified platform.ini and let the updater utility contained in the .pat do the programming.

I understand, that your current Winbond is toasted, so I reckon a donor image is the way to go. The bios.ROM files in the .pat archives are constructed for the updater utililty, and content is being shifted to new ROM adresses during the update. I know whats being shifted for a DS415+, but not for the DS412+. So a clean flash with a DS412+ bios.ROM from a .pat archive will most likely not work.

As per bios sources: To the extent it is possible, I load the isfl drivers and use the Insyde H2OFFT-Lx64 utility to read them out. If not possible, I ask a friend for a copy ;-)

 

[Vitaliy]

Looks like it is really not easy
Will have to wait for someone who can share image taken from working system or willing to create it.
What people do in case like mine if chip is totally dead (I hope it is chip only)? How often such issue happened?
All voltages seems to be fine so why it is grounded?

 

[Vitaliy]

Anyone?

 

[ragnarok]

Looks like it is really not easy
Will have to wait for someone who can share image taken from working system or willing to create it.
What people do in case like mine if chip is totally dead (I hope it is chip only)? How often such issue happened?
All voltages seems to be fine so why it is grounded?

It is normally the DOMs that break, rather than the eeproms.
Maybe @Elextrixman can spare you a bios image copy from a scrapped DS412+ board?

 

[Vitaliy]

As I mentioned above, the BIOS chip is DEAD 100% as power and other pins are grounded. DOM I could read and write used provided image. BIOS image provided above does not look correct as it is 95% empty. I would appreciate another BIOS image.

 

[ragnarok]

As I mentioned above, the BIOS chip is DEAD 100% as power and other pins are grounded. DOM I could read and write used provided image. BIOS image provided above does not look correct as it is 95% empty. I would appreciate another BIOS image.

Yes, a 95% empty bios image doesn't sound right

 

[Vitaliy]

Received chips and programmer. Programmer is already voltage fixed. Non of programming soft working correctly under Win10. Can read but not write. No problem with WinXP. Something here need support with. Chip size is 4MB but in archive, taken from Synology site, two .rom files by 2MB. I need help here how to correctly write BIOS.

 

[ragnarok]

Received chips and programmer. Programmer is already voltage fixed. Non of programming soft working correctly under Win10. Can read but not write. No problem with WinXP. Something here need support with. Chip size is 4MB but in archive, taken from Synology site, two .rom files by 2MB. I need help here how to correctly write BIOS.

My best guess would be to create a 4MB 0xFFh filled file and paste the content of the bios.ROM file from the .PAT to address 0x200000h and program the Winbond with that.

 

[Vitaliy]

HAPPY NEW YEAR!!!

Do you mean first half of rom will be FFs and second half contain of bios.rom?

 

[ragnarok]

HAPPY NEW YEAR!!!

Do you mean first half of rom will be FFs and second half contain of bios.rom?

Same to you ;-)

And yes

• Let the first half from 0x0h - 0x1FFFFFh be 0xFFh filled, and
• Copy the content of bios.ROM from the .PAT archive to 0x200000h - 0x3FFFFFh

..resulting in a 4.194.304 bytes file, and burn that to the Winbond.

 

[Vitaliy]

I took image provided by Elextrixman. It is 4MB file, where only first half is used, copied bios.rom tp this file from 0x200000. I upload this file to chip and guess what!!! I have beep, solid blue and flashing orange. Time to try assemble it

 

[Vitaliy]

I have access to web interface as well but cannot do anything without disc installed.

 

[ragnarok]

I took image provided by Elextrixman. It is 4MB file, where only first half is used, copied bios.rom tp this file from 0x200000. I upload this file to chip and guess what!!! I have beep, solid blue and flashing orange. Time to try assemble it

That’s awesome ;-) Sounds like it eventually is coming back to life..

 

[Vitaliy]

Confirmed fully operating. File transfer ~2.5 times comparing to Dlink