I recently bought a 1 year old XT1941-4 which had already been rooted with Magisk on Android Pie with the November PPKS29.68-16-36-11 security patch already installed (RETGB). Main reason was I wanted a rooted phone and did not want to have to mess with doing it myself. Phone is rooted perfectly and no issues. However, I started getting notifications that a new OTA is available for December. Initially I disabled these notifications and now I am getting a full screen nag about them and that the software update is unsuccessful. I decided to try the temp uninstall of Magisk procedure to allow the OTA to complete but when I hit restore images I get 'Back up does not exist'.
I thought one of the advantages of Magisk was that it could be temp installed to allow OTAs to complete. I see that mirrors.lolinet.com has the RETGB Dec update PPKS29.68-16-36-13. Can I use this someway to sort the problem out? I am a complete noob about this and have read several threads to find a solution but still not sure what direction to go. Can anyone explain to me step by step what I need to do?
Related
Back story: I recently rooted my Droid Razr (it was my first time rooting an Android phone) and completed it without a hitch. However, the update that was released after I rooted downloaded automatically and I became annoyed with the prompt to install now or later. So I unrooted and installed the update. No problems occurred. Fast forward to this morning. A new update is available (it's been available for about a week now, I'd say) and I go to install it. The phone turns back on and says, "Software update has failed!". I am not currently rooted, I've been too busy to re-root the phone. Now I'd like to install this update. Does anyone have any suggestions on how I'd go about doing this?
Thank you for any replies.
Edit: I apologize in advance if this isn't the appropriate section.
Edit 2: I have another question. Is it possible to update a phone's firmware when they are no longer associated with a carrier. I have an older Android phone I'd like to use as a Wifi only phone for apps and such. Am I able to install updates? It seems like the answer would be no, because the phone wouldn't know where to search for the updates. Perhaps a manual install is available?
Questions belong in Q&A
Hi all, I'm pretty new here. I've been a longtime iPhone/jailbreak user, switched to Android last month and really happy with the freedom of customization this device has afforded me. I've been reading and learning a lot, and I have some questions. I hope you'll be able to help.
I now have a Verizon Galaxy S4. I followed these excellent instructions, and am now rooted on 4.3 (MJ7) and am liking it quite a bit.
But as of yesterday I've started to see alerts about a "Software Update Ready to install."
I asked a friend who has the same phone and he said he updated, and went from 4.3... to 4.3. He couldn't tell what had changed (if anything.)
So here are my questions:
1) What is this new update all about? It seems like it's not 4.4 KitKat, it's just a small revision to 4.3 Jelly Bean. Is there any info out there about what it contains?
2) I know I shouldn't accept the update, as it would make me lose root. And I don't want to lose root, I need it for too many things. So, using Root Browser, I went into /cache/fota and moved "update.zip" to my SD card, thinking it would help. Then I rebooted. After a few minutes, the "Software update available" notification returned. How can I remove this? If I'm not supposed to accept this OTA update, I don't want to be nagged about it. I don't want to accidentally tap it.
3) Is there a way yet to accept this update, without losing root or bricking my device? If so, how?
Thanks for any answers, I appreciate it and am happy to be here.
Use Titanium Backup to freeze the "sdm.apk" and "fwupdate.apk" applications. Or rename those two apps with .bak.
People are reporting taking the update and not losing root here:
http://forum.xda-developers.com/showthread.php?t=2565430
Place SuperSU in "survival mode" before you update and you should still have root afterwards.
Excellent, thanks for then pointers! I will give it a go.
It took a few tries... and a few reboots... but finally, I got it to work. I just got the notification that the update was successful. Sweet! (And, more importantly, I checked with RootChecker and I still have root.) For anyone else following along, the paid version of SuperSU is required in order to be able to invoke "Survival Mode."
I am now running JSS15J.I545VRUEMK2 and I Googled to see these are the changes:
KEY DEVICE ENHANCEMENTS
• Email connectivity has been improved
• Consistent Data roaming in Canada and Mexico
• Device will ‘Power On’ after software update is completed
• Non-Samsung chargers will work correctly with the phone
• Improved data connections while using (enterprise) proxy servers
Click to expand...
Click to collapse
Now, in order to prevent future updates from interrupting me, I went into Titanium Backup and I froze "sdm.apk."
But I can't seem to find the "fwupdate.apk" application. Is there some other name for this?
Thanks very much!
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.
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.
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.