Database Info

Stuck at logo/Bootloop with locked bootloader

My Redmi Note 6 Pro Global version just rebooted itself out of nowhere and now its showing MI logo and rebooting every 3-5 seconds. I didn't unlock bootloader and had MIUI 10 latest stable version installed. I can still enter fastboot mode. What can I do to fix this?

UPDATE
Over the last few days, these are the things that I've tried:
I can enter Fastboot mode and connect to my PC, but can't enter recovery mode.
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
I tried flashing fastboot rom with MiFlash, but when MiFlash causes phone to reboot towards the end of flashing, the bootlooping problem occurs again and it cannot complete flashing.
I also tried flashing TWRP from fastboot, it says that it's successful, but when I try fastboot boot twrp.img, the same problem: MI logo and constant reboots.
I also tried to use fastboot oem edl mode and my phone is recognized as Qualcomm device, but MiFlash can't flash in this mode, saying that hello packet is not received.
At this point, I don't know what else to do and wondering if this is a hardware problem. Any ideas?

Did you tried to press VOL UP + POWER BUTTON after you flash TWRP? If flashing TWRP doesn't work Try to flash Official MIUI RECOVERY 3.0 That's all you can do. Otherwise you should give it to Mi customer service for faster solution.

I have the same problem, did you manage to solve this issue?

hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.

MI stuck at boot logo
m1s3rys1gn4l said:
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
Click to expand...
Click to collapse
Hello all ! same problem here !
i reinstall the last version in EDL mode every week !!
I can not handle it anymore !
sometime he match 1 day sometime 3 week ... everytime he stuck on menu and i can't reboot .
the only version i can use its 10.3.2 global ... all other version don't match !
Sorry for my english (i'm french) and thanx you for your help

hi my redmi note 6 pro is stuck on mi logo its not getting over it .
i dont have any pc or laptop at my home how can i solve this issue
during this lockdown ,and now its showing charging in shutdown mode?

Hello All i have the same problem stuck on MI logo
I have tried to wipe through Mi recovery but no use
I cant flash anything because the bootloader is locked
and i dont want to use EDL mode cuz i am stuck at home and dont have necessary tools for that
My question is can we flash anything using Fastboot command or can we ON usb debugging through fastboot be cause Mi flash wont work until USB debugging in On
Please help

Try another flash tool i.e. Qfil_flash_tool

Hi, I have even tried EDL mode to flash latest rom (android 9,miui11.0.4) using Mi flash tool,still facing the same issue.
It constantly reboots while on charging, and it doesn't turn on otherwise(2 Sec of that logo and then it fades away).
Please Help

any one find solution for this?

Hi, my problem is simpler, so is there any suggestion.
after last official update, due to the internal partition was encrypted, update wasn't finished and I am stuck on MI logo when restarted the phone.
bootloader is unlocked and I can enter to (orangefox) recovery, yet I am not sure what is the best way just to return phone to the bootable state? I presume some wiping is to be done, which is not the problem, just to have as short procedure as possible, preferably without need to re-flash clean ROM from recovery?
regards

mertcanekiz said:
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
Click to expand...
Click to collapse
Hi, i'm in the same situation as you. How did you solve it? with the miunlock app I can't unlock it because it tells me that I have to select something on the phone first, but if the phone doesn't start I can't select anything ..

Try to remove hardware buttons from board and try

redmi 6 pro (bootloader locked)
same problem...
tried methods :
1) using mi flah tool ( error occurred : )
2) edl method (showing: device is locked)
........still stuck on miui logo .........

Redmi 6 Dead Brick ( Black Screen + Continuous Vibration Only )

i have recently flashed a wrong twrp recovery with a cmd program file in my redmi 6 that caused the phone to be dead with black screen and vibration only. i have no access to fastboot mode neither twrp recovery
i followed a method of using SPflashtools for flashing the stock rom in redmi 6 but it gives me a brom cmd error 0xC0060005 everytime i try to do it
the only thing i haven't done is to remove the battery and then accessing the fastboot mode bcz its back is fixed and it requires a professional skillset to open it that can only be done by the phone repairers
so i am looking for a solution before going to the repair center if you can help me with that i would be very grateful to you
Thanks !

