[Q] SM-T311 4.4.2 OTA update problem - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hi guys,
It's been a long time I've posted on this forum, I'm really happy to see that the community it's always here.
I have changed my SGT2 7.0" to a new SGT3 8.0" which i really love and it was working so well that i have never take into consideration rooting and changing roms.
The problem starts about last week or two, when a popup message tell me there was a new update for my device (4.4.2).
Everything go well as expected, the update is working but the next day I realize i have a big problem: my tablet now doesn't charge to 100%!
Thinking it was my fault I have rebooted the device and it seems that this trick help a bit (after one or two reboot the tablet start charging normally and go to 100% without any problem) but i have no time for this, i wake up in the morning at 5 am and i have just the time to take a coffee before going to university, this mean no time for:
1- Reboot the tablet
2- Watch to see if it is charging, if not repeat step 1
3- If it is charging, wait for completely charging
And by the way this problem happens every day.
Yesterday I have done the root in my device and now i'm here to ask you: what can I do to solve this pathetic problem without changing rom?
In twrp there isn't an option for "wipe battery stats".
I have attached 3 screenshots from my tablet settings, you can really see what's going on.
As always, sorry for my english
Cheers

I think i have solved the problem.
-Open the tablet
-Disconnect the battery (no need to remove it, only unplug the connector)
-Press the power button for a generous amount of time (from 30 to 60 seconds to make sure)
-Reconnect the battery
-Close the tablet
-Turn on
This seems to work, my tablet is now charging normally as before, without worring about reboot it every morning and wait for fully charging.
Only time will tell me if it's a permanent fix, surely it's not an hardware issue because BEFORE 4.4.2 UPDATE the problem doesn't exists.

Related

[Q] [D2LTE] CM11 Sudden Death issue

Hey All,
I'm currently on the CM11 04/22 nightly, and have made it all the way up to the 04/27 nightly to try and resolve this issue and have not been able to. Basically - the sudden death issue has been hitting me very hard - I can't use my phone at all.
I understand the 04/11 nightly is stable and doesn't have this issue, howevery CyanogenMod does not have this on their website.
Does anyone have this install available? (CM-11-Nightly-20140411-D2LTE.zip)
Thanks so much in advance
SLiK
please explain what you mean by sudden death? thanks
rkant18 said:
please explain what you mean by sudden death? thanks
Click to expand...
Click to collapse
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
SLiK786 said:
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
Click to expand...
Click to collapse
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone: https://www.youtube.com/watch?v=3Glllc7bEJs
Good Luck
imcol said:
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone:
Good Luck
Click to expand...
Click to collapse
I'm fairly confident that this isn't the power switch. And if it were I'm not sure how comfortable I would feel breaking the power switch off.
The thing that begs me to think this is a software issue is that I'll have 45% battery, the phone will die, and then I'll try to turn the phone on again only for it to tell me I have 1% battery left. I'll put the phone on charge (after it dies again) and it will say charging - 45%.
Anyway I've rolled back a few updates and it seems to be fairly usable now...
Try cleaning the USB port real well and don't use a cheap cable. Use a needle and make sure there is no lint packed in there. These things can cause the phone to cycle itself even when not plugged in. I've fixed several doing exactly what you describe.

[Q] Need Help Plz phone won't start

hi guys,
i have a serious problem
i just drop my lg g3 in water by mistake so i remove
the battery quickly , after a time i wait for it until
the water inside go away
the first time the phone works fine
so i turned it off , and plug it into charger
i charge it a bit
when i turn it on
it wouldn't start and stucks in the first opening
so i flash an official firmware
the flash pass fine
but it start fine then show the small green android of recovery menu
and come back to first opening again
after a wait of 5-7 minutes it goes to the animation opening
but it stucks there just repeat and repeat again, i wait it more
than one hour but nothing
i flash it over and over and always same problem
so guys can someone please tell me what's exactly the problem
Dz-Doflamingo said:
hi guys,
i have a serious problem
i just drop my lg g3 in water by mistake so i remove
the battery quickly , after a time i wait for it until
the water inside go away
the first time the phone works fine
so i turned it off , and plug it into charger
i charge it a bit
when i turn it on
it wouldn't start and stucks in the first opening
so i flash an official firmware
the flash pass fine
but it start fine then show the small green android of recovery menu
and come back to first opening again
after a wait of 5-7 minutes it goes to the animation opening
but it stucks there just repeat and repeat again, i wait it more
than one hour but nothing
i flash it over and over and always same problem
so guys can someone please tell me what's exactly the problem
Click to expand...
Click to collapse
My daughter ran her d851 through the washing machine, and it is fine. There's a guy on youtube that puts his in a bowl of water, turned on, for an hour without any problems. The phone is pretty water resistant.
Bearing that in mind, I'd be more suspicious that your issue lies more with a bad flash than any permanent damage to the phone.
What particular model do you have?

