Related
Hello everyone,
My phone suddenly got stuck in EDL mode (getting recognized as Qualcomm .... 9008 on my pc) and for the life of me, I cannot figure out how to get it out of it. Cannot even boot in fastboot.
I have tried almost all versions of MiFlash, back to a 2014 one, and each of them gets stuck at "Sending nop command" or "Ping target via firehose" which are practically the same in the logs.
I'm trying all this with the battery and fingerprint sensor unlocked.
Also tried to use QFIL but all I get is "FHLoader failed The system cannot find the specified file".
Unfortunately there's no Xiaomi tech support in my country so I cannot take my phone to any physical place as far as I know.
Any ideas?
Things I tried so far:
Various versions of MiFlash
Fastboot ROM
Stock ROM
QFIL
Windows on Test mode
Shorted to EDL mode
No battery connected
No Fingerprint connected
No module connected
Holding Vol Up / Vol Down and Power
Holding the Power button for more than 3 minutes and while flashing
Drained the battery and charged it back
Different voltages, chargers and cables
You will most likely need Deep Flash cable...\
Edit:
Your phone is most likely hardbricked, so DF cable is only solution.
OR
Try this:
http://en.miui.com/thread-380827-1-1.html
After you unbrick your device with EDL with patched programmer, you might have issues with your partition table being problematic and TWRP not flashing ROMs that are zipped.
This may also happen when MIUI gets updated to a degree that it doesn't accept custom ROMs.
Here is the solution.
Prerequisties
Download MIUI Fastboot ROM version 8.9.6
Download MiFlash 2016.04.01.0 (64 Bit)
Download TWRP CN
Download the patched programmer
Installation
Way 1 (Fastboot way)
After you have done downloading the needed files, install MiFlash, extract the firmware.
Open MiFlash, select the firmware folder, choose Flash All.
Boot to fastboot
Click refresh after you have connected, and flash.
After done, instantly boot to fastboot.
Boot this TWRP: recovery-TWRP-3.2.3-0810-XIAOMI6X-CN-wzsx150.img
Backup your whole phone (excluding "System Image" and "Vendor Image") just in case and copy the backup to your computer.
Flash a ROM now.
Format data.
Flash the ROM again.
Way 2 (EDL way)
After you have done downloading the needed files, install MiFlash, extract the firmware.
Then, backup stock "prog_emmc_firehose_Sdm660_ddr.elf" somewhere else, and ONLY REPLACE THAT FILE WITH THE PATCHED ONE.
Open MiFlash, select the firmware folder, choose Flash All.
Force your phone to EDL. If you can flash via normal ways, good for you. But if you can't, there is only one solution. Testpoints. (Explained later)
Click refresh after you have connected, and flash.
After done, instantly boot to fastboot.
Boot this TWRP: recovery-TWRP-3.2.3-0810-XIAOMI6X-CN-wzsx150.img
Backup your whole phone (excluding "System Image" and "Vendor Image") just in case and copy the backup to your computer.
Flash a ROM now.
Format data.
Flash the ROM again.
I don't recommend flashing TWRP. Boot if you need.
How to testpoint
• Turn off the phone, unplug the USB.
• Unscrew the bottom screws.
• Open the back of your phone, carefully. You may damage your screen.
• Unscrew the port protector.
• Unplug the screen, battery and EDL protector.
• Connect two EDL Testpoints with a metal piece and connect the device to the PC via USB.
Reserved
Hi, i Hope you Can help me.
Some months ago i rooted my Mi A2, After some weeks i wanted to go back to stock, and i tried to do It, but i missed something and the process went wrong. I tried to Save It with EDL, the first flash was good and phone booted up, so i decided to turn It Off to reassamble It, but After that the phone didn't boot up never again, i tried some others flash with edl, mi flash said success but the phone didn't boot.
I tried several times but in the last (i think) 50 try mi flash returned errors like "cannot read from port... etc", After this several tries my phone stopped to go to edl, (connecting test points doesn't work) and now It is completly dead. I tried to let It discharge and take It in charge for some days, nothing works.
Do you have any idea?
Thanks.
Inviato dal mio Redmi 3 utilizzando Tapatalk
michiamoantonio said:
Hi, i Hope you Can help me.
Some months ago i rooted my Mi A2, After some weeks i wanted to go back to stock, and i tried to do It, but i missed something and the process went wrong. I tried to Save It with EDL, the first flash was good and phone booted up, so i decided to turn It Off to reassamble It, but After that the phone didn't boot up never again, i tried some others flash with edl, mi flash said success but the phone didn't boot.
I tried several times but in the last (i think) 50 try mi flash returned errors like "cannot read from port... etc", After this several tries my phone stopped to go to edl, (connecting test points doesn't work) and now It is completly dead. I tried to let It discharge and take It in charge for some days, nothing works.
Do you have any idea?
Thanks.
Inviato dal mio Redmi 3 utilizzando Tapatalk
Click to expand...
Click to collapse
Use QFIL instead of MiFlash and disconnect the battery. Hold testpoints and connect the phone to computer.
Make sure to plug out the correct one (the one with black overlay, not the right, wider one. That's of USB ports).
Letzen said:
Use QFIL instead of MiFlash and disconnect the battery. Hold testpoints and connect the phone to computer.
Make sure to plug out the correct one (the one with black overlay, not the right, wider one. That's of USB ports).
Click to expand...
Click to collapse
Already tried, PC doesn't detect the phone
Inviato dal mio Redmi 3 utilizzando Tapatalk
michiamoantonio said:
Hi, i Hope you Can help me.
Some months ago i rooted my Mi A2, After some weeks i wanted to go back to stock, and i tried to do It, but i missed something and the process went wrong. I tried to Save It with EDL, the first flash was good and phone booted up, so i decided to turn It Off to reassamble It, but After that the phone didn't boot up never again, i tried some others flash with edl, mi flash said success but the phone didn't boot.
I tried several times but in the last (i think) 50 try mi flash returned errors like "cannot read from port... etc", After this several tries my phone stopped to go to edl, (connecting test points doesn't work) and now It is completly dead. I tried to let It discharge and take It in charge for some days, nothing works.
Do you have any idea?
Thanks.
Inviato dal mio Redmi 3 utilizzando Tapatalk
Click to expand...
Click to collapse
you have the same problem that i have. your phone can't go to fastboot,recovery,boot,no vibration,no LED blinking. only 1 thing works that is stucks in EDL Mode.
did you have this same problem ?
If yes, then your eMMC is corrupted !!
you need to be go to a talented person that can open your mobile and remove eMMC then put eMMC in UFI Box or EasyJtag Plus Box. then eMMC is programmed from there and after this reentered eMMC in phone !!
and your phone will be Boot Successfully !!
Thanks !! :good::good::good:
Hi, just wondering, I have a Mi A2, did a test point boot, used Miflash to install an official ROM, it showed progress and got the success message, but when i try to start it it shows the android screen, and then shuts down.... Any toughts on what could happen?
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"
So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
falzer2007 said:
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Click to expand...
Click to collapse
that's not very descriptive, produce the error and share results here
dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse
Okay so I open the msm tool. Then I have my oneplus 6t (t mobile) turned off. I hold both volume buttons and keep holding them while I connect the USB cable to the phone. Its basically in edl mode at this point. Then I press the start option on the msm tool. The bar fills up with green and completes itself. However a number appears that saids "4s" inside of the square. I assume that means 4 seconds left or completed in 4 seconds. My phone is still in edl mode at this time and will not boot up in any menu (normal.menu, boot menu/recovery mode). Unlesss I boot it manually.
And yes I tried a scenario where I held down both volume buttons, connected USB cord, and then let go. I also tried the scenario where I held both volume buttons, connected usb cord and kept holding the volume buttons until the process completed itself but I would get the same result. "4s"
dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse
falzer2007 said:
So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, Falzer. had all but given up and was prepared to head to T-Mobile to buy the 1+ 9 Pro (I almost wish I did not fix my phone... *BUT* I DID!
My issue occurred trying to flash a Magisk patched boot.img to my newly unlocked bootloader phone. I was following an article that alleged one could root the phone without TWRP. I will say this TWRP is your friend; don't dis "him". By the way, unlocking my phone wiped my data so always important to read the whole article first as it was mentioned in the NEXT step.
[Should be including the actual error here - it is found throughout these forums but I cannot recall the exact display. Basically, if you have an unlocked bootloader and then get to the CrashDump screen, follow from here:]
Retrieve the file, boot11.1.1.1.img and download from this thread/link:
OOS stable boot image and patched magisk boot image both for 11.1.1.1.
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out. Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"...
forum.xda-developers.com
Do *NOT* mess with the other file to the right.
Hold all 3 buttons (2 volume buttons + power) and once/if you see Fastboot Mode, release the buttons.
Have ADB installed (you should be able to find plenty of directions for doing this).
From either PowerShell (or *maybe* CMD Prompt started as Administrator as I had been using this "successfully" for most functions):
fastboot devices
fastboot flash boot boot11.1.1.1.img
fastboot reboot
I could not believe my phone ACTUALLY booted (even with the McLaren animation intact; I'm sure one of the gurus here knows why) after all the failed attempts fooling around with MSM Download Tool [4.0] which almost EVERYONE swears by fixes/restores any brick. I understand ON ONE is forcing anyone to use any specific resolution; I am just trying to provide another last ditch effort.
EDIT/Caveat: I did not even check to see how old that thread above is, I believe late September and I had actually taken updates [via TMobile??] until the last one with a week to 10 days *but* that was probably wiped with the boot unlock so I do not know which "update" I got but figured I didn't have much to lose as I already had a "bad" version of a boot.img flashed anyway. Anyone with any technical explanations, feel free to comment. Thanks!
I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.
Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.