Windows should detect the dom as an normal USB Stick - you should see it in the device manager. I have used linux on my raspberry to make an image. I used the "dd" (disk dump) tool of linux as described here: How to use dd in Linux without destroying your disk
You are correct, I can see it as a drive station in device manager. Added a drive letter with diskpart and can see the files and made the image.
I see three partitions on the bios chip, two are filled with files. I can also download Bios files from Synology's website (see attachment after extracting with 7-zip).
Can you please indicate the files that need to be checked, replaced or corrected (e.g. only the EFI files)?
I have exchanged the following files with files from Synology website.
On the 94 MB partition:
zImage
rd.gz
Grub_cksum.syno
Checksum.syno
On the 16 MB partition:
zImage
rd.gz
GRUB_VER
I have the impression that the USB DOM is not read (no reading, no change).
So still no boat : , please advice?
The disk is visable in Chip Genius (VID and PID not correct). But in device manager the ID is still correct (see attachment)
So I tried to repair the link of UT165 chip e.g. with the USBest UT MPTool (UT.1.65.17.0) on a XP 32bit PC or with the USbest UT165 rescue v1.0.3.1 format tool. The rescue tool did not find the device (device not found, please insert device, at XP and W11). Further with US Best UT MPTool the Synology flash disk is visable and can be scanned.
Next step format the USB. If I format the disk in Windows (CDM > diskpart > list vol > sel vol 10 > format fs=fat) it does not update to VID F400 and PID F400. Tha advice is with RMPrepUSB
@all: I managed it to repair my Dom, the Synology is booting again. (YES!)
It´s definitly the UT165 Chip which needs to be replaced (see my Post above about compatibilty, revisions and Flash Chips). It stops working on USB 2.0 and only works on USB1.1 - on Linux (and Windows) it´s fine, the DS412+ needs definitly USB2.0. I suggest to also replace the flash chip because it´s aging, but it seems it´s only neccessary if the new UT165 revision it not regognizing the old flash chip. For this you need good soldering skills.
Perhaps an replacement USB Dom is also fine, when it´s configurable for VID and PID.
@Nats Once again: USE LINUX and dd (the third time!). You also need to replace the UT165 chip - without replacing you dont have a chance, it´s an hardware defect! Windows recognizes your USB DOM, the Synology not, same as here. You CANNOT REPAIR the USB Dom by replacing the files or Reformat it with the tools mentioned.
I am not sure, but I guess you have already destroyed the contents of your Dom (you wrote: "format the USB") - there is more than only the files on it - there is also a boot loader and at least one more partition. Once again: use Linux, use dd to make an image of the working USB Dom in 1.1 Mode! Synology also uses Linux and the file-Systems are not compatible.
When your are in luck, it´s not too late, make an image, replace the chip, try your luck.
But please: Read the posts, everything what you need is described in this Thread.
Sebastian
-- post merged: --
Hi again,
here is an update about the hardware configuration(s) and the used Software versions.
In all cases the UT165 must be fully ok (=already replaced), working also in USB2 Mode!
1. Original Hardware (on my DOM): UT165 Rev. A0A, Flash Chip: Samsung K9F1G08U0D
confirmed: UT165_rescue_v1.0.3.1 for firmware update/recovery, UT165_1.65.17.0 for configuring
2. replaced UT165 with Rev A1B, replaced Flash Chip with Samsung K9F8G08U0M (Pin compatible)
confirmed: USBest_URescue_v1.3.0.71 for firmware update/recovery, UT165_V1.65.30.0 for configuring
3. replaced UT165 with Rev A1B, original Flash Chip: Samsung K9F1G08U0D
UT165_rescue_v1.0.3.1 does NOT recognize the UT165 Rev A1B and/or the flash chip.
perhaps someone could give the newer versions (USBest_URescue_v1.3.0.71, UT165_V1.65.30.0) a try.
Thanks for the clear explanation. I found two models of the UT148-L48 chip, but I'm not sure I can use them. Because it's unclear to me how to link this to the compatibility list you posted.
One Amazon and one on Aliexpress.
I have an old DS412+ with blinking blue LED problem too.
Connected my PC to the serial port and got the message:
[...] Booting from EFI Internal Shell [Fv(30D9ED01-38D2-418A-90D5-C561750BF80F)/FvFile(C57AD6B7-0515-40A8-9D21-551652854E37)]
EFI Shell version 2.30 [1.0]
Current running mode 1.1.2
map: Cannot find required map name.
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell>
Next I attached this little DOM unit with its mini USB to my Raspberry Pi and was able to save the contents of both partitions using "dd", with speed of 12....13MB/s. Mounted the 2 images, both seem ok.
I assume have the same problem as Sebastian, and need to replace the UT165, rev A0A.
But... where can I buy such a chip?
Google hardly finds anything :-(
I plan to replace the UT165 A0A with exactly the same type.
Content of the (big) flash chip seems ok, expecting that I don't need to replace that one as well.
So, in this specific case, just replace the UT165 chip, nothing else?
@Nats that's a disapointment. Maybe you can order a compatible flash chip as well.
For me, this adventure has ended unexpectedly:
When placing back the little PCB, I have shifted it 1 position wrongly (no poka yoke, the connectors don't protect you against it, but its is visible). Now when I power op the nas the blue LED flashes very quickly for some seconds and then it stops. Fans are not running anymore, serial port is silent. Seems like I have broken something additionally. I give up now, this is taking too much time, energy and money than this old DS412+ is actually worth.
It was interesting though, thank you all for that.
I ordered the UT165 at Amazon as well, in the rare case I do get the intended A0A version in a few weeks time, I will let you know.
Either because several buyers have complained or due to pure luck, I’ve received the older A0A version from the mentioned Amazon seller. After replacing the defective UT165 with a new one, the DOM enumerated as Synology DiskStation F400/F400 with USB 2.0 speed and my DS1513+ booted up normally.
So in this best case scenario no software tools are needed.
@all: I managed it to repair my Dom, the Synology is booting again. (YES!)
It´s definitly the UT165 Chip which needs to be replaced (see my Post above about compatibilty, revisions and Flash Chips). It stops working on USB 2.0 and only works on USB1.1 - on Linux (and Windows) it´s fine, the DS412+ needs definitly USB2.0. I suggest to also replace the flash chip because it´s aging, but it seems it´s only neccessary if the new UT165 revision it not regognizing the old flash chip. For this you need good soldering skills.
Perhaps an replacement USB Dom is also fine, when it´s configurable for VID and PID.
@Nats Once again: USE LINUX and dd (the third time!). You also need to replace the UT165 chip - without replacing you dont have a chance, it´s an hardware defect! Windows recognizes your USB DOM, the Synology not, same as here. You CANNOT REPAIR the USB Dom by replacing the files or Reformat it with the tools mentioned.
I am not sure, but I guess you have already destroyed the contents of your Dom (you wrote: "format the USB") - there is more than only the files on it - there is also a boot loader and at least one more partition. Once again: use Linux, use dd to make an image of the working USB Dom in 1.1 Mode! Synology also uses Linux and the file-Systems are not compatible.
When your are in luck, it´s not too late, make an image, replace the chip, try your luck.
But please: Read the posts, everything what you need is described in this Thread.
Sebastian
-- post merged: --
Hi again,
here is an update about the hardware configuration(s) and the used Software versions.
In all cases the UT165 must be fully ok (=already replaced), working also in USB2 Mode!
1. Original Hardware (on my DOM): UT165 Rev. A0A, Flash Chip: Samsung K9F1G08U0D
confirmed: UT165_rescue_v1.0.3.1 for firmware update/recovery, UT165_1.65.17.0 for configuring
2. replaced UT165 with Rev A1B, replaced Flash Chip with Samsung K9F8G08U0M (Pin compatible)
confirmed: USBest_URescue_v1.3.0.71 for firmware update/recovery, UT165_V1.65.30.0 for configuring
3. replaced UT165 with Rev A1B, original Flash Chip: Samsung K9F1G08U0D
UT165_rescue_v1.0.3.1 does NOT recognize the UT165 Rev A1B and/or the flash chip.
perhaps someone could give the newer versions (USBest_URescue_v1.3.0.71, UT165_V1.65.30.0) a try.
You can us USBEST, or even PHISON for the controller. Replace the controller fixes the DOM issue on these. Also can buy USB FLASH DOMS on ebay for $5. Just have to change the pid/vid to 400. And you're good to go with a new Flash DRIVE DOM.
Hello everyone. I found this forum and thread through a Google search. I had this same problem with our DS412+ not booting. After it did a recent update to DSM 6.2.4-25556 Update 7 it failed to boot. After reading and re-reading all of the posts made in this thread I decided to attempt the repair. I am a machinist by trade, and not an electrical technician. I possess less than a basic knowledge in this realm; and have just enough soldering experience to be dangerous! However, our DS412+ had literally, a decade's worth of files, documents, photos, database files, etc., contained on it. So, I decided it was a worth a shot to retrieve 10 years worth of data. I found the USBEST UT165-L48 chip from a seller on eBay here: 2PCS UT165-L48 LQFP48 USBEST | eBay and after messaging them explaining I needed the REV A0A version of the chip, they said to include that message when ordering and they would make sure that version would be shipped - I received the A0A version chip. I did copy the disk Flash image with a Raspberry as Sebastian had instructed in his post (just in case), removed the original chip, and soldered the new one back in place. Put everything back together and it booted up! Did not need to use any other software tools or procedures, just replaced the UT165 chip and it worked. Thank God! All the data was there. I would like to thank everyone who posted and contributed to this thread, but most of all to our Lord Jesus Christ for allowing this to happen!
, please advice?
