i have build a sysupgrade image for a GL-B1300, and i have upload this and now the device is bricked and a reset(with the button) doesn't work. dhcp server doesnt work and the device is not reachable. can i recover it in some other way?
Afaik recovery using a local TFTP server works with the bootloader on this device.
If that won't wort the device also got a built-in serial console which allows you to interact with the bootloader (as well as Linux/OpenWrt once it has booted). You will have to open it and wire it up with a 3.3V TTL level serial adapter (do not just connect RX, TX and GND to RS-232, that's 12V level and can easily fry the CPU of the router!)
All details are documented in the wiki
i have both rs232->serial(with max232 IC) and a usbToSerial-converter both should be 3.3V outputs
a image with this config.buildinfo have i try to flash:
CONFIG_TARGET_ipq40xx=y
CONFIG_TARGET_ipq40xx_generic=y
CONFIG_TARGET_ipq40xx_generic_DEVICE_glinet_gl-b1300=y
CONFIG_EXPERIMENTAL=y
CONFIG_FSTOOLS_OVL_MOUNT_COMPRESS_ZLIB=y
CONFIG_FSTOOLS_OVL_MOUNT_FULL_ACCESS_TIME=y
CONFIG_IB=y
CONFIG_IB_STANDALONE=y
CONFIG_KSMBD_SMB_INSECURE_SERVER=y
CONFIG_PACKAGE_getrandom=m
CONFIG_PACKAGE_kmod-asn1-decoder=m
CONFIG_PACKAGE_kmod-cdrom=m
CONFIG_PACKAGE_kmod-crypto-arc4=m
CONFIG_PACKAGE_kmod-crypto-cbc=m
CONFIG_PACKAGE_kmod-crypto-crc32=m
CONFIG_PACKAGE_kmod-crypto-cts=m
CONFIG_PACKAGE_kmod-crypto-des=m
CONFIG_PACKAGE_kmod-crypto-ecb=m
CONFIG_PACKAGE_kmod-crypto-md4=m
CONFIG_PACKAGE_kmod-crypto-md5=m
CONFIG_PACKAGE_kmod-crypto-sha1=m
CONFIG_PACKAGE_kmod-crypto-sha512=m
CONFIG_PACKAGE_kmod-dnsresolver=m
CONFIG_PACKAGE_kmod-fs-cifs=m
CONFIG_PACKAGE_kmod-fs-configfs=m
CONFIG_PACKAGE_kmod-fs-cramfs=m
CONFIG_PACKAGE_kmod-fs-exfat=m
CONFIG_PACKAGE_kmod-fs-exportfs=m
CONFIG_PACKAGE_kmod-fs-f2fs=m
CONFIG_PACKAGE_kmod-fs-isofs=m
CONFIG_PACKAGE_kmod-fs-ksmbd=m
CONFIG_PACKAGE_kmod-fs-nfs=m
CONFIG_PACKAGE_kmod-fs-nfs-common=m
CONFIG_PACKAGE_kmod-fs-nfs-common-rpcsec=m
CONFIG_PACKAGE_kmod-fs-nfs-v3=m
CONFIG_PACKAGE_kmod-fs-nfs-v4=m
CONFIG_PACKAGE_kmod-fs-nfsd=m
CONFIG_PACKAGE_kmod-fs-ntfs=m
CONFIG_PACKAGE_kmod-fs-reiserfs=m
CONFIG_PACKAGE_kmod-fs-squashfs=m
CONFIG_PACKAGE_kmod-fs-udf=m
CONFIG_PACKAGE_kmod-fs-vfat=m
CONFIG_PACKAGE_kmod-fs-xfs=m
CONFIG_PACKAGE_kmod-fuse=m
CONFIG_PACKAGE_kmod-gpio-cascade=m
CONFIG_PACKAGE_kmod-i2c-algo-bit=m
CONFIG_PACKAGE_kmod-i2c-core=m
CONFIG_PACKAGE_kmod-i2c-gpio=m
CONFIG_PACKAGE_kmod-i2c-mux=m
CONFIG_PACKAGE_kmod-i2c-mux-gpio=m
CONFIG_PACKAGE_kmod-i2c-tiny-usb=m
CONFIG_PACKAGE_kmod-input-core=m
CONFIG_PACKAGE_kmod-input-leds=m
CONFIG_PACKAGE_kmod-leds-gpio=m
CONFIG_PACKAGE_kmod-lib-crc-itu-t=m
CONFIG_PACKAGE_kmod-lib-crc16=m
CONFIG_PACKAGE_kmod-lib-lz4=m
CONFIG_PACKAGE_kmod-lib-textsearch=m
CONFIG_PACKAGE_kmod-lib-zlib-inflate=m
CONFIG_PACKAGE_kmod-lib-zstd=m
CONFIG_PACKAGE_kmod-mux-core=m
CONFIG_PACKAGE_kmod-mux-gpio=m
CONFIG_PACKAGE_kmod-nf-conntrack-netlink=m
CONFIG_PACKAGE_kmod-nf-socket=m
CONFIG_PACKAGE_kmod-nf-tproxy=m
CONFIG_PACKAGE_kmod-nfnetlink-queue=m
CONFIG_PACKAGE_kmod-nft-queue=m
CONFIG_PACKAGE_kmod-nft-socket=m
CONFIG_PACKAGE_kmod-nft-tproxy=m
CONFIG_PACKAGE_kmod-nls-cp1250=m
CONFIG_PACKAGE_kmod-nls-cp437=m
CONFIG_PACKAGE_kmod-nls-iso8859-1=m
CONFIG_PACKAGE_kmod-nls-iso8859-15=m
CONFIG_PACKAGE_kmod-nls-utf8=m
CONFIG_PACKAGE_kmod-oid-registry=m
CONFIG_PACKAGE_libatomic=m
CONFIG_PACKAGE_libblkid=m
CONFIG_PACKAGE_libgmp=m
CONFIG_PACKAGE_libgomp=m
CONFIG_PACKAGE_libiconv=m
CONFIG_PACKAGE_libiconv-full=m
CONFIG_PACKAGE_libintl-full=m
CONFIG_PACKAGE_libiw=m
CONFIG_PACKAGE_liblua=m
CONFIG_PACKAGE_libmount=m
CONFIG_PACKAGE_libncurses=m
CONFIG_PACKAGE_libnetfilter-conntrack=m
CONFIG_PACKAGE_libnfnetlink=m
CONFIG_PACKAGE_libnl=m
CONFIG_PACKAGE_libnl-core=m
CONFIG_PACKAGE_libnl-genl=m
CONFIG_PACKAGE_libnl-nf=m
CONFIG_PACKAGE_libnl-route=m
CONFIG_PACKAGE_libpcap=m
CONFIG_PACKAGE_libpcre=m
CONFIG_PACKAGE_libpopt=m
CONFIG_PACKAGE_libreadline=m
CONFIG_PACKAGE_librt=m
CONFIG_PACKAGE_libstdcpp=m
CONFIG_PACKAGE_libubox-lua=m
CONFIG_PACKAGE_libubus-lua=m
CONFIG_PACKAGE_libuci-lua=m
CONFIG_PACKAGE_libusb-1.0=m
CONFIG_PACKAGE_libuuid=m
CONFIG_PACKAGE_terminfo=m
CONFIG_PACKAGE_wireless-tools=y
CONFIG_PACKAGE_zlib=m
CONFIG_PCRE_JIT_ENABLED=y
CONFIG_TARGET_ROOTFS_CPIOGZ=y
CONFIG_TARGET_ROOTFS_PERSIST_VAR=y
CONFIG_TARGET_ROOTFS_TARGZ=y
and this version.buildinfo
r19345-72b93b77a5
should the image normally works? (and ends not in unreachable state) can i check somehow the image for mistakes?
but the serial access should work ever?
and how i install a working image over serial?
yes its not reachable
but what was false on my image?
Too late to know at this point...
You can't access anything, so you won't be able to retrieve any info from the logs.
Unbrick it with the stable release.
the device boots, but it is doesnt accessible. and rs232 is ever accessible?
You might get some information when you boot with a serial connection to do the recovery.
Have you tried these steps in the wiki section titled "Debricking"?
Looks like a serial connection is the next step.
how to send the img over serial?
I don't think anyone has documented the serial recovery procedure for GL-B1300
https://docs.gl-inet.com/en/2/dev/serial/
links to
https://docs.gl-inet.com/en/2/dev/uboot/
Try asking on GL-inet forum
https://forum.gl-inet.com/
Good luck...
It's U-Boot running there with TFTP client, so you can follow