Unbrick Synology DS918+
Posted by superchromix
|
Re: Unbrick Synology DS918+ June 09, 2023 05:01AM |
Registered: 1 year ago Posts: 15 |
|
Re: Unbrick Synology DS918+ June 10, 2023 06:59AM |
Registered: 5 months ago Posts: 2 |
Are you sure you're flashing the chip correctly?
Yes. First I've deleted the chip and verify it. Later I wrote the chip and verified with the software itself. Later I've read the chip and save in a file and compare the both files having clear that the bios is the same like I've writed.
the strange is after the first try to boot the NAS If I read the chip, the content always it's different than the wrote before.
Did you remove the chip from the board to flash it? Which programmer are you using?
At the beginning yes because using the CH431 programmer always have problems on verification, but later I've soldered and do it direclty in the mainboard with the software NeoProgrammer_2.2.0.8_from_4pda and AsProgrammer_2.0.3a, both works perfectly.
During boot, are you watching the output on the UART serial port?
During the boot I not see anything on the serial port. Only if I remove the memory ram in that case I see something like "Memory training fail, In a Dead Loop: Acting...". if I plug again the memory then not shows anything.
I've seen in the forum something about this, I need to check it but I'm open to some sugeriments...
Yes. First I've deleted the chip and verify it. Later I wrote the chip and verified with the software itself. Later I've read the chip and save in a file and compare the both files having clear that the bios is the same like I've writed.
the strange is after the first try to boot the NAS If I read the chip, the content always it's different than the wrote before.
Did you remove the chip from the board to flash it? Which programmer are you using?
At the beginning yes because using the CH431 programmer always have problems on verification, but later I've soldered and do it direclty in the mainboard with the software NeoProgrammer_2.2.0.8_from_4pda and AsProgrammer_2.0.3a, both works perfectly.
During boot, are you watching the output on the UART serial port?
During the boot I not see anything on the serial port. Only if I remove the memory ram in that case I see something like "Memory training fail, In a Dead Loop: Acting...". if I plug again the memory then not shows anything.
I've seen in the forum something about this, I need to check it but I'm open to some sugeriments...
|
Re: Unbrick Synology DS918+ June 10, 2023 07:26AM |
Registered: 1 year ago Posts: 15 |
|
SteveM
Re: Unbrick Synology DS918+ July 21, 2023 10:28AM |
Afternoon guys - just wanted to update you on my adventures as per the above. Had the exact same issue as above, only my DS918 would occasionally boot. Say one time in thirty ish, it would progress from flashing blue light to solid and beep, and then be absolutely fine for weeks at a time! However, the reboot or a power issue killed it again.
I used the CH341 as per above along with a SOIC clip, read the chip twice, extracted the bios.rom from the PAT files (only the ones before 7.1 will open in 7ZIP I think) and followed all of the above. However, no joy when trying to boot, same situation. However, after 3/4 retries, the Winbond chip seemed to go faulty and would have read/write errors.
Decided to roll the dice on a whole £5 worth of replacement Winbond chip, flashed it, then replaced it for my funky one. And just like superchromix, I was blown away that it now is absolutely fine again. Boots just fine every time so far, and it's been rebooted a lot!
So there you go, folks... If you are desparate, replace the Winbond. It's like 5 mins to flash, 2 mins of careful soldering and £5 to try, so give it a go!
Huge thanks to everybody above for their feedback and for basically getting me to this point. Awesome work guys.
I used the CH341 as per above along with a SOIC clip, read the chip twice, extracted the bios.rom from the PAT files (only the ones before 7.1 will open in 7ZIP I think) and followed all of the above. However, no joy when trying to boot, same situation. However, after 3/4 retries, the Winbond chip seemed to go faulty and would have read/write errors.
Decided to roll the dice on a whole £5 worth of replacement Winbond chip, flashed it, then replaced it for my funky one. And just like superchromix, I was blown away that it now is absolutely fine again. Boots just fine every time so far, and it's been rebooted a lot!
So there you go, folks... If you are desparate, replace the Winbond. It's like 5 mins to flash, 2 mins of careful soldering and £5 to try, so give it a go!
Huge thanks to everybody above for their feedback and for basically getting me to this point. Awesome work guys.
|
Re: Unbrick Synology DS918+ August 01, 2023 03:44AM |
Registered: 4 months ago Posts: 1 |
Good day everyone,
I managed to flash the chip through your advice. However, I was too quick to flash the chip right away with the bios file from Synology. I didn't think about modifying the file with a hex editor.
Do any of you have the relevant information where to start and end the file?
Thank you very much in advance for your answers.
I managed to flash the chip through your advice. However, I was too quick to flash the chip right away with the bios file from Synology. I didn't think about modifying the file with a hex editor.
Do any of you have the relevant information where to start and end the file?
Thank you very much in advance for your answers.
|
Re: Unbrick Synology DS918+ August 01, 2023 05:41AM |
Registered: 1 year ago Posts: 15 |
|
JWBR
Re: Unbrick Synology DS918+ August 02, 2023 02:30AM |
|
Re: Unbrick Synology DS918+ September 17, 2023 08:19PM |
Registered: 2 months ago Posts: 1 |
|
ravic
Re: Unbrick Synology DS918+ October 11, 2023 10:23PM |
I tried to unbrick by DS918+ but unsuccessful so far. Good instructions by PH3. I am able to read/write my bios. Then I connected console to see what is going on.
Seems like my NAS hangs right after booting SMP configuration.
Not sure what is causing this. Started happening right after I tried to upgrade to DSM 7.2
Seems like my NAS hangs right after booting SMP configuration.
Not sure what is causing this. Started happening right after I tried to upgrade to DSM 7.2
GNU GRUB version 2.00
Press "CTRL-C" for boot menu or it boots automatically in 0s.
Booting `SYNOLOGY_2'
Checking file [/zImage]...Passed.
Checking file [/rd.gz]...Passed.
Serial: 18C0PDN161909
Custom Serial: Empty or invalid checksum.
MAC1: 001132a1b95f
MAC2: 001132a1b960
MAC3: Empty or invalid checksum.
MAC4: Empty or invalid checksum.
MAC5: Empty or invalid checksum.
MAC6: Empty or invalid checksum.
MAC7: Empty or invalid checksum.
MAC8: Empty or invalid checksum.
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.302+ (root@build7) (gcc version 12.2.0 (GCC) ) #69057 SMP Sat Sep 23 21:44:10 CST 2023
[ 0.000000] Command line: root=/dev/md0 earlyprintk=apl console=ttyS2,115200n8 ihd_num=4 netif_num=2 HddHotplug=1 SataPortMap=23 sata_remap=0>2:1>3:2>0:3>1 syno_hw_version=DS918+ vender_format_version=2 syno_hdd_detect=18,179,176,175 syno_hdd_enable=21,20,19,9 syno_usb_vbus_gpio=13@0000:00:15.0@1,11@0000:00:15.0@2 sn=18C0PDN161909 macs=001132a1b95f,001132a1b960
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] x86/fpu: xstate_offset[3]: 960, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 1024, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
[ 0.000000] x86/fpu: Enabled xstate features 0x1b, context size is 1088 bytes, using 'standard' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x0000000000085fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000086000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000010000000-0x0000000012150fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000012151000-0x0000000067c17fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000067c18000-0x0000000067c18fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000067c19000-0x0000000067c42fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000067c43000-0x0000000067c7dfff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000067c7e000-0x0000000068c7dfff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000068c7e000-0x000000007822efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007822f000-0x000000007aebefff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007aebf000-0x000000007afbefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007afbf000-0x000000007affefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000007afff000-0x000000007affffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007b000000-0x000000007fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000d3709000-0x00000000d370afff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000017fffffff] usable
[ 0.000000] bootconsole [earlyser0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] extended physical RAM map:
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000059000-0x0000000000085fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000000086000-0x00000000000fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x0000000001ddc5af] usable
[ 0.000000] reserve setup_data: [mem 0x0000000001ddc5b0-0x0000000001ddc5bf] usable
[ 0.000000] reserve setup_data: [mem 0x0000000001ddc5c0-0x000000000fffffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000010000000-0x0000000012150fff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000012151000-0x0000000067c17fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000067c18000-0x0000000067c18fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000067c19000-0x0000000067c42fff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000067c43000-0x0000000067c7dfff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000067c7e000-0x0000000068c7dfff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000068c7e000-0x000000007822efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000007822f000-0x000000007aebefff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000007aebf000-0x000000007afbefff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000007afbf000-0x000000007affefff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000007afff000-0x000000007affffff] usable
[ 0.000000] reserve setup_data: [mem 0x000000007b000000-0x000000007fffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000d3709000-0x00000000d370afff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000017fffffff] usable
[ 0.000000] efi: EFI v2.50 by INSYDE Corp.
[ 0.000000] efi: ACPI 2.0=0x7affe014 SMBIOS=0x78757000 SMBIOS 3.0=0x78755000
[ 0.000000] SMBIOS 3.0.0 present.
[ 0.000000] Kernel/User page tables isolation: disabled
[ 0.000000] e820: last_pfn = 0x180000 max_arch_pfn = 0x400000000
[ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC
[ 0.000000] e820: last_pfn = 0x7b000 max_arch_pfn = 0x400000000
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] RAMDISK: [mem 0x37564000-0x37aa9fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x000000007AFFE014 000024 (v02 INSYDE)
[ 0.000000] ACPI: XSDT 0x000000007AFDA188 0000DC (v01 INSYDE INSYDE 00000003 01000013)
[ 0.000000] ACPI: FACP 0x000000007AFF5000 000114 (v06 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: DSDT 0x000000007AFE6000 00772B (v02 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: FACS 0x000000007AFAF000 000040
[ 0.000000] ACPI: FACS 0x000000007AFAF000 000040
[ 0.000000] ACPI: UEFI 0x000000007AFFD000 000236 (v01 INSYDE INSYDE 00000001 ACPI 00040000)
[ 0.000000] ACPI: BDAT 0x000000007AFFB000 000030 (v02 INSYDE INSYDE 00000000 ACPI 00040000)
[ 0.000000] ACPI: UEFI 0x000000007AFFA000 000042 (v01 INSYDE INSYDE 00000002 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFF9000 000554 (v01 INSYDE Tpm2Tabl 00001000 ACPI 00040000)
[ 0.000000] ACPI: TPM2 0x000000007AFF8000 000034 (v03 INSYDE INSYDE 00000002 ACPI 00040000)
[ 0.000000] ACPI: PSDS 0x000000007AFF7000 00004D (v01 INSYDE INSYDE 00000005 ACPI 00040000)
[ 0.000000] ACPI: HPET 0x000000007AFF4000 000038 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: LPIT 0x000000007AFF3000 00005C (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: APIC 0x000000007AFF2000 000084 (v03 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: MCFG 0x000000007AFF1000 00003C (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: NPKT 0x000000007AFF0000 000065 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: WDRT 0x000000007AFEF000 000047 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: WSMT 0x000000007AFEE000 000028 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFE4000 00024A (v02 INSYDE UsbCTabl 00000003 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFE3000 0000BC (v01 INSYDE Platform 00001000 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFE2000 00045A (v02 INSYDE Cpu0Ist 00003000 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFE1000 00072B (v02 INSYDE CpuSsdt 00003000 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x000000007AFDE000 002760 (v02 INSYDE SaSsdt 00003000 ACPI 00040000)
[ 0.000000] ACPI: FPDT 0x000000007AFDD000 000034 (v01 INSYDE INSYDE 00000002 ACPI 00040000)
[ 0.000000] ACPI: WDAT 0x000000007AFF6000 000104 (v01 INSYDE INSYDE 00000000 ACPI 00040000)
[ 0.000000] ACPI: BGRT 0x000000007AFE5000 000038 (v01 INSYDE INSYDE 00000001 ACPI 00040000)
[ 0.000000] ACPI: NHLT 0x000000007AFDC000 00002D (v00 INTEL EDK2 00000002 01000013)
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x000000017fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x0000000000057fff]
[ 0.000000] node 0: [mem 0x0000000000059000-0x0000000000085fff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000000fffffff]
[ 0.000000] node 0: [mem 0x0000000012151000-0x0000000067c17fff]
[ 0.000000] node 0: [mem 0x0000000067c43000-0x0000000067c7dfff]
[ 0.000000] node 0: [mem 0x0000000068c7e000-0x000000007822efff]
[ 0.000000] node 0: [mem 0x000000007afff000-0x000000007affffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000017fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000017fffffff]
[ 0.000000] Reserving Intel graphics memory at [mem 0x7c000000-0x7fffffff]
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-119
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x00058000-0x00058fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x00086000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x01ddc000-0x01ddcfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x01ddc000-0x01ddcfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x10000000-0x12150fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x67c18000-0x67c18fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x67c19000-0x67c42fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x67c7e000-0x68c7dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7822f000-0x7aebefff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7aebf000-0x7afbefff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7afbf000-0x7affefff]
[ 0.000000] PM: Registered nosave memory: [mem 0x7b000000-0x7fffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x80000000-0xd3708fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xd3709000-0xd370afff]
[ 0.000000] PM: Registered nosave memory: [mem 0xd370b000-0xdfffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xe3ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xe4000000-0xfed00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed01000-0xfed01fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed02000-0xff7fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xff800000-0xffffffff]
[ 0.000000] e820: [mem 0x80000000-0xd3708fff] available for PCI devices
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 37 pages/cpu @ffff88017fc00000 s111576 r8192 d31784 u524288
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 987870
[ 0.000000] Kernel command line: root=/dev/md0 earlyprintk=apl console=ttyS2,115200n8 ihd_num=4 netif_num=2 HddHotplug=1 SataPortMap=23 sata_remap=0>2:1>3:2>0:3>1 syno_hw_version=DS918+ vender_format_version=2 syno_hdd_detect=18,179,176,175 syno_hdd_enable=21,20,19,9 syno_usb_vbus_gpio=13@0000:00:15.0@1,11@0000:00:15.0@2 sn=18C0PDN161909 macs=001132a1b95f,001132a1b960
[ 0.000000] Internal HD num: 4
[ 0.000000] Internal netif num: 2
[ 0.000000] Support HDD Hotplug.
[ 0.000000] Sata Port Map: 23
[ 0.000000] SYNO: sata remap initialized
[ 0.000000] Synology Hardware Version: DS918+
[ 0.000000] Vender format version: 2
[ 0.000000] SYNO GPIO hdd detect pin: 18 179 176 175
[ 0.000000] SYNO GPIO hdd enable pin: 21 20 19 9
[ 0.000000] USB Vbus GPIO Control:
[ 0.000000] Gpp#13 - Host: dev_name:usb2 - Port:1 - Polarity: ACTIVE_HIGH
[ 0.000000] Gpp#13 - Host: dev_name:usb1 - Port:3 - Polarity: ACTIVE_HIGH
[ 0.000000] Gpp#11 - Host: dev_name:usb2 - Port:2 - Polarity: ACTIVE_HIGH
[ 0.000000] Gpp#11 - Host: dev_name:usb1 - Port:1 - Polarity: ACTIVE_HIGH
[ 0.000000] Serial Number: 18C0PDN161909
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] Memory: 3817420K/4014304K available (5718K kernel code, 866K rwdata, 1784K rodata, 924K init, 664K bss, 196884K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[ 0.000000] NR_IRQS:4352 nr_irqs:1024 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 99544814920 ns
[ 0.000000] tsc: PIT calibration matches HPET. 1 loops
[ 0.000000] tsc: Detected 1497.513 MHz processor
[ 0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 2995.02 BogoMIPS (lpj=1497513)
[ 0.011858] pid_max: default: 32768 minimum: 301
[ 0.017018] ACPI: Core revision 20150930
[ 0.035154] ACPI: 7 ACPI AML tables successfully acquired and loaded
[ 0.045585] Security Framework initialized
[ 0.050000] AppArmor: AppArmor initialized
[ 0.054569] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.062042] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.070340] Initializing cgroup subsys io
[ 0.074658] Initializing cgroup subsys memory
[ 0.079519] Initializing cgroup subsys devices
[ 0.084469] Initializing cgroup subsys freezer
[ 0.089478] CPU: Physical Processor ID: 0
[ 0.093894] CPU: Processor Core ID: 0
[ 0.110074] CPU0: Thermal monitoring enabled (TM1)
[ 0.115300] Last level iTLB entries: 4KB 48, 2MB 0, 4MB 0
[ 0.121276] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[ 0.130502] Freeing SMP alternatives memory: 24K
[ 0.142816] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.159359] smpboot: CPU0: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz (family: 0x6, model: 0x5c, stepping: 0x9)
[ 0.170179] Performance Events: PEBS fmt3+, generic architected perfmon, full-width counters, Intel PMU driver.
[ 0.181427] ... version: 4
[ 0.185894] ... bit width: 48
[ 0.190461] ... generic registers: 4
[ 0.194930] ... value mask: 0000ffffffffffff
[ 0.200857] ... max period: 00007fffffffffff
[ 0.206784] ... fixed-purpose events: 3
[ 0.211253] ... event mask: 000000070000000f
[ 0.217832] x86: Booting SMP configuration:
[ 0.222320] .... node #0, CPUs: #1
|
Bahodir
Re: Unbrick Synology DS918+ October 31, 2023 08:58AM |
Hi, I have bricked DS218+ and followed your steps (more or less expect getting exact file size, i have still difference in bytes)
anyways, i cannot get similarity between my ROM file and PAT file (i tried different firmware versions)
would be great if you could share your modified firmware so that i could flash it directly.
in the meantime, I am trying to get it work.
Thanks, Bahodir
anyways, i cannot get similarity between my ROM file and PAT file (i tried different firmware versions)
would be great if you could share your modified firmware so that i could flash it directly.
in the meantime, I am trying to get it work.
Thanks, Bahodir
|
Re: Unbrick Synology DS918+ October 31, 2023 09:17AM |
Registered: 1 year ago Posts: 15 |
|
Re: Unbrick Synology DS918+ November 09, 2023 04:19PM |
Registered: 4 weeks ago Posts: 1 |
|
Re: Unbrick Synology DS918+ November 19, 2023 07:09AM |
Registered: 4 weeks ago Posts: 1 |
Sorry for overdue message: I have managed to get my ds218+ running with the help of this forum and input from members.
I wanted to add some more details so other no-so-experienced users like me can follow instructions mentioned earlier:
- I have replaced CMOS battery with no luck, kept new battery in.
- I have used CH341A Programmer with 1.8 v adapter and SOIC8 Clip. I did not use any soldering as I could easily attach clip to the chip
- I could read/delete/write to the chip with the help of CH341A programmer but I had wrong file to write
- my mistake was using latest firmware from synology website, it is not possible to get ROM from that .pat file. So use 6.* or 7.1* version, not 7.2*
- the .pat file is like archive file that can be extracted with 7zip or similar programs. I have tried several and worked well without issues
- I used HxD hex editor and followed instructions from other members. it was way easy to get exact file size with one of the commands in hex
editor, i just had to give file size and save it.
- my first flash did not work for some reasons and i wanted to connect to serial port to read the outcome but even after several days' trial could not make it work.
- then I read / delete / write my new firmware once again and I let it run for some minutes.... and after couple or more minutes I could hear BEEP.
Cannot thank enough to instructions of superchromix & PH3!
I have working rom file in case someone needs it for DS218+
all the best, Bahodir
I wanted to add some more details so other no-so-experienced users like me can follow instructions mentioned earlier:
- I have replaced CMOS battery with no luck, kept new battery in.
- I have used CH341A Programmer with 1.8 v adapter and SOIC8 Clip. I did not use any soldering as I could easily attach clip to the chip
- I could read/delete/write to the chip with the help of CH341A programmer but I had wrong file to write
- my mistake was using latest firmware from synology website, it is not possible to get ROM from that .pat file. So use 6.* or 7.1* version, not 7.2*
- the .pat file is like archive file that can be extracted with 7zip or similar programs. I have tried several and worked well without issues
- I used HxD hex editor and followed instructions from other members. it was way easy to get exact file size with one of the commands in hex
editor, i just had to give file size and save it.
- my first flash did not work for some reasons and i wanted to connect to serial port to read the outcome but even after several days' trial could not make it work.
- then I read / delete / write my new firmware once again and I let it run for some minutes.... and after couple or more minutes I could hear BEEP.
Cannot thank enough to instructions of superchromix & PH3!
I have working rom file in case someone needs it for DS218+
all the best, Bahodir
