This is now committed in snapshot and 23.05.4 branch
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9ac1523062a5818e566627ad4cbea6f3f5114387
Hi All,
It's been a while since i did pull request for openwrt.
If any openwrt dev can make an opinion on my commits that i will be submitting
Thanks
db260179
After much faffing
This AP is fast!
In the commit message
hi
Thanks all worked fine..
The only tiny thing is that in the /etc/shadow, section of the comment a ':' is missing.
Lets hope this will be in stable soon.
I opened up the unit, and will post them to a device info page next week
G
Had a problem after flashing the factory image, where the AP did not boot.
Had to connect via UART, and then I got:
Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit
ubi0: attaching mtd6
ubi0: scanning is finished
ubi0: attached mtd6 (name "ubi", size 64 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 512, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 1675675700
ubi0: available PEBs: 489, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Volume kernel not found!
MT7981>
Fixed by running initramfs using tftp, and re-flashing the factory image again.
Not sure what did I miss in the first time.
Hi,
How do you connect via UART? could you give me instructions please?
Hi,
I mean, what IP did you set to TFTP server and which commands did you use to upload the firmware? If you could give detailed instructions please, thank you.
Getting a new AP soon, will add step by step instructions then.
However in general, you will need to open up the AP, remove the heatsink (As the UART pins are underneath it) and connect a UART to USB to it.
Then you will need to boot the AP, stop it in the boot menu, and select initramfs boot option.
From there steps are strait forware, as it will ask for AP IP, Server IP, firmware file name ...
Once it boots up, it will have standard openwrt, where you will be able to follow the instruction in the git commit.
I accidentally forced the AP to upgrade firmware without the file, I think it erased the firmware. Now the ap won't boot (stays in pink led)
Is there any solution for this?
Thanks and sorry for the inconvenience
Faced this same issue after using the git instructions
I had to download intiramfs and sysupgrade (customized syspgrade adding luci) from:
https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Ffilogic&id=comfast_cf-e393ax
Connected usb uart, loaded initramfs image (option 6 I believe) with TFTP and when booted to OpenWRT only had to copy sysupgrade image to router and install with sysupgrade -n -F
@db260179 why do we need the factory image in this case? Can't we simply flash the sysupgrade?
Does the factory image add any changes to the u-boot?
Btw, I this if we can generate the sysupgrade with different control file(cf-e393ax instead of confast_cf-e393ax) we should be able to flash it using the gui. Did not test it yet, will test it once I get new ap.
I see the original commit message has a typo in the firmware file wildcard prefix *-- with double -
Could this lead to the issues you got?
root@OpenWrt:/tmp# sysupgrade -n -T /tmp/*--test.bin
Mon Jul 22 18:01:55 UTC 2024 upgrade: Image metadata not present
Mon Jul 22 18:01:55 UTC 2024 upgrade: Use sysupgrade -F to override this check when downgrading or flashing to vendor firmware
Image check failed.
I used -T in pace of -F to avoid bricking things at random, but it seems sysupgrade is indeed trying to flash something (even when my "hello world" /tmp/hello-test.bin does not exist)
Oem web ui will not allow the openwrt firmware to be uploaded. The early versions of this AP have a snapshot openwrt and legacy u-boot.
I'm just revisiting this again for my own reasons, alot has changed in the whole mediatek/mt7981 world.
For now its a requirement to have uart access in case the factory image doesn't complete correctly - could be a newer AP that breaks? unknown.
Just an example of selecting the image name, you can just select the actual name.
Force is required because the oem checksums wont match the openwrt image - reason for factory image so it can format the UBI partitions, sysupgrade wont do that.
I found you can just solder some awg 30 wire on the underneath,thus not needing to take the heatsink off.
Can you help with E935AX not sure of the exact difference, but have put image and chipset details below
Hi,
@GwaiTsi So for me to help you i will need you to dump the flash contents of this device, so this means ssh access as per the git commit of cf-e393(download from oem web ui the config, then remove password from the etc/shadow) - if you get stuck on that part just send me the oem config file i can adjust for you.
can you use the factory rom image? If so, i will download the config.
So from the original oem rom (as installed now and the link you sent) you can download the router config - thats how we gain access, by changing the oem config file and removing the root password.
Then you reimport the new changed config back so that you can - ssh root@yourrouterip