• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Hard Bricked Poco X3 NFC

Search This thread

BjornBear

Member
Jul 13, 2015
5
3
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?

Welcoming all advice/condolences.
 

SkaboXD

Senior Member
Jan 18, 2017
1,068
390
Ganja
Xiaomi Poco X3 NFC
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?

Welcoming all advice/condolences.

You need EDL Flash
 
  • Like
Reactions: BjornBear

MocnePifko

Senior Member
Jan 24, 2015
54
42
Xiaomi Poco X3 NFC
It's all good. If it's already being recognised by your PC just flash the correct stock ROM using Mi Flash Tool ad you're golden. Just make sure it's the tight one fore your device and you've checked "clean all" option in Mi Flash Tool.

BTW if you end up in a boot loop after flashing a ROM again make sure you do "FORMAT DATA" not "wipe data". It is not the same thing!
 
  • Like
Reactions: BjornBear and pnin

ineedroot69

Senior Member
Nov 13, 2019
825
1
176
there should be a speedrun for bricking your device

also how did you wipe your data partition? fastboot erase userdata ??
try restoring it via fastboot format:ext4 userdata
 
  • Like
Reactions: BjornBear

BjornBear

Member
Jul 13, 2015
5
3
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.



Best of luck.
Thanks everyone for your help so far. I was considering paying for an EDL flash service (someone I know had theirs done successfully through an account on Telegram) Unfortunately the Mi Flash Tool doesn't seem to be working. I can't even get up to the bit where it would ask for an authorised Xiaomi EDL account. After clicking flash it just says 'timeout maybe the device was unplugged' or something like that and returns this string of code (taken from flash.bat)

fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || exit /B 1 set CURRENT_ANTI_VER=2 for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i) if [%version%] EQU [] set version=0 if %version% GTR %CURRENT_ANTI_VER% ( echo current device antirollback version is greater than this package exit /B 1 ) fastboot %* flash xbl %~dp0images\xbl.elf || @echo "Flash xbl error" && exit /B 1 fastboot %* flash xblbak %~dp0images\xbl.elf || @echo "Flash xblbak error" && exit /B 1 fastboot %* flash xbl_config %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1 fastboot %* flash xbl_configbak %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1 fastboot %* flash imagefv %~dp0images\imagefv.elf || @echo "Flash imagefv error" && exit /B 1 fastboot %* flash imagefvbak %~dp0images\imagefv.elf || @echo "Flash imagefvbak error" && exit /B 1 fastboot %* flash aop %~dp0images\aop.mbn || @echo "Flash aop error" && exit /B 1 fastboot %* flash aopbak %~dp0images\aop.mbn || @echo "Flash aopbak error" && exit /B 1 fastboot %* flash uefisecapp %~dp0images\uefi_sec.mbn || @echo "Flash uefisecapp error" && exit /B 1 fastboot %* flash uefisecappbak %~dp0images\uefi_sec.mbn || @echo "Flash uefisecappbak error" && exit /B 1 fastboot %* flash qupfw %~dp0images\qupv3fw.elf || @echo "Flash qupfw error" && exit /B 1 fastboot %* flash metadata %~dp0images\metadata.img || @echo "Flash xbl error" && exit /B 1 fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1 fastboot %* flash tzbak %~dp0images\tz.mbn || @echo "Flash tzbak error" && exit /B 1 fastboot %* flash hyp %~dp0images\hyp.mbn || @echo "Flash hyp error" && exit /B 1 fastboot %* flash hypbak %~dp0images\hyp.mbn || @echo "Flash hypbak error" && exit /B 1 fastboot %* flash keymaster %~dp0images\km4.mbn || @echo "Flash keymaster error" && exit /B 1 fastboot %* flash keymasterbak %~dp0images\km4.mbn || @echo "Flash keymasterbak error" && exit /B 1 fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1 fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1 fastboot %* flash cmnlib64 %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1 fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1 fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1 fastboot %* flash dsp %~dp0images\dspso.bin || @echo "Flash dsp error" && exit /B 1 fastboot %* flash bluetooth %~dp0images\BTFM.bin || @echo "Flash bluetooth error" && exit /B 1 fastboot %* flash storsec %~dp0images\storsec.mbn || @echo "Flash storsec error" && exit /B 1 fastboot %* flash devcfg %~dp0images\devcfg.mbn || @echo "Flash devcfg error" && exit /B 1 fastboot %* flash abl %~dp0images\abl.elf || @echo "Flash abl error" && exit /B 1 fastboot %* flash ablbak %~dp0images\abl.elf || @echo "Flash ablbak error" && exit /B 1 fastboot %* flash dtbo %~dp0images\dtbo.img || @echo "Flash dtbo error" && exit /B 1 fastboot %* flash vbmeta %~dp0images\vbmeta.img || @echo "Flash vbmeta error" && exit /B 1 fastboot %* flash boot %~dp0images\boot.img || @echo "Flash boot error" && exit /B 1 fastboot %* flash recovery %~dp0images\recovery.img || @echo "Flash recovery error" && exit /B 1 fastboot %* flash super %~dp0images\super.img || @echo "Flash super error" && exit /B 1 fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1 fastboot %* flash vbmeta_system %~dp0images\vbmeta_system.img || @echo "Flash vbmeta_system error" && exit /B 1 fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1 fastboot %* flash ffu %~dp0images\ffu.img || @echo "Flash ffu error" && exit /B 1 fastboot %* flash cache %~dp0images\cache.img || @echo "Flash cache error" && exit /B 1 fastboot %* erase misc fastboot %* erase apdp fastboot %* erase multiimgoem fastboot %* reboot

