Database Users

device bricked by itself..? unable to boot or charge

i shut down my device by tapping power off. then removed sim card and sd card after screen went black. but when i tried to power on, it doesnt respond.. i tried holding the power button for 10s, it gives me a black screen and vibrates and instantly closes again.. so i cant boot into recovery, i cant boot to fastboot, and its unreadable on pc, it doesnt charge, no bootlogo, nothing. just bricked..
.
i dont know why, but it just bricked by itself.. i've been using mokee 9 date of 1/1/2020 thats the last update i installed, with add on su and everything was working perfectly and even if i reboot multiple times..
bootloader was unlocked so xiaomi centers wont help me..
how is it possible to make it boot again? i mean like wtf even happened? i did nothing.. i didnt flash anything and system was READ ONLY before powering off.. all i did was remove sim and sd cards... even after flashing mokee updates yesterday, it booted normally and idk what's going on..
any help?
EDIT: the phone's hard disk IC was damaged. I went to a tech guy and he changed it but then the motherboard broke entirely after flashing the qcn file for imei. Device out of warranty of course because of the damn bootloader. Thank you xiaomi for the great phone that only lasted one month before dying completely.

attempt 2
in attempt 1 i tried force reboot as mentioned, didnt work
attempt 2 : i tried force reboot while plugged to pc, this showed up

attempt 3
i tried to flash a new firmware, but device unreadable. must be on fastboot mode for mi flasher to be able to read it. im starting to lose hope.. the device is new though it makes me sad

on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything, because it didnt actually boot into EDL mode, had to open my device physically and use test points. so attempt 4 failed

does this mean fastboot works?
after attempt 4, it said successful so if fastboot works like that then i can flash stock boot.img or something.. right? which image should i start with

forum
boody shaban said:
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything. so attempt 4 failed
Click to expand...
Click to collapse
this is the forum of the bricked phone similar to mine, except that i didnt try any flash like him it just happened randomly
https://c.mi.com/thread-2334646-1-0.html

attempt 5
attempt 5 failed, i tried flashing whole firmware one by one, i started with vbmeta, then recovery but it failed. idk what to do

notice
i have noticed that it only flashes small img files, if its 100kb or more it will fail. maybe due to device restart because the only way to make it read in fastboot mode is to force restart multiple times until it flashes. what to do now?

attempt 6
so according to this video
https://www.youtube.com/watch?v=yJoIiLE_w3w
he installed a driver (name in attachment) then refreshed on mi flash so his device became readable on mi flasher
i tried that but it didnt work.

final attempt.. out of hope
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.

boody shaban said:
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
Click to expand...
Click to collapse
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.

Reason for brick
cg730620 said:
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Click to expand...
Click to collapse
Yes, I hate tearing up my device so I took it to a professional. He failed to open ADL but he did the 9008. Now he waits some kind of credit. Not sure if for the app to work or for the bootloader to unlock, although it was already unlocked but maybe somehow got locked..
Any way, expected reason for brick is either latest magisk module, or kernel tweaks..

I gave the device to a professional, but he also failed to flash it even with test point. He said he was searching for a file.. I dont remember its name, something like IMOH..

Now I need to know any possible reason that might brick my phone again to avoid it
cg730620
Click to expand...
Click to collapse

cg730620 said:
.
Click to expand...
Click to collapse
The app he used was called ultimate multi tools

test point attempt failed
i did the test point, booted to 9008 mode but still nothing.

i think i know why the phone got bricked by itself, it got ARB stands for AUTOROLLBACK
read more about it here https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
bootloader got automatically locked again.

Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
boody shaban said:
i did the test point, booted to 9008 mode but still nothing.
Click to expand...
Click to collapse
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/

cg730620 said:
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
Click to expand...
Click to collapse
but im sure i have all drivers installed in fact i used mi flash more than once and it worked perfectly fine, and i swear i didnt try to lock it or anything, what happened is, mokee auto updates installed add on magisk and it was the latest version so i think this might have bricked it. idk..

ok i downloed all the drivers and reinstalled them, same error : "library not registered"

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.

Did you managed to fix this?

Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!

ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).

Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Might have bricked my Mi9T (non-pro) - Bootloop, XiaoMiTool V2

