Galaxy Note 4 “Could not do normal boot, mmc_read failed” error, other boot problems

Could not do normal boot error

Do you have problems starting your #GalaxyNote4? Our post today may point you to the right direction. Below are some of the booting problems shared by some members of our community:

  1. “DM-verity verification failed” error after rooting Galaxy Note 4
  2. Galaxy Note 4 screen won’t lock up for 10 seconds after booting
  3. Galaxy Note 4 keeps saying account passwords are incorrect
  4. Galaxy Note 4 “Could not do normal boot, mmc_read failed” error

If you are looking for solutions to your own #Android issue, you can contact us by using the link provided at the bottom of this page.


 

Problem #1: “DM-verity verification failed” error after rooting Galaxy Note 4

I attempted to root my Galaxy Note 4 on Odin. Showed a message with the red logo that reboot would take place in 10 seconds, and phone showed the normal Galaxy Note 4, and then Samsung and then went back to Galaxy Note 4, and wouldn’t boot up for two days.

I took the battery out a few times, attempted re-rooting a few times, all to no avail. So went into the Recovery Mode but at the bottom of my phone, the message, “dm-verity verification failed” appeared. Attempted cache partition, wipe data and each time the message shows complete for each, except that when I did reboot system now, the same problem of  persisted and the dm-verity message is still showing in the recovery screen. — Adeola

Solution: Hi Adeola. Rooting has inherent risks and can sometimes lead to really nasty software glitches. One of such glitches is the error “dm-verity verification failed”, although it can also specifically result from installing an incorrect firmware. During most times, “dm-verity verification failed” error happens after damaging or changing some files in the EFS folder which keeps unique information about your device. Whatever the true cause is, there’s only one effective solution that we know of for this issue — re-installation of stock ROM or firmware. Once you’ve reinstalled the stock firmware, the phone should boot normally again.

We recommend that you be careful when rooting your device again. Doing so is risky and does not always guarantee that the device will work properly.

Problem #2: Galaxy Note 4 screen won’t lock up for 10 seconds after booting

This is the 2nd Note 4 I’ve owned, the one I’m now using replaced a new one.  When I updated to Lollipop 5.0.1 on the 1st Note 4, I noticed the screen would be unlocked for about 10 seconds upon power up. I thought it was the fault of the update, so I reset the phone and updated it a 2nd time.  Same issue. I searched for the problem in different forums and found nothing, so I assumed it was the phone.

Verizon sent me a refurbished phone and its doing the same thing. I haven’t  found anyone else having this issue, or at least no one has asked that I can see. So, can you tell me what may be going on?

These are my settings: I have the screen set to lock after 2 min of non use; the screen is supposed to be locked at startup but it’s unlocked, exposing my texts, email, contacts, etc. for at least 10 seconds on startup. Then, after about 10 seconds the screen will enter lock mode and the pin keyword will appear.  Can you tell how to fix that?  I prefer NOT to use a 3rd party screen lock app.  Thanks. — Jeff

Solution: Hi Jeff. You’re right. No one appears to have reported this particular issue to us or to any other Android forum although we think it’s a Verizon firmware bug. If this issue started happening after Verizon pushed an over-the-air update, other users might also be experiencing it though you may be the first to report it publicly. To be frank, we can’t think of any other solution other than letting Verizon technical support team, especially their developer team that maintains Android firmware for their devices. An issue like this runs deeper on how their firmware is coded so the solution is beyond us.

Try to visit Verizon Android community forum and post a thread there. Verizon’s community forum is monitored and if you’re in luck, you may get specific support from the right technical team.

Problem #3: Galaxy Note 4 keeps saying account passwords are incorrect

I can no longer log into any app or any website that requires a password. When I enter my password that I KNOW is correct because I just checked them by logging into all the same sites on my desktop and writing down the password exactly as I entered it, it tells me that the password is incorrect or invalid every time. I cannot change password either because when I enter the password it will always tell me that the password and confirmation passwords don’t match when I KNOW that they do. Even when I can SHOW passwords and confirm they match I get the same error. I also cannot create a new account on any website for that same reason.

