Relocking the Xperia 10 iii with Windows

Devices
#1

Whether for warranty purposes or for getting the damn Revolut app to work.

Firstly, disable Windows driver verification (for Win 11).

I didn’t do this initially and installing Sony’s Fastboot drivers in normal fastboot mode didn’t work for me. It did get ADB working though.
So I did adb reboot bootloader with the cable attached to Windows. This seemed to put my 10 iii into a different fastboot mode. It suddenly introduced a new “Android” device (without drivers) in Device Manager.
I then reinstalled Sony Fastboot drivers.

For me, the last step made fastboot oem lock work. When booting, it erases (Android’s) user data. I think this breaks Sailfish and Sailfish cannot be installed if the bootloader is locked. I might test the former later.

I don’t know if this reinstalls the original camera filters and they talk about it not restoring the individual device key. A better chance of reinstalling the original camera filters is using NewFlasher and your new firmware’s .TA files but be careful. Do delete the persist*.SIN file and do back up your TA firmware (& re-run).

#2

Warranty is not the proper reason.

#3

You do not have to do this. Follw this guide to revert back to Android: Reinstalling Sailfish OS | Sailfish OS Documentation

No need to test, SailfishOS can not boot when bootloader is locked.

This has not been needed starting from the 1 / 5 / 10 series.

1 Like
#4

The thread is not about reverting to Android. :face_vomiting:

It’s very very clearly about “Relocking the Xperia 10 iii with Windows”. :woman_shrugging:

#5

Like it or not; they are one and the same. Relocking with SFOS is not a thing. So reverting is a prerequisite (for anything to actually boot anyway), not to mention it will do a factory reset on top of that.

PS. Revolut inside a container on top of SFOS can most certainly not see any real bootloader locking status.

#6

For all intents and purposes yes. But note how a prerequisite to X is not the same thing as X. Simple logic.

PS. Revolut inside a container on top of SFOS can most certainly not see any real bootloader locking status.

I agree and App Support presumably lies that it’s bootlocked. But I owed a friend money for about 2 weeks and had to pay her. So now I’m stuck on Android, occasionally reinstalling SF for a few hours at a time until I can figure this out.