Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
I guess this is an option also: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
mcappleman said:
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
Click to expand...
Click to collapse
Call verizon and they will send you an replacement. If its thats far gone theres no way they can check to see if its been modded.
Me too!!!!
Message removed
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
fr8cture said:
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
Click to expand...
Click to collapse
But I've had it for 20 days now and their website says they don't allow returns or replacements after 14 days. Or is this different because it randomly died?
Also. I don't get insurance on my phones because they always would charge me $10 or more a month and then when the phone died they would charge half the cost of the phone just to get it replaced!
Honestly I think I may just send it to MobileTechVideos.........
Unless I still have a chance with Verizon. Hard decision............
I'm pretty sure the 14 day timeframe is for refunds on the purchase. Most electronics have some sort of manufacturer's warranty.
Have you tried to get it into download mode? volume down, then home, then power, Hold them all together until it boots into download mode? Do this while plugged in maybe?
samsung s 3
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
You really give your phone number out to strangers like that?
Sent from my SCH-I535 using Tapatalk 2
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
mcappleman said:
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
Click to expand...
Click to collapse
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
silver04v said:
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
mcappleman said:
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
Click to expand...
Click to collapse
If you can't get into download mode then yea, most likely I guess or the battery died. I just didn't see that you said you tried to get into download mode.
Sent from my Synergized vzw S3!
Glad you got this fixed! Also i think its a 30 day replacement or swap for another phone if you don't like it. Thats what i was told when i got mine.
I have a n8000 running stock european firmware 4.1.3 rooted using HOA method, TWRP recovery, has binary count 0.
in the past 4 days it kept shutting down for no apparent reason, so I fixed permissions and factory reset/wipe then rerooted..
still kept shutting down.. I didnt have time to look further into it. but today at 100% battery life, my poor note was sitting in my passenger seat, but when I picked it up I realized that it took a **** and completely died, no boot no recovery no odin, nothing just a black screen, no powaah! plugged it into the wall and nothing, plugged into pc and nothing!
so ok now! I know its F**KED, im gonna send it in. but I would love to know, wtf happened man? I took care of this thing and yeah I never OC'd.
also forgot to mention. I dont consider myself a pro but im not a complete idiot when it comes to android dev.
Hi there.
I have a friend that had a galaxy s3 mini till a few days ago when supposedly the board got fried up from an official OS update. His phone was never rooted.. and minding one or two scratches.. it was a "virgin" phone.
He said that one day he had his phone turned off and when he turned it on, it displayed the message that it was updating but then a few % in, it completely shut down and since then he was never able to turn it on again. He tried charging the battery, switching battery, pressing those combinations of buttons to get into download and recovery mode and nothing.
He went to a unofficial store and also to a samsung store and both believed it was the board that fried up. Even though the guys from samsung never admitted, the guy from that unofficial store said it wasn't the first samsung he was getting that week with the same problem after that latest update. He really believed it was the update that fried it. Oh well.. if it's true or not, we don't know. Either way, since they didn't take responsibility and wasn't a way to really know if it was samsung's fault or just a somewhat old phone problem.. my friend got the s7 (yeah.. samsung got money for this xD..) and we were wondering if there is anyway he can recover at least some of the internal data of the dead phone? It doesn't turn on at all.. so don't know if that's possible. Can someone please clarify me that?
Google shows a lot of results about data recovery but the tools used for that are fishy imo and say that they are used to recover data from dead phones but require the phone to be in recovery or download mode which is even fishier right? I mean.. if it's dead.. xD
Any help on this would be very much appreciated!
Hi !
A device which can`t be powered on it is a dead device , the local storage can`t be accessible so its data can`t be recovered
Cheers !
Oh.. those are indeed sad news. But oh well..
Thank you for replying!!
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Silicon Knight said:
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Click to expand...
Click to collapse
I'm assuming you used Kingroot to root it? It's a common issue for Kingroot to cause a bootloop.
Typically, this is fixed by re-flashing the stock firmware but you have to get it to connect to PC to do it, and that's only if the stock firmware is even available.
Sent from my SM-S903VL using Tapatalk
Okay so it may be a little redundant but I'm gonna start from the beginning I bought a pixel 2 about a year and 1-2 months ago on Amazon I immediately knew I needed root and a custom ROM so I put linage on it as it was at the time the only ROM being updated I then switched to 2 others pixel dust and it was great but was missing a few features so I tried another one I'm still on and terrified to turn my phone off I'm not blaming the ROM
I went to bed the other day charging my phone got up on 100 scrolled Facebook for maybe 10-15 and it was on 78 I figured maybe I was on it longer than I thought or maybe it was too bright idk but I thought ok I'll go out and take less than 5 and I'll be back to charge it but I never got a chance the screen went black and never came back on. I plugged it in for an hour and nothing. I tryed PC it didn't show up at all no device manager nothing so I took the screen off and unplugged the battery (hesitantly) as I didn't know if it would ever work again I then used my heat gun on it set at about 445 (I don't know if it's bad solder just trying something new) I then put it back together and when I did it was in qqm 9008 (hard bricked) so I unplugged the battery again and it reboot to recovery before rebooting to the os.
Now I'm scared on what to do as I don't want the device to die incase it won't turn on again cause I lost work and can't afford another but I need to know if there's anything I can do to ensure that it doesn't happen long enough for me to flash a new ROM incase it's the ROM so please anyone with this phone that can help me out even a little would be great