Database Develop

Please Help_After OTA Update Xiaomi Mi A2 died

On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks

We are in the same boat buddy, the same thing happened to the phone of my wife.

It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers

I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.

I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.

I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.

Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.

I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.

Guys I REALLY NEED HELP

Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE

The app works just fine... Also why are you trying to use a Xiaomi flash tool on an Asus device?

Get out of EDL mode with vol- vol+ power all three together.

EfeKamil said:
Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE
Click to expand...
Click to collapse
Have you tried doing the process with the correct drivers installed? (I have not done this method, but it could be driver related) See here for drivers
EDIT: at the bottom of your EDL thread it does state you need the Qualcom drivers installed, not sure if they're the same as the ones i linked to, but the ones in that thread are here
Also, this post may be of some use to you, might wanna read the rest of the thread too for tips...
'I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).
I have no idea why that's the case but it worked for me.'

Hardbrick - flashing rom in edl-mode

Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png

PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authenticated mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
As redmi 9 is mtk based device so their is not any edl point...if you have authorized account then you can easily flash it without the device open

Just use older preloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

That I have an authorized account was a wrong information.
When I try to flash it with sp_tool the following error is displayed: STATUS_CRC_BROM_FAIL 0xC0060005

PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
Disable authorization and unbrick your Redmi 9
Now you can unbrick your device even if the redmi logo not coming..just go to below link and follow their steps.... https://megafon929.github.io/mtk For more information and how to do follow the below post...
forum.xda-developers.com

Question Black screen and hard brick

Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English

Hi if you can open bootloader, flash stock rom

The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.

I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless

May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).

RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked

Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now

Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse

RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account

Question The current image (boot/recovery) have been destroyed

Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!

Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me

Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon

Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing

hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha

KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware

DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware

KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files

I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.

KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?

yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials

KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.

yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot

Damn!! I hope you find some way to fix your device. Good luck.

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate

GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.

hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?

yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.

hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)