Almost the same way you unlocked. Connect into Fastboot mode (blue led) and run fastboot oem lock
1 Like
Thanx @eson. Both Xperiaâs 10V are already on newest Android again. Eagerly awaiting to get rid of it again.
@MeeGo-Junky has already guided me to the command which @wetab73 posted before and I have just overlooked.
1 Like
Dear All,
With help of wetab73 and olf, I noticed soon that it was a driver problem. Device manager showed
! beside android when Device manager of Windows 11 was opened.
This morning I wrote in Youtube (Fastboot devices add any device), that resulted a lot of Youtube videos. With exotic english spoken behind videos, I just looked pictures. I updated some Android bootload interface ( usb driver). Unfortunately I did not find anymore the internet address. But please look Youtube!
And then I set Xperia 10 V in fastboot mode, and fastboot devices showed information. The I add as given fastboot oem lock. And now my Xperia 10 V is receiving OTA updates. First 68.0.A.0.797, then 68.0.A.811, 68.0.A.0.829 and is going on ⌠Looking for ver 14!
68.1.A.2.93
Aggiornato ad Android 14
68.1.A.2.170 coming âŚ
After that shall close the machine. 
Thank you for your help!
PS.
It was this presentation:
2 Likes
Sorry to bother you, but has there been anything interesting in the past 10 days? I think nothing was on the community meeting about this, but maybe I should have proxied in a question about what âreleasing soonerâ might mean for time 
At least it seems our data would be safe and the upgrades would all happen on an OS level, so thatâs great!
Recently, there were multiple releases for both Murray and Zambezi when it comes to Android 13 based Sony binaries, but no new Android 14 ones since early June. So it seems that Android 13-based binaries get more attention from Sony and maybe are more polished. If so, maybe the decision to wait for Android 14-based binaries fixing the camera issue isnât good and weâre only wasting time.
In what aspects are the Android 13 based binaries for Zambezi and Murray worse than Android 14 based binaries? If at present they are more polished and do not have the camera bug, why wait for the release of Android 14 based ones fixing this issue, which may take Sony many months?
3 Likes
Android 15 shall enter soon to Xperia V. Itâ's going to be a hell of a mess right there of everything. 
1 Like
Source?
20 characters.
Therefore, I would say: if Android 13 binaries are sufficiently stable, polished and functional, f*** Android 14 (or soon 15) ones. Or else, Iâm afraid, we wonât see a fully stable and functional Xperia IV and V build before 2026, if at all.
2 Likes
I found only 10 V on that site:
Xperia phones expected to receive Android 15:
- Sony Xperia 1 IV
- Sony Xperia 1 V
- Sony Xperia 1 VI
- Sony Xperia 5 IV
- Sony Xperia 5 V
- Sony Xperia 10 V
- Sony Xperia 10 VI
- Sony Xperia Pro-I
You have right. I have read Xperia VI as Xperia IV. 
Excuse me. Xperia IV has itâs updates fr a 12 to 14 allready.
Jolla said that Sony denoted Android 14 to be maintained on the Xperia IV and V for long. As their hardware is almost the same, I think it makes a lot of sense for Jolla to base their SailfishOS port for these two devices on Android 14 and Sonyâs âsoftware binaries for AOSPâ 14.
2 Likes
Both of opinions seem to be understandable. Personally Iâm only able to wish best available solution. Itâ's not good if weâve to wait for too long time.
It is said that Sony will provide Android 15 to last two generations of their phones, which means that the 10 V would get it but the 10 IV would not.
I fully agree that it would be the optimal situation. The only question is when will those new Android 14 based binaries come out and whether they will address the camera issue. The way @rainemak described it, i.e.
and
doesnât seem like itâs guaranteed or something. Hence, if the existing Android 13 blobs are already now usable and lacking any major issues (I donât know if they are, Iâm just wondering), maybe it would be more reasonable to use them, at least for now. Just like the XA2 uses Android 8 based binaries (even though Android 9, 10 and 11 based ones were then also released for it) or the 10 III uses Android 11 based binaries (even though Android 12 and 13 based ones came out then). Time runs fast, and at this pace we may not see a âdaily driverâ grade 10 IV / V support not only before 2025 but before 10 VII comes outâŚ
1 Like
You are misunderstanding (or ignoring?) that they would switch to the corresponding kernel with all the improvements that brings. Sure, some 'droid versions have compatibility with previous or later ODM blobs, but thatâs not the whole difference. SFOS is unfortunately stuck on whatever kernel version the port selects as a starting point (though it might get minor patches).
There was an update on 2024-08-01 in Sailfish Community News, 1st August 2024 - Jolla C2 :
To make our life easier in the future release, we have decided to go with the Android 14 base. Issue with Android 14 vendor blobs is that camera wonât start and needs to be disabled. Hopefully next version of the Android 14 vendor blobs contain the proposed fix. We asked from you, Sailfish Community, an opinion on how would you prefer this and seems that preferred approach is to release the free version quickly rather than waiting for the new vendor blobs. This means that the first version comes with disabled camera service. Reason for disabling is that broken camera service prevents suspend causing battery draining. Once we have the new Android 14 vendor blobs containing needed changes to fix the camera service, we do a minor Sailfish OS update to re-enable camera and provide instructions on how to flash the vendor blobs.
We also confirmed support for XQ-CC72 and XQ-DC72 variants of Sony Xperia 10 IV and Sony Xperia 10 V. These two devices need variant configurations meaning that we will create dedicated flashable images for XQ-CC72 and XQ-DC72 variants. The 72 variants are likely released separately right after XQ-CC54 and XQ-DC54 variants.
5 Likes
No, I am only saying that if A13 blobs are already there and satisfactory stable (if they are, I donât know, Iâm merely asking if it is the case as what Iâve heard so far from Jolla was quite vague) whereas the A14 blobs fixing the current serious issues with camera et al are in the âhopefully soonâ or âgiven that we get themâ degree of probability, then maybe it should be thought over once again. Thatâs all.
Right. So whatâs better: a (slightly) older kernel but physically available to use right now, or a newer (and better) kernel but currently blocked from serious use in SFOS by camera (and other power consumption related?) issues, which may get a fix from Sony âsoonâ, or maybe not so soon. I am not saying that the newer kernel wouldnât be highly desired, I am only afraid that it may not be a top priority for Sony to do it as quickly as Jolla would expect it, leaving us with no usable 10 IV / V support for months.
1 Like
Yes, but still in the âhopefullyâ form, like e.g.
meaning that while updated Android 14 based blobs will certainly come out relatively soon, there is no guarantee that they will contain that specific fix. And what if they donât? Itâs quite late already now.
1 Like
What are you up to, i.e. what are you arguing for (or against)?
Jolla made a decision, communicated it along reasoning, and described the possible routes for the near future. We both know that âcommunicating something with reasoningâ are two large steps in one go for Jolla, even if that is easy for most, especially both of us; so please ignore their use of explicitly undetermined and vague language, which is another well-known and long-standing tradition (almost a âmustâ) for sailors. One may call this tradition confusing and ill-fated, and I would not disagree; nevertheless, âit is what it isâ.
So for the Xperia 10 IV and V it is going to be a SailfishOS port on an Android 14 âbaseâ (i.e. firmwares etc.) utilising Sonyâs âsoftware binaries for AOSPâ 14. If the current release of the latter (Sonyâs âsoftware binaries for AOSPâ 14) does not provide a working camera when the SailfishOS port for these devices is about to be released, the Camera app is going to be disabled in the initial release(s). As soon as Sony releases a new âsoftware binaries for AOSPâ 14 which provides a working camera on the Xperia 10 IV and V, Jolla is going to prepare a new point release of SailfishOS, which re-enables the camera app.
I do not think there is anything unclear or left to discuss with this plan.
3 Likes
Not arguing, merely discussing, wondering. Or is it some kind of undisputable dogma?
Yes, just one thing: what âas soon asâ may mean, and what if it actually isnât soon.