Model Name: MI Play M1901F9E
Problem: It is bricked, in bootloop. I cannot shut down the device until its charge gets depleted.
Abilities: It can get into recovery mode and fastboot mode. Pc detects the phone without any problem in both modes.
Observations:
- Factory Reset fails when it reaches 65%.
What is done:
- I tried flashing the latest stock ROM (V11.0.9.0.OFIMIXM) via recovery, using Mi Flash Tool Pro. Everything was going fine, however the percentage in the pc screen got stuck at 49% and after a while it gave a success result but nothing happened. I tried this a couple more times and same thing happened at different percentages (60%, 65%...)
- I tried using Xiaomi Tool V2. Everything was the same. After trying more, the percentage came to 100% and the program gave success result. However, after this process, phone started to count percentage again and it got stuck exactly at 55%.
-I tried using Xiaomi Adb tool via CMD. Similar things happened. It either gets stuck while flashing, or after flashing at different percentage values.
- I tried using MiFlashTool, however, it requires an unlocked bootloader. It gives error. I tried unlocking the bootloader via fastboot but it gives: "token verification failed". Tried Mi unlock tool, but it requires an authorized account.
- I tried using SpFlashTool, however, it requires an authorized account.
So, I'm stuck. I don't have usb debugging enabled, and I don't have the bootloader unlocked. I am not sure if there is any problem with the hardware. Any ideas? Does anyone know why does it get stuck during the recovery flash process via adb?
Related
Hello guys,
i wanted to upgrade my Ressurection Remix ROM and managed to softbrick my phone. While flashing the software (Flashing system partition unconditionally) TWRP got stuck.
My phone got an unlocked bootloader and i already tried to flash the global MIUI ROM via EDL and also fastboot. The flashing process is successfull but after i restart my phone i'm stuck at the MI Logo with the moving Android Circles for loading.
I let this run for ~6 hours, no progress at all.
I also tried flashing the Global DEV Rom, same as above.
Factory Reset via Recovery Mode (with MI Suite) also didn't do the trick.
I think something with the bootloader went wrong. Any ideas to unbrick it?
I can access Fastboot and EDL Mode, unlocked Bootloader. I also got a TWRP backup with System and Data Partition, but currently only the original Revocery is installed.
Any help is very much appreciated, thank you.
Did you tried using this guide to flash stock firmware/recovery?
http://en.miui.com/a-234.html
Yes, the problem is not to flash the Fastboot ROM, but after successfully flashing the ROM i got stuck at the MI Logo with the loading Android dots
That's weird.. this bootloop usually happens when you flash stock MIUI and still have TWRP installed, can you check if you have stock recovery after fastboot flash?
After i flashed the global DEV ROM i got the stock recovery where i can choose between Wiping Data, switch to MI Suite etc.
Edit: Its not really an bootloop, it just gets stuck there without doing anything
Update: Got TWRP back, now if i want to flash any ROM (doesn't matter if stock/custom) i'm stuck at TWRP saying: "Patching system unconditionally..." it stays there for hours.
Any advice in this case?
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
tandob said:
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
Click to expand...
Click to collapse
That has absolutely nothing to do with the problem mentioned above.
Hi, offering $10 PayPal to anyone that helps me fix my phone. (Don't know if this is against the rules, if so, I take it back).
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
What are my options guys? Is this a dead case? Any help is greatly appreciated.
Since i was recieving less SOT (4-3 hours on light usage) on my mido even after flashing the stock rom (xiaomi.eu rom), i decided to replace the battery at an authorised mi service centre. They said they wont accept unlocked mi devices. So i decided to relock the bootloader. Heres what i did, (im using orange fox recovery)
1 . wiped system, data, cache, dalvik cache
2. formatted internal storage
3.flashed stock rom (from the official site stable version)
4.flashed the lazyflasher zip
then after finishing the initial setup of rom, i went to recovery and flashed the stock recovery.
then in fastboot mode I ran the script " fastboot oem lock" to lock the bootloader. But after rebooting, mi logo blinks for a second or two and shows a black screen.
I checked the bootloader status and it says locked (device unlocked : false). I tried the testpoint method and the DFC method but pc dont detect my device and i cant find the qualcomm hs-usb qdloader 9008 in device manager. No matter how hard i try i cant get my pc to detect my phone in both the methods. Also when i try to get into edl mode (by shotting the first and 4th contact points located above the battery) i can hear windows 10 sound of detecting a device but nothing appears in the device manager. Im sure i have all the drivers installed and i really dont know what im doing wrong here. Is there any other way to unbrick my device?
Try detect your phone by using latest mi flasher. (Download and install it first). If your device's blink red, i sign if it in EDL mode. I dont know what happen to your device actually, because i never try to relock my mi phones using ''fastboot oem lock". I use mi flasher to relock my phone by clicking ''flash and relock" on Mi flasher. Try mi flash first, then comment here again if it fails.
aah i didnt know testpoint method requires battery plugged in, silly me. This time pc detected my phone (testpoint) and as per your suggestion i tried miflasher and it worked (yaay). thanks for helping me out here...
didnt xiaomi removed edl mode from RN4 due to security reasons??
Can anyone help me with this???
My OEM unlocking option gets unselected on its own even after my phone is unlocked. I have rn4 SD variant.
Hi, I beg your help. Well what happened is,
I was on CORVUS OS, then I thought of rolling back to stock rom. So after flashing "laurel_sprout_global_images_V12.0.21.0.RFQMIXM_11.0" using Mi Flash tool (clean and unlock), My phone said to me "This device has been destroyed". So I thought I might have flashed a wrong version. So I again flashed "Xiaomi_Mi_A3_V10.3.4.0.PFQMIXM_20190815.0000.00_Global_9.0_XFT" using Mi flash tool. But this time, android one logo showed up and did'nt proceed. Luckily I could access to fastboot mode. But after doing this flashing few more times, My phone blacked out completely. Things I have done so far:
1. Tried flashing again using Mi flash tool. The device manager says that the "QDloader 9008" is connected properly, but the flash tool is saying "cannot receive hello packet" and eventually fails the proccess.
2. Tried volume button and plugin combination. Nothing happened.
3. Download QFIL software. But it's not detecting any device.
4. Tried switching USB port
Please save me. I am going through a disaster. and it's my primary driver T_T
try to disconnect the battery, and plug usb
Try flashing using Paltform-Tools instead of Mi Flash Tool. See https://forum.xda-developers.com/t/slot-a-is-destroyed.4399965/ for links to instructions.
Do not take the back off your phone. Seriously, shell out the ten bucks for the deep flash cable. You need to get to EDL. Here are a couple of methods, depending on what you want:
Repackaged A11 stock here: https://c.mi.com/thread-3527044-1-0.html
CC9e Conversion here: https://forum.xda-developers.com/t/miui-12-port-10-miui-12-for-mi-a3-stable-weekly-rom.4016457/
Note: If you want to use QFIL, make sure you're using the latest version with QPST. Save yourself the time and install it system wide. https://qpsttool.com/qpst-tool-v2-7-104
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Roudero said:
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Click to expand...
Click to collapse
Yeah, same story for me. Looking for an answer too
I was facing same problem. so i gave it to local phone repair shop. they solved it perfectly.
angshuman_sarkar said:
I was facing same problem. so i gave it to local phone repair shop. they solved it perfectly.
Click to expand...
Click to collapse
can you tell us what local repair shop done with phone? i also gave to local repair shop they said it cant be repaired!
Roudero said:
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Click to expand...
Click to collapse
same thing hapannig with me . is it your issue fixed if tell me how ?