Has anyone seen the following with Galaxy Note 4

anon(394005)

Banned
Jul 5, 2011
1,914
162
0
Visit site
That's download mode usually accessed by pressing power+home+volume down buttons at the same time. It's typically only used with the Odin program to flash firmware to the phone. To get out of it pull the battery for a bit (then put it back in and power back up).
 

anon(394005)

Banned
Jul 5, 2011
1,914
162
0
Visit site
Possibly but sounds more like an issue with the operating system or a bad app.

Try wiping the cache partition (does not affect any data just clears OS temp files):

Wipe cache partition:
1. Turn the device off.
2. Press and hold the Volume Up, Home, and Power buttons at the same time until the Android System Recovery menu displays and then release (this step may take several seconds)
3. Press the Volume Down key to highlight 'wipe cache partition.'
4. Press the Power key to select.
5. When the wipe cache partition is complete, 'Reboot system now' is highlighted.
6. Press the Power key to restart the device

If still an issue try booting into safe mode: https://support.t-mobile.com/docs/DOC-28897
 

rmholler

New member
Dec 6, 2016
4
0
0
Visit site
Possibly but sounds more like an issue with the operating system or a bad app.

Try wiping the cache partition (does not affect any data just clears OS temp files):

Wipe cache partition:
1. Turn the device off.
2. Press and hold the Volume Up, Home, and Power buttons at the same time until the Android System Recovery menu displays and then release (this step may take several seconds)
3. Press the Volume Down key to highlight 'wipe cache partition.'
4. Press the Power key to select.
5. When the wipe cache partition is complete, 'Reboot system now' is highlighted.
6. Press the Power key to restart the device

If still an issue try booting into safe mode: https://support.t-mobile.com/docs/DOC-28897
That combination of buttons wouldn't do anything and then I had to take out the battery and replace to boot back up
 

anon(394005)

Banned
Jul 5, 2011
1,914
162
0
Visit site
Had a chance to get a closer look at your attached pictures which show:

Could not do normal boot.
ddi: mmc_read failed


That's typically an indication the phone's internal storage is failing, which could also explain the phone freezing and rebooting on you and possibly also why you're having trouble getting into recovery (to wipe the cache partition). In reading numerous threads at XDA looks like re-flashing the firmware (via Odin) may help although temporarily (many reported the error returned and/or at some point the phone just stopped working all together). The only permanent solution seems to be either replacing the motherboard or the entire phone.
 
Last edited:

nahoku

Well-known member
Jan 26, 2013
3,300
0
0
Visit site
That combination of buttons wouldn't do anything and then I had to take out the battery and replace to boot back up
You need to make sure the last button you press and hold is the "power" button. You may have done that, but there's no way of telling from your post.

There has been success with reflashing the phone even with it showing mmc_failed error. People have done it... like in this XDA thread... see post #37. The post refers to a T-Mobile device, and since you didn't state what carrier/model you have, this post may not apply to you. Even so, it may still be possible if you can find the correct firmware, and perhaps the correct modem file for your phone. If you're on AT&T, then it might be tougher to find firmware as AT&T doesn't release it like the other carriers... still, someone on XDA might have uploaded it. You will have to search XDA.

The key to success is apparently not giving up, and also pulling the battery, holding the power button to cause a full discharge of the phone, reinserting the battery, and flashing with an older version of Odin.

In any case, read through the link (and thread) and search out similar cases for your carrier/model phone on XDA. I personally would spend a considerable amount of time doing research before replacing the motherboard or the phone. Successes like the link above points to the mmc_failed error as not always being a hardware problem.
 
Last edited: