I flashed the phone with an incorrect firmware, and got a brick.
in the device manager appeared: qhsusb_bulk
I have a driver for this device: QDLoader HS-USB Driver
But I do not know what tool can be used to restore the bootloader.
is there any software available for this phone model? (something like BoardDiag3.99c)
igorya79 said:
I flashed the phone with an incorrect firmware, and got a brick.
in the device manager appeared: qhsusb_bulk
I have a driver for this device: QDLoader HS-USB Driver
But I do not know what tool can be used to restore the bootloader.
is there any software available for this phone model? (something like BoardDiag3.99c)
Click to expand...
Click to collapse
It's a perma brick
Sent from my LG-H910 using XDA Labs
I think you could jtag it back to life, program the nand directly, but you would need somebody to dump all partitions for you, which could be tricky to do because of how the meid and whatnot are stored.. maybe you're lucky and those are intact, and you just need to push a bootloader..
Sent from my LG-VS995 using XDA Labs
Hey, what device do you have, I can run a partition dump using lgup
Related
I have hard bricked my E8 (China mobile single SIM version) by flashing the hboot:crying:
It can be recognized as Qualcomm HS-USB QDLoader 9008 in my computer
I cannot enter the download/recovery/fastboot mode
Anyway to unbrick the phone? Many thanks:crying:
tommychu said:
I have hard bricked my E8 (China mobile single SIM version) by flashing the hboot:crying:
It can be recognized as Qualcomm HS-USB QDLoader 9008 in my computer
I cannot enter the download/recovery/fastboot mode
Anyway to unbrick the phone? Many thanks:crying:
Click to expand...
Click to collapse
Hi,
Your situation looks very bad, mess up with boot partition and I only know earlier model HTC One M7 and sensation have tool to fix this problem. But unfortunately not available yet for M8/E8.
Please try to get information from the following thread :
http://forum.xda-developers.com/showthread.php?t=2770684
http://forum.xda-developers.com/showthread.php?t=1522351
http://forum.xda-developers.com/showthread.php?t=1674226
Or you can start to do unbrick project for E8?
Good Luck!
tommychu said:
I have hard bricked my E8 (China mobile single SIM version) by flashing the hboot:crying:
It can be recognized as Qualcomm HS-USB QDLoader 9008 in my computer
I cannot enter the download/recovery/fastboot mode
Anyway to unbrick the phone? Many thanks:crying:
Click to expand...
Click to collapse
You need a compatible good HBOOT in Hex format, which you can write using QPST.. That is what 3-4 minutes of searching tells me.
buggerman said:
You need a compatible good HBOOT in Hex format, which you can write using QPST.. That is what 3-4 minutes of searching tells me.
Click to expand...
Click to collapse
i have another working E8, but how can i back up my good hboot?
many thanks:crying:
tommychu said:
i have another working E8, but how can i back up my good hboot?
many thanks:crying:
Click to expand...
Click to collapse
Honestly, I have no idea..
But I'm sure you can backup your working phone using QPST and use the files from there.. You need to search more for "how to backup using QPST" or something..
afther install OTA my phone
- No Download mode
- No recovery mode
- Secure booting error
- but no recognized on device manager
any solution without disassemble the phone?
yulianov25 said:
afther install OTA my phone
- No Download mode
- No recovery mode
- Secure booting error
- but no recognized on device manager
any solution without disassemble the phone?
Click to expand...
Click to collapse
Was the device with root?
Did you used OTA from custom ROM
enkhtwshn said:
Was the device with root?
Did you used OTA from custom ROM
Click to expand...
Click to collapse
yes my device was rooted and has OTA from custom ROM
yulianov25 said:
yes my device was rooted and has ota from custom rom
Click to expand...
Click to collapse
that is a total gg
enkhtwshn said:
that is a total gg
Click to expand...
Click to collapse
any solution?
yulianov25 said:
any solution?
Click to expand...
Click to collapse
Have you tried the LG pc suite? I got out of many messes using it with my LG G3 similar to your problem, even when the pc didn't appear to recognise it. Look for the option in the menu : Repair upgrade errors.
Before you try this, plug your device into the pc and look in device manager and see if it shows up as:
QUALCOMM HS-USB QDLOADER 9008 (COM4) device
If it does, it's well and truly bricked I'm afraid and can only be repaired under warranty. This is not as bad news as it may seem, as if this has happened, they will not be able to tell that you have rooted your device or anything else for that matter.
bobsie41 said:
Have you tried the LG pc suite? I got out of many messes using it with my LG G3 similar to your problem, even when the pc didn't appear to recognise it. Look for the option in the menu : Repair upgrade errors.
Before you try this, plug your device into the pc and look in device manager and see if it shows up as:
QUALCOMM HS-USB QDLOADER 9008 (COM4) device
If it does, it's well and truly bricked I'm afraid and can only be repaired under warranty. This is not as bad news as it may seem, as if this has happened, they will not be able to tell that you have rooted your device or anything else for that matter.
Click to expand...
Click to collapse
I get same problem, my phone can not go to download mode and can not connect with PC after I flashed 5.0.1 by KDZ file (in Connectivity option of phone, I can not see and any option for USB connect).
Please kindly help me. Thank you very much!
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
DallasCZ said:
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
Click to expand...
Click to collapse
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Alek Dev said:
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Click to expand...
Click to collapse
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
DallasCZ said:
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
Click to expand...
Click to collapse
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Alek Dev said:
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Click to expand...
Click to collapse
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
maybe when the 6.0.1 will be released i can connect with propper mbn. but i cant wait. I will send it to repair on friday or buy another device (zenfone 3 or moto g4plus).
Now i am still trying to bring it to life.
DallasCZ said:
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
Click to expand...
Click to collapse
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
here is the screen.
Alek Dev said:
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
Click to expand...
Click to collapse
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
DallasCZ said:
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
Click to expand...
Click to collapse
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Alek Dev said:
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Click to expand...
Click to collapse
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Did you have TeamViewer..i think that i can help you to get your device to life ( if you have Teamviewer send me ID AND pass to PM)
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
We are tried but Nothing same error . .i will google it ..)
murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
frankie paul said:
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:30 AM ----------
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Sent a my SM-N920V using XDA Free mobile app
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
I tried with "Android HS-USB QDLoader 9008" and also with "Qualcomm HS-USB QDLoader 9008" and even with "Alcatel HS-USB QDLoader 9008" always error when reading MPRG from the device.
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
yash_rathore25 said:
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
Click to expand...
Click to collapse
maybe,but you have to rewrite all the .xml files with data for your device, which we dont have.
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
HuhhooXDA said:
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
Click to expand...
Click to collapse
You cant even go in bootloader?
Us3rNam3d said:
You cant even go in bootloader?
Click to expand...
Click to collapse
No
Download samsung smartswitch and try to recover your phone from there.
Us3rNam3d said:
Download samsung smartswitch and try to recover your phone from there.
Click to expand...
Click to collapse
My phone doesn't turn on....
HuhhooXDA said:
My phone doesn't turn on....
Click to expand...
Click to collapse
Is it charged?
HuhhooXDA said:
Hi, I wasn't sure where to post this.
I was using Odin to reinstall the stock firmware for the Verizon S7, and then it won't turn on... In device manager, I see it is called qualcomm HS-usb qdloader 9008 (COM6)
Thank you for your help!
Click to expand...
Click to collapse
That sounds like you entered Qualcomm's download mode. Had encountered issues like that with HTC devices which ended with the device being sent back to HTC. Search around the HTC forums here on XDA. As before, the methods are device specific. But, maybe you'll get an idea. According to what I've read a long time ago, this happens when the device loses drivers for the chip or something. What happened exactly?
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
UP. Any thoughts? Any suggestions? Please!
Svobodniy_ said:
UP. Any thoughts? Any suggestions? Please!
Click to expand...
Click to collapse
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
BillGoss said:
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
Click to expand...
Click to collapse
It's complicated, because I tried a lot of ROMs from this forum and from other sources... The main problems, that MSM doesn't see my phone if I want to install ROM through MSM, and Fastboot give a lot of errors, if I want to install ROM through Fastboot...
How I brick my phone? I used file from OnePlus to unlock the bootloader (before it I unlock my phone from T-Mobile). After that all my data was wiped and I decided to change ROM from T-Mobile's to Global. I tried one of the ROM's (I don't remember which, but one from this forum). And my phone became a brick. (previously in my life I reinstalled a lot of ROMs on my Samsung Galaxy S2, Samsung Galaxy S4 - and have no issues, but this time...)
Use EDL to recover. You can get to fastboot, so you are not hard bricked. Make sure drivers are installed properly, try a different computer/cable
Svobodniy_ said:
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
Click to expand...
Click to collapse
It seems, on PC side of things you don't have drivers properly installed, otherwise you wouldn't have
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager.
For the same reason, i presume MSM doesn't see your phone.