Pod 3 setup issue - after completing steps, light is just blinking white and device does not connect to wifi.

[nota-nota-nota]

Hi, I am trying to follow the instructions, but something seems to not be working properly. Has anyone gotten this to work recently?

My main control board is the same as same as the original guide "Control Board 230-0030 Rev-10.7-PRD"

After completing the setup, my pod ends with a blinking white light. The device is not connected to wifi (checking router logs).

If I restore the original rootfs.tar.gz, the device is able to be setup like new after reset. (blinking blue light -> prompted to connect to Wifi through app, etc)

Steps:
0. open pod3 + remove sd card that was on the main board (hidden underneath the pop-up daughter board).

1. copy file from SD card to linux machine -> macos computer (connect to linux to read the ext3 format):
   /opt/images/Yocto/rootfs.tar.gz
2. untar file (double click on macos)
3. modify files using instructions from Add more detailed instructions for jailbreaking process #5

• generate a password to put in /etc/shadow and 'chmod 400' file
• openssl passwd -1 -salt root insert_password_here
• create the /etc/NetworkManager/system-connections/customer-wifi.nmconnection file with the network name and password and 'chmod 600' file
• add my ssh key to /etc/ssh/authorized_keys and chmod 644 file (ssh-keygen and pbcopy < ~/.ssh/id_rsa.pub)

4. tar file, then copy back to sd card sudo tar -czvf rootfs.tar.gz -C ./rootfs

5. reinstall SD card - hold small button while powering on device.

6. Light blinks green, then light starts slowly breathing white. (device never connects to network (checking router logs))

7. restore the original rootfs.tar.gz file

8. reset the machine using small button + power cord again. Machine blinks blue and I can pair normally using the app.

[timwu]

Could the permissions and ownership of files in the tar have gotten mangled when repacking it? I followed a combination of the instructions at: #5 and https://blopker.com/writing/04-zerosleep-1 to put my rootfs.tar.gz file together.

One more thing I did in addition to the zerosleep blog instructions was to explicitly set --group=0 and --owner=0 for files copied into the tarball:

tar --group=0 --owner=0 --numeric-owner -rf ../rootfs.tar ./etc/shadow

This carried the group/owner numbers into the tar file on inspection with tar -tvf rootfs.tar.

[Constantier]

Hello @nota-nota-nota, I just managed to get it working but I needed to make some changes in the customer-wifi.nmconnection file. Here is what it looks like:

[connection]
id=customer-wifi
uuid=700a7a76-2105-4f46-b1b4-c9f3c791c440
type=802-11-wireless
interface-name=wlan0
autoconnect=yes
autoconnect-priority=0
permissions=

[802-11-wireless]
mac-address-blacklist=
mode=infrastructure
ssid=<WIFI NAME>

[802-11-wireless-security]
auth-alg=open
key-mgmt=wpa-psk
psk=<PASSWORD>

[ipv4]
dns-search=
method=auto
     
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

[proxy]
method=none

And +1 about adding --group and --owner flag but I've done it a bit differently: --group=0:0 --owner=0:0. Not sure the difference though.