Related
So, for the past month or two my Charge has been great. Absolutely no problems that couldn't be fixed but yesterday this phone started crapping out. First, the phone got itself stuck in a bootloop without me even flashing any files/messing with system files in ANY way. I just noticed I couldn't install any apps through a file manager/market so I rebooted and the boot animation would never end.
I did a factory reset and reflashed Eclipse131, I didn't want to do that because I hadn't backed up my apps but it seemed to be the only way. Well, it fixed the bootloop issue but then EVERYTHING force closed. I literally couldn't do a thing on the phone, anything I tried opening force closed.
So, I used Odin to flash the .pit/.md5 recovery files to fix my phone and all was well... except now I can't recover my contacts from the SD card(so all my 100+ contacts are lost). I can download apps from the market again but installing them through a file manager causes a bootloop! I've never been angry at this phone but right now I'm considering throwing it at the wall, mainly for the 35+ apps, 7 homepages & 100+ contacts I lost for no apparent reason.
Could anyone help? I don't know what the hell is going on and I want to just install the .pit/.md5 again and sell this annoying thing on eBay and buy an S2/Prime when they come out.
I had some similar issues bizarre issues start recently. I would periodically have issues with the market, which I didn't think was a big deal. All of a sudden, my phone was blazing hot in my pocket. I pulled it out and was at the boot animation and it was just sitting there. I pulled the battery, booted it up, and everything start force closing all the time.
I couldn't isolate it because I had recently done a lot of new things to my phone in a short time. I was running GC FE, but installed imoseyen's kernel, V6 SC, Loopy smoothness, Badass tweaks, and the 3G enhancing script all in a short period.
Since all that, I simply ran eclipse with PBJ non-OC for a day and then flashed GC GBE with ext4 when Kejar posted it. No more issues, but I'm trying to be careful with what I install. I'm not even restoring stuff via Titanium right now, just to be safe.
Not really a solution or even a diagnosis of your issues, but I know where you're at.
The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
I'm on stock rooted ROM 20H sep 2018. Last time I checked (just now) this is still the latest verion.
However my H910 keeps bugging me about new update available from AT&T.
Does that happen to you guys?
It didn't give me any info about versions and so on.
Should I proceed?
I got it too. Came here to see if it was just me. I'm on H910 Oreo stock rooted.
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running RootedStock, you'll end up in a slow semi-bootloop where Android boots, you'll have about 3-5 minutes, then it will forcibly install the update, reboot, you'll end up in TWRP, and when you reboot to system (or power off, then power up later), the whole cycle will repeat.
I'm not sure how robustly my solution worked, but here's how I broke out of it. So far, about 15 minutes after rebooting, it seems to have worked. Since I'm writing this AFTER seemingly fixing the problem, I'm writing it from memory, and can't say with 100% certainty which step was actually the one that fixed the problem for me. I actually began the process of installing Titanium backup about a half-dozen FOTA-reboot cycles before tripping over another post here that advised deleting /cache/FOTA. Titanium Backup might, or might not, be an essential element of my apparent success. I honestly don't know. If you own it, use it... you have nothing to lose. If you don't already own it, try just deleting /cache/FOTA first from TWRP's file manager and see whether it works (temporarily or permanently).
Anyway... here's the approximate path to slaying the FOTA beast:
1. I installed Titanium Backup from Google Play. It actually took two reboot cycles to do this... you REALLY have to be ready to unlock the phone, launch Google Play, search for Titanium, and trigger its installation while standing a few feet from your wifi AP for it to finish the download and begin installing it before the next forced-update attempt begins. When it does, swear violently. It'll make you feel a tiny bit better.
1b. When FOTA forces the reboot into TWRP, try deleting /cache/FOTA before rebooting. It might work to temporarily slay the FOTA beast, it might not. If it does, it'll save you about 30 minutes of FOTA-reboot misery for the remaining steps. Feel free to repeat this after each of the following steps. It can't hurt.
2. On the next cycle, launch Google Play the moment your phone finishes booting, and go back to Titanium Backup. Hopefully, it'll be installing. With a little luck, installation will finish before FOTA begins. Then sigh, and let FOTA waste another 5 minutes of your time.
3. On the next cycle, launch Ti backup, give it permanent root permission, and give it permission to do everything it wants. Then, try to launch Google Play, search for Titanium, scroll down, select Ti Backup pro key, and try to initiate installation before FOTA kicks in yet again.
4. On the next cycle, launch Google Play, search for Titanium, scroll down, select the pro key, and begin installation if it isn't already downloading and/or installing. 99% likely you'll end up going through another round of FOTA misery.
4b. If FOTA is still forcing reboots up to this point, repeat step 1b before step 5.
5. On the next cycle, launch Titanium Backup, give it any additional permissions it wants, then select Backup/Restore, scroll down to "FOTA Update 8.0.0", and freeze it.
5b. If FOTA kicks in again, repeat step 1b.
If, despite deleting /cache/FOTA, then freezing FOTA Update 8.0.0 using Ti backup, then deleting /cache/FOTA again, it's still happening... well, then my solution didn't work for you (and possibly not for me. I'll start breathing again normally if my phone is still working normally tomorrow).
Anyway, hopefully this will help someone. I suspect a lot of people running RootedStock Oreo are going to get stung by this. I'd guess that more than a few v20 owners actually bought theirs long after AT&T's previous forced update, and have never actually HAD to deal with blocking forced updates with their current ROM.
It's entirely possible that purchasing Ti backup (I don't think the free version can freeze apps) will be essential for the H910 going forward if you want to keep using what was, prior to yesterday, the newest rooted-stock Oreo ROM without having AT&T's FOTA harass you every few hours (or wipe your phone and reflash once someone releases a newer build based on the current update). Trust me, you can't swat it away forever. I went through this forced-update nagging bull**** years ago with my Motorola Photon. Someday, when you least expect it, the dialog will come flying at you when you're driving and trying to select a song using Amazon Music, or in the middle of a phone call, or semi-distracted, or scrolling down a web page while the phone is bogged down because it's grinding its wheels in the background preparing to harass you about updating again, and you WILL accidentally click "ok" & have your life go down the toilet for the next few hours until you're able to dig yourself out of the mess.
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
For those finding their way here, make sure to back up in the brief period of time before you get hamstrung if you can't freeze the process. I am/was bone stock H910 and after ATT forced the update on me, my phone now won't finish starting up and functionally boot-loops now until I pull the battery.
It will start, get to the home screen, I might get 5-15 seconds of actual usable time with the phone before it freezes, goes back to the bootscreen and will get warmer and warmer and give me less and less time until it freezes in the middle of the ATT logo. Tried pulling SD card and SIM card, just in case. The sim card removal bought me enough time to get the phone to tell me it was "finished updating" but upon attempting to power down and start re-inserting cards, the phone locked up and bootlooped.
No idea what this update is for but it seems to have killed my phone rather handily, beware.
FWIW, airplane mode does not stall the update either.
bitbang3r said:
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running Roote
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
Click to expand...
Click to collapse
Hope I'm not jinxing myself, but this appears to have worked for me.
I have gotten a "update could not be installed" popup, which I'm taking to be a good sign.
Still annoying, since I have auto-updates turned off.
Ugh, it popped up again. Confirmed, FOTA is still frozen.
It initiated the update for me on its own. Luckily I noticed and plugged it in or it would have died and maybe bricked the phone.
I don't notice a difference. Same Android version (8.0) same security patch (Sept 2018). The ATT version might have gone from H to I.
Yep, it started nagging me again, too. Goddamn it, this is really starting to piss me off.
Okay, on mine I think when I delete /cache/FOTA while in TWRP, it might not actually be deleting the folder.
I deleted the folder in recovery mode, then rebooted and went straight to X-plore file manager. The FOTA folder was either still there, or it just recreated itself on boot. I deleted it again in X-plore and it's now been working since my previous post.
Fingers crossed.
I just rooted a H910 yesterday, and this morning the same "slow boot loop" with the update started. I tried different things, and what so far seems to have worked was:
1. Entered TWRP recovery (from the last "update cycle." (Not like I had a choice.)
2. Wiped everything and re-installed Oreo, and all other zip and img files back to the way I originally set it all up.
3. After phone was booted up, I DID NOT have a SIM card in it, nor did I enable WiFi.
4. Temporarily skipped all the Google sign in stuff.
5. Enabled Developer options, and turned off "automatic system updates." (Not Google Play Updates!)
6. Re-booted phone and then confirmed that the above setting still showed "off."
7. Enabled WiFi and connected.
8. Set up Google account and other misc settings.
9. Restored a backup that I had made prior to the phone doing the update reboot loop, but was careful to uncheck settings. I did not use Titanium Backup. I used the built in one.
NOTE: This is not my daily driver phone. It is meant to be used as an emergency backup phone in the event that my regular phone (Samsung Galaxy S Series) falls in a canal or gets run over by a truck. (Or City Bus)
So far so good. I will use the phone for the day and check again the following morning to see if it starts the forced update. I will check back here in a few days and let everyone know what the end result was.
My theory is that if the phone does not have a chance via cell data or WiFi to get any FOTA updates prior to me turning off the "automatic system updates" that is in the Developer Options, it will never check in with AT&T's update server.
I am not sure about this, and if someone else knows, please correct the following:
I don't think AT&T "pushes" updates out. At least the type of updates we are talking about. I believe the software in the phone periodically polls an AT&T update server, and "pulls" any update at a schedule time, or time interval. My working theory is that turning off the automatic system updates will disable this automatic check, or polling routine. If it already has an update that it downloaded prior to turning off automatic system updates, its too late.
Thanks for everyone's input on this in advance.
Hi, I have a samsung galaxy tab s2 the 9.7 inches one, but lately some apps have been crashing or having errors, chrome for example throws that snap somethjng wrong, perfect viewer sometimes gets stuck on an image and I cant chnge it, but all menus work, several apps keep crashing as well.
I have it with official firmware, never touched it, its rooted with magisk since before the problems started, apps that use root are file explorer, vanced manger and an app to disable some samsung bloatware.
I dont know how to troubleshoot android, on pc I would check memory and hdds, but theres nothing lkke that kn android that I could find.
I think it could be memory or storage, but everything Ive downloaded or copied/moved hasnt have any problems or errors. Or something is corrupted in the system, or I dont know what else or how to check.
What would you recommend to fix it? Hopefully starting with less drastic, as in less data loss, factory reset, flashing an original rom or somethjng.
The device is aSamsung galaxy tab s2 9.7 with android 7 with lean launcher.
All help is appreciated.
I believe this were an common issue for Android 7 and below !
and you have an old device and android which I believe it's no longer supported by the most of developers.
try to flash any custome roms & kernels if available.
If apps are randomly crashing then the reason might be it's caused by an update of Google's tool called Android System WebView.
Abdullah.Csit said:
I believe this were an common issue for Android 7 and below !
and you have an old device and android which I believe it's no longer supported by the most of developers.
try to flash any custome roms & kernels if available.
Click to expand...
Click to collapse
But it hasnt happened before until now, what would it fix using a custom rom instead of the original?
jwoegerbauer said:
If apps are randomly crashing then the reason might be it's caused by an update of Google's tool called Android System WebView.
Click to expand...
Click to collapse
I had that problem with my phone, my tablet never got that update.
Thanks
Clear system cache...
Wiped dalvik and system cache, but still having the same problems.
Thanks
totopesce said:
Wiped dalvik and system cache, but still having the same problems.
Thanks
Click to expand...
Click to collapse
Try using the stock launcher.
See what apks are running and cached right when this happens is it may give you a clue.
I would completely backup all critical data now.
Android is normally very stable.
Scan with Malwarebytes. If you can't find the root cause, suspect a virus, rootkit etc.
This is rare but can happen.
Karma Firewall can help you to see what's accessing what and how often. It uses almost no battery or resources, freeware, adfree, a near perfect little app.
Cant remove lean launcher it gets stuck in android is starting and it doesnt let me change to stock, installed nova just to check if it was lean and still the same problems.
Installed malwarebytes, had to run the scan several times cause it kept crashing, it completed and it didnt find anything.
Installed karma firewall and will see if I find anything.
Thanks
totopesce said:
Cant remove lean launcher it gets stuck in android is starting and it doesnt let me change to stock, installed nova just to check if it was lean and still the same problems.
Installed malwarebytes, had to run the scan several times cause it kept crashing, it completed and it didnt find anything.
Installed karma firewall and will see if I find anything.
Thanks
Click to expand...
Click to collapse
Figure out how to get the stock launcher back.
Any 3rd party app you can't uninstall is already malware. Check Device Administrators to see if it's registered there. Nova is no saint either.
If you can't resolve it error on the side of caution that it is malware and nuke it. Sometimes you never find out which one it was... getting rid of it is all that matters.
Sorry, what I meant was that after uninstalling it it got stuck in androiid is starting, somehow I lost the stock launcher, so it got stuck with no launcher. Found the launcher that came stock, installed it and uninstalled the other 2.
Apps are still crashing, I deleted all apps that I dont really use.
totopesce said:
Sorry, what I meant was that after uninstalling it it got stuck in androiid is starting, somehow I lost the stock launcher, so it got stuck with no launcher. Found the launcher that came stock, installed it and uninstalled the other 2.
Apps are still crashing, I deleted all apps that I dont really use.
Click to expand...
Click to collapse
Lol, that can crash it for sure.
See if you can find a common apk between the effected apps. Any recent system app updates?
New or uninstalled apps?
A system apk may have gotten corrupted.
Android is pretty good compared to Windows when uninstalling apps but occasionally a poorly designed app will screw it up.
It's just about factory reset time or your equivalent.
If it an old load that's probably best anyway.
I haven't reloaded in almost a year but I'm ready to go at any time.
Takes me about 2 hours to get it back within 99%. All the data I need for a full restore is on my SD card otherwise it would an additional 6-8 hours to restore the SD card data as well.
If you don't have a complete reload plan that saves all your critical data no matter what, implement one now before you get burnt.
Those stories are too common here
Dont remember when it started, cause at first it was one app from a github that was having problems, then yesterday magisk started and when I got that working it all when to hell.
The app that I use most has a backup/restore file that I saved on my sd, what do you use to backup/restore?
I would think that some backup solution could bring the problem back or am I mistaken, like if you fully restore something corrupted it should still be corrupted?
A factory reset could be corrupted as well? I mean after a factory reset, assuming its software, could it still have the same problems?
Though I dont really have any critical data on the tablet its mostly for browsing, youtube and reading comics. Still its a bother to re configure everything xD. IIRC I think its only been factory reset once.
Thanks.
It's unlikely the factory reload image is corrupted.
The current one your using likely is.
Other than apps that allow you to back them up like Poweramp or perhaps bookmarks, most app data I would write off just in case that was connected to the current issues.
None of my database is on internal memory except DCIM and downloads (both I back it up at least monthly). Critical apps like Poweramp are backed up on the SD card as export backup files.
The Poweramp setup would literally take a week to recreate. Most apps you can throw together rather easily.
All the SD card data is then again backed up at least twice to other separate drives.
I will try Samsung Smart Switch to restore home settings and see how it does on the next reset.
If you issues are of unknown origins being conservative about what you allow on the new load could save you more time in the long run.
If you unintentionally import corrupted data you'll end up doing it over again.
Or do so if the reload time isn't that great and is an easy write off for you.
Fun times... especially if the reload doesn't fix it
Did a factory reset and problem solved, took me less time than I thought to get my most used apps ready to go.
Thanks for the help.
totopesce said:
Did a factory reset and problem solved, took me less time than I thought to get my most used apps ready to go.
Thanks for the help.
Click to expand...
Click to collapse
Yay! Success!
And a minty fresh OS load.
Load apps and especially updates over time to see if one these were the cause.
Forced reloads are rare but they happen usually caused by a rogue app screwing up boot or a malware infection. Otherwise you can usually track down the root cause which is preferable to avoid it from happening again.
Lazy techs misuse factory reset a lot
Will do that, install apps just as I need them and try not to instal a bunch at once.
I had a problem with an sd card and sent it to samsung, they did just that factory reset it and gave it back with the same problem, and they dont even let you know so you can back your stuff up, just lucky it was fairly new at the time and I had the sd card with me.
totopesce said:
Will do that, install apps just as I need them and try not to instal a bunch at once.
I had a problem with an sd card and sent it to samsung, they did just that factory reset it and gave it back with the same problem, and they dont even let you know so you can back your stuff up, just lucky it was fairly new at the time and I had the sd card with me.
Click to expand...
Click to collapse
Sammy tech support sucks.
I'm using the Lexar .5 tb V30 card, just format in phone and it's good to go. Zero issues for $64.
Been using it for over a year now. Play movies and music from it all the time from it flawlessly.
Been using Lexar flash cards for over 15 years and all cards are still functional. No failures or card related issues at all. I like that brand a lot.