In TWRP, go to Wipe and perform a Factory Reset .
This means that even with an unlocked bootloader, you may not be able to simply flash a global stock ROM. This is where the next step comes in: installing a custom ROM.
This is a carrier-level restriction. Sony has confirmed that DOCOMO versions of Xperia devices are excluded from its official bootloader unlock program. For Samsung, Google Pixel, and other manufacturers, a DOCOMO-branded device almost always arrives with this flag set to "No," preventing any official unlocking method.
Re-flash the original baseband, modem, and EFS partition images from your device's original stock Docomo firmware dump using Fastboot. Issue 3: Mobile Payment Apps Crash docomo unlock bootloader install
Global variants of phones from Sony, Samsung, or Google often support official bootloader unlocking via developer websites. Docomo variants (such as Sony Xperia "SO" models or Samsung Galaxy "SC" models) actively disable these official channels.
Before attempting any procedures, you must verify your device's current status.
If visible, toggle on . (Note: If this option is greyed out or missing, your specific Docomo model may require an exploit or third-party paid service to unlock). Phase 2: Unlocking the Docomo Bootloader In TWRP, go to Wipe and perform a Factory Reset
Go to the main menu of TWRP, select Reboot , and tap System .
Once your bootloader is unlocked (either permanently or temporarily), you can install custom software. The following steps are general guidelines for Xperia DOCOMO devices after unlocking:
Before attempting an unlock, you must prepare the device environment: Enable Developer Options This is a carrier-level restriction
If your device says for unlocking, the standard installation flow is:
Boot the phone back into Fastboot mode and connect it to the PC. In the command prompt, flash the recovery image: fastboot flash recovery recovery.img Use code with caution.
Are you planning to target a like LineageOS or Pixel Experience?
Unlocking the bootloader on NTT Docomo devices is generally restricted by the carrier, preventing the installation of custom ROMs or recoveries like TWRP. While Docomo offers a streamlined process for SIM unlocking
| Problem | Likely Cause | Solution | |---------|--------------|----------| | fastboot devices shows nothing | Driver issue | Reinstall device drivers (use Google USB Driver for Windows or check your system's driver manager). | | fastboot oem unlock fails with "remote: Command not allowed" | Bootloader is locked and "unlock allowed" is NO | You need a commercial tool or the xperable exploit — official methods will not work. | | xperable returns "No such file or directory" | You did not download the correct payload blob | Download the appropriate p118 or o82 blob from SourceForge and place it in the same folder as xperable.exe . | | Device is stuck in a bootloop after flashing | Wrong kernel or boot image compatibility | Boot into recovery (usually Power + Volume Down) and restore your backup, or reflash the original stock firmware with Flashtool or Newflasher. | | Camera quality is poor after unlocking | DRM keys were lost | If you did not back up TA before unlocking, there is no way to restore the original keys. Some custom ROMs include partial DRM fixes, but full restoration is impossible. | | Phone shows "bootloader unlocked" but won't boot custom ROMs | Bootloader signature enforcement may still be active | Use the xperable exploit each time you boot an unsigned image, or flash a custom recovery that disables signature checks. |