After an installation of DD-WRT it was not easy for me to quickly reinstall the original firmware , bricked ?
I had wired the serial / ttl port
1 - You must use tftp to install OpenWrt ( see slh post )
2 - Once openwrt started use scp
3 - Copy partition 11 previously saved in tmp/tmp
4 - Flash partition 11 with mtd -> mtd write 11.bin ubi
5 - From openwrt run "g10_back_to_factory" script from /sbin "
6 - Power off , power on
where <filename> is one of
"openwrt-22.03.[0|1|2]-ipq806x-generic-asrock_g10-initramfs-fit-uImage.itb"
(IPQ) # tftpboot 22.03.0.itb
Using eth1 device
TFTP from server 192.168.1.8; our IP address is 192.168.1.9
Filename '22.03.0.itb'.
Load address: 0x44000000
Loading: ####### lots of hash signs ###########
######################################
done
Bytes transferred = 9137672 (8b6e08 hex)
(IPQ) # iminfo
Checking Image at 44000000 ...
FIT image found
FIT description: ARM OpenWrt FIT (Flattened Image Tree)
Image 0 (kernel-1)
Description: ARM OpenWrt Linux-5.10.138
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x440000e4
Data Size: 9107843 Bytes = 8.7 MiB
Architecture: ARM
OS: Linux
Load Address: 0x42208000
Entry Point: 0x42208000
Hash algo: crc32
Hash value: 0951c88d
Hash algo: sha1
Hash value: ba23c3037a10b18ac22f88779fe7db4349ee60e4
Image 1 (fdt-1)
Description: ARM OpenWrt asrock_g10 device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x448afb9c
Data Size: 27950 Bytes = 27.3 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 7ef7d574
Hash algo: sha1
Hash value: e079695641cfeb20b660039e777fd10232dd9c2c
Default Configuration: 'config@1'
Configuration 0 (config@1)
Description: OpenWrt asrock_g10
Kernel: kernel-1
FDT: fdt-1
Checking hash(es) for FIT Image at 44000000 ...
Hash(es) for Image 0 (kernel-1): crc32 error!
Bad hash value for 'hash@1' hash node in 'kernel-1' image node
Bad hash in FIT image!
(IPQ) # bootm
Booting kernel from FIT Image at 44000000 ...
Using 'config@1' configuration
Trying 'kernel-1' kernel subimage
Description: ARM OpenWrt Linux-5.10.138
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x440000e4
Data Size: 9107843 Bytes = 8.7 MiB
Architecture: ARM
OS: Linux
Load Address: 0x42208000
Entry Point: 0x42208000
Hash algo: crc32
Hash value: 0951c88d
Hash algo: sha1
Hash value: ba23c3037a10b18ac22f88779fe7db4349ee60e4
Verifying Hash Integrity ... crc32 error!
Bad hash value for 'hash@1' hash node in 'kernel-1' image node
Bad Data Hash
ERROR: can't get kernel image!
(IPQ) # tftpboot 22.03.1.itb
Using eth1 device
TFTP from server 192.168.1.8; our IP address is 192.168.1.9
Filename '22.03.1.itb'.
Load address: 0x44000000
Loading: ####### lots of hash signs ###########
######################################
done
Bytes transferred = 9147464 (8b9448 hex)
(IPQ) # iminfo
Checking Image at 44000000 ...
FIT image found
FIT description: ARM OpenWrt FIT (Flattened Image Tree)
Image 0 (kernel-1)
Description: ARM OpenWrt Linux-5.10.146
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x440000e4
Data Size: 9117633 Bytes = 8.7 MiB
Architecture: ARM
OS: Linux
Load Address: 0x42208000
Entry Point: 0x42208000
Hash algo: crc32
Hash value: 2de289b1
Hash algo: sha1
Hash value: b581816a225c0d260928a987a82fe3c7f3ad7cd0
Image 1 (fdt-1)
Description: ARM OpenWrt asrock_g10 device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x448b21dc
Data Size: 27950 Bytes = 27.3 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 7ef7d574
Hash algo: sha1
Hash value: e079695641cfeb20b660039e777fd10232dd9c2c
Default Configuration: 'config@1'
Configuration 0 (config@1)
Description: OpenWrt asrock_g10
Kernel: kernel-1
FDT: fdt-1
Checking hash(es) for FIT Image at 44000000 ...
Hash(es) for Image 0 (kernel-1): crc32 error!
Bad hash value for 'hash@1' hash node in 'kernel-1' image node
Bad hash in FIT image!
(IPQ) # tftpboot snapshot.itb
Using eth1 device
TFTP from server 192.168.1.8; our IP address is 192.168.1.9
Filename 'snapshot.itb'.
Load address: 0x44000000
Loading: ####### lots of hash signs ###########
######################################
done
Bytes transferred = 9225312 (8cc460 hex)
(IPQ) # iminfo
Checking Image at 44000000 ...
FIT image found
FIT description: ARM OpenWrt FIT (Flattened Image Tree)
Image 0 (kernel-1)
Description: ARM OpenWrt Linux-5.15.85
Type: Unknown Image
Compression: Unknown Compression
Data Start: 0x440000e4
Data Size: 9194880 Bytes = 8.8 MiB
Checking hash(es) for FIT Image at 44000000 ...
Hash(es) for Image 0 (kernel-1):
(IPQ) # bootm
Booting kernel from FIT Image at 44000000 ...
ERROR: can't get kernel image!
(IPQ) #
(IPQ) # tftpboot 22.03.2.itb
Using eth1 device
TFTP from server 192.168.1.8; our IP address is 192.168.1.9
Filename '22.03.2.itb'.
Load address: 0x44000000
Loading: ####### lots of hash signs ###########
######################################
done
Bytes transferred = 9148744 (8b9948 hex)
(IPQ) # iminfo
Checking Image at 44000000 ...
FIT image found
FIT description: ARM OpenWrt FIT (Flattened Image Tree)
Image 0 (kernel-1)
Description: ARM OpenWrt Linux-5.10.146
Type: Unknown Image
Compression: Unknown Compression
Data Start: 0x440000e4
Data Size: 9118915 Bytes = 8.7 MiB
Checking hash(es) for FIT Image at 44000000 ...
Hash(es) for Image 0 (kernel-1):
(IPQ) # bootm
Booting kernel from FIT Image at 44000000 ...
ERROR: can't get kernel image!
Things I've tried:
Different LAN cable(s)
Resolder the serial console (this time taking GND from the JTAG header)
Back to OEM FW, upgarde OEM FW and install OpenWRT again.
I'm running out of ideas
I just tried tftp-booting the FB-4040 from the .ITB image the same way, worked out of the box.
That box was driving me mad ...
After loading the image via tftp I did a checksum calculation.
The output of tftpboot 22.03.3.itb was something like:
...
Load address: 0x44000000
...
Bytes transferred = 9161376 (8bcaa0 hex)
So I did a
crc 0x440000008bcaa0
After each tftpboot with the same file the checksum had changed
WTF is going on ?
Next thing I tried was LAN Port 2,3 4 on the G10.
Same error on LAN port 2 and 3, only with with LAN port 4 constant checksums and the beast finally booted from RAM.
Is this just my device or do others have the same issue ?