[Q] Device reboots after SIM unlock

Hi all,
recently my D855 with v20T (root/xposed) started to sort of randomly reboot. It seems like once the device gets too hot, it's gone.
Happens rarely during general usage, often while playing a game, and especially often when starting the camera.
But it behaves strangely in general: if I do *not* unlock the SIM (and thus can't use the phone), the device runs forever, without a reboot, no matter what the device temperature is. Same for recovery (TWRP), it can stay there for hours and heat up however it likes, no reboot.
Removing the SIM and/or microSD does not make a difference, battery level does not matter.
I pulled a backup of the stock ROM, wiped everything (system, data, cache, dalvik) and flashed Fulmics 5.
Unlocking worked once or twice, the next time I entered my SIM pin, the lock screen showed, then reboot. This behaviour (unlock SIM, reboot) repeats endlessly. If I leave it turned off for 10-15 minutes - or sitting at the SIM unlock screen - it most of the time works fine after unlocking.
Wiped again, flashed robalm's v30F ROM.
Guess what, exactly the same.
On both variants, the phone got rather hot during the "optimizing app x of 190" screen, but never rebooted, only after I unlocked the SIM.
Let it sit overnight on the unlock screen, no reboot at all. Unlocked this morning, added my google account, rebooted - same thing again.
It's starting to drive me crazy, now it froze right in the middle of setting up the google account after another clean flash.
Is the phone prone for repair, or can anyone think of another solution to this weird issue?
Edit: Fun fact: if I manage to do the lock screen swipe before the SIM lock screen comes up, the phone reboots instantly as well.
Edit2: Followed the instructions from this thread to go back to completely stock v20T. Rebooted after optimizing apps before I could even choose a language, ran seemingly fine after this, started bootlooping after the first manual reboot. A full wipe later (volDn+Power) it at least boots. What the hell?
Thank you and best regards,
Sub
I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.
foxracer89 said:
I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.
Click to expand...
Click to collapse
Try a new battery
Anik49 said:
Try a new battery
Click to expand...
Click to collapse
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub
subworx said:
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub
Click to expand...
Click to collapse
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....
Anik49 said:
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....
Click to expand...
Click to collapse
I used to have thermals installed, the 75 dregrees Celsius variant, iirc.
Everything else was at stock, except for one short excursion to CM12 and one to ... some custom ROM.
Think I never actually took 4k videos, and the first 1,5 years the phone got a bit warmer but never really hot. Only recently it started to get really hot especially when using the camera, this also consistently was what could cause the reboot loops for sure. Other candidates were a few games which use more processing power like Alto's Adventure.
The battery drops by 2-3% after a reboot, because of the load the phone has (and the heat it develops during boot).
Anyway, I added the screenshot to the next repair request, and the woman at the counter said they'd look into the battery specifically (it seems to give out too much voltage, she said), but also check everything else once more.
I'll let them repair up to three times, then ask for a replacement, should be legal within 2 years after purchase in Germany.
Also, next time I'll take the 15 minutes (before doing a 1h/direction trip) to factory reset the phone, set it up and start the camera. If it reboots during any of this -> return, repeat.
Regards,
sub
Received my phone back from LG, finally.
Battery's broken - it outputs too much power.
Ordered a new battery and just put it in, so far no reboots during setup.
At least this got me a new mainboard and new IMEI
Regards,
sub
Hahahahahahahahaha
I just wondered why the phone shows 25 GB free everywhere, even without SD.
Turns out, during repair instead of replacing the 16GB/2GB board with an identical one, they installed the 32GB/3GB board
\o/ for LG

Rebooting every few minutes - my tablet now resembles a potato

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

Random Reboots?

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.

Categories

Resources