These parts worry me:

"product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device"
and
"current device antirollback version is greater than this package"

Does anyone know what else I could try? I found this (https://romprovider.com/test-point-poco-x3-reboot-edl-mod/) but it's using software I'm unsure of. Is this my only option now do you think?
 
Last edited:

j49

Senior Member
Feb 22, 2016
58
15
Try to move the MiFlash folder to the root directory (i.e. C:/MiFlash) and put the ROM inside the MiFlash folder and proceed this way. You never know ......
 
  • Like
Reactions: BjornBear

BjornBear

Member
Jul 13, 2015
5
3
Okay so I might get into trouble for this but SkaboXD was right, the only thing that would fix my phone was an EDL flash. I tried everything and this was the only thing that worked. I found a YouTuber by the name of Munchy (who basically spends his time telling people how to avoid tech scams) who endorsed a guy operating exclusively on Telegram on his video.

Seeing as so many people are being scammed for EDL accounts at the moment because real ones are like gold dust I think I'll take the risk of the banhammer to recommend (the guy the YouTuber endorsed) Angeluss69 on Telegram. I paid in Bitcoin because I wanted to stay anonymous but he accepts PayPal business and I don't know maybe he accepts more transfer types, didn't ask. I won't quote his prices just in case that isn't allowed but it's not so bad and he's running what seems like an honest business so I say it's worth it when compared to the expensive brick I had an hour ago. He's Spanish and his English isn't so good so he uses the Telegram in-built translator but it works well enough and he's quite friendly.

Sidenote: Apparently the reason why Xiaomi refused to fix my phone is because most staff don't have Authorised EDL accounts in their repair centers. This kind of makes sense. Gotta admit though, I'm curious as to how the heck he got that account. I'm putting up pictures as proof. Do your worst, Admins.
 

Attachments

  • IMG_20210408_014602_508.jpg
    IMG_20210408_014602_508.jpg
    63.5 KB · Views: 30
  • IMG_20210408_014137_957.jpg
    IMG_20210408_014137_957.jpg
    71.2 KB · Views: 30
  • IMG_20210408_014529_374.jpg
    IMG_20210408_014529_374.jpg
    70.4 KB · Views: 30
Last edited:
  • Like
Reactions: pnin and iakoboss7

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    condolences...
    2
    It's all good. If it's already being recognised by your PC just flash the correct stock ROM using Mi Flash Tool ad you're golden. Just make sure it's the tight one fore your device and you've checked "clean all" option in Mi Flash Tool.

    BTW if you end up in a boot loop after flashing a ROM again make sure you do "FORMAT DATA" not "wipe data". It is not the same thing!
    2
    Okay so I might get into trouble for this but SkaboXD was right, the only thing that would fix my phone was an EDL flash. I tried everything and this was the only thing that worked. I found a YouTuber by the name of Munchy (who basically spends his time telling people how to avoid tech scams) who endorsed a guy operating exclusively on Telegram on his video.

    Seeing as so many people are being scammed for EDL accounts at the moment because real ones are like gold dust I think I'll take the risk of the banhammer to recommend (the guy the YouTuber endorsed) Angeluss69 on Telegram. I paid in Bitcoin because I wanted to stay anonymous but he accepts PayPal business and I don't know maybe he accepts more transfer types, didn't ask. I won't quote his prices just in case that isn't allowed but it's not so bad and he's running what seems like an honest business so I say it's worth it when compared to the expensive brick I had an hour ago. He's Spanish and his English isn't so good so he uses the Telegram in-built translator but it works well enough and he's quite friendly.

    Sidenote: Apparently the reason why Xiaomi refused to fix my phone is because most staff don't have Authorised EDL accounts in their repair centers. This kind of makes sense. Gotta admit though, I'm curious as to how the heck he got that account. I'm putting up pictures as proof. Do your worst, Admins.
    1
    So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
    Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
    Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
    It's a goner, isn't it?

    Welcoming all advice/condolences.

    You need EDL Flash
    1
    I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.



    Best of luck.