Samsung Galaxy SIII Discussion and Owners Thread

Forums › Android › Samsung Galaxy SIII Discussion and Owners Thread

1 | ... | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | ... | 376

524 posts

Ultimate Geek

#740929 7-Jan-2013 11:00

fallen: My S3 died couple of weeks ago, didn't check the HW revision when the phone died. Got the phone back last week, they replaced the mainboard and the new HW revision is MP 1.500 (16gb, 2Degrees)

There's heaps of us with a 2Degrees 16GB.. so its just wait and watch for us I suppose...

lokhor

2858 posts

Uber Geek

Trusted

#740945 7-Jan-2013 11:37

Mine is 2degrees 16GB, same with my fiancee. we both have MP1.100 HW Rev

So far neither has bricked. I flashed the XXELLA bootloaders though so hoping I won't be affected.. I'll probably flash hers in the next few days.

All comments are my own opinion, and not that of my employer unless explicitly stated.

mjb

996 posts

Ultimate Geek

Trusted

#740946 7-Jan-2013 11:39

MurrayM: I hope this isn't the start of the "sudden death"!

It will be. My condolences.

contentsofsignaturemaysettleduringshipping

Johnnyrs

18 posts

Geek

#740950 7-Jan-2013 11:44

http://www.samsungupdate.com/tag/galaxy-s3-dying

mjb

996 posts

Ultimate Geek

Trusted

#740951 7-Jan-2013 11:45

lokhor: My HW Rev is MP 1.100

Wondering if this means I am susceptible to the sudden death issue.

It's not just the HW Rev, it's also the emmc chip - grab the emmc superbrick checking app (ignore the result for that, it's for the S2), but it does give you the emmc chip model and fw rev.

VTU000M, 0xf1 I think, are the chips to worry about. Don't hold me to that.

contentsofsignaturemaysettleduringshipping

mjb

996 posts

Ultimate Geek

Trusted

#740955 7-Jan-2013 11:49

Johnnyrs: http://www.samsungupdate.com/tag/galaxy-s3-dying

Which links to http://www.samsungupdate.com/android-how-to/new-update-fix-galaxy-s3-sudden-death-and-exynos-security-exploit.

Be interesting to know what their research was - if it was reading sammobile, or other news and forum sites, then they've made a pretty bold assertion.

There is no consensus around whether XELLA fixes the bug.

contentsofsignaturemaysettleduringshipping

Damager

2125 posts

Uber Geek

#740959 7-Jan-2013 11:51

I'm already on an ELLA custom rom, does this mean it already has the bootloader fix?

- Telstra HTC Touch Pro2 - Energy ROM WM6.5.5 20 Oct/Cyanogen Mod Froyo 2.2 - R.I.P
- AT&T Galaxy S Captivate 16GB on XT (now with brother)
- Samsung Galaxy S2 on XT- Runs ICS 4.0.3 Resurrection Remix 9.2
- Business Hours - Work In The Electricity Industry, After Hours - DJ/Turntablist - Will Scratch Vinyl For Free'
- What's next??? S3?

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

lokhor

2858 posts

Uber Geek

Trusted

#740964 7-Jan-2013 11:54

Damager: I'm already on an ELLA custom rom, does this mean it already has the bootloader fix?

Most custom roms don't include a bootloader, you need to flash it separately using Odin on a PC to be sure.

All comments are my own opinion, and not that of my employer unless explicitly stated.

lokhor

2858 posts

Uber Geek

Trusted

#740967 7-Jan-2013 11:58

mjb:
lokhor: My HW Rev is MP 1.100

Wondering if this means I am susceptible to the sudden death issue.

It's not just the HW Rev, it's also the emmc chip - grab the emmc superbrick checking app (ignore the result for that, it's for the S2), but it does give you the emmc chip model and fw rev.

VTU000M, 0xf1 I think, are the chips to worry about. Don't hold me to that.

:( here's my eMMC chip details:
Type: VTU00M
Date: 04/2012
CID: too long to type
FWRev: 0xf1

I got my S3 at release so it's more than 6 months old now.

All comments are my own opinion, and not that of my employer unless explicitly stated.

mjb

996 posts

Ultimate Geek

Trusted

#740971 7-Jan-2013 11:59

lokhor: :( here's my eMMC chip details:
Type: VTU00M
Date: 04/2012
CID: too long to type
FWRev: 0xf1

I got my S3 at release so it's more than 6 months old now.

Mine is the same, and I've just ticked up 200 days. waiting patiently for the symptoms.

contentsofsignaturemaysettleduringshipping

webup

545 posts

Ultimate Geek

#740972 7-Jan-2013 12:00

My 32gb class 10 Sandisk from MyMemory has started failing and giving loads of errors in my S3 so im sending it back.

Ive been reading lots of complaints online with people claiming Mymemory.co.uk are selling fake cards and to use H2testw 1.4 to test the card to see its speeds etc.

webup

545 posts

Ultimate Geek

#740975 7-Jan-2013 12:04

mjb:
lokhor: My HW Rev is MP 1.100

Wondering if this means I am susceptible to the sudden death issue.

It's not just the HW Rev, it's also the emmc chip - grab the emmc superbrick checking app (ignore the result for that, it's for the S2), but it does give you the emmc chip model and fw rev.

VTU000M, 0xf1 I think, are the chips to worry about. Don't hold me to that.

just checked an mine is VTU000M, 0xf1

Is there something we are meant to do when we have these?

Phone still runs fine although i noticed some slight lag lately to get screen back on after pressing power or home button.

mjb

996 posts

Ultimate Geek

Trusted

#740986 7-Jan-2013 12:14

webup: Is there something we are meant to do when we have these?

Just hope. ;)

contentsofsignaturemaysettleduringshipping

Damager

2125 posts

Uber Geek

#740989 7-Jan-2013 12:21

webup:
mjb:
lokhor: My HW Rev is MP 1.100

Wondering if this means I am susceptible to the sudden death issue.

It's not just the HW Rev, it's also the emmc chip - grab the emmc superbrick checking app (ignore the result for that, it's for the S2), but it does give you the emmc chip model and fw rev.

VTU000M, 0xf1 I think, are the chips to worry about. Don't hold me to that.

just checked an mine is VTU000M, 0xf1

Is there something we are meant to do when we have these?

Phone still runs fine although i noticed some slight lag lately to get screen back on after pressing power or home button.

Check again, as mine's VTU00M. Looks like you have 1 too many 0?

Damager

2125 posts

Uber Geek

#740990 7-Jan-2013 12:23

mjb:
lokhor: :( here's my eMMC chip details:
Type: VTU00M
Date: 04/2012
CID: too long to type
FWRev: 0xf1

I got my S3 at release so it's more than 6 months old now.

Mine is the same, and I've just ticked up 200 days. waiting patiently for the symptoms.

Mine is dated 05/12

Not sure whether to wait.. or flash that bootloader fix? Got mine off trademe.. Might have to hit up the seller for a receipt or something, or can providing serial number somewhere confirm the retailer?

1 | ... | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | ... | 376