Database Info

Unbricking

Hi,
This morning I wanted to charge my Mi4c, but when I went to check on it, it wouldn't unlock anymore.
I powered off the device by long-pressing the power button and tried to boot it again, without success.
When I connect the device to a computer it shows up as "QHSUSB_BULK" , which appears to be a Qualcomm test interface.
I installed the driver for it (apparently MiFlash includes it) and tried to flash it with the fastboot images from Xiaomi.. Again, no success.
I continued my search and found some OnePlus users have had this issue as well and were able to fix it using "QFIL", an imaging tool by Qualcomm.
Unfortunately, same story here, when I try to flash it gives me the following error:
HTML:
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
Does anybody know how to fix it? Would be awesome if I could fix it myself instead of sending it back to China and being without a phone for a couple of weeks.

On the miui forums I've heard in some instances you need to drain the battery to get it to reset itself.

rickbovenkamp said:
On the miui forums I've heard in some instances you need to drain the battery to get it to reset itself.
Click to expand...
Click to collapse
Seems to be right! I already put it in the box, ready to ship it back to China, when I tried one more time.
This time, I noticed the LED was blinking red (which according to other forums means the battery is fully drained).
I then tried booting it again and I started up in the official MIUI ROM (which I flashed using MiFlash when it was "dead").
Thanks for the suggestion!

I am currently experiencing the same thing. Phone was working fine one minute, and suddenly it wouldn't wake up when pressing the power button. I see the same Qualcomm USB port when attached to my PC, so I'm guessing I'll also just wait for the battery to drain.
I guess I'll be able to fix it by reflashing the ROM but I'm more curious why this happens and, more importantly, how to prevent it from happening again!
For what it's worth, I was running the xiaomi.eu version of MIUI, not the official global ROM.

[Help] Super Hard Brick - Stuck in EDL and no button response at all + SHA256 fail

Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.

ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672

billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?

Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro

Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol

thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.

hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please

op6 stuck while loading, it tries to load,then reboot,then load again..

its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal

I think ur phone might be soft bricked or idk. But I'm pretty sure the problems didn't caused by the new battery.
Seems the phone didn't recognize the /system/ or something on twrp that says "There's no system installed" coz i've faced that (no system installed) before.
If u can manage boot into bootloader, try to fastboot a twrp.img and flash a stock firmware.
If u can't, or let's just say you really feel ur phone in fked up state, try to reflash everything with MSM Download Tool.
Here's some threads I found :
Soft Bricked?
I apologize as I've been out of flashing ROMs for over 4 years now. I unlocked my OP6 bootloader, added TWRP, the flashed Lineage 11. One of my apps wont play nice with root so I tried to go back to stock. I tried to use TWRP 3.5.2_9-0 to...
forum.xda-developers.com
[OP6][LATEST 10.3.8] Collection of unbrick tools
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
Credits goes to them.
Hope it helped.

NoalFey said:
its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal
Click to expand...
Click to collapse
It is much better to state the status of your device briefly. Like are you on OOS or custom ROM, unlocked bootloader, with custom recovery installed, magisk installed, etc. Then tell the story on what you did or what happen before your phone got the issue you stated. Then maybe someone can help you in more specific way.
Like Azhar_Fahry recommended, I also recommend using MSM tool and revert back to original state like you first bought your device.

Oneplus6 qualcomm crashdump mode

Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan

Check this:
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode

Mohamedkam000 said:
Check this:
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Click to expand...
Click to collapse
As I have said earlier it is hardware issue not software so MSM tool has low chance of fixing it. It might succeed and boot but crashdump will come back again.

drsaog said:
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Click to expand...
Click to collapse
Same here..
Now i'm scared of using OOS

Question Hard Bricked my Poco X3 Pro

So for the last three months I've been using my rooted phone with the Pixel Experience ROM, and today I decided to switch back to the stock rom. I first tried to uninstall Magisk, but when I checked the app it was already uninstalled, which I think was a bit strange. Then I downloaded the global 14.0.1 MIUI and tried to flash it via recovery mode using adb, and it failed at the end of the flashing process. So I went to try to install it using fastboot, but after using the command fastboot devices, my phone was not listed. Then I went to the recovery mode again (I was using orange fox when doing so) and tried to reboot into fastboot mode. Doing so didn't change anything when using the command to list the devices, but MiFlash had it listed, so I tried using it. I selected the rom, and selected the "clean and lock" IIRC, it started to flash and said it finished without any errors, however my phone showed some errors that I can't remember now. I tried to reboot the phone, and it went back to recovery mode, so I tried to flash it again. In this time, I tried to stop the flashing process by removing the usb because I thought I should look for the errors first, and then I remembered that I shouldn't do it (I have a very bad short term memory), so I tried to put the usb back and flashing it again. This time the Miflash showed an error, and I realized I was using the flash command while in recovery mode, not fastboot (I accidentaly pressed "adb" in the recovery), so I tried to reboot my phone to change it and it turned off. There's no more battery charging screen, fastboot or recovery. After a lot of research, I found out that my phone is in ETL mode, it shows in the device manager on my pc and also shows in the miflash as "COM3" or "COM4".
Can someone please help me? I tried so many things so far, and I still don't want to send it to repair

If you selected clean and lock and it finished, that means you locked your bootloader, and with locked bootloader, you can't flash anything. And you also yanked usb out of your phone in the middle of flashing process? My bet, you screwed up partition or two, and now your phone is in EDL, my man... Just take it to a service centre, before it's completely destoryed

When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.

seiguisage said:
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
Click to expand...
Click to collapse
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.

TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
So probably It really is just a paperweight now

seiguisage said:
So probably It really is just a paperweight now
Click to expand...
Click to collapse
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.

TheMystic said:
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
Click to expand...
Click to collapse
Since my gf gave me her old Mi 9 I think I'll make this a new hobby lol

TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
What are you talking about. if he has access to EDL mode he can fix everything. Even if your UFS was completely wiped and had no partitions. EDL is a completely separate thing. However you can't reflash the software using EDL because only service centers have the authorisation to do that (some people have that access too, and you can reflash your phone if you pay them). Another way to do it is open the phone up, and short some pins to get access to unauthorised EDL.

TheMystic said:
If it shows signs of life, you may be able to resuscitate it.
Click to expand...
Click to collapse
Yeah, mouth-to-usb always helps.