Is there any possibility that a screen+frame replacement on an xperia 10 iii could interfere with encryption?

Yesterday I received a replacement screen+digitizer+frame set (“original” from Aliexpress) in order to service my broken xperia 10 iii. (Note that I have plenty of patience and experience to practice such simple tasks, and I do it only on my personal devices, mainly as a hobby)

Long story short, after carefully transferring all hardware from my damaged device to the new frame set, I tried to power it up before gluing it for the final check. The device powers up, shows the “Unlocked device” warning, shows the SONY logo and then shows the SAILFISH OS logo with the notification LED turned green, and stays there for ever. I could also enter recovery.

Then, carefully transferring the device internals back to the old frame, the device boots normally.

After very close inspection and comparison of both frames when both completely stripped, I cannot find any difference what-so-ever…

I just gave up trying, and will see what I can do tomorrow.

And now the stupid question…
Is there any chance that the new screen+digitizer affects the device encryption?

It could be a faulty replacement part, it did come from Aliexpress after all.

1 Like

Why do you say encryption and not just bootup in general?
That seems much more likely…

2 Likes

I ordered similar set one month ago and it worked fine. I checked screen functionality only cables attached.

1 Like

This means that SFOS boots up but gets stuck somewhere. You probably need to enable persistant journaling, reproduce the problem, then get the logs.

All this is relatively straightforward once you know how to get into recovery, but somebody made a script around it, with an article that explains the process.

Disclaimer: linking to this article does not mean I will read all your logs.

1 Like

Maybe the plug of the new screen or some part of the rear part of the new cabinet has bad contact, or some part of the rear cabinet is incompatible (wireless charging coil). I suggest for a test, use the new display and the old rear part of the housing and test again.

2 Likes

Thank you guys for the replies! And yes, you were right, it was a boot-up hardware check fail after all.

Well, long story short, there was a short-circuit between the digitizer cable and the chasis, and a small bit of isolation tape solved the problem!

How I found the root of the problem? Well, after a few trials, the device would boot (short-circuit not present during time of boot possibly), but would lose digitizer response every now and then while in the OS. Pulling up the screen cable connection would solve the issue temporarily. Applied a tiny bit of isolation tape, and problem solved.

3 Likes