[GUIDE] Unbrick / Hard Brick Recovery Moto G14 (XT2341-2) - Restore GPT & System (Unisoc) (Safety patch, August 2026)

[GEDByR]

Disclaimer: I am not responsible for bricked devices, dead SD cards, or thermonuclear war. Proceed at your own risk. This process will wipe all user data.

This guide will help you revive a hard-bricked Moto G14 (XT2341-2) featuring the Unisoc T616 processor (black screen, dead, only port detected). We will use a dump and the spd_dump tool to rebuild the partition table and bootloaders.

Prerequisites & Tools

• Drivers: Spreadtrum / Unisoc Drivers (SPRD U2S Diag). Ensure Windows Driver Signature Enforcement is disabled if the port isn't recognized.
  Direct link to download⇝Spreadtrum / Unisoc Drivers (SPRD U2S Diag)
  
  
• Core Tool: spd_dump (Stable Windows release).
  I included this tool in the DUMP zip, just download the zip, unzip and inside the folder you will find all the files that you are going to occupy, you just have to download the drivers and SoftwareFix, I share the rest together, so that they only open the console in the folder that comes out of the zip and copy and paste the commands.
  
  
• Official Tool: SoftwareFix (Motorola Rescue and Smart Assistant - RSA) installed on your PC.
  Direct link to download⇝Motorola Rescue and Smart Assistant - RSA
  
  
• Firmware/Dump Files: Download the attached ZIP in this thread and extract absolutely everything into the same folder containing spd_dump.exe.
  Link to the zip with the dump, the parts to be flashed separately and what is necessary for the correct functioning of the commands uploaded to Google Drive. No password, free.
  
  
• Battery: At least 50% charged.
• Hardware: A good quality USB cable and tools to open the back cover (if Testpoint is required).

How to Connect (BROM / SPD Mode)

Depending on your brick state and security patch, there are three ways to trigger the required port:

1. Auto-connect: If the device has a completely wiped eMMC/UFS, simply plugging it in while powered off might trigger the port.
2. Button Combo: With the phone off, hold Volume Up + Volume Down simultaneously and plug in the USB cable.
3. Hardware Testpoint (Mandatory for High Security): If the above methods fail or your phone has a recent security patch, you must remove the back cover. Locate the Testpoint on the motherboard, short it to a ground shield using tweezers, and plug in the USB cable.
   
   Testpoint

Phase 1: Initial Connection & Repartitioning​

1. Open your working folder (where you extracted the ZIP), type cmd in the Windows address bar, and hit Enter.
2. Paste the following command and press Enter:

spd_dump --wait 60 exec_addr 0x65015f08 fdl fdl1-dl.bin 0x65000800 fdl fdl2-dl.bin 0x9efffe00 exec

1. Connect the phone using one of the methods above. Once successfully connected, the console will change and display the FDL2> prompt at the beginning of each line. Note: The connection is now stable; if you used a Testpoint, you can release the tweezers now.
2. Enter the following commands one by one (hit Enter after each). The first two configure the tool, the latter ones execute the flashing. Let each process reach 100% before typing the next one:

timeout 100000
blk_size 0x3000
repartition partition.xml
write_parts dump
reset

Example of correct reading and writing

Phase 2: System Recovery (Two Scenarios)​

Immediately after sending the reset command, the phone will drop the connection. Hold down Volume Down + Power. One of two things will happen:

Scenario A: Boots directly to Fastboot

• If you reach the Fastboot screen, launch SoftwareFix (Motorola RSA) on your PC and click "Rescue".
• The official tool will download clean firmware and flash it. Once finished, the phone will reboot automatically, fully recovered.

Scenario B: BROM / SPD Bootloop (Black Screen)

• If holding the buttons forces the phone back into the BROM/SPD port instead of Fastboot (which happened to me), close the current CMD and open a new one in your working folder.
• Run the initial connection command again:

spd_dump --wait 60 exec_addr 0x65015f08 fdl fdl1-dl.bin 0x65000800 fdl fdl2-dl.bin 0x9efffe00 exec

• Once you see FDL2>, manually flash these critical partitions to force the bootloader to wake up:

timeout 100000
blk_size 0x3000
write_part splloader u-boot-spl-16k-ufs-sign.bin
write_part uboot lk-sign.bin
write_part boot boot.img
write_part vendor_boot vendor_boot.img
write_part init_boot init_boot.img
write_part dtb dtb.img
write_part dtbo dtbo.img
write_part vbmeta vbmeta.img
write_part vbmeta_system vbmeta_system.img
write_part vbmeta_vendor vbmeta_vendor.img
write_part vbmeta_system_ext vbmeta_system_ext.img
write_part vbmeta_product vbmeta_product.img
write_part vbmeta_odm vbmeta_odm.img
reset

• After the reset command, immediately hold Volume Down + Power until the Fastboot menu appears.
• Open SoftwareFix (Motorola RSA) and rescue the device to complete the process.

Extra: Bootloader Unlock (Optional)​

If you need to unlock the bootloader, I've attached an automated script in the ZIP.

1. Do this only after fully recovering the phone and letting it boot completely to the Android setup screen.
2. Power off the phone. Because SoftwareFix flashes the latest high-security patch, you MUST open the phone and perform the Hardware Testpoint so the tool can bypass BROM security.
3. Run the unlock_autopatch_9230.bat file and connect your device via Testpoint when prompted by the script. (Tip: You can right-click > Edit the .bat file in Notepad to verify its commands and ensure it is safe to use).

That would be all from me, good luck. Thanks to ilyakurdyukov for creating the spreadtrum_flash tool.