Hello all,
I've read and searched through a few posts before posting this, and it seems there has not been one consistent solution offered that is a guaranteed fix. And no problems that have been solved like this in the past 6 months or more that I saw.
About 10 days ago my Note 3 started doing all kinds of crazy crap. It would:
Boot up with a yellow exclamation point and says Verizon Wireless had detected unauthorized software on my device. In the top corner it would say secure fail: modem. This almost always went away with just another reboot of the phone.
Boot up with a splash screen that normally just says Samsung Galaxy Note 3, but now also has an unlocked padlock and "Custom" on the screen.
Extremely intermittently recognize that I had a sim in my phone and provision my phone on the 4g network.
Not allowi a significant amount of internet activity even when connected to wifi.
Pop up an error box upon entering the OS saying that there was a process system error and ask me to wait or kill the process.
Random unrequested reboots of my phone without even touching it. (this has happened 7 times now through the course of typing this post)
Also a problem, though not a recent development, is a common complaint that there has been significant difficulty in placing clear phone calls even though signal strength looks good, sometimes resulting in attempts to dial timing out without making a connection.
As a bit of background: I've never rooted this phone. Years ago I sold smartphones for a living and I knew how much of bastards Verizon et. al. were when it came to providing hardware warranty coverage to people who had rooted their devices. Having said that, I have no idea why I just randomly started seeing an unlocked padlock and a callout for a custom OS on the boot up splash screen. Also, I've already gone to verizon and replaced the sim just in case it was a defective chip causing these problems. There have been no significant changes, though it does seem that the intermittent rate at which the phone actually finds the network happens a little more often with a new sim. Maybe that's just my wishful thinking that my situation has improved.
Other things I've tried for troubleshooting already:
Booted into recovery mode, wiped cache, rebooted.
Booted into recovery mode, wiped and factory reset the phone from the on board restore software.
Downloaded Kies and booted into download mode on the device and pushed the current OS image to my phone.
Tried some silly battery trick that some guy made a youtube video about where he suggests pulling the battery, pressing the power button for a few seconds, then putting the battery back in will fix the problem.
This phone is out of warranty now, so I'm not opposed to trying a rooting solution to fix it -- if that is even plausible. I also downloaded a 1.6GB zip that is supposed to contain an image of the LP OS (N900VVRUEOF1_N900VVZWEOF1_VZW.zip), but have not done anything with it yet. My only concern with trying to wipe out the stock OS is that I've never attempted it before and don't want to F it up, although at this point could it get much worse??
Cosmetically this phone is in perfect condition. I'm not a phone dropper, and it has been in an otterbox defender case since the day I got it. I bought this phone outright in 2013 so that I could preserve my unlimited data plan, so I'm really hoping there is a potential solution here that does not involve buying a new phone.
Any suggestions you can offer would be great. Like I said, I did some keyword searching on this form and read a few threads before posting, but it seemed like there were a bunch of different theories on how to fix this problem and no consistent solution.
Thanks!
The forum for your phone is here .
http://forum.xda-developers.com/verizon-galaxy-note-3
Related
I've had the DInc since day -1 and haven't had a real problem until recently. Whenever the phone gets a little warm from 10+ minutes of straight use, the phone will reboot itself and goes into a reboot cycle. What seems to happen is the phone will overheat from use and then heat up some more from booting up. Once it gets to the home screen, it'll reboot again in an endless cycle. The cycle cannot be stopped unless the battery is pulled or the down key is held prior to it rebooting and shutting it down in the bootloader. The reboots are pretty predictable just by feeling the temperature of the phone. Using the phone while charging is a definite no-no for me. The only way I can get the phone to function again is to either let it sit for 10 minutes or put it in front of the AC for 5.
My phone was rooted and all roms seem to have the same effect. I've tried all hydra's kernels and all of them causes the problem, even the stock kernel. The only temporary fix was to use setcpu and enable the temp profile to lower the cpu to 500MHz at 36 degrees. This gave me extended use and was bearable but I really shouldn't have to do this. I've got so annoyed and reverted back to full stock/unrooted by downgrading with the official rom but the phone is STILL rebooting from overheating.
This is an obvious problem and I've already called Verizon for an RMA. I just hope it's not a widespread defect. It seems random reboots are pretty common with the DInc based on what I've read and other people's experience at work. There's about 5 of us who has the Inc at my job and all of our phones rebooted about a few minute from one another.
Has anyone had this issue? If so, did your replacement take care of it? I've read stories of people having to go thru four exchanges to finally land on a good device. How hot does your phones get from use and has it ever rebooted from the heat? It's a real bummer to be unable to play games on my phone for extended periods of time. The Droid X is looking mighty tempting right now
Same issue here
I've had the Incredible since day 1 (I actually upgraded from the original Droid, which I loved, but I wanted the faster CPU and more memory) and within the first 2 weeks, I got the random reboot issue, but it wasn't consistent and I believe that an OTA update fixed the problem (which was a general reception issue for the Triad area of NC).
However, the last couple of weeks, the phone seems possessed and reboots randomly and will keep rebooting until I pull the battery. It doesn't matter if I'm using the GPS, surfing the web, sending a text message, etc. or if I'm using the Verizon 3G network or my home Wi-Fi.
I tried testing various scenarios, soft/hard resets, removing my micro-SD card, charging the battery overnight, etc., but when the phone gets into one of its random reboot loops/cycles, there is no remedy but to pull the battery for about 5-10 minutes.
I have taken the phone 3 times to a retail Verizon store (that has a technician onsite) and they can't fix the phone (just keep doing factory "hard" resets).
I called HTC and they just told me how to hold the phone "with your fingertips and by the edges of the phone), and if I still had issues, I could ship the phone to them and they could attempt to repair it (but, then I'm without a phone for several days/weeks, which is not acceptable).
I have also called Verizon support and they finally agreed to issue me a replacement "refurb" phone (which I think is totally BS), but if I have the same issue with this replacement phone, I'm thinking of seeking legal counsel to get out of my contract and/or start a class action lawsuit against Verizon and/or HTC.
I've been a Verizon wireless customer for over 12 years with no issues with their "network", so I know it's an issue with this phone.
If the root cause is heat buildup, then to me, this would be considered a factory defect and all Incredible phones should be recalled (or the customer given the option to swapout to another phone, like the Droid X).
Besides the reboot problem, the phone has poor battery life (even more so than other smartphones), poor call quality, and poor reception.
Me Too
I have the random reboot issue as well, although I am 99.999999% it is due to heat. That said, heat could be caused by it trying desperately to secure a decent signal.
I really do not want to try to convince Verizon I have this problem, and have just been living with it.
Ive havent had that problem, but my inc overheats to 50°c sometimes. My advise, go to big red and have it replaced.
Sent from my Incredible using XDA App
I've got two main problems with my galaxy s.
1) Today at around 1pm I had to force close something (I don't even remember what it was. I had just woken up the phone and went to check my mail, so I assume Launcher pro or something). It kept prompting me to force close, so I just took out the battery and reboot it. The phone can no longer get passed the initial screen (before the S). I've tried to reset to factory defaults, and it still doesn't work. I assume I can re-flash (not home yet) - but I'm wondering what would cause this type of behavior. FYI - I've been running 2.2 JPH with Rombie's mod)
2) I get really bad reception. I constantly will have my phone go from no service to 3-4 bars while sitting in the same spot. I also have a problem in busy areas where I'll lose my connection completely (whereas other people with different phones seem to have no problem right beside me). Is there anything that could be causing these issues?
Side note: When I originally upgraded to 2.2 JPH I had efs issues for a while, and it took me a while to get it up and running. It's working now (phone and data) - I'm just worried there's some residual effects of a mildly corrupted efs or something.
Update...
Things have gotten worse and I really need some suggestions.
I've tried flashing about 5 different firmwares and I can't get the thing going.
The closest I've come is with the stock jh2 firmware. It boots and it goes to a black screen after the S logo. I know this has been brought up but I have not had success with solutions I've found in other threads. I've tried it with pit512 513 and 803. I've tried it with repartition checked and unchecked.
When I try a 2.2 rom (such as the latest jpk) and upon resetting in the recovery mode, I receive an SDCARD failed to mount error (although one time I also received a failed to load DBDATA error). It also won't let me format the sdcard in this screen as obviously it can't mount it.
The closest I've come to getting the sdcard working is on the jh2 firmware i can "load update.zip" from my firmware, and it seems to actually load - unfortunately that update.zip is completely useless (as it's just an unlocker update i believe) - and I can't change the update.zip as I can't access the sdcard.
Please help if you can!
I had the same problem. My phone was working fine and then it just turned off and froze. I resetted it a few times and it would go to the S logo and then the screen would go blank and the buttons would light up. Resetting it a few more times made it work once but then when i started it again the phone would go back to the same problem.
I tried a ton of rom on it and some worked (but my internal sd card wouldn't mount). The problem got progressively worse by it's self and my phone wouldn't even start now. I recently send it back to Bell to get it repaired and hopefully they don't ping me saying it was my fault for ****ing around, which I doubt they will find out at this point since the damn thing doesn't even turn on.
I researched this a fair bit (2 full nights) and found out that it had something to do with me flashing Jp3 and that set my internal sd card as read only somehow. It's a bug and if you google it a lot of people have had this problem but none had a working solution and everyone of them had to send it back for repair.
Edit: I am also Canadian with a bell phone.
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
fuffalo said:
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
Click to expand...
Click to collapse
Honestly, it is a very frustrating process. They quote you a 2 - 6 week window and do not give you any hard time table and to top that off they don't have any loaner phones that are smart phones. The loaners cost $25 and $250 down.
I had to go out and find one from a friend and even then they wouldn't let me use a CDMA phone since i had a HSPA+ data plan and it some how ****s with their system. The only way you can use a phone on their network is using a HSPA+ phone if you need data. Luckily a friend had a HTC magic that was unlocked so I am using that now.
You can try to load up the default rom that ships with it and then send it in for repair.
Is the default rom JH2?
I believe it is this one I9000UGJH2
Alright so I can adb in to my phone when it's in recovery mode.
Does this help at all? Can i try anything from here?
Ever since unlocking my phone, I have been experiencing very troublesome issues. It all started with picture messages not going through and giving me "Can't Send Message. Try Again." Then pictures that I received started coming in as "Media content in this message" that never downloads. I tried showing this to a friend of mine that also has WP7, but of course the image sent. That is literally the only picture I have been able to send in the past two weeks.
Nothing seems to affect it as far as battery percentage, signal strength, Wi-Fi connectivity, or anything.
Websites are also having a lot of trouble loading. Most won't load unless I let the loading bar get to about 90%, then re-enter the address. I also get a lot of "We're having trouble viewing this page right now" messages. Very frustrating.
The Marketplace has been having trouble loading at times as well.
Some apps and games that require internet connections are having spotty issues. Sometimes USA Today won't load any news. Words By Post gives me network connection errors. 4th and Mayor sometimes tells me I have no connection to location services.
All of this is really starting to frustrate me. I can't figure out what is going wrong. The only thing I can think of is that I Windowsbreak/interop unlocked my phone around the same time I started having issues. All I've installed is a battery percentage meter, a screenshot app, AdvancedConfig to change my themes and get rid of app dehydration, and WP7 Root Tools so I could get the 8107 update.
PLEASE, someone help me.
and for reference, I have a Samsung Focus with 8107 on it.
Oh and another issue, sometimes my phone goes through HUGE lag phases where scrolling through menus is incredibly choppy and slow. The only way to fix it is to lock the device and let it rest for a minute.
I may try and get video evidence of this.
I would do a hard reset and see how it works and then slowly proceed with unlocks/homebrews again one step at a time and make sure your phone works well before going the next step. And, make a back-up each time so you can go back one step if you find the one that messes up.
Never try to change and hack everything at once; errors can occur.
Ehh I'm really not trying to do a hard reset just yet...I'm hoping there is some magical solution to this.
SD Card?
Have you an SD Card installed and how much of it is used? Like you, I would do everything short of a hard reset to solve this problem.
No sir, no SD card has been installed into this phone. I learned my lesson after having to get a replacement when I got an irreversible card read error on my last Focus.
That being said, this is a refurbished device.
rmcgraw said:
No sir, no SD card has been installed into this phone. I learned my lesson after having to get a replacement when I got an irreversible card read error on my last Focus.
That being said, this is a refurbished device.
Click to expand...
Click to collapse
Some users were having data issues after windowbreaking. There is a fix in the thread and it's quite simple iirc. Ask in the thread.
edit: try this too
http://answers.microsoft.com/en-us/...n/6a94ab3b-484b-4f29-88b7-d752fdbe4737?page=2
Well, after failed attempts at fixing this, and even working with Heathcliff on a solution, I decided to hard reset.
Re-unlocked my phone and installed AdvancedConfig. So far everything seems ok.
I know that it resets to release 5 instead of 6 which could lessen your data , but it is easily fixed in diagnostics :
*#32489#
back 1 time
NAS CONTROL
[5] RRC(HSPA) CONTROL
1 TO DISPLAY mine read release 5 after windowbreak
I then changed it back to release 6
you might also have dualmode turned off, turn it on for better perfomance
if you used heathcliffs interop did you also go to *#94765# auto sim config?
If all else fails talk Jax he made windowbreak!
So, just yesterday, I purchased my new Nexus 7 from a Gamestop. Brought it home, started loading all my apps, things went smoothly, everything was great, more importantly, my WiFi signal was strong, even on the second floor of the house. Fast forward to today, I see I can update to Android 4.2.2, so i go ahead an load it up, it updates quick and easy. However I am noticing that the signal strength is abysmal. I can barely connect, even from right in front of where the router is located. However, any other devices are connecting just fine, such as my HTC One S running Android 4.0.4
I've searched around, but I haven't seen any fix for it. I've turned NFC off but that seems to have no effect. My sister has a Nexus 7 Android 4.2.2 and hasn't complained about this issues, so I assume not every tablet is affected
SO my question is:
What is my best course of action?
Do I factory reset it, reload all my apps, start over, and just not update to android 4.2.2?
Return it to GameStop, replace it with another unit, and hope it doesn't have the same problem?
Or do you have another suggestion?
Any help would be much appreciated! Thanks
Exchange it for a new replacement after doing a factory reset.
(You might want to first check signal strength side-by-side with the other N7 to verify it's not just a reception dead spot issue in your home)
First, the stock upgrade should not cause any problem.
Second, if something were to go wrong with the software upgrade in a way that affected WiFi, the most likely trouble would be complete failure (or perhaps intermittent signals) - not a signal strength change.
It sounds like an "infant mortality" issue - a hardware failure that occurs shortly after you put hardware in service. It could be something stupid like a loose antenna connector, but you don't want to invalidate the warranty trying to diagnose the trouble in case the trouble is elsewhere (same thing goes for unlocking the boot loader in order to re-flash stock). If it is a new device, use your warranty privileges to let somebody else figure out what the problem is.
good luck
PS it is apparent that you might be a little new to android - a "factory reset" does not really return the device to as it was when you first pulled it out of the box. It probably should have been called "Erase all user data and settings changes". When you do the factory reset, it will still be on the *new* OS - 4.2.2 - not whatever was on it to begin with. (For pure-stock, non-rooted devices, upgrades are not reversible using a "factory reset" procedure)
I've had problems with random reboots since I got my Moto X Pure last November. I kept hoping that a software update would solve the problem, but so far nothing has helped. In fact is seems to be getting worse with updates, not any better. Since I have an unlocked bootloader I can't send it back for repair, so I'm kind of stuck, but it is really frustrating.
It only happens when I'm at work, and it doesn't matter if I'm using my phone, its just sitting on my desk or if it's in my pocket. It will just randomly reboot. And sometimes when it gets in this state it will just keep rebooting over and over and I have to force it to shut down. If I leave it for a while and then restart it will be fine for a little while.
I was very excited about the Moto X as I've always had good luck with Motorola phones in the past. It has a lot of upsides, but this constand rebooting has made me question going with Motorola.
If I could sovle this, I'd be happy to keep the phone, but at this point its not really usable.
Sorr that this is a bit of a rant, but I'm just really frustrated.
Could it be related to very weak wifi signal? In my case, at work, wifi was so weak that it killed the battery because it was always searching for a network and will always gets disconnected. I solved it by disabling the wifi when at work and only using LTE.
In your case, it's worse than killing the battery as it reboots, but maybe you could try to disable wifi to see if it helps?
Thanks for the idea.
I don't use WiFi at the office. We have pico cells in the office that give really good coverage and I don't use much data while working. But I'll try disabling WiFi and see if I see any difference.
Its so random that I've had a really hard time pinpointing the issue. So any ideas on how to find out the root cause would be much appreciated.
I am sorry to hear you are having trouble. My device also has an unlocked bootloader and has began to suffer random reboots. I get them at least once a day. It usually happens when I am pulling the device out of my pocket and the ambient [Moto] display is triggered. I am running the stock Motorola firmware (May), my device is encrypted, rooted with SuperSU, and running Xposed. Any similarities? I haven't had a chance to look at the logs.
Thanks for the idea to check my WiFi.
I've been experimenting for a while and it seems that it was related to WiFi. We have a certificate based authentication on a hidden SSID wireless network. I had set this up on an older phone and it was imported as part of my Google backup. But because I didn't have a valid certificate it kept failing and retrying and eventually it would cause a reboot. I "forgot" the network so that my phone would stop trying to connect and it's been a couple of weeks since I had a reboot. So at this point I think it has been resolved.
I've had problems with random reboots
I've also had problems with random reboots. I've thought it could be SD card related or to some interplay between the SD card and Sim card.
I have had this as well... although I replaced my SIM card (for an entirely different reason) and it has not recurred... Maybe coincidence, maybe not, but for most people it is a simple thing to do.
Yeah, random reboots here too. It is not ROM or Kernel related.
I thinking it is a hardware failure. I have 6 months to go until my contract is up, so I just have to put up with it for now.
Just started rebooting as soon as I connect to my WiFi hotspot.. Within a second of connecting, reboot. It was fine yesterday!
Never had so many issues with my phone!