whoa thank you from the file you provided it is true that it can be used for asus vivobook s14 X1 26 100. Previously I was very sad because I ordered the wrong laptop and could not install linux, but with the existing developments at least there is a possibility in the future I can enjoy ubuntu with this laptop. Is there anything else I can do? because the drivers don’t seem to be loaded, the battery is empty, the camera cannot be accessed, there is no wifi, no sound. maybe I can help to contribute while learning more deeply.
1 Like
Hi All,
I recevied my zenbook A14 earlier in the week. Here are the steps I used to get where I am now.
- read posts in snapdragon thread
- removed from box; charge
- power-on; initlialize windows; power off
- on my ubuntu laptop, use disk-init to create bootable iso from here
- plug usb in zenbook; hold ESC key, click power button, holding ESC until boot menu appears
- boot from USB, install Ubuntu (alongside windows option)
a. my install did not find wifi
b. my install would not reboot from installer; restart from gnome (IIRC) - connect to internet via usb-ethernet adapter
- run
a.apt update
b.apt upgrade
c.apt install qcom-firmware-extract - reboot
- mount windows partition
a.sudo -s
b.# mkdir /mnt/c
c.# fdisk -l /dev/nvme0n1
This should show which partition windows is installed on. p14 for me
d.# mount -t ntfs-3g -o ro /dev/nvme0n1p14 /mnt/c
e.# ls /mnt/c
to convince yourself that you have the right partition # qcom-firmware-extract- reboot
- Use readme here to extract
- disconnect ethernet; reboot
- you should now have wifi
The following things still do not work:
- In GNOME, many of the function keys do not do what they say.
- There are a lot of used partiions on the laptop, not sure what
they are for. See below. I’m not sure how to deal with the
Windows partition. - I’m still exploring what does/doesn’t work.
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: MTFDKBA1T0QGN-1BN1AABGA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier:
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 4095 2048 1M unknown
/dev/nvme0n1p2 4096 36863 32768 16M unknown
/dev/nvme0n1p3 36864 38911 2048 1M unknown
/dev/nvme0n1p4 38912 40959 2048 1M unknown
/dev/nvme0n1p5 40960 184319 143360 70M unknown
/dev/nvme0n1p6 184320 430079 245760 120M unknown
/dev/nvme0n1p7 430080 675839 245760 120M unknown
/dev/nvme0n1p8 675840 677887 2048 1M unknown
/dev/nvme0n1p9 677888 679935 2048 1M unknown
/dev/nvme0n1p10 679936 681983 2048 1M unknown
/dev/nvme0n1p11 681984 1730559 1048576 512M unknown
/dev/nvme0n1p12 1730560 2263039 532480 260M EFI System
/dev/nvme0n1p13 2263040 2295807 32768 16M Microsoft reserved
/dev/nvme0n1p14 2295808 1845633023 1843337216 879G Microsoft basic data
/dev/nvme0n1p15 1997705216 1999876095 2170880 1G Windows recovery environment
/dev/nvme0n1p16 1999876096 2000408575 532480 260M Windows recovery environment
/dev/nvme0n1p17 1845633024 1997705215 152072192 72.5G Linux filesystem
1 Like
Hello,
I need help getting wifi to work jf possible. I installed ‘ubuntu-26.04.1-desktop-arm64’ LTS verion on an ASUS Zenbook A14 purchased 2 days ago.
When I rebooted, got error: Divicetree The command is not allowed when lockdown is enforced.
After updating all the software using a bluetooth tether and eventually getting qcom-firmware-extract to run I rebooted (still getting the error about lockdown) and no wifi was available. I went into BIOS and disabled Secure boot, the error disappeared but even after running qcom-firmware-extract again still not getting any wifi option, only bluetooth, I did notice that the battery indicated 100% now so something worked:
sudo qcom-firmware-extract [sudo: authenticate] Password:
Mounting Windows partition nvme0n1p14…
Extracting firmware from /tmp/fwfetch.pfQ3Z9Hf/mnt/Windows/System32/DriverStore/FileRepository
adsp_dtbs.elf
adspr.jsn
adsps.jsn
adspua.jsn
battmgr.jsn
cdsp_dtbs.elf
cdspr.jsn
qcadsp8380.mbn
qccdsp8380.mbn
qcdxkmsuc8380.mbn
qcdxkmsucpurwa.mbn
Building package qcom-x1e-firmware-extracted-x1p42100-asustek-zenbooka14_20260831_arm64…
Installing qcom-x1e-firmware-extracted-x1p42100-asustek-zenbooka14_20260831_arm64…
update-initramfs: Generating /boot/initrd.img-7.0.0-30-generic
Using DTB: qcom/x1p42100-asus-zenbook-a14.dtb
Installing /lib/firmware/7.0.0-30-generic/device-tree/qcom/x1p42100-asus-zenbook-a14.dtb into /boot/dtbs/7.0.0-30-generic/qcom/x1p42100-asus-zenbook-a14.dtb
Taking backup of x1p42100-asus-zenbook-a14.dtb.
Installing new x1p42100-asus-zenbook-a14.dtb.
System running in EFI mode, skipping.
Done! Reboot to load the added firmware files.
I’ll have a look at that, thanks. It seems a bit complex for me. I’m busy this morning but will look again at it tonight.
I’ve not been able to look at this till today and having problems:
$dmesg -w doesnt have any entries in for ath11k_pci
There isn’t a windows directory qcwlanhsp8380.inf_arm64_ecbde8f5eb2c6dd5 but there is one called
qcwlanhsp8380.inf_arm64_63d471932b9d3ea3 with the 3 files in it (m3.bin … etc) date june 2025.
Would you use these? There is another windows directory with the 3 files date March 2025.
Also the .elf files there are:
- bdwlan_wcn685x_2p1_nfa725a_UX3407Q.elf file and
- a bdwlan_wcn685x_2p1_nfa765a_AS_SA_S3407QA.elf
I assume it is file 1. I want for model UX3407QA?
It says to copy the 3 files to /lib/firmware/updates/ath11k/WCN6855/hw2.1/ which doesn’t exist on this PC.
Also /tmp/qca for the ‘elf file doesn’t exist.
I’ve copied them and the .elf files to my home directory.
Not sure what to do now: create a directory /lib/firmware/updates/ath11k/WCN6855/hw2.1/
and /tmp/qca?
@markriga, my experience also: the hash code on the directory didn’t match but I used what I had.
You should mkdir -p /lib/firmware/updates/ath11k/WCN6855/hw2.1.
Then copy the files over.
OK thanks, I’ll try that.
I thought I might be able to make the Windows directory, copy the files in there and run qcom-firmware-extract again but couldn't create the directory.