I recently bought a new Samsung Galaxy Tab 3 P-5210. Initially the tab would work perfectly fine for about 30 minutes and then restart abruptly and then the restarts would get quicker and quicker. Now, if I start the tab after resting it for a few hours, it works for 10 minutes perfectly well and then crashes and then gets stuck in a restart loop only showing the first Samsung Galaxy Tab 3 screen and then blacking out and starting all over again. It doesn't get better until I rest it for a few hours and then try using it. It has stock android 4.2.2 installed on it. Is it a hardware fault? Is there any software that can check the hardware components of the tab?
Wao that is bad. I truly do not know, but here is what I will do If that happen to me.
1) Lets talk a little bit more technical.
There is the possibility that the event causing the shutdown gets log by Android OS.
The problem is detecting the issue and try to undestand it from logcat.
This is what I will do:
Go to here:
Android Development and Hacking > Android Software Development > [TOOL] [LOGCAT] [VTS] Advanced Logcat Viewer 1.9.28.1000 => http://forum.xda-developers.com/showthread.php?t=2454610
download=>
Code:
http://bit.ly/16I1sXA
Extract the program to you PC.
Read, read read. jijijiji
Now hook your TAB3 to the PC and run "Advanced Logcat Viewer.exe"
Click on [Start logcat receiver]
Notice how it start dumping stuff, I know none sense to us.
Now start using the TAB3 as usual. Hopefully if it shutdown go quick and look at the output. With luck you may catch the event causing the problem.
2) If you do not catch the error: Then I do the opposite check software first! Do a backup of important data.
I then wipe the TAB3 and Factory Reset. Or even Use Odin to go back to Stock.
After factory reset try not to add your usual apps. Just the basics so you can study the TAB for a few days.
Hopefully the problem will go away.
This are possible hardware related root causes.
If you are playing a High intensive graphic game, that can over heat graphic controller causing shutdown. I seen this issues more in PC not phones. I am not saying that it is normal neither. But instead you may have a possible cause, due to overheat of GPU.
Now another possible root cause could be the overheat protector they place in Batteries this days, their there to prevent batteries from explode. Like it has happen on some Sony laptops explosions on airplanes. For this reason and depending on the cause if I have no warranty that will be the first item i will try to replace.
With luck you will get it
Thanks for such a detailed reply. I'll try it out and get back.
Related
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
focusedonsound said:
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
Click to expand...
Click to collapse
Anyone have any ideas.
focusedonsound said:
Anyone have any ideas.
Click to expand...
Click to collapse
I think it's just an hardware problem.
Something happens when a part of code is executed and the hardware does not respond correctly.
Similar problems happen with desktop computers, a faulty memory module, for example may create a reboot due to the error, or making a driver to crash. These smartphones are little computers...
This is what i think IMHO. I'm a computer technician.
PS. Maybe when you scroll faster the cpu goes at an higher frequency an becomes instable, did you overclocked it in the past? Try to lock the frequency as lower as possible with a custom kernel and verify if the issue appears anyway.
Anyway I'll pay a lot of attention flashing a new kernel or recovery on an instable phone, if it reboots during flash you may brick your device!
I hope this helps.
Thanks for the reply,
This is kind of the theory that I had but I didn't want to make any assumptions. With my computer background I am very familiar and understand how to trouble shoot problems with a computer. However phones area whole new cup of tea.
The phone resided in an otterbox which could have led to overheating and ultimately the processor going bad. I am no so quick to flash a new kernal etc to restrict the frequency.
The thing that I find most odd though is that there have been no similar functionality reports.
-Nick
Malfunctioning on Marshmallow update from Samsung.
I was going to install Cyanogen OS, but haven't yet.
The update from Samsung to M 6.0.1 seemed to go ok.
But, now I have errant screen touches, abrupt restarts for no apparent reason, and white streaks flashing on the display (intermittent).
It works fine for a few hours, then wacky again.
Is there anything that I can do?
This is the 8.4 WiFi only version. TM-7400 I believe.
No apparent damage to the display, no water damage recently, or ever.
Thanks!
I just now booted in safe mode. Seems to be working OK, but it has worked OK for hours after having the glitches the past couple of days.
Should I remove the SD card? Maybe an app on there is the problem?
What apps do you have? Use this and post a list.
http://www.onyxbits.de/listmyapps
Anyone?
I updated the few remaining apps which required it, and it's run fine since my OP.
I just now saw a white streak on the display, and a few seconds later it restarted by itself.
Thanks.
And, how much time involved in flashing Cyanogen Mod for a first time ever having done it?
Sorry, I didn't see this reply. I'll post apps list shortly..
TY.
steamrollerpark said:
What apps do you have? Use this and post a list. I'm using a different device, presently to post here.
I'll log in on affected device, of I can.
http://www.onyxbits.de/listmyapps
Click to expand...
Click to collapse
What you need to do to fix this is:
Open tablet. Pull battery out for 3 minutes , pop it back in. Close tablet, your tablet will be fixed
Removing the battery is not only troublesome but seems a little unnecessary.
You should try formatting all partitions through TWRP and reflashing the 6.0.1 firmware using Odin. I did that and have no issues with my device.
The 3 symptoms this dude has are what the battery issue have. Pulling the battery and getting into the inside are not difficult with the correct tools from Amazon or eBay and tutorials from YouTube. This fix has worked with my gfs tab s
suburbadroid said:
The 3 symptoms this dude has are what the battery issue have. Pulling the battery and getting into the inside are not difficult with the correct tools from Amazon or eBay and tutorials from YouTube. This fix has worked with my gfs tab s
Click to expand...
Click to collapse
While removing the battery can be a good idea for removing leftover electricity from the circuits and probably fixing those issues, if not careful can end up breaking some component.
He said when booting the device in safe mode all issues disappeared, so flashing the stock rom using Odin probably will solve all problems.
Hi all,
I have a vanilla, unrooted tablet which had Marshmallow installed a few weeks ago. It reboots constantly (like I am lucky to get 2-3 minutes out of it). Sometimes it reboots 7 or 8 times in a row until I give up and hold the power button down.
Have cleared cache and factory reset (multiple times). This hasnt solved the problem. I thought this might be an issue with the Google Play Store, as it generally crashes as soon as I run this (as the first thing I do after the reset) - so after one of the resets I downloaded the latest playstore APK and installed it. Also did not login to the play store in case this was corrupted or something. Have tried this without loading ANY apps other than the stock that comes after the reset - but still the issue persists.
All of the above has been done with the SD card removed - and with full charge
Generally it crashes as soon as I try and run any app or go to settings etc. This is even with the completely factory reset and wiped tablet with no additional apps installed.
Having tried everything, am down to the theory of hardware fault - specifically the battery. After the last update (which failed half way through) I had big problems with battery life and the tablet got (and still gets) quite hot. I am thinking something in the new update might have put extra stress on the battery, which after a few weeks has caused it to fail.
Is this possible, and is there anyway in logs etc to tell if this is hardware or software?
Anyway, other than throwing this away and buying a new one - am not sure what the next step to solve this is. (Maybe revert to previous Android?). Any suggestions or help is welcome, but I am thinking of throwing this away and not throwing good money after bad...
(Have emailed Samsung but of course never heard back - so suffice to say my next tab wont be Samsung)
try download your stock firmware and flash it with odin via your pc.
i had problem with my tab...i had restarts always...whatever i do, every few seconds it restarts by itself... but it works normaly on cable so i went to search for a solution and lol i laughed when i saw what was the solution...i removed the backcover fo the device and then just reatached the battery connector cable and thats it and now my tab works normaly even on battery.not sure if u have similar issue but u can try it it will take u 5 min work and also u have video on Youtube how to dissambly galaxy tab S...cheers mate and wish u good luck
I solved this prob yesterday, itb works fine nw, didnt crash since, just open the tablet remove the basttery vlean its pins then reinstall it
U can find vedios explaining hw to remomve z battery
OK - have updated firmware with ODIN (and tried 3 different versions going back to Android 5)
Have undone the back and removed battery and reset cables. Even replaced the battery with one I bought off Ebay
Cant think of anything else, must be a fault on a board somewhere...
I think she is dead. :crying:
Thanks to those who posted and sent me PM's - really do appreciate it.
By the way, it is definitely something to do with the power. When it reboots and it is attached to a USB, the screen flashes up with the empty battery (ie charging from completely empty) symbol momentarily (maybe a second or 2 tops) before flashing up with 64% or whatever the actual battery level is...
michjfro said:
By the way, it is definitely something to do with the power. When it reboots and it is attached to a USB, the screen flashes up with the empty battery (ie charging from completely empty) symbol momentarily (maybe a second or 2 tops) before flashing up with 64% or whatever the actual battery level is...
Click to expand...
Click to collapse
If your battery can go from 0% to 64% in a few seconds, the battery connector needs to be resoldered due to cracked solder joints.
This rework only takes 5 minutes , ask a repair shop or anyone knows how to solder for assistant.
https://www.youtube.com/watch?v=DaAKjmrMR2s
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.
I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!
Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.