Sudden death syndrom for Galaxy note 2 and S3

Louis40

Hi,

Any one heard about the SDS for Note 2 and S3? some of my surroundings have warned me about this and had their s3 and note 2 completely died. I downloaded eMMC check and apparently my note 2 is on the way.. we need to find a solution before this happens..

Roudykh

My note 2 died two weeks ago because of this

mesa177

This post on xda suggests updating the firmware from 4.1.1 to 4.1.2. But if the problem persists, I think the only solution is to replace the PCB of the phone with a VTU00M chip that is flashed with the latest firmware revision. Naturally, backup all your data before doing either.

Louis40

I have updated mine to 4.1.2 for Poland, but the EMMC gives me that the chip is insane and there is a sudden death.
Below are the details:
Type: VTU00M
Date:09/2012
CID: many figures..
FwRev: 0xf1

If there is any flash to be done pls let me know..
Thx

AvoK95

Louis40 wroteI have updated mine to 4.1.2 for Poland, but the EMMC gives me that the chip is insane and there is a sudden death.
Below are the details:
Type: VTU00M
Date:09/2012
CID: many figures..
FwRev: 0xf1

If there is any flash to be done pls let me know..
Thx

Try flashing to the latest 4.1.2 update build

Louis40

AvoK95 wrote
Louis40 wroteI have updated mine to 4.1.2 for Poland, but the EMMC gives me that the chip is insane and there is a sudden death.
Below are the details:
Type: VTU00M
Date:09/2012
CID: many figures..
FwRev: 0xf1

If there is any flash to be done pls let me know..
Thx
Try flashing to the latest 4.1.2 update build

Fine but which one is the suitable..
No one has the same issue?

AvoK95

If you're not rooted, check for a new software update.

Louis40

I'm not rooted and checked for software update with Kies and no updates..

AvoK95

Louis40 wroteI'm not rooted and checked for software update with Kies and no updates..

Download Odin 3.07 here
Download the latest 4.1.2 Official Jelly Bean Samsung Firmware from here (Considering you got the N7100 version. Check from Settings>About device If you don't have the N7100, do not follow this guide as it will brick your phone
UNINSTALL SAMSUNG KIES AS IT WILL CONFLICT WITH ODIN AND CORRUPT THE FLASH

Extract both of them.

- Go into download mode on your phone by holding the Volume Down, Center and Power buttons together. If the phone turns on, let go of the power button while still holding the others.

- Connect it to your computer. Make sure Samsung Kies isn't installed on that PC as it conflicts with Odin
- If your PC doesn't recognize the device, download and install the Samsung drivers from here
- Now, on Odin the ID:COM section should be yellow and the “added” message should be there.
- Up next, click on “PDA” and select the update file (the .tar one). DO NOT TOUCH/TICK/OR UNTICK ANYTHING AS THERE IS A RISK WHERE IT CAN PERMANENTLY CORRUPT YOUR DEVICE AND MAKE IT USELESS
- Click on “start” and in the end you should see the “pass” message displayed (Do not remove it until you see "Pass")
- Unplug the USB cable as you are done
- Turn it off again by removing the battery
- Boot into recovery mode (press on Volume Up, Home and Power buttons).
- From there wipe the system
- You can make a wipe by selecting “wipe data factory reset” and “wipe cache partition”. (By using the Volume Up and Down buttons and using the center button to select)
- Then, choose “+++go back+++” and “reboot system now”.
- The first boot might take longer than usual; don’t panic there is nothing wrong with your phone

Cheers!

Louis40

Thx i will try it tonight and will let you know..

Louis40

Hi i just did the maneuver but it gave the same warning.. best way is to sell it before it crashes..
thx anyway

yasamoka

I believe that app gives the warning due to the chip model itself. If it detects the presence of the insane chip, then it gives a warning. This doesn't mean that you are likely to brick, as the patch would be active with 4.1.2.

I have a similar issue with my Note 1. Notes can brick if ypu wipe the eMMC, due to the MMC_CAP_ERASE command causing corruption. Stock ICS kernels suffered from it, CM kernels did not, and new stock JB kernels and custom "brick-free" kernels do not face the issue as they have disabled that command.