A similar configuration (same packages, same files) but v24.10 works perfectly on the WR3000S v1, but on this device, it just refuses to work.
I followed the the upgrade procedure as discribed on openwrt-website. First the signed transition image and then a snapshot-image.
Here is the boot log captured via soldered serial pins. It includes:
OpenWrt boot log
Sysupgrade process
Reboot sequence (until it gets stuck)
Hitting Enter to access OpenWrt and running logread
Observations:
The sysupgrade process seems unusually fast compared to other devices I’ve flashed before.
When the device gets stuck, the system LED blinks, and both WiFi LEDs blink simultaneously and alternately.
I can debrick via failsafe mode and sysupgrade a plain snapshot which then works.
I’d really appreciate any insights to figure out why my imagebuilder-image isnt working! Let me know if you need any additional details. Thanks in advance!
Which installation procedure did you follow? Was it an initial flash from a stock firmware or an upgrade from a vanilla OpenWrt? Initial flash is a bit more involved than usual: https://github.com/openwrt/openwrt/pull/17458
And, finally, what is custom about the image that you were flashing?
I flashed a WR3000H about 9 days ago using the signed transition image from Cudy and a custom snapshot image from the firmware selector. Its running fine as a bridged AP but haven't tried a firmware upgrade since
The WR3000H is only supported in snapshot. By definition snapshot images are unstable and for testing. They work, but sometimes not. Let's assume you have installed a non-working snapshot (boot log error). Let's also assume that your custom image contains all the necessary stuff, hence you didn't remove a critical package.
Restore the cudy software with the FTP procedure, than reinstall Openwrt of course, but another version, a working one. Use the default official image (meanwhile no LuCI).
Thx for the insights. I am able to recover via failsafe mode and sysupgrade with a default official snapshot image. Do you think restoring the cudy software is necessary?
If I understand you right, this might just be a consequence of a non-working snapshot? Why is a default official snapshot image working? Does this mean, the error is because of my package selections and configuration files?
The package selection and configuration files with version 24.10 work fine on a wr3000s-v1, though. Hence I would asume they are fine.
Apparently you were able to install something stable, so it's enough.
I assume you meant "not-working" ? Well it happens when a bug is introduced in a newer version. You can't tell until testing. Official snapshots are built daily, without any check whatsoever. It's part of the development process.
It can also be.
I agree, both devices are extremly close. I'm also a happy WR3000S user.
ok apparently my image is working. I am now able to connect to the device. I might have used the wrong subnet and got confused by the leds which are not working properly with my image but thats a minor.
I am using the device as an APs therefore dnsmasq and firewall is only running on my core-router. You are right, some packages might not be needed. They are part of the bbb-configs-selections, I cant tell which ones are necessary. But thanks for the hint.
