Is there any fix for this or EDL files available? This started happening in July. It resolved for quite a while and now has started again with an Android 12 update alert. It has not been downloaded are people having these issues on Custom Roms like Lineage or Graphene OS or is this specific to Stock OS . I am unmodified stock
Just a follow up. The Android 12 update went through and the EDL issues have resolved. The solution when it was stuck in EDL mode was to just hold the power button until it powered on. I understand that does not work for everyone. The way I determined it was in EDL mode was by connecting it to a Windows 10 PC and checking device manager.
Related
Hi, today my Axon 7 got stuck in EDL mode for the second time. And I would like to know why...
I was about to flash TWRP in order to try LOS 16.0 and when I turned the phone off and plugged the cable with the button combo it entered into EDL Mode sucessfully (PC recognises it normally, COM3) but EDL Tool got stuck at "Loading the programmer: prog_ufs_firehose_8996_ddr.elf".
The only way to fix this problem as far as I know is by restarting the phone into EDL again but mine is somehow getting stuck and I can't restart/turn off
As I said before this is the second time it's happening, and the last time the only way i got it fixed was by waiting until the battery runs out and then try again.
Does anybody know what causes this? Is there any fix? Thanks in advance
Sorry for my english
joaocandeias said:
Hi, today my Axon 7 got stuck in EDL mode for the second time. And I would like to know why...
I was about to flash TWRP in order to try LOS 16.0 and when I turned the phone off and plugged the cable with the button combo it entered into EDL Mode sucessfully (PC recognises it normally, COM3) but EDL Tool got stuck at "Loading the programmer: prog_ufs_firehose_8996_ddr.elf".
The only way to fix this problem as far as I know is by restarting the phone into EDL again but mine is somehow getting stuck and I can't restart/turn off
As I said before this is the second time it's happening, and the last time the only way i got it fixed was by waiting until the battery runs out and then try again.
Does anybody know what causes this? Is there any fix? Thanks in advance
Sorry for my english
Click to expand...
Click to collapse
Only way out of EDL Mode (asides from flashing a file) is to let the battery drain completely.
If your phone gets stuck loading the .elf file whilst using the Axon 7 EDL Tool, you can try a couple things: -
- Change which USB port you are plugging into
- Change your wire
- Use MiFlash instead, simply just put the twrp into a folder and rename the twrp to recovery.img and select that folder in MiFlash.
- Make sure your Axon 7 EDL Tool is extracted properly to C:/ Axon 7 EDL Tool
- Go into EDL mode via ADB and try again, or go into EDL mode via just plugging in your device whilst it's on the home screen and launching the EDL Tool. The EDL Tool will automatically take you to EDL mode.
Hey there,
just wanted to add that I had the very same issue. In my case I solved it by letting my battery drain just like you described and get into EDL Mode once more but this time with another USB slot.
More precisely I tried it with USB 2.0 instead of 3.0. I don't know if that was the resolving change in the end but then it suddenly worked out for my. In my case it was full flashing nougat 7.1.1 when I had Oreo b03 before.
2 solutions:
- try rebooting to EDL, using Axon 7 EDL Tool flash a custom recovery. It will then ask you to reboot.
- you can also flash a full EDL stock ROM, but you will certainly lose data.
- if you can't use Axon 7 EDL Tool because EDL mode isn't working correcly, let the battery drain totally then boot to EDL.
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!
So im gonna start off by saying that im just some dumb 18 year old and have never actually posted to ask for help, only reading other peoples situations to try to figure out my own.
but introductions aside im just gonna jump in to everything wrong with my oneplus 8 pro (global)
I was on the OOS 12 beta for a while, ive been way too lazy to change it back since ive been occupied by other stuff.
I was using magisk and decided to do some fun shenanigans with it.
I get into bootloop after flying to close to the sun with modules - a common occurrence.
so I try to switch to a custom rom since I was gonna reset anyway.
I download CR droid's recovery and main rom, went into fastboot and flashed the recovery.
I notced that whenever my phone was plugged into the computer, the options would rapidly switch on fastboot's end
when I tried to boot to recovery after flashing, it would only return to fastboot
confused I thought that maybe the recovery was bad and try another rom, no dice
i submit defeat and go to msm tool to fix the issues
I get that "Sahara communication failed" error so I hold down the volume up + power for 13 seconds before trying again.
it flashed smoothly
after getting sad at all the bloatware that was on oxygen OS after a full reset, I get the motivation to try using a custom rom again, this time using a different rom.
same weird fastboot behavior
I was unable to go into recovery
I then tried downloading stock firmware to flash it manually
fixed nothing
I delete the boot and recovery partitions and flash them again, still no dice
I even make a partion called fart, before remembering that I do not know the partition structure of android so i Ctrl+C out before it makes the partition
I go back to msm tool again in shame
"Unknown Target Device"
I reinstalled drivers
switched computers and cables
changed the source of my drivers
nothing fixed this error
and every time I would try to do anything it would go directly back to fastboot.
I try reflashing partitions in this broken fastboot mode and it would only flash if I unplugged, selected reboot bootloader, and plugged it back in
I would then try to fastboot boot into TWRP or other recoveries i downloaded
they would shut off the phone
I remember a/b partitions exist so I switch over between them and try to flash stock OOS again
after more fiddling and nothing working, I noticed some more weird traits of fastboot
twrp did boot directly after switching my main slot, not specific which one just if the slot was changed.
the "this device has an unlooked bootloader" message did not appear
only on slot a would the oneplus logo show up on boot
again every option I would click would take me right back to fastboot.
I wait a day for the phone to die so I could use EDL that way, at this point the twrp method randomly stopped working so I couldn't go into edl that way.
"Unknown Target Device Param Preload"
and like I know Param Preload is a common error but nowhere could I find information on the unknown target device part.
the phone still vibrates if I hold the power and vol+
it just vibrates in a loop as if it keeps rebooting, probably fastboot just selecting the start key over and over when I hold it down.
vol- and power do nothing, and did nothing for the entirety of this story.
is there any chance of saving my poor instantnoodle professional?
## edit for people googling this
the problem I was having was that I didn't set the "target" button on the MSM tool correctly, so make sure its set to O2 or your appropriate reigon
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
xtcislove said:
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
Click to expand...
Click to collapse
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
NatunaSushi said:
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
Click to expand...
Click to collapse
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
xtcislove said:
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
Click to expand...
Click to collapse
after a week of fiddling I DID figure out the issue
unsupported Target unknown was refering to the fact that I had the MSM tool set to Target mode, which I assume tries to set the region according to what the current device has. After selecting that to O2 for the global models, the flash worked fine. I ended up coming across some C stock of a google pixel 3a and will try messing with that so I dont have to go a while without calls or texts. Glad to know I learned some bit of responsibility from this excursion.
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Ezzell said:
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Click to expand...
Click to collapse
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
HolyHog said:
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
Click to expand...
Click to collapse
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Ezzell said:
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Click to expand...
Click to collapse
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
HolyHog said:
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
Click to expand...
Click to collapse
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Ezzell said:
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Click to expand...
Click to collapse
If MSM does not recognize your phone there is something wrong with your PC.
Make sure that you read the full post:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use another USB Port and/ or another USB cable.
Dont use Windows11
Install latest Universal ADB Driver
Install latest Qualcomm Drivers
Install latest OnePlus drivers.
In fact the last thing that will NOT work is MSM. If MSM does not work your phone is completly dead. (Which yours is obviously not because it boots into bootloader) This means if MSM does not work, there is something wrong on your end.
Talking about dead devices, be etremly careful what you do in Fastboot mode!
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anything you do in the OS, like allowing OEM unlocking has **nothing** to do with MSM. In fact, a MSM flash will relock the bootloader. You will have to unlock again if you want to run anything except stock.
You have to boot the phone into EDL mode. Start MSM, then while holding the volume bar down, (UP and down, the entire button) plug into usb. Dont use the power button. (You may let volume keys go once done) There will be a dark screen, the only way to tell if in EDL mode is to check your device manager for the correct device. If you see anything on the screen you are not in EDL mode. I did use USB 2.0, do not use a hub.
I ask to start MSM first because on my Oneplus8, the EDL mode wont stay active for too long, unless MSM finds the phone.
If that does not work, put the phone into EDL mode and check your device manager (ports COM anf LPT) for QDLOADER 9008. Anything else, and the driver is not installed correctly and MSM won't work, If adb is working you can issue "adb reboot download" but the button press seems more applicable in your case.
There is a lot in the link below, it is for A10, I believe there is now a MSM for A11 but I have no experience with them.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
I have tried all these and msm will not recognize the device in any state so Iv reverted to using a repair shop msm was successful in making the device stock the problem came from rebooting the device while msm was still connected and running. Pressing any button would lead to the download failed screen where the device is not recognized or into bootloader where oem is locked and even though before boot I checked unlocking enabled the fastboot command would not unlock the bootloader, if the store fix it I will try get details on what they did
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.