I also frequently get error messages about password tips. For instance when I’m entering the new password and follow the password tips exactly it tells me I’m using characters that aren’t allowed when all I’ve used is letters and numbers, no special characters. It will always give me error messages that basically tell me I’ve not followed the password guidelines when I’m very careful to follow them exactly. This just started happening about 3-4 weeks ago I never had a problem before that and I’ve had the phone for almost a year now.

Here’s what I’ve done so far: soft reset then wiped the cache partition, uninstalled almost every downloaded app, cleared all browsing history including saved  passwords and auto-fill and even turned both of those off in Settings. Last week I took the phone to the Samsung Repair Center in Plano, TX because I had a couple other issues as well and they removed the entire OS and reinstalled Android Lollipop 5.0.1.

I thought the problem was fixed because I was able to log into Google and set everything up but obviously it did not fix this problem.

Also the Samsung keyboard was always freezing and it didn’t fix that either, it still freezes even now while typing this email. I’m so frustrated because I can’t get into any of my accounts. Please help! — Teresa

Solution: Hi Teresa. Did you install the exact same set of applications after Samsung reflashed the firmware? There’s a chance that one of your apps may be hosting a malware or virus that may have compromised the operating system and your accounts. If the phone works normally right after the OS was wiped out  and reinstalled, something you’ve added afterwards is most likely to blame. Try doing these basic solutions to see which one will work for you.

Boot the phone in safe mode

Restarting in safe mode can help you narrow down possible factors because it prevents third party applications from running. Safe mode won’t help you point which of your apps is the culprit. However, it will give you a general idea that one of them is behind this trouble.

Here’s how it’s done:

  • Turn off the phone completely.
  • Press and hold the Power key and the Volume Down key.
  • When the phone starts to boot, release the Power key but continue holding the Volume Down key until the phone finished restarting.
  • Safe mode will be display at the lower left corner; you may release the Volume Down key now.

Keep in mind that some malicious apps may ignore safe mode to protect itself from being uncovered so if the problem continues even when on safe mode, proceed to  factory reset.

Perform a factory reset

Doing a factory reset has many uses and in your case, it is to wipe out phone storage to make sure that you set it up clean again. Don’t forget to create a copy of your personal data (photos, videos, contacts, etc.) first before proceeding. If you haven’t done master or factory reset before, here are the steps to do it:

  • Turn off the Galaxy Note 4 completely.
  • Press and hold the Volume Up and the Home keys together, then press and hold the Power key.
  • When the Note 4 vibrates, release both the Home and Power keys but continue holding the Volume Up key.
  • When the Android System Recovery shows on the screen, release the Vol Up key.
  • Using the Volume Down key, highlight ‘wipe data / factory reset’ and press the Power key to select it.
  • Now highlight ‘Yes — delete all user data’ using the Vol Down key and press the Power key to begin the reset.
  • When the master reset is complete, highlight ‘Reboot system now’ and hit the Power key.
  • The Note 4 will restart but it will be longer than usual. When it reaches the Home screen, then begin your setup.

Because there’s no way for you to know which of your added apps is the problem, we recommend that you check for the problem after installing an app to identify the culprit. We know this solution will take time but it’s the most effective way to deal with it.

Problem #4: Galaxy Note 4 “Could not do normal boot, mmc_read failed” error

Hi, this would be a lengthy post. (My apologies).

I updated to 5.1.1 recently via OTA update. Things were fine for about a few days. Suddenly, my phone keeps random rebooting, frequently crashes and freezing. Often when I power down, I cannot boot up the phone, and had to resort to taking out battery, doing soft reset, then boot up. Although this may require repeated tries).

Sometimes while booting up, the phone would boot to Odin mode saying “Could not do normal boot, mmc_read failed”. These persist even after I did factory reset and wiping of cache partition. My phone would even hang when I’m plugged into the charger. There would be a black screen and nothing comes up when I press the buttons. What exactly happened? I’m really at a loss and phone is out of warranty.

I tried to flash firmware via Odin but apparently unable to do so.

