I had my Note 3 unlocked, running an Arωma Rom installed 2/3 years ago.
After flashing a kenzo firmware (don't ask me why, stupid things happen without reason), it didn't turn on again. It's stays black/dead.
I can enter neither fastboot nor bootloader.
Windows recognizes the COM port (Qualcomm QDLoader 9008) after installing the drivers.
Any advise how I can ressurect it?
All the threads I read were refffering to recovery with one of the 2 modes, I didn't find something for my case.
Thank you
Related
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
You need a working phone with USB debug enabled, then " adb reboot edl" from cmd... Sorry but if you are in a boot loop there is no knows way to access the Qualcomm mode...
There is no way for you to go into EDL mode. You need to apply for unlock permission from Xiaomi if you want to fix your mi4c yourself.
I applied for permission on Feb 1, and I got it today (Feb 18) despite the Chinese New Year holidays. I haven't even received my mi4c from China yet, and am not even a diamond member at miui.com, either. Good luck!!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
Did you try flashing it with Miflash? I got bricked yesterday, so I reflashed system this way, but via Qualcomm HS-USB QDLoader. Also, my phone did not react to anything except bootloader mode (holding buttons for a long long time), no charging, no lights - nothing.
Me too
Me too. :crying:
Hi,
I have the same problem of the bootloader locked. Not let me do anything. It is blocked. I've tried to give instructions by ADB, but will not let me load any file since it claims to be the phone locked.
I have applied the code unlock via SMS to Xiaomi, but they are very slow. Yesterday I wrote and asked you to unlock it. They asked me 2 days more waiting, at least.
This is still horrible, a shame.
I read the post of a colleague who manages to unlock it but has to be the phone working. For those who stayed with my at startup, there is no solution.
Regards.
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
press power button for more than 30 seconds to get out of edl mode.
yawarniazi said:
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
Click to expand...
Click to collapse
AFAIK , there's no such things as "automatically reboot after successfully flashed the device"
I was also in this condition but with different phone (it was Redmi 4 Prime (markw)), and all I did is just disconnect the battery form the circuit and then replug it, then I can boot to the system successfully
Hope it helps, but if it isn't then maybe something wrong
Hello. I am new to this subject (flasing ROMs, root..) and messed up ¯\_(ツ)_/¯. So I installed Havoc OS GSI on my Redmi 9, and it worked. The issues began when I tried to fastboot to become root. The process failed for some reason, so my phone was stuck on a bootloop but wasn't totally bricked at this point (could access fastboot, recovery [stock Xiaomi recovery], was recognized on pc...). In my ignorance, I tried to unbrick the phone with XiaoMiTools, program that also failed to unbrick the phone. This is the issue I am facing currently: After failing to unbrick the phone, XiaoMiTools restarted it, an has been since yesterday in a weird bootloop.
The phone displays the Redmi logo, some seconds later, it restarts itself, displaying the Redmi logo again and never loading any OS. Pc does not recognize it now, or at least I can't see it neither on ADB nor the Windows 10 Device Manager, as well as I can't access the fastboot nor recovery. It is a weird situation, because I am sure that the cable does work (tried with other devices) along with the phone's USB C port (it boots when I plug it), the phone also vibrates.
I have accepted that the phone is dead, but as a last option I come here to see if you guys could help me. Thank you.
Hint: Add " Redmi 9 to front of this thread's title thus people who own such a device get mainly addressed.
Hello,
First, some context:
After a factory reset of my Xiaomi Mi 10 Lite 5G (the phone is more than 2 years old, the warranty expired), the phone worked fine for a few days, but while playing a video game it suddenly crashed, then it showed up the following error: "Your device is corrupted. It cannot be trusted and will not boot."
Then the phone started displaying random white and black horizontal lines everywhere on the screen before shutting itself down again.
As of now, the screen stays completely dark, no sound, no vibration, no LED flashing, nothing shows on the screen whatever key combinaison I press.
Nothing happens when charging the phone either.
However, the device is recognized as "Qualcomm HS-USB QDLoader 9008" when plugged into my PC, so it is in EDL mode.
The phone has never been unlocked, nor flashed, and was (before this incident) running on the official MIUI 13 (Developer options had never been activated, nor ADB and it never entered into fastboot mode).
tl;dr; The device crashed without notice and put itself in EDL mode after displaying a worrying error message.
I tried draining the battery, no luck, nothing changed.
The phone is recognized by MiFlashPro (latest version: 7.3.706.21) but it shows a forseen error saying i need a authorized Mi account to flash it (but I don't want to pay 25$ a random guy on the Internet to flash it for me, knowing the device might be dead).
It is also recognized by QFIL, and I got my hands on a "patched Firehose" to bypass the authorized Mi account, but it always ends up showing the QSahara error (the error remains the same whatever firehose I select, patched or not, and whatever rawprogram*.xml too).
So, does anyone know how to flash a hard bricked Xiaomi in EDL mode using QFIL?
Anyway, I tried to be precise and concise, I hope someone has a working solution.
Thanks in advance for your answers!
PS: I tried to flash Monet EEA Global V13.0.4.0 (MIUI 13).
I have had the exact same problem happen to me with a Xiaomi Mi Note 10 Pro (tujana).it's just that I bought the device already bricked by the previous owner who flashed it with the ROM for the wrong device, namely the Redmi Note 10 Pro(sunny/mojito)I've since then succumbed to giving money to strangers online to flash it, but the flashing kept throwing an error(couple of guys tried it) and I couldn't flash it myself with QFIL as well, getting the same error messages as you. So I decided to dig a bit deeper and found out that the primary bootloader that is bar unflashable in those devices(please someone correct me if i'm wrong here) is different on the Xiaomi Mi Note 10 Pro that has version 2 primary BL and the Redmi Note 10 Pro has version 3. I do not know why and how the previous owner flashed the device to hardbrick it like that. I can't seem to figure it out. If anyone comes up with a solution I'm buying.