there's a ubidetach command, if I remember correctly.
Yes, I googled it. but is it safe to do that? And what else will change in the standard steps? Sorry for dumb questions. I'm doing this stuff like ever 3-4 years only and my memory is rusty
no idea, probaby 
do a printenv, what's the current value of mtdparts and bootcmd ?
Went ahead and detached and followed the rest of the process to full success! 
This time upgrading from luci went smooth too. It was probably a result of different(new) snapshot version? Hmmm
1 Like
that wil 10000% result in fw getting rejected due to checksum mismatch
1 Like
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.3.1-00163
S - IMAGE_VARIANT_STRING=HAACANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x000002e5
B - 203 - PBL, Start
B - 2741 - bootable_media_detect_entry, Start
B - 4170 - bootable_media_detect_success, Start
B - 4174 - elf_loader_entry, Start
B - 6843 - auth_hash_seg_entry, Start
B - 44719 - auth_hash_seg_exit, Start
B - 106728 - elf_segs_hash_verify_entry, Start
B - 169581 - PBL, End
B - 185318 - SBL1, Start
B - 238510 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B - 245159 - pm_device_init, Start
B - 370148 - PM_SET_VAL:Skip
D - 124501 - pm_device_init, Delta
B - 372588 - pm_driver_init, Start
D - 5429 - pm_driver_init, Delta
B - 378901 - clock_init, Start
D - 2135 - clock_init, Delta
B - 382927 - boot_flash_init, Start
D - 12566 - boot_flash_init, Delta
B - 399184 - boot_config_data_table_init, Start
D - 3080 - boot_config_data_table_init, Delta - (575 Bytes)
B - 406656 - Boot Setting : 0x00000618
B - 410591 - CDT version:2,Platform ID:8,Major ID:133,Minor ID:1,Subtype:5
B - 417697 - sbl1_ddr_set_params, Start
B - 421418 - CPR configuration: 0x30c
B - 424895 - cpr_init, Start
B - 427671 - Rail:0 Mode: 5 Voltage: 832000
B - 432886 - CL CPR settled at 784000mV
B - 435692 - Rail:1 Mode: 5 Voltage: 896000
B - 439993 - Rail:1 Mode: 7 Voltage: 936000
D - 16500 - cpr_init, Delta
B - 446764 - Pre_DDR_clock_init, Start
B - 450790 - Pre_DDR_clock_init, End
B - 454175 - DDR Type : PCDDR4
B - 460946 - do ddr sanity test, Start
D - 1067 - do ddr sanity test, Delta
B - 464637 - DDR: Start of HAL DDR Boot Training
B - 469364 - DDR: End of HAL DDR Boot Training
B - 475037 - DDR: Checksum to be stored on flash is 774779121
B - 485377 - Image Load, Start
D - 505476 - QSEE Image Loaded, Delta - (1378368 Bytes)
B - 990945 - Image Load, Start
D - 61 - SEC Image Loaded, Delta - (0 Bytes)
B - 998631 - Image Load, Start
D - 293867 - DEVCFG Image Loaded, Delta - (32488 Bytes)
B - 1292590 - Image Load, Start
D - 305030 - RPM Image Loaded, Delta - (93060 Bytes)
B - 1597712 - Image Load, Start
D - 369873 - APPSBL Image Loaded, Delta - (537454 Bytes)
B - 1967738 - QSEE Execution, Start
D - 61 - QSEE Execution, Delta
B - 1973533 - USB D+ check, Start
D - 0 - USB D+ check, Delta
B - 1979938 - SBL1, End
D - 1796907 - SBL1, Delta
S - Flash Throughput, 6729 KB/s (2042617 Bytes, 303529 us)
S - DDR Frequency, 600 MHz
S - Core 0 Frequency, 1651 MHz
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Just like this directly into the system, can not be interrupted
Did you test and successfully downgradeļ¼
Yes, after modifying the OEM sysupgrade script I tested it many times as I was testing OEM partitions slots and to trigger the switch I had to allow downgrading.
But again, as far as I know, the the OEM images don't contain the bootloader, at least the ones I checked.
That is an interesting log.
I get the U-Boot version instead of your "Booting Linux" message at the end.
It seems to be attempting to start the kernel instead of U-Boot.
Did you by any chance flashed mtd15 (0:APPSBL) or mtd16 (0:APPSBL_1) instead of mtd18 and mtd20?
@robimarko, @Ansuel, have you seen something like this before?
No updates to mtd15 (0:APPSBL) or mtd16 (0:APPSBL_1)
It is because the 231 firmware is automatically updatedļ¼Capture the packet to get the url
http://dl46.askeycloudapi.com/file/dynalink/RT5010W-D350/DL-WRX36/1.10.01.231/Dynalink-RT5010W-d350-V1.10.01.231_sysupgrade_nand_img.bin The server removed the old version of firmware
I deleted the update check code and successfully updated with 1.10.01.201, but I still canāt enter uboot
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.3.1-00163
S - IMAGE_VARIANT_STRING=HAACANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x000002e5
B - 203 - PBL, Start
B - 2740 - bootable_media_detect_entry, Start
B - 4168 - bootable_media_detect_success, Start
B - 4172 - elf_loader_entry, Start
B - 6840 - auth_hash_seg_entry, Start
B - 44691 - auth_hash_seg_exit, Start
B - 106667 - elf_segs_hash_verify_entry, Start
B - 169522 - PBL, End
B - 186782 - SBL1, Start
B - 240462 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B - 247141 - pm_device_init, Start
B - 372374 - PM_SET_VAL:Skip
D - 124684 - pm_device_init, Delta
B - 374784 - pm_driver_init, Start
D - 5368 - pm_driver_init, Delta
B - 381158 - clock_init, Start
D - 2135 - clock_init, Delta
B - 385093 - boot_flash_init, Start
D - 12688 - boot_flash_init, Delta
B - 401563 - boot_config_data_table_init, Start
D - 3080 - boot_config_data_table_init, Delta - (575 Bytes)
B - 409066 - Boot Setting : 0x00000618
B - 413000 - CDT version:2,Platform ID:8,Major ID:133,Minor ID:1,Subtype:5
B - 420107 - sbl1_ddr_set_params, Start
B - 423828 - CPR configuration: 0x30c
B - 427274 - cpr_init, Start
B - 430141 - Rail:0 Mode: 5 Voltage: 832000
B - 435265 - CL CPR settled at 784000mV
B - 438102 - Rail:1 Mode: 5 Voltage: 896000
B - 442372 - Rail:1 Mode: 7 Voltage: 936000
D - 16439 - cpr_init, Delta
B - 449173 - Pre_DDR_clock_init, Start
B - 453199 - Pre_DDR_clock_init, End
B - 456585 - DDR Type : PCDDR4
B - 463630 - do ddr sanity test, Start
D - 1037 - do ddr sanity test, Delta
B - 467046 - DDR: Start of HAL DDR Boot Training
B - 471774 - DDR: End of HAL DDR Boot Training
B - 477447 - DDR: Checksum to be stored on flash is 774779121
B - 487786 - Image Load, Start
D - 505477 - QSEE Image Loaded, Delta - (1378368 Bytes)
B - 993354 - Image Load, Start
D - 61 - SEC Image Loaded, Delta - (0 Bytes)
B - 1001010 - Image Load, Start
D - 293837 - DEVCFG Image Loaded, Delta - (32488 Bytes)
B - 1294938 - Image Load, Start
D - 305061 - RPM Image Loaded, Delta - (93060 Bytes)
B - 1600091 - Image Load, Start
D - 369904 - APPSBL Image Loaded, Delta - (537454 Bytes)
B - 1970117 - QSEE Execution, Start
D - 61 - QSEE Execution, Delta
B - 1975912 - USB D+ check, Start
D - 0 - USB D+ check, Delta
B - 1982317 - SBL1, End
D - 1797822 - SBL1, Delta
S - Flash Throughput, 6734 KB/s (2042617 Bytes, 303316 us)
S - DDR Frequency, 600 MHz
S - Core 0 Frequency, 1651 MHz
Looks like version 231 upgrades uboot and blocks uboot output
dumpimage -l ./oem_firmware.bin
FIT description: Dynalink_RT5010W-D350 Sysupgrade_Nand_Image 1.10.01.231
Created: Fri Dec 9 02:34:37 2022
Image 0 (sbl1)
Description: sbl1_nand.mbn
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 231624 Bytes = 226.20 KiB = 0.22 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 619eed32
Image 1 (tz)
Description: tz.mbn
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 1387212 Bytes = 1354.70 KiB = 1.32 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 5a8476ae
Image 2 (devcfg)
Description: devcfg.mbn
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 37880 Bytes = 36.99 KiB = 0.04 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 5d55e983
Image 3 (rpm)
Description: rpm.mbn
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 98484 Bytes = 96.18 KiB = 0.09 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 02fc0154
Image 4 (ddr-RT5010W-REV2)
Description: cdt-RT5010W-REV2_256M32_DDR3.bin
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 548 Bytes = 0.54 KiB = 0.00 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: d18587bb
Image 5 (ddr-RT5010W-D350-REV0)
Description: cdt-RT5010W-D350-REV0_256M32_DDR4.bin
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 548 Bytes = 0.54 KiB = 0.00 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 27473892
Image 6 (u-boot)
Description: openwrt-ipq807x-u-boot
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 604382 Bytes = 590.22 KiB = 0.58 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: 4248b431
Image 7 (askey-rootfs)
Description: rt5010w-d350-ubi-root.img
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 42729472 Bytes = 41728.00 KiB = 40.75 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: ac0de132
Image 8 (wififw_v1-rt5010w-d350)
Description: rt5010w-d350-ubi-wififw.img
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 2097152 Bytes = 2048.00 KiB = 2.00 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: daa41489
Image 9 (wififw_v2-rt5010w-d350)
Description: rt5010w-d350-ubi-wififw_v2.img
Created: Fri Dec 9 02:34:37 2022
Type: Firmware
Compression: uncompressed
Data Size: 2490368 Bytes = 2432.00 KiB = 2.38 MiB
Architecture: ARM
OS: Unknown OS
Load Address: unavailable
Hash algo: crc32
Hash value: cb175bed
For readability, use the </> button when posting cli output.
1 Like
Just want to give a big THANK YOU for all those who have contributed so far. Received mine today, flashing went smoothly, and Iāll be testing things out for the next few days. So far very impressed.
One question right off the bat - any benefits found from running irqbalance? It looks like most processes are running on the first proc core.
1 Like
Its crazy if they disabled UART in U-boot
if the uboot isn't updated by firmware update, as someone said, it would then mean it's done by uboot parameter update...
Thank you for contacting Dynalink Customer Support.
Dear
Regarding your inquiry:
I'm sorry, but we cannot send out any firmware versions. It is not possible to downgrade the firmware for this router.
Usually when people have issues with the newest firmware, a factory reset of the device will usually fix everything.
We appreciate the opportunity to assist you. If you have any further questions, please reply to this email directly without changing the Subject of this email.
They are clearly updating it in this FW version as they are using the script based one from U-boot so they included the whole bundle.