Giving so few information makes it almost impossible to help you... First of all which TWRP did you flash?

I had the same Error. I opened the phone. Removed 3 screws and the schield. Then you can disconnect the Battery. When you connect the battery while pressing Volume down you will get into the fastboot mode. I only needed to flash the recovery twrp again.
Good luck.

Mar_5 said:
I had the same Error. I opened the phone. Removed 3 screws and the schield. Then you can disconnect the Battery. When you connect the battery while pressing Volume down you will get into the fastboot mode. I only needed to flash the recovery twrp again.
Good luck.
Click to expand...
Click to collapse
Does your phone have display visuals or entered in fastboot with that black screen ?

redmi6 vibration only
DesignerAQ17 said:
i have recently flashed a wrong twrp recovery with a cmd program file in my redmi 6 that caused the phone to be dead with black screen and vibration only. i have no access to fastboot mode neither twrp recovery
i followed a method of using SPflashtools for flashing the stock rom in redmi 6 but it gives me a brom cmd error 0xC0060005 everytime i try to do it
the only thing i haven't done is to remove the battery and then accessing the fastboot mode bcz its back is fixed and it requires a professional skillset to open it that can only be done by the phone repairers
so i am looking for a solution before going to the repair center if you can help me with that i would be very grateful to you
Thanks !
Click to expand...
Click to collapse
has no repair, need to change the motherboard

This just need to flash with spflashtool+mtk driver+MCT mtk+python+fastboot rom.
Don't replace emmc, your emmc is good

Because your phone still vibrate

Brom cmd error 0x0006005 = need bypass with MCT mtk, and python to solve this problem

xame problem..
for my xiaomi redmi 6

HELP :: I bricked my Mi MIX 2S installing a Magisk Module of another phone (K20pro)

