Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Some more excellent work from
@yshalsager
https://t.me/s/MotoUpdatesTracker?q=KYOTO
Opening the link in your browser will keep the Kyoto filter, as opposed to opening in telegram.
does the moto edge 20 fusion have a different codename than 'kyoto', since that is for moto edge 20 lite?
in another thread someone bricked their edge 20 fusion by flashing a lite edge 20 lite rom and needed to get it repaired under warranty.
i have the edge 20 fusion so i'm trying to be careful to make sure i don't brick it when trying to root it.
edit - nevermind, i was able to unlock the bootloader and from running 'fastboot getvar all' i can confirm this variant is also 'kyoto'.
i have a question about OTA security updates.
i'm in australia, and the march update is just being pushed through. this is the first update i've had since i only purchased this phone new about a month ago.
over the last week or so, the first 2 or 3 times the OTA security update notification came through, it said "this update is not compatible with your software version' or something like that and wouldn't let me update.
but this time, it is giving me the option to update.
my device is rooted with the latest magisk, and using LSposed. can we still do security updates as normal like this OTA?
trevtdogg said:
i have a question about OTA security updates.
i'm in australia, and the march update is just being pushed through. this is the first update i've had since i only purchased this phone new about a month ago.
over the last week or so, the first 2 or 3 times the OTA security update notification came through, it said "this update is not compatible with your software version' or something like that and wouldn't let me update.
but this time, it is giving me the option to update.
my device is rooted with the latest magisk, and using LSposed. can we still do security updates as normal like this OTA?
Click to expand...
Click to collapse
You can download and install, but before you reboot.
Open Magisk and select
Install/ Install to inactive slot (After OTA)
sd_shadow said:
You can download and install, but before you reboot.
Open Magisk and select
Install/ Install to inactive slot (After OTA)
Click to expand...
Click to collapse
thank you!
i remember that from flashing the stock rom before rooting, my phone showed this in the getvar all:
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
Click to expand...
Click to collapse
will the slot b unsuccessful be a problem with this?
and within magisk, do i do the 'magisk install' option or the 'app install' option?
Related
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 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?
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
That's the Android 12 GPS fix it sounds like.
Google Pixel 6 getting 'Introducing Android 12' update
Many Google Pixel 6 series users are confused due to an 'Introducing Android 12' update ahead of Android 13, here is what's happening.
piunikaweb.com
Lughnasadh said:
That's the Android 12 GPS fix it sounds like.
Click to expand...
Click to collapse
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
OTAs are arguably the safest way to update regarding any danger to bricking devices. Any hoopla you may have heard about A13->A12 or A12->A13 bricking is via flashing not OTA updates. You will have to re-root/magisk. Those guides have been (should) updated for a13. But OTA updates within android 12 and to android 13 should not brick your device and should be totally safe. But once you are on android 13, you are on it forever. No downgrading. You can only move forward (for now).
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
pleiotropy said:
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
Click to expand...
Click to collapse
Yeah, that guide is accurate but the "Install to Inactive Slot" method has been hit and miss for some. If you are on a custom kernel you also need to return to stock kernel to make it work as well.
pleiotropy said:
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
Click to expand...
Click to collapse
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Good point. Missed that he was on that.
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Thanks for the info, I will update Magisk and then try it
pleiotropy said:
Thanks for the info, I will update Magisk and then try it
Click to expand...
Click to collapse
Make sure to disable any Magisk mods that may need updating as well, but since you're just making a minor update from one July build to another July build I suspect you'll be ok. But it's still good practice to disable mods when updating to avoid potential bootloops.
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
michaelrager said:
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
Click to expand...
Click to collapse
Did you ever figure this out? Or what happened? I have updates disabled under dev but I got the same notification.
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
tbgakaadan said:
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
Click to expand...
Click to collapse
Take the update. You'll have to root again.
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.
I'm currently on Android 12 with unlocked bootloader and magisk root. This is a cph2417 model. My phone says I'm 70 days out on the update. When the update first came out I saw a bunch of comments saying not to take it but I haven't see much lately.
Has anyone had any success going to 13 and keeping root (if so, how)? Should I stay on 12?
I ended up flashing the full update from an app taken from oxygen updater, and that lost me root, but I just re-rooted right after using same direct install method. I think I kept all my modules, but I could be wrong. It is possible to keep root if you use the app from oxygen updater, I think it's called myapplication2, and then before clicking reboot after update finishes, you go to magisk and install to inactive slot. Then go back to app and reboot.
HutchOven said:
I'm currently on Android 12 with unlocked bootloader and magisk root. This is a cph2417 model. My phone says I'm 70 days out on the update. When the update first came out I saw a bunch of comments saying not to take it but I haven't see much lately.
Has anyone had any success going to 13 and keeping root (if so, how)? Should I stay on 12?
Click to expand...
Click to collapse
Yeah...
If you use the built-in update method via the settings app, the phone reboots automatically before you can re-root via magisk. Then, you must use fastboot to get root back.
However, you can avoid this if you:
Use Oxygen Updater app to download the update.
Use one of OP's local update apps (see below)
BEFORE REBOOTING, use the Magisk App to flash Magisk to the inactive slot.
Reboot.
The following is pulled from the instructions within Oxygen Updater:
"If the system's built-in “Local install” feature doesn't work for whatever reason, or if you're on global/NA firmware, you'll need to use OnePlus' separate app. Choose any, they're all developed & provided by OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk"
JPower123 said:
I ended up..
Click to expand...
Click to collapse
notorious.dds said:
Yeah...
• ttps://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Click to expand...
Click to collapse
Thank you both, I got it to work. Here's what I did for anyone else.
1.Downloaded Oxygen updated from play store.
2. Downloaded the incremental update
3. Used 2nd link above to download the oxygen system update app and changed name to apk (delete .zip and the end) and installed.
4. Used that app to install the update
5. Once installed, before reboot I went to magisk and installed to inactive slot.
6. Reboot and good to go.