Develop Bugs

Cannot Go Back :'(

Please someone help me.
I unlocked my bootloader and flashed TWRP to get the flavours of custom ROMS on my new (1 week old) Lenovo Z2.
But due to some reason i cannot get VOLTE to work on any ROM.
Now I want to go back to my stock ZUI 2.5.104ST through QFIL or MiFlash.
But I cannot enter EDL mode by any means.
I can get to the diagnostic mode by keeping the power button pressed for 2 reboots. But no way can i get to the very necessary EDl mode.
Please someone help me reach the EDL mode.
Please :crying:

Are you able to connect to ADB?
If yes, you can type 'adb reboot edl'
This will put your phone in edl mode after which your qfil will show Qualcomm 9008 mode

Sam3087 said:
Are you able to connect to ADB?
If yes, you can type 'adb reboot edl'
This will put your phone in edl mode after which your qfil will show Qualcomm 9008 mode
Click to expand...
Click to collapse
Thank you so much for your response but yes I can access adb but when I enter adb reboot edl, it reboots normally and not into edl.
The press volume keys within 5 seconds screen pop up and after that it boots to the OS.
Please help:crying:

Shinichi Kudo said:
Please someone help me.
I unlocked my bootloader and flashed TWRP to get the flavours of custom ROMS on my new (1 week old) Lenovo Z2.
But due to some reason i cannot get VOLTE to work on any ROM.
Now I want to go back to my stock ZUI 2.5.104ST through QFIL or MiFlash.
But I cannot enter EDL mode by any means.
I can get to the diagnostic mode by keeping the power button pressed for 2 reboots. But no way can i get to the very necessary EDl mode.
Please someone help me reach the EDL mode.
Please :crying:
Click to expand...
Click to collapse
You can find flashable zips for ZUI, search the forum

visheshjain25 said:
You can find flashable zips for ZUI, search the forum
Click to expand...
Click to collapse
Thank you so much for your reply once again, but I have some queries., if you don't mind.
I just flashed stock ZUI TWRP flashable and VOLTE is back. And now flashing other ROMS makes VOLTE work. Twisted logic as I just came from stock.
But can I never go back to complete stock with locked bootloader? Can i never use QPST/QFIL or MiFlash ever again? Am I completely done for?
And finally, my benchmark on antutu is very low and this thread
https://forum.xda-developers.com/showpost.php?p=72341523&postcount=28
Says to update baseband to 1.7066.
But this post warns to do so
https://forum.xda-developers.com/showpost.php?p=74761705&postcount=3585
So please tell me what to do.

There are couple of ways to enter the emergency download mode edl mode - the first is by using the adb reboot edl and the second is the trick you mentioned. If you are entering the edl mode but qpst is not recognizing it is because you need to really very quickly press the start button as soon as you connect the cable. If that's not the case then sorry, this comment is not useful to you.

As another try, check this link
https://forum.xda-developers.com/le...ol-tool-one-driversunlocktwrpfactory-t3708276
Once your phone is recognised, click on the button that says reboot to edl
Qfil flashing is a complete override. Bootloader status is immaterial. It will flash the image even if your BL is locked.

Mi A2 Lite bricked on stock

Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options

pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
Two quick questions:
1.The phone died on its self without your intervention or...?
2.Have you tried to flash the stock firmware via MiFlash , while the phone is in edl mode(the command is: fastboot oem edl)?

1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?

pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
I think you are confusing some things here; adb is not an option now so you can´t boot device normally and also you said "fastboot edl" but they are different modes.
While in fastboot how did you try booting to TWRP image? (you said through adb but this is not right)

Can you get to fastboot? (hold vol down while booting, should see a rabbit on the screen)

pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
When your phone is in EDL mode(you won't be seeing any logo on your phone ,only black screen) it's absolutely normal to see the device as COM port , because the device is in another factory mode. And there is no problem flashing stock ,when your phone is seen as COM port. So if you can't flash the stock firmware in fastboot mode or EDL mode , maybe you have a hardware issue. To be sure -take a screenshot of the error in MiFalsh when the phone is in edl Mode (seen as a COM port) and you try to flash the stock firmware.

Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!

pocchio said:
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
Click to expand...
Click to collapse
Here is the stock firmware from Xiaomi site:
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Don't worry that it says MIUI , the firmware is Android One , they just forgot to change the name from MIUI to Android One , I have already tried it ,and I can confirm that it's 100% stock Android One firmware , good luck!

Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz

pocchio said:
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Click to expand...
Click to collapse
I will give a solution in a minute
EDIT: Are you sure your bootloader is unlocked? (fastboot oem unlock)
You have two choices , you need to find an older version of MiFlash beta , i'll give you a video :
https://m.youtube.com/watch?v=-7O1Svib14g
In the video description you can find a link for the MiFlash beta ,I hope it helps.
If not , you'll have to consider the Testpoint unbrick method , there are several guides.

OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar

pocchio said:
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
Click to expand...
Click to collapse
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop

nikoman1987 said:
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
Click to expand...
Click to collapse
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?

pocchio said:
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
Click to expand...
Click to collapse
the command is: fastboot oem get-product-model

nikoman1987 said:
the command is: fastboot oem get-product-model
Click to expand...
Click to collapse
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....

pocchio said:
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
Click to expand...
Click to collapse
tried the command too, it doesn't work.
So test point doesn't work too.. That's bad news
EDIT: fastboot getvar product command works , you can try it
And another question , have you tried to boot with patched boot.IMG ?

It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....

pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
You need a recovery to flash , which has a specific partition in the phone storage. You can flash only via fastboot . You need to boot into recovery , so try with a patched boot image for your version of the rom
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
So the last resort , we'll try to flash the ROM that I have mentioned before via fastboot. Place the zip file GM 1.1 in your PC (it has to be in the same directory as your adb and fastboot tools)
then open cmd and run the command
fastboot flash (the full name of the zip).zip
and hit enter
maybe that will solve it
And if this doesn't help again... type these fastboot commands :
fastboot format userdata
fastboot format system
fastboot format cache
fastboot format vendor
fastboot format recovery
fastboot format boot
then try again to reflash the stock rom (first try in edl mode ,if this doesn't do anything ,you'll have to format everything via fastboot commands again ,and try to flash the ROM in fastboot mode)
And if this doesn't help too... Then you're free to hit that ? in the ground hahahah (just kidding)

Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash

pocchio said:
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
Click to expand...
Click to collapse
which version of the firmware you are flashing? 10.0.9.0 or another version , so I can send you a link and walk you through the procedure.
And when you flashed the GM 1.1 the boot screen didn't changed from Android one? (the GM 1.1 version is a MIUI stock port and has to change your boot screen to black screen with white MI logo on it) It is very important to know
One of my friends told me to try this: just open the directory of the stock firmware , navigate to flash_all.bat and run the bat file (NOT THE FLASH_ALL_LOCK!!!) and wait for the end of the process. He had a similar problem , and it worked. He explained that for any reason , the recovery was the problem , because it was flashed in the boot partition. When you use flash_all.bat The file will erase all partitions and rewrite them. MiFlash won't , so try that

Question Phone Bricked

I was flashing pixel experience rom in my unlocked bootloader
° Wiped dalvik cache and art
° Flashed firmware
° Flashed Custom Rom
Then Later Rebooted. And device got dead
No display no fastboot no recovery
When connected with mi flash tool I can see COM10 in device
Whats happend really?

u should go to service center ,i had got this issue in my previous samsung phone and the service center guys replaced motherboard with new and gave it back.

prathu.x said:
u should go to service center ,i had got this issue in my previous samsung phone and the service center guys replaced motherboard with new and gave it back.
Click to expand...
Click to collapse
Can't fix it via local shops? Since warranty is not there bcz me unlocked bootloader

abi00723 said:
Can't fix it via local shops? Since warranty is not there bcz me unlocked bootloader
Click to expand...
Click to collapse
u can try in local shops

Unlocked bootloader is still under warranty. Try it.

Animesh Singh said:
Unlocked bootloader is still under warranty. Try it.
Click to expand...
Click to collapse
But me flashed custom rom too,

abi00723 said:
I was flashing pixel experience rom in my unlocked bootloader
° Wiped dalvik cache and art
° Flashed firmware
° Flashed Custom Rom
Then Later Rebooted. And device got dead
No display no fastboot no recovery
When connected with mi flash tool I can see COM10 in device
Whats happend really?
Click to expand...
Click to collapse
That sounds bad. You tried booting to Fastboot, right?
When the phone can't even boot into Fastboot Mode, it'll automatically boot into EDL Mode.
The Qualcomm EDL (Emergency DownLoad Mode). In that mode, you can still flash a ROM, but through "QPST" (Qualcomm Product Support Tool): https://androidmtk.com/download-qpst-flash-tool
I think you can use Fastboot ROMs with that tool. But I also must mention that you may not be able to flash a ROM, because the Qualcomm EDL Mode may be locked to only Authorised Repair Centres, and to those who have some type of a key or something...
I have a bit of experience with that mode, because I deliberately erased all partitions (including the critical ones required for booting Fastboot etc), without having thought about the consequences :
https://www.reddit.com/r/Xiaomi/comments/ntptsb
I wasn't able to recover it with EDL (didn't communicate properly with phone), and I had to replace it.

dreamytom said:
That sounds bad. You tried booting to Fastboot, right?
When the phone can't even boot into Fastboot Mode, it'll automatically boot into EDL Mode.
The Qualcomm EDL (Emergency DownLoad Mode). In that mode, you can still flash a ROM, but through "QPST" (Qualcomm Product Support Tool): https://androidmtk.com/download-qpst-flash-tool
I think you can use Fastboot ROMs with that tool. But I also must mention that you may not be able to flash a ROM, because the Qualcomm EDL Mode may be locked to only Authorised Repair Centres, and to those who have some type of a key or something...
I have a bit of experience with that mode, because I deliberately erased all partitions (including the critical ones required for booting Fastboot etc), without having thought about the consequences :
https://www.reddit.com/r/Xiaomi/comments/ntptsb
I wasn't able to recover it with EDL (didn't communicate properly with phone), and I had to replace it.
Click to expand...
Click to collapse
We can repair that with mi authorised account or emmc repairing?

