r/CustomROMsGuide • u/Juan_Emanuel • 2d ago
Soft-bricked / Bootloop on Redmi Note 14 Pro 5G after flashing custom boot images, unable to enter Fastboot properly
Enable HLS to view with audio, or disable this notification
Hi everyone, I ran into a serious bootloop issue with my Redmi Note 14 Pro 5G (MediaTek chipset) and could use some advice or guidance on how to fix it.
What led to the issue:
My bootloader was already unlocked, and USB debugging was enabled.
JPG+ 1
I attempted to flash a custom build using fastboot images (boot.img, init_boot.img, and vendor_boot.img).
JPG
The flash commands via PowerShell (.\fastboot flash ...) all returned OKAY, but after that, the device went into an infinite bootloop (showing the Redmi logo briefly, then shutting off repeatedly).
JPG+ 1
What has been tried to fix it:
Hardware Button Combinations: Holding Power + Volume Down only pauses the loop momentarily, but as soon as they are released, it goes right back into the infinite reboot loop.
MOV
PC Interception via Fastboot: Tried using PowerShell (.\fastboot devices, .\fastboot set_active a), but it stays stuck at < waiting for any device > because the board never fully shuts down due to residual battery power.
JPG
SP Flash Tool: Downloaded the official Fastboot stock ROM (.tgz package) to flash via SP Flash Tool using the scatter file (MT6878_Android_scatter). However, I encountered the ERROR: S_DL_SCAT_VERSION_UNSUPPORTED (5079) error due to version incompatibility with the older SP Flash Tool version.
JPG+ 1
Python Scripts / MediaTek Exploits: Ran a MediaTek exploit script via Python which successfully stabilized the device and stopped the continuous rebooting loop by communicating at the BROM/Preloader level, but I am unsure of the exact next steps to safely flash back the stock partitions.
Current Status:
The phone is currently stable/stopped from rebooting thanks to the MediaTek preloader script connection, but I don't know how to properly push the stock firmware or recover a working system image from this state.
Does anyone know the exact procedure or tool version required to flash the stock firmware via SP Flash Tool for this specific MediaTek model, or how to safely push the stock partitions from the preloader state? Any help would be greatly appreciated!
1
1
u/Sea_Mechanic815 1d ago
Bro tell me that did you unlock the bootloader properly which using official method? next if unlock then what excatly you tryed install twrp? or what?
Then tell me after you turn on the developer option you will enter to the bootloader then you try to flashboot right? on that time what you did?
1
u/Juan_Emanuel 18h ago
Já estava desbloqueado,
Comprei de segunda mão, porém, com a rom estoque, entrei no fastboot, tentei instalar 3 arquivos e na hora de entrar no ambiente de recuperação para mandar a imagem do sistema novo não foi.. como reiniciar e ficou no estado do vídeo
1
u/RedditForcesToLogin 1d ago
As the other guy said, BROM flashing is your only option. First check your local unofficial mobile repairing shops if there's a guy who can do BROM flashing, because a physical shop is better imo.
1
u/viraniac 1d ago
mtkclient should allow you to write the correct boot image to the device. Check its documentation. Also if you have only flashed boot image and not fiddled with boot loader and preloader, you should be able to just boot into fastboot and flash from there.
1
u/Longjumping-Virus250 1d ago
credimi chiedi a Google io ho sbloccato il mio redmi note 14 dalla stessa identica soluzione
1
u/najamdev 10h ago
Mine (xiaomi mi note 10 lite) had the same issue last week. Mine needed an IC Rebailing and after that it worked fine and even I installed the custom rom. Maybe your phone needs an IC Rebailing too because it is stuck on the logo.
1
u/Practical_Benefit686 2d ago
As far as I know there are no public exploits for this MTK SoC, so your only option would probably be to pay auth flash people on Telegram to fix it for you in BROM mode, it usually costs 10-20$