The System Has Been Destroyed - Xiaomi Poco X3 NFC Questions & Answers

So I tried to install TWRP from this website
Download And Install TWRP on Xiaomi Poco X3 NFC - FlashXiaomi
Download And Install TWRP on Xiaomi Poco X3 NFC allows facilitates the use of custom software, including the latest custom ROMs, kernels...
flashxiaomi.com
& stupidly me replaced the twrp file with "twrp-3.4.0-15-surya-mauronofrio" then finished the following instruction( I think the twrp won't match with vbmeta.img stuff like that) after that my phone stuck on logo and try to turn off & on it say Destroyed like the title. pls Help me

Hello. When trying to boot, try to catch fastboot, it should come in. I also had one and I could do it fastboot + miflash.

rambo1155 said:
Hello. When trying to boot, try to catch fastboot, it should come in. I also had one and I could do it fastboot + miflash.
Click to expand...
Click to collapse
yeah I'm to confident using CMD, that more safe & likely work with Mi Tool. ty anyway

I had similiar situation and all I did was I flashed different version of TWRP and it worked.

Related

F2 Pro completely stuck

Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file

Bootloop after installing V12.2.1.0.RJAMIXM

Hi XDA community
I'm struggling with my Mi 10 Pro after installing V12.2.1.0.RJAMIXM global verison and can't get the phone to boot up again. As already mentioned in the title, the phone stuck in an bootloop. The Mi logo is shown up for few seconds and the phone is restarting again.
Before, I was on EEA V12.0.5.0.QJAEUXM, unlocked bootloader and rooted with Magisk over fastboot with patched boot.img, so no TWRP at all. Additional task "--disable-verity --disable-verification flash vbmeta vbmeta.img" was done, to be able to mount system partition as r/w to remove some unwanted apps, no problems at all.
I've tried to reinstall the EEA version V12.0.5.0.QJAEUXM again, also the global version V12.0.5.0.QJAMIXM, both with Fastboot ROMs manually over flash_all.bat and over the Mi flash tool, but no success, phone is still in bootloop.
The strange thing is, over TWRP I was able to install the latest xiaomi.eu and also the stock EEA V12.0.5.0.QJAEUXM Recovery ROM, where the phone is finally booting up. But even after stock EEA V12.0.5.0.QJAEUXM Recovery ROM over TWRP, if I'm trying to install the Fastboot version over it, the phone ends again in an bootloop.
Does anybody have an idea what I've messed up and how to fix it?
Many thanks and best
Adnan

Xiaomi Redmi Note 4 (Snapdragon) flashing problem.

Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..
Can you boot up normally?
If not what happens, when you try?
gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.
Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician

how to reinstall Oxygen OS

HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/

Redmi 9 hard brick, bootloop and CAN'T ACCESS FASTBOOT

I was trying to install TWRP using fast boot. At first I was using the usual commands,
fastboot flash recovery twrp.img
fastboot flash (some command) vbmeta vbmeta.img
and it would just boot directly into the system (twrp wouldn't work)
then I did it again but I added
fastboot flash misc misc.bin
And now my phone is stuck in a bootloop. Whatever I do it just goes to the Redmi logo screen, then turns off, and turns on again by itself. (I can't even turn it off)
I say this again: I cannot access fastboot. Is there a possible solution to this or is the phone gone for good? (OEM unlocking was unlocked, I'm sure of it)
Try to re-flash phone's Stock ROM.
xXx yYy said:
Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
I can't access neither fastboot nor recovery, how do i do that?
Xiaomi MI Flash Tool can flash in fastboot mode or EDL mode. consider deep flash cable.
edit: misc partition is mediatek. erase misc partition from mtkclient
there is a (paid) Xiaomi Pro Tool v3.8 for mediatek on post #28
cross posted here (1)
aIecxs said:
Xiaomi MI Flash Tool can flash in fastboot mode or EDL mode. consider deep flash cable.
edit: misc partition is mediatek. erase misc partition from mtkclient
Click to expand...
Click to collapse
Thank you. I fixed it and flashed it with SP Flash Tool and a python script to bypass Xiaomi protection
Nuythe said:
Thank you. I fixed it and flashed it with SP Flash Tool and a python script to bypass Xiaomi protection
Click to expand...
Click to collapse
bro please provide steps plox
Nuythe said:
Thank you. I fixed it and flashed it with SP Flash Tool and a python script to bypass Xiaomi protection
Click to expand...
Click to collapse
I think I have the same problem after downgrading from 13.0.5 Miui 13 CN rom to 11.0.4 Miui 11 Global rom. Lolz
I'm already on the part where I can bypass but I can't proceed to downloading the firmware to my phone w/ SP flashtool because my Redmi 9 keeps on bootlooping everytime it connects
In your case, were you in point where you need to open the backcase of the phone so that you can manually remove the battery so that it doesn't keep on reconnecting during flashing?
sturzerblitz said:
I think I have the same problem after downgrading from 13.0.5 Miui 13 CN rom to 11.0.4 Miui 11 Global rom. Lolz
I'm already on the part where I can bypass but I can't proceed to downloading the firmware to my phone w/ SP flashtool because my Redmi 9 keeps on bootlooping everytime it connects
In your case, were you in point where you need to open the backcase of the phone so that you can manually remove the battery so that it doesn't keep on reconnecting during flashing?
Click to expand...
Click to collapse
The timing is a bit tricky. Just keep doing it, it'll eventually connect in the right time and stop bootlooping.
Nuythe said:
The timing is a bit tricky. Just keep doing it, it'll eventually connect in the right time and stop bootlooping.
Click to expand...
Click to collapse
Yep you're right! timing is essential, I actually have fixed it and not needed to open the back case to manually remove the battery. I just tried another port, waited until it stops bootlooping after the bypass and followed those succeeding steps again.
But...
After successfully flashing with my stock firmware and updating it to MIUI 12.5.6 Global. It seems the bootlooping wrecked the hell out of my battery and I'm always suffering with occasional reboots everytime I maxxed out the volume and whenever I tried to call. Seems my phone is getting weak current or battery supply, sucks.

Categories

Resources