N1 can brush the flying bull, can the player cloud brush?
Routing enthusiast• Publish Time:2025-12-18 10:14• Category: Comprehensive classification
•Views：88221• Comments: (
23 )
Feixun N1 can now brush Feiniu OS, and the official has given the ARM internal test package; OneCloud is completely unswipeable for the time being, and there is no hope in the short term.
1. Hardware differences: 64-bit vs 32-bit is the biggest threshold
- N1: Amlogic S905D, quad-core Cortex-A53, ARMv8 64-bit , 2GB memory, Gigabit network port, and a lot of community information.
- Wanke Cloud : Amlogic S805, quad-core Cortex-A5, ARMv7 32-bit , 1GB memory, same Gigabit network port, but does not have a 64-bit instruction set .
the ARM internal beta launched by Feiniu OS in 2025-12, is directly compiled into aarch64, which means that the kernel, Docker, and all additional services are all 64-bit ELF, and the Wanke Cloud CPU cannot run at all.
2. Official attitude: N1 is in the first batch of lists, and Wanke Cloud is clearly excluded
Feiniu forum administrator original words:
"ARM is thinking too much...... Wanke Cloud's configuration is still an honest set-top box. "
" cannot support Wanke Cloud's 32-bit ARM processor, even if it is released, it must be 64-bit. ”
official GitHub and download site currently only two image , x86_64 and aarch64, there is no armv7l branch, and there is no 32-bit porting plan.
3. Community status: The N1 flashing tutorial has been released, and Wanke Cloud can still only be a "title party"
- N1: The nanny-level graphic tutorial for 2026-01 has been launched, covering the whole process from downgrading the bootloader to writing ARM images, and the measured Docker, SMB, WebDAV, and PT downloads can be run.
- Wanke Cloud : Although there is a "Wanke Cloud Brushing Feiniu NAS Tutorial" on the Internet, I found that it was not at all when I clicked in, it was Armbian+ CasaOS, not the real fnOS.
4. Is it possible to transplant it yourself?
want to "change" the N1's Feiniu OS firmware to Wanke Cloud, you need:
- recompiling the entire system into armv7l.
- Rewrite the device tree (1GB of memory, PHY model, Flash partition are all different);
- repackaged into an image that can be recognized by S805, it is necessary to flash the flying wire into the community U-Boot first;
- fix the Docker OOM issue with 1GB of memory.
workload is equivalent to making a new release for S805, which is currently not maintained by the community, and the official has confirmed that it will not be invested.
5. What else can you play with Keyun?
if you just want to make the most of it, you can continue to brush :
- Armbian/Debian: Hang qBittorrent, Alist, Syncthing, as a lightweight download machine;
- OpenWrt: Bypassing, de-ad, SmartDNS;
- OMV: Pure NAS, power consumption 4W, when the "old hen" runs 7×24.
but if you want to experience the exquisite web console, app store, and one-click Docker of Feiniu OS, you can only change the 64-bit device (N1, RK3566/RK3568 small box, x86 soft routing, etc.).
summary
- N1: Official son, zero obstacles to brushing Feiniu OS, complete tutorials, can get on the bus immediately.
- Wanke Cloud : 32-bit CPU is an innate disadvantage, there is no official plan, and the community has no finished product, it will definitely not be able to brush the at this stage. If you want to play Flying Bull, you can either change to N1 or go directly to the x86 small host.
Read More
Comment List