XA2+ stuck in "Sony logo + white LED", e2fsck says "bad magic number" [answered]

What do you mean with 'should have read instructions'? Which instructions?

I thought only the X10 was affected by this Defender boot problem.
https://together.jolla.com/question/217403/defender-app-stops-xperia-10-from-booting/?answer=222140#post-id-222140

Does that mean all devices will not boot anymore when encryption activated and Defender installed?

@peterleinchen: No, it does not but the risk may be higher. We (Jolla) have test-installed the Defender app from OpenRepos to several Xperia devices having OS release 3.2.1.20 in them. The Defender was not used in any particular way in these tests - it was just opened to see that it basically works. Then, those devices were upgraded to the latest version of the upcoming 3.3.0 release. The encryption of user data was activated at the same time. The update went smoothly. We do not know if more serious use of Defender would change something in the system so that this would make OS updates fail. It might be possible, judging by the reports of some users. Therefore, it may be good to remove Defender before installing the update.

@jovirkku
Thanks for the comment (did not notice until just now). But would it then not be a good idea to announce that better in 3.3.0 release notes? That likely all XA2 might be affected, too.

I had a look at the package and do not see any obvious alteration of system files (did not go through all sources). But it uses systemd.path, systemd.service and systemd.timer and I might remember that there was something with services (or was it jobs?) enabled during upgrade. Nevertheless.

You say the solely installation of defender does not affect upgrade nor booting up an encrypted XA2!
That is counterfeited by @Lutwolf!
Or did you configure something after installation?
And @Lutwolf: would you be brave enough to test it once more then? Just install and reboot?
Or at least let us know if you changed config and which?

As I see it only modifies the /etc/hosts file and/or makes the cookie database under /home/nemo/.config/... read-only. Nothing what should affect a boot process, so my guess goes to systemd hang-up (unfortunately my systemd knowledge is erm ...).

@jovirkku
what happens if the defender system service is called early and does not return? I might have spotted one reason for that. (edit: but that should have affect my XA2 3.2.1, no encryption, as well. So wrong path. But what is the dfference why defender crashes encrypted device???).

Thanks @Lutwolf. I confirm that Defender can also break a freshly flashed Xperia X... I flashed it in 3.3.0.16. It's probably related to the encryption indeed (It was working when I was on 3.3.0.16 without encryption). I wonder if it would break also for people just enabling encryption.

@peterleinchen I did nothing else than:

• flash / factory reset
• install gPodder (to get PyOtherSide, required by Defender)
• install Defender and reboot (I didn't even opened the app).

It failed to boot all the time. I did multiple tests: with and without setting a passcode for encryption, same result. Welcome back, ads :( :(

@Sthocs
are you brave enough for another test (or two ;)?

Then you might flash (only if not booting), enable encryption (should be automatically if you flash a 3.3.x.x image, or?), install defender and then

devel-su  
systemctl stop harbour-defender.path harbour-defender.service harbour-defender.timer
systemctl disable harbour-defender.path harbour-defender.service harbour-defender.timers

cross fingers and reboot.

If it boots, lets enable the services one-by-one, first the service, then the timer and only then the path and reboot every time. Be prepared to see the non-booting device :(.
So

systemctl enable harbour-defender.service  
systemctl start harbour-defender.service

Reboot

systemctl enable harbour-defender.timer  
systemctl start harbour-defender.timer

Reboot

systemctl enable harbour-defender.path  
systemctl start harbour-defender.path

Reboot (bang?).