Starting on the first week of 2019, I have experienced problems with my Tab3 7 Essentials tablet that I bought 7-8 months after its initial release. I enjoyed it until that following day.
The problem first started after I am updating some apps from Google Play Store. I tried to update it, but got an error of -504 after 5-10 minutes of trying to install (not downloading from WiFi). One reviewer even said that the same thing happened on his device which runs Android 5.0.
I tried numerous apps to install/update, but the same problem, even for the apps that are not installed yet. I restarted my tablet.
The tablet went to the manufacturer bootlogo (right after the initial bootscreen with "Powered by Android" text) and instead of taking the regular time (about 15-40 seconds), it went up to about 7 minutes of the bootlogo to just start up.
I then tried to install/update my apps again, but this time, Play Store gave me an error of 910 (again install). Even Play Store is unable to update itself, but it either gives up and makes me unable to open Play Store until I restarted my tablet, or the tablet automatically restarts which took about another 7 minutes. What's weird is if the tablet has automatically restarted (soft reboot) because Android crashed, the logo doesn't show up but it boots up normally.
Also, my apps are soon going to be dependent on Lollipop and above, by making them incompatible with Jellybean, or my apps that I'm going to install isn't compatible with Jellybean.
I scanned my device for suspected malware by Malwarebytes, but nothing is found except one of the system apps (related to system update) that has Adups. None of the ads show up yet.
My firmware is updated to its latest version, if it helps. It originally came with the S00025 firmware and I'm running S000028. Each upgrade took around 30-35 minutes to optimize all apps with the black screen.
I knew that Lollipop should run correctly, because I have another tablet, which runs Jellybean, that works correctly except the ghost touch issue. Is there any solution to get out of this problem where I can't install some apps and the tablet taking around 7 minutes to boot up?
Sent from my Lenovo TB3-710F using Tapatalk
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
slow boot Tab3 7
tried volume UP + power and reseted cache -> no changes
EoflaOE said:
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
Click to expand...
Click to collapse
finally reset to factory solved issue - booting 35 sec
nEON7T said:
tried volume UP + power and reseted cache -> no changes
Click to expand...
Click to collapse
Related
I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Ctrl_Alt_Del said:
I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Click to expand...
Click to collapse
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
NaminatoR1254jaime.sier said:
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
Click to expand...
Click to collapse
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Ctrl_Alt_Del said:
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Click to expand...
Click to collapse
Unfortunately I'm in the same boat. I never rooted my shield tablet so the lack of otg support and always having the optimizing app on reboot sucks.
I hope nvidia puts a pach out soon
OTG should work if you power on the tablet with the OTG plugged in...pain in the butt...but better then nothing until they fix it.
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.
One day, I got tired of the lame and boring Kindle interface, so I decided to use CyanogenMod to fix that problem. The Kindle Model I had was the 2012 HD Kindle "Soho" model, the one they had a warning on not to mod. So I previously rooted my tablet, and after unknowingly installing the wrong TWRP version, I got Recovery Reboot from the Google Play .apk I got. The first time I used the app, it gave me a red triangle saying I should reset to factory default or reboot. Each time I rebooted got the same triangle, but factory resetting fixed that problem. I logged my Amazon account back in and got all my apps back, then re-rooted and got the Google Play .apk from before. I saw the warning about the Soho models after going back to the CyanogenMod wiki to see what I did wrong, and I gave up and stayed with the boring interface. BUT, my Kindle ran out of battery, and it automatically shut down, and when I charged it, it rebooted into the familiar red triangle. I rebooted again a couple times, didn't work, factory reset didn't work either, and leaving it on for a few hours to completely drain the battery didn't work. I think the TWRP files were still hidden in the system files after I reset it the first time, and rebooting with charging the tablet activated the reboot into recovery, which triggered the TWRP files into action, but it was the wrong version, leading to this brick. How do you fix this? Do I need a fast boot cable?
I was running KatKiss 4.4.4 on TWRP v2.6.3.0.
Lately it was getting extremely slow. Yesterday I removed some apps I didn't use anyway. I think I removed too much perhaps because today suddenly gapps and many other things started crashing.
I thought I'd just reinstall it, and discovered there's now a KatKiss 6.0.029:
https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
so I downloaded it, and all the other files, rebooted into TWRP and wiped, and tried the install - it just left me with a boot loop. Ugh.
Got back into TWRP and happened to format everything. Then I installed Universal Naked Driver 0.72 in Win10.
Current behaviour:
Regular reset: boot loop.
Power+up: APX mode.
Power+down: tiny menu, then boot loop after cold boot.
Power+down+up: TWRP.
EasyFlasher asks me to go into APX, then I select one of TWRP 2.2.1 and RogueXM and Roach CWM and even the WW_epaduser9_2_1_24UpdateLauncher.zip file, but in all cases it's just the same. There's some text output, then suddenly a 0.001ms black popup disappearing before I can read it, then the regular window says OK. BUT... there is no change at all.
Any idea what I can try? I searched a lot before deciding to ask here.
The KatKiss link above assumes that the files are already inside the TF101.
How do I put the files into the TF101? What is the next step?
After mannnnnnny hours, I actually managed to install and run the Asus ROM.
I went on to TWRP 2.8.1.1, KatKiss 6.0.029 and the belonging files. Now it's booting up Android, but... not very far.
It keeps complaining with many popups "Google Play services stopped". Is that normal for a fresh ROM?
I add Wifi - then it gets stuck on Checking Connection "it can take a while". It's now more than half an hour. How long is a "while" normally?
I gave up on KitKat 6 and went back to 4.4.4 which then starts.
Still the weird frequent popups "Google Play services stopped".
Reinstalled three times now (KitKat and gapps) and still the same problem.
Could this be a hardware problem?
Well, for all you who read all the above (no one? lol), it is not a hardware problem. It's google messing up: https://forum.xda-developers.com/ee...google-play-services-update-breaking-t3555444
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Maybe a battery issue?
a friend just gave me his very same model phone with the very same issues.. if I find out anything I'll tell you here, or if you solve it first please write down what you did.
Thanks Vibbuz.
I've been trying to download a stock firmware to flash via Odin, but download speeds from Updato are really bad.
So I managed to flash a firmware after installing Odin on a Windows laptop (painful trying to get it to work on my Mac)
Firmware installed OK, but after boot I was getting a constant "com.sec.epdg" pop-up box that wouldn't let me use the phone at all. Not sure if that's due to the tsar3000 firmware?
Wiped the cache and did a factory reset after booting into recovery, and now it's stuck in a boot-loop again (95% of the time it hangs at the Samsung logo animation)
Just tried using SamFirm v0.3.6 to find the correct file. Downloaded a 4gb file, but several attempts to extract only gives BL, CP, CSC files but no AP (throws up an Unknown Error during process).
So still stumped!
Yet another update. Left Updato running overnight and downloaded a firmware.
Flashed it with Odin, claims to have succeeded but phone then reboots and hangs at "Erasing" stage (Android logo is spinning, then stops)
I'm starting to think it's pretty broken...
I've been having this exact same issue since June. If your phone happens to boot try activating power saving mode (to reduce cpu speed) as soon as possible.
It seems that doing that diminished the frequency in which my phone rebooted. If it also helps you it might be a faulty battery that can't provide enough voltage. (I'm not 100% sure on this part though, just thought of it because of the apple batteries drama)
Please post your results! Looks like a lot of people are affected by this and it would be great if we could find the cause of the problem.
I just read your thread actually! Sounds very similar to mine.
I've got nowhere. I don't think it's hard-bricked as I can still access Odin mode on the phone, and sometimes boots to Recovery, but it freezes and various different points and is currently unusable (either freezes at Samsung logo, "Erasing" part after installing firmware, or once it started to run though new device setup then froze).
Went ahead and bought an S8, but still want to fix the S6!
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Does it have twrp? Try a non stock ROM and kernel
So did anyone manage to find an issue in this rebooting. I am having the same issue.
damir_nis said:
So did anyone manage to find an issue in this rebooting. I am having the same issue.
Click to expand...
Click to collapse
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Hello,
anyone found some kind of solution? Happened to me also - freezing, restarts and then my S6 stopped working.. Sometimes I can boot to recovery menu, sometimes it boots up to android (and then freezes again), but the chances are almost non existing. Service man told me the same thing as @ghasemzm - eMMC failure. Yes, it is completely possible, but i don't wanna believe it, because they only tried to reflash the rom. I've made some "google research" and found that there were some issues in power IC on S6/S6E. Could this be related to it?
ghasemzm said:
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Click to expand...
Click to collapse
Will test the theory and let the group know.
So i have installed philipines latest update 6.0.1 i think with PIT file provided on Sammobile.
I have tested it for a day with normal ussage like i set up every other phone and it still continued restarting.
Figured out let me test with no google account signed in and the phone is working perfectly. For a full day.
So i dont know what the problem is but i will try again with google account tomorrow for a day see what happens.
After that will install 7.0.1 uk update with PIT file for it and test with that.
I have the same problem and I am quite sure that it is the mobile hard drive.
I tried to use F2FS but didn't find a working rom for that.
Samsung refused repair because of root.... Never Samsung again!
same issues here - any solutions found? My best guess is hardware fault...