I´m pretty sure I hardbricked my smartphone. I tried to downgrade from A11 since it messed up my touchscreen, but the process of flashing the older ROM (V11.0.10.0.QFQEUXM) stopped and my phone wont start since then. I know its not completly dead since its recognized on Windows as QDLoader 9008, but I cant flash the ROM I mentioned through MiFlash (using 2020-03-14, also tried 2018-05-28 and 2018-11-15 without success) since it always gives the error "cannot recieve hello packet" (sometimes "cannot read from COM" before that).
It´s worth to mention that I have the EU version, not global, I haven´t opened the back of the phone and I´d rather not to do it, the notification LED is always off and I have ADB, fastboot and the Qualcomm drivers installed. Any idea of what can I do next?
Exactly problem I faced to the T. Same error and everything. The only solution is to go to the device centre and lie android 11 update did it. That's what I did.
Me too, broken touchscreen after update to A11, try to downgrade and my a3 was bricked. I believe that process triggered Android verified boot (anti rollback) and make our a3 bricked. You should bring your phone to service center because you cannot flash through EDL mode without xiaomi authorized account. I'm in Vietnam, service center fixed my A3 for free, even bootloader unlocked
sorry but you can flash stock a11 by qfile and your phone will back to life again
elprfesor said:
sorry but you can flash stock a11 by qfile and your phone will back to life again
Click to expand...
Click to collapse
where can we download stock a11? I'm having the same problem
Related
Hello everyone!
So i've been recently playing with custom roms and I messed up my device shutting it down during a TWRP install (I know how dumb it is and I swore I wouldn't do it again).
My device got bootlooped on the pocophone logo and I could only press the volume down and power button to access a weird black screen (no fastboot, no recovery and not detected by the computer). My last chance was to open it and test points to enter EDL mode (it was almost impossible for me to access it with tweezers). My computer now detects it and I was so happy, MiFlash Tool said my account was bound to my PC so I thought it would work, but I got the message:
Sorry, couldn't flash the device before turning off "Find my Device", and I couldn't find a lot of documentation about that error on the internet.
But how am I supposed to do this considering that I can't even boot my phone ? Or is it just that my account is not authorized, and I need to pay some weird ukrainian guy to posess my computer and work his magic to fix my phone? and how can I contact this kind of guy then?
I have tried doing the same method with Qualcomm Flashing tool QFIL but got the Sahara error. maybe I didn't use the software correctly, I don't really know.
Any help would be very much appreciated, I've been through every website google told me about to fix it, but did not manage to do so.
Thank y'all!
Sorry I didn't read your whole post but I saw you have issues with miflash
Miflash tool has a lot of issues on windows 10
I recommend using vmware with windows 7
Or a computer with windows 7(don't forget to have vcredist 86 and 64 installed)
Superpaupaul said:
Hello everyone!
So i've been recently playing with custom roms and I messed up my device shutting it down during a TWRP install (I know how dumb it is and I swore I wouldn't do it again).
My device got bootlooped on the pocophone logo and I could only press the volume down and power button to access a weird black screen (no fastboot, no recovery and not detected by the computer). My last chance was to open it and test points to enter EDL mode (it was almost impossible for me to access it with tweezers). My computer now detects it and I was so happy, MiFlash Tool said my account was bound to my PC so I thought it would work, but I got the message:
Sorry, couldn't flash the device before turning off "Find my Device", and I couldn't find a lot of documentation about that error on the internet.
But how am I supposed to do this considering that I can't even boot my phone ? Or is it just that my account is not authorized, and I need to pay some weird ukrainian guy to posess my computer and work his magic to fix my phone? and how can I contact this kind of guy then?
I have tried doing the same method with Qualcomm Flashing tool QFIL but got the Sahara error. maybe I didn't use the software correctly, I don't really know.
Any help would be very much appreciated, I've been through every website google told me about to fix it, but did not manage to do so.
Thank y'all!
Click to expand...
Click to collapse
Flashing through EDL mode requires Authorized Xiaomi account. So if you know a person who can perform flashing in your physical presence, approach him or take the phone to the service center.
Hi guys, I did something very stupid, flashed the wrong boot.img and ended up completely bricking my device. I tried changing the active partition to see if it would boot, that didn't help.
I was on the latest august update of official android 11 . Then I found a boot.img I found online, but apparently it wasn't from the exact same rom. The phone booted but no WIFI.
It wouldn't allow me to flash any update through settings - system update hence I decided to try to use a fastboot rom....tried that, but the process when I hit flash_all.bat gives a lot of FAILED (remote: Flashing is not allowed for critical particions) or FAILED (Error reading sparse file)....what am I doing wrong?
I can't do anything except get in fastboot.
Is there any way I can get the phone to work agan? Needless to say that as the idiot I am the whole phone is wiped so this doesn't matter anymore. As long as I can get it to work.
Please advise and thanks (The phone is OP7T Pro ME european).
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
leginhee said:
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
Click to expand...
Click to collapse
Thanks the problem is i can't get it to start qualcomm edl. I power off, press both vol buttons and conmect to usb but nothing happens. What am i doing wrong?
Qualcomm edl Mode is just a blackscreen
"I can't do anything except get in fastboot."
Your Bootloader was unlocked ?
You can try fastboot reboot edl.
Or you can find a ROM that works, extract all images and flash all of them.
I have a similar problem.. kind of. I just flashed a rooted boot to my phone but there is no wifi at all, and since i dont have a SIM card im not getting any updates. the Boot.img came from the oneplus software update and i did the payload dumper. Since I have rooted it ive lost the wifi capabilites. (its the 7T pro me international.)
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Did you try using Qualcomm's QPST software like described here: https://c.mi.com/thread-3527044-1-1.html
I literally unbricked two Mi A3 phones this morning that had been so screwed up one was boot looping and the other was so bad it wouldn't show the charging light or even boot, nothing would show on the screen at all. I followed this on both phones and I now have two working Mi A3 again.
Pyro556 said:
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Click to expand...
Click to collapse
Hello, im trying to convert it to CCe9 miui12, and I have the same message, even with different cables and PCs.
have you figure it out ?
STALKER18 said:
Hello, im trying to convert it to CCe9 miui12, and I have the same message, even with different cables and PCs.
have you figure it out ?
Click to expand...
Click to collapse
no mate i could not find any way out
dephekt said:
Did you try using Qualcomm's QPST software like described here: https://c.mi.com/thread-3527044-1-1.html
I literally unbricked two Mi A3 phones this morning that had been so screwed up one was boot looping and the other was so bad it wouldn't show the charging light or even boot, nothing would show on the screen at all. I followed this on both phones and I now have two working Mi A3 again.
Click to expand...
Click to collapse
I did try the qflash , it shows
download fail firehose fail fhloader fail process fail
Pyro556 said:
no mate i could not find any way out
Click to expand...
Click to collapse
Hi friend!
do you still having that Issue ? i might have the solution PM me
for those who still have only EDL mode as the last hope, I have a solution.
I have tried all the available solutions on XDA... QFIL.. MiFlashTool all mentioned vesions, Drivers, PCs, Cables etc...eventually I just disconnected the Screen cable (after battery's one) the one on the right side of the battery port. started the flash like mentioned with mi flash tool and the phone on EDL (vol + vol -, enter the cable). it runs smoothly took 177s to finish and the phone is back to A11 stock
Pyro556 said:
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"
Click to expand...
Click to collapse
@Pyro556 Thread closed as you've created a subject matter related thread in March 2022:
Mi A3 hard bricked
My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even...
forum.xda-developers.com
And I've also closed this thread created by you yesterday respectively on Sunday:
[CLOSED] Mi A3 hard bricked
I guess the bootloader is locked , i am not sure , it was bricked due to the Android 11 update , i unbricked it twice using mi flash and update through system update but it got bricked again and this time it's showing the error "write time out...
forum.xda-developers.com
[CLOSED] Mi A3 not flashing , error "write time out device may be disconnected"
My mi A3 was bricked after the Android 11 update , i unbricked it twice using flash tool and test point method through edl then when the device was on , i updated it through system update , thinking that the update might remove the corrupted...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5, post only ONCE and post in existing threads instead of creating new ones! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
so i have tried updating my phone os by using local ota because i have root, i downloaded the zip with oxygen updater and tried flashing it with twrp but it said its wrong device twrp was reporting denniz and the update was for OP515BL1 but when i checked the phone model it said its OP515BL1 so i just removed the abort function when it checked the model since i thought twrp was just reporting incorrect model and after flashing i tried rebooting and now its just stuck on bootloop, i cant get into any recovery/fastboot mode, when its rebooting for a flash of a second it says recovery mode and left bottom corner, i have tried mtk but when i try connecting the device on boot and holding both volume buttons on console it reports this Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m so i kinda dont know what to do anymore, it the device just hardbricked or is there still way to make it boot again, i did backup the data i needed so full wipe is no problem but since i cant even boot to recovery i cant even wipe it any suggestions and help would be welcome
Hi, I made the exact same thing and have the same issue as you.
I have been reading and trying so many different things to get it connected to mtk client but no success,
tools in linux and windows..
I have read that to get access to the mtk client first we have to use the mtk bypass https://github.com/MTK-bypass/bypass_utility but it doesnt even recognize the usb in both windows and linux for me.
And the payloads does not yet include our chip mt6893 anyway..
MT6893 Can't dump bootrom · Issue #27 · MTK-bypass/exploits_collection
MT6893 Can't dump bootrom
github.com
I had some hope in this:
https://www.martview-forum.com/threads/mtk-auth-bypass-tool-v6-exclusive-version.51284/ and it does recognize the chip and starts the bypass but then times out.
Can you try and see if you can bypass with the tool above?
I have given up and will go buy a new phone today i think.
Can confirm, times out after 30 sec or so. I read in another thread that they killed brom mode in android 12 and it does seem that way.
Hey, can I join your club? I did the exact same thing as well ^^
I just got my phone back from a free warranty claim on this boot loop, and they have somehow reflashed it at OnePlus so now I have OOS 12 C.11 trying to downgrade now to get fastboot and brom and thing back to normal: https://community.oneplus.com/thread/1596759
So i took the phone to service on november 8 and it seems like they are almost done with fixing it, by the status changes on the website it seems like they changed the motherboard itself which is a bit strange since i thought they had special manufacturer flashing tools but ah well, for now it seems its gona be on the warranty which i thought just not gonna happen cuz like the orange status which says its not trusted device since its been unlocked shows up when you try booting the device so thats really cool from the service or oneplus warranty policy, but i still havent got the device back since they are still testing it after repairs but i do expect it this week.
So i dont really know if i should buy oneplus ever again if they just disable fastboot and mtk because if they didnt i could have just fixed this myself, but cant really put all the blame on oneplus since i did root and flash twrp on the device so maybe that was the cause of the bootloop, and i would like to know anyone that had the exact, same issue was your device rooted, did you unlock bootloader, custom recovery, how did you flash the ota update.
And sorry everyone that i didnt reply to you if you wanted to test something since i didnt bother checking the forum since i was just so upset that i ****ed up my device by updating and damn oneplus, idont know why they disabled fastboot and mtk, is there maybe vulnerability in it or something so they just disabled it because they could not fix it?
If you have any questions feel free to ask il awnser when them whenever i can.
UPDATE: after i wrote this i rechecked the website and it says its fixed so yeah i should get the phone this week still waiting on them to message me about shipping it to me
totaltmega said:
I have given up and will go buy a new phone today i think.
Click to expand...
Click to collapse
try sending it to service center under warranty since it seems like they did fix mine under warranty when it did show orange alert on boot which did say it is untrusted if you have unlocked your bootloader
totaltmega said:
I just got my phone back from a free warranty claim on this boot loop, and they have somehow reflashed it at OnePlus so now I have OOS 12 C.11 trying to downgrade now to get fastboot and brom and thing back to normal: https://community.oneplus.com/thread/1596759
Click to expand...
Click to collapse
why downgrade? is android 12 really that bad on oxygenos?
So i got my phone back but after like a 2 minutes in the setup screen i noticed that the fingerprint was not working, i did try updating to the latest update since strangely they gave me back one that was year old and it was strange because on the service center website they state that they update the phones to latest version, on the documents i got back with the phone it does say that they changed the motherboard and new imei which was odd seeing how totalmega on this thread got his because they just reflashed it, i might try maybe doing a full reflash of OS if thats possible but if the problem still persists i might need to send it back but still it was still cool that they repaired it under warranty since it had unlocked bootloader.
Hello,
recently I started to play with my Honor 8X JSN-L21 Europe version and I wanted to install a custom ROM from MOS. The instructions said to downgrade my phone to EMUI9.0. I had EMUI10 installed, used HiSuite to downgrade, but it could only go down to EMUI9.1. So, after a little googling, I tried to flash official ROM using the update.app method. After many attempts which ended at 0% the phone finally started to "verify the image," only to stop at 3% and fail. After this i restarted my phone and it is totally bricked. No LED flashing, nothing on the screen, no fastboot/update mode.
The only thing that works now (my computer can see) is putting the phone in COM mode using test point.
I found on the internet some HiSilicon flashing tool that could help, but it doesn't detect my phone when I plug it in (Device Manager says Huawei COM1 - clearly it's connected). The only other option is to buy DX Phoenix and try it out.
Before buying the software, do you guys think it could help? I don't want to spend some $$$ on a software that might (not) work.
Thanks everyone!