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?

Hard-Bricked Redmi Note 8 Pro after MIUI 11 Update

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

Question Soft Bricked T-Mobile OnePlus 9 Pro

So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?

I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...

I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck

Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !

For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.

I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.

razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message

KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.

Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool

This was fixed via MSM. But I had another issue come up where MSM doesn't work.

Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?

its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.

Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).

ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that

Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.

ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...

ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.

Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?

ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.

Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).

Question LineageOS Bootloop within 1 second

Hi Guys,
Oneplus 9 Pro
I installed LineageOS 19.1 and Gapps and all worked fine. The phone booted up and entered setup. I skipped setting it up as I wanted to relock the bootloader so I could use Google Pay.
After rebooting into fastboot, I typed in "fastboot oem lock" and now I'm in an infinite loop. Phone starts up for 1/2 a second I see the startup flash for a split second and then it reboots.
I cant enter fastboot mode or recovery and holding down vol up or down does nothing along with holding power button. The phone literally stays on for 0.5 secs...
Please help

..

hidara said:
Hi Guys,
Oneplus 9 Pro
I installed LineageOS 19.1 and Gapps and all worked fine. The phone booted up and entered setup. I skipped setting it up as I wanted to relock the bootloader so I could use Google Pay.
After rebooting into fastboot, I typed in "fastboot oem lock" and now I'm in an infinite loop. Phone starts up for 1/2 a second I see the startup flash for a split second and then it reboots.
I cant enter fastboot mode or recovery and holding down vol up or down does nothing along with holding power button. The phone literally stays on for 0.5 secs...
Please help
Click to expand...
Click to collapse
You cant relock bootloader on a custom rom unless stated so.the only option you have is to try and get it into edl mode and msm back to stock

gillim74 said:
You cant relock bootloader on a custom rom unless stated so.the only option you have is to try and get it into edl mode and msm back to stock
Click to expand...
Click to collapse
Thank you. Just managed to get into fastboot by holding both vol up and down at the same time. Reflashing now. I hear of people relocking the bootloader after installing LineageOS. Is there any way to do this. All I really want is google pay
Cheers for the help

hidara said:
Thank you. Just managed to get into fastboot by holding both vol up and down at the same time. Reflashing now. I hear of people relocking the bootloader after installing LineageOS. Is there any way to do this. All I really want is google pay
Cheers for the help
Click to expand...
Click to collapse
If you want Google Pay, locking bootloader won't help you.
Set your fingerprint to an A11 print with props config, install Universal SafetyNet fix, and clear data on play services. Easy.

Umgak said:
If you want Google Pay, locking bootloader won't help you.
Set your fingerprint to an A11 print with props config, install Universal SafetyNet fix, and clear data on play services. Easy.
Click to expand...
Click to collapse
Appreciated though my phone is now a paperweight . No fastboot etc. Just a blank screen. Qualcomm driver detected when I plug it in but MSM tool fails ;(

From my understanding you should never re-lock your bootloader unless you're on stock, with no modifications flashed, unless you want to deal with a bricked phone. MSM is your only hope. When you open the MSM tool you need to put your phone in EDL Mode you have connect it to the MSM tool quickly, is that the issue? If you have the Qualcomm driver detected then, maybe you're missing a vital step?

hidara said:
Appreciated though my phone is now a paperweight . No fastboot etc. Just a blank screen. Qualcomm driver detected when I plug it in but MSM tool fails ;(
Click to expand...
Click to collapse
This isn't very descriptive. MSM Tool is fussy, you have to use the right combo of settings and you have to be quick about it.
Open the MSM Tool, check use lite firehose, click Start so it's already looking for the phone, press and hold both volume buttons and while doing so connect the cable.
If it gives you device not match image error, try to uncheck Sha256 check too and if that doesn't work, download the Indian variant MSM and try that.
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If that works, you then need to flash the appropriate downgrade package to get back on the right software for your model. Unlock the bootloader and use the local update tool and flash the downgrade package from your model from here - https://forum.xda-developers.com/t/oneplus-9-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254587/
If your phone can go into EDL, it should be able to be recovered, it just is the matter of finding the right combination.

EtherealRemnant said:
This isn't very descriptive. MSM Tool is fussy, you have to use the right combo of settings and you have to be quick about it.
Open the MSM Tool, check use lite firehose, click Start so it's already looking for the phone, press and hold both volume buttons and while doing so connect the cable.
If it gives you device not match image error, try to uncheck Sha256 check in too and if that doesn't work, download the Indian variant MSM and try that. PL
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If that works, you then need to flash the appropriate downgrade package to get back on the right software for your model. Unlock the bootloader and use the local update tool and flash the downgrade package from your model from here - https://forum.xda-developers.com/t/oneplus-9-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254587/
If your phone can go into EDL, it should be able to be recovered, it just is the matter of finding the right combination.
Click to expand...
Click to collapse
Thanks for the advice. Not sure if it's having the Chinese version is the issue but heres what I tried.
Tried the EU and global version of MSM.
With stock settings I get
"Sahara communication failed"
With lite firehouse checked I get "incorrect image ......" With and without SHA.. checked. Tried to download the Indian rom but got an anti-virus message (had these with Linux based PC/Android images before so we going to revisit)
This is where I was at when I posted the paperweight message above and had spent the day on it, not a great idea when you're in the middle of Uni exams
Will revisit the Indian rom though. Thanks for the advice again

hidara said:
Thanks for the advice. Not sure if it's having the Chinese version is the issue but heres what I tried.
Tried the EU and global version of MSM.
With stock settings I get
"Sahara communication failed"
With lite firehouse checked I get "incorrect image ......" With and without SHA.. checked. Tried to download the Indian rom but got an anti-virus message (had these with Linux based PC/Android images before so we going to revisit)
This is where I was at when I posted the paperweight message above and had spent the day on it, not a great idea when you're in the middle of Uni exams
Will revisit the Indian rom though. Thanks for the advice again
Click to expand...
Click to collapse
The Indian MSM Tool doesn't seem to actually run those checks to make sure the device firmware matches for some reason. I have used it on my regular 9 to recover it when none of the other MSM Tools would work.
Disable your antivirus before running MSM Tool as it can trigger false positives. None of these files are infected though. They all trigger multiple false positives but the EXE is the same across all of them.
VirusTotal
VirusTotal
www.virustotal.com

EtherealRemnant said:
The Indian MSM Tool doesn't seem to actually run those checks to make sure the device firmware matches for some reason. I have used it on my regular 9 to recover it when none of the other MSM Tools would work.
Disable your antivirus before running MSM Tool as it can trigger false positives. None of these files are infected though. They all trigger multiple false positives but the EXE is the same across all of them.
VirusTotal
VirusTotal
www.virustotal.com
Click to expand...
Click to collapse
Wooohoooo I'm back. Thank you

hidara said:
Wooohoooo I'm back. Thank you
Click to expand...
Click to collapse
Glad that you got it all sorted out!

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?" =)