So, I'll be up front and honest, I work in electronic sales. I've stopped selling Note 20's, S20's, S21's and even Note 10's/Galaxy S10's because I'm getting so many returned for a dead boot issue. I've gone through 13 total devices so far, where when I plug it into the computer, it's seen as a Qualcomm HS-USB QDLoader 9008 device on COM23. Odin doesn't see it, according to some shady youtube stuff, I'd have to JTAG these devices to get them to boot again
Was wondering if anyone else has experienced this, has an in house fix (instead of samsung warranty) or has recommendations
Thanks!
Its not phone fault ! Users try to change csc if i remember "without etoken" and this method ends in a dead boot !!! Try to search this thing
Related
Good afternoon, all,
I have a tough one here: I think I may have put the wrong ROM on the device, and now it's totally dead: No power, no boot mode (I've tried power + camera), hard reset, soft reset, different batteries, etc. I've let it charge for days on the original charger, removed the battery and let the phone sit for several days, etc. No love. The only signs of life I get are when you unplug the USB, I get a red light flash, and sometimes the screen will flash at the same time as the red light.
Are my only options to flash it with jtag tools? Is there a howto on that?
Let me know what you think,
Mark
If you were unlucky enough to flash a G3 rom to a G4 device then I regret to inform you that your device is bricked. Generally speaking if you are unable to get into bootloader mode then your device is unrecoverable.
Many people believe that bricked wizards can be recovered via JTAG, however to the best of my knowledge nobody has discovered the location of these points therefore this theory is unproven.
It seems to me that if your device is unrecoverable your two options are warranty or motherboard replacement.
peter petrelli said:
If you were unlucky enough to flash a G3 rom to a G4 device then I regret to inform you that your device is bricked. Generally speaking if you are unable to get into bootloader mode then your device is unrecoverable.
Many people believe that bricked wizards can be recovered via JTAG, however to the best of my knowledge nobody has discovered the location of these points therefore this theory is unproven.
It seems to me that if your device is unrecoverable your two options are warranty or motherboard replacement.
Click to expand...
Click to collapse
i know this sounds bad, but if you bricked your phone, and you change motherboards, you can donate your motherboard to find out where the JTAG testpoints are.
if i ever brick mine, i will probably try to find the Jtag testpoints.
Ok, I'm gonna try to keep this as simple and easy as possible.
I bought my phone in March. Off contract, one year warranty. Golden.
Dropped it in June. Nasty scratches all along the BACK of the phone, so I took the opportunity to replace the colour from black to grey. Everything went smoothly and I was very satisfied.
Ran into some account issues that for some reason wouldn't be solved easily. Tried to do them properly, but got annoyed and said
F*** this, let's just factory reset the phone.
Spinning cogs for 5 minutes, then 15 minutes, then 4 hours, then 3 days. Started doing all possible hardware resets and button combinations. Nothing. Tried to reflash the OS with Nokia Care Suite. Found out it's now locked.
Here's the situation at this very moment:
-Phone does not boot past Nokia logo or cogs.
-Cannot get to the exclamation mark screen.
-No warranty, hardware change voided it.
-Microsoft Store gave up, said buy a 1020 instead.
-Carrier "Rogers" refuses to fix it due to voided warranty.
-No service shops nearby.
Any ideas? I pretty much gave up on the phone, I just don't have another 600 dollars for another.
What do you mean with "Found out it's now locked." ?
Phone is stuck on Nokia boot logo ?
Did you try refurbished method in NCS ? Save my silly ass several times
One time I even thought I bricked until finally manage to get mine 920 in flash mode...on youtube video seems so easy to get it..probably I was too impatience
boril said:
What do you mean with "Found out it's now locked." ?
Phone is stuck on Nokia boot logo ?
Did you try refurbished method in NCS ? Save my silly ass several times
One time I even thought I bricked until finally manage to get mine 920 in flash mode...on youtube video seems so easy to get it..probably I was too impatience
Click to expand...
Click to collapse
When I tried using the program it says I'm not allowed, I heard on other forums that Nokia locked out consumers and made it private....
Not sure about the NCS method, never heard of it. Mind explaining?
yasha.sinitski said:
When I tried using the program it says I'm not allowed, I heard on other forums that Nokia locked out consumers and made it private....
Not sure about the NCS method, never heard of it. Mind explaining?
Click to expand...
Click to collapse
NCS = Nokia Care Suite...here in the forum there were links about version, which is working and connecting OK.
Hello ladies and gents,
I am trying to help my fiancee revive her completely dead Amaze. This phone, unlike my own, is completely stock. No recovery or ROM flashing or S-off etc. It's straight from Wind Mobile (though around 22 months old at this point).
What happened: Phone was low on battery, so it was left plugged in to charge. Seemed fine. Going back to it a couple hours later, and it was died, which was odd since it was plugged in. Now it does not turn on at all (no HTC or carrier splash, recovery boot [vol down + pwr] does nothing), and the LED behind the speaker does not illuminate to indicate charging (no flashing, either).
Plugged into my computer, I get the "QHSUSB_DLOAD" device identifier, but using the brickdetect.sh script from the Unbricker thread doesn't detect anything. Likely because this has nothing to do with S-off bricking, but since I found that thread via the QHS string, I figured trying to detect it was worth a shot.
I would really love to be able to revive this device. The fiancee is back in school right now, so my income is the only one. Spending several hundred dollars on a new phone is just a kick in the pants while trying to manage already frightening wedding-related expenses. :/
What I have tried:
- Tried cleaning the battery terminals (battery and phone side) on my device
- Tried charging both on USB and wall charger for several hours (no change, no LED, no boot, no recovery boot)
- At my carriers store, I tested a known-good battery in our device, same behaviour
- Tested our battery in a known-good Amaze, after after a longer initial charge (battery was completely flat), that device booted with our battery.
- Tried booting into recovery, no luck
- Tried following steps in several other XDA Amaze and Sensation threads, and didn't get anywhere.
- I've ordered a new battery and external charger, but I'm not hopeful due to the above testing
What I haven't tried:
- Because I am still trying to get my Credit Card Extended Warranty to cover repair replacement, I have not opened the insides of the device. This thread proposes removing and replacing a battery on the mobo to get it to reset itself. I have not tried this yet.
- Anything to do with JTAG. While I've flashed ROMs and such myself many times on my own devices, I've never ventured into JTAG territory before.
What I want to know:
- Primary: What else can I try to diagnose what is wrong with this Amaze, and if it is recoverable?
- Secondary: Unfortunately we have photos on the internal memory (not SD-card) that are not backed up. If the phone cannot be revived, is there any way for me to get into the internal storage to try to recover those photos? This would be more of a challenge project. We can live without the photos, though she'll be disappointed. I'll be the hero if I can get them back, even if it means destroying the device permanently.
Thanks in advance for anyone who may have suggestions. I'm heading to bed for the night, but I'll check this tomorrow and test out any theories.
Does anybody have any theories I can test out aside from some sort of hardware failure on the mainboard?
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Darin_Ram said:
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Click to expand...
Click to collapse
I'm using Windows 7 (64-bit), but I also tried using the Ubuntu 10.04 based Live CD (PHToolz?) from the Unbricking thread, and it didn't detect anything at all (tried with and without automount enabled).
Reading what you said again, I'd say that it's a manufacture defect. It could be a wide list of things actually, hard to pinpoint.
In regards to recovering your photos and other files on the phone's storage itself, I don't think you can recover it at all.
The best bet right now is to get it exchanged if it's still under warranty (I'm assuming you didn't void the warranty by unlocking bootloader, attaining S-Off or flashing any custom roms/kernels/incompatible zip files e.g. A rom meant for another phone)
If it has warranty, don't give up hope.
Hello,
I have a Verizon Samsung Galaxy S4 SCH-i545. This phone was given to me by my buddy from work to try and fix it for him. I asked him whats wrong with the phone he said he doesn't know he said he went to bed and left it charged and the screen would never come on any more.
I've tried working know good battery
Working wall charger & USB cable
Tried pressing Home button and power button together and holding it
Tried pressing different combinations of home/power vol up/down
Installed KIES thinking the drivers would load
Still cant get this to come on.
I tried doing the same things while having the phone plugged in with the USB to a computer but the only message i got was unable to load drivers for qhusb_dload
I finally found drivers from the forums and installed them, i looked up a few other threads that didn't specify the how-to for the S4 but i downloaded Odin and a stock ROM firmware for the Verizon S4 but still even with the drivers installed Odin was still not able to recognize it. I am unable to find a Guide specifically for this model S4 and after a lot of searching it sounds like i need either some kind of JTAG RIFF or some kind of MicroSD card 16GB or 32GB with some software on it. If i need to solider anything to the board I have no problem in doing so. If i can avoid soldering and do the SD card fix that would be even better or anything else that i need to do in order to get this phone to work again..
Can someone help me out with this S4 qhusb_dload issue or point me to the correct thread so I can get this phone up and going again. The Data is not important to him as he said there's noting important he doesn't already have.
Odin/Download mode is accomplished by holding down Vol- and power and then let go of only power when screen lights up (even if still black) ... that doesn't work?
The the phone work AT QLL? It doesn't seem like it does. If so, you have a chance of getting the debrick image on a micro SD...
...reading over this again, yeah you're hard bricked, going to need JTAG
ToastyZ71 said:
...reading over this again, yeah you're hard bricked, going to need JTAG
Click to expand...
Click to collapse
Hi, yah after reading many other threads i feel like its called a hard brick and not a soft brick as you said.
I was reading about jtag but the device needed is called Jtag Riff and cost over $100, is that the only hardware device i can use in order to fix this phone? If there is another way can someone point me to a thread so i can try to save this phone?
Thank you for your help
mikey323 said:
Hi, yah after reading many other threads i feel like its called a hard brick and not a soft brick as you said.
I was reading about jtag but the device needed is called Jtag Riff and cost over $100, is that the only hardware device i can use in order to fix this phone? If there is another way can someone point me to a thread so i can try to save this phone?
Thank you for your help
Click to expand...
Click to collapse
As far as I know, that's it. Every other method, including USB Jig are for softbrick. - at over $100 for the JTAG Riff, might be better off hitting up swappa for a used/replacement device.
25 bucks on eBay to get it jtag. http://m.ebay.com/itm/181786279537?_mwBanner=1
Hi guys, this might seem like a bit of a noob question so bear with me.
Wife's G4 is stuck in boot loop and is pretty much a paper weight at this point. I've seen the tutorial (link at bottom) about flashing in factory firmware to fix phones stuck in boot loop. Does this pertain to a phone that has never been messed with, and is in boot loop from the LG hardware issues that cause it? Or does it only apply to when you brick the phone from trying to flash custom roms or whatever into it?
The tutorial doesn't really specify if it will fix my issue or if I'm screwed since it's a hardware issue.
Also, I'm using a motorola usb cable, but I've used this same exact cable to connect to the same G4 before to copy pictures and stuff and it has worked. But I absolutely cannot get the phone to connect to the PC in download mode. Any ideas?
http://rootmygalaxy.net/unbrick-lg-g4-with-lg-flash-tool/
http://tool.lime.gdms.lge.com/client/app/LGMobileSupportTool.exe grab this and when you install it click install usb driver. Then, hold volume up and while holding it plug in the usb cable. Hold the button until you see download mode.
If you have never modified the software, then it's almost certainly the known LG hardware issue. You can send it to LG and they will fix it for free, though it will take a bit to get it back.
Well before I did too much more, I decided to try verizon again. The last lady I talked to seemed completely ignorant and not interested in helping at all. This time I ended up talking to a guy who was pretty knowledgeable and understood the issue with these phones. And we also pay for insurance on our phones, which I completely forgot about. So he ended up getting a new G4 overnighted to us at no charge. It showed up yesterday and thankfully booted up without any issue lol. So if nothing else, at least there's a happy end to the saga.
Thank you guys for the responses.