XT1768 Hard Brick NEED HELP - Moto E4 Questions & Answers

I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!

skotseno said:
I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!
Click to expand...
Click to collapse
You bricked it. Many others have done the same thing to theirs by flashing the wrong firmware.

skotseno said:
I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!
Click to expand...
Click to collapse
I think you can just use a blankflash file. I even used the one for 1767 one on my 1768 when I bricked mine by accident (had the exact same symptoms as you, no bootloader, nothing). Got it form here: https://forum.kingfirmware.com/thread-4419.html

Related

[Q] Lg G2 d802 - bricked problem

Hello all, after ota update i stuck in bootloop, than i try factory reset, than i try to install CWM via fastboot and than my phone get bricked. First time before i bring phone to phone service phone shows LG logo and than security boot error. After "service provider" gives me phone back to me and tell me that he couldnt do nothin i try to power on the phone but screen is only black, nothing on it. Computer shows my phone like Qualcomm HS-USB QDLoader 9008 (com 3 port) . What should i do now, is there any chance to revive it ?
Thanks
djordjesl said:
Hello all, after ota update i stuck in bootloop, than i try factory reset, than i try to install CWM via fastboot and than my phone get bricked. First time before i bring phone to phone service phone shows LG logo and than security boot error. After "service provider" gives me phone back to me and tell me that he couldnt do nothin i try to power on the phone but screen is only black, nothing on it. Computer shows my phone like Qualcomm HS-USB QDLoader 9008 (com 3 port) . What should i do now, is there any chance to revive it ?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582142 if you have partition pop out try this link
skypang said:
http://forum.xda-developers.com/showthread.php?t=2582142 if you have partition pop out try this link
Click to expand...
Click to collapse
Like him i have the same problem, and i don't see any partitions at all, nothing appears when i plug mi phone

Chinese Axon 7 is not seen in ADB or MiFlash..Bricked??

After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
cozzysa said:
After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck
Choose an username... said:
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck
Click to expand...
Click to collapse
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.
cozzysa said:
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.
Click to expand...
Click to collapse
well that's the other way lol
I had to follow the guide, and it fixed my phone, so be assured that you can fix it if they send it back
It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.
cozzysa said:
It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.
Click to expand...
Click to collapse
Usually you can't enter Factory Test Mode when on a DFU brick. The known procedure to do that is to discharge the phone, then put it into FTM somehow and then using ADB to get to EDL. It's really weird that you've been able to pull that off that way
Could you tell us how you got into FTM? Just by vol down and power? It would be a nice addition to the brick guide, before attempting to take the phone apart
Yeah, it was just by power + volume down.

Moto x play don't trun on after system update

Hi,
During an android update (by OTA) my phone turnend off. Power button + volume down don't turn on the bootloader (nothing happens, I can only see a blackscreen).
Commands ADB and Fastboot don't work. Computer shows only a saying "Didnt recognized the USB device" or sometimes "Qualcomm HS-USB QDLoader 9008".
In the past the phone had TWRP and a lot of custom ROM's but I went back to stock.
Is it possible to flash it with PC? (With some kind of aplication like "smart phone flash tool")
Best regards!
You can't do anything. You lost your device. But if you find any solution then tell me.
bump
hubert987 said:
bump
Click to expand...
Click to collapse
You hard-bricked your device by Installing official OTA update in your unlocked device. This thing has happened to a lot of us unknowingly or by mistake. I did the same thing by mistake, I forgot about having an unlocked BL and flashed an official OTA update.
We basically fcuked up the bootloader/Fastboot I think and Motorola won't publish the required files to reflash it using Qfil.

Xiaomi Mi A 1 brick

hello install a custon rom for twpr and when reboot came out in bootloop then I was going to install the stock firware for my flash and the electric light went away and the pause, from there I do not recognize the device in my pc and try to do it of the moden of qualcomm uncovering the phone and I work halfway, I'm desperate and I need help
apart when it turns on it goes out encrypting and it is reinitiated again and again infinitely
Linux1026 said:
hello install a custon rom for twpr and when reboot came out in bootloop then I was going to install the stock firware for my flash and the electric light went away and the pause, from there I do not recognize the device in my pc and try to do it of the moden of qualcomm uncovering the phone and I work halfway, I'm desperate and I need help
apart when it turns on it goes out encrypting and it is reinitiated again and again infinitely
Click to expand...
Click to collapse
Hi there!
Well, first of all, I don't really understand very well what you're trying to say, but I think I get what you mean, and don't worry, your mi a1 at least does "something" which means it's probably just a Soft Brick and it's easy to get it back up and running
You just need to flash the stock firmware onto it, that's it, but if MiFlash Tool does not detect it, you can try the following:
Connect your phone to a PC via USB, open the “Run” dialog box by pressing and holding the Windows key, then press the R key and type "devmgmt.msc". That should open Device Manager. Then, look for a category called "Ports (COM & LPT)", open it, and if it says something like "Qualcomm HS-USB QDLoader 900E mode", follow this tutorial: https://www.youtube.com/watch?v=yJoIiLE_w3w
But if not, you need to tell me more details, are you able to enter Recovery mode? Can you boot in Fastboot mode?

[SOLVED!] Hard Bricked 6T Help Pls

Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
You must post in Q/A not here
Tapatalké depuis mon OnePlus 6T Havoc OS avec FP !
What were u exactly trying to do while this happened ?
Extreme_Ninja2099 said:
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
Click to expand...
Click to collapse
You can restore you device using fastboot rom. Search for oos 6t fastboot rom.. There are guides for installation.
P.S. It will give a whole bunch of error in the cmd during installation but don't interrupt the process as your device will be restored in the end
Use Mnm tool to fix your phone. It can fix hard brick devices and guidance is there how to use .
PS: this is not right place post next time post on Q/A section.
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
parker.stephens said:
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
Click to expand...
Click to collapse
Hold down every button till it shuts off, then force reboot to bootloader, then select power off to make sure it's off. Then do as I instructed above to fix it. Sometimes u can just run a fastboot rom to fix it, or boot twrp and flash a rom. I do this multiple times a day sometimes.
fullofhell said:
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Click to expand...
Click to collapse
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Extreme_Ninja2099 said:
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Click to expand...
Click to collapse
Everybody, it's called the MSMDownload Tool. It cannot be used in Fastboot Mode or Qualcomm CrashDump Mode, it can only be used in EDL Mode (Emergency Download Mode).
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
CaptionNixx said:
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
Click to expand...
Click to collapse
Power off use msm. Done.
fullofhell said:
Power off use msm. Done.
Click to expand...
Click to collapse
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
CaptionNixx said:
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
Click to expand...
Click to collapse
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Extreme_Ninja2099 said:
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Click to expand...
Click to collapse
Yes i did that and driver is fully installed Qualcomm HS-USB QDloader 9008 and there is No yallow sigh in driver
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Extreme_Ninja2099 said:
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Click to expand...
Click to collapse
Thanks brother its done
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Voldemort13 said:
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Click to expand...
Click to collapse
did yoy got any solution

Categories

Resources