Database Info

Stuck in EDL mode locked bootloader any way to flah rom?

Never unlocked or flashed a custom rom on my device since I got it a few years back so its always been on stock.
My phont turned off one night while I was using it aand sicne its been stuck in EDL mode.
Black screen won't boot etc.
Device Manager shows Qualcomm HD-USB QDLoader 9008
I tried diffrent roms and diffrent Mi Flash tools wioth no luck.
In the latest Mi flash I cant flash because of authorisation.
In previous versions I get Waiting for hello packet and Object referance not set to instance of object.
I tried the diffrent firehose files from online.
I am going to try Xiaomi.eu rom and see what happens.
But anyone had this before and can help me get the phone back up and running?

I had a custom ROM installed. One night I just typed "fastboot oem lock" without giving it much of a thought. Than, of course, the phone was bricked. It wouldn't boot and gave the error "The system was deleted" or something like this and since the bootloader was locked and all MiFlash couldn't flash.
The solution was simple. I just used Mi Unlock and it worked. The bootloader was unlocked again. I didn't think it would work.

relock bootloader but no OS help please

hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz

in case anyone has the same problem.
i did solve it by flashing the (raw) firmware via fastboot ( Flash_AFT method )

M-772007 said:
hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz
Click to expand...
Click to collapse
There are new guides on how to get volte if you want to try again.
[Guide] Easy method to Enable Volte (with root) on Tmobile and maybe other networks on Android 11 and maybe 10
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around. Then once you do that, follow these directions, What I did was manually entered all of these setprop commands below, on the...
forum.xda-developers.com
This is one but there are others if you need the help.

After relock bootloader i can send phone to warranty?

I tried to relock the phone with the command "fastboot oem asus-lock", but it shows "waitting for any device" and my phone just sit there and do nothing..
Any other method to relock the Zenfone 7 pro?

M-772007 said:
hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz
Click to expand...
Click to collapse
I believe that relock is impossible and but to make the device recovery to installed status of stock rom keeping with unlock bootloader.
Please see my post. May make it help or not.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com

Oneplus 8 stuck in fastboot mode after trying to downgrade from A12

I was on A12 beta1, so I decided to go back to older firmware, I unlocked my bootloader and wanted to flash fastboot rom. When I tried it it says "Flashing not allowed for Critical partition" and when I try command:
fastboot flashing unlock_critical
It says failed, device already unlocked.
So I gave up and wanted to try MSM Tool, downloaded it and after literally 2hrs of looking for a proper driver somehow got it to work and see my device in EDL mode, but when I start flash it says "Param Preload Fails".
I have no idea what should I try next, tried everything in past 3/4 hours.
Device stuck in Fastboot mode, no booting, bootloader unlocked, any suggestions are welcome..

Redim 9A system is destroyed

Hi,
I just recently tried flashing my redmi 9A phone from china rom to global rom, but it failed, now the phone is bricked and it loops to "system is destroyed". Though I can still access fastboot by pressing volume down +power, when i try to flash it again using Miflashtool with dandelion fasboot global room, it gives me an error " crclist" or "remote device is locked" error. Please help
Thanks

Hi. Try flashing the China rom. If it doesn't work try reunlocking the bootloader. If this doesn't work either. You need to flash it using Sp Flash Tool. There are many tutorials on YouTube.

Question Bricked: "the current image have been destroyed and cannot boot..." on Realme C2

Hey guys,
I need some help with my phone. I tried to install twrp recovery on it, but I messed up.
Here's what I did: I unlocked the bootloader using "fastboot unlock" and then I flashed the twrp image using "fastboot flash recovery twrp-3.7.0_11-0-RMX1941.img". Then I tried to boot into twrp using "fastboot boot twrp-3.7.0_11-0-RMX1941.img", but it didn't work.
I should lock the bootloader again, so I stupidly ran "fastboot lock" without doing any research. Then I selected "recovery" from the bootloaders options, hoping it would boot into twrp. But instead, it showed me a message saying "the current image have been destroyed and cannot boot..." And now it won't boot at all.
Additionally, I can enter the recovery mode nonetheless, the error is still showing up and I'm unable to connect my phone to my PC using cable either anymore, so no fastboot.
Here's my hypothesis: I think this is just a soft-brick however, is there a way out?
Specifications: Realme C2, Mediatek (I don't know which MediaTek it is)
Did I brick my phone? Is there any way to fix this? Please help me out, I'm desperate.
I really appreciate any help you can provide. Ask me freely if you want some further information regarding this.