Problem with installing SailfishOS on XPeria 10 V (XQ-DC54)

Hey Guys,

I’m a long time user of Sailfish OS on Sony XPeria XA2 (which I installed personally) and Jolla C2 (which was installed originally of course). Now I bought Sony XPeria 10 V and trying to install Sailfish and… there’s a problem. I bought XQDC54 “version” - the one need for this OS.

But when I try to unlock to bootloader (I tap service info>Configuration>Rooting status, there’s a “statement” Bootloader allowed: no.

So what? There’s nothing I can do? No means no and no Sailfish OS for my device? I’m A BIT disappointed to be honest. Can someone help?

1 Like

Did you follow the instructions? Did you “become a developer“? (Chapter 6 in the guide).

Aim that at whoever locked toy out of your own phone that you bought and paid good money for, not anyone here.

Of course I did. I strictly follow the instruction here: How to install Sailfish X on Xperia™ 10 V on Windows - The Privacy Respecting European OS and AI Solution Provider

I’ve bought a brand new device - that’s the problem.

But here - on Sony page - it states:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.

Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked

That’s why I ask here - no means no and that’s all? I wasted quite a nice sum because NO? Help plz :frowning:

1 Like

6.3 and 6.4 specifically - what happens and how does it look?

In step 6 everything is perfectly fine. In 7.4 there’s everything ok UNTIL I get here

So I enable developer options, OEM unlocking (AND USB debugging of course), then “call” *#*#7378423#*#*, go to Service info > Configuration > Rooting Status aaaaaaand… see “Bootloader unlock allowed: No”.

I even tried to override it, triggering 7.12, but the command is rejected.

Btw. - thanks your will to help :slight_smile:

1 Like

If this is the case there is nothing you can do. There seem to be more of these non-unlockables around these days, if you buy secondhand get the owner to check; if you buy new it’s a gamble. There used to be a tool called Qunlock for windows, it cost about 30€ per operation but it’s no longer available. Repackage the phone and sell it “as new.”

Out of curiosity, is it retail or carrier’s provided device?

Oh damn…

In retail, a german store.

1 Like

This is weird. I have the same phone model and it worked for me (it worked with some issues, but not at that step of the guide).

First of all, I strongly recommend you do not use the Xperia 10 V for Sailfish OS.
The phone is not actually supported, unless by “supported” you mean “half-assed guide available to flash Sailfish OS on it”.

Unless you are a masochist or you don’t plan to use the phone as a regular phone, I recommend you return the Xperia to the seller and buy a Jolla C2 instead.
That fugly joke of a phone is the only one somewhat supported, but make sure you read the forums before first use to find out all the rituals you need to perform for it to not brick itself, because that turd of a phone tends to brick itself right out of the box.

Back to Xperia 10 V:
Can you install AIDA64 and see what hardware you have?
My model is the same as yours, but maybe there is some other more subtle difference.

1 Like

Which are the current problems in the Xperia 10 V?

1 Like

It’s probably hardlocked. I’m trying to contact any Sony Developer - it’s my last hope.

I don’t know all of them, but the ones that I encounter every time I turn on the phone are the fact that camera does not work, the fact that the fingerprint does not work, the fact that the battery percentage indicator never gets updated (it always shows the value computed when the phone starts) and the fact that the keyboard does not have word prediction and, implicitly, no swipe typing.

There might be more issues, but in the current state, I can’t even use the phone for long enough periods of time to encounter other issues.

I just purchased a refurbished one online and ran into the same issue.

There is nothing you can do, you need to send the phone back if you can or resell it.

I sent it back, I will try with another one.

Please note my extreme frustration in the difficulty to get a decent SFOS device. I would even accept a C2, but I cannot purchase a device that I will have to ditch in two years’ time because there is no way to get a replacement battery, let alone a screen or a protective case.

1 Like

Jolla C2 is a fugly turd of a phone, and I don’t know what you should do when the battery dies (maybe send it to Jolla for a battery replacement? You should ask Jolla about this), but you can definitely buy cases and screen protectors from the Jolla store.

2 Likes

Well, maybe that’s the reason why they gave lifelong SFOS support for free.

In the span of three years from now there will be no more working C2’s.

Maybe you can take a new battery from another device that fits physically and has the same parameters (voltage, max voltage, capacity, NTC sensor).

I could test it in our workshop when my C2 battery gets worse. We have access to spare parts from common brands.

1 Like

That’s what I did with the Jolla 1. There was a ZTE device with the same battery but with different contacts. I ended up creating fake contacts with copper band. They worked indeed. But it was a PITA.

Or, now that I think better, that was the Jolla C. For the Jolla 1, I had to recreate the top part of the battery using dual component epoxy resin embedding the original PCB of the battery.

1 Like