I found out the only way to prevent my phone from hanging, showing black screen or rebooting was to play the music player or watch video. Is this a software or hardware issue?

I’m really at a loss and it’s really frustrating.

Really really would appreciate your reply and thanks in advance. — Jake

Solution: Hi Jake. Did you try to make any operating system level modifications like rooting? If you did and that modification failed, the error “Could not do normal boot, mmc_read failed” usually shows up. Sometimes, a flash memory failure may also result to boot problems (usually due to rooting or OS modification). Unfortunately, there’s no way for us right now to know exactly what’s causing the boot failure problem.

Try to call your carrier and convince them that your phone needs to be replaced due to operating system bug.

If you want to fix the issue yourself, consider flashing a custom ROM to see if it will any difference.

 


Engage with us

If you are one of the users who encounters a problem with your device, let us know. We offer solutions for Android-related problems for free so if you have an issue with your Android device, simply fill in the short questionnaire in this link and we will try to publish our answers in the next posts. We cannot guarantee a quick response so if your issue is time sensitive, please find another way to resolve your problem. 

When describing your issue, please be as detailed as possible so we can easily pinpoint a relevant solution. If you can, kindly include the exact error messages you are getting to give us an idea where to start. If you have already tried some troubleshooting steps before emailing us, make sure to mention them so we can skip them in our answers.

If you find this post helpful, please help us by spreading the word to your friends. TheDroidGuy has social network presence as well so you may want to interact with our community in our Facebook and Google+ pages.

