Lag/Random reboots on stock unrooted - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Hey all. I have an unrooted, stock N4 that appears to be "overloaded" and randomly lags and reboots. It's been happening for a week
I have tried the following solutions
- Factory reset
- PopRocks ROM
- 5.1.1 Stock ROM
- SD Card reformatting
- SD Card removal
- Clearing cache
I am at a loss of what it could possibly be. I am running the latest firmware for the phone now. It seems to just reboot doing the simplest things. Even scrolling through XDA on chrome was laggy as hell. I've tried searching the internet for another solution but to no avail. The only thing I haven't tried is KitKat but it doesn't make sense since I was running Lollipop with no problems until a week ago.

I have the exact same issues on my phone, completely stock out of the box. T-Mobile is sending a warranty replacement next week. Hopefully it won't happen with the new device

kitchencop said:
I have the exact same issues on my phone, completely stock out of the box. T-Mobile is sending a warranty replacement next week. Hopefully it won't happen with the new device
Click to expand...
Click to collapse
I've had this phone for about 7 months now and I got it on Ebay so I don't think there's any chance of me getting a new one from tmobile. Seems like hardware failure to me.

Related

[Q] My phone reboots after I receive a txt msg

I have an AT&T Nexus One. Got it since it was first released for AT&T never had any problems untill now.
I can do anything without problems except when I receive a text message my phone reboots. I tried factory reset no luck. I formatted my sd card wiped my phone and updated my rom from cm6 to the stable version of cm7 and it still reboots after I receive a text message. I searched google and found other people with the same problem with various android phones but I haven't found a fix yet.
I was hoping some of the genius here at xda dev could help me out with this.
My phone is out of warranty and it's unlocked/rooted.
Please help if you can.
Thanks,
Rick
*********************************************************
EDIT: Just found out that it restarts when I receive phone call aswell.
*********************************************************
This exact problem is happening with my Droid Incredible. I ran CM7 for quite a while and was just living with the problem... it doesn't happen every time I receive a text, but maybe half of the times it triggers my phone to reboot.
I have tried the following, but the phone continues to reboot on receiving texts:
- moved data off of SD card and formatted card.
- wiped data/did factory reset of CM7.
- installed MIUI rom
- wiped data/factory reset of MIUI
- deleted all backups
I'm currently running a completely wiped MIUI phone and it still reboots. I am at a loss as to what to try next. Did you ever solve your problem? Does anyone else have any suggestions?
You could try a new SIM...?

[Q] Galaxy S i9000 won't factory reset and force closes frequently - now with logcat

Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I

[Q] Faulty hardware or something else? Please help!

Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..

Experienced flasher, soft-bricked my Note 4 real good.

Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.

N920C Randomly freezing then rebooting

It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.

Categories

Resources