Database Users

I can' get it to boot properly. Help me please!

A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.

Tried ZUI QPST image or CM one?

ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.

ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM

kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?

ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.

kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?

ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.

ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.

kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns

Bad flashing through MiFlash

Hello! A few days ago I tried flashing the android 9.0 in the MI A2 and in the middle of the process I turned off the PC and did not finish the process ... I wanted to turn it on and it remains in the MI logo, I put it in fastboot mode but the pc does not recognize me the cell and it does not let me flash again ...
What I can do?:crying:
thank you.

andygunch1993 said:
Hello! A few days ago I tried flashing the android 9.0 in the MI A2 and in the middle of the process I turned off the PC and did not finish the process ... I wanted to turn it on and it remains in the MI logo, I put it in fastboot mode but the pc does not recognize me the cell and it does not let me flash again ...
What I can do?:crying:
thank you.
Click to expand...
Click to collapse
go in fastboot
cmd -> then "fastboot oem edl"
the phone will turn on in the bootlader mode ... run my flash and upload the system I install there and I have no problem
when MI Flash shows the message success
disconnect the phone from the computer
keep the power button on the phone will not show the AndroidONE logo

martin5263 said:
go in fastboot
cmd -> then "fastboot oem edl"
the phone will turn on in the bootlader mode ... run my flash and upload the system I install there and I have no problem
when MI Flash shows the message success
disconnect the phone from the computer
keep the power button on the phone will not show the AndroidONE logo
Click to expand...
Click to collapse
That's not going to work, I had the same problem, you have to force the EDL mode with the test points on the motherboard.
Check this: https://forum.xda-developers.com/showpost.php?p=78554236&postcount=12

syncstar32 said:
That's not going to work, I had the same problem, you have to force the EDL mode with the test points on the motherboard.
Check this: https://forum.xda-developers.com/showpost.php?p=78554236&postcount=12
Click to expand...
Click to collapse
can I change the batteries?

martin5263 said:
can I change the batteries?
Click to expand...
Click to collapse
I don't understand

syncstar32 said:
I don't understand
Click to expand...
Click to collapse
you can replace the batteries with a new one ?

andygunch1993 said:
Hello! A few days ago I tried flashing the android 9.0 in the MI A2 and in the middle of the process I turned off the PC and did not finish the process ... I wanted to turn it on and it remains in the MI logo, I put it in fastboot mode but the pc does not recognise me the cell and it does not let me flash again ...
What I can do?:crying:
thank you.
Click to expand...
Click to collapse
This was same problem with me .So due to my was under warranty and I know opening phone(Because there is possibility that many Xiaomi Devices like redmi series , these devices can force device to edl mode by sorting points in board) may void warranty. So I don't consider to take risk and went to service centre and after 2 day they weren't able to recover ,that said if I would take risk to recover it wont happen just due to motherboard was damage due to partial flash and it also Fastboot and boot file thus device wasn't detecting or going into that mode .
My best recommendation is get repaired from service centre .BEFORE warranty is Void
I Got New Board with new IMEI and all new stuff.

Rushikesh googlelar said:
This was same problem with me .So due to my was under warranty and I know opening phone(Because there is possibility that many Xiaomi Devices like redmi series , these devices can force device to edl mode by sorting points in board) may void warranty. So I don't consider to take risk and went to service centre and after 2 day they weren't able to recover ,that said if I would take risk to recover it wont happen just due to motherboard was damage due to partial flash and it also Fastboot and boot file thus device wasn't detecting or going into that mode .
My best recommendation is get repaired from service centre .BEFORE warranty is Void
I Got New Board with new IMEI and all new stuff.
Click to expand...
Click to collapse
if it is in warranty so I will resort to take it and they tell me, but take it to a technical service that can be solved, it hurts that here in Argentina there are not many who know or repair .....

A similar thing happened to me. I was flashing Pixel Experience (clean installed stock Oreo before that) and once the flashing finished and I switched to the partition it flashed to I was greeted with the Android One screen without the Unlocked message at the bottom. The phone wasn't even detected by my PC while in fastboot so I just went to the service center and told them it just got stuck like that after a system update. They fixed it and it was covered by the warranty.

Urgent Help needed to flash realme 2 pro (RMX 1801)

I need to flash my oppo realme 2 pro (RMX 1801) phone. In msm download tool it ask for username and password, i did try some bypassing method by googling, but they didn't work. And i didn't find Qfil version of 1801. can anyone help me how can i flash my phone??

Rakib475 said:
I need to flash my oppo realme 2 pro (RMX 1801) phone. In msm download tool it ask for username and password, i did try some bypassing method by googling, but they didn't work. And i didn't find Qfil version of 1801. can anyone help me how can i flash my phone??
Click to expand...
Click to collapse
You have to visit Service Center. As the username and password are secure and only available to official Developers (Service Center) .Did you relock your bootloader????

My phone has also suffered the same fate when I tried to exit the in-depth program via the app. The app said that I need to lock the bootloader before I can actually exit it. But, the problem is that the bootloader stopped working immediately after.
If I try to go to fastboot mode, then the word fastboot is displayed on the screen with the reasoning given in Chinese language. Though, in between the reasoning "6 ~ 10" is written. I wonder what these numbers means.
Also, the option to enter the program has disappeared already.
I did visit, service center this morning and they installed the old color os again. With this ROM, I did got my OTA update to color os 6 and the phone didn't showed orange state screen upon boot. But, in the developer options, it still said that the bootloader is still unlocked.
Upon updating the phone with OTA to color os 6, the orange state screen appeared again upon boot. Weird.
I really don't know what to do now. My phone has stock recovery, stock rom but no access to fastboot.

handsome_94 said:
My phone has also suffered the same fate when I tried to exit the in-depth program via the app. The app said that I need to lock the bootloader before I can actually exit it. But, the problem is that the bootloader stopped working immediately after.
If I try to go to fastboot mode, then the word fastboot is displayed on the screen with the reasoning given in Chinese language. Though, in between the reasoning "6 ~ 10" is written. I wonder what these numbers means.
Also, the option to enter the program has disappeared already.
I did visit, service center this morning and they installed the old color os again. With this ROM, I did got my OTA update to color os 6 and the phone didn't showed orange state screen upon boot. But, in the developer options, it still said that the bootloader is still unlocked.
Upon updating the phone with OTA to color os 6, the orange state screen appeared again upon boot. Weird.
I really don't know what to do now. My phone has stock recovery, stock rom but no access to fastboot.
Click to expand...
Click to collapse
Attached are the screenshot of the screen and its translated version.

so far there is no free method for flashing the firmware for realme.

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"

[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!