Develop Bugs

MiFlash Can not read from port com - whyred

Hi, can someone help? I was about to flash the official whyred Linedage OS for my Redmi Note 5. I did that with note 3 and note 4 before, so kind of knew what I was doing.. But was not aware of the antirollback thing.. So after i decided to flash the new miui 10 firs for the firmware..(wasn't the best idea I know) and you know the rest.. something went wrong and now I am stuck with dead phone.. no recovery, no fastboot, nothing.. I had unlocked bootloader officially a few weeks ago, got the device connected with the mi account (not sure about if the account is authorized or not).
I tried the test point method - dissembling the device from miui dot com
I have the right driver listed in device manager (Qualcom HS-USB QDLoader 9008)
I tried several roms listed here or miui dot com
I tired several versions of MiFlash
Every time I only get the message about not reading the com port (tried all USB ports on two PCs, reinstalled drivers .. everything) .. It starts flashing "read hello packet", then after 5 seconds stops with the mesage "can not read from port comXY"
In edb its just waiting for the device on any command (or not devices found)
Anyone can help please? I spent the whole day searching for solution and found nothing, or nothing helps
thx in advance

I am in your same situation. did you solved it?
thank you

rfiore said:
I am in your same situation. did you solved it?
thank you
Click to expand...
Click to collapse
Yeah, posted my ID on the forum, got authorized, then used the "portable" miflash and it worked.. But on the other PC still got errors in miflash.. didn't even check for the authorization, so I suppose its PC related.. perhaps something with the drivers..

FKuzel said:
Hi, can someone help? I was about to flash the official whyred Linedage OS for my Redmi Note 5. I did that with note 3 and note 4 before, so kind of knew what I was doing.. But was not aware of the antirollback thing.. So after i decided to flash the new miui 10 firs for the firmware..(wasn't the best idea I know) and you know the rest.. something went wrong and now I am stuck with dead phone.. no recovery, no fastboot, nothing.. I had unlocked bootloader officially a few weeks ago, got the device connected with the mi account (not sure about if the account is authorized or not).
I tried the test point method - dissembling the device from miui dot com
I have the right driver listed in device manager (Qualcom HS-USB QDLoader 9008)
I tried several roms listed here or miui dot com
I tired several versions of MiFlash
Every time I only get the message about not reading the com port (tried all USB ports on two PCs, reinstalled drivers .. everything) .. It starts flashing "read hello packet", then after 5 seconds stops with the mesage "can not read from port comXY"
In edb its just waiting for the device on any command (or not devices found)
Anyone can help please? I spent the whole day searching for solution and found nothing, or nothing helps
thx in advance
Click to expand...
Click to collapse
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.

Simple.. Disconnect and Reconnect with your PC Via Testpoint.. Thanks.

thank you very much
Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
I was lose hope because 12 hour my mido error cant read hello packet, and now fix it with your tips.. thanks a lot man

Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
Thank you. I was in the "read hello packet" part and i was able to flash the Chinese rm
Thanks

Can u please give me your mi authorized I'd it will help for me
Am also stuck on edl mode redmi note 5 pro so please give me your mi I'd

Raviganthy said:
Am also stuck on edl mode redmi note 5 pro so please give me your mi I'd
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780

Help!
Help! i am also stuck on this problem on my Redmi 3. Can someone please help me?:crying:
---------- Post added at 06:18 AM ---------- Previous post was at 06:15 AM ----------
FKuzel said:
Yeah, posted my ID on the forum, got authorized, then used the "portable" miflash and it worked.. But on the other PC still got errors in miflash.. didn't even check for the authorization, so I suppose its PC related.. perhaps something with the drivers..
Click to expand...
Click to collapse
What forum?

can not read from port com xy
guilherme06 said:
Thank you. I was in the "read hello packet" part and i was able to flash the Chinese rm
Thanks
Click to expand...
Click to collapse
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.

talhosvi said:
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.
Click to expand...
Click to collapse
I have the same problem with my jasmine(which used to be wayne) when I tried to change it back into wayne again... do you have any solution already ?

kunoir said:
I have the same problem with my jasmine(which used to be wayne) when I tried to change it back into wayne again... do you have any solution already ?
Click to expand...
Click to collapse
have you find any solution?

jayspiker said:
have you find any solution?
Click to expand...
Click to collapse
i had the same problem but fixed with edl cable

Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
where can i find this chinese rom for MI A3

talhosvi said:
can not read from port com xy
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.
Click to expand...
Click to collapse
same problem with me . Have you solved it ?? let me know please

Hi Guys,
I have the same problem trying to flash MIUI 11 in mi A3 with MIUI 12. Anyone knows a solution for this?

Whyred Bricked Suddenly, ARB issue with ANTI 3???

Hi, i don't know what happened but i'll explain with details.
My Redmi note 5(global) was on the last miui.eu, his ANTI is 3.
Today i went to the street, used the Uber app and came back to home like always, as i can remember, the phone had 50% battery. A couple minutes later i was using the web whatsapp on PC and the software disconnected, at the first moment i didn't understood because the wifi was online, but when i took my RN5 he was turned off and didn't turned on anymore. I tried to power on the device and nothing, i put on USB and discovered the issue
QUECTEL QDLoader 900(COM6) : EDL?
I tried to use MiFlash and after trying flash the rom, i received : Cannot read hello packet
What?? My phone bricked like the ARB Issue even if my ANTI is 3????
He's dead and i don't know what to do, Xiaomi doesn't give the authorization anymore, someone could help me?

Use miflash beta and flash with arb3 fastboot rom

devcon69 said:
Use miflash beta and flash with arb3 fastboot rom
Click to expand...
Click to collapse
I used the last MiFlash, who needs the authorized Mi Account

first it should be in 9008 mode .. u need to trip edl points to make it in 9008/ edl mode as per my knowledge . check the link it may help
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932

I tried everything, my ID isn't authorized, just need this from Xiaomi :crying:

Maybe this will work for you. Read carefully
http://en.miui.com/thread-3450268-1-1.html

my xiaomi redmi note 5 does not turn on, I think it's in fullbrick

you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)

Modularkarma said:
you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)
Click to expand...
Click to collapse
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.

