Choose style:

Author Topic: Updating Firmware  (Read 4038 times)

0 Members and 1 Guest are viewing this topic.

Offline Timeslider

  • Backer
  • *
  • Posts: 7
  • Thanks: 0
  • Registered : 05/10/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Updating Firmware
« on: June 25, 2018, 11:47:14 am »
I have problems (since years) updating my first Almond+.

Today I logged through the console and got following info:

Code: [Select]
Checking dest="mtd:kernel_standby" for 4139912 bytes ...
  -> destination: /dev/mtd5
  -> good! md5=0280ee10232bfe71651befdb03ccc07c
Checking dest="mtd:rootfs_standby" for 31457284 bytes ...
  -> destination: /dev/mtd6
  -> good! md5=10feb5bb0ceec5f318677e327b874eeb
killall: CloudHa: no process killed
killall: runCloudRouter: no process killed
Adjusting conffile list ...
Saving config files...
almond/config/ZWnky
almond/email
almond/mode
almond/name
etc/config/6rd
etc/config/algapp
etc/config/apmode
etc/config/bridge_network
etc/config/csmi
etc/config/ddns
etc/config/dhcp
etc/config/dhcp6c
etc/config/dhcp6s
etc/config/dropbear
etc/config/firewall
etc/config/fstab
etc/config/ftpsamba
etc/config/g2qos
etc/config/igmpproxy
etc/config/ipsec
etc/config/luci
etc/config/memory
etc/config/minidlna-gui
etc/config/minidlna-gui.lan
etc/config/minidlna-gui.wan
etc/config/music-gui
etc/config/network
etc/config/ntpclient
etc/config/openvpn
etc/config/p910nd
etc/config/pcontrol
etc/config/radvd
etc/config/repeater
etc/config/router_network
etc/config/samba
etc/config/superblock
etc/config/system
etc/config/timeserver
etc/config/transmission
etc/config/uart-server
etc/config/ucitrack
etc/config/uhttpd
etc/config/upnpd
etc/config/vpn-g
etc/config/webdav
etc/config/wireless
etc/config/wireless_ar9880
etc/config/wireless_ar988x
etc/crontabs/root
etc/dnsmasq.conf
etc/dropbear/dropbear_dss_host_key
etc/dropbear/dropbear_rsa_host_key
etc/firewall.user
etc/fw_env.config
etc/group
etc/hosts
etc/inittab
etc/passwd
etc/profile
etc/rc.local
etc/shells
etc/sysctl.conf
etc/uhttpd.crt
etc/uhttpd.key
etc/uhttpd.key
etc/uhttpd.crt
Killing watchdog timer ...
Switching to ramdisk...
Performing system upgrade...
/usr/bin/cs.extract --commit --burn --verbose --sb0-device=/dev/mtd2 --sb1-device=/dev/mtd3 --erase-blksz=0x20000 AP2-R093-L009-W016-ZW016-ZB005
Invalidating standby super-block ...
Could not find a suitable superblock!
Failed to obtain the standby superblock!
Refreshing partitions
Refreshing mtd partition rootfs ...
Refreshing mtd partition rootfs_standby ...
Unlocking rootfs_data ...
Erasing rootfs_data ...
Appending /tmp/sysupgrade.tgz to jffs2 partition rootfs_data
Upgrade completed
Rebooting system...
g2_pcie_wr_conf: bsu number=5, PCI Configuration space PCI_HEADER_TYPE=0x0
g2_pcie_wr_conf: bsu number=5, PCI Configuration space PCI_HEADER_TYPE=0x0
Restarting system.

Somebody has an idea solving the problem?

Offline Timeslider

  • Backer
  • *
  • Posts: 7
  • Thanks: 0
  • Registered : 05/10/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Updating Firmware
« Reply #1 on: June 25, 2018, 04:14:26 pm »
I solved it myself after a stressful evening.  ;)

I made a DUMP of the NAND of my good Almond+ and wrote it into the bad Almond+

Working Almond+:

Code: [Select]
nanddump -nf /tmp/mtd2dump /tmp/mtd2
scp /tmp/mtd3dump root@10.10.10.bad:/tmp/
rm /tmp/mtd2dump

I did the same for mtd3 mtd5 mtd6  (afer copying every DUMP I delteted them because auf limited space)

Bad Almond+
Code: [Select]
flash_erase /dev/mtd2
nandwrite -on /dev/mtd2 /tmp/mtd2
rm /tmp/mtd2dump

same for mtd3 mtd5 mtd6

finaly:
Code: [Select]
wget http://firmware.securifi.com/AP2/AP2-R093-L009-W016-ZW016-ZB005
sysupgrade -i -v AP2-R093-L009-W016-ZW016-ZB005


Now the bad Almond+ has the newest firmware and is working fine

 

Page created in 0.057 seconds with 17 queries.