Related
Phone won't boot into anything. When trying to boot into download mode windows does make noise but that's it. Tried a jig but still nothing. Suggestions?
any possibility the battery is dead? other then that not sure *bump* to the top maybe someone else has a better idea
blkbltwrestler said:
any possibility the battery is dead? other then that not sure *bump* to the top maybe someone else has a better idea
Click to expand...
Click to collapse
Try a battery? How would we know if it was dead?
Sent from my SGH-T989 using xda premium
if it was just a bad battery the phone would power on when plugged into an outlet
Tried a good battery from another phone, forgot to mention thst
Sent from my SGH-T989 using XDA App
what did you do before it died custom rom? flash a new recovery?
You sure its bricked fully? Cuz i had a brick a few weeks ago flashing something and testing it. My phone would not do anything with any of the button combos, no dl mode no recovery and when i plugged it into computer via usb i didnt get any sound or nothing. Thats a brick! Do u get any sound when connecting to comp? Idk if u cant figure it out call jtag but not sure if the debrick our device yet that will take around ten days u can google them i think its mobile tech. And what they do is take the board out of the phone sodder some wires on to it then run there software to debrick it then put phone back together. Now an easier option is ro just tell tmobile your phone died on charger and wont turn on tell them it was hot. They will never know especiallt if the phone wont turn on they will overnite one and it should only be 5bucks for a warranty exchange thats all it cost for me since our phones do have a warranty for year that is your best option u will get it the next day and it will be a refurb but mine is beautiful and looks brand new and the scree has like no lines actually nice. Now if u lost it or have damage that what insurance is for. That if u got it but like i said do the warranty exchange
yep that phone thejron is talking about, it became silent after trying to install a zip via rom manager. immediately after running the manager, reboot phone now, it flashed a small white light in the middle of the screen like a old tube tv turning off and that was it. no button light up. no dl mode no recovery. we tried everything. when hooked up to a pc via usb, the pc makes a usb connected sound but doesn't recognize anything or show up anywhere. if i hold the power button down, the pc actually makes the usb disconnected sound and does the usb connected sound when released. makes no sense really.
i have had something like this happen before...even though obviously from screen phone is not on , have you tryed opening odin the plugging phone up to see if odin recognizes? also since when in dl mode you first have to hit vol up to get there, you should try doing that too
just because phone is black and non responsive does not mean that it will not work.
odin doesnt recognize it at all. and when the jig was hoked up to it on and identical phone, it immediately went to dl mode. on this phone, we got nothing. jig in or out, volume up or down. nothing
theoldbaboon said:
yep that phone thejron is talking about, it became silent after trying to install a zip via rom manager. immediately after running the manager, reboot phone now, it flashed a small white light in the middle of the screen like a old tube tv turning off and that was it. no button light up. no dl mode no recovery. we tried everything. when hooked up to a pc via usb, the pc makes a usb connected sound but doesn't recognize anything or show up anywhere. if i hold the power button down, the pc actually makes the usb disconnected sound and does the usb connected sound when released. makes no sense really.
Click to expand...
Click to collapse
Can you tell us what zip you flashed?
Sent from my SGH-T989 using XDA App
Hi guys. Have a problem with my phone. Seems like I screwed it up. I was running sacs custom rom and I downloaded the TWRP (maybe a wrong version), the thing is that I downloaded it and flashed through Clockwork recovery and after that the phone went black and now doesn't turn on. Not even with home+vol up+power and not even with vol down+home+power. Nothing. Removed battery for 30 seconds and nothing.
any advice? I know I was a dumb. I'm paying insurance for it so I guess I could turn it in. But if there's something I can do, please let me know.
Thanks!
You might be hard bricked and have to take it into repair or replacement
Sent from my GT-I9300 using xda app-developers app
Where did u get the twrp u flashed? gotta link?
Double check you didn't flash something for the I9300 or another version. If it won't give you any sort of life (Try getting to download (Odin) mode) Then more then likely it's bricked..
Same problem here. No joy so far. The PC detects something (USB connected device) when I plug it in, but nothing that Odin is picking up.
ok. I downloaded TWRP 2.3 BL or something. Downloaded through GooManager doing a search,. Then rebooted the phone on recovery mode and installed it from CW. After it was flashed, the phone went black and never turned back on. If I connect usb cable to a PC I get the sound on the PC when you put any USB device but phone doesn't turn on. Tried removing the battery for a few hours and back in but nothing. tried conecting usb without the battery and it turns on the red light as if it's charging. then goes off. tried with vol up (and down), home and power but nothing.
I guess I got a hard bricked phone and I'm screwed for being stupid and install something I wasn't sure. It wasn't a ROM, so I thought it would not harm the device. Was wrong.
^ you say it all.
But when you got a replacement. Just press menu key in Goo Manager and select "install open recovery"
Sent from my O=O
yeap. asked sprint about repair it, since I have the insurance but they told me I had to pay a deductible. So I just called insurance I reported lost. Rather pay the same deductible amount and have it for spare parts than give it to them, plus the deductible. hehe. maybe someday I find way to make it work or just use it a spare parts.
thanks you guys for all the advices given. Still, if there's something else I could try, let me know.
Just hope no one else do that.
Once again... Thanks!
Since you found it via searching it could have been for any phone, probably not yours. a link would have helped here to confirm. The best way to confirm it's a paperweight is to plug in PC n see what windows calls it. If it shows up as QHSUSB_DLOAD then it's fukd.
billard412 said:
Since you found it via searching it could have been for any phone, probably not yours. a link would have helped here to confirm. The best way to confirm it's a paperweight is to plug in PC n see what windows calls it. If it shows up as QHSUSB_DLOAD then it's fukd.
Click to expand...
Click to collapse
yes. for sure was for any other phone that mine. so, should I put a bootloader on the micro sd and try lo connect it through odin to see if it detects it? where it's supposed to show that QHSUSB_DLOAD ?
Anyone know if OMAPFlash works for the GSIII? I'd suggest trying that. Google it.
Sent from my SPH-L710 using xda premium
I saw on ebay selling a Jig for the galaxy s3 but it says for: S3 /SIII I-9300 / I-747 Samsung Galaxy.
Does anyone knows if that device may work also for the Sprint S3? also if it may work for this kind of brick?
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Mr_Pistachios said:
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Click to expand...
Click to collapse
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
another Xperia Play Problem
Hi I am a noob also.
I am having a similar problem. Today I was trying to install the wifi module since it wasn't installed on the gin2Jellybean rom, i tried to flash the phone using the Flashtool (turned the cellphone off and pluged it in again while holding the back button) then the window disappeared and nothing happened. So I tried again, but first I took out the battery and put it in again and tried to flash again and now nothing is happening, Doesn't turn on, Flashtool doesn't do anything and when I try plugging it the laptop does the sound of an unrecognized device. The phone doesn't vibrate or anything when I press the power button.
Just realized that I tried flashing my cell phone using the x10 BLRelock.ftf crap.. is there anyway I can fix this?
Please Help.
Thank you.
216Monster said:
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
Click to expand...
Click to collapse
Flashtool and fastboot doesn't detect my phone. So yea .
Mr_Pistachios said:
Flashtool and fastboot doesn't detect my phone. So yea .
Click to expand...
Click to collapse
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
216Monster said:
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Mr_Pistachios said:
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Click to expand...
Click to collapse
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Mr_Pistachios said:
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Click to expand...
Click to collapse
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Mr_Pistachios said:
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Click to expand...
Click to collapse
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Mr_Pistachios said:
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Click to expand...
Click to collapse
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Mr_Pistachios said:
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Click to expand...
Click to collapse
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Made sure to on my phone with the sim card in this time
Never gonna off my phone ever again (Hope it doesn't run out of batt LOL)
One thing to note is this really weird fluctuation in my phone's battery levels. Maybe my battery is going nuts? Attached is the screenshot.
Made sure to on my phone with the sim card in this time
The epic fluctuation may provide clues as to why my phone's behaving like so.
As you can see from the third dip, I was charging my phone. And then after switching it off, it wouldn't turn on. After a day, and countless times of trying to wake it up, you can see that the battery level has dropped sharply. Weird.
The first dip happened a few days ago(not able to turn on) on 1st Feb. The second dip happened on the 4th, while the third happened on the 5th, today These drops in battery levels happened when my phone couldn't turn on.
Qhsusb_dload
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
extrem3hunt said:
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
Click to expand...
Click to collapse
Does plugging the phone into the computer while holding the back button work?
Mr_Pistachios said:
Does plugging the phone into the computer while holding the back button work?
Click to expand...
Click to collapse
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Even if it finds the driver, it wouldn't help you, cos QHSUSB_DLOAD means that the phone can't find the rom, and kernel or whatever. (I think) Its like a computer without an operating system. QHSUSB_DLOAD = Qualcomm Highspeed USB Download Mode, which means its waiting for the manufacturer to flash the rom and shyt, and therefore, your phone is bricked. (Dead brick, i think?)
For me, i think there's something wrong with the connections in my motherboard, resulting in the phone not being able to find the rom and stuff.
Maybe there's no hope for you.........
In short, I think your phone's bricked forever.... Most probably.
any fix bricked play
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
QSHUSB_Dload Fix
tommyforest123 said:
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
Click to expand...
Click to collapse
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
extrem3hunt said:
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
Click to expand...
Click to collapse
Well, okay, imma give it a try, tnks.
Before flashing your "bricked" device, try this!
Mr_Pistachios said:
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Click to expand...
Click to collapse
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
proteusgr said:
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
Click to expand...
Click to collapse
HAHAHAHA LOL.
Glad it worked out for you
My guess is that there's something loose inside, and repeatedly trying to do that may help.
I think it's something to do with Sony's build quality, or maybe because the phone sustained hard knocks and stuff. (Probably just wear and tear)
Aledranssimo didn't reply me, so yea. T.T
This issue is probably an intermittent one I guess. I've since moved on and gotten a new phone (Lumia 520)
I have a Galaxy Note II with a striaghttalk SIM in it, and i was just browsing the web, put it back in my pocket, and when i tried to turn it on, it wouldnt turn on.
I tried replacing the battery, doing a hard reset, charging it, connecting it to a computer, but it wont even show the start up screen.
I bought this seven months ago from Newegg, but I rooted it so I probably dont have the warranty. Does anyone know how long/much it would take to fix this? Also, has anyone had similar problems?
Thanks in advance
Can you access your recovery?
Simone said:
Can you access your recovery?
Click to expand...
Click to collapse
Nope. Nothing will even turn on the screen to the samsung screen or the recovery screen.
The computer doesnt even recognize it
minnkwonn said:
Nope. Nothing will even turn on the screen to the samsung screen or the recovery screen.
The computer doesnt even recognize it
Click to expand...
Click to collapse
This might be the Sudden Death Syndrome everyone is talking about.
Can you go into Download Mode?? Vol- + HomeButton + PowerButton
If Download Mode works you can Flash stock rom with Odin
[My device is a Sprint Galaxy S III, unrooted on STOCK 4.1 (with multi-view)]
So the previous night I plugged my phone into the charger as normal and went to bed. Strangely, when I woke up, my phone was turned off. Curious, I went to turn it back on and waited for it to boot back up, only to have it freeze up in the middle of opening an app. I wasn't worried at this point, but after a battery reseating and restart, it happened again. This time, it froze up on the 'Galaxy S III' boot logo. I tried multiple times to restart, swapping batteries, waiting, and managed somehow to get it to recovery mode. There, I managed to wipe cache and attempt to restart the phone once more. Nothing--it was still frozen on the boot logo. After waiting a while, I tried to get it back into recovery mode, popping out the battery whenever it froze. To my horror, this time, pressing and holding the power button did not get a response from the device.
Mind you in my (roughly) year's worth of time with this phone, I had never dropped it or subjected it to any form of shock or damage. Seriously--the phone looks out-of-the-box-brand-new.
Now the device is bricked(?) I'm thinking it's some sort of hardware defect, but I'm confused because it happened out of nowhere--simply overnight. Nothing I do seems to elicit a response from it and I even tried swapping in a freshly charged battery.
I really don't care about most of the data on the internal storage (cloud sync ftw!) but there are a ton of photos inside that I would give anything to save. Is there any way I could save them? I'd appreciate any input!
TL;DR: Out of nowhere, my 1yr old GSIII suddenly started acting strange and after some troubleshooting bricked itself. Need photos on internal storage.
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Whiplashh said:
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
CNexus said:
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
My phone actually won't even go into download mode. It stays off no matter what I press. Will the adb commands still work?
Additionally, my phone is not rooted.
EDIT: Actually, upon plugging my phone into my PC, it says exactly that. QQ
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
CNexus said:
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
Click to expand...
Click to collapse
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
cytark said:
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
Click to expand...
Click to collapse
No bueno. Here this can get you fixed up. http://forum.xda-developers.com/showthread.php?p=43724690
Sent from the future via Tapatalk 4
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Whiplashh said:
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
Click to expand...
Click to collapse
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Dude c'mon, I'm just teasing
CNexus said:
Dude c'mon, I'm just teasing
Click to expand...
Click to collapse
Oh alright. Lol. I figured you knew more about this.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Similar issues
I had a similar issue with my phone today. I'm mostly posting to show that this isn't an isolated incident, since I have insurance and can get my phone replaced, but any suggestions for fixing it would be very welcome.
My phone is a year old Sprint SGS3 running CM10.0 or so, stock battery with plenty of juice, haven't flashed anything or even booted into recovery in quite a while, no new apps for a week or so, no recent battery pulls, no usage out of the ordinary.
The phone died in my pocket, and upon trying to boot it would display the SAMSUNG screen for ~0.5 seconds, then display the "Samsung Galaxy S III" screen for ~0.2 seconds before dying. It did not bootloop, but remained off. Similar behavior was exhibited when trying to boot into recovery and download mode:
When booting into recovery, the SAMSUNG screen with the recovery overlay would display for ~0.5 seconds, then the "Samsung Galaxy S III" screen would come up for ~0.2 seconds before it died.
When booting into download mode, the SAMSUNG screen came up for ~0.5 seconds, then the warning about running custom ROMs came up. If I was quick, I could press volume up to start going into download mode, but it would still die almost immediately either way.
When plugged into a USB cable attached to a laptop or power, the battery icon would come up with the loading circle for ~0.5 s, then it would die. If plugged in with the battery removed, the right indicator light would come on and it would vibrate, but the screen would not turn on.
After booting over and over for some time, it will no longer respond in any fashion, except when plugged in with the battery removed as described directly above. I suspect the battery has died, and cannot be charged because the phone crashes before charging begins.
Any thoughts on how to fix it, or ways to revert back to stock when the phone won't stay on for more than 2 seconds?
That is The Sudden death Syndrome. Your power button has failed. It is messed up internally. This is a known issue with the S3. You can try blowing some air in the power button area and jiggling it around to get a temporarily working. But they do replace it for this condition.
Sent from the future via Tapatalk 4
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
CogDancer said:
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
Click to expand...
Click to collapse
Sorry when I referred to as they i meant Sprint.
Sent from the future via Tapatalk 4
Do you know if they will replace the phone past the standard warranty? I'm out of warranty by only a few days. I figured I had a problem with my battery so I bought a new one to test before I found the power button to have failed. I'm going to be heading back over in a few minutes to return the battery kit, and hopefully they will replace my phone without making me go through insurance.
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
I haven't ever replied to these threads but I need help so I hope im doing this right. I have a galaxy note 2 that did pretty much the same thing as the original thread poster. I can get to the recovery screen but I cannot connect to a computer. I really want my pictures and possibly to fix my phone. I appreciate any help you can provide. thanks