FORUMS

ddi: mmc_read failed boot error fix for Samsung Galaxy Note 4 SM-N910T

22 posts
Thanks Meter: 24
 
By NYiCoN, Junior Member on 7th August 2016, 04:32 AM
Post Reply Email Thread
28th March 2017, 07:15 AM |#81  
Death-Dealer's Avatar
Senior Member
Thanks Meter: 72
 
More
This is my second time since launch going through this. The first time when marshmallow was released, I got a free advanced exchange. This second time, Sprint did that but it's been replaced with a S6. I'm putting that on eBay to pay for the note 4 that I already ordered. I just hope this one lasts until the note 8 release.
29th March 2017, 02:29 PM |#82  
Senior Member
Thanks Meter: 1,228
 
Donate to Me
More
So I get dreaded Odin mode sometimes when I reboot, but I was able to Odin to stock to clear things out, and still get occasionally Odin mode when I reboot?

Look for new phone? Anyone has priced note4? How much?

Sent from my SM-N910V using Tapatalk

---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------

Anyone has replaced motherboard? Looked it online for price, but not sure if I want to spend replacing it.

Sent from my SM-N910V using Tapatalk
29th March 2017, 03:53 PM |#83  
Junior Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by tempy1

I ended up sending the phone to Samsung. They sent it back to me without even touching it because it was rooted.
So i'm **** out of luck. I guess i'll just try a local repair place.

I would suggest to try it yourself. It is not hard. There are plenty of good videos available as how to disassemble your Note 4. I did this and I had no experience before. Now I am waiting for the motherboard to arrive and I'll replace the motherboard myself. Because going to repair shop means spending around $200 and it is tooo much.
4th April 2017, 02:26 AM |#84  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by fidagill

I would suggest to try it yourself. It is not hard. There are plenty of good videos available as how to disassemble your Note 4. I did this and I had no experience before. Now I am waiting for the motherboard to arrive and I'll replace the motherboard myself. Because going to repair shop means spending around $200 and it is tooo much.


Samsung f**ked me. They sent the phone back with "No economical way to fix" later i spoke to a rep and they said, your phone is rooted we don't touch rooted phones.

All the motherboards that i can find for my processor are marked as bad ESN. I already preordered the new galaxy s8 so i don't know if it's even worth fixing at this point.
So frustrating!
4th April 2017, 04:40 PM |#85  
ubigred's Avatar
Senior Member
Flag Houston
Thanks Meter: 411
 
More
Quote:
Originally Posted by tempy1

Samsung f**ked me. They sent the phone back with "No economical way to fix" later i spoke to a rep and they said, your phone is rooted we don't touch rooted phones.

All the motherboards that i can find for my processor are marked as bad ESN. I already preordered the new galaxy s8 so i don't know if it's even worth fixing at this point.
So frustrating!

Not worth it. Get the s8+ btw

Sent from my SM-N910T using Tapatalk
4th April 2017, 09:46 PM |#86  
Member
Thanks Meter: 8
 
More
I started experiencing this issue since last week. Out of nowhere, my Note 4 started to lag and freeze. At first I thought maybe it was the battery too, so I got myself a brand new Anker Battery. And hey, nope it's not a battery issue. Then I reformatted my phone, and yes, it was still lagging and freezing.

Fast forward to this week, last night, I got the mmc_read failed message. Shoot me.

Now I've been using the Wake Lock app and it's set to Level 4 (Partial Wake Lock). It's been much better with this App running. Of course, my battery takes a hit. But at least the phone is usable, as long as I don't restart the Phone.

My gf's phone is exactly the same as mine, Note 4, and we're exactly on the same firmware version. She has no issue at all. We've switched batteries as well and her phone works fine with any battery.

I never rooted my phone, and I've been using only the original, official firmware pushed by T-mobile. My phone is running the latest firmware (EQB1) released last month. The problem didn't start right after my phone was updated. Only since last week.

Now, I've been scouring the Internet and many say this is a hardware issue, but some say too that this is probably caused by the firmware. Does anyone now know better if this is a hardware or software issue?

I was going to get myself another Note 4 but then if this is a firmware issue, it could happen too to a new Note 4. If this is a hardware issue, then a new Note 4 may not get this problem.

There's also a conspiracy theory saying that Samsung purposely did this so as to force all Note 4 users to upgrade their phones. If this is a firmware issue, can we file a class suit? Sigh.

UPDATE 1:
I just came back from the Samsung Experience Center. I also talked with Samsung, T-mobile over the Phone today.
So basically, from what the guy over at the Samsung Experience Center told me, a few months ago, many Note 4 Sprint users had this exact same issue. Basically the firmware update caused the phone to malfunction. In the end Samsung replaced all the affected phones. I went there, talked to him, and initially I wanted him to reflash my phone but he then told me that this issue was basically a faulty firmware. Reflashing wouldn't really help because the firmware itself is faulty. The firmware could have affected (damaged) the hardware. That this exact same issue has happened in the past with Sprint users.
I then called Samsung hotline up and talked with, fortunately, a friendly and helpful rep who was willing to document everything and escalate the issue on my behalf. She told me that she would call me back in a few days to update me on how the case is going.
At this point, I'll just have to wait and see.

