Choose your own, but that is not quite what I am said.
Well, if the bootloader is getting relocked, then yes, that forced locking step , most likely will trying force a wipe. HUM, which might be what is causing the bootloop.
. ok , im off the download the update so i can read the updater-script.
Alright, I checked again and take back everything.
In the developer settings the switch "OEM unlock" is disabled and says bootloader is unlocked. Therefore I rebooted the phone and the splash screen still shows the warning message that the device is unlocked and can't be trusted.
I'll push the modded boot.img again and see if that works.
EDIT: IT DID! Hooray! As easy as 1, 2, 3... Indeed the bootloader unlock was left untouched by the OTA update. I managed to flash the patched boot.img again, and back I have my root access. Yay!
Now I can try to change the WiFi settings according to the recommendation of
@BZ0RG
---------- Post added at 15:09 ---------- Previous post was at 14:28 ----------
Can you report if geo-tagging is working ? I'm not able to have it with stock camera [emoji848].
CONFIRMED! I just shot a photo with geo-tagging enabled, and Google photos shows me my location on the map.
Try to backup saved WiFi networks with another device using Swift Backup, then restore on F1 (require root).
Didn't work. I backed up the WiFi connection from my old Samsung Galaxy S4, which is able to connect to the hidden network, and restored it onto my F1 Play. But alas, it behaves the same way as if I entered the details manually. Shows the network but does not connect to it.