Gotcha. Will give it a go.
EDIT: Alright, the comment stayed after I pushed the update, so it looks like the config wasn’t overwritten. Successfully updated to 4.6 with no further incidents. Which means, now I can continue in recovering from backups.
So far, I only noticed Manufacturer and Product name under ‘About product’ showing UNKNOWN, but that’s about it.
EDIT 2: Camera is not working either.
Think I am gonna revert back on 4.5.0 and stay there for now.
Yeah, looks like Waydroid is busted.
(003446) [22:34:20] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(003446) [22:34:20] New background process: pid=3647, output=background
lxc-start: waydroid: ../src/lxc/network.c: netdev_configure_server_veth: 711 No such file or directory - Failed to attach "veth7zZ5S2" to bridge "waydroid0", bridge interface doesn't exist
lxc-start: waydroid: ../src/lxc/network.c: lxc_create_network_priv: 3427 No such file or directory - Failed to create network device
lxc-start: waydroid: ../src/lxc/start.c: lxc_spawn: 1840 Failed to create the network
lxc-start: waydroid: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "waydroid"
lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126
lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"
lxc-start: waydroid: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: waydroid: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
(003446) [22:34:20] waiting 10 seconds for container to start...
(003446) [22:34:21] waiting 9 seconds for container to start...
(003446) [22:34:22] waiting 8 seconds for container to start...
(003446) [22:34:24] waiting 7 seconds for container to start...
(003446) [22:34:25] waiting 6 seconds for container to start...
(003446) [22:34:26] waiting 5 seconds for container to start...
(003446) [22:34:27] waiting 4 seconds for container to start...
(003446) [22:34:28] waiting 3 seconds for container to start...
(003446) [22:34:29] waiting 2 seconds for container to start...
(003446) [22:34:30] waiting 1 seconds for container to start...
(003446) [22:34:31] ERROR: container failed to start
(003446) [22:34:31] See also: <https://github.com/waydroid>
(003446) [22:34:31] Traceback (most recent call last):
File "/opt/waydroid/tools/__init__.py", line 68, in main
actions.container_manager.start(args)
File "/opt/waydroid/tools/actions/container_manager.py", line 131, in start
raise OSError("container failed to start")
OSError: container failed to start
So…reverted to 4.5.0.25.
Camera is now black (same with Advanced Camera).
sigh Not my day today it would seem.
@piggz is this an adaptation, why does it say android instead of waydroid?
This is the halium lxc, not the waydroid one 
Out of curiosity piggzy (or whoever else also updated Volla 22), is your camera working? Mine doesn’t, even after reverting back to 4.5.0.
Journalctl spits out a lot of stuff, posted it in the pastebin as well:
Are you using a GS5 or a rephone or a Volla22 ? I’ve had odd behaviour on the rephone, but, if I select the camera modes carefully (in advanced camera) and use advanced camera, I get consistantly good behviour on the rephone (recent angelfish is a fine browser, too). My GS5 is a bit trashed at the moment and the Volla22 I passed on.
Volla 22. Everything worked fine before the update (with the expected bugs) to 4.6.
AdvancedCamera gives me the same nothing like the normal Camera app.
In 4.5 now, or 4.6? Try going to advanced camera:
And try making a video. Then switch to image, leave the resolution initially and try a simple picture.
Right now I have 4.5.0.25
Manufacturer and Product name both show UNKNOWN which I don’t think was there before.
On Advanced camera, I only see resolution -1x-1
Changing cameras did nothing, it was still black.
Oh, ok, that seems extreme, though I’ve had very odd resolution issues with the volla22/rephone (not on the GS5). Hmmm.
Yeah, it’s an odd one. I thought it would be fixed if I reflash the same image I did the first time (4.4 I think?). Once I updated that with ssu, it went to shit
I just checked and I have 4.5.0.21 on my rephone (with everything but bluetooth le working). There the Manufacturer is Volla and Product name Phone 22 …
Try going to 4.5.0.21 …
Well…that fixed everything 
Got camera back AND the phone info as well.
Now I wonder why 4.6.0 was so busted…
I havnt released 4.6 yet 
If you installed it, you must be running the devel build, not the testing one i guess? I submitted a PR to Halium last night to update droidmedia in the halium image to the version used in 4.6, so I hope that fixes and media/camera issues.
Possibly
I got too horny for the update, can’t help it sometimes. 
so that revert to 4.5.0.21 went smooth? cool if so. I haven’t needed to do that for a while
Yup, it went smoothly. Nothing (re)broke as far as I can tell.
After I smahed my Screen in March, it is now more or less dead. Unfortunately I was stupid enough to reboot. Any chance to get my data which is on the phone without repairing the screen? My last backup is unfortunately from December 2023 
.
I managed to get in fastboot mode but I have no clue if this helps.
I think you;d need to at least get into recovery mode, and use ADB to pull data. Is that an option for you?