GGsmZone

Post

Hi, I need professional recovery/service assistance for a **POCO M7 Pro 5G / Redmi Note 14 5G (Beryl), India variant** that is currently soft-bricked and only reliably accessible in **MediaTek BROM mode**. **Device details** * Model: POCO 2409FPCC4I * Platform/device: Beryl * India E-Commerce Edition * SKU: MZB0ICAIN * SoC: MediaTek MT6855 * BROM HWCODE: `0x1129` * HW subcode: `0x8A00` * HW version: `0xCA00` * Target configuration: `0xE7` * SBC: Enabled * SLA: Enabled * DAA: Enabled * ME_ID / SOC_ID available if required for service authentication **Current condition** The phone no longer boots into Fastboot or Android reliably. It repeatedly shows the Xiaomi/POCO logo, goes black, and restarts. When forced into BROM, it reliably enumerates as: `0E8D:0003 — MediaTek USB BROM` I have successfully communicated with the device using **native Arch Linux + libusb** and `mtkclient`. **Confirmed BROM behavior** * BROM handshake: successful * `gettargetconfig`: successful * HWCODE `0x1129`: confirmed * Target config `0xE7`: confirmed * `SLA=True`: confirmed * `DAA=True`: confirmed * Attempting DA upload returns: `0x1D0D — SLA required` The device therefore reaches BROM correctly but blocks DA execution at the SLA boundary. **Files available** I have the original India/global Beryl firmware package, including: * `preloader_beryl.bin` * `DA_BR.bin` * `auth_sv5.auth` * complete partition images * MT6855 scatter/configuration files The firmware images and CRC/sparse-CRC data have already been checked for internal consistency. **Important:** I am specifically looking for a service/tool that can handle **MTK V6 / MT6855 / HWCODE 0x1129 / target-config 0xE7 with SLA enabled**, in BROM mode. A generic statement that MT6855 or Beryl is supported is not sufficient. ### Service requested I need you to: 1. Authenticate the device in BROM/MTK V6 mode using your server/service authorization, if supported. 2. Load the appropriate DA/authorized loader. 3. Restore the damaged or stale bootloader/preloader state. 4. Restore the correct stock Beryl firmware as necessary. 5. Return the phone to a normal boot/Fastboot state. 6. Preserve user data where technically possible, but I understand that a full firmware recovery may require data loss. I am **not requesting FRP bypass or account bypass**. I am requesting recovery of my own device from a software/boot failure. ### Please confirm before payment Can your current service explicitly support: `POCO 2409FPCC4I` `Beryl` `MT6855 / HWCODE 0x1129` `Target config 0xE7` `SLA enabled` `BROM mode` `DA upload blocked with 0x1D0D` I can provide the full BROM log, target configuration output, firmware package information, and device service identifiers privately if required.
Help RequestOpen

Comments

Sign in to comment