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
Related
Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??
oscarito619 said:
Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??
Click to expand...
Click to collapse
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.
gallaxxeess said:
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.
Click to expand...
Click to collapse
Yeah well people here are advised to send their bricked device to Samsung all the time because Samsung won't know the difference... I don't see how that is any different from what this guy is proposing...
Sent from my SGH-T989 using xda premium
It sounds like you have a stuck or broken power button. Try doing what the guy above said to do and after you return it to stock, send it to Samsung for a replacement.
If you have insurance on your phone just tell them you lost it, but you would have to pay the copay
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
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.
Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.
You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app
LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.
For the record I did search the forum (pretty quickly) and didn't find what I was looking for so I hope I'm not reposting the same issue.
So I was flashing the Slim Bean 4.2.2 rom to my galaxy s3 using goomanager and i think my phone is hard bricked.
In goomanager it allows you to select multiple zips to flash, and I'm pretty sure they flash in the order they are listed. Well i planned to flash the Slim-i9300-4.2.2.build.6-OFFICIAL (the rom itself), Slim_Gapps.4.2.2.build.6 (google apps for the rom), and Extras.4.2.2.build.6 (extras specific to the rom) for the Slim Bean rom from the slimroms site.
I had the Extras.4.2.2.build.6 zip listed first then accidentally pressed the flash button and without thought confirmed my actions in the pop up window (Yes i'm an idiot). So it rebooted and went through some script then my phone went black.
It wont go into download mode (home, power, vol down), it won't display anything on the screen, and it wont power on. My computer recognizes it and shows that it is connected. I don't know if that will do anything it terms of fixing it on my own? I haven't read up on bricked phones too much but i'm pretty sure its hard bricked.
Sooooooo, first off does anyone have any suggestions as to what i should do?
-If i were to take it to a Sprint store what would they say? I've had it for a year and I don't think i have any warranty (granted i know rooting my phone would technically void it anyways). If it doesn't power on or do anything could I say it turned off in the middle of the 4.1.2 OTA update and resulted in its current state?
-Would a usb JIG boot my phone into download mode and fix my problem?
-Is a jtag service my only option?
-If it is jtag does anyone know a place around the Louisville, KY area that does this sort of thing? I google searched but didn't find anything local.
-If not i guess mobiletechvideos is my best option?
Any help would be much appreciated. I'm in dire need of this phone to be fixed as I start my new job in a 2 weeks and need it for obvious communication reasons.
DrewFerg11 said:
For the record I did search the forum (pretty quickly) and didn't find what I was looking for so I hope I'm not reposting the same issue.
So I was flashing the Slim Bean 4.2.2 rom to my galaxy s3 using goomanager and i think my phone is hard bricked.
In goomanager it allows you to select multiple zips to flash, and I'm pretty sure they flash in the order they are listed. Well i planned to flash the Slim-i9300-4.2.2.build.6-OFFICIAL (the rom itself), Slim_Gapps.4.2.2.build.6 (google apps for the rom), and Extras.4.2.2.build.6 (extras specific to the rom) for the Slim Bean rom from the slimroms site.
I had the Extras.4.2.2.build.6 zip listed first then accidentally pressed the flash button and without thought confirmed my actions in the pop up window (Yes i'm an idiot). So it rebooted and went through some script then my phone went black.
It wont go into download mode (home, power, vol down), it won't display anything on the screen, and it wont power on. My computer recognizes it and shows that it is connected. I don't know if that will do anything it terms of fixing it on my own? I haven't read up on bricked phones too much but i'm pretty sure its hard bricked.
Sooooooo, first off does anyone have any suggestions as to what i should do?
-If i were to take it to a Sprint store what would they say? I've had it for a year and I don't think i have any warranty (granted i know rooting my phone would technically void it anyways). If it doesn't power on or do anything could I say it turned off in the middle of the 4.1.2 OTA update and resulted in its current state?
-Would a usb JIG boot my phone into download mode and fix my problem?
-Is a jtag service my only option?
-If it is jtag does anyone know a place around the Louisville, KY area that does this sort of thing? I google searched but didn't find anything local.
-If not i guess mobiletechvideos is my best option?
Any help would be much appreciated. I'm in dire need of this phone to be fixed as I start my new job in a 2 weeks and need it for obvious communication reasons.
Click to expand...
Click to collapse
"Slim-i9300-4.2.2.build.6-OFFICIAL" that is the international model version of the ROM. Flashing International ROMs hard brick your phone. So yes, you do have a hard brick. As to taking it to sprint, Idk if they'll do anything for you especially if you have no insurance or warranty. Sorry bud
Well your problem is not that you flashed in the wrong order. Your problem is that you flashed a rom from the International S3 (i9300) not the sprint SPH-L710. You attempted to turn your Sprint phone into an International S3. This flashed completely different partitions onto your device. JTAG is the only way to fix it. They have to open the device and repartition everything. Mobiltech is the way to go. My advice in the future is if you don't find the rom in the Sprint Galaxy S3 forums do not flash it.
Sent from the future via Xparent Green Tapatalk 2
solis888 said:
"Slim-i9300-4.2.2.build.6-OFFICIAL" that is the international model version of the ROM. Flashing International ROMs hard brick your phone. So yes, you do have a hard brick. As to taking it to sprint, Idk if they'll do anything for you especially if you have no insurance or warranty. Sorry bud
Click to expand...
Click to collapse
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
DrewFerg11 said:
Is JTAG service the only way to fix it/will that fix it?.
Click to expand...
Click to collapse
JTAG is in fact the only way to repair it. Yes guaranteed it will be fixed.
Sent from the future via Xparent Green Tapatalk 2
DrewFerg11 said:
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
Click to expand...
Click to collapse
Just do more research next time before flashing. And as the person above said, don't flash anything that isn't on the sprint GS3 forums.
DrewFerg11 said:
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
Click to expand...
Click to collapse
Unfortunately yes you are hard bricked and it sucks. JTAG will fix it Google it there are good services out there for about $60 and week or so turn around.
If you pay for insurance you could also take it to sprint and tell them it won't boot and they should replace it for a deductible. Some will call this fraud but the way I see it if you pay for insurance it is there to cover mistakes. You didn't mean to brick it just like some one who dropped it in a pool didn't mean to ruin their phone.
Sent from my SPH-L710 using xda premium
Thanks for the quick response everyone. I really appreciate it. I feel dumb. I usually do my research, but I was bord and a spur of the moment action got me in trouble this time.
I guess I'll run to the sprint store tomorrow and see what they can do, if anything.
If they can't do anything, mobiletech it is! It looks to be a reliable site. Will my phone be active on the sprint network still after the JTAG? or will I have to do anything to it? I also assume I will get all the text messages and what not that my phone is currently incapable of receiving now?
Any thing else I should know about the JTAG or my phones hard bricked state before I go ahead with it since we are on the subject and I don't want this to happen again.
DrewFerg11 said:
Thanks for the quick response everyone. I really appreciate it. I feel dumb. I usually do my research, but I was bord and a spur of the moment action got me in trouble this time.
I guess I'll run to the sprint store tomorrow and see what they can do, if anything.
If they can't do anything, mobiletech it is! It looks to be a reliable site. Will my phone be active on the sprint network still after the JTAG? or will I have to do anything to it? I also assume I will get all the text messages and what not that my phone is currently incapable of receiving now?
Any thing else I should know about the JTAG or my phones hard bricked state before I go ahead with it since we are on the subject and I don't want this to happen again.
Click to expand...
Click to collapse
I doubt you will get any texts, sprint is not saving to deliver them later. Unless your using Google Voice. Your phone will be up and running rom flashed but it won't activate until you log into it with your google ID, just like when you get in the box brand new.
Sent from the future via Xparent Green Tapatalk 2
My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
*Update* Went to a cell repair shop, turns out its actually the power button that needs replacing and this is why the phone continually turns off and on and never reaches passed the logo screen. Apparently it's common for the power button to stop working or get all messed up on the gs3, if you have not rooted your phone or played around with the software the power button may be the cause of it not passing the logo screen and your phone might actually not be bricked
me too
KeeKeeB said:
My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
Click to expand...
Click to collapse
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.
keviinricoy said:
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.
Click to expand...
Click to collapse
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed
Have you tried another battery. ...thats what I would try. Also make sure all your ports are clean and debris free.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KeeKeeB said:
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed
Click to expand...
Click to collapse
Yes i tried my friends battery, this sadly did not work.
recovery
Have you tried to boot into the phones stock recovery and clear it ? Or how about odin a stock rom ? Just trying to brainstorm, but I seriously do not think your phone is toast. I would try seaching these ideas and see if you have any luck....otherwise search for how to recover a bricked phone for your carrier...the same method might work to get you up and running again???
same thing happening to me...i can boot into recovery/download mode but only for 2-3 seconds and then the phone reboots itself...all started after I dropped it from my sofa earlier today. any suggestions anybody?
turns out it was the power button that was malfunctioning for me..got it repaired and now its working fine..