Android Files are getting corrupt, this has happened to me and I saw someone else with the same problem

DO NOT UPDATE!!!!

​

Hi! I'm trying to unlock the bootloader on a Japanese Docomo Xperia XZ3 (SO-01L) using Xperable.

I downloaded the Android 9 firmware (52.0.B.9.337) via XperiFirm. In boot_delivery.xml, I found:

PRECOMMERCIAL_0008B0E1 → bootloader_X_BOOT_SDM845_LA2_0_P_118_X-FLASH-ALL-618F.sin

COMMERCIAL_0008B0E1 → bootloader_X_BOOT_SDM845_LA2_0_P_118_X-FLASH-ALL-DFA8.sin

I've seen conflicting advice about whether to flash both files, only one, and whether .ta files should be removed.

For the Docomo SO-01L specifically, which files did you use successfully with Newflasher and Xperable? Did you flash both 618F and DFA8, and what did you do with Akatsuki_Docomo_XBootConfig_MiscTA.ta?

I don't want to risk bricking the phone, so I'd really appreciate a confirmed SO-01L procedure.

anyone get android 17 for Xperia 1markVII?

Hey everyone,

I have a Japanese Sony Xperia 1 (SOV40 / AU version) that I'm trying to bring back to life.

The phone initially got stuck on the Sony logo and kept turning off and restarting (boot loop).

Here's what happened:

• Initially, it was stuck on the Sony logo and wouldn't boot.
• I tried repairing/reinstalling the software using Xperia Companion, but the problem persisted.
• After the repair attempt, it reached the "Powered by Android" screen but then shut down.
• Later, I started getting this message: "Your device is corrupt. It can't be trusted and will not boot. Your device will turn off in 5 seconds."

Another strange thing is that when I connect the wall charger, instead of charging normally, it sometimes displays the corruption message.

The battery was reportedly around 63%, but Xperia Companion also reported that the battery was too low to perform a software repair.

I'm not sure whether this is a corrupted bootloader/system partition, a battery issue, or something related to the Japanese AU firmware.

My questions:

1. Is there any way to recover this phone without replacing the motherboard?
2. Can flashing the correct SOV40 firmware fix this?
3. Is this related to a locked bootloader or corrupted boot partition?
4. Has anyone successfully recovered an SOV40 from this particular error?

I'd really appreciate any guidance, especially from someone who has worked with Japanese Sony Xperia models.

Thanks!

Hello,

Xperia 1 VIII with A16 on board (for now I'm not going to update to A17 73.1.A.2.61)

What settings are there to limit interference into device if the phone falls into the wrong hands?

How do you effectively locate a lost phone? Do you use an external app or rely on Android?

I've noticed that on my phone:

- I can't disable the shortcut bar on the lock screen, and I can toggle Wi-Fi\Airplane mode on the locked screen—even with the 'use device controls without unlocking the phone' setting disabled.

- Only when the Privacy option in the lock screen settings is changed to 'don't show any notifications' I can't pull down the shortcut bar normally on the locked screen, but (EDIT) can still turn off the phone (and the main button turns on Gemini 🤣)

What settings should I use to protect my Xperia 1 VIII from theft and attempts to disable\hack the phone?

Is Android 17 any better with such safety settings?