I have a G8X running Android 10. Stock ROM or whatever, right from the box. It is, however, a Sprint phone that I overwrote a abl file to run on T Mobile and ATT .
Everything was fine, one day I recieved a Android security update notice, acknowledged it, it downloaded but couldn't or wouldn't install. Now, every day it will occasionally try again to install it, and then it fails again.
How do I stop it? If I go to updates in Settings, it automatically tries again to install this patch and fails. It doesn';t give a number or anything, just a size, 51.41 MB. Do I have to do a hard reset? Or how do I get this update out of trying to install every day...
Related
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
AstroDigital said:
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
Click to expand...
Click to collapse
Install could have failed for a variety of reasons. If you are rooted, or have a custom kernel, or are unencrypted, of there is any modification to the system.
You can sideload the OTA, but really? That's as much work as fastboot flashing the system image.
So, if your bootloader is unlocked, I'd suggest that you just fastboot flash the individual .img files, extracted from the system image.
.... I did a manual install, I have not had much luck with OTAs
Hey guys,
I have my tablet since one week. I love it, all works fine, Xposed offers me OBB move and so on. But now I have a question:
How can I get the new Updates for my Tablet with ROOT/TWRP?I know OTA can't be updated due to TWRP, but is there any way to flash updates dirty?! (like with LineageOS, OxygenOS, ... )
At the moment, if I try to search for new updates, I get following message:
The operating system on your device hase been modified in an unauthorised way. Try downloading softwar updates using Smart Switch on PC or visit a customer service centre.
Maybe someone got an early version of the Tab S3 with early factory Android and can give some enlightenment.
Greetz,
CM
First, this should be posted in the q&a section. You're going to have to flash the upgrade firmware tar in odin. Then re-set up your device and re-root. It's a pita. Google has gotten better at saving your apps and data, which helps, or use something like titanium backup
isn't it enough flashing stock recovery and uninstall supersu via app?
I've been away from Samsung devices for awhile, I've been using Nexus but just got a tab3. I haven't tried this but it's possible that you could flash the update.zip that would be pushed to your device using flashfire. You would probably also be able to retain root and TWRP. Maybe someone with more recent samsung use could confirm that. However, based on the message you're getting the update looks like it won't be pushed to your device. And afik samsung doesn't publish the ota, only the full firmware so someone here would have to capture the ota and post it. Whenever samsung gets around to providing an update we can play around with it and see.
PS, do you have a flashable copy of the stock recovery?
has anyone lost root updating to current this month? i know my v10 became an ad filled, stock navbar, paper weight after it's last forced update.
I'm curious about this as well.
I finally got around to rooting my Stylo 3 Plus for the first time over the weekend, after closely following the developments in this forum for the past 6 months. It took a lot of trial and error and reflashing of TWRP before I got the timing down right, but I finally got it rooted (using Magisk 15.2).
And of course, luck would have it that within a few hours of my rooting success, a new system update notification (which I had never heard of until now!), pops up and asks me to restart to install it. I am using Titanium Backup to force stop the particular Google service involved, which makes the notification go away and I can reboot without it upgrading. But it always come back within 24 hours or so.
Has anyone installed this update yet (MP45010f) and successfully re-rooted? I'm currently using Magisk 15.2 with systemless hosts, Ad-Away, and Xposed with Greenify & MinMinGuard enabled. I would welcome any advice on how to proceed after the update to restore root and continue using Ad-Away, Xposed, etc. Or even how to disable the update notification for good so I can stay on MP45010e a while longer.
eliaslear said:
has anyone lost root updating to current this month?
Click to expand...
Click to collapse
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
yeah thats what i did was revert back to stock so u can update then i update it then re rooted my phone
if you update using the LG Bridge computer program, it will update a rooted phone. but you will need to reroot afterward.
joetbd said:
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
Click to expand...
Click to collapse
Thanks for testing this out. If you don't mind me asking, which method do you use to root? And do you also use Xposed?
To anyone else who might know, does everything Magisk- or Xposed-related get removed by the security updates (frameworks, modules, configs, etc)? Just trying to get an idea how many of my modules I should expect to reinstall and configure from scratch if I decide to update from 10e to 10f.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
Yeah, I thought this was kind of weird too. I've never used LG Bridge to update. The notification just appeared on my phone shortly after rooting.
Is Xposed only for Magisk or can it be used on the rom, if so can I get a link to how to do so
LG Bridge
DM.IDOL said:
root?
Click to expand...
Click to collapse
Im using Magisk 16.1 (no Xposed) and TWRP 3.2.1
I have not run into any issues.
It appears to simply be a security patch update.
I doubt it should cause any new headaches.
The original method still works to reroot and reinstall TWRP.
Using the LG Bridge program is about as easy as an update can be. You install it on your computer, plug your phone into the computer, and click "update" on the computer program. Its all automatic.
I picked up a second hand Galaxy S8 over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization?
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
jwoegerbauer said:
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
Click to expand...
Click to collapse
Thanks, I've heard different in the past. That OTA updates can lock you out of being able to run certain bootloaders for multiboot and such.
bump for input from others
Downloaded one S8 ota zip and checked. According to install-recovery.sh the command and path to fota package is on cache.
So going into recovery and wiping cache should do it.
edit: then again it might write it back on boot... but does it install it right away? IDK. Factory reset?
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
deusfaux said:
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
Click to expand...
Click to collapse
You're rooted so you're failing the pr-OTA block verifications, thus the OTA is failing, is the likely scenario.
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
deusfaux said:
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
Click to expand...
Click to collapse
I normally manually flash updates with fastboot.
Only use OTA update on one or two devices.
You have to restore the original boot image.
Run the update and patch the new boot image with Magisk.
Normally the steps are something like this.
1. Open the Magisk app and restore images.
--- Do not reboot ---
2. Open the OTA Updater
- Download and install the OTA -
--- Do not reboot to continue ---
3. Open the Magisk app and install to inactive slot (after OTA).
4. Switch back to the OTA updater and select reboot to continue.
Cheers.
You could use PixelFlasher to make the process a little easier If you don't want to do everything manually each month.