UPDATE 2:
And apparently I just learned that Note 4 in Europe and Sprint here in the US just received a latest firmware update around 300-400mb in size.
"The firmware update description reveals that it brings better stability and performance as well as optimizations for improving battery efficiency. This Galaxy Note 4 update also comes with the March security patch that has 73 fixes for Android OS vulnerabilities and fixes for a dozen vulnerabilities that Samsung found in its own software."

Fingers-crossed, hopefully this update will soon come to T-mobile and other carriers and fix our issue.
The Following User Says Thank You to febzz88 For This Useful Post: [ View ] Gift febzz88 Ad-Free
5th April 2017, 03:06 AM |#87  
Junior Member
Flag Buffalo
Thanks Meter: 2
 
More
I'm adding a "me too" to this thread. Carrier is Verizon. Phone lags, freezes and spontaneously shuts off. I've had to pull the battery and replace it, sometimes multiple times before the phone will boot. Sometimes it boots successfully, other times it ends up on the ddi: mmc_read failed boot with an Android downloading screen. Sometimes it shuts off while trying to boot. The last system update was Feb 25 but the issue only started 4 or 5 days ago. I also got a brand new Anker replacement battery but it didn't make a difference.

Though I've installed Android on a few HP Touchpads, I'm probably too chicken sh*t to try to mess with my beloved Note 4. Besides, I haven't seen anyone mention files for the SM-N910V.

Right now, I'll limp along with Wake Lock and get everything I want to save off the phone. I'll have to figure out whether insurance or trade-in is the route to take with this 28 month old phone.
5th April 2017, 03:44 PM |#88  
Junior Member
Flag Muharraq
Thanks Meter: 0
 
More
Quote:
Originally Posted by NYiCoN

I've been reading online that some people are receiving an error message similar to this:

ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START

If so then there might be hope because I was able to successfully make my Note 4 go from a paper weight to a fully working phone. Aside from the error message in DOWNLOAD MODE there were multiple times where I had to remove the battery and place it back in because for some reason the phone wouldn't power on unless I did just that. I'm going to try my best to replicate what I did so that someone else can benefit from this.

You can find the files attached here in this link

***THESE FILES ARE ONLY FOR SM-N910T (SAMSUNG GALAXY NOTE 4 FOR T-MOBILE)***

https://drive.google.com/folderview?...F9CTk1MSnJxQlE

***THESE ARE THE FILES YOU NEED***

1) ODIN 3.09
2) N910TTMB1COD6_Modem_CP.tar (5.0.1 Modem)
3) N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME_AP. tar (6.0.1 Firmware Stock)
4) N910TUVU2EPE3_CP.tar (6.0.1 Modem)

Instructions:

1)Place phone in DOWNLOAD MODE (volume down + home + power button)
2) Open ODIN 3.09
3) Place file N910TTMB1COD6_Modem_CP.tar in CP box
4) Place file N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME_AP. tar in AP box
5) Once ODIN is finished flashing the files power off your phone and go back into DOWNLOAD MODE
6) Place file N910TUVU2EPE3_CP.tar in CP box
7) Once the file is flashed your phone will be mmc error free and you will have a 100% working phone again.

If you're having any issues please let me know.



I'm having the same exact issue.. But i have a Sprint carrier phone which is unlocked to support any SIM.. Can this work on my phone.. Please do advice.
12th April 2017, 03:34 PM |#89  
Member
Thanks Meter: 12
 
More
Adding another me to. Started acting up about 2 weeks ago. Does doing what the OP stated actually fix the phone or is this a hardware failure?
12th April 2017, 04:48 PM |#90  
Senior Member
Thanks Meter: 1,228
 
Donate to Me
More
i used to get mmc_boot issue when I was running LineageOS or Note7 and other ROM all together using Dualboot Patcher, and had all sorts of issue when I boot or reboot or update.

I have simplified, and running only one ROM. following what is described here has mitigated my problem if I run stock. It boots fine, and very seldomly I see mmc error, but stock ROM is slow and bloated, so I am running CM14, but still same issue if I run LineageOS or RR. If I run EmotionOS, It appears to be more stable and have less issues. I can reboot if I shut down the phone, and then wait for few seconds to power up, and it works.

I am going to keep this for a while to see what's going on or buy some time to see if I should pickup another Note4 or Le Max for about $180. Just love OLED display so much, so i may buy another Note 4.

Seriously quality issue with Note4 hardware. I have Note2, and it just works. NO MMC issue. I have note3, and no issues so far.
13th April 2017, 07:53 PM |#91  
Junior Member
Thanks Meter: 0
 
More
What am I doing wrong? I have done exactly how it is explained. However, im getting (success 0/failed 0) I dont l know, im realy getting frustrated. Why should they take off this phone from market by killing them this way?

What can i do to get my phone back?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes