I am dealing with a large number of SM-T530 tablets and a some of them have been showing signs of memory corruptions after a few months of usages. The symptoms varied from:
Stuck at first samsung logo, then going to Download mode with "emmc read failed" error
Stuck at second samsung logo
Not charging, not switching on (dead)
Sending the devices to Samsung service, they said it requires motherboard replacement
Examining the devices that are still switching on, by going to recovery mode, I found the data partition corrupted (lots of IO errors)
As for the dead devices, I was able to boot them off an external SD-card, and by examining the internal EMMC I found the bootloader partitions corrupt. In some cases I was able to rewrite those partitions via dd or odin, and the devices are back working, in other cases they became not even writable (IO error), although I was able to reflash other partitions on the same EMMC (recovery, system ..etc).
Another interesting find is about the devices which had only the userdata partition corrupt (stuck at second samsung logo), I changed the system to mount userdata to an external Sdcard partition, which means all future writes were going to the external SD card. Yet, after a while their bootloaders still got corrupted badly (not writable). I initially thought maybe there were too many writes into userdata that is shortenening the EMMC life, but this should discard that assumption.
I've done a lot of research (very useful information by @Oranav @E:V:A @Entropy512 @Hashcode @danarama @sfhub)and the closest symptoms I've come to is the description of Samsung eMMC secure erase bug/ Superbrick bug
This bug results in damage to wear leveller internal data structures when a secure erase command is issued to the chip when the wear leveller is in a particular state. The issue manifests itself as the chip locking up whenever an attempt is made to access regions that were near whatever region was erased. This is why some users had hardbricks (damage hit the bootloader) but others only found /data inaccessible. Once damage occurs, the only way to repair a device is a motherboard replacement. Not even JTAG can fix these devices -- hence the term "Superbrick".
Click to expand...
Click to collapse
But I do not think it's the case because:
- The device does an OTA update in recovery just once, and the update binary only executes a delete_recursive command, and the device is used fine for several months afterwards.
- During the usage, the device never does an OTA update, and never goes into recovery mode again, so unless android automatically issues a secure erase for some reason, then it never happens
- The EMMC model is a Toshiba, which in fact is listed in the same section as non affected by the bug
The EMMC name is 016GE2 (Toshiba), which supposedly is not affected. I'd appreciate ANY helps or pointers to how to diagnose this, or how to even manually reproduce the problem on working devices.
These are Qualcomm MSM8226 devices, which means they go to QDL mode when they're dead and connected via USB, in case there is something to do from there.
t,
Thanks for confirming a debrick image will function :good:
okay, the sm-t530nu && sm-t330nu are both Model: MMC 016GE2
From what i can see so far this could be "fixable" via firmware maybe,
I have both these tabs and abuse them heavily, so thoughts are, firmware version, could be something app-related skunking data partition,
the devices may need /data partition reformatted through a recovery. If you did make the jump to LP that could be more likely, as well as incompatible data leftovers from previous api level. Take one of the dead ones and start by wiping/reformatting data through recovery and work from there, reinstalling your apps with no "leftovers" and so on and so forth.
m
if it is the chip itself then the tab is probably doomed.
This does seem to be more than likely a firmware issue...
eMMC sudden death research
also this http://forum.xda-developers.com/showpost.php?p=38112844&postcount=79
On
I've done a lot of research and the closest symptoms I've come to is the description of Samsung eMMC secure erase bug/ Superbrick bug
Click to expand...
Click to collapse
kernel patch does appear to be present in the LL kernel source releases so should be sorted in LP 5.x firmware
moonbutt74 said:
f you did make the jump to LP that could be more likely, as well as incompatible data leftovers from previous api level. Take one of the dead ones and start by wiping/reformatting data through recovery and work from there, reinstalling your apps with no "leftovers" and so on and so forth.
Click to expand...
Click to collapse
So far all bricked devices happen to be 4.4.2. I have not yet seen it on LP, but then only very very few of them are on LP and haven't been in use long enough.
moonbutt74 said:
kernel patch does appear to be present in the LL kernel source releases so should be sorted in LP 5.x firmware
Click to expand...
Click to collapse
Can you point to where it is in the kernel source? So far all fixes in kernel that I've seen target only specific chips by name, and 016GE2 is not there. I mean if it's the same problem as those Samsung EMMC chips, I believe it it has only been fixed for those Samsung chips, right ?
t,
okay from my git master branch for SM-T530_EUR_LL
drivers/mmc/card/block.c @ 2874-2876 , @ 3249 , and look at static const struct mmc_fixup blk_fixups[] = from 3252 onward
if this is what's going on i suppose you need the value for MMC_QUIRK_INAND_CMD??
and the correct id for the chip, it lloks to be something like this maybe?
Code:
MMC_FIXUP("MMC[COLOR="Red"]???[/COLOR]", CID_MANFID_TOSHIBA, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD[COLOR="Red"]??[/COLOR]),
That appears to be the meat of the patches you originally pointed to.
and from include/linux/mmc/card.h#L367 @ 367 #define MMC_QUIRK_SEC_ERASE_TRIM_BROKEN (1<<10) /* Skip secure for erase/trim */
also about three lines up you may need an entry to match correct CMD##
Code:
#define MMC_QUIRK_INAND_CMD38 (1<<6) /* iNAND devices have broken CMD38 */
#define MMC_QUIRK_BLK_NO_CMD23 (1<<7) /* Avoid CMD23 for regular multiblock */
not so sure about it though.
The 016GE2 is apparently Toshiba, so maybe something like
Code:
MMC_FIXUP("MMC16GE2", CID_MANFID_TOSHIBA, CID_OEMID_ANY, add_quirk_mmc,
MMC_QUIRK_BLK_NO_CMD??),
i'm not sure how to find CMD##
LP runs pretty good, although with the date of these patches this was probably present in the KK source as well but didn't address this device.
tgalal,
I have a SM-T331 tablet that just died. Can you explain me how did you booted your dead devices from an external SDHC?
I had the same answer from Samsung service: the motherboard must be replaced (almost the same price of a new device)
Thanks!
tgalal said:
I am dealing with a large number of SM-T530 tablets and a some of them have been showing signs of memory corruptions after a few months of usages. The symptoms varied from:
Stuck at first samsung logo, then going to Download mode with "emmc read failed" error
Stuck at second samsung logo
Not charging, not switching on (dead)
Sending the devices to Samsung service, they said it requires motherboard replacement
...
As for the dead devices, I was able to boot them off an external SD-card, and by examining the internal EMMC I found the bootloader partitions corrupt. In some cases I was able to rewrite those partitions via dd or odin, and the devices are back working, in other cases they became not even writable (IO error), although I was able to reflash other partitions on the same EMMC (recovery, system ..etc).
...
Click to expand...
Click to collapse
Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Details of Phone
Model: SM-N910G (India)
Android: 5.0.1 (Stock, Official ROM)
Build: LRX22C.N910GDTY1BOK1
Details of Errors
1. Hangs and restarts every now and then. Problem started suddenly.
2. After restart, going to Download Mode with error >> Could not do normal boot. ddi : mmc read failed
3. Unable to restart, going to Download Mode always.
4. Removed battery, started in Recovery mode and rebooted from there to turn the phone on.
5. Again same problem, hangs and restarts -> Download mode.
Solution Tried
1. Full factory reset (from Recovery wipe data and within phone both)
2. Reloading of ROM from Samsung Kies
3. Reloading of ROM from Samsung Service Center
Nothing worked.
New Errors appeared
1. dm-verity verification failed in Recovery Mode
2. Attention Message: "An error has occurred with the fingerprint sensor"
3. Unable to store WiFi information (every-time need to connect)
Questions
1. What might be the issue of this? Hardware / Software / OS related?
2. As per Samsung Service Center it might be the issue with Motherboard. (Cost. INR 9000/- or USD 135) - They are not sure
3. My handset is out of warranty, should I try something else?
I am totally upset for this. Any help and suggestion will be highly appreciated.
Thanks a lot.
- Rahul
Sounds like a damaged EMMC (NAND) , you can try fixing it by flashing stock with a PIT file. If that fails it's a hardware defect and you should claim warranty.
SquirtingCherry said:
Sounds like a damaged EMMC (NAND) , you can try fixing it by flashing stock with a PIT file. If that fails it's a hardware defect and you should claim warranty.
Click to expand...
Click to collapse
Thanks mate.
Perhaps you are correct. Now phone is completely dead, upon boot it is showing: "Device Memory Damaged".
Can you suggest the possible solution. Can only internal memory be changed or I have to change the complete motherboard?
rahul319 said:
Details of Phone
Model: SM-N910G (India)
Android: 5.0.1 (Stock, Official ROM)
Build: LRX22C.N910GDTY1BOK1
Details of Errors
1. Hangs and restarts every now and then. Problem started suddenly.
2. After restart, going to Download Mode with error >> Could not do normal boot. ddi : mmc read failed
3. Unable to restart, going to Download Mode always.
4. Removed battery, started in Recovery mode and rebooted from there to turn the phone on.
5. Again same problem, hangs and restarts -> Download mode.
Solution Tried
1. Full factory reset (from Recovery wipe data and within phone both)
2. Reloading of ROM from Samsung Kies
3. Reloading of ROM from Samsung Service Center
Nothing worked.
New Errors appeared
1. dm-verity verification failed in Recovery Mode
2. Attention Message: "An error has occurred with the fingerprint sensor"
3. Unable to store WiFi information (every-time need to connect)
Questions
1. What might be the issue of this? Hardware / Software / OS related?
2. As per Samsung Service Center it might be the issue with Motherboard. (Cost. INR 9000/- or USD 135) - They are not sure
3. My handset is out of warranty, should I try something else?
I am totally upset for this. Any help and suggestion will be highly appreciated.
Thanks a lot.
- Rahul
Click to expand...
Click to collapse
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Ashwin Prabhunerurkar said:
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Click to expand...
Click to collapse
I tried the same flashing everything and reloading the same ROM but no luck
Ashwin Prabhunerurkar said:
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Click to expand...
Click to collapse
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
rahul319 said:
I tried the same flashing everything and reloading the same ROM but no luck
Click to expand...
Click to collapse
Any update?
joeb690 said:
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Any update?
Click to expand...
Click to collapse
Samsung told that entire motherboard needs to be replaced which costs INR. 18500/- (US$ 275)
I have given the phone to the local mobile shop, and eventually that shop is also a Samsung retail shop. They told that it is a problem with internal memory emmc and they are replacing the faulty part which costs INR. 2400/- (US$ 35). Lets hope for the best. Will update you as soon as get back my phone.
joeb690 said:
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Any update?
Click to expand...
Click to collapse
Gave back the phone for full refund
So cant help you
rahul319 said:
Samsung told that entire motherboard needs to be replaced which costs INR. 18500/- (US$ 275)
I have given the phone to the local mobile shop, and eventually that shop is also a Samsung retail shop. They told that it is a problem with internal memory emmc and they are replacing the faulty part which costs INR. 2400/- (US$ 35). Lets hope for the best. Will update you as soon as get back my phone.
Click to expand...
Click to collapse
How does the internal memory (emmc) gets damaged on a user error? I think that must be a manufacturing defect.
btw, I have a similar problem with random freezing and restarts since I updated my Note 4 (Tmobile) from 4.4.4 to 5.11
I used a Tekxodus URV5 (5.11) and these problems started, then I tried to fix the problem .. I flashed stock 5.11 (DOK2), TWRP, flashed the latest Tekxodus URV6.5 (after wiping my internal memory, cache, davlik.) ... Same problems.
I guess lesson learned is to stay a way from Lollipop and stay with Kitkat.
Ditto
I am also very curious about this.
I have a note 4 which exhibited these same symptoms and error messages. Although it was in any app at any stage or merely when the phone was in standby.
NB this was purchased direct from the Samsung store.
I sent it back to Samsung two or three times without them fixing the issue. On the last time I was told that they would not fix the phone – which is still well within warranty – because the phone “has been subjected to severe physical damage internally”.
The unit has always been well kept, there is no water damage and there is not a scratch on it….anywhere. also there was no indication of this severe physical damage during the previous Samsung inspections.
I can’t think of a good way to contest this prove this is a problem with the phone and not my use of it.
Samsung are not responsive when contacted. Is there any advice in the forum?? Many Thanks
lewis.james.750983 said:
How does the internal memory (emmc) gets damaged on a user error? I think that must be a manufacturing defect.
btw, I have a similar problem with random freezing and restarts since I updated my Note 4 (Tmobile) from 4.4.4 to 5.11
I used a Tekxodus URV5 (5.11) and these problems started, then I tried to fix the problem .. I flashed stock 5.11 (DOK2), TWRP, flashed the latest Tekxodus URV6.5 (after wiping my internal memory, cache, davlik.) ... Same problems.
I guess lesson learned is to stay a way from Lollipop and stay with Kitkat.
Click to expand...
Click to collapse
Strange thing that's EXATLY what happens to me too
it seems Samsung is trying to kill it's last Flagship Note phone with a MicroSD and removable battery.
Rahul, any update on replacement of emmc. My note 4 has also developed the same problem. Eagerly waiting for a solution.
raj0052 said:
Rahul, any update on replacement of emmc. My note 4 has also developed the same problem. Eagerly waiting for a solution.
Click to expand...
Click to collapse
Hi Raj. No luck
I have got an exchange offer from Flipkart with Rs. 23000/- and have replaced it with my old phone; because replacing motherboard with Rs. 18500/- with only 3 months warranty doesn't make any sense.
I have got a new phone with 1 year warranty with an option of further warranty extension.
Lesson learnt: For high-end phone always go for extended warranty.
emmc_read error
I am now very confident that the "emmc_read error" message is a caused by firmware problem.
I have a N910F for a long time, that was working like a Swiss watch, on the 5.0.x Android.
Recently I've got an update to 5.1.1 and installed it.
The update went through very smooth but after the phone started for the first time it began to freeze.
A few times i have got emmc_read failed message on boot screen and in the logcat the most notable error was SecureStorage TA driver related
it fails to write /efs partition :
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon sent config to TA/driver
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)system error
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)It is failed to write a file to /efs partition.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)Please check
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(1) if there is a valid /efs partition, and
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(2) if /efs directory has the correct permission.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)Error sending config file to TA/driver!
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon stopped
Although the directory and premissions are fine (i've checked many times)
Odin cannot flash with or without PIT file:
<ID:0/009> hidden.img.ext4
<ID:0/009> FAIL! (Write)
As a conclusion i can suggest that the update causes the problem.
I am pretty sure there could be a tool to check emmc, but i could not find any and i am lazy to develop it myself, but for the guys from TWRP this could be a good hint.
BR
Max
I'm not entirely sure the emmc fail is due to updates. i'm still on KK and today i experienced the emmc failure. Major lag so i restarted it but took forever. Then, about 2 hours later, it crashed while opening up snapchat. I try to restart the phone and it goes into download mode saying "emmc read fail". Can't believe so many people are being affected by this.
If you flashed stock ROM with PIT file and the phone doesnt work properly i think your EMMC is corrupted. EMMC can be corrupted by a lot of thing like bad custom rom, ported recovery, etc... Search for a tutorial to flash with PIT and REPARTITION and if that didnt work the EMMC is the fault for sure. You can change the EMMC only very easy if you go to a GSM service center... or buy a hot air station, a leaded solder wire, a wick wire and the EMMC chip.
So first try repartition the phone and if doesnt work just change that EMMC.
Its a software issue. I had the exact same issue with my T-Mobile version SM-N910T. I was able to resolve it by using ODIN to install the stock EPE3 along with the modem of COD6. After the phone restarted I placed the phone in download mode again and from there went on ODIN to install the EPE3 modem. After the phone restarts it should boot straight to the home screen.
maxrfon said:
A few times i have got emmc_read failed message on boot screen and in the logcat the most notable error was SecureStorage TA driver related
it fails to write /efs partition :
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon sent config to TA/driver
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)system error
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)It is failed to write a file to /efs partition.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)Please check
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(1) if there is a valid /efs partition, and
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(2) if /efs directory has the correct permission.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)Error sending config file to TA/driver!
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon stopped
Although the directory and premissions are fine (i've checked many times)
Odin cannot flash with or without PIT file:
<ID:0/009> hidden.img.ext4
<ID:0/009> FAIL! (Write)
As a conclusion i can suggest that the update causes the problem.
I am pretty sure there could be a tool to check emmc, but i could not find any and i am lazy to develop it myself, but for the guys from TWRP this could be a good hint.
BR
Max
Click to expand...
Click to collapse
I do believe that is similar to my issue, on TouchWiz, I will just get crashes that shut off the phone and the mmc issue. On Cyanogenmod, I don't get the mmc crashes, but at random times, my cell service will cut out and stop working, it eventually restores itself, or sometimes it triggers a kernel panic. I tried backing up my efs from TWRP and then restoring the back up multiple times, first time was 0 seconds, second was 104 seconds. Either time seems wrong. But after constant swipe to restores, It stopped doing the lag, I wonder if the update somehow wrote iffy data that was causing problems on the partition. From what I have also noticed, the mmc issue (at least for me) seems that the chip just becomes incredibly slow for a short time and then speeds back up, when I reboot from TWRP or the OS. It hangs at black for a while and then the phone seems to boot itself.
yaoers said:
I'm not entirely sure the emmc fail is due to updates. i'm still on KK and today i experienced the emmc failure. Major lag so i restarted it but took forever. Then, about 2 hours later, it crashed while opening up snapchat. I try to restart the phone and it goes into download mode saying "emmc read fail". Can't believe so many people are being affected by this.
Click to expand...
Click to collapse
I have your exact same problem: still on KK 4.4.4 (stock, no root) the phone always went well until yesterday... First it seems to freeze (also when using the power button) and then I cannot boot again until I removed the battery.
Then I got the emmc read fail error, removed the battery, restarted and it booted, but still sometimes there are major lags (never seen before).
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk
Hi, after going through the process of getting the S7 fixed - and Samsung denying everything (as usual), I'd share this issue as it's been happening to multiple Samsung devices in the workplace.
Here's how to brick your phone:
-An unwilling user goes on a business network, which happens to issue Android security updates via "Android at work".
-Due to Samsung making changes to Android, it manages to break the OS.
-Enjoy a chance to either go into infinite bootloops or if you're lucky - it'll boot in an unresponsive state with a line near the top and an empty desktop.
Now get this, because we tried to flash official firmwares provided by sammobile, the software state has been changed to custom. While the "warranty void" flag remains 0, they claim the device was rooted and want to charge ~$900 for it to be fixed.
As an owner of a S4 a few years ago, who's battery exploded. (And gave me a document to sign to not tell anyone about this) A note 5 owner who's display died while overseas and Samsung refusing to repair, as it wasn't bought in the US. I do not trust Samsung to make a reliable device.
Maybe your work security updates need updating / fixing
And flashing stock with ODIN does not change status to custom, as it is a stock ROM - in fact if your status is already custom and you use ODIN to flash stock, it will change back to Official
have you tried to reflash with odin?
oplix said:
have you tried to reflash with odin?
Click to expand...
Click to collapse
I also got a custom status once flashing samsung firmware, but that was only because the flash was terminated before completion.
Knox flag was still not triggered.
Flashed again with the same stock and now all was fine.
Showed back as Official.
I think you should try to use SmartSwitch if you want to go back to the original firmware, tho it comes with a cost of resetting the whole device including internal storage, you could boot into safe mode, copy your data, then open SmartSwitch > More > Emergency Initialization (or something like that) > 2nd Tab > you put the device model then Search > you put the S/N (check the back of the phone for S7, or under the battery for some phones) > follow the exact instructions > it will be initialized with the latest software and good as new. Hope this helps, also everybody knows Samsung likes not to be responsible on something they did, that's why xda and the devs here exist!
Turbine1991 said:
Hi, after going through the process of getting the S7 fixed - and Samsung denying everything (as usual), I'd share this issue as it's been happening to multiple Samsung devices in the workplace.
Here's how to brick your phone:
-An unwilling user goes on a business network, which happens to issue Android security updates via "Android at work".
-Due to Samsung making changes to Android, it manages to break the OS.
-Enjoy a chance to either go into infinite bootloops or if you're lucky - it'll boot in an unresponsive state with a line near the top and an empty desktop.
Now get this, because we tried to flash official firmwares provided by sammobile, the software state has been changed to custom. While the "warranty void" flag remains 0, they claim the device was rooted and want to charge ~$900 for it to be fixed.
As an owner of a S4 a few years ago, who's battery exploded. (And gave me a document to sign to not tell anyone about this) A note 5 owner who's display died while overseas and Samsung refusing to repair, as it wasn't bought in the US. I do not trust Samsung to make a reliable device.
Click to expand...
Click to collapse
I hope you learned a lesson and you will stop buying Samsung products so we dont have to read your pathetic posts(lies) ever again.
Hello fellow XDA'ers.
I'm looking for some help in resurrecting a tablet I recently bought off of someone..
The issue with the tablet plays on multiple ROMS.
With the stock Samsung OS, the tablet gets past the boot-loader, hits the first few frames of the boot animation and freezes, Reboots and repeats the process.
With the same firmware and Lineage OS, the tablet does the same thing but not as quickly.
The neat thing is that if we leave the tablet to rest for a few hours, the farther the boot process advances.
We've gotten into both OS' setup screens, but lineage was able to get to the part of telling us that theres a missing SIM card.
Which this tablet does not contain a sim card reader...
Could I possibly have the incorrect Firmware image on the tablet or a bad motherboard?
The device has been verified as a SM-T530NU via serial sticker located on the back.
Model Number : SM-T530NZWAXAC
Model Name: SM-T530NU
I used this firmware to bring it back to stock
I would love to receive some help in terms of pulling logs (Samsung Hardware Logs - Not dmesg)
and finding the culprit to this non-booting Tablet. I will compensate for the work as well
Here's a paste bin of dmesg if that might help
same problem
hi, got same problem with stock os and an untouched device
Mozziliac said:
Hello fellow XDA'ers.
I'm looking for some help in resurrecting a tablet I recently bought off of someone..
The issue with the tablet plays on multiple ROMS.
With the stock Samsung OS, the tablet gets past the boot-loader, hits the first few frames of the boot animation and freezes, Reboots and repeats the process.
With the same firmware and Lineage OS, the tablet does the same thing but not as quickly.
The neat thing is that if we leave the tablet to rest for a few hours, the farther the boot process advances.
We've gotten into both OS' setup screens, but lineage was able to get to the part of telling us that theres a missing SIM card.
Which this tablet does not contain a sim card reader...
Could I possibly have the incorrect Firmware image on the tablet or a bad motherboard?
The device has been verified as a SM-T530NU via serial sticker located on the back.
Model Number : SM-T530NZWAXAC
Model Name: SM-T530NU
I used this firmware to bring it back to stock
I would love to receive some help in terms of pulling logs (Samsung Hardware Logs - Not dmesg)
and finding the culprit to this non-booting Tablet. I will compensate for the work as well
Here's a paste bin of dmesg if that might help
Click to expand...
Click to collapse
Do you by any chance know if you have connectivity issues with wifi or BT?
See my thread as I have been working through this issue and let me know what we maybe can hash through together.
https://forum.xda-developers.com/tab-4/help/samsung-galaxy-tab-4-10-1-sm-t530nu-t3441044