Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Related
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
.
zeroiron said:
Hey guys!
i'm a bloody noob.
i never did something like unbricking my phone or wiping it or flashing it. It was my first time doing something like this because i just hate stock roms nowadays.
to unlocking the bootloader on my phone was no problem. but the problem was, that i updated my phone to adroid 11 and all the files i found in the past (half year ago) was for android 10, i think.
BUT I DIDN'T KNEW THAT BEFORE! I didn't knew that it would cause problems or that i had to be cautions about that.
Whatever. I tried to follow the instructions on this site: https://wiki.lineageos.org/devices/guacamole/upgrade
the twrp site i used was: https://eu.dl.twrp.me/guacamole/
Is the data "https://eu.dl.twrp.me/guacamole/twrp-3.6.0_11-0-guacamole.img.html" from 2021-11-22 know for adroid 11?
Because half year ago, i think, this all didn't work because there was no twrp for adroid 11 outside.
to be honest i don't know if i tried to install something else too in the past. i don't remember anymore.
I stuck half year ago on this bootloop problem. and i didn't worked again on this phone. i thought i could just wait for a new data for android 11 and try it later again.
Later is today but i made i worse!
I downloaded from this site https://download.lineageos.org/guacamole the file:
lineage-18.1-20220227-recovery-guacamole.img
after the command 'fastboot flash boot xxx.img' i reboot my phone.
Now my phone is displaying :
qualcomm crashdump mode
dm-verity device corrupted force dump
kernel-restart
what can i do now?
If i press the sound buttons + off-button i come the the boot screen which says:
blablabla
internetsite
press power button to pause boot
but this display won't stay long enough. after few seconds it's again on this crashdump mode
edit: i think i wiped in the past the whole os. And now? What should i do?
On this MSM Tool my phone isn't recognized. even with newest driver or other cable.
What should i do know? Is my phone lost now?
If some can help me please write exactly down what i should click / download etc.
If someone can german here and knows help, please help me in german. but don't have to. i'm glad if anyone can help me.
Click to expand...
Click to collapse
From what I can gather from your details I would try to get the MSM tool to work, it sounds like a driver issue, just make sure you uninstall previous driver first then go here
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
and get latest driver , follow all instructions,, also make sure your PC is installing all the optional drivers in the windows update section while your phone is connected to the PC, hth,, good luck
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!
Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/
Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.
Hi,
I f'd up when trying to install the pixel experience and chose the wrong rom. When I flashed it the phone went into EDL mode. The PC now recognizes it as Qualcomm.
I have found the correct ROM and tried to install it using several versions of MiFlash and QFIL to no avail.
I removed the phones battery and did the two point short and still, no change.
I bought a Xiaomi usb cable from amazon for Mi Note 10 and above and still same errors occur (yes, I tried all USB ports).
I have installed the unsigned drivers correctly, still, same error.
I hold all the buttons on the device for 30 seconds and then plug it in and hit flash ASAP. The result is always cannot read from COM07. Then, if I try and flash again, it says it cannot read hello packet.
With QFIL I get the sahara error.
I may be missing something here, I'm a noob who should have read the instructions and double checked everything. I have paid someone on telegram to help me, but they seem to be out of ideas too and can only suggest that it might be a hardware issue. Can installing the incorrect firmware damage hardware beyond repair?
At this point I am close to just giving up as it's taken so much of my time and the stress is unbearable lol.
Thanks to anyone who reads this post, hopefully there is something that I haven't tried yet.
Thank you
You need Xiaomi AUTH or proffessional repairing tools. Or wait untill someone patch the loader.
Hello . I have OnePlus 7 pro I update it to android 12 and the next day something went wrong and my phone started an error Qualcomm crash dump something... Now it is stuck in EDL . Display none , power key And volume key works but keep booting in EDL even without connecting the USB cable . I flash the firmware with msm tool firmware flashed %100 but it didn't boot still in EDL .can someone guide me how to fix it
Can someone help!
jahanzaiblohani said:
Can someone help!
Click to expand...
Click to collapse
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
darksx said:
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
Click to expand...
Click to collapse
Drivers are correct and I was flashing it with USB 3.0 port .
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
KyRol said:
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
Click to expand...
Click to collapse
I have the old stock ROM which I flashed it in EDL but phone didn't boot when it is completed phone reboot too but not in normal mode in EDL again
Most often people have bad experience with qualcomm drivers. So make sure that you have some released after 2020 year, as oneplus 7 pro was released in 2020 year. Another issue is related to usb 3.x, better avoid that and try USB 2.0 instead, most of people have best results with older interface of that kind. EDL is kind of old solution, so better to stay away with USB 3.x and use USB 2.0.
Have you got any idea your flash is successful in edl tool? Have you got clean results or warnings/errors?
To be honest with you, I have to use EDL too, because I did wrong upgrade. I used custom ROM instead of stock ROM. Now I have not access to fastboot nor adb via USB either.
try different EDL ROMs, I found 2 threads. one is here, second there. As almost nobody anserws our questions, I will let you know what I did if I do it successfully.
Well, I discovered that I'm in pretty bad situation. In my case not only adb and fastboot does not works. It appears that EDL does not work either. Why? because I connected another oneplus phone over USB to PC and EDL mode was detected spot on. In case my o+7pro, well still same error as previously with adb/fastboot over USB. Something messed with USB on my phone at software side.
So I have to get motherboard get cheap. I do not thik that I can desolder flash or eMMC and revert that so easy.
Sorry Man, can not help you any
further. Turns out my issue is signifigantly other than yours.