No
Incogn said:
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.
Click to expand...
Click to collapse
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl

Modularkarma said:
No
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl
Click to expand...
Click to collapse
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum

Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash several fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.

Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash roms fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.

Accidentally flashed to invalid file! Bricked phone! Help!

I accidentally did "fastboot flash preloader preloader.img" and now my phone won't boot, I can connect the cable and the phone led turns on and I get "sound of new device", however I can't do "fastboot devices or adb devices" nothing is found and after a bit the device disconnects from my PC.
What can I do to recover my phone? Please help I'm broke :crying::crying::crying::crying::crying:
Edit: the device is recognized as MediaTek USB Port, but SPFlashtool asks for permission, it has to be the authorized Xiaomi account that I need, I need this service please someone help me
Edit 2: Opened device, removed battery, tried to connect the test points, and no success SPFlashTool still requests authorization, and MiFlash does not recognize the phone at all (I think because it only works with fastboot?)

search in this RN8P thread some people got succeed after draining the battery

alejandromujica.rsm said:
I accidentally did "fastboot flash preloader preloader.img" and now my phone won't boot, I can connect the cable and the phone led turns on and I get "sound of new device", however I can't do "fastboot devices or adb devices" nothing is found and after a bit the device disconnects from my PC.
What can I do to recover my phone? Please help I'm broke :crying::crying::crying::crying::crying:
Edit: the device is recognized as MediaTek USB Port, but SPFlashtool asks for permission, it has to be the authorized Xiaomi account that I need, I need this service please someone help me
Edit 2: Opened device, removed battery, tried to connect the test points, and no success SPFlashTool still requests authorization, and MiFlash does not recognize the phone at all (I think because it only works with fastboot?)
Click to expand...
Click to collapse
you must drain the battery or disconnect and connect the battery

THE MAXIMUM POWER said:
search in this RN8P thread some people got succeed after draining the battery
Click to expand...
Click to collapse
I disconnected the battery and it doesn't work.

Read, read read

THE MAXIMUM POWER said:
Read, read read
Click to expand...
Click to collapse
I've read everywhere about every RN8Pro brick. I removed my phone case, disconnected battery, waited 10 seconds, connected again, pressed volume powers + and -, did everything I could and SPFlash everytime asks for authorization and I can't get fastboot screen.

I'm begging for someone to give me service for authorization so I can unbrick my device, I'm begging with my life on it, I suffer of depression and you've no idea how hard this is for me, I use my phone to work and I'm dying here of the anxiety since yesterday because I'm broke and can't get a new phone, all I can afford is the service, please, contact me

Bro just go to service center dnt panic

Shuvamilu said:
Bro just go to service center dnt panic
Click to expand...
Click to collapse
There is no service center in Venezuela.

You can do it remotely...

djzero86 said:
You can do it remotely...
Click to expand...
Click to collapse
How you need autorize I'd

Shuvamilu said:
How you need autorize I'd
Click to expand...
Click to collapse
Yes, someone with an authorized account can flash remotely your device, obviously this method require some money

djzero86 said:
Yes, someone with an authorized account can flash remotely your device, obviously this method require some money
Click to expand...
Click to collapse
I am contact a person he said you need ufi toll

The only way to solve your bootloop is a deep flashing, and for this you need an authorized account, search in YouTube or Google, XDA don't let people post numbers or contacts for business , is a rule..