**EDIT**: Had to send the phone back as the bootloader was locked and nothing was flashing. I believe they EDL flashed it and all is good now. Unlocked the bootloader on the new one just in case this happens again, I will be able to fix
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BACKSTORY:
Okay, so I recently updated to MiUI 12 and it wasn't great. My apps were crashing all the time and the general stability was not good. (this was around a week ago)
Then earlier today, my device just went into the boot screen (the colourful MiUI one) and stayed there for over 30 mins.
I forcefully restarted my phone using the volume buttons and it would go into the first "Mi powered by android" screen and then back into the colourful MiUI screen.
Then it would stay in the MiUI screen for a minute or so, and then restart itself, continually repeating the process.
At this stage, I had no custom recovery, had not tried to tinker with the phone (other than disabling some default apps through FastbootTools), and everything was fine until MiUI 12 came.
WHAT I DID:
I was able to access the default XiaoMi recovery (3.0?) and tried to wipe the data and restart, but nothing would change.
I tried to use the MiPC Suite after selecting in recovery, but it would recognise my device, even after updating to latest version.
I tried to use FastBootTools, but that would also not recognise my device.
I tried to use XiaoMiTool V2 (by Francesco Tescari), and that did recognise my device. I selected "my device is bricked" option and it did its thing, downloading and trying to sideload something. And then on the device, it got stuck at 4.99% with a message "You won't be able to turn on your device if you try to reboot it", and on the XiaoMiTool, the progress was at around 400% and said -70 seconds remaining, and around 40000MB / 3000 MB or something along those lines. Basically, **** was ****ed.
So I just let it sit there for a bit and then the XiaoMiTool V2 gave and error, "miui sideload failed adb execution exception adb sideload exited with status 1"
I had 3 options,
"Retry step"
"Go back to previous step"
"Cancel and abort"
I tried to search what the error was, but all of the results came from years ago, for different devices. So I clicked "Cancel and abort", only for the device to remain unchanged (4.99%, You won't be able to turn on your device if you try to reboot it), while the XiaoMiTool V2 went back to the start screen.
So I tried it again, the "my device is bricked option", and went through the same steps, and now it is stuck at "Pushing file to the device via ADB, ..., Starting MIUI sideload procedure".
Now I am stuck. My phone screen just says
"4.99%, You won't be able to turn on your device if you try to reboot it"
and my XiaoMiTool is stuck on the beginning sideload procedure.
Closing
If you managed to read this far, thanks, even if you don't have a solution. I appreciate anything that could help with this situation.

U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine

Badis st said:
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Click to expand...
Click to collapse
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?

coolboy328509 said:
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
Click to expand...
Click to collapse
Try another computer and another USB port...
The solution will benunder fastboot. You have to unclock your bootloader and flash a custom twrp or flash a stock rom using miflash

Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro

EdoDT99 said:
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
Click to expand...
Click to collapse
this is totally the wrong thread for ur device

Bricked Redmi 2

Hey! I've got some real issues, please read my whole story and try to help me.
So, I've got Redmi 2 (wt80047) and I have installed an custom rom i.e..Atomic OS because that was the best of all, but I was facing issues of LTE network, it automatically disconnects, and then I have to restart my phone like 8-9 times to get the LTE network back , so I decided to switch back to stock ROM, and successfully I have re-installed my stock rom (MIUI8), afterwards I have downloaded some files like Magisk.zip and SuperSU.zip for rooting purpose, but I don't know what happened but my device was bricked, it was not openinig, it was stucked at logo, it was neither going in Fastboot mode nor my pc was detecting the device so I can flash again it with MI Flash tool. The only thing that was happening was that multiples drives were showing on my windows whenever I connect my Redmi 2 to pc like E: drive, F; drive, G, H, I: drive. So i have opened an application (Disk Partition Tool) and deleted all the drives. Then my device was ****ed x100. Now it is totally dead. No response, no powering on, no vibration, no fastboot mode, but now my PC and MI Flash Tool is recognizing it with COM6 (ports), so now whenever I try to flash it. it gives me error "Cannot receive hello packet" and sometimes "Ping target failed". Please Help Me, Pleasee!
Some Things that I have already tried:-
1.Tried every version of Mi Flash Tool
2. Tried chineese and global rom version both
3. Tried QFIL
4. Tried every ports on my cpu
5. Cannot flash it with cmd, coz adb and fastboot both does not recognize my device (Waiting for device...)
6. Pressed the Power button and then flashed it.
7. Remove the battery, short the EDL points, I have tried all the hardware stuff also.
I am stucked in this for like 1 month, and I have only this phone, my parents won't give me a new one.
Help!)

Looks to me the phone was connected to Windows computer in USB-MTP mode, so the computer believed the phone to be a portable media player and/or USB-drive. Deleting partitions always causes a complete data loss. Hence it's not wondering me that the phone actually is dead: you fully wiped it.

jwoegerbauer said:
Looks to me the phone was connected to Windows computer in USB-MTP mode, so the computer believed the phone to be a portable media player and/or USB-drive. Deleting partitions always causes a complete data loss. Hence it's not wondering me that the phone actually is dead: you fully wiped it.
Click to expand...
Click to collapse
so, is there anything that I can do now?
Thanks

[Urgent help] Xiaomi Mi A1 Unlock bootloader

Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output

Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?

oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above

How's the progress so far?

Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line

arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!