dreamytom said:
That sounds bad. You tried booting to Fastboot, right?
When the phone can't even boot into Fastboot Mode, it'll automatically boot into EDL Mode.
The Qualcomm EDL (Emergency DownLoad Mode). In that mode, you can still flash a ROM, but through "QPST" (Qualcomm Product Support Tool): https://androidmtk.com/download-qpst-flash-tool
I think you can use Fastboot ROMs with that tool. But I also must mention that you may not be able to flash a ROM, because the Qualcomm EDL Mode may be locked to only Authorised Repair Centres, and to those who have some type of a key or something...
I have a bit of experience with that mode, because I deliberately erased all partitions (including the critical ones required for booting Fastboot etc), without having thought about the consequences :
https://www.reddit.com/r/Xiaomi/comments/ntptsb
I wasn't able to recover it with EDL (didn't communicate properly with phone), and I had to replace it.
Click to expand...
Click to collapse
After flashing rom I tried to reboot into twrp for formatting device. Then no response. I can see com10 in mi flash tool

abi00723 said:
After flashing rom I tried to reboot into twrp for formatting device. Then no response. I can see com10 in mi flash tool
Click to expand...
Click to collapse
Yeah I think your phone unfortunately got hardbricked somehow through that Flash..
Yes, I think it has to be a Mi Authorised Account.
But you can still try your luck and try QPST/QFIL, maybe you'll be able to flash it! If you need help with QPST, you can do some research with Google and YouTube, and ask me.

dreamytom said:
Yeah I think your phone unfortunately got hardbricked somehow through that Flash..
Yes, I think it has to be a Mi Authorised Account.
But you can still try your luck and try QPST/QFIL, maybe you'll be able to flash it! If you need help with QPST, you can do some research with Google and YouTube, and ask me.
Click to expand...
Click to collapse
Is there anyway to contact you in telegram?

abi00723 said:
Is there anyway to contact you in telegram?
Click to expand...
Click to collapse
Yes sir, my username's @dreamytom

Update : the phone stucked in edl mode and u need one authorised mi account to flash

Question Bricked Poco F3 Global.

I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.

Did you read any tutorial? For which reason you flash 12.0.3?

Looks like you triggered anti-rollback protection. Read here https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
You cannot install previous versions of miui.
If by some chance the phone still boots to fastboot mode, try to install the LATEST firmware for your phone via mi flash tool (make sure you check "clean all" option and NOT the "clean all and lock" which is default in the flash tool).
And no, you cannot use EDL with this phone. EDL is locked to regular users and can only be accessed by an authorized account.

If you ca access fastboot and the device is recognized by you computer in fastboot mode then you can flash Miui using MiFlash.EDL mode is when you dont have access to fastboot.
Read tutorials about flashing miui using miflash on youtube.

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works

X0PIRAT3 said:
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works
Click to expand...
Click to collapse
Or install via any mi flash lol.
It sounds like normal thing...
Cross flashing global/EEA tends to fail for whatever reason ( Super doesn't flash correctly ) and you get stuck bootlooping or straight towards fastboot depending on how far the super flashed...
Go back to global ROM and sit there. It should flash alright.
Idk why it does this ... Something is not alright with this phone

{Mod edit: Quoted post has been deleted}
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda
You can always tell your on Xda when they offer help that is 1 link and try this is the only information they give. The reason you screwed up is because lazy people that don't leave full instructions. You never never never never need to worry about edl mode. Fast boot or bootloader mode as it's called is how you restore a soft bricked phone what did you do with edl mode I don't even understand what you tried to do.

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
You thought this is something you needed to do? Edl mode is nothing that a regular soft brick would require

Here's another one edl mode I can't understand why you or anyone else would think this is how we restore a soft bricked phone lol this would be crazy I would be done. Your not even close to the first person to say this. Same with battery backup that doesn't make sense it's not battery backup you don't backup your battery it's battery life

[SOLVED] Hardbricked, but bootloops instead of "System got destroyed" text error.

so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.

hellohell0 said:
so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Click to expand...
Click to collapse
"System got destroyed" does not display on all types of bricks
hellohell0 said:
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.
Click to expand...
Click to collapse
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery

loopypalm said:
"System got destroyed" does not display on all types of bricks
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery
Click to expand...
Click to collapse
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.

hellohell0 said:
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.
Click to expand...
Click to collapse
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL

loopypalm said:
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL
Click to expand...
Click to collapse
Just got back from my friend's house. Yes, the solution is EDL
My phone is back to normal now, but this would happen again since my friend told me that the eMMC might be corrupted.
Thank you for the help! I thought it was impossible since my phone won't fully recognized in the PC (It was called Android but with question mark)
Case closed.