Hello XDA members,
my phone did an OTA update but it's dead now (no boot, no recovery, no download mode, only black screen and QDLoader 9008 under Device manager), I looked everywhere for a whole week to find a solution, but nothing seems to work.
There is one thing that I found is that I need to Unbrick it using a JTAG box (but I don't have one).
do you know any other solution that might work in my case?
PS: solutions that I have tried
- Debrick image on SD card.
- using Ubuntu to push img files to the phone but it didn't detect it.
- I wanted to try QFIL but i couldn't find xml files for my phone
thank you for your time :fingers-crossed:
Have your device been fixed?
Related
Hello guys,
first thank you for this website and forum, i hope that you can help me with my phone. I have got my lg g2 into fastboot mode when i tried to flash a new rom, so I searched in the net and found the solution in here, the one that needs linux to copy the needed partitions to the phone I mean (laf.img, aboot.img .......), I have done everything right, however after doing it, my phone gone completely dead, no fastboot no logo, no recovery mode, no download mode, It's only a piece of hardware without a soul, when i connect it to a pc (win, linux) doesn't recognize it like before, so I cannot even try that solution again, after a while when i tried to open my device back cover i found that the version Written in the back was wrong it is not D802, but LS980, so all the partition files that i have used are the wrong onces, that what caused my phone to go black,
so please can you help, and if I change the mother board of the phone will i get a new functioning os or not?
thnks
Has anyone any idea on how to get out of this situation. Device totally unresponsive, screen is black blank and displays nothing irrespective of button press combinations, including EDL. Not that its of any consequence now but this was achieved by my flashing a data file onto and overwriting the "aboot protected partition"
Device cannot be switched "on" and therefore is not recognized by windows device manager. Windows has all drivers installed i.e. ZTE - Qualcomm - Qualcomm EDL, although this is rather a moot point considering the device won't switch on.
The following files are still alive both on my device external SD card and in a windows "C:" folder --- B20 file, B27 file, B29 file, B15 file, plus a TWRP backup. To repeat myself all and every button combination has been used to no effect.
I rather much doubt that I shall get an answer to this question but has anyone any idea as to how I can get in the position where I can flash any of the above files?
Attempt to put it in edl mode I believe there is an unbrick guide somewhere around here. Aboot is related to bootloader so your phone is bricked.
Do you hear any sound from the PC when you connect the phone? This is particularly important because with the "wrong" driver enabled your device may not show in Device Manager, but it most likely, may have booted into EDL mode. Please check this and post back. If there's a sound on connect, there is hope. Nothing ZaDig and the new unbrick guide can't help you fix. I was in a similar hopeless situation a few weeks back but I resolved it with the help of the unbrick guide.
@george241312 ... @KwesiJnr ... I appreciate your answers and thank you for bothering to reply.
george ... Sad to say I was fully aware of what I was doing when I overwrote the "aboot" partition and anticipated ending up in something like my present situation. I have one final line of help to try before giving up all together.
Kwesi ... The only sound my device made was agonizing screams as I totally bricked it.
THANK YOU ALL BUT NO MORE REPLIES IF YOU PLEASE - CONSIDER THIS MATTER CLOSED ..... The device is dead due to my own stupidity and I will just live with that.
Try connecting the phone to another computer or wall charger ?
Hi,
My wife's ZF3 died on saturday night, she was using it at night, next morning, it was completely dead, I have been trying to search what happened, but cant find an actual solution, when I connect it to a PC, or almost any PC (have tried 3 different) it shows as Qualcomm HS-USB QDLoader 9008...
I have downloaded the QFIL and have searched for several mbn files mostly downloaded from "Libra_QFIL_8953_...", tried with some of the partition and patch XML files I have found here, mostly downloaded from the 8675_W00 folder, and always receive the same SAHARA error...
I have some question, first would be, why did it fail by itself, I have seen some post saying they were trying to upgrade or downgrade the ROM and it crashed, that I get it, but my wife has no idea about OS and she did not certainly tried to upgrade or downgrade, so why it happened?
Second, will it work if I get the same model phone, download whatever files I need (emmc dump I think is called) and then update that to the bricked phone?
Can someone please help on this, I have barely no experience on this but want and can learn fast... I have read a lot of post from Wang1Chun and Saktis_STi but unfortunately, the later got banned and the necessary files were removed from the thread so I cant download those...
Please, any light or lead will be appreciated.
Thanks!
Hi ... I don't know if this problem of mine has happened to others, but I hope that someone who knows it can help me out. I'll explain my problem:
a few days ago I dusted off my old G7 and I wanted to get on a custom rom, whereupon I got to the problem of the locked bootloader, I do some research and I find that huawei no longer gives the unlock codes since 2018 (if I have not misunderstood) , then I try to put the root permissions and I can, believing that with the root I could have installed a modified recovery, but this did not happen ... now my problem is this: that I no longer have a recovery installed, nor custom , in stock, I also tried to do the factory reset but it does not make me do it because it does not enter recovery, much less using the dload folder with the UPDATE.APP inside. I'd like to at least put the recovery stock back. How could I solve this problem, since I don't have the bootloader unlock code? ... Thanks.
maybe this will lead
Ok.. i had this like you did exactly
the only fix was going into EDL MODE, which is launched by turning your phone off, disassemble your phone and short-connect pins like in photo, while shorting plug in your usb cable, if you have the right drivers your phone will show up in device manager in ports as "Qualcomm HS-USB QDLoader 9008"
once there, download any cracked box's like emmc dongle....
open box and replace any files you want or even replace the whole firmware files...
"BUT REMEMBER JUST IN CASE FOR THE FUTURE, IN BOX TAKE A FULL BACKUP OF YOUR EMMC"
My Nothing Phone is hard bricked and not working.
No Fastboot Mode
No Recovery Mode
Mobile in Dead Condition.
Nothing Phone 1 Firmware do not have emmc, raw program and patch file.
I own a heavily Bricked Nothing Phone 1. Currently, I am trying to bring it back to life. It is detected as Qualcomm HS_USB QDLoader 9008 (Com3). After spending some time online, i got a possible solution, flashing it using QFIL. I downloaded the firmware, it didn't have 3 files needed to start the flash process which were raw program XML file, patch file, prog emmc file. I looked up Online for these file specifically, But found nothing. Do anyone know what should I do.
I'm interested in this too! EDL Firehose saved my butt twice already. Would be great to have a saviour after an incredible eff-up on this phone.
If I can help in any way, let me know. The QPST tools and COM driver are installed, and can put my working phone in EDL for testing.
up on this post.
me be nothing phone is nothing
my phone now restart problem all i know sulotion already try in try but the same problem
iqcuratorhub said:
My Nothing Phone is hard bricked and not working.
No Fastboot Mode
No Recovery Mode
Mobile in Dead Condition.
Nothing Phone 1 Firmware do not have emmc, raw program and patch file.
I own a heavily Bricked Nothing Phone 1. Currently, I am trying to bring it back to life. It is detected as Qualcomm HS_USB QDLoader 9008 (Com3). After spending some time online, i got a possible solution, flashing it using QFIL. I downloaded the firmware, it didn't have 3 files needed to start the flash process which were raw program XML file, patch file, prog emmc file. I looked up Online for these file specifically, But found nothing. Do anyone know what should I do.
Click to expand...
Click to collapse
QFIL file for Nothing Phone is totally different compared to ROM firmware . You can't flash it . For unbrick the phone you must have this particular QFIL file which I don't think you find it online for now .
If by any chance you find it please share .