Database Info

[Q] Bricked Qualcomm's secondary bootloader, what to do?

Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.

LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
in my opinion go to coustmer service and you know it but i think 
 @ShadowsDie can help you

LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance

ShadowsDie said:
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance
Click to expand...
Click to collapse
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.

LucentW said:
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.
Click to expand...
Click to collapse
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]

ShadowsDie said:
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]
Click to expand...
Click to collapse
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever

LucentW said:
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever
Click to expand...
Click to collapse
check your email

ShadowsDie said:
check your email
Click to expand...
Click to collapse
Tried to burn the SD card, it seems that the 7227A doesn't support boot-from-SD.
Anyways, I ordered off eBay for some change a jig dongle, as soon as I get that I'll try that way, but I think that it won't work since most of the hardware components (except for the NAND) are not made by Samsung.
I'll let you know how it proceeds

Nexus 5 QPST/QDLoader Mode

So, messing around with kernels and stuff, I wound up with a bricked device (wouldn't turn on, no response to anything, etc [I did eventually manage to get it functional again through a combination of button mashing and praying])
However, when plugging it into my computer, it showed up as "Qualcomm HS-USB QDLoader" which seemed interesting.
Searching the internet, I found several things. The QPST (Qualcomm Product Support Tool) Software suite, as well as other less useful links about the LGFlash tool, etc.
The programs also makes reference to debug and other modes, but there isn't a lot of documentation on the internet.
What I want to know is, is there a way to put the device back into the QDLoader or other QPST related modes so as to either update the firmware again, or just make backups for future use?
If there is, this seems like it would be a great tool for undoing any damage to the phone that isn't hardware related (the documentation says this part resides on a read only chip[which it seems fastboot doesn't])

It looked like you borked your phone to the point where there was nothing recognizable as Android left on it. I don't know anything about this loader but based on my past experiences dealing with proprietary OEM tools (Samsung KIES), I hope I never find myself in a situation where I'd need to learn. :crying:

Turn off your phone. Press all the keys if nothing happens your phone bricked. If you end up qualcomm 9008 mode we cant do much, because we dont have a working flash programmer and a working bootloader which would be flashed to the phone with the flash programmer. You can do 2 things. Replace your motherboard, or find the emmc pins on the motherboard to get direct acces to the storage then with a modified sdcard reader you could have access to the storage content then you could restore the bootloader. This is pretty hard method almost impossible.
If you have qualcomm 9006 mode then you can restore the bootloader with any kind of linux, because in 9006 mode the phone acts like a external hdd.

May I ask how exactly you messed around with the kernels to get this? Did you flash an incompatible kernel or something?

It sounded like he resolved his issue and wanted to know if this hidden mode can be used.

Wakamatsu said:
It sounded like he resolved his issue and wanted to know if this hidden mode can be used.
Click to expand...
Click to collapse
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off

It works!
bitdomo said:
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off
Click to expand...
Click to collapse
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...

caffeinatedangel said:
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...
Click to expand...
Click to collapse
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.

Well darn
bitdomo said:
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.
Click to expand...
Click to collapse
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!

I've never bricked my phones that bad man when I was a noob I installed safestrap on a device with an unlocked boot loader and tried to flash a ROM it didn't work out to well,man that was about two years ago

caffeinatedangel said:
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!
Click to expand...
Click to collapse
There were two placed where qualcomm documentatiosn could be found. One was a chinese forum where you have to be veteran or admin to get access to the files. This forum not exist anymore. The other is a chinese ebay like website where they are selling qualcomm documents for 3000 usd.
If you search for msm8974 boot flow or sahara protocol you will find file names for qualcomm pdf documents. Sadly just file names no download possibilty.

help| hard bricked my h830 after trying to flash another rom..

i rooted my phone and i wanted to switch rom for it,i flashed h850 rom rebooted device and it wont boot...i figured im on qualcomm 9008 mode in my computer so what can i do?
please please help me!!
thanks in advance..

Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...

Dark Nightmare said:
Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...
Click to expand...
Click to collapse
You probably didnt understand me well.. I cant put it in any mode...it wont turn on on any condition..

You said you rebooted twice, that tells me the device powers on, therefore, by doing a battery pull, holding the recovery or download mode button combos and powering up should get you into the desired mode. IF its not powering on at all:
1. Try charging the battery externally and try again.
2. See if the device is being recognized by a pc, if so there is hope that resting the device and trying again may work or we can see what mode it is in via adb/fastboot to get the device into a recoverable mode.
So....

Dark Nightmare said:
You said you rebooted twice, that tells me the device powers on, therefore, by doing a battery pull, holding the recovery or download mode button combos and powering up should get you into the desired mode. IF its not powering on at all:
1. Try charging the battery externally and try again.
2. See if the device is being recognized by a pc, if so there is hope that resting the device and trying again may work or we can see what mode it is in via adb/fastboot to get the device into a recoverable mode.
So....
Click to expand...
Click to collapse
The computer recognizes my device as qualcomm 9008

I have the same problem. My phone is dead only shows Qualcomm 9008.

Silly... If it's not for your phone why would you flash it??? Might have to wait for the official kdz from lg assuming you can some how get it into download mode. Or simply use your insurance for a new device. Expensive lesson learned

Maybe you can try the lg mobile support tool, since a tot file is available LG may have the stock kdz file available now, so try the recovery option for the mobile support tool.

Pretty sure that Qualcomm message thing is the true hard brick...
Sent from my pretty nifty brand new LG V10

This might sound stupid and it is usually for devices which have problems turning on or similar. I think is better to try anything that not trying all the options.
Why dont you try removing the battery, then close the module part without the battery. Press and hold the power button for at least 30 seconds. then release it. then put the batttery back on and try to make it boot into download mode. Chances are slim but the chance still there. This worked with my Samsung galaxy s5 after i flashed a rom that claimed to be for all models including the tmobile version when it clearly was for the g900f version . and i decided to try what i have done with other types of electronics and it worked.

Just tried on my phone. No go. Still dead. Trying lg repair. Hope I can get it fixed and not cost a arm and a leg.

Here is a guide to recover from 9008 mode
Here is a tool to extract kdz from tot
I've not read through these all the way, but if the PC sees it at all, it's not truly bricked... It might just be a pain in the ... to get it fixed. Those 2 links are good starting points for you. I hope you get this resolved.

I have the same error... My LG g5 H860 no turn on only connect in the PC on mode Qualcomm HS-USB QDLoader 9800.
Any idea or solution to resolve this?
Thx
BR

Dark Nightmare said:
Put it into download mode and restore the device via LGUP+TOT file, or if you made a backup, just reboot into recovery and restore your backup...
Click to expand...
Click to collapse
same issue just that my lgg5 tm is stuck on the firmware update for trying to root via lgup/tot file now not even lg bridge reads the phone it wants to then it says can not odetect nothin has worked

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.

Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient

Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore

The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers

you should be able to repair preloader from bootrom mode (BROM)

How to enter bootrom mode. I am sorry if it is a noob question

Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html

Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved

you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.

Question Need Help - ROG 5s bootloop

Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver

Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.

Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?

dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.

I believe it's more likely motherboard. Is there any fix for it?