hallo sir,
i have device yuncore A770
https://firmware-selector.openwrt.org/?version=22.03.6&target=ath79%2Fgeneric&id=yuncore_a770
why i done upload file bin, my device not replay, and not working reset in button
stuck in here
please how to upgrade frimware..?
hi,
usually as per the instructions you linked: if you already use openwrt should select sysupgrade option. as you did not specified which binary you tried , i see you might used "kernel.bin" which is for when you replace the factory firmware to openwrt.
also, it looks you are on ancient v17 and want to do a major release upgrade. the bigger the leap it is less likely you can make a direct jump, there is a chance you might need to upgrade to intermediate version between 17 and 22. and sometimes it is required to restore factory image then do fresh owrt install instead of upgrade.
and, usually in case of major upgrades it is recommended to backup current config then do clean upgrade instead of keeping settings.
i am not familiar with your device so not sure whether you need revert to factory then change to owrt, or you can upgrade from 17 to 22, or upgrade first to some intermediate versions first but i'd rather pick the latest supported version v24 instead of the also out dated v22.
hi @grrr2
Is there a way to make my own firmware to customize my device?
Without having to wait for the release of the OpenWRT web selector...?
Your device clearly isn't running official OpenWrt. Is there a reason you keep making threads for unsupported devices/firmware?
You may want to verify with the manufacturer or vendor that they didn't disable sysupgrade somehow.
You can download and use the image builder or SDK.
please guide me sir 
It's not clear what you're attempting to accomplish, or what you mean by "customize my device without having to wait for the release of the OpenWRT web selector".
What do you need guidance on?
hi @lleachii ,
With my current device which doesn't have firmware on the OpenWRT site, can I make my own firmware?
Because my current device kernel doesn't use the official OpenWRT firmware, that's why I want to use the official OpenWRT firmware
sorry I'm not very fluent in English
Yes, and you can also download the official firmware without the SDK or Image Builder. What are you trying to accomplish by "making your own"?
Did you fix this?
The firmware that is currently running cannot be run by iptables
how to fix it ?
I.g. in case, you are SHURE, your unsupported device can run a specific supported firmware image, AND sysupgrade does not work (i.e. error: wrong device type), often there is the possibility, to use the boot loaders functionality to flash any firmware image.
I.e. actually I am playing around with a HC540-H, which is an out-door router, but based on a supported WE826. The org (custom) firmware on the HC540 is based on openwrt, but refused to sysupgrade an image for the WE826.
I used the U-Boot web based flashing procedure, to flash a WE826 image. Worked.
In case, you have ssh access into your device, you can force sysupgrade to do the upgrade, using sysupgrade option "-F". Easier compared to U-Boot, but a bit risky, as well. You need to be SHURE, that the new image is suitable.
hi @reinerotto , yes i have accses to ssh and telnet
Review the entire reply.
If the creator of the firmware included the requisite packages for doing so.
hy @lleachii , i will try
now my device not loading 
this file my sysupgrade
frimware
root@LEDE:/tmp# sysupgrade -F -v ax820.bin
Device mt7621-rfb-ax-nor not supported by this image
Supported devices: yuncore,ax820 - Image version mismatch: image 1.1, device 1.0. Please wipe config during upgrade (force required) or reinstall. Reason: Config cannot be migrated from swconfig to DSA
Image check 'fwtool_check_image' failed but --force given - will update anyway!
Saving config files...
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/fstab
etc/config/luci
etc/config/mtkhnat
etc/config/network
etc/config/omcproxy
etc/config/rpcd
etc/config/system
etc/config/ucitrack
etc/config/uhttpd
etc/dropbear/dropbear_rsa_host_key
etc/firewall.user
etc/group
etc/hosts
etc/inittab
etc/luci-uploads/.placeholder
etc/opkg/keys/5151f69420c3f508
etc/opkg/keys/72a57f2191b211e0
etc/opkg/keys/792d9d9b39f180dc
etc/opkg/keys/9ef4694208102c43
etc/opkg/keys/b5043e70f9a75cde
etc/opkg/keys/dace9d4df16896bf
etc/opkg/keys/dd6de0d06bbd3d85
etc/opkg/keys/e0760118d73802db
etc/passwd
etc/profile
etc/rc.local
etc/shadow
etc/shells
etc/sysctl.conf
etc/sysctl.d/local.conf
etc/wireless/l1profile.dat
etc/wireless/mediatek/DBDC_card0.dat
etc/wireless/mediatek/map_mt7915.dbdc.b0.dat
etc/wireless/mediatek/map_mt7915.dbdc.b1.dat
etc/wireless/mediatek/mt7615e-sku-bf.dat
etc/wireless/mediatek/mt7615e-sku.dat
etc/wireless/mediatek/mt7915.dbdc.b0.dat
etc/wireless/mediatek/mt7915.dbdc.b1.dat
etc/wireless/mediatek/mt7915_eeprom.bin
etc/wireless/mediatek/version
etc/wireless/mediatek/wifi_cert_b0.dat
etc/wireless/mediatek/wifi_cert_b1.dat
etc/wireless/sigma_test/wifi_cert.1.dat
etc/wireless/sigma_test/wifi_cert.2.dat
etc/wireless/sigma_test/wifi_cert_b0.dat
etc/wireless/sigma_test/wifi_cert_b1.dat
killall: watchdog: no process killed
Sending TERM to remaining processes ... fwdd logd rpcd odhcpd uhttpd ntpd dnsmasq netifd ubusd askfirst
Sending KILL to remaining processes ... askfirst
Switching to ramdisk...
Performing system upgrade...
Unlocking firmware ...
Writing from <stdin> to firmware ...
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware..
Upgrade completed
Rebooting system...
umount: can't unmount /dev/pts: Resource busy
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
umount: can't unmount /sys: Resource busy
umount: can't unmount /proc: Resource busy
Why did you force-flash an incompatible image from a different device?
You said you have yuncore A770 and yet you flashed the firmware from AX280.
hi @Dante ,
because the a770 failed at the start for these treads, so I used a different type of device
I'm not sure how messed up your device is now, but you can try the Failsafe mode. Otherwise, open it up and look for the serial pins.
And, in the future, try to avoid doing something without understanding the consequences.
There are 4 pins in the top right corner. Unless they are clearly marked, use a multimeter to figure out which one is V, G, RX and TX, and which voltage they are running at.
Wow. So I guess you never fixed your issue.
(I didn't quote the other user to suggest you try "anything" like flashing another firmware. I quoted to make note that sysupgrades generally work for the devices in question.)
