yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] spotlight79:
Hi guys!

Just wanted to share my pain, hope you won´t mind...

This is what happened:

Yesterday I came home from work, pulled my S3 out of my pocket and saw it was turned off. I tried to turn it on, but no luck. The phone was dead! Tried pulling the battery out, leaving it alone for more than 10 mins... tried to boot it into recovery - nothing. Tried the download mode - no signs of life at all. It was just a shiny brick! Putting it on charger didn´t help. No reaction, no led flashing, NOTHING! And just half an hour before everything was fine.

I was running the latest official AOKP build the last couple of days, so I really don´t believe that the software has something to do with it since I didn´t flash anything yesterday. The other question is now if the Samsung guys will notice that the phone wasn´t running stock software and that the warranty is actually void... I hope they won´t! :p But if they too won´t be able to turn it on, I guess they won´t!

I took the phone to the Samsung service center this morning and didn´t receive any feedback yet. As soon as I know something I´ll share it.

Did anyone happen something similar to this?
[Galaxy S III General] fahadsul3man:
awww sorry to hear that , i am sure its covered in warranty
[Galaxy S III General] XenomorphXx121:
I don't understand the warranty thing, if the phone is dead and not due to you installing a Rom or kernel or modding it then can't really see any reason to refuse fixing or replacing it.

If however it was because of the reason that you did install things then I can see how the warranty is void.

Hope you get it seen to
[Galaxy S III General] Jcossack88:
In 2013, rooting won't be illegal. Too bad it happened to your device, that is just bad luck.
[Galaxy S III General] s0undless:
i don't know where you live but i'm pretty sure rooting is not illegal anywhere it just voids your warranty. removing the simlock is an entirely different story
[Galaxy S III General] kaynpayn:
Has happened to me too, 1 week after purchase (got stuck on the Samsung Galaxy SIII on boot). Got mine replaced right there and then but i'm left wondering about the quality of the phone. I get it that there are always problems with every product but i see so many people reporting the same lately i start thinking it may be chronic. Some component failing or some batch where something went wrong..

Sorry to hear that, they are an absolute pain in the ass with warranty in my country. They didn't even want to replace mine because the dude was claiming the back of my phone was slightly scratched (i wasn't, even) and they are quite anal about modded phones but, wish you the best of lucks!
[Galaxy S III General] ch0ka:
Could you please be a little bit more precise? Is this a rumor or a new law to get passed?
[Galaxy S III General] budx:
exaclty the same happened to me. just in the middle of the day i realized that my sg3 was off. tried to turn it on but it didnt react. later at home i tried to charge but had the same bad result.

my biggest problem was, that it was rooted and running on a custom firmware since they tell you at every point, that you lose your warranty doing that...

after several hours of trying / searching and reading i became sure, that it would be an hardware fault and sent it to a local cellphone-support center.

they needed about 2 weeks to find out the problem, order a new main board, fix it and luckily didnt care about my custom firmware. they even updated it to the latest offical 4.1!

2 day ago i got it back and became happy - in this 2 weeks i realized how much i depend on this little thing ;)

soo... i feel with you on this and good luck!
[Galaxy S III General] MJW:
It is for the US, YMMV. Droid Life Article/
[Galaxy S III General] spotlight79:
Thanks! :)

This is actually what I´m thinking... that the motherboard died... I just hope that tomorrow or on wednesday, I will at least get informed what is wrong with it... Don´t even dare to think how long it will take to have it again... And yes... I depend on it too!!! Maybe even too much!!! LOL
[Galaxy S III General] nhariamine:
Stop flashing whatever roms you don't know ,or u will suffer a sever consequence "i'm talking about hard brick" .READ FORUMS AND TUTORIALS
[Galaxy S III General] Isadora:
Mine completely died just about 2 weeks ago, stock rom but rooted. Dropped it off at a service centre and got it back today with a shiny new motherboard (and JB)... As long as it's properly dead, they can't tell what's on it as the only way to revive it is to change the innards.
[Galaxy S III General] spotlight79:
Dude, I´m not a noob, what happened has nothing to do with software.
[Galaxy S III General] Gustopher:
I entirely accept that this is a generalism and as such is bound to attract a hoard of punters contradicting it, but in many years on these boards I can recall few if any instances where repairs have been refused due to the installation of non-standard ROMs. It is sensible for manufacturers to discourage the practice - XDA-Developers is plagued with ill-informed noobs charging off to do things beyond their technical capabilities without doing adequate research - but I suspect a refusal to play the game would be counterproductive.