Please mods, I dont know if this post is in the correct forum. I'm exhausted after being hours trying to solve this issue and here is 2am. Feel free to move the thread wherever you think it suits better.
I posted the same message here: https://forum.xda-developers.com/k2...9t-pro-one-t4093255/post83029067#post83029067
I think that maybe this Mi MIX 2S forum is more suitable for asking for some help. This is the original message:
Yes I did. I feel like an ashole... The module is not for the MI MIX 2S, but I thought (yes, I told you, I'm an ashole, that being Magisk, it could be universal. For all smartphones with Magisk)
Is my fault, I know. I come here to beg for your help.
I had my Xiamo Mi MIX 2S with the last Xiaomi EU rom with MIUI 12, rooted with Magisk. Everything worked flawlessly.
Then I say that fantastic module: Screen Overclock. I thought, fantastic! I could have a lower refresh rate and that way save some battery... I did... And now I'm stuck in Fastboot.
I installed the latest official room with MiFlash following this tutorial: https://c.mi.com/oc/miuidownload/detail?guide=2
I even downloaded the last room from there (Global) as it says is the latest.
The biggest outcome is to boot into the official recovery. I tried to install TWRP and it install (fastboot flash recovery twrp-3.3.1-0-polaris.img ---> version 3.4 doesn't work either) but after that, I can't reboot into recovery. It comes back to Fastboot again.
Trying to boot the recovery with fastboot boot twrp-3.3.1-0-polaris.img throws the following error:
PHP:
Sending 'boot.img' (42476 KB) OKAY [ 1.219s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
So I don't know what to do, and I do really need your help please.
I'll post this same message in the Mi MIX 2S board. Hopefully somebody who could imagine what went on, can give a helping hand.
Please help
Thank you all
Manu

So know is even worse.
For a reason I don't know, now I'm able to load adb sideload (pcsuite) but when entering in fastboot, inmediatly I can see a very small letters in the top left corner that say: "Press any key to shutdown"
Solved connecting the MI MIX 2S to a USB2 port rather than a USB3. Weird... At least I have again access to Fastboot

I dont think this have any solution. I managed to install via XiaomiADB sideload to the 99%
And at 99%... it stopped:
C:\Users\manu\Downloads\XiaomiADB>XiaomiADB.exe miui_MIMIX2SGlobal_V11.0.5.0.QDGMIXM_42f0653956_10.0.zip
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~99%)
* Sideload output: *
ERROR: Sideload error -> Unknown error during file installation
Installation FAILED!, press ENTER to exit
So I'll try to see tomorrow if you guys can help, but I don't see any option here...
Well, at least connecting it to a USB2 port seems that I Can, again, to fastboot without the small "Press any key to shutdown" message

So another question.
A guy in the other thread told me this:
kiran8631 said:
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Click to expand...
Click to collapse
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?

manudas said:
So another question.
A guy in the other thread told me this:
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?
Click to expand...
Click to collapse
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work

kiran8631 said:
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work
Click to expand...
Click to collapse
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway

Take it to service center

manudas said:
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway
Click to expand...
Click to collapse
If you get fastboot working again I can give you mix2s vbmeta

cvamoose said:
If you get fastboot working again I can give you mix2s vbmeta
Click to expand...
Click to collapse
Thank you, but the only reaction of the phone when I press any combination of buttons is to blink the led a couple of times. So I don't think that now it could be sorted out. Anyway, why don't you attach it here so if anybody in the future needs it, don't download the wrong one?

Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working

reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Even if he got into edl mode he cant flash anything unless he has an authorized account. Also to get into edl at his current state the back of phone must come off and certain spots need to be shorted.

reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?

You have to press vol- and vol+ at once and connect USB cable.
If it doesn't work I believe that test points should work. To do that you need to remove back cover then short two test points that are below camera using for instance scissors with small ends (this may help https://www.youtube.com/watch?v=koj3cGnhic0) and having both points connected with each other connect USB cable.

manudas said:
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?
Click to expand...
Click to collapse
If you access edl mode contact me with a private message

F2 Pro completely stuck

Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...

Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked

Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....

My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.

Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)

Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...

i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse

I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works

Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer

Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.

Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.

You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards

Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop

As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?

Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back

Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?

ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?

NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode

ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?

My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file

Unable to flash any recovery

Hi,
After updating my OnePlus Nord (EU) to OxygenOS 12 and noticing how full of bugs it is, I've decided to flash PixelExperience on it.
I followed the official PixelExperience install guide: I successfully unlocked my bootloader, and then went ahead to flash the recovery.
Exactly as written in the guide, I performed a fastboot flash recovery recovery.img.
The command finished as expected without any errors, so I rebooted into the recovery with fastboot reboot recovery, only to get an error screen, with a title in Chinese and an error message: "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.", so my device got soft-bricked.
I tried flashing it again - didn't work.
So I tried flashing TWRP - also didn't work.
I tried to flash a stock recovery from this thread - also didn't work.
I at least tried to recover it back to stock, so I downloaded the MSM tool and Qualcomm drivers and tried to get my device into Qualcomm EDL mode.
I tried many combinations of button pressings, I tried fastboot oem edl, but I just couldn't get it into EDL mode, it just booted into fastboot every time.
How could I fix this - flashing a recovery or at least revert it back to stock?

Bro, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works

krish-ag said:
Oo, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works
Click to expand...
Click to collapse
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?

AmitGold said:
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?
Click to expand...
Click to collapse
In edl mode, u will not see anything on the phone screen.
To use edl mode, press vol up and down simultaneously (without power botton) for 10 secs and then connect it to pc via usb cable
Then u will hv to use the MSM tool according to ur nation (like India, EU etc) for a specific OOS version

Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times

AmitGold said:
Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times
Click to expand...
Click to collapse
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..

krish-ag said:
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..
Click to expand...
Click to collapse
Tried that also... Didn't work

AmitGold said:
Tried that also... Didn't work
Click to expand...
Click to collapse
did it just reboot or boot into bootloader again?
Also can u share a recorded video of the process i hv told u?

It booted into the bootloader.
Attaching a video of this process

Bro first thing, it should be of 10 secs not 30. I m pretty sure that's what preventing to to boot to edl
Second, i want a video of those adb method steps that i told u but now first try ur method only but for 10 secs

AmitGold said:
It booted into the bootloader.
Attaching a video of this process
Click to expand...
Click to collapse
I have the same issue, did you fix that?

Use a USB2 port if not already obvious. (I fought getting into EDL mode for hours the first time - maybe you already know this, sorry if redundant. 10 seconds, 40 seconds, doesn't matter, adl, fastboot, key presses - everyone focuses on the that. Finally with red cable and USB-2 port, it works easily.)