Related
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?
My phone is redmi note 5 pro. I flashed miuibeta 8.4 from beta 8.8 with twrp . I cleared system before reboot but not data. As i reboot,now my phone is stuck in edl mode. Wont got to fastboot,no logo,no vibrate,no led. Only miflash detect it. Butas flash got a failed to receive hello packet error. Can anyone help me out asap
If you werent that lazy and first tried reading forum or using search you would know, that to solve this problem you need to do is hold power button on phone for like 10s. Also, if you werent lazy and did research first, you would know that you have ARB brick, and in order to fix that you need authorized account.
Thank for the reply but i wouldn't have posted this if any of these methods works
Tens of people got hello packet error and every single one of them solved it by pressing and holding power button when required. Might also check if all your drivers are correct
Can it be flash from another authorized account other then the one on phone
Mikebsimte said:
Can it be flash from another authorized account other then the one on phone
Click to expand...
Click to collapse
Yes, as long as its authorized account. Authorized account can be used once for unbricking. If someone unbricked, and you use same account to unbrick another device, it wont work
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Redmi Note 8 Pro Hard Bricked
I'm in the same situation.
please help me
Hello,
The same thing happened to me when I installed the Orange FOX recovery, it didn't go into Fastboot mode, so I had to press the 3 buttons and wait for it to turn off completely, open the ADB control console and then connect it to the PC via USB by pressing the volume + button.
The latter I did on several occasions (Turn it off completely and connect by USB). Until I recognized it, when I recognized them, I had to flash the SYSTEM, CUST, RECOVERY. One by one, in total it took almost 5 minutes.
After that the phone started normal, obviously without root, nor custom recovery.
I'm also in the same situation as all of you, the PC doesn't recognize me and I can't go into fastboot
Hey,
I tried everything I could (battery connected/unplugged), my phone seems to have a corrupted preloader and only start the boot rom. That's why it shows up as "Mediatek USB PORT", if the preloader was'nt corrupted, it should be named "MediaTek PreLoader USB VCOM port" or something similar.
The only way to recover it imo is to flash a healthy preloader using SPFlashTool low level flash mode and next flash a full rom when "MediaTek PreLoader USB VCOM port" appears in the device manager.
Unfortunately, xiaomi ask for a certified account for low level flashing. I found one but the guy ask for 40$ for just logging it into my pc with teamviewer.
I buyed a Samsung Note10+ in replacement and i'll just wait someone find a solution to sell my 10-day-used redmi if I can revive it one day.
I got hundreds $ of Xiaomi home automation products in my home, but that was my first phone from this brand. I think it will also be the last.
I'm sad to see that their security policy on the phones is so frustrating to the people who just want to have a full acces on their devices.
Authorise can be done with professional tools
Tools like umt, hydra tool, miracle xiaomi tool, does the authorization. And i think mtk cpu Auth will only be available in miracle xiaomi tool, be aware every Auth cost credit of 4 to 10 u will have but credit separate from the tool.. Hope this will help
MOD EDIT: quote removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
girishjangir7 said:
MOD EDIT: name removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
Click to expand...
Click to collapse
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
djzero86 said:
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
Click to expand...
Click to collapse
It's against forum rules to post paid services
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
petenoni said:
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
Click to expand...
Click to collapse
I Also Had Adguard But I Was Still Not Satisfied
I Wanted My Phone To Be Rooted And Use The Custom ROMs If Build In Future.
Hemant Singh Rajput said:
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Click to expand...
Click to collapse
mine only take 3 hours at the service center in Jaipur
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
hi
does anyone find a solution for this?
please help
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
JuanM2020 said:
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
Click to expand...
Click to collapse
doesn't work
samadsaba said:
doesn't work
Click to expand...
Click to collapse
This is only for unbricked devices.... As I stated. If your device was already bricked it won't help you.
I also faced this problem... I used paid service to unbrick it... I must pay 35USD for the service.. but just wait.. If it works I will post here again. I bricked my phone when flashed anti brick on Android 10.. I forgot downgrade it to Android 9
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?" =)
Ok, I might have ****ed this up really bad this time, I have flashed custom roms on my old device many times and once before on my Poco F3, so I was a bit over confident trying to flash the Elite ROM miui 14 following this not very detailed guide using orange fox:
EliteRomLite V14.0.22.12.8.DEV China DEV MIUI 14 A13 Released for PUBLIC!
Devices: Poco F3 / K40/...
www.elitedevelopment.com.pk
after formatting and flashing everything I tried to reboot ignoring the "no OS" warning (Big mistake). And now my phone doesn't boot, neither to the (non existing) OS neither to the fast boot screen.
If anyone can help I would be immensely grateful
Bata123 said:
Ok, I might have ****ed this up really bad this time, I have flashed custom roms on my old device many times and once before on my Poco F3, so I was a bit over confident trying to flash the Elite ROM miui 14 following this not very detailed guide using orange fox:
EliteRomLite V14.0.22.12.8.DEV China DEV MIUI 14 A13 Released for PUBLIC!
Devices: Poco F3 / K40/...
www.elitedevelopment.com.pk
after formatting and flashing everything I tried to reboot ignoring the "no OS" warning (Big mistake). And now my phone doesn't boot, neither to the (non existing) OS neither to the fast boot screen.
If anyone can help I would be immensely grateful
Click to expand...
Click to collapse
does it not boot to twrp?
Bata123 said:
Ok, I might have ****ed this up really bad this time, I have flashed custom roms on my old device many times and once before on my Poco F3, so I was a bit over confident trying to flash the Elite ROM miui 14 following this not very detailed guide using orange fox:
EliteRomLite V14.0.22.12.8.DEV China DEV MIUI 14 A13 Released for PUBLIC!
Devices: Poco F3 / K40/...
www.elitedevelopment.com.pk
after formatting and flashing everything I tried to reboot ignoring the "no OS" warning (Big mistake). And now my phone doesn't boot, neither to the (non existing) OS neither to the fast boot screen.
If anyone can help I would be immensely grateful
Click to expand...
Click to collapse
Hi, As 3zozHashim mentioned,
do you still have RECOVERY, i have been stuck in "No O/S installed" but after reboot has always automatically rebooted into Recovery.
You can enter Recovery manually by pressing and holding the Power + Volume up buttons and releasing the power button.
I have never lost FASTBOOT, if you still have recovery you could try reverting back to your old rom, can you connect to your pc.
I had this issue once and I've solved in TWRP (hope you may accessit!).
Try to reboot, from main screen, and switch to the other partition (if you don't know which one is the actually active, try first with B and after a failing reboot try with A)
no matter if I hold power button, or power + volume up, or power+ volume down the screen just stays black
You need to flash miui using an authorized account by paying someone with one of these accounts.
Where I can found someone with one of these accounts?
Since your phone appears to be hard bricked, you could try a patched firehose and flash a firmware yourself. I will link it if you want. Just a disclaimer, try it at your own risk since yours is the first hard bricked device I came across since I got the firehose file.
user0u said:
Since your phone appears to be hard bricked, you could try a patched firehose and flash a firmware yourself. I will link it if you want. Just a disclaimer, try it at your own risk since yours is the first hard bricked device I came across since I got the firehose file.
Click to expand...
Click to collapse
I would really enjoy if could link me the patched firehose
Bata123 said:
I would really enjoy if could link me the patched firehose
Click to expand...
Click to collapse
Here you go.
I do not know how to use it though. Maybe @cyanGalaxy can guide you through it?
EDIT: I tried it and it looks like it does not work.
user0u said:
Here you go.
I do not know how to use it though. Maybe @cyanGalaxy can guide you through it?
Click to expand...
Click to collapse
I've found tutorials on the internet using miflash but I only get errors
Bata123 said:
I've found tutorials on the internet using miflash but I only get errors
Click to expand...
Click to collapse
I don't think it can be used with miflash. You need something like QFIL.
Bata123 said:
I've found tutorials on the internet using miflash but I only get errors
Click to expand...
Click to collapse
Hi,
Was your F3 recognised in Device manager, if so was it listed as Qualcomm HS-USB QDLoader 9008 , also have you tried to hold down the power button for 10 seconds
user0u said:
I don't think it can be used with miflash. You need something like QFIL.
Click to expand...
Click to collapse
I had to use Qfil to install Orangerfox patched Recovery on my LG G7 "many times"
Entering 9008 mode was easy thou, i was done by using a combination of keys at reboot, it looks like MIUI is a different beast.
I was tring qfil this afternoon but I got a bunch of errors, some I found how to fix online (like sahara fail and "The system cannot find the specified file") but not the "FHLoader Fail: Process Fail." tried a bunch of Qfil versions and nothing unfortunately. Apperntly I will have to pay someone on a service center to fix it
Bata123 said:
I was tring qfil this afternoon but I got a bunch of errors, some I found how to fix online (like sahara fail and "The system cannot find the specified file") but not the "FHLoader Fail: Process Fail." tried a bunch of Qfil versions and nothing unfortunately. Apperntly I will have to pay someone on a service center to fix it
Click to expand...
Click to collapse
Sorry to hear that. Well, it was worth a try at least.
I wonder what that error means. Does it mean the patched firehose is not working or something else. Hmmm...
Also I read that you need to set "device type" to ufs in configuration. This is essential.
user0u said:
Sorry to hear that. Well, it was worth a try at least.
I wonder what that error means. Does it mean the patched firehose is not working or something else. Hmmm...
Also I read that you need to set "device type" to ufs in configuration. This is essential.
Click to expand...
Click to collapse
This guy has the same problem as you. I don't know if the video doesn't work for you, but it's not hard to try.
vickmen said:
This guy has the same problem as you. I don't know if the video doesn't work for you, but it's not hard to try.
Click to expand...
Click to collapse
This only works with MediaTek phones.
Bata123 said:
I was tring qfil this afternoon but I got a bunch of errors, some I found how to fix online (like sahara fail and "The system cannot find the specified file") but not the "FHLoader Fail: Process Fail." tried a bunch of Qfil versions and nothing unfortunately. Apperntly I will have to pay someone on a service center to fix it
Click to expand...
Click to collapse
Does your phone show up in Windows Device Manager as "Qualcomm 9008" ?
The EDL Mode of the Xiaomi Poco F3 is locked to authorised Xiaomi Service Centres only...
The Poco F3 modified MBN (Firehose) file that the other guy here posted, *may* work, to circumvent the authorisation required. I haven't tried it myself because my phone's not bricked at the moment
I did brick my Poco F3 once last year, tried QPST/QFIL. I couldn't find *any* modified Firehose back then so QPST/QFIL didn't work. {Mod edit. Oswald Boelcke}
Another thing to mention, my phone did not go into EDL Mode automatically, I had to open the back of my phone (took a lot of patience and carefulness but was flawless!), and short 2 Test-points on my phone.
In the end it all worked out well for me.
The Qualcomm SOC, when it detects that the bootloader is completely f***ed, will boot into EDL Mode instead. When you power on your device, the Qualcomm SOC first tries to boot Android's Bootloader, if it detects that the bootloader is erased (or similar), it will sidetrack to the Qualcomm read-only EDL Mode.
But there are times where it's not erased but only broken/damaged, and in that case the Qualcomm SOC doesn't auto-boot to EDL Mode, but instead, you're "invisibly" stuck in a broken/damaged Android bootloader.
About the modified Firehose file and QPST/QFIL: You have to put it into the Fastboot ROM-folder where the other ROM images are... The Official MIUI Fastboot ROM can also be used for EDL Mode (QPST/QFIL/Mi Flash)...
I think you CAN actually use Mi Flash for EDL Mode. What happens when you try to flash in EDL Mode, by default, is that a popup will show asking you to login with a Xiaomi Service Account (which of course you don't have).
So.. you can try Mi Flash with the Modified Firehose, or QPST/QFIL...
Otherwise I can give you contact details about the third party service that would flash your phone in EDL Mode (the same that I used last year).
I can not mention it here on XDA tho... Guidelines.
Or, if it costs less to go to a Xiaomi Service Centre (or sending it in), then do that. Maybe you can, with warranty.
Here in Germany I think there are very very few Xiaomi Service Centres, and we have to send in, I think...
OK I have to plead guilty to something...
I bricked my Poco F3 twice actually.
But the very first time when it happened (2 months after I bought the device hahah), I had no clue about Qualcomm EDL Mode and the other technicalities related to Xiaomi and Qualcomm, so I returned it to Amazon and said "Software borked due to OS update", and they sent me a free replacement.
It was a bad move of course, but I was without a phone and had nightmares from that occurence. The second time I made my hands dirty (so to speak ;D ), and I fixed it!