That said, I would always be inclined to revert back to a stock ROM and clean up a bit if I had the option before doing a return for repair.
[Galaxy S III General] LemonPlusTea:
its the same thing that happened to my phone running cm10 about 2 days ago.

sent my phone in for repairs to samsung. they probably won't be able to find out it was modified. probably needs to change hardware to even boot the phone up.

disappointing experience. :/
[Galaxy S III General] devadatta:
by any means, did you played with the clock levels?

oc/uc?
[Galaxy S III General] Kremata:
It's not illegal. You won't go to prison or even get sued (Android is not Apple). It just void your warranty.
[Galaxy S III General] LemonPlusTea:
just got back my phone.

They fixed it even though I rooted & had custom rom installed.

Guess they couldn't tell as the phone couldn't even start up. hahah.

Now restoring the latest nandroid I had. :D
[Galaxy S III General] PetritH:
Nice to here that pal, hope this will not happen to anyone in future... this is my 2nd GS 3 (first broken due to Barca loss vs Madrid in August) and never had hardware problems.
[Galaxy S III General] spotlight79:
So... here I am again...

Got my phone back yesterday. And it was the motherboard so they replaced it.

Man was I happy to have my phone back! But... my hapiness didn't last long.

When I came home I had to discover that now the gyroscope is not working. No autorotate whatsoever, no games that require the accelerometer...

Means they just replaced the mother board, flashed the latest firmware but didn't bother to test the device.

So tomorrow I'm going back to the service center and I'm going to yell my soul out at whoever responsible...

Unbelievable!

(screen rotation is checked, I tried calibrating the gyro, pulling out the battery, etc...)

This is such a disappointing experience... I'll think twice before buying a Samsung phone again...
[Galaxy S III General] fahadsul3man:
that sucks :(

---------- Post added at 08:15 AM ---------- Previous post was at 08:09 AM ----------

this thread is about motherboard dieing not about hard brick ......:p
[Galaxy S III General] CROrION:
I can se you are from Croatia (so am I).

I work with phones so I'm very interested where did you send your phone for repair?
[Galaxy S III General] Obagleyfreer:
9 times out of 10 when I read about an S3 suddenly dying it has been running CM10 or an AOKP build.

This can't be a coincidence, I'm yet to read about an S3 dying suddenly on an Official Samsung ROM.
[Galaxy S III General] Isadora:
Mine was on stock ROM (not a leaked one, just Sammy's official ICS) when it died. It was rooted with cf root but that's it. Several other people were on stock ROMs too...
[Galaxy S III General] g0t-cheeri0s:
My friend's s3 died two days ago. Completely stock and only two months old. Turned itself off and wouldn't turn back on. No charging LED, no USB connection. Dead.
[Galaxy S III General] drraptor:
Please post the details in this thread http://xdaforums.com/showthread.php?t=1993044&page=94
[Galaxy S III General] mortuus82:
The phone dies because something on the mainboard breaks, this happend me too 3 months ago.. good thing it goes on warranty but on swedens biggest droid forum there is starting to be more reports of sudden deaths of sgs3 and the first sign of this to anyone is sudden restarts, thats a sign it will soon break it happen same for me and 5 days later.. total dead.. :(

And like i said it doesnt matter if u are root or not its a hardware issue, maybe a capacitator or whatever are bad from the start on the mainboard and some breaks down after some months of use so its def a problem for many phones.
[Samsung Galaxy Mini] Nilabhra:
SO here's the long story short :

I installed minisense 4 rom on my mini.then tried to install cyanmobile X.for doing the latter I wiped data + cache + dalvik cache. then rebooted the system forgetting to recover the minisense 4 back from the nandroid backup I did. now my phone's bricked. I can't get into downloading mode (nothing happens if I press vol down + home +power ). I presses vol up + down + hom+ power . that installed the drivers...and odin detects is as "Android" not GT-S5570. I have found similar threads but nothing has worked so far. I still haven't used the USB jig method yet though..... Please help me out here!! :crying:

by the way I needed to recover minisense 4 because the installation of the cyanmobile X (update-CyanMobile-eXperience-Blade-20120721-Release.zip) didn't install...gave a status 7 ( when later pointed out by a member here it was for blade no galaxy mini [obviously] )

Thanks in advance! :angel:
[Samsung Galaxy Mini] Nilabhra:
please some one!! :'(
[Samsung Galaxy Mini] Galaxy_Rohit:
Since, u have no Download Mode, so, if odin is somehow detecting ur phone, try flashing stock firmware that way only. By the way, odin only show yellow com port mapping box indication as soon as you connect ur phone to pc. It shows model no. on its title bar due to that ops file you've selected(regardless of whether you've physically connected ur device to pc OR NOT). Also, use Galaxy Mini mobile drivers on ur pc(ur drivers might also be corrupt).

Otherwise, take it to Service Center & get it repaired there.:thumbup::thumbup:

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
hey thanks Rohit!... I downloaded the samsung galaxy mini firmware for india and also the ops file requited. it set them up in odin but odin get's stuck at "set up connection" and another question : the firmware S5570DDKQ7_S5570ODDKQ6_S5570DDKQ7_HOME.tar.md5 came with a dll file "SS_Dl.dll" where do I use this dll file ?
[Samsung Galaxy Mini] Galaxy_Rohit:
Try another USB port or even another firmware. I too was stuck at setup connection when flashing Gingerbread DDKT3, so I went for FROYO & it worked. But u can also try another USB port(to connect ur phone).

Don't touch/delete that "SS_DL.dll" file. Just use that firmware package file(.tar.md5) and place it in One Package field in Odin. Place ops file, and click start.

Done!!:):)

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
okay thanks again rohit! okay so where do I get the froyo firmware ? samfirmware doesn't have it sadly :( .I have tried differnt port and isntalled/uninstalled the driver. and if can please tell me what exactly is wrong wiith my phone? I wiped the data that means it's like a PC without an OS right ? so why don't I get the boot screen? :rolleyes:
[Samsung Galaxy Mini] Galaxy_Rohit:
GT-S5570 DXKB1 FROYO 2.2.1

