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
Related
have a sprint galaxy s 3 here.
someone tried to flash an international rom therefor flashing the gsm stuff.
i cant access download mode at all however i did install the QHSUSB_drivers.
now with odin 3.07 the .com box will not light up however on previous versions of odin for ex odin v1.85 the .com box will light. im trying to flash the cdma bootloader for the sprint version and it doesnt fail just hangs at setup connection.
any ideas?
vabeachfc3s said:
have a sprint galaxy s 3 here.
someone tried to flash an international rom therefor flashing the gsm stuff.
i cant access download mode at all however i did install the QHSUSB_drivers.
now with odin 3.07 the .com box will not light up however on previous versions of odin for ex odin v1.85 the .com box will light. im trying to flash the cdma bootloader for the sprint version and it doesnt fail just hangs at setup connection.
any ideas?
Click to expand...
Click to collapse
Have you tried following the steps on this thread http://forum.xda-developers.com/showthread.php?t=1727171 ? Also they may be able to help you out more than the QA section.
Edit: Sorry posted the wrong link.
yes ive tried that way.
any ideas welcome
did you switch to download mode/
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
^^^^He cannot get to dl mode it is hard bricked.
And to the op-
Unlike some devices where this was a savior it is worthless to us. You are hard bricked. Go get some jtag as this mode won't help you
I tried for a few days to talk to this phone in that mode.Using everthing from odin to cdma workshop to qpst to emma. Nothing will do it trust me
It was a customer phone i dont brick phones.
Sent from my Galaxy Nexus using xda app-developers app
vabeachfc3s said:
It was a customer phone i dont brick phones.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
At least its not urs then. Well be happy ur not the owner of a shiny doorstop and let the customer know its a paperweight and they need JTAG.:good:
All he have to do is call Samsung and they will replace it you have a year factory warranty as long as theres no physical damage. They send the phone fast. I did it four times already don't waste your time looking for solution just tell them it won't boot just turned off and won't start that's all i said. You don't have to have insurance either.
Sent from my SPH-L710 using XDA Premium App
bonebeatz1234 said:
All he have to do is call Samsung and they will replace it you have a year factory warranty as long as theres no physical damage. They send the phone fast. I did it four times already don't waste your time looking for solution just tell them it won't boot just turned off and won't start that's all i said. You don't have to have insurance either.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
Really? You've done this four times? I'd be interested in if anyone else has had such luck? Seems like they would try to turn on the device or figure out whats wrong when they get it back. Thats awesome though!
thatisandwas said:
Really? You've done this four times? I'd be interested in if anyone else has had such luck? Seems like they would try to turn on the device or figure out whats wrong when they get it back. Thats awesome though!
Click to expand...
Click to collapse
I can vouch for that cause I've had to swap out my 1st. Maybe not due to that particular reason, but still, if it doesn't light up they gets frustrated and swap time.
Sent from my SPH-L710 using xda premium
bonebeatz1234 said:
All he have to do is call Samsung and they will replace it you have a year factory warranty as long as theres no physical damage. They send the phone fast. I did it four times already don't waste your time looking for solution just tell them it won't boot just turned off and won't start that's all i said. You don't have to have insurance either.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
I used to have an Epic 4G Touch and yesterday accidentally flashed a kernel for it on my S3. I was left with a beautiful pebble blue coffee table piece. I started to freak out because I couldn't power on or anything. Long story short, I purchased my phone less than 14 days ago so I took it back to the store. The technician took a look at it, couldn't power it on and they gave me a replacement phone, no questions asked!!
I promise if you hard bricked hell or even soft bricked you can get it exchanged from Samsung as long as it's been less than a year and no water damage or cracked screen .I really think they don't look into all the rooting stuff they just install new software in the phone and send it right back out to someone else which works for me.
If you go threw your carrier avoid it they ask to much question call Samsung and i sware they will send you a new or refurbished phone but a working one and that's all you can ask for and i didn't pay a dime the box they send you to send your phone is prepaid by them i just put my bricked phone in there then dropped it off to ups. I will say this two times i wasn't at home and ups left the damn phone in the box right on my door step than goodness no one stole it.
Sent from my SPH-L710 using XDA Premium App
So I want to start off saying my device is not bricked. Just have have a question about knowing If a phone is bricked or if a hardware issue. I know the difference between a soft brick and hard brick but can a hard brick only happen after flashing some zip. Or can it still happen randomly without flashing or even entering the recovery in over a week.
I ask this cause it has happened to me before. Where one day my A100 wouldnt turn on. Not even the boot screen. The only sign of life was the light by power button while charging.
SO is it possible still to hard brick if nothing was flashed in over a week or most likely a hardware issue?
I thought the same thing happened to my note 2 yesterday. But all it was, was this damn new update draining my battery so fast. I thought somehow it was bricked lol
ANy answer to my question will be thanked
Yes, a device can get hard bricked without flashing or messing around with the recovery. That will most likely be a hardware failure issue.
But as you found out with your GN2, that the problem can be something else. That is where the art of troubleshooting becomes important.
That's not called hard brick. That's call device failure because of age or defect.
Sent from my SGH-T889 using Tapatalk 2
whatsitsnamenow said:
That's not called hard brick. That's call device failure because of age or defect.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Hard brick is the effect. Device failure (hardware failure) can be a cause of a hard brick. Not always, but can be a cause.
Hard brick is a non-recoverable bricked device (no matter how the device became non-recoverable bricked).
Hey everybody,
I rooted my phone a couple weeks ago and one day it just pooped out. I researched a bunch on google etc and found some things to try but so far no solutions.
Model: SGH-T999 T-mobile s3 (Used CF-Auto-Root and Odin for rooting)
Problem: After the phone pooped out, I was unable to enter recovery mode. I could enter dl mode however it crashes at variable intervals. So I bought a jig figuring maybe that would help but it still crashes in dl about 5 seconds later. Any suggestions?
Everything that I have found on the internet has been were people can usually get it into dl mode and keep it there or they cant get there at all even with a jig. Any help would be appreciated. Thanks!
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I just tried the kasperd brick fix and it didnt work. It still crashes at variable times and I cannot get it into download mode long enough to do anything. I tried a jig and it also still crashes. Any help would be great. Thanks!
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
It starts and then crashes. After awhile it might make it to the animation with the blue wave forming around the words samsung, but usually it crashes on the Samsung Galaxy SIII logo in the beginning. Also when I put it into download mode it crashes anywhere from 1-5 seconds after. When I try to get into recovery mode it crashes almost right away when the blue words are at the top left of the screen.
Also when I put the battery in it tries to boot on its own without me pressing power button, and sometimes it tries to reboot after it crashes and turns off without me pressing anything. Also after it crashes I usually cannot just press the power button to try and power it up again so I have to take the battery out and put it back in.
When I was doing the Kasperd brick fix I used the T999 debrick image. How do I know if I have a different variant of the T999. I saw that some people had T999v and T999N. What are those?
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
Ok I just see T999 on the label.
How can it be a hardware issue when I never dropped the phone or anything. I was just thinking it was because I rooted the phone because it happened about a week after I rooted it. It was working one minute and then a couple hours later when I took it out of my pocket it was off and I tried turning it on and all that stuff started happening. I will definitely check the power button though. Thanks for the help.
Also another piece of info to add. When I plug it in to charge both the battery charging symbol and red light will sometimes turn on and then it crashes/goes black similar to what happens when trying to power up the phone. Not sure if that helps at all. Thanks!
If my phone was hard bricked I wouldnt be able to turn it on at all correct? Im trying to figure out if I will need to get this thing jtagged or something in order to get it working again.
phillycheese917 said:
How can it be a hardware issue when I never dropped the phone or anything.
Click to expand...
Click to collapse
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Aerowinder said:
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Click to expand...
Click to collapse
True, however I just find it odd that I rooted the phone and a week later it happened. That is why I am leading towards an issue involving that and not hardware damage.
If it was a problem with rooting, it would have gone south right away. Many people are having these button issues recently. And you don't have to drop it, like aerowinder said, but you do use the button right? Moving parts wear out. Hardware fails. That's really all there is to it. While I could be wrong in my diagnosis, I don't think that will prove to be the case here.
Sent from my SGH-T999L using Tapatalk 4
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
KAsp3rd said:
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
Click to expand...
Click to collapse
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
I took the back casing off to see if the button is getting stuck or anything, but all the mechanics look normal.
phillycheese917 said:
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
Click to expand...
Click to collapse
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
KAsp3rd said:
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
Click to expand...
Click to collapse
Thanks guys! I found a good thread on here about the S3 sudden death thread. Im going to read up on that and see what I can do. It was just tough to find since I was thinking it was bricked but the descriptions for this power button sudden death thing sound spot on. Hopefully I will be able to get everything back in working order.
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
Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.
majicmazo said:
Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.
Click to expand...
Click to collapse
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?
Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.
Not actually my device
Aerowinder said:
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?
Click to expand...
Click to collapse
Perseus71 said:
Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.
Click to expand...
Click to collapse
Yea thats what i was afraid of, I actually don't know the version it was on prior, to be honest this isn't my device I actually run a small time craigslist base business generally rooting peoples phones and installing roms and fixing softbricks, someone asked me if I can help them and i thought it would be a simple softbrick issue until I actually got a hold of the phone and saw this issue now i think its hardware problem but i thought id ask my good friends at xda before completely giving up
[