Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!
Try EDL mode opening your phone...
Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.
up
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?
Go to service center this is last option you save RIP mi a2 ?
As I can see from picture you have posted, your bootloader is unlocked.
SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.
bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?
Text me on telegram. @dejavutr
Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.
Here's some stuff that should get you going again. The 3 links I posted all contain the necessary files to flash your phone to stock. You'll need the latest firmware for your phone as well. Install the Moto drivers, adb and fastboot files, and use the xml to batch converter to convert the firmware to a Windows batch script (assuming you use Windows). All the links will have instructions on installation and usage. If you need any more help let me know. I have the same device. http://www.rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
http://rootjunkysdl.com/files/?dir=Adb Fastboot Files
http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola
Something happened to my Google Pixel this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
I did some searching around, and it sounds like the phone might be stuck in Emergency Download Mode (EDL)? Anyone has a solution on how to fix this issue?
(I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.)
BTW mine is Google Pixel 3,
Anyone has the solution !! Please help !!!
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
mindyabiznis said:
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
Click to expand...
Click to collapse
Yeah, but nothing happened! Its EDL mode.
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
mindyabiznis said:
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
Click to expand...
Click to collapse
Thanks for the reply...
I already did all of this but couldn't get the phone out of Emergency Mode,
and I already said (I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide and I'm not able to locate the QSPT Flashable Firmware File for my device Pixel 3.
It's very frustrating to saw that even a pixel phone has to go through this...
It was not rooted / not Bootloader unlocked / or any kind of modification wasn't done with it only an OTA update from Google was installed last wk.
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
mindyabiznis said:
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
Click to expand...
Click to collapse
Yeah, thinking of battery disconnect..
sifatrhmn said:
Yeah, thinking of battery disconnect..
Click to expand...
Click to collapse
Can you disconnect the cable and just let it run out of juice?
Give your information to this proposed lawsuit this office may pursue.
Google Pixel 3 Class Action Investigation - Chimicles Schwartz Kriner & Donaldson-Smith LLP
chimicles.com
When your device appears like this on your PC, it means it's stuck in QPST mode - Qualcomm Product Support Tool. The software is not freely available from Qualcomm, nor are the necessary files that would be required to reprogram the PROM.
Some users have had success leaving their phone to run out of battery. Failing that, there is unfortunately no way to recover the device beyond seeking repair.
Can anyone please help me? I did the all steps but nothing works and I get the STATUS_EXT_RAM_EXCEPTION (0xC0050005) error... The only solution I found is to drain the battery while the device is bootlooping but sadly, my phone vibrates 1 second and dies because there is no fastboot or recovery or nothing to boot with, I tried SP Flash Tool but it stucks at Download DA 100% then shows me the ram error. PLEASE HELP ME
P.S: I know people will say MTK Bypass is a virus but please ignore it and focus on my main subject
Use latest fastboot rom and download agent to mtk all.bin
Restart phone by power+ volume key
Also usb dk driver and libusb tool
Or remove back cover and battery take care with fingerprint
Already done everything you said, nothing works.
iOussamato_ said:
Already done everything you said, nothing works.
Click to expand...
Click to collapse
Try again
faisal9666 said:
Try again
Click to expand...
Click to collapse
What do you mean try again? I tried it 50 times and still doesn't work, tried so many other roms and DAs and NOTHING
iOussamato_ said:
What do you mean try again? I tried it 50 times and still doesn't work, tried so many other roms and DAs and NOTHING
Click to expand...
Click to collapse
Very strange
STATUS_EXT_RAM_EXCEPTION (0xC0050005)
1.
Hello bro, I only registered on XDA to inform you and gonna post on other thread for people suffering from this error.
2.
I have redmi 9c angelica
3.
I had the same issue like yours. Just fixed it 2,3 mins ago after many days of suffering. I tried 3 fastboot roms in which only this work (angelica_global_images_V12.0.12.0.QCRMIXM_20210412.0000.00_10.0_global). I hope it also work with you. Give a try
i followed this and boom now all of my stress has been released.
Firmware link
How to Unbrick Redmi 9C (angelica) without using auth account. Tested and working! - OmBob Opreker
This is tutorial how to unbrick Xiaomi Redmi 9C (angelica) using mediatek bypass tool and sp flash tools without using mi auth account using global stock
ombob.my.id
iOussamato_ said:
Can anyone please help me? I did the all steps but nothing works and I get the STATUS_EXT_RAM_EXCEPTION (0xC0050005) error... The only solution I found is to drain the battery while the device is bootlooping but sadly, my phone vibrates 1 second and dies because there is no fastboot or recovery or nothing to boot with, I tried SP Flash Tool but it stucks at Download DA 100% then shows me the ram error. PLEASE HELP ME
P.S: I know people will say MTK Bypass is a virus but please ignore it and focus on my main subject
Click to expand...
Click to collapse
use this video 100% working
Device locked and need test point. You can't use MTK bypass and SP Flashtool directly. Your device may have patch on July 2022 and newest version (12.5.3 and above).
And if you see 3 dot pin for TP, it's Redmi 9c but if you found only 1 point (for TP), it's Redmi 9c NFC.
Remember to use TP for any operation and if not work, TP with Professional software.
demoimoet said:
Device locked and need test point. You can't use MTK bypass and SP Flashtool directly. Your device may have patch on July 2022 and newest version (12.5.3 and above).
And if you see 3 dot pin for TP, it's Redmi 9c but if you found only 1 point (for TP), it's Redmi 9c NFC.
Remember to use TP for any operation and if not work, TP with Professional software.
Click to expand...
Click to collapse
where are test points located?
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
ax0 said:
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
Click to expand...
Click to collapse
did you try Yurian's post info, my phone was totally bricked and thats what kinda worked, I left extensive guides on how I did it on there too
also, here are the files that worked for me (redmi 9a, not the exact same but its pretty similar)
your ROMs should be these (use the fastboot one, to the best of my knoledge, the recovery one only changes the recovery hence, its useles to unbrick) if that doesnt work try ROMs for different regions or a one previous version (I dont recomend this because MI is super against downgrading so they f-up your phone if you try) always with the fastboot one
the scatter should be on ROM/images
if that scatter doesnt work, try the ones I provided, theyre for a different version but hey, in for a pound, if its already hard bricked you may as well try crazy stuff, I would suggest you look for the correct scatters online, but I have some slight experience looking for android files and I couldnt find any that are the correct ones.
Lastly, Im just a nobody that unbricked his device and got a little confident, I know next to nothing about phone config, that said, I do think I know more than most but I dont know if scatter files are completely imposible to be compatible between versions or even the ROMs, most Custom ROM work in both 9a and 9c so I think they might, but IDK.
Ivan.Adriazola said:
did you try Yurian's post info, my phone was totally bricked and thats what kinda worked, I left extensive guides on how I did it on there too
also, here are the files that worked for me (redmi 9a, not the exact same but its pretty similar)
your ROMs should be these (use the fastboot one, to the best of my knoledge, the recovery one only changes the recovery hence, its useles to unbrick) if that doesnt work try ROMs for different regions or a one previous version (I dont recomend this because MI is super against downgrading so they f-up your phone if you try) always with the fastboot one
View attachment 5859871
the scatter should be on ROM/images
if that scatter doesnt work, try the ones I provided, theyre for a different version but hey, in for a pound, if its already hard bricked you may as well try crazy stuff, I would suggest you look for the correct scatters online, but I have some slight experience looking for android files and I couldnt find any that are the correct ones.
Lastly, Im just a nobody that unbricked his device and got a little confident, I know next to nothing about phone config, that said, I do think I know more than most but I dont know if scatter files are completely imposible to be compatible between versions or even the ROMs, most Custom ROM work in both 9a and 9c so I think they might, but IDK.
Click to expand...
Click to collapse
Hello! Thanks so much for replying
I still get the same issue, it just shows a screen for a split secconds and then turns off
if you wan
ax0 said:
Hello! Thanks so much for replying
I still get the same issue, it just shows a screen for a split secconds and then turns off
Click to expand...
Click to collapse
t to some day we could hop on a discord call and see if I can help you in any way, although I doubt it since our hardwares arent exactly the same
Ivan.Adriazola said:
if you wan
t to some day we could hop on a discord call and see if I can help you in any way, although I doubt it since our hardwares arent exactly the same
Click to expand...
Click to collapse
sure my discord is axon#7061
same problem but fixed,try tft free tool.here are the steps.
1.remove battery connection,do not connect untill flashed
2.open tft tool,go to mtk section flash scatter
3.connect mobile while holding both volume bouttons
4.now tft tool starts flashing but failed & rebooting device
5.now remove cable & connect battery,bootup
Hoping this should work for you,mine is fixed that way
brav3h3ar8 said:
same problem but fixed,try tft free tool.here are the steps.
1.remove battery connection,do not connect untill flashed
2.open tft tool,go to mtk section flash scatter
3.connect mobile while holding both volume bouttons
4.now tft tool starts flashing but failed & rebooting device
5.now remove cable & connect battery,bootup
Hoping this should work for you,mine is fixed that way
Click to expand...
Click to collapse
thank you so much
idk why but TFT managed to fix it!
ax0 said:
thank you so much
idk why but TFT managed to fix it!
Click to expand...
Click to collapse
It's my pleasure
ax0 said:
sure my discord is axon#7061
Click to expand...
Click to collapse
Hello, please add me, I'm desperate how to do this :-(
ax0 said:
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
Click to expand...
Click to collapse
Hi,
Just follow the steps and you'll be good.
[Guide] How to unbrick redmi 9C by flashing with SP Tools without Auth file(Tested Working)
This is a last ditch effort to restore your phone to working order. This should only be used if your phone DOES NOT BOOT AT ALL or if you are unable to boot into FASTBOOT. If you can boot into Fastboot mode then I would encourage you to flash...
forum.xda-developers.com
I already tried it with my device and it works well.