Could not find anything related in searching.
My cousins S2 randomly died. He could not give me much info about how.
It won't turn on, and it won't charge. It isn't the battery, we have tried other batteries. We don't know if its a brick, because he didn't do anything that could brick it (did not install a custom ROM, no custom kernel). Anyone have any idea? I don't have much to work off of. Anyone know a way I can get it to boot into recovery or download modes when it won't boot normally?
Plug it in press power if it doesn't boot but you see Samsung logo then you need a new power button
-if you can turn it on no logo just vibrates then you bricked it
Sent from my SGH-T989 using xda app-developers app
Same thing on my Galaxy S2
Mine did the exact same thing. One minute it was FTPing data to my server and (backup) and the next, it was dead... Luckily it was under factory warranty and they replaced all the guts (new everything inside, different MAC address, SN, and IMEI numbers... New SW too...
The folks on the phone at Samsung were great about the RMA process and the turn around was really quick! (sent back 2 days after receipt, via UPS 2 day!)
Samsung US Warranty Phone Number
FYI - I got much better response when talking on the phone than doing anything on the website. So here's their US contact info:
Samsung Warranty - 1-888-987-4357
Related
I was flashing the Energy Rom and I received and error when it was trying to install the kernel. I tried again, same thing. Foolishly, I rebooted instead of restoring. Now my phone won't turn on, led is off when plugged in. Looks dead. I plugged into my PC and it finds new hardware (which I think is a good sign), it is referring to my phone as QHSUSB_DLOAD. Also, when I hold the power down it seems to try to reboot as the computer finds the new hardware again. I tried with the volume up, home, and power same response, also volume down, home, and power, same response. My phone was successfully rooted prior to this and running perfectly. I made a nandroid back up prior to flash. Not sure what to do at this point. Please advise!! Thank you all in advance. I am using T-Mobile too.
Looks like I am bricked from what I have been reading. Phone is under 2 weeks old...can I send it back or should I just report it lost at this point and pay $130 and have a new phone in a day?
Called insurance and told them I lost the phone. Hopefully there will be a fix for this in the future and I will have a backup phone that I can sell.
you hardbricked it....lol. Even if a fix comes out carriers are now blacklisting lost&stolen phones.
Sent from my SAMSUNG-SGH-I747 using xda premium
Edited.
Carriers have been doing that for a long time. Go LOL at your face, dude was asking advice you ****head. Realistically he could have just called T-Mobile and say the device wouldn't turn on, justifying a free warranty exchange.
Hey I actually had the same problem. I bought my phone from Craigslist and didn't know if I could go through T-Mobile for exchanging. I researched this problem for the Galaxy S2 and other Samsung devices, and I read that people sent their devices into Samsung and got it fixed. I decided to do the same; I called Samsung and explained my problem to the rep. She emailed me a UPS label for the phone, and I sent it in. They replaced my phone with a new unit, and it should be back tomorrow.
http://imgur.com/1JKLx
http://imgur.com/craXM
That's what my friend recommended. Thats what I'm going time try
Sent from my SGH-T999 using xda app-developers app
I accidentally flashed a pit file in Odin which I think was made for a Galaxy Vibrant, my other phone.
The phone wont boot at all. When I plug it into the computer, the computer makes noise like it registers it though. The normal 'ding' sound followed by an error-like sound.
Is there any fix?
steelefriese said:
I accidentally flashed a pit file in Odin which I think was made for a Galaxy Vibrant, my other phone.
The phone wont boot at all. When I plug it into the computer, the computer makes noise like it registers it though. The normal 'ding' sound followed by an error-like sound.
Is there any fix?
Click to expand...
Click to collapse
Please don't spam your post all over xda I anwered it in general
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
If your phone does not enter download mode, or turn on to samsung logo, or enter recovery or anything then you're hard bricked. Your last resort would be to hope that Odin could somehow recognize your phone and you do a complete reset to factory ICS with no roots or anything. If you cant get any of those you are screwed. Your options? T-Mobile does not check on hard-bricked phones and does a replacement in 2 ways. 1. If your phone is under 20 days of purchase date you can get a full replacement (brand new) overnighted to you and just send your old one back and the amount is credited to your account when they process the return. 2. If your phone is under the 1 year warranty you can get a refurbished replacement for the 20$ processing fee as long as you turn yours in (just give it to the T-mobile rep and they should mail it for you so you dont gotta worry about dropping it off or making sure its packaged correctly) and then just wait for your refurbished.
NOTE: If there is any physical damage or water damage they will not replace it under any circumstances. I gave you your best options.
SOURCE: I've bricked mine on like the 18th day and got a overnighted replacement and sent my old one back.
i did something with the pit file and my phone does the same thing do u guys thing i can get a new phone through tmobile no recovery no boot no vibrate nothing any help would be appreciated but what do u mean damage i got a ding or two but nothing bad no water damage i was thinking i would tell them i have had problems wit the hard key power button and started into boot loop so i pulled the batt then this happen ive read that these phones have had problems wit the power button
Waiting for my replacement right now ups should be pulling up any min thank god
Think I just borked by AT&T Galaxy S3, and yes it is completely my fault. This is probably a dead end, buy I figured I'd ask as a last resort.
I've got a lot of experience rooting and flashing ROMS and flashing custom recoveries and was rushing a proceedure when the problem occurred. I was trying to flash the CWM touch recovery using the instructions here: http://forum.xda-developers.com/showthread.php?t=1739426
I tried to do all this through my phone using Terminal Emulator and typed in the portion "mmcblk0p18" one letter off from what I should have (I think I typed in "mmcblk0p08" ... sick sinking feeling my stomach right now). The code went through as I started to power down the phone as I was looking at the code I wrote. Noticed the mispelled line of code right as the screen was powering off. Now my phone is completely unresponsive, after I rebooted. The phone does not power on, cannot boot into recovery mode, and worst of all seemingly will not boot into download mode. I've had boot loops before and am familiar with how to traditionally boot into Download mode via POWER + Vol Down + Home Button and used Odin to flash a fix.
Are there any other options, short of taking it to a repair shop, that I can try? I'm guessing it's completely bricked, but I just wanted to see if there were any options I was missing that are worth trying.
About to start calling repair shops to see if they can take a look at it as well.
Warranty replacement. Just say you don't know why it won't turn on. I did this after dropping my rooted phone and they asked no questions.
On the phone now, I'll let you know if they're able to assist with troubleshooting or otherwise.
I did the same thing.... I had insurance through att reported the phone lost... I repeat lost not stolen.. Got a replacement in 2 days brand new white and used that to pull the stock rom and flash it to my old phone. The then turned around and sold the replacement phone
Sent from my SGH-I747M using xda premium
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Mphill46 said:
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I agree that it doesn't make sense. It's behaving almost as if the battery is just flat out dead. I have a spare battery, but when I tried that one it made no difference. I plugged the phone into a couple of different chargers while the AT&T rep was helping me troubleshoot and the charging light wouldn't turn on. The phone was not responding to anything at all, no matter what we tried.
They declared it hardware failure and are sending a replacement, as part of the original warranty. It did not have any physical damage, scratches, no water damage, etc.
Let this be a lesson to others: Be very very VERY careful with ADB and read your commands carefully. Those warnings about bricking your phone are real and shouldn't be taken lightly. I've rooted 6 devices and flashed what I'd estimate as over 60 ROMs over all my Android devices. I let my guard down and rushed things, and really my carelessness is all to blame at this point.
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So my phone running CM 10.1, turned off randomly. So I tried to reboot but kept getting stuck on the Samsung boot logo. I rebooted to CWM recovery mode, wiped cache and dalvik and rebooted which I thought would fix the problem somehow which it did. However, when it said "Android upgrading, optimizing apps", my phone lost battery (thought the phone charger was plugged in). When I plugged it in the outlet properly this time, I got through the battery charging logo. But when I tried turning it on afterwards, nothing. The phone doesn't respond when I tried to turn it on. Took the battery off, placed it back and when I plug it into the outlet, there is no more battery charging logo and I can no longer reboot. How can I fix this? Somehow, the phone might be trying to continue to turn on but is not responding when I try to actually turn it on. When I plug the charger, take off the battery, unplug and replug charger, the battery charging led lights up for 5 minutes (which is weird cause I disabled the indicator led when charging in the system settings). I allowed it to be plugged in to the charger overnight and when I checked this morning, nothing. No symptoms that it was charging; no heat on the phone. Is not being able to charge a symptom of a bricked phone. I have yet to try using another battery.
If you can't power on or get to DL mode or anything and none of the buttons respond it could be a hard brick
Check here:
http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SPH-L710 using xda app-developers app
I checked at a Sprint store and the device they have couldn't make a reading off my battery meaning it was most likely dead. I'm gonna try with a new battery and hopefully my phone isn't actually bricked.
Best of luck sir
Sent from my SPH-L710 using xda app-developers app
Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?
bonsly16 said:
Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?
Click to expand...
Click to collapse
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app
IDontKnowMang said:
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.
bonsly16 said:
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.
Click to expand...
Click to collapse
Its kind if hard to say if this was a brick or not. Usually sudden death is out of the blue, as far as I know the only way to achieve a hard brick is flashing a bad or international zip file
What's 150$ though? The emmc or the jtag
Sent from my SPH-L710 using xda app-developers app
I just experienced a similar problem as OP, and I didn't even flash a new ROM or international ROM. Since January, I've been using the ICS version of FreeGS3, stock kernel.
http://forum.xda-developers.com/showthread.php?t=1748818
I haven't flashed any new ROM's since January 2013 and have not experienced any problems until now.
This morning, however, when I woke up, I discovered that my Sprint S3 was stuck on the "Samsung Galaxy S III" logo. I pulled the battery and powered up, and it got stuck on the same logo again. I repeated this process several times and the same thing happened. After looking at some XDA threads, I went into recovery and decided to wipe cache and dalvik to see if that fixed anything. Again, the phone booted up and got stuck on the "Samsung Galaxy S III" logo again.
However, when I tried to boot into recovery again, I wasn't able to do so. I tried several times without any luck. I decided to see if I could put the phone into download mode. I did, and it was successful. I didn't do anything just yet because I needed to research more fixes before seeing what needed to be done. I put the phone into download mode several times without doing anything, but then later, the phone itself wouldn't power on.
No matter what combination of buttons I pressed, the phone simply wouldn't power on. I even tried other batteries which I knew were fully charged. When I put the phone on the charger or plug it into my PC, no charging lights light up. However, when I pull the battery an plug the phone into my PC, the charging light lights up and it the PC seems to try to install drivers. However, despite the charging light lighting up with the battery pulled, but phone plugged into the PC, I still can't get the phone to power on at all and therefore can't get into recovery or download mode.
It's similar to the problem the person in this video is having where he uses a jig to get back into download mode.
http://youtu.be/FdrdWqaXUBE
I have a jig on the way, so hopefully that helps fix my problems, but I don't really understand how the phone got bricked in the first place; First it was soft bricked when it got stuck on the "Samsung Galaxy S III" logo, but I was still able to get into recovery and download mode. Then, it was hard bricked when it wouldn't even power on to get into recovery or download mode. Did it get hard bricked because I went into download mode too many times? What might have caused it to be soft bricked. The thread for my ROM is now closed, so I don't know where else to ask these questions. I'll update you as I try to fix this problem. Any other suggestions are welcome.
Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!
edfunkycold said:
Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!
Click to expand...
Click to collapse
Hmm...I suggest you are talking about the other poster since I am not able to power it on at all (Recovery nor Download mode). I don't have insurance nor have warranty, I don't think Sprint would be able to fix it without me paying an incredibly huge amount. I was hoping that my data would be recovered but now that you mention the possibility of sudden death syndrome, there's no way I can recover the data if it is. A sudden death syndrome would require a replacement of the eMMC which is rather costly.
@bonsly16 My apologies yes my reply was to Lawyerman... But you do have an alternative option, http://forum.xda-developers.com/showthread.php?p=43724690 many have had success and in many cases everything was there for them.
Have a great day!