alejandromujica.rsm said:
I accidentally did "fastboot flash preloader preloader.img" and now my phone won't boot, I can connect the cable and the phone led turns on and I get "sound of new device", however I can't do "fastboot devices or adb devices" nothing is found and after a bit the device disconnects from my PC.
What can I do to recover my phone? Please help I'm broke :crying::crying::crying::crying::crying:
Edit: the device is recognized as MediaTek USB Port, but SPFlashtool asks for permission, it has to be the authorized Xiaomi account that I need, I need this service please someone help me
Edit 2: Opened device, removed battery, tried to connect the test points, and no success SPFlashTool still requests authorization, and MiFlash does not recognize the phone at all (I think because it only works with fastboot?)
Click to expand...
Click to collapse
Send me emails [email protected]

alejandromujica.rsm said:
I'm begging for someone to give me service for authorization so I can unbrick my device, I'm begging with my life on it, I suffer of depression and you've no idea how hard this is for me, I use my phone to work and I'm dying here of the anxiety since yesterday because I'm broke and can't get a new phone, all I can afford is the service, please, contact me
Click to expand...
Click to collapse
I had same issue but i go to service centre and said that my phone was dead after updating (lie) after 1 hour they flashed my phone and no warrenty void.but keep in mind do not said about root if asking customer exicutive.

