Hello! I have a bricked OnePlus Nord N200 5G with me, and I'm pretty sure I have tried everything at this point.
I mistakenly downloaded the N100 firmware files, namely XBL, ABOOT, and TZ and flashed them through fastboot, and came back to a nice looking brick on reboot.
MSM Download Tool or EDL should be able to save the phone, in theory, but even with the correct programmer, it won't take a flash of any kind. I have tried the global firmware, the T-Mobile firmware, tried Windows and Linux with QPST and EDL respectively, and can't get the phone to do anything.
Almost as if it is crashing halfway through firehose upload?
Would it be possible to short UFS through the board perhaps, maybe it's trying to crosscheck N200 files with N100? But PBL being in bootROM should take a flash with the correct programmer, right?
To be upfront about it too, if this phone is perma-dead, so be it. I have a lot of free time on my hands at the moment and wanted to try and revive it if possible. I'd appreciate anyone chiming in. Thanks!
do you have a screenshot of what the phone driver looks like in device manager when in EDL mode?
do you have a screenshot of what MSM download tool status looks like right before you click START?
AiM2LeaRn said:
do you have a screenshot of what the phone driver looks like in device manager when in EDL mode?
do you have a screenshot of what MSM download tool status looks like right before you click START?
Click to expand...
Click to collapse
I don't have any screenshots, however I installed the drivers correctly, phone on Windows shows up as Qualcomm 9008 COM Port. As for MSM Tool, I have tried messing with the SHA and lite and reboot options, to no avail.
I currently run Arch Linux, and bum family's Windows PC for flashing.
If you need any Linux screenshots, I have those.
have you tried a different USB cable?
different USB port?
and/or different computer?
AiM2LeaRn said:
have you tried a different USB cable?
different USB port?
and/or different computer?
Click to expand...
Click to collapse
Yeah, I have tried an Intel based Linux machine and a Ryzen based Windows machine, tried different cables, even made a DIY EDL cable where I short DAT+ with GND.
yea sounds like you been doing the right things, well im sorry but thats beyond my knowledge, sounds like you really did something unusual and changed up the wrong boot files, usually MSM download tools works. Good luck.
AiM2LeaRn said:
yea sounds like you been doing the right things, well im sorry but thats beyond my knowledge, sounds like you really did something unusual and changed up the wrong boot files, usually MSM download tools works. Good luck.
Click to expand...
Click to collapse
Thanks for the help either way. Maybe someone who has messed with EDL more than I will come across this with some new info...
DaKillaz98 said:
Thanks for the help either way. Maybe someone who has messed with EDL more than I will come across this with some new info...
Click to expand...
Click to collapse
out of curosity in windows devie manager is is EXACTLY saying "Qualcomm HS-USB QDLoader 9008 (COM)" or is it just saying exactly "Qualcomm 9008"?
another question: when you are in EDL mode what is showing on the phone screen?
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
DaKillaz98 said:
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
Click to expand...
Click to collapse
sounds like you pulled a number on it, good luck!
DaKillaz98 said:
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
Click to expand...
Click to collapse
try this: https://github.com/bkerler/edl
it's an universal blankflash tool that allows you to flash every single partition individually.
WoKoschekk said:
try this: https://github.com/bkerler/edl
it's an universal blankflash tool that allows you to flash every single partition individually.
Click to expand...
Click to collapse
I've tried this tool,
Code:
edl --memory=ufs --debugmode --loader='/home/austen/Desktop/Phone Repair/0000000000515152_07b00c8737956b3d_fhprg_dre8t.bin' qfil '/home/austen/Desktop/Phone Repair/Firmware/extract/rawprogram0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract/patch0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract'
showed me that it is crashing halfway through the programmer upload. I get "Cannot receive number of program headers." when I send a bad programmer, as expected.
I made my own rawprogram0.xml and patch0.xml using the settings.xml to flash XBL and such, but didn't even get that far.
I'm going to try a clean Windows 10 VM, just to make sure this isn't a Windows 11 issue maybe.
DaKillaz98 said:
I've tried this tool,
Code:
edl --memory=ufs --debugmode --loader='/home/austen/Desktop/Phone Repair/0000000000515152_07b00c8737956b3d_fhprg_dre8t.bin' qfil '/home/austen/Desktop/Phone Repair/Firmware/extract/rawprogram0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract/patch0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract'
showed me that it is crashing halfway through the programmer upload. I get "Cannot receive number of program headers." when I send a bad programmer, as expected.
I made my own rawprogram0.xml and patch0.xml using the settings.xml to flash XBL and such, but didn't even get that far.
I'm going to try a clean Windows 10 VM, just to make sure this isn't a Windows 11 issue maybe.
Click to expand...
Click to collapse
you can also try a loader provided by the tool. it helped me to recover my Moto phone.
WoKoschekk said:
you can also try a loader provided by the tool. it helped me to recover my Moto phone.
Click to expand...
Click to collapse
That's the loader I used at first actually, I also tried one extracted from stock firmware, but no dice, trying a windows vm soon.
Related
I am new to this forum but have very high hopes that someone with more technical skills will be able to help me with my LG G watch
To start , i bought this new LG G watch and did not turn it on for 3 months after purchase , then i tried to run it on and it never came up , left it on charging overnight many times ,tried reset button and all other tricks i could find with help of Mr. Google except opening it .
So i plugged it in laptop USB port and at first it was showing some "Bulk" in device manager but it managed to get drivers automatically and now shows as HS-USB QDloader 9008 in device manager , than i again asked Mr. Google to help and read several forums and tricks and tips about getting device out of this phase using QPST etc. nothing worked so far.
I also tried LG flash tool but that also fails .
now i am here seeking help , anyone have any idea on how to get this device turned on ?
Is there someone who figured this??? Please help .. I did nothing it has happened suddenly. Now only showing this QDloader 9008.
sasadara said:
Is there someone who figured this??? Please help .. I did nothing it has happened suddenly. Now only showing this QDloader 9008.
Click to expand...
Click to collapse
I hate to say this but, you might be screwed. You should send it in or get a new watch.
Sorry.
drewmrk8 said:
I hate to say this but, you might be screwed. You should send it in or get a new watch.
Sorry.
Click to expand...
Click to collapse
But I didn't do anything. Sadly we have no option here in my country to send the watch back. i have seen that there are threads which unbrick from this state. But unfortunatly all the files are related to LG G3 and G2 and so on. So I don't have necessary files for unbrick Qualcomm. Hope if i could get any help :?
sasadara said:
But I didn't do anything. Sadly we have no option here in my country to send the watch back. i have seen that there are threads which unbrick from this state. But unfortunatly all the files are related to LG G3 and G2 and so on. So I don't have necessary files for unbrick Qualcomm. Hope if i could get any help :?
Click to expand...
Click to collapse
I don't think this would work, but hey, it's worth a shot.
droidsavvy.com/unbrick-qualcomm-mobiles/
Ya I tried before I post this, but it didn't success, im getting an error like this
Sahara Connecting …
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
v QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
No answers for that. May be the incompatible *. xml
sasadara said:
Ya I tried before I post this, but it didn't success, im getting an error like this
Sahara Connecting …
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
v QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
No answers for that. May be the incompatible *. xml
Click to expand...
Click to collapse
I was just searching around and I can't seem to find anything on the topic of an LG G Watch hard brick. Just wondering, did you buy the watch from eBay or a used one from Amazon etc...?
No I have brought from my friend. I have used this like from more than a year ago without any problem. normally i forget to charge. So it will completely out sometimes. Y]Day before yesterday also I forgot to charge. But yesterday I tried to charge, but it didn't turn on. I couldn't charge it. So I just connected to the computer then I saw this mode.
sasadara said:
No I have brought from my friend. I have used this like from more than a year ago without any problem. normally i forget to charge. So it will completely out sometimes. Y]Day before yesterday also I forgot to charge. But yesterday I tried to charge, but it didn't turn on. I couldn't charge it. So I just connected to the computer then I saw this mode.
Click to expand...
Click to collapse
It's also possible that it may just be dead for good, or it might be a defective model.
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
ChiefIlliniwek5 said:
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
Click to expand...
Click to collapse
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
netookska05 said:
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
ChiefIlliniwek5 said:
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
Click to expand...
Click to collapse
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
netookska05 said:
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
Click to expand...
Click to collapse
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
ChiefIlliniwek5 said:
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
Click to expand...
Click to collapse
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
netookska05 said:
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
ChiefIlliniwek5 said:
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
Click to expand...
Click to collapse
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Also, were you already rooted and wanted to go back to stock or what version of software were you downgrading from ( ex. 46A,47A what).
netookska05 said:
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Click to expand...
Click to collapse
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
ChiefIlliniwek5 said:
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
Click to expand...
Click to collapse
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
So the long story is that I was originally running 47A stock with root and TWRP recovery. I was having TERRIBLE battery life and it got to the point where I couldn't take it any more so I decided to flash a CM13 nightly. I was going to test the waters to see if I could use a systemless SuperSU version with CM13 so when I flashed CM13 I also flashed SuperSU 2.68 at the same time. It turns out that's a big no-no. So when I tried to reboot, I got the error message that the secure boot failed, or something to that effect. So after looking at posts on XDA I intended on doing the "revert to 10B from 47A" method with a TOT file and the flash tool. Everything with that was working great...it got to 94% complete and got the point in the process where the phone reboots, but when the phone left download mode it never came back and the flash tool never made a re-connection with the phone to complete the end of the process. From that point on, I could not even load into download mode, thus here I am.
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
Ok so I used the androidbrick tool in that link you sent me and the process seems to have gone through correctly. After re-installing my battery the phone booted to the LG screen, then showed the little android guy with a progress bar, but that screen didn''t last long before the phone rebooted again and this time after the LG screen I got a screen that said "miniOS" and following that came a blue screen with the words "Factory Reset Status" and a big red number 2. So that's where I'm at now and I'm going to look up info on that to see what I do next. If you have any experience with this step please let me know.
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
Ok, this is where I was earlier today and when it got to about 94% complete and commanded the phone to reboot, the phone never came back to a state that allowed the flash tool to complete. I've seen some sites talk about having to hold the up volume button at a certain juncture around the time that it failed for me last time. Is there some trick to this?
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
ChiefIlliniwek5 said:
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
Click to expand...
Click to collapse
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
netookska05 said:
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
Click to expand...
Click to collapse
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
roirraW "edor" ehT said:
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
Click to expand...
Click to collapse
@roirraW "edor" ehT Good idea I may just do that myself.
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
CP100 said:
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
Click to expand...
Click to collapse
Hello!
When you say that the phone won't turn on at all, do you mean that the LG logo does not appear when you attempt to turn it on? In any case, your phone seems to be recognized by your computer, so download LGUP (with UPPERCUT) and see if they can communicate. You can flash the stock firmware using the .kdz files linked by @autoprime in his All-in-One G5 thread. I believe the firmware made for the RS988 Brightpoint (BPT) variant doesn't have anti-rollback protection, so you'll have the most luck flashing it. Make sure, though, if you go that route, to flash the non-carrier firmware afterwards.
NextDroid said:
Hello!
When you say that the phone won't turn on at all, do you mean that the LG logo does not appear when you attempt to turn it on? In any case, your phone seems to be recognized by your computer, so download LGUP (with UPPERCUT) and see if they can communicate. You can flash the stock firmware using the .kdz files linked by @autoprime in his All-in-One G5 thread. I believe the firmware made for the RS988 Brightpoint (BPT) variant doesn't have anti-rollback protection, so you'll have the most luck flashing it. Make sure, though, if you go that route, to flash the non-carrier firmware afterwards.
Click to expand...
Click to collapse
The Logo doesn't appear, after being plugged in to my PC, it just gets a little warm.
As for the LGUP with uppercut, I ran the program and it gives me a message of it saying "no handset connected". It is currently on COM3 in device manager named "Qualcomm HS-USB QDLoader 9008".
CP100 said:
The Logo doesn't appear, after being plugged in to my PC, it just gets a little warm.
As for the LGUP with uppercut, I ran the program and it gives me a message of it saying "no handset connected". It is currently on COM3 in device manager named "Qualcomm HS-USB QDLoader 9008".
Click to expand...
Click to collapse
Interesting. This reminds me of APX mode from the NVIDIA Tegra devices.
I think there's a Qualcomm-developed firmware flashing tool that can detect the device via the COM3 port. I cannot recall the name, but if you find it, you should give it a try.
I also have same issue flashed wrong Rom showing qualcomm 9008,complete black screen not even showing charging also,no recovery mode no download mode.is there any solution for it.
balu9999 said:
I also have same issue flashed wrong Rom showing qualcomm 9008,complete black screen not even showing charging also,no recovery mode no download mode.is there any solution for it.
Click to expand...
Click to collapse
I don't know if they exist. You need qfil and whatever firmware parts and edl recovery files. Your fire hose programmer for your chipset.
I've read some guys claim sd card method. But I've never done it on this device
Where you ever able to unbrick the phone?
I am currently experiencing the same issue, the best method that would seem to work so far is through QFIL but I can't find the firehose file.
same problem, any help?
CP100 said:
It's been hardbricked for almost a month now. I've looked everywhere on how to unbrick this specific model on XDA but didn't find anything.
I know it's been done for models like the V10, G3, etc.. so I thought there might be some hope from bringing my phone back to life.
I goofed up accidentally installing the wrong ROM for the phone. It had TWRP and all but the phone won't turn on at all.
Does anybody have system dump files for the RS988?
Click to expand...
Click to collapse
I have the exact same problem but i have the h850
Stupid excuse, but I was under the influence and decided to flash PE on my phone and messed the A/B slot choice, so got stuck in fastboot and it didn't boot into recovery anymore no matter how much I erased and flashed it to any of both slots. More stupid decisions kept coming, and I erased EVERYTHING, system, vendor, modem, etc... pushed recovery via fastboot again but now it won't even go to fastboot, screen shows nothing, and Windows detects the device as Qualcomm HS-USB QDLoader 9008. Did some research and apparently phone is in Qualcomm Emergency Download Mode. Found this https://forum.hovatek.com/thread-19721.html and apparently it's possible to extract mmcblk0.img file from a similar device. Does anybody know if this will work ? Also MiFlash keeps showing " cannot receive hello packet " and then times out in like 19 seconds and device is unresponsive to everything and anything... Help please :')
freeze1994 said:
Stupid excuse, but I was under the influence and decided to flash PE on my phone and messed the A/B slot choice, so got stuck in fastboot and it didn't boot into recovery anymore no matter how much I erased and flashed it to any of both slots. More stupid decisions kept coming, and I erased EVERYTHING, system, vendor, modem, etc... pushed recovery via fastboot again but now it won't even go to fastboot, screen shows nothing, and Windows detects the device as Qualcomm HS-USB QDLoader 9008. Did some research and apparently phone is in Qualcomm Emergency Download Mode. Found this and apparently it's possible to extract mmcblk0.img file from a similar device. Does anybody know if this will work ? Also MiFlash keeps showing " cannot receive hello packet " and then times out in like 19 seconds and device is unresponsive to everything and anything... Help please :')
Click to expand...
Click to collapse
Maybe you will need do the EDL mode with an authorized account, and reflash system.
X7REME13 said:
Maybe you will need do the EDL mode with an authorized account, and reflash system.
Click to expand...
Click to collapse
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
freeze1994 said:
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
Click to expand...
Click to collapse
Visit a service center or use some online service. EDL stands for Emergeny DownLoad mode..
freeze1994 said:
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
Click to expand...
Click to collapse
You are going to have to look for any user who has such an account. I know of some that have them, but I don't know if they are trustworthy (it remains in you).
- @Android_Servis on Telegram
- +7 967 777 15 98 Telegram and (I guees Whatsapp to)
- +880 1771989858 Whatsapp only
Write to them, hopefully they can solve your problem.
If you solve it, let me know with whom and how you did it...
I have an A3 with SoftBrick and I also need to solve it.
Apparently it's quite hard to get an authorized account to be able to flash in EDL mode indeed, trying to authorize mine, guess all that I can do is wait or go to s-unlock.com, reports of it working all around, really appreciate the help guys...
_mysiak_ said:
Visit a service center or use some online service. EDL stands for Emergeny DownLoad mode..
Click to expand...
Click to collapse
Appreciate the tip but I hate that EDL is locked and kinda want to go headstrong against it and get this done without paying a dime, phone is my property after I bought it, I don't see why any part of it should be locked and inaccessible to me as its owner ... just hate the way this has been handled by Xiaomi, feels greedy and wrong to me... Really appreciate the heads-up though, maybe it'll code to that eventually
freeze1994 said:
Appreciate the tip but I hate that EDL is locked and kinda want to go headstrong against it and get this done without paying a dime, phone is my property after I bought it, I don't see why any part of it should be locked and inaccessible to me as its owner ... just hate the way this has been handled by Xiaomi, feels greedy and wrong to me... Really appreciate the heads-up though, maybe it'll code to that eventually
Click to expand...
Click to collapse
Well, we are lucky that we can unlock the bootloader without any hassle, unlike many other Android phones out there. Xiaomi "locked" EDL mode probably because of some sellers, who bought cheaper phones (be it MIUI or Android One), swapped the ROM and re-sold them at higher price. Ordinary folks do not need to use EDL, if service center needs to use it, it will be free of charge. If someone's willing to unlock the bootloader and mess up with the phone, he should face the consequences if something goes wrong. It's not manufacturer's fault. Personally I'm glad that Xiaomi did not take the route of Nokia or Huawei, where you can't unlock the bootloader at all (at least not without a paid service).
- download and register MI FLASH PRO https://miflashpro.com/
- download Fastboot ROM https://xiaomifirmwareupdater.com/miui/laurel/
- download (Mi A3) prog_firehose_ddr_unbrick.elf https://www.leakite.com/xiaomi-programmer-firehose-files/
- check device manager - ports: qualcomm hs-usb qdloader 9008 (com3) - device is in EDL mode
- replace ROM/images/prog_firehose_ddr.elf with downloaded prog_firehose_ddr_unbrick.elf - fix for "Your Account is Unauthorized for this operation"
- open Mi Flash Pro/Mi Flash
- select path to ROM (can not have any space)
- select clean all
- select flash
if you are getting "cannot receive hello packet" or "cannot read from port com" it's probably EDL timeout or driver issue.
- unplug usb from phone, push power button for 40 sec, plug usb back to phone, refresh and flash
just pushing power button and waiting for disconnect/reconnect wasn't working..
just unplug/plug usb wasn't working..
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
mimshipio said:
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
Click to expand...
Click to collapse
Seems it's completely bricked and will need to reflash in EDL mode
TheExploitedOne said:
Seems it's completely bricked and will need to reflash in EDL mode
Click to expand...
Click to collapse
How do I boot into edl mode?
mimshipio said:
How do I boot into edl mode?
Click to expand...
Click to collapse
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
TheExploitedOne said:
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
Click to expand...
Click to collapse
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
mimshipio said:
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
Click to expand...
Click to collapse
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
TheExploitedOne said:
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
Click to expand...
Click to collapse
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
mimshipio said:
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
Click to expand...
Click to collapse
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
TheExploitedOne said:
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
Click to expand...
Click to collapse
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
mimshipio said:
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
Click to expand...
Click to collapse
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
TheExploitedOne said:
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
Click to expand...
Click to collapse
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
mimshipio said:
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
Click to expand...
Click to collapse
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
TheExploitedOne said:
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
Click to expand...
Click to collapse
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
Try to look for other devices and search deeply good sir you may find what you need. I use Qualcomm devices because we have a special EDL mode and I have a programmer for all my devices to restore in the case of a hard brick like yours. I've been able to use custom tools to create a restore firmware like the Zone 2 (LG) and flash the device far enough to get it into download mode to flash the KDZ
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
You'll need to search with other devices or just in general. I seen posts about it being in some USB mode but Samsung probably don't have that implementation
Hello,
I am currently facing the same problem. Were you able to solve the problem?