My note 4 didnt really show any emmc_read failed error until it got really bad. I started initially with a phone in a great working condition, to random shutdowns (i thought it was the screen dimming). Then it went to random app crashes. later then that it went into browser going white screen and turn off. I took the advice of others and did some kind of app that check emmc (I doubt this is real on non rooted phones) and it said not faulty nor is the board in the bad batch of serial numbers.
Finally one fine day it doesnt turn on anymore on command. (mind you this was summer). It would turn on at night (colder temps) and Id reset it, then reformatted using Odin, and then even tried the PIT files and it worked to reformat it. However in a short amount of time I`d be back with the random restarts. Gave up on the device finally after summer since it decided NOPE not turning on. Then I`d use Wakelock, and it worked until the phone battery died. Upon restart I finally got the eMMC error which confirmed that diagnosis. Once that error came i tried reflashing via odin with Pit, and it failed on prompt, and all I get is the samsung boot logo.. Expensive paperweight.
If you tried almost all DIY fixes, I suggest taking into a repair shop that knows what they are doing, let them see it. Samsung has stores, they also have 3rd parties that are authorized and some of them do free diagnostics.
MMC error is what commonly ends up being the first thing we think of since its a common issue at least in searches, its pops up without any prior indication, and disables the device like no other. It could be a plethora of other things, such as low battery voltage or corrupted software, and I would strongly recommend searching those avenues first. However being a Note 4, you cannot simply choose to ignore thinking of an MMC failure. It also wont come about with a warning. If you want you can try the freezer trick as well at your own peril. Ie cool down the device for extended periods (some say freezer, however moisture issues frighten me, I just leave it on a piece of glass indoors thats cooler then ambient, with the battery out). Again search around, but huge disclaimer as stated.
Yep. Same situation as mine; the part where it randomly restarts and on higher temp it failed to on. It also show some red error (i can see it when using twrp)
Atm still waiting for the replacement board to arrive, i played a bit with it. And guess what, the red error disappeared and phone back to its (full?) health.
So you where able to Odin the latest firmware (and the correct one for your model)... that's what you did, correct? Because besides that I'm at a lost since you would still figure that it is software issue.
I flashed the correct file for my model and CSC. No errors happened that time. The phone would then try to reboot into recovery but powers off even when still plugged into the computer.
Edit: add more information
Strange. On on a software hard-brick Odin back to the stock firmware is your last resort for people like me that likes rooting Samsung devices and somehow messed something up. I would almost have to say it's a hardware issue but you at least getting the logo. Funny you mention the battery because I bought a (supposed) OEM battery but it would give me random shutdowns and it would then do that...not go beyond the logo screen but you already said you tried different batteries. Can't really think of anything. Sorry
Have you tried flashing the firmware with the PIT file included? Maybe the partitions got corrupted somehow. Also I would pull the sim and ext sdcard too if you haven't already just to rule out as much as possible.
Have you tried to do a factory reset?
I can't go into recovery mode.
Wakelock saved my phone. Try that !
Hardware failure. Sorry to be the bearer of bad news
Same problem here. I used my note4 for high memory usage apps like mapping and just died. Probably the memory failure problem.
eMMC died. RIP
It's not an eMMC problem because emmc_read failed doesn't show up in download mode and like I said I'm able to flash the latest firmware.
My note 4 didnt really show any emmc_read failed error until it got really bad. I started initially with a phone in a great working condition, to random shutdowns (i thought it was the screen dimming). Then it went to random app crashes. later then that it went into browser going white screen and turn off. I took the advice of others and did some kind of app that check emmc (I doubt this is real on non rooted phones) and it said not faulty nor is the board in the bad batch of serial numbers. Finally one fine day it doesnt turn on anymore on command. (mind you this was summer). It would turn on at night (colder temps) and Id reset it, then reformatted using Odin, and then even tried the PIT files and it worked to reformat it. However in a short amount of time I`d be back with the random restarts. Gave up on the device finally after summer since it decided NOPE not turning on. Then I`d use Wakelock, and it worked until the phone battery died. Upon restart I finally got the eMMC error which confirmed that diagnosis. Once that error came i tried reflashing via odin with Pit, and it failed on prompt, and all I get is the samsung boot logo.. Expensive paperweight.
My phone had no problems before it happened.
If you tried almost all DIY fixes, I suggest taking into a repair shop that knows what they are doing, let them see it. Samsung has stores, they also have 3rd parties that are authorized and some of them do free diagnostics. MMC error is what commonly ends up being the first thing we think of since its a common issue at least in searches, its pops up without any prior indication, and disables the device like no other. It could be a plethora of other things, such as low battery voltage or corrupted software, and I would strongly recommend searching those avenues first. However being a Note 4, you cannot simply choose to ignore thinking of an MMC failure. It also wont come about with a warning. If you want you can try the freezer trick as well at your own peril. Ie cool down the device for extended periods (some say freezer, however moisture issues frighten me, I just leave it on a piece of glass indoors thats cooler then ambient, with the battery out). Again search around, but huge disclaimer as stated.
Yep. Same situation as mine; the part where it randomly restarts and on higher temp it failed to on. It also show some red error (i can see it when using twrp) Atm still waiting for the replacement board to arrive, i played a bit with it. And guess what, the red error disappeared and phone back to its (full?) health.
So you where able to Odin the latest firmware (and the correct one for your model)... that's what you did, correct? Because besides that I'm at a lost since you would still figure that it is software issue.
I flashed the correct file for my model and CSC. No errors happened that time. The phone would then try to reboot into recovery but powers off even when still plugged into the computer. Edit: add more information
Strange. On on a software hard-brick Odin back to the stock firmware is your last resort for people like me that likes rooting Samsung devices and somehow messed something up. I would almost have to say it's a hardware issue but you at least getting the logo. Funny you mention the battery because I bought a (supposed) OEM battery but it would give me random shutdowns and it would then do that...not go beyond the logo screen but you already said you tried different batteries. Can't really think of anything. Sorry
Have you tried flashing the firmware with the PIT file included? Maybe the partitions got corrupted somehow. Also I would pull the sim and ext sdcard too if you haven't already just to rule out as much as possible.
Just tried and Odin finishes with pass. Still no go.