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.

Bootloop

Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.

I dont think there is way to get the pictures but you can fix the phone tho

_matze__ said:
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
Click to expand...
Click to collapse
the photos has not synchronized with the google account?
maybe you can try with some tool like this
https://www.wondershare.net/ad/dr-fone/dr-fone-android.html
(it is difficult but you can try)
to reset the device in stock etc you can try with test points & edl mode ...If you have guarantee, send it to service but the photos will be lost of course...

Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?

_matze__ said:
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
Click to expand...
Click to collapse
Really IDK....Can work may or may not.Not all devices in the list,the list is updated but many users do not add their devices
there are other such applications.hit on google search for example : "recovery data from android phone"
and you will see and others like that

I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.

_matze__ said:
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
Click to expand...
Click to collapse
Reboot on edl mode & flash stock rom via miflash tool
if your device can boot on fastboot
"fastboot reboot edl" (need unlocked BT)
https://forum.xda-developers.com/showpost.php?p=78963902&postcount=6
from test points > edl > miflash tool (not needs unlocked BT)
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
(the better solution? If you have a warranty send it to service...All this needs some experience)

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Lumia 1320 in flash mode "NOKIA FLASH" loop restarts

I recently recovered my nokia lumia 1320 RM-994 from death, thanks to some .hex and .mbn files posted in a thread on this forum. But now I'm in another very big problem and I need help.
It turns out that a red screen appeared with white letters saying: NOKIA. The problem is that the phone restarts every two minutes or so constantly and so on. I can't find a solution to this problem, please help!

Could you send a picture of said screen?

That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.

felipeunderx said:
That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.
Click to expand...
Click to collapse
What software are you flashing and have you tried dirty flashing the phone?

You need to try only with wpInternals 1.2 . You can enter into emergency download mode by following key combination specified at 'restore bootloader section', try for restoring bootloder first.
You need original FFu image and emergency files.
All key combinations to be tried while you have connected your device to the pc's usb port.

Or just follow this tutorial
Tutorial | Lumia devices flashing
Tutorial | Lumia devices flashing Hello world Please, use Archive for Tutorial | Lumia devices flashing if you have an issue. No entity or person can not be responsible if a software damage occurs from the Lumia device by the utilization of...
forum.xda-developers.com

I have tried to flash the phone with wpinternals 1.2 and it has now reached 45%, I will keep trying until I reach 100% and complete the flashing
At this point the phone stopped rebooting, so I was able to try to flash it.
Thank you.

Now it's up to 52%, and it stops, but I'm already in the middle of the process, I hope to finish these days and we'll see what happens in the end.

Question Data recovery over fastboot on a broken screen

Hello everybody.
I currently have a Mi 11 with a broken screen (touchscreen works but no image is visible).
I want to recover all the user data inside it, because there's important stuff I need to backup.
I have tried booting into EDL and follow this guide, though while trying to load the EDL mode it says FAILED (remote: 'Error Invalid Parameter').
The bootloader is locked, and since I want to take some data from it I cannot unlock it as it will wipe everything inside.
I also have tried having the screen from a USB-C to USB-C/USB/HDMI adapter, it shows nothing. It's not an adapter issue as it works with a OnePlus 8 Pro.
I currently am in lack of solutions and I really need to back everything up.
Thanks in advance for any person that can enlighten me.

Did you prudently enable USB debugging mode?