I've just picked up a Galaxy Note 8.0 and what a fantastic tablet.
Anyway everything was going great until I noticed the time and date would reset to 10:00 on 1st January 2013 each time the device is restarted. I've done a factory reset twice now and it hasn't solved the problem.
Has anyone else encountered this little issue?
Related
Hey, everyone. I know this issue has been reported before, but NONE of the solutions are working for me. Perhaps I just have a bad Nexus.
I received the device for Christmas and it has worked perfectly fine. Super fast, fluid, responsive. Then, suddenly, I was using the device and it randomly rebooted. I thought, "whatever, this happens to all devices at one point or another". But then, after I turned it on, it got stuck on the Google startup screen for at least 5 minutes. I decided to restart and try again, but this time, it got stuck on the google screen, rebooted on its own and got stuck on the google screen again, repeating this cycle over and over.
So I went into Recovery mode to wipe the cache and do a factory reset. Not even this would work. The factory reset worked, but when I started up my tablet again, it froze at the Google screen. Eventually, it would just continue the cycle of freezing and rebooting. This is ridiculous. A brand-new, unrooted Nexus 7 on 4.4.2 should not be completely unusable. My warranty is up on the 18th, so I will probably just return it, unless someone has an idea.
Thanks.
domjd56 said:
... so I will probably just return it, unless someone has an idea.
Thanks.
Click to expand...
Click to collapse
That'a your best option. If you haven't modified it in any way then use your warranty.
I agree. Since you did not root it, there is probably something wrong with your tablet and you should get it exchanged while you can
Sent from my Nexus 7
I am going through the EXACT same thing and no one has been able to help.. What I did to fix it was re-flash the 03.15 bootloader and that allowed it to start. I think there's some tablets out there that "don't like" the new bootloader included with the KitKat update and I'm glad to see that it's not just me... At least you are able to return yours. I purchased mine back in August last year
Hi there, I have a locked AT&T Samsung Galaxy Note 4 Edge (SM-N915A) that is experiencing issues after the Marshmallow upgrade (6.0.1). I have had the following issues:
--> phone freezes (will not wake after wallet is closed and then opened);
--> the phone will randomly re-boot;
--> if phone is awake, the response times have been very slow;
--> Issue seems to occur more often when charging
The only method to remedy the issue is to remove the battery and then power back on. I have wiped cache and factory reset the unit but still experience the same issues. I went to Samsung desk at Best Buy and they re-flashed the operating system but this did not fix the issue. I finally narrowed down the issue to the Samsung Gear application (I have the new Frontier Gear S3). When this application is not running the issue seems to disappear (although still testing). I am attempting to pinpoint whether NumberSync is causing the issue or the application itself. Has anyone else experienced this issue?
Update: while writing this email, my unit just re-booted when I woke it up
Any suggestions would be greatly appreciated....
Update to issue...
I attempted another factory reset. Again, once I installed the Samsung Gear application and proceeded to setup my Gear S3 wearable, the phone started to "act up". Details on setting up Frontier Gear S3...
--> Downloaded/Installed Samsung Gear application
--> Used "Connect to New Phone" to setup Gear S3
--> Setup and Activated NumberSync
After this process, phone response time was sluggish and then froze. I pulled the battery, and then uninstalled the Samsung Gear application, and the phone seemed to recover. After some careful thought, I performed a complete factory reset on my Gear S3 wearable (in lieu of using "Connect New Phone"), then, I re-installed the Samsung Gear application. The phone seemed to be functioning as normal. I proceeded to setup NumberSync and again, the phone was still functioning as normal for most of the day. In the evening, I setup the wearable (added back watch faces, setup S Health, added localized weather and setup notifications). The phone still seemed to be fine. I plugged the phone in to charge (fast charge) and left the phone alone. Came back several hours later and the phone had froze. I concluded that my issue is directly related to the Samsung Gear application although I am continuing to test.
UPDATE 4/5/2017 - After experiencing 2 weeks of freezing, slow response times, removing the battery, numerous re-boots and factory resets my phone finally died (would not power on). I finally succumbed to calling Samsung Customer Care. I sent my Note 4 in for servicing on March 29th. Here is the response: Problem found: NO POWER UP - IF/CHARGING PORT - FWT - LOW BATTERY (STBY) Solution: REPLACED PBA - REPLACED COMPONENT. I think this means they changed out the motherboard and also replaced my battery. My Note 4 is performing flawlessly thus far. The only issue I have is the timing of all of this....I started having problems directly after the Marshmallow (AT&T 6.0.1) upgrade. My wife and son have the same phone, bought at the same time, and are also having issues but not as profound as mine.
Maybe it has something to do with the notifications on the Gear? My phone was aggressively rebooting after a notification from Hangouts would arrive. I have the Gear Fit 2.
I was just about to give up on this phone today, but I'm hoping that removing the Gear app may stop the freezes.
Followup from earlier. Nope, removing the Gear app for me didn't fix my phone. I'm not getting reboots, but it is still freezing up. Sorry dude/ dudette. I think I'm going to have to bow out of the Note 4. It was a great phone for me.
Same happen today to my SM-N910A. It happened after half of a year successful run with 6.0.1.
Erasing cache and factory reset bring no results.
Unfortunately the phone looks slow even in recovery. Is it a hardware failure?
filon said:
Same happen today to my SM-N910A. It happened after half of a year successful run with 6.0.1.
Erasing cache and factory reset bring no results.
Unfortunately the phone looks slow even in recovery. Is it a hardware failure?
Click to expand...
Click to collapse
My issue turned out to be a HW and battery issue (as noted in my original post above (updated))
cswackha said:
My issue turned out to be a HW and battery issue (as noted in my original post above (updated))
Click to expand...
Click to collapse
I've been having the same issue for the past year after the update to 5 and i've researched and purchased 5 new batteries as that somewhat made the issue better but it freezes sometimes up to 10 times a day. currently i can't get it to actually boot. usually i can get it working but i'm so upset with theis phone. for the 1st year it was great. purchased dec of 2014 on the ATT Next plan. I think i have 1 more payment but there are no phones ATT offers that I like. I'm calling Samsung.
Hello all,
My Pixel XL randomly started resetting on its own and then gets stuck in a bootloop. It used to reset 1-3 times a day a do this (Its been going on about a week now), but the last couple of days its been doing this several times an hour. I can get it to stop the bootloop and finishing turning on by pressing the power button a bunch during the loop, but it will shortly reset and start the bootloop.
I can't even power my device off, because before it can finish powering down, it will reset into the bootloop. I have contacted Google, and they weren't much help. They said they can send me a new device, but it will be a week or two. Any suggestions on what I can do in the meantime to try and fix this? I've already done a factory reset and that did not help.
Thanks!
This keeps happening to me. Any luck finding a fix?
Same here. I updated to the latest patch a few days ago and now my Pixel (not Pixel XL) goes through bootloop a few times a day...
I've had similar issues with my Pixel XL recently. It started with a random reboot, after which it just ran really slowly, with apps telling me they weren't responding or the whole thing just freezing up. Shortly after that it went into a boot-loop (boot, input PIN to unlock, screen freezes, auto reboot, rinse/repeat).
For me, a factory reset would solve the issue for a couple of days then it was back to the same problems.
I returned mine to the shop this weekend, and they have sent it off for repair/replacement; in the meantime they've given me a basic Android loan-phone.
Sorry; I'd like to tell you I had a fix for this, but I just wanted to say that I too experienced this issue and simply took it back for replacement/repair. I guess it depends where you bought it (I got mine SIM-free from a shop in the UK) for them to offer something else to tie you over.
Hello everyone, so i got my device yesterday, it's the NA version and it was ok, today i recieved the update of 100mb(same version as the first one) 1nd it fixed the gpay too. But the phone shutted down alone twice and only been able to boot by volume up and power. I dont know if it's because of the update or no because it's been only 2 days since i got it. But am i the only one who got the sudden shutdown? Didnt the OP 7 pro has an issue like that??
Edit: by the end of the day, it happened for the 5th time now. really ?!! I'm the only one?!
Edit2: i did a factory reset and i hope it fixes it, will keep updates
Edit 3: factory reset didnt fix it, but what did( and i hope) it's disabling the bubbles notifications, so it didnt happen since 3 days now.
Hey everyone my totally new 20 bought A72 randomly freezes and restarts. Does it every now and then (e.g. did it on Friday then again today). I ve made a factory data reset as well as a clear cache partition in the meantime. Do you think it might be a hardware issue? It is not super often but consider it as once in 3 to 4 days. Should I bring it to samsung for a check?
If it does it at the same time, on the same days. Try checking the auto restart feature.
Otherwise, I'm inclined to believe that it is a hardware issue. You should get it checked at Samsung.
One thing you can try as well is flashing the official firmware using Odin.
No unfortunately it does it randomly. I thought about flashing the firmware since it got a bit better after the factory data reset but i m afraid it needs to be checked ... unfortunately