Develop Bugs

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8

Question Bricked while flashing Mi Pad 5 from Chinese to Global ROM

Hi guys,
i want to flash my MiPad 5 from chinese to global Rom.
I already installed the Bootloader Unlock Tool and waited one week.
Now the bootloader is unlocked and i downloaded "Xiaomi Pad 5 Global MIUI V12.5.4.0.RKXMIXM Update". There are two different Download Versions, one for Recovery and one for fastboot. Which one is correct and usable without root?
Now i'm Stuck in the Process of Downloading TWRP because I can't find a specific version for my MiPad 5. Is there anybody who can give me a step by step Guide what to do now?
Thank you

chrwo said:
Hi guys,
i want to flash my MiPad 5 from chinese to global Rom.
I already installed the Bootloader Unlock Tool and waited one week.
Now the bootloader is unlocked and i downloaded "Xiaomi Pad 5 Global MIUI V12.5.4.0.RKXMIXM Update". There are two different Download Versions, one for Recovery and one for fastboot. Which one is correct and usable without root?
Now i'm Stuck in the Process of Downloading TWRP because I can't find a specific version for my MiPad 5. Is there anybody who can give me a step by step Guide what to do now?
Thank you
Click to expand...
Click to collapse
Try fastboot method without bootloader lock

I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?

chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Could maybe try this:
https://www.xiaomitool.com/V2/
Don't have any experience with it personally, but worth a try

TWRP is not required to flash the global ROM.
Just specify the unzipped global ROM as the working directory of MiFlash.

try flashing fastboot rom using miflash tool

finally could flash the global rom.
i am pretty sure it was about the ryzen gaming pc i used. now it worked out with my intel laptop....
strange problem

chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Mi Pad 5 didn't have recovery partition, since it use A/B structure. You must execute fastboot boot recovery.img and after that install recovery to RAMdisk.

chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Whered you even get twrp? Had an error while flashing from cn to global as well about sparse super failed. Then tried reflashing but i got the same error as you had and all i did was reboot the tablet in fastboot while it was still in fastboot and after that it flashed successfully even though it threw out am error flash is not done but the tablet rebooted hy itself and then booted up after a minute or two. Almost gave me a heart attack while i was at it
Edit: seems you flashed it successfully already thats good. Fastboot can be clunky on ryzen sometimes, i remeber back on mi a2 had to use a hub instead of directly connecting my phone to my ryzen pc for fastboot to work properly and not get stuck while flashing. But now i can connect directly after switching to a b450motherboard, was using a b350 before

I am trying to use the Mi Flash tool and when I open it, it tells me to install Drivers, but the screen just hangs there when I press Continue.
I also get an error saying a specific log folder is not present.
I also am trying to install global rom on china model. Please help!

chrwo said:
finally could flash the global rom.
i am pretty sure it was about the ryzen gaming pc i used. now it worked out with my intel laptop....
strange problem
Click to expand...
Click to collapse
It would be great if you can make a step-by-step guide on how to do this. Thank you.

puleen said:
I am trying to use the Mi Flash tool and when I open it, it tells me to install Drivers, but the screen just hangs there when I press Continue.
I also get an error saying a specific log folder is not present.
I also am trying to install global rom on china model. Please help!
Click to expand...
Click to collapse
prob just driver problems, i use ryzen and it works fine.

Don't know if I need to create a new thread. After the unlocking, I tried to change the region from RU to CN and got the same problem after a "successful" update as chrwo with "Mismatching image and device" error and fastboot mode. Then I tried to flash global version and the device error is gone but I still have the fastboot mode. Recovery from MiToolv2 doesn't help either, after successful recovery tablet still goes only to fastboot.

Got it working after flashing with miflash on the intel PC. I used a USB port on the motherboard this time.
So maybe there is really a problem with Ryzen.

Choochter said:
Could maybe try this:
https://www.xiaomitool.com/V2/
Don't have any experience with it personally, but worth a try
Click to expand...
Click to collapse
Not work for me.
But when I try with Miflash tool and anoter Rom (newest), it worked

Critical Hit said:
Got it working after flashing with miflash on the intel PC. I used a USB port on the motherboard this time.
So maybe there is really a problem with Ryzen.
Click to expand...
Click to collapse
I meer the same errỏr when I use Intel PC.
So, I dont think this a problem of Ryzen

i also brick the device using mi-flash sucking program. i finally using fastboot command flashing which copying from the stock rom "flash_all.bat" file.

So we can't lock the bootloader after installing the global rom?

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.

Question Poco f3 Error: Sending modem_ab

good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.

Same problem. Don't try more things because you will brick your phone like mine.

Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance

As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz

Thanks you so much I will try that

and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots

Still the Same Error unfortunatelly

nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?

No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?

Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock

Still the Same Error . Can This be because of a Driver or a hardware issue?

i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.

It doesnt seem to make any difference to the error whether i flash it via cmd or miflash

nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...

I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you

You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.

Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.

I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot

nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse

okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?