Dont return your expensive paperweights yet as i was to do after few frustrating hours … but then the hero appeared = Huge thanks to  — his patch inspired me to do the hard work :)  and ask AI to give me manual steps to follow because i have oem lenovo PGX and his patch wouldnt work for me

In my case, what worked was this:I used the Lenovo OEM recovery imageBefore first boot, I stopped thereI had Secure Boot disabled (at least in my case, because I was using Ventoy)I booted Ubuntu Desktop for ARM64

From the live system, I found and mounted the installed root partition, then patched the installed oobe-serviceAfter reboot, the Wi-Fi/setup loop was gone and the machine booted normally and updated via ethernet (network uses dhcp)

I only tested this on a fresh install before first boot, and that worked for me. I’m not sure whether everyone needs to reflash/reinstall first, or whether this also works on an already booted “broken” system.

Steps I used from the live ubuntu system:

sudo sulsblk -f

Replace /dev/nvme0n1p3 below with the real root device you found.

Mount the installed system:

mkdir -p /mnt/targetmount /dev/nvme0n1p3 /mnt/target

Check that the target file exists:

ls -l /mnt/target/opt/nvidia/dgx-oobe/oobe-service

Back it up and verify current bytes:

cp /mnt/target/opt/nvidia/dgx-oobe/oobe-service /mnt/target/opt/nvidia/dgx-oobe/oobe-service.bakod -An -tx1 -N8 -j3999512 /mnt/target/opt/nvidia/dgx-oobe/oobe-service | tr -d ’ \n’; echo

Expected before patch:

ff3b00f9ffdf0039

If you see anything else, stop.

Apply the patch:

printf ‘\x20\x00\x80\x52\x4d\x00\x00\x14’ | dd of=/mnt/target/opt/nvidia/dgx-oobe/oobe-service bs=1 seek=3999512 conv=notrunc status=none

Verify the patch:

od -An -tx1 -N8 -j3999512 /mnt/target/opt/nvidia/dgx-oobe/oobe-service | tr -d ’ \n’; echo

Expected after patch:

200080524d000014

Unmount and reboot:

sync
umount /mnt/target