Database Info

Xiaomi Hard Brick, Can't enter Fastboot mode

Hi,
I flashed a wrong boot.img via fastboot, and done reboot.
Now the phone stuck in bootloop with no screen at all. no mi logo, just black screen (vibrate when it try to boot).
- Phone is Xiaomi Redmi 6, battery is not removable.
- Can't enter to fastboot mode (not either to TWRP recovery).
- Can't even turn the phone off (tried with pow + vol-up + vol-down, but didn't work).
- PC not recognize the phone (included miFlash and spFlashtool).
I have an unlocked bootloader if it make any different to this situation.
Please help :crying:
Thanks.
If need more details I would like to give it.

nikai said:
Hi,
I flashed a wrong boot.img via fastboot, and done reboot.
Now the phone stuck in bootloop with no screen at all. no mi logo, just black screen (vibrate when it try to boot).
- Phone is Xiaomi Redmi 6, battery is not removable.
- Can't enter to fastboot mode (not either to TWRP recovery).
- Can't even turn the phone off (tried with pow + vol-up + vol-down, but didn't work).
- PC not recognize the phone (included miFlash and spFlashtool).
I have an unlocked bootloader if it make any different to this situation.
Please help :crying:
Thanks.
If need more details I would like to give it.
Click to expand...
Click to collapse
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.

mrmazak said:
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.
Click to expand...
Click to collapse
Thanks, but I'm get the same error, STATUS_BROM_CMD_FAIL (0xC0060005)

same problem with me..haha :laugh:

folow these steps
the only way you flash your phone is by installing mtk (mediatek) drivers.
if you are using windows 10. Disable Driver Signature Enforcement
download MRT_V3.26
there you have MTK_driver.exe install it. than open folder MTK_CDC_Driver_for_imei right click on Android_Gadget_CDC_driver and install.
download Xiaomi_Flash_20181115.zip
and stable global fastboot rom V10.3.3.0.OCGMIXM
extract it
run mi flash and choose extracted folder, click refresh than flash.
THIS IS 100% TESTED by me.

mrmazak said:
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.
Click to expand...
Click to collapse
Where can i get scatter file from?
edit: nevermind, found it, tried to flash boot.img but it never did anything

same
i have the same problem but with a redmi 6A, its stuck on a bootloop with the "the system has been destroyed" screen and unable to boot into fastboot, i alredy tried setting up sp flash and connecting the device pressing the vol+ button, but i always get the "STATUS_BROM_CMD_FAIL (0xC0060005)" error and i cant find anything about it.

https://forum.xda-developers.com/re...rick-stuck-da-mode-authorised-t4000433/page24 try this and let me know if its working for you guys also

samusamu2304 said:
Deleted
Click to expand...
Click to collapse

Pradeep1998 said:
https://forum.xda-developers.com/re...rick-stuck-da-mode-authorised-t4000433/page24 try this and let me know if its working for you guys also
Click to expand...
Click to collapse
The workaround doesn't support MT6762, which is the processor in the R6, sadly.

Immortal68 said:
The workaround doesn't support MT6762, which is the processor in the R6, sadly.
Click to expand...
Click to collapse
MT6765 supported and in Redmi 6

I Have A Problem That My Redmi Note 9 Is Struck On BootLoop It's Not Entering Recovery And Fastboot Mode Also It's Just Showing Redmi Logo Only How To Fix It Any One Help Me Plzzz....

BTS Arm said:
I Have A Problem That My Redmi Note 9 Is Struck On BootLoop It's Not Entering Recovery And Fastboot Mode Also It's Just Showing Redmi Logo Only How To Fix It Any One Help Me Plzzz....
Click to expand...
Click to collapse
Same problem here. I think I just got myself a brand new brick (Redmi k50)!
@BTS Arm, were you able to overcome this problem?

jholiveira said:
Same problem here. I think I just got myself a brand new brick (Redmi k50)!
@BTS Arm, were you able to overcome this problem?
Click to expand...
Click to collapse
Same problem, I'm trying right now with MiFlash as suggested by Tommy0412. The program detects the device and is in "flashing" from 500s to this moment. I'll let you know if it's working
Edit: Finished with "error: flash timout". I'm trying again, this time with very less hope. By the way my phone is a Redmi 9A (dandelion)
Edit 2: I fixed the problem without flashing (almost) anything. I used the Xiaomi ADB/Fastboot Tool (a simple .jar file) that allowed me to reboot in fastboot mode without doing anything strange. Then I flashed the correct recovery and everything is now back to normal. Thanks to whoever developed that java application. That saved my ass!

GiZeta said:
Same problem, I'm trying right now with MiFlash as suggested by Tommy0412. The program detects the device and is in "flashing" from 500s to this moment. I'll let you know if it's working
Edit: Finished with "error: flash timout". I'm trying again, this time with very less hope. By the way my phone is a Redmi 9A (dandelion)
Edit 2: I fixed the problem without flashing (almost) anything. I used the Xiaomi ADB/Fastboot Tool (a simple .jar file) that allowed me to reboot in fastboot mode without doing anything strange. Then I flashed the correct recovery and everything is now back to normal. Thanks to whoever developed that java application. That saved my ass!
Click to expand...
Click to collapse
Unfortunately, I no longer have access to recovery or fastboot. The phone is stuck in a loop and no longer offers those options. I need a tool that can recover it in BROM mode.

jholiveira said:
Unfortunately, I no longer have access to recovery or fastboot. The phone is stuck in a loop and no longer offers those options. I need a tool that can recover it in BROM mode.
Click to expand...
Click to collapse
If it keeps restarting, this may not help at all, but I'll leave the tool here for you (or whomever may need it) to maybe give it a try.
Hope you can recover it somehow, good luck and have a nice day

Yuhuu!
Try this up guys:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com

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

Xiaomi Redmi Note 4 (Snapdragon) flashing problem.

Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..

Can you boot up normally?
If not what happens, when you try?

gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.

Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician

Just bricked

Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?

BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model

CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).

BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me

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.)