Related
Hi everyone, after trying everything I could to fix this phone I don't know what to do anymore so I'm here asking for other options.
So the story is, I was just using my phone as I usually would that day and it just randomly turned off and won't turn back on anymore.
(it randomly turned off before a couple of times but it would always turn back on)
- It won't go into recovery mode or any other of the 'modes' (I tried all the different combinations of pressing the keys).
- It's not a battery issue as I've tried my battery on my brother's phone (he has a Note 4 too) and it worked fine and I tried his battery on mine and it wouldn't work.
- I tried the 'drain' method (removing the battery and holding the power button for a minute or more).
- I tried using multiple cables to charge my phone nothing worked.
I didn't drop my phone, wet it, root it or anything and it was working fine the day it happened until it just powered off by itself. When I plug it in my laptop it would make
a sound indicating I've plugged something in but nothing happens. It was version 5.1.1 model SM-N910F.
TLDR; Is there a way to somehow recover the files in the internal phone memory?
This is happening to me as well, also started in February. I'm suspecting a hardware issue. Tried it ALL but rooting. In the past 30 minutes my phone has booted and rebooted itself till it died. If someone can confirm it is a hardware issue. Maybe it's time to unite and get it fixed for free. ~Tamarnouche
Recovering data from a brain dead phone may not be possible, as it probably need some internal component replacement which may erase the data(Mostly). Have u tried connecting it to pc? Better give it to service immediately. Good Luck.
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
HXOY said:
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
Click to expand...
Click to collapse
I have the same problem with my Note 3. Only if I keep the battery out for a long (over 24 hours) time I can see the boot logo. So if you find a solution to this kindly don't forget to tag me, will really appreciate it.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
This is my first post on this forum. I searched around here for a solution, didn't really find one matching my problem. I am not a phone wizard or anything like that either. So I'll try my best explaining my problem.
First things first:
Phone: Note 4
Model #: SM-N910T
Android Version: 5.1.1
Rom: Stock Rom
Rooted: Rooted Once and used a custom Stock T Mobile Rom Once.
Here's the ROM I used at the time: http://forum.xda-developers.com/not...10tuvu1cog2-debloated-deodexed-stock-t3175406
Recently I So recently my phone out of the blue started lagging, freezing, and restarting itself. I didn't download any applications or anything like that for it to freeze up. I was currently then on the custom ROM I have mentioned above and it was the updated version. I have tried everything to my knowledge to try and fix the problem. I have tried going back to stock T mobile ROM (currently on stock rom now) through odin and stuff. After all that, it was still lagging, freezing, and restarting etc... Ran it through safe mode and the only problem in safe mode is that the lag is gone, but the restart is still there. Running in safe mode, if I would turn the screen off and back on to unlock my phone, there would be like 40% chance that it would restart after unlocking the phone and the phone would just restart normally. Rarely, whenever my phone would attempt to restart.. I would get a "Could not boot normally" message along with couples codes below and the image of android guy. Then I would have to take my battery out and attempt to restart the phone once again.. I've wiped the cache and everything in recovery mode, nothing helps at all. Also, the phone is in perfect condition. Hasn't been dropped, cracked, no water damage, or anything like that.
This place is my only hope to fix my phone before I will go out to buy another phone from the carrier.
Thank you all for taking your time to help me
u r not alone
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964
doctor geek said:
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964
Click to expand...
Click to collapse
Well I already got rid of my note 4 unfortunately before anyone could help me here so I had to upgrade my phone to note 5 and return note 4. While I still had my note 4, I realized something weird. While the phone was lagging and crashing etc.. When I had it plugged in for charge it would work perfectly fine. No lag, it wouldn't freeze up or restart (had it running perfect for 7 hours). It was like my phone was brand new again. As soon as I unplugged it from the charger, few minutes in and it was back to restarting and all that. I never knew why it did that.
Anyone know why this mightve happened?
Might be the battery though
I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.
Huntitude said:
I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.
Click to expand...
Click to collapse
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.
d4rkkn16ht said:
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.
Click to expand...
Click to collapse
I never used finger print scanning on my Note 4. Always disabled.
Here is the story,
I flashed Marshmallow on my note 4 n910w8 via odin (I had 5.1.1). After it was done I noticed that the phone got laggy and warm. It would sometimes not boot/restart or it would shut down after it freezes for sometime. I would get the download page with mmc_read failure in red, I would pull out the battery and try again.
What I did:
*Unrooted the phone through SuperSu and flashed Twrp throughout (because it gave other errors and I had to do it again and again after each attempt)
*I tried flashing through twrp but I got the "no md5" error
*Flashed the stock ROM 6.0.1 with PIT since it gave the PIT error on odin
*Wiped cache/data/factory reset multiple times.
*I used both Kies and Smartswitch and was not successful (either read or write failure)
*Flashed the stock 4.4.1 (the original, It could not boot up once) so I returned to the stock 6.0.1
*The phone boots up 3 out 5 times and I was able to watch a full movie on Netflix and browse the web and google maps. But as soon as I locked it, It shut off and did not power up (until i took out the battery and let it cool down).
Where I went:
*A Samsung repair agent here in Montreal said that most of the time it is the Mob and that it would cost 300-400$ CAD to replace
*I went to other repair shops, a few hinted that it might just a matter of reprogramming the Mob and that it involved a risk of bricking the phone for good.
N.B: It is not under warranty and I'm not on contract, It is my own phone.
My question(s): Is there something else I could try? Is there someone who fixed the issued (Assuming it is not hardware) maybe and unbrick fix or something? And also, it there anyway to thoroughly wipe out the old installations so I could start anew?
Also I consider myself pretty knowledgeable. Or I at least learn quick. Do not hesitate to suggest something coarse for me to try. Worse comes to worse, Ill sell it on eBay for part, since it it in mint condition.
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
The Sponge said:
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
Click to expand...
Click to collapse
Thank you very much for your reply, I take it you have the same problem? I will try Wake Lock. And also I'm way ahead of you in the freezing game. Leave for 10mins in the freezer and you can basically flash anything. Also, do you a custom ROM would help?
I'm having this issue on my 2 week old Moto Z Force.
I actually noticed a similar issue on a display model in Verizon but chalked it up to just that.. a display model in Verizon and I carried on with my purchase.
I've had a few experiences where it randomly reboots and then it's good to go again. Seems to happen more frequently when the phone is in high use, so I suspected an issue with RAM being full? The restart seems to take place at the same part of the startup animation every time.
TODAY - phone was in pocket while I was on a call for work and I felt it vibrate on a consistent interval. When off the phone, I looked at the phone and it is in a restart loop. The only thing I can do at this point is hold the Volume Down key to get into BIOs (through the rebooting loop) and then I have the following uptions:
1) Start
2) Restart Boot loader
3) Recovery Mode
4) Power Off
5) Factory Mode
6) Barcodes
7) BP Tools
8) QCOM
9) Bootloader Logs
If I sit in this menu inactive for awhile it will timeout and just shut the phone off until I turn it back on and then the loop resumes. I'm beginning to think I need to go with option 5 here... any help is appreciated...
No new apps were recently installed. I barely used my phone the morning when getting to work besides charging it to 90+/- % on my way in.
First I buy a hand grenade of a phone, forced to return, and now I buy a phone that is actually showing me a big issue (it is getting hot too). I'm going to let it sit off before trying a Factory Mode. :crying:
Video of the cycle here: https://www.dropbox.com/s/v7dc6erfydj87ib/Skys Phone.MOV?dl=0
Better ask in a Moto Z Force subforum.
SteveHG said:
Better ask in a Moto Z Force subforum.
Click to expand...
Click to collapse
Thanks Steve. Any suggestion on where would be best? I would have thought the Q&A would be accurate...
I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.
I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.
broprah said:
I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.
Click to expand...
Click to collapse
Awesome! Glad to hear that it worked out for you. Fingers crossed they don't give me a refurbished model (again, mine was 2 weeks old) and that I have the same luck as you.
rmonjay said:
I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.
Click to expand...
Click to collapse
I have tried all of the options at this point and none of those work. I can't even get into recovery. Every option does the same thing... reboots, reboots, reboots, etc.
New phone should be here tomorrow. I've got the good old run around on this one though and I'm not happy about it with Verizon and Best Buy. Best Buy's return policy is 14 days and I ran into issues on day 16, no exceptions according to them and off to Verizon I go where I had to purchase a temporary flip phone for the week my phone has been out of commission.
I'm in need of a new SD card before I put anything on there, it has been flaky. The only thing I care about on my phone is the media (photos, videos, and music), all of which are on Google. The crap thing is that now I need to spend another X hours putting all my apps, passwords, etc. on it to my liking. Just did this when moving to the Note 7, then Moto Z Force, and now again with the replacement. Starting to get annoyed.
Update - when switching to the replacement device I found the issue followed to the new phone... Meaning the issue was with the SD card or the SIM card. Found it was an issue with the SD card after switching between the two phones and experimenting. Unreal. Who would have thought?!
I will be formatting the card and keeping this thread posted on if that resolves it or if it's time for a new card (as I mentioned above).
I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.
TBabbs said:
I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.
Click to expand...
Click to collapse
I just fixed my Moto Z Play by removing the SD card... for the second time... -_- I've had a previous issue where my phone rebooted as part of an update and it stopped seeing my previous SD card. After checking the SD card in various other systems, I found the SD card was completely shot. After some digging online, there is apparently an issue with the new Moto Z's that if your SD card isn't fast enough (somewhere around 85-90+ Mb/s)m, the Moto Z will slowly start to eat your SD card until it fails and causes issues for your phone. In this case, my second SD card failure was that my phone went into infinite booting loops until I removed the card. -_-
This card lasted longer, mainly I think due to the fact that it was larger and faster then my previous one, but it looks like I will need to get a new fast card.
Anyways, I hope this helps you or anyone else who comes across this thread.
About 2-3 weeks ago, the same thing started to happen to me, after that, phone started to act crazy...
-Bluetooth connection was working but glitching,
-Overheat (bottom of the phone) then started reboot in loop (until at start I'm able to turn off wifi). Did everything your supposed to do, clear cache, forget network, deleted my latest app, reboot, reboot in safe mode, remove sd/sim tray... the issues we're still there...
-After a few days of repeating all those steps (or don't know what I did), I finally got rid of the oveheat reboot loop when the wifi is on. But can only see and connect to 2,4g network, no 5g (doesn't see any) and no Bluetooth (turns on, but doesn't see anything), every other device in house works and connect like they should.
-the setting app, and the phone app started to be slow (freezes for a few seconds before the system ask you if you wanna wait or close the app, I choose wait and the app unfreeze)
-Ive tried the rsa (repair system assistant) from verizon without any fix
-finally decide to go for the factory reset. It fixed the freezing issues, works like a charm, but still no 5g wifi nor Bluetooth...
Is there a driver update possible for this ? Or because of overheat it might have damage the device...
I have the phone since September, never had any issues, went through all update, force droid edition xt1650-02, build ncl25.86-11.5, nougat 7.0 (wish verizon would update to 7.1.1 anytime soon), since its gsm unlocked, I'm using it on a Canadian network (Fido)
thanks for this thread. It was able to help me diagnose my wifes phone. The SD card she has been using since her DROID CHARGE (2011!!!) finally bit the dust in this phone. I swapped it out for a new Sandisk micro sdxc uhs-I up to 80 MB/s card class 10 and it booted. funny thing was she was not even storing pictures on the card.
Motorola Droid Z Force restarting (Bootloop)
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....
alidanwer said:
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....
Click to expand...
Click to collapse
I've had bootloops happen a couple of times for different triggers, and I still run the phone stock since release date with no updates ever taken. This has worked to correct the issue for me a couple of times. Give it a try:
Let your phone get down below 5% battery life, then plug into the turbo charger. Then fool around with whatever triggers the reboots.
Eventually the phone will not restart because the phone's battery needs to charge a little. When phone charges beyond 10% try to turn the phone back on, and see if boot loop persists. If it persists drain below the 5% battery life and try again. Usually, when I have fooled around with this scenario two or three times the bootloop has corrected itself.
Hope this works for you. Good luck.
Thanku, I will definitle give it a try .... and i am updated to nougat all updates till date installed...
Still restarts.... its been a month... without solution..
alidanwer said:
Still restarts.... its been a month... without solution..
Click to expand...
Click to collapse
A couple of weeks ago, the restart loop happened to me again, and my usual tinkering while connecting and disconnecting Turbo Charger wouldn't work. So I did some research on "stuck power button" or "power button not working".
I did the following:
I blew with my mouth over the power button (kind of like puting your lips in position to whistle)
I also gently tried to clasp the power button using a pair of tweezers, but couldn't. Instead I just kind of lifted/tugged-on the power button from the top and bottom.
I feel like I didn't really do anything, but the phone has been working for over a week now. Maybe pure luck.
Its weird, this made me think it is a hardware issue, but somehow the phone reacts as if it were software related.
Give it a try. Hope you have some luck.
Hello, so i've had this Note 4 for about 2 years, i had no problems with it thus far until recently ( 3 hours ago actually) i was just texting and browsing Instagram and out of no where the screen froze, it became unresponsive and the screen went black and started constantly vibrating so i quickly pulled the battery out and put it back in again, tried to start it again and it got stuck on the Samsung logo, i went for recovery mode and tried to look up latest cashe log and it froze right there too and restarted, pulled battery out and in again, tried to get into Recovery mode for a second time and a dm-verity verification failed error on the lower left corner popped up, i selected "Restart phone" and it got stuck on the Samsung logo again, battery in-out, tried to get into Recovery mode for a third time to do a factory reset but this time it got stuck whilst trying to boot onto recovery, and i had to out-in battery again, tried several times to get into recovery and it didn't work, i just gave up and started searching, then after 14 minutes i decide to give it another try and it normally booted up! i inserted in my PIN and browsed the apps for about 2mins but it froze, again, and the whole cycle kept repeating i let it cool down for 15mins and it boots up normally but freezes again after a few minutes of usage, i noticed that it insanely overheats before freezing (especially right above the SIM card area) and the four CPU cores are showing 2469MHz and on 100% (But that's also the case when the phone just boots up right?), Now i basically can't access recovery mode and i'm stuck with a Freeze-Reboot looped and i'm left with no other option but a full Stock ROM flash, the thing is i can't even get into recovery to do a full wipe before flashing in the ROM, can i just flash in again a TWRP recovery? and is there any way to fix this without having to do a full Stock ROM flash (i Tried the wake lock app it didn't work) and i'm on Android 5.0.1, this has JUST happened today and never before. i'm hoping this isn't a hardware issue.
UPDATE: i have just noticed something rather interesting, the phone immediately freezes and goes nuts with the reboots and failed recovery modes instantly after i connect it to a wifi network, and exactly when it's attempting to "send report", a sending report sign shows up in the notification bar and it immediately screws up the phone until i do another Factory reset, i just did another one without connecting to a wifi network and i've already gone 40mins with it without any issues but perhaps it's just because it's not on heavy usage?
Sounds like you have the eMMC issue.
You can try and reflash with Odin. Get the right version from Sammobile.
Do yu get to download mode in any of the scenarios you describe?
Try WakeLock again and select the level to 4
Having the same issue
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Cybrid013 said:
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Click to expand...
Click to collapse
If you have the Snapdragon version - it's highly possible to have the emmc problem. Which is a bummer and the phone is like dead.
Unless you can buy another 910C motherboard and swap it.
Sorry.
What is short name for emmc?
jjoeshua said:
What is short name for emmc?
Click to expand...
Click to collapse
embedded multimedia controller
Just been having a very similar problem. I posted this elsewhere, but it may be helpful:
"My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1."
Also now downloaded a eMMC bug check that says my eMMC chip is 'sane'. Guess we'll see