My question is concerning a physical EMMC chip failure. I have rooted my phone and eventually bricked it, I didn't want to go through the carrier because if I was the cause of my phone being bricked I didn't mind taking responsibility for it. I found out though that it was a physical EMMC chip failure. If its a hardware problem that was not my fault I wouldn't mind taking it to my carrier's store to get fixed. So can rooting your phone cause a EMMC chip to fail?
ruin700 said:
My question is concerning a physical EMMC chip failure. I have rooted my phone and eventually bricked it, I didn't want to go through the carrier because if I was the cause of my phone being bricked I didn't mind taking responsibility for it. I found out though that it was a physical EMMC chip failure. If its a hardware problem that was not my fault I wouldn't mind taking it to my carrier's store to get fixed. So can rooting your phone cause a EMMC chip to fail?
Click to expand...
Click to collapse
Rooting by itself isn't enough to cause the brick. Flashing something through CWM that called an older script could cause it as it was causing issues in the emmc partition controlled by the emmc chip.
ruin700 said:
My question is concerning a physical EMMC chip failure. I have rooted my phone and eventually bricked it, I didn't want to go through the carrier because if I was the cause of my phone being bricked I didn't mind taking responsibility for it. I found out though that it was a physical EMMC chip failure. If its a hardware problem that was not my fault I wouldn't mind taking it to my carrier's store to get fixed. So can rooting your phone cause a EMMC chip to fail?
Click to expand...
Click to collapse
How do you know it was a "physical" chip failure??? Have you already taken it to a service center???
It's not often in these forums that you see someone will to take responsibility when they dork there device... But I must say it is nice to see.
But like rwilco stated, simply rooting your phone doesn't cause the eMMC brick. The only real way is to flash or wipe the wrong way.
I don't think your eMMC chip has "physically", unless you've taken your device apart and checked it specifically.
I'm get the feeling the you just flash or wiped from an unsafe ICS kernel/recovery.
Sent From My Galaxy10.1 Class Starship....
An emmc brick is not a physical failure.. it is though a bug in the firmware put in by the manufacturer that we can't patch. You can, if you don't want to goto the carrier, repartition the phone and not use the corrupted emmc area, assuming its not in the bootloader area.
Sent from my SPH-D700 using xda app-developers app
haven't a few people got their borked emmc phones fixed directly through Samsung support as well? I know I saw a post somewhere around here... I think in the thread that led to our current emmc thread in general where at least one person had success sending it directly to Samsung for warrenty service
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
haven't a few people got their borked emmc phones fixed directly through Samsung support as well? I know I saw a post somewhere around here... I think in the thread that led to our current emmc thread in general where at least one person had success sending it directly to Samsung for warrenty service
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I brick my phone on April, I sent for repair to Josh, in Texas, mobiletechvideos.com.
He can"t fixed, then I had to send to Samsung, and they repaired for me. Try any of these first, Good luck.:good:
mguzman0971 said:
I brick my phone on April, I sent for repair to Josh, in Texas, mobiletechvideos.com.
He can"t fixed, then I had to send to Samsung, and they repaired for me. Try any of these first, Good luck.:good:
Click to expand...
Click to collapse
I am reviving an old thread, but this comes up in google when searching for emmc failure.
same with my galaxy S2, sent to mobiletechvideos and they can'T repair it.. emmc failure.
I will try with Samsung. Where did you send it? Mine is not under warranty.
Related
i am keeping an eye on sds problem now a days . i am soon going to get a (used) note2 but i dont want repaired phone from Samsung service center. how to check if motherbooard has been changed or replaced?
EDIT:- And ya sorry for my bad English (i think my title was wrong)
sorry!
Re: How do i check if chip(after sds) has been changed or not?
Well you can determine if it is prone to sds or not.
Use emmc brick bug check from play store.
Sent from my GT-N7100
UtkarshGupta said:
Well you can determine if it is prone to sds or not.
Use emmc brick bug check from play store.
Sent from my GT-N7100
Click to expand...
Click to collapse
i think my title was wrong i just edited it please answer if you know...
If samsung have replaced board then it is nearly impossible to know it, unauthorized replacement can be know from two different imie, one on device and other on backside of device.
Samsung port old imei to new mother board.
Sent from my GT-N7100 using xda premium
Maybe serial and all?
this is XXXDDDAAA
If you are going to replace your motherboard from a Local unauthorized repair center then how would you the replaced motherboard is NEW not refurbished or swapped from any older one ???
I've got all the symptoms for SDS and I downloaded the eMMC check app which says I have an insane chip. I'm on the current firmware (4.1.2), so that didn't fix it for me.
How can I contact Samsung about this issue? I bought this phone from an Amazon seller.
This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?
I have similar problems with my GT-N7100 which I bought from Newegg.com last November (British unit). The phone often freezes, reboots and I believe once turned itself off. Those symptoms happen several times a day and I consider this phone to be unusable at this time.
There is no US warranty and I have no clue whether anything can be done and by whom. Is this phone reparable? If yes, which outfit can do it?
Memphis_ said:
This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?
Click to expand...
Click to collapse
Thanks for the response.
My phone is 6 months old now. It freezes and must be rebooted very often now, usually a matter of minutes. This even happens in safe mode.
I am running Perseus - alpha32 kernel, which I believe should include Samsung's SDS fix
WCF said:
Thanks for the response.
My phone is 6 months old now. It freezes and must be rebooted very often now, usually a matter of minutes. This even happens in safe mode.
I am running Perseus - alpha32 kernel, which I believe should include Samsung's SDS fix
Click to expand...
Click to collapse
Yeah Perseus kernel has the SDS's fix since January, 2013 so without being sure I don't think the SDS can arrive if you have this protection.
A clean installation of your system may solves your problem.
You can also try to update your firmware via OTA or Odin flash.
Memphis_ said:
This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?
Click to expand...
Click to collapse
I saw that i have an insane chip and then your comment calmed me down :good:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
How do you replace the motherboard? Who does it - would you know of a contact?
Thanks.
tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?
Reuven007 said:
How do you replace the motherboard? Who does it - would you know of a contact?
Thanks.
Click to expand...
Click to collapse
By using your warranty.
WCF said:
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?
Click to expand...
Click to collapse
Let it die then. Don't try too hard to prolong SDS. It's still under warranty right? You should get a replacement easily.
WCF said:
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?
Click to expand...
Click to collapse
What symptoms have you got - if you 're flashing ROMS/Kernels then how can it be SDS. As I understand it SDS means that your phone is a brick. Just because it's freezing or rebooting doesn't mean it's SDS - could be many things
tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
eladwf said:
By using your warranty.
Click to expand...
Click to collapse
Unfortunately my phone is an international version, purchased last November from newegg.com with 90 day warranty. So I need an independent technician or lab to fix it and I have no clue where to start.
Reuven007 said:
Unfortunately my phone is an international version, purchased last November from newegg.com with 90 day warranty. So I need an independent technician or lab to fix it and I have no clue where to start.
Click to expand...
Click to collapse
16gb or 32 gb
Rampant reboots and freezes are also symptoms of a badly coded app, a faulty memory card, a bug in a custom kernel, a bug in a custom rom, a dying sim card, malware, a bad flash.. You get the point
Sent from my GT-N7100 using Tapatalk 2
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
The Sudden Death Syndrome (SDS) issue is caused by a buggy firmware (low level machine code) on the emmc of devices, specifically, a 16GB VTU00M chip with firmware revision 0xf1. The phone dies when trying to write data to an affected block. Samsung has issued a temporary fix to avoid sudden death but this is not a permanent solution. It causes a device freeze or lock-up when attempting to write to an affected block. For devices which have undergone a lot of writes before the fix, the users experience persistant freezing which may last from 2min to even an hour.
Click to expand...
Click to collapse
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
My GT-N7100 16GB phone fits exactly the SDS definition. Since I have no warranty, what could be done to fix this problem? It's only 6 months old phone...
WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
Exactly! According to this definition, your phone is not showing symptoms of SDS but merely demonstrating that the fix is kicking into action. Don't you think its weird calling it a "Sudden" Death Syndrome and then thinking it should have symptoms. The irony -_-
Sent from my GT-N7100 using xda app-developers app
WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
Since you said it seemed ok after a factory reset, I was thinking it might be something else. Not saying it's absolutely not sds, but as bushako said, it seems as it might as well be the protection kicking in, it has happened a couple of times for me too.
What you could try, is taking a look at last_kmsg immediately after booting after you get a freeze. If the log has no alarms or anything out of the ordinary, chances are it's the fix kicking in and blocking the bad commands sent to eMMC.
Sent from my GT-N7100 using Tapatalk 2
bushako said:
Exactly! According to this definition, your phone is not showing symptoms of SDS but merely demonstrating that the fix is kicking into action. Don't you think its weird calling it a "Sudden" Death Syndrome and then thinking it should have symptoms. The irony -_-
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I see what you are saying. But if the prevention for SDS makes the phone unusable, isn't this just a lesser of two evils? Wouldn't this inevitably happen again and I would be better off sending this for warranty?
Hi XDA,
I recently hard bricked my SPH-L710 (Sprint version of the Samsung Galaxy S3). I was going to attempt the procedure here: (http://forum.xda-developers.com/showthread.php?t=2023069) Then I quickly realized after tearing down my SPH-L710 that we have a different system board and processor (thanks sprint!). I was wondering if anyone had a shot in the dark as to whether or not there's an equivalent resistor you can trip on the SPH-L710 that will cause the device to boot from SD?
I appreciate any help. Here are some pictures of the SPH-L710 System board: http://imgur.com/a/jOJ5x#0
I've also attached the Samsung PDF(gt-i9300.7z) describing the same resistor/process to trip.
Not only that it has completely different partitions. Nothing which works on the International S3 will function on a US variant. If your looking to repair the bricked device Jtag is the only thing. It has to be reset at a partition level first before being able to reload software.
Sent from the future via Tapatalk 4
edfunkycold said:
Not only that it has completely different partitions. Nothing which works on the International S3 will function on a US variant. If your looking to repair the bricked device Jtag is the only thing. It has to be reset at a partition level first before being able to reload software.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Yep, I actually have the appropriate PIT for the SPH-L710, though, that won't help at this point.
I called Samsung and they sent me a shipping label for repair. They didn't ask any pointed questions.
It was more or less: "What's wrong with it?, Oh it won't boot? OK we'll send you a shipping label, it'll take 2 business days to ship, 5 to repair, and 2 to ship back." I was hoping to hang on to it for a bit to try and fix it to maybe provide a solution for other SPH-L710 users, however everything I find is "It's hard bricked, just pay to get the JTAG repair". A bit disheartening as a computer scientist to have to pay to get something fixed, luckily it doesn't look like I'll have to pay Samsung.
I have a contact in Samsung's memory division, I'm going to see if they can get hook me up with a schematic for the SPH-L710.
If I find anything further, I'll update this thread. Otherwise Samsung is repairing my device.
Howdy all<
First, I swear I've searched high and low for this answer. I've been to the xda threads with guides to disassembly and reassembly and followed the links to OEM part retailers and come up with zilch.
So, I have a bricked GT-N7105 with suspected sudden death syndrome. It acted screwy for a few days with random reboots etc and then, one day, I took it out of my pocket and it was dead. No boot, no charge, no lights, no nothing. I sent it to Samsung who (classic) are claiming liquid damage and want to charge me $588 Australian to fix it. I am unprepared to pay this. I know that the chip should be covered by extended warranty but this is voided by the supposed liquid damage. I will fight them on it but am not optimistic about the outcome.
So, assuming that I'm not giving my money to Samsung or the company that they outsource their repairs to, can anyone point me towards a link for a store selling replacement motherboards for the N7105?
Furthermore, I haven't managed to find specific information on the motherboard model number for the N7105: is it the same as the N7100 or any of the other Note II variants? Anything that can widen my search criteria will be helpful.
Thanks all. Love your work.:good:
Anyone?
aceofdaves said:
Anyone?
Click to expand...
Click to collapse
try ebay?
If your phone has suffered SDS,then only emmc is damaged,not the whole motherboard.You can get it(emmc) replaced from a third party repair shop.
Gud luck.
1st of all, a motherboard is about 200-250$, and you can repair it at a normal smartphone repair shop, screw samsung.
request photos of the "liquid damage"
i'd take this to the court.
When i destroyed the partitions on my old galaxy player 5.0, they said it was corrosion from some sticky liquid lol, and they eventually gave me a replacement (probably because i figured out they were lying)
+1,Its the same old story they tell to everyone...here in india too .So if you are sure that its not damaged by liquid,just stick to your point and be stern in your approach while dealing with these so called 'technicians'...
Gud luck.
Sent from my GT-N7100 using XDA Premium HD app
Wow. Thanks all! That's all really useful information. I now have it back so I think I'm going to try replaceing the emmc. Will update the thread then.
aceofdaves said:
Howdy all<
First, I swear I've searched high and low for this answer. I've been to the xda threads with guides to disassembly and reassembly and followed the links to OEM part retailers and come up with zilch.
So, I have a bricked GT-N7105 with suspected sudden death syndrome. It acted screwy for a few days with random reboots etc and then, one day, I took it out of my pocket and it was dead. No boot, no charge, no lights, no nothing. I sent it to Samsung who (classic) are claiming liquid damage and want to charge me $588 Australian to fix it. I am unprepared to pay this. I know that the chip should be covered by extended warranty but this is voided by the supposed liquid damage. I will fight them on it but am not optimistic about the outcome.
So, assuming that I'm not giving my money to Samsung or the company that they outsource their repairs to, can anyone point me towards a link for a store selling replacement motherboards for the N7105?
Furthermore, I haven't managed to find specific information on the motherboard model number for the N7105: is it the same as the N7100 or any of the other Note II variants? Anything that can widen my search criteria will be helpful.
Thanks all. Love your work.:good:
Click to expand...
Click to collapse
there you go http://www.etradesupply.com/samsung/galaxy-models/samsung-note-ii-lte-n7105.html?limit=all
N7105 is totally different to the N7100 internally so the mainboard will not physically fit onto the chassis if you put the wrong one in ..as the chassis behind the screen which carries the mainboard is totally different ... so get the the correct one if you are going to change the mainboard
nounnouu said:
there you go etradesupply link
Click to expand...
Click to collapse
Thanks for that, mate. This comes up on google. They have no motherboards!
DId you manage to find a replacement motherboard @acesofdaves?
Hello guys,
My 5X is infected by this "bootloop" issues which I posted here https://forum.xda-developers.com/nexus-5x/help/help-screen-freeze-stuck-lines-reboot-t3528689, well I manage to temporary fixed it but yeah sometimes it still reboot or hang by itself like once in a week.
I know it's not a big deal but I'm afraid it will lead to something worse in the future, so I think I should try to fix the hardware.
Some people says it was the EMMC thou other say it gotta be something else, then I asked one of phone repair technician in my place to help to fix the EMMC, well after I told him, he agreed that it's has problem with the EMMC. So he offer to change the EMMC with the one from Samsung, but as I look into the spreadsheet the original one is made by Toshiba, then he tell me that it will make no difference since they both are made for phone.
So I'm asking for help from anyone who knows about this technical or maybe an expert at repairing a phone is it true ?
Is there anything to notice before changing the EMMC on the phone ? like the EMMC specification ? since the Toshiba one has "5.0" on it and I'm sure it meaning something but I couldnt figure it out.
Please any advice will be appriciated.
Thanks in advanced.
please help anyone ? or someone with experienced in tearing down the phone components ?
I owned G3 before i facing screen faded,bootloop
first method i use piece of paper to push EMMC it work for few day
second method i reheat EMMC with baker for 8min 200'c it work for a week then i sell it
you should reheat you EMMC and add pressure to EMMC to make more contact in mainboard.
Duckscreen said:
I owned G3 before i facing screen faded,bootloop
first method i use piece of paper to push EMMC it work for few day
second method i reheat EMMC with baker for 8min 200'c it work for a week then i sell it
you should reheat you EMMC and add pressure to EMMC to make more contact in mainboard.
Click to expand...
Click to collapse
thanks for your response
so are two of those method just works for temporary ?
do you know by a chance that it is possible to change the EMMC with another EMMC different from the original one ?
Here!
https://www.xda-developers.com/nexus-5-hardware-modded-to-64gb-internal-storage-by-replacing-emmc/
second method i reheat it but i didnt add pressure on the chip so you might try it,before change the emmc.
Heat it up and press on the chip to make more contact on mainboard
when you press try to not move to chip it might malfunctional.
Duckscreen said:
Here!
https://www.xda-developers.com/nexus-5-hardware-modded-to-64gb-internal-storage-by-replacing-emmc/
second method i reheat it but i didnt add pressure on the chip so you might try it,before change the emmc.
Heat it up and press on the chip to make more contact on mainboard
when you press try to not move to chip it might malfunctional.
Click to expand...
Click to collapse
I tried to pm you but it appear I can't
So here it is....I want to try your method about heating the chip but I need to ask few questions and hope you help me on this.
How much temperature needed to heat the chip and how long it took ?
Is it the processor chip or the emmc one ?
Thanks in advance.
8min at 200 degrees Celsius.
Sent from my Pixel using Tapatalk