I think ; in your case some emmc partitions are corrupted,exept recovery.
And that's why u r able to boot in recovery but emmc unable to mount corrupted partitions..
**Ultimate GS3 sudden death thread**
- Thread starter Obagleyfreer
- Start date
And that's why u r able to boot in recovery but emmc unable to mount corrupted partitions..
Hi,
I'm wondering if mine is a sudden death case. I bought my S3 (I9300) in August 2012. Always updated to the latest firmware, even earlier than UK firmwares were out and currently on the latest 4.3 stock firmware. Rooted (cf-auto) with stock recovery and kernel. Used it continuously for 2 years and again for the past few weeks as my new phone was stolen. It was on and working yesterday, left it at home for around 8 hours and it is dead now. No response to connecting the charger or trying to turn it on. It has a power button issue, so it went into a bootloop just before I was leaving. I sorted it out and allowed it to boot normally before I left.
From what I read sudden death shouldn't happen with this firmware? Or are there any developments on that? It is clearly out of warranty and I don't care for a wiped phone. The data can be useful but I suspect it is lost?
Thanks for your insight and help.
I'm wondering if mine is a sudden death case. I bought my S3 (I9300) in August 2012. Always updated to the latest firmware, even earlier than UK firmwares were out and currently on the latest 4.3 stock firmware. Rooted (cf-auto) with stock recovery and kernel. Used it continuously for 2 years and again for the past few weeks as my new phone was stolen. It was on and working yesterday, left it at home for around 8 hours and it is dead now. No response to connecting the charger or trying to turn it on. It has a power button issue, so it went into a bootloop just before I was leaving. I sorted it out and allowed it to boot normally before I left.
From what I read sudden death shouldn't happen with this firmware? Or are there any developments on that? It is clearly out of warranty and I don't care for a wiped phone. The data can be useful but I suspect it is lost?
Thanks for your insight and help.
sudden death
Hey,
so here's my problem:
It suddenly went off.
When i try to boot it, it only shows the white "Samsung Galaxy s III" logo.
Can boot into recovery and into download mode.
Tried already to wipe cache and dalvik cache.
Also when it's off and i plug it in it shows the battery load/search but not the loading icon.
Any ideas how to save it?
Hey,
so here's my problem:
It suddenly went off.
When i try to boot it, it only shows the white "Samsung Galaxy s III" logo.
Can boot into recovery and into download mode.
Tried already to wipe cache and dalvik cache.
Also when it's off and i plug it in it shows the battery load/search but not the loading icon.
Any ideas how to save it?
Last edited:
ive got a similar S3 here...
will go into download mode, and recovery mode, so can/have delete cache, parition, and delvik, and tried diferent/basic roms, which seems to install with no errors...
but boots up to the Samsung animated logo, and stays there !
what else could i try ? is there a way of formatting/reflashing boot-loaders, or the other partitions ??
anyhelp would be great ....
Google it "i9300 PIT File"
Flash it in Odin under Bootloader Tab...
Mate...do some search on google how to flash it in Odin..
Hope you a good luck..
@miniminus if you flash only the PIT file like this guy wrote you, your phone will be dead forever.
tetakpatalked from 1+One
tetakpatalked from 1+One
i did have a good search around, an found this thread
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367/page10
an as you can read, i did a ful format, and re-install of "factory" files ...
of which it has altered some things, dont get as many error about files/locations.
but am still having "error cannot mount /efs"
which KaosMaster suggests is a EFS partition error/curruption, that can only be done via a proper box/lead
here http://forum.xda-developers.com/showpost.php?p=61716165&postcount=95
cheers for any help thou ! .. MIck ...
I have a S3 GT-I9300 that might be experiencing the sudden death syndrome.
it happen just a hour ago, everything was running normal, battery is 80% charged, then all of a sudden it turn off on its own.
i have try all kinds of permutation of turning the device back on, but it won't power.
i try plugging it to a computer via usb and still won't power on.
Took battery out press the power button to discharge all power in the phone, waited 10 mins, plug it back in, and still won't turn on.
Anyone can verified whether it is the sudden death syndrome, and is there any way to revive the phone?
it happen just a hour ago, everything was running normal, battery is 80% charged, then all of a sudden it turn off on its own.
i have try all kinds of permutation of turning the device back on, but it won't power.
i try plugging it to a computer via usb and still won't power on.
Took battery out press the power button to discharge all power in the phone, waited 10 mins, plug it back in, and still won't turn on.
Anyone can verified whether it is the sudden death syndrome, and is there any way to revive the phone?
Fix SDS Reboots with TRIM
Hi all,
I have a i9300 with insane chip (SDS - Sudden Death Syndrome). When doing a clean install of a new ROM I always had random freezes or reboots. I have always provoked them with DFG (Dummy File Generator). And after running it a few times, I never (or only a long time after) had issues. The DFG workaround always seemed to work for me.
But not this time....
Environment:
Symptoms:
When running DFG, at some point the phone suddenly reboots (without shutting down). Sometimes it was hung in a bootloop afterwards (i exited after letting it loop about 6h). Sometimes it rebuilds the cache on startup (Optimizing App 1 from 100...). I considered everything of this as normal behavior when having the SDS.
The strange thing this time was: I normally had to run DFG for three or four times and had a stable system afterwards. This time (yesterday) the phone rebooted randomly every time on each and every run. I tried over 30 times and never got a stable system. Sometimes it crashed at 30 %, sometimes at 100 %, then again at 15 %. Totally random.
Thinking this was odd, I googled a lot and found nothing specific. Until I had the idea...
Idea:
What if deleting the DFG File after the reboot doesn't work as expected? What if the storage cells get scrambled by over provisioning and somehow the one bad cell is used again and again and can't be masked as bad by the kernel, because it has to be used somehow...
Solution:
After running DFG, letting it reboot and deleting the File (by Settings -> Apps -> Dummy File Generator -> Delete Data) I ran the TRIM command with Trimmer (fstrim).
When I run DFG afterwards it runs all the way through until the last bit and then suddenly reboots. So I guess the kernel uses the bad cell as last resort. IT ****ING WORKS FINALLY!
To verify my success I repeated the Cycle (DFG -> Reboot -> Delete -> TRIM -> DFG) three times. My phone only reboots when writing the very last available bit.
So I really hope this helps you if DFG doesn't work as expected, like with my phone.
tl;dr
When Dummy File Generator (DFG) does not seem to help you do:
Greets
Beneter
Hi all,
I have a i9300 with insane chip (SDS - Sudden Death Syndrome). When doing a clean install of a new ROM I always had random freezes or reboots. I have always provoked them with DFG (Dummy File Generator). And after running it a few times, I never (or only a long time after) had issues. The DFG workaround always seemed to work for me.
But not this time....
Environment:
- Samsung Galaxy S3 International (i9300) with insane Chip (SDS)
- Wiped -> Flashed three-parted Stock ROM with PIT in Odin 3 -> CF Auto-Root -> Flash TWRP 2.8.6.1 -> Wipe everything -> Clean Flash
- ROM: BlissPop-v3.6-i9300-OFFICIAL-20150714-1120 (Reported as 1031 under about the phone)
- Kernel: boeffla-kernel-4.0-alpha7-CM12.1-NG-i9300 (With MGH CM12 INTELLIACTIVE V3 Profile)
Symptoms:
When running DFG, at some point the phone suddenly reboots (without shutting down). Sometimes it was hung in a bootloop afterwards (i exited after letting it loop about 6h). Sometimes it rebuilds the cache on startup (Optimizing App 1 from 100...). I considered everything of this as normal behavior when having the SDS.
The strange thing this time was: I normally had to run DFG for three or four times and had a stable system afterwards. This time (yesterday) the phone rebooted randomly every time on each and every run. I tried over 30 times and never got a stable system. Sometimes it crashed at 30 %, sometimes at 100 %, then again at 15 %. Totally random.
Thinking this was odd, I googled a lot and found nothing specific. Until I had the idea...
Idea:
What if deleting the DFG File after the reboot doesn't work as expected? What if the storage cells get scrambled by over provisioning and somehow the one bad cell is used again and again and can't be masked as bad by the kernel, because it has to be used somehow...
Solution:
After running DFG, letting it reboot and deleting the File (by Settings -> Apps -> Dummy File Generator -> Delete Data) I ran the TRIM command with Trimmer (fstrim).
When I run DFG afterwards it runs all the way through until the last bit and then suddenly reboots. So I guess the kernel uses the bad cell as last resort. IT ****ING WORKS FINALLY!
To verify my success I repeated the Cycle (DFG -> Reboot -> Delete -> TRIM -> DFG) three times. My phone only reboots when writing the very last available bit.
So I really hope this helps you if DFG doesn't work as expected, like with my phone.
tl;dr
When Dummy File Generator (DFG) does not seem to help you do:
- Run Dummy File Generator -> Generate(FULL) on internal memory
- After finished or reboot, delete Data at Settings -> Apps -> Dummy File Generator -> Delete Data
- Run TRIM command with Trimmer (fstrim)
- Repeat until your Phone only freezes / reboots when DFG filled nearly 100 %
- Enjoy your stable ROM
Greets
Beneter
Last edited:
So what you are saying is that the first post solution is a security measure against SDS, and once it happens, no software/kernel updates will bring it alive?
My device seems to charge/power up but only via recovery mode and through PC USB. It won't charge in the socket. eMMC app says that I have an insane chip.
Hello.
I too have a problem with the sudden death sundrome. I have given away my phone to a service, where they performed a clean install of an 4.3 Android. After about two months the problem has returned. It looks like this: after hitting the function button on the right side of the phone id reacts as it would be pressed and held (shows reboot/turn off menu). Something like this sometimes also happens after pressing the HOME button.
Reboots are random or sometimes they being triggered by plugging/unplugging a charger or a headphones. Reboot looks like regular SDS- SAMSUNG logo->offline->Samsung logo->offline and it goes like that sometimes for a couple minutes.
Ps. Sorry for my bad English- I'm from Poland.
Cheers.
I too have a problem with the sudden death sundrome. I have given away my phone to a service, where they performed a clean install of an 4.3 Android. After about two months the problem has returned. It looks like this: after hitting the function button on the right side of the phone id reacts as it would be pressed and held (shows reboot/turn off menu). Something like this sometimes also happens after pressing the HOME button.
Reboots are random or sometimes they being triggered by plugging/unplugging a charger or a headphones. Reboot looks like regular SDS- SAMSUNG logo->offline->Samsung logo->offline and it goes like that sometimes for a couple minutes.
Ps. Sorry for my bad English- I'm from Poland.
Cheers.
Please... help... My I9300 Death after a white screen with points...
I read solutions in which Odin is used, but if the phone does not start, how to proceed?....
Replace the eMMC necessary, mandatory and only solution?
Thks...
I read solutions in which Odin is used, but if the phone does not start, how to proceed?....
Replace the eMMC necessary, mandatory and only solution?
Thks...
Amazing talk on this issue at 34C3!
If you are interested in GS3 and eMMC hacking you will love this talk.
Oran Avraham gives great history, explanations and hacking details on this problem.
Talk: 34C3 - eMMC hacking, or: how I fixed long-dead Galaxy S3 phones.
https://media.ccc.de/v/34c3-8784-emmc_hacking_or_how_i_fixed_long-dead_galaxy_s3_phones
Original youtube link:
https://www.youtube.com/watch?v=JrsJvlij6V4
Improved audio link:
https://www.youtube.com/watch?v=OY7OlY0OW2Q
If you are interested in GS3 and eMMC hacking you will love this talk.
Oran Avraham gives great history, explanations and hacking details on this problem.
Talk: 34C3 - eMMC hacking, or: how I fixed long-dead Galaxy S3 phones.
https://media.ccc.de/v/34c3-8784-emmc_hacking_or_how_i_fixed_long-dead_galaxy_s3_phones
Original youtube link:
https://www.youtube.com/watch?v=JrsJvlij6V4
Improved audio link:
https://www.youtube.com/watch?v=OY7OlY0OW2Q
Rather late in the game, but I have had a look at some eMMC firmware images for the chips commonly found in S3s.
KLMAG4FE4B-B002 (MAG4FB, commonly found in I9305) and KMVTU000LM-B503 (the infamous VTU00M) share the same firmware! MAG4FB 0xFC and VTU00M 0xFC differ only by the last 16 bytes of the firmware image, and MAG4FB 0xF7 is binary identical to VTU00M 0xF7.
So, MAG4FB 0xF1 is likely vulnerable to SDS! (assuming it even exists - I've only ever seen 0xF7 and 0xFC, but some people on other forums are reporting 0xF1)
KLMAG4FE4B-B002 (MAG4FB, commonly found in I9305) and KMVTU000LM-B503 (the infamous VTU00M) share the same firmware! MAG4FB 0xFC and VTU00M 0xFC differ only by the last 16 bytes of the firmware image, and MAG4FB 0xF7 is binary identical to VTU00M 0xF7.
So, MAG4FB 0xF1 is likely vulnerable to SDS! (assuming it even exists - I've only ever seen 0xF7 and 0xFC, but some people on other forums are reporting 0xF1)
Do you mind sharing the 0xf1 firmware? I followed the guide and the firmware I pulled from my phone has a different checksum than the sample checksums provided in the guide.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone