• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Sudden death precautions ?

S

silvercats

Well-Known Member
If I update my i9300 to the latest version, am I safe? I don't have warranty in this country as I bought it from a different country.


If I do not root it,am I safe?

If I root this later, Can it cause problems.?

what is the reason for sudden death?
 
silvercats said:
If I update my i9300 to the latest version, am I safe? I don't have warranty in this country as I bought it from a different country.


If I do not root it,am I safe?

If I root this later, Can it cause problems.?

what is the reason for sudden death?
Click to expand...
IIRC, the most recent update dealt with that and fixed it...not sure tho as I am on a different carrier.

Root or no root, the SDS had to do with the processor I believe. So rooting won't fix it.

Aside from the SDS, rooting it won't affect the phone if done correctly, it will void your warranty. (I base that comment on Verizon's policy)
 
I think SDS only affects the i9300 and 4.1.2 (official or 'based on' official s3 4.1.2) "fixes" it. Its to do with how the internal memory is used.
Are you on 4.1.2 yet Silver?
 
The SDS was caused by a faulty sector in NAND RAM, when Androud attempts to access/write to this sector (or block of sectors) the NAND would corrupt and hard brick the device.
The fix was addressed a while ago.
Only handsets with a specific chipset were affected in the first place.
A) if you don't have the affected chipset, you don't have to worry. (there's an app in the play store you can download to check)
B) evan if you do have that chipset, any 4.1.2 update on any stock / aftermarket ROM should fix it.
The fix itself as issued by Samsung was to re-format a portion of the NAND RAM to include the affected sector (or block) and make it inaccessible to the Android OS - hense nothing can attempt to write/access to it and cause the corruption leading to the brick state.

Hope this clears things up a little.
 
so its RAM's fault? Some people say that 4.1.2(which I am on now) is supposed to fix the error. Samsung didn't confirm it !
 
So if the fix was by samsung.. did they make it available for 3rd party devs? (Cyanogen etc) (just out of interest in how developer-friendly Sammy are)
 
If I update to Cyanogen mod, will I be completely safe? Also is there a time period for this to happen? like after 6 months of usage or something?
 
silvercats said:
If I update to Cyanogen mod, will I be completely safe? Also is there a time period for this to happen? like after 6 months of usage or something?
Click to expand...

Read the link Sherlock posted. It tells you which version of cm is safe. In fact it tells you everything you need to know
 
No one really knows for definite what the trigger is. It is believed that the trigger is the wear levelling tried to write to a bad sector or block but its not really possible to put time scales on it. Just make sure you are safe.
 
I have a 10 month old S3, and last Nov I had to send it to the service centre for the sudden death problem. The guys replaced the mother board. Now after 4 months, over the last week, my phone switches off by itself everytime i lock the screen. Yesterday I had to start my phone nearly 10-15 times over a 10 hour period. Very frustrating. Did a complete reset (factory). Still of no use.
Any assistance would be helpful before I hand it over to the service care.
Thanks
Shivram.K
 
Id return it if its turning off so much. Aparently freezing is the "fix" that came with 4.1.2. The phone freezes to save itself from SDS. I dont know if switching off is the same thing or another fault
 
are u on the latest firmware? If u are not try updating it once and see if it helps. Also try a factory reset otherwise im sorry to say u will most likely have to give it back to sammy.
 
You must log in or register to reply here.
Back
Top Bottom