http://www.mediafire.com/?c32k2du6gwmpe2n

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
I have been searching that for 20 mins and you got it? where di you get the link!! and thanks a ton! sure hope it works!
[Samsung Galaxy Mini] Galaxy_Rohit:
ur welcome...;):)

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
it's not downloading rohit !! "Repair Download" comes up... :( (which obviously down't repair anything)
[Samsung Galaxy Mini] Galaxy_Rohit:
I've just tried. It's downloading bro!!. From phone, use UC browser & long press download & select "save as"(3G/Wifi preferred).

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
ya it's downloading...hope it works.. :fingers-crossed:
[Samsung Galaxy Mini] Nilabhra:
:( nope.... still stuck at setup connection in froyo... :'( what's wrong with it?
[Samsung Galaxy Mini] Galaxy_Rohit:
First, try switching it on now... Do u see that screen indicating

"phone-----/!\-----computer". If u see this, then remove battery re-insert it & go for download mode. It should enter now.

OR try this...

Place all files correctly. There r usually four files in Froyo fw. The correct order is(see the stating filename):-

OPS:- TASS_v1.0.ops

BOOT:- APBOOT....

PHONE:- MODEM....

PDA:- CODE....

CSC:- CSC...

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
okay...trying...
[Samsung Galaxy Mini] Nilabhra:
what goes in EFS ? the kernel ? and trid that method... the phone's disconnecting from pc when I try to power up, nothing else happens (yellow box disappears and usb connection sound plays in pc )
[Samsung Galaxy Mini] Galaxy_Rohit:
Remove usb cable, then switch it on. Is phone responsing now? Post a screenshot(if possible.)

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
no phone is completely unresponsive as before but these are the set of observations I have made :

when usb is connected

1 ) if I press the power button + home + vol up + vol down - it connects to pc and installs drivers

2 ) if I press just the power button + home vol down - it disconnects

3 ) if I press just the power button it disconnects

4 ) the battery heats up If I leave it connected to PC

I haven't observed anything else...otherwise phone's just as if there's no battery
[Samsung Galaxy Mini] Galaxy_Rohit:
O.K. Try flashing Froyo or Gingerbread again or do this (with least luck...)

1. Remove sim/sdcard & battery.

2. Connect ur phone to pc with odin ready.

3. Press download mode combo keys(without battery)

4. Insert battery while holding keys.

See if something happens(download mode) or if odin detects ur phone, etc.

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
nope, phone's not detected at all by this method
[Samsung Galaxy Mini] Galaxy_Rohit:
Hey bro!! Did you've USB debugging enabled before all this.

