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.
hey guys
my honor 6 phone is bricked and adb or fastboot methods dosent work
but it connects to computer as HUAWEI USB COM 1.0
so i tried IDT method for board software but it failed either
Code:
20210124-22:29:30 usb1:Start downloading with VCom!
20210124-22:29:30 usb1:Load DownLoadBoot Version 2.0.0.9
20210124-22:29:31 usb1:Opening COM4 Success
20210124-22:29:33 usb1:download mode enter:17
20210124-22:29:33 usb1:Downloading xloader begin.
20210124-22:29:33 usb1:Writing xloader...
20210124-22:29:33 usb1:Write delay = 3000 ms.
20210124-22:29:36 usb1:Download xloader end.
20210124-22:29:36 usb1:download mode enter:255
20210124-22:29:36 usb1:Downloading fastboot begin.
20210124-22:29:38 usb1:Writing fastboot...
20210124-22:29:38 usb1:Write delay = 3000 ms.
20210124-22:29:41 usb1:Download fastboot end.
20210124-22:29:41 usb1:VCom download successfully.
20210124-22:36:06 FAIL (395 s). Error (41)
is there any hope???
what is the problem?
May you could help, i have redmi 5 plus stuck in logo and restart continously with locked condition and should be use testpoint flash. ive been use 2 methods, miflash and qfill. miflash shows error code 'couldnt receive hello package' ive been checked qualcomm driver, were in test mode, detected in device manager. second methods is using qfill to install firmware engineering but have some error with code 'Sahara FailValue Cannot be Null', 'Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified' and 'Download Fail:Sahara Fail:QSaharaServer Failrocess fail'. Ive been Checked all and seems to be right but still couldnt solve the problem. A guy from other forum said that it has a possibility its emmc damaged. Thanks guys
Logs are attached below
Random - Google Drive
drive.google.com
So i tried to unlock bootloader and ended up there, that's a short story.
The long story is: I tried to unlock bootloader but failed with code -1 repeatedly, tried flashing 12.0.18 global bypassing fastboot altogether and now stuck in edl mode and device fails to send descriptors to pc hence being unrecognized, and i tried a lot already, so it's another try at recovering this device, if someone can help, please do
Disconnect battery?
Hello there!
My phone was bricked because I was flashing xiaomi.eu ROM in fastboot mode using cmd, and the flashing process was stopped midway.
I am able to enter into EDL mode only and only by using the test points, my phone is recognised as "Qualcomm HS-USB QDLoader 9008" as it should and also appears in MiFlash.
But when I try to flash a ROM (I tried global and Chinese) it gives me this error: "object reference is not set to an instance of the object".
I believe I have all the necessary drivers and my battery is probably long dead since the phone has been bricked for about a month now.
I read a bunch of articles describing similar problems but none of them gave a clear answer.
BlackTrade30 said:
Thank you for the quick reply!
I was guessing I needed an authorized account but MiFlash usually clearly indicated when you did. Something like "Authentication error". At least I have a solution!
Also, the thread you linked; the guy had symptoms that are exactly the same as I have. Unfortunately, he hasn't replied to me yet. According to him, he managed to get the phone unbricked using QFIL but didn't describe how. But thank you for bringing it to my attention!
Click to expand...
Click to collapse
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Try flash it by UMT
MaximeMNT said:
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Click to expand...
Click to collapse
Hello!
I manager to fix the phone!
Entering EDL mode should be possible using the test points.
Make sure your battery is disconnected.
Connect the USB to your phone but not to the PC.
Then short out the two pins.
I used tweezers to short them out.
While shorted plug in the USB the the PC. The PC then should detect the phone as a COM-PORT, you need the drivers if it says bulk device. It has to be USB 9008.
Now you need someone who can flash.
Mod edit: Paid services TG link removed.
EDL are Qcom's special access protocol. You should be able to flash via Qfil or Qpst suite, not Mi tool.
MA7MOD_GSM said:
Try flash it by UMT
Click to expand...
Click to collapse
UMT is free tool ???
NOSS8 said:
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Click to expand...
Click to collapse
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
chandan shah said:
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
Click to expand...
Click to collapse
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Yes sir.
I have tried to refresh again in edl mode for SANTONI_10.3NAMMIXM but gives same error all the time.
Most surprising thing is that just 7 days ago i had been successfully flashed 10.3nammixm
But on the same version miflash tool, same computer, same rom file, this time it gives error: "object reference not set as an object"
Mi flash tool : miflash20220218
I sent you log on private conversation please check.
Thank you for quick response sir.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Thank you sir for your suggestion.
I have revived again my redmi 4 device.
Flashed an older version of rom santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz
With miflash-20220218
Thanks again.