Hi - I'm sorry to 'hijack' this thread, but I have a quick question regarding bricking of devices. I've rooted my Note 8 Pro and it works nicely (I haven't restarted in a while). If I bricked it, would I know by now (as in, it would have been obvious when I was using fastboot and such)? Or upon restart, might there be an issue, if I use a new Magisk module or such? Thank you.

Question Help Needed, Poco f3 is in Edl mode after trying Installing custom rom

Hello, I am a poco f3 user and i've been using this phone for quite a while. till now i never had any problem installing or using custom rom. i was using cr droid and wanted to go for corvus os. after flashing corvus os through twrp my phone never rebooted and device manager showing qualcomm port 9008. after searching i found out i need patched firehose file for no auth flashing but couldn't find any file for poco f3. if anyone could help me with any solution then plz help me. i can't afford online servirces fees cause i'm broke af. so if anyone has any solution then plz help me

how did you manage to put it on QCOM mode? wrong custom rom flashed?

fireclouu said:
how did you manage to put it on QCOM mode? wrong custom rom flashed?
Click to expand...
Click to collapse
at first i was able to go into fastboot mood. then with miflash tool i tried to flash the firmwere but antirollback error given. then i left the phone in that fastboot mood for a while. some times after the screeen was black and i tried to boot into fastboot but nothing happened. so when i plugged it with pc the qcom port notification appered and after searching i found out that my phone was in edl mood

Zaman6234 said:
at first i was able to go into fastboot mood. then with miflash tool i tried to flash the firmwere but antirollback error given. then i left the phone in that fastboot mood for a while. some times after the screeen was black and i tried to boot into fastboot but nothing happened. so when i plugged it with pc the qcom port notification appered and after searching i found out that my phone was in edl mood
Click to expand...
Click to collapse
you can remove antirollback, just edit those checkpoints on notepad it will run fine, be sure to flash correct firmware corresponds to your version and release, mine's global so i choose global
but since your problem is now on edl, well... hmm no one but with authorized mi account can bypass miflash tool. either take it to xiaomi directly if it was covered with warranty hoping to get it fixed
dont fall to 25$ guys, sure yeah they hold the keys but thats soo much

fireclouu said:
you can remove antirollback, just edit those checkpoints on notepad it will run fine, be sure to flash correct firmware corresponds to your version and release, mine's global so i choose global
but since your problem is now on edl, well... hmm no one but with authorized mi account can bypass miflash tool. either take it to xiaomi directly if it was covered with warranty hoping to get it fixed
dont fall to 25$ guys, sure yeah they hold the keys but thats soo much
Click to expand...
Click to collapse
yea right but the thing is that mine was purchased from another country so here xiaomi won't take itas a warranty product. I was hoping ir I could find someone here who has the mi authorized account or tell me how to get one. if it costs me to pay only once for getting a permanent mi authorized account I will definitely go for that

Zaman6234 said:
yea right but the thing is that mine was purchased from another country so here xiaomi won't take itas a warranty product. I was hoping ir I could find someone here who has the mi authorized account or tell me how to get one. if it costs me to pay only once for getting a permanent mi authorized account I will definitely go for that
Click to expand...
Click to collapse
I think I've heard of ppl on telegram offering this.

Zaman6234 said:
Hello, I am a poco f3 user and i've been using this phone for quite a while. till now i never had any problem installing or using custom rom. i was using cr droid and wanted to go for corvus os. after flashing corvus os through twrp my phone never rebooted and device manager showing qualcomm port 9008. after searching i found out i need patched firehose file for no auth flashing but couldn't find any file for poco f3. if anyone could help me with any solution then plz help me. i can't afford online servirces fees cause i'm broke af. so if anyone has any solution then plz help me
Click to expand...
Click to collapse
did you try to flash stock firmware using any qcom toolin windows?

tutibreaker said:
did you try to flash stock firmware using any qcom toolin windows?
Click to expand...
Click to collapse
Hello, I have tried to flash with qfil but it gave an error mostly because of the mi authentication part of the firmware. I searched for some time and found out that I need a patched firehose file to bypass the edl authentication problem. But if U have any Solutions or suggestions then plz tell me. i will try to apply your method

Zaman6234 said:
yea right but the thing is that mine was purchased from another country so here xiaomi won't take itas a warranty product. I was hoping ir I could find someone here who has the mi authorized account or tell me how to get one. if it costs me to pay only once for getting a permanent mi authorized account I will definitely go for that
Click to expand...
Click to collapse
the thing is that you cant get authorized mi account, someone offers it remotely
surely xiaomi centers can help you with that, if youre paying those remote flashers I suggest you take it there hoping to assist you
or just wait for some exploits on miflash to arise but surely that takes time

Goofy ahh locked EDL mode. Sent you a contact person in dm lol

Zaman6234 said:
Hello, I have tried to flash with qfil but it gave an error mostly because of the mi authentication part of the firmware. I searched for some time and found out that I need a patched firehose file to bypass the edl authentication problem. But if U have any Solutions or suggestions then plz tell me. i will try to apply your method
Click to expand...
Click to collapse
I have the exact same problem as you. My F3 is only loading the QCOM port and not loading in to fastboot. Please can you tell what did you do to get it working?

symbiansucks said:
I have the exact same problem as you. My F3 is only loading the QCOM port and not loading in to fastboot. Please can you tell what did you do to get it working?
Click to expand...
Click to collapse
This is my understanding. You have 2 options:
Go to Xiaomi Service Center and let them repair it (worth trying/checking out, even if out-of-warranty I think!).
Or, contacting someone who's got an Authorised Xiaomi Account who'd be able to flash the ROM. That's what I did:
I contacted a group on Telegram, got in contact with the moderator. Paid 23€ over PayPal. Needed to wait a few hours for his technician to become available for me. I had to send him TeamViewer session credentials, so he can remote-connect to my PC. He was then available and connected to my PC. I had prepared with the latest MIUI Fastboot ROM and made sure my phone is connected and detected by Windows as a QCOM device. He downloaded some zipped piece of software, opened it, had to move out the TeamViewer session and came back and entered some kind of a Token into that program. He then used Mi Flash (I don't know if *my* Mi Flash, or from his downloaded zip-file), flashed the ROM and it worked.
Actually, during the flash in Mi Flash, my phone disconnected once, which was my fault though. He got a little annoyed, but he flashed it the second time and it worked.
It sounds very sketchy, but it's what I did, and it worked.

cyanGalaxy said:
This is my understanding. You have 2 options:
Go to Xiaomi Service Center and let them repair it (worth trying/checking out, even if out-of-warranty I think!).
Or, contacting someone who's got an Authorised Xiaomi Account who'd be able to flash the ROM. That's what I did:
I contacted a group on Telegram, got in contact with the moderator. Paid 23€ over PayPal. Needed to wait a few hours for his technician to become available for me. I had to send him TeamViewer session credentials, so he can remote-connect to my PC. He was then available and connected to my PC. I had prepared with the latest MIUI Fastboot ROM and made sure my phone is connected and detected by Windows as a QCOM device. He downloaded some zipped piece of software, opened it, had to move out the TeamViewer session and came back and entered some kind of a Token into that program. He then used Mi Flash (I don't know if *my* Mi Flash, or from his downloaded zip-file), flashed the ROM and it worked.
Actually, during the flash in Mi Flash, my phone disconnected once, which was my fault though. He got a little annoyed, but he flashed it the second time and it worked.
It sounds very sketchy, but it's what I did, and it worked.
Click to expand...
Click to collapse
You didnt have to open your phone and short the pins?

ApexPrime said:
You didnt have to open your phone and short the pins?
Click to expand...
Click to collapse
I did. My phone didn't auto-enter EDL Mode. I've heard that if the Qualcomm SOC detects that the bootloader can't be booted, it automatically alternates to the EDL Mode, which resides on the SOC itself, is read-only, and can't be erased.
Didn't happen for me. My suspicion is that my phone was able to boot into the BL, but couldn't load anything (Fastboot, Recovery, System..), and so it was stuck there instead of in EDL Mode.
I could've bought a Deep Flash Cable, but I didn't. I think I wanted an excuse to open up my phone "What could possibly go wrong?" =)