A few days ago we purchased a couple of Samsung GalaxyTab A 9.7. For some reason that I haven't been able to work out two of them will reboot every now and then, there is no pattern to it, it could take a day or two and then it will reboot while reading a book. Or another example I decided to do a factory reset of the tablet to see if it was the kindle app or the SD card I put in it, so with nothing in it after doing a factory reset and while updating the preinstalled Galaxy Apps it once again restarted. Just wondering if this is an issue with the tablet or just the buggy android 5.0.2 it is running.
I've had one for a couple weeks now with the same restarting issue. I've hard reset and cleared cache at the recovery menu with no luck. Hoping it's a 5.0.2 bug, because I bought for use while instructing.
We have three, one of them isn't doing it. We took one into the shop, did a factory reset so they could send it back to samsung. The stupid assistant manager had a look at it and said oh the sleep is set to 3 seconds, he set it to 30 minutes then said it was fixed, he couldn't comprehend it was set at that because it had been factory reset to send up to samsung. Then we came home, let it rip to Samsung and they wanted both sent back. According to the samsung rep they haven't heard of this happening with this tablet.
Thought I would update this thread. The shop rang today and decided that they wouldn't wait on Samsung so replaced both tablets that were having this problem. Got home, charged the first replacement tablet, then set it up, as soon as it gets past the set up it reboots. then basically within a period of 10 minutes it reboots 5 times. Second replacement tablet so far seems alright. Samsung want the replacement tablet sent to them, so my advice dgr00s is get in touch with them and get a replacement.
So, i've been troubleshooting and whatnot. I used Samsung SmartSwitch and initialized the tablet. I used it all day at work without issue, today. Could be coincidence, but I will let you know if the reboots return.
Sorry for your bad luck. You could try the initialize with SmartSwitch to see if it resolves your issue.
according to samsung it was a fault with the tablets. all faulty tablets were returned and replaced all is good now, samsung have three faulty tablets to mess around with
Related
Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
Got mine from amazon on launch day. From second day, it reboots many times (more than 10) a day, whether in use or left alone. Last night it even hung at the Samsung glowing logo, and needed a factory reset/wipe via recovery.
Just me?
I'll be returning it to amazon unless someone can show me what to look at to see a likely cause/fix? Happens with or without the SD card present.
I've seen a few mentions of this behaviour with earlier galaxy models. Not sure if there was a fix for these, either?
Device is not rooted, or otherwise modified. Using GiffGaff SIM.
Thanks for any advice.
Hello sorry to hear that
I've had mine for 2 days now and not one reboot, so am thinking yours maybe faulty
Did it start happening from the first boot or after an app install?
Sent from my GT-I9300 using Tapatalk
it wasn't until the second day, so all of my existing apps were installed fine from Google Play store long before then.
No reboot issues here after 3 days. Maybe you should try a Full Wipe/Factory Reset and see how that goes?
No reboots here either, not even while stress testing. Sounds like either a specific app is causing it or you have a hardware problem.
Is there a way to view the kernel log after a crash? I saw 'adb shell cat /proc/kmsg' but this gives 'permission denied' (because I'm unrooted?)
Just an update: amazon replaced my faulty phone and the replacement hasn't rebooted once in several days. Perfect! Clearly something wrong with the hardware of the original unit...
Using since 25th may not a single reboot. O/c'd @ 1700mhz now
3 days ago I've ordered a brand new Galaxy S2 (Samsung CPU version) Right after ordering the S2 I've got brand new 3G SIM CARD subscription.
Placed the SIM inside of S2 and turned on the device after a full charge. Few hours later after it was charged the device got into "black screen" and rebooted it self.
I hoped its a one time thing but then later the same day and the next day it happened again. I've decided to reload a fresh ROM and hopefully it gets solved but even with the new ROM I had the same crash and self reboot two or three times during past 2 days.
Last night I've decided to try and pull off the battery for 2 hours and plug it back. Since then it didn't happened again for 20 hours approx.
However during my research I have found the following forum thread: http://androidforums.com/samsung-galaxy-s2-international/342229-s2-keeps-rebooting.html it says about many people that had same problem some people had it right after they got S2 same as I did and some people had it after few weeks or year...Some people had it even after Samsung has replaced their main board/device.
The question here is following: What If it will happen to me again?
I don't want bring it to store and stay without a device for 2 weeks until they fix it. I dont think I want 2-3 days old product from Samsung to be fixed. I didn't paid for such expensive device to not use it after I paid for it a full amount. (The computer vendor store where I bought it, they have a paper on the wall says that mobile phones cannot be returned if turned on or opened and that lab service takes 14 business days if something needs be repaired, they can either repair or give refurb/used replacement after this 14 days.
Also, If it will happen again on my device, How can I have full trust back in S2 after I had this issue and was reading all this information at the forum?
Looking to hear your thoughts
SOLUTION!
Oh man! This is really bad. living without a phone for two weeks is better than living with a phone that hangs and reboots everyday.
Don't decide now, use it for more few days and try many rom and kernels that you can and atleast try everyone of them for one battery cycle or two. And if after this it happened again I think you know what to do!
That rule doesnt apply to faulty stuff.Take it back for a refund-or at very least gwt it swapped for a new one and let the vendor piss about with Samsung
Sent from my GT-I9100
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.