When to call the Galaxy S3 dead

Forums › Android › When to call the Galaxy S3 dead

GeorgeNZ

29 posts

Geek
+1 received by user: 2

Topic # 198297 3-Jul-2016 21:34

After some confusion when turning on the phone with a low battery warning and flashing screens, upon restarting the phone stuck with the Samsung logo staring at us.

In recovery mode clearing the cache didn't fix the problem and a factory reset didn't either. Of note there was a message that never left the scene of the crime at the bottom that said E:failed to mount /efs (Invalid argument)

Tried Kies and connected by choosing the Firmware Upgrade and Initialization, which worked but still stuck at the Samsung screen. (Tried twice)

Tried two versions of Odin and flashed stock firmware which worked we know because the boot was different with no splash screen, then stopped at the Samsung logo again.

Any suggestions that someone with limited tech can try, or is the phone a lost cause.

Thanks

Samsung Galaxy GT-I9300T

Stu

Hammered
5085 posts

Uber Geek
+1 received by user: 1072

Moderator

Trusted

Lifetime subscriber

Reply # 1585359 4-Jul-2016 01:22

Casting my mind back, I seem to recall that once the EFS has been damaged/corrupted/lost/whatever, that unless you have a backup, that it's rather impossible (or was that just unlikely?) to recover/repair your phone. A quick Google of the issue may shed some light.

Keep calm, and carry on posting.

Brendan

703 posts

Ultimate Geek
+1 received by user: 67

Trusted

Reply # 1585360 4-Jul-2016 01:27

One person supports this post

It looks like your efs partition is stuffed. And therefore your phone is stuffed. Sorry about that.

There is no fixing it unless you had a backup of it, and that is usually only done if you had previously ROOTED the device. Fixing the EFS partition would involve flashing a valid IEMI number to it, in it's encrypted form, and they do not allow that because if you could just DO that, you could clone anyones phone out there, and receive their phone calls and messages. And that upsets people.

You then have to ask WHY it is corrupted. Is it some system software that stamped all over it? Not unheard of. Playing around with ROOT access can do it also. Or is the memory chip in that area faulty? In the end it does not matter, as the cure is the same:

You could get a new motherboard for it from trademe or etc, and put that in and get a working phone. But I'm guessing you'd be better with a whole new modern phone.

michaelt

423 posts

Ultimate Geek
+1 received by user: 8

Reply # 1585365 4-Jul-2016 02:11

I have an S3 (i9300) motherboard I could sell you, if you want to fix it. Pretty sure it's working fine, but I can refund if it's not. Could replace it for you as well if you're in Auckland,

GeorgeNZ

29 posts

Geek
+1 received by user: 2

Reply # 1585382 4-Jul-2016 07:35

Thanks for the replies and confirmation. The phone was the last I handed down from my own upgrades over the years so had done good service, now time to move on.

Challenge now is to sort out a good mid priced phone the daughters budget can afford.

Oblivian

2873 posts

Uber Geek
+1 received by user: 308

Reply # 1585403 4-Jul-2016 08:56

Wont help if your EFS is screwed, but Flickering screen and low battery just happened to mine (well, has been getting worse at low battery). Then I realised I can spin it around when sitting on the desk. Seems the batteries in these like to die, and almost severely. Mine was swollen and heated up something chronic in my hand the day I noticed as the battery was being used for a fair bit of screen time before the flickering at 40% and shutdown occurred. :)

Nice new OEM one from BPtech pending charge..