Related
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.
I was reading multiple threads this morning about people soft bricking (or hard bricking their phones) and I was wondering (because I'm still learning)
Is there a lasting effect of soft bricking or hard bricking (aside from needing a jtag etc)
If I for some reason soft brick and get it back to stock is everything going to be perfect or is there a possibility for damage?
It might sound like a dumb question but...
KorGuy123 said:
I was reading multiple threads this morning about people soft bricking (or hard bricking their phones) and I was wondering (because I'm still learning)
Is there a lasting effect of soft bricking or hard bricking (aside from needing a jtag etc)
If I for some reason soft brick and get it back to stock is everything going to be perfect or is there a possibility for damage?
It might sound like a dumb question but...
Click to expand...
Click to collapse
JTag repair will restore it to stock, no issues... A soft-brick means signs of life but won't boot properly, or a bootloop, etc... Fix it with flashing, and no ill effects...
Excellent thanks.
Its good to know how to
A) avoid a brick
B) fix a brick
and now
C) if you brick and fix you can go back to normal.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well my phone used to freeze a lot so I decided to try a new ROM.. I flashed Cyanogen, several builds, until I ended up picking the Nightly build. The phone kept working for about 12 hours before it went black and dead. It's totally dead. Should I assume that it's hard bricked? Assuming that it was hard bricked, does it have to die right away or is it possible for it to keep working for a few hours?
This is the Sprint S3 US version. Not the International section.
If your phone doesn't turn on at all, doesn't vibrate when you hit the power button either the battery is dead or the device is hard bricked. If it does anything else all like those mentioned it's not bricked.
Remember search is your best friend, Have a great day!
edfunkycold said:
This is the Sprint S3 US version. Not the International section.
If your phone doesn't turn on at all, doesn't vibrate when you hit the power button either the battery is dead or the device is hard bricked. If it does anything else all like those mentioned it's not bricked.
Remember search is your best friend, Have a great day!
Click to expand...
Click to collapse
Well sorry for posting in the wrong section..
Anyways, could it be a faulty power circuit/mobo?
What you described sounded more like "sudden death syndrome" a hard brick is always caused by flashing the wrong files. Check for the method to fix without a JTAG but you need to find the international "debrick image" to write to an sd that could work if it is bricked
Sent from my SPH-L710 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!
Forum Noob here, I was using my Galaxy S3 (Wind) and all of a sudden the screen went black and it turned off. Something similar had happened a couple hours before and the phone wouldn't turn on through the power button so I simply took out the battery and put it back in and it worked. Then when it happened for a second time I tried the same thing but to no avail the phone stayed dead.
So far I've tried:
Using another GS3 Stock Battery
Tried getting into download and recovery mode
Tried charging it (I do know that the battery is charging since I checked it on another phone. The red light is not on but it turns on when I take out the battery and then plug it in. After 20-30 seconds of battery insertion the red light goes away and is completely unresponsive all that time)
Tried Keeping the battery out of the phone for a couple of hours (Suggested by a friend)
Also Tried connecting it to a pc, and it only connects when I keep the battery out. When it finally connects it tries to install drivers for "QHSUSB_DLOAD" but fails.
I have no idea what's happening to my phone and I would like to get it fixed as soon as possible. After some searches I've narrowed down to either a Hard Brick or a Sudden Death Syndrome but it doesn't completely match with all the characteristics of either problem. I greatly appreciate any help and I would like to know what exactly the problem is and what my best viable option.
Thank you.
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
TheSoldierDude said:
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
Click to expand...
Click to collapse
Only reason I suspect the power button is you mentioned you couldn't get it to turn on using the button, but removing/replacing the battery worked. And it can work perfectly and then fail out of nowhere. So goes when you have plastic parts! But lots of people have had issues with this button recently.
Wasn't trying to convince you that was the problem, just letting you know it's a potential culprit.
But if you think it's ok, then try to use KAsp3rd's debrick thread and see if that gets you going again.
Sent from my SGH-T999 using Tapatalk
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
ssingh0247 said:
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Click to expand...
Click to collapse
Since they are seeing the QHUSB_DLOAD (which is technically a hard brick) a simple USB jig wouldn't work, however they can attempt to use my recovery method. It's at no cost and just takes some time and reading.
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Remove and reinsert battery. If it turns on by itself, you are probably right about the button.
Sent from my SGH-T999N using Tapatalk
You're Right I believe
tomy1986.nt said:
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
Click to expand...
Click to collapse
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Nope
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Nothing happens at all.. its completely dead, simply a paper weight.. a very bad one of sorts
TheSoldierDude said:
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Click to expand...
Click to collapse
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Thank you
Perseus71 said:
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Click to expand...
Click to collapse
Nope.. xD 3 months off warranty, and yes I got it repaired from Samsung.. Motherboard was replaced, $300.. :|
Thanks to everyone helping out though
I can't believe I didn't know about these forums before :good:
Samsung Galaxy S3 died-black screen
my s3 gone black,its not getting turned on.there was red light(indicator) for some time before i tried to restart but when i tried to switch on. it's completly died,i am not getting any display.i have purchased in UK, unlocked using it now in India.some guys told me it would because of motherboard issue (if i replace motherboard it in India will it work normal,is there any possibility?)how to fix it?please give me some solutions.
screen not working
Hi all. In my s3 the red light is flashing fast. Also the screen is black but it works. Also the phone works and I can receive phone calls. Every few minutes the screen turns on for a sec and goes off again. I can feel the vibration when I touch the screen. Pkease help me.
Thanks
hard bricked
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
syben7 said:
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
Click to expand...
Click to collapse
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yea, sry about that, was actually trying to get 10 posts in so that i could go post in the dev thread concerning this, gonna check out the method you sent, thanks a ton man!
STUCK
Well my s3 (us cellular r530u), has no boot but has a red led without the battery. Is there a debricking procedure? And if so..where can i find a debrick file.
There is for us. But you need to be in Sprints forums. Theres nothing for your device here, and I dont know what they have over there. Good luck though!
Sent from my SGH-T999 using Tapatalk