So, here is my problem. I've got an almost four years old Note4. I flashed some custom ROM's after i bought it but then I found an old X-note 4.4.4 based custom ROM and i was using that for more than 2 years. Yesterday around noon i noticed that if I try to use Viber, it takes seconds till it opens, and lags badly. (Before that the phone was working perfectly for years). I deleted it, reinstalled, but the problem stayed the same. After a few hours all the other apps started to do the same, the phone became really laggy. As time went by it got worse and worse, around 8pm it started to freeze, reboot, became almost completely useless. I thought maybe a factory reset and a new flash would help. I did a factory reset, and flashed a completely stock ROM on it. It started well, was working good for an hour or so, and then the same problems occured again. Lag, freeze, reboot.... And then nothing. Did not even restart. I can switch it on every now and then, (like in every 20 minutes), but it boots into odin mode. I thought maybe the battery, but that is less then 2 months old. Anyone any idea what happened? I mean the phone is almost 4 years old, so I'm not really pissed off, the only reason why I wanna keep using the Note4 cuz it's removable battery. I don't like phones with built-in battery, this is why i did not upgrade to Note8 for instance. Any help would be much appreciated. By the way, my device is an SM-N910F.
Well, things got even weirder later. I found my old battery which i replaced 2 months ago, still had some juice in it, i put it in, and the phone started!!! Worked perfectly, for about an hour and a bit, then the same problems occured again, lag freeze reboot, and now it boots itself into recovery if i can start it up at all... All the same story. Anyway, i threw it in the drawer and bought a new phone.
Related
Hello lads! The last few days I have been trying to fix a huge problem with my Galaxy S4 i9505. I had been using the Google 4.4 rom for almost a month without any problem. One day, when my phone was low on battery it shutted down and I plugged it in my charger to power it on again. When it turned on I was prompted to the screen you see when you use the 4.4 rom for the first time. I had all my apps but everything was resetted. Every setting, all the app data, messages, etc. I thought this was a one time thing so I used about an hour to get everything back to normal again. Then the next day, same happened again. Phone turned off because of low battery, and everything was reset. I tried to google it but with no luck, so I did a factory reset and flashed the newest Google rom (4.4.2) with a new kernel called Ktoonsez. Got everything back to normal again and used my phone for a couple of hours before it just suddenly shutted down once again, but this time with almost full battery. When i tried to turn it on I was stuck on the Google loading animation and had to reflash 4.4.2. It turned back on and this time I decided to let the phone stay stock to see if any of my problems was caused of my apps or settings. It lasted for 2-3 days before the same thing happened again... I tried to flash different modems, other roms and firmwares but nothing have helped so far. I am also prompted with a message each time I turn the phone on which tells me that com.android.phone has stopped working. I have tried several factory resets, wiped dalvik, wiped cache, but still has the same problem... I have now given up trying and wonder if anyone of you know what I can do to fix the problem? Any tip is much appreciated and I hope to hear from you! Thanks!
Fredrik
Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone
Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.
Currently I can turn on the phone, but after I turn the screen off, it won't come back on again
Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.
I've used 2 different ROMS, AOSP extended and Pure Nexus. I've tried using custom kernels and with the default one that comes with the ROM. I've tried going into safe mode. But my phone still randomly reboots. I found that it restarts much more often when I open the Google Maps App, and sometimes camera app too.
Unlike other people, the phone can stay on for a long time if I don't touch it and just keep it in my pocket; it doesn't reboot.
Is it a software or hardware problem? Is it because I am trying to use Android 7 on it?
My phone rebooted during two consecutive nights, a few days ago. It happened between 6 and 7 in the morning, while the phone was lying on my desk, in flight mode. I always put my phone (and previous phones) in flight mode when I go to sleep. Battery usage showed how long ago the reboot took place. The first time my battery was drained from 50% to 20%, second time it didn't (stayed around 80%). I made a TWRP backup, and planned to restore a backup from a few weeks back. Due to lack of time I didn't do that. The reboots didn't happen after that.
The first reboot was after I installed GlassWIre in the afternoon. I uninstalled it after the first reboot. So far I have no idea what caused the reboots.
My phone is on stock 6.1 with january 2017 security patches, and is rooted.
This is a weird one.
No problems until I switched my SIM out (went to a different carrier) and since then any app that tried to access the GPS causes a reboot.
Read that I should change my APN type to "default,mms" so I did so and rebooted, have not had any issue since.
Hi everybody,
So I have a S7 Edge that I buyed in Spain in December 2016, so it has a year and a half by now.
The phone have the Gorilla Glass a bit broken but the display is perfect aswell as the touch, the back is also broken, main issue there was a corner fall but, this either started nor agraviated the issue in hand, it was no difference between before and after that situation.
The phone was submerged in water, less than a meter for less than 5 minutes, again I dont remember that this issue started nor agraviated the issue.
Now the issue I'm not sure when it started but it was this year for sure, maybe 2 to 3 months ago.
As far as I remember the issue started after a Samsung update, a large update like 1 Gb, the phone restarted to install the Update and during the Update it froze while installing the update in the boot and started heating up I wasnt able to do a thing I wasnt able to either restart it nor shutdown it, so I just waited until the batery run out wich it wasnt much time since it was heating up a lot.
After it shutdown I charged it and then started, it was able to update but from that point I didnt want to either shutdown nor update the phone again being afraid of the phone dying, so some day the phone forced another update, and I encountered the same issue, after that once in a while the phone restarted.
From that point I dont actually remember how it happens if I had some issues but one day the phone restarted and entered a boot loop restarting the phone after a second or two of the Samsung ROM splash, so I tried to shut it down and wasnt able to do so, at some point it "shutdown" but with a red led on and I wasnt able to start it, after 3 to 4 days the light went off (batery run out) and then I charged the phone again but wasnt able to boot up, after a few restart it boot up but then restarted and loop again.
After a few tries I was able to Factory Reset the phone and the phone started functioning kinda alright, I installed an app and while using it the phone restarted so I uninstalled the app, after that the phone didnt shutdown, so I used the phone for some days and never shut it down nor let the batery run out, till one day I updated the apps from the Play Store while updating the apps the phone shutdown again, boot loop and subsecuently shutdown with a blue led this time and not being able to start the phone again, so I waited like before, but for some reason the blue light stayed for like 2 weeks, I guess the phone has a lot of charge and the only thing using the batery was the led I dont know.
After all this I decided that the problem was a Software problem since all the main issues apeared while updating apps, updating the system, using apps, etc, so because I didnt have guaranty I decided to install TWRP and then some custom ROM, so I do it so, I installed TWRP, booted into TWRP, backup EFS, wipe dalvik, cache, data and system, in this process the phone rebooted, boot loop and then again blue led and not being able to start the phone, so I was tired by now and I opened the backpanel breaking quite a bit one side didnt care if I fix this I will change the back and front glass, I detached the batery and the phone shutdown then I was able to start it, boot into recovery TWRP and installed HavocOS this time (I will try with another one just in case), I installed it run it and it appears to be working fine... it rebooted one time and after that nothing I installed Whatsapp a 2.3 gb backup started to download alongside 34 apps from the PlayStore I guess the apps that I had in the previous installation.
While downloading the 34 apps the phone restarted I guess while installing Facebook, after that it shutdowns again after apparently working just fine for an hour or so.
So I decided to install again HavocOS but dont instal any APP but Whatsapp, maps and some other things I need (Keepass, Bank stuff, etc) but from here on the phone started to reboot even in TWRP, while installing the ROM sometimes it freezes sometimes it shutdown sometimes it rebooted and antered boot loop but at least it didnt get stuck anymore I was always able to shutdown and start the phone but with boot loops and shutdowns and totally impossible to use.
So now I'm almost totally sure that it is not a Software (free fix) problem, and now I'm thinking in replacing the batery, the batery is not very expensive (compared to a now phone ofc) but it is a bit expensive for my economy and I'm not totally sure that the batery is the problem, can somebody, with all the information given here tell me something like "I'm at least 90% sure that the problem is the batery"?, cause, I'm a PC Technician that didnt know much about phone but they are practically the same as a PC but less modular and sincerilly I think that it might be the Processor or the Internal Storage, both non-easy-removable and change and both more expensive than a batery and both things that I have to buy outside of my country that may or may not come in 1 to 3 months so, is it really worth buying a batery or this issues point to a direction that the phone is almost imposible to fix with the money I have so its better to save money and buy a new one... thing is in this effing country a new S9 for example cost 1000 u$s and my salary is 600 u$s so its a bit anoying to save for something like that, even a new S7 Edge is worth 600 u$s here, and thats what I paid in Spain one and a half year ago when it was the latest Samsung phone available.
Sorry for the long post I wanted to explain everything throughly and I hope my english is ok.
Best regards.
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom
Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.