37 thoughts on “Galaxy Note 4 “Could not do normal boot, mmc_read failed” error, other boot problems”

  1. Could not do normal boot.
    ddl: mmc_read failed
    ODIN MODE
    PRODUCT NAME: SM-T331
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS : Custom
    KNOX WARRANTY VOID : 0X0
    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T2, R1, A1, P1
    UDC START

    (Green Android Icon Displayed)
    Downloading…
    Do not turn off target !!

  2. Could not do normal boot.
    ddl: mmc_read failed
    ODIN MODE
    PRODUCT NAME: SM-T331
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS : Custom
    KNOX WARRANTY VOID : 0X0
    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T2, R1, A1, P1
    UDC START

    (Green Android Icon Displayed)
    Downloading…
    Do not turn off target !!

  3. same problem with my note 4

    ddi: mmc_read failed
    ODIN MODE (HIGH SPEED)
    PRODUCT NAME: SM-N910F
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS: Custom
    REACTIVATION LOCK: OFF
    KNOX WARRANTY VOID: 0X0
    QUALCOM SECUREBOOT: ENABLE (CSB)
    RP SWREV: S1, T1,R1.A1.P1
    SECURE DOWNLOAD: ENABLE
    UDC START

    any one have any solution for this problem that I have it from the last official firmware update ?

  4. Try this with your Note 4:

    1. Pull the battery and wait 10 seconds. (Ignore the “Do not turn off target” because it crashed)
    2. Put the battery back in (and add a USB charging cable if your battery may be dead)
    3. Hold down the ‘Volume Up’, ‘Power’, and ‘Home’ buttons to boot into Recovery Mode.
    4. This should display something like ‘Installing System Update…”
    5. Wait for it to finish (it sometimes can take up to 10 minutes). This work-around seems to apply the Update when it fails to install normally. You will see the Android Icon animating.
    6. The screen will go black for a few seconds, then start to try the boot again.

    Mine shows:
    Could not do normal boot.
    ddl: mmc_read failed
    ODIN MODE (HIGH SPEED)
    PRODUCT NAME: SM-N910V
    CURRENT BINARY: Samsung Official
    REACTIVATON LOCK: OFF
    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T2, R1, A2, P1
    SECURE DOWNLOAD: ENABLE
    UDC START

    (Green Android Icon Displayed)
    Downloading…
    Do not turn off target !!

    7. I’m not patient if it takes longer than 60 seconds….so…
    8. Pull battery
    9. Hold down ‘Volume down’ + ‘Power’ + ‘Home’
    10. I’m seeing

    Warning!!
    A custom OS can cause critical problems
    in phone an installed applications.

    If you want to download a custom OS,
    press the volume up key.
    Otherwise, press the volume down key
    to cancel.

    8. Press Volume Down Key
    9. Samsung Galaxy Note 4 Boot Screen appears
    10. Wait 10 minutes…yes, it is slow….
    11. Drink a Vodka Cranberry
    12. If screen turns off…press Power Button once and wait 30 seconds…
    12. Phone reboots into Recovery Mode… with Samsung Galaxy Note 4 screen and little blue message at the top showing ‘Recovery mode…”
    13. Animation of Android Icon shows with ‘Installing System Update…”
    14. After 3-5 minutes….Screen may timeout and go black.
    15. Press Power Button and wait 30 seconds….
    16.Same issue occurs with:

    Could not do normal boot.
    ddl: mmc_read failed
    ODIN MODE (HIGH SPEED)
    PRODUCT NAME: SM-N910V
    CURRENT BINARY: Samsung Official
    REACTIVATON LOCK: OFF
    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T2, R1, A2, P1
    SECURE DOWNLOAD: ENABLE
    UDC START

    (Green Android Icon Displayed)
    Downloading…
    Do not turn off target !!

    17. Pull battery.
    18. Turn on normally.
    19. Samsung Note 4 displays
    20. Verizon Red Screen with Checkbox Icon displays
    21. Wait 1 minute
    22. Drink another Vodka Cranberry
    23. Android is updating…Optimizing 44 of 389…
    24. It may take about 40 minutes…yes, it is slow…
    25. Cheers

    Buy me a beer sometime at a pub and we can share stories as friends? Or hire me to help your software company? Or to reverse engineer something? Verizon, I’m open for a CTO position? I can help with the Yahoo integration?

  5. I got the same error message after an update. I pressed all 3 buttons at my Samsung Galaxy Note Edge and then it ask me if I wanted to install some ordinary settings or something like it then I should press sound up button. But if I didnt want that press sound down button. I press sound down button then it restarted again as normal.

  6. I have the same issue mentioned in Problem #4
    I got the following message;
    ” Could not do normal boot.
    ddi: mmc_read failed
    ODIN MODE (HIGH SPEED)
    PRODUCT NAME: SM-N910F
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS: Custom
    REACTIVATION LOCK: OFF
    KNOX WARRANTY VOID: 0X0
    QUALCOM SECUREBOOT: ENABLE (CSB)
    RP SWREV: S1, T1,R1.A1.P1
    SECURE DOWNLOAD: ENABLE
    UOC START”
    I send the device to the agent and wanted to replace the motherboard and gave me a quotation not worth for a repair as the warranty of the device has been expired.
    I am really frustrated and disappointed of buying a Samsung.
    Please make me aware if anybody has a reasonable solution.
    Thank you everybody.

  7. Incredibly, Note 4 and my partner’s Note 3 are experiencing the ‘lag-freeze-reboot-mmc_read failed’ issue at the same time. This has to be an update issue, surely.

    I’ve been waiting for the Note 8, but won’t be buying any Samsumg phones ever again if this turns out to be planned obsolescence.

    I love the Notes. I’m really really hoping Sumsung sort this out.

  8. As a previous post stated just take out the SD card and it will install, the clue is in the MMC_Failed line

  9. Hello Samsung Note 4

    My phone has a BOOT PROBLEM, IT COULDNOT DO NORMAL BOOT
    The following are the problems

    ” Could not do normal boot.
    ddi: mmc_read failed
    ODIN MODE (HIGH SPEED)
    PRODUCT NAME: SM-N910F
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS: Custom
    REACTIVATION LOCK: OFF
    KNOX WARRANTY VOID: 0X0
    QUALCOM SECUREBOOT: ENABLE (CSB)
    RP SWREV: S1, T1,R1.A1.P1
    SECURE DOWNLOAD: ENABLE
    YDCSTART

  10. since the update….I now got could not do normal boot same story as all above… great just great

  11. i was experiencing this same issue. For days I tried to get past the downloading screen. Even let it run overnight. My phone just one day wouldn’t turn on, it wouldn’t identify a charger, I switched batteries and it wouldn’t work. Plugged it into another charger and got the battery charging screen. When I turned it on It said downloading. So I let it download thinking it was updating and a few hours later still downloading. I couldn’t turn it off so I took out the battery, then couldn’t get it to turn on again or recognize a charger. I removed the batter again and held in the power button awhile then put the battery in and plugged it in and got the battery charging screen. When I powered it I got downloading so I just let it go. Got to work this morning and still downloading. So I removed the back and removed the battery again. Then decided to test something. I know sometimes computers fail to boot because of external drives so I removed the memory card. Put the battery in and hit the power button. It WORKED! If you are having this problem try removing the SD card. I hope this works for everyone. I am curious…please email me and let me know if it worked for you.

  12. i just bought a used NOTE4 its N910F. i tried to factory reset it and it showed custom recovery like wipe cache, update from external source and below it DM verity error. i looked into it and found that its a rooted mobile. i looked at youtube tutorials but so far no luck now the mobile is pretty much useless to me. i wasted almost 3 months saving to buy a used mobile. any help in this regard will be highly appreciated. it showed mmc error, dm verity error and boot warenty kernal issues.

  13. See my earlier post for background. My Note 4 was repaired under warranty. The motherboard and the screen were replaced by the repair subcontractor, Dynafix. The phone was reset to factory state so I had to reinstall all apps and so on. Now the phone seems to be faster than it was before it started exhibiting noticeable hangs.

  14. It’s maybe time to start a class action (“recours collectif” in French) against Samsung for that Galaxy Note 4’s “mmc_read failed” failure caused by hardware failure of the main board (PCB) of that phone.

    How could we do for starting that collective complaint?

  15. My Sprint Note 4 has the same problem as Jake “Problem #4: Galaxy Note 4 “. I do not have warranty on my phone. It looks it is a OTA software update causing the failure of hardware. Searching a solution…

  16. I have the exact same problem as Jake; “Problem #4: Galaxy Note 4 “Could not do normal boot, mmc_read failed” error” and the “solution” posted is not a solution at all as far as I can see. I have not rooted this phone and I have no idea what the rest of those instructions even mean. Can someone point me in the right direction to a step by step guide to solving this problem? Cheers.

  17. Nope. The phone keeps hanging and resetting. Just checked and I am within days of the end of the two-year warranty, so it seems I am lucky with the timing. Sending in for repair. To be continued.

  18. My Note 4 just started behaving roughly the way Jake described in problem #4. A couple of days ago it started freezing, e.g., while I was entering text into a messaging app. Once the phone spontaneously rebooted after freezing for a long time. Then last night the phone downloaded a system software update. I elected to “install now” and left the phone on the wireless charging pad. When I checked it an hour later its screen looked very much like the screenshot above with the text “Could not do normal boot…” on a screen with the android cartoon character and the large message “downloading… Do not turn off target!”. Because it really wasn’t making any progress after a long time I pulled the battery and restarted it. The system software update continued where it had apparently left off with “optimizing app 44 of 153” or whatever. The update completed successfully.

    One other thing that changed around the same time that the phone started freezing is that Peel Smart Remote had updated itself. This is an app from which I had removed permissions a long time ago without fully disabling. It’s an uppity factory-installed app. There seemed to be no way completely to disable its (frequent, unwanted) notifications in the settings panel of the app itself (which I don’t use, as I prefer another IR remote app) so I had used “Sounds and notifications | App Notifications | Peel Smart Remote | Allow notifications = off” to disable notifications, but on update the app somehow managed to regain permission to put up notifications. In the most recent app update the app had installed a new lock screen with a pretty photograph and the message “good afternoon” or “good night … sound is now disabled … you may miss messages” (https://forums.androidcentral.com/samsung-galaxy-note-4/777821-slide-unlock-screen-suddenly.html)! I have since disabled the app (Application manager | Peel Smart Remote | DISABLE; uinstall updates and restore factory version = yes). I wonder if this app could be part of the problem. It’s an app that manages a relatively uncommon piece of hardware — the IR blaster — and bugs in that sort of software can easily cause freezes/hangs. This is speculation, obviously.

    I’ll report back.

  19. February 21, 2017 at 4:47 pm
    I have the same problem note 4 was stuck on downloading mode no reactions for anything.
    start work very slow before this happend.I try to do anything.
    nothing help .
    send to service Samsung and they charge me 63 pounds for check
    and they send me phone back not fixed .
    says it’s not under warranty .
    I will never use Samsung again.
    poor service . where is point to by phone for 500 pounds and after 1.5 year trow in bin .
    This was problem with their software .
    They say fixing cost can go over WICH is device worth.

    This Is was after update . They have lots issue with it and they want to have clear hand . and they want to charge for something WICH was samsung faulty software update.
    I’m so angry for them how they can ignore it.
    never again. poor service

  20. The commonality of the failure to reboot issues smells like a recall. The question is how to initiate a drive to force Samsung to recall a poorly designed phone?

  21. Hey. So after wasting two days trying to fix it the damn thing, I ended up failing and taking it to a samsung store where they took in the phone and said they will fix it for free. I explained to them that it seems to be a software issue and put all the blame on them by saying I updated my phone OTA and afterwards it’s stopped booting.

    When you hand in the phone to the shop directly it can take up to 4 weeks for it to be fixed because they need to order the parts for the note 4 as it’s an old model OR you can send your phone directly to samsung with a prepaid envelope they send you and it can take around 10 days to repair.

    At this point all data is lost. Anyway, hope I helped.

  22. my phone has the same model number..I really would appreciate it if you tell me how you fixed it when you do cuz I wanna sell it too and just get in peace cuz this shit had been causing me too much stress since it happened…thanks in advance.

  23. Also have the same problem as Jake in #4. I updated my Note 4 OTA from 5.1.1 to 6.0.1 two weeks ago and my phone got the EXACT same symptoms. Unresponsive unlock and charging followed by the freezing up until the point it completely ruined itself and have the mmc_read error. Freezes within 5-15 minutes (lasts longer like mentioned when playing music) before it freezes and I have to remove the battery to restart it. Flashing the stock firmware did not work. Even tried to fix the pit file and that didn’t work either (which people say is extremely risky). Through both Odin and Keis 3. (The download mode still works but get errors whatever I do which kinda feels like a borderline hard brick). It is extremely frustrating that this feels like its Samsung’s fault as I never rooted or flashed my phone before. My network provider is EE and the phone model is SM-N910F.

    Anyway I’m due for an upgrade in a week and a bit and already pre-ordered the Note 7 so meh… will try and fix it so I can sell it.

  24. I did not. After doing little research I came to the conclusion that doing a custom ROM on the AT&T phone wouldn’t be viable as it wouldn’t be a true flash of a new ROM, more of an overlay that wouldn’t be permanent.

    I don’t believe that Samsung would be able to accept the phone if there is different software on it either. I would recommend just sending it in rather than trying a new ROM. Seemed to be a hardware issue anyway rather than software.

  25. I’m curious… did you try to flash a custom ROM before sending it to Samsung? I’m considering trying to flash a custom ROM to resolve the issue so I don’t have to send my phone in.

  26. Mine was also repaired and they pretty much made it new:

    *01/11/2016//22:37:34//0001773863//Telephone//ASC*

    1/11/2016 9:36 PM-Asai Velazquez: The unit is shipped.

    *01/11/2016//22:36:33//0001773863//Telephone//ASC*

    1/11/2016 9:36 PM-Asai Velazquez: No hold amount

    *01/11/2016//20:58:31//0001773863//Telephone//ASC*

    1/11/2016 7:58 PM-Maria Aguirre: QC Pass.

    *01/11/2016//09:32:05//0001773863//Telephone//ASC*

    1/11/2016 8:31 AM-Robel Bezuneh: The unit has left the technician. SOLUTION: Replaced PBA – Replaced LCD – Replaced Component

    *01/11/2016//09:28:31//0001773863//Telephone//ASC*

    1/11/2016 8:28 AM-Robel Bezuneh: The Unit did not pass Quality Assurance Check.

    *01/08/2016//10:38:15//0001773863//Telephone//ASC*

    1/8/2016 9:37 AM-Robel Bezuneh: The unit has left the technician. SOLUTION: Replaced PBA – Replaced LCD – Replaced Component

    *01/08/2016//10:38:15//0001773863//Telephone//ASC*

    rear have dents and crack on charging port

    *01/08/2016//08:19:25//0001773863//Telephone//ASC*

    1/8/2016 7:18 AM-Yuri Sanabria: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)

    *01/08/2016//08:19:25//0001773863//Telephone//ASC*

    1/8/2016 7:18 AM-Yuri Sanabria: Accessory: BATTERY,BATTERY COVER,STYLUS

    A couple of days after the phone was received, it shut down by itself and was like in a loop. I removed the battery and fixed it, it has not happened since.

    My battery life now seems to be very short, less than half a day with the phone. Sometimes with around 50% left, it shuts down and I have to recharge it. Looking for solutions to that now.

  27. Just got the phone back this afternoon after the warranty work.

    Samsung replaced three components in the phone. The main board (PN GH82-08936B), CBF Coaxial Cable 33.3MM (PN GH39-01723A), and CBF Coaxial Cable 49MM (PN GH39-01727A).

    Basically, they re-newed the entire phone save for the screen and body as far as I can tell. The phone is working flawlessly so far. It seems they checked the battery as well and the battery is within spec, so it will not need replacing any time soon, though it may be done anyway with something a little longer lasting.

  28. Sent the phone into Samsung and here’s what they’ve done via their Repair Update.

    01/14/2016//14:51:33//0001773863//Web Chat//ASC

    1/14/2016 1:51 PM-Robel Bezuneh: The unit has left the technician. SOLUTION: Replaced PBA – Replaced Component

    01/14/2016//14:49:30//0001773863//Web Chat//ASC 1/14/2016 1:49 PM-Robel Bezuneh: The Unit did not pass Quality Assurance Check.

    01/12/2016//13:23:09//0001773863//Web Chat//ASC 1/12/2016 12:22 PM-Juan Hernandez: The unit has left the technician. SOLUTION: S/W Updated

    01/12/2016//13:23:08//0001773863//Web Chat//ASC S/W Updated,,,SOWARE PASS

    01/12/2016//13:23:08//0001773863//Web Chat//ASC SCRATCH IN REAR..AND LCD

    01/12/2016//09:06:37//0001773863//Web Chat//ASC 1/12/2016 8:05 AM-Jennifer Bastardo: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)

    01/12/2016//09:06:37//0001773863//Web Chat//ASC 1/12/2016 8:05 AM-Jennifer Bastardo: Accessory: Battery,Battery Cover,Stylus

    It appears that they flashed on the stock ROM again, but to no avail. Tested from there and still failed. Now they’re replacing the PBA, which I’ve researched what the acronym is and appears to be the Phone Board Assembly, main board.

    Came down to being a hardware failure not due to water damage.

  29. Same here. I just sent mine in today. It would be nice for them to find out what the problem is and let us know, whether software or hardware (more likely) issue.

  30. I stand corrected then. Samsung just approved the repair of my phone under warranty even though I bought it over 14 months ago after I explained the symptoms. They did not even try to argue or get more explanation like they already knew what it was. I sent it to them last Tuesday and should have it back next week.

  31. Not so much a T-Mobile issue as I’ve started experiencing this problem and I’m with AT&T. I had 5.1.1 for quite some time, they over the past 3 days it’s been acting up.

  32. Me too, same exact problem and T-mobile does not offer solutions to the problem. It seems to be a T-mobile issue at this point. This pisses me off bad as my phone is completely useless.

  33. I have the same exact problem as Jake in Problem #4. I did the OTA update on my T-Mobile Note 4 last week and just recently it started to develop the same exact symptoms as Jake. My phone has not been rooted and has been kept stock. It is really frustrating!

Comments are closed.