Database Info

Stuck in EDL mode , "hello packet error" , unauthorized to flash. [BRICK NOTE 7 PRO]

Stuck in EDL mode , "hello packet error" , unauthorized to flash. [BRICK NOTE 7 PRO]
[URGENT] Redmi Note 7 Pro stuck in EDL mode. I was trying to flash stock Mi rom using TWRP on my rooted device to unroot it but idk something went wrong. I had cleared Delvik-cache , cache , Data and Internal Storage. I formatted my data to de-encrypt my Internal Storage too.Now i cannot boot into recovery / cannot boot into download mode. From googling a little i know my phone is in something called EDL mode. My PC detects my phone when i plug it in but nothing in my phone works, absolutely nothing. Screen is blank since 2 days and i think it's bricked.The only thing that works is power button , it just power-cycles my phone. I am trying to flash a stock fastboot rom using MiFlash tool which is able to detect my phone but it keeps saying that i'm not authorized to flash this rom , . Has anyone found themselves in a similar situation? Please help me!
TL;DR - Bricked Redmi Note 7 Pro , Stuck in EDL Mode , MiFlash - "hello packet error" , unauthorized to flash the rom.
Any help will be much appreciated i really need my phone

Hey man, i don’t think MIFlash works with EDL mode without an authorized account.
Do you have an authorized account?

Peaceful.Ori0n said:
Hey man, i don’t think MIFlash works with EDL mode without an authorized account.
Do you have an authorized account?
Click to expand...
Click to collapse
nope , don't have. Do you know anyone who has it?

No, you have to pay to get an authorised account. It's a pretty complex and sketchy process. Take it to your nearest service center as soon as lockdown ends. Or find a way to get an account like that online.

Need help! No fastboot!

I was on Crdroid and wanted to get back into Miui since there was weekly miui 12 version now. Downloaded it and flashed it but it would not boot. I remembered on poco i had that i needed to flash latest miui andro 9 before flashing latest miui andro 10 for some reason so i got back into twrp and did it. After reboot it went into some sort of boot loot and i lost any recovery and fastboot. Cant get into edl for that matter also. Anyone has any suggestion?

Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?

malimukk said:
Can you elaborate a bit more, when you try to boot into fastboot with the button combination, does it work?
Do you get any indications when trying to turn on your phone?
Click to expand...
Click to collapse
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me

scudteshka said:
Button combination gives me blank screen and revovery gives MI logo and just that until it rebots and stays like that in some loop. I can get into test mode after opening it to try QFill flashing but i forgot about account authorisation thing. I do not have any type of service center in my country that wants to deal with this. Issue is probably due to anti rollback policy in 2s. So i need solution to flash somehow thru qualcomm port but aparently only wth that account that has authorisation.
Thats where i got till now. Spent a whole day also at 4pda trying to find solution but nothing there worked for me
Click to expand...
Click to collapse
Oh that's unfortunate! I think that in this case you will need to find someone with an authorized account that will flash it for you remotely. There have been some people around here offering that service for a small fee but it might be worth paying as that might be the only way to fix it.

Same thing happend to me, first time i tried using custom rom. i dont know what exactly happened. i think its have something common with anti-rollback feature. I sent the divice to OFFICIAL service center.... I told them "use mi flash tool and authorised account to flash fastboot rom in edl" These OFFICIAL trained technicians... ehm idiots... change whole mother board.... atleast they count it as warrasnty repair.... there is one guy on reddit who succesfull unbricked his device via "shady bussines" (there is also contact on reddit page)... some guys offer xiaomi unbrick services via teamviewer. you can give it a try: https://www.reddit.com/r/Xiaomi/comments/ftix9v/shady_services_unbrick_with_mi_authorised_account/ EDIT: its last reply reddit (hope its allowed to post links)
note: you can put yr device in edl mode by pressing powerbutton. im not sure if its pressing or holding. (yr phone need to by connected to pc, then mi flash detect the phone if all drivers are instaled, it should be shown in "windows device manager" as PORT named "qualcomm hs-usb qdloader 9008")
if you dont have authorised acc. this will happen https://imgur.com/a/oJVpKEl so you need someone with authorised account who will unbrick yr phone via teamviewer [Sorry for my bad english]
Ijust dont understand why xiaomi dont allow user flashing in edl mode... or just make harder to brick phone... i had oneplus and i never bricked it. bricking xiaomi is just super easy thank to their stupid anti-rollback and other b****its. i will never use custom rom on xiaomi again. i will dont buy xiaomi again

