Sven Wegener

While developing I did a recovery SPI flash installation with the generated v1 TP-Link factory firmware file. u-boot accepts the generated file just fine and boots it. I just switched...

I've updated the flashing instruction. The OEM firmware images have a special header, like the recently added TL-WPA8630 v1, which also requires serial or SPI flashing.

> @swegener Is the header situation similar to what's described here? > https://forum.openwrt.org/t/unknown-tp-link-header/77182 No, that looks completely different. For the WP8730 OEM images binwalk is able to identify the TP-Link...

 As written the device consists of two boards This is an image of the SoC and Wi-Fi board, which is attached to the front half of the device shell....

> > > I used an SPI programmer with test clips > > > > This is not necessary though correct? @sixtyfive can load the initramfs-kernel.bin using TFTP via the...

OEM firmware image wpa8730v1_1_0_2_up(170407)-20170407.bin looks like this. It has a 56 bytes header, see the bottom of this post for information on this. After that comes a tp-link v1.1 header,...

Just a heads up: After being pointed at Ghidra in another ticket I took a deeper look at the OEM firmware and I'm now able to generate a factory.bin image...

Can someone take a new look? Generating the firmware images for OEM uploading requires changes to firmware-utils, see https://github.com/swegener/openwrt-firmware-utils/compare/master..tp-link-v11 for the required commits.

> Have you tried modifying the U-Boot environment like explained in the UniFi 6 Lite installation instructions? > > https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fb4d7a9680117a00721936c98ce41eeb2dea95c9 > > Only try this if you have serial access,...

> > Because of using an older bootloader for my previous installation I was not able to look at the usetled output. > > Understandable. I can have a look...