Database Users

Phone crash after battery died!!

my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..

Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje

Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?

everything was stock on mine, no root.......maybe thats why i could recover it??!!

Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.

I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.

Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions

That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!

I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1

Note 4 freezes while charging after lollipop

I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.

ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late

jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?

ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).

Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.

Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.

Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1

I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.

I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).

Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.

same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..

Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.

With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO

I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.

S5 SM-G900F : Black screen/Boot loop; Help?

tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits

Moto Z Force - Restart Loop

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.

Galaxy Note 4 keeps freezing after 2mins usage, gets in bootloop

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