Did you try the MI Flash app? ...try to fastboot and check if mi flash works
Also try fastboot(combo-buttons only) and see if you can see the phone (cmd -> fastboot devices) ...if you see a device then you are good to go
If you have a fastboot miui rom you can use my guide: https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/weird-behavior-boot-loop-random-t4086703
It's like using MI flash program but doing it manually - if mi flash gives you issues or else
P.S. CMD MUST be with administrator rights of course!

Hi Guys,
got a big problem here today. after installing on orangefox a miui11 stable rom suddenly flashlight went on and it stopped to install it... i was like WTF? so i have go to reboot to the recovery and my mix 2s DIED.
now
1) battery is drained
2) no fastboot (black screen on vol down + power key)
3) no recovery (black screen on vol up + power key)
4) bootloop on miui logo
any idea?

Redmi note 6 pro self-bricked overnight - EDL flashing fails

Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...

I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .

Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations

Help with phone on bootloop

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.

Question POCO X3 PRO device (brick)

Hello!
Sorry, I don't know vell ENG, so I use a translator.
Problem with Xiaomi Poco X3 Pro phone (Global Update 12.0.6.0.RJURUXM) + device unlocked
Unsuccessfully decided to flash the phone... I got the POCO X3 PRO and POCO X3 NFC phones mixed up a bit. I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery. Then I tried to return everything as it was, but I couldn't. Accidentally via the TWRP menu formatted the System + partition Cache + Data and a few more sections, I don't really remember. At this stage, the phone was still functioning, turned on and rebooted in the recovery - TWRP menu. Then I tried to return the old recovery menu and connect Fastboot, but I couldn't. The phone turned into a brick. The phone does not turn on, does not work, the "POCO" logo does not appear, there is no way to go to recovery and Fastboot. The battery charge at that time was 46%...
HOWEVER, my computer sees the device as an emergency communication channel through the COM4 port - Qualcomm HS-USB QDLoader 9008 port
I'm already desperate and don't know what to do or what the instructions are... I don't want to open the phone and put it in EDL mode (if it helps at all)
I contacted a person with a service account, tried to restore the phone through the application "MiFlash_1212" by bypassing authorization and obtaining KEYS and access (I did not quite understand this point and how it works).
As a result, the firmware was able to run and the device began to be requested. But the following problem appeared, which I do not know how to solve, and that person stopped helping me (he has no time and simply does not want to, even though I paid him with money)
I read a lot of information on the form. Many tips and instructions did not help me.
What do I need to do? Who can I contact for help?
I wanted to get ROOT access (Magisc + YouTube Vanced + remove ads)
PS : But first I need to bring my phone back to life...

"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?

I guessed that you would ask about this moment.
It was my mistake and I thought they were the same.
And when the phone did not turn on properly, only THEN DID I REALIZE that I had downloaded the wrong files.
But what should I do?
Nitritus said:
"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?
Click to expand...
Click to collapse

I hope you find some help here

abood.mhd said:
I hope you find some help here
Click to expand...
Click to collapse
As they say : "Hope dies last" =((

Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty

Contact your nearest Customer Support Center. They will fix the problem

Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.

thenameisJEFF said:
Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty
Click to expand...
Click to collapse
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink

xelrix said:
Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.
Click to expand...
Click to collapse
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.

WoodenSKY said:
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.
Click to expand...
Click to collapse
This is likely because you might have format some important part as IMEI number. Like this guy said: https://forum.xda-developers.com/t/no-imei-and-no-wifi-plss-help.4276823/post-85014473
In this state, no matter what you do, you have to pay.
https://forum.xda-developers.com/t/poco-x3-pro-hard-bricked.4277803/post-85025433
The most safe way is Xiaomi repair support center. High charge, but for sure a working phone.

my poco x3 pro global stable(VAYU) is stuck in miui log i tired to flash it with magisk method now its stuck ther. any one can help me with it

WoodenSKY said:
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink
Click to expand...
Click to collapse
Straight to service center you go then )
It should still be within warranty becuz they only refuse hardware error not software brick
Beside it shouldn't cost much tbh

i did this mistake with my brand new galaxy s6 when it came out but the only solution i had was going to repair shop and the dude used a hardware tool called octoplus and he flashed it and worked but i lost my original imei adress but it worked i did search for you i found the tool you need is ufi box google it contact them and see if you get one or find a repair shop by the way i repaired that s6 with 10bucks

unfortunately, your only option is service centre as they are the only one who can get access to phone via edl mode and flash what was formatted

Just to be sure, I asked customer support and they said the following... "By installing custom ROM, Recovery, and/or Rooting your phone, the warranty is not void. However if your phone bricks while installing a custom ROM, then the warranty is considered void". They adding insult to injury for you

My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?

True ayush Kushwaha said:
My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?
Click to expand...
Click to collapse
same here, did you manage to fix yours?