Internal Photos Internal Photos
It's is the same chipset same ram looks like a similar Nand/ Nor layout:
it just lacks the extra 4 Eithernet ports and the LCM.
[ 2.486356] 21 ofpart partitions found on MTD device spi32766.0
[ 2.486363] Creating 21 MTD partitions on "spi32766.0":
[ 2.486373] 0x000000000000-0x000000050000 : "SBL1"
[ 2.487002] 0x000000050000-0x000000060000 : "MIBIB"
[ 2.487554] 0x000000060000-0x000000080000 : "BOOTCONFIG"
[ 2.488114] 0x000000080000-0x0000000a0000 : "BOOTCONFIG1"
[ 2.488688] 0x0000000a0000-0x000000220000 : "QSEE"
[ 2.489252] 0x000000220000-0x0000003a0000 : "QSEE_1"
[ 2.489813] 0x0000003a0000-0x0000003b0000 : "DEVCFG"
[ 2.490372] 0x0000003b0000-0x0000003c0000 : "DEVCFG_1"
[ 2.490927] 0x0000003c0000-0x0000003d0000 : "APDP"
[ 2.491495] 0x0000003d0000-0x0000003e0000 : "APDP_1"
[ 2.492053] 0x0000003e0000-0x000000420000 : "RPM"
[ 2.492611] 0x000000420000-0x000000460000 : "RPM_1"
[ 2.493165] 0x000000460000-0x000000470000 : "CDT"
[ 2.493723] 0x000000470000-0x000000480000 : "CDT_1"
[ 2.494374] 0x000000480000-0x000000490000 : "u-boot-env"
[ 2.494954] 0x000000490000-0x000000530000 : "u-boot"
[ 2.495525] 0x000000530000-0x0000005d0000 : "u-boot2"
[ 2.496097] 0x0000005d0000-0x000000610000 : "ART"
[ 2.496652] 0x000000610000-0x000000620000 : "eeprom"
[ 2.497213] 0x000000620000-0x000000690000 : "reserved"
[ 2.497767] 0x000000690000-0x0000006a0000 : "prst"
[ 2.499486] nand: device found, Manufacturer ID: 0xef, Chip ID: 0xaa
[ 2.499495] nand: ONFI 10-Compliant Winbond W29N02GZ
[ 2.499503] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 2.499532] 1 ofpart partitions found on MTD device qcom_nand.0
[ 2.499539] Creating 1 MTD partitions on "qcom_nand.0":
[ 2.499547] 0x000000000000-0x000010000000 : "ubi"
It looks like they use the same DTS as the eth ports of the non mesh are defined:
does it use the same flash update?
[ 25.554039] br-lan: port 3(wlan1-1) entered disabled state
[ 25.554466] br-guest: port 1(wlan1-2) entered disabled state
[ 25.554719] br-lan: port 4(wlan1-3) entered disabled state
[ 25.554865] br-iot: port 1(wlan1-4) entered disabled state
[ 25.554999] br-lan: port 5(wlan1-5) entered disabled state
[ 25.555125] br-lan: port 6(wlan1-6) entered disabled state
1 Like
The chipset is not supported by linux/ OpenWrt yet from what I remember, I did look into it ages ago.
1 Like
UniFi/ubiquiti uses if not always Qualcomm hardware for their stuff.. we dont know without any FCC photos etc tho.
I’ll focus on the main ALN-R for now and finish the env before/after factory reinstall comparison there.
If the boot/update logic is shared, that should give us clarity for both devices.
Maybe the MeshPoint NAND dump can come from the new guy since he already has it wired up?
Yeah that makes sense — if they reused the same base DTS and just removed the extra ports/LCM, that would explain the nearly identical NOR/NAND layout.
If the flash/update mechanism is also shared, then the slot/boot logic we confirm on the ALN-R should apply to the MeshPoint as well.
1 Like
I've got to this point without turning it into a paper weight 
This was done on the Router, so will try the Mesh using the same initramfs image
BusyBox v1.37.0 (2026-01-04 21:54:53 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r32506-4495c9fda8
-----------------------------------------------------
1 Like
Quick Update: I've managed to compile OpenWRT using @professor_jonny github repository.
Got an error with wget_ssl which I had to comment out the config to get it to compile and it doesn't actually work when testing But it's a start.
Is github up to date 
?
1 Like
I have successfully built it my self without issue It is likely an issue with the feeds?
you could try rebase it on top of master ?
1 Like
By what do you mean does not work? as in the initramfs image wont boot ? can't flash it won't compile?
As we have had it running an initramfs image before that is how we got all the partition dumps.
1 Like
Sorry that wasn't very helpful.
The image booted, but none of the Lan or Wan Ports where visible. It's probably something I've done as this is my first compile attempt.
I'll give it another go tomorrow and do some better testing.
Thanks for your help 
1 Like
ports should show in the boot log, they worked before for A-Somebody_8272
if you boot the intraramfs image all should work except mac capture may not work.
1 Like
I've learnt a little bit more today and realised I need to learn a lot more
The build process is getting better, just finding it hard to workout what needs to be in the ipq807x.mk file and the DTS file.
The images you posted work fine and as expected, it's my builds that are not working.
I'll post an update when I've make progress.
1 Like
I have my own repo here:
professor-jonny/pj_openwrt at amplify-alien-router
there is a ./update_script that will help you clear artifacts and build from fresh with bash based menu pulling in the feeds etc...
2 Likes
Thanks you so much..
That has worked and I can now build an up to date image with all the LAN ports working
Update: I have also wired up a 2nd Alien Router which will make comparing things while they are running a lot easier
1 Like
@professor_jonny made this:
It provides useful information about the Alien Router (not for MeshPoint) which we gathered!
Btw I didn’t have time yet to continue on the Alien Router where I left off so that’s why y’all heard nothing from me.. sorry.
You really help us very much! Thank you 
. Fingers crossed indeed.