WARNING: Do not resume FW update if it cancels mid-download - Captivate General

If your download fully cancels in the middle, do not resume the download. When you try to resume - the phone will think you want to resume installation [it thinks the download is complete] and will update the phone with the partial firmware download.
For those phones that were bricked, that is what was said happened to them - myself included.
Now, why would the update not realize the firmware isn't complete and just abort the update is beyond me. Many of us ended up with paperweights from that. Had to go to AT&T to replace the phone last night.

Kinda like when you press check for update and it starts downloading something. No, mf, I just said to check, not download arbitrary files from at&t servers. That's what happened to me.
From a phone on an app

Related

Can new update be stopped?

Sorry to start yet another thread on it... but I didn't want the question to get lost in the shuffle.
I'm rooted, and absolutely do NOT want to run the update. I just got a text message saying an update was going to be coming and when asked to do it to say okay. I've shut down my phone for now... from other experience, when the update tries to be forced... can it be stopped?
Sorry to double post... just a bit surprised no one has answered. I saw the post with the update available to be ran through clockwork, so as soon as my phone said it was connecting to some server (red/white arrow), I shut the sucker down and downloaded the update from the thread in the developers section that is flashable with clockwork. Turned the phone back on, copied over the update and flashed it before the phone could offer me the over air update.
Worked great, so I recommend it to anyone.
Still have the question out there though... to users who got the over air update, were you given any option to stop it or not?
There was a cancel button, but all that did was stop downloading and next time you tried to re-download/continue downloading you would just go straight to install.

[Q] How do I suppress firmware updates?

I got a notification on my phone that there is a software update available for my phone. After reading up on it a bit, I decided it's not worth the hassle to update. I thought I had gone through steps to suppress firmware updates a while back but I guess not. What's the easiest way to suppress this warning? Let me know when you get the chance. Thanks, guys!
Well, a bit of an update, I found the original information on how to suppress OTA updates here:
http://forum.xda-developers.com/showpost.php?p=56693607&postcount=370
As I thought before, I had already gone through this step and disabled it (it was disabled in the hidden menu already). However, the update still seems to have popped up. t tried to auto update this morning but reported back that it suspects my system is rooted so it wasn't able to install. That's good news to a point (at least it didn't screw anything up) but I don't like that it even attempted it without me giving it permission.
Any idea what might have changed? Or is there a difference between an OTA update and a "software update"?
I don't know the answer but I am having the same problem. My phone keeps restarting and giving the error that it wasn't able to install. This actually happened before when I was on 4.X and eventually it bricked my phone and the AT&T store couldn't fix it so they gave me a refurb. It sucked because I didn't have all my photos backed up(I have since fixed that problem.) Now I am having the same issue and I don't want it to brick my phone. I also hate that it restarts automatically...I might need to use my phone for something at the moment. I also have tried the info in the link to disable OTA both phones and neither time has it worked. If anyone can help, please do. Thanks.
The only thing I have ever done and has worked every time is to root and then freeze a file called. "software update" or "update manager". Hope this helps.
I would actually like someone to put together an update.zip that will update us to the latest version without having to go through the hassle of flashing back to stock and what not.
I like the idea of LTE voice calls but not so much that I am willing to go through the work of starting over.
sent from a location using an app
In Titanium Backup (or similar app) find the app call "Software Update 2.3.3.1" and freeze it
That is what solved me receiving software updates and I no longer see the option in the About phone area.

Help! Is my new handset dead / hacked?

Hi folks.
I've just got a new, second hand s7 from a CEX store here in the U.K.
However when it boots up it keeps saying the the logging service has failed (like every couple of mins) and I've also noticed on a reboot it will forget it's been connected to wifi.
Knox keeps saying it's detected unauthorised activity.
There is a firmware update available but it fails during install.
I've tried using smart swap to install the update but it gets stuck at 0% and then looses connection with the handset.
I'm currently downloading firmware to try and install with Odin. But I have to admit if that fails I'm kind of out of my depth.
Any ideas?
I guess I can try and return it to the store but I have no idea what the returns policy is like.
Many thanks
Jason
I would try and return it mate
Sime

H910 OTA update popped up today?

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.

Question Problems with Random Shutdowns and Inability to play certain games.

Hello. Rather new here. I have newly purchased a Red Magic 7 Pro from their Official Website. It hasn't even been 10 minutes since I got it before it started having problems like random shut down and reboots.
I've reached out to their support page now where they've told me to try updating the version of the phone. I've done both online updates and local updates, but neither method worked. I've thought about sending the phone back for a replacement if this continues, but I'd rather see if I can resolve the issue first before resorting to that
Mine is the global version and I've been told the update to download in the US and Asia update 3.14. The current version it's running is 3.12
I've considered rooting the device to see if I can do a true factory reset since their method of resetting it via the phone's settings and getting in its debug menu has done nothing. But it's still under warranty so if they give me the option to return it for a new one I will. Hopefully, if this is busted, it's only this particular phone.
When you got the the phone new did you transfer the data of your old phone?
Yea I was trying to transfer files at the time to my other android.
Pokemonaces said:
Yea I was trying to transfer files at the time to my other android.
Click to expand...
Click to collapse
There was a bug in the beginning i've you transfer files the Cellar data will never connect and turn off on with cause the phone to overheat. But you got a different bug i see. you can only try to update the phone to 3.14 or factory reset without transfer the apps first and update then. Btw ask on Reddit there are more active people.
Reddit link: https://www.reddit.com/r/RedMagic/
Update link: https://help.redmagic.gg/hc/en-us/articles/6360319907865-REDMAGIC-7-Pro\
I've tried updating first before transferring, but I get the same errors on the images above.
Depending on how often it reboots, in some cases it gets stuck on gaming mode and I have to wipe the data via holding down the volume down and power button method.
Some other causes include missing apps as it keeps resetting. The common factors is that certain games fail to download and random reboots.
The reboots happen pretty frequently when I try to update using Wifi. Even if it does go through, I get the update package error or poor signals error even though I have a solid internet connection.
And thanks I'll check out the Reddit page for more solutions there
Pokemonaces said:
I've tried updating first before transferring, but I get the same errors on the images above.
Depending on how often it reboots, in some cases it gets stuck on gaming mode and I have to wipe the data via holding down the volume down and power button method.
Some other causes include missing apps as it keeps resetting. The common factors is that certain games fail to download and random reboots.
The reboots happen pretty frequently when I try to update using Wifi. Even if it does go through, I get the update package error or poor signals error even though I have a solid internet connection.
And thanks I'll check out the Reddit page for more solutions there
Click to expand...
Click to collapse
Hmm can you check your google play system update. There is a bug that hasn't been fixed it can't update so the phone will reboot twice.
The only options is to reflash the software or send it back for a replacement.

Categories

Resources