Also, acc. to one XDA guy, when it stuck at setup connection, unplug usb cable & plug it back.(it worked for him)!!

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
ok will try that...and yes USB debugging was enabled ....
[Samsung Galaxy Mini] Nilabhra:
nope...ain't working that way either..
[Samsung Galaxy Mini] Nilabhra:
oh no! now the pc isn't detecting it anymore! I have tried uninstalling the drivers and installing, different ports and all.... it's so f'd up!
[Samsung Galaxy Mini] Nilabhra:
okay fixed that by revoing kies and then reinstalling everything again. but still same problem
[Samsung Galaxy Mini] Galaxy_Rohit:
Disable kies & antivirus & even firewall... They sometimes interfere with odin.

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
nope... still not working, if my phone's so dead then how come my PC and odin detects it?
[Samsung Galaxy Mini] Galaxy_Rohit:
Battery out...

VolDown+menu+power...

Battery in...

I've a doubt. Does that firmware has 4 files?? Coz, one of these is bootloader.

Still got setup prob., try diff fw. or I'll give.

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
the gingerbread firmware has a one file tar.md5. but the froyo has five files, boot,modem, csc, code and kernel...
[Samsung Galaxy Mini] Galaxy_Rohit:
Kernel...?? For Froyo, there need 2 b only & only 4 files:- boot,modem,code,csc & no other. Leave EFS field(don't touch it).

Extract all Froyo files in one single folder. Remove any gingerbread fw folder/files(if exist) before flashing Froyo.

Or you may try this fw:-

S5570 Froyo DXKA8

http://mediafire.com/?871j3ddp1xyfiy2

Sent Via XDA™ Premium
[Samsung Galaxy Mini] hsay:
I don't know if you have noticed your mistake but here it is you installed cyanmobile for blade and not for mini so obviously what happened had to happen
[Samsung Galaxy Mini] Nilabhra:
yes I know!.. so what has happened?
[Samsung Galaxy Mini] F4uzan:
Great here's your fault :

#tree of problem
## main root problem : flashing %cyanmobile% for blade on tass device (galaxy mini)
% exact problem : flashed up and mocked up your mini by flashing froyo rom. why don't you flash gingerbread ?
*exit
#created by problemlog.sh
[Samsung Galaxy Mini] Galaxy_Rohit:
It doesn't matter whichever u flash first. Don't u read it b'4 that the guy is having setup connection prob. Atleast, help him rather than counting faults, he has already mentioned!!

Sent Via XDA™ Premium
[Samsung Galaxy Mini] tietganFTW:
You said earlier that ODIN was stuck at setup connection. May I ask if there is anything showing on the screen on your phone? If there isn't anything, your phone is probably bricked and try using a jig method.

You can follow this link for a guide on what to do at different scenarios:

http://xdaforums.com/showthread.php?t=1929525
[Samsung Galaxy Mini] Nilabhra:
nope, shows nothing on screen....ok I will se if I can make a jig.....
[Samsung Galaxy Mini] F4uzan:
Go to SSC. It's your only way, rather than exploding your Mini with bigger problem. Also act stupid there, if they ask you why it doesn't boot say this "i put alarm and then it never wake up again". If they ask you for root, ROM, CWM say "No, i don't know"
[Samsung Galaxy Mini] Nilabhra:
err....my phone's out of waranty....
[Samsung Galaxy Mini] tietganFTW:
Try doing a jig or a RIFF JTAG.
[Samsung Galaxy Mini] Galaxy_Rohit:
Did u tried that 2nd firmware??...(see post #30)

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
Ok will try that...damn exams came up all of a sudden... :crying:
[Samsung Galaxy Mini] fintaneduffy:
i too also have this same problem, nothing seems to be working, the only thing that works is the beep noise you get when you plug a usb device in.

has there been a fix for this yet?
[Samsung Galaxy Mini] Nilabhra:
^ don't think so....
[Samsung Galaxy Mini] Jeffrianz:
Try This Tutorial

http://db.tt/9yiv6xl0

Sent from my GT-S5570
[Samsung Galaxy Mini] fintaneduffy:
have tried the usb jig, made it today, all connections seem fine set to 301k but when i plug it in nothing happens.

any ideas?
[Samsung Galaxy Mini] Nilabhra:
nope haven't tried it..but dont think it's gona work...
[Samsung Galaxy Mini] fintaneduffy:
i made up one today but didnt do anything, didnt work. has anyone succesfully done this with a mini?
[Samsung Galaxy Mini] Nilabhra:
they guys in youtube are the only ones I guess... :P I gave to service centre...don't know what they are gonna charge me for it...
[Samsung Galaxy Mini] Galaxy_Rohit:
I'm quite sure, they gonna tell u that they replaced motherboard of ur device which costs pretty high!!!

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
yeah! that's the problem! they say the motherboard replace thing to every customer with smart phones!
[Samsung Galaxy Mini] fintaneduffy:
yea if they charge for a new motherboard, its not worth sending it in, mines out of warranty ant it only cost me €60 from new.

hopefully someone may have a "real fix" pretty soon
[Samsung Galaxy Mini] Nilabhra:
yep! they called up! said my mother board is burnt out!! >_<
[Samsung Galaxy Mini] Galaxy_Rohit:
There "IS" a real fix if u don't wanna goto service center & that's Riff Jtag:cool:. The thing is, whether YOU know how to use it:rolleyes:.

Sent Via XDA™ Premium
[Samsung Galaxy Mini] Nilabhra:
so after getting back my mobile do you think I should go for cyanmobile X ? works good for mini? I found the gallery in minisense to be buggy
[Samsung Galaxy Mini] Nilabhra:
http://xdaforums.com/showthread.php?t=1983437 help me out here please!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hitmantb:
This happens randomly and because I promised my wife Android is now stable/bug free, it makes me really look bad because it is her first Android phone. I googled and it looks like other people have similar problems with S3 as well, with no definitive solution.

Her dial pad will not stay on during the call consistently, literally as soon as she tries to press 1 to hit customer service during call, 2 for support , 1234 for voice mail password etc, her screen goes off and does not let her type. This happens about 50% of the times.

Is this a hardware problem or software problem? It is awful!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] accrews2001:
I have experienced this issue as well. It doesn't happen often to me with but when it does it's very frustrating. I also don't know what the issue is, but would love to hear if someone has an idea.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
You're holding it wrong haha.

Seriously though, make sure your hand doesn't get near the top of the screen while trying to type a number because the proximity sensor will think that is your face and shut off the screen.

Edit: Also, nothing is bug free, not even the iPhone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
lol she is blocking the light to the ir sensor at the top of the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elementaldragon:
Yep.... i've experienced it, too, and it's exactly as they're saying. If you have your hand positioned in such a way where your fingers are essentially pointing down the screen, it's likely putting your hand in a position where the proximity sensor feels that it might be your head approaching the phone, and shuts the display off.

It's nothing to "look bad" about... it's just simply how proximity sensors work. Some phones have them set up a bit more sensitive than others. As long as she isn't basically doing a "hunt and peck" style of trying to type while in a call, there shouldn't really be an issue with it. It's not even like it's something when Apple was saying "You're holding it wrong" in regards to their previous Antennagate issue. It's just the proximity sensor reacting to less light due to hand position.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] accrews2001:
Hmm, I'll have to pay attention when/if it happens again to see if that's what was going on. I don't usually point at the phone with my index finger. I usually hold it where my palm is on the right side of the phone and enter numbers with my thumb.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elementaldragon:
I've noticed that sometimes when i'm doing things on the phone, i'm more prone to hold it in one hand, and press stuff with the other. Most notably when using the dial pad while on a call to go through menu's and such. Just seems a little less likely to hit something else by accident that way. I dunno. But simply keeping my hand down and away from the proxy sensor seems to be the cure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superm1:
Does she have a case or a screen protector that might be misinstalled and covering the proximity sensor? It might be more sensitive consequently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spoonerdee:
Don't forget there is a timer on the screen that will shut it off, even if you are on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itsme_4ucz:
If its the proximity sensor, you can try my app proximity screen off and select "enable during call only". It will force screen to turn on/off when its uncovered/covered respectively.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hitmantb:
I don't get this issue nearly as often when using her phone to make calls with calling card. It may be the way she is holding her device, I will try to explain she's holding it wrong. I always hold my device from the bottom, she seems to hold from the top/center from her iPhone days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deoxlar:
Also check if your screen is set to turn off after 15 seconds of inactivity. The sensors are at the top of the phone, to the right of the word Samsung. Make sure there's nothing blocking that